Public report of CellixJs/cellixjs, published 8 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.2). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 8 November 2026, 01:34 UTC · Survey ID cd_0f24391c33514015854ef11719e47655

CellixJs/cellixjs

Measured 8 November 2026, 01:34 UTC, at code version 0dda578

CAI score 47out of 100 At risk Down 1 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A medium codebase: 43,941 lines of product code in 51 projects, tests not counted · Estimated rebuild effort: about 0.9 person-years · Weakest lens: Production Readiness, 44

Findings by how serious they are

58 critical 330 serious 272 minor

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

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
8 November 2026, 01:34 UTC

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

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

92of 92 dimensions measured by tools.
639of 660 findings point to an exact file and line, so you can open each one in the code. The other 21 concern the repository as a whole, such as missing documentation.
92dimensions across 8 lenses, read from 43,941 lines of product code in 51 projects.
Chapters

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.

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

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 44 · counts for 45%Accessibility 45 · counts for 25%Security and Compliance 48 · counts for 14%Domain Modelling 51 · counts for 8%Architecture 55 · counts for 4%Performance 60 · counts for 2%Code Health 63 · counts for 1%Maturity 87 · counts for 1%

The weakest lenses score close to each other, so improving any of them moves the score.

Code composition: what the lines of code are
Product code 42%Tests 58%
New since the last survey: 33 findings

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

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

Fixed since the last survey: 205 findings

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

  • 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 problemHigh, 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.
SizeMedium: 43,941 lines of product code
What it is notNot 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.

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

Top priorities

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

1
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.
Raises the score by about 3 points · Low effort · Secret Scanning
2
Resolve the 7 No assertions (empty test) finding(s) in Test Quality — start with mongo-unit-of-work.integration.test.ts (7).
Raises the score by about 2 points · Low effort · Test Quality
3
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
Raises the score by about 2 points · Medium effort · Dependency Hygiene

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €130,000 to build again, about 0.9 person-years of work. Its weakest lens is Production Readiness, at 44 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
One cause behind 37 Domain Modelling findings · Common cause
37 findings in the Domain Modelling lens come from the same cause. The code models the business as objects, such as an order or a customer, and each object should guard its own rules: an order, for example, should refuse to be shipped before it has been paid. Here the objects don't do that. Other code can change an object's data directly, so it can put an order into a state the rules forbid. Some objects only hold data, while the rules that should keep that data valid sit elsewhere in the code. Identifiers, such as order numbers and customer numbers, are passed around as plain numbers or text, so nothing stops the code from using one kind where another belongs. Because all of these findings have the same cause, fixing it once, in the business objects themselves, deals with them together.
Based on: Encapsulated state (13 findings) · Rich vs anemic model (11 findings) · Strongly-typed ids (13 findings)
What to do: Give each business object the methods that enforce its rules, such as a method for shipping an order that first checks it has been paid, and let only those methods change its data. Give each kind of identifier a type of its own, so an order number can't be used where a customer number belongs.
If you do one thing first · First action
Resolve the 1 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 3 points for low effort, because it clears the 1 Secret Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch @apps/api api @cellix/mongoose-seedwork mongoose-seedwork @apps/api->@cellix/mongoose-seedwork @ocom/application-services application-services @apps/api->@ocom/application-services @ocom/graphql graphql @apps/api->@ocom/graphql @ocom/graphql-handler graphql-handler @apps/api->@ocom/graphql-handler @ocom/persistence persistence @apps/api->@ocom/persistence @apps/ui-community ui-community @cellix/ui-core ui-core @apps/ui-community->@cellix/ui-core @ocom/local-dev-config local-dev-config @apps/ui-community->@ocom/local-dev-config @ocom/ui-community-route-accounts ui-community-route-accounts @apps/ui-community->@ocom/ui-community-route-accounts @ocom/ui-community-route-admin ui-community-route-admin @apps/ui-community->@ocom/ui-community-route-admin @ocom/ui-community-shared ui-community-shared @apps/ui-community->@ocom/ui-community-shared @apps/ui-staff ui-staff @apps/ui-staff->@cellix/ui-core @apps/ui-staff->@ocom/local-dev-config @ocom/ui-shared ui-shared @apps/ui-staff->@ocom/ui-shared @ocom/ui-staff-shared ui-staff-shared @apps/ui-staff->@ocom/ui-staff-shared @cellix/domain-seedwork domain-seedwork @cellix/event-bus-seedwork-node event-bus-seedwork-node @cellix/event-bus-seedwork-node->@cellix/domain-seedwork @cellix/mongoose-seedwork->@cellix/domain-seedwork @cellix/mongoose-seedwork->@cellix/event-bus-seedwork-node @cellix/serenity-framework serenity-framework @ocom/domain domain @ocom/application-services->@ocom/domain @ocom/application-services->@ocom/persistence @ocom/data-sources-mongoose-models data-sources-mongoose-models @ocom/data-sources-mongoose-models->@cellix/mongoose-seedwork @ocom/domain->@cellix/domain-seedwork @ocom/domain->@cellix/event-bus-seedwork-node @ocom/graphql->@ocom/application-services @ocom/graphql->@ocom/domain @ocom/graphql-handler->@ocom/application-services @ocom/graphql-handler->@ocom/graphql @ocom/persistence->@cellix/domain-seedwork @ocom/persistence->@cellix/event-bus-seedwork-node @ocom/persistence->@cellix/mongoose-seedwork @ocom/persistence->@ocom/data-sources-mongoose-models @ocom/persistence->@ocom/domain @ocom/ui-community-route-accounts->@cellix/ui-core @ocom/ui-community-route-accounts->@ocom/ui-community-shared @ocom/ui-community-route-accounts->@ocom/ui-shared @ocom/ui-community-route-admin->@cellix/ui-core @ocom/ui-community-route-admin->@ocom/ui-community-shared @ocom/ui-community-route-admin->@ocom/ui-shared @ocom/ui-community-shared->@cellix/ui-core @ocom/ui-community-shared->@ocom/ui-shared @ocom/ui-shared->@cellix/ui-core @ocom/ui-staff-shared->@cellix/ui-core @ocom/ui-staff-shared->@ocom/ui-shared __more__ +30 more projects

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

617 modules, with 809 dependencies between them. One loop runs through 68 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 577 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 cellix.domain-seedwork.src.domain-seedwork.domain-event2 cellix.domain-seedwork.src.domain-seedwork.prop-array3 ocom.application-services.src4 ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_visa5 ocom.domain.src.domain.contexts.community.community_visa6 ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects7 ocom.domain.src.domain.contexts.property.property_visa8 ocom.domain.src.domain.contexts.user.user_visa9 cellix.domain-seedwork.src.domain-seedwork.value-object10 ocom.domain.src.domain.contexts.community.community.community11 ocom.domain.src.domain.contexts.user.vendor-user.vendor-user12 ocom.domain.src.domain.contexts.community.community_passport13 ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions14 ocom.domain.src.domain.contexts.community.role.vendor-user-role.vendor-user-role-permissions15 ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity16 ocom.domain.src.domain.contexts.service.service.service_aggregate17 ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions18 ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role19 ocom.domain.src.domain.contexts.property.property.property_aggregate20 ocom.domain.src.domain.contexts.service.service_passport21 ocom.domain.src.domain.contexts.user.staff-role.staff-role22 ocom.persistence.src.datasources.domain.property.property.property_domain-adapter23 ocom.persistence.src.datasources.domain.user.staff-role.staff-role_domain-adapter24 ocom.application-services.src.contexts.user.staff-role25 ocom.domain.src.domain.contexts.community.member.member26 ocom.domain.src.domain.contexts.property.property_passport27 ocom.domain.src.domain.contexts.user.staff-user.staff-user28 ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate29 ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate30 ocom.domain.src.domain.contexts.user.user_passport31 ocom.domain.src.domain.contexts.case.case_passport32 ocom.domain.src.domain.contexts.passport33 ocom.domain.src.domain.contexts.user.end-user.end-user34 ocom.application-services.src.contexts.community.member35 ocom.domain.src.domain.iam.member.member_passport-base36 ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport37 ocom.persistence.src.datasources.domain.community.community.community_repository38 cellix.domain-seedwork.src.domain-seedwork.domain-entity39 ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository40 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-object1
10 ocom.domain.src.domain.contexts.community.community.community1121
11 ocom.domain.src.domain.contexts.user.vendor-user.vendor-user111
12 ocom.domain.src.domain.contexts.community.community_passport11
13 ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions11
14 ocom.domain.src.domain.contexts.community.role.vendor-user-role.vendor-user-role-permissions11
15 ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity12511
16 ocom.domain.src.domain.contexts.service.service.service_aggregate411
17 ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions11
18 ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role13211
19 ocom.domain.src.domain.contexts.property.property.property_aggregate13311
20 ocom.domain.src.domain.contexts.service.service_passport1
21 ocom.domain.src.domain.contexts.user.staff-role.staff-role1211
22 ocom.persistence.src.datasources.domain.property.property.property_domain-adapter111
23 ocom.persistence.src.datasources.domain.user.staff-role.staff-role_domain-adapter1
24 ocom.application-services.src.contexts.user.staff-role4
25 ocom.domain.src.domain.contexts.community.member.member113311
26 ocom.domain.src.domain.contexts.property.property_passport11
27 ocom.domain.src.domain.contexts.user.staff-user.staff-user11211
28 ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate11111
29 ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate11111
30 ocom.domain.src.domain.contexts.user.user_passport11111
31 ocom.domain.src.domain.contexts.case.case_passport11
32 ocom.domain.src.domain.contexts.passport11111
33 ocom.domain.src.domain.contexts.user.end-user.end-user111
34 ocom.application-services.src.contexts.community.member21
35 ocom.domain.src.domain.iam.member.member_passport-base111
36 ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport111111
37 ocom.persistence.src.datasources.domain.community.community.community_repository1
38 cellix.domain-seedwork.src.domain-seedwork.domain-entity1
39 ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository111111
40 cellix.domain-seedwork.src.domain-seedwork.aggregate-root111
Uses a module listed above itPart of a loopThe module itself
1 cellix.domain-seedwork.src.domain-seedwork.domain-event2 cellix.domain-seedwork.src.domain-seedwork.prop-array3 ocom.application-services.src4 ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_visa5 ocom.domain.src.domain.contexts.community.community_visa6 ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects7 ocom.domain.src.domain.contexts.property.property_visa8 ocom.domain.src.domain.contexts.user.user_visa9 cellix.domain-seedwork.src.domain-seedwork.value-object10 ocom.domain.src.domain.contexts.community.community.community11 ocom.domain.src.domain.contexts.user.vendor-user.vendor-user12 ocom.domain.src.domain.contexts.community.community_passport13 ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions14 ocom.domain.src.domain.contexts.community.role.vendor-user-role.vendor-user-role-permissions15 ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity16 ocom.domain.src.domain.contexts.service.service.service_aggregate17 ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions18 ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role19 ocom.domain.src.domain.contexts.property.property.property_aggregate20 ocom.domain.src.domain.contexts.service.service_passport21 ocom.domain.src.domain.contexts.user.staff-role.staff-role22 ocom.persistence.src.datasources.domain.property.property.property_domain-adapter23 ocom.persistence.src.datasources.domain.user.staff-role.staff-role_domain-adapter24 ocom.application-services.src.contexts.user.staff-role25 ocom.domain.src.domain.contexts.community.member.member26 ocom.domain.src.domain.contexts.property.property_passport27 ocom.domain.src.domain.contexts.user.staff-user.staff-user28 ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate29 ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate30 ocom.domain.src.domain.contexts.user.user_passport31 ocom.domain.src.domain.contexts.case.case_passport32 ocom.domain.src.domain.contexts.passport33 ocom.domain.src.domain.contexts.user.end-user.end-user34 ocom.application-services.src.contexts.community.member35 ocom.domain.src.domain.iam.member.member_passport-base36 ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport37 ocom.persistence.src.datasources.domain.community.community.community_repository38 cellix.domain-seedwork.src.domain-seedwork.domain-entity39 ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository40 cellix.domain-seedwork.src.domain-seedwork.aggregate-rootcellix.domain-seedwork.src.domain-seedwork.domain-event1cellix.domain-seedwork.src.domain-seedwork.prop-array2ocom.application-services.src3ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_visa4ocom.domain.src.domain.contexts.community.community_visa5ocom.domain.src.domain.contexts.property.property.property-listing-detail_value-objects6ocom.domain.src.domain.contexts.property.property_visa7ocom.domain.src.domain.contexts.user.user_visa8cellix.domain-seedwork.src.domain-seedwork.value-object9ocom.domain.src.domain.contexts.community.community.community10ocom.domain.src.domain.contexts.user.vendor-user.vendor-user11ocom.domain.src.domain.contexts.community.community_passport12ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role-permissions13ocom.domain.src.domain.contexts.community.role.vendor-user-role.vendor-user-role-permissions14ocom.domain.src.domain.contexts.property.property.property-listing-detail_entity15ocom.domain.src.domain.contexts.service.service.service_aggregate16ocom.domain.src.domain.contexts.user.staff-role.staff-role-permissions17ocom.domain.src.domain.contexts.community.role.end-user-role.end-user-role18ocom.domain.src.domain.contexts.property.property.property_aggregate19ocom.domain.src.domain.contexts.service.service_passport20ocom.domain.src.domain.contexts.user.staff-role.staff-role21ocom.persistence.src.datasources.domain.property.property.property_domain-adapter22ocom.persistence.src.datasources.domain.user.staff-role.staff-role_domain-adapter23ocom.application-services.src.contexts.user.staff-role24ocom.domain.src.domain.contexts.community.member.member25ocom.domain.src.domain.contexts.property.property_passport26ocom.domain.src.domain.contexts.user.staff-user.staff-user27ocom.domain.src.domain.contexts.case.service-ticket.v1.service-ticket-v1_aggregate28ocom.domain.src.domain.contexts.case.violation-ticket.v1.violation-ticket-v1_aggregate29ocom.domain.src.domain.contexts.user.user_passport30ocom.domain.src.domain.contexts.case.case_passport31ocom.domain.src.domain.contexts.passport32ocom.domain.src.domain.contexts.user.end-user.end-user33ocom.application-services.src.contexts.community.member34ocom.domain.src.domain.iam.member.member_passport-base35ocom.domain.src.domain.iam.user.staff-user.contexts.staff-user_user_passport36ocom.persistence.src.datasources.domain.community.community.community_repository37cellix.domain-seedwork.src.domain-seedwork.domain-entity38ocom.persistence.src.datasources.domain.case.service-ticket-v1.service-ticket-v1_repository39cellix.domain-seedwork.src.domain-seedwork.aggregate-root4011121111111111125114111113211133111121111114113311111121111111111111111111111111112111111111111111111111+577 more modules (most-connected shown)

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

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

