simnova/sharethrift

Executive summary

simnova/sharethrift scores 46 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.

The weakest lens counts most in the score, and here that is Production Readiness, which scores 32 and is rated Weak. Its Dependency Hygiene 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 remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies and to resolve the 32 Low coverage finding(s) in Code Coverage, and if Production Readiness rose to 70, the score would rise from 46 to about 57.

83 findings are critical: 53 in Dependency Vulnerabilities, 13 in Test isolation, eight in Static Analysis (SAST), four in Secrets (history), three in Knowledge Freshness, one in Circular Imports and one in Dependency direction.

Watchdog couldn't measure 4 dimensions in this code, among them Dependency Hygiene, Navigability and Structured logging, so they are left out of the score. The product code is 52,233 lines, which would take an estimated 0.9 person-years, around €130,000, to rebuild.

Code Health 55 Adequate, capped by Nullable reference types Architecture 53 Adequate, capped by Test isolation Maturity 62 Adequate, capped by Documentation accuracy Production Readiness 32 Weak, capped by Dependency Hygiene, Observability, Release Hygiene and Outbound HTTP resilience Security and Compliance 66 Adequate, capped by Static Analysis (SAST), Dependency Vulnerabilities and Supply-chain Provenance & Signing Domain Modelling 100 ★ Exemplary Accessibility 76 Strong Performance 60 Adequate

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

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

Production Readiness 32 · counts for 45%Architecture 53 · counts for 25%Code Health 55 · counts for 14%Performance 60 · counts for 8%Maturity 62 · counts for 4%Security and Compliance 66 · counts for 2%Accessibility 76 · counts for 1%Domain Modelling 100 · counts for 1%

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

Code composition: what the lines of code are

Product code 48%Tests 52%

New since the last survey: 140 findings

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

Boundary Type-Coupling · Cross-context type UserEntityReference (domain → acceptance-api) packages/sthrift-verification/acceptance-api/src/shared/support/domain-test-helpers.ts
Boundary Type-Coupling · Cross-context type UserEntityReference (domain → acceptance-ui) packages/sthrift-verification/acceptance-ui/src/shared/support/domain-test-helpers.ts
Boundary Type-Coupling · Cross-context type UserEntityReference (domain → application-services) packages/sthrift/application-services/src/contexts/listing/item/create.ts
Boundary Type-Coupling · Cross-context type UserEntityReference (domain → persistence) packages/sthrift/persistence/src/datasources/domain/conversation/conversation/conversation.repository.ts
Boundary Type-Coupling · Cross-context type UserEntityReference (domain → persistence) packages/sthrift/persistence/src/datasources/domain/listing/item/item-listing.repository.ts
Boundary Type-Coupling · Cross-context type UserEntityReference (domain → persistence) packages/sthrift/persistence/src/datasources/domain/reservation-request/reservation-request/reservation-request.repository.ts
Secrets (history) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
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
IaC & Container Security · REDACTED
Knowledge Freshness · Orphaned knowledge packages/cellix/service-payment-cybersource/src/index.ts
Knowledge Freshness · Orphaned knowledge packages/sthrift/ui-sharethrift-route-signup/src/components/shared/address-form/countries-mock-data.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/account-plan/account-plan/create.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/account-plan/account-plan/index.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/account-plan/account-plan/query-all.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/account-plan/account-plan/query-by-id.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/account-plan/account-plan/query-by-name.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/account-plan/index.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/appeal-request/index.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/create.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/get-all.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/get-by-id.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/index.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/update-state.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/create.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/get-all.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/get-by-id.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/index.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/update-state.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/conversation/conversation/create.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/conversation/conversation/index.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/conversation/conversation/query-by-id.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/conversation/conversation/query-by-user.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/conversation/conversation/send-message.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/conversation/index.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/listing/index.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/listing/item/cancel.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/listing/item/create.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/listing/item/delete.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/listing/item/index.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/listing/item/query-all.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/listing/item/query-by-id.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/listing/item/query-by-sharer.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/listing/item/query-paged.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/listing/item/unblock.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/listing/item/update.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/reservation-request/index.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/reservation-request/reservation-request/create.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/reservation-request/reservation-request/index.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/reservation-request/reservation-request/query-active-by-listing-id.ts
Import Boundaries · Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/reservation-request/reservation-request/query-active-by-reserver-id-and-listing-id.ts
Large Files · packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/listing-information/listing-information.container.stories.tsx: 1994 lines of code packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/listing-information/listing-information.container.stories.tsx
Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/listing-information/listing-information.container.stories.tsx: 1994 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/listing-information/listing-information.container.stories.tsx
Large Files · packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.container.stories.tsx: 1647 lines of code packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.container.stories.tsx
Large Files · packages/cellix/server-payment-seedwork/src/index.ts: 1292 lines of code packages/cellix/server-payment-seedwork/src/index.ts
Large Files · packages/cellix/service-payment-cybersource/src/index.ts: 1031 lines of code packages/cellix/service-payment-cybersource/src/index.ts
Large Files · packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/listing-information/listing-information.stories.tsx: 950 lines of code packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/listing-information/listing-information.stories.tsx
Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/listing-information/listing-information.stories.tsx: 950 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/listing-information/listing-information.stories.tsx
Large Files · packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/view-listing.container.stories.tsx: 899 lines of code packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/view-listing.container.stories.tsx
Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/view-listing.container.stories.tsx: 899 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/view-listing.container.stories.tsx
Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.container.stories.tsx: 868 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.container.stories.tsx
Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/pages/settings-view.tsx: 764 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/pages/settings-view.tsx
Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/requests-table.container.stories.tsx: 761 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/requests-table.container.stories.tsx
Large Files · packages/sthrift/ui-sharethrift-route-signup/src/components/pages/select-account-type/components/select-account-type.container.stories.tsx: 683 lines of code packages/sthrift/ui-sharethrift-route-signup/src/components/pages/select-account-type/components/select-account-type.container.stories.tsx
Large Files · packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users.stories.tsx: 678 lines of code packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users.stories.tsx
Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-view.container.stories.tsx: 674 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-view.container.stories.tsx
Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.container.stories.tsx: 627 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.container.stories.tsx
Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-reservations/components/reservations-view-active.container.stories.tsx: 549 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-reservations/components/reservations-view-active.container.stories.tsx
Large Files · packages/cellix/service-payment-mock/src/index.ts: 546 lines of code packages/cellix/service-payment-mock/src/index.ts
Large Files · packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.stories.tsx: 496 lines of code packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.stories.tsx
Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-container.stories.tsx: 488 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-container.stories.tsx
Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/components/messages.stories.tsx: 467 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/components/messages.stories.tsx
Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.stories.tsx: 405 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.stories.tsx
Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.tsx: 403 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.tsx
Exception handling · Swallowed exception (empty catch) packages/cellix/serenity-framework/src/cucumber/screenshot-hooks.ts
Exception handling · Swallowed exception (empty catch) packages/cellix/serenity-framework/src/dom/asset-loader-hooks.ts
Exception handling · Swallowed exception (empty catch) REDACTED
Exception handling · Swallowed exception (empty catch) packages/cellix/server-oauth2-seedwork/src/manager.ts

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

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

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 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: [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: [GHSA redacted] REDACTED
Code Duplication · Duplicated block with local edits (49 matched lines × 2 locations) packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.container.tsx
Code Duplication · Duplicated block with local edits (48 matched lines × 2 locations) packages/sthrift/domain/src/domain/contexts/user/personal-user/personal-user-account-profile-billing-subscription.ts
Code Duplication · Duplicated block (46 lines × 2 locations) packages/sthrift/domain/src/domain/contexts/appeal-request/listing-appeal-request/listing-appeal-request.aggregate.ts
Code Duplication · Duplicated block with local edits (41 matched lines × 2 locations) packages/sthrift/persistence/src/datasources/domain/role/admin-role/admin-role.domain-adapter.ts
Code Duplication · Duplicated block (40 lines × 2 locations) packages/cellix/server-payment-seedwork/src/index.ts
Code Duplication · Duplicated block with local edits (38 matched lines × 2 locations) packages/cellix/server-messaging-seedwork/src/routes/participants.ts
Code Duplication · Duplicated block (38 lines × 2 locations) packages/sthrift/persistence/src/datasources/domain/appeal-request/listing-appeal-request/listing-appeal-request.repository.ts
Code Duplication · Duplicated block (37 lines × 2 locations) packages/sthrift-verification/acceptance-api/src/contexts/listing/abilities/listing-types.ts
Code Duplication · Duplicated block (36 lines × 2 locations) packages/sthrift/domain/src/domain/contexts/user/personal-user/personal-user-account-profile.ts
Code Duplication · Duplicated block (35 lines × 2 locations) packages/cellix/service-payment-cybersource/src/index.ts
Code Duplication · Duplicated block (35 lines × 2 locations) packages/sthrift/application-services/src/contexts/user/admin-user/get-all-users.ts
Code Duplication · Duplicated block (35 lines × 2 locations) packages/sthrift/domain/src/domain/contexts/user/admin-user/admin-user-account-profile.ts
Code Duplication · Duplicated block (35 lines × 2 locations) packages/sthrift/domain/src/domain/contexts/user/role/admin-role/admin-role-reservation-request-permissions.ts
Code Duplication · Duplicated block (34 lines × 2 locations) packages/sthrift-verification/acceptance-api/src/contexts/reservation-request/abilities/reservation-request-types.ts
Code Duplication · Duplicated block with local edits (33 matched lines × 2 locations) packages/sthrift/domain/src/domain/iam/guest/guest.passport.ts
Code Duplication · Duplicated block (32 lines × 2 locations) packages/sthrift/domain/src/domain/iam/user/admin-user/admin-user.passport.ts
Code Duplication · Duplicated block with local edits (31 matched lines × 2 locations) packages/sthrift/persistence/src/datasources/readonly/user/admin-user/admin-user.read-repository.ts
Code Duplication · Duplicated block (30 lines × 2 locations) packages/sthrift/persistence/src/datasources/readonly/appeal-request/listing-appeal-request/listing-appeal-request.read-repository.ts
Code Duplication · Duplicated block (29 lines × 2 locations) packages/sthrift/domain/src/domain/contexts/user/role/admin-role/admin-role-conversation-permissions.ts
Code Duplication · Duplicated block (29 lines × 2 locations) packages/sthrift/ui-admin-route-root/src/components/pages/home/components/listings-page.tsx
Code Duplication · Duplicated block (28 lines × 2 locations) packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/update-state.ts
Code Duplication · Duplicated block (28 lines × 2 locations) packages/sthrift/ui-sharethrift-route-root/src/section-layout.tsx
Code Duplication · Duplicated block (27 lines × 3 locations) packages/sthrift/domain/src/domain/contexts/user/personal-user/personal-user-account-profile-location.ts
Code Duplication · Duplicated block (27 lines × 2 locations) packages/sthrift/persistence/src/datasources/domain/conversation/conversation/conversation.domain-adapter.ts
Code Duplication · Duplicated block (27 lines × 2 locations) packages/sthrift/persistence/src/datasources/domain/user/admin-user/admin-user.repository.ts
Code Duplication · Duplicated block (27 lines × 2 locations) packages/sthrift/persistence/src/datasources/readonly/user/personal-user/personal-user.read-repository.ts
Code Duplication · Duplicated block (26 lines × 2 locations) apps/ui-admin/src/main.tsx
Code Duplication · Duplicated block (26 lines × 3 locations) packages/sthrift/domain/src/domain/contexts/user/personal-user/personal-user-account-profile-billing-subscription.ts
Code Duplication · Duplicated block (26 lines × 2 locations) packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-reservations/components/reservations-view-active.container.tsx
Code Duplication · Duplicated block (25 lines × 2 locations) packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.tsx
Code Duplication · Duplicated block with local edits (24 matched lines × 2 locations) packages/sthrift/domain/src/domain/iam/user/admin-user/admin-user.user.passport.ts
Code Duplication · Duplicated block (24 lines × 4 locations) packages/sthrift/persistence/src/datasources/domain/conversation/conversation/conversation.domain-adapter.ts
Code Duplication · Duplicated block (24 lines × 2 locations) packages/sthrift/ui-admin-route-listing-operations/src/components/pages/admin-listing-operations/components/admin-listings-table/admin-listings-table.container.tsx
Code Duplication · Duplicated block (24 lines × 2 locations) packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/view-listing.tsx
Code Duplication · Duplicated block with local edits (23 matched lines × 2 locations) packages/cellix/serenity-framework/src/pages/page-adapter.ts
Code Duplication · Duplicated block (23 lines × 2 locations) packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/get-all.ts
Code Duplication · Duplicated block (23 lines × 2 locations) packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/listing-image-gallery/listing-image-gallery.container.tsx
Code Duplication · Duplicated block (22 lines × 2 locations) packages/cellix/server-messaging-seedwork/src/store.ts
Code Duplication · Duplicated block (22 lines × 2 locations) packages/sthrift/domain/src/domain/iam/user/admin-user/contexts/admin-user.appeal-request.listing-appeal-request.visa.ts
Code Duplication · Duplicated block (22 lines × 2 locations) packages/sthrift/domain/src/domain/iam/user/personal-user/contexts/personal-user.appeal-request.listing-appeal-request.visa.ts
Code Duplication · Duplicated block (22 lines × 3 locations) packages/sthrift/persistence/src/datasources/domain/account-plan/account-plan/account-plan.repository.ts
Code Duplication · Duplicated block (22 lines × 2 locations) packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/pages/settings-view.tsx
Code Duplication · Duplicated block (21 lines × 2 locations) packages/cellix/server-messaging-seedwork/src/store.ts
Code Duplication · Duplicated block (20 lines × 2 locations) packages/cellix/serenity-framework/src/servers/apollo-graphql-test-server.ts
Code Duplication · Duplicated block (20 lines × 3 locations) packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.tsx
Code Duplication · Duplicated block (20 lines × 2 locations) packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-reservations/components/reservations-grid.tsx
Code Duplication · Duplicated block (19 lines × 5 locations) packages/sthrift/domain/src/domain/iam/user/admin-user/contexts/admin-user.appeal-request.listing-appeal-request.visa.ts
Code Duplication · Duplicated block with local edits (19 matched lines × 2 locations) packages/sthrift/persistence/src/datasources/domain/listing/item/item-listing.repository.ts
Code Duplication · Duplicated block (19 lines × 2 locations) packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.tsx
Code Duplication · Duplicated block with local edits (18 matched lines × 2 locations) packages/cellix/server-oauth2-seedwork/src/jwt.ts
Code Duplication · Duplicated block (18 lines × 2 locations) packages/sthrift-verification/acceptance-api/src/contexts/listing/questions/listing-status.ts
Code Duplication · Duplicated block (18 lines × 2 locations) packages/sthrift/graphql/src/schema/types/personal-user.resolvers.ts
Code Duplication · Duplicated block (18 lines × 2 locations) packages/sthrift/ui-admin-route-root/src/components/pages/home/components/hero-section.container.tsx
Code Duplication · Duplicated block with local edits (18 matched lines × 2 locations) packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-card.tsx
Code Duplication · Duplicated block (18 lines × 2 locations) packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-reservations/components/reservations-view-active.container.tsx
Code Duplication · Duplicated block (17 lines × 2 locations) REDACTED
Code Duplication · Duplicated block (17 lines × 3 locations) packages/cellix/server-payment-seedwork/src/index.ts
Code Duplication · Duplicated block (17 lines × 2 locations) packages/sthrift/ui-admin-route-root/src/auth-redirect.tsx
Code Duplication · Duplicated block (17 lines × 3 locations) packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.container.tsx
Code Duplication · Duplicated block (17 lines × 2 locations) packages/sthrift/ui-sharethrift-route-signup/src/components/pages/terms/components/terms-communication-preferences.tsx
Code Duplication · Duplicated block (16 lines × 2 locations) apps/ui-admin/src/config/oidc-config.tsx
Code Duplication · Duplicated block with local edits (16 matched lines × 2 locations) packages/cellix/server-oauth2-seedwork/src/manager.ts
Code Duplication · Duplicated block (16 lines × 2 locations) packages/cellix/ui-core/src/components/molecules/component-query-loader/index.tsx
Code Duplication · Duplicated block with local edits (16 matched lines × 2 locations) packages/sthrift-verification/acceptance-api/src/contexts/listing/tasks/api/create-listing.ts
Code Duplication · Duplicated block (16 lines × 2 locations) packages/sthrift-verification/acceptance-api/src/shared/support/application-services/mock-application-services.ts
Code Duplication · Duplicated block (16 lines × 2 locations) packages/sthrift-verification/acceptance-ui/src/shared/support/domain-test-helpers.ts
Code Duplication · Duplicated block (16 lines × 4 locations) packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/update-state.ts
Code Duplication · Duplicated block (16 lines × 4 locations) packages/sthrift/application-services/src/contexts/listing/item/cancel.ts
Code Duplication · Duplicated block (16 lines × 2 locations) packages/sthrift/domain/src/domain/contexts/reservation-request/reservation-request/reservation-request.aggregate.ts
Code Duplication · Duplicated block (16 lines × 2 locations) packages/sthrift/persistence/src/datasources/readonly/reservation-request/reservation-request/reservation-request.read-repository.ts
Code Duplication · Duplicated block (16 lines × 2 locations) packages/sthrift/ui-shared/src/organisms/login-form.tsx
Code Duplication · Duplicated block (16 lines × 3 locations) packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-card.tsx
Code Duplication · Duplicated block (15 lines × 2 locations) apps/api/src/cellix.ts
Code Duplication · Duplicated block (15 lines × 3 locations) packages/cellix/service-payment-cybersource/src/index.ts
Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) packages/cellix/ui-core/.storybook/preview.tsx
Code Duplication · Duplicated block (15 lines × 2 locations) packages/sthrift/domain/src/domain/contexts/conversation/conversation/conversation.aggregate.ts
Code Duplication · Duplicated block (15 lines × 4 locations) packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.container.tsx
Code Duplication · Duplicated block (15 lines × 2 locations) packages/sthrift/ui-sharethrift-route-signup/src/components/pages/terms/components/terms-communication-preferences.tsx
Code Duplication · Duplicated block (14 lines × 2 locations) REDACTED
Code Duplication · Duplicated block (14 lines × 2 locations) packages/sthrift-verification/acceptance-ui/src/contexts/listing/questions/listing-status.ts
Code Duplication · Duplicated block (14 lines × 7 locations) packages/sthrift/domain/src/domain/contexts/appeal-request/listing-appeal-request/listing-appeal-request.value-objects.ts
Code Duplication · Duplicated block (14 lines × 2 locations) packages/sthrift/domain/src/domain/contexts/user/admin-user/admin-user.aggregate.ts
Code Duplication · Duplicated block (14 lines × 6 locations) packages/sthrift/domain/src/domain/contexts/value-objects.ts
Code Duplication · Duplicated block (14 lines × 4 locations) packages/sthrift/domain/src/domain/iam/user/admin-user/contexts/admin-user.conversation.visa.ts
Code Duplication · Duplicated block (14 lines × 2 locations) packages/sthrift/graphql/src/schema/types/admin-user.resolvers.ts
Code Duplication · Duplicated block (14 lines × 2 locations) packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/pages/settings-view.tsx
Code Duplication · Duplicated block (14 lines × 2 locations) packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing-image-gallery.tsx

Rebuild cost: about €130,000 · Estimate

Cost to rebuild	€43,000 to €220,000, for 724 to 2,298 hours of work, about 0.9 person-years for 1 to 2 engineers
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 46. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size	Medium: 52,233 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.

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

Raises the score by about 5 points · Medium effort · Dependency Hygiene

Resolve the 32 Low coverage finding(s) in Code Coverage — start with REDACTED (2), code-metrics.ts (2), code-quality.ts (2).

Raises the score by about 3 points · Medium effort · Code Coverage

Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.

