Executive summary
CellixJs/cellixjs is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 47 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 44, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is fixing the password or key in the code, worth about 3 points. Tidying the declared packages would lift Production Readiness itself, worth about 2 points.
Twenty-seven known security holes in the packages the code depends on can be used by attackers. Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and two weaknesses in the code could be used by an attacker. Updating the vulnerable packages, pinning each tool to an exact version and fixing the weaknesses the scanner points to would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and hashing passwords with a password-hashing function such as Argon2, bcrypt or PBKDF2 would deal with the place where passwords are scrambled with a fast general-purpose hash. The eight pieces of product code that depend on test code need their reference to the test project removed.
The product code is 43,941 lines, about €130,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 33 findings
- Cyclomatic Complexity · member-management.updateMemberProfile.<returned closure> (cyclomatic 22) packages/ocom/application-services/src/contexts/community/member/member-management.ts
- Cognitive Complexity · member-management.updateMemberProfile.<returned closure> (cognitive 21) packages/ocom/application-services/src/contexts/community/member/member-management.ts
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Import Boundaries · Boundary violation [package:test-suite-dependency] packages/ocom-verification/acceptance-api/src/mock-application-services.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] packages/ocom-verification/acceptance-api/src/servers/test-mongo-server.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] packages/ocom-verification/acceptance-api/src/servers/test-mongo-server.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] packages/ocom-verification/acceptance-ui/src/contexts/authentication/tasks/click-header-sign-in.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] packages/ocom-verification/acceptance-ui/src/contexts/community/tasks/create-community.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] packages/ocom-verification/acceptance-ui/src/contexts/staff-role/abilities/mock-staff-role-backend.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] packages/ocom-verification/acceptance-ui/src/contexts/staff-role/tasks/staff-roles-screen.ts
- Data Protection · No data-protection/encryption packages/ocom/data-sources-mongoose-models/src/models/user/end-user.model.ts
- Forms & labels · <Input> field component without a label packages/ocom/ui-community-route-admin/src/components/members-list.tsx
Fixed since the last survey: 205 findings
- Cyclomatic Complexity · member-management.updateMemberProfile (cyclomatic 22) packages/ocom/application-services/src/contexts/community/member/member-management.ts
- Cognitive Complexity · member-management.updateMemberProfile (cognitive 21) packages/ocom/application-services/src/contexts/community/member/member-management.ts
- Boundary Type-Coupling · Cross-context type ServiceTicketV1 (domain → persistence) packages/ocom/persistence/src/datasources/domain/case/service-ticket-v1/service-ticket-v1.repository.ts
- Boundary Type-Coupling · Cross-context type ServiceTicketV1 (domain → persistence) packages/ocom/persistence/src/datasources/domain/case/service-ticket-v1/service-ticket-v1.repository.ts
- Static Analysis (SAST) · Medium: watchdog-regex-match-index-beyond-capture-groups-js .agents/skills/cellix-tdd/evaluator/evaluate-cellix-tdd.ts
- Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Code Duplication · Duplicated block (29 lines × 2 locations) packages/ocom/ui-community-route-admin/src/components/members-list.container.tsx
- Code Duplication · Duplicated block (28 lines × 2 locations) packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role-service-ticket-permissions.ts
- Code Duplication · Duplicated block (27 lines × 2 locations) apps/ui-community/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx
- Code Duplication · Duplicated block (27 lines × 2 locations) apps/ui-community/src/components/ui/organisms/apollo-connection/index.tsx
- Code Duplication · Duplicated block (27 lines × 2 locations) apps/ui-community/src/config/oidc-config.tsx
- Code Duplication · Duplicated block with local edits (27 matched lines × 2 locations) packages/ocom-verification/acceptance-api/src/contexts/staff-role/step-definitions/staff-role-management.steps.ts
- Code Duplication · Duplicated block (27 lines × 2 locations) packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role-community-permissions.ts
- Code Duplication · Duplicated block (26 lines × 2 locations) packages/ocom/domain/src/domain/contexts/user/end-user/end-user-identity-details.ts
- Code Duplication · Duplicated block (26 lines × 2 locations) packages/ocom/graphql/src/schema/types/member.resolvers.ts
- Code Duplication · Duplicated block (26 lines × 4 locations) packages/ocom/persistence/src/datasources/domain/community/role/end-user-role/end-user-role.domain-adapter.ts
- Code Duplication · Duplicated block with local edits (26 matched lines × 2 locations) packages/ocom/persistence/src/datasources/domain/user/staff-user/staff-user.repository.ts
- Code Duplication · Duplicated block (26 lines × 2 locations) packages/ocom/ui-community-route-accounts/src/components/community-list.tsx
- Code Duplication · Duplicated block (25 lines × 2 locations) apps/ui-community/src/main.tsx
- Code Duplication · Duplicated block with local edits (23 matched lines × 2 locations) packages/cellix/ui-core/.storybook/preview.tsx
- Code Duplication · Duplicated block (23 lines × 3 locations) packages/ocom/ui-staff-route-user-management/src/components/staff-role-create.container.tsx
- Code Duplication · Duplicated block (22 lines × 2 locations) packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role-permissions.ts
- Code Duplication · Duplicated block (22 lines × 2 locations) packages/ocom/domain/src/domain/iam/member/contexts/member.service-ticket.visa.ts
- Code Duplication · Duplicated block (22 lines × 3 locations) packages/ocom/graphql/src/schema/types/member.resolvers.ts
- Code Duplication · Duplicated block (21 lines × 7 locations) packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role-property-permissions.ts
- Code Duplication · Duplicated block (21 lines × 2 locations) packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role-finance-permissions.ts
- Code Duplication · Duplicated block (21 lines × 2 locations) packages/ocom/persistence/src/datasources/domain/property/property/property.domain-adapter.ts
- Code Duplication · Duplicated block (20 lines × 4 locations) packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role-community-permissions.ts
- Code Duplication · Duplicated block (20 lines × 2 locations) packages/ocom/persistence/src/datasources/domain/case/service-ticket-v1/service-ticket-v1.domain-adapter.ts
- Code Duplication · Duplicated block (20 lines × 3 locations) packages/ocom/ui-community-route-accounts/src/sub-page-layout.tsx
- Code Duplication · Duplicated block (20 lines × 2 locations) packages/ocom/ui-staff-route-user-management/src/pages/staff-roles.tsx
- Code Duplication · Duplicated block (19 lines × 2 locations) apps/ui-community/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx
- Code Duplication · Duplicated block (19 lines × 2 locations) packages/ocom-verification/acceptance-api/src/contexts/staff-role/tasks/grant-staff-role-permission.ts
- Code Duplication · Duplicated block (19 lines × 3 locations) packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role-property-permissions.ts
- Code Duplication · Duplicated block (19 lines × 8 locations) packages/ocom/graphql/src/schema/types/member.resolvers.ts
- Code Duplication · Duplicated block with local edits (19 matched lines × 2 locations) packages/ocom/persistence/src/datasources/domain/case/service-ticket-v1/service-ticket-v1.domain-adapter.ts
- Code Duplication · Duplicated block with local edits (18 matched lines × 2 locations) packages/cellix/server-oauth2-mock-seedwork/src/jwt.ts
- Code Duplication · Duplicated block (18 lines × 3 locations) packages/ocom-verification/acceptance-api/src/contexts/staff-role/tasks/assign-staff-role-to-user.ts
- Code Duplication · Duplicated block (18 lines × 2 locations) packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role-service-permissions.ts
- Code Duplication · Duplicated block (18 lines × 3 locations) packages/ocom/domain/src/domain/iam/member/contexts/member.user.staff-role.visa.ts
- Code Duplication · Duplicated block (18 lines × 2 locations) packages/ocom/graphql/src/schema/types/member.resolvers.ts
- Code Duplication · Duplicated block (17 lines × 2 locations) packages/ocom-verification/acceptance-api/src/contexts/staff/step-definitions/staff-landing.steps.ts
- Code Duplication · Duplicated block (17 lines × 2 locations) packages/ocom/domain/src/domain/contexts/community/member/member.search-specs.ts
- Code Duplication · Duplicated block (17 lines × 2 locations) packages/ocom/domain/src/domain/contexts/user/end-user/end-user.value-objects.ts
- Code Duplication · Duplicated block (17 lines × 2 locations) packages/ocom/ui-community-route-admin/src/components/members-invite-modal.tsx
- Code Duplication · Duplicated block (16 lines × 2 locations) packages/ocom/application-services/src/contexts/user/staff-role/create.ts
- Code Duplication · Duplicated block (16 lines × 2 locations) packages/ocom/application-services/src/contexts/user/staff-role/query-by-id.ts
- Code Duplication · Duplicated block (16 lines × 4 locations) packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1-finance-details-adhoc-transactions-approval.ts
- Code Duplication · Duplicated block (16 lines × 3 locations) packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1.aggregate.ts
- Code Duplication · Duplicated block (16 lines × 3 locations) packages/ocom/domain/src/domain/iam/member/contexts/member.community.visa.ts
- Code Duplication · Duplicated block (16 lines × 3 locations) packages/ocom/persistence/src/datasources/domain/community/member/member-invitation.domain-adapter.ts
- Code Duplication · Duplicated block (16 lines × 4 locations) packages/ocom/persistence/src/datasources/domain/community/role/vendor-user-role/vendor-user-role.domain-adapter.ts
- Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) packages/ocom-verification/acceptance-api/src/contexts/community/step-definitions/create-community.steps.ts
- Code Duplication · Duplicated block (15 lines × 2 locations) packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1-finance-details-adhoc-transactions-finance-reference.ts
- Code Duplication · Duplicated block (15 lines × 2 locations) packages/ocom/domain/src/domain/contexts/community/member/member-account.ts
- Code Duplication · Duplicated block (15 lines × 2 locations) packages/ocom/domain/src/domain/contexts/user/end-user/end-user.ts
- Code Duplication · Duplicated block (15 lines × 2 locations) packages/ocom/persistence/src/datasources/domain/user/staff-role/staff-role.repository.ts
- Code Duplication · Duplicated block (15 lines × 2 locations) packages/ocom/ui-community-route-admin/src/section-layout.tsx
- Code Duplication · Duplicated block (15 lines × 4 locations) packages/ocom/ui-staff-route-community-management/src/index.tsx
- Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) packages/cellix/server-oauth2-mock-seedwork/src/manager.ts
- Code Duplication · Duplicated block (14 lines × 2 locations) packages/ocom/application-services/src/contexts/community/member/member-management.ts
- Code Duplication · Duplicated block (14 lines × 2 locations) packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts
- Code Duplication · Duplicated block (14 lines × 3 locations) packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role.ts
- Code Duplication · Duplicated block (14 lines × 3 locations) packages/ocom/persistence/src/datasources/domain/community/member/member-invitation.repository.ts
- Code Duplication · Duplicated block (14 lines × 2 locations) packages/ocom/persistence/src/datasources/domain/community/role/end-user-role/end-user-role.repository.ts
- Code Duplication · Duplicated block (14 lines × 2 locations) packages/ocom/persistence/src/datasources/domain/user/vendor-user/vendor-user.domain-adapter.ts
- Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) packages/ocom/ui-staff-route-user-management/src/components/staff-roles-list.container.tsx
- Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) packages/ocom-verification/acceptance-api/src/contexts/authentication/step-definitions/header-login.steps.ts
- Code Duplication · Duplicated block (13 lines × 2 locations) packages/ocom-verification/acceptance-api/src/contexts/community/questions/community-name.ts
- Code Duplication · Duplicated block (13 lines × 2 locations) packages/ocom-verification/acceptance-ui/src/contexts/staff-role/abilities/mock-staff-role-backend.ts
- Code Duplication · Duplicated block (13 lines × 17 locations) packages/ocom/domain/src/domain/contexts/community/member/member-profile.ts
- Code Duplication · Duplicated block (13 lines × 2 locations) packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role.ts
- Code Duplication · Duplicated block (13 lines × 2 locations) packages/ocom/domain/src/domain/iam/user/staff-user/contexts/staff-user.service-ticket.visa.ts
- Code Duplication · Duplicated block (13 lines × 2 locations) packages/ocom/graphql/src/schema/types/member.resolvers.ts
- Code Duplication · Duplicated block (13 lines × 2 locations) packages/ocom/graphql/src/schema/types/member.resolvers.ts
- Code Duplication · Duplicated block (13 lines × 4 locations) packages/ocom/persistence/src/datasources/domain/community/member/member-invitation.domain-adapter.ts
- Code Duplication · Duplicated block (13 lines × 5 locations) packages/ocom/ui-community-route-accounts/.storybook/main.ts
- Code Duplication · Duplicated block (13 lines × 2 locations) packages/ocom/ui-community-route-admin/src/components/members-accounts-edit.container.tsx
- Code Duplication · Duplicated block (12 lines × 2 locations) apps/ui-community/.storybook/main.ts
- Code Duplication · Duplicated block (12 lines × 2 locations) packages/cellix/domain-seedwork/src/domain-seedwork/aggregate-root.ts
- Code Duplication · Duplicated block (12 lines × 2 locations) packages/cellix/domain-seedwork/src/domain-seedwork/domain-event.ts
- Code Duplication · Duplicated block (12 lines × 3 locations) packages/ocom/application-services/src/contexts/community/member/member-management.ts
- Code Duplication · Duplicated block (12 lines × 2 locations) packages/ocom/data-sources-mongoose-models/src/models/case/service-ticket.model.ts
- Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1-activity-detail.value-objects.ts
- Code Duplication · Duplicated block (12 lines × 2 locations) packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role.ts
- Code Duplication · Duplicated block (12 lines × 2 locations) packages/ocom/domain/src/domain/iam/member/contexts/member.user.staff-role.visa.ts
- Code Duplication · Duplicated block (12 lines × 4 locations) packages/ocom/graphql/src/schema/types/member.resolvers.ts
- Code Duplication · Duplicated block (12 lines × 9 locations) packages/ocom/persistence/src/datasources/domain/property/property/property.domain-adapter.ts
- Code Duplication · Duplicated block (11 lines × 4 locations) packages/cellix/api-core/src/cellix.ts
- Code Duplication · Duplicated block (11 lines × 2 locations) packages/cellix/service-queue-storage/src/internal-queue-storage-service.ts
- Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) packages/ocom-verification/acceptance-ui/src/contexts/authentication/tasks/click-header-sign-in.ts
- Code Duplication · Duplicated block (11 lines × 9 locations) packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1-finance-details-adhoc-transactions.ts
- Code Duplication · Duplicated block (11 lines × 2 locations) packages/ocom/persistence/src/datasources/domain/community/community/community.domain-adapter.ts
Rebuild cost: about €130,000 · Estimate
| Cost to rebuild | €42,000 to €210,000, for 699 to 2,219 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 47. 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: 43,941 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 cellix.domain-seedwork.src.domain-seedwork.domain-event | 2 cellix.domain-seedwork.src.domain-seedwork.prop-array | 3 ocom.application-services.src | 4 ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_visa | 5 ocom.domain.src.domain.contexts.community.community_visa | 6 ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects | 7 ocom.domain.src.domain.contexts.property.property_visa | 8 ocom.domain.src.domain.contexts.user.user_visa | 9 cellix.domain-seedwork.src.domain-seedwork.value-object | 10 ocom.domain.src.domain.contexts.community.community.community | 11 ocom.domain.src.domain.contexts.user.vendor-user.vendor-user | 12 ocom.domain.src.domain.contexts.community.community_passport | 13 ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions | 14 ocom.domain.src.domain.contexts.community.role.vendor-user-role.vendor-user-role-permissions | 15 ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity | 16 ocom.domain.src.domain.contexts.service.service.service_aggregate | 17 ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions | 18 ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role | 19 ocom.domain.src.domain.contexts.property.property.property_aggregate | 20 ocom.domain.src.domain.contexts.service.service_passport | 21 ocom.domain.src.domain.contexts.user.staff-role.staff-role | 22 ocom.persistence.src.datasources.domain.property.property.property_domain-adapter | 23 ocom.persistence.src.datasources.domain.user.staff-role.staff-role_domain-adapter | 24 ocom.application-services.src.contexts.user.staff-role | 25 ocom.domain.src.domain.contexts.community.member.member | 26 ocom.domain.src.domain.contexts.property.property_passport | 27 ocom.domain.src.domain.contexts.user.staff-user.staff-user | 28 ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate | 29 ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate | 30 ocom.domain.src.domain.contexts.user.user_passport | 31 ocom.domain.src.domain.contexts.case.case_passport | 32 ocom.domain.src.domain.contexts.passport | 33 ocom.domain.src.domain.contexts.user.end-user.end-user | 34 ocom.application-services.src.contexts.community.member | 35 ocom.domain.src.domain.iam.member.member_passport-base | 36 ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport | 37 ocom.persistence.src.datasources.domain.community.community.community_repository | 38 cellix.domain-seedwork.src.domain-seedwork.domain-entity | 39 ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository | 40 cellix.domain-seedwork.src.domain-seedwork.aggregate-root |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 cellix.domain-seedwork.src.domain-seedwork.domain-event | ||||||||||||||||||||||||||||||||||||||||
| 2 cellix.domain-seedwork.src.domain-seedwork.prop-array | ||||||||||||||||||||||||||||||||||||||||
| 3 ocom.application-services.src | ||||||||||||||||||||||||||||||||||||||||
| 4 ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_visa | ||||||||||||||||||||||||||||||||||||||||
| 5 ocom.domain.src.domain.contexts.community.community_visa | ||||||||||||||||||||||||||||||||||||||||
| 6 ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects | ||||||||||||||||||||||||||||||||||||||||
| 7 ocom.domain.src.domain.contexts.property.property_visa | ||||||||||||||||||||||||||||||||||||||||
| 8 ocom.domain.src.domain.contexts.user.user_visa | ||||||||||||||||||||||||||||||||||||||||
| 9 cellix.domain-seedwork.src.domain-seedwork.value-object | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 ocom.domain.src.domain.contexts.community.community.community | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 11 ocom.domain.src.domain.contexts.user.vendor-user.vendor-user | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 12 ocom.domain.src.domain.contexts.community.community_passport | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 ocom.domain.src.domain.contexts.community.role.vendor-user-role.vendor-user-role-permissions | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity | 1 | 25 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 16 ocom.domain.src.domain.contexts.service.service.service_aggregate | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role | 1 | 3 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 19 ocom.domain.src.domain.contexts.property.property.property_aggregate | 1 | 3 | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 20 ocom.domain.src.domain.contexts.service.service_passport | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 ocom.domain.src.domain.contexts.user.staff-role.staff-role | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 22 ocom.persistence.src.datasources.domain.property.property.property_domain-adapter | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 ocom.persistence.src.datasources.domain.user.staff-role.staff-role_domain-adapter | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 ocom.application-services.src.contexts.user.staff-role | 4 | |||||||||||||||||||||||||||||||||||||||
| 25 ocom.domain.src.domain.contexts.community.member.member | 1 | 1 | 3 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 26 ocom.domain.src.domain.contexts.property.property_passport | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 ocom.domain.src.domain.contexts.user.staff-user.staff-user | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 28 ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 29 ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 30 ocom.domain.src.domain.contexts.user.user_passport | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 31 ocom.domain.src.domain.contexts.case.case_passport | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 ocom.domain.src.domain.contexts.passport | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 33 ocom.domain.src.domain.contexts.user.end-user.end-user | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 ocom.application-services.src.contexts.community.member | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 ocom.domain.src.domain.iam.member.member_passport-base | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 37 ocom.persistence.src.datasources.domain.community.community.community_repository | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 cellix.domain-seedwork.src.domain-seedwork.domain-entity | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 40 cellix.domain-seedwork.src.domain-seedwork.aggregate-root | 1 | 1 | 1 |
9→37 cellix.domain-seedwork.src.domain-seedwork.value-object uses ocom.persistence.src.datasources.domain.community.community.community_repository part of a loop✕
- Connections
- 1 pair of types, where a type in cellix.domain-seedwork.src.domain-seedwork.value-object uses a type in ocom.persistence.src.datasources.domain.community.community.community_repository.
- The types involved
packages.cellix.domain-seedwork.src.domain-seedwork.value-object.ValueObject→packages.ocom.persistence.src.datasources.domain.community.community.community_repository.PropType
- Direction
- cellix.domain-seedwork.src.domain-seedwork.value-object uses ocom.persistence.src.datasources.domain.community.community.community_repository, so a change to ocom.persistence.src.datasources.domain.community.community.community_repository can break cellix.domain-seedwork.src.domain-seedwork.value-object, while a change to cellix.domain-seedwork.src.domain-seedwork.value-object can't break ocom.persistence.src.datasources.domain.community.community.community_repository.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→5 ocom.domain.src.domain.contexts.community.community.community uses ocom.domain.src.domain.contexts.community.community_visa✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.community.community.community uses a type in ocom.domain.src.domain.contexts.community.community_visa.
- The types involved
packages.ocom.domain.src.domain.contexts.community.community.community.Community→packages.ocom.domain.src.domain.contexts.community.community_visa.CommunityVisa
- Direction
- ocom.domain.src.domain.contexts.community.community.community uses ocom.domain.src.domain.contexts.community.community_visa, so a change to ocom.domain.src.domain.contexts.community.community_visa can break ocom.domain.src.domain.contexts.community.community.community, while a change to ocom.domain.src.domain.contexts.community.community.community can't break ocom.domain.src.domain.contexts.community.community_visa.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.community.community.community uses a module listed above it, which is the healthy direction.
10→32 ocom.domain.src.domain.contexts.community.community.community uses ocom.domain.src.domain.contexts.passport part of a loop✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.community.community.community uses a type in ocom.domain.src.domain.contexts.passport.
- The types involved
packages.ocom.domain.src.domain.contexts.community.community.community.Community→packages.ocom.domain.src.domain.contexts.passport.Passport
- Direction
- ocom.domain.src.domain.contexts.community.community.community uses ocom.domain.src.domain.contexts.passport, so a change to ocom.domain.src.domain.contexts.passport can break ocom.domain.src.domain.contexts.community.community.community, while a change to ocom.domain.src.domain.contexts.community.community.community can't break ocom.domain.src.domain.contexts.passport.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→33 ocom.domain.src.domain.contexts.community.community.community uses ocom.domain.src.domain.contexts.user.end-user.end-user part of a loop✕
- Connections
- 2 pairs of types, where a type in ocom.domain.src.domain.contexts.community.community.community uses a type in ocom.domain.src.domain.contexts.user.end-user.end-user.
- The types involved
packages.ocom.domain.src.domain.contexts.community.community.community.Community→packages.ocom.domain.src.domain.contexts.user.end-user.end-user.EndUserEntityReferencepackages.ocom.domain.src.domain.contexts.community.community.community.CommunityProps→packages.ocom.domain.src.domain.contexts.user.end-user.end-user.EndUserEntityReference
- Direction
- ocom.domain.src.domain.contexts.community.community.community uses ocom.domain.src.domain.contexts.user.end-user.end-user, so a change to ocom.domain.src.domain.contexts.user.end-user.end-user can break ocom.domain.src.domain.contexts.community.community.community, while a change to ocom.domain.src.domain.contexts.community.community.community can't break ocom.domain.src.domain.contexts.user.end-user.end-user.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→40 ocom.domain.src.domain.contexts.community.community.community uses cellix.domain-seedwork.src.domain-seedwork.aggregate-root part of a loop✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.community.community.community uses a type in cellix.domain-seedwork.src.domain-seedwork.aggregate-root.
- The types involved
packages.ocom.domain.src.domain.contexts.community.community.community.Community→packages.cellix.domain-seedwork.src.domain-seedwork.aggregate-root.AggregateRoot
- Direction
- ocom.domain.src.domain.contexts.community.community.community uses cellix.domain-seedwork.src.domain-seedwork.aggregate-root, so a change to cellix.domain-seedwork.src.domain-seedwork.aggregate-root can break ocom.domain.src.domain.contexts.community.community.community, while a change to ocom.domain.src.domain.contexts.community.community.community can't break cellix.domain-seedwork.src.domain-seedwork.aggregate-root.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→8 ocom.domain.src.domain.contexts.user.vendor-user.vendor-user uses ocom.domain.src.domain.contexts.user.user_visa✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.user.vendor-user.vendor-user uses a type in ocom.domain.src.domain.contexts.user.user_visa.
- The types involved
packages.ocom.domain.src.domain.contexts.user.vendor-user.vendor-user.VendorUser→packages.ocom.domain.src.domain.contexts.user.user_visa.UserVisa
- Direction
- ocom.domain.src.domain.contexts.user.vendor-user.vendor-user uses ocom.domain.src.domain.contexts.user.user_visa, so a change to ocom.domain.src.domain.contexts.user.user_visa can break ocom.domain.src.domain.contexts.user.vendor-user.vendor-user, while a change to ocom.domain.src.domain.contexts.user.vendor-user.vendor-user can't break ocom.domain.src.domain.contexts.user.user_visa.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.user.vendor-user.vendor-user uses a module listed above it, which is the healthy direction.
11→32 ocom.domain.src.domain.contexts.user.vendor-user.vendor-user uses ocom.domain.src.domain.contexts.passport part of a loop✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.user.vendor-user.vendor-user uses a type in ocom.domain.src.domain.contexts.passport.
- The types involved
packages.ocom.domain.src.domain.contexts.user.vendor-user.vendor-user.VendorUser→packages.ocom.domain.src.domain.contexts.passport.Passport
- Direction
- ocom.domain.src.domain.contexts.user.vendor-user.vendor-user uses ocom.domain.src.domain.contexts.passport, so a change to ocom.domain.src.domain.contexts.passport can break ocom.domain.src.domain.contexts.user.vendor-user.vendor-user, while a change to ocom.domain.src.domain.contexts.user.vendor-user.vendor-user can't break ocom.domain.src.domain.contexts.passport.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→40 ocom.domain.src.domain.contexts.user.vendor-user.vendor-user uses cellix.domain-seedwork.src.domain-seedwork.aggregate-root part of a loop✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.user.vendor-user.vendor-user uses a type in cellix.domain-seedwork.src.domain-seedwork.aggregate-root.
- The types involved
packages.ocom.domain.src.domain.contexts.user.vendor-user.vendor-user.VendorUser→packages.cellix.domain-seedwork.src.domain-seedwork.aggregate-root.AggregateRoot
- Direction
- ocom.domain.src.domain.contexts.user.vendor-user.vendor-user uses cellix.domain-seedwork.src.domain-seedwork.aggregate-root, so a change to cellix.domain-seedwork.src.domain-seedwork.aggregate-root can break ocom.domain.src.domain.contexts.user.vendor-user.vendor-user, while a change to ocom.domain.src.domain.contexts.user.vendor-user.vendor-user can't break cellix.domain-seedwork.src.domain-seedwork.aggregate-root.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→5 ocom.domain.src.domain.contexts.community.community_passport uses ocom.domain.src.domain.contexts.community.community_visa✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.community.community_passport uses a type in ocom.domain.src.domain.contexts.community.community_visa.
- The types involved
packages.ocom.domain.src.domain.contexts.community.community_passport.CommunityPassport→packages.ocom.domain.src.domain.contexts.community.community_visa.CommunityVisa
- Direction
- ocom.domain.src.domain.contexts.community.community_passport uses ocom.domain.src.domain.contexts.community.community_visa, so a change to ocom.domain.src.domain.contexts.community.community_visa can break ocom.domain.src.domain.contexts.community.community_passport, while a change to ocom.domain.src.domain.contexts.community.community_passport can't break ocom.domain.src.domain.contexts.community.community_visa.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.community.community_passport uses a module listed above it, which is the healthy direction.
12→10 ocom.domain.src.domain.contexts.community.community_passport uses ocom.domain.src.domain.contexts.community.community.community✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.community.community_passport uses a type in ocom.domain.src.domain.contexts.community.community.community.
- The types involved
packages.ocom.domain.src.domain.contexts.community.community_passport.CommunityPassport→packages.ocom.domain.src.domain.contexts.community.community.community.CommunityEntityReference
- Direction
- ocom.domain.src.domain.contexts.community.community_passport uses ocom.domain.src.domain.contexts.community.community.community, so a change to ocom.domain.src.domain.contexts.community.community.community can break ocom.domain.src.domain.contexts.community.community_passport, while a change to ocom.domain.src.domain.contexts.community.community_passport can't break ocom.domain.src.domain.contexts.community.community.community.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.community.community_passport uses a module listed above it, which is the healthy direction.
13→5 ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions uses ocom.domain.src.domain.contexts.community.community_visa✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions uses a type in ocom.domain.src.domain.contexts.community.community_visa.
- The types involved
packages.ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions.EndUserRolePermissions→packages.ocom.domain.src.domain.contexts.community.community_visa.CommunityVisa
- Direction
- ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions uses ocom.domain.src.domain.contexts.community.community_visa, so a change to ocom.domain.src.domain.contexts.community.community_visa can break ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions, while a change to ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions can't break ocom.domain.src.domain.contexts.community.community_visa.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions uses a module listed above it, which is the healthy direction.
13→9 ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions uses cellix.domain-seedwork.src.domain-seedwork.value-object✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions uses a type in cellix.domain-seedwork.src.domain-seedwork.value-object.
- The types involved
packages.ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions.EndUserRolePermissions→packages.cellix.domain-seedwork.src.domain-seedwork.value-object.ValueObject
- Direction
- ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions uses cellix.domain-seedwork.src.domain-seedwork.value-object, so a change to cellix.domain-seedwork.src.domain-seedwork.value-object can break ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions, while a change to ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions can't break cellix.domain-seedwork.src.domain-seedwork.value-object.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions uses a module listed above it, which is the healthy direction.
14→5 ocom.domain.src.domain.contexts.community.role.vendor-user-role.vendor-user-role-permissions uses ocom.domain.src.domain.contexts.community.community_visa✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.community.role.vendor-user-role.vendor-user-role-permissions uses a type in ocom.domain.src.domain.contexts.community.community_visa.
- The types involved
packages.ocom.domain.src.domain.contexts.community.role.vendor-user-role.vendor-user-role-permissions.VendorUserRolePermissions→packages.ocom.domain.src.domain.contexts.community.community_visa.CommunityVisa
- Direction
- ocom.domain.src.domain.contexts.community.role.vendor-user-role.vendor-user-role-permissions uses ocom.domain.src.domain.contexts.community.community_visa, so a change to ocom.domain.src.domain.contexts.community.community_visa can break ocom.domain.src.domain.contexts.community.role.vendor-user-role.vendor-user-role-permissions, while a change to ocom.domain.src.domain.contexts.community.role.vendor-user-role.vendor-user-role-permissions can't break ocom.domain.src.domain.contexts.community.community_visa.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.community.role.vendor-user-role.vendor-user-role-permissions uses a module listed above it, which is the healthy direction.
14→9 ocom.domain.src.domain.contexts.community.role.vendor-user-role.vendor-user-role-permissions uses cellix.domain-seedwork.src.domain-seedwork.value-object✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.community.role.vendor-user-role.vendor-user-role-permissions uses a type in cellix.domain-seedwork.src.domain-seedwork.value-object.
- The types involved
packages.ocom.domain.src.domain.contexts.community.role.vendor-user-role.vendor-user-role-permissions.VendorUserRolePermissions→packages.cellix.domain-seedwork.src.domain-seedwork.value-object.ValueObject
- Direction
- ocom.domain.src.domain.contexts.community.role.vendor-user-role.vendor-user-role-permissions uses cellix.domain-seedwork.src.domain-seedwork.value-object, so a change to cellix.domain-seedwork.src.domain-seedwork.value-object can break ocom.domain.src.domain.contexts.community.role.vendor-user-role.vendor-user-role-permissions, while a change to ocom.domain.src.domain.contexts.community.role.vendor-user-role.vendor-user-role-permissions can't break cellix.domain-seedwork.src.domain-seedwork.value-object.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.community.role.vendor-user-role.vendor-user-role-permissions uses a module listed above it, which is the healthy direction.
15→2 ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity uses cellix.domain-seedwork.src.domain-seedwork.prop-array✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity uses a type in cellix.domain-seedwork.src.domain-seedwork.prop-array.
- The types involved
packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetailProps→packages.cellix.domain-seedwork.src.domain-seedwork.prop-array.PropArray
- Direction
- ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity uses cellix.domain-seedwork.src.domain-seedwork.prop-array, so a change to cellix.domain-seedwork.src.domain-seedwork.prop-array can break ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity, while a change to ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity can't break cellix.domain-seedwork.src.domain-seedwork.prop-array.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity uses a module listed above it, which is the healthy direction.
15→6 ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity uses ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects✕
- Connections
- 25 pairs of types, where a type in ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity uses a type in ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.
- The types involved
packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.Amenitiespackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.Bathroomspackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.Bedroomspackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.Descriptionpackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.FloorPlanpackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.FloorPlanImagespackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.Imagespackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.Leasepackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.ListingAgentpackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.ListingAgentCompanypackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.ListingAgentCompanyAddresspackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.ListingAgentCompanyEmailpackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.ListingAgentCompanyPhonepackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.ListingAgentCompanyWebsitepackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.ListingAgentEmailpackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.ListingAgentPhonepackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.ListingAgentWebsitepackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.LotSizepackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.MaxGuestspackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.Pricepackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.RentHighpackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.RentLowpackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.SquareFeetpackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.Videopackages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.YearBuilt
- Direction
- ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity uses ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects, so a change to ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects can break ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity, while a change to ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity can't break ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity uses a module listed above it, which is the healthy direction.
15→7 ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity uses ocom.domain.src.domain.contexts.property.property_visa✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity uses a type in ocom.domain.src.domain.contexts.property.property_visa.
- The types involved
packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.ocom.domain.src.domain.contexts.property.property_visa.PropertyVisa
- Direction
- ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity uses ocom.domain.src.domain.contexts.property.property_visa, so a change to ocom.domain.src.domain.contexts.property.property_visa can break ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity, while a change to ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity can't break ocom.domain.src.domain.contexts.property.property_visa.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity uses a module listed above it, which is the healthy direction.
15→9 ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity uses cellix.domain-seedwork.src.domain-seedwork.value-object✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity uses a type in cellix.domain-seedwork.src.domain-seedwork.value-object.
- The types involved
packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetail→packages.cellix.domain-seedwork.src.domain-seedwork.value-object.ValueObject
- Direction
- ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity uses cellix.domain-seedwork.src.domain-seedwork.value-object, so a change to cellix.domain-seedwork.src.domain-seedwork.value-object can break ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity, while a change to ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity can't break cellix.domain-seedwork.src.domain-seedwork.value-object.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity uses a module listed above it, which is the healthy direction.
16→10 ocom.domain.src.domain.contexts.service.service.service_aggregate uses ocom.domain.src.domain.contexts.community.community.community✕
- Connections
- 4 pairs of types, where a type in ocom.domain.src.domain.contexts.service.service.service_aggregate uses a type in ocom.domain.src.domain.contexts.community.community.community.
- The types involved
packages.ocom.domain.src.domain.contexts.service.service.service_aggregate.Service→packages.ocom.domain.src.domain.contexts.community.community.community.CommunityEntityReferencepackages.ocom.domain.src.domain.contexts.service.service.service_aggregate.ServiceEntityReference→packages.ocom.domain.src.domain.contexts.community.community.community.CommunityEntityReferencepackages.ocom.domain.src.domain.contexts.service.service.service_aggregate.ServiceProps→packages.ocom.domain.src.domain.contexts.community.community.community.CommunityEntityReferencepackages.ocom.domain.src.domain.contexts.service.service.service_aggregate.ServiceProps→packages.ocom.domain.src.domain.contexts.community.community.community.CommunityProps
- Direction
- ocom.domain.src.domain.contexts.service.service.service_aggregate uses ocom.domain.src.domain.contexts.community.community.community, so a change to ocom.domain.src.domain.contexts.community.community.community can break ocom.domain.src.domain.contexts.service.service.service_aggregate, while a change to ocom.domain.src.domain.contexts.service.service.service_aggregate can't break ocom.domain.src.domain.contexts.community.community.community.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.service.service.service_aggregate uses a module listed above it, which is the healthy direction.
16→32 ocom.domain.src.domain.contexts.service.service.service_aggregate uses ocom.domain.src.domain.contexts.passport part of a loop✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.service.service.service_aggregate uses a type in ocom.domain.src.domain.contexts.passport.
- The types involved
packages.ocom.domain.src.domain.contexts.service.service.service_aggregate.Service→packages.ocom.domain.src.domain.contexts.passport.Passport
- Direction
- ocom.domain.src.domain.contexts.service.service.service_aggregate uses ocom.domain.src.domain.contexts.passport, so a change to ocom.domain.src.domain.contexts.passport can break ocom.domain.src.domain.contexts.service.service.service_aggregate, while a change to ocom.domain.src.domain.contexts.service.service.service_aggregate can't break ocom.domain.src.domain.contexts.passport.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→40 ocom.domain.src.domain.contexts.service.service.service_aggregate uses cellix.domain-seedwork.src.domain-seedwork.aggregate-root part of a loop✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.service.service.service_aggregate uses a type in cellix.domain-seedwork.src.domain-seedwork.aggregate-root.
- The types involved
packages.ocom.domain.src.domain.contexts.service.service.service_aggregate.Service→packages.cellix.domain-seedwork.src.domain-seedwork.aggregate-root.AggregateRoot
- Direction
- ocom.domain.src.domain.contexts.service.service.service_aggregate uses cellix.domain-seedwork.src.domain-seedwork.aggregate-root, so a change to cellix.domain-seedwork.src.domain-seedwork.aggregate-root can break ocom.domain.src.domain.contexts.service.service.service_aggregate, while a change to ocom.domain.src.domain.contexts.service.service.service_aggregate can't break cellix.domain-seedwork.src.domain-seedwork.aggregate-root.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→8 ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions uses ocom.domain.src.domain.contexts.user.user_visa✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions uses a type in ocom.domain.src.domain.contexts.user.user_visa.
- The types involved
packages.ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions.StaffRolePermissions→packages.ocom.domain.src.domain.contexts.user.user_visa.UserVisa
- Direction
- ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions uses ocom.domain.src.domain.contexts.user.user_visa, so a change to ocom.domain.src.domain.contexts.user.user_visa can break ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions, while a change to ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions can't break ocom.domain.src.domain.contexts.user.user_visa.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions uses a module listed above it, which is the healthy direction.
17→9 ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions uses cellix.domain-seedwork.src.domain-seedwork.value-object✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions uses a type in cellix.domain-seedwork.src.domain-seedwork.value-object.
- The types involved
packages.ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions.StaffRolePermissions→packages.cellix.domain-seedwork.src.domain-seedwork.value-object.ValueObject
- Direction
- ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions uses cellix.domain-seedwork.src.domain-seedwork.value-object, so a change to cellix.domain-seedwork.src.domain-seedwork.value-object can break ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions, while a change to ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions can't break cellix.domain-seedwork.src.domain-seedwork.value-object.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions uses a module listed above it, which is the healthy direction.
18→5 ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role uses ocom.domain.src.domain.contexts.community.community_visa✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role uses a type in ocom.domain.src.domain.contexts.community.community_visa.
- The types involved
packages.ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role.EndUserRole→packages.ocom.domain.src.domain.contexts.community.community_visa.CommunityVisa
- Direction
- ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role uses ocom.domain.src.domain.contexts.community.community_visa, so a change to ocom.domain.src.domain.contexts.community.community_visa can break ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role, while a change to ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role can't break ocom.domain.src.domain.contexts.community.community_visa.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role uses a module listed above it, which is the healthy direction.
18→10 ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role uses ocom.domain.src.domain.contexts.community.community.community✕
- Connections
- 3 pairs of types, where a type in ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role uses a type in ocom.domain.src.domain.contexts.community.community.community.
- The types involved
packages.ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role.EndUserRole→packages.ocom.domain.src.domain.contexts.community.community.community.CommunityEntityReferencepackages.ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role.EndUserRoleEntityReference→packages.ocom.domain.src.domain.contexts.community.community.community.CommunityEntityReferencepackages.ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role.EndUserRoleProps→packages.ocom.domain.src.domain.contexts.community.community.community.CommunityProps
- Direction
- ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role uses ocom.domain.src.domain.contexts.community.community.community, so a change to ocom.domain.src.domain.contexts.community.community.community can break ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role, while a change to ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role can't break ocom.domain.src.domain.contexts.community.community.community.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role uses a module listed above it, which is the healthy direction.
18→13 ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role uses ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions✕
- Connections
- 2 pairs of types, where a type in ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role uses a type in ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions.
- The types involved
packages.ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role.EndUserRoleEntityReference→packages.ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions.EndUserRolePermissionsEntityReferencepackages.ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role.EndUserRoleProps→packages.ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions.EndUserRolePermissionsProps
- Direction
- ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role uses ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions, so a change to ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions can break ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role, while a change to ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role can't break ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role uses a module listed above it, which is the healthy direction.
18→32 ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role uses ocom.domain.src.domain.contexts.passport part of a loop✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role uses a type in ocom.domain.src.domain.contexts.passport.
- The types involved
packages.ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role.EndUserRole→packages.ocom.domain.src.domain.contexts.passport.Passport
- Direction
- ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role uses ocom.domain.src.domain.contexts.passport, so a change to ocom.domain.src.domain.contexts.passport can break ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role, while a change to ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role can't break ocom.domain.src.domain.contexts.passport.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→40 ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role uses cellix.domain-seedwork.src.domain-seedwork.aggregate-root part of a loop✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role uses a type in cellix.domain-seedwork.src.domain-seedwork.aggregate-root.
- The types involved
packages.ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role.EndUserRole→packages.cellix.domain-seedwork.src.domain-seedwork.aggregate-root.AggregateRoot
- Direction
- ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role uses cellix.domain-seedwork.src.domain-seedwork.aggregate-root, so a change to cellix.domain-seedwork.src.domain-seedwork.aggregate-root can break ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role, while a change to ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role can't break cellix.domain-seedwork.src.domain-seedwork.aggregate-root.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→7 ocom.domain.src.domain.contexts.property.property.property_aggregate uses ocom.domain.src.domain.contexts.property.property_visa✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.property.property.property_aggregate uses a type in ocom.domain.src.domain.contexts.property.property_visa.
- The types involved
packages.ocom.domain.src.domain.contexts.property.property.property_aggregate.Property→packages.ocom.domain.src.domain.contexts.property.property_visa.PropertyVisa
- Direction
- ocom.domain.src.domain.contexts.property.property.property_aggregate uses ocom.domain.src.domain.contexts.property.property_visa, so a change to ocom.domain.src.domain.contexts.property.property_visa can break ocom.domain.src.domain.contexts.property.property.property_aggregate, while a change to ocom.domain.src.domain.contexts.property.property.property_aggregate can't break ocom.domain.src.domain.contexts.property.property_visa.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.property.property.property_aggregate uses a module listed above it, which is the healthy direction.
19→10 ocom.domain.src.domain.contexts.property.property.property_aggregate uses ocom.domain.src.domain.contexts.community.community.community✕
- Connections
- 3 pairs of types, where a type in ocom.domain.src.domain.contexts.property.property.property_aggregate uses a type in ocom.domain.src.domain.contexts.community.community.community.
- The types involved
packages.ocom.domain.src.domain.contexts.property.property.property_aggregate.Property→packages.ocom.domain.src.domain.contexts.community.community.community.CommunityEntityReferencepackages.ocom.domain.src.domain.contexts.property.property.property_aggregate.PropertyEntityReference→packages.ocom.domain.src.domain.contexts.community.community.community.CommunityEntityReferencepackages.ocom.domain.src.domain.contexts.property.property.property_aggregate.PropertyProps→packages.ocom.domain.src.domain.contexts.community.community.community.CommunityProps
- Direction
- ocom.domain.src.domain.contexts.property.property.property_aggregate uses ocom.domain.src.domain.contexts.community.community.community, so a change to ocom.domain.src.domain.contexts.community.community.community can break ocom.domain.src.domain.contexts.property.property.property_aggregate, while a change to ocom.domain.src.domain.contexts.property.property.property_aggregate can't break ocom.domain.src.domain.contexts.community.community.community.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.property.property.property_aggregate uses a module listed above it, which is the healthy direction.
19→15 ocom.domain.src.domain.contexts.property.property.property_aggregate uses ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity✕
- Connections
- 3 pairs of types, where a type in ocom.domain.src.domain.contexts.property.property.property_aggregate uses a type in ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.
- The types involved
packages.ocom.domain.src.domain.contexts.property.property.property_aggregate.Property→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetailEntityReferencepackages.ocom.domain.src.domain.contexts.property.property.property_aggregate.PropertyEntityReference→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetailEntityReferencepackages.ocom.domain.src.domain.contexts.property.property.property_aggregate.PropertyProps→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetailProps
- Direction
- ocom.domain.src.domain.contexts.property.property.property_aggregate uses ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity, so a change to ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity can break ocom.domain.src.domain.contexts.property.property.property_aggregate, while a change to ocom.domain.src.domain.contexts.property.property.property_aggregate can't break ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.property.property.property_aggregate uses a module listed above it, which is the healthy direction.
19→32 ocom.domain.src.domain.contexts.property.property.property_aggregate uses ocom.domain.src.domain.contexts.passport part of a loop✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.property.property.property_aggregate uses a type in ocom.domain.src.domain.contexts.passport.
- The types involved
packages.ocom.domain.src.domain.contexts.property.property.property_aggregate.Property→packages.ocom.domain.src.domain.contexts.passport.Passport
- Direction
- ocom.domain.src.domain.contexts.property.property.property_aggregate uses ocom.domain.src.domain.contexts.passport, so a change to ocom.domain.src.domain.contexts.passport can break ocom.domain.src.domain.contexts.property.property.property_aggregate, while a change to ocom.domain.src.domain.contexts.property.property.property_aggregate can't break ocom.domain.src.domain.contexts.passport.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→40 ocom.domain.src.domain.contexts.property.property.property_aggregate uses cellix.domain-seedwork.src.domain-seedwork.aggregate-root part of a loop✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.property.property.property_aggregate uses a type in cellix.domain-seedwork.src.domain-seedwork.aggregate-root.
- The types involved
packages.ocom.domain.src.domain.contexts.property.property.property_aggregate.Property→packages.cellix.domain-seedwork.src.domain-seedwork.aggregate-root.AggregateRoot
- Direction
- ocom.domain.src.domain.contexts.property.property.property_aggregate uses cellix.domain-seedwork.src.domain-seedwork.aggregate-root, so a change to cellix.domain-seedwork.src.domain-seedwork.aggregate-root can break ocom.domain.src.domain.contexts.property.property.property_aggregate, while a change to ocom.domain.src.domain.contexts.property.property.property_aggregate can't break cellix.domain-seedwork.src.domain-seedwork.aggregate-root.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→16 ocom.domain.src.domain.contexts.service.service_passport uses ocom.domain.src.domain.contexts.service.service.service_aggregate✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.service.service_passport uses a type in ocom.domain.src.domain.contexts.service.service.service_aggregate.
- The types involved
packages.ocom.domain.src.domain.contexts.service.service_passport.ServicePassport→packages.ocom.domain.src.domain.contexts.service.service.service_aggregate.ServiceEntityReference
- Direction
- ocom.domain.src.domain.contexts.service.service_passport uses ocom.domain.src.domain.contexts.service.service.service_aggregate, so a change to ocom.domain.src.domain.contexts.service.service.service_aggregate can break ocom.domain.src.domain.contexts.service.service_passport, while a change to ocom.domain.src.domain.contexts.service.service_passport can't break ocom.domain.src.domain.contexts.service.service.service_aggregate.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.service.service_passport uses a module listed above it, which is the healthy direction.
21→8 ocom.domain.src.domain.contexts.user.staff-role.staff-role uses ocom.domain.src.domain.contexts.user.user_visa✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.user.staff-role.staff-role uses a type in ocom.domain.src.domain.contexts.user.user_visa.
- The types involved
packages.ocom.domain.src.domain.contexts.user.staff-role.staff-role.StaffRole→packages.ocom.domain.src.domain.contexts.user.user_visa.UserVisa
- Direction
- ocom.domain.src.domain.contexts.user.staff-role.staff-role uses ocom.domain.src.domain.contexts.user.user_visa, so a change to ocom.domain.src.domain.contexts.user.user_visa can break ocom.domain.src.domain.contexts.user.staff-role.staff-role, while a change to ocom.domain.src.domain.contexts.user.staff-role.staff-role can't break ocom.domain.src.domain.contexts.user.user_visa.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.user.staff-role.staff-role uses a module listed above it, which is the healthy direction.
21→17 ocom.domain.src.domain.contexts.user.staff-role.staff-role uses ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions✕
- Connections
- 2 pairs of types, where a type in ocom.domain.src.domain.contexts.user.staff-role.staff-role uses a type in ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions.
- The types involved
packages.ocom.domain.src.domain.contexts.user.staff-role.staff-role.StaffRoleEntityReference→packages.ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions.StaffRolePermissionsEntityReferencepackages.ocom.domain.src.domain.contexts.user.staff-role.staff-role.StaffRoleProps→packages.ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions.StaffRolePermissionsProps
- Direction
- ocom.domain.src.domain.contexts.user.staff-role.staff-role uses ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions, so a change to ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions can break ocom.domain.src.domain.contexts.user.staff-role.staff-role, while a change to ocom.domain.src.domain.contexts.user.staff-role.staff-role can't break ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.user.staff-role.staff-role uses a module listed above it, which is the healthy direction.
21→32 ocom.domain.src.domain.contexts.user.staff-role.staff-role uses ocom.domain.src.domain.contexts.passport part of a loop✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.user.staff-role.staff-role uses a type in ocom.domain.src.domain.contexts.passport.
- The types involved
packages.ocom.domain.src.domain.contexts.user.staff-role.staff-role.StaffRole→packages.ocom.domain.src.domain.contexts.passport.Passport
- Direction
- ocom.domain.src.domain.contexts.user.staff-role.staff-role uses ocom.domain.src.domain.contexts.passport, so a change to ocom.domain.src.domain.contexts.passport can break ocom.domain.src.domain.contexts.user.staff-role.staff-role, while a change to ocom.domain.src.domain.contexts.user.staff-role.staff-role can't break ocom.domain.src.domain.contexts.passport.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→40 ocom.domain.src.domain.contexts.user.staff-role.staff-role uses cellix.domain-seedwork.src.domain-seedwork.aggregate-root part of a loop✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.user.staff-role.staff-role uses a type in cellix.domain-seedwork.src.domain-seedwork.aggregate-root.
- The types involved
packages.ocom.domain.src.domain.contexts.user.staff-role.staff-role.StaffRole→packages.cellix.domain-seedwork.src.domain-seedwork.aggregate-root.AggregateRoot
- Direction
- ocom.domain.src.domain.contexts.user.staff-role.staff-role uses cellix.domain-seedwork.src.domain-seedwork.aggregate-root, so a change to cellix.domain-seedwork.src.domain-seedwork.aggregate-root can break ocom.domain.src.domain.contexts.user.staff-role.staff-role, while a change to ocom.domain.src.domain.contexts.user.staff-role.staff-role can't break cellix.domain-seedwork.src.domain-seedwork.aggregate-root.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→2 ocom.persistence.src.datasources.domain.property.property.property_domain-adapter uses cellix.domain-seedwork.src.domain-seedwork.prop-array✕
- Connections
- 1 pair of types, where a type in ocom.persistence.src.datasources.domain.property.property.property_domain-adapter uses a type in cellix.domain-seedwork.src.domain-seedwork.prop-array.
- The types involved
packages.ocom.persistence.src.datasources.domain.property.property.property_domain-adapter.PropertyListingDetailDomainAdapter→packages.cellix.domain-seedwork.src.domain-seedwork.prop-array.PropArray
- Direction
- ocom.persistence.src.datasources.domain.property.property.property_domain-adapter uses cellix.domain-seedwork.src.domain-seedwork.prop-array, so a change to cellix.domain-seedwork.src.domain-seedwork.prop-array can break ocom.persistence.src.datasources.domain.property.property.property_domain-adapter, while a change to ocom.persistence.src.datasources.domain.property.property.property_domain-adapter can't break cellix.domain-seedwork.src.domain-seedwork.prop-array.
- Position
- Below the diagonal: ocom.persistence.src.datasources.domain.property.property.property_domain-adapter uses a module listed above it, which is the healthy direction.
22→10 ocom.persistence.src.datasources.domain.property.property.property_domain-adapter uses ocom.domain.src.domain.contexts.community.community.community✕
- Connections
- 1 pair of types, where a type in ocom.persistence.src.datasources.domain.property.property.property_domain-adapter uses a type in ocom.domain.src.domain.contexts.community.community.community.
- The types involved
packages.ocom.persistence.src.datasources.domain.property.property.property_domain-adapter.PropertyDomainAdapter→packages.ocom.domain.src.domain.contexts.community.community.community.CommunityProps
- Direction
- ocom.persistence.src.datasources.domain.property.property.property_domain-adapter uses ocom.domain.src.domain.contexts.community.community.community, so a change to ocom.domain.src.domain.contexts.community.community.community can break ocom.persistence.src.datasources.domain.property.property.property_domain-adapter, while a change to ocom.persistence.src.datasources.domain.property.property.property_domain-adapter can't break ocom.domain.src.domain.contexts.community.community.community.
- Position
- Below the diagonal: ocom.persistence.src.datasources.domain.property.property.property_domain-adapter uses a module listed above it, which is the healthy direction.
22→15 ocom.persistence.src.datasources.domain.property.property.property_domain-adapter uses ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity✕
- Connections
- 1 pair of types, where a type in ocom.persistence.src.datasources.domain.property.property.property_domain-adapter uses a type in ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.
- The types involved
packages.ocom.persistence.src.datasources.domain.property.property.property_domain-adapter.PropertyDomainAdapter→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.PropertyListingDetailProps
- Direction
- ocom.persistence.src.datasources.domain.property.property.property_domain-adapter uses ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity, so a change to ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity can break ocom.persistence.src.datasources.domain.property.property.property_domain-adapter, while a change to ocom.persistence.src.datasources.domain.property.property.property_domain-adapter can't break ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity.
- Position
- Below the diagonal: ocom.persistence.src.datasources.domain.property.property.property_domain-adapter uses a module listed above it, which is the healthy direction.
23→17 ocom.persistence.src.datasources.domain.user.staff-role.staff-role_domain-adapter uses ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions✕
- Connections
- 1 pair of types, where a type in ocom.persistence.src.datasources.domain.user.staff-role.staff-role_domain-adapter uses a type in ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions.
- The types involved
packages.ocom.persistence.src.datasources.domain.user.staff-role.staff-role_domain-adapter.StaffRoleDomainAdapter→packages.ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions.StaffRolePermissionsProps
- Direction
- ocom.persistence.src.datasources.domain.user.staff-role.staff-role_domain-adapter uses ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions, so a change to ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions can break ocom.persistence.src.datasources.domain.user.staff-role.staff-role_domain-adapter, while a change to ocom.persistence.src.datasources.domain.user.staff-role.staff-role_domain-adapter can't break ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions.
- Position
- Below the diagonal: ocom.persistence.src.datasources.domain.user.staff-role.staff-role_domain-adapter uses a module listed above it, which is the healthy direction.
24→21 ocom.application-services.src.contexts.user.staff-role uses ocom.domain.src.domain.contexts.user.staff-role.staff-role✕
- Connections
- 4 pairs of types, where a type in ocom.application-services.src.contexts.user.staff-role uses a type in ocom.domain.src.domain.contexts.user.staff-role.staff-role.
- The types involved
packages.ocom.application-services.src.contexts.user.staff-role.apply-permissions→packages.ocom.domain.src.domain.contexts.user.staff-role.staff-role.StaffRolePropspackages.ocom.application-services.src.contexts.user.staff-role.create→packages.ocom.domain.src.domain.contexts.user.staff-role.staff-role.StaffRoleEntityReferencepackages.ocom.application-services.src.contexts.user.staff-role.create→packages.ocom.domain.src.domain.contexts.user.staff-role.staff-role.StaffRolePropspackages.ocom.application-services.src.contexts.user.staff-role.update→packages.ocom.domain.src.domain.contexts.user.staff-role.staff-role.StaffRoleEntityReference
- Direction
- ocom.application-services.src.contexts.user.staff-role uses ocom.domain.src.domain.contexts.user.staff-role.staff-role, so a change to ocom.domain.src.domain.contexts.user.staff-role.staff-role can break ocom.application-services.src.contexts.user.staff-role, while a change to ocom.application-services.src.contexts.user.staff-role can't break ocom.domain.src.domain.contexts.user.staff-role.staff-role.
- Position
- Below the diagonal: ocom.application-services.src.contexts.user.staff-role uses a module listed above it, which is the healthy direction.
25→2 ocom.domain.src.domain.contexts.community.member.member uses cellix.domain-seedwork.src.domain-seedwork.prop-array✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.community.member.member uses a type in cellix.domain-seedwork.src.domain-seedwork.prop-array.
- The types involved
packages.ocom.domain.src.domain.contexts.community.member.member.MemberProps→packages.cellix.domain-seedwork.src.domain-seedwork.prop-array.PropArray
- Direction
- ocom.domain.src.domain.contexts.community.member.member uses cellix.domain-seedwork.src.domain-seedwork.prop-array, so a change to cellix.domain-seedwork.src.domain-seedwork.prop-array can break ocom.domain.src.domain.contexts.community.member.member, while a change to ocom.domain.src.domain.contexts.community.member.member can't break cellix.domain-seedwork.src.domain-seedwork.prop-array.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.community.member.member uses a module listed above it, which is the healthy direction.
25→5 ocom.domain.src.domain.contexts.community.member.member uses ocom.domain.src.domain.contexts.community.community_visa✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.community.member.member uses a type in ocom.domain.src.domain.contexts.community.community_visa.
- The types involved
packages.ocom.domain.src.domain.contexts.community.member.member.Member→packages.ocom.domain.src.domain.contexts.community.community_visa.CommunityVisa
- Direction
- ocom.domain.src.domain.contexts.community.member.member uses ocom.domain.src.domain.contexts.community.community_visa, so a change to ocom.domain.src.domain.contexts.community.community_visa can break ocom.domain.src.domain.contexts.community.member.member, while a change to ocom.domain.src.domain.contexts.community.member.member can't break ocom.domain.src.domain.contexts.community.community_visa.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.community.member.member uses a module listed above it, which is the healthy direction.
25→10 ocom.domain.src.domain.contexts.community.member.member uses ocom.domain.src.domain.contexts.community.community.community✕
- Connections
- 3 pairs of types, where a type in ocom.domain.src.domain.contexts.community.member.member uses a type in ocom.domain.src.domain.contexts.community.community.community.
- The types involved
packages.ocom.domain.src.domain.contexts.community.member.member.Member→packages.ocom.domain.src.domain.contexts.community.community.community.CommunityEntityReferencepackages.ocom.domain.src.domain.contexts.community.member.member.MemberEntityReference→packages.ocom.domain.src.domain.contexts.community.community.community.CommunityEntityReferencepackages.ocom.domain.src.domain.contexts.community.member.member.MemberProps→packages.ocom.domain.src.domain.contexts.community.community.community.CommunityEntityReference
- Direction
- ocom.domain.src.domain.contexts.community.member.member uses ocom.domain.src.domain.contexts.community.community.community, so a change to ocom.domain.src.domain.contexts.community.community.community can break ocom.domain.src.domain.contexts.community.member.member, while a change to ocom.domain.src.domain.contexts.community.member.member can't break ocom.domain.src.domain.contexts.community.community.community.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.community.member.member uses a module listed above it, which is the healthy direction.
25→18 ocom.domain.src.domain.contexts.community.member.member uses ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role✕
- Connections
- 3 pairs of types, where a type in ocom.domain.src.domain.contexts.community.member.member uses a type in ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role.
- The types involved
packages.ocom.domain.src.domain.contexts.community.member.member.Member→packages.ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role.EndUserRoleEntityReferencepackages.ocom.domain.src.domain.contexts.community.member.member.MemberEntityReference→packages.ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role.EndUserRoleEntityReferencepackages.ocom.domain.src.domain.contexts.community.member.member.MemberProps→packages.ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role.EndUserRoleEntityReference
- Direction
- ocom.domain.src.domain.contexts.community.member.member uses ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role, so a change to ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role can break ocom.domain.src.domain.contexts.community.member.member, while a change to ocom.domain.src.domain.contexts.community.member.member can't break ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.community.member.member uses a module listed above it, which is the healthy direction.
25→32 ocom.domain.src.domain.contexts.community.member.member uses ocom.domain.src.domain.contexts.passport part of a loop✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.community.member.member uses a type in ocom.domain.src.domain.contexts.passport.
- The types involved
packages.ocom.domain.src.domain.contexts.community.member.member.Member→packages.ocom.domain.src.domain.contexts.passport.Passport
- Direction
- ocom.domain.src.domain.contexts.community.member.member uses ocom.domain.src.domain.contexts.passport, so a change to ocom.domain.src.domain.contexts.passport can break ocom.domain.src.domain.contexts.community.member.member, while a change to ocom.domain.src.domain.contexts.community.member.member can't break ocom.domain.src.domain.contexts.passport.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→40 ocom.domain.src.domain.contexts.community.member.member uses cellix.domain-seedwork.src.domain-seedwork.aggregate-root part of a loop✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.community.member.member uses a type in cellix.domain-seedwork.src.domain-seedwork.aggregate-root.
- The types involved
packages.ocom.domain.src.domain.contexts.community.member.member.Member→packages.cellix.domain-seedwork.src.domain-seedwork.aggregate-root.AggregateRoot
- Direction
- ocom.domain.src.domain.contexts.community.member.member uses cellix.domain-seedwork.src.domain-seedwork.aggregate-root, so a change to cellix.domain-seedwork.src.domain-seedwork.aggregate-root can break ocom.domain.src.domain.contexts.community.member.member, while a change to ocom.domain.src.domain.contexts.community.member.member can't break cellix.domain-seedwork.src.domain-seedwork.aggregate-root.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→7 ocom.domain.src.domain.contexts.property.property_passport uses ocom.domain.src.domain.contexts.property.property_visa✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.property.property_passport uses a type in ocom.domain.src.domain.contexts.property.property_visa.
- The types involved
packages.ocom.domain.src.domain.contexts.property.property_passport.PropertyPassport→packages.ocom.domain.src.domain.contexts.property.property_visa.PropertyVisa
- Direction
- ocom.domain.src.domain.contexts.property.property_passport uses ocom.domain.src.domain.contexts.property.property_visa, so a change to ocom.domain.src.domain.contexts.property.property_visa can break ocom.domain.src.domain.contexts.property.property_passport, while a change to ocom.domain.src.domain.contexts.property.property_passport can't break ocom.domain.src.domain.contexts.property.property_visa.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.property.property_passport uses a module listed above it, which is the healthy direction.
26→19 ocom.domain.src.domain.contexts.property.property_passport uses ocom.domain.src.domain.contexts.property.property.property_aggregate✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.property.property_passport uses a type in ocom.domain.src.domain.contexts.property.property.property_aggregate.
- The types involved
packages.ocom.domain.src.domain.contexts.property.property_passport.PropertyPassport→packages.ocom.domain.src.domain.contexts.property.property.property_aggregate.PropertyEntityReference
- Direction
- ocom.domain.src.domain.contexts.property.property_passport uses ocom.domain.src.domain.contexts.property.property.property_aggregate, so a change to ocom.domain.src.domain.contexts.property.property.property_aggregate can break ocom.domain.src.domain.contexts.property.property_passport, while a change to ocom.domain.src.domain.contexts.property.property_passport can't break ocom.domain.src.domain.contexts.property.property.property_aggregate.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.property.property_passport uses a module listed above it, which is the healthy direction.
27→2 ocom.domain.src.domain.contexts.user.staff-user.staff-user uses cellix.domain-seedwork.src.domain-seedwork.prop-array✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.user.staff-user.staff-user uses a type in cellix.domain-seedwork.src.domain-seedwork.prop-array.
- The types involved
packages.ocom.domain.src.domain.contexts.user.staff-user.staff-user.StaffUserProps→packages.cellix.domain-seedwork.src.domain-seedwork.prop-array.PropArray
- Direction
- ocom.domain.src.domain.contexts.user.staff-user.staff-user uses cellix.domain-seedwork.src.domain-seedwork.prop-array, so a change to cellix.domain-seedwork.src.domain-seedwork.prop-array can break ocom.domain.src.domain.contexts.user.staff-user.staff-user, while a change to ocom.domain.src.domain.contexts.user.staff-user.staff-user can't break cellix.domain-seedwork.src.domain-seedwork.prop-array.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.user.staff-user.staff-user uses a module listed above it, which is the healthy direction.
27→8 ocom.domain.src.domain.contexts.user.staff-user.staff-user uses ocom.domain.src.domain.contexts.user.user_visa✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.user.staff-user.staff-user uses a type in ocom.domain.src.domain.contexts.user.user_visa.
- The types involved
packages.ocom.domain.src.domain.contexts.user.staff-user.staff-user.StaffUser→packages.ocom.domain.src.domain.contexts.user.user_visa.UserVisa
- Direction
- ocom.domain.src.domain.contexts.user.staff-user.staff-user uses ocom.domain.src.domain.contexts.user.user_visa, so a change to ocom.domain.src.domain.contexts.user.user_visa can break ocom.domain.src.domain.contexts.user.staff-user.staff-user, while a change to ocom.domain.src.domain.contexts.user.staff-user.staff-user can't break ocom.domain.src.domain.contexts.user.user_visa.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.user.staff-user.staff-user uses a module listed above it, which is the healthy direction.
27→21 ocom.domain.src.domain.contexts.user.staff-user.staff-user uses ocom.domain.src.domain.contexts.user.staff-role.staff-role✕
- Connections
- 2 pairs of types, where a type in ocom.domain.src.domain.contexts.user.staff-user.staff-user uses a type in ocom.domain.src.domain.contexts.user.staff-role.staff-role.
- The types involved
packages.ocom.domain.src.domain.contexts.user.staff-user.staff-user.StaffUser→packages.ocom.domain.src.domain.contexts.user.staff-role.staff-role.StaffRoleEntityReferencepackages.ocom.domain.src.domain.contexts.user.staff-user.staff-user.StaffUserProps→packages.ocom.domain.src.domain.contexts.user.staff-role.staff-role.StaffRoleProps
- Direction
- ocom.domain.src.domain.contexts.user.staff-user.staff-user uses ocom.domain.src.domain.contexts.user.staff-role.staff-role, so a change to ocom.domain.src.domain.contexts.user.staff-role.staff-role can break ocom.domain.src.domain.contexts.user.staff-user.staff-user, while a change to ocom.domain.src.domain.contexts.user.staff-user.staff-user can't break ocom.domain.src.domain.contexts.user.staff-role.staff-role.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.user.staff-user.staff-user uses a module listed above it, which is the healthy direction.
27→32 ocom.domain.src.domain.contexts.user.staff-user.staff-user uses ocom.domain.src.domain.contexts.passport part of a loop✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.user.staff-user.staff-user uses a type in ocom.domain.src.domain.contexts.passport.
- The types involved
packages.ocom.domain.src.domain.contexts.user.staff-user.staff-user.StaffUser→packages.ocom.domain.src.domain.contexts.passport.Passport
- Direction
- ocom.domain.src.domain.contexts.user.staff-user.staff-user uses ocom.domain.src.domain.contexts.passport, so a change to ocom.domain.src.domain.contexts.passport can break ocom.domain.src.domain.contexts.user.staff-user.staff-user, while a change to ocom.domain.src.domain.contexts.user.staff-user.staff-user can't break ocom.domain.src.domain.contexts.passport.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→40 ocom.domain.src.domain.contexts.user.staff-user.staff-user uses cellix.domain-seedwork.src.domain-seedwork.aggregate-root part of a loop✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.user.staff-user.staff-user uses a type in cellix.domain-seedwork.src.domain-seedwork.aggregate-root.
- The types involved
packages.ocom.domain.src.domain.contexts.user.staff-user.staff-user.StaffUser→packages.cellix.domain-seedwork.src.domain-seedwork.aggregate-root.AggregateRoot
- Direction
- ocom.domain.src.domain.contexts.user.staff-user.staff-user uses cellix.domain-seedwork.src.domain-seedwork.aggregate-root, so a change to cellix.domain-seedwork.src.domain-seedwork.aggregate-root can break ocom.domain.src.domain.contexts.user.staff-user.staff-user, while a change to ocom.domain.src.domain.contexts.user.staff-user.staff-user can't break cellix.domain-seedwork.src.domain-seedwork.aggregate-root.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→2 ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate uses cellix.domain-seedwork.src.domain-seedwork.prop-array✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate uses a type in cellix.domain-seedwork.src.domain-seedwork.prop-array.
- The types involved
packages.ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate.ServiceTicketV1Props→packages.cellix.domain-seedwork.src.domain-seedwork.prop-array.PropArray
- Direction
- ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate uses cellix.domain-seedwork.src.domain-seedwork.prop-array, so a change to cellix.domain-seedwork.src.domain-seedwork.prop-array can break ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate, while a change to ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate can't break cellix.domain-seedwork.src.domain-seedwork.prop-array.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate uses a module listed above it, which is the healthy direction.
28→6 ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate uses ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate uses a type in ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.
- The types involved
packages.ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate.ServiceTicketV1→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.Description
- Direction
- ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate uses ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects, so a change to ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects can break ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate, while a change to ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate can't break ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate uses a module listed above it, which is the healthy direction.
28→25 ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate uses ocom.domain.src.domain.contexts.community.member.member✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate uses a type in ocom.domain.src.domain.contexts.community.member.member.
- The types involved
packages.ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate.ServiceTicketV1→packages.ocom.domain.src.domain.contexts.community.member.member.MemberEntityReference
- Direction
- ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate uses ocom.domain.src.domain.contexts.community.member.member, so a change to ocom.domain.src.domain.contexts.community.member.member can break ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate, while a change to ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate can't break ocom.domain.src.domain.contexts.community.member.member.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate uses a module listed above it, which is the healthy direction.
28→32 ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate uses ocom.domain.src.domain.contexts.passport part of a loop✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate uses a type in ocom.domain.src.domain.contexts.passport.
- The types involved
packages.ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate.ServiceTicketV1→packages.ocom.domain.src.domain.contexts.passport.Passport
- Direction
- ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate uses ocom.domain.src.domain.contexts.passport, so a change to ocom.domain.src.domain.contexts.passport can break ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate, while a change to ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate can't break ocom.domain.src.domain.contexts.passport.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→40 ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate uses cellix.domain-seedwork.src.domain-seedwork.aggregate-root part of a loop✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate uses a type in cellix.domain-seedwork.src.domain-seedwork.aggregate-root.
- The types involved
packages.ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate.ServiceTicketV1→packages.cellix.domain-seedwork.src.domain-seedwork.aggregate-root.AggregateRoot
- Direction
- ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate uses cellix.domain-seedwork.src.domain-seedwork.aggregate-root, so a change to cellix.domain-seedwork.src.domain-seedwork.aggregate-root can break ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate, while a change to ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate can't break cellix.domain-seedwork.src.domain-seedwork.aggregate-root.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→2 ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate uses cellix.domain-seedwork.src.domain-seedwork.prop-array✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate uses a type in cellix.domain-seedwork.src.domain-seedwork.prop-array.
- The types involved
packages.ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate.ViolationTicketV1Props→packages.cellix.domain-seedwork.src.domain-seedwork.prop-array.PropArray
- Direction
- ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate uses cellix.domain-seedwork.src.domain-seedwork.prop-array, so a change to cellix.domain-seedwork.src.domain-seedwork.prop-array can break ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate, while a change to ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate can't break cellix.domain-seedwork.src.domain-seedwork.prop-array.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate uses a module listed above it, which is the healthy direction.
29→4 ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate uses ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_visa✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate uses a type in ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_visa.
- The types involved
packages.ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate.ViolationTicketV1→packages.ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_visa.ViolationTicketV1Visa
- Direction
- ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate uses ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_visa, so a change to ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_visa can break ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate, while a change to ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate can't break ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_visa.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate uses a module listed above it, which is the healthy direction.
29→25 ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate uses ocom.domain.src.domain.contexts.community.member.member✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate uses a type in ocom.domain.src.domain.contexts.community.member.member.
- The types involved
packages.ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate.ViolationTicketV1→packages.ocom.domain.src.domain.contexts.community.member.member.MemberEntityReference
- Direction
- ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate uses ocom.domain.src.domain.contexts.community.member.member, so a change to ocom.domain.src.domain.contexts.community.member.member can break ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate, while a change to ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate can't break ocom.domain.src.domain.contexts.community.member.member.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate uses a module listed above it, which is the healthy direction.
29→32 ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate uses ocom.domain.src.domain.contexts.passport part of a loop✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate uses a type in ocom.domain.src.domain.contexts.passport.
- The types involved
packages.ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate.ViolationTicketV1→packages.ocom.domain.src.domain.contexts.passport.Passport
- Direction
- ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate uses ocom.domain.src.domain.contexts.passport, so a change to ocom.domain.src.domain.contexts.passport can break ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate, while a change to ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate can't break ocom.domain.src.domain.contexts.passport.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→40 ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate uses cellix.domain-seedwork.src.domain-seedwork.aggregate-root part of a loop✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate uses a type in cellix.domain-seedwork.src.domain-seedwork.aggregate-root.
- The types involved
packages.ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate.ViolationTicketV1→packages.cellix.domain-seedwork.src.domain-seedwork.aggregate-root.AggregateRoot
- Direction
- ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate uses cellix.domain-seedwork.src.domain-seedwork.aggregate-root, so a change to cellix.domain-seedwork.src.domain-seedwork.aggregate-root can break ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate, while a change to ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate can't break cellix.domain-seedwork.src.domain-seedwork.aggregate-root.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→8 ocom.domain.src.domain.contexts.user.user_passport uses ocom.domain.src.domain.contexts.user.user_visa✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.user.user_passport uses a type in ocom.domain.src.domain.contexts.user.user_visa.
- The types involved
packages.ocom.domain.src.domain.contexts.user.user_passport.UserPassport→packages.ocom.domain.src.domain.contexts.user.user_visa.UserVisa
- Direction
- ocom.domain.src.domain.contexts.user.user_passport uses ocom.domain.src.domain.contexts.user.user_visa, so a change to ocom.domain.src.domain.contexts.user.user_visa can break ocom.domain.src.domain.contexts.user.user_passport, while a change to ocom.domain.src.domain.contexts.user.user_passport can't break ocom.domain.src.domain.contexts.user.user_visa.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.user.user_passport uses a module listed above it, which is the healthy direction.
30→11 ocom.domain.src.domain.contexts.user.user_passport uses ocom.domain.src.domain.contexts.user.vendor-user.vendor-user✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.user.user_passport uses a type in ocom.domain.src.domain.contexts.user.vendor-user.vendor-user.
- The types involved
packages.ocom.domain.src.domain.contexts.user.user_passport.UserPassport→packages.ocom.domain.src.domain.contexts.user.vendor-user.vendor-user.VendorUserEntityReference
- Direction
- ocom.domain.src.domain.contexts.user.user_passport uses ocom.domain.src.domain.contexts.user.vendor-user.vendor-user, so a change to ocom.domain.src.domain.contexts.user.vendor-user.vendor-user can break ocom.domain.src.domain.contexts.user.user_passport, while a change to ocom.domain.src.domain.contexts.user.user_passport can't break ocom.domain.src.domain.contexts.user.vendor-user.vendor-user.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.user.user_passport uses a module listed above it, which is the healthy direction.
30→21 ocom.domain.src.domain.contexts.user.user_passport uses ocom.domain.src.domain.contexts.user.staff-role.staff-role✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.user.user_passport uses a type in ocom.domain.src.domain.contexts.user.staff-role.staff-role.
- The types involved
packages.ocom.domain.src.domain.contexts.user.user_passport.UserPassport→packages.ocom.domain.src.domain.contexts.user.staff-role.staff-role.StaffRoleEntityReference
- Direction
- ocom.domain.src.domain.contexts.user.user_passport uses ocom.domain.src.domain.contexts.user.staff-role.staff-role, so a change to ocom.domain.src.domain.contexts.user.staff-role.staff-role can break ocom.domain.src.domain.contexts.user.user_passport, while a change to ocom.domain.src.domain.contexts.user.user_passport can't break ocom.domain.src.domain.contexts.user.staff-role.staff-role.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.user.user_passport uses a module listed above it, which is the healthy direction.
30→27 ocom.domain.src.domain.contexts.user.user_passport uses ocom.domain.src.domain.contexts.user.staff-user.staff-user✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.user.user_passport uses a type in ocom.domain.src.domain.contexts.user.staff-user.staff-user.
- The types involved
packages.ocom.domain.src.domain.contexts.user.user_passport.UserPassport→packages.ocom.domain.src.domain.contexts.user.staff-user.staff-user.StaffUserEntityReference
- Direction
- ocom.domain.src.domain.contexts.user.user_passport uses ocom.domain.src.domain.contexts.user.staff-user.staff-user, so a change to ocom.domain.src.domain.contexts.user.staff-user.staff-user can break ocom.domain.src.domain.contexts.user.user_passport, while a change to ocom.domain.src.domain.contexts.user.user_passport can't break ocom.domain.src.domain.contexts.user.staff-user.staff-user.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.user.user_passport uses a module listed above it, which is the healthy direction.
30→33 ocom.domain.src.domain.contexts.user.user_passport uses ocom.domain.src.domain.contexts.user.end-user.end-user part of a loop✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.user.user_passport uses a type in ocom.domain.src.domain.contexts.user.end-user.end-user.
- The types involved
packages.ocom.domain.src.domain.contexts.user.user_passport.UserPassport→packages.ocom.domain.src.domain.contexts.user.end-user.end-user.EndUserEntityReference
- Direction
- ocom.domain.src.domain.contexts.user.user_passport uses ocom.domain.src.domain.contexts.user.end-user.end-user, so a change to ocom.domain.src.domain.contexts.user.end-user.end-user can break ocom.domain.src.domain.contexts.user.user_passport, while a change to ocom.domain.src.domain.contexts.user.user_passport can't break ocom.domain.src.domain.contexts.user.end-user.end-user.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→28 ocom.domain.src.domain.contexts.case.case_passport uses ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.case.case_passport uses a type in ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate.
- The types involved
packages.ocom.domain.src.domain.contexts.case.case_passport.CasePassport→packages.ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate.ServiceTicketV1EntityReference
- Direction
- ocom.domain.src.domain.contexts.case.case_passport uses ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate, so a change to ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate can break ocom.domain.src.domain.contexts.case.case_passport, while a change to ocom.domain.src.domain.contexts.case.case_passport can't break ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.case.case_passport uses a module listed above it, which is the healthy direction.
31→29 ocom.domain.src.domain.contexts.case.case_passport uses ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.case.case_passport uses a type in ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate.
- The types involved
packages.ocom.domain.src.domain.contexts.case.case_passport.CasePassport→packages.ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate.ViolationTicketV1EntityReference
- Direction
- ocom.domain.src.domain.contexts.case.case_passport uses ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate, so a change to ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate can break ocom.domain.src.domain.contexts.case.case_passport, while a change to ocom.domain.src.domain.contexts.case.case_passport can't break ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.case.case_passport uses a module listed above it, which is the healthy direction.
32→12 ocom.domain.src.domain.contexts.passport uses ocom.domain.src.domain.contexts.community.community_passport✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.passport uses a type in ocom.domain.src.domain.contexts.community.community_passport.
- The types involved
packages.ocom.domain.src.domain.contexts.passport.Passport→packages.ocom.domain.src.domain.contexts.community.community_passport.CommunityPassport
- Direction
- ocom.domain.src.domain.contexts.passport uses ocom.domain.src.domain.contexts.community.community_passport, so a change to ocom.domain.src.domain.contexts.community.community_passport can break ocom.domain.src.domain.contexts.passport, while a change to ocom.domain.src.domain.contexts.passport can't break ocom.domain.src.domain.contexts.community.community_passport.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.passport uses a module listed above it, which is the healthy direction.
32→20 ocom.domain.src.domain.contexts.passport uses ocom.domain.src.domain.contexts.service.service_passport✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.passport uses a type in ocom.domain.src.domain.contexts.service.service_passport.
- The types involved
packages.ocom.domain.src.domain.contexts.passport.Passport→packages.ocom.domain.src.domain.contexts.service.service_passport.ServicePassport
- Direction
- ocom.domain.src.domain.contexts.passport uses ocom.domain.src.domain.contexts.service.service_passport, so a change to ocom.domain.src.domain.contexts.service.service_passport can break ocom.domain.src.domain.contexts.passport, while a change to ocom.domain.src.domain.contexts.passport can't break ocom.domain.src.domain.contexts.service.service_passport.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.passport uses a module listed above it, which is the healthy direction.
32→26 ocom.domain.src.domain.contexts.passport uses ocom.domain.src.domain.contexts.property.property_passport✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.passport uses a type in ocom.domain.src.domain.contexts.property.property_passport.
- The types involved
packages.ocom.domain.src.domain.contexts.passport.Passport→packages.ocom.domain.src.domain.contexts.property.property_passport.PropertyPassport
- Direction
- ocom.domain.src.domain.contexts.passport uses ocom.domain.src.domain.contexts.property.property_passport, so a change to ocom.domain.src.domain.contexts.property.property_passport can break ocom.domain.src.domain.contexts.passport, while a change to ocom.domain.src.domain.contexts.passport can't break ocom.domain.src.domain.contexts.property.property_passport.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.passport uses a module listed above it, which is the healthy direction.
32→30 ocom.domain.src.domain.contexts.passport uses ocom.domain.src.domain.contexts.user.user_passport✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.passport uses a type in ocom.domain.src.domain.contexts.user.user_passport.
- The types involved
packages.ocom.domain.src.domain.contexts.passport.Passport→packages.ocom.domain.src.domain.contexts.user.user_passport.UserPassport
- Direction
- ocom.domain.src.domain.contexts.passport uses ocom.domain.src.domain.contexts.user.user_passport, so a change to ocom.domain.src.domain.contexts.user.user_passport can break ocom.domain.src.domain.contexts.passport, while a change to ocom.domain.src.domain.contexts.passport can't break ocom.domain.src.domain.contexts.user.user_passport.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.passport uses a module listed above it, which is the healthy direction.
32→31 ocom.domain.src.domain.contexts.passport uses ocom.domain.src.domain.contexts.case.case_passport✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.passport uses a type in ocom.domain.src.domain.contexts.case.case_passport.
- The types involved
packages.ocom.domain.src.domain.contexts.passport.Passport→packages.ocom.domain.src.domain.contexts.case.case_passport.CasePassport
- Direction
- ocom.domain.src.domain.contexts.passport uses ocom.domain.src.domain.contexts.case.case_passport, so a change to ocom.domain.src.domain.contexts.case.case_passport can break ocom.domain.src.domain.contexts.passport, while a change to ocom.domain.src.domain.contexts.passport can't break ocom.domain.src.domain.contexts.case.case_passport.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.passport uses a module listed above it, which is the healthy direction.
33→8 ocom.domain.src.domain.contexts.user.end-user.end-user uses ocom.domain.src.domain.contexts.user.user_visa✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.user.end-user.end-user uses a type in ocom.domain.src.domain.contexts.user.user_visa.
- The types involved
packages.ocom.domain.src.domain.contexts.user.end-user.end-user.EndUser→packages.ocom.domain.src.domain.contexts.user.user_visa.UserVisa
- Direction
- ocom.domain.src.domain.contexts.user.end-user.end-user uses ocom.domain.src.domain.contexts.user.user_visa, so a change to ocom.domain.src.domain.contexts.user.user_visa can break ocom.domain.src.domain.contexts.user.end-user.end-user, while a change to ocom.domain.src.domain.contexts.user.end-user.end-user can't break ocom.domain.src.domain.contexts.user.user_visa.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.user.end-user.end-user uses a module listed above it, which is the healthy direction.
33→32 ocom.domain.src.domain.contexts.user.end-user.end-user uses ocom.domain.src.domain.contexts.passport✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.user.end-user.end-user uses a type in ocom.domain.src.domain.contexts.passport.
- The types involved
packages.ocom.domain.src.domain.contexts.user.end-user.end-user.EndUser→packages.ocom.domain.src.domain.contexts.passport.Passport
- Direction
- ocom.domain.src.domain.contexts.user.end-user.end-user uses ocom.domain.src.domain.contexts.passport, so a change to ocom.domain.src.domain.contexts.passport can break ocom.domain.src.domain.contexts.user.end-user.end-user, while a change to ocom.domain.src.domain.contexts.user.end-user.end-user can't break ocom.domain.src.domain.contexts.passport.
- Position
- Below the diagonal: ocom.domain.src.domain.contexts.user.end-user.end-user uses a module listed above it, which is the healthy direction.
33→40 ocom.domain.src.domain.contexts.user.end-user.end-user uses cellix.domain-seedwork.src.domain-seedwork.aggregate-root part of a loop✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.contexts.user.end-user.end-user uses a type in cellix.domain-seedwork.src.domain-seedwork.aggregate-root.
- The types involved
packages.ocom.domain.src.domain.contexts.user.end-user.end-user.EndUser→packages.cellix.domain-seedwork.src.domain-seedwork.aggregate-root.AggregateRoot
- Direction
- ocom.domain.src.domain.contexts.user.end-user.end-user uses cellix.domain-seedwork.src.domain-seedwork.aggregate-root, so a change to cellix.domain-seedwork.src.domain-seedwork.aggregate-root can break ocom.domain.src.domain.contexts.user.end-user.end-user, while a change to ocom.domain.src.domain.contexts.user.end-user.end-user can't break cellix.domain-seedwork.src.domain-seedwork.aggregate-root.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→25 ocom.application-services.src.contexts.community.member uses ocom.domain.src.domain.contexts.community.member.member✕
- Connections
- 2 pairs of types, where a type in ocom.application-services.src.contexts.community.member uses a type in ocom.domain.src.domain.contexts.community.member.member.
- The types involved
packages.ocom.application-services.src.contexts.community.member.member-management→packages.ocom.domain.src.domain.contexts.community.member.member.MemberEntityReferencepackages.ocom.application-services.src.contexts.community.member.query-by-id→packages.ocom.domain.src.domain.contexts.community.member.member.MemberEntityReference
- Direction
- ocom.application-services.src.contexts.community.member uses ocom.domain.src.domain.contexts.community.member.member, so a change to ocom.domain.src.domain.contexts.community.member.member can break ocom.application-services.src.contexts.community.member, while a change to ocom.application-services.src.contexts.community.member can't break ocom.domain.src.domain.contexts.community.member.member.
- Position
- Below the diagonal: ocom.application-services.src.contexts.community.member uses a module listed above it, which is the healthy direction.
34→33 ocom.application-services.src.contexts.community.member uses ocom.domain.src.domain.contexts.user.end-user.end-user✕
- Connections
- 1 pair of types, where a type in ocom.application-services.src.contexts.community.member uses a type in ocom.domain.src.domain.contexts.user.end-user.end-user.
- The types involved
packages.ocom.application-services.src.contexts.community.member.member-management→packages.ocom.domain.src.domain.contexts.user.end-user.end-user.EndUserEntityReference
- Direction
- ocom.application-services.src.contexts.community.member uses ocom.domain.src.domain.contexts.user.end-user.end-user, so a change to ocom.domain.src.domain.contexts.user.end-user.end-user can break ocom.application-services.src.contexts.community.member, while a change to ocom.application-services.src.contexts.community.member can't break ocom.domain.src.domain.contexts.user.end-user.end-user.
- Position
- Below the diagonal: ocom.application-services.src.contexts.community.member uses a module listed above it, which is the healthy direction.
35→10 ocom.domain.src.domain.iam.member.member_passport-base uses ocom.domain.src.domain.contexts.community.community.community✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.iam.member.member_passport-base uses a type in ocom.domain.src.domain.contexts.community.community.community.
- The types involved
packages.ocom.domain.src.domain.iam.member.member_passport-base.MemberPassportBase→packages.ocom.domain.src.domain.contexts.community.community.community.CommunityEntityReference
- Direction
- ocom.domain.src.domain.iam.member.member_passport-base uses ocom.domain.src.domain.contexts.community.community.community, so a change to ocom.domain.src.domain.contexts.community.community.community can break ocom.domain.src.domain.iam.member.member_passport-base, while a change to ocom.domain.src.domain.iam.member.member_passport-base can't break ocom.domain.src.domain.contexts.community.community.community.
- Position
- Below the diagonal: ocom.domain.src.domain.iam.member.member_passport-base uses a module listed above it, which is the healthy direction.
35→25 ocom.domain.src.domain.iam.member.member_passport-base uses ocom.domain.src.domain.contexts.community.member.member✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.iam.member.member_passport-base uses a type in ocom.domain.src.domain.contexts.community.member.member.
- The types involved
packages.ocom.domain.src.domain.iam.member.member_passport-base.MemberPassportBase→packages.ocom.domain.src.domain.contexts.community.member.member.MemberEntityReference
- Direction
- ocom.domain.src.domain.iam.member.member_passport-base uses ocom.domain.src.domain.contexts.community.member.member, so a change to ocom.domain.src.domain.contexts.community.member.member can break ocom.domain.src.domain.iam.member.member_passport-base, while a change to ocom.domain.src.domain.iam.member.member_passport-base can't break ocom.domain.src.domain.contexts.community.member.member.
- Position
- Below the diagonal: ocom.domain.src.domain.iam.member.member_passport-base uses a module listed above it, which is the healthy direction.
35→33 ocom.domain.src.domain.iam.member.member_passport-base uses ocom.domain.src.domain.contexts.user.end-user.end-user✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.iam.member.member_passport-base uses a type in ocom.domain.src.domain.contexts.user.end-user.end-user.
- The types involved
packages.ocom.domain.src.domain.iam.member.member_passport-base.MemberPassportBase→packages.ocom.domain.src.domain.contexts.user.end-user.end-user.EndUserEntityReference
- Direction
- ocom.domain.src.domain.iam.member.member_passport-base uses ocom.domain.src.domain.contexts.user.end-user.end-user, so a change to ocom.domain.src.domain.contexts.user.end-user.end-user can break ocom.domain.src.domain.iam.member.member_passport-base, while a change to ocom.domain.src.domain.iam.member.member_passport-base can't break ocom.domain.src.domain.contexts.user.end-user.end-user.
- Position
- Below the diagonal: ocom.domain.src.domain.iam.member.member_passport-base uses a module listed above it, which is the healthy direction.
36→8 ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses ocom.domain.src.domain.contexts.user.user_visa✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses a type in ocom.domain.src.domain.contexts.user.user_visa.
- The types involved
packages.ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport.StaffUserUserPassport→packages.ocom.domain.src.domain.contexts.user.user_visa.UserVisa
- Direction
- ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses ocom.domain.src.domain.contexts.user.user_visa, so a change to ocom.domain.src.domain.contexts.user.user_visa can break ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport, while a change to ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport can't break ocom.domain.src.domain.contexts.user.user_visa.
- Position
- Below the diagonal: ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses a module listed above it, which is the healthy direction.
36→11 ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses ocom.domain.src.domain.contexts.user.vendor-user.vendor-user✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses a type in ocom.domain.src.domain.contexts.user.vendor-user.vendor-user.
- The types involved
packages.ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport.StaffUserUserPassport→packages.ocom.domain.src.domain.contexts.user.vendor-user.vendor-user.VendorUserEntityReference
- Direction
- ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses ocom.domain.src.domain.contexts.user.vendor-user.vendor-user, so a change to ocom.domain.src.domain.contexts.user.vendor-user.vendor-user can break ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport, while a change to ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport can't break ocom.domain.src.domain.contexts.user.vendor-user.vendor-user.
- Position
- Below the diagonal: ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses a module listed above it, which is the healthy direction.
36→21 ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses ocom.domain.src.domain.contexts.user.staff-role.staff-role✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses a type in ocom.domain.src.domain.contexts.user.staff-role.staff-role.
- The types involved
packages.ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport.StaffUserUserPassport→packages.ocom.domain.src.domain.contexts.user.staff-role.staff-role.StaffRoleEntityReference
- Direction
- ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses ocom.domain.src.domain.contexts.user.staff-role.staff-role, so a change to ocom.domain.src.domain.contexts.user.staff-role.staff-role can break ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport, while a change to ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport can't break ocom.domain.src.domain.contexts.user.staff-role.staff-role.
- Position
- Below the diagonal: ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses a module listed above it, which is the healthy direction.
36→27 ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses ocom.domain.src.domain.contexts.user.staff-user.staff-user✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses a type in ocom.domain.src.domain.contexts.user.staff-user.staff-user.
- The types involved
packages.ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport.StaffUserUserPassport→packages.ocom.domain.src.domain.contexts.user.staff-user.staff-user.StaffUserEntityReference
- Direction
- ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses ocom.domain.src.domain.contexts.user.staff-user.staff-user, so a change to ocom.domain.src.domain.contexts.user.staff-user.staff-user can break ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport, while a change to ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport can't break ocom.domain.src.domain.contexts.user.staff-user.staff-user.
- Position
- Below the diagonal: ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses a module listed above it, which is the healthy direction.
36→30 ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses ocom.domain.src.domain.contexts.user.user_passport✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses a type in ocom.domain.src.domain.contexts.user.user_passport.
- The types involved
packages.ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport.StaffUserUserPassport→packages.ocom.domain.src.domain.contexts.user.user_passport.UserPassport
- Direction
- ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses ocom.domain.src.domain.contexts.user.user_passport, so a change to ocom.domain.src.domain.contexts.user.user_passport can break ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport, while a change to ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport can't break ocom.domain.src.domain.contexts.user.user_passport.
- Position
- Below the diagonal: ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses a module listed above it, which is the healthy direction.
36→33 ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses ocom.domain.src.domain.contexts.user.end-user.end-user✕
- Connections
- 1 pair of types, where a type in ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses a type in ocom.domain.src.domain.contexts.user.end-user.end-user.
- The types involved
packages.ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport.StaffUserUserPassport→packages.ocom.domain.src.domain.contexts.user.end-user.end-user.EndUserEntityReference
- Direction
- ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses ocom.domain.src.domain.contexts.user.end-user.end-user, so a change to ocom.domain.src.domain.contexts.user.end-user.end-user can break ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport, while a change to ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport can't break ocom.domain.src.domain.contexts.user.end-user.end-user.
- Position
- Below the diagonal: ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport uses a module listed above it, which is the healthy direction.
37→33 ocom.persistence.src.datasources.domain.community.community.community_repository uses ocom.domain.src.domain.contexts.user.end-user.end-user✕
- Connections
- 1 pair of types, where a type in ocom.persistence.src.datasources.domain.community.community.community_repository uses a type in ocom.domain.src.domain.contexts.user.end-user.end-user.
- The types involved
packages.ocom.persistence.src.datasources.domain.community.community.community_repository.CommunityRepository→packages.ocom.domain.src.domain.contexts.user.end-user.end-user.EndUserEntityReference
- Direction
- ocom.persistence.src.datasources.domain.community.community.community_repository uses ocom.domain.src.domain.contexts.user.end-user.end-user, so a change to ocom.domain.src.domain.contexts.user.end-user.end-user can break ocom.persistence.src.datasources.domain.community.community.community_repository, while a change to ocom.persistence.src.datasources.domain.community.community.community_repository can't break ocom.domain.src.domain.contexts.user.end-user.end-user.
- Position
- Below the diagonal: ocom.persistence.src.datasources.domain.community.community.community_repository uses a module listed above it, which is the healthy direction.
38→37 cellix.domain-seedwork.src.domain-seedwork.domain-entity uses ocom.persistence.src.datasources.domain.community.community.community_repository✕
- Connections
- 1 pair of types, where a type in cellix.domain-seedwork.src.domain-seedwork.domain-entity uses a type in ocom.persistence.src.datasources.domain.community.community.community_repository.
- The types involved
packages.cellix.domain-seedwork.src.domain-seedwork.domain-entity.DomainEntity→packages.ocom.persistence.src.datasources.domain.community.community.community_repository.PropType
- Direction
- cellix.domain-seedwork.src.domain-seedwork.domain-entity uses ocom.persistence.src.datasources.domain.community.community.community_repository, so a change to ocom.persistence.src.datasources.domain.community.community.community_repository can break cellix.domain-seedwork.src.domain-seedwork.domain-entity, while a change to cellix.domain-seedwork.src.domain-seedwork.domain-entity can't break ocom.persistence.src.datasources.domain.community.community.community_repository.
- Position
- Below the diagonal: cellix.domain-seedwork.src.domain-seedwork.domain-entity uses a module listed above it, which is the healthy direction.
39→6 ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects✕
- Connections
- 1 pair of types, where a type in ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses a type in ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.
- The types involved
packages.ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository.ServiceTicketV1Repository→packages.ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.Description
- Direction
- ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects, so a change to ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects can break ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository, while a change to ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository can't break ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects.
- Position
- Below the diagonal: ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses a module listed above it, which is the healthy direction.
39→10 ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses ocom.domain.src.domain.contexts.community.community.community✕
- Connections
- 1 pair of types, where a type in ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses a type in ocom.domain.src.domain.contexts.community.community.community.
- The types involved
packages.ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository.ServiceTicketV1Repository→packages.ocom.domain.src.domain.contexts.community.community.community.CommunityEntityReference
- Direction
- ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses ocom.domain.src.domain.contexts.community.community.community, so a change to ocom.domain.src.domain.contexts.community.community.community can break ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository, while a change to ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository can't break ocom.domain.src.domain.contexts.community.community.community.
- Position
- Below the diagonal: ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses a module listed above it, which is the healthy direction.
39→19 ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses ocom.domain.src.domain.contexts.property.property.property_aggregate✕
- Connections
- 1 pair of types, where a type in ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses a type in ocom.domain.src.domain.contexts.property.property.property_aggregate.
- The types involved
packages.ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository.ServiceTicketV1Repository→packages.ocom.domain.src.domain.contexts.property.property.property_aggregate.PropertyEntityReference
- Direction
- ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses ocom.domain.src.domain.contexts.property.property.property_aggregate, so a change to ocom.domain.src.domain.contexts.property.property.property_aggregate can break ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository, while a change to ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository can't break ocom.domain.src.domain.contexts.property.property.property_aggregate.
- Position
- Below the diagonal: ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses a module listed above it, which is the healthy direction.
39→25 ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses ocom.domain.src.domain.contexts.community.member.member✕
- Connections
- 1 pair of types, where a type in ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses a type in ocom.domain.src.domain.contexts.community.member.member.
- The types involved
packages.ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository.ServiceTicketV1Repository→packages.ocom.domain.src.domain.contexts.community.member.member.MemberEntityReference
- Direction
- ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses ocom.domain.src.domain.contexts.community.member.member, so a change to ocom.domain.src.domain.contexts.community.member.member can break ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository, while a change to ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository can't break ocom.domain.src.domain.contexts.community.member.member.
- Position
- Below the diagonal: ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses a module listed above it, which is the healthy direction.
39→28 ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate✕
- Connections
- 1 pair of types, where a type in ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses a type in ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate.
- The types involved
packages.ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository.ServiceTicketV1Repository→packages.ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate.ServiceTicketV1
- Direction
- ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate, so a change to ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate can break ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository, while a change to ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository can't break ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate.
- Position
- Below the diagonal: ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses a module listed above it, which is the healthy direction.
39→37 ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses ocom.persistence.src.datasources.domain.community.community.community_repository✕
- Connections
- 1 pair of types, where a type in ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses a type in ocom.persistence.src.datasources.domain.community.community.community_repository.
- The types involved
packages.ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository.ServiceTicketV1Repository→packages.ocom.persistence.src.datasources.domain.community.community.community_repository.PropType
- Direction
- ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses ocom.persistence.src.datasources.domain.community.community.community_repository, so a change to ocom.persistence.src.datasources.domain.community.community.community_repository can break ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository, while a change to ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository can't break ocom.persistence.src.datasources.domain.community.community.community_repository.
- Position
- Below the diagonal: ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository uses a module listed above it, which is the healthy direction.
40→1 cellix.domain-seedwork.src.domain-seedwork.aggregate-root uses cellix.domain-seedwork.src.domain-seedwork.domain-event✕
- Connections
- 1 pair of types, where a type in cellix.domain-seedwork.src.domain-seedwork.aggregate-root uses a type in cellix.domain-seedwork.src.domain-seedwork.domain-event.
- The types involved
packages.cellix.domain-seedwork.src.domain-seedwork.aggregate-root.AggregateRoot→packages.cellix.domain-seedwork.src.domain-seedwork.domain-event.CustomDomainEvent
- Direction
- cellix.domain-seedwork.src.domain-seedwork.aggregate-root uses cellix.domain-seedwork.src.domain-seedwork.domain-event, so a change to cellix.domain-seedwork.src.domain-seedwork.domain-event can break cellix.domain-seedwork.src.domain-seedwork.aggregate-root, while a change to cellix.domain-seedwork.src.domain-seedwork.aggregate-root can't break cellix.domain-seedwork.src.domain-seedwork.domain-event.
- Position
- Below the diagonal: cellix.domain-seedwork.src.domain-seedwork.aggregate-root uses a module listed above it, which is the healthy direction.
40→37 cellix.domain-seedwork.src.domain-seedwork.aggregate-root uses ocom.persistence.src.datasources.domain.community.community.community_repository✕
- Connections
- 1 pair of types, where a type in cellix.domain-seedwork.src.domain-seedwork.aggregate-root uses a type in ocom.persistence.src.datasources.domain.community.community.community_repository.
- The types involved
packages.cellix.domain-seedwork.src.domain-seedwork.aggregate-root.AggregateRoot→packages.ocom.persistence.src.datasources.domain.community.community.community_repository.PropType
- Direction
- cellix.domain-seedwork.src.domain-seedwork.aggregate-root uses ocom.persistence.src.datasources.domain.community.community.community_repository, so a change to ocom.persistence.src.datasources.domain.community.community.community_repository can break cellix.domain-seedwork.src.domain-seedwork.aggregate-root, while a change to cellix.domain-seedwork.src.domain-seedwork.aggregate-root can't break ocom.persistence.src.datasources.domain.community.community.community_repository.
- Position
- Below the diagonal: cellix.domain-seedwork.src.domain-seedwork.aggregate-root uses a module listed above it, which is the healthy direction.
40→38 cellix.domain-seedwork.src.domain-seedwork.aggregate-root uses cellix.domain-seedwork.src.domain-seedwork.domain-entity✕
- Connections
- 1 pair of types, where a type in cellix.domain-seedwork.src.domain-seedwork.aggregate-root uses a type in cellix.domain-seedwork.src.domain-seedwork.domain-entity.
- The types involved
packages.cellix.domain-seedwork.src.domain-seedwork.aggregate-root.AggregateRoot→packages.cellix.domain-seedwork.src.domain-seedwork.domain-entity.DomainEntity
- Direction
- cellix.domain-seedwork.src.domain-seedwork.aggregate-root uses cellix.domain-seedwork.src.domain-seedwork.domain-entity, so a change to cellix.domain-seedwork.src.domain-seedwork.domain-entity can break cellix.domain-seedwork.src.domain-seedwork.aggregate-root, while a change to cellix.domain-seedwork.src.domain-seedwork.aggregate-root can't break cellix.domain-seedwork.src.domain-seedwork.domain-entity.
- Position
- Below the diagonal: cellix.domain-seedwork.src.domain-seedwork.aggregate-root uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 56 | High / Critical |
| A05:2025 — Injection | 25 | High / Critical |
| A02:2025 — Security Misconfiguration | 11 | Medium |
| A07:2025 — Authentication Failures | 1 | High / Critical |
Roadmap
Top priorities: Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED; Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies; Resolve the 7 No assertions (empty test) finding(s) in Test Quality — start with mongo-unit-of-work.integration.test.ts (7).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. | +2.5 pts | Low | Secret Scanning |
| Resolve the 7 No assertions (empty test) finding(s) in Test Quality — start with mongo-unit-of-work.integration.test.ts (7). | +2.1 pts | Low | Test Quality |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +2.4 pts | Medium | Dependency Hygiene |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +1.8 pts | Medium | Forms & labels |
| 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 run the Storybook a11y addon's checks as tests (@storybook/test-runner or @storybook/addon-vitest, with `parameters.a11y.test: 'error'` in .storybook/preview), then run that in CI. | +1.6 pts | Medium | A11y enforcement |
| Enable Dependabot/Renovate or a dependency-review gate. | +1.6 pts | Medium | Security & performance tooling |
| Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery). | +1.6 pts | Medium | DR & Backup |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +1.5 pts | Medium | Page structure |
File quality
| 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.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| packages/cellix/mongoose-seedwork/tests/integration/mongo-unit-of-work.integration.test.ts | 6.0 | Mixed | Test Quality: No assertions (empty test): Then the integration event should be dispatched by integrationEventBus after the transaction commits |
| REDACTED | 6.1 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.3 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| packages/ocom/persistence/src/datasources/domain/case/service-ticket-v1/service-ticket-v1.domain-adapter.ts | 6.6 | Mixed | Explicit Debt: TodoComment |
| packages/cellix/event-bus-seedwork-node/src/node-event-bus.ts | 6.6 | Mixed | Explicit Debt: HackComment |
| REDACTED | 6.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| packages/ocom/application-services/src/contexts/community/member/member-management.ts | 7.0 | Mixed | Cyclomatic Complexity: member-management.updateMemberProfile.<returned closure> (cyclomatic 22) |
| REDACTED | 7.2 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| build-pipeline/scripts/detect-changes.cjs | 7.3 | Mixed | Cyclomatic Complexity: detect-changes.detectChanges (cyclomatic 20) |
| packages/ocom/ui-staff-shared/src/section-layout.tsx | 7.4 | Mixed | Cyclomatic Complexity: section-layout.SectionLayout (cyclomatic 40) |
| packages/ocom/ui-community-route-admin/src/components/members-list.container.tsx | 7.4 | Mixed | Cyclomatic Complexity: members-list.container.MemberListContainer (cyclomatic 37) |
| apps/ui-staff/src/contexts/theme-context.tsx | 7.4 | Mixed | Cyclomatic Complexity: theme-context.ThemeProvider (cyclomatic 34) |
| packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts | 7.4 | Mixed | Cyclomatic Complexity: file-user-store.createFileUserStore.validateEntries (cyclomatic 25) |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
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
This survey 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. All 92 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 92 dimensions across the health lenses
- 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, 639 of 660 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, 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.
Tools & methods
| 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 |
| Canine Code Analyzer 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 |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for the repository root failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for the repository root failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in the repository root was NOT MEASURED: the dependency install for the repository root failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in apps/api/ was NOT MEASURED: the dependency install for apps/api/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in apps/docs/ was NOT MEASURED: the dependency install for apps/docs/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in apps/server-oauth2-mock/ was NOT MEASURED: the dependency install for apps/server-oauth2-mock/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in apps/ui-community/ was NOT MEASURED: the dependency install for apps/ui-community/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in apps/ui-staff/ was NOT MEASURED: the dependency install for apps/ui-staff/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in packages/cellix/api-core/ was NOT MEASURED: the dependency install for packages/cellix/api-core/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in packages/cellix/archunit-tests/ was NOT MEASURED: the dependency install for packages/cellix/archunit-tests/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in packages/cellix/config-rolldown/ was NOT MEASURED: the dependency install for packages/cellix/config-rolldown/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in packages/cellix/config-vitest/ was NOT MEASURED: the dependency install for packages/cellix/config-vitest/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in packages/cellix/domain-seedwork/ was NOT MEASURED: the dependency install for packages/cellix/domain-seedwork/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in packages/cellix/event-bus-seedwork-node/ was NOT MEASURED: the dependency install for packages/cellix/event-bus-seedwork-node/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D12 Dependency Hygiene — not measured this run — We 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 — We measured this, but not all of it. What we 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.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we 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 kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We 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. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we 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 kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
- D32 Data Compliance (PII/GDPR) — not measured this run — We 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/docs/sidebars.ts`, `apps/ui-community/src/App.stories.tsx`, `apps/ui-community/src/components/ui/molecules/auth-landing/auth-landing.stories.tsx`, `apps/ui-community/src/components/ui/organisms/apollo-connection/apollo-client-links.stories.tsx`, … (+39 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.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in packages/cellix/api-core/src/infrastructure-service-store.ts, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXB2 Runtime readiness — not measured this run — We 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. A program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. (rule: missing-tool). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> cellixjs@1.0.0 dev / > pnpm proxy:stop && pnpm proxy:start && turbo watch azurite dev --filter='./apps/*' --filter='./packages/*' / sh: 1: pnpm: not found" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We 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 (`npm run dev`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> cellixjs@1.0.0 dev / > pnpm proxy:stop && pnpm proxy:start && turbo watch azurite dev --filter='./apps/*' --filter='./packages/*' / sh: 1: pnpm: not found" No runtime evidence was gathered.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we 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 — We measured this, but not all of it. What we 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. 177 further occurrence(s) are not listed individually; the score already reflects all 217.
- R11 Import Boundaries — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 13 further occurrence(s) are not listed individually; the score already reflects all 53.
- X2 Cancellation propagation — not measured this run — We 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, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
- X4 Structured logging — not measured this run — We 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 log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, 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.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do 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
- 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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 publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- 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.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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.
Dimensions
D1 · Cyclomatic Complexity
17 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was router.buildOidcRouter at 71.
What to do
- Bring the 5 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with router.buildOidcRouter (cyclomatic 71), login-handlers.createLoginHandlers.registerRoutes (cyclomatic 62), section-layout.SectionLayout (cyclomatic 40). — 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 5 together lifts Cyclomatic Complexity from 7.0 to about 7.9/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
21 method(s) exceeded the cognitive complexity threshold of 15; the worst was router.buildOidcRouter at 92.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with router.buildOidcRouter (cognitive 92), login-handlers.createLoginHandlers.registerRoutes (cognitive 72). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 6.4 to about 6.9/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
12 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 12 FunctionTooLong finding(s) in God Classes — start with REDACTED (2), REDACTED, members-list.tsx. — One of this dimension's main actionable groups (12 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D5 · Coupling
50 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 9 module(s) off the main sequence, with abstractness counted on 48 of the 50 (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).
What to do
- Resolve the 8 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (8 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 80 classes have LCOM4 above 3.
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
What to do
- Resolve the 34 Classify ADR enforcement finding(s) in Architectural Integrity — start with 0001-madr-architecture-decisions.md, 0002-open-telemetry.md, 0003-domain-driven-design.md. — One of this dimension's main actionable groups (34 recommendation-level).
- Enforce Architectural Integrity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D9 · Test Distribution
724 test methods: 697 unit, 27 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 724 `it`/`test` case(s) across 307 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 7 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 724 tests.
What to do
- Resolve the 7 No assertions (empty test) finding(s) in Test Quality — start with mongo-unit-of-work.integration.test.ts (7). — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 4 Mock-dominated test finding(s) in Test Quality — start with member-management.operations.test.ts (2), world.test.ts, cellix.test.ts. — One of this dimension's main actionable groups (4 recommendation-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
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.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
7 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts. Counted over 244 of the 1026 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
17 deducted task-comment markers across 42734 LoC (0.0/KLoC) → score 9.9. 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.
What to do
- Resolve the 13 TodoComment finding(s) in Explicit Debt — start with service-ticket-v1.domain-adapter.ts (4), property.domain-adapter.ts, member.community.visa.ts. — One of this dimension's main actionable groups (13 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).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 2 documentation facets pass in full; short on: F2 example. 57 document(s) read across 57 unit(s).
D20 · ADR Quality
8 of 34 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D23 · Boundary Type-Coupling
2 domain type(s) cross context boundaries across 52 contexts; they are measured and withheld (not published, not scored). Contexts: acceptance-api, acceptance-ui, api, api-core, api-services-spec, application-services, archunit-tests, config-rolldown, config-vitest, context-spec, data-sources-mongoose-models, docs and 40 more.
D24 · Comment Value
63 of 892 judged comments only repeat the code they sit on (7.1 %). 29 comment(s) in another language or script were not judged.
What to do
- Resolve the 43 redundant comment finding(s) in Comment Value — start with index.test.ts (7), apollo-client-links.tsx (4), create-member.test.ts (4). — One of this dimension's main actionable groups (43 recommendation-level).
D26 · Project Cohesion
1 of 51 build units (npm) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
25 finding(s): 0 critical, 9 high, 16 medium, 0 low. 6 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 51 file(s) — `.github/hooks/enforce-agent-workflow.sh`, `apps/docs/docusaurus.config.ts` (line 71, line 148, line 151), `apps/docs/sidebars.ts` (line 31), `apps/server-mongodb-memory-mock/src/seed/roles.ts` (line 67, line 97), `apps/ui-community/src/App.stories.tsx` (line 80), … (+46 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.
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 6 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (6 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
52 finding(s): 4 critical, 23 high, 22 medium, 3 low.
What to do
- Resolve the 22 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (21), REDACTED. — One of this dimension's main actionable groups (22 issue-level).
- Resolve the 4 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
11 finding(s): 0 critical, 0 high, 11 medium, 0 low.
What to do
- Resolve the 11 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (7), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (11 warning-level).
D34 · Knowledge Freshness
76 of 244 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/ocom/graphql/src/schema/types/member.resolvers.ts. Counted over 244 of the 1026 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 74 Orphaned file finding(s) in Knowledge Freshness — start with section-layout.stories.tsx (2), menu-component.stories.tsx (2), staff-landing.steps.ts (2). — One of this dimension's main actionable groups (74 recommendation-level).
- Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with member.resolvers.ts, member-management.ts. — One of this dimension's main actionable groups (2 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).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
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).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 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.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
- This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×2) — packages/ocom/ui-community-route-admin/src/components/members-list.tsx:226, packages/ocom/ui-staff-route-user-management/src/components/staff-user-detail.tsx:94
- This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. — packages/ocom/ui-community-route-admin/src/components/members-list.tsx:234
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. (×2) — apps/ui-community/index.html:2, apps/ui-staff/index.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC6 · Visual & motion safety
AC7 · A11y enforcement
- No accessibility enforcement found — Storybook's a11y addon runs axe over your stories and a Storybook test runner is declared, but `parameters.a11y.test` is not 'error' (the default, 'todo', reports a violation and fails nothing). Set `a11y: { test: 'error' }` in .storybook/preview so a violation fails the run, and run it in CI. No a11y linter is configured either (eslint-plugin-jsx-a11y). What was searched, so you can tell an absence from a miss: the 112 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. — REDACTED:72
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 run the Storybook a11y addon's checks as tests (@storybook/test-runner or @storybook/addon-vitest, with `parameters.a11y.test: 'error'` in .storybook/preview), then run that in CI.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
- `@cellix/api-core` is a Domain project but references `@cellix/api-services-spec`, a Web 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/cellix/api-core/package.json:30
- `@ocom/application-services` is a Application project but references `@ocom/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/ocom/application-services/package.json:31
What to do
- Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion).
AX5 · Architecture & structure
AX6 · Interface segregation
- `MemberApplicationService` declares 18 required operations: `determineIfAdmin`, `queryById`, `queryByEndUserExternalId`, `queryByCommunityId`, `createMember`, `createMemberAccount`, `updateMemberAccount`, `removeMemberAccount`, `updateMemberProfile`, `inviteMember`, `bulkInviteMembers`, `updateMemberRole`, `activateMember`, `deactivateMember`, `removeMember`, `bulkActivateMembers`, `bulkDeactivateMembers`, `bulkRemoveMembers`. 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/ocom/application-services/src/contexts/community/member/index.ts:38
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation
- `@apps/api` (production) references the test project `@ocom/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:35
- `@cellix/api-core` (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/api-core/package.json:30
- `@cellix/service-blob-storage` (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-blob-storage/package.json:31
- `@ocom/application-services` (production) references the test project `@ocom/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/ocom/application-services/package.json:29
- `@ocom/service-apollo-server` (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/ocom/service-apollo-server/package.json:30
- `@ocom/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/ocom/service-mongoose/package.json:29
- `@ocom/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:30
- `@ocom/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/ocom/service-token-validation/package.json:29
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.
C1 · Data Protection
- No encryption usage (node:crypto createCipheriv, Web Crypto subtle.encrypt, crypto-js AES, tweetnacl/libsodium secretbox, a column-encryption layer such as typeorm-encrypted, prisma-field-encryption or mongoose-field-encryption, or MongoDB client-side field-level encryption) was found, and this repository persists personal data in the model cited here — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore. — packages/ocom/data-sources-mongoose-models/src/models/user/end-user.model.ts:72
- No in-app HTTPS enforcement, but a trusted-proxy setting ('trust proxy' / trustProxy) indicates a reverse-proxy topology — terminating TLS in the app would be wrong in this layout. Verify the reverse proxy enforces TLS. — packages/cellix/server-oauth2-mock-seedwork/src/manager.ts:63
What to do
- Encrypt sensitive data at rest (AES-256-GCM through node:crypto createCipheriv, or a column-encryption layer such as typeorm-encrypted / prisma-field-encryption / MongoDB CSFLE) and manage keys in a vault (AWS KMS, Azure Key Vault, GCP KMS, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.).
C2 · Access Controls
- 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. — packages/cellix/serenity-framework/src/infrastructure/api-infrastructure.ts:210
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.
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM2 · Strongly-typed ids
- `DomainEventBase.aggregateId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — packages/cellix/domain-seedwork/src/domain-seedwork/domain-event.ts:16
- `EndUser.externalId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — packages/ocom/domain/src/domain/contexts/user/end-user/end-user.ts:93
- `Member.cybersourceCustomerId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — packages/ocom/domain/src/domain/contexts/community/member/member.ts:212
- `Member.communityId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — packages/ocom/domain/src/domain/contexts/community/member/member.ts:221
- `StaffUser.externalId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — packages/ocom/domain/src/domain/contexts/user/staff-user/staff-user.ts:149
- `VendorUser.externalId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — packages/ocom/domain/src/domain/contexts/user/vendor-user/vendor-user.ts:97
- `ViolationTicketV1.communityId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1.aggregate.ts:209
- `ViolationTicketV1.requestorId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1.aggregate.ts:231
- `MemberInvitation.communityId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — packages/ocom/domain/src/domain/contexts/community/member/member-invitation.ts:173
- `ServiceTicketV1.communityId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:234
- `ServiceTicketV1.requestorId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:256
- `ServiceTicketV1.assignedToId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:267
- `ServiceTicketV1.serviceId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:278
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model
- `EndUserRole` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role.ts:28
- `EndUser` is an aggregate/entity with 11 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/ocom/domain/src/domain/contexts/user/end-user/end-user.ts:31
- `Member` is an aggregate/entity with 13 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/ocom/domain/src/domain/contexts/community/member/member.ts:43
- `Property` is an aggregate/entity with 17 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/ocom/domain/src/domain/contexts/property/property/property.aggregate.ts:42
- `Service` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/ocom/domain/src/domain/contexts/service/service/service.aggregate.ts:25
- `StaffRole` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role.ts:25
- `VendorUser` is an aggregate/entity with 10 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/ocom/domain/src/domain/contexts/user/vendor-user/vendor-user.ts:28
- `ViolationTicketV1` is an aggregate/entity with 21 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1.aggregate.ts:61
- `VendorUserRole` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role.ts:28
- `Community` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/ocom/domain/src/domain/contexts/community/community/community.ts:27
- `ServiceTicketV1` is an aggregate/entity with 18 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:51
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
- `EndUserRole` exposes publicly writable state (roleName, isDefault). — packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role.ts:28
- `EndUser` exposes publicly writable state (email, displayName, externalId, accessBlocked, tags). — packages/ocom/domain/src/domain/contexts/user/end-user/end-user.ts:31
- `Member` exposes publicly writable state (memberName, cybersourceCustomerId, community, role). — packages/ocom/domain/src/domain/contexts/community/member/member.ts:43
- `Property` exposes publicly writable state (location, owner, propertyName, propertyType, listedForSale, listedForRent, and 6 more). — packages/ocom/domain/src/domain/contexts/property/property/property.aggregate.ts:42
- `Service` exposes publicly writable state (serviceName, description, isActive). — packages/ocom/domain/src/domain/contexts/service/service/service.aggregate.ts:25
- `StaffRole` exposes publicly writable state (roleName, enterpriseAppRole, isDefault). — packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role.ts:25
- `StaffUser` exposes publicly writable state (role, firstName, lastName, email, displayName, externalId, and 2 more). — packages/ocom/domain/src/domain/contexts/user/staff-user/staff-user.ts:36
- `VendorUser` exposes publicly writable state (email, displayName, externalId, accessBlocked, tags). — packages/ocom/domain/src/domain/contexts/user/vendor-user/vendor-user.ts:28
- `ViolationTicketV1` exposes publicly writable state (communityId, propertyId, assignedToId, serviceId, title, description, and 6 more). — packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1.aggregate.ts:61
- `VendorUserRole` exposes publicly writable state (isDefault, roleName). — packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role.ts:28
- `Community` exposes publicly writable state (name, domain, whiteLabelDomain, handle). — packages/ocom/domain/src/domain/contexts/community/community/community.ts:27
- `MemberInvitation` exposes publicly writable state (email, message, expiresAt). — packages/ocom/domain/src/domain/contexts/community/member/member-invitation.ts:27
- `ServiceTicketV1` exposes publicly writable state (title, description, status, priority, communityId, propertyId, and 6 more). — packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:51
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary
DM7 · Repository granularity
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body. — REDACTED:173
- `onSigninCallback` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/ocom/ui-community-route-accounts/.storybook/preview.tsx:15
What to do
- Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Add a README to the 26 of 63 project(s) that lack one — worth up to 0.8 pts.
M2 · Architecture documentation
What to do
- Grow the ADR log (currently 36) — reach 50 to raise the maturity tier; document significant decisions as they're made.
M3 · Folder & project structure
M4 · Documentation accuracy
- 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/ocom/ui-staff-shared/README.md links to `./.github/instructions/ui/layouts.instructions.md`, but `packages/ocom/ui-staff-shared/.github/instructions/ui/layouts.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/ocom/ui-staff-shared/README.md:172
- packages/cellix/mongoose-seedwork/src/mongoose-seedwork/README.md links to `../../../cellix-domain-seedwork/src/domain-seedwork/README.md`, but `packages/cellix/cellix-domain-seedwork/src/domain-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/mongoose-seedwork/src/mongoose-seedwork/README.md:11
- 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: 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; packages/ocom/ui-staff-shared/README.md links to `./.github/instructions/ui/layouts.instructions.md`, but `packages/ocom/ui-staff-shared/.github/instructions/ui/layouts.instructions.md` does not exist; packages/cellix/mongoose-seedwork/src/mongoose-seedwork/README.md links to `../../../cellix-domain-seedwork/src/domain-seedwork/README.md`, but `packages/cellix/cellix-domain-seedwork/src/domain-seedwork/README.md` does not exist; 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.
P1 · CI/CD gates
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.
P10 · Library API & versioning
P11 · BDD / executable specs
P2 · Observability
- Only 1/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/cellix/config-rolldown`, `packages/cellix/service-queue-storage`.
- `packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts` reports through `console.*` at line 77 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:77
- `packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts` reports through `console.*` at line 94 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:94
- `packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts` reports through `console.*` at line 108 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:108
- `packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts` reports through `console.*` at line 124 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:124
- `packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts` reports through `console.*` at line 134 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:134
- `packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts` reports through `console.*` at line 148 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:148
- `packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts` reports through `console.*` at line 155 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:155
- `packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts` reports through `console.*` at line 165 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:165
- `packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts` reports through `console.*` at line 172 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:172
- `packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts` reports through `console.*` at line 179 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:179
- `packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts` reports through `console.*` at line 188 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:188
- `packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts` reports through `console.*` at line 290 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:290
- `packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts` reports through `console.*` at line 293 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:293
- `packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts` reports through `console.*` at line 321 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:321
- `packages/cellix/server-oauth2-mock-seedwork/src/logger.ts` reports through `console.*` at line 20 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/logger.ts:20
- `packages/cellix/server-oauth2-mock-seedwork/src/logger.ts` reports through `console.*` at line 22 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/logger.ts:22
- `REDACTED` reports through `console.*` at line 150 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — REDACTED:150
- `packages/cellix/server-oauth2-mock-seedwork/src/manager.ts` reports through `console.*` at line 74 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/manager.ts:74
- `packages/cellix/server-oauth2-mock-seedwork/src/manager.ts` reports through `console.*` at line 75 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/manager.ts:75
- `packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts` reports through `console.*` at line 19 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:19
- `packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts` reports through `console.*` at line 108 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:108
- `packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts` reports through `console.*` at line 135 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:135
- `packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts` reports through `console.*` at line 142 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:142
- `packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts` reports through `console.*` at line 163 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:163
- `packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts` reports through `console.*` at line 180 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:180
- `packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts` reports through `console.*` at line 189 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:189
- `packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts` reports through `console.*` at line 198 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:198
- `packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts` reports through `console.*` at line 209 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:209
- `packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts` reports through `console.*` at line 232 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:232
- `packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts` reports through `console.*` at line 244 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:244
- `packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts` reports through `console.*` at line 249 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:249
- `packages/cellix/server-oauth2-mock-seedwork/src/server.ts` reports through `console.*` at line 34 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/server.ts:34
- `packages/cellix/server-oauth2-mock-seedwork/src/server.ts` reports through `console.*` at line 35 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/cellix/server-oauth2-mock-seedwork/src/server.ts:35
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
- Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:72
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
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 we 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.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
- Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
PF3 · Async & latency hygiene
- `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. (×4) — packages/cellix/archunit-tests/src/checks/frontend-architecture.ts:24, packages/cellix/archunit-tests/src/checks/frontend-architecture.ts:29, packages/cellix/archunit-tests/src/checks/frontend-architecture.ts:33, …
- `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:48
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.
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- 29 duplicated blocks under packages/ocom/domain/src/domain/contexts/ have copies in at least two of the sibling directories case, community, property, service, user — 13 of them are reported below, and 16 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 29 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 29 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 29 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/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role-property-permissions.ts:7
- 22 duplicated blocks under packages/ocom/ have copies in at least two of the sibling directories data-sources-mongoose-models, domain, persistence, ui-community-route-accounts, ui-community-route-admin, ui-community-route-root (+7 more sibling(s) not listed) — 9 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 22 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 22 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 22 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/ocom/ui-community-route-admin/src/sub-page-layout.tsx:12
- 17 duplicated blocks under packages/ocom/persistence/src/datasources/domain/ have copies in at least two of the sibling directories case, community, property, service, user — 12 of them are reported below, and 5 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 17 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 17 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 17 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/ocom/persistence/src/datasources/domain/case/service-ticket-v1/service-ticket-v1.domain-adapter.ts:232
- 9 duplicated blocks under apps/ have copies in at least two of the sibling directories ui-community, ui-staff — 8 of them are reported below, and 1 is 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 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 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-community/src/contexts/theme-context.tsx:11
- 9 duplicated blocks under packages/ocom/domain/src/domain/iam/ have copies in at least two of the sibling directories guest, member, system, user — 7 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 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 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/ocom/domain/src/domain/iam/guest/guest.passport.ts:14
- 8 duplicated blocks under packages/ocom/domain/src/domain/contexts/case/ have copies in at least two of the sibling directories service-ticket, violation-ticket — 5 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 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/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:45
- 7 duplicated blocks under packages/ocom/application-services/src/contexts/ have copies in at least two of the sibling directories community, user — 1 of them are reported below, and 6 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 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 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/ocom/application-services/src/contexts/community/community/update-settings.ts:18
- 7 duplicated blocks under packages/ocom/domain/src/domain/contexts/user/ have copies in at least two of the sibling directories end-user, staff-role, staff-user, vendor-user — 5 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 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 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/ocom/domain/src/domain/contexts/user/end-user/end-user.ts:11
- 7 duplicated blocks under packages/ocom/persistence/src/datasources/domain/user/ have copies in at least two of the sibling directories end-user, staff-role, staff-user, vendor-user — 3 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 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 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/ocom/persistence/src/datasources/domain/user/staff-user/staff-user.domain-adapter.ts:55
- 6 duplicated blocks under packages/ocom/domain/src/domain/contexts/community/role/ have copies in at least two of the sibling directories end-user-role, vendor-user-role — 5 of them are reported below, and 1 is 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. — packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role.ts:25
- 5 duplicated blocks under the repository root have copies in at least two of the sibling directories apps, packages — 3 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 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. — apps/ui-community/src/App.tsx:20
- 5 duplicated blocks under packages/ have copies in at least two of the sibling directories cellix, ocom, ocom-verification — 3 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 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/ocom-verification/acceptance-ui/src/contexts/staff-role/abilities/mock-staff-role-backend.ts:14
- 5 of the duplicated blocks reported below have copies in at least two of the sibling directories acceptance-api, acceptance-ui under packages/ocom-verification/. 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/ocom-verification/acceptance-api/src/contexts/staff/step-definitions/staff-landing.steps.ts:41
- packages/ocom/persistence/src/datasources/domain/community/role/end-user-role/end-user-role.domain-adapter.ts:18 · packages/ocom/persistence/src/datasources/domain/community/role/vendor-user-role/vendor-user-role.domain-adapter.ts:23 — the two spans are one implementation copied and then locally edited — 1437 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/ocom/persistence/src/datasources/domain/community/role/end-user-role/end-user-role.domain-adapter.ts:18
- 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
- apps/ui-community/src/contexts/theme-context.tsx:11 · apps/ui-staff/src/contexts/theme-context.tsx:6 — the two spans are one implementation copied and then locally edited — 591 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. — apps/ui-community/src/contexts/theme-context.tsx:11
- packages/ocom/data-sources-mongoose-models/src/models/role/end-user-role.model.ts:1 · packages/ocom/data-sources-mongoose-models/src/models/role/vendor-user-role.model.ts:1 — these 2 files are line-for-line copies of one another — 94 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/ocom/data-sources-mongoose-models/src/models/role/end-user-role.model.ts:1
- packages/ocom/ui-staff-route-user-management/src/components/staff-role-create.container.tsx:15 · packages/ocom/ui-staff-route-user-management/src/components/staff-role-edit.container.tsx:15 — the two spans are one implementation copied and then locally edited — 471 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/ocom/ui-staff-route-user-management/src/components/staff-role-create.container.tsx:15
- packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role.ts:25 · packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role.ts:25 — the two spans are one implementation copied and then locally edited — 476 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/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role.ts:25
- packages/ocom/data-sources-mongoose-models/src/models/user/end-user.model.ts:27 · packages/ocom/data-sources-mongoose-models/src/models/user/vendor-user.model.ts:31 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/ocom/data-sources-mongoose-models/src/models/user/end-user.model.ts:27
- packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:45 · packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1.aggregate.ts:55 — the two spans are one implementation copied and then locally edited — 548 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/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:45
- REDACTED:76 · REDACTED:218 — the two spans are one implementation copied and then locally edited — 440 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. — REDACTED:76
- packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1-message.entity.ts:11 · packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1-message.ts:10 — the two spans are one implementation copied and then locally edited — 380 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/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1-message.entity.ts:11
- packages/ocom/domain/src/domain/contexts/user/end-user/end-user.ts:11 · packages/ocom/domain/src/domain/contexts/user/vendor-user/vendor-user.ts:10 — the two spans are one implementation copied and then locally edited — 355 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/ocom/domain/src/domain/contexts/user/end-user/end-user.ts:11
- packages/ocom/data-sources-mongoose-models/src/models/case/service-ticket.model.ts:33 · packages/ocom/data-sources-mongoose-models/src/models/case/violation-ticket.model.ts:133 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/ocom/data-sources-mongoose-models/src/models/case/service-ticket.model.ts:33
- packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role-service-ticket-permissions.ts:7 · packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role-violation-ticket-permissions.ts:7 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role-service-ticket-permissions.ts:7
- packages/ocom/ui-community-route-admin/src/components/members-accounts-add.tsx:7 · packages/ocom/ui-community-route-admin/src/components/members-accounts-edit.tsx:9 — 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/ocom/ui-community-route-admin/src/components/members-accounts-add.tsx:7
- packages/ocom/ui-community-route-admin/src/sub-page-layout.tsx:12 · packages/ocom/ui-staff-shared/src/sub-page-layout.tsx:28 — 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/ocom/ui-community-route-admin/src/sub-page-layout.tsx:12
- packages/ocom/persistence/src/datasources/domain/user/staff-user/staff-user.domain-adapter.ts:55 · packages/ocom/persistence/src/datasources/domain/user/vendor-user/vendor-user.domain-adapter.ts:24 — the two spans are one implementation copied and then locally edited — 212 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/ocom/persistence/src/datasources/domain/user/staff-user/staff-user.domain-adapter.ts:55
- packages/ocom/domain/src/domain/iam/guest/guest.passport.ts:14 · packages/ocom/domain/src/domain/iam/system/system.passport.ts:14 — the two spans are one implementation copied and then locally edited — 189 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/ocom/domain/src/domain/iam/guest/guest.passport.ts:14
- packages/ocom/ui-community-route-admin/src/section-layout.tsx:88 · packages/ocom/ui-staff-shared/src/section-layout.tsx:201 — 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/ocom/ui-community-route-admin/src/section-layout.tsx:88
- packages/ocom/domain/src/domain/iam/guest/guest.passport.ts:15 · packages/ocom/domain/src/domain/iam/member/member.passport.ts:16 — the two spans are one implementation copied and then locally edited — 179 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/ocom/domain/src/domain/iam/guest/guest.passport.ts:15
- packages/ocom/domain/src/domain/iam/member/member.passport.ts:16 · packages/ocom/domain/src/domain/iam/system/system.passport.ts:15 — the two spans are one implementation copied and then locally edited — 179 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/ocom/domain/src/domain/iam/member/member.passport.ts:16
- packages/ocom/ui-staff-route-user-management/src/components/staff-roles-list.tsx:38 · packages/ocom/ui-staff-route-user-management/src/components/staff-users-list.tsx:34 — the two spans are one implementation copied and then locally edited — 198 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/ocom/ui-staff-route-user-management/src/components/staff-roles-list.tsx:38
- packages/ocom/ui-community-route-root/src/components/header.tsx:6 · packages/ocom/ui-staff-route-root/src/components/header.tsx:6 — 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/ocom/ui-community-route-root/src/components/header.tsx:6
- packages/ocom/domain/src/domain/iam/guest/guest.passport.ts:14 · packages/ocom/domain/src/domain/iam/user/staff-user/staff-user.passport.ts:12 — the two spans are one implementation copied and then locally edited — 157 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/ocom/domain/src/domain/iam/guest/guest.passport.ts:14
- packages/ocom/domain/src/domain/iam/system/system.passport.ts:14 · packages/ocom/domain/src/domain/iam/user/staff-user/staff-user.passport.ts:12 — the two spans are one implementation copied and then locally edited — 157 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/ocom/domain/src/domain/iam/system/system.passport.ts:14
- packages/ocom/domain/src/domain/iam/member/member.passport.ts:16 · packages/ocom/domain/src/domain/iam/user/staff-user/staff-user.passport.ts:13 — the two spans are one implementation copied and then locally edited — 154 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/ocom/domain/src/domain/iam/member/member.passport.ts:16
- packages/ocom-verification/acceptance-api/src/contexts/staff/step-definitions/staff-landing.steps.ts:41 · packages/ocom-verification/acceptance-ui/src/contexts/staff/step-definitions/create-staff-landing.steps.ts:32 — the two spans are one implementation copied and then locally edited — 292 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/ocom-verification/acceptance-api/src/contexts/staff/step-definitions/staff-landing.steps.ts:41
- packages/ocom/domain/src/domain/contexts/property/property/property-listing-detail-additional-amenity.entity.ts:7 · packages/ocom/domain/src/domain/contexts/property/property/property-listing-detail-bedroom-detail.entity.ts:7 — 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/ocom/domain/src/domain/contexts/property/property/property-listing-detail-additional-amenity.entity.ts:7
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.
R11 · Import Boundaries
- packages/ocom-verification/acceptance-api/src/mock-application-services.ts:10 imports packages/ocom-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/ocom-verification/acceptance-api/src/mock-application-services.ts:10
- packages/ocom-verification/acceptance-api/src/servers/test-mongo-server.ts:2 imports packages/ocom-verification/verification-shared/src/environment/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/ocom-verification/acceptance-api/src/servers/test-mongo-server.ts:2
- packages/ocom-verification/acceptance-api/src/servers/test-mongo-server.ts:3 imports packages/ocom-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/ocom-verification/acceptance-api/src/servers/test-mongo-server.ts:3
- packages/ocom-verification/acceptance-ui/src/contexts/authentication/tasks/click-header-sign-in.ts:4 imports packages/ocom-verification/verification-shared/src/pages/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/ocom-verification/acceptance-ui/src/contexts/authentication/tasks/click-header-sign-in.ts:4
- packages/ocom-verification/acceptance-ui/src/contexts/community/tasks/create-community.ts:4 imports packages/ocom-verification/verification-shared/src/pages/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/ocom-verification/acceptance-ui/src/contexts/community/tasks/create-community.ts:4
- packages/ocom-verification/acceptance-ui/src/contexts/staff-role/abilities/mock-staff-role-backend.ts:2 imports packages/ocom-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/ocom-verification/acceptance-ui/src/contexts/staff-role/abilities/mock-staff-role-backend.ts:2
- packages/ocom-verification/acceptance-ui/src/contexts/staff-role/abilities/mock-staff-role-backend.ts:4 reaches into another package with a relative path (../../../../../../ocom/ui-staff-shared/src/staff-route-shell.tsx) — import the package by name instead. — packages/ocom-verification/acceptance-ui/src/contexts/staff-role/abilities/mock-staff-role-backend.ts:4
- packages/ocom-verification/acceptance-ui/src/contexts/staff-role/tasks/staff-roles-screen.ts:4 imports packages/ocom-verification/verification-shared/src/pages/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/ocom-verification/acceptance-ui/src/contexts/staff-role/tasks/staff-roles-screen.ts:4
- packages/ocom-verification/acceptance-ui/src/contexts/staff-role/tasks/staff-roles-screen.ts:9 reaches into another package with a relative path (../../../../../../ocom/ui-staff-route-user-management/src/pages/staff-roles.tsx) — import the package by name instead. — packages/ocom-verification/acceptance-ui/src/contexts/staff-role/tasks/staff-roles-screen.ts:9
- packages/ocom-verification/acceptance-ui/src/shared/ocom-component-wrapper.ts:6 reaches into another package with a relative path (../../../../ocom/ui-staff-shared/src/staff-route-shell.tsx) — import the package by name instead. — packages/ocom-verification/acceptance-ui/src/shared/ocom-component-wrapper.ts:6
- packages/ocom/application-services/src/contexts/community/community/create.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/community/community/create.ts:2
- packages/ocom/application-services/src/contexts/community/community/index.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/community/community/index.ts:2
- packages/ocom/application-services/src/contexts/community/community/query-by-end-user-external-id.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/community/community/query-by-end-user-external-id.ts:2
- packages/ocom/application-services/src/contexts/community/community/query-by-id.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/community/community/query-by-id.ts:2
- packages/ocom/application-services/src/contexts/community/community/update-settings.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/community/community/update-settings.ts:2
- packages/ocom/application-services/src/contexts/community/index.ts:1 imports packages/ocom/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/ocom/application-services/src/contexts/community/index.ts:1
- packages/ocom/application-services/src/contexts/community/member/determine-if-admin.ts:1 imports packages/ocom/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/ocom/application-services/src/contexts/community/member/determine-if-admin.ts:1
- packages/ocom/application-services/src/contexts/community/member/index.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/community/member/index.ts:2
- packages/ocom/application-services/src/contexts/community/member/member-management.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/community/member/member-management.ts:2
- packages/ocom/application-services/src/contexts/community/member/query-by-community-id.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/community/member/query-by-community-id.ts:2
- packages/ocom/application-services/src/contexts/community/member/query-by-end-user-external-id.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/community/member/query-by-end-user-external-id.ts:2
- packages/ocom/application-services/src/contexts/community/member/query-by-id.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/community/member/query-by-id.ts:2
- packages/ocom/application-services/src/contexts/community/role/end-user-role/index.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/community/role/end-user-role/index.ts:2
- packages/ocom/application-services/src/contexts/community/role/end-user-role/query-by-community-id.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/community/role/end-user-role/query-by-community-id.ts:2
- packages/ocom/application-services/src/contexts/community/role/end-user-role/query-by-id.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/community/role/end-user-role/query-by-id.ts:2
- packages/ocom/application-services/src/contexts/community/role/index.ts:1 imports packages/ocom/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/ocom/application-services/src/contexts/community/role/index.ts:1
- packages/ocom/application-services/src/contexts/service/index.ts:1 imports packages/ocom/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/ocom/application-services/src/contexts/service/index.ts:1
- packages/ocom/application-services/src/contexts/service/service/create.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/service/service/create.ts:2
- packages/ocom/application-services/src/contexts/service/service/index.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/service/service/index.ts:2
- packages/ocom/application-services/src/contexts/user/end-user/create-if-not-exists.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/user/end-user/create-if-not-exists.ts:2
- packages/ocom/application-services/src/contexts/user/end-user/index.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/user/end-user/index.ts:2
- packages/ocom/application-services/src/contexts/user/end-user/query-by-community-id.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/user/end-user/query-by-community-id.ts:2
- packages/ocom/application-services/src/contexts/user/end-user/query-by-id.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/user/end-user/query-by-id.ts:2
- packages/ocom/application-services/src/contexts/user/end-user/query-by-name.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/user/end-user/query-by-name.ts:2
- packages/ocom/application-services/src/contexts/user/index.ts:1 imports packages/ocom/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/ocom/application-services/src/contexts/user/index.ts:1
- packages/ocom/application-services/src/contexts/user/staff-role/create-default-roles.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/user/staff-role/create-default-roles.ts:2
- packages/ocom/application-services/src/contexts/user/staff-role/create.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/user/staff-role/create.ts:2
- packages/ocom/application-services/src/contexts/user/staff-role/delete-and-reassign.ts:1 imports packages/ocom/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/ocom/application-services/src/contexts/user/staff-role/delete-and-reassign.ts:1
- packages/ocom/application-services/src/contexts/user/staff-role/index.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/user/staff-role/index.ts:2
- packages/ocom/application-services/src/contexts/user/staff-role/list.ts:2 imports packages/ocom/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/ocom/application-services/src/contexts/user/staff-role/list.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 (38 rows); import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (8 rows); move the shared test helper into a source directory production code may depend on (7 rows).
R2 · Cyclomatic Complexity
- SectionLayout has cyclomatic complexity 37 and cognitive complexity 37; 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/ocom/ui-staff-shared/src/section-layout.tsx:37
- validateEnvNames has cyclomatic complexity 33 and cognitive complexity 59; 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/ocom-verification/archunit-tests/src/validate-env-names.cjs:286
- (anonymous) has cyclomatic complexity 29 and cognitive complexity 37; 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:103
- checkFrontendArchitecture has cyclomatic complexity 27 and cognitive complexity 32; 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/archunit-tests/src/checks/frontend-architecture.ts:12
- validateEntries has cyclomatic complexity 26 and cognitive complexity 42; 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/server-oauth2-mock-seedwork/src/file-user-store.ts:119
- (anonymous) has cyclomatic complexity 26 and cognitive complexity 31; 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/ocom-verification/e2e-tests/src/contexts/community/tasks/create-community.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. — packages/cellix/archunit-tests/src/checks/circular-dependencies.ts:50
- (anonymous) has cyclomatic complexity 22 and cognitive complexity 30; 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:134
- StaffUserDetailContainer has cyclomatic complexity 22 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/ocom/ui-staff-route-user-management/src/components/staff-user-detail.container.tsx:32
- (anonymous) has cyclomatic complexity 21 and cognitive complexity 24; 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:244
- (anonymous) has cyclomatic complexity 21 and cognitive complexity 20; 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/ocom/application-services/src/contexts/community/member/member-management.ts:517
- detectChanges has cyclomatic complexity 20 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — build-pipeline/scripts/detect-changes.cjs:137
- (anonymous) has cyclomatic complexity 19 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. — apps/ui-staff/src/hooks/use-staff-permissions.ts:87
- skipTemplateExpression has cyclomatic complexity 18 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/ocom-verification/archunit-tests/src/validate-env-names.cjs:44
- StaffRoutes has cyclomatic complexity 18 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/ui-staff/src/App.tsx:20
- (anonymous) has cyclomatic complexity 17 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. — REDACTED:241
- (anonymous) has cyclomatic complexity 17 and cognitive complexity 24; 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. — apps/ui-staff/src/contexts/theme-context.tsx:92
- findEnvVarsInText has cyclomatic complexity 15 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. — packages/ocom-verification/archunit-tests/src/validate-env-names.cjs:204
- normalizeUserInfo has cyclomatic complexity 15 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/cellix/server-oauth2-mock-seedwork/src/helpers.ts:38
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files
- packages/ocom/graphql/src/schema/types/member.resolvers.ts has 700 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/ocom/graphql/src/schema/types/member.resolvers.ts:1
- packages/ocom/persistence/src/datasources/domain/property/property/property.domain-adapter.ts has 527 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/ocom/persistence/src/datasources/domain/property/property/property.domain-adapter.ts:1
- packages/ocom/application-services/src/contexts/community/member/member-management.ts has 444 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/ocom/application-services/src/contexts/community/member/member-management.ts:1
- packages/ocom/persistence/src/datasources/domain/user/staff-role/staff-role.domain-adapter.ts has 430 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/ocom/persistence/src/datasources/domain/user/staff-role/staff-role.domain-adapter.ts:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- packages/cellix/archunit-tests/src/typescript-config-conventions.test.ts:8 imports '../../..', 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/cellix/archunit-tests/src/typescript-config-conventions.test.ts:8
- packages/ocom-verification/archunit-tests/src/typescript-config-conventions.test.ts:8 imports '../../..', 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/ocom-verification/archunit-tests/src/typescript-config-conventions.test.ts:8
- 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. (×22) — build-pipeline/scripts/detect-changes.cjs:1, apps/ui-staff/src/contexts/theme-context.tsx:1, apps/ui-community/src/contexts/theme-context.tsx:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
- This repository declares test tooling, and the ✓ above records that declaration — but packages/cellix/archunit-tests/src/typescript-config-conventions.test.ts and 1 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/cellix/archunit-tests/src/typescript-config-conventions.test.ts:8
R7 · Dead Code
- 6 file(s) (~281 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: packages/cellix/graphql-core/src/index.ts imports './schema/base-type-defs.generated.ts', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — packages/cellix/graphql-core
- 48 file(s) (~2034 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/ocom-verification/acceptance-api
- 30 file(s) (~1182 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/ocom-verification/acceptance-ui
- Unreachable from the 207 application, 141 tooling and 527 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 (207 application, 141 tooling, 527 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 (×2) — build-pipeline/scripts/get-pr-number.cjs, packages/ocom/graphql/src/schema/types/end-user-role.resolvers.ts
- Nothing imports this binding — it is safe to review for removal. (×2) — packages/cellix/mongoose-seedwork/src/mongoose-seedwork/mongo-connection.ts:6, packages/cellix/mongoose-seedwork/src/mongoose-seedwork/mongo-connection.ts:7
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- 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:8
- Only test files import it (first: packages/ocom/ui-shared/src/components/organisms/vertical-tabs/index.stories.tsx:1) — move it to devDependencies. — packages/ocom/ui-shared/package.json:32
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- packages/ocom/ui-staff-shared/src/section-layout.tsx → packages/ocom/ui-staff-shared/src/staff-route-shell.tsx → packages/ocom/ui-staff-shared/src/section-layout.tsx — packages/ocom/ui-staff-shared/src/section-layout.tsx:6
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture
- `user.password !== password` checks a password against the stored one in plaintext, so the store holds the password itself and whoever reads it holds every account. — REDACTED:164
- `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-mock-seedwork/src/manager.ts:73
- `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.) — packages/cellix/server-oauth2-mock-seedwork/src/server.ts:33
What to do
- Store passwords with a salted, deliberately slow KDF — scrypt or PBKDF2 from node:crypto, or bcrypt/Argon2 — and compare with a constant-time check. A fast digest of a password, however it is encoded, is reversed by precomputed tables or GPU guessing. Start in `REDACTED:164`.
- 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`.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
- `escapedIssuerBaseUrl` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. (×3) — packages/cellix/server-oauth2-mock-seedwork/src/html-builders.ts:16, packages/cellix/server-oauth2-mock-seedwork/src/html-builders.ts:22, packages/cellix/server-oauth2-mock-seedwork/src/html-builders.ts:36
- `link` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through `res.send` (the page this server sends) with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — REDACTED:155
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- 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. (×24) — packages/ocom-verification/acceptance-ui/src/cucumber-lifecycle-hooks.ts:21, packages/ocom-verification/acceptance-api/src/contexts/community/step-definitions/create-community.steps.ts:88, packages/ocom-verification/acceptance-api/src/contexts/community/step-definitions/create-community.steps.ts:105, …
- `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — packages/cellix/server-oauth2-mock-seedwork/src/manager.ts:87
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- 4/98 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.
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 `?`).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| 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 |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 63% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 55% | Adequate — gated by AX8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 87% | Strong | Strongest area. |
| Readiness | 44% | Weak — gated by R8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 48% | Weak — gated by D29, D36, C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 51% | Adequate — gated by DM5, DM2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 45% | Weak — gated by AC2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 60% | Adequate | Acceptable, with room to improve. |
Unscored — 3 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 5 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 — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model, an ORM write hook that records changes — a TypeORM/MikroORM subscriber, a Sequelize or Mongoose hook, Prisma middleware — or a change-history plugin such as mongoose-history or sequelize-paper-trail) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 43 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 (`npm run dev`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> cellixjs@1.0.0 dev / > pnpm proxy:stop && pnpm proxy:start && turbo watch azurite dev --filter='./apps/*' --filter='./packages/*' / sh: 1: pnpm: not found" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
- 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.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript, Python not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
- D25 ADR Conformance — None of 25 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D32 Data Compliance (PII/GDPR) — 44 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.
- D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- 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
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript source (service entry point: packages/cellix/server-oauth2-mock-seedwork/src/manager.ts:44 (express()))
- 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 — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage --coverage.reporter=lcovonly`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — 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 scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- 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.
- X2 Cancellation propagation — 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
- 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)
Critical — 58 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Production project references a test project: @apps/api → @ocom/context-spec apps/api/package.json:35
- Production project references a test project: @cellix/api-core → @cellix/api-services-spec packages/cellix/api-core/package.json:30
- Production project references a test project: @cellix/service-blob-storage → @cellix/api-services-spec packages/cellix/service-blob-storage/package.json:31
- Production project references a test project: @ocom/application-services → @ocom/context-spec packages/ocom/application-services/package.json:29
- Production project references a test project: @ocom/service-apollo-server → @cellix/api-services-spec packages/ocom/service-apollo-server/package.json:30
- Production project references a test project: @ocom/service-mongoose → @cellix/api-services-spec packages/ocom/service-mongoose/package.json:29
- Production project references a test project: @ocom/service-otel → @cellix/api-services-spec REDACTED:30
- Production project references a test project: @ocom/service-token-validation → @cellix/api-services-spec packages/ocom/service-token-validation/package.json:29
- No assertions (empty test): Then the integration event should be dispatched by integrationEventBus after the transaction commits packages/cellix/mongoose-seedwork/tests/integration/mongo-unit-of-work.integration.test.ts:748
- No assertions (empty test): Then no integration events should be dispatched packages/cellix/mongoose-seedwork/tests/integration/mongo-unit-of-work.integration.test.ts:757
- No assertions (empty test): Then all integration events should be dispatched by integrationEventBus after the transaction commits packages/cellix/mongoose-seedwork/tests/integration/mongo-unit-of-work.integration.test.ts:765
- No assertions (empty test): Then the transaction should still commit and persist data, and the error should not abort the operation packages/cellix/mongoose-seedwork/tests/integration/mongo-unit-of-work.integration.test.ts:773
- No assertions (empty test): Then the dispatching should not block transaction completion but should still be awaited packages/cellix/mongoose-seedwork/tests/integration/mongo-unit-of-work.integration.test.ts:781
- No assertions (empty test): Then domain events should be dispatched before the transaction commits and integration events after packages/cellix/mongoose-seedwork/tests/integration/mongo-unit-of-work.integration.test.ts:789
- No assertions (empty test): Then the transaction should commit, but the failure should be surfaced/logged appropriately packages/cellix/mongoose-seedwork/tests/integration/mongo-unit-of-work.integration.test.ts:797
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Dependency-rule violation: @cellix/api-core (Domain) → @cellix/api-services-spec (Web) packages/cellix/api-core/package.json:30
- Dependency-rule violation: @ocom/application-services (Application) → @ocom/persistence (Infrastructure) packages/ocom/application-services/package.json:31
- Orphaned knowledge packages/ocom/graphql/src/schema/types/member.resolvers.ts:1
- Orphaned knowledge packages/ocom/application-services/src/contexts/community/member/member-management.ts:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Import cycle (2 files) packages/ocom/ui-staff-shared/src/section-layout.tsx:6
- Password hashing without a KDF REDACTED:164
Serious — 330 finding(s)
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/community/create.ts:2
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/community/index.ts:2
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/community/query-by-end-user-external-id.ts:2
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/community/query-by-id.ts:2
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/community/update-settings.ts:2
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/index.ts:1
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/member/determine-if-admin.ts:1
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/member/index.ts:2
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/member/member-management.ts:2
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/member/query-by-community-id.ts:2
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/member/query-by-end-user-external-id.ts:2
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/member/query-by-id.ts:2
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/role/end-user-role/index.ts:2
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/role/end-user-role/query-by-community-id.ts:2
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/role/end-user-role/query-by-id.ts:2
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/role/index.ts:1
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/service/index.ts:1
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/service/service/create.ts:2
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/service/service/index.ts:2
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/user/end-user/create-if-not-exists.ts:2
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/user/end-user/index.ts:2
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/user/end-user/query-by-community-id.ts:2
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/user/end-user/query-by-id.ts:2
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/user/end-user/query-by-name.ts:2
- Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/user/index.ts:1
- Swallowed exception (empty catch) packages/ocom-verification/acceptance-ui/src/cucumber-lifecycle-hooks.ts:21
- Swallowed exception (empty catch) packages/ocom-verification/acceptance-api/src/contexts/community/step-definitions/create-community.steps.ts:88
- Swallowed exception (empty catch) packages/ocom-verification/acceptance-api/src/contexts/community/step-definitions/create-community.steps.ts:105
- Swallowed exception (empty catch) packages/ocom-verification/acceptance-api/src/contexts/community/step-definitions/create-community.steps.ts:125
- Swallowed exception (empty catch) packages/ocom-verification/acceptance-api/src/contexts/community/step-definitions/create-community.steps.ts:132
- Swallowed exception (empty catch) packages/cellix/ui-core/src/components/molecules/require-auth/index.tsx:65
- Swallowed exception (empty catch) packages/cellix/service-queue-storage/src/internal-queue-storage-service.ts:296
- Swallowed exception (empty catch) packages/cellix/service-queue-storage/src/internal-queue-storage-service.ts:326
- Swallowed exception (empty catch) packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:275
- Swallowed exception (empty catch) REDACTED:141
- Swallowed exception (empty catch) packages/cellix/server-oauth2-mock-seedwork/src/manager.ts:59
- Swallowed exception (empty catch) packages/cellix/server-oauth2-mock-seedwork/src/manager.ts:87
- Swallowed exception (empty catch) packages/cellix/server-oauth2-mock-seedwork/src/manager.ts:138
- Swallowed exception (empty catch) REDACTED:109
- Swallowed exception (empty catch) REDACTED:167
- Swallowed exception (empty catch) packages/cellix/serenity-framework/src/dom/asset-loader-hooks.ts:48
- Swallowed exception (empty catch) packages/cellix/serenity-framework/src/dom/asset-loader-hooks.ts:60
- Swallowed exception (empty catch) packages/cellix/serenity-framework/src/cucumber/screenshot-hooks.ts:49
- Swallowed exception (empty catch) packages/cellix/config-rolldown/src/index.ts:96
- Swallowed exception (empty catch) apps/ui-staff/src/contexts/theme-context.tsx:84
- Swallowed exception (empty catch) apps/ui-staff/src/contexts/theme-context.tsx:107
- Swallowed exception (empty catch) apps/ui-staff/src/contexts/theme-context.tsx:154
- Swallowed exception (empty catch) apps/ui-staff/src/contexts/theme-context.tsx:177
- Swallowed exception (empty catch) apps/ui-staff/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx:44
- Swallowed exception (empty catch) apps/ui-community/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx:44
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No test reaches this file build-pipeline/scripts/detect-changes.cjs:1
- No test reaches this file apps/ui-staff/src/contexts/theme-context.tsx:1
- No test reaches this file apps/ui-community/src/contexts/theme-context.tsx:1
- No test reaches this file apps/server-mongodb-memory-mock/src/seed/properties.ts:1
- No test reaches this file apps/server-mongodb-memory-mock/src/seed/roles.ts:1
- No test reaches this file build-pipeline/scripts/check-sonar-quality-gate.cjs:1
- No test reaches this file build-pipeline/scripts/merge-coverage.js:1
- No test reaches this file apps/server-mongodb-memory-mock/src/seed/members.ts:1
- No test reaches this file apps/server-mongodb-memory-mock/src/seed/seed.ts:1
- No test reaches this file build-pipeline/scripts/get-pr-number.cjs:1
- No test reaches this file build-pipeline/scripts/build-bicep.js:1
- No test reaches this file apps/server-mongodb-memory-mock/src/seed/end-users.ts:1
- No test reaches this file apps/server-mongodb-memory-mock/src/seed/services.ts:1
- No test reaches this file apps/ui-community/src/config/oidc-config.tsx:1
- No test reaches this file apps/ui-staff/src/config/oidc-config.tsx:1
- No test reaches this file packages/ocom/graphql/src/schema/types/end-user-role.resolvers.ts:1
- No test reaches this file apps/server-mongodb-memory-mock/src/seed/communities.ts:1
- No test reaches this file apps/server-mongodb-memory-mock/src/setup-environment.ts:1
- No test reaches this file apps/server-oauth2-mock/src/setup-environment.ts:1
- No test reaches this file apps/api/start-dev.ts:1
- No test reaches this file packages/cellix/graphql-core/src/schema/core/graphql-tools-scalars.ts:1
- No test reaches this file apps/api/start-azurite.ts:1
- TodoComment packages/ocom/persistence/src/datasources/domain/property/property/property.domain-adapter.ts:153
- TodoComment packages/ocom/persistence/src/datasources/domain/case/service-ticket-v1/service-ticket-v1.domain-adapter.ts:263
- TodoComment packages/ocom/persistence/src/datasources/domain/case/service-ticket-v1/service-ticket-v1.domain-adapter.ts:275
- TodoComment packages/ocom/persistence/src/datasources/domain/case/service-ticket-v1/service-ticket-v1.domain-adapter.ts:321
- TodoComment packages/ocom/persistence/src/datasources/domain/case/service-ticket-v1/service-ticket-v1.domain-adapter.ts:333
- TodoComment packages/ocom/domain/src/domain/iam/member/contexts/member.community.visa.ts:36
- TodoComment packages/ocom/domain/src/domain/contexts/community/member/member.ts:227
- TodoComment packages/ocom/data-sources-mongoose-models/src/patterns.ts:6
- TodoComment packages/ocom/data-sources-mongoose-models/src/models/user/end-user.model.ts:105
- TodoComment packages/ocom/data-sources-mongoose-models/src/models/role/role.model.ts:8
- TodoComment packages/ocom/data-sources-mongoose-models/src/models/case/ticket.model.ts:8
- TodoComment packages/cellix/mongoose-seedwork/src/mongoose-seedwork/mongo-unit-of-work.ts:49
- TodoComment packages/cellix/domain-seedwork/src/domain-seedwork/child-entity.ts:1
- Mutable entity: EndUserRole packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role.ts:28
- Mutable entity: EndUser packages/ocom/domain/src/domain/contexts/user/end-user/end-user.ts:31
- Mutable entity: Member packages/ocom/domain/src/domain/contexts/community/member/member.ts:43
- Mutable entity: Property packages/ocom/domain/src/domain/contexts/property/property/property.aggregate.ts:42
- Mutable entity: Service packages/ocom/domain/src/domain/contexts/service/service/service.aggregate.ts:25
- Mutable entity: StaffRole packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role.ts:25
- Mutable entity: StaffUser packages/ocom/domain/src/domain/contexts/user/staff-user/staff-user.ts:36
- Mutable entity: VendorUser packages/ocom/domain/src/domain/contexts/user/vendor-user/vendor-user.ts:28
- Mutable entity: ViolationTicketV1 packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1.aggregate.ts:61
- Mutable entity: VendorUserRole packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role.ts:28
- Mutable entity: Community packages/ocom/domain/src/domain/contexts/community/community/community.ts:27
- Mutable entity: MemberInvitation packages/ocom/domain/src/domain/contexts/community/member/member-invitation.ts:27
- Mutable entity: ServiceTicketV1 packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:51
- FunctionTooLong: router.buildOidcRouter REDACTED:44
- FunctionTooLong: members-list.MemberList packages/ocom/ui-community-route-admin/src/components/members-list.tsx:59
- FunctionTooLong: login-handlers.createLoginHandlers REDACTED:44
- FunctionTooLong: login-handlers.createLoginHandlers.registerRoutes REDACTED:63
- FunctionTooLong: members-invite-modal.MembersInviteModal packages/ocom/ui-community-route-admin/src/components/members-invite-modal.tsx:27
- FunctionTooLong: file-user-store.createFileUserStore packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:43
- FunctionTooLong: members-list.container.MemberListContainer packages/ocom/ui-community-route-admin/src/components/members-list.container.tsx:21
- FunctionTooLong: section-layout.SectionLayout packages/ocom/ui-staff-shared/src/section-layout.tsx:37
- FunctionTooLong: member-profile.MemberProfile packages/ocom/ui-community-shared/src/components/member-profile.tsx:28
- FunctionTooLong: theme-context.ThemeProvider apps/ui-staff/src/contexts/theme-context.tsx:34
- FunctionTooLong: community-list.CommunityList packages/ocom/ui-community-route-accounts/src/components/community-list.tsx:16
- FunctionTooLong: staff-role-edit.container.StaffRoleEditContainer packages/ocom/ui-staff-route-user-management/src/components/staff-role-edit.container.tsx:32
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Anemic entity: EndUserRole packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role.ts:28
- Anemic entity: EndUser packages/ocom/domain/src/domain/contexts/user/end-user/end-user.ts:31
- Anemic entity: Member packages/ocom/domain/src/domain/contexts/community/member/member.ts:43
- Anemic entity: Property packages/ocom/domain/src/domain/contexts/property/property/property.aggregate.ts:42
- Anemic entity: Service packages/ocom/domain/src/domain/contexts/service/service/service.aggregate.ts:25
- Anemic entity: StaffRole packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role.ts:25
- Anemic entity: VendorUser packages/ocom/domain/src/domain/contexts/user/vendor-user/vendor-user.ts:28
- Anemic entity: ViolationTicketV1 packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1.aggregate.ts:61
- Anemic entity: VendorUserRole packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role.ts:28
- Anemic entity: Community packages/ocom/domain/src/domain/contexts/community/community/community.ts:27
- Anemic entity: ServiceTicketV1 packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:51
- Boundary violation [package:test-suite-dependency] packages/ocom-verification/acceptance-api/src/mock-application-services.ts:10
- Boundary violation [package:test-suite-dependency] packages/ocom-verification/acceptance-api/src/servers/test-mongo-server.ts:2
- Boundary violation [package:test-suite-dependency] packages/ocom-verification/acceptance-api/src/servers/test-mongo-server.ts:3
- Boundary violation [package:test-suite-dependency] packages/ocom-verification/acceptance-ui/src/contexts/authentication/tasks/click-header-sign-in.ts:4
- Boundary violation [package:test-suite-dependency] packages/ocom-verification/acceptance-ui/src/contexts/community/tasks/create-community.ts:4
- Boundary violation [package:test-suite-dependency] packages/ocom-verification/acceptance-ui/src/contexts/staff-role/abilities/mock-staff-role-backend.ts:2
- Boundary violation [package:relative-cross-package] packages/ocom-verification/acceptance-ui/src/contexts/staff-role/abilities/mock-staff-role-backend.ts:4
- Boundary violation [package:test-suite-dependency] packages/ocom-verification/acceptance-ui/src/contexts/staff-role/tasks/staff-roles-screen.ts:4
- Boundary violation [package:relative-cross-package] packages/ocom-verification/acceptance-ui/src/contexts/staff-role/tasks/staff-roles-screen.ts:9
- Boundary violation [package:relative-cross-package] packages/ocom-verification/acceptance-ui/src/shared/ocom-component-wrapper.ts:6
- Off the main sequence: @cellix/graphql-core
- Off the main sequence: @cellix/ui-core
- Off the main sequence: @ocom/service-apollo-server
- Off the main sequence: @ocom/service-otel
- Off the main sequence: @cellix/local-dev
- Off the main sequence: @cellix/service-blob-storage
- Off the main sequence: @ocom/local-dev-config
- Off the main sequence: @cellix/service-queue-storage
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Sync-over-async blocking packages/cellix/archunit-tests/src/checks/frontend-architecture.ts:24
- Sync-over-async blocking packages/cellix/archunit-tests/src/checks/frontend-architecture.ts:29
- Sync-over-async blocking packages/cellix/archunit-tests/src/checks/frontend-architecture.ts:33
- Sync-over-async blocking packages/cellix/archunit-tests/src/checks/frontend-architecture.ts:36
- Sync-over-async blocking packages/cellix/serenity-framework/src/cucumber/screenshot-hooks.ts:41
- Sync-over-async blocking packages/cellix/serenity-framework/src/cucumber/screenshot-hooks.ts:48
- HackComment packages/cellix/event-bus-seedwork-node/src/node-event-bus.ts:111
- HackComment packages/cellix/event-bus-seedwork-node/src/node-event-bus.ts:113
- HackComment packages/cellix/event-bus-seedwork-node/src/node-event-bus.ts:114
- HackComment packages/cellix/event-bus-seedwork-node/src/node-event-bus.ts:115
- Untrusted text written into markup unescaped packages/cellix/server-oauth2-mock-seedwork/src/html-builders.ts:16
- Untrusted text written into markup unescaped packages/cellix/server-oauth2-mock-seedwork/src/html-builders.ts:22
- Untrusted text written into markup unescaped packages/cellix/server-oauth2-mock-seedwork/src/html-builders.ts:36
- Untrusted text written into markup unescaped REDACTED:155
- REDACTED
- REDACTED
- REDACTED
- Workspace package's tests never run by CI packages/ocom/ui-community-shared/package.json:14
- Workspace package's tests never run by CI packages/ocom/ui-staff-route-user-management/package.json:15
- Workspace package's tests never run by CI packages/ocom/ui-staff-shared/package.json:14
- Duplicated block with local edits (35 matched lines × 2 locations) packages/ocom/domain/src/domain/iam/guest/guest.passport.ts:15
- Duplicated block with local edits (35 matched lines × 2 locations) packages/ocom/domain/src/domain/iam/member/member.passport.ts:16
- Duplicated block with local edits (35 matched lines × 2 locations) packages/ocom/ui-staff-route-user-management/src/components/staff-roles-list.tsx:38
- <Select> field component without a label packages/ocom/ui-community-route-admin/src/components/members-list.tsx:234
- <Select> field component without a label packages/ocom/ui-staff-route-user-management/src/components/staff-user-detail.tsx:94
- Page without a main landmark apps/ui-community/index.html:2
- Page without a main landmark apps/ui-staff/index.html:2
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- CI test gate excludes suites by filter build-pipeline/core/monorepo-build-stage.yml:245
- CI test gate excludes suites by filter build-pipeline/core/monorepo-build-stage.yml:251
- Duplication concentrated across 4 sibling directories (7 clone groups) packages/ocom/domain/src/domain/contexts/user/end-user/end-user.ts:11
- Duplication concentrated across 4 sibling directories (7 clone groups) packages/ocom/persistence/src/datasources/domain/user/staff-user/staff-user.domain-adapter.ts:55
- Duplication concentrated across 2 sibling directories (5 clone groups) apps/ui-community/src/App.tsx:20
- Duplication concentrated across 2 sibling directories (5 clone groups) packages/ocom-verification/acceptance-api/src/contexts/staff/step-definitions/staff-landing.steps.ts:41
- Duplicated block (39 lines × 2 locations) packages/ocom/ui-community-route-admin/src/components/members-accounts-add.tsx:7
- Duplicated block (39 lines × 2 locations) packages/ocom/ui-community-route-admin/src/sub-page-layout.tsx:12
- Duplicated block with local edits (33 matched lines × 2 locations) packages/ocom/domain/src/domain/iam/guest/guest.passport.ts:14
- Duplicated block with local edits (33 matched lines × 2 locations) packages/ocom/domain/src/domain/iam/system/system.passport.ts:14
- This test file cannot be loaded packages/cellix/archunit-tests/src/typescript-config-conventions.test.ts:8
- This test file cannot be loaded packages/ocom-verification/archunit-tests/src/typescript-config-conventions.test.ts:8
- <Input> field component without a label packages/ocom/ui-community-route-admin/src/components/members-list.tsx:226
- Accessibility enforcement below the top rung REDACTED:72
- No data-protection/encryption packages/ocom/data-sources-mongoose-models/src/models/user/end-user.model.ts:72
- router.buildOidcRouter (cyclomatic 71) REDACTED:44
- login-handlers.createLoginHandlers.registerRoutes (cyclomatic 62) REDACTED:63
- section-layout.SectionLayout (cyclomatic 40) packages/ocom/ui-staff-shared/src/section-layout.tsx:37
- members-list.container.MemberListContainer (cyclomatic 37) packages/ocom/ui-community-route-admin/src/components/members-list.container.tsx:21
- theme-context.ThemeProvider (cyclomatic 34) apps/ui-staff/src/contexts/theme-context.tsx:34
- file-user-store.createFileUserStore.validateEntries (cyclomatic 25) packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:119
- staff-user-detail.container.StaffUserDetailContainer (cyclomatic 24) packages/ocom/ui-staff-route-user-management/src/components/staff-user-detail.container.tsx:32
- member-management.updateMemberProfile.<returned closure> (cyclomatic 22) packages/ocom/application-services/src/contexts/community/member/member-management.ts:514
- members-list.MemberList (cyclomatic 21) packages/ocom/ui-community-route-admin/src/components/members-list.tsx:59
- parse-tool-call.main (cyclomatic 21) .github/hooks/parse-tool-call.py:67
- detect-changes.detectChanges (cyclomatic 20) build-pipeline/scripts/detect-changes.cjs:137
- theme-context.ThemeProvider (cyclomatic 18) apps/ui-community/src/contexts/theme-context.tsx:39
- use-staff-permissions.useStaffPermissions (cyclomatic 18) apps/ui-staff/src/hooks/use-staff-permissions.ts:81
- App.StaffRoutes (cyclomatic 18) apps/ui-staff/src/App.tsx:20
- members-accounts-edit.container.MembersAccountsEditContainer (cyclomatic 17) packages/ocom/ui-community-route-admin/src/components/members-accounts-edit.container.tsx:23
- manager.createMockOAuth2Manager.ensureStarted (cyclomatic 16) packages/cellix/server-oauth2-mock-seedwork/src/manager.ts:38
- members-invite-modal.container.MembersInviteModalContainer (cyclomatic 16) packages/ocom/ui-community-route-admin/src/components/members-invite-modal.container.tsx:14
- router.buildOidcRouter (cognitive 92) REDACTED:44
- login-handlers.createLoginHandlers.registerRoutes (cognitive 72) REDACTED:63
- file-user-store.createFileUserStore.validateEntries (cognitive 40) packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:119
- section-layout.SectionLayout (cognitive 40) packages/ocom/ui-staff-shared/src/section-layout.tsx:37
- members-list.container.MemberListContainer (cognitive 40) packages/ocom/ui-community-route-admin/src/components/members-list.container.tsx:21
- theme-context.ThemeProvider (cognitive 39) apps/ui-staff/src/contexts/theme-context.tsx:34
- parse-tool-call.main (cognitive 37) .github/hooks/parse-tool-call.py:67
- detect-changes.detectChanges (cognitive 23) build-pipeline/scripts/detect-changes.cjs:137
- merge-coverage.mergeLcovFiles (cognitive 23) build-pipeline/scripts/merge-coverage.js:32
- member-management.updateMemberProfile.<returned closure> (cognitive 21) packages/ocom/application-services/src/contexts/community/member/member-management.ts:514
- members-list.MemberList (cognitive 21) packages/ocom/ui-community-route-admin/src/components/members-list.tsx:59
- member-profile.MemberProfile (cognitive 20) packages/ocom/ui-community-shared/src/components/member-profile.tsx:28
- staff-user-detail.container.StaffUserDetailContainer (cognitive 20) packages/ocom/ui-staff-route-user-management/src/components/staff-user-detail.container.tsx:32
- InternalQueueStorageService.startUp (cognitive 19) packages/cellix/service-queue-storage/src/internal-queue-storage-service.ts:144
- members-accounts-edit.container.MembersAccountsEditContainer (cognitive 19) packages/ocom/ui-community-route-admin/src/components/members-accounts-edit.container.tsx:23
- members-invite-modal.container.MembersInviteModalContainer (cognitive 19) packages/ocom/ui-community-route-admin/src/components/members-invite-modal.container.tsx:14
- check-sonar-quality-gate.pollTaskStatus (cognitive 18) build-pipeline/scripts/check-sonar-quality-gate.cjs:63
- index.buildApplicationServicesFactory.forRequest (cognitive 18) packages/ocom/application-services/src/index.ts:46
- theme-context.ThemeProvider (cognitive 17) apps/ui-community/src/contexts/theme-context.tsx:39
- manager.createMockOAuth2Manager.ensureStarted (cognitive 17) packages/cellix/server-oauth2-mock-seedwork/src/manager.ts:38
- portal-discovery.discoverPortalConfigs (cognitive 17) packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:112
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Both branches are identical — the condition decides nothing REDACTED:173
- Duplication concentrated across 5 sibling directories (29 clone groups) packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role-property-permissions.ts:7
- Duplication concentrated across 13 sibling directories (22 clone groups) packages/ocom/ui-community-route-admin/src/sub-page-layout.tsx:12
- Duplication concentrated across 5 sibling directories (17 clone groups) packages/ocom/persistence/src/datasources/domain/case/service-ticket-v1/service-ticket-v1.domain-adapter.ts:232
- Duplication concentrated across 2 sibling directories (9 clone groups) apps/ui-community/src/contexts/theme-context.tsx:11
- Duplication concentrated across 4 sibling directories (9 clone groups) packages/ocom/domain/src/domain/iam/guest/guest.passport.ts:14
- Duplication concentrated across 2 sibling directories (8 clone groups) packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:45
- Duplication concentrated across 2 sibling directories (7 clone groups) packages/ocom/application-services/src/contexts/community/community/update-settings.ts:18
- Duplication concentrated across 2 sibling directories (6 clone groups) packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role.ts:25
- Duplication concentrated across 3 sibling directories (5 clone groups) packages/ocom-verification/acceptance-ui/src/contexts/staff-role/abilities/mock-staff-role-backend.ts:14
- Duplicated block with local edits (220 matched lines × 2 locations) packages/ocom/persistence/src/datasources/domain/community/role/end-user-role/end-user-role.domain-adapter.ts:18
- Duplicated block with local edits (122 matched lines × 2 locations) packages/cellix/serenity-framework/src/infrastructure/api-infrastructure.ts:96
- Duplicated block with local edits (113 matched lines × 2 locations) apps/ui-community/src/contexts/theme-context.tsx:11
- Wholesale file copy (94 identical lines × 2 files) packages/ocom/data-sources-mongoose-models/src/models/role/end-user-role.model.ts:1
- Duplicated block with local edits (86 matched lines × 2 locations) packages/ocom/ui-staff-route-user-management/src/components/staff-role-create.container.tsx:15
- Duplicated block with local edits (73 matched lines × 2 locations) packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role.ts:25
- Duplicated block (72 lines × 2 locations) packages/ocom/data-sources-mongoose-models/src/models/user/end-user.model.ts:27
- Duplicated block with local edits (70 matched lines × 2 locations) packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:45
- Duplicated block with local edits (63 matched lines × 2 locations) REDACTED:76
- Duplicated block with local edits (54 matched lines × 2 locations) packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1-message.entity.ts:11
- Duplicated block with local edits (53 matched lines × 2 locations) packages/ocom/domain/src/domain/contexts/user/end-user/end-user.ts:11
- Duplicated block (43 lines × 2 locations) packages/ocom/data-sources-mongoose-models/src/models/case/service-ticket.model.ts:33
- Duplicated block (42 lines × 2 locations) packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role-service-ticket-permissions.ts:7
- Duplicated block with local edits (38 matched lines × 2 locations) packages/ocom/persistence/src/datasources/domain/user/staff-user/staff-user.domain-adapter.ts:55
- Duplicated block with local edits (37 matched lines × 2 locations) packages/ocom/domain/src/domain/iam/guest/guest.passport.ts:14
- Duplicated block (36 lines × 2 locations) packages/ocom/ui-community-route-admin/src/section-layout.tsx:88
- Duplicated block (34 lines × 2 locations) packages/ocom/ui-community-route-root/src/components/header.tsx:6
- Duplicated block with local edits (32 matched lines × 2 locations) packages/ocom/domain/src/domain/iam/member/member.passport.ts:16
- Duplicated block with local edits (31 matched lines × 2 locations) packages/ocom-verification/acceptance-api/src/contexts/staff/step-definitions/staff-landing.steps.ts:41
- Duplicated block (30 lines × 2 locations) packages/ocom/domain/src/domain/contexts/property/property/property-listing-detail-additional-amenity.entity.ts:7
- Complex function SectionLayout (cyclomatic 37, cognitive 37) packages/ocom/ui-staff-shared/src/section-layout.tsx:37
- Complex function validateEnvNames (cyclomatic 33, cognitive 59) packages/ocom-verification/archunit-tests/src/validate-env-names.cjs:286
- Complex function (anonymous) (cyclomatic 29, cognitive 37) REDACTED:103
- Complex function checkFrontendArchitecture (cyclomatic 27, cognitive 32) packages/cellix/archunit-tests/src/checks/frontend-architecture.ts:12
- Complex function validateEntries (cyclomatic 26, cognitive 42) packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:119
- Complex function (anonymous) (cyclomatic 26, cognitive 31) packages/ocom-verification/e2e-tests/src/contexts/community/tasks/create-community.ts:58
- Complex function checkLayeredArchitecture (cyclomatic 25, cognitive 36) packages/cellix/archunit-tests/src/checks/circular-dependencies.ts:50
- Complex function (anonymous) (cyclomatic 22, cognitive 30) REDACTED:134
- Complex function StaffUserDetailContainer (cyclomatic 22, cognitive 18) packages/ocom/ui-staff-route-user-management/src/components/staff-user-detail.container.tsx:32
- Complex function (anonymous) (cyclomatic 21, cognitive 24) REDACTED:244
- Complex function (anonymous) (cyclomatic 21, cognitive 20) packages/ocom/application-services/src/contexts/community/member/member-management.ts:517
- Complex function detectChanges (cyclomatic 20, cognitive 23) build-pipeline/scripts/detect-changes.cjs:137
- Complex function (anonymous) (cyclomatic 19, cognitive 13) apps/ui-staff/src/hooks/use-staff-permissions.ts:87
- Complex function skipTemplateExpression (cyclomatic 18, cognitive 27) packages/ocom-verification/archunit-tests/src/validate-env-names.cjs:44
- Complex function StaffRoutes (cyclomatic 18, cognitive 10) apps/ui-staff/src/App.tsx:20
- Complex function (anonymous) (cyclomatic 17, cognitive 25) REDACTED:241
- Complex function (anonymous) (cyclomatic 17, cognitive 24) apps/ui-staff/src/contexts/theme-context.tsx:92
- Complex function findEnvVarsInText (cyclomatic 15, cognitive 21) packages/ocom-verification/archunit-tests/src/validate-env-names.cjs:204
- Complex function normalizeUserInfo (cyclomatic 15, cognitive 17) packages/cellix/server-oauth2-mock-seedwork/src/helpers.ts:38
- packages/ocom/graphql/src/schema/types/member.resolvers.ts: 700 lines of code packages/ocom/graphql/src/schema/types/member.resolvers.ts:1
- packages/ocom/persistence/src/datasources/domain/property/property/property.domain-adapter.ts: 527 lines of code packages/ocom/persistence/src/datasources/domain/property/property/property.domain-adapter.ts:1
- packages/ocom/application-services/src/contexts/community/member/member-management.ts: 444 lines of code packages/ocom/application-services/src/contexts/community/member/member-management.ts:1
- packages/ocom/persistence/src/datasources/domain/user/staff-role/staff-role.domain-adapter.ts: 430 lines of code packages/ocom/persistence/src/datasources/domain/user/staff-role/staff-role.domain-adapter.ts:1
- The declared test suite includes a file that cannot be loaded packages/cellix/archunit-tests/src/typescript-config-conventions.test.ts:8
- Dead file (~86 LoC) build-pipeline/scripts/get-pr-number.cjs
- Dead file (~26 LoC) packages/ocom/graphql/src/schema/types/end-user-role.resolvers.ts
- Unused dependency '@ant-design/cli'
- Unused dependency '@graphql-codegen/introspection'
- Unused dependency '@graphql-codegen/typed-document-node'
Minor — 266 finding(s)
- Orphaned file packages/ocom/ui-community-route-admin/src/components/members-list.tsx:1
- Orphaned file packages/ocom/ui-community-route-admin/src/components/members-list.container.tsx:1
- Orphaned file packages/ocom/ui-staff-shared/src/section-layout.tsx:1
- Orphaned file packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role.ts:1
- Orphaned file packages/ocom/ui-staff-shared/src/section-layout.stories.tsx:1
- Orphaned file packages/ocom/ui-staff-route-user-management/src/components/staff-role-create.tsx:1
- Orphaned file packages/ocom/domain/src/domain/contexts/user/staff-user/staff-user.ts:1
- Orphaned file packages/ocom/ui-staff-route-user-management/src/components/staff-role-edit.container.tsx:1
- Orphaned file packages/ocom/domain/src/domain/contexts/community/member/member-invitation.ts:1
- Orphaned file packages/ocom/ui-community-route-admin/src/components/members-invite-modal.tsx:1
- Orphaned file packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role-permissions.ts:1
- Orphaned file packages/ocom/ui-staff-route-user-management/src/components/staff-user-detail.container.tsx:1
- Orphaned file packages/cellix/event-bus-seedwork-node/src/node-event-bus.ts:1
- Orphaned file apps/ui-staff/src/contexts/theme-context.tsx:1
- Orphaned file packages/ocom/ui-community-route-admin/src/components/members-list.stories.tsx:1
- Orphaned file packages/ocom/ui-staff-route-user-management/src/components/staff-role-create.container.tsx:1
- Orphaned file packages/ocom/persistence/src/datasources/readonly/community/community/community.read-repository.ts:1
- Orphaned file packages/ocom/data-sources-mongoose-models/src/models/role/vendor-user-role.model.ts:1
- Orphaned file packages/ocom/service-otel/src/otel-builder.ts:1
- Orphaned file packages/ocom/data-sources-mongoose-models/src/models/role/end-user-role.model.ts:1
- Orphaned file packages/ocom/ui-community-route-admin/src/components/members-accounts-edit.container.tsx:1
- Orphaned file packages/ocom/ui-community-shared/src/components/member-profile.tsx:1
- Orphaned file packages/ocom/ui-community-route-admin/src/section-layout.stories.tsx:1
- Orphaned file packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role.ts:1
- Orphaned file packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role-permissions.ts:1
- redundant comment apps/ui-community/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx:27
- redundant comment apps/ui-community/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx:82
- redundant comment apps/ui-staff/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx:27
- redundant comment apps/ui-staff/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx:56
- redundant comment build-pipeline/scripts/detect-changes.cjs:154
- redundant comment build-pipeline/scripts/merge-coverage.js:102
- redundant comment packages/cellix/server-oauth2-mock-seedwork/tests/multi-registration.test.ts:94
- redundant comment packages/cellix/service-blob-storage/src/client-upload-signer.auth-header.test.ts:186
- redundant comment packages/cellix/service-blob-storage/src/client-upload-signer.auth-header.test.ts:194
- redundant comment packages/ocom/application-services/src/contexts/community/member/create-member.test.ts:123
- redundant comment packages/ocom/application-services/src/contexts/community/member/create-member.test.ts:133
- redundant comment packages/ocom/application-services/src/contexts/community/member/create-member.test.ts:197
- redundant comment packages/ocom/application-services/src/contexts/community/member/create-member.test.ts:200
- redundant comment packages/ocom/application-services/src/contexts/community/member/member-management.ts:38
- redundant comment packages/ocom/application-services/src/contexts/community/member/member-management.ts:493
- redundant comment packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1-activity-detail.value-objects.test.ts:82
- redundant comment packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1-activity-detail.value-objects.test.ts:82
- redundant comment packages/ocom/domain/src/domain/contexts/community/community/community.value-objects.test.ts:195
- redundant comment packages/ocom/domain/src/domain/contexts/community/member/member-account.value-objects.test.ts:174
- redundant comment packages/ocom/domain/src/domain/contexts/community/member/member-custom-view.value-objects.test.ts:13
- redundant comment packages/ocom/domain/src/domain/contexts/community/member/member.value-objects.test.ts:103
- redundant comment packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role-community-permissions.test.ts:59
- redundant comment packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role-community-permissions.test.ts:58
- redundant comment packages/ocom/domain/src/domain/contexts/property/property/property-listing-detail.value-objects.test.ts:252
- redundant comment packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role-community-permissions.test.ts:51
- Classify ADR enforcement: Use Markdown Any Decision Records (MADR) to track Architectural Decisions apps/docs/docs/decisions/0001-madr-architecture-decisions.md
- Classify ADR enforcement: Use Open Telemetry to add observability to the project apps/docs/docs/decisions/0002-open-telemetry.md
- Classify ADR enforcement: Use DDD Framework to build the data-access project apps/docs/docs/decisions/0003-domain-driven-design.md
- Classify ADR enforcement: Use of Azure Active Directory (AAD) and Azure Active Directory B2C (AAD B2C) for Identity and Access Control apps/docs/docs/decisions/0004-identity-access.md
- Classify ADR enforcement: Use Passport/Visa for Access Management apps/docs/docs/decisions/0005-authorization.md
- Classify ADR enforcement: Use Maps for the project apps/docs/docs/decisions/0006-maps.md
- Classify ADR enforcement: Use SerenityJS to ensure delivering right features apps/docs/docs/decisions/0007-serenityjs.md
- Classify ADR enforcement: White label website using CraftJs + Blob Storage and Vercel apps/docs/docs/decisions/0008-white-label.md
- Classify ADR enforcement: Automatically Refresh Screen on Application Update apps/docs/docs/decisions/0009-cache-purging.md
- Classify ADR enforcement: React Router Loader apps/docs/docs/decisions/0010-react-router-loaders.md
- Classify ADR enforcement: Using Bicep for Infrastructure as Code instead of manual configuration of environments apps/docs/docs/decisions/0011-bicep.md
- Classify ADR enforcement: Select a Linter: Oxlint vs Biome apps/docs/docs/decisions/0012-linter.md
- Classify ADR enforcement: Select a Test Suite: Jest vs Vitest vs Node apps/docs/docs/decisions/0013-test-suite.md
- Classify ADR enforcement: Select a Deployment Approach: AVM vs Bicep apps/docs/docs/decisions/0014-azure-infrastructure-deployments.md
- Classify ADR enforcement: Addressing Node.js 16 End-of-Life in SonarCloud apps/docs/docs/decisions/0015-sonarcloud.md
- Classify ADR enforcement: Bypassing SonarCloud Code Duplication Checks for Unit Tests apps/docs/docs/decisions/0016-sonarcloud-code-duplication-checks.md
- Classify ADR enforcement: Chrome Content Overrides for FeatureFlags.json apps/docs/docs/decisions/0017-chrome-content-overrides.md
- Classify ADR enforcement: Split Docusaurus Azure Pipeline into Separate Build and Deploy Stages apps/docs/docs/decisions/0018-docusaurus-azure-pipeline-stages.md
- Classify ADR enforcement: Monorepo Structure with Turborepo apps/docs/docs/decisions/0019-monorepo-turborepo.md
- Classify ADR enforcement: Azure DevOps Monorepo Pipeline Architecture apps/docs/docs/decisions/0020-azure-devops-monorepo-pipeline.md
- Classify ADR enforcement: Bicep Resource Scoping Strategy apps/docs/docs/decisions/0021-bicep-resource-scoping-strategy.md
- Classify ADR enforcement: Integrate Snyk for Security Scanning at Inception apps/docs/docs/decisions/0022-snyk-security-integration.md
- Classify ADR enforcement: TypeScript Go (tsgo) Migration apps/docs/docs/decisions/0023-tsgo-migration.md
- Classify ADR enforcement: Adopt Agent Skills Framework to Enforce MADR Standards in Code apps/docs/docs/decisions/0024-madr-agent-skills.md
- Classify ADR enforcement: Adopt Rolldown for Azure Functions API Applications and Static GraphQL Code Generation apps/docs/docs/decisions/0025-rolldown-azure-functions-graphql-codegen.md
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:77
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:94
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:108
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:124
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:134
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:148
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:155
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:165
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:172
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:179
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:188
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:290
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:293
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:321
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/logger.ts:20
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/logger.ts:22
- Console output used as the logging channel REDACTED:150
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/manager.ts:74
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/manager.ts:75
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:19
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:108
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:135
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:142
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:163
- Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:180
- Duplicated predicate apps/ui-community/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx:34
- Duplicated predicate apps/ui-community/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx:85
- Duplicated predicate packages/ocom-verification/acceptance-api/src/contexts/community/step-definitions/create-community.steps.ts:98
- Duplicated predicate apps/ui-staff/src/App.tsx:34
- Duplicated predicate apps/ui-community/src/contexts/theme-context.tsx:169
- Duplicated predicate packages/ocom/domain/src/domain/contexts/community/member/member-invitation.ts:69
- Duplicated predicate packages/ocom/ui-community-route-admin/src/components/members-accounts-add.tsx:16
- Duplicated predicate .agents/skills/cellix-tdd/evaluator/evaluate-cellix-tdd.ts:789
- Duplicated predicate packages/ocom/application-services/src/contexts/user/staff-role/create-default-roles.ts:13
- Duplicated predicate apps/ui-community/src/contexts/theme-context.tsx:148
- Duplicated predicate apps/ui-community/src/contexts/theme-context.tsx:122
- Duplicated predicate apps/ui-community/src/contexts/theme-context.tsx:104
- Duplicated predicate apps/ui-community/src/contexts/theme-context.tsx:113
- Duplicated predicate packages/ocom/ui-staff-shared/src/section-layout.container.tsx:26
- Duplicated predicate packages/ocom-verification/acceptance-api/src/contexts/staff/step-definitions/staff-landing.steps.ts:26
- Duplicated predicate packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role-community-permissions.ts:24
- Duplicated predicate packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role-community-permissions.ts:27
- Duplicated predicate packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:142
- Duplicated predicate packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1-message.entity.ts:50
- Duplicated predicate packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role-community-permissions.ts:19
- Duplicated predicate packages/ocom/domain/src/domain/contexts/user/end-user/end-user-contact-information.ts:26
- Duplicated predicate packages/ocom/domain/src/domain/contexts/user/vendor-user/vendor-user-contact-information.ts:36
- Duplicated predicate packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:123
- Duplicated predicate packages/ocom/domain/src/domain/contexts/property/property/property-listing-detail-additional-amenity.entity.ts:22
- Duplicated predicate packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:155
- Primitive id on a domain type: DomainEventBase.aggregateId packages/cellix/domain-seedwork/src/domain-seedwork/domain-event.ts:16
- Primitive id on a domain type: EndUser.externalId packages/ocom/domain/src/domain/contexts/user/end-user/end-user.ts:93
- Primitive id on a domain type: Member.cybersourceCustomerId packages/ocom/domain/src/domain/contexts/community/member/member.ts:212
- Primitive id on a domain type: Member.communityId packages/ocom/domain/src/domain/contexts/community/member/member.ts:221
- Primitive id on a domain type: StaffUser.externalId packages/ocom/domain/src/domain/contexts/user/staff-user/staff-user.ts:149
- Primitive id on a domain type: VendorUser.externalId packages/ocom/domain/src/domain/contexts/user/vendor-user/vendor-user.ts:97
- Primitive id on a domain type: ViolationTicketV1.communityId packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1.aggregate.ts:209
- Primitive id on a domain type: ViolationTicketV1.requestorId packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1.aggregate.ts:231
- Primitive id on a domain type: MemberInvitation.communityId packages/ocom/domain/src/domain/contexts/community/member/member-invitation.ts:173
- Primitive id on a domain type: ServiceTicketV1.communityId packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:234
- Primitive id on a domain type: ServiceTicketV1.requestorId packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:256
- Primitive id on a domain type: ServiceTicketV1.assignedToId packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:267
- Primitive id on a domain type: ServiceTicketV1.serviceId packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:278
- ADR has no Consequences section apps/docs/docs/decisions/0002-open-telemetry.md:14
- ADR has no Consequences section apps/docs/docs/decisions/0004-identity-access.md:13
- ADR has no Consequences section apps/docs/docs/decisions/0005-authorization.md:14
- ADR has no Consequences section apps/docs/docs/decisions/0006-maps.md:13
- ADR has no Consequences section apps/docs/docs/decisions/0007-serenityjs.md:14
- Mock-dominated test: removes a member through domain operation packages/ocom/application-services/src/contexts/community/member/member-management.operations.test.ts:138
- Mock-dominated test: passes reason to bulk deactivate and bulk remove domain methods packages/ocom/application-services/src/contexts/community/member/member-management.operations.test.ts:149
- Mock-dominated test: starts infrastructure, validates state, creates the cast, and resets during cleanup packages/cellix/serenity-framework/src/cucumber/world.test.ts:6
- Mock-dominated test: allows additional handlers after the first registration packages/cellix/api-core/tests/cellix.test.ts:222
- README/code drift packages/cellix/domain-seedwork/readme.md:11
- README/code drift packages/ocom/ui-staff-shared/README.md:172
- README/code drift packages/cellix/mongoose-seedwork/src/mongoose-seedwork/README.md:11
- README/code drift packages/cellix/ui-core/src/components/molecules/README.md:18
- REDACTED
- REDACTED
- REDACTED
- Documentation: no build, run or usage example apps/api/readme.md:1
- Documentation: no build, run or usage example apps/ui-staff/README.md:1
- ADR considers only one option apps/docs/docs/decisions/0005-authorization.md:30
- ADR considers only one option apps/docs/docs/decisions/0009-cache-purging.md:27
- ADR consequences name no cost apps/docs/docs/decisions/0027-typescript-6-upgrade.md:36
- ADR consequences name no cost apps/docs/docs/decisions/0030-typescript-7-upgrade.md:36
- ADR decides a question another record already decided apps/docs/docs/decisions/0004-identity-access.md:13
- ADR decides a question another record already decided apps/docs/docs/decisions/0006-maps.md:13
- No app-layer HTTPS enforcement detected packages/cellix/server-oauth2-mock-seedwork/src/manager.ts:73
- No app-layer HTTPS enforcement detected packages/cellix/server-oauth2-mock-seedwork/src/server.ts:33
- Silent fallback default in catch packages/ocom-verification/acceptance-ui/src/contexts/staff-role/questions/staff-role-screen.ts:49
- Silent fallback default in catch packages/ocom-verification/acceptance-ui/src/contexts/staff-role/questions/staff-role-screen.ts:67
- Fat interface: MemberApplicationService (18 required operations) packages/ocom/application-services/src/contexts/community/member/index.ts:38
- No named authorization policies packages/cellix/serenity-framework/src/infrastructure/api-infrastructure.ts:210
- Off-boarding risk: anonymized user #1
- Projects may be oversized for their cohesion
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- Empty method body packages/ocom/ui-community-route-accounts/.storybook/preview.tsx:15
- Logging is not universal
- No dependency-update automation REDACTED:72
- Unused export 'GetModelFunction' packages/cellix/mongoose-seedwork/src/mongoose-seedwork/mongo-connection.ts:6
- Unused export 'GetModelFunctionWithSchema' packages/cellix/mongoose-seedwork/src/mongoose-seedwork/mongo-connection.ts:7
- Type-only dependency 'mongoose' in production deps apps/server-mongodb-memory-mock/src/seed/seed.ts:8
- Test-only dependency '@ant-design/icons' in production deps packages/ocom/ui-shared/package.json:32
- Strict null checking is not enabled everywhere the repository type-checks
Minor — 6 finding(s)
- doc comments repeat the names packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:35
- doc comments repeat the names packages/cellix/ui-core/src/components/molecules/component-query-loader/index.tsx:5
- doc comments repeat the names packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1-message.entity.ts:9
- doc comments repeat the names packages/ocom/graphql-handler/src/handler.ts:10
- doc comments repeat the names packages/ocom/service-apollo-server/src/index.ts:29
- Off the main sequence: @ocom/ui-staff-shared
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ecd2d2f96233407da50c00128e2e7c95/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ecd2d2f96233407da50c00128e2e7c95/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/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 25 | 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 | 52 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 11 | 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 44 file(s) — `apps/docs/docusaurus.config.ts`, `apps/docs/sidebars.ts`, `apps/ui-community/src/App.stories.tsx`, `apps/ui-community/src/components/ui/molecules/auth-landing/auth-landing.stories.tsx`, `apps/ui-community/src/components/ui/organisms/apollo-connection/apollo-client-links.stories.tsx`, … (+39 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 |