At a glance — Maturity · 87% · Strong ·

At a glance — Readiness · 44% · Weak · gated by R8 ·

At a glance — Security · 48% · Weak · gated by D29, D36, C1 ·

At a glance — Domain Modelling · 51% · Adequate · gated by DM5, DM2 ·

At a glance — Accessibility · 45% · Weak · gated by AC2 ·

At a glance — Performance · 60% · Adequate ·

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures56High / Critical
A05:2025 — Injection25High / Critical
A02:2025 — Security Misconfiguration11Medium
A07:2025 — Authentication Failures1High / 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).

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

Do thisHelpsEffortDimension
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.+2.5 ptsLowSecret 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 ptsLowTest Quality
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.+2.4 ptsMediumDependency 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 ptsMediumForms & 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 ptsMediumA11y enforcement
Enable Dependabot/Renovate or a dependency-review gate.+1.6 ptsMediumSecurity & performance tooling
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).+1.6 ptsMediumDR & 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 ptsMediumPage structure

File quality

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

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.5MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedDependency Vulnerabilities: High CVE: REDACTED
packages/cellix/mongoose-seedwork/tests/integration/mongo-unit-of-work.integration.test.ts6.0MixedTest Quality: No assertions (empty test): Then the integration event should be dispatched by integrationEventBus after the transaction commits
REDACTED6.1MixedIaC & Container Security: Medium IaC: REDACTED
REDACTED6.3MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.3MixedIaC & Container Security: Medium IaC: REDACTED
packages/ocom/persistence/src/datasources/domain/case/service-ticket-v1/service-ticket-v1.domain-adapter.ts6.6MixedExplicit Debt: TodoComment
packages/cellix/event-bus-seedwork-node/src/node-event-bus.ts6.6MixedExplicit Debt: HackComment
REDACTED6.9MixedIaC & Container Security: Medium IaC: REDACTED
packages/ocom/application-services/src/contexts/community/member/member-management.ts7.0MixedCyclomatic Complexity: member-management.updateMemberProfile.<returned closure> (cyclomatic 22)
REDACTED7.2MixedSecret Scanning: Leaked secret: REDACTED
build-pipeline/scripts/detect-changes.cjs7.3MixedCyclomatic Complexity: detect-changes.detectChanges (cyclomatic 20)
packages/ocom/ui-staff-shared/src/section-layout.tsx7.4MixedCyclomatic Complexity: section-layout.SectionLayout (cyclomatic 40)
packages/ocom/ui-community-route-admin/src/components/members-list.container.tsx7.4MixedCyclomatic Complexity: members-list.container.MemberListContainer (cyclomatic 37)
apps/ui-staff/src/contexts/theme-context.tsx7.4MixedCyclomatic Complexity: theme-context.ThemeProvider (cyclomatic 34)
packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts7.4MixedCyclomatic Complexity: file-user-store.createFileUserStore.validateEntries (cyclomatic 25)

How the grades work

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

Critical — 58

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 330

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 272

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

Could not be resolved — 13

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.

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

What we checked — 92 dimensions across the health lenses
D1D2D3D5D6D7D9D10D13D14D15D16D17D19D20D23D24D26D28D29D30D31D34D35D36D43D44AC2AC3AC6AC7AX10AX3AX4AX5AX6AX8C1C2DM1DM10DM11DM2DM4DM5DM6DM7DM9GD1IC1M1M2M3M4P1P10P11P2P3P4P5PF3R1R10R11R2R3R4R6R7R8R9S1X1X12X13X14X15X16X17X18X19X21X22X23X24X25X28X29X3X30X5

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

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

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

Tools & methods

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

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1b8ca-dc0d-770a-be0b-bc252a5c86ff.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — not measured this run — 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.

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

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

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
  • 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 Complexity7.0 / 10Strong✓ Tool-verified

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

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

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

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

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

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

What to do

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

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

D2 · Cognitive Complexity6.4 / 10Adequate✓ Tool-verified

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

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

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

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

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

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

What to do

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

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

D3 · God Classes8.8 / 10Strong✓ Tool-verified

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

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

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

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

FunctionTooLong: router.buildOidcRouter · ×12REDACTED:44

What to do

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

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

D5 · Coupling8.7 / 10Strong✓ Tool-verified

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

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

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

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

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

Off the main sequence: @cellix/graphql-core · ×8
Off the main sequence: @ocom/ui-staff-shared

What to do

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

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

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

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

0 of 80 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D7 · Architectural Integrity6.0 / 10Adequate✓ Tool-verified

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

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

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

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

Classify ADR enforcement: Use Markdown Any Decision Records (MADR) to track Architectural Decisions · ×34apps/docs/docs/decisions/0001-madr-architecture-decisions.md

What to do

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

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

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

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

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

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

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.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality9.7 / 10Adequategated by 7 critical findings✓ Tool-verified

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

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

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

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

No assertions (empty test): Then the integration event should be dispatched by integrationEventBus after the transaction commits · ×7packages/cellix/mongoose-seedwork/tests/integration/mongo-unit-of-work.integration.test.ts:748
Mock-dominated test: removes a member through domain operation · ×4packages/ocom/application-services/src/contexts/community/member/member-management.operations.test.ts:138

What to do

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

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

D13 · Secret Scanning5.0 / 10Adequate✓ Tool-verified

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

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

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

1 secret(s) detected.

REDACTED

What to do

  1. Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

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

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

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

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

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.

Off-boarding risk: anonymized user #1

✓ On the Gold path — maintain.

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

D17 · Explicit Debt9.9 / 10Stronggated by 17 serious findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

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

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.

TodoComment · ×13packages/ocom/persistence/src/datasources/domain/property/property/property.domain-adapter.ts:153
HackComment · ×4packages/cellix/event-bus-seedwork-node/src/node-event-bus.ts:111

What to do

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

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

D19 · Documentation Quality9.2 / 10Exemplary✓ Tool-verified

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

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

1 of 2 documentation facets pass in full; short on: F2 example. 57 document(s) read across 57 unit(s).

Documentation: no build, run or usage example · ×2apps/api/readme.md:1

✓ On the Gold path — maintain.

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

D20 · ADR Quality9.0 / 10Exemplary✓ Tool-verified

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

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

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

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.

ADR has no Consequences section · ×5apps/docs/docs/decisions/0002-open-telemetry.md:14detected by adr-integrity
ADR considers only one option · ×2apps/docs/docs/decisions/0005-authorization.md:30detected by adr-integrity
ADR consequences name no cost · ×2apps/docs/docs/decisions/0027-typescript-6-upgrade.md:36detected by adr-integrity
ADR decides a question another record already decided · ×2apps/docs/docs/decisions/0004-identity-access.md:13detected by adr-integrity

✓ On the Gold path — maintain.

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

D23 · Boundary Type-Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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.

✓ On the Gold path — maintain.

Detailed fixes: d23_recommendation.md.

D24 · Comment Value2.9 2.9 / 10Weak✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 2.9 / 10 · rule-coverage 98% · ceiling Documented

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.

redundant comment · ×43apps/ui-community/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx:27
doc comments repeat the names · ×5packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:35

What to do

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

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

D26 · Project Cohesion9.6 / 10Exemplary✓ Tool-verified

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

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

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

1 of 51 build units (npm) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

✓ On the Gold path — maintain.

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

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

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

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

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

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)2.6 / 10Weak✓ Tool-verified

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

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

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

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

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.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

52 finding(s): 4 critical, 23 high, 22 medium, 3 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. 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).
  2. Resolve the 4 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
  3. Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D31 · IaC & Container Security8.9 / 10Strong✓ Tool-verified

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

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

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

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

REDACTED

What to do

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

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

D34 · Knowledge Freshness6.7 / 10Adequate✓ Tool-verified

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

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

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

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.

Orphaned knowledge · ×2packages/ocom/graphql/src/schema/types/member.resolvers.ts:1
Orphaned file · ×74packages/ocom/ui-community-route-admin/src/components/members-list.tsx:1
Further orphaned files (smaller)

What to do

  1. 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).
  2. 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).
  3. Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

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

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

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

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

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

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

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

REDACTED
REDACTED
REDACTED
REDACTED

What to do

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

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 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.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AC2 · Forms & labels2.2 / 10Critical✓ Tool-verified

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

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

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

  • This 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 structure5.1 / 10Adequate✓ Tool-verified

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

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

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

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

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

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

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

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

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

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

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

  • No accessibility enforcement found — 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 composition9.6 / 10Exemplary✓ Tool-verified

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

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

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

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

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

AX4 · Dependency direction6.8 / 10Adequate✓ Tool-verified

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

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

  • `@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 & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `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 isolation0.0 / 10Critical✓ Tool-verified

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

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

  • `@apps/api` (production) references the test project `@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 Protection3.0 / 10Weak✓ Tool-verified

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

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

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

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

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

  • Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect. — 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 boundaries10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.

Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.

Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.

DM10 · One transaction, one aggregate10.0 / 10Exemplary○ Nothing flagged

Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.

Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.

DM11 · Constructible invalid state10.0 / 10Exemplary○ Nothing flagged

Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.

Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule / an XException.ThrowIf* helper). C#: a static factory beside a public constructor does not exempt it, and a public parameterless constructor followed by public raw-primitive setters that refuse nothing is charged when the type also declares a validating way in (a guarded constructor or a guarding static method returning the type); TypeScript: a static Create/Of/From/New factory exempts the type. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.

DM2 · Strongly-typed ids3.0 / 10Weak✓ Tool-verified

Other · Domain Modelling — How much of the domain uses strongly-typed ids vs raw Guid/string/int — adoption curve, not all-or-nothing.

Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. An id wrapper is recognised by VALUE SEMANTICS, not by being a struct — a record struct, a record class (`record ApartmentId(Guid Value)`) or a class declared by a typed-id base (`class MemberId : TypedIdValueBase`) all count, while a plain mutable class (reference equality) and a verb-phrase query record (`GetCustomerById`) do not. Deterministic, adoption percentage.

Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.

  • `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 model4.1 / 10Weak✓ Tool-verified

Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.

Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.

Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.

  • `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 state1.0 / 10Critical✓ Tool-verified

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

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

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

  • `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 boundary10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain aggregate fused to a persistence ORM (TypeORM/Prisma/MikroORM/Sequelize/Mongoose) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.

Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.

Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.

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

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

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

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

DM9 · Scattered domain decisions10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.

Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

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

IC1 · Incompleteness & stubs9.0 / 10Strong✓ Tool-verified

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

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • 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)9.2 / 10Exemplary✓ Tool-verified

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

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

What to do

  • Add a README to the 26 of 63 project(s) that lack one — worth up to 0.8 pts.
M2 · Architecture documentation10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

What to do

  • Grow the ADR log (currently 36) — reach 50 to raise the maturity tier; document significant decisions as they're made.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy7.4 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

  • 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 gates8.5 / 10Strong✓ Tool-verified

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

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

What to do

  • Run the test suite in CI via an explicit runner step (`pnpm test` for the toolchain this pipeline already uses) and gate merges on it.
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