Raises the score by about 2 points · Medium effort · Test isolation

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 €130,000 to build again, about 0.9 person-years of work. Its weakest lens is Production Readiness, at 32 (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

Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for medium effort. The next survey will show the change in the score.

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

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

711 modules, with 660 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; 671 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 →	11 sthrift.data-sources-mongoose-models.src.models.user.personal-user_model	12 sthrift.domain.src.domain.contexts.account-plan.account-plan_passport	13 sthrift.domain.src.domain.contexts.appeal-request.appeal-request_visa	14 sthrift.domain.src.domain.contexts.conversation.conversation_visa	15 sthrift.domain.src.domain.contexts.listing.listing_visa	16 sthrift.domain.src.domain.contexts.reservation-request.reservation-request_visa	17 sthrift.domain.src.domain.contexts.user	18 sthrift.domain.src.domain.contexts.user.personal-user.personal-user_entity	19 sthrift.domain.src.domain.contexts.user.role.admin-role.admin-role_entity	20 sthrift.domain.src.domain.contexts.user.user_visa	22 sthrift.domain.src.domain.contexts.listing.item.item-listing_entity	23 sthrift.domain.src.domain.contexts.user.admin-user.admin-user_entity	24 sthrift.domain.src.domain.iam.user.personal-user.personal-user_passport-base	25 sthrift.domain.src.domain.contexts.appeal-request.listing-appeal-request.listing-appeal-request_entity	26 sthrift.domain.src.domain.contexts.conversation.conversation.conversation_entity	27 sthrift.domain.src.domain.contexts.listing.listing_passport	28 sthrift.domain.src.domain.contexts.reservation-request.reservation-request.reservation-request_entity	29 sthrift.domain.src.domain.contexts.user.user_passport	31 sthrift.domain.src.domain.contexts.appeal-request.appeal-request_passport	32 sthrift.domain.src.domain.contexts.conversation.conversation_passport	33 sthrift.domain.src.domain.contexts.reservation-request.reservation-request_passport	34 sthrift.domain.src.domain.contexts.passport
1 cellix.api-services-spec.src
2 cellix.arch-unit-tests.src.checks
3 cellix.arch-unit-tests.src.test-suites
4 cellix.serenity-framework.src.pages.page-adapter
5 cellix.serenity-framework.src.servers.test-server
6 cellix.service-messaging-base.src
7 cellix.service-payment-base.src
8 sthrift-verification.arch-unit-tests.src.test-suites
9 sthrift.application-services.src
10 sthrift.data-sources-mongoose-models.src.models.listing.item-listing_model
11 sthrift.data-sources-mongoose-models.src.models.user.personal-user_model
12 sthrift.domain.src.domain.contexts.account-plan.account-plan_passport
13 sthrift.domain.src.domain.contexts.appeal-request.appeal-request_visa
14 sthrift.domain.src.domain.contexts.conversation.conversation_visa
15 sthrift.domain.src.domain.contexts.listing.listing_visa
16 sthrift.domain.src.domain.contexts.reservation-request.reservation-request_visa
17 sthrift.domain.src.domain.contexts.user
18 sthrift.domain.src.domain.contexts.user.personal-user.personal-user_entity
19 sthrift.domain.src.domain.contexts.user.role.admin-role.admin-role_entity
20 sthrift.domain.src.domain.contexts.user.user_visa
21 sthrift.persistence.src.datasources.readonly.mongo-data-source
22 sthrift.domain.src.domain.contexts.listing.item.item-listing_entity							2
23 sthrift.domain.src.domain.contexts.user.admin-user.admin-user_entity									1
24 sthrift.domain.src.domain.iam.user.personal-user.personal-user_passport-base								1
25 sthrift.domain.src.domain.contexts.appeal-request.listing-appeal-request.listing-appeal-request_entity								1			1
26 sthrift.domain.src.domain.contexts.conversation.conversation.conversation_entity							2				2
27 sthrift.domain.src.domain.contexts.listing.listing_passport					1						1
28 sthrift.domain.src.domain.contexts.reservation-request.reservation-request.reservation-request_entity							2				2
29 sthrift.domain.src.domain.contexts.user.user_passport								1	1	1		1
30 sthrift.persistence.src.datasources.domain.conversation.conversation.conversation_repository							1				1
31 sthrift.domain.src.domain.contexts.appeal-request.appeal-request_passport			1											1
32 sthrift.domain.src.domain.contexts.conversation.conversation_passport				1											1
33 sthrift.domain.src.domain.contexts.reservation-request.reservation-request_passport						1											1
34 sthrift.domain.src.domain.contexts.passport		1														1		1	1	1	1
35 sthrift.domain.src.domain.contexts.user.admin-user.admin-user_aggregate									1	1		1										1
36 sthrift.domain.src.domain.contexts.user.personal-user.personal-user_aggregate	3							1		1												1
37 sthrift.domain.src.domain.iam.guest.guest_passport		1														1		1	1	1	1	1
38 sthrift.domain.src.domain.iam.system.system_passport		1														1		1	1	1	1	1
39 sthrift.domain.src.domain.iam.user.admin-user.admin-user_passport		1														1		1	1	1	1	1
40 sthrift.domain.src.domain.iam.user.personal-user.personal-user_passport		1											1			1		1	1	1	1	1

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 55% · Adequate · gated by X5 ·

The Good

D1 · TypeScript Cyclomatic Complexity 7.8 D2 · TypeScript Cognitive Complexity 7.2 D3 · TypeScript God Classes 7.2 D17 · TypeScript Explicit Debt 9.8 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 8.4 R1 · React / TS Type Safety 9.9 R10 · React / TS Code Duplication 8.2 R2 · React / TS Cyclomatic Complexity 9.3 R3 · React / TS Large Files 9.0 R7 · React / TS Dead Code 9.2 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 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0

The Bad

X3 · Repo Exception handling 5.2

The Ugly

X2 · Repo Cancellation propagation 4.0 X5 · Repo Nullable reference types 2.3

At a glance — Architecture · 53% · Adequate · gated by AX8 ·

The Good

D5 · TypeScript Coupling 9.7 D6 · TypeScript Cohesion (LCOM4) 9.8 D7 · TypeScript Architectural Integrity 10.0 D23 · TypeScript Boundary Type-Coupling 9.8 D26 · TypeScript Project Cohesion 8.8 D35 · TypeScript Change Coupling 10.0 AX10 · Repo Code composition 9.2 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 7.1 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 10.0 R9 · React / TS Circular Imports 8.3

The Bad

D22 · TypeScript Internal API Consistency 6.0

The Ugly

AX8 · Repo Test isolation 0.0 R11 · React / TS Import Boundaries 4.4

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

The Good

D15 · TypeScript Churn × Complexity Hotspots 10.0 D16 · TypeScript Bus Factor 9.2 D19 · TypeScript Documentation Quality 9.0 D20 · TypeScript ADR Quality 8.1 D21 · TypeScript Naming Consistency 10.0 D25 · TypeScript ADR Conformance 10.0 M1 · Repo Documentation (README) 9.0 M2 · Repo Architecture documentation 10.0 M3 · Repo Folder & project structure 10.0

The Bad

D34 · TypeScript Knowledge Freshness 6.4

The Ugly

M4 · Repo Documentation accuracy 0.0

At a glance — Readiness · 32% · Weak · gated by R8, P2, P6, P7 ·

The Good

D8 · TypeScript Code Coverage 7.1 D9 · TypeScript Test Distribution 10.0 D10 · TypeScript Test Quality 10.0 D11 · TypeScript Test Reliability 10.0 D13 · TypeScript REDACTED Scanning 10.0 D14 · TypeScript License Compliance 10.0 P1 · Repo CI/CD gates 8.5 P10 · Repo Library API & versioning 10.0 P11 · Repo BDD / executable specs 10.0 R4 · React / TS Test Coverage 9.0 R6 · React / TS Tooling 10.0

The Bad

P4 · Repo Deployment & Rollback 5.0

The Ugly

P2 · Repo Observability 3.0 P3 · Repo Security & performance tooling 4.0 P5 · Repo DR & Backup 4.0 P6 · Repo Release Hygiene 3.0 P7 · Repo Outbound HTTP resilience 3.0 R8 · React / TS Dependency Hygiene 0.0

At a glance — Security · 66% · Adequate · gated by D29, D30, D36 ·

The Good

D31 · TypeScript IaC & Container Security 9.0 D43 · TypeScript Malicious Dependencies 10.0 D44 · TypeScript Platform End-of-Life 10.0 C2 · Repo Access Controls 7.0 S1 · Repo Web-Security Posture 8.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0

The Bad

D28 · TypeScript Secrets (history) 6.0

The Ugly

D29 · TypeScript Static Analysis (SAST) 3.4 D30 · TypeScript Dependency Vulnerabilities 0.0 D36 · TypeScript Supply-chain Provenance & Signing 0.0

At a glance — Domain Modelling · 100% · Exemplary ·

The Good

DM10 · Repo One transaction, one aggregate 10.0 DM6 · Repo Domain ↔ infrastructure boundary 10.0 DM9 · Repo Scattered domain decisions 10.0

At a glance — Accessibility · 76% · Strong ·

The Good

AC1 · Repo Text alternatives 10.0 AC2 · Repo Forms & labels 10.0 AC3 · Repo Page structure 10.0 AC5 · Repo ARIA correctness 10.0 AC6 · Repo Visual & motion safety 7.3

The Ugly

AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 60% · Adequate ·

The Bad

PF3 · Repo Async & latency hygiene 6.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP category	Findings	Severity
A03:2025 — Software Supply Chain Failures	89	High / Critical
A05:2025 — Injection	19	High / Critical
A02:2025 — Security Misconfiguration	10	Medium
A07:2025 — Authentication Failures	5	High / Critical

Roadmap

First, clean up the dependency tree by removing unused packages and moving type- and test-only tools to development dependencies. Next, address the 32 low code coverage findings, prioritizing REDACTED, code-metrics.ts, and code-quality.ts, while also fixing test isolation by ensuring production code does not depend on test projects. Finally, implement structured logging with pino or winston in all runnable modules and maintain a current, versioned changelog for every release.

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

Do this	Helps	Effort	Dimension
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.	+5.1 pts	Medium	Dependency Hygiene
Resolve the 32 Low coverage finding(s) in Code Coverage — start with REDACTED (2), code-metrics.ts (2), code-quality.ts (2).	+3.3 pts	Medium	Code Coverage
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.	+1.7 pts	Medium	Test isolation
Adopt pino (or winston) and log at meaningful points in the services you run.	+1.7 pts	Medium	Observability
Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.	+1.7 pts	Medium	Release Hygiene
Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.	+1.7 pts	Medium	Outbound HTTP resilience
Fix the listed violations: respect the layer/slice order — import only through a slice's public index and never upward into a higher layer (65 rows); move the shared test helper into a source directory production code may depend on (1 row).	+1.4 pts	Medium	Import Boundaries
Enable Dependabot/Renovate or a dependency-review gate.	+1.2 pts	Medium	Security & performance tooling

File quality

Per-file score 0–10 — a quality signature. Of 134 files carrying findings, judged against the Production bar: 1% slop · 27% mixed · 72% near-clean.

File	Score	Band	Worst signal
REDACTED	0.0	Slop	Dependency Vulnerabilities: Critical CVE: REDACTED
REDACTED	4.0	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	4.6	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.6	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	5.1	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.1	Mixed	Dependency Vulnerabilities: High CVE: REDACTED
packages/cellix/service-payment-cybersource/src/index.ts	5.9	Mixed	God Classes: ClassTooLong: ServicePaymentCybersource
packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.tsx	6.0	Mixed	Explicit Debt: TodoComment
packages/sthrift/ui-admin-route-listing-operations/src/components/pages/admin-listing-operations/components/admin-listings-table/admin-listings-table.container.tsx	6.0	Mixed	Explicit Debt: TodoComment
packages/sthrift/ui-shared/src/organisms/listing-banner.tsx	6.0	Mixed	Explicit Debt: TodoComment
REDACTED	6.1	Mixed	IaC & Container Security: Medium IaC: REDACTED
REDACTED	6.3	Mixed	IaC & Container Security: Medium IaC: REDACTED
packages/cellix/mongoose-seedwork/tests/integration/mongo-unit-of-work.integration.test.ts	6.4	Mixed	Explicit Debt: TodoComment
packages/sthrift/graphql/src/schema/types/user-appeal-request.resolvers.ts	6.5	Mixed	Explicit Debt: TodoComment
packages/sthrift/graphql/src/schema/types/listing-appeal-request.resolvers.ts	6.5	Mixed	Explicit Debt: TodoComment
packages/cellix/event-bus-seedwork-node/src/node-event-bus.ts	6.6	Mixed	Explicit Debt: HackComment
packages/cellix/mongoose-seedwork/src/mongoose-seedwork/mongo-unit-of-work.ts	6.7	Mixed	Explicit Debt: TodoComment
packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.container.tsx	6.9	Mixed	Explicit Debt: TodoComment
REDACTED	6.9	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	6.9	Mixed	IaC & Container Security: Medium IaC: REDACTED

How the grades work

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

Critical — 83

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

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

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

Could not be resolved — 4

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. 87 of 94 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 1.0 — 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 — 94 dimensions across the health lenses

D1D2D3D5D6D7D8D9D10D11D13D14D15D16D17D19D20D21D22D23D25D26D28D29D30D31D34D35D36D43D44AC1AC2AC3AC5AC6AC7AX10AX3AX4AX5AX6AX8C2DM10DM6DM9GD1IC1M1M2M3M4P1P10P11P2P3P4P5P6P7PF3R1R10R11R2R3R4R6R7R8R9S1X1X12X13X14X15X16X17X18X19X2X21X22X23X24X25X28X29X3X30X5

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, 734 of 765 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 01a163f9-e783-723e-87c9-0d9b720effc4.

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

Run transparency — what happened this run

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

D11 Test Reliability — 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. Test reliability for the vitest suite in the repository root was NOT MEASURED: the vitest run in the repository root produced no per-test report (⎯⎯⎯⎯⎯⎯⎯ Startup Error ⎯⎯⎯⎯⎯⎯⎯⎯). 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 — 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. Test reliability for the vitest suite in apps/server-messaging-mock/ was NOT MEASURED: the vitest run in apps/server-messaging-mock/ produced no per-test report (⎯⎯⎯⎯⎯⎯⎯ Startup Error ⎯⎯⎯⎯⎯⎯⎯⎯). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 1 shipped Python distribution(s) were read, but the outdated signal needs pypi.org, and no declaration here carries an exact pin to ask about — a floor or a range installs the newest release it admits and cannot be behind one, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — 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. This repository declares REDACTED, but the licence verdict published here was taken over its Python distribution dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `apps/docs/docusaurus.config.ts`, `apps/ui-sharethrift/src/app.stories.tsx`, `packages/cellix/serenity-framework/src/cucumber/world.ts`, `packages/cellix/ui-core/src/components/molecules/component-query-loader/component-query-loader.stories.tsx`, `packages/cellix/ui-core/src/components/molecules/require-auth/require-auth.stories.tsx`, … (+15 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
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 DevServer (dev). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
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.
P1 CI/CD gates — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
R10 Code Duplication — 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. 160 further occurrence(s) are not listed individually; the score already reflects all 200.
R11 Import Boundaries — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 26 further occurrence(s) are not listed individually; the score already reflects all 66.
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. 28 further occurrence(s) are not listed individually; the score already reflects all 68.
X4 Structured logging — 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 JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, 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 (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

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

Per-dimension blind spots

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

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
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.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
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.
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 Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
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 Complexity7.8 / 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 7.8 / 10 · rule-coverage 100% · ceiling Prevented

10 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was router.buildOidcRouter at 57.

router.buildOidcRouter (cyclomatic 57)REDACTED:31

settings-view.SettingsView (cyclomatic 50)packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/pages/settings-view.tsx:67

reservation-request-form.ReservationRequestForm (cyclomatic 29)packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/reservation-request-form.tsx:51

create-listing.CreateListing (cyclomatic 27)packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.tsx:40

all-listings-table.AllListingsTable (cyclomatic 25)packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.tsx:40

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

What to do

Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with router.buildOidcRouter (cyclomatic 57), settings-view.SettingsView (cyclomatic 50). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 7.8 to about 8.5/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.

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

Do you agree with this assessment?

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

17 method(s) exceeded the cognitive complexity threshold of 15; the worst was router.buildOidcRouter at 61.

router.buildOidcRouter (cognitive 61)REDACTED:31

settings-view.SettingsView (cognitive 49)packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/pages/settings-view.tsx:67

reservation-request-form.ReservationRequestForm (cognitive 35)packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/reservation-request-form.tsx:51

create-listing.CreateListing (cognitive 31)packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.tsx:40

verifyManifestData (cognitive 30).github/hooks/shared.mjs:226

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

What to do

Bring the 4 bodies over 30 down to 30 or less in Cognitive Complexity — start with router.buildOidcRouter (cognitive 61), settings-view.SettingsView (cognitive 49), reservation-request-form.ReservationRequestForm (cognitive 35). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 7.2 to about 7.9/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.

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

Do you agree with this assessment?

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

34 god class(es) detected.

FunctionTooLong: index.startMockPaymentServer · ×28packages/cellix/server-payment-seedwork/src/index.ts:34

FileTooLong: REDACTED · ×4packages/cellix/server-payment-seedwork/src/index.ts

ClassTooLong: ServicePaymentCybersourcepackages/cellix/service-payment-cybersource/src/index.ts:31

TooManyMethods: ServicePaymentCybersourcepackages/cellix/service-payment-cybersource/src/index.ts:31

What to do

Resolve the 28 FunctionTooLong finding(s) in God Classes — start with REDACTED, settings-view.tsx, all-listings-table.tsx. — One of this dimension's main actionable groups (28 warning-level).
Resolve the 4 FileTooLong finding(s) in God Classes — start with REDACTED (3), settings-view.tsx. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 ClassTooLong finding(s) in God Classes — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

D5 · Coupling9.7 / 10Stronggated by 2 serious findings✓ Tool-verified

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

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

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

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

48 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 4 module(s) off the main sequence, with abstractness counted on 45 of the 48 (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: @cellix/service-blob-storage · ×2

Off the main sequence: @cellix/server-messaging-seedwork · ×2

What to do

Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D6 · Cohesion (LCOM4)9.8 / 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.8 / 10 · rule-coverage 100% · ceiling Verified

1 of 70 classes have LCOM4 above 3.

Low cohesion: ServicePaymentCybersource (LCOM4 6)packages/cellix/service-payment-cybersource/src/index.ts:31

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).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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: 12 by analyzers, 2 by tests. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).

✓ On the Gold path — maintain.

Detailed fixes: d7_recommendation.md.

Do you agree with this assessment?

D8 · Code Coverage7.1 / 10Strong✓ Tool-verified

What it measures: How much of the code is actually exercised by tests.

Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.

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

Line coverage 35.0% — 32 file(s) below 50%. Measured from the JavaScript/TypeScript suite (vitest in the repository root: not run; vitest in apps/docs/: not run; vitest in apps/server-messaging-mock/: not run; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in apps/server-oauth2-mock/; vitest in apps/ui-sharethrift/: not run; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/cellix/arch-unit-tests/; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/cellix/domain-seedwork/; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/cellix/event-bus-seedwork-node/; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/cellix/mongoose-seedwork/; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/cellix/serenity-framework/; vitest in packages/cellix/service-messaging-mock/: not run; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in packages/cellix/service-messaging-twilio/).

Low coverage: packages/cellix/arch-unit-tests/src/checks/application-services-conventions.ts · ×32packages/cellix/arch-unit-tests/src/checks/application-services-conventions.ts:1

What to do

Resolve the 32 Low coverage finding(s) in Code Coverage — start with REDACTED (2), code-metrics.ts (2), code-quality.ts (2). — One of this dimension's main actionable groups (32 warning-level).

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

Do you agree with this assessment?

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

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

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

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

538 test methods: 525 unit, 13 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 538 `it`/`test` case(s) across 312 test file(s) declaring at least one; its tier split is read from package names and paths only.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

Mock-dominated test: starts infrastructure, validates state, creates the cast, and resets during cleanuppackages/cellix/serenity-framework/src/cucumber/world.test.ts:6

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests pass reliably, with no flakiness.

Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.

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

0 flaky across 1 measured tier(s). JavaScript/TypeScript (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in apps/docs/ (15 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in apps/server-messaging-mock/; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in apps/server-oauth2-mock/ (11 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in apps/ui-sharethrift/ (0 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/cellix/arch-unit-tests/ (9 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/cellix/domain-seedwork/ (93 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/cellix/event-bus-seedwork-node/ (93 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/cellix/mongoose-seedwork/ (107 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/cellix/serenity-framework/ (31 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/cellix/service-messaging-mock/ (1 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/cellix/service-messaging-twilio/ (14 tests)): measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

Do you agree with this assessment?

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

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

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

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

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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 1 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 1 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (0 reached that way). Requirements it states ONLY under an extra, a PEP 735 dependency group, a Poetry dev group or a dev-named requirements file are excluded: pip does not install any of them for a consumer. ★ This repository commits no dependency lockfile that this pass reads, so each licence is the one PyPI publishes for the distribution's CURRENT release rather than for a pinned version. ★ COVERAGE OF THIS VERDICT: it grades this repository's Python distribution dependencies and nothing else. The repository also declares REDACTED, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots10.0 / 10Stronggated by 1 serious finding✓ 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

Top hotspots: packages/sthrift-verification/e2e-tests/src/contexts/listing/tasks/create-listing.ts (2×18=36)

Hotspot: packages/sthrift-verification/e2e-tests/src/contexts/listing/tasks/create-listing.tspackages/sthrift-verification/e2e-tests/src/contexts/listing/tasks/create-listing.ts:21

What to do

Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with create-listing.ts. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

D16 · Bus Factor9.2 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

22 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/cellix/service-payment-cybersource/src/index.ts. Counted over 282 of the 1031 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1 · ×3

Further sole-owners (lower concentration)

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D17 · Explicit Debt9.8 / 10Stronggated by 48 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

48 deducted task-comment markers across 51492 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 · ×44packages/cellix/domain-seedwork/src/domain-seedwork/child-entity.ts:1

HackComment · ×4packages/cellix/event-bus-seedwork-node/src/node-event-bus.ts:143

What to do

Resolve the 44 TodoComment finding(s) in Explicit Debt — start with mongo-unit-of-work.integration.test.ts (8), user-appeal-request.resolvers.ts (6), listing-appeal-request.resolvers.ts (6). — One of this dimension's main actionable groups (44 warning-level).
Resolve the 4 HackComment finding(s) in Explicit Debt — start with node-event-bus.ts (4). — One of this dimension's main actionable groups (4 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 QualityExemplary◐ 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 Exemplary / 10 · rule-coverage 100% · ceiling Documented

The documentation is comprehensive and well-structured for a monorepo seedwork set: each package README documents its own directory (packages/cellix/mongoose-seedwork/ through packages/cellix/test-utils/) rather than the repository as a whole, with clear purpose, prerequisites, install/build steps, usage examples, an architecture folder of 52 markdown docs, and licensing. The visible content is exemplary for a seedwork set — no single document lacks installation, usage, or overview. (14 of 25 sampled documents could not be assessed: 1 of 2 evaluation groups failed.)

✓ On the Gold path — maintain.

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 38 ADR(s) individually; mean quality 8.1/10 (consistently complete and clear). 5 flagged with a specific gap.

Context/problem and consequences/trade-offs fall below the clip marker (only Control Classification and a partial review-process architecture are shown)apps/docs/docs/security-requirements/0004-listing-appeal-review.md

No problem statement or explicit decision: the body is a classification dump listing assessment type, coverage, status, and compensating controls with no context/problem and no decision (e.g. adopt CodeQL vs SonarCloud) statedapps/docs/docs/threat-assessments/0001-code-ql.md

No explicit Decision statement (what EdgeScan will do or deliver) and no consequences/trade-offs section are visible before the clip markerapps/docs/docs/threat-assessments/0002-edgescan.md

No explicit decision (what Dependabot will do or not do) is present; only status/pending is declaredapps/docs/docs/threat-assessments/0003-github-dependabot.md

No explicit decision (when REDACTED Scanning will be implemented) and consequences/trade-offs are not visible in the excerptapps/docs/docs/threat-assessments/0005-secret-scanning.md

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

What to do

Resolve the 1 Context/problem and consequences/trade-offs fall below the clip marker… finding(s) in ADR Quality — start with 0004-listing-appeal-review.md. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 No problem statement or explicit decision finding(s) in ADR Quality — start with 0001-code-ql.md. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 No explicit Decision statement (what EdgeScan will do or deliver) and no… finding(s) in ADR Quality — start with 0002-edgescan.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 ConsistencyAdequate◐ 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 Adequate / 10 · rule-coverage 100% · ceiling Verified

4 API inconsistencies across 74 exposed types.

Inconsistent lifecycle method signatures across TestServer implementations. `resetForScenario` returns `Promise<void> | void` in the base interface, but specific implementations like `MongoMemoryProcessTestServer` and `MongoMemoryTestServer` return `Promise<void>`. This creates ambiguity for consumers regarding whether they must await the result.

Inconsistent return type for `startUp`. The return type is a complex generic exclusion (`Promise<Exclude<T, ServiceBase>>`) which is likely intended to enforce that the instance is initialized, but the syntax varies slightly (spacing) and the type complexity is high. More importantly, `ServiceMessagingMock` and `ServiceMessagingTwilio` share this pattern, but `ServicePaymentCybersource` and `ServicePaymentMock` also share it. However, `TestServer` implementations use `start(): Promise<void>`. The inconsistency lies between the `Service*` classes (which return the instance for chaining or type narrowing) and the `TestServer` classes (which return void). While this might be intentional, it forces consumers to handle the return value differently depending on the service type.

Redundant factory methods. `GherkinDataTable` has both a constructor and a static `from` method that take the exact same argument (`DataTable`) and return the same type. This offers no benefit and increases API surface unnecessarily.

Ambiguous method naming. `unmount` and `discard` are both void methods on `RenderInDom`. It is unclear if they perform the same action (cleanup) or if `discard` implies a different semantic (e.g., ignoring errors vs. standard cleanup). If they do the same thing, it is a duplicate. If they differ, the names are not distinct enough to convey the difference.

What to do

Resolve the 1 Inconsistent lifecycle method signatures across TestServer… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Inconsistent return type for `startUp`. The return type is a complex… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Redundant factory methods. `GherkinDataTable` has both a constructor and… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

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

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

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

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

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

6 domain type(s) cross context boundaries across 51 contexts.

Cross-context type UserEntityReference (domain → persistence) · ×3packages/sthrift/persistence/src/datasources/domain/conversation/conversation/conversation.repository.ts:69

Cross-context type UserEntityReference (domain → acceptance-api)packages/sthrift-verification/acceptance-api/src/shared/support/domain-test-helpers.ts:42

Cross-context type UserEntityReference (domain → acceptance-ui)packages/sthrift-verification/acceptance-ui/src/shared/support/domain-test-helpers.ts:66

Cross-context type UserEntityReference (domain → application-services)packages/sthrift/application-services/src/contexts/listing/item/create.ts:5

What to do

Resolve the 3 Cross-context type UserEntityReference (domain → persistence) finding(s) in Boundary Type-Coupling — start with conversation.repository.ts, item-listing.repository.ts, reservation-request.repository.ts. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 Cross-context type UserEntityReference (domain → acceptance-api) finding(s) in Boundary Type-Coupling — start with domain-test-helpers.ts. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Cross-context type UserEntityReference (domain → acceptance-ui) finding(s) in Boundary Type-Coupling — start with domain-test-helpers.ts. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d23_recommendation.md · top locations in Appendix A, every location in findings.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

2 conform / 0 violate across 38 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

3 of 49 build units (npm) flagged as possibly oversized/incoherent.

Split packages/sthrift/domain

Split packages/sthrift/persistence

Split packages/sthrift/ui-sharethrift-route-root

What to do

Resolve the 1 Split packages/sthrift/domain finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Split packages/sthrift/persistence finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Split packages/sthrift/ui-sharethrift-route-root 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)6.0 / 10Adequate✓ 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 6.0 / 10 · rule-coverage 100% · ceiling Documented

4 finding(s): 0 critical, 4 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 3 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 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)3.4 / 10Weak✓ Tool-verified

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

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

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

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

19 finding(s): 0 critical, 8 high, 11 medium, 0 low. 5 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 22 file(s) — `apps/docs/docusaurus.config.ts` (line 76, line 158), `apps/ui-sharethrift/src/app.stories.tsx` (line 77), `packages/cellix/serenity-framework/src/cucumber/world.ts` (lines 71–76, lines 84–85, line 88), `packages/cellix/serenity-framework/src/servers/apollo-graphql-test-server.ts` (line 15), `packages/cellix/ui-core/src/components/molecules/component-query-loader/component-query-loader.stories.tsx` (line 9), … (+17 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.

REDACTED

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

What to do

Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 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 5 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 (5 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

85 finding(s): 8 critical, 45 high, 29 medium, 3 low.

REDACTED

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

What to do

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

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

Do you agree with this assessment?

D31 · IaC & Container Security9.0 / 10Stronggated by 10 serious findings✓ Tool-verified

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

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

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

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

REDACTED

What to do

Resolve the 10 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (7), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (10 warning-level).

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

Do you agree with this assessment?

D34 · Knowledge Freshness6.4 / 10Adequate✓ 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 6.4 / 10 · rule-coverage 100% · ceiling Documented

100 of 282 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/cellix/service-payment-cybersource/src/index.ts. Counted over 282 of the 1031 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledge · ×3packages/cellix/service-payment-cybersource/src/index.ts:1

Orphaned file · ×97packages/cellix/service-payment-mock/src/index.ts:1

Further orphaned files (smaller)

What to do

Resolve the 97 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (5), cellix.ts, settings-view.container.stories.tsx. — One of this dimension's main actionable groups (97 recommendation-level).
Resolve the 3 Orphaned knowledge finding(s) in Knowledge Freshness — start with REDACTED, countries-mock-data.ts, all-listings-table.container.stories.tsx. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D35 · Change Coupling10.0 / 10Stronggated by 2 serious findings✓ Tool-verified

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

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

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

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

Strongest change-coupling: message-thread.tsx↔conversations-main.tsx 64%; listing-information.container.tsx↔view-listing.container.tsx 55%

Change coupling: message-thread.tsx ↔ conversations-main.tsx · ×2packages/sthrift/ui-shared/src/organisms/message-thread.tsx:1

What to do

Resolve the 2 Change coupling finding(s) in Change Coupling — start with message-thread.tsx, listing-information.container.tsx. — One of this dimension's main actionable groups (2 warning-level).

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

Do you agree with this assessment?

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

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

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

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

0/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).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

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

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 dependency in any ecosystem this repository declares is published as malicious.

✓ 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 0 platform declaration(s) and 1 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 & labels10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

AC3 · Page structure10.0 / 10Exemplary○ Nothing flagged

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.

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 safety7.3 / 10Strong✓ 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.

This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade. — packages/sthrift/ui-shared/src/organisms/listing-information.tsx:27
`.sharer, .sharerIcon` sets color: #fefdfa on background-color: #3f8176 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — packages/sthrift/ui-shared/src/styles/theme.css:352
`.imageContainer` 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. — packages/sthrift/ui-shared/src/molecules/listing-card/listing-card.module.css:20
`.remove-image-button` moves (`transition: background 0.3s ease, transform 0.3s ease`) 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. — packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.overrides.css:120
`.ant-btn-primary` moves (`transition: transform 0.18s 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. — packages/sthrift/ui-shared/src/styles/theme.css:119
`.sidebar` moves (`transition: transform 0.3s cubic-bezier(0.4, 0, 0.2, 1)`) 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. — packages/sthrift/ui-shared/src/molecules/navigation/navigation.module.css:147

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

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

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

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

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

What to do

Enforce accessibility in the toolchain you already use: enable Biome's a11y rule group in your biome.json `linter.rules` (it is off whenever `recommended` is false and the group is unlisted), then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.

Do you agree with this assessment?

AX10 · Code composition9.2 / 10Exemplary✓ 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.

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 direction7.1 / 10Strong✓ 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.

`@sthrift/application-services` is a Application project but references `@sthrift/persistence`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — packages/sthrift/application-services/package.json:29

What to do

Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion).

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.

`PaymentService` declares 18 required operations: `generatePublicKey`, `createCustomerProfile`, `getCustomerProfile`, `addCustomerPaymentInstrument`, `getCustomerPaymentInstrument`, `getCustomerPaymentInstruments`, `deleteCustomerPaymentInstrument`, `updateCustomerPaymentInstrument`, `processPayment`, `processRefund`, `getSuccessOrLatestFailedTransactionsByReferenceId`, `createPlan`, `listOfPlans`, `getPlan`, `createSubscription`, `updatePlanForSubscription`, `listOfSubscriptions`, `suspendSubscription`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/cellix/service-payment-base/src/index.ts:3

What to do

Split fat interfaces into focused role-interfaces so clients depend only on what they use.

Do you agree with this assessment?

AX8 · Test isolation0.0 / 10Critical✓ 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.

`@apps/api` (production) references the test project `@cellix/api-services-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — apps/api/package.json:27
`@apps/api` (production) references the test project `@sthrift/context-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — apps/api/package.json:32
`@cellix/service-messaging-base` (production) references the test project `@cellix/api-services-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/cellix/service-messaging-base/package.json:23
`@cellix/service-messaging-mock` (production) references the test project `@cellix/api-services-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/cellix/service-messaging-mock/package.json:21
`@cellix/service-messaging-twilio` (production) references the test project `@cellix/api-services-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/cellix/service-messaging-twilio/package.json:21
`@cellix/service-mongoose` (production) references the test project `@cellix/api-services-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/cellix/service-mongoose/package.json:27
`@cellix/service-otel` (production) references the test project `@cellix/api-services-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — REDACTED:28
`@cellix/service-payment-base` (production) references the test project `@cellix/api-services-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/cellix/service-payment-base/package.json:22
`@cellix/service-payment-cybersource` (production) references the test project `@cellix/api-services-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — REDACTED:20
`@cellix/service-payment-mock` (production) references the test project `@cellix/api-services-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/cellix/service-payment-mock/package.json:20
`@cellix/service-token-validation` (production) references the test project `@cellix/api-services-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/cellix/service-token-validation/package.json:25
`@sthrift/application-services` (production) references the test project `@sthrift/context-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/sthrift/application-services/package.json:27
`@sthrift/persistence` (production) references the test project `@cellix/test-utils`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — packages/sthrift/persistence/package.json:36

What to do

Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.

Do you agree with this assessment?

C2 · Access Controls7.0 / 10Strong✓ Tool-verified

Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.

Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.

Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.

What to do

Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.

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?

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?

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?

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 shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — packages/cellix/service-payment-cybersource/src/index.ts:1077, packages/cellix/service-payment-cybersource/src/index.ts:1109

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

`listOfPlans` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — packages/cellix/service-payment-cybersource/src/index.ts:1077
`listOfSubscriptions` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — packages/cellix/service-payment-cybersource/src/index.ts:1109
`shutDown` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/cellix/service-blob-storage/src/index.ts:80

What to do

Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
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)9.0 / 10Exemplary✓ Tool-verified

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

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

What to do

Add a README to the 27 of 55 project(s) that lack one — worth up to 1 pts.

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.

What to do

Grow the ADR log (currently 40) — reach 50 to raise the maturity tier; document significant decisions as they're made.

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.

CONTRIBUTING.md names `listing-reservation.aggregate.ts`, but no file or folder `listing-reservation.aggregate.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. — CONTRIBUTING.md:99
CONTRIBUTING.md names `.aggregate.ts`, but no file or folder `.aggregate.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. — CONTRIBUTING.md:100
CONTRIBUTING.md names `.entity.ts`, but no file or folder `.entity.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. — CONTRIBUTING.md:101
CONTRIBUTING.md names `cellix/service-messaging`, but no file or folder `cellix/service-messaging` 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. — CONTRIBUTING.md:123
CONTRIBUTING.md names `sthrift/service-messaging-twilio`, but no file or folder `sthrift/service-messaging-twilio` 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. — CONTRIBUTING.md:124
CONTRIBUTING.md names `sthrift/service-messaging-mock`, but no file or folder `sthrift/service-messaging-mock` 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. — CONTRIBUTING.md:124
CONTRIBUTING.md links to `./packages/sthrift/service-sendgrid/src/features/`, but `packages/sthrift/service-sendgrid/src/features` 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. — CONTRIBUTING.md:142
readme.md links to `./packages/sthrift/service-mongoose/package.json`, but `packages/sthrift/service-mongoose/package.json` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — readme.md:123
readme.md runs `pnpm run sourcery:review # Review changed files`, but no REDACTED declares a `sourcery:review` 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.md:236
apps/docs/README.md documents the environment variable `USE_SSH`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — apps/docs/README.md:32
apps/server-messaging-mock/README.md names the package `@cellix/messaging`, but no REDACTED of the workspace declares or depends on it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — apps/server-messaging-mock/README.md:27
.agents/skills/vercel-react-best-practices/README.md names `area-description.md`, but no file or folder `area-description.md` 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. — .agents/skills/vercel-react-best-practices/README.md:10
.agents/skills/vercel-react-best-practices/README.md runs `pnpm validate`, but no REDACTED declares a `validate` 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. — .agents/skills/vercel-react-best-practices/README.md:30
.agents/skills/vercel-react-best-practices/README.md runs `pnpm extract-tests`, but no REDACTED declares a `extract-tests` 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. — .agents/skills/vercel-react-best-practices/README.md:35
packages/cellix/domain-seedwork/readme.md names Node.js 22, but the repository declares engines `>=18.0`. 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. — packages/cellix/domain-seedwork/readme.md:7
packages/cellix/domain-seedwork/readme.md links to `./src/passport-seedwork/README.md`, but `packages/cellix/domain-seedwork/src/passport-seedwork/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. — packages/cellix/domain-seedwork/readme.md:11
packages/cellix/mongoose-seedwork/readme.md names Node.js 22, but the repository declares engines `>=18.0`. 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. — packages/cellix/mongoose-seedwork/readme.md:7
packages/cellix/mongoose-seedwork/readme.md installs `@cellix/data-sources-mongoose` (`npm i -w @cellix/data-sources-mongoose`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/cellix/mongoose-seedwork/readme.md:15
packages/cellix/server-messaging-seedwork/README.md names `src/seed-data.ts`, but no file or folder `src/seed-data.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. — packages/cellix/server-messaging-seedwork/README.md:27
packages/cellix/service-messaging-mock/README.md names the package `@cellix/messaging`, but no REDACTED of the workspace declares or depends on it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/cellix/service-messaging-mock/README.md:29
packages/cellix/service-messaging-twilio/README.md names the package `@cellix/messaging`, but no REDACTED of the workspace declares or depends on it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/cellix/service-messaging-twilio/README.md:36
packages/cellix/service-otel/readme.md installs `service-otel` (`npm i -w service-otel @opentelemetry/sdk-node@^0.57.2`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/cellix/service-otel/readme.md:38
packages/cellix/service-otel/readme.md installs `@opentelemetry/auto-instrumentations-node` (`npm i -w service-otel @opentelemetry/auto-instrumentations-node@^0.56.0`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/cellix/service-otel/readme.md:46
packages/cellix/service-otel/readme.md installs `@tsconfig/node20` (`npm i -D -w service-otel @tsconfig/node20`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/cellix/service-otel/readme.md:57
packages/cellix/service-otel/readme.md installs `@tsconfig/node-ts` (`npm i -D -w service-otel @tsconfig/node-ts`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/cellix/service-otel/readme.md:58
packages/sthrift-verification/e2e-tests/README.md runs `pnpm run test:e2e:deployed`, but no REDACTED declares a `test:e2e:deployed` 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. — packages/sthrift-verification/e2e-tests/README.md:18
packages/sthrift-verification/e2e-tests/README.md runs `pnpm run test:acceptance:e2e`, but no REDACTED declares a `test:acceptance:e2e` 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. — packages/sthrift-verification/e2e-tests/README.md:27
packages/sthrift-verification/e2e-tests/README.md runs `pnpm run test:acceptance:e2e:deployed`, but no REDACTED declares a `test:acceptance:e2e:deployed` 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. — packages/sthrift-verification/e2e-tests/README.md:28
packages/sthrift-verification/e2e-tests/README.md documents the environment variable `E2E_DEPLOYED`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/sthrift-verification/e2e-tests/README.md:35
packages/sthrift-verification/e2e-tests/README.md documents the environment variable `E2E_API_URL`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/sthrift-verification/e2e-tests/README.md:36
packages/sthrift-verification/e2e-tests/README.md documents the environment variable `E2E_UI_URL`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/sthrift-verification/e2e-tests/README.md:37
packages/sthrift-verification/e2e-tests/README.md documents the environment variable `E2E_ACCESS_TOKEN`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/sthrift-verification/e2e-tests/README.md:38
packages/sthrift-verification/e2e-tests/README.md documents the environment variable `E2E_IGNORE_HTTPS_ERRORS`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/sthrift-verification/e2e-tests/README.md:39
packages/sthrift-verification/e2e-tests/README.md documents the environment variable `E2E_SKIP_UI_LOGIN`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/sthrift-verification/e2e-tests/README.md:40
packages/sthrift/domain/tests/acceptance/README.md names `cucumber-report.html`, but no file or folder `cucumber-report.html` 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. — packages/sthrift/domain/tests/acceptance/README.md:56
packages/sthrift/domain/tests/acceptance/README.md names `cucumber-report.json`, but no file or folder `cucumber-report.json` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/sthrift/domain/tests/acceptance/README.md:57
packages/cellix/ui-core/src/components/molecules/README.md links to `../../../../../.github/instructions//ui/container-components.instructions.md`, but `packages/.github/instructions/ui/container-components.instructions.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. — packages/cellix/ui-core/src/components/molecules/README.md:18

What to do

Reconcile the README with reality: CONTRIBUTING.md names `listing-reservation.aggregate.ts`, but no file or folder `listing-reservation.aggregate.ts` exists; CONTRIBUTING.md names `.aggregate.ts`, but no file or folder `.aggregate.ts` exists; CONTRIBUTING.md names `.entity.ts`, but no file or folder `.entity.ts` exists; CONTRIBUTING.md names `cellix/service-messaging`, but no file or folder `cellix/service-messaging` exists; CONTRIBUTING.md names `sthrift/service-messaging-twilio`, but no file or folder `sthrift/service-messaging-twilio` exists.

Do you agree with this assessment?

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

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

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

What to do

Run the test suite in CI via an explicit runner step (`pnpm test` for the toolchain this pipeline already uses) and gate merges on it.

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?

P11 · BDD / executable specs10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether behaviour is captured as executable Gherkin specifications (a plus for shared understanding) — only assessed when a BDD framework is present.

Method: Filesystem scan: BDD framework presence (SpecFlow, Gherkin files) when a project references a BDD tool. Exhaustive, deterministic.

Do you agree with this assessment?

P2 · Observability3.0 / 10Weak✓ 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.

No logging call was found in the 882 JavaScript/TypeScript production file(s) this check read across 54 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.

What to do

Adopt pino (or winston) and log at meaningful points in the services you run.

Do you agree with this assessment?

P3 · Security & performance tooling4.0 / 10Weak✓ Tool-verified

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

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

What to do

Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

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

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

What to do

Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where Watchdog can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.

Do you agree with this assessment?

P5 · DR & Backup4.0 / 10Weak✓ 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.

What to do

Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
No persistence guard on critical data stores — use Docker named volumes (or your orchestrator's persistent-volume equivalent) so the data store can't be wiped by a container recreate (or, in cloud, set purge-protection / soft-delete / prevent_destroy).

Do you agree with this assessment?

P6 · Release Hygiene3.0 / 10Weak✓ Tool-verified

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

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

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

What to do

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

Do you agree with this assessment?

P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

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

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

`https.request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — build-pipeline/scripts/check-sonar-quality-gate.cjs:54
`http.request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — build-pipeline/scripts/local-https-proxy.js:97

What to do

Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.

Do you agree with this assessment?

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

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

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

`fs.existsSync` in `checkFrontendArchitecture` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×6) — packages/cellix/arch-unit-tests/src/checks/frontend-architecture.ts:21, packages/cellix/arch-unit-tests/src/checks/frontend-architecture.ts:24, packages/cellix/arch-unit-tests/src/checks/frontend-architecture.ts:27, …
`mkdirSync` in `callback to After` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/cellix/serenity-framework/src/cucumber/screenshot-hooks.ts:41
`readFileSync` in `callback to After` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/cellix/serenity-framework/src/cucumber/screenshot-hooks.ts:51
`fs.existsSync` in `sendEmail` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/cellix/service-sendgrid/src/sendgrid.ts:45
`fs.mkdirSync` in `sendEmail` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/cellix/service-sendgrid/src/sendgrid.ts:45
`fs.writeFileSync` in `sendEmail` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/cellix/service-sendgrid/src/sendgrid.ts:49

What to do

TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.

Do you agree with this assessment?

R1 · Type Safety9.9 / 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 Duplication8.2 / 10Strong✓ 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.

52 duplicated blocks under packages/sthrift/ have copies in at least two of the sibling directories application-services, domain, graphql, persistence, ui-admin-route-listing-operations, ui-admin-route-root (+6 more sibling(s) not listed) — 37 of them are reported below, and 15 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 52 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 52 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 52 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/sthrift/ui-admin-route-root/src/components/pages/home/components/listings-page.container.tsx:1
21 duplicated blocks under packages/sthrift/persistence/src/datasources/domain/ have copies in at least two of the sibling directories account-plan, appeal-request, conversation, listing, reservation-request, role (+1 more sibling(s) not listed) — 8 of them are reported below, and 13 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 21 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 21 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 21 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/sthrift/persistence/src/datasources/domain/role/admin-role/admin-role.domain-adapter.ts:27
16 duplicated blocks under packages/sthrift/application-services/src/contexts/ have copies in at least two of the sibling directories account-plan, appeal-request, conversation, listing, reservation-request, user — 9 of them are reported below, and 7 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 16 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 16 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 16 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/sthrift/application-services/src/contexts/listing/item/cancel.ts:4
13 duplicated blocks under packages/sthrift/domain/src/domain/contexts/ have copies in at least two of the sibling directories account-plan, appeal-request, conversation, listing, reservation-request, user — 4 of them are reported below, and 9 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 13 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/sthrift/domain/src/domain/contexts/conversation/conversation/conversation.aggregate.ts:155
11 duplicated blocks under packages/ have copies in at least two of the sibling directories cellix, sthrift, sthrift-verification — 8 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 11 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/cellix/serenity-framework/src/formatters/agent-formatter.ts:11
10 duplicated blocks under packages/sthrift-verification/ have copies in at least two of the sibling directories acceptance-api, acceptance-ui, verification-shared — 8 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/sthrift-verification/acceptance-api/src/contexts/reservation-request/step-definitions/create-reservation-request.steps.ts:1
8 duplicated blocks under packages/sthrift/domain/src/domain/iam/user/ have copies in at least two of the sibling directories admin-user, personal-user — 4 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/sthrift/domain/src/domain/iam/user/admin-user/admin-user.passport.ts:16
6 duplicated blocks under apps/ have copies in at least two of the sibling directories server-messaging-mock, server-payment-mock, ui-admin, ui-sharethrift — 4 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — apps/ui-admin/src/main.tsx:12
5 duplicated blocks under packages/sthrift/domain/src/domain/contexts/user/ have copies in at least two of the sibling directories admin-user, personal-user, role — 2 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/sthrift/domain/src/domain/contexts/user/admin-user/admin-user.aggregate.ts:19
5 duplicated blocks under packages/sthrift/persistence/src/datasources/ have copies in at least two of the sibling directories domain, payment, readonly — 2 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/sthrift/persistence/src/datasources/domain/listing/item/item-listing.repository.ts:97
5 duplicated blocks under packages/sthrift/persistence/src/datasources/readonly/ have copies in at least two of the sibling directories account-plan, conversation, listing, reservation-request, user — 2 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/sthrift/persistence/src/datasources/readonly/conversation/conversation/conversation.read-repository.ts:11
packages/sthrift-verification/acceptance-api/src/contexts/reservation-request/step-definitions/create-reservation-request.steps.ts:1 · packages/sthrift-verification/acceptance-ui/src/contexts/reservation-request/step-definitions/create-reservation-request.steps.ts:1 — these 2 files are line-for-line copies of one another — 160 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. — packages/sthrift-verification/acceptance-api/src/contexts/reservation-request/step-definitions/create-reservation-request.steps.ts:1
packages/cellix/serenity-framework/src/infrastructure/api-infrastructure.ts:96 · packages/cellix/serenity-framework/src/infrastructure/e2e-infrastructure.ts:167 — the two spans are one implementation copied and then locally edited — 924 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. — packages/cellix/serenity-framework/src/infrastructure/api-infrastructure.ts:96
packages/sthrift-verification/acceptance-api/src/shared/support/domain-test-helpers.ts:1 · packages/sthrift-verification/acceptance-ui/src/shared/support/domain-test-helpers.ts:1 — these 2 files are line-for-line copies of one another — 122 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. — packages/sthrift-verification/acceptance-api/src/shared/support/domain-test-helpers.ts:1
packages/sthrift-verification/acceptance-api/src/contexts/listing/step-definitions/create-listing.steps.ts:1 · packages/sthrift-verification/acceptance-ui/src/contexts/listing/step-definitions/create-listing.steps.ts:1 — these 2 files are line-for-line copies of one another — 101 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. — packages/sthrift-verification/acceptance-api/src/contexts/listing/step-definitions/create-listing.steps.ts:1
packages/sthrift/persistence/src/datasources/domain/appeal-request/listing-appeal-request/listing-appeal-request.domain-adapter.ts:10 · packages/sthrift/persistence/src/datasources/domain/appeal-request/user-appeal-request/user-appeal-request.domain-adapter.ts:7 — the two spans are one implementation copied and then locally edited — 599 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. — packages/sthrift/persistence/src/datasources/domain/appeal-request/listing-appeal-request/listing-appeal-request.domain-adapter.ts:10
packages/sthrift/persistence/src/datasources/readonly/user/admin-user/admin-user.read-repository.ts:67 · packages/sthrift/persistence/src/datasources/readonly/user/personal-user/personal-user.read-repository.ts:61 — 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. — packages/sthrift/persistence/src/datasources/readonly/user/admin-user/admin-user.read-repository.ts:67
packages/sthrift/persistence/src/datasources/domain/user/admin-user/admin-user.domain-adapter.ts:25 · packages/sthrift/persistence/src/datasources/domain/user/personal-user/personal-user.domain-adapter.ts:69 — the two spans are one implementation copied and then locally edited — 437 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. — packages/sthrift/persistence/src/datasources/domain/user/admin-user/admin-user.domain-adapter.ts:25
packages/sthrift/ui-admin-route-root/src/components/pages/home/components/listings-page.container.tsx:1 · packages/sthrift/ui-sharethrift-route-root/src/components/pages/home/components/listings-page.container.tsx:1 — these 2 files are line-for-line copies of one another — 84 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. — packages/sthrift/ui-admin-route-root/src/components/pages/home/components/listings-page.container.tsx:1
packages/sthrift/graphql/src/schema/types/listing-appeal-request.resolvers.ts:19 · packages/sthrift/graphql/src/schema/types/user-appeal-request.resolvers.ts:17 — 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. — packages/sthrift/graphql/src/schema/types/listing-appeal-request.resolvers.ts:19
packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.tsx:189 · packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/requests-table.tsx:82 — the two spans are one implementation copied and then locally edited — 508 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. — packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.tsx:189
packages/sthrift/ui-admin-route-listing-operations/src/section-layout.tsx:1 · packages/sthrift/ui-admin-route-root/src/section-layout.tsx:1 · packages/sthrift/ui-admin-route-user-operations/src/section-layout.tsx:1 — these 3 files are line-for-line copies of one another — 77 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. — packages/sthrift/ui-admin-route-listing-operations/src/section-layout.tsx:1
packages/cellix/serenity-framework/src/formatters/agent-formatter.ts:11 · packages/sthrift-verification/verification-shared/src/formatters/agent-formatter.ts:23 — the two spans are one implementation copied and then locally edited — 644 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. — packages/cellix/serenity-framework/src/formatters/agent-formatter.ts:11
packages/cellix/serenity-framework/src/pages/adapters/dom-adapter.ts:86 · packages/sthrift-verification/verification-shared/src/pages/adapters/jsdom-adapter.ts:76 — the two spans are one implementation copied and then locally edited — 692 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. — packages/cellix/serenity-framework/src/pages/adapters/dom-adapter.ts:86
packages/sthrift/ui-admin-route-root/src/components/pages/messages/components/conversation-list.container.tsx:12 · packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/components/conversation-list.container.tsx:12 — the two spans are one implementation copied and then locally edited — 303 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. — packages/sthrift/ui-admin-route-root/src/components/pages/messages/components/conversation-list.container.tsx:12
packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/sharer-information/sharer-information.container.tsx:1 · packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/sharer-information/sharer-information.container.tsx:1 — these 2 files are line-for-line copies of one another — 75 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. — packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/sharer-information/sharer-information.container.tsx:1
packages/cellix/server-messaging-seedwork/src/routes/messages.ts:5 · packages/cellix/server-messaging-seedwork/src/routes/participants.ts:5 — the two spans are one implementation copied and then locally edited — 498 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. — packages/cellix/server-messaging-seedwork/src/routes/messages.ts:5
packages/cellix/service-messaging-mock/src/index.ts:34 · packages/cellix/service-messaging-twilio/src/index.ts:51 — the two spans are one implementation copied and then locally edited — 500 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. — packages/cellix/service-messaging-mock/src/index.ts:34
packages/sthrift/ui-admin-route-root/src/components/pages/messages/components/conversation-box.container.tsx:1 · packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/components/conversation-box.container.tsx:1 — these 2 files are line-for-line copies of one another — 70 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. — packages/sthrift/ui-admin-route-root/src/components/pages/messages/components/conversation-box.container.tsx:1
packages/sthrift/persistence/src/datasources/readonly/conversation/conversation/conversation.read-repository.ts:11 · packages/sthrift/persistence/src/datasources/readonly/reservation-request/reservation-request/reservation-request.read-repository.ts:18 — the two spans are one implementation copied and then locally edited — 377 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. — packages/sthrift/persistence/src/datasources/readonly/conversation/conversation/conversation.read-repository.ts:11
packages/cellix/server-payment-seedwork/src/index.ts:525 · packages/cellix/server-payment-seedwork/src/index.ts:613 — the two spans are one implementation copied and then locally edited — 225 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/cellix/server-payment-seedwork/src/index.ts:525
packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-draft-success.tsx:6 · packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing-success.tsx:7 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-draft-success.tsx:6
packages/sthrift/application-services/src/contexts/conversation/conversation/query-by-id.ts:4 · packages/sthrift/application-services/src/contexts/conversation/conversation/query-by-user.ts:4 — the two spans are one implementation copied and then locally edited — 312 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. — packages/sthrift/application-services/src/contexts/conversation/conversation/query-by-id.ts:4
packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-card.tsx:24 · packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.tsx: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. — packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-card.tsx:24
packages/sthrift/domain/src/domain/contexts/user/role/admin-role/admin-role-listing-permissions.ts:23 · packages/sthrift/persistence/src/datasources/domain/role/admin-role/admin-role.domain-adapter.ts:216 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — packages/sthrift/domain/src/domain/contexts/user/role/admin-role/admin-role-listing-permissions.ts:23
packages/sthrift/domain/src/domain/contexts/user/role/admin-role/admin-role-user-permissions.ts:23 · packages/sthrift/persistence/src/datasources/domain/role/admin-role/admin-role.domain-adapter.ts:99 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — packages/sthrift/domain/src/domain/contexts/user/role/admin-role/admin-role-user-permissions.ts:23
packages/sthrift/data-sources-mongoose-models/src/models/appeal-request/listing-appeal-request.model.ts:43 · packages/sthrift/data-sources-mongoose-models/src/models/appeal-request/user-appeal-request.model.ts:33 — 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. — packages/sthrift/data-sources-mongoose-models/src/models/appeal-request/listing-appeal-request.model.ts:43
packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/view-listing.container.tsx:11 · packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/view-listing.container.tsx:12 — the two spans are one implementation copied and then locally edited — 283 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. — packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/view-listing.container.tsx:11
packages/cellix/serenity-framework/src/pages/adapters/playwright-adapter.ts:7 · packages/sthrift-verification/verification-shared/src/pages/adapters/playwright-adapter.ts:15 — 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. — packages/cellix/serenity-framework/src/pages/adapters/playwright-adapter.ts:7
packages/sthrift/domain/src/domain/contexts/user/admin-user/admin-user.aggregate.ts:19 · packages/sthrift/domain/src/domain/contexts/user/personal-user/personal-user.aggregate.ts:18 — the two spans are one implementation copied and then locally edited — 267 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. — packages/sthrift/domain/src/domain/contexts/user/admin-user/admin-user.aggregate.ts:19

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

packages/sthrift-verification/verification-shared/src/servers/test-mongodb-server.ts:2 imports packages/sthrift-verification/verification-shared/src/test-data/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/sthrift-verification/verification-shared/src/servers/test-mongodb-server.ts:2
packages/sthrift/application-services/src/contexts/account-plan/account-plan/create.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/account-plan/account-plan/create.ts:2
packages/sthrift/application-services/src/contexts/account-plan/account-plan/index.ts:6 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/account-plan/account-plan/index.ts:6
packages/sthrift/application-services/src/contexts/account-plan/account-plan/query-all.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/account-plan/account-plan/query-all.ts:2
packages/sthrift/application-services/src/contexts/account-plan/account-plan/query-by-id.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/account-plan/account-plan/query-by-id.ts:2
packages/sthrift/application-services/src/contexts/account-plan/account-plan/query-by-name.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/account-plan/account-plan/query-by-name.ts:2
packages/sthrift/application-services/src/contexts/account-plan/index.ts:1 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/account-plan/index.ts:1
packages/sthrift/application-services/src/contexts/appeal-request/index.ts:1 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/appeal-request/index.ts:1
packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/create.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/create.ts:2
packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/get-all.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/get-all.ts:2
packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/get-by-id.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/get-by-id.ts:2
packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/index.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/index.ts:2
packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/update-state.ts:1 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/update-state.ts:1
packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/create.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/create.ts:2
packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/get-all.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/get-all.ts:2
packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/get-by-id.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/get-by-id.ts:2
packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/index.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/index.ts:2
packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/update-state.ts:1 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/update-state.ts:1
packages/sthrift/application-services/src/contexts/conversation/conversation/create.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/conversation/conversation/create.ts:2
packages/sthrift/application-services/src/contexts/conversation/conversation/index.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/conversation/conversation/index.ts:2
packages/sthrift/application-services/src/contexts/conversation/conversation/query-by-id.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/conversation/conversation/query-by-id.ts:2
packages/sthrift/application-services/src/contexts/conversation/conversation/query-by-user.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/conversation/conversation/query-by-user.ts:2
packages/sthrift/application-services/src/contexts/conversation/conversation/send-message.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/conversation/conversation/send-message.ts:2
packages/sthrift/application-services/src/contexts/conversation/index.ts:1 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/conversation/index.ts:1
packages/sthrift/application-services/src/contexts/listing/index.ts:1 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/listing/index.ts:1
packages/sthrift/application-services/src/contexts/listing/item/cancel.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/listing/item/cancel.ts:2
packages/sthrift/application-services/src/contexts/listing/item/create.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/listing/item/create.ts:2
packages/sthrift/application-services/src/contexts/listing/item/delete.ts:1 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/listing/item/delete.ts:1
packages/sthrift/application-services/src/contexts/listing/item/index.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/listing/item/index.ts:2
packages/sthrift/application-services/src/contexts/listing/item/query-all.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/listing/item/query-all.ts:2
packages/sthrift/application-services/src/contexts/listing/item/query-by-id.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/listing/item/query-by-id.ts:2
packages/sthrift/application-services/src/contexts/listing/item/query-by-sharer.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/listing/item/query-by-sharer.ts:2
packages/sthrift/application-services/src/contexts/listing/item/query-paged.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/listing/item/query-paged.ts:2
packages/sthrift/application-services/src/contexts/listing/item/unblock.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/listing/item/unblock.ts:2
packages/sthrift/application-services/src/contexts/listing/item/update.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/listing/item/update.ts:2
packages/sthrift/application-services/src/contexts/reservation-request/index.ts:1 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/reservation-request/index.ts:1
packages/sthrift/application-services/src/contexts/reservation-request/reservation-request/create.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/reservation-request/reservation-request/create.ts:2
packages/sthrift/application-services/src/contexts/reservation-request/reservation-request/index.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/reservation-request/reservation-request/index.ts:2
packages/sthrift/application-services/src/contexts/reservation-request/reservation-request/query-active-by-listing-id.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/reservation-request/reservation-request/query-active-by-listing-id.ts:2
packages/sthrift/application-services/src/contexts/reservation-request/reservation-request/query-active-by-reserver-id-and-listing-id.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one. — packages/sthrift/application-services/src/contexts/reservation-request/reservation-request/query-active-by-reserver-id-and-listing-id.ts: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 (65 rows); move the shared test helper into a source directory production code may depend on (1 row).

Do you agree with this assessment?

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

ThemeDemo has cyclomatic complexity 37 and cognitive complexity 36; 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. — packages/sthrift/ui-shared/src/theme/theme-demo/ThemeDemo.tsx:39
(anonymous) has cyclomatic complexity 31 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 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. — packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-view.container.tsx:76
(top-level) has cyclomatic complexity 27 and cognitive complexity 26; 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. — packages/sthrift/domain/src/domain/contexts/value-objects.ts:1
checkLayeredArchitecture has cyclomatic complexity 25 and cognitive complexity 36; 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. — packages/cellix/arch-unit-tests/src/checks/circular-dependencies.ts:58
performAs has cyclomatic complexity 22 and cognitive complexity 26; 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. — packages/sthrift-verification/e2e-tests/src/contexts/listing/tasks/create-listing.ts:21
checkFrontendArchitecture has cyclomatic complexity 22 and cognitive complexity 25; 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. — packages/cellix/arch-unit-tests/src/checks/frontend-architecture.ts:12
checkGraphqlResolverDependencies has cyclomatic complexity 21 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. — packages/cellix/arch-unit-tests/src/checks/graphql-resolver-conventions.ts:22
(top-level) has cyclomatic complexity 19 and cognitive complexity 18; 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. — packages/sthrift-verification/verification-shared/src/settings/local-settings.ts:1
(anonymous) has cyclomatic complexity 17 and cognitive complexity 21; 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. — REDACTED:130
(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. — REDACTED:292
(anonymous) has cyclomatic complexity 16 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 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. — packages/sthrift/application-services/src/contexts/user/personal-user/process-payment.ts:29
getDefinitionOrderCategory has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — packages/cellix/arch-unit-tests/src/checks/graphql-schema-conventions.ts:310
constructor has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — packages/cellix/service-payment-cybersource/src/index.ts:49
ProfileViewContainer has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/profile/components/profile-view.container.tsx:11
(anonymous) has cyclomatic complexity 14 and cognitive complexity 13; 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. — packages/sthrift/application-services/src/contexts/user/personal-user/update.ts:55
Navigation has cyclomatic complexity 14 and cognitive complexity 13; 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. — packages/sthrift/ui-shared/src/molecules/navigation/navigation.tsx:46
MessageBubble has cyclomatic complexity 14 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. — packages/sthrift/ui-shared/src/organisms/message-thread.tsx:168
getListingRequestsBySharerId has cyclomatic complexity 13 and cognitive complexity 28; 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. — packages/sthrift/persistence/src/datasources/readonly/reservation-request/reservation-request/reservation-request.read-repository.ts:197
checkUiIsolation has cyclomatic complexity 13 and cognitive complexity 18; 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. — packages/cellix/arch-unit-tests/src/checks/circular-dependencies.ts:181

What to do

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

Do you agree with this assessment?

R3 · Large Files9.0 / 10Strong✓ 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.

packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/listing-information/listing-information.container.stories.tsx has 1994 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/listing-information/listing-information.container.stories.tsx:1
packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/listing-information/listing-information.container.stories.tsx has 1994 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/listing-information/listing-information.container.stories.tsx:1
packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.container.stories.tsx has 1647 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.container.stories.tsx:1
packages/cellix/server-payment-seedwork/src/index.ts has 1292 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/cellix/server-payment-seedwork/src/index.ts:1
packages/cellix/service-payment-cybersource/src/index.ts has 1031 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/cellix/service-payment-cybersource/src/index.ts:1
packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/listing-information/listing-information.stories.tsx has 950 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/listing-information/listing-information.stories.tsx:1
packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/listing-information/listing-information.stories.tsx has 950 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/listing-information/listing-information.stories.tsx:1
packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/view-listing.container.stories.tsx has 899 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/view-listing.container.stories.tsx:1
packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/view-listing.container.stories.tsx has 899 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/view-listing.container.stories.tsx:1
packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.container.stories.tsx has 868 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.container.stories.tsx:1
packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/pages/settings-view.tsx has 764 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/pages/settings-view.tsx:1
packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/requests-table.container.stories.tsx has 761 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/requests-table.container.stories.tsx:1
packages/sthrift/ui-sharethrift-route-signup/src/components/pages/select-account-type/components/select-account-type.container.stories.tsx has 683 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/sthrift/ui-sharethrift-route-signup/src/components/pages/select-account-type/components/select-account-type.container.stories.tsx:1
packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users.stories.tsx has 678 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users.stories.tsx:1
packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-view.container.stories.tsx has 674 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-view.container.stories.tsx:1
packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.container.stories.tsx has 627 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.container.stories.tsx:1
packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-reservations/components/reservations-view-active.container.stories.tsx has 549 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-reservations/components/reservations-view-active.container.stories.tsx:1
packages/cellix/service-payment-mock/src/index.ts has 546 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/cellix/service-payment-mock/src/index.ts:1
packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.stories.tsx has 496 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.stories.tsx:1
packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-container.stories.tsx has 488 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-container.stories.tsx:1
packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/components/messages.stories.tsx has 467 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/components/messages.stories.tsx:1
packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.stories.tsx has 405 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.stories.tsx:1
packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.tsx has 403 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.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 Coverage9.0 / 10Strong✓ 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.

packages/sthrift/ui-admin-route-root/src/components/pages/messages/pages/messages-page.stories.tsx:12 imports '../../../../index.tsx', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/sthrift/ui-admin-route-root/src/components/pages/messages/pages/messages-page.stories.tsx:12
packages/sthrift/ui-sharethrift-route-root/src/app-routes.stories.tsx:2 imports './index.tsx', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/sthrift/ui-sharethrift-route-root/src/app-routes.stories.tsx:2
packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/profile/pages/profile-page.stories.tsx:2 imports '../../../../../../index.tsx', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/profile/pages/profile-page.stories.tsx:2
packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/pages/settings-page.stories.tsx:2 imports '../../../../../../index.tsx', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/pages/settings-page.stories.tsx:2
packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/pages/messages-page.stories.tsx:12 imports '../../../../index.tsx', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/pages/messages-page.stories.tsx:12
packages/sthrift/ui-sharethrift-route-shared/src/hooks/use-onboarding-redirect.stories.tsx:2 imports './use-has-completed-onboarding-check.ts', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/sthrift/ui-sharethrift-route-shared/src/hooks/use-onboarding-redirect.stories.tsx:2
packages/sthrift/ui-sharethrift-route-signup/src/signup-routes.stories.tsx:2 imports './index.tsx', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/sthrift/ui-sharethrift-route-signup/src/signup-routes.stories.tsx:2
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. (×33) — packages/cellix/server-payment-seedwork/src/index.ts:1, packages/cellix/server-messaging-seedwork/src/store.ts:1, build-pipeline/scripts/detect-changes.cjs:1, …

What to do

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

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.

This repository declares test tooling, and the ✓ above records that declaration — but packages/sthrift/ui-admin-route-root/src/components/pages/messages/pages/messages-page.stories.tsx and 6 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — packages/sthrift/ui-admin-route-root/src/components/pages/messages/pages/messages-page.stories.tsx:12

Do you agree with this assessment?

R7 · Dead Code9.2 / 10Exemplary✓ 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.

23 file(s) (~1384 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/sthrift-verification/e2e-tests
Unreachable from the 147 application, 83 tooling and 573 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (147 application, 83 tooling, 573 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 (×12) — packages/sthrift-verification/verification-shared/src/pages/adapters/jsdom-adapter.ts, build-pipeline/scripts/local-https-proxy.js, packages/sthrift-verification/verification-shared/src/pages/adapters/playwright-adapter.ts, …
no import path from any entry point (147 application, 83 tooling, 573 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/sthrift-verification/verification-shared/src/formatters/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 — packages/sthrift-verification/verification-shared/src/formatters/agent-formatter.ts
no import path from any entry point (147 application, 83 tooling, 573 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/sthrift-verification/verification-shared/src/settings/index.ts, packages/sthrift-verification/verification-shared/src/settings/local-settings.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 — packages/sthrift-verification/verification-shared/src/settings/settings-utils.ts
no import path from any entry point (147 application, 83 tooling, 573 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/sthrift-verification/verification-shared/src/settings/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 — packages/sthrift-verification/verification-shared/src/settings/local-settings.ts
no import path from any entry point (147 application, 83 tooling, 573 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/sthrift-verification/verification-shared/src/servers/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 — packages/sthrift-verification/verification-shared/src/servers/graphql-test-server.ts
no import path from any entry point (147 application, 83 tooling, 573 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/sthrift/domain/src/domain/events/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 — packages/sthrift/domain/src/domain/events/event-bus.ts
Nothing imports this binding — it is safe to review for removal. (×8) — packages/cellix/mongoose-seedwork/src/mongoose-seedwork/base.ts:33, packages/cellix/mongoose-seedwork/src/mongoose-seedwork/mongo-connection.ts:20, packages/cellix/mongoose-seedwork/src/mongoose-seedwork/mongo-connection.ts:24, …
Nothing ultimately consumes this binding: its only referrer is the re-export in packages/sthrift-verification/verification-shared/src/servers/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/sthrift-verification/verification-shared/src/servers/index.ts in the same commit, or the barrel will import a name that no longer exists. — packages/sthrift-verification/verification-shared/src/servers/test-mongodb-server.ts:67
Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect. — packages/sthrift/domain/tests/acceptance/screenplay/abilities/create-listing.ability.ts:21

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.

Declared in the root 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. — apps/server-mongodb-memory-mock/src/seed/seed.ts:1

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.

packages/sthrift-verification/verification-shared/src/servers/test-mongodb-server.ts → packages/sthrift-verification/verification-shared/src/test-data/index.ts → packages/sthrift-verification/verification-shared/src/servers/test-mongodb-server.ts — packages/sthrift-verification/verification-shared/src/servers/test-mongodb-server.ts:2

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 Posture8.0 / 10Strong✓ Tool-verified

Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository. Its Node HTTP listeners were read for HTTPS enforcement alone — TLS served, a redirect to https:// or HSTS, or a TLS-terminating proxy configuration committed beside the server — each judged per server package.

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.

`http(…).listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — packages/cellix/server-messaging-seedwork/src/index.ts:72
`a.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — packages/cellix/server-oauth2-seedwork/src/manager.ts:46
`app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) (×2) — packages/cellix/server-oauth2-seedwork/src/server.ts:22, packages/cellix/server-payment-seedwork/src/index.ts:1339

What to do

Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.

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

Other · Code Health — Whether async functions that make a cancellable request accept or pass on 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 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) 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.
`execute` 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 })`. — packages/sthrift-verification/acceptance-api/src/shared/abilities/graphql-client.ts:17

What to do

Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.

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

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

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

Do you agree with this assessment?

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

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

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

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?

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 handling5.2 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×30) — packages/cellix/serenity-framework/src/cucumber/screenshot-hooks.ts:52, packages/cellix/serenity-framework/src/dom/asset-loader-hooks.ts:53, REDACTED:98, …

What to do

Swallowed exception (empty catch)

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?

X5 · Nullable reference types2.3 / 10Critical✓ 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.

3/58 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.8 `!` null assertions per 1k TypeScript source lines — 41 assertion(s) across the 48585 source line(s) of the 756 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: packages/sthrift/persistence/src/datasources/domain/user/personal-user/personal-user.domain-adapter.ts (17), packages/sthrift/persistence/src/datasources/domain/user/admin-user/admin-user.domain-adapter.ts (12), packages/sthrift/domain/src/domain/contexts/user/admin-user/admin-user-account-profile-location.ts (6). 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 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

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

Reference — by lens

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

Lens	Score	Rating	Impact
Code Health	55%	Adequate — gated by X5	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture	53%	Adequate — gated by AX8	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity	62%	Adequate — gated by M4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	32%	Weak — gated by R8, P2, P6, P7	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	66%	Adequate — gated by D29, D30, D36	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling	100%	Exemplary	Strongest area.
Accessibility	76%	Strong	Solid.
Performance	60%	Adequate	Acceptable, with room to improve.

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 — 10 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 — 23 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.

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

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

AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
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 — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
D12 Dependency Hygiene — Not scored — 1 shipped Python distribution(s) were read, but the outdated signal needs pypi.org, and no declaration here carries an exact pin to ask about — a floor or a range installs the newest release it admits and cannot be behind one, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
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 counts a call into the standard library or a dependency as unresolved for this repository's language (.cjs,.js,.mjs,.ts,.tsx), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 20 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
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.
DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
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
DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage data present for 62 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
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.
X4 Structured logging — 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
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 83 finding(s)

D30 · Dependency Vulnerabilities · High CVE · ×44

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

AX8 · Test isolation · Production project references a test project · ×13

Production project references a test project: @apps/api → @cellix/api-services-spec apps/api/package.json:27 — `@apps/api` (production) references the test project `@cellix/api-services-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @apps/api → @sthrift/context-spec apps/api/package.json:32 — `@apps/api` (production) references the test project `@sthrift/context-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @cellix/service-messaging-base → @cellix/api-services-spec packages/cellix/service-messaging-base/package.json:23 — `@cellix/service-messaging-base` (production) references the test project `@cellix/api-services-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @cellix/service-messaging-mock → @cellix/api-services-spec packages/cellix/service-messaging-mock/package.json:21 — `@cellix/service-messaging-mock` (production) references the test project `@cellix/api-services-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @cellix/service-messaging-twilio → @cellix/api-services-spec packages/cellix/service-messaging-twilio/package.json:21 — `@cellix/service-messaging-twilio` (production) references the test project `@cellix/api-services-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @cellix/service-mongoose → @cellix/api-services-spec packages/cellix/service-mongoose/package.json:27 — `@cellix/service-mongoose` (production) references the test project `@cellix/api-services-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @cellix/service-otel → @cellix/api-services-spec REDACTED:28 — `@cellix/service-otel` (production) references the test project `@cellix/api-services-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @cellix/service-payment-base → @cellix/api-services-spec packages/cellix/service-payment-base/package.json:22 — `@cellix/service-payment-base` (production) references the test project `@cellix/api-services-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @cellix/service-payment-cybersource → @cellix/api-services-spec REDACTED:20 — `@cellix/service-payment-cybersource` (production) references the test project `@cellix/api-services-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @cellix/service-payment-mock → @cellix/api-services-spec packages/cellix/service-payment-mock/package.json:20 — `@cellix/service-payment-mock` (production) references the test project `@cellix/api-services-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @cellix/service-token-validation → @cellix/api-services-spec packages/cellix/service-token-validation/package.json:25 — `@cellix/service-token-validation` (production) references the test project `@cellix/api-services-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @sthrift/application-services → @sthrift/context-spec packages/sthrift/application-services/package.json:27 — `@sthrift/application-services` (production) references the test project `@sthrift/context-spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Production project references a test project: @sthrift/persistence → @cellix/test-utils packages/sthrift/persistence/package.json:36 — `@sthrift/persistence` (production) references the test project `@cellix/test-utils`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.

D30 · Dependency Vulnerabilities · Critical CVE · ×8

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D28 · Secrets (history) · REDACTED · ×3

REDACTED
REDACTED
REDACTED

D34 · Knowledge Freshness · Orphaned knowledge · ×3

Orphaned knowledge packages/cellix/service-payment-cybersource/src/index.ts:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/sthrift/ui-sharethrift-route-signup/src/components/shared/address-form/countries-mock-data.ts:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.container.stories.tsx:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.

AX4 · Dependency direction · Dependency-rule violation · ×1

Dependency-rule violation: @sthrift/application-services (Application) → @sthrift/persistence (Infrastructure) packages/sthrift/application-services/package.json:29 — `@sthrift/application-services` is a Application project but references `@sthrift/persistence`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.

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

REDACTED

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

REDACTED

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

REDACTED

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

REDACTED

D30 · Dependency Vulnerabilities · High vulnerability · ×1

REDACTED

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

Import cycle (2 files) packages/sthrift-verification/verification-shared/src/servers/test-mongodb-server.ts:2 — packages/sthrift-verification/verification-shared/src/servers/test-mongodb-server.ts → packages/sthrift-verification/verification-shared/src/test-data/index.ts → packages/sthrift-verification/verification-shared/src/servers/test-mongodb-server.ts

Serious — 462 finding(s)

D17 · Explicit Debt · TodoComment · ×44

TodoComment packages/cellix/domain-seedwork/src/domain-seedwork/child-entity.ts:1 — //TODO: Add a description of the file and its purpose - note why it does not extend DomainEntityProps — 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 packages/cellix/mongoose-seedwork/src/mongoose-seedwork/mongo-unit-of-work.ts:80 — //todo: can we make this an arry of CustomDomainEvents? — 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 packages/cellix/mongoose-seedwork/tests/integration/mongo-unit-of-work.integration.test.ts:674 — // TODO: Scenario: Executing a transaction with integration events — 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 packages/cellix/mongoose-seedwork/tests/integration/mongo-unit-of-work.integration.test.ts:677 — // TODO: Test definition: When withTransaction is called and integration event is added during aggregate save — 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 packages/cellix/mongoose-seedwork/tests/integration/mongo-unit-of-work.integration.test.ts:683 — // TODO: Test definition: When withTransaction is called but no integration event is registered — 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 packages/cellix/mongoose-seedwork/tests/integration/mongo-unit-of-work.integration.test.ts:689 — // TODO: Test definition: When withTransaction is called and multiple integration events are added — 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 packages/cellix/mongoose-seedwork/tests/integration/mongo-unit-of-work.integration.test.ts:695 — // TODO: Test definition: When withTransaction is called and integration event handler throws — 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 packages/cellix/mongoose-seedwork/tests/integration/mongo-unit-of-work.integration.test.ts:701 — // TODO: Test definition: When withTransaction is called and dispatching integration events is delayed — 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 packages/cellix/mongoose-seedwork/tests/integration/mongo-unit-of-work.integration.test.ts:707 — // TODO: Test definition: When withTransaction is called and both domain and integration events are registered — 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 packages/cellix/mongoose-seedwork/tests/integration/mongo-unit-of-work.integration.test.ts:713 — // TODO: Test definition: When withTransaction is called and integration event dispatch fails fatally — 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 packages/cellix/service-messaging-twilio/src/index.ts:17 — // TODO: Uncomment when Twilio API keys are configured in deployed environment — 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 packages/sthrift-verification/acceptance-api/src/contexts/listing/step-definitions/create-listing.steps.ts:82 — // TODO: Verify actual daily rate value once domain model exposes it via notes. — 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 packages/sthrift-verification/acceptance-ui/src/contexts/listing/step-definitions/create-listing.steps.ts:80 — // TODO: Verify actual daily rate value once domain model exposes it via notes. — 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 packages/sthrift/data-sources-mongoose-models/src/patterns.ts:8 — //TODO: fix email pattern so that it is unicode compliant — 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 packages/sthrift/data-sources-mongoose-models/src/models/role/role.model.ts:8 — // TODO: Discriminator key and Version can't exist together, if we don't use version key it will fall back to __v — 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 packages/sthrift/domain/tests/acceptance/screenplay/abilities/create-listing.ability.ts:5 — // TODO: Replace with real types when implementing actual domain integration — 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 packages/sthrift/graphql/src/schema/types/user-appeal-request.resolvers.ts:27 — // TODO: SECURITY - Add authentication and authorization check — 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 packages/sthrift/graphql/src/schema/types/listing-appeal-request.resolvers.ts:29 — // TODO: SECURITY - Add authentication and authorization check — 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 packages/sthrift/graphql/src/schema/types/user-appeal-request.resolvers.ts:39 — // TODO: SECURITY - Add admin permission check — 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 packages/sthrift/graphql/src/schema/types/user-appeal-request.resolvers.ts:86 — // TODO: SECURITY - Add admin permission check — 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 packages/sthrift/graphql/src/schema/types/listing-appeal-request.resolvers.ts:41 — // TODO: SECURITY - Add admin permission check — 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 packages/sthrift/graphql/src/schema/types/listing-appeal-request.resolvers.ts:88 — // TODO: SECURITY - Add admin permission check — 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 packages/sthrift/graphql/src/schema/types/user-appeal-request.resolvers.ts:61 — // TODO: SECURITY - Add authentication check — 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 packages/sthrift/graphql/src/schema/types/listing-appeal-request.resolvers.ts:63 — // TODO: SECURITY - Add authentication check — 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 packages/sthrift/graphql/src/schema/types/user-appeal-request.resolvers.ts:62 — // TODO: SECURITY - Verify the authenticated user matches userId — 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.
+ 19 more in this group — see findings.md.

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

Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/account-plan/account-plan/create.ts:2 — packages/sthrift/application-services/src/contexts/account-plan/account-plan/create.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/account-plan/account-plan/index.ts:6 — packages/sthrift/application-services/src/contexts/account-plan/account-plan/index.ts:6 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/account-plan/account-plan/query-all.ts:2 — packages/sthrift/application-services/src/contexts/account-plan/account-plan/query-all.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/account-plan/account-plan/query-by-id.ts:2 — packages/sthrift/application-services/src/contexts/account-plan/account-plan/query-by-id.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/account-plan/account-plan/query-by-name.ts:2 — packages/sthrift/application-services/src/contexts/account-plan/account-plan/query-by-name.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/account-plan/index.ts:1 — packages/sthrift/application-services/src/contexts/account-plan/index.ts:1 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/appeal-request/index.ts:1 — packages/sthrift/application-services/src/contexts/appeal-request/index.ts:1 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/create.ts:2 — packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/create.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/get-all.ts:2 — packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/get-all.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/get-by-id.ts:2 — packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/get-by-id.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/index.ts:2 — packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/index.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/update-state.ts:1 — packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/update-state.ts:1 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/create.ts:2 — packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/create.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/get-all.ts:2 — packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/get-all.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/get-by-id.ts:2 — packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/get-by-id.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/index.ts:2 — packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/index.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/update-state.ts:1 — packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/update-state.ts:1 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/conversation/conversation/create.ts:2 — packages/sthrift/application-services/src/contexts/conversation/conversation/create.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/conversation/conversation/index.ts:2 — packages/sthrift/application-services/src/contexts/conversation/conversation/index.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/conversation/conversation/query-by-id.ts:2 — packages/sthrift/application-services/src/contexts/conversation/conversation/query-by-id.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/conversation/conversation/query-by-user.ts:2 — packages/sthrift/application-services/src/contexts/conversation/conversation/query-by-user.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/conversation/conversation/send-message.ts:2 — packages/sthrift/application-services/src/contexts/conversation/conversation/send-message.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/conversation/index.ts:1 — packages/sthrift/application-services/src/contexts/conversation/index.ts:1 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/listing/index.ts:1 — packages/sthrift/application-services/src/contexts/listing/index.ts:1 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
Boundary violation [layered:package-upward-import] packages/sthrift/application-services/src/contexts/listing/item/cancel.ts:2 — packages/sthrift/application-services/src/contexts/listing/item/cancel.ts:2 imports packages/sthrift/persistence/src/index.ts, a module of a workspace package of an OUTER layer, from a package of an inner one — dependencies must point inward (domain ← application ← infrastructure/adapters/web). Define the abstraction in the inner package and implement it in the outer one.
+ 14 more in this group — see findings.md.

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

No test reaches this file packages/cellix/server-payment-seedwork/src/index.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 packages/cellix/server-messaging-seedwork/src/store.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 build-pipeline/scripts/detect-changes.cjs: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 packages/sthrift-verification/verification-shared/src/pages/adapters/jsdom-adapter.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 apps/server-mongodb-memory-mock/src/seed/item-listings.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 apps/server-mongodb-memory-mock/src/seed/personal-users.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 packages/cellix/server-messaging-seedwork/src/routes/participants.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 build-pipeline/scripts/local-https-proxy.js: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 packages/sthrift-verification/verification-shared/src/formatters/agent-formatter.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 build-pipeline/scripts/check-sonar-quality-gate.cjs: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 apps/server-messaging-mock/src/seed/seed-data.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 packages/sthrift-verification/verification-shared/src/pages/adapters/playwright-adapter.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 packages/cellix/service-messaging-mock/src/index.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 packages/cellix/service-blob-storage/src/index.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 packages/sthrift/ui-admin-route-listing-operations/src/section-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.
No test reaches this file packages/sthrift/ui-admin-route-user-operations/src/section-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.
No test reaches this file build-pipeline/scripts/merge-coverage.js: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 apps/server-oauth2-mock/src/index.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 packages/sthrift-verification/verification-shared/src/settings/settings-utils.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 packages/sthrift-verification/verification-shared/src/settings/local-settings.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 packages/cellix/server-messaging-seedwork/src/routes/messages.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 apps/server-mongodb-memory-mock/src/seed/admin-roles.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 apps/server-mongodb-memory-mock/src/seed/admin-users.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 apps/server-mongodb-memory-mock/src/seed/seed.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.
+ 8 more in this group — see findings.md.

D8 · Code Coverage · Low coverage · ×32

Low coverage: packages/cellix/arch-unit-tests/src/checks/application-services-conventions.ts packages/cellix/arch-unit-tests/src/checks/application-services-conventions.ts:1 — 0.0% line coverage (0/86).
Low coverage: packages/cellix/arch-unit-tests/src/checks/circular-dependencies.ts packages/cellix/arch-unit-tests/src/checks/circular-dependencies.ts:1 — 34.7% line coverage (25/72).
Low coverage: packages/cellix/arch-unit-tests/src/checks/code-metrics.ts packages/cellix/arch-unit-tests/src/checks/code-metrics.ts:1 — 0.0% line coverage (0/1).
Low coverage: packages/cellix/arch-unit-tests/src/checks/code-quality.ts packages/cellix/arch-unit-tests/src/checks/code-quality.ts:1 — 0.0% line coverage (0/1).
Low coverage: packages/cellix/arch-unit-tests/src/checks/data-sources-mongoose-models-conventions.ts packages/cellix/arch-unit-tests/src/checks/data-sources-mongoose-models-conventions.ts:1 — 0.0% line coverage (0/46).
Low coverage: packages/cellix/arch-unit-tests/src/checks/domain-conventions.ts packages/cellix/arch-unit-tests/src/checks/domain-conventions.ts:1 — 0.0% line coverage (0/94).
Low coverage: packages/cellix/arch-unit-tests/src/checks/frontend-architecture.ts packages/cellix/arch-unit-tests/src/checks/frontend-architecture.ts:1 — 0.0% line coverage (0/40).
Low coverage: packages/cellix/arch-unit-tests/src/checks/graphql-resolver-conventions.ts packages/cellix/arch-unit-tests/src/checks/graphql-resolver-conventions.ts:1 — 0.0% line coverage (0/102).
Low coverage: packages/cellix/arch-unit-tests/src/checks/graphql-schema-conventions.ts packages/cellix/arch-unit-tests/src/checks/graphql-schema-conventions.ts:1 — 0.6% line coverage (1/177).
Low coverage: packages/cellix/arch-unit-tests/src/checks/member-ordering.ts packages/cellix/arch-unit-tests/src/checks/member-ordering.ts:1 — 0.0% line coverage (0/23).
Low coverage: packages/cellix/arch-unit-tests/src/checks/naming-conventions.ts packages/cellix/arch-unit-tests/src/checks/naming-conventions.ts:1 — 0.0% line coverage (0/11).
Low coverage: packages/cellix/arch-unit-tests/src/checks/persistence-conventions.ts packages/cellix/arch-unit-tests/src/checks/persistence-conventions.ts:1 — 0.0% line coverage (0/105).
Low coverage: packages/cellix/arch-unit-tests/src/test-suites/application-services-conventions.ts packages/cellix/arch-unit-tests/src/test-suites/application-services-conventions.ts:1 — 0.0% line coverage (0/42).
Low coverage: packages/cellix/arch-unit-tests/src/test-suites/code-metrics.ts packages/cellix/arch-unit-tests/src/test-suites/code-metrics.ts:1 — 0.0% line coverage (0/14).
Low coverage: packages/cellix/arch-unit-tests/src/test-suites/code-quality.ts packages/cellix/arch-unit-tests/src/test-suites/code-quality.ts:1 — 0.0% line coverage (0/14).
Low coverage: packages/cellix/arch-unit-tests/src/test-suites/data-sources-mongoose-models-conventions.ts packages/cellix/arch-unit-tests/src/test-suites/data-sources-mongoose-models-conventions.ts:1 — 0.0% line coverage (0/31).
Low coverage: packages/cellix/arch-unit-tests/src/test-suites/dependency-rules.ts packages/cellix/arch-unit-tests/src/test-suites/dependency-rules.ts:1 — 46.2% line coverage (24/52).
Low coverage: packages/cellix/arch-unit-tests/src/test-suites/domain-conventions.ts packages/cellix/arch-unit-tests/src/test-suites/domain-conventions.ts:1 — 0.0% line coverage (0/38).
Low coverage: packages/cellix/arch-unit-tests/src/test-suites/frontend-architecture.ts packages/cellix/arch-unit-tests/src/test-suites/frontend-architecture.ts:1 — 0.0% line coverage (0/37).
Low coverage: packages/cellix/arch-unit-tests/src/test-suites/graphql-resolver-conventions.ts packages/cellix/arch-unit-tests/src/test-suites/graphql-resolver-conventions.ts:1 — 0.0% line coverage (0/39).
Low coverage: packages/cellix/arch-unit-tests/src/test-suites/graphql-schema-conventions.ts packages/cellix/arch-unit-tests/src/test-suites/graphql-schema-conventions.ts:1 — 0.0% line coverage (0/29).
Low coverage: packages/cellix/arch-unit-tests/src/test-suites/member-ordering.ts packages/cellix/arch-unit-tests/src/test-suites/member-ordering.ts:1 — 0.0% line coverage (0/26).
Low coverage: packages/cellix/arch-unit-tests/src/test-suites/naming-conventions.ts packages/cellix/arch-unit-tests/src/test-suites/naming-conventions.ts:1 — 0.0% line coverage (0/9).
Low coverage: packages/cellix/arch-unit-tests/src/test-suites/persistence-conventions.ts packages/cellix/arch-unit-tests/src/test-suites/persistence-conventions.ts:1 — 0.0% line coverage (0/48).
Low coverage: packages/cellix/arch-unit-tests/src/utils/frontend-helpers.ts packages/cellix/arch-unit-tests/src/utils/frontend-helpers.ts:1 — 0.0% line coverage (0/21).
+ 7 more in this group — see findings.md.

X3 · Exception handling · Swallowed exception (empty catch) · ×30

Swallowed exception (empty catch) packages/cellix/serenity-framework/src/cucumber/screenshot-hooks.ts:52 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/cellix/serenity-framework/src/dom/asset-loader-hooks.ts:53 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:98 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/cellix/server-oauth2-seedwork/src/manager.ts:136 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/cellix/service-token-validation/src/index.ts:73 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/sthrift-verification/acceptance-api/src/contexts/listing/step-definitions/create-listing.steps.ts:96 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/sthrift-verification/acceptance-api/src/contexts/listing/step-definitions/create-listing.steps.ts:113 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/sthrift-verification/acceptance-api/src/contexts/listing/step-definitions/create-listing.steps.ts:133 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/sthrift-verification/acceptance-api/src/contexts/listing/step-definitions/create-listing.steps.ts:154 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/sthrift-verification/acceptance-api/src/contexts/listing/step-definitions/create-listing.steps.ts:161 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/sthrift-verification/acceptance-api/src/contexts/reservation-request/step-definitions/create-reservation-request.steps.ts:152 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/sthrift-verification/acceptance-api/src/contexts/reservation-request/step-definitions/create-reservation-request.steps.ts:174 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/sthrift-verification/acceptance-api/src/contexts/reservation-request/step-definitions/create-reservation-request.steps.ts:181 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/sthrift-verification/acceptance-ui/src/contexts/listing/step-definitions/create-listing.steps.ts:94 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/sthrift-verification/acceptance-ui/src/contexts/listing/step-definitions/create-listing.steps.ts:111 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/sthrift-verification/acceptance-ui/src/contexts/listing/step-definitions/create-listing.steps.ts:131 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/sthrift-verification/acceptance-ui/src/contexts/listing/step-definitions/create-listing.steps.ts:152 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/sthrift-verification/acceptance-ui/src/contexts/listing/step-definitions/create-listing.steps.ts:159 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/sthrift-verification/acceptance-ui/src/contexts/reservation-request/step-definitions/create-reservation-request.steps.ts:152 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/sthrift-verification/acceptance-ui/src/contexts/reservation-request/step-definitions/create-reservation-request.steps.ts:174 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/sthrift-verification/acceptance-ui/src/contexts/reservation-request/step-definitions/create-reservation-request.steps.ts:181 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/sthrift/graphql/src/schema/resolver-helper.ts:27 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/sthrift/graphql/src/schema/resolver-helper.ts:40 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/sthrift/graphql/src/schema/resolver-helper.ts:63 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/sthrift/graphql/src/schema/resolver-helper.ts:174 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
+ 5 more in this group — see findings.md.

D3 · God Classes · FunctionTooLong · ×28

FunctionTooLong: index.startMockPaymentServer packages/cellix/server-payment-seedwork/src/index.ts:34 — FunctionTooLong — startMockPaymentServer runs 924 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 824 over it, 9.24× 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: settings-view.SettingsView packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/pages/settings-view.tsx:67 — FunctionTooLong — SettingsView runs 627 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 527 over it, 6.27× 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: all-listings-table.AllListingsTable packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.tsx:40 — FunctionTooLong — AllListingsTable runs 305 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 205 over it, 3.05× 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: router.buildOidcRouter REDACTED:31 — FunctionTooLong — buildOidcRouter runs 285 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 185 over it, 2.85× 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: admin-users-table.AdminUsersTable packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.tsx:33 — FunctionTooLong — AdminUsersTable runs 261 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 161 over it, 2.61× 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: create-listing.CreateListing packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.tsx:40 — FunctionTooLong — CreateListing runs 229 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 129 over it, 2.29× 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: settings-view.container.SettingsViewLoader packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-view.container.tsx:17 — FunctionTooLong — SettingsViewLoader runs 177 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 77 over it, 1.77× 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: login-form.LoginForm packages/sthrift/ui-shared/src/organisms/login-form.tsx:26 — FunctionTooLong — LoginForm runs 160 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 60 over it, 1.60× 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: reservation-request-form.ReservationRequestForm packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/reservation-request-form.tsx:51 — FunctionTooLong — ReservationRequestForm runs 160 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 60 over it, 1.60× 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: select-account-type.SelectAccountType packages/sthrift/ui-sharethrift-route-signup/src/components/pages/select-account-type/components/select-account-type.tsx:46 — FunctionTooLong — SelectAccountType runs 160 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 60 over it, 1.60× 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: all-listings-card.AllListingsCard packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-card.tsx:14 — FunctionTooLong — AllListingsCard runs 154 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 54 over it, 1.54× 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-setup-form.ProfileSetupForm packages/sthrift/ui-sharethrift-route-signup/src/components/pages/profile-setup/components/profile-setup-form.tsx:32 — FunctionTooLong — ProfileSetupForm runs 152 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× 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: requests-table.RequestsTable packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/requests-table.tsx:40 — FunctionTooLong — RequestsTable runs 149 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× 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-view.ProfileView packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/profile/components/profile-view.tsx:30 — FunctionTooLong — ProfileView runs 141 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× 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: listing-banner.ListingBanner packages/sthrift/ui-shared/src/organisms/listing-banner.tsx:21 — FunctionTooLong — ListingBanner runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× 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: messages.Messages packages/sthrift/ui-shared/src/organisms/messages.tsx:20 — FunctionTooLong — Messages runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× 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: payment-token-form-items.PaymentTokenFormItems packages/sthrift/ui-sharethrift-route-signup/src/components/pages/payment/components/payment-token-form-items.tsx:29 — FunctionTooLong — PaymentTokenFormItems runs 126 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× 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: payment-form.PaymentForm packages/sthrift/ui-sharethrift-route-signup/src/components/pages/payment/components/payment-form.tsx:25 — FunctionTooLong — PaymentForm runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× 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: admin-listings-table.AdminListingsTable packages/sthrift/ui-admin-route-listing-operations/src/components/pages/admin-listing-operations/components/admin-listings-table/admin-listings-table.tsx:39 — FunctionTooLong — AdminListingsTable runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× 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: terms.Terms packages/sthrift/ui-sharethrift-route-signup/src/components/pages/terms/components/terms.tsx:11 — FunctionTooLong — Terms runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× 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: billing-address-form-items.BillingAddressFormItems packages/sthrift/ui-sharethrift-route-signup/src/components/pages/payment/components/billing-address-form-items.tsx:20 — FunctionTooLong — BillingAddressFormItems runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× 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: manager.createMockOAuth2Manager packages/cellix/server-oauth2-seedwork/src/manager.ts:11 — FunctionTooLong — createMockOAuth2Manager runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× 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: section-layout.SectionLayout packages/sthrift/ui-sharethrift-route-root/src/section-layout.tsx:16 — FunctionTooLong — SectionLayout runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× 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: message-thread.MessageThread packages/sthrift/ui-shared/src/organisms/message-thread.tsx:34 — FunctionTooLong — MessageThread runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× 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: participants.setupParticipantRoutes packages/cellix/server-messaging-seedwork/src/routes/participants.ts:5 — FunctionTooLong — setupParticipantRoutes runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× 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.
+ 3 more in this group — see findings.md.

D30 · Dependency Vulnerabilities · Medium CVE · ×28

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 3 more in this group — see findings.md.

PF3 · Async & latency hygiene · Sync-over-async blocking · ×11

Sync-over-async blocking packages/cellix/arch-unit-tests/src/checks/frontend-architecture.ts:21 — `fs.existsSync` in `checkFrontendArchitecture` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cellix/arch-unit-tests/src/checks/frontend-architecture.ts:24 — `fs.existsSync` in `checkFrontendArchitecture` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cellix/arch-unit-tests/src/checks/frontend-architecture.ts:27 — `fs.existsSync` in `checkFrontendArchitecture` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cellix/arch-unit-tests/src/checks/frontend-architecture.ts:30 — `fs.existsSync` in `checkFrontendArchitecture` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cellix/arch-unit-tests/src/checks/frontend-architecture.ts:33 — `fs.existsSync` in `checkFrontendArchitecture` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cellix/arch-unit-tests/src/checks/frontend-architecture.ts:36 — `fs.existsSync` in `checkFrontendArchitecture` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cellix/serenity-framework/src/cucumber/screenshot-hooks.ts:41 — `mkdirSync` in `callback to After` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cellix/serenity-framework/src/cucumber/screenshot-hooks.ts:51 — `readFileSync` in `callback to After` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cellix/service-sendgrid/src/sendgrid.ts:45 — `fs.existsSync` in `sendEmail` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cellix/service-sendgrid/src/sendgrid.ts:45 — `fs.mkdirSync` in `sendEmail` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cellix/service-sendgrid/src/sendgrid.ts:49 — `fs.writeFileSync` in `sendEmail` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.

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

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

R4 · Test Coverage · This test file cannot be loaded · ×7

This test file cannot be loaded packages/sthrift/ui-admin-route-root/src/components/pages/messages/pages/messages-page.stories.tsx:12 — packages/sthrift/ui-admin-route-root/src/components/pages/messages/pages/messages-page.stories.tsx:12 imports '../../../../index.tsx', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/sthrift/ui-sharethrift-route-root/src/app-routes.stories.tsx:2 — packages/sthrift/ui-sharethrift-route-root/src/app-routes.stories.tsx:2 imports './index.tsx', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/profile/pages/profile-page.stories.tsx:2 — packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/profile/pages/profile-page.stories.tsx:2 imports '../../../../../../index.tsx', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/pages/settings-page.stories.tsx:2 — packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/pages/settings-page.stories.tsx:2 imports '../../../../../../index.tsx', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/pages/messages-page.stories.tsx:12 — packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/pages/messages-page.stories.tsx:12 imports '../../../../index.tsx', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/sthrift/ui-sharethrift-route-shared/src/hooks/use-onboarding-redirect.stories.tsx:2 — packages/sthrift/ui-sharethrift-route-shared/src/hooks/use-onboarding-redirect.stories.tsx:2 imports './use-has-completed-onboarding-check.ts', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/sthrift/ui-sharethrift-route-signup/src/signup-routes.stories.tsx:2 — packages/sthrift/ui-sharethrift-route-signup/src/signup-routes.stories.tsx:2 imports './index.tsx', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.

P12 · CI test-gate honesty · Workspace package's tests never run by CI · ×6

Workspace package's tests never run by CI apps/docs/package.json:17 — `apps/docs` is a workspace package with 15 test(s) in 3 file(s) (e.g. `apps/docs/sidebars.test.ts`, `apps/docs/src/pages/index.test.tsx`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI apps/server-oauth2-mock/package.json:18 — `apps/server-oauth2-mock` is a workspace package with 11 test(s) in 1 file(s) (e.g. `apps/server-oauth2-mock/tests/portal-discovery.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI apps/ui-sharethrift/package.json:15 — `apps/ui-sharethrift` is a workspace package with 2 test(s) in 1 file(s) (e.g. `apps/ui-sharethrift/src/app.container.test.tsx`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI packages/cellix/serenity-framework/package.json:109 — `packages/cellix/serenity-framework` is a workspace package with 31 test(s) in 11 file(s) (e.g. `packages/cellix/serenity-framework/src/settings/settings.test.ts`, `packages/cellix/serenity-framework/src/servers/process-test-server.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI packages/cellix/service-messaging-twilio/package.json:16 — `packages/cellix/service-messaging-twilio` is a workspace package with 14 test(s) in 1 file(s) (e.g. `packages/cellix/service-messaging-twilio/src/index.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI packages/cellix/service-token-validation/package.json:1 — `packages/cellix/service-token-validation` is a workspace package with 2 test(s) in 2 file(s) (e.g. `packages/cellix/service-token-validation/src/verified-token-service.test.ts`, `packages/cellix/service-token-validation/src/index.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.

D17 · Explicit Debt · HackComment · ×4

HackComment packages/cellix/event-bus-seedwork-node/src/node-event-bus.ts:143 — // hack to create dependency title in App Insights to show up nicely in trace details — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment packages/cellix/event-bus-seedwork-node/src/node-event-bus.ts:145 — // hack (becomes upper case) — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment packages/cellix/event-bus-seedwork-node/src/node-event-bus.ts:146 — // hack — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment packages/cellix/event-bus-seedwork-node/src/node-event-bus.ts:150 — // hack - dumps payload in command — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.

D3 · God Classes · FileTooLong · ×4

FileTooLong: REDACTED packages/cellix/server-payment-seedwork/src/index.ts — FileTooLong — 954 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: startMockPaymentServer (34-1359). The bar is 500 significant lines; this is 454 over it, 1.91× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: REDACTED packages/cellix/service-payment-cybersource/src/index.ts — FileTooLong — 717 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: ServicePaymentCybersource (31-1122). The bar is 500 significant lines; this is 217 over it, 1.43× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: pages/settings-view.tsx packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/pages/settings-view.tsx — FileTooLong — 679 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: SettingsView (67-788). The bar is 500 significant lines; this is 179 over it, 1.36× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: REDACTED packages/cellix/service-payment-base/src/index.ts — FileTooLong — 520 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 20 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.

P12 · CI test-gate honesty · Runner config excludes tests no gate runs · ×4

Runner config excludes tests no gate runs packages/sthrift/application-services/vitest.config.ts:8 — `src/arch-unit-tests/**` removes 1 test(s) in 1 file(s) (e.g. `packages/sthrift/application-services/src/arch-unit-tests/application-services-conventions.test.ts`) from what vitest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.
Runner config excludes tests no gate runs packages/sthrift/domain/vitest.config.ts:10 — `src/arch-unit-tests/**` removes 1 test(s) in 1 file(s) (e.g. `packages/sthrift/domain/src/arch-unit-tests/domain-conventions.test.ts`) from what vitest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.
Runner config excludes tests no gate runs packages/sthrift/graphql/vitest.config.ts:6 — `src/arch-unit-tests/**` removes 2 test(s) in 2 file(s) (e.g. `packages/sthrift/graphql/src/arch-unit-tests/graphql-schema-conventions.test.ts`, `packages/sthrift/graphql/src/arch-unit-tests/graphql-resolver-conventions.test.ts`) from what vitest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.
Runner config excludes tests no gate runs packages/sthrift/persistence/vitest.config.ts:8 — `src/arch-unit-tests/**` removes 1 test(s) in 1 file(s) (e.g. `packages/sthrift/persistence/src/arch-unit-tests/persistence-conventions.test.ts`) from what vitest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.

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

Animation without a prefers-reduced-motion guard packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.overrides.css:120 — `.remove-image-button` moves (`transition: background 0.3s ease, transform 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/sthrift/ui-shared/src/styles/theme.css:119 — `.ant-btn-primary` moves (`transition: transform 0.18s 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.
Animation without a prefers-reduced-motion guard packages/sthrift/ui-shared/src/molecules/navigation/navigation.module.css:147 — `.sidebar` moves (`transition: transform 0.3s cubic-bezier(0.4, 0, 0.2, 1)`) 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.

D23 · Boundary Type-Coupling · Cross-context type UserEntityReference (domain → persistence) · ×3

Cross-context type UserEntityReference (domain → persistence) packages/sthrift/persistence/src/datasources/domain/conversation/conversation/conversation.repository.ts:69 — UserEntityReference (context domain) is exposed in persistence's public surface via ConversationRepository.getNewInstance — couples the contexts.
Cross-context type UserEntityReference (domain → persistence) packages/sthrift/persistence/src/datasources/domain/listing/item/item-listing.repository.ts:27 — UserEntityReference (context domain) is exposed in persistence's public surface via ItemListingRepository.getNewInstance — couples the contexts.
Cross-context type UserEntityReference (domain → persistence) packages/sthrift/persistence/src/datasources/domain/reservation-request/reservation-request/reservation-request.repository.ts:47 — UserEntityReference (context domain) is exposed in persistence's public surface via ReservationRequestRepository.getNewInstance — couples the contexts.

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

Dead file (~1 LoC) packages/sthrift-verification/acceptance-api/src/shared/support/application-services/index.ts — no import path from any entry point (147 application, 83 tooling, 573 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) packages/sthrift-verification/verification-shared/src/formatters/index.ts — no import path from any entry point (147 application, 83 tooling, 573 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) packages/sthrift/domain/src/domain/events/index.ts — no import path from any entry point (147 application, 83 tooling, 573 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

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

REDACTED
REDACTED

D35 · Change Coupling · Change coupling · ×2

Change coupling: message-thread.tsx ↔ conversations-main.tsx packages/sthrift/ui-shared/src/organisms/message-thread.tsx:1 — `packages/sthrift/ui-shared/src/organisms/message-thread.tsx` and `packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/pages/conversations-main.tsx` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `cb804189` maintained the consistency (at that commit the files were still `apps/ui-sharethrift/src/components/layouts/home/messages/components/message-thread.tsx` and `apps/ui-sharethrift/src/components/layouts/home/messages/pages/conversations-main.tsx`); `62f6eaea` Remove unused API GraphQL files and update Twilio environment variabl… (at that commit the files were still `packages/ui-sharethrift/src/components/layouts/home/messages/components/message-thread.tsx` and `packages/ui-sharethrift/src/components/layouts/home/messages/pages/Main.tsx`); `8ac3fde6` Refactor messaging components: update environment variables, remove u… (at that commit the files were still `packages/ui-sharethrift/src/components/layouts/home/messages/components/message-thread.tsx` and `packages/ui-sharethrift/src/components/layouts/home/messages/pages/Main.tsx`) — run `git show` on any of them.
Change coupling: listing-information.container.tsx ↔ view-listing.container.tsx packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/listing-information/listing-information.container.tsx:1 — `packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/listing-information/listing-information.container.tsx` and `packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/view-listing.container.tsx` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `1c59e0e4` update settings view to accept user union and implement update admin … (at that commit the files were still `apps/ui-sharethrift/src/components/layouts/home/components/view-listing/listing-information/listing-information.container.tsx` and `apps/ui-sharethrift/src/components/layouts/home/components/view-listing/view-listing.container.tsx`); `3b8f178d` refactor: standardize import styles and enhance ComponentQueryLoader … (at that commit the files were still `apps/ui-sharethrift/src/components/layouts/home/components/view-listing/listing-information/listing-information.container.tsx` and `apps/ui-sharethrift/src/components/layouts/home/components/view-listing/view-listing.container.tsx`); `4ed54c6a` moved mock data to persistence layer, ensured correct components are … (at that commit the files were still `packages/ui-sharethrift/src/components/layouts/home/components/view-listing/listing-information/listing-information.container.tsx` and `packages/ui-sharethrift/src/components/layouts/home/components/view-listing/view-listing.container.tsx`) — run `git show` on any of them.

D5 · Coupling · Off the main sequence · ×2

Off the main sequence: @cellix/service-blob-storage — @cellix/service-blob-storage: 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.
Off the main sequence: @cellix/service-otel — @cellix/service-otel: 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.

GD1 · Unfinished & placeholder code · Unfinished stub · ×2

Unfinished stub — throws a "not implemented" error packages/cellix/service-payment-cybersource/src/index.ts:1077 — A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error packages/cellix/service-payment-cybersource/src/index.ts:1109 — A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.

IC1 · Incompleteness & stubs · Unfinished stub · ×2

Unfinished stub — throws a "not implemented" exception packages/cellix/service-payment-cybersource/src/index.ts:1077 — `listOfPlans` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception packages/cellix/service-payment-cybersource/src/index.ts:1109 — `listOfSubscriptions` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.

P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×2

Outbound HTTP without resilience build-pipeline/scripts/check-sonar-quality-gate.cjs:54 — `https.request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience build-pipeline/scripts/local-https-proxy.js:97 — `http.request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.

R10 · Code Duplication · Duplication concentrated across 3 sibling directories (5 clone groups) · ×2

Duplication concentrated across 3 sibling directories (5 clone groups) packages/sthrift/domain/src/domain/contexts/user/admin-user/admin-user.aggregate.ts:19 — 5 duplicated blocks under packages/sthrift/domain/src/domain/contexts/user/ have copies in at least two of the sibling directories admin-user, personal-user, role — 2 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (5 clone groups) packages/sthrift/persistence/src/datasources/domain/listing/item/item-listing.repository.ts:97 — 5 duplicated blocks under packages/sthrift/persistence/src/datasources/ have copies in at least two of the sibling directories domain, payment, readonly — 2 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

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

Duplicated block with local edits (75 matched lines × 2 locations) packages/cellix/serenity-framework/src/pages/adapters/dom-adapter.ts:86 — packages/cellix/serenity-framework/src/pages/adapters/dom-adapter.ts:86 · packages/sthrift-verification/verification-shared/src/pages/adapters/jsdom-adapter.ts:76 — the two spans are one implementation copied and then locally edited — 692 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.
Duplicated block with local edits (75 matched lines × 2 locations) packages/sthrift/ui-admin-route-root/src/components/pages/messages/components/conversation-list.container.tsx:12 — packages/sthrift/ui-admin-route-root/src/components/pages/messages/components/conversation-list.container.tsx:12 · packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/components/conversation-list.container.tsx:12 — the two spans are one implementation copied and then locally edited — 303 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 (73 matched lines × 2 locations) · ×2

Duplicated block with local edits (73 matched lines × 2 locations) packages/cellix/server-messaging-seedwork/src/routes/messages.ts:5 — packages/cellix/server-messaging-seedwork/src/routes/messages.ts:5 · packages/cellix/server-messaging-seedwork/src/routes/participants.ts:5 — the two spans are one implementation copied and then locally edited — 498 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.
Duplicated block with local edits (73 matched lines × 2 locations) packages/cellix/service-messaging-mock/src/index.ts:34 — packages/cellix/service-messaging-mock/src/index.ts:34 · packages/cellix/service-messaging-twilio/src/index.ts:51 — the two spans are one implementation copied and then locally edited — 500 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 (53 lines × 2 locations) · ×2

Duplicated block (53 lines × 2 locations) packages/sthrift/domain/src/domain/contexts/user/role/admin-role/admin-role-listing-permissions.ts:23 — packages/sthrift/domain/src/domain/contexts/user/role/admin-role/admin-role-listing-permissions.ts:23 · packages/sthrift/persistence/src/datasources/domain/role/admin-role/admin-role.domain-adapter.ts:216 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents.
Duplicated block (53 lines × 2 locations) packages/sthrift/domain/src/domain/contexts/user/role/admin-role/admin-role-user-permissions.ts:23 — packages/sthrift/domain/src/domain/contexts/user/role/admin-role/admin-role-user-permissions.ts:23 · packages/sthrift/persistence/src/datasources/domain/role/admin-role/admin-role.domain-adapter.ts:99 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents.

AC6 · Visual & motion safety · Low contrast Tailwind colour pair (2.5 · ×1

Low contrast Tailwind colour pair (2.5:1) packages/sthrift/ui-shared/src/organisms/listing-information.tsx:27 — This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.

AC6 · Visual & motion safety · Low contrast colour pair in CSS (4.4 · ×1

Low contrast colour pair in CSS (4.4:1) packages/sthrift/ui-shared/src/styles/theme.css:352 — `.sharer, .sharerIcon` sets color: #fefdfa on background-color: #3f8176 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.

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

Focus outline removed in CSS without a :focus replacement packages/sthrift/ui-shared/src/molecules/listing-card/listing-card.module.css:20 — `.imageContainer` 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.

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

Accessibility enforcement below the top rung — No accessibility enforcement found — your Biome config enables no a11y rules and there's no axe/pa11y/Lighthouse in tests or CI. Start by turning on Biome's own a11y rule group to catch issues at author time. What was searched, so you can tell an absence from a miss: the 163 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

D1 · Cyclomatic Complexity · router.buildOidcRouter (cyclomatic 57) · ×1

router.buildOidcRouter (cyclomatic 57) REDACTED:31 — router.buildOidcRouter has cyclomatic complexity 57 (threshold 15). Most of this is not in the body itself: 4 of the 57 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 130, 292, 81, …). 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 · settings-view.SettingsView (cyclomatic 50) · ×1

settings-view.SettingsView (cyclomatic 50) packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/pages/settings-view.tsx:67 — settings-view.SettingsView has cyclomatic complexity 50 (threshold 15). Most of this is not in the body itself: 1 of the 50 points is its own statement and the rest belongs to 17 function items inside it that branch (renderPlanCard, renderLocationSection, beginEdit, …). 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 · reservation-request-form.ReservationRequestForm (cyclomatic 29) · ×1

reservation-request-form.ReservationRequestForm (cyclomatic 29) packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/reservation-request-form.tsx:51 — reservation-request-form.ReservationRequestForm has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 2 of the 29 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 219, a function literal at line 137, handleDateRangeChange, …). 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 · create-listing.CreateListing (cyclomatic 27) · ×1

create-listing.CreateListing (cyclomatic 27) packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.tsx:40 — create-listing.CreateListing has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 9 of the 27 points are its own statements and the rest belongs to 7 function items inside it that branch (handleFormSubmit, a function literal at line 128, a function literal at line 94, …). 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 · all-listings-table.AllListingsTable (cyclomatic 25) · ×1

all-listings-table.AllListingsTable (cyclomatic 25) packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.tsx:40 — all-listings-table.AllListingsTable has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 4 of the 25 points are its own statements and the rest belongs to 9 function items inside it that branch (getActionButtons, a function literal at line 250, a function literal at line 341, …). 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 · settings-view.container.SettingsViewLoader (cyclomatic 25) · ×1

settings-view.container.SettingsViewLoader (cyclomatic 25) packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-view.container.tsx:17 — settings-view.container.SettingsViewLoader has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 4 of the 25 points are its own statements and the rest belongs to 5 function items inside it that branch (buildNextProfile, handlePersonalUserSave, handleSaveSection, …). 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 · conversations.setupConversationRoutes (cyclomatic 17) · ×1

conversations.setupConversationRoutes (cyclomatic 17) REDACTED:5 — conversations.setupConversationRoutes has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 55, 96, 6, …). 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 · PersonalUserReadRepositoryImpl.getAllUsers (cyclomatic 17) · ×1

PersonalUserReadRepositoryImpl.getAllUsers (cyclomatic 17) packages/sthrift/persistence/src/datasources/readonly/user/personal-user/personal-user.read-repository.ts:61 — PersonalUserReadRepositoryImpl.getAllUsers has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 belong to 5 function literals inside it that branch. 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 · AdminUserReadRepositoryImpl.getAllUsers (cyclomatic 17) · ×1

AdminUserReadRepositoryImpl.getAllUsers (cyclomatic 17) packages/sthrift/persistence/src/datasources/readonly/user/admin-user/admin-user.read-repository.ts:67 — AdminUserReadRepositoryImpl.getAllUsers has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 belong to 5 function literals inside it that branch. 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 · admin-users-table.AdminUsersTable (cyclomatic 16) · ×1

admin-users-table.AdminUsersTable (cyclomatic 16) packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.tsx:33 — admin-users-table.AdminUsersTable has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 178, a function literal at line 265, handleBlockConfirm, …). 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.

D15 · Churn × Complexity Hotspots · Hotspot · ×1

Hotspot: packages/sthrift-verification/e2e-tests/src/contexts/listing/tasks/create-listing.ts packages/sthrift-verification/e2e-tests/src/contexts/listing/tasks/create-listing.ts:21 — packages/sthrift-verification/e2e-tests/src/contexts/listing/tasks/create-listing.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in CreateListing.performAs at line 21. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-04-09..2026-07-08, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-09 11:13:48 -04:00' --until='2026-07-08 11:13:48 -04:00' --full-history --no-merges -- packages/sthrift-verification/e2e-tests/src/contexts/listing/tasks/create-listing.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.

D2 · Cognitive Complexity · router.buildOidcRouter (cognitive 61) · ×1

router.buildOidcRouter (cognitive 61) REDACTED:31 — router.buildOidcRouter has cognitive complexity 61 (threshold 15). Drivers by points: if/else 25 (30 pts), ternaries 14, boolean chains 10, error handling 5 (7 pts) (nesting depth added 7). Most of this is not in the body itself: 5 of the 61 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 130, 292, 81, …). 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 · settings-view.SettingsView (cognitive 49) · ×1

settings-view.SettingsView (cognitive 49) packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/pages/settings-view.tsx:67 — settings-view.SettingsView has cognitive complexity 49 (threshold 15). Drivers by points: boolean chains 17, ternaries 17, if/else 11, error handling 4. None of this is in the body itself: all 49 points belong to 17 function items inside it that branch (renderPlanCard, renderLocationSection, beginEdit, …). 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 · reservation-request-form.ReservationRequestForm (cognitive 35) · ×1

reservation-request-form.ReservationRequestForm (cognitive 35) packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/reservation-request-form.tsx:51 — reservation-request-form.ReservationRequestForm has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (13 pts), ternaries 7 (13 pts), boolean chains 8, loops 1 (nesting depth added 7). Most of this is not in the body itself: 1 of the 35 points is its own statement and the rest belongs to 5 function items inside it that branch (a function literal at line 219, a function literal at line 137, handleDateRangeChange::isRangeValid, …). 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 · create-listing.CreateListing (cognitive 31) · ×1

create-listing.CreateListing (cognitive 31) packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.tsx:40 — create-listing.CreateListing has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 14, if/else 10 (12 pts), ternaries 4 (5 pts) (nesting depth added 3). Most of this is not in the body itself: 8 of the 31 points are its own statements and the rest belongs to 7 function items inside it that branch (handleFormSubmit, a function literal at line 128, a function literal at line 204, …). 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 · verifyManifestData (cognitive 30) · ×1

verifyManifestData (cognitive 30) .github/hooks/shared.mjs:226 — verifyManifestData has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (26 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ReservationRequestReadRepositoryImpl.getListingRequestsBySharerId (cognitive 25) · ×1

ReservationRequestReadRepositoryImpl.getListingRequestsBySharerId (cognitive 25) packages/sthrift/persistence/src/datasources/readonly/reservation-request/reservation-request/reservation-request.read-repository.ts:197 — ReservationRequestReadRepositoryImpl.getListingRequestsBySharerId has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (19 pts), ternaries 2 (6 pts) (nesting depth added 12). 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 · all-listings-table.AllListingsTable (cognitive 25) · ×1

all-listings-table.AllListingsTable (cognitive 25) packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.tsx:40 — all-listings-table.AllListingsTable has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 11 (12 pts), if/else 7, boolean chains 6 (nesting depth added 1). Most of this is not in the body itself: 3 of the 25 points are its own statements and the rest belongs to 9 function items inside it that branch (getActionButtons, a function literal at line 250, a function literal at line 341, …). 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 · settings-view.container.SettingsViewLoader (cognitive 25) · ×1

settings-view.container.SettingsViewLoader (cognitive 25) packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-view.container.tsx:17 — settings-view.container.SettingsViewLoader has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 14 (15 pts), if/else 7, boolean chains 2, error handling 1 (nesting depth added 1). Most of this is not in the body itself: 3 of the 25 points are its own statements and the rest belongs to 5 function items inside it that branch (buildNextProfile, handlePersonalUserSave, handleSaveSection, …). 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 · check-sonar-quality-gate.pollTaskStatus (cognitive 18) · ×1

check-sonar-quality-gate.pollTaskStatus (cognitive 18) build-pipeline/scripts/check-sonar-quality-gate.cjs:70 — check-sonar-quality-gate.pollTaskStatus has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (14 pts), error handling 2 (3 pts), boolean chains 1 (nesting depth added 4). None of this is in the body itself: all 18 points belong to 2 function literals inside it that branch (lines 71, 98). 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 · conversations.setupConversationRoutes (cognitive 17) · ×1

conversations.setupConversationRoutes (cognitive 17) REDACTED:5 — conversations.setupConversationRoutes has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), error handling 5, boolean chains 2 (nesting depth added 1). None of this is in the body itself: all 17 points belong to 5 function literals inside it that branch (lines 55, 6, 96, …). 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 · admin-listings-table.container.AdminListings (cognitive 17) · ×1

admin-listings-table.container.AdminListings (cognitive 17) packages/sthrift/ui-admin-route-listing-operations/src/components/pages/admin-listing-operations/components/admin-listings-table/admin-listings-table.container.tsx:13 — admin-listings-table.container.AdminListings has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (6 pts), if/else 5, boolean chains 4, error handling 1 (2 pts) (nesting depth added 3). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 109, 117, 46, …). 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 · detect-changes.detectChanges (cognitive 16) · ×1

detect-changes.detectChanges (cognitive 16) build-pipeline/scripts/detect-changes.cjs:154 — detect-changes.detectChanges has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 4 (nesting depth added 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.

D2 · Cognitive Complexity · PersonalUserReadRepositoryImpl.getAllUsers (cognitive 16) · ×1

PersonalUserReadRepositoryImpl.getAllUsers (cognitive 16) packages/sthrift/persistence/src/datasources/readonly/user/personal-user/personal-user.read-repository.ts:61 — PersonalUserReadRepositoryImpl.getAllUsers has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 4 (5 pts), boolean chains 3 (nesting depth added 5). Of this number, 10 points are the body's own statements and 6 belong to 5 function literals inside it that branch. 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 · AdminUserReadRepositoryImpl.getAllUsers (cognitive 16) · ×1

AdminUserReadRepositoryImpl.getAllUsers (cognitive 16) packages/sthrift/persistence/src/datasources/readonly/user/admin-user/admin-user.read-repository.ts:67 — AdminUserReadRepositoryImpl.getAllUsers has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 4 (5 pts), boolean chains 3 (nesting depth added 5). Of this number, 10 points are the body's own statements and 6 belong to 5 function literals inside it that branch. 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 · admin-users-table.AdminUsersTable (cognitive 16) · ×1

admin-users-table.AdminUsersTable (cognitive 16) packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.tsx:33 — admin-users-table.AdminUsersTable has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 9, if/else 5, boolean chains 1, error handling 1. Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 265, a function literal at line 178, handleBlockConfirm, …). 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 · all-listings-card.AllListingsCard (cognitive 16) · ×1

all-listings-card.AllListingsCard (cognitive 16) packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-card.tsx:14 — all-listings-card.AllListingsCard has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (7 pts), if/else 5, boolean chains 4 (nesting depth added 2). Of this number, 8 points are the body's own statements and 8 belong to one function item inside it that branches. 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.

D2 · Cognitive Complexity · denyIfManifestGate (cognitive 16) · ×1

denyIfManifestGate (cognitive 16) .github/hooks/pre-tool-use.mjs:57 — denyIfManifestGate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (6 pts), ternaries 2 (6 pts), boolean chains 4 (nesting depth added 6). 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.

D20 · ADR Quality · Context/problem and consequences/trade-offs fall below the clip marker (only Control Classification and a partial review-process architecture are shown) · ×1

Context/problem and consequences/trade-offs fall below the clip marker (only Control Classification and a partial review-process architecture are shown) apps/docs/docs/security-requirements/0004-listing-appeal-review.md — Add a Context/Problem section explaining why blocked listings must be reviewed before reinstatement (e.g. prevent abuse of unblocked listing status) and a Consequences section covering trade-offs such as administrative burden and audit friction

D20 · ADR Quality · No problem statement or explicit decision · ×1

No problem statement or explicit decision: the body is a classification dump listing assessment type, coverage, status, and compensating controls with no context/problem and no decision (e.g. adopt CodeQL vs SonarCloud) stated apps/docs/docs/threat-assessments/0001-code-ql.md — State the concrete security problem the decision addresses (e.g. gap in SAST coverage against SQL/XSS) and the explicit decision (adopt CodeQL or SonarCloud, which one to use). Add a Consequences section on trade-offs of each choice.

D20 · ADR Quality · No explicit Decision statement (what EdgeScan will do or deliver) and no consequences/trade-offs section are visible before the clip marker · ×1

No explicit Decision statement (what EdgeScan will do or deliver) and no consequences/trade-offs section are visible before the clip marker apps/docs/docs/threat-assessments/0002-edgescan.md

D20 · ADR Quality · No explicit decision (what Dependabot will do or not do) is present; only status/pending is declared · ×1

No explicit decision (what Dependabot will do or not do) is present; only status/pending is declared apps/docs/docs/threat-assessments/0003-github-dependabot.md — Replace the Status note with a Decision section stating whether GitHub Dependabot is adopted as SCA/dependency updater and what trade-offs accompany it

D20 · ADR Quality · No explicit decision (when REDACTED Scanning will be implemented) and consequences/trade-offs are not visible in the excerpt · ×1

No explicit decision (when REDACTED Scanning will be implemented) and consequences/trade-offs are not visible in the excerpt apps/docs/docs/threat-assessments/0005-secret-scanning.md

D22 · Internal API Consistency · Inconsistent lifecycle method signatures across TestServer implementations. `resetForScenario` returns `Promise<void> | void` in the base interface, but specific implementations like `MongoMemoryProcessTestServer` and `MongoMemoryTestServer` return `Promise<void>`. This creates ambiguity for consumers regarding whether they must await the result. · ×1

Inconsistent lifecycle method signatures across TestServer implementations. `resetForScenario` returns `Promise<void> | void` in the base interface, but specific implementations like `MongoMemoryProcessTestServer` and `MongoMemoryTestServer` return `Promise<void>`. This creates ambiguity for consumers regarding whether they must await the result. — Standardize `resetForScenario` to always return `Promise<void>` across all implementations and the base interface to ensure consistent async handling. (signatures: TestServer.start(): Promise<void> | TestServer.stop(): Promise<void> | TestServer.isRunning(): boolean | TestServer.getUrl(): string | TestServer.resetForScenario(): Promise<void> | void)

D22 · Internal API Consistency · Inconsistent return type for `startUp`. The return type is a complex generic exclusion (`Promise<Exclude<T, ServiceBase>>`) which is likely intended to enforce that the instance is initialized, but the syntax varies slightly (spacing) and the type complexity is high. More importantly, `ServiceMessagingMock` and `ServiceMessagingTwilio` share this pattern, but `ServicePaymentCybersource` and `ServicePaymentMock` also share it. However, `TestServer` implementations use `start() · ×1

Inconsistent return type for `startUp`. The return type is a complex generic exclusion (`Promise<Exclude<T, ServiceBase>>`) which is likely intended to enforce that the instance is initialized, but the syntax varies slightly (spacing) and the type complexity is high. More importantly, `ServiceMessagingMock` and `ServiceMessagingTwilio` share this pattern, but `ServicePaymentCybersource` and `ServicePaymentMock` also share it. However, `TestServer` implementations use `start(): Promise<void>`. The inconsistency lies between the `Service*` classes (which return the instance for chaining or type narrowing) and the `TestServer` classes (which return void). While this might be intentional, it forces consumers to handle the return value differently depending on the service type. — Decide on a single pattern for service initialization. Either all services should return `Promise<void>` (simpler) or all should return `Promise<this>` (for fluent chaining). The current `Exclude` pattern is overly complex and inconsistent with the `TestServer` abstraction. (signatures: ServiceMessagingMock.startUp(): Promise<Exclude<ServiceMessagingMock, ServiceBase>> | ServiceMessagingTwilio.startUp(): Promise<Exclude<ServiceMessagingTwilio, ServiceBase>> | ServicePaymentCybersource.startUp(): Promise< Exclude<ServicePaymentCybersource, ServiceBase<ServicePaymentCybersource>> > | ServicePaymentMock.startUp(): Promise< Exclude<ServicePaymentMock, ServiceBase<ServicePaymentMock>> >)

D22 · Internal API Consistency · Redundant factory methods. `GherkinDataTable` has both a constructor and a static `from` method that take the exact same argument (`DataTable`) and return the same type. This offers no benefit and increases API surface unnecessarily. · ×1

Redundant factory methods. `GherkinDataTable` has both a constructor and a static `from` method that take the exact same argument (`DataTable`) and return the same type. This offers no benefit and increases API surface unnecessarily. — Remove the static `from` method and rely solely on the constructor, or vice versa, to reduce confusion. (signatures: GherkinDataTable.from(dataTable: DataTable): GherkinDataTable | GherkinDataTable.constructor(dataTable: DataTable))

D22 · Internal API Consistency · Ambiguous method naming. `unmount` and `discard` are both void methods on `RenderInDom`. It is unclear if they perform the same action (cleanup) or if `discard` implies a different semantic (e.g., ignoring errors vs. standard cleanup). If they do the same thing, it is a duplicate. If they differ, the names are not distinct enough to convey the difference. · ×1

Ambiguous method naming. `unmount` and `discard` are both void methods on `RenderInDom`. It is unclear if they perform the same action (cleanup) or if `discard` implies a different semantic (e.g., ignoring errors vs. standard cleanup). If they do the same thing, it is a duplicate. If they differ, the names are not distinct enough to convey the difference. — Clarify the distinction. If they are identical, remove one. If `discard` is a no-op or error-tolerant unmount, rename it to `unmountSilently` or similar to indicate the behavioral difference. (signatures: RenderInDom.unmount(): void | RenderInDom.discard(): void)

D23 · Boundary Type-Coupling · Cross-context type UserEntityReference (domain → acceptance-api) · ×1

Cross-context type UserEntityReference (domain → acceptance-api) packages/sthrift-verification/acceptance-api/src/shared/support/domain-test-helpers.ts:42 — UserEntityReference (context domain) is exposed in acceptance-api's public surface via domain-test-helpers.makeSharerUser — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type UserEntityReference (domain → acceptance-ui) · ×1

Cross-context type UserEntityReference (domain → acceptance-ui) packages/sthrift-verification/acceptance-ui/src/shared/support/domain-test-helpers.ts:66 — UserEntityReference (context domain) is exposed in acceptance-ui's public surface via domain-test-helpers.makeSharerUser — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type UserEntityReference (domain → application-services) · ×1

Cross-context type UserEntityReference (domain → application-services) packages/sthrift/application-services/src/contexts/listing/item/create.ts:5 — UserEntityReference (context domain) is exposed in application-services's public surface via ItemListingCreateCommand.sharer — couples the contexts.

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

REDACTED

D3 · God Classes · ClassTooLong · ×1

ClassTooLong: ServicePaymentCybersource packages/cellix/service-payment-cybersource/src/index.ts:31 — ClassTooLong — 693 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 400 significant lines; this is 293 over it, 1.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

D3 · God Classes · TooManyMethods · ×1

TooManyMethods: ServicePaymentCybersource packages/cellix/service-payment-cybersource/src/index.ts:31 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

D30 · Dependency Vulnerabilities · Medium vulnerability · ×1

REDACTED

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

REDACTED

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

Low cohesion: ServicePaymentCybersource (LCOM4 6) packages/cellix/service-payment-cybersource/src/index.ts:31 — ServicePaymentCybersource'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.

P2 · Observability · No structured logging · ×1

No structured logging — No logging call was found in the 882 JavaScript/TypeScript production file(s) this check read across 54 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.

R10 · Code Duplication · Duplication concentrated across 12 sibling directories (52 clone groups) · ×1

Duplication concentrated across 12 sibling directories (52 clone groups) packages/sthrift/ui-admin-route-root/src/components/pages/home/components/listings-page.container.tsx:1 — 52 duplicated blocks under packages/sthrift/ have copies in at least two of the sibling directories application-services, domain, graphql, persistence, ui-admin-route-listing-operations, ui-admin-route-root (+6 more sibling(s) not listed) — 37 of them are reported below, and 15 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 52 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 52 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 52 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Duplication concentrated across 7 sibling directories (21 clone groups) · ×1

Duplication concentrated across 7 sibling directories (21 clone groups) packages/sthrift/persistence/src/datasources/domain/role/admin-role/admin-role.domain-adapter.ts:27 — 21 duplicated blocks under packages/sthrift/persistence/src/datasources/domain/ have copies in at least two of the sibling directories account-plan, appeal-request, conversation, listing, reservation-request, role (+1 more sibling(s) not listed) — 8 of them are reported below, and 13 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 21 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 21 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 21 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Duplication concentrated across 6 sibling directories (16 clone groups) · ×1

Duplication concentrated across 6 sibling directories (16 clone groups) packages/sthrift/application-services/src/contexts/listing/item/cancel.ts:4 — 16 duplicated blocks under packages/sthrift/application-services/src/contexts/ have copies in at least two of the sibling directories account-plan, appeal-request, conversation, listing, reservation-request, user — 9 of them are reported below, and 7 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 16 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 16 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 16 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Duplication concentrated across 6 sibling directories (13 clone groups) · ×1

Duplication concentrated across 6 sibling directories (13 clone groups) packages/sthrift/domain/src/domain/contexts/conversation/conversation/conversation.aggregate.ts:155 — 13 duplicated blocks under packages/sthrift/domain/src/domain/contexts/ have copies in at least two of the sibling directories account-plan, appeal-request, conversation, listing, reservation-request, user — 4 of them are reported below, and 9 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 13 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Duplication concentrated across 3 sibling directories (11 clone groups) · ×1

Duplication concentrated across 3 sibling directories (11 clone groups) packages/cellix/serenity-framework/src/formatters/agent-formatter.ts:11 — 11 duplicated blocks under packages/ have copies in at least two of the sibling directories cellix, sthrift, sthrift-verification — 8 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 11 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Duplication concentrated across 3 sibling directories (10 clone groups) · ×1

Duplication concentrated across 3 sibling directories (10 clone groups) packages/sthrift-verification/acceptance-api/src/contexts/reservation-request/step-definitions/create-reservation-request.steps.ts:1 — 10 duplicated blocks under packages/sthrift-verification/ have copies in at least two of the sibling directories acceptance-api, acceptance-ui, verification-shared — 8 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Duplication concentrated across 2 sibling directories (8 clone groups) · ×1

Duplication concentrated across 2 sibling directories (8 clone groups) packages/sthrift/domain/src/domain/iam/user/admin-user/admin-user.passport.ts:16 — 8 duplicated blocks under packages/sthrift/domain/src/domain/iam/user/ have copies in at least two of the sibling directories admin-user, personal-user — 4 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Duplication concentrated across 4 sibling directories (6 clone groups) · ×1

Duplication concentrated across 4 sibling directories (6 clone groups) apps/ui-admin/src/main.tsx:12 — 6 duplicated blocks under apps/ have copies in at least two of the sibling directories server-messaging-mock, server-payment-mock, ui-admin, ui-sharethrift — 4 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Duplication concentrated across 5 sibling directories (5 clone groups) · ×1

Duplication concentrated across 5 sibling directories (5 clone groups) packages/sthrift/persistence/src/datasources/readonly/conversation/conversation/conversation.read-repository.ts:11 — 5 duplicated blocks under packages/sthrift/persistence/src/datasources/readonly/ have copies in at least two of the sibling directories account-plan, conversation, listing, reservation-request, user — 2 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Wholesale file copy (160 identical lines × 2 files) · ×1

Wholesale file copy (160 identical lines × 2 files) packages/sthrift-verification/acceptance-api/src/contexts/reservation-request/step-definitions/create-reservation-request.steps.ts:1 — packages/sthrift-verification/acceptance-api/src/contexts/reservation-request/step-definitions/create-reservation-request.steps.ts:1 · packages/sthrift-verification/acceptance-ui/src/contexts/reservation-request/step-definitions/create-reservation-request.steps.ts:1 — these 2 files are line-for-line copies of one another — 160 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 with local edits (122 matched lines × 2 locations) · ×1

Duplicated block with local edits (122 matched lines × 2 locations) packages/cellix/serenity-framework/src/infrastructure/api-infrastructure.ts:96 — packages/cellix/serenity-framework/src/infrastructure/api-infrastructure.ts:96 · packages/cellix/serenity-framework/src/infrastructure/e2e-infrastructure.ts:167 — the two spans are one implementation copied and then locally edited — 924 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 · Wholesale file copy (122 identical lines × 2 files) · ×1

Wholesale file copy (122 identical lines × 2 files) packages/sthrift-verification/acceptance-api/src/shared/support/domain-test-helpers.ts:1 — packages/sthrift-verification/acceptance-api/src/shared/support/domain-test-helpers.ts:1 · packages/sthrift-verification/acceptance-ui/src/shared/support/domain-test-helpers.ts:1 — these 2 files are line-for-line copies of one another — 122 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 · Wholesale file copy (101 identical lines × 2 files) · ×1

Wholesale file copy (101 identical lines × 2 files) packages/sthrift-verification/acceptance-api/src/contexts/listing/step-definitions/create-listing.steps.ts:1 — packages/sthrift-verification/acceptance-api/src/contexts/listing/step-definitions/create-listing.steps.ts:1 · packages/sthrift-verification/acceptance-ui/src/contexts/listing/step-definitions/create-listing.steps.ts:1 — these 2 files are line-for-line copies of one another — 101 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 with local edits (96 matched lines × 2 locations) · ×1

Duplicated block with local edits (96 matched lines × 2 locations) packages/sthrift/persistence/src/datasources/domain/appeal-request/listing-appeal-request/listing-appeal-request.domain-adapter.ts:10 — packages/sthrift/persistence/src/datasources/domain/appeal-request/listing-appeal-request/listing-appeal-request.domain-adapter.ts:10 · packages/sthrift/persistence/src/datasources/domain/appeal-request/user-appeal-request/user-appeal-request.domain-adapter.ts:7 — the two spans are one implementation copied and then locally edited — 599 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 (92 lines × 2 locations) · ×1

Duplicated block (92 lines × 2 locations) packages/sthrift/persistence/src/datasources/readonly/user/admin-user/admin-user.read-repository.ts:67 — packages/sthrift/persistence/src/datasources/readonly/user/admin-user/admin-user.read-repository.ts:67 · packages/sthrift/persistence/src/datasources/readonly/user/personal-user/personal-user.read-repository.ts:61 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.

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

Duplicated block with local edits (89 matched lines × 2 locations) packages/sthrift/persistence/src/datasources/domain/user/admin-user/admin-user.domain-adapter.ts:25 — packages/sthrift/persistence/src/datasources/domain/user/admin-user/admin-user.domain-adapter.ts:25 · packages/sthrift/persistence/src/datasources/domain/user/personal-user/personal-user.domain-adapter.ts:69 — the two spans are one implementation copied and then locally edited — 437 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 · Wholesale file copy (84 identical lines × 2 files) · ×1

Wholesale file copy (84 identical lines × 2 files) packages/sthrift/ui-admin-route-root/src/components/pages/home/components/listings-page.container.tsx:1 — packages/sthrift/ui-admin-route-root/src/components/pages/home/components/listings-page.container.tsx:1 · packages/sthrift/ui-sharethrift-route-root/src/components/pages/home/components/listings-page.container.tsx:1 — these 2 files are line-for-line copies of one another — 84 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 (83 lines × 2 locations) · ×1

Duplicated block (83 lines × 2 locations) packages/sthrift/graphql/src/schema/types/listing-appeal-request.resolvers.ts:19 — packages/sthrift/graphql/src/schema/types/listing-appeal-request.resolvers.ts:19 · packages/sthrift/graphql/src/schema/types/user-appeal-request.resolvers.ts:17 — 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 with local edits (80 matched lines × 2 locations) · ×1

Duplicated block with local edits (80 matched lines × 2 locations) packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.tsx:189 — packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.tsx:189 · packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/requests-table.tsx:82 — the two spans are one implementation copied and then locally edited — 508 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 · Wholesale file copy (77 identical lines × 3 files) · ×1

Wholesale file copy (77 identical lines × 3 files) packages/sthrift/ui-admin-route-listing-operations/src/section-layout.tsx:1 — packages/sthrift/ui-admin-route-listing-operations/src/section-layout.tsx:1 · packages/sthrift/ui-admin-route-root/src/section-layout.tsx:1 · packages/sthrift/ui-admin-route-user-operations/src/section-layout.tsx:1 — these 3 files are line-for-line copies of one another — 77 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 with local edits (76 matched lines × 2 locations) · ×1

Duplicated block with local edits (76 matched lines × 2 locations) packages/cellix/serenity-framework/src/formatters/agent-formatter.ts:11 — packages/cellix/serenity-framework/src/formatters/agent-formatter.ts:11 · packages/sthrift-verification/verification-shared/src/formatters/agent-formatter.ts:23 — the two spans are one implementation copied and then locally edited — 644 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 · Wholesale file copy (75 identical lines × 2 files) · ×1

Wholesale file copy (75 identical lines × 2 files) packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/sharer-information/sharer-information.container.tsx:1 — packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/sharer-information/sharer-information.container.tsx:1 · packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/sharer-information/sharer-information.container.tsx:1 — these 2 files are line-for-line copies of one another — 75 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 · Wholesale file copy (70 identical lines × 2 files) · ×1

Wholesale file copy (70 identical lines × 2 files) packages/sthrift/ui-admin-route-root/src/components/pages/messages/components/conversation-box.container.tsx:1 — packages/sthrift/ui-admin-route-root/src/components/pages/messages/components/conversation-box.container.tsx:1 · packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/components/conversation-box.container.tsx:1 — these 2 files are line-for-line copies of one another — 70 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 with local edits (66 matched lines × 2 locations) · ×1

Duplicated block with local edits (66 matched lines × 2 locations) packages/sthrift/persistence/src/datasources/readonly/conversation/conversation/conversation.read-repository.ts:11 — packages/sthrift/persistence/src/datasources/readonly/conversation/conversation/conversation.read-repository.ts:11 · packages/sthrift/persistence/src/datasources/readonly/reservation-request/reservation-request/reservation-request.read-repository.ts:18 — the two spans are one implementation copied and then locally edited — 377 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 (61 matched lines × 2 locations) · ×1

Duplicated block with local edits (61 matched lines × 2 locations) packages/cellix/server-payment-seedwork/src/index.ts:525 — packages/cellix/server-payment-seedwork/src/index.ts:525 · packages/cellix/server-payment-seedwork/src/index.ts:613 — the two spans are one implementation copied and then locally edited — 225 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

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

Duplicated block (56 lines × 2 locations) packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-draft-success.tsx:6 — packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-draft-success.tsx:6 · packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing-success.tsx:7 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.

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

Duplicated block with local edits (55 matched lines × 2 locations) packages/sthrift/application-services/src/contexts/conversation/conversation/query-by-id.ts:4 — packages/sthrift/application-services/src/contexts/conversation/conversation/query-by-id.ts:4 · packages/sthrift/application-services/src/contexts/conversation/conversation/query-by-user.ts:4 — the two spans are one implementation copied and then locally edited — 312 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 (54 lines × 2 locations) · ×1

Duplicated block (54 lines × 2 locations) packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-card.tsx:24 — packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-card.tsx:24 · packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.tsx: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 (50 lines × 2 locations) · ×1

Duplicated block (50 lines × 2 locations) packages/sthrift/data-sources-mongoose-models/src/models/appeal-request/listing-appeal-request.model.ts:43 — packages/sthrift/data-sources-mongoose-models/src/models/appeal-request/listing-appeal-request.model.ts:43 · packages/sthrift/data-sources-mongoose-models/src/models/appeal-request/user-appeal-request.model.ts:33 — 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 with local edits (50 matched lines × 2 locations) · ×1

Duplicated block with local edits (50 matched lines × 2 locations) packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/view-listing.container.tsx:11 — packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/view-listing.container.tsx:11 · packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/view-listing.container.tsx:12 — the two spans are one implementation copied and then locally edited — 283 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 (49 lines × 2 locations) · ×1

Duplicated block (49 lines × 2 locations) packages/cellix/serenity-framework/src/pages/adapters/playwright-adapter.ts:7 — packages/cellix/serenity-framework/src/pages/adapters/playwright-adapter.ts:7 · packages/sthrift-verification/verification-shared/src/pages/adapters/playwright-adapter.ts:15 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.

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

Duplicated block with local edits (49 matched lines × 2 locations) packages/sthrift/domain/src/domain/contexts/user/admin-user/admin-user.aggregate.ts:19 — packages/sthrift/domain/src/domain/contexts/user/admin-user/admin-user.aggregate.ts:19 · packages/sthrift/domain/src/domain/contexts/user/personal-user/personal-user.aggregate.ts:18 — the two spans are one implementation copied and then locally edited — 267 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.

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

Boundary violation [package:test-suite-dependency] packages/sthrift-verification/verification-shared/src/servers/test-mongodb-server.ts:2 — packages/sthrift-verification/verification-shared/src/servers/test-mongodb-server.ts:2 imports packages/sthrift-verification/verification-shared/src/test-data/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.

R2 · Cyclomatic Complexity · Complex function ThemeDemo (cyclomatic 37, cognitive 36) · ×1

Complex function ThemeDemo (cyclomatic 37, cognitive 36) packages/sthrift/ui-shared/src/theme/theme-demo/ThemeDemo.tsx:39 — ThemeDemo has cyclomatic complexity 37 and cognitive complexity 36; 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 31, cognitive 22) · ×1

Complex function (anonymous) (cyclomatic 31, cognitive 22) packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-view.container.tsx:76 — (anonymous) has cyclomatic complexity 31 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 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 (top-level) (cyclomatic 27, cognitive 26) · ×1

Complex function (top-level) (cyclomatic 27, cognitive 26) packages/sthrift/domain/src/domain/contexts/value-objects.ts:1 — (top-level) has cyclomatic complexity 27 and cognitive complexity 26; 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 checkLayeredArchitecture (cyclomatic 25, cognitive 36) · ×1

Complex function checkLayeredArchitecture (cyclomatic 25, cognitive 36) packages/cellix/arch-unit-tests/src/checks/circular-dependencies.ts:58 — checkLayeredArchitecture has cyclomatic complexity 25 and cognitive complexity 36; 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 performAs (cyclomatic 22, cognitive 26) · ×1

Complex function performAs (cyclomatic 22, cognitive 26) packages/sthrift-verification/e2e-tests/src/contexts/listing/tasks/create-listing.ts:21 — performAs has cyclomatic complexity 22 and cognitive complexity 26; 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 checkFrontendArchitecture (cyclomatic 22, cognitive 25) · ×1

Complex function checkFrontendArchitecture (cyclomatic 22, cognitive 25) packages/cellix/arch-unit-tests/src/checks/frontend-architecture.ts:12 — checkFrontendArchitecture has cyclomatic complexity 22 and cognitive complexity 25; 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 checkGraphqlResolverDependencies (cyclomatic 21, cognitive 27) · ×1

Complex function checkGraphqlResolverDependencies (cyclomatic 21, cognitive 27) packages/cellix/arch-unit-tests/src/checks/graphql-resolver-conventions.ts:22 — checkGraphqlResolverDependencies has cyclomatic complexity 21 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 (top-level) (cyclomatic 19, cognitive 18) · ×1

Complex function (top-level) (cyclomatic 19, cognitive 18) packages/sthrift-verification/verification-shared/src/settings/local-settings.ts:1 — (top-level) has cyclomatic complexity 19 and cognitive complexity 18; 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 21) · ×1

Complex function (anonymous) (cyclomatic 17, cognitive 21) REDACTED:130 — (anonymous) has cyclomatic complexity 17 and cognitive complexity 21; 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 17, cognitive 16) · ×1

Complex function (anonymous) (cyclomatic 17, cognitive 16) REDACTED:292 — (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 (anonymous) (cyclomatic 16, cognitive 17) · ×1

Complex function (anonymous) (cyclomatic 16, cognitive 17) packages/sthrift/application-services/src/contexts/user/personal-user/process-payment.ts:29 — (anonymous) has cyclomatic complexity 16 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 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 getDefinitionOrderCategory (cyclomatic 15, cognitive 14) · ×1

Complex function getDefinitionOrderCategory (cyclomatic 15, cognitive 14) packages/cellix/arch-unit-tests/src/checks/graphql-schema-conventions.ts:310 — getDefinitionOrderCategory has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 constructor (cyclomatic 15, cognitive 14) · ×1

Complex function constructor (cyclomatic 15, cognitive 14) packages/cellix/service-payment-cybersource/src/index.ts:49 — constructor has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 ProfileViewContainer (cyclomatic 15, cognitive 14) · ×1

Complex function ProfileViewContainer (cyclomatic 15, cognitive 14) packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/profile/components/profile-view.container.tsx:11 — ProfileViewContainer has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 14, cognitive 13) · ×1

Complex function (anonymous) (cyclomatic 14, cognitive 13) packages/sthrift/application-services/src/contexts/user/personal-user/update.ts:55 — (anonymous) has cyclomatic complexity 14 and cognitive complexity 13; 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 Navigation (cyclomatic 14, cognitive 13) · ×1

Complex function Navigation (cyclomatic 14, cognitive 13) packages/sthrift/ui-shared/src/molecules/navigation/navigation.tsx:46 — Navigation has cyclomatic complexity 14 and cognitive complexity 13; 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 MessageBubble (cyclomatic 14, cognitive 11) · ×1

Complex function MessageBubble (cyclomatic 14, cognitive 11) packages/sthrift/ui-shared/src/organisms/message-thread.tsx:168 — MessageBubble has cyclomatic complexity 14 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 getListingRequestsBySharerId (cyclomatic 13, cognitive 28) · ×1

Complex function getListingRequestsBySharerId (cyclomatic 13, cognitive 28) packages/sthrift/persistence/src/datasources/readonly/reservation-request/reservation-request/reservation-request.read-repository.ts:197 — getListingRequestsBySharerId has cyclomatic complexity 13 and cognitive complexity 28; 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 checkUiIsolation (cyclomatic 13, cognitive 18) · ×1

Complex function checkUiIsolation (cyclomatic 13, cognitive 18) packages/cellix/arch-unit-tests/src/checks/circular-dependencies.ts:181 — checkUiIsolation has cyclomatic complexity 13 and cognitive complexity 18; 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.

R3 · Large Files · packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/listing-information/listing-information.container.stories.tsx · ×1

packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/listing-information/listing-information.container.stories.tsx: 1994 lines of code packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/listing-information/listing-information.container.stories.tsx:1 — packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/listing-information/listing-information.container.stories.tsx has 1994 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/listing-information/listing-information.container.stories.tsx · ×1

packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/listing-information/listing-information.container.stories.tsx: 1994 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/listing-information/listing-information.container.stories.tsx:1 — packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/listing-information/listing-information.container.stories.tsx has 1994 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.container.stories.tsx · ×1

packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.container.stories.tsx: 1647 lines of code packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.container.stories.tsx:1 — packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.container.stories.tsx has 1647 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/cellix/server-payment-seedwork/src/index.ts · ×1

packages/cellix/server-payment-seedwork/src/index.ts: 1292 lines of code packages/cellix/server-payment-seedwork/src/index.ts:1 — packages/cellix/server-payment-seedwork/src/index.ts has 1292 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/cellix/service-payment-cybersource/src/index.ts · ×1

packages/cellix/service-payment-cybersource/src/index.ts: 1031 lines of code packages/cellix/service-payment-cybersource/src/index.ts:1 — packages/cellix/service-payment-cybersource/src/index.ts has 1031 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/listing-information/listing-information.stories.tsx · ×1

packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/listing-information/listing-information.stories.tsx: 950 lines of code packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/listing-information/listing-information.stories.tsx:1 — packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/listing-information/listing-information.stories.tsx has 950 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/listing-information/listing-information.stories.tsx · ×1

packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/listing-information/listing-information.stories.tsx: 950 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/listing-information/listing-information.stories.tsx:1 — packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/listing-information/listing-information.stories.tsx has 950 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/view-listing.container.stories.tsx · ×1

packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/view-listing.container.stories.tsx: 899 lines of code packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/view-listing.container.stories.tsx:1 — packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/view-listing.container.stories.tsx has 899 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/view-listing.container.stories.tsx · ×1

packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/view-listing.container.stories.tsx: 899 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/view-listing.container.stories.tsx:1 — packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/view-listing.container.stories.tsx has 899 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.container.stories.tsx · ×1

packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.container.stories.tsx: 868 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.container.stories.tsx:1 — packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.container.stories.tsx has 868 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/pages/settings-view.tsx · ×1

packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/pages/settings-view.tsx: 764 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/pages/settings-view.tsx:1 — packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/pages/settings-view.tsx has 764 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/requests-table.container.stories.tsx · ×1

packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/requests-table.container.stories.tsx: 761 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/requests-table.container.stories.tsx:1 — packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/requests-table.container.stories.tsx has 761 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/sthrift/ui-sharethrift-route-signup/src/components/pages/select-account-type/components/select-account-type.container.stories.tsx · ×1

packages/sthrift/ui-sharethrift-route-signup/src/components/pages/select-account-type/components/select-account-type.container.stories.tsx: 683 lines of code packages/sthrift/ui-sharethrift-route-signup/src/components/pages/select-account-type/components/select-account-type.container.stories.tsx:1 — packages/sthrift/ui-sharethrift-route-signup/src/components/pages/select-account-type/components/select-account-type.container.stories.tsx has 683 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users.stories.tsx · ×1

packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users.stories.tsx: 678 lines of code packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users.stories.tsx:1 — packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users.stories.tsx has 678 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-view.container.stories.tsx · ×1

packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-view.container.stories.tsx: 674 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-view.container.stories.tsx:1 — packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-view.container.stories.tsx has 674 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.container.stories.tsx · ×1

packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.container.stories.tsx: 627 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.container.stories.tsx:1 — packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.container.stories.tsx has 627 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-reservations/components/reservations-view-active.container.stories.tsx · ×1

packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-reservations/components/reservations-view-active.container.stories.tsx: 549 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-reservations/components/reservations-view-active.container.stories.tsx:1 — packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-reservations/components/reservations-view-active.container.stories.tsx has 549 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/cellix/service-payment-mock/src/index.ts · ×1

packages/cellix/service-payment-mock/src/index.ts: 546 lines of code packages/cellix/service-payment-mock/src/index.ts:1 — packages/cellix/service-payment-mock/src/index.ts has 546 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.stories.tsx · ×1

packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.stories.tsx: 496 lines of code packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.stories.tsx:1 — packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.stories.tsx has 496 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-container.stories.tsx · ×1

packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-container.stories.tsx: 488 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-container.stories.tsx:1 — packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-container.stories.tsx has 488 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/components/messages.stories.tsx · ×1

packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/components/messages.stories.tsx: 467 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/components/messages.stories.tsx:1 — packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/components/messages.stories.tsx has 467 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.stories.tsx · ×1

packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.stories.tsx: 405 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.stories.tsx:1 — packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.stories.tsx has 405 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.tsx · ×1

packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.tsx: 403 lines of code packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.tsx:1 — packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.tsx has 403 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R6 · Tooling · The declared test suite includes a file that cannot be loaded · ×1

The declared test suite includes a file that cannot be loaded packages/sthrift/ui-admin-route-root/src/components/pages/messages/pages/messages-page.stories.tsx:12 — This repository declares test tooling, and the ✓ above records that declaration — but packages/sthrift/ui-admin-route-root/src/components/pages/messages/pages/messages-page.stories.tsx and 6 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to.

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

Dead file (~226 LoC) packages/sthrift-verification/verification-shared/src/pages/adapters/jsdom-adapter.ts — no import path from any entry point (147 application, 83 tooling, 573 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 (~147 LoC) · ×1

Dead file (~147 LoC) build-pipeline/scripts/local-https-proxy.js — no import path from any entry point (147 application, 83 tooling, 573 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 (~144 LoC) · ×1

Dead file (~144 LoC) packages/sthrift-verification/verification-shared/src/formatters/agent-formatter.ts — no import path from any entry point (147 application, 83 tooling, 573 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/sthrift-verification/verification-shared/src/formatters/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 (~132 LoC) · ×1

Dead file (~132 LoC) packages/sthrift-verification/verification-shared/src/pages/adapters/playwright-adapter.ts — no import path from any entry point (147 application, 83 tooling, 573 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 (~106 LoC) · ×1

Dead file (~106 LoC) packages/sthrift-verification/verification-shared/src/settings/settings-utils.ts — no import path from any entry point (147 application, 83 tooling, 573 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/sthrift-verification/verification-shared/src/settings/index.ts, packages/sthrift-verification/verification-shared/src/settings/local-settings.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 (~105 LoC) · ×1

Dead file (~105 LoC) packages/sthrift-verification/verification-shared/src/settings/local-settings.ts — no import path from any entry point (147 application, 83 tooling, 573 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/sthrift-verification/verification-shared/src/settings/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 (~86 LoC) · ×1

Dead file (~86 LoC) build-pipeline/scripts/get-pr-number.cjs — no import path from any entry point (147 application, 83 tooling, 573 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 (~85 LoC) · ×1

Dead file (~85 LoC) packages/sthrift-verification/verification-shared/src/servers/graphql-test-server.ts — no import path from any entry point (147 application, 83 tooling, 573 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/sthrift-verification/verification-shared/src/servers/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 (~10 LoC) · ×1

Dead file (~10 LoC) packages/sthrift-verification/verification-shared/src/servers/index.ts — no import path from any entry point (147 application, 83 tooling, 573 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 (~9 LoC) · ×1

Dead file (~9 LoC) packages/sthrift-verification/verification-shared/src/settings/index.ts — no import path from any entry point (147 application, 83 tooling, 573 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 (~8 LoC) · ×1

Dead file (~8 LoC) packages/cellix/domain-seedwork/src/domain-seedwork/child-entity.ts — no import path from any entry point (147 application, 83 tooling, 573 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) packages/sthrift/graphql/src/schema/core/graphql-tools-scalars.ts — no import path from any entry point (147 application, 83 tooling, 573 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) packages/sthrift/domain/src/domain/events/event-bus.ts — no import path from any entry point (147 application, 83 tooling, 573 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/sthrift/domain/src/domain/events/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 (~0 LoC) · ×1

Dead file (~0 LoC) packages/sthrift/domain/src/domain/contexts/account-plan/account-plan/account-plan.value-objects.ts — no import path from any entry point (147 application, 83 tooling, 573 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 '@graphql-codegen/introspection' · ×1

Unused dependency '@graphql-codegen/introspection' — Declared in the root 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 '@graphql-codegen/typed-document-node' · ×1

Unused dependency '@graphql-codegen/typed-document-node' — Declared in the root 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 '@graphql-codegen/typescript-operations' · ×1

Unused dependency '@graphql-codegen/typescript-operations' — Declared in the root 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.

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

Async function without AbortSignal: execute packages/sthrift-verification/acceptance-api/src/shared/abilities/graphql-client.ts:17 — `execute` 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 })`.

Minor — 218 finding(s)

D34 · Knowledge Freshness · Orphaned file · ×97

Orphaned file packages/cellix/service-payment-mock/src/index.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file apps/api/src/cellix.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-view.container.stories.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/sthrift/ui-sharethrift-route-signup/src/components/pages/select-account-type/components/select-account-type.container.stories.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/cellix/ui-core/src/components/molecules/require-auth/require-auth.stories.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/cellix/service-payment-base/src/index.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-reservations/components/reservations-view-active.container.stories.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/components/messages.stories.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.stories.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/sthrift/ui-shared/src/shared/apollo-client-links.stories.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-container.stories.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.stories.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/sthrift/ui-sharethrift-route-signup/src/components/pages/profile-setup/components/profile-setup.container.stories.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/sthrift/ui-admin-route-user-operations/src/components/pages/admin-user-operations/components/admin-users-table/admin-users-table.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/sthrift/ui-sharethrift-route-signup/src/components/pages/payment/components/payment-form.stories.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-reservations/utils/reservation-story-mocks.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/pages/settings-view.stories.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/sthrift/ui-sharethrift-route-signup/src/components/pages/account-setup/components/account-setup.container.stories.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/cellix/server-messaging-seedwork/src/store.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/sthrift/ui-sharethrift-route-signup/src/components/pages/select-account-type/components/select-account-type.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-card.stories.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/sthrift/data-sources-mongoose-models/src/models/user/personal-user.model.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/sthrift/persistence/src/datasources/readonly/user/admin-user/admin-user.read-repository.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/sthrift/ui-sharethrift-route-signup/src/components/pages/payment/components/payment-token-form-items.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
+ 72 more in this group — see findings.md.

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

README/code drift CONTRIBUTING.md:99 — CONTRIBUTING.md names `listing-reservation.aggregate.ts`, but no file or folder `listing-reservation.aggregate.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.
README/code drift CONTRIBUTING.md:100 — CONTRIBUTING.md names `.aggregate.ts`, but no file or folder `.aggregate.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.
README/code drift CONTRIBUTING.md:101 — CONTRIBUTING.md names `.entity.ts`, but no file or folder `.entity.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.
README/code drift CONTRIBUTING.md:123 — CONTRIBUTING.md names `cellix/service-messaging`, but no file or folder `cellix/service-messaging` 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 CONTRIBUTING.md:124 — CONTRIBUTING.md names `sthrift/service-messaging-twilio`, but no file or folder `sthrift/service-messaging-twilio` 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 CONTRIBUTING.md:124 — CONTRIBUTING.md names `sthrift/service-messaging-mock`, but no file or folder `sthrift/service-messaging-mock` 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 CONTRIBUTING.md:142 — CONTRIBUTING.md links to `./packages/sthrift/service-sendgrid/src/features/`, but `packages/sthrift/service-sendgrid/src/features` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift readme.md:123 — readme.md links to `./packages/sthrift/service-mongoose/package.json`, but `packages/sthrift/service-mongoose/package.json` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift readme.md:236 — readme.md runs `pnpm run sourcery:review # Review changed files`, but no REDACTED declares a `sourcery:review` 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 apps/docs/README.md:32 — apps/docs/README.md documents the environment variable `USE_SSH`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift apps/server-messaging-mock/README.md:27 — apps/server-messaging-mock/README.md names the package `@cellix/messaging`, but no REDACTED of the workspace declares or depends on it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift .agents/skills/vercel-react-best-practices/README.md:10 — .agents/skills/vercel-react-best-practices/README.md names `area-description.md`, but no file or folder `area-description.md` 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 .agents/skills/vercel-react-best-practices/README.md:30 — .agents/skills/vercel-react-best-practices/README.md runs `pnpm validate`, but no REDACTED declares a `validate` 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 .agents/skills/vercel-react-best-practices/README.md:35 — .agents/skills/vercel-react-best-practices/README.md runs `pnpm extract-tests`, but no REDACTED declares a `extract-tests` 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 packages/cellix/domain-seedwork/readme.md:7 — packages/cellix/domain-seedwork/readme.md names Node.js 22, but the repository declares engines `>=18.0`. 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 packages/cellix/domain-seedwork/readme.md:11 — packages/cellix/domain-seedwork/readme.md links to `./src/passport-seedwork/README.md`, but `packages/cellix/domain-seedwork/src/passport-seedwork/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 packages/cellix/mongoose-seedwork/readme.md:7 — packages/cellix/mongoose-seedwork/readme.md names Node.js 22, but the repository declares engines `>=18.0`. 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 packages/cellix/mongoose-seedwork/readme.md:15 — packages/cellix/mongoose-seedwork/readme.md installs `@cellix/data-sources-mongoose` (`npm i -w @cellix/data-sources-mongoose`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/cellix/server-messaging-seedwork/README.md:27 — packages/cellix/server-messaging-seedwork/README.md names `src/seed-data.ts`, but no file or folder `src/seed-data.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.
README/code drift packages/cellix/service-messaging-mock/README.md:29 — packages/cellix/service-messaging-mock/README.md names the package `@cellix/messaging`, but no REDACTED of the workspace declares or depends on it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/cellix/service-messaging-twilio/README.md:36 — packages/cellix/service-messaging-twilio/README.md names the package `@cellix/messaging`, but no REDACTED of the workspace declares or depends on it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/cellix/service-otel/readme.md:38 — packages/cellix/service-otel/readme.md installs `service-otel` (`npm i -w service-otel @opentelemetry/sdk-node@^0.57.2`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/cellix/service-otel/readme.md:46 — packages/cellix/service-otel/readme.md installs `@opentelemetry/auto-instrumentations-node` (`npm i -w service-otel @opentelemetry/auto-instrumentations-node@^0.56.0`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/cellix/service-otel/readme.md:57 — packages/cellix/service-otel/readme.md installs `@tsconfig/node20` (`npm i -D -w service-otel @tsconfig/node20`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/cellix/service-otel/readme.md:58 — packages/cellix/service-otel/readme.md installs `@tsconfig/node-ts` (`npm i -D -w service-otel @tsconfig/node-ts`), but no REDACTED declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
+ 12 more in this group — see findings.md.

X10 · Duplicated predicate · Duplicated predicate · ×23

Duplicated predicate packages/sthrift/ui-admin-route-root/src/components/pages/messages/components/conversation-box.container.tsx:37 — `!data?.sendMessage?.status?.success || !data.sendMessage.message` appears character-identically in 2 files — packages/sthrift/ui-admin-route-root/src/components/pages/messages/components/conversation-box.container.tsx, packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/components/conversation-box.container.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 packages/cellix/ui-core/src/components/molecules/require-auth/index.tsx:19 — `!hasAuthParams() && props.forceLogin === true && !auth.isAuthenticated && !auth.activeNavigator && !auth.isLoading && !auth.error` appears character-identically in 2 files — packages/cellix/ui-core/src/components/molecules/require-auth/index.tsx, packages/sthrift/ui-shared/src/molecules/require-auth.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 packages/sthrift-verification/acceptance-api/src/contexts/listing/step-definitions/create-listing.steps.ts:106 — `!isFieldMentioned && !isValidationPattern` appears character-identically in 4 files — packages/sthrift-verification/acceptance-api/src/contexts/listing/step-definitions/create-listing.steps.ts, packages/sthrift-verification/acceptance-api/src/contexts/reservation-request/step-definitions/create-reservation-request.steps.ts, packages/sthrift-verification/acceptance-ui/src/contexts/listing/step-definitions/create-listing.steps.ts, packages/sthrift-verification/acceptance-ui/src/contexts/reservation-request/step-definitions/create-reservation-request.steps.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 packages/sthrift/ui-admin-route-root/src/components/pages/messages/components/conversation-list.container.tsx:45 — `!props.selectedConversationId && currentUserConversationsData?.conversationsByUser?.[0]?.id` appears character-identically in 2 files — packages/sthrift/ui-admin-route-root/src/components/pages/messages/components/conversation-list.container.tsx, packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/components/conversation-list.container.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 packages/sthrift/ui-admin-route-root/src/components/pages/home/components/listings-page.container.tsx:103 — `(listing.state as ItemListing['state']) || undefined` appears character-identically in 2 files — packages/sthrift/ui-admin-route-root/src/components/pages/home/components/listings-page.container.tsx, packages/sthrift/ui-sharethrift-route-root/src/components/pages/home/components/listings-page.container.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 packages/sthrift/graphql/src/schema/types/item-listing.resolvers.ts:22 — `args.sorter.order === 'ascend' || args.sorter.order === 'descend'` appears character-identically in 2 files — packages/sthrift/graphql/src/schema/types/item-listing.resolvers.ts, packages/sthrift/graphql/src/schema/types/reservation-request.resolvers.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 packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/get-all.ts:31 — `command.sorter.order === 'ascend' || command.sorter.order === 'descend'` appears character-identically in 4 files — packages/sthrift/application-services/src/contexts/appeal-request/listing-appeal-request/get-all.ts, packages/sthrift/application-services/src/contexts/appeal-request/user-appeal-request/get-all.ts, packages/sthrift/application-services/src/contexts/user/admin-user/get-all-users.ts, packages/sthrift/application-services/src/contexts/user/personal-user/get-all-users.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 packages/sthrift/ui-admin-route-root/src/auth-redirect.tsx:15 — `currentPath === '/login' || currentPath.startsWith('/auth-redirect')` appears character-identically in 2 files — packages/sthrift/ui-admin-route-root/src/auth-redirect.tsx, packages/sthrift/ui-shared/src/molecules/require-auth.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 packages/sthrift/ui-admin-route-root/src/components/pages/messages/components/conversation-box.container.tsx:85 — `data.sendMessage.status.errorMessage || 'Failed to send message'` appears character-identically in 2 files — packages/sthrift/ui-admin-route-root/src/components/pages/messages/components/conversation-box.container.tsx, packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/components/conversation-box.container.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 packages/sthrift/ui-admin-route-root/src/components/pages/messages/components/conversation-box.container.tsx:90 — `error.message || 'Failed to send message'` appears character-identically in 2 files — packages/sthrift/ui-admin-route-root/src/components/pages/messages/components/conversation-box.container.tsx, packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/components/conversation-box.container.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 packages/sthrift/ui-admin-route-root/src/components/pages/messages/components/conversation-list.container.tsx:20 — `errors.find(Boolean)?.message || 'Unknown error'` appears character-identically in 2 files — packages/sthrift/ui-admin-route-root/src/components/pages/messages/components/conversation-list.container.tsx, packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/components/conversation-list.container.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 packages/sthrift/ui-admin-route-root/src/components/pages/messages/components/conversation-box.container.tsx:61 — `existingConversation.conversation.messages || []` appears character-identically in 2 files — packages/sthrift/ui-admin-route-root/src/components/pages/messages/components/conversation-box.container.tsx, packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/components/conversation-box.container.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 packages/sthrift/domain/src/domain/contexts/account-plan/account-plan/account-plan-feature.ts:22 — `permissions.canCreateAccountPlan || permissions.canUpdateAccountPlan` appears character-identically in 2 files — packages/sthrift/domain/src/domain/contexts/account-plan/account-plan/account-plan-feature.ts, packages/sthrift/domain/src/domain/contexts/account-plan/account-plan/account-plan.aggregate.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 packages/sthrift/ui-admin-route-root/src/components/pages/home/components/listings-page.container.tsx:43 — `searchQuery && !listing.title.toLowerCase().includes(searchQuery.toLowerCase())` appears character-identically in 2 files — packages/sthrift/ui-admin-route-root/src/components/pages/home/components/listings-page.container.tsx, packages/sthrift/ui-sharethrift-route-root/src/components/pages/home/components/listings-page.container.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 packages/sthrift/ui-admin-route-root/src/components/pages/home/components/listings-page.container.tsx:36 — `selectedCategory && selectedCategory !== 'All' && listing.category !== selectedCategory` appears character-identically in 2 files — packages/sthrift/ui-admin-route-root/src/components/pages/home/components/listings-page.container.tsx, packages/sthrift/ui-sharethrift-route-root/src/components/pages/home/components/listings-page.container.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 packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-card.tsx:81 — `status === 'Active' || status === 'Paused'` appears character-identically in 2 files — packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-card.tsx, packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.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 packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-card.tsx:24 — `status === 'Active' || status === 'Reserved'` appears character-identically in 2 files — packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-card.tsx, packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.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 packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-card.tsx:37 — `status === 'Paused' || status === 'Expired'` appears character-identically in 2 files — packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-card.tsx, packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-listings/components/all-listings-table.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 packages/cellix/serenity-framework/src/formatters/agent-formatter.ts:81 — `stepStatus === 'PASSED' || stepStatus === 'SKIPPED'` appears character-identically in 2 files — packages/cellix/serenity-framework/src/formatters/agent-formatter.ts, packages/sthrift-verification/verification-shared/src/formatters/agent-formatter.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 packages/sthrift-verification/acceptance-api/src/contexts/listing/tasks/api/create-listing.ts:39 — `this.details.isDraft === 'false' || this.details.isDraft === false` appears character-identically in 2 files — packages/sthrift-verification/acceptance-api/src/contexts/listing/tasks/api/create-listing.ts, packages/sthrift-verification/acceptance-ui/src/contexts/listing/tasks/ui/create-listing.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 packages/cellix/serenity-framework/src/formatters/agent-formatter.ts:116 — `this.testRunStarted?.timestamp && testRunFinished.timestamp` appears character-identically in 2 files — packages/cellix/serenity-framework/src/formatters/agent-formatter.ts, packages/sthrift-verification/verification-shared/src/formatters/agent-formatter.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 packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/sharer-information/sharer-information.container.tsx:75 — `typeof sharerId === 'string' && (sharerId.includes(' ') || /^[a-zA-Z\s]+$/.test(sharerId))` appears character-identically in 2 files — packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/sharer-information/sharer-information.container.tsx, packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/sharer-information/sharer-information.container.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 packages/sthrift/persistence/src/datasources/readonly/user/admin-user/admin-user.read-repository.ts:134 — `typeof valA === 'string' && typeof valB === 'string'` appears character-identically in 2 files — packages/sthrift/persistence/src/datasources/readonly/user/admin-user/admin-user.read-repository.ts, packages/sthrift/persistence/src/datasources/readonly/user/personal-user/personal-user.read-repository.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.

D20 · ADR Quality · ADR has no Decision and Consequences section · ×8

ADR has no Decision and Consequences section apps/docs/docs/security-requirements/0001-identity-verification.md:13 — apps/docs/docs/security-requirements/0001-identity-verification.md has no Decision and Consequences section (a heading such as `## Decision`, 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 Decision and Consequences section apps/docs/docs/security-requirements/0002-malware-scanning.md:13 — apps/docs/docs/security-requirements/0002-malware-scanning.md has no Decision and Consequences section (a heading such as `## Decision`, 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 Decision and Consequences section apps/docs/docs/security-requirements/0003-user-blocking-moderation.md:13 — apps/docs/docs/security-requirements/0003-user-blocking-moderation.md has no Decision and Consequences section (a heading such as `## Decision`, 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 Decision and Consequences section apps/docs/docs/security-requirements/0004-listing-appeal-review.md:13 — apps/docs/docs/security-requirements/0004-listing-appeal-review.md has no Decision and Consequences section (a heading such as `## Decision`, 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 Decision and Consequences section apps/docs/docs/security-requirements/0005-content-auto-review.md:13 — apps/docs/docs/security-requirements/0005-content-auto-review.md has no Decision and Consequences section (a heading such as `## Decision`, 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 Decision and Consequences section apps/docs/docs/security-requirements/0007-admin-access-control.md:13 — apps/docs/docs/security-requirements/0007-admin-access-control.md has no Decision and Consequences section (a heading such as `## Decision`, 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 Decision and Consequences section apps/docs/docs/security-requirements/0008-blocked-user-restrictions.md:13 — apps/docs/docs/security-requirements/0008-blocked-user-restrictions.md has no Decision and Consequences section (a heading such as `## Decision`, 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 Decision and Consequences section apps/docs/docs/security-requirements/0009-reservation-mutual-consent.md:13 — apps/docs/docs/security-requirements/0009-reservation-mutual-consent.md has no Decision and Consequences section (a heading such as `## Decision`, 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.

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

ADR has no Consequences section apps/docs/docs/decisions/0001-madr-architecture-decisions.md:13 — apps/docs/docs/decisions/0001-madr-architecture-decisions.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 apps/docs/docs/decisions/0002-open-telemetry.md:14 — apps/docs/docs/decisions/0002-open-telemetry.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 apps/docs/docs/decisions/0004-identity-access.md:13 — apps/docs/docs/decisions/0004-identity-access.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 apps/docs/docs/decisions/0005-authorization.md:14 — apps/docs/docs/decisions/0005-authorization.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 apps/docs/docs/decisions/0006-maps.md:13 — apps/docs/docs/decisions/0006-maps.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 apps/docs/docs/decisions/0007-serenityjs.md:14 — apps/docs/docs/decisions/0007-serenityjs.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 apps/docs/docs/decisions/0010-react-router-loaders.md:11 — apps/docs/docs/decisions/0010-react-router-loaders.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.

S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×4

No app-layer HTTPS enforcement detected packages/cellix/server-messaging-seedwork/src/index.ts:72 — `http(…).listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
No app-layer HTTPS enforcement detected packages/cellix/server-oauth2-seedwork/src/manager.ts:46 — `a.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
No app-layer HTTPS enforcement detected packages/cellix/server-oauth2-seedwork/src/server.ts:22 — `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
No app-layer HTTPS enforcement detected packages/cellix/server-payment-seedwork/src/index.ts:1339 — `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)

X7 · Silent fallback defaults · Silent fallback default in catch · ×4

Silent fallback default in catch packages/sthrift-verification/e2e-tests/src/contexts/listing/questions/form-validation-error.ts:36 — `answeredBy` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/sthrift/persistence/src/datasources/domain/user/personal-user/personal-user.domain-adapter.ts:57 — `entityReference` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/sthrift/ui-admin-route-root/src/components/pages/view-listing/components/view-listing.container.tsx:20 — `computeTimeAgo` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/sthrift/ui-sharethrift-route-root/src/components/pages/view-listing/components/view-listing.container.tsx:21 — `computeTimeAgo` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.

D16 · Bus Factor · Off-boarding risk · ×3

Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 9 significant file(s) lose their only recent owner: packages/cellix/service-payment-cybersource/src/index.ts, packages/sthrift/ui-sharethrift-route-signup/src/components/shared/address-form/countries-mock-data.ts, packages/cellix/service-payment-base/src/index.ts, packages/sthrift/ui-sharethrift-route-signup/src/components/pages/payment/components/payment-form.tsx, packages/sthrift/application-services/src/contexts/user/personal-user/process-payment.ts, packages/sthrift/ui-sharethrift-route-signup/src/components/pages/profile-setup/components/profile-setup.tsx, packages/sthrift/ui-sharethrift-route-signup/src/components/pages/payment/components/billing-address-form-items.tsx, packages/sthrift/ui-sharethrift-route-signup/src/components/pages/payment/components/payment.container.tsx (+1 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 5 significant file(s) lose their only recent owner: packages/sthrift/data-sources-mongoose-models/src/models/role/admin-role.model.ts, packages/sthrift/graphql/src/schema/types/admin-user.resolvers.ts, packages/sthrift/application-services/src/contexts/user/admin-user/update.ts, packages/sthrift/data-sources-mongoose-models/src/models/user/admin-user.model.ts, packages/sthrift/domain/src/domain/iam/user/admin-user/admin-user.user.passport.ts. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 5 significant file(s) lose their only recent owner: packages/sthrift-verification/acceptance-ui/src/contexts/reservation-request/step-definitions/create-reservation-request.steps.ts, packages/sthrift-verification/acceptance-api/src/shared/support/domain-test-helpers.ts, apps/server-oauth2-mock/src/index.ts, packages/sthrift/ui-admin-route-root/src/section-layout.tsx, packages/cellix/service-sendgrid/src/sendgrid.ts. Pair on, review, or document these before any departure.

D20 · ADR Quality · ADR decides a question another record already decided · ×3

ADR decides a question another record already decided apps/docs/docs/decisions/0003-domain-driven-design.md:14 — apps/docs/docs/decisions/0003-domain-driven-design.md and apps/docs/docs/decisions/0002-open-telemetry.md are both in force and decide the same question ("These are optional elements. Feel free to remove any of them."), and neither names the other. If this record replaces the earlier one, say so ("Supersedes …") and mark the earlier one superseded; if both hold, state how they relate.
ADR decides a question another record already decided apps/docs/docs/decisions/0005-authorization.md:14 — apps/docs/docs/decisions/0005-authorization.md and apps/docs/docs/decisions/0002-open-telemetry.md, apps/docs/docs/decisions/0003-domain-driven-design.md are both in force and decide the same question ("These are optional elements. Feel free to remove any of them."), and neither names the other. If this record replaces the earlier one, say so ("Supersedes …") and mark the earlier one superseded; if both hold, state how they relate.
ADR decides a question another record already decided apps/docs/docs/decisions/0011-bicep.md:11 — apps/docs/docs/decisions/0011-bicep.md and apps/docs/docs/decisions/0002-open-telemetry.md, apps/docs/docs/decisions/0003-domain-driven-design.md, apps/docs/docs/decisions/0005-authorization.md are both in force and decide the same question ("These are optional elements. Feel free to remove any of them."), and neither names the other. If this record replaces the earlier one, say so ("Supersedes …") and mark the earlier one superseded; if both hold, state how they relate.

D30 · Dependency Vulnerabilities · Low CVE · ×3

REDACTED
REDACTED
REDACTED

R7 · Dead Code · Unused export 'makeTestPassport' · ×2

Unused export 'makeTestPassport' packages/sthrift-verification/acceptance-api/src/shared/support/domain-test-helpers.ts:22 — Nothing imports this binding — it is safe to review for removal.
Unused export 'makeTestPassport' packages/sthrift-verification/acceptance-ui/src/shared/support/domain-test-helpers.ts:22 — Nothing imports this binding — it is safe to review for removal.

AX6 · Interface segregation · Fat interface · ×1

Fat interface: PaymentService (18 required operations) packages/cellix/service-payment-base/src/index.ts:3 — `PaymentService` declares 18 required operations: `generatePublicKey`, `createCustomerProfile`, `getCustomerProfile`, `addCustomerPaymentInstrument`, `getCustomerPaymentInstrument`, `getCustomerPaymentInstruments`, `deleteCustomerPaymentInstrument`, `updateCustomerPaymentInstrument`, `processPayment`, `processRefund`, `getSuccessOrLatestFailedTransactionsByReferenceId`, `createPlan`, `listOfPlans`, `getPlan`, `createSubscription`, `updatePlanForSubscription`, `listOfSubscriptions`, `suspendSubscription`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.

C2 · Access Controls · No named authorization policies · ×1

No named authorization policies — Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.

D10 · Test Quality · Mock-dominated test · ×1

Mock-dominated test: starts infrastructure, validates state, creates the cast, and resets during cleanup packages/cellix/serenity-framework/src/cucumber/world.test.ts:6 — This test sets up 8 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.

D16 · Bus Factor · Further sole-owners (lower concentration) · ×1

Further sole-owners (lower concentration) — 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (22 single-owned of 282 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 282 of the 1031 production source files in this repository met that bar). They are anonymized user #4 (2 file(s)), anonymized user #5 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: packages/cellix/service-messaging-mock/src/index.ts, apps/server-messaging-mock/src/seed/seed-data.ts, packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-reservations/utils/reservation-story-mocks.ts.

D20 · ADR Quality · ADR has no Decision section · ×1

ADR has no Decision section apps/docs/docs/decisions/0024-madr-agent-skills.md:13 — apps/docs/docs/decisions/0024-madr-agent-skills.md has no Decision section (a heading such as `## Decision`, 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.

D26 · Project Cohesion · Split packages/sthrift/domain · ×1

Split packages/sthrift/domain — A domain project whose namespaces are all user/personal-user/role/admin-role/conversation/listing/appeal-request/reservation-request and iam/guest/system with no single cohesive concern. Suggested: split into one or more focused domain modules per the listed namespaces

D26 · Project Cohesion · Split packages/sthrift/persistence · ×1

Split packages/sthrift/persistence — A persistence project whose namespaces are all datasources/readonly/domain/messaging/conversation and spread across a single data-model family. Suggested: split into one or more focused persistence modules per the listed namespaces

D26 · Project Cohesion · Split packages/sthrift/ui-sharethrift-route-root · ×1

Split packages/sthrift/ui-sharethrift-route-root — A UI project whose namespaces are pages/components/pages/settings/profile and spread across many components with no single cohesive concern. Suggested: split into one or more focused ui modules per the listed namespaces

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

REDACTED

D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1

Further orphaned files (smaller) — 97 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: packages/cellix/service-payment-mock/src/index.ts, packages/sthrift/ui-sharethrift-route-root/src/components/pages/account/pages/settings/components/settings-view.container.stories.tsx, packages/sthrift/ui-sharethrift-route-signup/src/components/pages/select-account-type/components/select-account-type.container.stories.tsx, packages/cellix/ui-core/src/components/molecules/require-auth/require-auth.stories.tsx, packages/cellix/service-payment-base/src/index.ts, packages/sthrift/ui-sharethrift-route-root/src/components/pages/my-reservations/components/reservations-view-active.container.stories.tsx, packages/sthrift/ui-sharethrift-route-root/src/components/pages/messages/components/messages.stories.tsx, packages/sthrift/ui-sharethrift-route-root/src/components/pages/create-listing/components/create-listing.stories.tsx (and 89 more) (100 orphaned of 282 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 282 of the 1031 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.

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

REDACTED

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

REDACTED

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

REDACTED

IC1 · Incompleteness & stubs · Empty method body · ×1

Empty method body packages/cellix/service-blob-storage/src/index.ts:80 — `shutDown` has an empty body — confirm it's an intentional no-op and not an unfinished method.

P6 · Release Hygiene · Changelog looks stale/thin · ×1

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

R7 · Dead Code · Unused export 'SubdocumentBaseOptions' · ×1

Unused export 'SubdocumentBaseOptions' packages/cellix/mongoose-seedwork/src/mongoose-seedwork/base.ts:33 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'GetModelFunction' · ×1

Unused export 'GetModelFunction' packages/cellix/mongoose-seedwork/src/mongoose-seedwork/mongo-connection.ts:20 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'GetModelFunctionWithSchema' · ×1

Unused export 'GetModelFunctionWithSchema' packages/cellix/mongoose-seedwork/src/mongoose-seedwork/mongo-connection.ts:24 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'makeItemListingProps' · ×1

Unused export 'makeItemListingProps' packages/sthrift-verification/acceptance-api/src/shared/support/domain-test-helpers.ts:101 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'makeReservationRequestProps' · ×1

Unused export 'makeReservationRequestProps' packages/sthrift-verification/acceptance-api/src/shared/support/domain-test-helpers.ts:152 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'MongoDBTestServer' · ×1

Unused export 'MongoDBTestServer' packages/sthrift-verification/verification-shared/src/servers/test-mongodb-server.ts:67 — Nothing ultimately consumes this binding: its only referrer is the re-export in packages/sthrift-verification/verification-shared/src/servers/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/sthrift-verification/verification-shared/src/servers/index.ts in the same commit, or the barrel will import a name that no longer exists.

R7 · Dead Code · Unused export 'permissions' · ×1

Unused export 'permissions' packages/sthrift/graphql/src/schema/builder/resolver-builder.ts:24 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused private field 'uow' · ×1

Unused private field 'uow' packages/sthrift/domain/tests/acceptance/screenplay/abilities/create-listing.ability.ts:21 — Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.

R8 · Dependency Hygiene · Type-only dependency 'mongoose' in production deps · ×1

Type-only dependency 'mongoose' in production deps apps/server-mongodb-memory-mock/src/seed/seed.ts:1 — Every import is type-only — move it to devDependencies.

X2 · Cancellation propagation · Not all async functions that make a request accept an AbortSignal · ×1

Not all async functions that make a request accept an AbortSignal — Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) 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.

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 — 3/58 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.8 `!` null assertions per 1k TypeScript source lines — 41 assertion(s) across the 48585 source line(s) of the 756 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: packages/sthrift/persistence/src/datasources/domain/user/personal-user/personal-user.domain-adapter.ts (17), packages/sthrift/persistence/src/datasources/domain/user/admin-user/admin-user.domain-adapter.ts (12), packages/sthrift/domain/src/domain/contexts/user/admin-user/admin-user-account-profile-location.ts (6). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

Minor — 2 finding(s)

D5 · Coupling · Off the main sequence · ×2

Off the main sequence: @cellix/server-messaging-seedwork — @cellix/server-messaging-seedwork: abstractness 0.14, instability 0.00, distance 0.86 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Off the main sequence: @cellix/server-oauth2-seedwork — @cellix/server-oauth2-seedwork: abstractness 0.29, instability 0.00, distance 0.71 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.

Appendix B — Reproduction & audit trail

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

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-d29e115e2cb94ec7b4aa5c3f534622b9/history.json --exit-code 0 --source .	4	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-d29e115e2cb94ec7b4aa5c3f534622b9/tree.json --exit-code 0 --source .	0	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	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	85	artifacts/raw/trivy-fs.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	10	artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 20 file(s) — `apps/docs/docusaurus.config.ts`, `apps/ui-sharethrift/src/app.stories.tsx`, `packages/cellix/serenity-framework/src/cucumber/world.ts`, `packages/cellix/ui-core/src/components/molecules/component-query-loader/component-query-loader.stories.tsx`, `packages/cellix/ui-core/src/components/molecules/require-auth/require-auth.stories.tsx`, … (+15 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.	0	—
D37 · Vulnerability-disclosure Policy	disclosure	—	disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.	0	—
D40 · Network Egress 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	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	0	artifacts/raw/trivy-fs.json

Run 01a163f9-e783-723e-87c9-0d9b720effc4 · 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 · 55% · Adequate · gated by X5 ·

At a glance — Architecture · 53% · Adequate · gated by AX8 ·

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

At a glance — Readiness · 32% · Weak · gated by R8, P2, P6, P7 ·

At a glance — Security · 66% · Adequate · gated by D29, D30, D36 ·

At a glance — Domain Modelling · 100% · Exemplary ·

At a glance — Accessibility · 76% · Strong ·

At a glance — Performance · 60% · Adequate ·

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