P2 · Observability7.0 / 10Strong✓ Tool-verified

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

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

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

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

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

  • `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 & Rollback5.0 / 10Adequate✓ Tool-verified

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

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

What to do

  • Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where 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 & Backup4.0 / 10Weak✓ Tool-verified

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

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

What to do

  • Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
  • 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 hygiene6.0 / 10Adequate✓ Tool-verified

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

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

  • `fs.existsSync` in `checkFrontendArchitecture` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×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 Safety9.9 / 10Exemplary✓ Tool-verified

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

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

What to do

  • Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication7.7 / 10Strong✓ Tool-verified

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

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

  • 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 Boundaries5.5 / 10Adequate✓ Tool-verified

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

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

  • packages/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 Complexity8.9 / 10Strong✓ Tool-verified

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

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

  • 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 Files9.8 / 10Exemplary✓ Tool-verified

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

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

  • 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 Coverage9.6 / 10Exemplary✓ Tool-verified

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

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

  • packages/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 · Tooling10.0 / 10Exemplary✓ Tool-verified

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

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

  • This repository declares test tooling, and the ✓ above records that declaration — but packages/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 Code9.9 / 10Exemplary✓ Tool-verified

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

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

  • 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 Hygiene0.0 / 10Critical✓ Tool-verified

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

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

  • Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
  • Every import is type-only — move it to devDependencies. — apps/server-mongodb-memory-mock/src/seed/seed.ts: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 Imports8.3 / 10Strong✓ Tool-verified

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

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

  • packages/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 Posture5.0 / 10Adequate✓ Tool-verified

Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository. Its Node HTTP listeners were read for HTTPS enforcement alone — TLS served, a redirect to https:// or HSTS, or a TLS-terminating proxy configuration committed beside the server — each judged per server package.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

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

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

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

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

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

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

X24 · Document value interpolated into markup unescaped4.6 / 10Weak✓ Tool-verified

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

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

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

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

X3 · Exception handling5.3 / 10Adequate✓ Tool-verified

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

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

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×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 rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

X5 · Nullable reference types2.3 / 10Critical✓ Tool-verified

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

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

  • 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

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

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

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

Reference — by lens

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

LensScoreRatingImpact
Code Health63%Adequate — gated by X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture55%Adequate — gated by AX8Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity87%StrongStrongest area.
Readiness44%Weak — gated by R8Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security48%Weak — gated by D29, D36, C1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling51%Adequate — gated by DM5, DM2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility45%Weak — gated by AC2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance60%AdequateAcceptable, with room to improve.
Unscored — 3 check(s) recorded observations but carry no score

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

  • P12 CI test-gate honesty — 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

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

  • C3 Audit Trail — Repo shows no audit-logging mechanism (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

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

  • 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)

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

Critical — 58 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×22
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AX8 · Test isolation · Production project references a test project · ×8
  • Production project references a test project: @apps/api → @ocom/context-spec apps/api/package.json:35 — `@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.
  • Production project references a test project: @cellix/api-core → @cellix/api-services-spec packages/cellix/api-core/package.json:30 — `@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.
  • Production project references a test project: @cellix/service-blob-storage → @cellix/api-services-spec packages/cellix/service-blob-storage/package.json:31 — `@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.
  • Production project references a test project: @ocom/application-services → @ocom/context-spec packages/ocom/application-services/package.json:29 — `@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.
  • Production project references a test project: @ocom/service-apollo-server → @cellix/api-services-spec packages/ocom/service-apollo-server/package.json:30 — `@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.
  • Production project references a test project: @ocom/service-mongoose → @cellix/api-services-spec packages/ocom/service-mongoose/package.json:29 — `@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.
  • Production project references a test project: @ocom/service-otel → @cellix/api-services-spec REDACTED:30 — `@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.
  • Production project references a test project: @ocom/service-token-validation → @cellix/api-services-spec packages/ocom/service-token-validation/package.json:29 — `@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.
D10 · Test Quality · No assertions (empty test) · ×7
  • 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 — Test method has an empty body — it asserts nothing and exercises no code.
  • 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 — Test method has an empty body — it asserts nothing and exercises no code.
  • 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 — Test method has an empty body — it asserts nothing and exercises no code.
  • 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 — Test method has an empty body — it asserts nothing and exercises no code.
  • 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 — Test method has an empty body — it asserts nothing and exercises no code.
  • 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 — Test method has an empty body — it asserts nothing and exercises no code.
  • 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 — Test method has an empty body — it asserts nothing and exercises no code.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AX4 · Dependency direction · Dependency-rule violation · ×2
  • Dependency-rule violation: @cellix/api-core (Domain) → @cellix/api-services-spec (Web) packages/cellix/api-core/package.json:30 — `@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.
  • Dependency-rule violation: @ocom/application-services (Application) → @ocom/persistence (Infrastructure) packages/ocom/application-services/package.json:31 — `@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.
D34 · Knowledge Freshness · Orphaned knowledge · ×2
  • Orphaned knowledge packages/ocom/graphql/src/schema/types/member.resolvers.ts:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge packages/ocom/application-services/src/contexts/community/member/member-management.ts:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
D13 · Secret Scanning · Leaked secret · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · High vulnerability · ×1
  • REDACTED
R9 · Circular Imports · Import cycle (2 files) · ×1
  • Import cycle (2 files) packages/ocom/ui-staff-shared/src/section-layout.tsx:6 — 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
S1 · Web-Security Posture · Password hashing without a KDF · ×1
  • Password hashing without a KDF REDACTED:164 — `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.
Serious — 330 finding(s)
R11 · Import Boundaries · Boundary violation [layered · ×30
  • Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/community/create.ts:2 — 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.
  • Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/community/index.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.
  • Boundary violation [layered:package-upward-import] 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-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.
  • Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/community/query-by-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.
  • Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/community/update-settings.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.
  • Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/index.ts:1 — 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.
  • Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/member/determine-if-admin.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.
  • Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/member/index.ts:2 — 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.
  • Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/member/member-management.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.
  • Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/member/query-by-community-id.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.
  • Boundary violation [layered:package-upward-import] 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-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.
  • Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/member/query-by-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.
  • Boundary violation [layered:package-upward-import] 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/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.
  • Boundary violation [layered:package-upward-import] 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-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.
  • Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/role/end-user-role/query-by-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.
  • Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/community/role/index.ts:1 — 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.
  • Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/service/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.
  • Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/service/service/create.ts:2 — 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.
  • Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/service/service/index.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.
  • Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/user/end-user/create-if-not-exists.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.
  • Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/user/end-user/index.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.
  • Boundary violation [layered:package-upward-import] 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-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.
  • Boundary violation [layered:package-upward-import] 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-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.
  • Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/user/end-user/query-by-name.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.
  • Boundary violation [layered:package-upward-import] packages/ocom/application-services/src/contexts/user/index.ts:1 — 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.
  • + 5 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×25
  • Swallowed exception (empty catch) packages/ocom-verification/acceptance-ui/src/cucumber-lifecycle-hooks.ts:21 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/ocom-verification/acceptance-api/src/contexts/community/step-definitions/create-community.steps.ts:88 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/ocom-verification/acceptance-api/src/contexts/community/step-definitions/create-community.steps.ts:105 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/ocom-verification/acceptance-api/src/contexts/community/step-definitions/create-community.steps.ts:125 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/ocom-verification/acceptance-api/src/contexts/community/step-definitions/create-community.steps.ts:132 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/cellix/ui-core/src/components/molecules/require-auth/index.tsx:65 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/cellix/service-queue-storage/src/internal-queue-storage-service.ts:296 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/cellix/service-queue-storage/src/internal-queue-storage-service.ts:326 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:275 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:141 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/cellix/server-oauth2-mock-seedwork/src/manager.ts:59 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/cellix/server-oauth2-mock-seedwork/src/manager.ts:87 — `.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.
  • Swallowed exception (empty catch) packages/cellix/server-oauth2-mock-seedwork/src/manager.ts:138 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:109 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:167 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/cellix/serenity-framework/src/dom/asset-loader-hooks.ts:48 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/cellix/serenity-framework/src/dom/asset-loader-hooks.ts:60 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/cellix/serenity-framework/src/cucumber/screenshot-hooks.ts:49 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/cellix/config-rolldown/src/index.ts:96 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) apps/ui-staff/src/contexts/theme-context.tsx:84 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) apps/ui-staff/src/contexts/theme-context.tsx:107 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) apps/ui-staff/src/contexts/theme-context.tsx:154 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) apps/ui-staff/src/contexts/theme-context.tsx:177 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) apps/ui-staff/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx:44 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) apps/ui-community/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx:44 — 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.
D30 · Dependency Vulnerabilities · Medium CVE · ×22
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
R4 · Test Coverage · No test reaches this file · ×22
  • No test reaches this file build-pipeline/scripts/detect-changes.cjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/ui-staff/src/contexts/theme-context.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/ui-community/src/contexts/theme-context.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/server-mongodb-memory-mock/src/seed/properties.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/server-mongodb-memory-mock/src/seed/roles.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file build-pipeline/scripts/check-sonar-quality-gate.cjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file build-pipeline/scripts/merge-coverage.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/server-mongodb-memory-mock/src/seed/members.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/server-mongodb-memory-mock/src/seed/seed.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file build-pipeline/scripts/get-pr-number.cjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file build-pipeline/scripts/build-bicep.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/server-mongodb-memory-mock/src/seed/end-users.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/server-mongodb-memory-mock/src/seed/services.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/ui-community/src/config/oidc-config.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/ui-staff/src/config/oidc-config.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/ocom/graphql/src/schema/types/end-user-role.resolvers.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/server-mongodb-memory-mock/src/seed/communities.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/server-mongodb-memory-mock/src/setup-environment.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/server-oauth2-mock/src/setup-environment.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/api/start-dev.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/cellix/graphql-core/src/schema/core/graphql-tools-scalars.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file apps/api/start-azurite.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
D17 · Explicit Debt · TodoComment · ×13
  • TodoComment packages/ocom/persistence/src/datasources/domain/property/property/property.domain-adapter.ts:153 — // TODO: Temporary workaround for PropArray vs ReadonlyArray incompatibility — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/ocom/persistence/src/datasources/domain/case/service-ticket-v1/service-ticket-v1.domain-adapter.ts:263 — // TODO: Temporary workaround for PropArray vs ReadonlyArray incompatibility — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/ocom/persistence/src/datasources/domain/case/service-ticket-v1/service-ticket-v1.domain-adapter.ts:275 — // TODO: Temporary workaround for PropArray vs ReadonlyArray incompatibility — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/ocom/persistence/src/datasources/domain/case/service-ticket-v1/service-ticket-v1.domain-adapter.ts:321 — // TODO: Temporary workaround for PropArray vs ReadonlyArray incompatibility — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/ocom/persistence/src/datasources/domain/case/service-ticket-v1/service-ticket-v1.domain-adapter.ts:333 — // TODO: Temporary workaround for PropArray vs ReadonlyArray incompatibility — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/ocom/domain/src/domain/iam/member/contexts/member.community.visa.ts:36 — //TODO: add a more complext rule here like can only create one community for free, otherwise need a paid plan — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/ocom/domain/src/domain/contexts/community/member/member.ts:227 — //TODO: why is this not security checked? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/ocom/data-sources-mongoose-models/src/patterns.ts:6 — //TODO: fix email pattern so that it is unicode compliant — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/ocom/data-sources-mongoose-models/src/models/user/end-user.model.ts:105 — //TODO: This should be in singular form — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/ocom/data-sources-mongoose-models/src/models/role/role.model.ts:8 — // TODO: Discriminator key and Version can't exist together, if we don't use version key it will fall back to __v — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/ocom/data-sources-mongoose-models/src/models/case/ticket.model.ts:8 — // TODO: Discriminator key and Version can't exist together, if we don't use version key it will fall back to __v — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/cellix/mongoose-seedwork/src/mongoose-seedwork/mongo-unit-of-work.ts:49 — //todo: can we make this an arry of CustomDomainEvents? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/cellix/domain-seedwork/src/domain-seedwork/child-entity.ts:1 — //TODO: Add a description of the file and its purpose - note why it does not extend DomainEntityProps — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
DM5 · Encapsulated state · Mutable entity · ×13
  • Mutable entity: EndUserRole packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role.ts:28 — `EndUserRole` exposes publicly writable state (roleName, isDefault).
  • Mutable entity: EndUser packages/ocom/domain/src/domain/contexts/user/end-user/end-user.ts:31 — `EndUser` exposes publicly writable state (email, displayName, externalId, accessBlocked, tags).
  • Mutable entity: Member packages/ocom/domain/src/domain/contexts/community/member/member.ts:43 — `Member` exposes publicly writable state (memberName, cybersourceCustomerId, community, role).
  • Mutable entity: Property packages/ocom/domain/src/domain/contexts/property/property/property.aggregate.ts:42 — `Property` exposes publicly writable state (location, owner, propertyName, propertyType, listedForSale, listedForRent, and 6 more).
  • Mutable entity: Service packages/ocom/domain/src/domain/contexts/service/service/service.aggregate.ts:25 — `Service` exposes publicly writable state (serviceName, description, isActive).
  • Mutable entity: StaffRole packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role.ts:25 — `StaffRole` exposes publicly writable state (roleName, enterpriseAppRole, isDefault).
  • Mutable entity: StaffUser packages/ocom/domain/src/domain/contexts/user/staff-user/staff-user.ts:36 — `StaffUser` exposes publicly writable state (role, firstName, lastName, email, displayName, externalId, and 2 more).
  • Mutable entity: VendorUser packages/ocom/domain/src/domain/contexts/user/vendor-user/vendor-user.ts:28 — `VendorUser` exposes publicly writable state (email, displayName, externalId, accessBlocked, tags).
  • Mutable entity: ViolationTicketV1 packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1.aggregate.ts:61 — `ViolationTicketV1` exposes publicly writable state (communityId, propertyId, assignedToId, serviceId, title, description, and 6 more).
  • Mutable entity: VendorUserRole packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role.ts:28 — `VendorUserRole` exposes publicly writable state (isDefault, roleName).
  • Mutable entity: Community packages/ocom/domain/src/domain/contexts/community/community/community.ts:27 — `Community` exposes publicly writable state (name, domain, whiteLabelDomain, handle).
  • Mutable entity: MemberInvitation packages/ocom/domain/src/domain/contexts/community/member/member-invitation.ts:27 — `MemberInvitation` exposes publicly writable state (email, message, expiresAt).
  • Mutable entity: ServiceTicketV1 packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:51 — `ServiceTicketV1` exposes publicly writable state (title, description, status, priority, communityId, propertyId, and 6 more).
D3 · God Classes · FunctionTooLong · ×12
  • FunctionTooLong: router.buildOidcRouter REDACTED:44 — FunctionTooLong — buildOidcRouter runs 245 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 145 over it, 2.45× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: members-list.MemberList packages/ocom/ui-community-route-admin/src/components/members-list.tsx:59 — FunctionTooLong — MemberList runs 225 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 125 over it, 2.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: login-handlers.createLoginHandlers REDACTED:44 — FunctionTooLong — createLoginHandlers runs 207 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 107 over it, 2.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: login-handlers.createLoginHandlers.registerRoutes REDACTED:63 — FunctionTooLong — createLoginHandlers.registerRoutes runs 190 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 90 over it, 1.90× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: members-invite-modal.MembersInviteModal packages/ocom/ui-community-route-admin/src/components/members-invite-modal.tsx:27 — FunctionTooLong — MembersInviteModal runs 190 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 90 over it, 1.90× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: file-user-store.createFileUserStore packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:43 — FunctionTooLong — createFileUserStore runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: members-list.container.MemberListContainer packages/ocom/ui-community-route-admin/src/components/members-list.container.tsx:21 — FunctionTooLong — MemberListContainer runs 175 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: section-layout.SectionLayout packages/ocom/ui-staff-shared/src/section-layout.tsx:37 — FunctionTooLong — SectionLayout runs 151 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: member-profile.MemberProfile packages/ocom/ui-community-shared/src/components/member-profile.tsx:28 — FunctionTooLong — MemberProfile runs 142 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: theme-context.ThemeProvider apps/ui-staff/src/contexts/theme-context.tsx:34 — FunctionTooLong — ThemeProvider runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: community-list.CommunityList packages/ocom/ui-community-route-accounts/src/components/community-list.tsx:16 — FunctionTooLong — CommunityList runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: staff-role-edit.container.StaffRoleEditContainer packages/ocom/ui-staff-route-user-management/src/components/staff-role-edit.container.tsx:32 — FunctionTooLong — StaffRoleEditContainer runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D31 · IaC & Container Security · Medium IaC · ×11
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
DM4 · Rich vs anemic model · Anemic entity · ×11
  • Anemic entity: EndUserRole packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role.ts:28 — `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.
  • Anemic entity: EndUser packages/ocom/domain/src/domain/contexts/user/end-user/end-user.ts:31 — `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.
  • Anemic entity: Member packages/ocom/domain/src/domain/contexts/community/member/member.ts:43 — `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.
  • Anemic entity: Property packages/ocom/domain/src/domain/contexts/property/property/property.aggregate.ts:42 — `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.
  • Anemic entity: Service packages/ocom/domain/src/domain/contexts/service/service/service.aggregate.ts:25 — `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.
  • Anemic entity: StaffRole packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role.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.
  • Anemic entity: VendorUser packages/ocom/domain/src/domain/contexts/user/vendor-user/vendor-user.ts:28 — `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.
  • Anemic entity: ViolationTicketV1 packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1.aggregate.ts:61 — `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.
  • Anemic entity: VendorUserRole packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role.ts:28 — `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.
  • Anemic entity: Community packages/ocom/domain/src/domain/contexts/community/community/community.ts:27 — `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.
  • Anemic entity: ServiceTicketV1 packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:51 — `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.
R11 · Import Boundaries · Boundary violation [package · ×10
  • Boundary violation [package:test-suite-dependency] packages/ocom-verification/acceptance-api/src/mock-application-services.ts:10 — 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.
  • Boundary violation [package:test-suite-dependency] packages/ocom-verification/acceptance-api/src/servers/test-mongo-server.ts:2 — 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.
  • Boundary violation [package:test-suite-dependency] packages/ocom-verification/acceptance-api/src/servers/test-mongo-server.ts:3 — 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.
  • Boundary violation [package:test-suite-dependency] packages/ocom-verification/acceptance-ui/src/contexts/authentication/tasks/click-header-sign-in.ts:4 — 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.
  • Boundary violation [package:test-suite-dependency] packages/ocom-verification/acceptance-ui/src/contexts/community/tasks/create-community.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.
  • Boundary violation [package:test-suite-dependency] 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: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.
  • Boundary violation [package:relative-cross-package] 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/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.
  • Boundary violation [package:test-suite-dependency] 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: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.
  • Boundary violation [package:relative-cross-package] packages/ocom-verification/acceptance-ui/src/contexts/staff-role/tasks/staff-roles-screen.ts:9 — 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.
  • Boundary violation [package:relative-cross-package] packages/ocom-verification/acceptance-ui/src/shared/ocom-component-wrapper.ts:6 — 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.
D5 · Coupling · Off the main sequence · ×8
  • Off the main sequence: @cellix/graphql-core — @cellix/graphql-core: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
  • Off the main sequence: @cellix/ui-core — @cellix/ui-core: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
  • Off the main sequence: @ocom/service-apollo-server — @ocom/service-apollo-server: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
  • Off the main sequence: @ocom/service-otel — @ocom/service-otel: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
  • Off the main sequence: @cellix/local-dev — @cellix/local-dev: abstractness 0.04, instability 0.00, distance 0.96 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
  • Off the main sequence: @cellix/service-blob-storage — @cellix/service-blob-storage: abstractness 0.25, instability 0.00, distance 0.75 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
  • Off the main sequence: @ocom/local-dev-config — @ocom/local-dev-config: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
  • Off the main sequence: @cellix/service-queue-storage — @cellix/service-queue-storage: abstractness 0.29, instability 0.00, distance 0.71 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
PF3 · Async & latency hygiene · Sync-over-async blocking · ×6
  • Sync-over-async blocking packages/cellix/archunit-tests/src/checks/frontend-architecture.ts:24 — `fs.existsSync` in `checkFrontendArchitecture` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/cellix/archunit-tests/src/checks/frontend-architecture.ts:29 — `fs.existsSync` in `checkFrontendArchitecture` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/cellix/archunit-tests/src/checks/frontend-architecture.ts:33 — `fs.existsSync` in `checkFrontendArchitecture` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/cellix/archunit-tests/src/checks/frontend-architecture.ts:36 — `fs.existsSync` in `checkFrontendArchitecture` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/cellix/serenity-framework/src/cucumber/screenshot-hooks.ts:41 — `mkdirSync` in `callback to After` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/cellix/serenity-framework/src/cucumber/screenshot-hooks.ts:48 — `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.
D17 · Explicit Debt · HackComment · ×4
  • HackComment packages/cellix/event-bus-seedwork-node/src/node-event-bus.ts:111 — // hack to create dependency title in App Insights to show up nicely in trace details — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
  • HackComment packages/cellix/event-bus-seedwork-node/src/node-event-bus.ts:113 — // hack (becomes upper case) — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
  • HackComment packages/cellix/event-bus-seedwork-node/src/node-event-bus.ts:114 — // hack — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
  • HackComment packages/cellix/event-bus-seedwork-node/src/node-event-bus.ts:115 — // hack - dumps payload in command — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×4
  • Untrusted text written into markup unescaped packages/cellix/server-oauth2-mock-seedwork/src/html-builders.ts:16 — `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.
  • Untrusted text written into markup unescaped packages/cellix/server-oauth2-mock-seedwork/src/html-builders.ts:22 — `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.
  • Untrusted text written into markup unescaped packages/cellix/server-oauth2-mock-seedwork/src/html-builders.ts:36 — `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.
  • Untrusted text written into markup unescaped REDACTED:155 — `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.
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
P12 · CI test-gate honesty · Workspace package's tests never run by CI · ×3
  • Workspace package's tests never run by CI packages/ocom/ui-community-shared/package.json:14 — `packages/ocom/ui-community-shared` is a workspace package with 2 test(s) in 2 file(s) (e.g. `packages/ocom/ui-community-shared/src/archunit-tests/frontend-architecture.test.ts`, `packages/ocom/ui-community-shared/src/archunit-tests/naming-conventions.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
  • Workspace package's tests never run by CI packages/ocom/ui-staff-route-user-management/package.json:15 — `packages/ocom/ui-staff-route-user-management` is a workspace package with 14 test(s) in 1 file(s) (e.g. `packages/ocom/ui-staff-route-user-management/src/components/staff-user-detail.test.tsx`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
  • Workspace package's tests never run by CI packages/ocom/ui-staff-shared/package.json:14 — `packages/ocom/ui-staff-shared` is a workspace package with 12 test(s) in 1 file(s) (e.g. `packages/ocom/ui-staff-shared/src/staff-app-roles.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
R10 · Code Duplication · Duplicated block with local edits (35 matched lines × 2 locations) · ×3
  • Duplicated block with local edits (35 matched lines × 2 locations) packages/ocom/domain/src/domain/iam/guest/guest.passport.ts:15 — 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.
  • Duplicated block with local edits (35 matched lines × 2 locations) packages/ocom/domain/src/domain/iam/member/member.passport.ts:16 — 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.
  • Duplicated block with local edits (35 matched lines × 2 locations) packages/ocom/ui-staff-route-user-management/src/components/staff-roles-list.tsx:38 — 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.
AC2 · Forms & labels · <Select> field component without a label · ×2
  • <Select> field component without a label packages/ocom/ui-community-route-admin/src/components/members-list.tsx:234 — 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.
  • <Select> field component without a label packages/ocom/ui-staff-route-user-management/src/components/staff-user-detail.tsx:94 — 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.
AC3 · Page structure · Page without a main landmark · ×2
  • Page without a main landmark apps/ui-community/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark apps/ui-staff/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
P12 · CI test-gate honesty · CI test gate excludes suites by filter · ×2
  • CI test gate excludes suites by filter build-pipeline/core/monorepo-build-stage.yml:245 — `pnpm run test:coverage:affected` drops 1 test(s) in 1 file(s) (e.g. `packages/cellix/service-blob-storage/tests/service-blob-storage.integration.test.ts`), and no other gate runs them before merge. Run what it excludes in another job before merge (a complementary selection), or remove the exclusion.
  • CI test gate excludes suites by filter build-pipeline/core/monorepo-build-stage.yml:251 — `pnpm run test:coverage:merge` drops 1 test(s) in 1 file(s) (e.g. `packages/cellix/service-blob-storage/tests/service-blob-storage.integration.test.ts`), and no other gate runs them before merge. Run what it excludes in another job before merge (a complementary selection), or remove the exclusion.
R10 · Code Duplication · Duplication concentrated across 4 sibling directories (7 clone groups) · ×2
  • Duplication concentrated across 4 sibling directories (7 clone groups) packages/ocom/domain/src/domain/contexts/user/end-user/end-user.ts:11 — 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.
  • Duplication concentrated across 4 sibling directories (7 clone groups) packages/ocom/persistence/src/datasources/domain/user/staff-user/staff-user.domain-adapter.ts:55 — 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.
R10 · Code Duplication · Duplication concentrated across 2 sibling directories (5 clone groups) · ×2
  • Duplication concentrated across 2 sibling directories (5 clone groups) apps/ui-community/src/App.tsx:20 — 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.
  • Duplication concentrated across 2 sibling directories (5 clone groups) packages/ocom-verification/acceptance-api/src/contexts/staff/step-definitions/staff-landing.steps.ts:41 — 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.
R10 · Code Duplication · Duplicated block (39 lines × 2 locations) · ×2
  • Duplicated block (39 lines × 2 locations) packages/ocom/ui-community-route-admin/src/components/members-accounts-add.tsx: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.
  • Duplicated block (39 lines × 2 locations) packages/ocom/ui-community-route-admin/src/sub-page-layout.tsx:12 — 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.
R10 · Code Duplication · Duplicated block with local edits (33 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (33 matched lines × 2 locations) packages/ocom/domain/src/domain/iam/guest/guest.passport.ts:14 — 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.
  • Duplicated block with local edits (33 matched lines × 2 locations) packages/ocom/domain/src/domain/iam/system/system.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.
R4 · Test Coverage · This test file cannot be loaded · ×2
  • This test file cannot be loaded packages/cellix/archunit-tests/src/typescript-config-conventions.test.ts:8 — 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.
  • This test file cannot be loaded packages/ocom-verification/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.
AC2 · Forms & labels · <Input> field component without a label · ×1
  • <Input> field component without a label packages/ocom/ui-community-route-admin/src/components/members-list.tsx:226 — 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.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung REDACTED:72 — 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.
C1 · Data Protection · No data-protection/encryption · ×1
  • No data-protection/encryption packages/ocom/data-sources-mongoose-models/src/models/user/end-user.model.ts:72 — 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.
D1 · Cyclomatic Complexity · router.buildOidcRouter (cyclomatic 71) · ×1
  • router.buildOidcRouter (cyclomatic 71) REDACTED:44 — router.buildOidcRouter has cyclomatic complexity 71 (threshold 15). Most of this is not in the body itself: 6 of the 71 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 134, 241, 95, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · login-handlers.createLoginHandlers.registerRoutes (cyclomatic 62) · ×1
  • login-handlers.createLoginHandlers.registerRoutes (cyclomatic 62) REDACTED:63 — login-handlers.createLoginHandlers.registerRoutes has cyclomatic complexity 62 (threshold 15). Most of this is not in the body itself: 1 of the 62 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 103, 244, 202, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · section-layout.SectionLayout (cyclomatic 40) · ×1
  • section-layout.SectionLayout (cyclomatic 40) packages/ocom/ui-staff-shared/src/section-layout.tsx:37 — section-layout.SectionLayout has cyclomatic complexity 40 (threshold 15). Of this number, 36 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · members-list.container.MemberListContainer (cyclomatic 37) · ×1
  • members-list.container.MemberListContainer (cyclomatic 37) packages/ocom/ui-community-route-admin/src/components/members-list.container.tsx:21 — members-list.container.MemberListContainer has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 7 of the 37 points are its own statements and the rest belongs to 7 function items inside it that branch (handleBulkDeactivateMembers, handleBulkActivateMembers, handleBulkRemoveMembers, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · theme-context.ThemeProvider (cyclomatic 34) · ×1
  • theme-context.ThemeProvider (cyclomatic 34) apps/ui-staff/src/contexts/theme-context.tsx:34 — theme-context.ThemeProvider has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 2 of the 34 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 92, 48, 164, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · file-user-store.createFileUserStore.validateEntries (cyclomatic 25) · ×1
  • file-user-store.createFileUserStore.validateEntries (cyclomatic 25) packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:119 — file-user-store.createFileUserStore.validateEntries has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · staff-user-detail.container.StaffUserDetailContainer (cyclomatic 24) · ×1
  • staff-user-detail.container.StaffUserDetailContainer (cyclomatic 24) packages/ocom/ui-staff-route-user-management/src/components/staff-user-detail.container.tsx:32 — staff-user-detail.container.StaffUserDetailContainer has cyclomatic complexity 24 (threshold 15). Of this number, 17 points are the body's own statements and 7 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · member-management.updateMemberProfile.<returned closure> (cyclomatic 22) · ×1
  • member-management.updateMemberProfile.<returned closure> (cyclomatic 22) packages/ocom/application-services/src/contexts/community/member/member-management.ts:514 — member-management.updateMemberProfile.<returned closure> has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to one function literal inside it that branches (line 517). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · members-list.MemberList (cyclomatic 21) · ×1
  • members-list.MemberList (cyclomatic 21) packages/ocom/ui-community-route-admin/src/components/members-list.tsx:59 — members-list.MemberList has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 6 of the 21 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 71, handleBulkActionSubmit, a function literal at line 161, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · parse-tool-call.main (cyclomatic 21) · ×1
  • parse-tool-call.main (cyclomatic 21) .github/hooks/parse-tool-call.py:67 — parse-tool-call.main has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · detect-changes.detectChanges (cyclomatic 20) · ×1
  • detect-changes.detectChanges (cyclomatic 20) build-pipeline/scripts/detect-changes.cjs:137 — detect-changes.detectChanges has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · theme-context.ThemeProvider (cyclomatic 18) · ×1
  • theme-context.ThemeProvider (cyclomatic 18) apps/ui-community/src/contexts/theme-context.tsx:39 — theme-context.ThemeProvider has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 102, 63, 147, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · use-staff-permissions.useStaffPermissions (cyclomatic 18) · ×1
  • use-staff-permissions.useStaffPermissions (cyclomatic 18) apps/ui-staff/src/hooks/use-staff-permissions.ts:81 — use-staff-permissions.useStaffPermissions has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · App.StaffRoutes (cyclomatic 18) · ×1
  • App.StaffRoutes (cyclomatic 18) apps/ui-staff/src/App.tsx:20 — App.StaffRoutes has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · members-accounts-edit.container.MembersAccountsEditContainer (cyclomatic 17) · ×1
  • members-accounts-edit.container.MembersAccountsEditContainer (cyclomatic 17) packages/ocom/ui-community-route-admin/src/components/members-accounts-edit.container.tsx:23 — members-accounts-edit.container.MembersAccountsEditContainer has cyclomatic complexity 17 (threshold 15). Of this number, 10 points are the body's own statements and 7 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · manager.createMockOAuth2Manager.ensureStarted (cyclomatic 16) · ×1
  • manager.createMockOAuth2Manager.ensureStarted (cyclomatic 16) packages/cellix/server-oauth2-mock-seedwork/src/manager.ts:38 — manager.createMockOAuth2Manager.ensureStarted has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · members-invite-modal.container.MembersInviteModalContainer (cyclomatic 16) · ×1
  • members-invite-modal.container.MembersInviteModalContainer (cyclomatic 16) packages/ocom/ui-community-route-admin/src/components/members-invite-modal.container.tsx:14 — members-invite-modal.container.MembersInviteModalContainer has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 2 function items inside it that branch (handleBulkInvite, handleSingleInvite). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · router.buildOidcRouter (cognitive 92) · ×1
  • router.buildOidcRouter (cognitive 92) REDACTED:44 — router.buildOidcRouter has cognitive complexity 92 (threshold 15). Drivers by points: if/else 37 (52 pts), ternaries 12 (16 pts), error handling 7 (11 pts), boolean chains 10, loops 2 (3 pts) (nesting depth added 24). Most of this is not in the body itself: 7 of the 92 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 241, 134, 306, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · login-handlers.createLoginHandlers.registerRoutes (cognitive 72) · ×1
  • login-handlers.createLoginHandlers.registerRoutes (cognitive 72) REDACTED:63 — login-handlers.createLoginHandlers.registerRoutes has cognitive complexity 72 (threshold 15). Drivers by points: if/else 29 (39 pts), ternaries 17 (19 pts), error handling 7 (9 pts), boolean chains 5 (nesting depth added 14). None of this is in the body itself: all 72 points belong to 4 function literals inside it that branch (lines 103, 244, 202, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · file-user-store.createFileUserStore.validateEntries (cognitive 40) · ×1
  • file-user-store.createFileUserStore.validateEntries (cognitive 40) packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:119 — file-user-store.createFileUserStore.validateEntries has cognitive complexity 40 (threshold 15). Drivers by points: if/else 12 (25 pts), ternaries 5 (10 pts), boolean chains 4, loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · section-layout.SectionLayout (cognitive 40) · ×1
  • section-layout.SectionLayout (cognitive 40) packages/ocom/ui-staff-shared/src/section-layout.tsx:37 — section-layout.SectionLayout has cognitive complexity 40 (threshold 15). Drivers by points: if/else 17 (29 pts), boolean chains 7, loops 2, error handling 1, ternaries 1 (nesting depth added 12). Of this number, 36 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · members-list.container.MemberListContainer (cognitive 40) · ×1
  • members-list.container.MemberListContainer (cognitive 40) packages/ocom/ui-community-route-admin/src/components/members-list.container.tsx:21 — members-list.container.MemberListContainer has cognitive complexity 40 (threshold 15). Drivers by points: if/else 16 (18 pts), boolean chains 11, error handling 6, ternaries 5 (nesting depth added 2). Most of this is not in the body itself: 2 of the 40 points are its own statements and the rest belongs to 7 function items inside it that branch (handleBulkDeactivateMembers, handleBulkActivateMembers, handleBulkRemoveMembers, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · theme-context.ThemeProvider (cognitive 39) · ×1
  • theme-context.ThemeProvider (cognitive 39) apps/ui-staff/src/contexts/theme-context.tsx:34 — theme-context.ThemeProvider has cognitive complexity 39 (threshold 15). Drivers by points: if/else 15 (16 pts), error handling 5 (12 pts), boolean chains 10, ternaries 1 (nesting depth added 8). Most of this is not in the body itself: 1 of the 39 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 92, 48, 195, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · parse-tool-call.main (cognitive 37) · ×1
  • parse-tool-call.main (cognitive 37) .github/hooks/parse-tool-call.py:67 — parse-tool-call.main has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 4 (9 pts), boolean chains 3, error handling 2 (3 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · detect-changes.detectChanges (cognitive 23) · ×1
  • detect-changes.detectChanges (cognitive 23) build-pipeline/scripts/detect-changes.cjs:137 — detect-changes.detectChanges has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 5, ternaries 5 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · merge-coverage.mergeLcovFiles (cognitive 23) · ×1
  • merge-coverage.mergeLcovFiles (cognitive 23) build-pipeline/scripts/merge-coverage.js:32 — merge-coverage.mergeLcovFiles has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 3, boolean chains 2, error handling 1 (2 pts) (nesting depth added 9). Of this number, 12 points are the body's own statements and 11 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · member-management.updateMemberProfile.<returned closure> (cognitive 21) · ×1
  • member-management.updateMemberProfile.<returned closure> (cognitive 21) packages/ocom/application-services/src/contexts/community/member/member-management.ts:514 — member-management.updateMemberProfile.<returned closure> has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11, boolean chains 10. Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to one function literal inside it that branches (line 517). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · members-list.MemberList (cognitive 21) · ×1
  • members-list.MemberList (cognitive 21) packages/ocom/ui-community-route-admin/src/components/members-list.tsx:59 — members-list.MemberList has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 8 (10 pts), boolean chains 7, if/else 4 (nesting depth added 2). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 8 function items inside it that branch (handleBulkActionSubmit, a function literal at line 71, a function literal at line 161, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · member-profile.MemberProfile (cognitive 20) · ×1
  • member-profile.MemberProfile (cognitive 20) packages/ocom/ui-community-shared/src/components/member-profile.tsx:28 — member-profile.MemberProfile has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 7 (12 pts), boolean chains 5, if/else 2 (3 pts) (nesting depth added 6). Of this number, 18 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · staff-user-detail.container.StaffUserDetailContainer (cognitive 20) · ×1
  • staff-user-detail.container.StaffUserDetailContainer (cognitive 20) packages/ocom/ui-staff-route-user-management/src/components/staff-user-detail.container.tsx:32 — staff-user-detail.container.StaffUserDetailContainer has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 8, ternaries 5 (6 pts), if/else 5, error handling 1 (nesting depth added 1). Of this number, 12 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · InternalQueueStorageService.startUp (cognitive 19) · ×1
  • InternalQueueStorageService.startUp (cognitive 19) packages/cellix/service-queue-storage/src/internal-queue-storage-service.ts:144 — InternalQueueStorageService.startUp has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (8 pts), error handling 1 (5 pts), loops 1 (4 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · members-accounts-edit.container.MembersAccountsEditContainer (cognitive 19) · ×1
  • members-accounts-edit.container.MembersAccountsEditContainer (cognitive 19) packages/ocom/ui-community-route-admin/src/components/members-accounts-edit.container.tsx:23 — members-accounts-edit.container.MembersAccountsEditContainer has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 10, if/else 5, error handling 2, ternaries 1 (2 pts) (nesting depth added 1). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 2 function items inside it that branch (handleRemove, handleSave). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · members-invite-modal.container.MembersInviteModalContainer (cognitive 19) · ×1
  • members-invite-modal.container.MembersInviteModalContainer (cognitive 19) packages/ocom/ui-community-route-admin/src/components/members-invite-modal.container.tsx:14 — members-invite-modal.container.MembersInviteModalContainer has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 5, ternaries 3, error handling 2 (nesting depth added 1). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 2 function items inside it that branch (handleBulkInvite, handleSingleInvite). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · check-sonar-quality-gate.pollTaskStatus (cognitive 18) · ×1
  • check-sonar-quality-gate.pollTaskStatus (cognitive 18) build-pipeline/scripts/check-sonar-quality-gate.cjs:63 — check-sonar-quality-gate.pollTaskStatus has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (14 pts), error handling 2 (3 pts), boolean chains 1 (nesting depth added 4). None of this is in the body itself: all 18 points belong to 2 function literals inside it that branch (lines 64, 87). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · index.buildApplicationServicesFactory.forRequest (cognitive 18) · ×1
  • index.buildApplicationServicesFactory.forRequest (cognitive 18) packages/ocom/application-services/src/index.ts:46 — index.buildApplicationServicesFactory.forRequest has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 3 (7 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · theme-context.ThemeProvider (cognitive 17) · ×1
  • theme-context.ThemeProvider (cognitive 17) apps/ui-community/src/contexts/theme-context.tsx:39 — theme-context.ThemeProvider has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11, boolean chains 5, ternaries 1. Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 102, 63, 168, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · manager.createMockOAuth2Manager.ensureStarted (cognitive 17) · ×1
  • manager.createMockOAuth2Manager.ensureStarted (cognitive 17) packages/cellix/server-oauth2-mock-seedwork/src/manager.ts:38 — manager.createMockOAuth2Manager.ensureStarted has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), error handling 1 (3 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · portal-discovery.discoverPortalConfigs (cognitive 17) · ×1
  • portal-discovery.discoverPortalConfigs (cognitive 17) packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:112 — portal-discovery.discoverPortalConfigs has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
IC1 · Incompleteness & stubs · Both branches are identical · ×1
  • Both branches are identical — the condition decides nothing REDACTED:173 — 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.
R10 · Code Duplication · Duplication concentrated across 5 sibling directories (29 clone groups) · ×1
  • 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 — 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.
R10 · Code Duplication · Duplication concentrated across 13 sibling directories (22 clone groups) · ×1
  • Duplication concentrated across 13 sibling directories (22 clone groups) packages/ocom/ui-community-route-admin/src/sub-page-layout.tsx:12 — 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.
R10 · Code Duplication · Duplication concentrated across 5 sibling directories (17 clone groups) · ×1
  • 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 — 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.
R10 · Code Duplication · Duplication concentrated across 2 sibling directories (9 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (9 clone groups) apps/ui-community/src/contexts/theme-context.tsx:11 — 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.
R10 · Code Duplication · Duplication concentrated across 4 sibling directories (9 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (9 clone groups) packages/ocom/domain/src/domain/iam/guest/guest.passport.ts:14 — 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.
R10 · Code Duplication · Duplication concentrated across 2 sibling directories (8 clone groups) · ×1
  • 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 — 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.
R10 · Code Duplication · Duplication concentrated across 2 sibling directories (7 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (7 clone groups) packages/ocom/application-services/src/contexts/community/community/update-settings.ts:18 — 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.
R10 · Code Duplication · Duplication concentrated across 2 sibling directories (6 clone groups) · ×1
  • 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 — 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.
R10 · Code Duplication · Duplication concentrated across 3 sibling directories (5 clone groups) · ×1
  • 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 — 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.
R10 · Code Duplication · Duplicated block with local edits (220 matched lines × 2 locations) · ×1
  • 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 — 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.
R10 · Code Duplication · Duplicated block with local edits (122 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (122 matched lines × 2 locations) packages/cellix/serenity-framework/src/infrastructure/api-infrastructure.ts:96 — packages/cellix/serenity-framework/src/infrastructure/api-infrastructure.ts:96 · packages/cellix/serenity-framework/src/infrastructure/e2e-infrastructure.ts:167 — the two spans are one implementation copied and then locally edited — 924 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (113 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (113 matched lines × 2 locations) apps/ui-community/src/contexts/theme-context.tsx:11 — 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.
R10 · Code Duplication · Wholesale file copy (94 identical lines × 2 files) · ×1
  • Wholesale file copy (94 identical lines × 2 files) packages/ocom/data-sources-mongoose-models/src/models/role/end-user-role.model.ts:1 — 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.
R10 · Code Duplication · Duplicated block with local edits (86 matched lines × 2 locations) · ×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 — 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.
R10 · Code Duplication · Duplicated block with local edits (73 matched lines × 2 locations) · ×1
  • 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 — 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.
R10 · Code Duplication · Duplicated block (72 lines × 2 locations) · ×1
  • Duplicated block (72 lines × 2 locations) packages/ocom/data-sources-mongoose-models/src/models/user/end-user.model.ts:27 — 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.
R10 · Code Duplication · Duplicated block with local edits (70 matched lines × 2 locations) · ×1
  • 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 — 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.
R10 · Code Duplication · Duplicated block with local edits (63 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (63 matched lines × 2 locations) REDACTED:76 — 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.
R10 · Code Duplication · Duplicated block with local edits (54 matched lines × 2 locations) · ×1
  • 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 — 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.
R10 · Code Duplication · Duplicated block with local edits (53 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (53 matched lines × 2 locations) packages/ocom/domain/src/domain/contexts/user/end-user/end-user.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.
R10 · Code Duplication · Duplicated block (43 lines × 2 locations) · ×1
  • Duplicated block (43 lines × 2 locations) packages/ocom/data-sources-mongoose-models/src/models/case/service-ticket.model.ts:33 — 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.
R10 · Code Duplication · Duplicated block (42 lines × 2 locations) · ×1
  • 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 — 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.
R10 · Code Duplication · Duplicated block with local edits (38 matched lines × 2 locations) · ×1
  • 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 — 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.
R10 · Code Duplication · Duplicated block with local edits (37 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (37 matched lines × 2 locations) packages/ocom/domain/src/domain/iam/guest/guest.passport.ts:14 — 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.
R10 · Code Duplication · Duplicated block (36 lines × 2 locations) · ×1
  • Duplicated block (36 lines × 2 locations) packages/ocom/ui-community-route-admin/src/section-layout.tsx:88 — 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.
R10 · Code Duplication · Duplicated block (34 lines × 2 locations) · ×1
  • Duplicated block (34 lines × 2 locations) packages/ocom/ui-community-route-root/src/components/header.tsx:6 — 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.
R10 · Code Duplication · Duplicated block with local edits (32 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (32 matched lines × 2 locations) packages/ocom/domain/src/domain/iam/member/member.passport.ts:16 — 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.
R10 · Code Duplication · Duplicated block with local edits (31 matched lines × 2 locations) · ×1
  • 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 — 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.
R10 · Code Duplication · Duplicated block (30 lines × 2 locations) · ×1
  • Duplicated block (30 lines × 2 locations) 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-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.
R2 · Cyclomatic Complexity · Complex function SectionLayout (cyclomatic 37, cognitive 37) · ×1
  • Complex function SectionLayout (cyclomatic 37, cognitive 37) packages/ocom/ui-staff-shared/src/section-layout.tsx:37 — 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.
R2 · Cyclomatic Complexity · Complex function validateEnvNames (cyclomatic 33, cognitive 59) · ×1
  • Complex function validateEnvNames (cyclomatic 33, cognitive 59) packages/ocom-verification/archunit-tests/src/validate-env-names.cjs:286 — 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 29, cognitive 37) · ×1
  • Complex function (anonymous) (cyclomatic 29, cognitive 37) REDACTED:103 — (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.
R2 · Cyclomatic Complexity · Complex function checkFrontendArchitecture (cyclomatic 27, cognitive 32) · ×1
  • Complex function checkFrontendArchitecture (cyclomatic 27, cognitive 32) packages/cellix/archunit-tests/src/checks/frontend-architecture.ts:12 — 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.
R2 · Cyclomatic Complexity · Complex function validateEntries (cyclomatic 26, cognitive 42) · ×1
  • Complex function validateEntries (cyclomatic 26, cognitive 42) packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:119 — 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 26, cognitive 31) · ×1
  • Complex function (anonymous) (cyclomatic 26, cognitive 31) packages/ocom-verification/e2e-tests/src/contexts/community/tasks/create-community.ts:58 — (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.
R2 · Cyclomatic Complexity · Complex function checkLayeredArchitecture (cyclomatic 25, cognitive 36) · ×1
  • Complex function checkLayeredArchitecture (cyclomatic 25, cognitive 36) packages/cellix/archunit-tests/src/checks/circular-dependencies.ts:50 — checkLayeredArchitecture has cyclomatic complexity 25 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 22, cognitive 30) · ×1
  • Complex function (anonymous) (cyclomatic 22, cognitive 30) REDACTED:134 — (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.
R2 · Cyclomatic Complexity · Complex function StaffUserDetailContainer (cyclomatic 22, cognitive 18) · ×1
  • Complex function StaffUserDetailContainer (cyclomatic 22, cognitive 18) packages/ocom/ui-staff-route-user-management/src/components/staff-user-detail.container.tsx:32 — 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 21, cognitive 24) · ×1
  • Complex function (anonymous) (cyclomatic 21, cognitive 24) REDACTED:244 — (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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 21, cognitive 20) · ×1
  • Complex function (anonymous) (cyclomatic 21, cognitive 20) packages/ocom/application-services/src/contexts/community/member/member-management.ts:517 — (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.
R2 · Cyclomatic Complexity · Complex function detectChanges (cyclomatic 20, cognitive 23) · ×1
  • Complex function detectChanges (cyclomatic 20, cognitive 23) build-pipeline/scripts/detect-changes.cjs:137 — 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 19, cognitive 13) · ×1
  • Complex function (anonymous) (cyclomatic 19, cognitive 13) apps/ui-staff/src/hooks/use-staff-permissions.ts:87 — (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.
R2 · Cyclomatic Complexity · Complex function skipTemplateExpression (cyclomatic 18, cognitive 27) · ×1
  • Complex function skipTemplateExpression (cyclomatic 18, cognitive 27) packages/ocom-verification/archunit-tests/src/validate-env-names.cjs:44 — 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.
R2 · Cyclomatic Complexity · Complex function StaffRoutes (cyclomatic 18, cognitive 10) · ×1
  • Complex function StaffRoutes (cyclomatic 18, cognitive 10) apps/ui-staff/src/App.tsx:20 — 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 17, cognitive 25) · ×1
  • Complex function (anonymous) (cyclomatic 17, cognitive 25) REDACTED:241 — (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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 17, cognitive 24) · ×1
  • Complex function (anonymous) (cyclomatic 17, cognitive 24) apps/ui-staff/src/contexts/theme-context.tsx:92 — (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.
R2 · Cyclomatic Complexity · Complex function findEnvVarsInText (cyclomatic 15, cognitive 21) · ×1
  • Complex function findEnvVarsInText (cyclomatic 15, cognitive 21) packages/ocom-verification/archunit-tests/src/validate-env-names.cjs:204 — 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.
R2 · Cyclomatic Complexity · Complex function normalizeUserInfo (cyclomatic 15, cognitive 17) · ×1
  • Complex function normalizeUserInfo (cyclomatic 15, cognitive 17) packages/cellix/server-oauth2-mock-seedwork/src/helpers.ts:38 — 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.
R3 · Large Files · packages/ocom/graphql/src/schema/types/member.resolvers.ts · ×1
  • 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/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.
R3 · Large Files · packages/ocom/persistence/src/datasources/domain/property/property/property.domain-adapter.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/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.
R3 · Large Files · packages/ocom/application-services/src/contexts/community/member/member-management.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/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.
R3 · Large Files · packages/ocom/persistence/src/datasources/domain/user/staff-role/staff-role.domain-adapter.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 — 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.
R6 · Tooling · The declared test suite includes a file that cannot be loaded · ×1
  • The declared test suite includes a file that cannot be loaded packages/cellix/archunit-tests/src/typescript-config-conventions.test.ts:8 — 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.
R7 · Dead Code · Dead file (~86 LoC) · ×1
  • Dead file (~86 LoC) build-pipeline/scripts/get-pr-number.cjs — no import path from any entry point (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
R7 · Dead Code · Dead file (~26 LoC) · ×1
  • Dead file (~26 LoC) packages/ocom/graphql/src/schema/types/end-user-role.resolvers.ts — 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
R8 · Dependency Hygiene · Unused dependency '@ant-design/cli' · ×1
  • Unused dependency '@ant-design/cli' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@graphql-codegen/introspection' · ×1
  • Unused dependency '@graphql-codegen/introspection' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@graphql-codegen/typed-document-node' · ×1
  • Unused dependency '@graphql-codegen/typed-document-node' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Minor — 266 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×74
  • Orphaned file packages/ocom/ui-community-route-admin/src/components/members-list.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ocom/ui-community-route-admin/src/components/members-list.container.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ocom/ui-staff-shared/src/section-layout.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ocom/ui-staff-shared/src/section-layout.stories.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ocom/ui-staff-route-user-management/src/components/staff-role-create.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ocom/domain/src/domain/contexts/user/staff-user/staff-user.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ocom/ui-staff-route-user-management/src/components/staff-role-edit.container.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ocom/domain/src/domain/contexts/community/member/member-invitation.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ocom/ui-community-route-admin/src/components/members-invite-modal.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role-permissions.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ocom/ui-staff-route-user-management/src/components/staff-user-detail.container.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/cellix/event-bus-seedwork-node/src/node-event-bus.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file apps/ui-staff/src/contexts/theme-context.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ocom/ui-community-route-admin/src/components/members-list.stories.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ocom/ui-staff-route-user-management/src/components/staff-role-create.container.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ocom/persistence/src/datasources/readonly/community/community/community.read-repository.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ocom/data-sources-mongoose-models/src/models/role/vendor-user-role.model.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ocom/service-otel/src/otel-builder.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ocom/data-sources-mongoose-models/src/models/role/end-user-role.model.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ocom/ui-community-route-admin/src/components/members-accounts-edit.container.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ocom/ui-community-shared/src/components/member-profile.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ocom/ui-community-route-admin/src/section-layout.stories.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role-permissions.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 49 more in this group — see findings.md.
D24 · Comment Value · redundant comment · ×43
  • redundant comment apps/ui-community/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx:27 — "apollo link to add auth header" repeats the code it sits on: 5 of its 5 words (apollo, link, add, auth, header) are already in `export const ApolloLinkToAddAuthHeader = (auth: AuthContextProps): ApolloLink =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment apps/ui-community/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx:82 — "apollo link to add custom header" repeats the code it sits on: 5 of its 5 words (apollo, link, add, custom, header) are already in `export const ApolloLinkToAddCustomHeader = (headerName: string, headerValue: string | null | undefined, ifTrue?: boolean …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment apps/ui-staff/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx:27 — "apollo link to add auth header" repeats the code it sits on: 5 of its 5 words (apollo, link, add, auth, header) are already in `export const ApolloLinkToAddAuthHeader = (auth: AuthContextProps): ApolloLink =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment apps/ui-staff/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx:56 — "apollo link to add custom header" repeats the code it sits on: 5 of its 5 words (apollo, link, add, custom, header) are already in `export const ApolloLinkToAddCustomHeader = (headerName: string, headerValue: string | null | undefined, ifTrue?: boolean …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment build-pipeline/scripts/detect-changes.cjs:154 — 5 comments in this file only repeat the code they sit on (lines 154, 191, 204, 244, 250), for example "Check for infrastructure changes". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment build-pipeline/scripts/merge-coverage.js:102 — "Write merged content" repeats the code it sits on: 3 of its 3 words (write, merged, content) are already in `fs.writeFileSync(outputFile, mergedContent);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/cellix/server-oauth2-mock-seedwork/tests/multi-registration.test.ts:94 — "call authorize for h1 with its redirect" repeats the code it sits on: 3 of its 3 words (call, authorize, redirect) are already in `const authRes = await fetch(`${h1.baseUrl}/authorize?redirect_uri=${encodeURIComponent(cfg1.allowedRedirectUri)}`, { red …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/cellix/service-blob-storage/src/client-upload-signer.auth-header.test.ts:186 — "Generate auth header for text/plain" repeats the code it sits on: 4 of its 5 words (auth, header, text, plain) are already in `const authForText = await signer.createBlobWriteAuthorizationHeader({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/cellix/service-blob-storage/src/client-upload-signer.auth-header.test.ts:194 — "Generate auth header for application/json" repeats the code it sits on: 4 of its 5 words (auth, header, application, json) are already in `const authForJson = await signer.createBlobWriteAuthorizationHeader({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/ocom/application-services/src/contexts/community/member/create-member.test.ts:123 — "Mock the role repository to return a default role" repeats the code it sits on: 4 of its 5 words (mock, role, repository, default) are already in `mockRoleRepository.getByCommunityId.mockResolvedValue([`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/ocom/application-services/src/contexts/community/member/create-member.test.ts:133 — "Mock the member repository" repeats the code it sits on: 3 of its 3 words (mock, member, repository) are already in `mockMemberRepository.getNewInstance.mockResolvedValue(mockNewMember);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/ocom/application-services/src/contexts/community/member/create-member.test.ts:197 — "Mock the role repository to return a default role" repeats the code it sits on: 4 of its 5 words (mock, role, repository, default) are already in `mockRoleRepository.getByCommunityId.mockResolvedValue([mockDefaultRole]);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/ocom/application-services/src/contexts/community/member/create-member.test.ts:200 — "Mock the member repository" repeats the code it sits on: 3 of its 3 words (mock, member, repository) are already in `mockMemberRepository.getNewInstance.mockResolvedValue(mockNewMember);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/ocom/application-services/src/contexts/community/member/member-management.ts:38 — "Assign the default role to the member" repeats the code it sits on: 4 of its 4 words (assign, default, role, member) are already in `newMember.role = defaultRole as Domain.Contexts.Community.Role.EndUserRole.EndUserRoleEntityReference;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/ocom/application-services/src/contexts/community/member/member-management.ts:493 — "Find the account to remove" repeats the code it sits on: 3 of its 3 words (find, account, remove) are already in `const accountToRemove = member.accounts.find((acc) => acc.id === command.accountId);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1-activity-detail.value-objects.test.ts:82 — "ActivityTypeCode" repeats the code it sits on: 3 of its 3 words (activity, type, code) are already in `Scenario('Creating an activity type code with valid value "CREATED"', ({ When, Then }) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1-activity-detail.value-objects.test.ts:82 — "ActivityTypeCode" repeats the code it sits on: 3 of its 3 words (activity, type, code) are already in `Scenario('Creating an activity type code with valid value', ({ When, Then }) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/ocom/domain/src/domain/contexts/community/community/community.value-objects.test.ts:195 — "WhiteLabelDomain" repeats the code it sits on: 3 of its 3 words (white, label, domain) are already in `Scenario('Creating a white label domain with valid value', ({ When, Then }) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/ocom/domain/src/domain/contexts/community/member/member-account.value-objects.test.ts:174 — "AccountStatusCode" repeats the code it sits on: 3 of its 3 words (account, status, code) are already in `ScenarioOutline('Creating an account status code with valid value', ({ When, Then }, variables) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/ocom/domain/src/domain/contexts/community/member/member-custom-view.value-objects.test.ts:13 — 5 comments in this file only repeat the code they sit on (lines 13, 92, 143, 212, 311), for example "CustomViewName". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/ocom/domain/src/domain/contexts/community/member/member.value-objects.test.ts:103 — "CyberSourceCustomerId" repeats the code it sits on: 4 of its 4 words (cyber, source, customer, id) are already in `Scenario('Creating a CyberSourceCustomerId with valid value', ({ When, Then }) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role-community-permissions.test.ts:59 — 5 comments in this file only repeat the code they sit on (lines 59, 109, 159, 259, 309), for example "canManageEndUserRolesAndPermissions". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role-community-permissions.test.ts:58 — 5 comments in this file only repeat the code they sit on (lines 58, 108, 158, 258, 308), for example "canManageVendorUserRolesAndPermissions". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/ocom/domain/src/domain/contexts/property/property/property-listing-detail.value-objects.test.ts:252 — "ListingAgentEmail" repeats the code it sits on: 3 of its 3 words (listing, agent, email) are already in `Scenario('Creating a listing agent email with valid value', ({ When, Then }) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role-community-permissions.test.ts:51 — "canManageStaffRolesAndPermissions" repeats the code it sits on: 4 of its 4 words (manage, staff, roles, permissions) are already in `Scenario('Changing canManageStaffRolesAndPermissions with manage staff roles permission', ({ Given, When, Then }) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • + 18 more in this group — see findings.md.
D7 · Architectural Integrity · Classify ADR enforcement · ×34
  • Classify ADR enforcement: Use Markdown Any Decision Records (MADR) to track Architectural Decisions apps/docs/docs/decisions/0001-madr-architecture-decisions.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Use Open Telemetry to add observability to the project apps/docs/docs/decisions/0002-open-telemetry.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Use DDD Framework to build the data-access project apps/docs/docs/decisions/0003-domain-driven-design.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • 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 — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Use Passport/Visa for Access Management apps/docs/docs/decisions/0005-authorization.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Use Maps for the project apps/docs/docs/decisions/0006-maps.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Use SerenityJS to ensure delivering right features apps/docs/docs/decisions/0007-serenityjs.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: White label website using CraftJs + Blob Storage and Vercel apps/docs/docs/decisions/0008-white-label.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Automatically Refresh Screen on Application Update apps/docs/docs/decisions/0009-cache-purging.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: React Router Loader apps/docs/docs/decisions/0010-react-router-loaders.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Using Bicep for Infrastructure as Code instead of manual configuration of environments apps/docs/docs/decisions/0011-bicep.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Select a Linter: Oxlint vs Biome apps/docs/docs/decisions/0012-linter.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Select a Test Suite: Jest vs Vitest vs Node apps/docs/docs/decisions/0013-test-suite.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Select a Deployment Approach: AVM vs Bicep apps/docs/docs/decisions/0014-azure-infrastructure-deployments.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Addressing Node.js 16 End-of-Life in SonarCloud apps/docs/docs/decisions/0015-sonarcloud.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Bypassing SonarCloud Code Duplication Checks for Unit Tests apps/docs/docs/decisions/0016-sonarcloud-code-duplication-checks.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Chrome Content Overrides for FeatureFlags.json apps/docs/docs/decisions/0017-chrome-content-overrides.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Split Docusaurus Azure Pipeline into Separate Build and Deploy Stages apps/docs/docs/decisions/0018-docusaurus-azure-pipeline-stages.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Monorepo Structure with Turborepo apps/docs/docs/decisions/0019-monorepo-turborepo.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Azure DevOps Monorepo Pipeline Architecture apps/docs/docs/decisions/0020-azure-devops-monorepo-pipeline.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Bicep Resource Scoping Strategy apps/docs/docs/decisions/0021-bicep-resource-scoping-strategy.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Integrate Snyk for Security Scanning at Inception apps/docs/docs/decisions/0022-snyk-security-integration.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: TypeScript Go (tsgo) Migration apps/docs/docs/decisions/0023-tsgo-migration.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: Adopt Agent Skills Framework to Enforce MADR Standards in Code apps/docs/docs/decisions/0024-madr-agent-skills.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • 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 — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • + 9 more in this group — see findings.md.
P2 · Observability · Console output used as the logging channel · ×33
  • Console output used as the logging channel 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 77 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel 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 94 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel 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 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.
  • Console output used as the logging channel 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 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.
  • Console output used as the logging channel 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 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.
  • Console output used as the logging channel 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 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.
  • Console output used as the logging channel 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 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.
  • Console output used as the logging channel 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 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.
  • Console output used as the logging channel 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 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.
  • Console output used as the logging channel 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 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.
  • Console output used as the logging channel 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 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.
  • Console output used as the logging channel 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 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.
  • Console output used as the logging channel 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 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.
  • Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts:321 — `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.
  • Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/logger.ts:20 — `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.
  • Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/logger.ts:22 — `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.
  • Console output used as the logging channel REDACTED:150 — `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.
  • Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/manager.ts:74 — `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.
  • Console output used as the logging channel packages/cellix/server-oauth2-mock-seedwork/src/manager.ts:75 — `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.
  • Console output used as the logging channel 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 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.
  • Console output used as the logging channel 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 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.
  • Console output used as the logging channel 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 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.
  • Console output used as the logging channel 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 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.
  • Console output used as the logging channel 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 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.
  • Console output used as the logging channel 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 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.
  • + 8 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×25
  • Duplicated predicate apps/ui-community/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx:34 — `!access_token && typeof globalThis !== 'undefined' && !` appears character-identically in 2 files — apps/ui-community/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx, apps/ui-staff/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate apps/ui-community/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx:85 — `!headerValue || (ifTrue !== undefined && ifTrue === false)` appears character-identically in 2 files — apps/ui-community/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx, apps/ui-staff/src/components/ui/organisms/apollo-connection/apollo-client-links.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/ocom-verification/acceptance-api/src/contexts/community/step-definitions/create-community.steps.ts:98 — `!isFieldMentioned && !isValidationPattern` appears character-identically in 2 files — packages/ocom-verification/acceptance-api/src/contexts/community/step-definitions/create-community.steps.ts, packages/ocom-verification/acceptance-api/src/contexts/staff-role/step-definitions/staff-role-management.steps.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate apps/ui-staff/src/App.tsx:34 — `canManageUsers || canAssignStaffRoles || canViewStaffUsers || canManageStaffRolesAndPermissions || canViewRoles || canAddRole || canEditRole…` appears character-identically in 2 files — apps/ui-staff/src/App.tsx, packages/ocom/ui-staff-shared/src/section-layout.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate apps/ui-community/src/contexts/theme-context.tsx:169 — `currentTokens?.type === 'custom' || currentTokens?.type === 'light'` appears character-identically in 2 files — apps/ui-community/src/contexts/theme-context.tsx, apps/ui-staff/src/contexts/theme-context.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/ocom/domain/src/domain/contexts/community/member/member-invitation.ts:69 — `domainPermissions.canManageMembers || domainPermissions.isSystemAccount` appears character-identically in 2 files — packages/ocom/domain/src/domain/contexts/community/member/member-invitation.ts, packages/ocom/domain/src/domain/contexts/community/member/member.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/ocom/ui-community-route-admin/src/components/members-accounts-add.tsx:16 — `endUser.displayName || endUser.personalInformation?.contactInformation?.email || endUser.id` appears character-identically in 2 files — packages/ocom/ui-community-route-admin/src/components/members-accounts-add.tsx, packages/ocom/ui-community-route-admin/src/components/members-accounts-edit.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate .agents/skills/cellix-tdd/evaluator/evaluate-cellix-tdd.ts:789 — `entry.comparison && !entry.comparison.matches` appears character-identically in 2 files — .agents/skills/cellix-tdd/evaluator/evaluate-cellix-tdd.ts, .agents/skills/cellix-tdd/evaluator/run-integration.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/ocom/application-services/src/contexts/user/staff-role/create-default-roles.ts:13 — `error instanceof Error && (error.name === 'NotFoundError' || error.message.toLowerCase().includes('not found'))` appears character-identically in 4 files — packages/ocom/application-services/src/contexts/user/staff-role/create-default-roles.ts, packages/ocom/application-services/src/contexts/user/staff-role/query-by-id.ts, packages/ocom/application-services/src/contexts/user/staff-role/query-by-role-name.ts, packages/ocom/application-services/src/contexts/user/staff-user/create-if-not-exists.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate apps/ui-community/src/contexts/theme-context.tsx:148 — `event.metaKey && event.shiftKey && event.key === 'k'` appears character-identically in 2 files — apps/ui-community/src/contexts/theme-context.tsx, apps/ui-staff/src/contexts/theme-context.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate apps/ui-community/src/contexts/theme-context.tsx:122 — `extractFromLocal && extractFromLocal.type === 'custom'` appears character-identically in 2 files — apps/ui-community/src/contexts/theme-context.tsx, apps/ui-staff/src/contexts/theme-context.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate apps/ui-community/src/contexts/theme-context.tsx:104 — `extractFromLocal && extractFromLocal.type === 'dark'` appears character-identically in 2 files — apps/ui-community/src/contexts/theme-context.tsx, apps/ui-staff/src/contexts/theme-context.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate apps/ui-community/src/contexts/theme-context.tsx:113 — `extractFromLocal && extractFromLocal.type === 'light'` appears character-identically in 2 files — apps/ui-community/src/contexts/theme-context.tsx, apps/ui-staff/src/contexts/theme-context.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/ocom/ui-staff-shared/src/section-layout.container.tsx:26 — `href.includes('dev') || href.includes('localhost')` appears character-identically in 2 files — packages/ocom/ui-staff-shared/src/section-layout.container.tsx, packages/ocom/ui-staff-shared/src/section-layout.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/ocom-verification/acceptance-api/src/contexts/staff/step-definitions/staff-landing.steps.ts:26 — `normalized === 'finance' || normalized === 'tech admin' || normalized === 'service line owner' || normalized === 'case manager'` appears character-identically in 2 files — packages/ocom-verification/acceptance-api/src/contexts/staff/step-definitions/staff-landing.steps.ts, packages/ocom-verification/acceptance-ui/src/contexts/staff/step-definitions/create-staff-landing.steps.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role-community-permissions.ts:24 — `permissions.canManageEndUserRolesAndPermissions || permissions.isSystemAccount` appears character-identically in 5 files — packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role-community-permissions.ts, packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role-property-permissions.ts, packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role-service-permissions.ts, packages/ocom/domain/src/domain/contexts/community/role/end-user-role/end-user-role-service-ticket-permissions.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role-community-permissions.ts:27 — `permissions.canManageStaffRolesAndPermissions || permissions.isSystemAccount` appears character-identically in 10 files — packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role-community-permissions.ts, packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role-finance-permissions.ts, packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role-property-permissions.ts, packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role-role-permissions.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:142 — `permissions.canManageTickets || permissions.canAssignTickets || (permissions.canCreateTickets && permissions.isEditingOwnTicket) || (permiss…` appears character-identically in 2 files — packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts, packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1.aggregate.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1-message.entity.ts:50 — `permissions.canManageTickets || permissions.isSystemAccount` appears character-identically in 3 files — packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1-message.entity.ts, packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1-message.ts, packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1-revision-request.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role-community-permissions.ts:19 — `permissions.canManageVendorUserRolesAndPermissions || permissions.isSystemAccount` appears character-identically in 6 files — packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role-community-permissions.ts, packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role-property-permissions.ts, packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role-service-permissions.ts, packages/ocom/domain/src/domain/contexts/community/role/vendor-user-role/vendor-user-role-service-ticket-permissions.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/ocom/domain/src/domain/contexts/user/end-user/end-user-contact-information.ts:26 — `permissions.isEditingOwnAccount || permissions.canManageEndUsers` appears character-identically in 3 files — packages/ocom/domain/src/domain/contexts/user/end-user/end-user-contact-information.ts, packages/ocom/domain/src/domain/contexts/user/end-user/end-user-identity-details.ts, packages/ocom/domain/src/domain/contexts/user/end-user/end-user.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/ocom/domain/src/domain/contexts/user/vendor-user/vendor-user-contact-information.ts:36 — `permissions.isEditingOwnAccount || permissions.canManageVendorUsers` appears character-identically in 2 files — packages/ocom/domain/src/domain/contexts/user/vendor-user/vendor-user-contact-information.ts, packages/ocom/domain/src/domain/contexts/user/vendor-user/vendor-user-identity-details.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:123 — `permissions.isSystemAccount || (permissions.canCreateTickets && permissions.isEditingOwnTicket) || (permissions.canWorkOnTickets && permissi…` appears character-identically in 2 files — packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts, packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1.aggregate.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/ocom/domain/src/domain/contexts/property/property/property-listing-detail-additional-amenity.entity.ts:22 — `permissions.isSystemAccount || permissions.canManageProperties || (permissions.canEditOwnProperty && permissions.isEditingOwnProperty)` appears character-identically in 5 files — packages/ocom/domain/src/domain/contexts/property/property/property-listing-detail-additional-amenity.entity.ts, packages/ocom/domain/src/domain/contexts/property/property/property-listing-detail-bedroom-detail.entity.ts, packages/ocom/domain/src/domain/contexts/property/property/property-listing-detail.entity.ts, packages/ocom/domain/src/domain/contexts/property/property/property-location.entity.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:155 — `permissions.isSystemAccount || permissions.canManageTickets` appears character-identically in 3 files — packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts, packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1-activity-detail.ts, packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1.aggregate.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
DM2 · Strongly-typed ids · Primitive id on a domain type · ×13
  • Primitive id on a domain type: DomainEventBase.aggregateId packages/cellix/domain-seedwork/src/domain-seedwork/domain-event.ts:16 — `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.
  • Primitive id on a domain type: EndUser.externalId packages/ocom/domain/src/domain/contexts/user/end-user/end-user.ts:93 — `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.
  • Primitive id on a domain type: Member.cybersourceCustomerId packages/ocom/domain/src/domain/contexts/community/member/member.ts:212 — `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.
  • Primitive id on a domain type: Member.communityId packages/ocom/domain/src/domain/contexts/community/member/member.ts:221 — `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.
  • Primitive id on a domain type: StaffUser.externalId packages/ocom/domain/src/domain/contexts/user/staff-user/staff-user.ts:149 — `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.
  • Primitive id on a domain type: VendorUser.externalId packages/ocom/domain/src/domain/contexts/user/vendor-user/vendor-user.ts:97 — `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.
  • Primitive id on a domain type: ViolationTicketV1.communityId packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1.aggregate.ts:209 — `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.
  • Primitive id on a domain type: ViolationTicketV1.requestorId packages/ocom/domain/src/domain/contexts/case/violation-ticket/v1/violation-ticket-v1.aggregate.ts:231 — `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.
  • Primitive id on a domain type: MemberInvitation.communityId packages/ocom/domain/src/domain/contexts/community/member/member-invitation.ts:173 — `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.
  • Primitive id on a domain type: ServiceTicketV1.communityId packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:234 — `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.
  • Primitive id on a domain type: ServiceTicketV1.requestorId packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:256 — `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.
  • Primitive id on a domain type: ServiceTicketV1.assignedToId packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:267 — `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.
  • Primitive id on a domain type: ServiceTicketV1.serviceId packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1.aggregate.ts:278 — `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.
D20 · ADR Quality · ADR has no Consequences section · ×5
  • ADR has no Consequences section apps/docs/docs/decisions/0002-open-telemetry.md:14 — apps/docs/docs/decisions/0002-open-telemetry.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Consequences section apps/docs/docs/decisions/0004-identity-access.md:13 — apps/docs/docs/decisions/0004-identity-access.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Consequences section apps/docs/docs/decisions/0005-authorization.md:14 — apps/docs/docs/decisions/0005-authorization.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Consequences section apps/docs/docs/decisions/0006-maps.md:13 — apps/docs/docs/decisions/0006-maps.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Consequences section apps/docs/docs/decisions/0007-serenityjs.md:14 — apps/docs/docs/decisions/0007-serenityjs.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
D10 · Test Quality · Mock-dominated test · ×4
  • Mock-dominated test: removes a member through domain operation packages/ocom/application-services/src/contexts/community/member/member-management.operations.test.ts:138 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: passes reason to bulk deactivate and bulk remove domain methods packages/ocom/application-services/src/contexts/community/member/member-management.operations.test.ts:149 — This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: starts infrastructure, validates state, creates the cast, and resets during cleanup packages/cellix/serenity-framework/src/cucumber/world.test.ts:6 — This test sets up 8 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: allows additional handlers after the first registration packages/cellix/api-core/tests/cellix.test.ts:222 — This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
M4 · Documentation accuracy · README/code drift · ×4
  • README/code drift packages/cellix/domain-seedwork/readme.md:11 — packages/cellix/domain-seedwork/readme.md links to `./src/passport-seedwork/README.md`, but `packages/cellix/domain-seedwork/src/passport-seedwork/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift packages/ocom/ui-staff-shared/README.md:172 — 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.
  • README/code drift packages/cellix/mongoose-seedwork/src/mongoose-seedwork/README.md:11 — 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.
  • README/code drift packages/cellix/ui-core/src/components/molecules/README.md:18 — 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.
D30 · Dependency Vulnerabilities · Low CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D19 · Documentation Quality · Documentation · ×2
  • Documentation: no build, run or usage example apps/api/readme.md:1 — `api` is runnable (a `start` script in `REDACTED`) and neither `apps/api/readme.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example apps/ui-staff/README.md:1 — `ui-staff` is runnable (a `start` script in `REDACTED`) and neither `apps/ui-staff/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
D20 · ADR Quality · ADR considers only one option · ×2
  • ADR considers only one option apps/docs/docs/decisions/0005-authorization.md:30 — `apps/docs/docs/decisions/0005-authorization.md:30` lists one option, one sub-heading, so the record shows no choice being made. List the alternatives that were rejected and why, or remove the section.
  • ADR considers only one option apps/docs/docs/decisions/0009-cache-purging.md:27 — `apps/docs/docs/decisions/0009-cache-purging.md:27` lists one option, "**Option 1: Polling Mechanism**: Implement a polling mechanism that periodica...", so the record shows no choice being made. List the alternatives that were rejected and why, or remove the section.
D20 · ADR Quality · ADR consequences name no cost · ×2
  • ADR consequences name no cost apps/docs/docs/decisions/0027-typescript-6-upgrade.md:36 — `apps/docs/docs/decisions/0027-typescript-6-upgrade.md:36` lists its consequences as good-polarity items only, and none is a drawback, while other records in `apps/docs/docs/decisions` record drawbacks the same way. State what this decision costs or rules out.
  • ADR consequences name no cost apps/docs/docs/decisions/0030-typescript-7-upgrade.md:36 — `apps/docs/docs/decisions/0030-typescript-7-upgrade.md:36` lists its consequences as good-polarity items only, and none is a drawback, while other records in `apps/docs/docs/decisions` record drawbacks the same way. State what this decision costs or rules out.
D20 · ADR Quality · ADR decides a question another record already decided · ×2
  • ADR decides a question another record already decided apps/docs/docs/decisions/0004-identity-access.md:13 — apps/docs/docs/decisions/0004-identity-access.md and apps/docs/docs/decisions/0002-open-telemetry.md are both in force and decide the same question: this record weighs the option it chose and chooses "option 1", and neither names the other. If this record replaces the earlier one, say so ("Supersedes …") and mark the earlier one superseded; if both hold, state how they relate.
  • ADR decides a question another record already decided apps/docs/docs/decisions/0006-maps.md:13 — apps/docs/docs/decisions/0006-maps.md and apps/docs/docs/decisions/0004-identity-access.md are both in force and decide the same question: this record weighs the option it chose and chooses "option 2", and neither names the other. If this record replaces the earlier one, say so ("Supersedes …") and mark the earlier one superseded; if both hold, state how they relate.
S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×2
  • No app-layer HTTPS enforcement detected packages/cellix/server-oauth2-mock-seedwork/src/manager.ts:73 — `a.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
  • No app-layer HTTPS enforcement detected packages/cellix/server-oauth2-mock-seedwork/src/server.ts:33 — `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
X7 · Silent fallback defaults · Silent fallback default in catch · ×2
  • Silent fallback default in catch packages/ocom-verification/acceptance-ui/src/contexts/staff-role/questions/staff-role-screen.ts:49 — `ErrorFeedbackContaining` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch packages/ocom-verification/acceptance-ui/src/contexts/staff-role/questions/staff-role-screen.ts:67 — `ValidationErrorMatching` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
AX6 · Interface segregation · Fat interface · ×1
  • Fat interface: MemberApplicationService (18 required operations) packages/ocom/application-services/src/contexts/community/member/index.ts:38 — `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.
C2 · Access Controls · No named authorization policies · ×1
  • No named authorization policies packages/cellix/serenity-framework/src/infrastructure/api-infrastructure.ts:210 — 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.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 7 significant file(s) lose their only recent owner: packages/cellix/server-oauth2-mock-seedwork/src/file-user-store.ts, apps/server-oauth2-mock/src/index.ts, packages/cellix/server-oauth2-mock-seedwork/src/types.ts, packages/ocom/service-token-validation/src/verified-token-service.ts, packages/cellix/archunit-tests/src/utils/member-ordering-rule.ts, packages/ocom/domain/src/domain/contexts/property/property/property-location.entity.ts, packages/cellix/ui-core/src/components/molecules/component-query-loader/index.tsx. Pair on, review, or document these before any departure.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 51 project(s) overshoot their size bounds, lowering Project Cohesion to 9.6/10. The most over is `packages/ocom/domain` (7592 LoC, 424 module-visible types across 31 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1
  • Further orphaned files (smaller) — 74 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role.ts, packages/ocom/ui-community-route-admin/src/components/members-list.tsx, packages/ocom/domain/src/domain/contexts/user/staff-user/staff-user.ts, packages/ocom/domain/src/domain/contexts/community/member/member-invitation.ts, packages/ocom/ui-community-route-admin/src/components/members-list.container.tsx, packages/ocom/domain/src/domain/contexts/user/staff-role/staff-role-permissions.ts, packages/ocom/ui-staff-shared/src/section-layout.tsx, packages/ocom/ui-staff-shared/src/section-layout.stories.tsx (and 66 more) (76 orphaned of 244 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 244 of the 1026 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
IC1 · Incompleteness & stubs · Empty method body · ×1
  • Empty method body packages/ocom/ui-community-route-accounts/.storybook/preview.tsx:15 — `onSigninCallback` has an empty body — confirm it's an intentional no-op and not an unfinished method.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — 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`.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation REDACTED:72 — `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`.
R7 · Dead Code · Unused export 'GetModelFunction' · ×1
  • Unused export 'GetModelFunction' packages/cellix/mongoose-seedwork/src/mongoose-seedwork/mongo-connection.ts:6 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'GetModelFunctionWithSchema' · ×1
  • Unused export 'GetModelFunctionWithSchema' packages/cellix/mongoose-seedwork/src/mongoose-seedwork/mongo-connection.ts:7 — Nothing imports this binding — it is safe to review for removal.
R8 · Dependency Hygiene · Type-only dependency 'mongoose' in production deps · ×1
  • Type-only dependency 'mongoose' in production deps apps/server-mongodb-memory-mock/src/seed/seed.ts:8 — Every import is type-only — move it to devDependencies.
R8 · Dependency Hygiene · Test-only dependency '@ant-design/icons' in production deps · ×1
  • Test-only dependency '@ant-design/icons' in production deps packages/ocom/ui-shared/package.json:32 — Only test files import it (first: packages/ocom/ui-shared/src/components/organisms/vertical-tabs/index.stories.tsx:1) — move it to devDependencies.
X5 · Nullable reference types · Strict null checking is not enabled everywhere the repository type-checks · ×1
  • Strict null checking is not enabled everywhere the repository type-checks — 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.
Minor — 6 finding(s)
D24 · Comment Value · doc comments repeat the names · ×5
  • doc comments repeat the names packages/cellix/server-oauth2-mock-seedwork/src/portal-discovery.ts:35 — 0 of 18 documented parameters and 1 of 38 summaries in `@cellix/server-oauth2-mock-seedwork` only repeat the member or parameter name (e.g. "Options for ." for `DiscoverPortalConfigsOptions`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/cellix/ui-core/src/components/molecules/component-query-loader/index.tsx:5 — 0 of 2 documented parameters and 2 of 14 summaries in `@cellix/ui-core` only repeat the member or parameter name (e.g. "Props for ." for `ComponentQueryLoaderProps`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/ocom/domain/src/domain/contexts/case/service-ticket/v1/service-ticket-v1-message.entity.ts:9 — 0 of 1 documented parameters and 7 of 67 summaries in `@ocom/domain` only repeat the member or parameter name (e.g. "Props for ServiceTicketV1Message" for `ServiceTicketV1MessageProps`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/ocom/graphql-handler/src/handler.ts:10 — 1 of 4 documented parameters and 0 of 2 summaries in `@ocom/graphql-handler` only repeat the member or parameter name (e.g. "The Apollo Server service instance" for `apolloServerService`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/ocom/service-apollo-server/src/index.ts:29 — 0 of 0 documented parameters and 1 of 10 summaries in `@ocom/service-apollo-server` only repeat the member or parameter name (e.g. "Allow batched HTTP requests." for `allowBatchedHttpRequests`). Delete the restating tags, or add what the name does not say.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: @ocom/ui-staff-shared — @ocom/ui-staff-shared: abstractness 0.00, instability 0.25, distance 0.75 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ecd2d2f96233407da50c00128e2e7c95/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ecd2d2f96233407da50c00128e2e7c95/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/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 .25artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update52artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .11artifacts/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 Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json

Run 01a1b8ca-dc0d-770a-be0b-bc252a5c86ff · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md