medusajs/medusa

Executive summary

medusajs/medusa is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back because it has pieces of business logic tied to the database or web code. It scores 35 out of 100, which the At risk rating leaves unchanged.

Domain Modelling, at 17, is the weakest lens and counts most in the score. The best first step is moving database and web code out of the business core, worth about 15 points. Raising Domain Modelling to 70 would lift the score to about 50.

165 pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Seventy-two known security holes in the packages the code depends on can be used by attackers, and forty-four secrets can leak from the build pipeline. Pinning each tool to an exact version, updating the vulnerable packages and limiting each secret to its own step would close these risks. Passing outside input through environment variables would fix the three pipeline steps that put outside input straight into a shell command, and fixing the weaknesses the scanner points to would deal with the three security weaknesses in the code. The 26 controls that only work with a mouse need to work with the keyboard, or to become a real button.

The product code is 2,522 lines, about €97,000 to rebuild.

Code Health 91 ★ Exemplary Architecture 81 Adequate, capped by Boundary Type-Coupling Maturity 68 Adequate, capped by Architecture documentation Production Readiness 39 Weak, capped by Dependency Hygiene, Dependency Hygiene, Observability and Security & performance tooling Security and Compliance 66 Adequate, capped by Static Analysis (SAST), Dependency Vulnerabilities and Supply-chain Provenance & Signing Domain Modelling 17 ⚠ Critical, capped by Domain ↔ infrastructure boundary Accessibility 44 Weak, capped by Keyboard semantics Performance 100 ★ Exemplary

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

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

Domain Modelling 17 · counts for 45%Production Readiness 39 · counts for 25%Accessibility 44 · counts for 14%Security and Compliance 66 · counts for 8%Maturity 68 · counts for 4%Architecture 81 · counts for 2%Code Health 91 · counts for 1%Performance 100 · counts for 1%

If Domain Modelling rose from 17 to 70, the lowest score rated Strong, the score would rise from 35 to about 50.

Code composition: what the lines of code are

Product code 2%Tests 98%

New since the last survey: 288 findings

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

Test Quality · Skipped test: should export the appropriate linkable configuration packages/modules/rbac/integration-tests/__tests__/rbac.spec.ts
Test Quality · Skipped test: should release lock in case of timeout failure packages/modules/providers/locking-postgres/integration-tests/__tests__/index.spec.ts
Test Quality · Skipped test: test update performance packages/modules/product/integration-tests/__tests__/product-module-service/products.spec.ts
Test Quality · Skipped test: set the points to null when explicitly set to null packages/core/utils/src/dml/integration-tests/__tests__/entity.spec.ts
Test Quality · Skipped test: should benchmark serializers with autocannon load testing packages/core/utils/src/dal/mikro-orm/__tests__/mikro-orm-serializer.spec.ts
Test Quality · Skipped test: should return 401 when admin is not authenticated packages/core/framework/src/http/__tests__/index.spec.ts
Test Quality · Skipped test: should add, remove and delete price list prices in batch successfully integration-tests/modules/__tests__/price-lists/admin/price-lists.spec.ts
Test Quality · Skipped test: should create a customer integration-tests/modules/__tests__/customer/store/create-customer.spec.ts
Test Quality · Skipped test: should throw an error upon logging in with a non existing auth user integration-tests/modules/__tests__/auth/admin/email-password-provider.spec.ts
Test Quality · Skipped test: Deletes a user and their analytics config integration-tests/http/__tests__/user/admin/user.spec.ts
Test Quality · Skipped test: should throw error when required params are missing integration-tests/http/__tests__/shipping-option/admin/shipping-option.spec.ts
Test Quality · Skipped test: should add rules to a shipping option successfully integration-tests/http/__tests__/shipping-option/admin/shipping-option.spec.ts
Test Quality · Skipped test: should add two promotions and remove one from cart using delete integration-tests/http/__tests__/promotions/admin/promotions.spec.ts
Test Quality · Skipped test: should add two promotions and remove one from cart using update integration-tests/http/__tests__/promotions/admin/promotions.spec.ts
Test Quality · Skipped test: throws an error if invalid ID is sent integration-tests/http/__tests__/product-category/admin/product-category.spec.ts
Test Quality · Skipped test: returns all products if passed PK doesn't have associated channels integration-tests/http/__tests__/product/store/product.spec.ts
Test Quality · Skipped test: should return 404 when the requested variant doesn't exist integration-tests/http/__tests__/product/store/product.spec.ts
Test Quality · Skipped test: correctly returns a product if passed PK has no associated SCs integration-tests/http/__tests__/product/store/product.spec.ts
Test Quality · Skipped test: returns a list of ordered products by variants title DESC integration-tests/http/__tests__/product/store/product.spec.ts
Test Quality · Skipped test: returns a list of ordered products by variants prices DESC integration-tests/http/__tests__/product/store/product.spec.ts
Test Quality · Skipped test: returns a list of ordered products by variants prices ASC integration-tests/http/__tests__/product/store/product.spec.ts
Test Quality · Skipped test: returns gift card product integration-tests/http/__tests__/product/store/product.spec.ts
Test Quality · Skipped test: returns non gift card products integration-tests/http/__tests__/product/store/product.spec.ts
Test Quality · Skipped test: should list only categories that are public and active integration-tests/http/__tests__/product/store/product.spec.ts
Test Quality · Skipped test: should return prices not in price list for list product endpoint integration-tests/http/__tests__/product/admin/product.spec.ts
Test Quality · Skipped test: returns a list of products filtered by discount condition id integration-tests/http/__tests__/product/admin/product.spec.ts
Test Quality · Skipped test: should return products filtered by price_list_id integration-tests/http/__tests__/product/admin/product.spec.ts
Test Quality · Skipped test: Sets variant ranks when creating a product integration-tests/http/__tests__/product/admin/product.spec.ts
Test Quality · Skipped test: updates a product (variant ordering) integration-tests/http/__tests__/product/admin/product.spec.ts
Test Quality · Skipped test: successfully deletes a product variant and its associated prices integration-tests/http/__tests__/product/admin/product.spec.ts
Test Quality · Skipped test: successfully deletes a product and any prices associated with one of its variants integration-tests/http/__tests__/product/admin/product.spec.ts
Test Quality · Skipped test: successfully updates a variant's price by changing an existing price (given a region_id) integration-tests/http/__tests__/product/admin/variant.spec.ts
Test Quality · Skipped test: successfully updates a variant's prices by updating an existing price (using region_id) and adding another price integration-tests/http/__tests__/product/admin/variant.spec.ts
Test Quality · Skipped test: successfully deletes a region price integration-tests/http/__tests__/product/admin/variant.spec.ts
Test Quality · Skipped test: successfully updates a variants prices by deleting both a currency and region price integration-tests/http/__tests__/product/admin/variant.spec.ts
Test Quality · Skipped test: lists only price lists with customer_group integration-tests/http/__tests__/price-list/admin/price-list.spec.ts
Test Quality · Skipped test: should throw an error when fetching draft order integration-tests/http/__tests__/order/store/order.spec.ts
Dependency Hygiene · Deprecated: @types/chalk REDACTED
Dependency Hygiene · Deprecated: @types/commander REDACTED
Dependency Hygiene · Deprecated: rollup-plugin-ts REDACTED
Dependency Hygiene · Deprecated: uuid REDACTED
Dependency Hygiene · Deprecated: lodash.isequal packages/admin/dashboard/package.json
Dependency Hygiene · Deprecated: @readme/json-schema-ref-parser REDACTED
Dependency Hygiene · Deprecated: lodash.isequal packages/design-system/ui/package.json
Dependency Hygiene · Deprecated: eslint packages/eslint-plugin/package.json
Dependency Hygiene · Deprecated: lodash.isequal packages/plugins/draft-order/package.json
Dependency Hygiene · Deprecated: eslint www/apps/api-reference/package.json
Dependency Hygiene · Deprecated: eslint www/apps/book/package.json
Dependency Hygiene · Deprecated: eslint www/apps/cloud/package.json
Dependency Hygiene · Deprecated: eslint www/apps/resources/package.json
Dependency Hygiene · Deprecated: eslint www/apps/ui/package.json
Dependency Hygiene · Deprecated: eslint www/apps/user-guide/package.json
Dependency Hygiene · Deprecated: eslint www/package.json
Dependency Hygiene · Deprecated: eslint-plugin-markdown www/package.json
Dependency Hygiene · Deprecated: eslint www/packages/docs-ui/package.json
Dependency Hygiene · Deprecated: react-uuid www/packages/docs-ui/package.json
Dependency Hygiene · Deprecated: eslint REDACTED
Dependency Hygiene · Deprecated: eslint www/utils/packages/docs-generator/package.json
Dependency Hygiene · Deprecated: eslint www/utils/packages/typedoc-plugin-custom/package.json
Dependency Hygiene · Deprecated: eslint www/utils/packages/typedoc-plugin-workflows/package.json
Boundary Type-Coupling · Cross-context type AuthLoginResponse (js-sdk → dashboard) packages/admin/dashboard/src/hooks/api/auth.tsx
Boundary Type-Coupling · Cross-context type AdminCreateShippingOption (types → dashboard) packages/admin/dashboard/src/hooks/api/shipping-options.tsx
Boundary Type-Coupling · Cross-context type AdminAcceptInviteResponse (types → dashboard) packages/admin/dashboard/src/hooks/api/invites.tsx
Boundary Type-Coupling · Cross-context type Filter (search → dashboard) packages/admin/dashboard/src/components/table/data-table/data-table-query/data-table-query.tsx
Boundary Type-Coupling · Cross-context type DataTableColumnAlignment (ui → dashboard) packages/admin/dashboard/src/lib/table/table-adapters.ts
Boundary Type-Coupling · Cross-context type Filter (search → dashboard) packages/admin/dashboard/src/hooks/table/filters/use-order-table-filters.tsx
Boundary Type-Coupling · Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/payment-collection/steps/create-payment-session.ts
Boundary Type-Coupling · Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/payment-collection/steps/update-payment-session.ts
Boundary Type-Coupling · Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/cart/workflows/refund-payment-recreate-payment-session.ts
Boundary Type-Coupling · Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/cart/steps/confirm-inventory.ts
Boundary Type-Coupling · Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/cart/utils/find-matching-line-item.ts
Boundary Type-Coupling · Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/cart/steps/get-line-item-pricing-quantities.ts
Boundary Type-Coupling · Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/cart/steps/validate-variant-prices.ts
Boundary Type-Coupling · Cross-context type CreateShippingOptionsWorkflowInput (types → core-flows) packages/core/core-flows/src/fulfillment/workflows/create-shipping-options.ts
Boundary Type-Coupling · Cross-context type UpdateShippingOptionsWorkflowInput (types → core-flows) packages/core/core-flows/src/fulfillment/workflows/update-shipping-options.ts
Boundary Type-Coupling · Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/cart/utils/prepare-line-item-data.ts
Boundary Type-Coupling · Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/cart/utils/prepare-line-item-data.ts
Boundary Type-Coupling · Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/cart/workflows/confirm-variant-inventory.ts
Boundary Type-Coupling · Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/order/workflows/payments/create-order-refund-credit-lines.ts
Boundary Type-Coupling · Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/inventory/steps/delete-inventory-items.ts
Boundary Type-Coupling · Cross-context type PromotionActions (utils → core-flows) packages/core/core-flows/src/draft-order/steps/update-draft-order-promotions.ts
Boundary Type-Coupling · Cross-context type PromotionActions (utils → core-flows) packages/core/core-flows/src/draft-order/workflows/refresh-draft-order-adjustments.ts
Boundary Type-Coupling · Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/payment/workflows/refund-payment.ts
Boundary Type-Coupling · Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/draft-order/workflows/add-draft-order-shipping-methods.ts
Boundary Type-Coupling · Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/draft-order/steps/restore-draft-order-shipping-methods.ts
Boundary Type-Coupling · Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/draft-order/steps/update-draft-order-shipping-metod.ts
Boundary Type-Coupling · Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/draft-order/workflows/update-draft-order-shipping-method.ts
Boundary Type-Coupling · Cross-context type RegisterModuleJoinerConfig (modules-sdk → framework) packages/core/framework/src/medusa-app-loader.ts
Boundary Type-Coupling · Cross-context type AdminCreateShippingOption (types → js-sdk) packages/core/js-sdk/src/admin/shipping-option.ts
Boundary Type-Coupling · Cross-context type TransactionHandlerType (utils → orchestration) packages/core/orchestration/src/transaction/distributed-transaction.ts
Boundary Type-Coupling · Cross-context type TransactionHandlerType (utils → orchestration) packages/core/orchestration/src/transaction/distributed-transaction.ts
Boundary Type-Coupling · Cross-context type TransactionHandlerType (utils → orchestration) packages/core/orchestration/src/transaction/distributed-transaction.ts
Boundary Type-Coupling · Cross-context type TransactionHandlerType (utils → orchestration) packages/core/orchestration/src/transaction/distributed-transaction.ts
Boundary Type-Coupling · Cross-context type TransactionHandlerType (utils → orchestration) packages/core/orchestration/src/transaction/distributed-transaction.ts
Boundary Type-Coupling · Cross-context type Filter (search → types) packages/core/types/src/product/common.ts
Boundary Type-Coupling · Cross-context type Filter (search → types) packages/core/types/src/product/common.ts
Boundary Type-Coupling · Cross-context type Filter (search → types) packages/core/types/src/http/product/common.ts
Boundary Type-Coupling · Cross-context type Filter (search → types) packages/core/types/src/http/product/store/queries.ts
Boundary Type-Coupling · Cross-context type Filter (search → types) packages/core/types/src/http/product/admin/queries.ts
Boundary Type-Coupling · Cross-context type Filter (search → types) packages/core/types/src/http/promotion/admin/queries.ts

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

Fixed since the last survey: 96 findings

These 96 critical or serious findings were in the previous survey, on 12 October 2026, and are gone from this one.

Dependency Hygiene · Floating npm dependency: tailwind
License Compliance · Banned license: tailwind
Static Analysis (SAST) · High: REDACTED .github/actions/cache-deps/action.yml
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED .github/workflows/create-linear-issue-on-pr.yml
Static Analysis (SAST) · High: REDACTED .github/workflows/create-linear-issue-on-pr.yml
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: watchdog-untrusted-context-laundered-through-step-output REDACTED
Static Analysis (SAST) · High: watchdog-untrusted-context-laundered-through-step-output REDACTED
Static Analysis (SAST) · High: watchdog-untrusted-context-laundered-through-step-output REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: watchdog-untrusted-context-laundered-through-step-output REDACTED
Static Analysis (SAST) · High: watchdog-untrusted-context-laundered-through-step-output REDACTED
Static Analysis (SAST) · High: REDACTED .github/workflows/dx-triage-doc-fixes.yml
Static Analysis (SAST) · High: REDACTED .github/workflows/dx-triage-doc-fixes.yml
Static Analysis (SAST) · High: REDACTED .github/workflows/fix-bug-action.yml
Static Analysis (SAST) · High: REDACTED .github/workflows/fix-bug-action.yml
Static Analysis (SAST) · High: REDACTED .github/workflows/fix-bug-action.yml
Static Analysis (SAST) · High: REDACTED .github/workflows/fix-bug-action.yml
Static Analysis (SAST) · High: REDACTED .github/workflows/fix-bug-action.yml
Static Analysis (SAST) · High: REDACTED .github/workflows/fix-bug-action.yml
Static Analysis (SAST) · High: REDACTED .github/workflows/fix-bugs.yml
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED .github/workflows/stale-bot.yml
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED REDACTED
Static Analysis (SAST) · High: REDACTED .github/workflows/triage-issue-action.yml
Static Analysis (SAST) · High: REDACTED .github/workflows/triage-issue-action.yml
Static Analysis (SAST) · High: REDACTED .github/workflows/triage-issue-action.yml
Static Analysis (SAST) · High: REDACTED .github/workflows/triage-issue-action.yml
Static Analysis (SAST) · High: REDACTED .github/workflows/triage-issue-action.yml
Static Analysis (SAST) · High: REDACTED REDACTED
Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
Dependency Vulnerabilities · Critical vulnerability: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High vulnerability: [GHSA 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: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Supply-chain Provenance & Signing · REDACTED
Supply-chain Provenance & Signing · REDACTED
Supply-chain Provenance & Signing · REDACTED
Supply-chain Provenance & Signing · REDACTED
Supply-chain Provenance & Signing · REDACTED
Forms & labels · <Combobox> field component without a label packages/admin/dashboard/src/routes/products/product-create/components/product-create-details-form/components/product-create-details-variant-section/product-create-details-variant-section.tsx

Rebuild cost: about €97,000 · Estimate

Cost to rebuild	€32,000 to €160,000, for 538 to 1,706 hours of work, about 0.7 person-years for 1 to 2 engineers
Difficulty of the problem	Standard, 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 35. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size	Small: 2,522 lines of product code
What it is not	Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository).

Raises the score by about 15 points · Medium effort · Domain ↔ infrastructure boundary

Resolve the 6 No assertions (empty test) finding(s) in Test Quality — start with index.ts (2), medusa-cloud-search.spec.ts, index.spec.ts.

Raises the score by about 1 point · Low effort · Test Quality

Resolve the 32 Floating npm dependency finding(s) in Dependency Hygiene.

Raises the score by about 3 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 €97,000 to build again, about 0.7 person-years of work. Its weakest lens is Domain Modelling, at 17 (Critical). Domain Modelling is about whether the code protects the rules the business depends on. Because the weakest lens counts most in the score, work on Domain Modelling also moves the score most.

Based on: the rebuild estimate · the Domain Modelling grade · how much each lens counts

What to do: Start with the Domain Modelling actions in Top priorities.

If you do one thing first · First action

Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository). Of all the actions in this report, it raises the score most for the work it takes: about 15 points for medium effort. The next survey will show the change in the score.

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

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

3563 modules, with 3521 dependencies between them. 10 loops run through 23 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 3523 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 →	4 core.types.src.common.common	5 core.types.src.http.common.request	6 core.types.src.http.order.admin.queries	7 core.types.src.http.product.admin.entitites	8 core.types.src.http.product.admin.queries	9 core.types.src.http.promotion.admin.queries	10 core.types.src.http.return.admin.payloads	11 core.types.src.logger	12 core.types.src.totals.big-number	13 core.workflows-sdk.src.utils.composer.helpers.workflow-response	14 plugins.loyalty.src.types.http.store-credit-account	16 core.js-sdk.src.client	17 core.types.src.dal.repository-service	18 core.types.src.fulfillment.service	19 core.types.src.http.order.admin.entities	20 core.types.src.http.product.admin.responses	21 core.types.src.modules-sdk.medusa-internal-service	22 core.types.src.order.mutations	23 core.types.src.product.common	24 medusa.src.types.global	29 core.types.src.http.order.admin.responses	30 core.types.src.http.product.admin.payloads	31 core.types.src.order.common	35 core.types.src.http.claim.admin.responses	36 core.types.src.http.exchange.admin.responses	37 core.types.src.http.return.admin.responses
1 admin.dashboard.src.lib.table.table-adapters
2 core.core-flows.src.draft-order.steps
3 core.instantsearch-adapter.src.types
4 core.types.src.common.common
5 core.types.src.http.common.request
6 core.types.src.http.order.admin.queries
7 core.types.src.http.product.admin.entitites
8 core.types.src.http.product.admin.queries
9 core.types.src.http.promotion.admin.queries
10 core.types.src.http.return.admin.payloads
11 core.types.src.logger
12 core.types.src.totals.big-number
13 core.workflows-sdk.src.utils.composer.helpers.workflow-response
14 plugins.loyalty.src.types.http.store-credit-account
15 core.core-flows.src.fulfillment.workflows										10
16 core.js-sdk.src.client								1
17 core.types.src.dal.repository-service	1
18 core.types.src.fulfillment.service	1
19 core.types.src.http.order.admin.entities				2
20 core.types.src.http.product.admin.responses				6
21 core.types.src.modules-sdk.medusa-internal-service	1
22 core.types.src.order.mutations									26														9
23 core.types.src.product.common	24
24 medusa.src.types.global	1
25 core.core-flows.src.cart.steps																				4
26 core.framework.src.http.types	1																			1
27 core.framework.src.types.container								1						1
28 core.js-sdk.src.admin												1
29 core.types.src.http.order.admin.responses															4
30 core.types.src.http.product.admin.payloads																			2
31 core.types.src.order.common									11									3
32 modules.fulfillment.src.services.fulfillment-module-service	1												1	1			1
33 core.core-flows.src.draft-order.workflows										7													5
34 core.core-flows.src.order.steps																		7					1
35 core.types.src.http.claim.admin.responses															2								1
36 core.types.src.http.exchange.admin.responses															2								1
37 core.types.src.http.return.admin.responses															1								1
38 plugins.draft-order.src.admin.hooks.api		4	3		1	1						9									4
39 plugins.loyalty.src.admin.hooks.api		1			2						6	10				3						3
40 admin.dashboard.src.hooks.api		7	4		6	3	10					55				13		1			5	10		5	4	2

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 91% · Exemplary ·

The Good

D1 · TypeScript Cyclomatic Complexity 10.0 D2 · TypeScript Cognitive Complexity 10.0 D3 · TypeScript God Classes 10.0 R1 · React / TS Type Safety 9.5 R10 · React / TS Code Duplication 10.0 R2 · React / TS Cyclomatic Complexity 10.0 R3 · React / TS Large Files 10.0 R7 · React / TS Dead Code 10.0 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X3 · Repo Exception handling 10.0 X30 · Repo Support guard that admits what it rejects 10.0

The Bad

D17 · TypeScript Explicit Debt 7.0

At a glance — Architecture · 81% · Adequate · gated by D23 ·

The Good

D5 · TypeScript Coupling 10.0 D6 · TypeScript Cohesion (LCOM4) 9.7 D26 · TypeScript Project Cohesion 10.0 D35 · TypeScript Change Coupling 10.0 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX6 · Repo Interface segregation 9.4 AX8 · Repo Test isolation 10.0 R9 · React / TS Circular Imports 10.0

The Bad

AX10 · Repo Code composition 5.6

The Ugly

D23 · TypeScript Boundary Type-Coupling 0.0

At a glance — Maturity · 68% · Adequate · gated by M2 ·

The Good

D15 · TypeScript Churn × Complexity Hotspots 10.0 D16 · TypeScript Bus Factor 9.0 D19 · TypeScript Documentation Quality 10.0 M1 · Repo Documentation (README) 9.0 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0

The Bad

D34 · TypeScript Knowledge Freshness 6.5

The Ugly

D20 · TypeScript ADR Quality 0.0 M2 · Repo Architecture documentation 2.0

At a glance — Readiness · 39% · Weak · gated by D12, R8, P2, P3 ·

The Good

D9 · TypeScript Test Distribution 10.0 D10 · TypeScript Test Quality 9.9 D13 · TypeScript Secret Scanning 10.0 D14 · TypeScript License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P4 · Repo Deployment & Rollback 10.0 P6 · Repo Release Hygiene 10.0 R6 · React / TS Tooling 10.0

The Bad

D8 · TypeScript Code Coverage 6.6

The Ugly

D12 · TypeScript Dependency Hygiene 3.0 P2 · Repo Observability 2.0 P3 · Repo Security & performance tooling 3.0 R8 · React / TS Dependency Hygiene 0.0

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

The Good

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

The Ugly

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

At a glance — Domain Modelling · 17% · Critical · gated by DM6 ·

The Good

DM9 · Repo Scattered domain decisions 9.6

The Ugly

DM6 · Repo Domain ↔ infrastructure boundary 1.7

At a glance — Accessibility · 44% · Weak · gated by AC4 ·

The Good

AC5 · Repo ARIA correctness 10.0

The Bad

AC2 · Repo Forms & labels 5.0 AC3 · Repo Page structure 6.2

The Ugly

AC1 · Repo Text alternatives 4.8 AC4 · Repo Keyboard semantics 2.8 AC6 · Repo Visual & motion safety 4.7 AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 100% · Exemplary ·

The Good

PF3 · Repo Async & latency hygiene 10.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP category	Findings	Severity
A05:2025 — Injection	220	High / Critical
A03:2025 — Software Supply Chain Failures	142	High / Critical
A02:2025 — Security Misconfiguration	4	High / Critical

Roadmap

First, enforce a strict boundary between domain logic and infrastructure by keeping entities framework-free and using repositories for data mapping. Next, clean up the dependency tree by removing unused packages, explicitly declaring imports, and moving test-only tools to development dependencies. Then, address security and stability by resolving deprecated packages and fixing floating version constraints. Finally, improve operational visibility by adopting a standard logging library and adding logs at key service points.

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

Do this	Helps	Effort	Dimension
Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository).	+15.4 pts	Medium	Domain ↔ infrastructure boundary
Resolve the 6 No assertions (empty test) finding(s) in Test Quality — start with index.ts (2), medusa-cloud-search.spec.ts, index.spec.ts.	+1.5 pts	Low	Test Quality
Resolve the 32 Floating npm dependency finding(s) in Dependency Hygiene.	+2.9 pts	Medium	Dependency Hygiene
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.	+2.5 pts	Medium	Dependency Hygiene
Resolve the 23 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (23).	+2.2 pts	Medium	Dependency Hygiene
Adopt pino (or winston) and log at meaningful points in the services you run.	+1.8 pts	Medium	Observability
Resolve the 17 One package at two majors across the workspace finding(s) in Dependency Hygiene.	+1.8 pts	Medium	Dependency Hygiene
Resolve the 1 No ADRs found finding(s) in ADR Quality.	+0.9 pts	Low	ADR Quality

File quality

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

File	Score	Band	Worst signal
REDACTED	0.0	Slop	Dependency Vulnerabilities: Critical CVE: REDACTED
REDACTED	0.0	Slop	Dependency Vulnerabilities: Critical vulnerability: REDACTED
REDACTED	0.0	Slop	Dependency Vulnerabilities: Critical CVE: REDACTED
REDACTED	2.3	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	2.3	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	2.3	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	2.3	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	2.3	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	2.5	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	2.7	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	2.7	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	2.7	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	2.7	Slop	IaC & Container Security: Critical IaC: REDACTED
REDACTED	3.0	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	3.7	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	3.7	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	3.7	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	3.7	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	3.7	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	3.7	Slop	Static Analysis (SAST): High: REDACTED

How the grades work

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

Critical — 392

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

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

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

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 81 of 81 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

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

What we checked — 81 dimensions across the health lenses

D1D2D3D5D6D8D9D10D12D13D14D15D16D17D19D20D23D26D29D30D31D34D35D36D37D43D44AC1AC2AC3AC4AC5AC6AC7AX10AX3AX4AX6AX8DM6DM9M1M2M3M4P1P10P2P3P4P6PF3R1R10R2R3R6R7R8R9S1X1X12X13X14X15X16X17X18X19X21X22X23X24X25X26X27X28X29X3X30

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

How to trust any code-health report — three questions

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

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

Tools & methods

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

Method	Backs	Version	Evaluator
Roslyn static analysis	Complexity, cohesion, coupling, dead code, API surface, layering	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	—	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a17a27-0979-770a-868f-b934a713b4a1.

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

Run transparency — what happened this run

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

D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not included — the JavaScript/TypeScript suite (vitest via `yarn install --immutable --mode=skip-build` in the repository root (193 tests); jest via `yarn install --immutable --mode=skip-build` in integration-tests/http/ (0 tests); jest via `yarn install --immutable --mode=skip-build` in integration-tests/modules/ (0 tests); vitest via `yarn install --immutable --mode=skip-build` in packages/admin/admin-vite-plugin/ (23 tests); vitest via `yarn install --immutable --mode=skip-build` in packages/admin/dashboard/ (157 tests); jest via `yarn install --immutable --mode=skip-build` in packages/cli/create-medusa-app/ (123 tests); jest via `yarn install --immutable --mode=skip-build` in packages/cli/http-types-generator/ (156 tests); jest via `yarn install --immutable --mode=skip-build` in packages/cli/medusa-cli/ (34 tests); jest via `yarn install --immutable --mode=skip-build` in packages/cli/oas/oas-github-ci/ (0 tests); jest via `yarn install --immutable --mode=skip-build` in packages/core/core-flows/ (22 tests); jest via `yarn install --immutable --mode=skip-build` in packages/core/framework/ (144 tests); jest via `yarn install --immutable --mode=skip-build` in packages/core/instantsearch-adapter/ (41 tests)) did not finish re-running within its budget: too large to re-run within its budget.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D28 Secrets (history) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `gitleaks` TIMED OUT after 426.2s against a 426.2s budget, so we killed its process tree. The budget is ours; the work may simply be larger than it allows. Nothing about this repository is asserted by the absence of a result; the budget is ours to raise, and raising it is our backlog item, not an action for this repository's owner.
D31 IaC & Container Security — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Checkov ran but its report could not be read (checkov produced no output — not a clean result). Every misconfiguration only checkov reports — most of its Terraform, CloudFormation, Bicep and Ansible policies — is absent from this card, so its absence here is not evidence those resources are configured correctly.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Python is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Python is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). 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.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 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 is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
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.
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.
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 method(s) exceeded the cyclomatic complexity threshold of 15.

✓ On the Gold path — maintain.

Detailed fixes: d1_recommendation.md.

Do you agree with this assessment?

D2 · Cognitive Complexity10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 method(s) exceeded the cognitive complexity threshold of 15.

✓ On the Gold path — maintain.

Detailed fixes: d2_recommendation.md.

Do you agree with this assessment?

D3 · God Classes10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 god class(es) detected.

✓ On the Gold path — maintain.

Detailed fixes: d3_recommendation.md.

Do you agree with this assessment?

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

2 production modules (source-import), 0 dependency cycle(s), 0 unstable depended-on module(s). No manifest declares this repository's modules, so the modules are its top-level source directories and the edges the imports between them; 0 module(s) off the main sequence, with abstractness counted on 1 of the 2 (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).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

Do you agree with this assessment?

D6 · Cohesion (LCOM4)9.7 / 10Stronggated by 5 serious findings✓ Tool-verified

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

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

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

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

5 of 201 classes have LCOM4 above 3.

Low cohesion: DashboardApp (LCOM4 10) · ×5packages/admin/dashboard/src/dashboard-app/dashboard-app.tsx:61

What to do

Resolve the 5 Low cohesion finding(s) in Cohesion (LCOM4) — start with dashboard-app.tsx, postgres-provider.ts, migrator.ts. — One of this dimension's main actionable groups (5 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D8 · Code Coverage6.6 / 10Adequate✓ Tool-verified

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

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

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

Line coverage 31.6%, branch coverage 19.1%. Measured from the JavaScript/TypeScript suite (vitest + @vitest/coverage-v8 via `yarn install --immutable --mode=skip-build` in the repository root; jest in integration-tests/http/: not run; jest in integration-tests/modules/: not run; vitest + @vitest/coverage-v8 via `yarn install --immutable --mode=skip-build` in packages/admin/admin-vite-plugin/; vitest + @vitest/coverage-v8 via `yarn install --immutable --mode=skip-build` in packages/admin/dashboard/; jest via `yarn install --immutable --mode=skip-build` in packages/cli/create-medusa-app/; jest via `yarn install --immutable --mode=skip-build` in packages/cli/http-types-generator/; jest via `yarn install --immutable --mode=skip-build` in packages/cli/medusa-cli/; jest in packages/cli/oas/oas-github-ci/: not run; jest via `yarn install --immutable --mode=skip-build` in packages/core/core-flows/; jest via `yarn install --immutable --mode=skip-build` in packages/core/framework/; jest via `yarn install --immutable --mode=skip-build` in packages/core/instantsearch-adapter/).

What to do

Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d8_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D10 · Test Quality9.9 / 10Adequategated by 6 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.9 / 10 · rule-coverage 100% · ceiling Prevented

41 skipped (4 with a documented reason), 27 zero-assertion, 1 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 8544 tests.

No assertions (empty test): requires Medusa Cloud search credentials · ×6packages/modules/search/integration-tests/__tests__/medusa-cloud-search.spec.ts:164

Skipped test: should export the appropriate linkable configuration · ×37packages/modules/rbac/integration-tests/__tests__/rbac.spec.ts:26

No assertions: should subscribe to a async workflow and receive the response when it finishes · ×21packages/modules/workflow-engine-redis/integration-tests/__tests__/index.spec.ts:947

Fixed-sleep synchronisation: should reject a replay while the first attempt is still in flightpackages/modules/payment/integration-tests/__tests__/services/payment-module/index.spec.ts:1869

Mock-dominated test: closes mobile sidebar when active and mobile · ×77www/packages/docs-ui/src/components/Sidebar/Item/Link/__tests__/index.test.tsx:293

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

What to do

Resolve the 6 No assertions (empty test) finding(s) in Test Quality — start with index.ts (2), medusa-cloud-search.spec.ts, index.spec.ts. — One of this dimension's main actionable groups (6 issue-level).
Resolve the 37 Skipped test finding(s) in Test Quality — start with product.spec.ts (16), variant.spec.ts (4), index.spec.ts (2). — One of this dimension's main actionable groups (37 warning-level).
Resolve the 21 No assertions finding(s) in Test Quality — start with medusa-service-typings.spec.ts (8), index.spec.ts (3), use-query-graph-step.spec.ts (3). — One of this dimension's main actionable groups (21 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

Maturity: Documented → Verified → Prevented · effective 3.0 / 10 · rule-coverage 99% · ceiling Verified

245 outdated direct production npm dependency(ies) of 331 graded, 49 pinning defect(s), across 112 REDACTED (111 of them the product) and 3 committed lockfile(s). 331 of 336 resolved direct production dependency(ies) were graded against registry.npmjs.org (5 not published there — private or renamed). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 9 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.

Floating npm dependency: @medusajs/workflows-sdk · ×32

Deprecated: @types/chalk · ×23REDACTED:39

One package at two majors across the workspace: @medusajs/core-flows · ×17

Deprecated: @humanwhocodes/config-array · ×36REDACTED:2389

Outdated (npm): @inquirer/checkbox · ×23packages/medusa/package.json:59

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

What to do

Resolve the 32 Floating npm dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (32 warning-level).
Resolve the 23 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (23). — One of this dimension's main actionable groups (23 warning-level).
Resolve the 17 One package at two majors across the workspace finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (17 warning-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

Do you agree with this assessment?

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

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

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

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

0 of 331 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 336 production dependency(ies) this repository's committed lockfile resolves, across 111 product REDACTED manifest(s). Its 479 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 14 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. A further 5 package(s) the lockfile resolves are not published on the public registry at all — a private scope, a workspace-internal name or a git install — and are outside this verdict. This repository publishes itself under ISC / MIT / SEE LICENSE IN LICENSE, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

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

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

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

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

Do you agree with this assessment?

D16 · Bus Factor9.0 / 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.0 / 10 · rule-coverage 100% · ceiling Documented

1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is integration-tests/http/src/utils/providers/payment-account-holder/services/account-holder-payment.ts. Counted over 7 of the 40 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.

Do you agree with this assessment?

D17 · Explicit Debt7.0 / 10Adequate✓ 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 7.0 / 10 · rule-coverage 100% · ceiling Prevented

57 deducted task-comment markers across 1752 LoC (1.5/KLoC) → score 7.0. 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 · ×57integration-tests/modules/__tests__/product/workflows/update-product-options.spec.ts:787

What to do

Resolve the 57 TodoComment finding(s) in Explicit Debt — start with product.spec.ts (23), variant.spec.ts (5), product-category.spec.ts (3). — One of this dimension's main actionable groups (57 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 1 documentation facets pass in full. 3 document(s) read across 1 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

Do you agree with this assessment?

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

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

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

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

No architecture decision records were found.

No ADRs found

What to do

Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D23 · Boundary Type-Coupling0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Verified

120 domain type(s) cross context boundaries across 81 contexts.

Cross-context type BigNumberInput (types → order) · ×22packages/modules/order/src/types/line-item.ts:32

Cross-context type BigNumberInput (types → core-flows) · ×17packages/core/core-flows/src/payment-collection/steps/create-payment-session.ts:24

Cross-context type BigNumberInput (types → promotion) · ×17packages/modules/promotion/src/types/application-method.ts:16

Cross-context type BigNumberInput (types → utils) · ×10packages/core/utils/src/totals/big-number.ts:16

Cross-context type Filter (search → types) · ×7packages/core/types/src/product/common.ts:766

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

What to do

Resolve the 22 Cross-context type BigNumberInput (types → order) finding(s) in Boundary Type-Coupling — start with index.ts (11), order-detail.ts (7), line-item.ts (2). — One of this dimension's main actionable groups (22 warning-level).
Resolve the 17 Cross-context type BigNumberInput (types → core-flows) finding(s) in Boundary Type-Coupling — start with prepare-line-item-data.ts (2), create-payment-session.ts, update-payment-session.ts. — One of this dimension's main actionable groups (17 warning-level).
Resolve the 17 Cross-context type BigNumberInput (types → promotion) finding(s) in Boundary Type-Coupling — start with application-method.ts (8), campaign-budget.ts (6), usage.ts. — One of this dimension's main actionable groups (17 warning-level).
Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D26 · Project Cohesion10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

220 finding(s): 0 critical, 219 high, 1 medium, 0 low. 162 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 1 file(s) — `integration-tests/http/__tests__/upload/admin/presigned-urls.spec.ts` (line 20) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 13 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED

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

What to do

Resolve the 40 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (21), REDACTED (4), REDACTED (3). — One of this dimension's main actionable groups (40 issue-level).
Resolve the 3 REDACTED finding(s) charged to Static Analysis (SAST) — the other 162 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (165 issue-level, 3 of them charged here).
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).

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

Do you agree with this assessment?

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

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

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

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

115 finding(s): 8 critical, 64 high, 35 medium, 8 low.

REDACTED

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

What to do

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

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

Do you agree with this assessment?

D31 · IaC & Container Security8.8 / 10Adequategated by 2 critical findings✓ Tool-verified

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

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

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

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

REDACTED

What to do

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

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

Do you agree with this assessment?

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

2 of 7 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is integration-tests/modules/medusa-config.ts. Counted over 7 of the 40 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×2integration-tests/modules/medusa-config.ts:1

Orphaned files with no living knowledge

What to do

Resolve the 2 Orphaned file finding(s) in Knowledge Freshness — start with medusa-config.ts, wait-for-index.ts. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

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

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

Do you agree with this assessment?

D36 · Supply-chain Provenance & 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

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

What to do

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

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

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives4.8 / 10Weak✓ Tool-verified

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

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

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

An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×5) — packages/admin/dashboard/src/routes/product-variants/product-variant-detail/components/variant-media-section/variant-media-section.tsx:57, packages/admin/dashboard/src/routes/product-variants/product-variant-media/components/edit-product-variant-media-form/edit-product-variant-media-form.tsx:396, packages/admin/dashboard/src/routes/product-variants/product-variant-media/components/edit-product-variant-media-form/edit-product-variant-media-form.tsx:430, …
A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. — packages/admin/dashboard/src/routes/profile/profile-detail/components/profile-mfa-section/mfa-qr-code.tsx:44

What to do

Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.

Do you agree with this assessment?

AC2 · Forms & labels5.0 / 10Adequate✓ Tool-verified

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

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

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

This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — 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. (×6) — packages/admin/dashboard/src/components/data-grid/components/data-grid-textarea-modal-cell.tsx:220, packages/admin/dashboard/src/components/table/data-table/data-table-filter/date-filter.tsx:221, packages/admin/dashboard/src/components/table/data-table/data-table-filter/date-filter.tsx:236, …
A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one. (×2) — packages/admin/dashboard/src/components/forms/address-form/address-form.tsx:36, packages/admin/dashboard/src/components/forms/address-form/address-form.tsx:101
This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×4) — packages/admin/dashboard/src/components/forms/metadata-form/metadata-form.tsx:154, packages/admin/dashboard/src/components/forms/metadata-form/metadata-form.tsx:159, packages/plugins/draft-order/src/admin/routes/draft-orders/[id]/@metadata/page.tsx:149, …
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×7) — packages/admin/dashboard/src/components/inputs/chip-input/chip-input.tsx:171, packages/design-system/ui/src/blocks/data-table/components/data-table-filter.tsx:618, packages/design-system/ui/src/blocks/data-table/components/data-table-filter.tsx:946, …
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. (×6) — packages/admin/dashboard/src/routes/orders/order-balance-settlement/components/order-balance-settlement-form/order-balance-settlement-form.tsx:252, packages/admin/dashboard/src/routes/orders/order-create-refund/components/create-refund-form/create-refund-form.tsx:139, packages/admin/dashboard/src/routes/products/product-create/components/product-create-details-form/components/product-create-details-variant-section/product-create-details-variant-section.tsx:470, …
This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. 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. (×2) — packages/design-system/ui/src/blocks/data-table/components/data-table-filter.tsx:1209, www/packages/docs-ui/src/components/Feedback/index.tsx:246
A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. — www/packages/docs-ui/src/components/AiAssistant/ChatWindow/Footer/index.tsx:17
This <span> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×2) — www/packages/docs-ui/src/components/CodeBlock/Actions/AskAi/index.tsx:47, www/packages/docs-ui/src/components/CodeBlock/Actions/Bloom/index.tsx:53
A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). — www/packages/docs-ui/src/layouts/main-content.tsx:82

What to do

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

Do you agree with this assessment?

AC3 · Page structure6.2 / 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.

A page with no <title> gives no name in the tab, history or screen-reader page list. Declare it the way this router does — Next App Router `export const metadata = { title }`, React Router/Remix `export function meta`, TanStack Start `head`, or a Helmet/Head component. — www/packages/docs-ui/src/layouts/barebone.tsx:17
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — www/packages/docs-ui/src/layouts/barebone.tsx:17

What to do

Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.

Do you agree with this assessment?

AC4 · Keyboard semantics2.8 / 10Weak✓ Tool-verified

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

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

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

A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×23) — packages/admin/dashboard/src/components/common/display-id/display-id.tsx:23, packages/admin/dashboard/src/components/common/json-view-section/json-view-section.tsx:197, packages/admin/dashboard/src/routes/orders/order-allocate-items/components/order-create-fulfillment-form/order-allocate-items-item.tsx:239, …
This <div> carries tabIndex={0}, so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler. (×2) — packages/admin/dashboard/src/components/data-grid/components/data-grid-root.tsx:684, packages/plugins/loyalty/src/admin/components/data-grid/components/data-grid-root.tsx:561
An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×5) — packages/admin/dashboard/src/routes/orders/order-create-claim/components/claim-create-form/claim-create-form.tsx:634, packages/admin/dashboard/src/routes/orders/order-create-claim/components/claim-create-form/claim-outbound-section.tsx:302, packages/admin/dashboard/src/routes/orders/order-create-exchange/components/exchange-create-form/exchange-inbound-section.tsx:346, …
This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus. (×3) — packages/admin/dashboard/src/routes/translations/translation-list/components/translations-completion-section/translations-completion-section.tsx:206, www/packages/docs-ui/src/components/MainNav/Items/Dropdown/index.tsx:83, www/packages/docs-ui/src/components/Menu/SubMenu/index.tsx:20

What to do

Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.

Do you agree with this assessment?

AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

Do you agree with this assessment?

AC6 · Visual & motion safety4.7 / 10Weak✓ Tool-verified

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

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

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

<button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×20) — packages/admin/dashboard/src/components/common/file-upload/file-upload.tsx:114, packages/admin/dashboard/src/components/inputs/combobox/combobox.tsx:358, packages/admin/dashboard/src/components/inputs/combobox/combobox.tsx:420, …
<div> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×4) — packages/admin/dashboard/src/components/data-grid/components/data-grid-root.tsx:684, packages/design-system/ui/src/blocks/data-table/components/data-table-filter.tsx:482, packages/design-system/ui/src/blocks/data-table/components/data-table-filter.tsx:704, …
<input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×8) — packages/admin/dashboard/src/components/forms/metadata-form/metadata-form.tsx:318, packages/admin/dashboard/src/components/inputs/quantity-input/quantity-input.tsx:54, packages/admin/dashboard/src/routes/products/common/components/category-combobox/category-combobox.tsx:293, …
<textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — www/apps/book/components/Homepage/Bloom/index.tsx:69
<span> moves — its `animate-[pulsingCursor_0.8s_ease-in-out_infinite]` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — www/apps/book/components/Homepage/Bloom/index.tsx:91
<div> moves — its `animate-[shimmer_1.5s_linear_infinite]` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — www/packages/docs-ui/src/components/AiAssistant/Loading/index.tsx:178

What to do

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

Do you agree with this assessment?

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

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

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

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

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

What to do

Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.

Do you agree with this assessment?

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

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

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

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

What to do

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

AX6 · Interface segregation9.4 / 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.

`Logger` declares 16 required operations: `panic`, `shouldLog`, `setLogLevel`, `unsetLogLevel`, `activity`, `progress`, `error`, `failure`, `success`, `silly`, `debug`, `verbose`, `http`, `info`, `warn`, `log`. 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/core/types/src/logger/index.ts:1
`ICartModuleService` declares 84 required operations: `retrieveCart`, `listCarts`, `listAndCountCarts`, `createCarts`, `createCarts`, `updateCarts`, `updateCarts`, `updateCarts`, `deleteCarts`, `deleteCarts`, `listAddresses`, `createAddresses`, `createAddresses`, `updateAddresses`, `updateAddresses`, `deleteAddresses`, `deleteAddresses`, `retrieveLineItem`, `listLineItems`, `addLineItems`, `addLineItems`, `addLineItems`, `updateLineItems`, `updateLineItems`, `updateLineItems`, `updateLineItems`, `listShippingMethods`, `addShippingMethods`, `addShippingMethods`, `addShippingMethods`, `updateShippingMethods`, `updateShippingMethods`, `listLineItemAdjustments`, `addLineItemAdjustments`, `addLineItemAdjustments`, `addLineItemAdjustments`, `setLineItemAdjustments`, `listShippingMethodAdjustments`, `addShippingMethodAdjustments`, `addShippingMethodAdjustments`, and 44 more. 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. Those 84 declarations carry 55 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 55 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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/core/types/src/cart/service.ts:50
`ICustomerModuleService` declares 41 required operations: `retrieveCustomer`, `createCustomers`, `createCustomers`, `updateCustomers`, `updateCustomers`, `updateCustomers`, `deleteCustomers`, `deleteCustomers`, `deleteCustomers`, `createCustomerGroups`, `createCustomerGroups`, `retrieveCustomerGroup`, `updateCustomerGroups`, `updateCustomerGroups`, `updateCustomerGroups`, `deleteCustomerGroups`, `deleteCustomerGroups`, `deleteCustomerGroups`, `addCustomerToGroup`, `addCustomerToGroup`, `removeCustomerFromGroup`, `removeCustomerFromGroup`, `createCustomerAddresses`, `createCustomerAddresses`, `updateCustomerAddresses`, `updateCustomerAddresses`, `updateCustomerAddresses`, `deleteCustomerAddresses`, `deleteCustomerAddresses`, `deleteCustomerAddresses`, `listCustomerAddresses`, `listAndCountCustomerAddresses`, `listCustomerGroupCustomers`, `listCustomers`, `listAndCountCustomers`, `listCustomerGroups`, `listAndCountCustomerGroups`, `softDeleteCustomers`, `restoreCustomers`, `softDeleteCustomerGroups`, and 1 more. 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. Those 41 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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/core/types/src/customer/service.ts:28
`IPaymentModuleService` declares 52 required operations: `createPaymentCollections`, `createPaymentCollections`, `retrievePaymentCollection`, `listPaymentCollections`, `listAndCountPaymentCollections`, `updatePaymentCollections`, `updatePaymentCollections`, `upsertPaymentCollections`, `upsertPaymentCollections`, `deletePaymentCollections`, `deletePaymentCollections`, `softDeletePaymentCollections`, `restorePaymentCollections`, `completePaymentCollections`, `completePaymentCollections`, `retrievePaymentSession`, `retrievePayment`, `createPaymentSession`, `updatePaymentSession`, `deletePaymentSession`, `authorizePaymentSession`, `listPaymentSessions`, `listPayments`, `updatePayment`, `capturePayment`, `refundPayment`, `cancelPayment`, `listPaymentProviders`, `listAndCountPaymentProviders`, `createAccountHolder`, `updateAccountHolder`, `deleteAccountHolder`, `listPaymentMethods`, `listAndCountPaymentMethods`, `createPaymentMethods`, `createPaymentMethods`, `deletePaymentMethods`, `deletePaymentMethods`, `listCaptures`, `deleteCaptures`, and 12 more. 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. Those 52 declarations carry 42 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 42 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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/core/types/src/payment/service.ts:46
`IOrderModuleService` declares 209 required operations: `retrieveOrder`, `listOrders`, `listAndCountOrders`, `retrieveReturn`, `listReturns`, `listAndCountReturns`, `retrieveOrderClaim`, `listOrderClaims`, `listAndCountOrderClaims`, `retrieveOrderExchange`, `listOrderExchanges`, `listAndCountOrderExchanges`, `createOrders`, `createOrders`, `updateOrders`, `updateOrders`, `updateOrders`, `deleteOrders`, `deleteOrders`, `softDeleteOrders`, `restoreOrders`, `listOrderAddresses`, `createOrderAddresses`, `createOrderAddresses`, `updateOrderAddresses`, `updateOrderAddresses`, `deleteOrderAddresses`, `deleteOrderAddresses`, `retrieveOrderLineItem`, `listOrderLineItems`, `createOrderLineItems`, `createOrderLineItems`, `createOrderLineItems`, `updateOrderLineItems`, `updateOrderLineItems`, `updateOrderLineItems`, `deleteOrderLineItems`, `deleteOrderLineItems`, `deleteOrderLineItems`, `updateOrderItem`, and 169 more. 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. Those 209 declarations carry 136 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 136 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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/core/types/src/order/service.ts:102
`IRegionModuleService` declares 16 required operations under just 12 distinct name(s): `createRegions`, `createRegions`, `upsertRegions`, `upsertRegions`, `updateRegions`, `updateRegions`, `deleteRegions`, `deleteRegions`, `retrieveRegion`, `listRegions`, `listAndCountRegions`, `retrieveCountry`, `listCountries`, `listAndCountCountries`, `softDeleteRegions`, `restoreRegions`. 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. That is an OVERLOAD SET, not 16 separate responsibilities: a caller binds to 12 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 16 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — packages/core/types/src/region/service.ts:16
`IFulfillmentModuleService` declares 99 required operations: `retrieveFulfillmentSet`, `listFulfillmentSets`, `listAndCountFulfillmentSets`, `createFulfillmentSets`, `createFulfillmentSets`, `updateFulfillmentSets`, `updateFulfillmentSets`, `deleteFulfillmentSets`, `deleteFulfillmentSets`, `softDeleteFulfillmentSets`, `restoreFulfillmentSets`, `retrieveServiceZone`, `listServiceZones`, `listAndCountServiceZones`, `createServiceZones`, `createServiceZones`, `updateServiceZones`, `updateServiceZones`, `upsertServiceZones`, `upsertServiceZones`, `deleteServiceZones`, `deleteServiceZones`, `softDeleteServiceZones`, `restoreServiceZones`, `retrieveGeoZone`, `listGeoZones`, `listAndCountGeoZones`, `createGeoZones`, `createGeoZones`, `updateGeoZones`, `updateGeoZones`, `deleteGeoZones`, `deleteGeoZones`, `softDeleteGeoZones`, `restoreGeoZones`, `retrieveShippingOption`, `listShippingOptions`, `listShippingOptionsForContext`, `listAndCountShippingOptions`, `createShippingOptions`, and 59 more. 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. Those 99 declarations carry 74 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 74 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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/core/types/src/fulfillment/service.ts:53
`IProductModuleService` declares 102 required operations: `retrieveProduct`, `listProducts`, `listAndCountProducts`, `createProducts`, `createProducts`, `upsertProducts`, `upsertProducts`, `updateProducts`, `updateProducts`, `deleteProducts`, `softDeleteProducts`, `restoreProducts`, `retrieveProductTag`, `listProductTags`, `listAndCountProductTags`, `createProductTags`, `createProductTags`, `upsertProductTags`, `upsertProductTags`, `updateProductTags`, `updateProductTags`, `deleteProductTags`, `softDeleteProductTags`, `restoreProductTags`, `retrieveProductType`, `listProductTypes`, `listAndCountProductTypes`, `createProductTypes`, `createProductTypes`, `upsertProductTypes`, `upsertProductTypes`, `updateProductTypes`, `updateProductTypes`, `deleteProductTypes`, `softDeleteProductTypes`, `restoreProductTypes`, `retrieveProductOption`, `listProductOptions`, `listAndCountProductOptions`, `createProductOptions`, and 62 more. 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. Those 102 declarations carry 76 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 76 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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/core/types/src/product/service.ts:53
`IPromotionModuleService` declares 35 required operations: `registerUsage`, `revertUsage`, `computeActions`, `createPromotions`, `createPromotions`, `updatePromotions`, `updatePromotions`, `listPromotions`, `listAndCountPromotions`, `retrievePromotion`, `deletePromotions`, `deletePromotions`, `softDeletePromotions`, `restorePromotions`, `addPromotionRules`, `addPromotionTargetRules`, `addPromotionBuyRules`, `removePromotionRules`, `removePromotionTargetRules`, `removePromotionBuyRules`, `createCampaigns`, `createCampaigns`, `updateCampaigns`, `updateCampaigns`, `listPromotionRules`, `updatePromotionRules`, `listCampaigns`, `listAndCountCampaigns`, `retrieveCampaign`, `deleteCampaigns`, `deleteCampaigns`, `softDeleteCampaigns`, `restoreCampaigns`, `addPromotionsToCampaign`, `removePromotionsFromCampaign`. 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. Those 35 declarations carry 29 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 29 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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/core/types/src/promotion/service.ts:31
`IPricingModuleService` declares 51 required operations: `calculatePrices`, `retrievePriceSet`, `listPriceSets`, `listAndCountPriceSets`, `createPriceSets`, `createPriceSets`, `upsertPriceSets`, `upsertPriceSets`, `updatePriceSets`, `updatePriceSets`, `deletePriceSets`, `addPrices`, `addPrices`, `listPrices`, `softDeletePrices`, `restorePrices`, `listAndCountPrices`, `retrievePriceRule`, `listPriceRules`, `listAndCountPriceRules`, `createPriceRules`, `updatePriceRules`, `deletePriceRules`, `retrievePriceList`, `listPriceLists`, `listAndCountPriceLists`, `createPriceLists`, `updatePriceLists`, `deletePriceLists`, `softDeletePriceLists`, `restorePriceLists`, `retrievePriceListRule`, `listPriceListRules`, `listAndCountPriceListRules`, `deletePriceListRules`, `addPriceListPrices`, `updatePriceListPrices`, `setPriceListRules`, `removePriceListRules`, `removePrices`, and 11 more. 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. Those 51 declarations carry 44 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 44 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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/core/types/src/pricing/service.ts:43
`IInventoryService` declares 42 required operations: `listInventoryItems`, `listAndCountInventoryItems`, `listReservationItems`, `listAndCountReservationItems`, `listInventoryLevels`, `listAndCountInventoryLevels`, `retrieveInventoryItem`, `retrieveInventoryLevelByItemAndLocation`, `retrieveInventoryLevel`, `retrieveReservationItem`, `createReservationItems`, `createReservationItems`, `createInventoryItems`, `createInventoryItems`, `createInventoryLevels`, `createInventoryLevels`, `updateInventoryLevels`, `updateInventoryLevels`, `updateInventoryItems`, `updateInventoryItems`, `updateReservationItems`, `updateReservationItems`, `deleteReservationItemsByLineItem`, `restoreReservationItemsByLineItem`, `deleteReservationItems`, `softDeleteReservationItems`, `restoreReservationItems`, `deleteInventoryItems`, `softDeleteInventoryItems`, `restoreInventoryItems`, `deleteInventoryItemLevelByLocationId`, `deleteReservationItemByLocationId`, `deleteInventoryLevel`, `deleteInventoryLevels`, `softDeleteInventoryLevels`, `restoreInventoryLevels`, `adjustInventory`, `adjustInventory`, `confirmInventory`, `retrieveAvailableQuantity`, and 2 more. 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. Those 42 declarations carry 35 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 35 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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/core/types/src/inventory/service.ts:27
`IRbacModuleService` declares 41 required operations: `createRbacRoles`, `createRbacRoles`, `updateRbacRoles`, `updateRbacRoles`, `deleteRbacRoles`, `retrieveRbacRole`, `listRbacRoles`, `listAndCountRbacRoles`, `createRbacPolicies`, `createRbacPolicies`, `updateRbacPolicies`, `updateRbacPolicies`, `deleteRbacPolicies`, `retrieveRbacPolicy`, `listRbacPolicies`, `listAndCountRbacPolicies`, `createRbacRolePolicies`, `createRbacRolePolicies`, `updateRbacRolePolicies`, `updateRbacRolePolicies`, `deleteRbacRolePolicies`, `retrieveRbacRolePolicy`, `listRbacRolePolicies`, `listAndCountRbacRolePolicies`, `createRbacRoleParents`, `createRbacRoleParents`, `updateRbacRoleParents`, `updateRbacRoleParents`, `deleteRbacRoleParents`, `retrieveRbacRoleParent`, `listRbacRoleParents`, `listAndCountRbacRoleParents`, `listPoliciesForRole`, `softDeleteRbacRoles`, `restoreRbacRoles`, `softDeleteRbacPolicies`, `restoreRbacPolicies`, `softDeleteRbacRolePolicies`, `restoreRbacRolePolicies`, `softDeleteRbacRoleParents`, and 1 more. 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. Those 41 declarations carry 33 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 33 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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/core/types/src/rbac/service.ts:26
`ISettingsModuleService` declares 47 required operations: `retrieveViewConfiguration`, `listViewConfigurations`, `listAndCountViewConfigurations`, `createViewConfigurations`, `createViewConfigurations`, `updateViewConfigurations`, `updateViewConfigurations`, `deleteViewConfigurations`, `retrieveUserPreference`, `listUserPreferences`, `listAndCountUserPreferences`, `createUserPreferences`, `createUserPreferences`, `updateUserPreferences`, `getUserPreference`, `setUserPreference`, `deleteUserPreferences`, `getActiveViewConfiguration`, `setActiveViewConfiguration`, `getSystemDefaultViewConfiguration`, `clearActiveViewConfiguration`, `retrieveLayoutConfiguration`, `listLayoutConfigurations`, `listAndCountLayoutConfigurations`, `createLayoutConfigurations`, `createLayoutConfigurations`, `deleteLayoutConfigurations`, `getSystemDefaultLayoutConfiguration`, `setLayoutConfiguration`, `setSystemDefaultLayoutConfiguration`, `clearLayoutConfiguration`, `getActiveLayoutScope`, `setActiveLayoutScope`, `retrievePropertyLabel`, `listPropertyLabels`, `listAndCountPropertyLabels`, `createPropertyLabels`, `createPropertyLabels`, `updatePropertyLabels`, `updatePropertyLabels`, and 7 more. 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. Those 47 declarations carry 40 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 40 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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/core/types/src/settings/service.ts:28
`ITaxModuleService` declares 33 required operations: `retrieveTaxRate`, `listTaxRates`, `listAndCountTaxRates`, `createTaxRates`, `createTaxRates`, `updateTaxRates`, `updateTaxRates`, `updateTaxRates`, `upsertTaxRates`, `upsertTaxRates`, `deleteTaxRates`, `deleteTaxRates`, `restoreTaxRates`, `createTaxRegions`, `createTaxRegions`, `updateTaxRegions`, `updateTaxRegions`, `deleteTaxRegions`, `deleteTaxRegions`, `listTaxRegions`, `createTaxRateRules`, `listTaxProviders`, `createTaxRateRules`, `deleteTaxRateRules`, `deleteTaxRateRules`, `listTaxRateRules`, `getTaxLines`, `softDeleteTaxRates`, `softDeleteTaxRegions`, `restoreTaxRegions`, `softDeleteTaxRateRules`, `restoreTaxRateRules`, `getProvider`. 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. Those 33 declarations carry 23 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 23 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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/core/types/src/tax/service.ts:33
`ITranslationModuleService` declares 31 required operations: `retrieveLocale`, `listLocales`, `listAndCountLocales`, `createLocales`, `createLocales`, `updateLocales`, `updateLocales`, `deleteLocales`, `softDeleteLocales`, `restoreLocales`, `retrieveTranslation`, `listTranslations`, `listAndCountTranslations`, `createTranslations`, `createTranslations`, `updateTranslations`, `updateTranslations`, `deleteTranslations`, `softDeleteTranslations`, `restoreTranslations`, `getStatistics`, `getTranslatableFields`, `getInactiveTranslatableFields`, `createTranslationSettings`, `createTranslationSettings`, `updateTranslationSettings`, `updateTranslationSettings`, `deleteTranslationSettings`, `listTranslationSettings`, `listAndCountTranslationSettings`, `retrieveTranslationSettings`. 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. Those 31 declarations carry 25 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 25 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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/core/types/src/translation/service.ts:32
`IUserModuleService` declares 22 required operations: `validateInviteToken`, `refreshInviteTokens`, `retrieveUser`, `listUsers`, `listAndCountUsers`, `createUsers`, `createUsers`, `updateUsers`, `updateUsers`, `deleteUsers`, `softDeleteUsers`, `restoreUsers`, `retrieveInvite`, `listInvites`, `listAndCountInvites`, `createInvites`, `createInvites`, `updateInvites`, `updateInvites`, `deleteInvites`, `softDeleteInvites`, `restoreInvites`. 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. Those 22 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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/core/types/src/user/service.ts:16
`IAuthModuleService` declares 37 required operations: `authenticate`, `listAuthProviders`, `register`, `updateProvider`, `createPasswordResetToken`, `consumePasswordResetToken`, `validateCallback`, `validateAuthIdentity`, `startAuthMfa`, `verifyAuthMfa`, `createAuthMfaChallenge`, `verifyAuthMfaChallenge`, `disableAuthMfa`, `retrieveAuthMfa`, `listAuthMfa`, `generateAuthMfaRecoveryCodes`, `useAuthMfaRecoveryCode`, `requestAuthVerification`, `confirmAuthVerification`, `retrieveAuthVerification`, `listAuthVerifications`, `listAndCountAuthVerifications`, `retrieveAuthIdentity`, `listAuthIdentities`, `listAndCountAuthIdentities`, `createAuthIdentities`, `createAuthIdentities`, `updateAuthIdentities`, `updateAuthIdentities`, `deleteAuthIdentities`, `retrieveProviderIdentity`, `listProviderIdentities`, `createProviderIdentities`, `createProviderIdentities`, `updateProviderIdentities`, `updateProviderIdentities`, `deleteProviderIdentities`. 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. Those 37 declarations carry 33 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 33 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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/core/types/src/auth/service.ts:44
`IMedusaInternalService` declares 20 required operations under just 10 distinct name(s): `retrieve`, `retrieve`, `list`, `listAndCount`, `create`, `create`, `update`, `update`, `update`, `update`, `delete`, `delete`, `delete`, `delete`, `delete`, `softDelete`, `restore`, `upsert`, `upsert`, `upsertWithReplace`. 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. That is an OVERLOAD SET, not 20 separate responsibilities: a caller binds to 10 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 20 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — packages/core/types/src/modules-sdk/medusa-internal-service.ts:12

What to do

Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

DM6 · Domain ↔ infrastructure boundary1.7 / 10Critical✓ 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.

BaseEntity is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. — packages/core/utils/src/dal/mikro-orm/base-entity.ts:10
Product is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. — packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:14
ProductOption is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. — packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:33
ProductOptionValue is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. — packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:53
ProductVariant is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. — packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:80
RecursiveEntity1 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. (×2) — packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:113, packages/core/utils/src/dal/mikro-orm/integration-tests/__fixtures__/utils.ts:13
RecursiveEntity2 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. (×2) — packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:132, packages/core/utils/src/dal/mikro-orm/integration-tests/__fixtures__/utils.ts:32
Entity1 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. (×2) — packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:157, packages/core/utils/src/dal/mikro-orm/integration-tests/__fixtures__/utils.ts:57
Entity2 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. (×2) — packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:176, packages/core/utils/src/dal/mikro-orm/integration-tests/__fixtures__/utils.ts:76
DeepRecursiveEntity1 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. (×2) — packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:204, packages/core/utils/src/dal/mikro-orm/integration-tests/__fixtures__/utils.ts:104
DeepRecursiveEntity2 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. (×2) — packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:228, packages/core/utils/src/dal/mikro-orm/integration-tests/__fixtures__/utils.ts:123
DeepRecursiveEntity3 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. (×2) — packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:256, packages/core/utils/src/dal/mikro-orm/integration-tests/__fixtures__/utils.ts:151
DeepRecursiveEntity4 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. (×2) — packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:280, packages/core/utils/src/dal/mikro-orm/integration-tests/__fixtures__/utils.ts:175
InternalCircularDependencyEntity1 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. (×2) — packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:304, packages/core/utils/src/dal/mikro-orm/integration-tests/__fixtures__/utils.ts:199
Entity1WithUnDecoratedProp is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. (×2) — packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:340, packages/core/utils/src/dal/mikro-orm/integration-tests/__fixtures__/utils.ts:235
Entity2WithUnDecoratedProp is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. (×2) — packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:361, packages/core/utils/src/dal/mikro-orm/integration-tests/__fixtures__/utils.ts:256
SearchableEntity1 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. (×2) — packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:391, packages/core/utils/src/dal/mikro-orm/integration-tests/__fixtures__/utils.ts:286
SearchableEntity2 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper. (×2) — packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:413, packages/core/utils/src/dal/mikro-orm/integration-tests/__fixtures__/utils.ts:308

What to do

Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository).

Do you agree with this assessment?

DM9 · Scattered domain decisions9.6 / 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.

packages.cli.http-types-generator.src.core.schema-extractor.ExtractedSchema's [exportName, httpTypeName] are judged in packages.cli.http-types-generator.src.commands.generate, packages.cli.http-types-generator.src.commands.validate — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.

What to do

Move each repeated judgement onto the type that owns the members it reads, so the rule has one home and cannot drift.

Do you agree with this assessment?

M1 · Documentation (README)9.0 / 10Exemplary✓ Tool-verified

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

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

What to do

Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add a README to the 17 of 114 project(s) that lack one — worth up to 0.3 pts.

Do you agree with this assessment?

M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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

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

No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.

Do you agree with this assessment?

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

Do you agree with this assessment?

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

P2 · Observability2.0 / 10Critical✓ Tool-verified

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

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

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

What to do

Adopt pino (or winston) and log at meaningful points in the services you run.
Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.

Do you agree with this assessment?

P3 · Security & performance tooling3.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.

No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 488335 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

P4 · Deployment & Rollback10.0 / 10Exemplary✓ 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.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

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

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

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

What to do

Migrate the remaining .js/.jsx files to TypeScript.

Do you agree with this assessment?

R10 · Code Duplication10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

R2 · Cyclomatic Complexity10.0 / 10Exemplary✓ Tool-verified

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

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

(anonymous) has cyclomatic complexity 15 and cognitive complexity 38; 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/design-system/ui/src/blocks/data-table/data-table.stories.tsx:94
(anonymous) has cyclomatic complexity 12 and cognitive complexity 15; 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/cli/oas/medusa-oas-cli/src/__tests__/command-oas.test.ts:45

Do you agree with this assessment?

R3 · Large Files10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

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

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

This repository declares test tooling, and the ✓ above records that declaration — but integration-tests/environment-helpers/start-server-with-environment.js 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. — integration-tests/environment-helpers/start-server-with-environment.js:2

Do you agree with this assessment?

R7 · Dead Code10.0 / 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.

15 file(s) (~703 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — integration-tests
5 file(s) (~1048 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/admin/admin-vite-plugin
30 file(s) (~3794 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/admin/dashboard
Unreachable from the 235 application, 0 tooling and 1545 test entry point(s) detected in this repo. Gate removals on `yarn run build` — an undetected custom entry would make these reachable.
no import path from any entry point (235 application, 0 tooling, 1545 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 — define_jest_config.js

Do you agree with this assessment?

R8 · Dependency Hygiene0.0 / 10Critical✓ Tool-verified

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

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

Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×11) — integration-tests/http/__tests__/product-category/store/product-category.spec.ts:4, integration-tests/modules/__tests__/rbac-match-endpoint-entities.spec.ts:4, packages/core/framework/src/jobs/__tests__/register-jobs.spec.ts:13, …
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. — packages/admin/dashboard/src/routes/products/product-media/components/edit-product-media-form/edit-product-media-form.spec.tsx:34
Only test files import it (first: integration-tests/http/__tests__/auth/admin/auth-asymetric.spec.ts:4) — move it to devDependencies. — integration-tests/package.json:22

What to do

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

Do you agree with this assessment?

R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

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

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

None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `_headers` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — www/apps/user-guide/public/_headers:1

What to do

Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

X3 · Exception handling10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

WCAG coverage — what static analysis assessed

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

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

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

Reference — by lens

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

Lens	Score	Rating	Impact
Code Health	91%	Exemplary	Solid.
Architecture	81%	Adequate — gated by D23	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity	68%	Adequate — gated by M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	39%	Weak — gated by D12, R8, P2, P3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	66%	Adequate — gated by D29, D30, D36	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling	17%	Critical — gated by DM6	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility	44%	Weak — gated by AC4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance	100%	Exemplary	Strongest area.

Unscored — 4 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 — 7 observation(s) recorded · Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X9 Subsumed condition operand — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.

Not evidenced — 1 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.

P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control

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

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

AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route and starts no server another machine can reach (no Flask/FastAPI/Starlette route, Django urlpatterns or class-based view, Tornado handler). Access control is therefore N/A here — a library or command-line tool is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or MongoEngine model, a migration or a SQL schema — and no database or data-store client (Django ORM, SQLAlchemy, psycopg, PyMongo, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D11 Test Reliability — Test reliability not included
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# only; JavaScript, Python, TypeScript not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed JavaScript, TypeScript surface was not measured.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .py, .ts, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.cjs,.js,.mjs,.ts,.tsx), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D28 Secrets (history) — gitleaks killed before it finished — this repository's git history not scanned
D32 Data Compliance (PII/GDPR) — 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.
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) 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.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
DM1 Aggregate boundaries — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM10 One transaction, one aggregate — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM2 Strongly-typed ids — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM4 Rich vs anemic model — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM5 Encapsulated state — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
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
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — 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
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Python source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage data present for 898 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: Python and TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — 1544 test file(s) reach none of 2 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
R5 Dependency Freshness — uses a yarn 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 — no C# was loaded; this repository's Python was read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
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.
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
X5 Nullable reference types — 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.

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

D29 · Static Analysis (SAST) · REDACTED

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

D30 · Dependency Vulnerabilities · High CVE · ×63

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

D29 · Static Analysis (SAST) · REDACTED

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

DM6 · Domain ↔ infrastructure boundary · Domain fused to persistence infrastructure · ×31

Domain fused to persistence infrastructure: BaseEntity packages/core/utils/src/dal/mikro-orm/base-entity.ts:10 — BaseEntity is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: Product packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:14 — Product is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: ProductOption packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:33 — ProductOption is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: ProductOptionValue packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:53 — ProductOptionValue is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: ProductVariant packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:80 — ProductVariant is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: RecursiveEntity1 packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:113 — RecursiveEntity1 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: RecursiveEntity2 packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:132 — RecursiveEntity2 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: Entity1 packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:157 — Entity1 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: Entity2 packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:176 — Entity2 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: DeepRecursiveEntity1 packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:204 — DeepRecursiveEntity1 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: DeepRecursiveEntity2 packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:228 — DeepRecursiveEntity2 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: DeepRecursiveEntity3 packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:256 — DeepRecursiveEntity3 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: DeepRecursiveEntity4 packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:280 — DeepRecursiveEntity4 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: InternalCircularDependencyEntity1 packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:304 — InternalCircularDependencyEntity1 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: Entity1WithUnDecoratedProp packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:340 — Entity1WithUnDecoratedProp is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: Entity2WithUnDecoratedProp packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:361 — Entity2WithUnDecoratedProp is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: SearchableEntity1 packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:391 — SearchableEntity1 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: SearchableEntity2 packages/core/utils/src/dal/mikro-orm/__fixtures__/utils.ts:413 — SearchableEntity2 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: RecursiveEntity1 packages/core/utils/src/dal/mikro-orm/integration-tests/__fixtures__/utils.ts:13 — RecursiveEntity1 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: RecursiveEntity2 packages/core/utils/src/dal/mikro-orm/integration-tests/__fixtures__/utils.ts:32 — RecursiveEntity2 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: Entity1 packages/core/utils/src/dal/mikro-orm/integration-tests/__fixtures__/utils.ts:57 — Entity1 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: Entity2 packages/core/utils/src/dal/mikro-orm/integration-tests/__fixtures__/utils.ts:76 — Entity2 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: DeepRecursiveEntity1 packages/core/utils/src/dal/mikro-orm/integration-tests/__fixtures__/utils.ts:104 — DeepRecursiveEntity1 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: DeepRecursiveEntity2 packages/core/utils/src/dal/mikro-orm/integration-tests/__fixtures__/utils.ts:123 — DeepRecursiveEntity2 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
Domain fused to persistence infrastructure: DeepRecursiveEntity3 packages/core/utils/src/dal/mikro-orm/integration-tests/__fixtures__/utils.ts:151 — DeepRecursiveEntity3 is a domain type carrying TypeORM (@Entity/@Column) persistence decorators fused ON ITS OWN DECLARATION in the domain layer (with domain behaviour, no separated infrastructure model) — a domain ↔ infrastructure leak: the domain entity IS the persistence row (an active-record fusion). Separate the persistence model from the domain aggregate with a mapper.
+ 6 more in this group — see findings.md.

AC4 · Keyboard semantics · Click handler on a non-interactive <span> · ×10

Click handler on a non-interactive <span> packages/admin/dashboard/src/components/common/display-id/display-id.tsx:23 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> packages/admin/dashboard/src/components/common/json-view-section/json-view-section.tsx:197 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> packages/plugins/draft-order/src/admin/components/draft-orders/json-view-section.tsx:189 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> packages/plugins/loyalty/src/admin/components/display-id.tsx:21 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> packages/plugins/loyalty/src/admin/components/json-view-section.tsx:179 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> www/packages/docs-ui/src/components/AiAssistant/SearchWindow/index.tsx:104 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> www/packages/docs-ui/src/components/CodeBlock/Actions/AskAi/index.tsx:47 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> www/packages/docs-ui/src/components/CodeBlock/Actions/Bloom/index.tsx:53 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> www/packages/docs-ui/src/components/CodeBlock/Actions/index.tsx:102 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> www/packages/docs-ui/src/components/CopyButton/index.tsx:48 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.

AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×9

Click handler on a non-interactive <div> packages/admin/dashboard/src/routes/orders/order-allocate-items/components/order-create-fulfillment-form/order-allocate-items-item.tsx:239 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> packages/admin/dashboard/src/routes/orders/order-detail/components/order-summary-section/order-summary-section.tsx:690 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> packages/admin/dashboard/src/routes/orders/order-detail/components/order-summary-section/order-summary-section.tsx:955 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> packages/admin/dashboard/src/routes/product-variants/product-variant-media/components/edit-product-variant-media-form/edit-product-variant-media-form.tsx:411 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> packages/design-system/ui/src/components/code-block/code-block.tsx:140 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> www/packages/docs-ui/src/components/ContentMenu/Section/index.tsx:51 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> www/packages/docs-ui/src/components/MainNav/MobileMenu/SubMenu/index.tsx:56 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> www/packages/docs-ui/src/components/Select/Badge/index.tsx:80 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> www/packages/docs-ui/src/components/Select/Input/index.tsx:45 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.

D30 · Dependency Vulnerabilities · Critical CVE · ×7

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D10 · Test Quality · No assertions (empty test) · ×6

No assertions (empty test): requires Medusa Cloud search credentials packages/modules/search/integration-tests/__tests__/medusa-cloud-search.spec.ts:164 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): noop packages/modules/sales-channel/src/services/__tests__/index.ts:1 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): noop packages/modules/product/src/services/__tests__/index.ts:1 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): noop packages/modules/pricing/src/services/__tests__/index.spec.ts:1 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): noop packages/modules/file/src/services/__tests__/file.spec.ts:2 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): lists payment collections integration-tests/http/__tests__/payment-collection/admin/payment-collection.spec.ts:21 — Test method has an empty body — it asserts nothing and exercises no code.

AC1 · Text alternatives · <img> without a text alternative · ×5

<img> without a text alternative packages/admin/dashboard/src/routes/product-variants/product-variant-detail/components/variant-media-section/variant-media-section.tsx:57 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative packages/admin/dashboard/src/routes/product-variants/product-variant-media/components/edit-product-variant-media-form/edit-product-variant-media-form.tsx:396 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative packages/admin/dashboard/src/routes/product-variants/product-variant-media/components/edit-product-variant-media-form/edit-product-variant-media-form.tsx:430 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative packages/admin/dashboard/src/routes/products/product-image-variants-edit/product-image-variants-edit.tsx:52 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative www/packages/docs-ui/src/components/LearningPath/Icon/index.tsx:26 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.

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

<input> without a programmatic label packages/admin/dashboard/src/components/inputs/chip-input/chip-input.tsx:171 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label packages/design-system/ui/src/blocks/data-table/components/data-table-filter.tsx:618 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label packages/design-system/ui/src/blocks/data-table/components/data-table-filter.tsx:946 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label packages/plugins/loyalty/src/admin/components/chip-input.tsx:171 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label www/apps/book/components/Homepage/NewsletterForm/index.tsx:70 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.

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

<label> that labels no control packages/admin/dashboard/src/components/forms/metadata-form/metadata-form.tsx:154 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/admin/dashboard/src/components/forms/metadata-form/metadata-form.tsx:159 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/plugins/draft-order/src/admin/routes/draft-orders/[id]/@metadata/page.tsx:149 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/plugins/draft-order/src/admin/routes/draft-orders/[id]/@metadata/page.tsx:152 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.

AC4 · Keyboard semantics · Click handler on a non-interactive <li> · ×4

Click handler on a non-interactive <li> www/apps/api-reference/components/Tags/Operation/Parameters/Types/OneOf/index.tsx:80 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <li> www/packages/docs-ui/src/components/MainNav/MobileMenu/Main/index.tsx:28 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <li> www/packages/docs-ui/src/components/Select/Dropdown/index.tsx:93 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <li> www/packages/docs-ui/src/components/VerticalCodeTabs/index.tsx:65 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.

AC4 · Keyboard semantics · Hover-only interaction on <div> · ×3

Hover-only interaction on <div> packages/admin/dashboard/src/routes/translations/translation-list/components/translations-completion-section/translations-completion-section.tsx:206 — This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
Hover-only interaction on <div> www/packages/docs-ui/src/components/MainNav/Items/Dropdown/index.tsx:83 — This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
Hover-only interaction on <div> www/packages/docs-ui/src/components/Menu/SubMenu/index.tsx:20 — This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED

AC2 · Forms & labels · <textarea> without a programmatic label · ×2

<textarea> without a programmatic label www/apps/book/components/Homepage/Bloom/index.tsx:69 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<textarea> without a programmatic label www/packages/docs-ui/src/components/AiAssistant/ChatWindow/Input/index.tsx:166 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.

AC2 · Forms & labels · Custom control with no accessible name on <span> · ×2

Custom control with no accessible name on <span> www/packages/docs-ui/src/components/CodeBlock/Actions/AskAi/index.tsx:47 — This <span> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <span> www/packages/docs-ui/src/components/CodeBlock/Actions/Bloom/index.tsx:53 — This <span> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.

AC4 · Keyboard semantics · Focusable <div> isn't keyboard-operable · ×2

Focusable <div> isn't keyboard-operable packages/admin/dashboard/src/components/data-grid/components/data-grid-root.tsx:684 — This <div> carries tabIndex={0}, so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler.
Focusable <div> isn't keyboard-operable packages/plugins/loyalty/src/admin/components/data-grid/components/data-grid-root.tsx:561 — This <div> carries tabIndex={0}, so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED

REDACTED
REDACTED

R8 · Dependency Hygiene · Unlisted import '@/components' · ×2

Unlisted import '@/components' packages/design-system/ui/src/blocks/data-table/data-table.stories.tsx:5 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@/components' www/packages/docs-ui/src/components/CodeTabs/__tests__/index.test.tsx:4 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import '@/utils' · ×2

Unlisted import '@/utils' packages/design-system/ui/src/components/toaster/toaster.stories.tsx:5 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@/utils' www/apps/api-reference/app/versions/__tests__/route.test.ts:26 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.

AC2 · Forms & labels · Link with no accessible name · ×1

Link with no accessible name www/packages/docs-ui/src/components/AiAssistant/ChatWindow/Footer/index.tsx:17 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.

AC2 · Forms & labels · <button> with no accessible text · ×1

<button> with no accessible text www/packages/docs-ui/src/layouts/main-content.tsx:82 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).

AC3 · Page structure · Document without a <title> · ×1

Document without a <title> www/packages/docs-ui/src/layouts/barebone.tsx:17 — A page with no <title> gives no name in the tab, history or screen-reader page list. Declare it the way this router does — Next App Router `export const metadata = { title }`, React Router/Remix `export function meta`, TanStack Start `head`, or a Helmet/Head component.

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

REDACTED

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

REDACTED

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

REDACTED

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

REDACTED

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

REDACTED

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

REDACTED

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

REDACTED

D30 · Dependency Vulnerabilities · Critical vulnerability · ×1

REDACTED

D30 · Dependency Vulnerabilities · High vulnerability · ×1

REDACTED

D31 · IaC & Container Security · Critical IaC · ×1

REDACTED

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

REDACTED

R8 · Dependency Hygiene · Unlisted import 'qs' · ×1

Unlisted import 'qs' integration-tests/http/__tests__/product-category/store/product-category.spec.ts:4 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'lodash' · ×1

Unlisted import 'lodash' integration-tests/modules/__tests__/rbac-match-endpoint-entities.spec.ts:4 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'ulid' · ×1

Unlisted import 'ulid' packages/core/framework/src/jobs/__tests__/register-jobs.spec.ts:13 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'graphql' · ×1

Unlisted import 'graphql' packages/modules/caching/src/utils/__tests__/parser.test.ts:1 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import '@services/translation-module' · ×1

Unlisted import '@services/translation-module' packages/modules/translation/integration-tests/__tests__/translation-module-service.spec.ts:4 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import '@/hooks' · ×1

Unlisted import '@/hooks' www/packages/docs-ui/src/components/Prerequisites/__tests__/index.test.tsx:4 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import '@/providers' · ×1

Unlisted import '@/providers' www/packages/docs-ui/src/components/Notification/__tests__/index.test.tsx:4 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.

Serious — 446 finding(s)

D17 · Explicit Debt · TodoComment · ×57

TodoComment integration-tests/modules/__tests__/product/workflows/update-product-options.spec.ts:787 — // todo: should we consider only allowing creation of new values for non-exclusive options with this product sepcific flow? — 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 integration-tests/modules/__tests__/price-lists/admin/price-lists.spec.ts:441 — // TODO: reenable when this is translated — 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 integration-tests/modules/__tests__/price-lists/admin/price-lists.spec.ts:573 — // TODO: This is flaky, investigate why — 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 integration-tests/modules/__tests__/order/draft-order.spec.ts:248 — // TODO: add summary fields — 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 integration-tests/modules/__tests__/order/draft-order.spec.ts:614 — // TODO: add summary fields — 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 integration-tests/modules/__tests__/order/order.spec.ts:420 — // TODO: add all summary fields — 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 integration-tests/modules/__tests__/order/workflows/create-complete-return.spec.ts:272 — // TODO: check calculation, I think it should be 60 wit the shipping but the order total is 50 — 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 integration-tests/modules/__tests__/order/workflows/create-complete-return.spec.ts:453 — // TODO: What about order with a sales channel but a shipping option link to a stock from another channel? — 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 integration-tests/modules/__tests__/fulfillment/fulfillment.workflows.spec.ts:361 — // TODO: the revert isn't handling deleting the labels. This needs to be handled uniformly across. — 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 integration-tests/modules/__tests__/customer/store/create-customer.spec.ts:33 — // TODO: Reenable once the customer authentication is fixed, and use the HTTP endpoints instead. — 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 integration-tests/modules/__tests__/cart/store/cart.workflows.spec.ts:546 — // TODO: the state must be "reverted" when runAsStep of sync flows can be reverted — 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 integration-tests/modules/__tests__/cart/store/carts.spec.ts:1093 — // TODO: validate tax totals when calculations are ready — 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 integration-tests/modules/__tests__/auth/admin/email-password-provider.spec.ts:110 — // TODO: This is creating a user with a scope of admin. The client consuming the auth service — 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 integration-tests/http/__tests__/user/admin/user.spec.ts:239 — // TODO: Migrate when analytics config is implemented in 2.0 — 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 integration-tests/http/__tests__/user/admin/user.spec.ts:362 — // TODO: Migrate when implemented in 2.0 — 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 integration-tests/http/__tests__/stock-location/admin/stock-location.spec.ts:455 — // TODO: Ideally we use HTTP here, maybe we should have a get endpoint for fulfillment sets? — 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 integration-tests/http/__tests__/shipping-profile/admin/shipping-profile.spec.ts:114 — // TODO: Associate products with shipping profiles — 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 integration-tests/http/__tests__/shipping-option/store/shipping-option-calculated.spec.ts:212 — // TODO: Update endpoint validator to not require prices if type is calculated — 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 integration-tests/http/__tests__/promotions/admin/promotions.spec.ts:4065 — // TODO: This is returning a default sales channel, but very flakily — 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 integration-tests/http/__tests__/product-category/admin/product-category.spec.ts:1221 — // TODO: In almost all places we use a selector, not an id, to do the update, so throwing a 404 doesn't make sense from the workflow POV — 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 integration-tests/http/__tests__/product-category/admin/product-category.spec.ts:1241 — // TODO: This seems to be a redundant test, I would remove this in V2 — 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 integration-tests/http/__tests__/product-category/admin/product-category.spec.ts:1374 — // TODO: This seems to be a redundant test, I would remove this in V2 — 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 integration-tests/http/__tests__/product/store/product.spec.ts:317 — // TODO: Decide if this is the behavior we want to keep in v2, as it seems a bit strange — 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 integration-tests/http/__tests__/product/store/product.spec.ts:411 — // TODO: Add variant endpoints to the store API (if that is what we want) — 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 integration-tests/http/__tests__/product/store/product.spec.ts:464 — // TODO: Similar to above, decide what the behavior should be in v2 — 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.
+ 32 more in this group — see findings.md.

D10 · Test Quality · Skipped test · ×37

Skipped test: should export the appropriate linkable configuration packages/modules/rbac/integration-tests/__tests__/rbac.spec.ts:26 — Skipped — switched off by it.skip
Skipped test: should release lock in case of timeout failure packages/modules/providers/locking-postgres/integration-tests/__tests__/index.spec.ts:170 — Skipped — switched off by it.skip
Skipped test: test update performance packages/modules/product/integration-tests/__tests__/product-module-service/products.spec.ts:178 — Skipped — switched off by it.skip
Skipped test: set the points to null when explicitly set to null packages/core/utils/src/dml/integration-tests/__tests__/entity.spec.ts:102 — Skipped — switched off by it.skip
Skipped test: should benchmark serializers with autocannon load testing packages/core/utils/src/dal/mikro-orm/__tests__/mikro-orm-serializer.spec.ts:337 — Skipped — switched off by it.skip
Skipped test: should return 401 when admin is not authenticated packages/core/framework/src/http/__tests__/index.spec.ts:273 — Skipped — switched off by it.skip
Skipped test: should add, remove and delete price list prices in batch successfully integration-tests/modules/__tests__/price-lists/admin/price-lists.spec.ts:574 — Skipped — switched off by it.skip
Skipped test: should create a customer integration-tests/modules/__tests__/customer/store/create-customer.spec.ts:34 — Skipped — switched off by it.skip
Skipped test: should throw an error upon logging in with a non existing auth user integration-tests/modules/__tests__/auth/admin/email-password-provider.spec.ts:98 — Skipped — switched off by it.skip
Skipped test: Deletes a user and their analytics config integration-tests/http/__tests__/user/admin/user.spec.ts:240 — Skipped — switched off by it.skip
Skipped test: should throw error when required params are missing integration-tests/http/__tests__/shipping-option/admin/shipping-option.spec.ts:1249 — Skipped — switched off by it.skip
Skipped test: should add rules to a shipping option successfully integration-tests/http/__tests__/shipping-option/admin/shipping-option.spec.ts:1321 — Skipped — switched off by it.skip
Skipped test: should add two promotions and remove one from cart using delete integration-tests/http/__tests__/promotions/admin/promotions.spec.ts:1637 — Skipped — switched off by it.skip
Skipped test: should add two promotions and remove one from cart using update integration-tests/http/__tests__/promotions/admin/promotions.spec.ts:1800 — Skipped — switched off by it.skip
Skipped test: throws an error if invalid ID is sent integration-tests/http/__tests__/product-category/admin/product-category.spec.ts:1223 — Skipped — switched off by it.skip
Skipped test: returns all products if passed PK doesn't have associated channels integration-tests/http/__tests__/product/store/product.spec.ts:318 — Skipped — switched off by it.skip
Skipped test: should return 404 when the requested variant doesn't exist integration-tests/http/__tests__/product/store/product.spec.ts:412 — Skipped — switched off by it.skip
Skipped test: correctly returns a product if passed PK has no associated SCs integration-tests/http/__tests__/product/store/product.spec.ts:465 — Skipped — switched off by it.skip
Skipped test: returns a list of ordered products by variants title DESC integration-tests/http/__tests__/product/store/product.spec.ts:816 — Skipped — switched off by it.skip
Skipped test: returns a list of ordered products by variants prices DESC integration-tests/http/__tests__/product/store/product.spec.ts:847 — Skipped — switched off by it.skip
Skipped test: returns a list of ordered products by variants prices ASC integration-tests/http/__tests__/product/store/product.spec.ts:855 — Skipped — switched off by it.skip
Skipped test: returns gift card product integration-tests/http/__tests__/product/store/product.spec.ts:1009 — Skipped — switched off by it.skip
Skipped test: returns non gift card products integration-tests/http/__tests__/product/store/product.spec.ts:1018 — Skipped — switched off by it.skip
Skipped test: should list only categories that are public and active integration-tests/http/__tests__/product/store/product.spec.ts:2287 — Skipped — switched off by it.skip
Skipped test: should return prices not in price list for list product endpoint integration-tests/http/__tests__/product/admin/product.spec.ts:206 — Skipped — switched off by it.skip
+ 12 more in this group — see findings.md.

D30 · Dependency Vulnerabilities · Medium CVE · ×34

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

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

Focus outline removed inline packages/admin/dashboard/src/components/common/file-upload/file-upload.tsx:114 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/admin/dashboard/src/components/data-grid/components/data-grid-root.tsx:684 — <div> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/admin/dashboard/src/components/forms/metadata-form/metadata-form.tsx:318 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/admin/dashboard/src/components/inputs/combobox/combobox.tsx:358 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/admin/dashboard/src/components/inputs/combobox/combobox.tsx:420 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/admin/dashboard/src/components/inputs/quantity-input/quantity-input.tsx:54 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/admin/dashboard/src/components/layout-composer/sortable-entry.tsx:147 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/admin/dashboard/src/components/layout/main-layout/main-layout.tsx:268 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/admin/dashboard/src/components/layout/nav-item/nav-item.tsx:200 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/admin/dashboard/src/routes/categories/category-detail/components/category-organize-section/category-organize-section.tsx:103 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/admin/dashboard/src/routes/login/components/mfa-challenge-form.tsx:154 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/admin/dashboard/src/routes/products/common/components/category-combobox/category-combobox.tsx:274 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/admin/dashboard/src/routes/products/common/components/category-combobox/category-combobox.tsx:293 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/admin/dashboard/src/routes/products/common/components/category-combobox/category-combobox.tsx:311 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/admin/dashboard/src/routes/products/product-media/components/product-media-gallery/product-media-gallery.tsx:280 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/design-system/ui/src/blocks/data-table/components/data-table-filter.tsx:223 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/design-system/ui/src/blocks/data-table/components/data-table-filter.tsx:238 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/design-system/ui/src/blocks/data-table/components/data-table-filter.tsx:482 — <div> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/design-system/ui/src/blocks/data-table/components/data-table-filter.tsx:618 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/design-system/ui/src/blocks/data-table/components/data-table-filter.tsx:704 — <div> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/design-system/ui/src/blocks/data-table/components/data-table-filter.tsx:946 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/design-system/ui/src/components/input/input.tsx:98 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/plugins/draft-order/src/admin/components/inputs/combobox.tsx:243 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/plugins/draft-order/src/admin/components/inputs/number-input.tsx:72 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/plugins/draft-order/src/admin/routes/draft-orders/[id]/@metadata/page.tsx:293 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
+ 8 more in this group — see findings.md.

D12 · Dependency Hygiene · Floating npm dependency · ×32

Floating npm dependency: @medusajs/workflows-sdk — `@medusajs/workflows-sdk` is declared as `latest` in www/utils/packages/workflows-diagrams-generator/package.json, which names no releasable version: `latest` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: docs-ui — `docs-ui` is declared as `*` in www/apps/api-reference/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: docs-ui — `docs-ui` is declared as `*` in www/apps/book/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: docs-ui — `docs-ui` is declared as `*` in www/apps/cloud/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: docs-ui — `docs-ui` is declared as `*` in www/apps/resources/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: docs-ui — `docs-ui` is declared as `*` in www/apps/ui/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: docs-ui — `docs-ui` is declared as `*` in www/apps/user-guide/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: docs-utils — `docs-utils` is declared as `*` in www/apps/api-reference/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: docs-utils — `docs-utils` is declared as `*` in www/apps/book/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: docs-utils — `docs-utils` is declared as `*` in www/packages/build-scripts/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: docs-utils — `docs-utils` is declared as `*` in www/packages/docs-ui/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: docs-utils — `docs-utils` is declared as `*` in www/packages/remark-rehype-plugins/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: docs-utils — `docs-utils` is declared as `*` in www/packages/tags/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: remark-rehype-plugins — `remark-rehype-plugins` is declared as `*` in www/apps/api-reference/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: remark-rehype-plugins — `remark-rehype-plugins` is declared as `*` in www/apps/book/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: remark-rehype-plugins — `remark-rehype-plugins` is declared as `*` in www/apps/cloud/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: remark-rehype-plugins — `remark-rehype-plugins` is declared as `*` in www/apps/ui/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: remark-rehype-plugins — `remark-rehype-plugins` is declared as `*` in www/apps/user-guide/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: tags — `tags` is declared as `*` in www/packages/build-scripts/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: tsconfig — `tsconfig` is declared as `*` in www/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: turbo — `turbo` is declared as `latest` in www/package.json, which names no releasable version: `latest` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: typedoc-plugin-custom — `typedoc-plugin-custom` is declared as `*` in www/utils/packages/react-docs-generator/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: typedoc-plugin-custom — `typedoc-plugin-custom` is declared as `*` in www/utils/packages/typedoc-generate-references/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: typedoc-plugin-medusa-theme — `typedoc-plugin-medusa-theme` is declared as `*` in www/utils/packages/typedoc-generate-references/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: typedoc-plugin-workflows — `typedoc-plugin-workflows` is declared as `*` in www/utils/packages/typedoc-generate-references/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
+ 7 more in this group — see findings.md.

D12 · Dependency Hygiene · Deprecated · ×23

Deprecated: @types/chalk REDACTED:39 — @types/chalk 2.2.4, declared in REDACTED, is marked deprecated by its publisher: "This is a stub types definition. chalk provides its own type definitions, so you do not need this installed.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @types/commander REDACTED:40 — @types/commander 2.12.5, declared in REDACTED, is marked deprecated by its publisher: "This is a stub types definition. commander provides its own type definitions, so you do not need this installed.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: rollup-plugin-ts REDACTED:111 — rollup-plugin-ts 3.4.5, declared in REDACTED, is marked deprecated by its publisher: "please use @rollup/plugin-typescript and rollup-plugin-dts instead". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: uuid REDACTED:122 — uuid 9.0.1, declared in REDACTED, is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: lodash.isequal packages/admin/dashboard/package.json:92 — lodash.isequal 4.5.0, declared in packages/admin/dashboard/package.json, is marked deprecated by its publisher: "This package is deprecated. Use require('node:util').isDeepStrictEqual instead.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @readme/json-schema-ref-parser REDACTED:40 — @readme/json-schema-ref-parser 1.2.1, declared in REDACTED, is marked deprecated by its publisher: "This package is no longer maintained. Please use `@apidevtools/json-schema-ref-parser` instead.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: lodash.isequal packages/design-system/ui/package.json:68 — lodash.isequal 4.5.0, declared in packages/design-system/ui/package.json, is marked deprecated by its publisher: "This package is deprecated. Use require('node:util').isDeepStrictEqual instead.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint packages/eslint-plugin/package.json:62 — eslint 9.39.4, declared in packages/eslint-plugin/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: lodash.isequal packages/plugins/draft-order/package.json:58 — lodash.isequal 4.5.0, declared in packages/plugins/draft-order/package.json, is marked deprecated by its publisher: "This package is deprecated. Use require('node:util').isDeepStrictEqual instead.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint www/apps/api-reference/package.json:75 — eslint 9.13.0, declared in www/apps/api-reference/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint www/apps/book/package.json:53 — eslint 9.13.0, declared in www/apps/book/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint www/apps/cloud/package.json:52 — eslint 9.13.0, declared in www/apps/cloud/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint www/apps/resources/package.json:54 — eslint 9.13.0, declared in www/apps/resources/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint www/apps/ui/package.json:55 — eslint 9.13.0, declared in www/apps/ui/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint www/apps/user-guide/package.json:50 — eslint 9.13.0, declared in www/apps/user-guide/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint www/package.json:27 — eslint 9.13.0, declared in www/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint-plugin-markdown www/package.json:47 — eslint-plugin-markdown 5.1.0, declared in www/package.json, is marked deprecated by its publisher: "Please use @eslint/markdown instead". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint www/packages/docs-ui/package.json:61 — eslint 9.13.0, declared in www/packages/docs-ui/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: react-uuid www/packages/docs-ui/package.json:104 — react-uuid 2.0.0, declared in www/packages/docs-ui/package.json, is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint REDACTED:20 — eslint 8.36.0, declared in REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint www/utils/packages/docs-generator/package.json:26 — eslint 8.56.0, declared in www/utils/packages/docs-generator/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint www/utils/packages/typedoc-plugin-custom/package.json:38 — eslint 9.39.4, declared in www/utils/packages/typedoc-plugin-custom/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint www/utils/packages/typedoc-plugin-workflows/package.json:41 — eslint 8.57.1, declared in www/utils/packages/typedoc-plugin-workflows/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.

D23 · Boundary Type-Coupling · Cross-context type BigNumberInput (types → order) · ×22

Cross-context type BigNumberInput (types → order) packages/modules/order/src/types/line-item.ts:32 — BigNumberInput (context types) is exposed in order's public surface via CreateOrderLineItemDTO.quantity — couples the contexts.
Cross-context type BigNumberInput (types → order) packages/modules/order/src/types/line-item.ts:33 — BigNumberInput (context types) is exposed in order's public surface via CreateOrderLineItemDTO.unit_price — couples the contexts.
Cross-context type BigNumberInput (types → order) packages/modules/order/src/types/order-detail.ts:8 — BigNumberInput (context types) is exposed in order's public surface via PartialUpsertOrderItemDTO.quantity — couples the contexts.
Cross-context type BigNumberInput (types → order) packages/modules/order/src/types/order-detail.ts:9 — BigNumberInput (context types) is exposed in order's public surface via PartialUpsertOrderItemDTO.fulfilled_quantity — couples the contexts.
Cross-context type BigNumberInput (types → order) packages/modules/order/src/types/order-detail.ts:10 — BigNumberInput (context types) is exposed in order's public surface via PartialUpsertOrderItemDTO.return_requested_quantity — couples the contexts.
Cross-context type BigNumberInput (types → order) packages/modules/order/src/types/order-detail.ts:11 — BigNumberInput (context types) is exposed in order's public surface via PartialUpsertOrderItemDTO.return_received_quantity — couples the contexts.
Cross-context type BigNumberInput (types → order) packages/modules/order/src/types/order-detail.ts:12 — BigNumberInput (context types) is exposed in order's public surface via PartialUpsertOrderItemDTO.return_dismissed_quantity — couples the contexts.
Cross-context type BigNumberInput (types → order) packages/modules/order/src/types/order-detail.ts:13 — BigNumberInput (context types) is exposed in order's public surface via PartialUpsertOrderItemDTO.written_off_quantity — couples the contexts.
Cross-context type BigNumberInput (types → order) packages/modules/order/src/types/order-detail.ts:22 — BigNumberInput (context types) is exposed in order's public surface via CreateOrderItemDTO.quantity — couples the contexts.
Cross-context type BigNumberInput (types → order) packages/modules/order/src/types/shipping-method.ts:11 — BigNumberInput (context types) is exposed in order's public surface via CreateOrderShippingMethodDTO.amount — couples the contexts.
Cross-context type BigNumberInput (types → order) packages/modules/order/src/types/shipping-method.ts:19 — BigNumberInput (context types) is exposed in order's public surface via UpdateOrderShippingMethodDTO.amount — couples the contexts.
Cross-context type BigNumberInput (types → order) packages/modules/order/src/types/utils/index.ts:98 — BigNumberInput (context types) is exposed in order's public surface via OrderSummaryCalculated.current_order_total — couples the contexts.
Cross-context type BigNumberInput (types → order) packages/modules/order/src/types/utils/index.ts:99 — BigNumberInput (context types) is exposed in order's public surface via OrderSummaryCalculated.original_order_total — couples the contexts.
Cross-context type BigNumberInput (types → order) packages/modules/order/src/types/utils/index.ts:100 — BigNumberInput (context types) is exposed in order's public surface via OrderSummaryCalculated.transaction_total — couples the contexts.
Cross-context type BigNumberInput (types → order) packages/modules/order/src/types/utils/index.ts:101 — BigNumberInput (context types) is exposed in order's public surface via OrderSummaryCalculated.pending_difference — couples the contexts.
Cross-context type BigNumberInput (types → order) packages/modules/order/src/types/utils/index.ts:102 — BigNumberInput (context types) is exposed in order's public surface via OrderSummaryCalculated.paid_total — couples the contexts.
Cross-context type BigNumberInput (types → order) packages/modules/order/src/types/utils/index.ts:103 — BigNumberInput (context types) is exposed in order's public surface via OrderSummaryCalculated.refunded_total — couples the contexts.
Cross-context type BigNumberInput (types → order) packages/modules/order/src/types/utils/index.ts:104 — BigNumberInput (context types) is exposed in order's public surface via OrderSummaryCalculated.credit_line_total — couples the contexts.
Cross-context type BigNumberInput (types → order) packages/modules/order/src/types/utils/index.ts:105 — BigNumberInput (context types) is exposed in order's public surface via OrderSummaryCalculated.accounting_total — couples the contexts.
Cross-context type BigNumberInput (types → order) packages/modules/order/src/types/utils/index.ts:109 — BigNumberInput (context types) is exposed in order's public surface via OrderTransaction.amount — couples the contexts.
Cross-context type BigNumberInput (types → order) packages/modules/order/src/types/utils/index.ts:114 — BigNumberInput (context types) is exposed in order's public surface via OrderChangeEvent.amount — couples the contexts.
Cross-context type BigNumberInput (types → order) packages/modules/order/src/types/utils/index.ts:149 — BigNumberInput (context types) is exposed in order's public surface via ActionTypeDefinition.operation — couples the contexts.

D10 · Test Quality · No assertions · ×21

No assertions: should subscribe to a async workflow and receive the response when it finishes packages/modules/workflow-engine-redis/integration-tests/__tests__/index.spec.ts:947 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should not skip step if condition is true packages/modules/workflow-engine-redis/integration-tests/__tests__/index.spec.ts:973 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should subscribe to a async workflow and receive the response when it finishes packages/modules/workflow-engine-inmemory/integration-tests/__tests__/index.spec.ts:856 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: deletes multiple files in bulk packages/modules/providers/file-s3/integration-tests/__tests__/services.spec.ts:198 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should create a payment session successfully packages/modules/payment/integration-tests/__tests__/loaders/providers.spec.ts:41 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: create client connection from connection options packages/core/utils/src/pg/integration-tests/__tests__/pg_utils.spec.ts:22 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: create client connection from connectionString without db name packages/core/utils/src/pg/integration-tests/__tests__/pg_utils.spec.ts:28 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: type-hint model properties packages/core/utils/src/modules-sdk/__tests__/medusa-service-typings.spec.ts:76 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: type-hint DTO properties packages/core/utils/src/modules-sdk/__tests__/medusa-service-typings.spec.ts:135 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: type-hint force overridden properties packages/core/utils/src/modules-sdk/__tests__/medusa-service-typings.spec.ts:150 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: define custom DTO for inputs packages/core/utils/src/modules-sdk/__tests__/medusa-service-typings.spec.ts:169 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: type-hint model properties packages/core/utils/src/modules-sdk/__tests__/medusa-service-typings.spec.ts:188 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: type-hint DTO properties packages/core/utils/src/modules-sdk/__tests__/medusa-service-typings.spec.ts:267 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: type-hint force overridden properties packages/core/utils/src/modules-sdk/__tests__/medusa-service-typings.spec.ts:330 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: define custom DTO for inputs packages/core/utils/src/modules-sdk/__tests__/medusa-service-typings.spec.ts:349 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: define JSON property without a data-type does not widen to any packages/core/utils/src/dml/__tests__/entity-builder.spec.ts:1546 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should return a single data item when is_list is false packages/core/core-flows/src/common/steps/__tests__/use-query-graph-step.spec.ts:24 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should return a list of data items when is_list is true packages/core/core-flows/src/common/steps/__tests__/use-query-graph-step.spec.ts:52 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should return a list of data items when is_list is not specified packages/core/core-flows/src/common/steps/__tests__/use-query-graph-step.spec.ts:77 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should cancel an order integration-tests/modules/__tests__/order/workflows/cancel-order.spec.ts:58 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should search through the indexed data and return the correct results ordered and filtered [3] integration-tests/modules/__tests__/index/search.spec.ts:188 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.

D12 · Dependency Hygiene · One package at two majors across the workspace · ×17

One package at two majors across the workspace: @medusajs/core-flows — `@medusajs/core-flows` is maintained at 2 different major versions inside this one repository — major 0 in integration-tests/package.json; major 2 in packages/medusa/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: @medusajs/medusa — `@medusajs/medusa` is maintained at 2 different major versions inside this one repository — major 1 in integration-tests/package.json; major 2 in REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: @react-hook/resize-observer — `@react-hook/resize-observer` is maintained at 2 different major versions inside this one repository — major 1 in www/packages/docs-ui/package.json; major 2 in www/apps/api-reference/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: @readme/openapi-parser — `@readme/openapi-parser` is maintained at 2 different major versions inside this one repository — major 2 in REDACTED, www/apps/api-reference/package.json; major 3 in www/packages/build-scripts/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: @typescript-eslint/parser — `@typescript-eslint/parser` is maintained at 2 different major versions inside this one repository — major 6 in REDACTED; major 8 in packages/eslint-plugin/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: algoliasearch — `algoliasearch` is maintained at 2 different major versions inside this one repository — major 4 in www/apps/api-reference/package.json; major 5 in www/packages/docs-ui/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: chalk — `chalk` is maintained at 2 different major versions inside this one repository — major 4 in packages/cli/create-medusa-app/package.json, packages/cli/http-types-generator/package.json, packages/cli/medusa-cli/package.json (+1 more); major 5 in www/utils/packages/docs-automator/package.json, www/utils/packages/docs-generator/package.json, www/utils/packages/react-docs-generator/package.json (+1 more). Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: clsx — `clsx` is maintained at 2 different major versions inside this one repository — major 1 in packages/design-system/ui/package.json; major 2 in www/apps/api-reference/package.json, www/apps/book/package.json, www/apps/cloud/package.json (+3 more). Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: eslint — `eslint` is maintained at 2 different major versions inside this one repository — major 8 in REDACTED, www/utils/packages/docs-generator/package.json, www/utils/packages/typedoc-plugin-workflows/package.json; major 9 in www/package.json, www/utils/packages/typedoc-plugin-custom/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: get-port — `get-port` is maintained at 2 different major versions inside this one repository — major 5 in packages/admin/admin-bundler/package.json, packages/medusa-test-utils/package.json; major 7 in integration-tests/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: minimatch — `minimatch` is maintained at 2 different major versions inside this one repository — major 9 in www/utils/packages/docs-generator/package.json; major 10 in www/utils/packages/typedoc-plugin-custom/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: motion — `motion` is maintained at 2 different major versions inside this one repository — major 11 in packages/admin/dashboard/package.json; major 12 in www/packages/docs-ui/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: prettier — `prettier` is maintained at 2 different major versions inside this one repository — major 2 in packages/cli/http-types-generator/package.json; major 3 in www/package.json, REDACTED, www/utils/packages/utils/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: react — `react` is maintained at 2 different major versions inside this one repository — major 18 in packages/admin/dashboard/package.json; major 19 in www/apps/api-reference/package.json, www/apps/book/package.json, www/apps/cloud/package.json (+4 more). Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: react-dom — `react-dom` is maintained at 2 different major versions inside this one repository — major 18 in packages/admin/dashboard/package.json; major 19 in www/apps/api-reference/package.json, www/apps/book/package.json, www/apps/cloud/package.json (+4 more). Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: rehype-mdx-code-props — `rehype-mdx-code-props` is maintained at 2 different major versions inside this one repository — major 2 in www/apps/book/package.json, www/apps/cloud/package.json, www/apps/resources/package.json (+2 more); major 3 in www/apps/api-reference/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: stripe — `stripe` is maintained at 2 different major versions inside this one repository — major 15 in packages/modules/providers/payment-stripe/package.json; major 19 in packages/modules/payment/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.

D23 · Boundary Type-Coupling · Cross-context type BigNumberInput (types → core-flows) · ×17

Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/payment-collection/steps/create-payment-session.ts:24 — BigNumberInput (context types) is exposed in core-flows's public surface via CreatePaymentSessionStepInput.amount — couples the contexts.
Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/payment-collection/steps/update-payment-session.ts:13 — BigNumberInput (context types) is exposed in core-flows's public surface via UpdatePaymentSessionStepInput.amount — couples the contexts.
Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/cart/workflows/refund-payment-recreate-payment-session.ts:50 — BigNumberInput (context types) is exposed in core-flows's public surface via refundPaymentAndRecreatePaymentSessionWorkflowInput.amount — couples the contexts.
Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/cart/steps/confirm-inventory.ts:20 — BigNumberInput (context types) is exposed in core-flows's public surface via ConfirmVariantInventoryStepInput.items — couples the contexts.
Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/cart/utils/find-matching-line-item.ts:10 — BigNumberInput (context types) is exposed in core-flows's public surface via MatchableLineItem.unit_price — couples the contexts.
Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/cart/steps/get-line-item-pricing-quantities.ts:24 — BigNumberInput (context types) is exposed in core-flows's public surface via GetLineItemPricingQuantitiesStepInput.items — couples the contexts.
Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/cart/steps/validate-variant-prices.ts:12 — BigNumberInput (context types) is exposed in core-flows's public surface via ValidateVariantPricesStepInput.variants — couples the contexts.
Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/cart/utils/prepare-line-item-data.ts:62 — BigNumberInput (context types) is exposed in core-flows's public surface via PrepareVariantLineItemInput.calculated_price — couples the contexts.
Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/cart/utils/prepare-line-item-data.ts:79 — BigNumberInput (context types) is exposed in core-flows's public surface via PrepareLineItemDataInput.unitPrice — couples the contexts.
Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/cart/workflows/confirm-variant-inventory.ts:19 — BigNumberInput (context types) is exposed in core-flows's public surface via ConfirmVariantInventoryWorkflowOutput.items — couples the contexts.
Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/order/workflows/payments/create-order-refund-credit-lines.ts:36 — BigNumberInput (context types) is exposed in core-flows's public surface via create-order-refund-credit-lines.createOrderRefundCreditLinesWorkflow — couples the contexts.
Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/inventory/steps/delete-inventory-items.ts:7 — BigNumberInput (context types) is exposed in core-flows's public surface via ValidateInventoryDeleteStepInput.inventory_items — couples the contexts.
Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/payment/workflows/refund-payment.ts:71 — BigNumberInput (context types) is exposed in core-flows's public surface via refund-payment.validateRefundPaymentExceedsCapturedAmountStep — couples the contexts.
Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/draft-order/workflows/add-draft-order-shipping-methods.ts:48 — BigNumberInput (context types) is exposed in core-flows's public surface via AddDraftOrderShippingMethodsWorkflowInput.custom_amount — couples the contexts.
Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/draft-order/steps/restore-draft-order-shipping-methods.ts:18 — BigNumberInput (context types) is exposed in core-flows's public surface via RestoreDraftOrderShippingMethodsStepInput.shippingMethods — couples the contexts.
Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/draft-order/steps/update-draft-order-shipping-metod.ts:30 — BigNumberInput (context types) is exposed in core-flows's public surface via UpdateDraftOrderShippingMethodStepInput.amount — couples the contexts.
Cross-context type BigNumberInput (types → core-flows) packages/core/core-flows/src/draft-order/workflows/update-draft-order-shipping-method.ts:37 — BigNumberInput (context types) is exposed in core-flows's public surface via UpdateDraftOrderShippingMethodWorkflowInput.data — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type BigNumberInput (types → promotion) · ×17

Cross-context type BigNumberInput (types → promotion) packages/modules/promotion/src/types/application-method.ts:16 — BigNumberInput (context types) is exposed in promotion's public surface via CreateApplicationMethodDTO.value — couples the contexts.
Cross-context type BigNumberInput (types → promotion) packages/modules/promotion/src/types/application-method.ts:19 — BigNumberInput (context types) is exposed in promotion's public surface via CreateApplicationMethodDTO.max_quantity — couples the contexts.
Cross-context type BigNumberInput (types → promotion) packages/modules/promotion/src/types/application-method.ts:20 — BigNumberInput (context types) is exposed in promotion's public surface via CreateApplicationMethodDTO.buy_rules_min_quantity — couples the contexts.
Cross-context type BigNumberInput (types → promotion) packages/modules/promotion/src/types/application-method.ts:21 — BigNumberInput (context types) is exposed in promotion's public surface via CreateApplicationMethodDTO.apply_to_quantity — couples the contexts.
Cross-context type BigNumberInput (types → promotion) packages/modules/promotion/src/types/application-method.ts:29 — BigNumberInput (context types) is exposed in promotion's public surface via UpdateApplicationMethodDTO.value — couples the contexts.
Cross-context type BigNumberInput (types → promotion) packages/modules/promotion/src/types/application-method.ts:32 — BigNumberInput (context types) is exposed in promotion's public surface via UpdateApplicationMethodDTO.max_quantity — couples the contexts.
Cross-context type BigNumberInput (types → promotion) packages/modules/promotion/src/types/application-method.ts:33 — BigNumberInput (context types) is exposed in promotion's public surface via UpdateApplicationMethodDTO.buy_rules_min_quantity — couples the contexts.
Cross-context type BigNumberInput (types → promotion) packages/modules/promotion/src/types/application-method.ts:34 — BigNumberInput (context types) is exposed in promotion's public surface via UpdateApplicationMethodDTO.apply_to_quantity — couples the contexts.
Cross-context type BigNumberInput (types → promotion) packages/modules/promotion/src/types/campaign-budget.ts:10 — BigNumberInput (context types) is exposed in promotion's public surface via CreateCampaignBudgetDTO.limit — couples the contexts.
Cross-context type BigNumberInput (types → promotion) packages/modules/promotion/src/types/campaign-budget.ts:12 — BigNumberInput (context types) is exposed in promotion's public surface via CreateCampaignBudgetDTO.used — couples the contexts.
Cross-context type BigNumberInput (types → promotion) packages/modules/promotion/src/types/campaign-budget.ts:19 — BigNumberInput (context types) is exposed in promotion's public surface via UpdateCampaignBudgetDTO.limit — couples the contexts.
Cross-context type BigNumberInput (types → promotion) packages/modules/promotion/src/types/campaign-budget.ts:21 — BigNumberInput (context types) is exposed in promotion's public surface via UpdateCampaignBudgetDTO.used — couples the contexts.
Cross-context type BigNumberInput (types → promotion) packages/modules/promotion/src/types/campaign-budget.ts:28 — BigNumberInput (context types) is exposed in promotion's public surface via CreateCampaignBudgetUsageDTO.used — couples the contexts.
Cross-context type BigNumberInput (types → promotion) packages/modules/promotion/src/types/campaign-budget.ts:33 — BigNumberInput (context types) is exposed in promotion's public surface via UpdateCampaignBudgetUsageDTO.used — couples the contexts.
Cross-context type BigNumberInput (types → promotion) packages/modules/promotion/src/utils/compute-actions/usage.ts:28 — BigNumberInput (context types) is exposed in promotion's public surface via usage.computeActionForBudgetExceeded — couples the contexts.
Cross-context type BigNumberInput (types → promotion) packages/modules/promotion/src/utils/compute-actions/buy-get.ts:517 — BigNumberInput (context types) is exposed in promotion's public surface via buy-get.getComputedActionsForBuyGet — couples the contexts.
Cross-context type BigNumberInput (types → promotion) packages/modules/promotion/src/utils/compute-actions/shipping-methods.ts:65 — BigNumberInput (context types) is exposed in promotion's public surface via shipping-methods.applyPromotionToShippingMethods — couples the contexts.

D36 · Supply-chain Provenance & Signing · REDACTED

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

D23 · Boundary Type-Coupling · Cross-context type BigNumberInput (types → utils) · ×10

Cross-context type BigNumberInput (types → utils) packages/core/utils/src/totals/big-number.ts:16 — BigNumberInput (context types) is exposed in utils's public surface via BigNumber.constructor — couples the contexts.
Cross-context type BigNumberInput (types → utils) packages/core/utils/src/totals/big-number.ts:23 — BigNumberInput (context types) is exposed in utils's public surface via BigNumber.setRawValueOrThrow — couples the contexts.
Cross-context type BigNumberInput (types → utils) packages/core/utils/src/totals/big-number.ts:109 — BigNumberInput (context types) is exposed in utils's public surface via BigNumber.raw — couples the contexts.
Cross-context type BigNumberInput (types → utils) packages/core/utils/src/totals/credit-lines/index.ts:7 — BigNumberInput (context types) is exposed in utils's public surface via index.calculateCreditLinesTotal — couples the contexts.
Cross-context type BigNumberInput (types → utils) packages/core/utils/src/totals/adjustment/index.ts:6 — BigNumberInput (context types) is exposed in utils's public surface via index.calculateAdjustmentTotal — couples the contexts.
Cross-context type BigNumberInput (types → utils) packages/core/utils/src/totals/tax/index.ts:5 — BigNumberInput (context types) is exposed in utils's public surface via index.calculateTaxTotal — couples the contexts.
Cross-context type BigNumberInput (types → utils) packages/core/utils/src/totals/cart/index.ts:19 — BigNumberInput (context types) is exposed in utils's public surface via DecorateCartLikeInputDTO.credit_lines — couples the contexts.
Cross-context type BigNumberInput (types → utils) packages/core/utils/src/totals/cart/index.ts:22 — BigNumberInput (context types) is exposed in utils's public surface via DecorateCartLikeInputDTO.items — couples the contexts.
Cross-context type BigNumberInput (types → utils) packages/core/utils/src/totals/cart/index.ts:32 — BigNumberInput (context types) is exposed in utils's public surface via DecorateCartLikeInputDTO.shipping_methods — couples the contexts.
Cross-context type BigNumberInput (types → utils) packages/core/utils/src/totals/promotion/index.ts:97 — BigNumberInput (context types) is exposed in utils's public surface via index.calculateAdjustmentAmountFromPromotion — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type Filter (search → types) · ×7

Cross-context type Filter (search → types) packages/core/types/src/product/common.ts:766 — Filter (context search) is exposed in types's public surface via FilterableProductProps.tags — couples the contexts.
Cross-context type Filter (search → types) packages/core/types/src/product/common.ts:778 — Filter (context search) is exposed in types's public surface via FilterableProductProps.options — couples the contexts.
Cross-context type Filter (search → types) packages/core/types/src/http/product/common.ts:551 — Filter (context search) is exposed in types's public surface via BaseProductVariantParams.options — couples the contexts.
Cross-context type Filter (search → types) packages/core/types/src/http/product/store/queries.ts:70 — Filter (context search) is exposed in types's public surface via StoreProductListParams.variants — couples the contexts.
Cross-context type Filter (search → types) packages/core/types/src/http/product/admin/queries.ts:132 — Filter (context search) is exposed in types's public surface via AdminProductExportParams.variants — couples the contexts.
Cross-context type Filter (search → types) packages/core/types/src/http/promotion/admin/queries.ts:33 — Filter (context search) is exposed in types's public surface via AdminGetPromotionsParams.application_method — couples the contexts.
Cross-context type Filter (search → types) packages/core/types/src/auth/common/auth-identity.ts:186 — Filter (context search) is exposed in types's public surface via FilterableAuthIdentityProps.provider_identities — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type BigNumberInput (types → cart) · ×7

Cross-context type BigNumberInput (types → cart) packages/modules/cart/src/types/line-item-adjustment.ts:5 — BigNumberInput (context types) is exposed in cart's public surface via CreateLineItemAdjustmentDTO.amount — couples the contexts.
Cross-context type BigNumberInput (types → cart) packages/modules/cart/src/types/line-item.ts:30 — BigNumberInput (context types) is exposed in cart's public surface via CreateLineItemDTO.quantity — couples the contexts.
Cross-context type BigNumberInput (types → cart) packages/modules/cart/src/types/line-item.ts:31 — BigNumberInput (context types) is exposed in cart's public surface via CreateLineItemDTO.unit_price — couples the contexts.
Cross-context type BigNumberInput (types → cart) packages/modules/cart/src/types/shipping-method.ts:6 — BigNumberInput (context types) is exposed in cart's public surface via CreateShippingMethodDTO.amount — couples the contexts.
Cross-context type BigNumberInput (types → cart) packages/modules/cart/src/types/shipping-method.ts:13 — BigNumberInput (context types) is exposed in cart's public surface via UpdateShippingMethodDTO.amount — couples the contexts.
Cross-context type BigNumberInput (types → cart) packages/modules/cart/src/types/shipping-method-adjustment.ts:6 — BigNumberInput (context types) is exposed in cart's public surface via CreateShippingMethodAdjustmentDTO.amount — couples the contexts.
Cross-context type BigNumberInput (types → cart) packages/modules/cart/src/types/shipping-method-adjustment.ts:15 — BigNumberInput (context types) is exposed in cart's public surface via UpdateShippingMethodAdjustmentDTO.amount — couples the contexts.

AC4 · Keyboard semantics · Anchor without href · ×5

Anchor without href packages/admin/dashboard/src/routes/orders/order-create-claim/components/claim-create-form/claim-create-form.tsx:634 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href packages/admin/dashboard/src/routes/orders/order-create-claim/components/claim-create-form/claim-outbound-section.tsx:302 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href packages/admin/dashboard/src/routes/orders/order-create-exchange/components/exchange-create-form/exchange-inbound-section.tsx:346 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href packages/admin/dashboard/src/routes/orders/order-create-exchange/components/exchange-create-form/exchange-outbound-section.tsx:310 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href packages/admin/dashboard/src/routes/orders/order-create-return/components/return-create-form/return-create-form.tsx:438 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.

D23 · Boundary Type-Coupling · Cross-context type TransactionHandlerType (utils → orchestration) · ×5

Cross-context type TransactionHandlerType (utils → orchestration) packages/core/orchestration/src/transaction/distributed-transaction.ts:101 — TransactionHandlerType (context utils) is exposed in orchestration's public surface via TransactionStepError.constructor — couples the contexts.
Cross-context type TransactionHandlerType (utils → orchestration) packages/core/orchestration/src/transaction/distributed-transaction.ts:103 — TransactionHandlerType (context utils) is exposed in orchestration's public surface via TransactionStepError.handlerType — couples the contexts.
Cross-context type TransactionHandlerType (utils → orchestration) packages/core/orchestration/src/transaction/distributed-transaction.ts:443 — TransactionHandlerType (context utils) is exposed in orchestration's public surface via DistributedTransaction.getErrors — couples the contexts.
Cross-context type TransactionHandlerType (utils → orchestration) packages/core/orchestration/src/transaction/distributed-transaction.ts:451 — TransactionHandlerType (context utils) is exposed in orchestration's public surface via DistributedTransaction.addError — couples the contexts.
Cross-context type TransactionHandlerType (utils → orchestration) packages/core/orchestration/src/transaction/distributed-transaction.ts:463 — TransactionHandlerType (context utils) is exposed in orchestration's public surface via DistributedTransaction.addResponse — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type BigNumberInput (types → inventory) · ×5

Cross-context type BigNumberInput (types → inventory) packages/modules/inventory/src/services/inventory-module.ts:917 — BigNumberInput (context types) is exposed in inventory's public surface via InventoryModuleService.adjustInventory — couples the contexts.
Cross-context type BigNumberInput (types → inventory) packages/modules/inventory/src/services/inventory-module.ts:924 — BigNumberInput (context types) is exposed in inventory's public surface via InventoryModuleService.adjustInventory — couples the contexts.
Cross-context type BigNumberInput (types → inventory) packages/modules/inventory/src/services/inventory-module.ts:933 — BigNumberInput (context types) is exposed in inventory's public surface via InventoryModuleService.adjustInventory — couples the contexts.
Cross-context type BigNumberInput (types → inventory) packages/modules/inventory/src/services/inventory-module.ts:972 — BigNumberInput (context types) is exposed in inventory's public surface via InventoryModuleService.adjustInventory_ — couples the contexts.
Cross-context type BigNumberInput (types → inventory) packages/modules/inventory/src/services/inventory-module.ts:1146 — BigNumberInput (context types) is exposed in inventory's public surface via InventoryModuleService.confirmInventory — couples the contexts.

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

Low cohesion: DashboardApp (LCOM4 10) packages/admin/dashboard/src/dashboard-app/dashboard-app.tsx:61 — DashboardApp's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PostgresProvider (LCOM4 5) packages/modules/index/src/services/postgres-provider.ts:43 — PostgresProvider's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Migrator (LCOM4 4) packages/core/framework/src/migrations/migrator.ts:8 — Migrator's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: KnowledgeBaseFactory (LCOM4 4) www/utils/packages/docs-generator/src/classes/helpers/knowledge-base-factory.ts:63 — KnowledgeBaseFactory's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: DefaultKindGenerator (LCOM4 4) www/utils/packages/docs-generator/src/classes/kinds/default.ts:43 — DefaultKindGenerator's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.

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

Runner config excludes tests no gate runs integration-tests/http/jest.config.js:11 — `__tests__/fixtures` removes 2 test(s) in 2 file(s) (e.g. `integration-tests/http/__tests__/fixtures/order.ts`, `integration-tests/http/__tests__/fixtures/shipping.ts`) from what jest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.
Runner config excludes tests no gate runs integration-tests/modules/jest.config.js:12 — `__tests__/fixtures` removes 3 test(s) in 3 file(s) (e.g. `integration-tests/modules/__tests__/fixtures/index.ts`, `integration-tests/modules/__tests__/fixtures/fulfillment/index.ts`) from what jest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.
Runner config excludes tests no gate runs integration-tests/modules/jest.config.js:15 — `__fixtures__` removes 15 test(s) in 15 file(s) (e.g. `integration-tests/modules/__tests__/__fixtures__/testing-module/index.ts`, `integration-tests/modules/__tests__/__fixtures__/translation-test/medusa-config.ts`) from what jest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.
Runner config excludes tests no gate runs packages/cli/http-types-generator/jest.config.js:7 — `__tests__/utils/` removes 1 test(s) in 1 file(s) (e.g. `packages/cli/http-types-generator/src/__tests__/utils/ts-utils.ts`) from what jest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.

AC2 · Forms & labels · <RadioGroup> field component without a label · ×3

<RadioGroup> field component without a label packages/admin/dashboard/src/routes/orders/order-balance-settlement/components/order-balance-settlement-form/order-balance-settlement-form.tsx:217 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — 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.
<RadioGroup> field component without a label packages/plugins/loyalty/src/admin/routes/gift-cards/[id]/@expiration/page.tsx:103 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — 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.
<RadioGroup> field component without a label www/packages/docs-ui/src/components/Feedback/index.tsx:246 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. 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.

AC2 · Forms & labels · <Select> field component without a label · ×3

<Select> field component without a label packages/admin/dashboard/src/routes/orders/order-balance-settlement/components/order-balance-settlement-form/order-balance-settlement-form.tsx:252 — 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.
<Select> field component without a label packages/admin/dashboard/src/routes/orders/order-create-refund/components/create-refund-form/create-refund-form.tsx:139 — 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.
<Select> field component without a label packages/design-system/ui/src/blocks/data-table/components/data-table-filter.tsx:1209 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing it renders carries one either (a name prop is the form-submission key, not a label). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. 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.

AC2 · Forms & labels · <Combobox> field component without a label · ×3

<Combobox> field component without a label packages/admin/dashboard/src/routes/products/product-create/components/product-create-details-form/components/product-create-details-variant-section/product-create-details-variant-section.tsx:470 — 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.
<Combobox> field component without a label packages/admin/dashboard/src/routes/products/product-create/components/product-create-details-form/components/product-create-details-variant-section/product-create-details-variant-section.tsx:568 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — 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.
<Combobox> field component without a label packages/admin/dashboard/src/routes/products/product-options-manage/components/product-options-manage-form/product-options-manage-form.tsx:625 — 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.

D23 · Boundary Type-Coupling · Cross-context type CheckConstraint (types → utils) · ×3

Cross-context type CheckConstraint (types → utils) packages/core/utils/src/dml/entity.ts:188 — CheckConstraint (context types) is exposed in utils's public surface via DmlEntity.parse — couples the contexts.
Cross-context type CheckConstraint (types → utils) packages/core/utils/src/dml/entity.ts:336 — CheckConstraint (context types) is exposed in utils's public surface via DmlEntity.checks — couples the contexts.
Cross-context type CheckConstraint (types → utils) packages/core/utils/src/dml/helpers/mikro-orm/apply-checks.ts:8 — CheckConstraint (context types) is exposed in utils's public surface via apply-checks.applyChecks — couples the contexts.

D36 · Supply-chain Provenance & Signing · REDACTED

REDACTED
REDACTED
REDACTED

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

<fieldset> without a <legend> packages/admin/dashboard/src/components/forms/address-form/address-form.tsx:36 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> packages/admin/dashboard/src/components/forms/address-form/address-form.tsx:101 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.

AC2 · Forms & labels · <DatePicker> field component without a label · ×2

<DatePicker> field component without a label packages/admin/dashboard/src/components/table/data-table/data-table-filter/date-filter.tsx:221 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — 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.
<DatePicker> field component without a label packages/admin/dashboard/src/components/table/data-table/data-table-filter/date-filter.tsx:236 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — 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.

AC2 · Forms & labels · <TextArea> field component without a label · ×2

<TextArea> field component without a label www/packages/docs-ui/src/components/Feedback/index.tsx:272 — 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.
<TextArea> field component without a label www/packages/docs-ui/src/components/Rating/index.tsx:124 — 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.

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

Animation without a prefers-reduced-motion guard www/apps/book/components/Homepage/Bloom/index.tsx:91 — <span> moves — its `animate-[pulsingCursor_0.8s_ease-in-out_infinite]` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard www/packages/docs-ui/src/components/AiAssistant/Loading/index.tsx:178 — <div> moves — its `animate-[shimmer_1.5s_linear_infinite]` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.

D23 · Boundary Type-Coupling · Cross-context type Filter (search → dashboard) · ×2

Cross-context type Filter (search → dashboard) packages/admin/dashboard/src/components/table/data-table/data-table-query/data-table-query.tsx:9 — Filter (context search) is exposed in dashboard's public surface via DataTableQueryProps.filters — couples the contexts.
Cross-context type Filter (search → dashboard) packages/admin/dashboard/src/hooks/table/filters/use-order-table-filters.tsx:11 — Filter (context search) is exposed in dashboard's public surface via use-order-table-filters.useOrderTableFilters — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type PromotionActions (utils → core-flows) · ×2

Cross-context type PromotionActions (utils → core-flows) packages/core/core-flows/src/draft-order/steps/update-draft-order-promotions.ts:30 — PromotionActions (context utils) is exposed in core-flows's public surface via UpdateDraftOrderPromotionsStepInput.action — couples the contexts.
Cross-context type PromotionActions (utils → core-flows) packages/core/core-flows/src/draft-order/workflows/refresh-draft-order-adjustments.ts:55 — PromotionActions (context utils) is exposed in core-flows's public surface via RefreshDraftOrderAdjustmentsWorkflowInput.action — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type BigNumberInput (types → payment) · ×2

Cross-context type BigNumberInput (types → payment) packages/modules/payment/src/providers/payment-medusa/utils/get-smallest-unit.ts:45 — BigNumberInput (context types) is exposed in payment's public surface via get-smallest-unit.getSmallestUnit — couples the contexts.
Cross-context type BigNumberInput (types → payment) packages/modules/payment/src/providers/payment-medusa/utils/get-smallest-unit.ts:72 — BigNumberInput (context types) is exposed in payment's public surface via get-smallest-unit.getAmountFromSmallestUnit — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type BigNumberInput (types → payment-stripe) · ×2

Cross-context type BigNumberInput (types → payment-stripe) packages/modules/providers/payment-stripe/src/utils/get-smallest-unit.ts:45 — BigNumberInput (context types) is exposed in payment-stripe's public surface via get-smallest-unit.getSmallestUnit — couples the contexts.
Cross-context type BigNumberInput (types → payment-stripe) packages/modules/providers/payment-stripe/src/utils/get-smallest-unit.ts:72 — BigNumberInput (context types) is exposed in payment-stripe's public surface via get-smallest-unit.getAmountFromSmallestUnit — couples the contexts.

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

REDACTED
REDACTED

P12 · CI test-gate honesty · Test selection matches no test, and passes anyway · ×2

Test selection matches no test, and passes anyway REDACTED:184 — `yarn test -- --shard=${{ matrix.shard_index }}/4 --maxWorkers=${{ steps.cpu-cores.outputs.count }} --passWithNoTests` selects `src`, which matches no test file, and `--passWithNoTests` turns the empty run into a pass — the step is green while running nothing. Point it at the tests it is meant to run, or drop the flag.
Test selection matches no test, and passes anyway REDACTED:42 — `yarn test` selects `src`, which matches no test file, and `--passWithNoTests` turns the empty run into a pass — the step is green while running nothing. Point it at the tests it is meant to run, or drop the flag.

AC1 · Text alternatives · <canvas> without a text alternative · ×1

<canvas> without a text alternative packages/admin/dashboard/src/routes/profile/profile-detail/components/profile-mfa-section/mfa-qr-code.tsx:44 — A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.

AC2 · Forms & labels · <Textarea> field component without a label · ×1

<Textarea> field component without a label packages/admin/dashboard/src/components/data-grid/components/data-grid-textarea-modal-cell.tsx:220 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — 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.

AC3 · Page structure · Page without a main landmark · ×1

Page without a main landmark www/packages/docs-ui/src/layouts/barebone.tsx:17 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.

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

Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 2060 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.

D10 · Test Quality · Fixed-sleep synchronisation · ×1

Fixed-sleep synchronisation: should reject a replay while the first attempt is still in flight packages/modules/payment/integration-tests/__tests__/services/payment-module/index.spec.ts:1869 — This test starts work it did not wait for (`first`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 100))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.

D23 · Boundary Type-Coupling · Cross-context type AuthLoginResponse (js-sdk → dashboard) · ×1

Cross-context type AuthLoginResponse (js-sdk → dashboard) packages/admin/dashboard/src/hooks/api/auth.tsx:52 — AuthLoginResponse (context js-sdk) is exposed in dashboard's public surface via auth.useSignInWithEmailPass — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type AdminCreateShippingOption (types → dashboard) · ×1

Cross-context type AdminCreateShippingOption (types → dashboard) packages/admin/dashboard/src/hooks/api/shipping-options.tsx:64 — AdminCreateShippingOption (context types) is exposed in dashboard's public surface via shipping-options.useCreateShippingOptions — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type AdminAcceptInviteResponse (types → dashboard) · ×1

Cross-context type AdminAcceptInviteResponse (types → dashboard) packages/admin/dashboard/src/hooks/api/invites.tsx:110 — AdminAcceptInviteResponse (context types) is exposed in dashboard's public surface via invites.useAcceptInvite — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type DataTableColumnAlignment (ui → dashboard) · ×1

Cross-context type DataTableColumnAlignment (ui → dashboard) packages/admin/dashboard/src/lib/table/table-adapters.ts:81 — DataTableColumnAlignment (context ui) is exposed in dashboard's public surface via TableAdapter.getColumnAlignment — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type CreateShippingOptionsWorkflowInput (types → core-flows) · ×1

Cross-context type CreateShippingOptionsWorkflowInput (types → core-flows) packages/core/core-flows/src/fulfillment/workflows/create-shipping-options.ts:104 — CreateShippingOptionsWorkflowInput (context types) is exposed in core-flows's public surface via create-shipping-options.createShippingOptionsWorkflow — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type UpdateShippingOptionsWorkflowInput (types → core-flows) · ×1

Cross-context type UpdateShippingOptionsWorkflowInput (types → core-flows) packages/core/core-flows/src/fulfillment/workflows/update-shipping-options.ts:72 — UpdateShippingOptionsWorkflowInput (context types) is exposed in core-flows's public surface via update-shipping-options.updateShippingOptionsWorkflow — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type RegisterModuleJoinerConfig (modules-sdk → framework) · ×1

Cross-context type RegisterModuleJoinerConfig (modules-sdk → framework) packages/core/framework/src/medusa-app-loader.ts:60 — RegisterModuleJoinerConfig (context modules-sdk) is exposed in framework's public surface via MedusaAppLoader.constructor — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type AdminCreateShippingOption (types → js-sdk) · ×1

Cross-context type AdminCreateShippingOption (types → js-sdk) packages/core/js-sdk/src/admin/shipping-option.ts:35 — AdminCreateShippingOption (context types) is exposed in js-sdk's public surface via ShippingOption.create — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type RelationshipTypes (types → utils) · ×1

Cross-context type RelationshipTypes (types → utils) packages/core/utils/src/dml/relations/base.ts:28 — RelationshipTypes (context types) is exposed in utils's public surface via BaseRelationship.type — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type Filter (search → utils) · ×1

Cross-context type Filter (search → utils) packages/core/utils/src/dal/mikro-orm/mikro-orm-create-connection.ts:73 — Filter (context search) is exposed in utils's public surface via mikro-orm-create-connection.mikroOrmCreateConnection — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type SearchFacetKind (types → utils) · ×1

Cross-context type SearchFacetKind (types → utils) packages/core/utils/src/search/model/properties/base.ts:141 — SearchFacetKind (context types) is exposed in utils's public surface via RangeFacetSearchProperty.facetable — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type AdminAcceptInviteResponse (types → medusa) · ×1

Cross-context type AdminAcceptInviteResponse (types → medusa) packages/medusa/src/api/admin/invites/accept/route.ts:9 — AdminAcceptInviteResponse (context types) is exposed in medusa's public surface via route.POST — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type AdminCreateShippingOption (types → medusa) · ×1

Cross-context type AdminCreateShippingOption (types → medusa) packages/medusa/src/api/admin/shipping-options/route.ts:38 — AdminCreateShippingOption (context types) is exposed in medusa's public surface via route.POST — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type StoreCompleteCartResponse (types → medusa) · ×1

Cross-context type StoreCompleteCartResponse (types → medusa) packages/medusa/src/api/store/carts/[id]/complete/route.ts:13 — StoreCompleteCartResponse (context types) is exposed in medusa's public surface via route.POST — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type IdentifyAnalyticsEventDTO (types → analytics) · ×1

Cross-context type IdentifyAnalyticsEventDTO (types → analytics) packages/modules/analytics/src/services/analytics-service.ts:40 — IdentifyAnalyticsEventDTO (context types) is exposed in analytics's public surface via AnalyticsService.identify — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type CreateGeoZoneDTO (types → fulfillment) · ×1

Cross-context type CreateGeoZoneDTO (types → fulfillment) packages/modules/fulfillment/src/services/fulfillment-module-service.ts:511 — CreateGeoZoneDTO (context types) is exposed in fulfillment's public surface via FulfillmentModuleService.createGeoZones — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type UpdateGeoZoneDTO (types → fulfillment) · ×1

Cross-context type UpdateGeoZoneDTO (types → fulfillment) packages/modules/fulfillment/src/services/fulfillment-module-service.ts:1719 — UpdateGeoZoneDTO (context types) is exposed in fulfillment's public surface via FulfillmentModuleService.updateGeoZones — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type LinkMigrationsPlannerAction (types → link-modules) · ×1

Cross-context type LinkMigrationsPlannerAction (types → link-modules) packages/modules/link-modules/src/migration/index.ts:511 — LinkMigrationsPlannerAction (context types) is exposed in link-modules's public surface via MigrationsExecutionPlanner.executePlan — couples the contexts.

D23 · Boundary Type-Coupling · Cross-context type SearchFacetKind (types → search) · ×1

Cross-context type SearchFacetKind (types → search) packages/modules/search/src/utils/index.ts:67 — SearchFacetKind (context types) is exposed in search's public surface via index.isFacetable — couples the contexts.

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

REDACTED

D30 · Dependency Vulnerabilities · Medium vulnerability · ×1

REDACTED

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

REDACTED

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

REDACTED

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

REDACTED

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

REDACTED

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

Workspace package's tests never run by CI REDACTED:1 — `packages/cli/oas/medusa-oas-cli` is a workspace package with 44 test(s) in 2 file(s) (e.g. `packages/cli/oas/medusa-oas-cli/src/__tests__/command-docs.test.ts`, `packages/cli/oas/medusa-oas-cli/src/__tests__/command-oas.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.

P2 · Observability · No structured logging · ×1

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

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 15, cognitive 38) · ×1

Complex function (anonymous) (cyclomatic 15, cognitive 38) packages/design-system/ui/src/blocks/data-table/data-table.stories.tsx:94 — (anonymous) has cyclomatic complexity 15 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

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

Complex function (anonymous) (cyclomatic 12, cognitive 15) packages/cli/oas/medusa-oas-cli/src/__tests__/command-oas.test.ts:45 — (anonymous) has cyclomatic complexity 12 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

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

The declared test suite includes a file that cannot be loaded integration-tests/environment-helpers/start-server-with-environment.js:2 — This repository declares test tooling, and the ✓ above records that declaration — but integration-tests/environment-helpers/start-server-with-environment.js 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 (~30 LoC) · ×1

Dead file (~30 LoC) define_jest_config.js — no import path from any entry point (235 application, 0 tooling, 1545 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 '@swc/helpers' · ×1

Unused dependency '@swc/helpers' — 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 'axios-mock-adapter' · ×1

Unused dependency 'axios-mock-adapter' — 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 'esbuild' · ×1

Unused dependency 'esbuild' — 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 — 210 finding(s)

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

Mock-dominated test: closes mobile sidebar when active and mobile www/packages/docs-ui/src/components/Sidebar/Item/Link/__tests__/index.test.tsx:293 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: does not close mobile sidebar when not active www/packages/docs-ui/src/components/Sidebar/Item/Link/__tests__/index.test.tsx:307 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: doesn't scroll into view when disableActiveTransition is true www/packages/docs-ui/src/components/Sidebar/Item/Link/__tests__/index.test.tsx:345 — This test sets up 4 test doubles (for example `a double assigned in a shared setup`) 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: calls setSelected with empty array when clear button is clicked www/packages/docs-ui/src/components/Select/Input/__tests__/index.test.tsx:247 — This test sets up 3 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.
Mock-dominated test: stops propagation when clear button is clicked www/packages/docs-ui/src/components/Select/Input/__tests__/index.test.tsx:265 — 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.
Mock-dominated test: passes correct options to useSelect www/packages/docs-ui/src/components/Select/Input/__tests__/index.test.tsx:303 — This test sets up 6 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.
Mock-dominated test: calls handleChange when option is clicked www/packages/docs-ui/src/components/Select/Dropdown/__tests__/index.test.tsx:314 — This test sets up 3 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.
Mock-dominated test: calls handleChange with wasSelected=true when clicking selected option www/packages/docs-ui/src/components/Select/Dropdown/__tests__/index.test.tsx:333 — This test sets up 3 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.
Mock-dominated test: closes dropdown when option is clicked in single mode www/packages/docs-ui/src/components/Select/Dropdown/__tests__/index.test.tsx:352 — This test sets up 3 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.
Mock-dominated test: does not close dropdown when option is clicked in multiple mode www/packages/docs-ui/src/components/Select/Dropdown/__tests__/index.test.tsx:372 — This test sets up 3 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.
Mock-dominated test: calls setSelectedValues when all is selected and option is clicked www/packages/docs-ui/src/components/Select/Dropdown/__tests__/index.test.tsx:450 — 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.
Mock-dominated test: supports function ref www/packages/docs-ui/src/components/Select/Dropdown/__tests__/index.test.tsx:472 — This test sets up 3 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.
Mock-dominated test: passes correct options to useSelect www/packages/docs-ui/src/components/Select/Badge/__tests__/index.test.tsx:220 — This test sets up 6 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.
Mock-dominated test: calls sendEvent when hit link is clicked www/packages/docs-ui/src/components/Search/Hits/__tests__/index.test.tsx:229 — This test sets up 3 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.
Mock-dominated test: closes search modal for internal links www/packages/docs-ui/src/components/Search/Hits/__tests__/index.test.tsx:246 — This test sets up 5 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.
Mock-dominated test: calls setNoResults when hits are empty www/packages/docs-ui/src/components/Search/Hits/__tests__/index.test.tsx:267 — 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.
Mock-dominated test: calls onClose callback when collapsed www/packages/docs-ui/src/components/Details/__tests__/index.test.tsx:334 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: calls changeSelectedTab when tab is clicked www/packages/docs-ui/src/components/CodeTabs/__tests__/index.test.tsx:363 — This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: does not scroll when not in browser www/apps/api-reference/components/Tags/Section/__tests__/index.test.tsx:625 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: updates the URL via history.replaceState when in view and path does not match www/apps/api-reference/components/Tags/Section/__tests__/index.test.tsx:658 — This test sets up 3 test doubles (for example `vi.spyOn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: updates URL and active path when in view and activePath is different www/apps/api-reference/components/Tags/Section/Schema/__tests__/index.test.tsx:369 — This test sets up 4 test doubles (for example `vi.spyOn`) 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: does not update when activePath already matches schemaPath www/apps/api-reference/components/Tags/Section/Schema/__tests__/index.test.tsx:392 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: updates when element is in viewport even if not in view www/apps/api-reference/components/Tags/Section/Schema/__tests__/index.test.tsx:410 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: sets active path when in view and activePath is different www/apps/api-reference/components/Tags/Operation/__tests__/index.test.tsx:277 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: updates the highlight and URL when scrolled into view www/apps/api-reference/components/Tags/Operation/__tests__/index.test.tsx:302 — This test sets up 4 test doubles (for example `vi.spyOn`) 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.
+ 52 more in this group — see findings.md.

D12 · Dependency Hygiene · Deprecated · ×36

Deprecated: @humanwhocodes/config-array REDACTED:2389 — @humanwhocodes/config-array 0.13.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/config-array instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/object-schema REDACTED:2414 — @humanwhocodes/object-schema 2.0.3 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/object-schema instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @oclif/config REDACTED:4655 — @oclif/config 1.18.16 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @oclif/config REDACTED:4669 — @oclif/config 1.18.2 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @oclif/errors REDACTED:4697 — @oclif/errors 1.3.5 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @oclif/help REDACTED:4723 — @oclif/help 1.0.15 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @oclif/screen REDACTED:4778 — @oclif/screen 1.0.4 is resolved in REDACTED and is marked deprecated by its publisher: "Deprecated in favor of @oclif/core". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @opentelemetry/propagator-jaeger REDACTED:5134 — @opentelemetry/propagator-jaeger 2.9.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. See https://github.com/open-telemetry/opentelemetry-js/pull/7077". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @opentelemetry/sdk-trace-base REDACTED:5220 — @opentelemetry/sdk-trace-base 2.9.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use @opentelemetry/sdk-trace package". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @ungap/structured-clone REDACTED:9468 — @ungap/structured-clone 1.3.0 is resolved in REDACTED and is marked deprecated by its publisher: "Potential CWE-502 - Update to 1.3.1 or higher". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: cli-ux REDACTED:11124 — cli-ux 5.6.7 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:14193 — glob 10.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: inflight REDACTED:14799 — inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: rimraf REDACTED:20352 — rimraf 3.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: uuid REDACTED:23058 — uuid 8.3.2 is resolved in REDACTED and is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @readme/json-schema-ref-parser REDACTED:6629 — @readme/json-schema-ref-parser 1.2.1 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer maintained. Please use `@apidevtools/json-schema-ref-parser` instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @ungap/structured-clone REDACTED:8437 — @ungap/structured-clone 1.2.0 is resolved in REDACTED and is marked deprecated by its publisher: "Potential CWE-502 - Update to 1.3.1 or higher". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:13106 — glob 10.3.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: lodash.isequal REDACTED:14745 — lodash.isequal 4.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "This package is deprecated. Use require('node:util').isDeepStrictEqual instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: mkdirp REDACTED:15754 — mkdirp 0.3.0 is resolved in REDACTED and is marked deprecated by its publisher: "Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: node-domexception REDACTED:16023 — node-domexception 1.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native DOMException instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: tsconfck REDACTED:19574 — tsconfck 3.1.6 is resolved in REDACTED and is marked deprecated by its publisher: "unmaintained". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: whatwg-encoding REDACTED:20717 — whatwg-encoding 3.1.1 is resolved in REDACTED and is marked deprecated by its publisher: "Use @exodus/bytes instead for a more spec-conformant and faster implementation". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/config-array REDACTED:797 — @humanwhocodes/config-array 0.13.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/config-array instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @octokit/webhooks-types REDACTED:1560 — @octokit/webhooks-types 7.6.1 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
+ 11 more in this group — see findings.md.

X10 · Duplicated predicate · Duplicated predicate · ×25

Duplicated predicate packages/core/core-flows/src/draft-order/workflows/update-draft-order.ts:329 — `!!input.locale && input.locale !== order.locale` appears character-identically in 2 files — packages/core/core-flows/src/draft-order/workflows/update-draft-order.ts, packages/core/core-flows/src/order/workflows/update-order.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/modules/workflow-engine-inmemory/src/utils/workflow-orchestrator-storage.ts:511 — `!!latestTransactionCancelledAt && currentTransactionCancelledAt == null` appears character-identically in 2 files — packages/modules/workflow-engine-inmemory/src/utils/workflow-orchestrator-storage.ts, packages/modules/workflow-engine-redis/src/utils/workflow-orchestrator-storage.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/admin/dashboard/src/components/common/chip-group/chip-group.tsx:41 — `!!onClearAll && Children.count(children) > 0` appears character-identically in 2 files — packages/admin/dashboard/src/components/common/chip-group/chip-group.tsx, packages/plugins/loyalty/src/admin/components/chip-group.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/admin/dashboard/src/routes/orders/order-balance-settlement/components/order-balance-settlement-form/order-balance-settlement-form.tsx:281 — `!!payment.canceled_at || totalRefunded >= payment.amount` appears character-identically in 2 files — packages/admin/dashboard/src/routes/orders/order-balance-settlement/components/order-balance-settlement-form/order-balance-settlement-form.tsx, packages/admin/dashboard/src/routes/orders/order-create-refund/components/create-refund-form/create-refund-form.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/cli/create-medusa-app/src/utils/claude-code-plugin.ts:20 — `!!process.env.CLAUDE_CODE || fs.existsSync(CLAUDE_DIR)` appears character-identically in 2 files — packages/cli/create-medusa-app/src/utils/claude-code-plugin.ts, packages/medusa/src/utils/claude-code-plugin.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/admin/dashboard/src/routes/products/product-create/product-create.tsx:47 — `!!store && !isStorePending && !!regions && !isRegionsPending && !!sales_channel && !isSalesChannelPending && !!price_preferences && !isPrice…` appears character-identically in 2 files — packages/admin/dashboard/src/routes/products/product-create/product-create.tsx, packages/plugins/loyalty/src/admin/routes/gift-cards/gift-card-products/@create/page.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/core/core-flows/src/rbac/workflows/create-rbac-role-policies.ts:53 — `!!validationData?.actor_id && !!validationData?.policy_ids?.length` appears character-identically in 3 files — packages/core/core-flows/src/rbac/workflows/create-rbac-role-policies.ts, packages/core/core-flows/src/rbac/workflows/create-rbac-roles.ts, packages/core/core-flows/src/rbac/workflows/update-rbac-roles.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/modules/workflow-engine-inmemory/src/utils/workflow-orchestrator-storage.ts:258 — `!(isNotStarted || isFinished || isWaitingToCompensate) && !shouldStoreCurrentSteps && !asyncVersion` appears character-identically in 2 files — packages/modules/workflow-engine-inmemory/src/utils/workflow-orchestrator-storage.ts, packages/modules/workflow-engine-redis/src/utils/workflow-orchestrator-storage.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/core/orchestration/src/workflow/global-workflow.ts:26 — `!Array.isArray(modulesLoaded) && modulesLoaded` appears character-identically in 2 files — packages/core/orchestration/src/workflow/global-workflow.ts, packages/core/orchestration/src/workflow/local-workflow.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/modules/auth/src/services/auth-module.ts:988 — `!Number.isInteger(ttlSeconds) || ttlSeconds < 1` appears character-identically in 2 files — packages/modules/auth/src/services/auth-module.ts, packages/modules/auth/src/utils/verification-token.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 www/apps/api-reference/scripts/upload-specs-to-r2.mjs:49 — `!accountId || !accessKeyId || !secretAccessKey` appears character-identically in 3 files — www/apps/api-reference/scripts/upload-specs-to-r2.mjs, www/apps/resources/scripts/upload-references-to-r2.mjs, www/apps/ui/scripts/upload-specs-to-r2.mjs. 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/admin/dashboard/src/components/inputs/chip-input/chip-input.tsx:65 — `!allowDuplicates && chips.includes(cleanValue)` appears character-identically in 2 files — packages/admin/dashboard/src/components/inputs/chip-input/chip-input.tsx, packages/plugins/loyalty/src/admin/components/chip-input.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/eslint-plugin/src/rules/middleware-must-call-next/rule.ts:134 — `!arg || arg.type !== AST_NODE_TYPES.ObjectExpression` appears character-identically in 4 files — packages/eslint-plugin/src/rules/middleware-must-call-next/rule.ts, packages/eslint-plugin/src/rules/no-duplicate-step-id-in-workflow/rule.ts, packages/eslint-plugin/src/rules/no-trailing-slash-in-route-matcher/rule.ts, packages/eslint-plugin/src/util/ast.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/admin/dashboard/src/components/data-grid/hooks/use-data-grid-error-highlighting.tsx:81 — `!columnsWithErrors.has(index) && index !== 0` appears character-identically in 2 files — packages/admin/dashboard/src/components/data-grid/hooks/use-data-grid-error-highlighting.tsx, packages/plugins/loyalty/src/admin/components/data-grid/hooks/use-data-grid-error-highlighting.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/core/core-flows/src/product/steps/batch-link-products-collection.ts:25 — `!data.add?.length && !data.remove?.length` appears character-identically in 2 files — packages/core/core-flows/src/product/steps/batch-link-products-collection.ts, packages/core/core-flows/src/product/steps/batch-link-products-in-category.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/admin/dashboard/src/components/data-grid/components/data-grid-root.tsx:154 — `!disableInteractions && internalTrapActive` appears character-identically in 2 files — packages/admin/dashboard/src/components/data-grid/components/data-grid-root.tsx, packages/plugins/loyalty/src/admin/components/data-grid/components/data-grid-root.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/admin/dashboard/src/components/common/file-upload/file-upload.tsx:62 — `!dropZoneRef.current || dropZoneRef.current.contains(event.relatedTarget as Node)` appears character-identically in 2 files — packages/admin/dashboard/src/components/common/file-upload/file-upload.tsx, packages/plugins/loyalty/src/admin/components/file-upload.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/modules/providers/search-postgres/src/utils/plan.ts:150 — `!field.dimensions || field.dimensions < 1` appears character-identically in 2 files — packages/modules/providers/search-postgres/src/utils/plan.ts, packages/modules/search/src/providers/search-medusa/utils/plan.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/core/utils/src/search/definition-helpers.ts:128 — `!filters || !Object.keys(filters).length` appears character-identically in 3 files — packages/core/utils/src/search/definition-helpers.ts, packages/modules/search/src/providers/search-medusa/utils/filters.ts, packages/modules/search/src/services/search-module-service.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/admin/dashboard/src/routes/refund-reasons/refund-reason-create/components/refund-reason-create-form/refund-reason-create-form.tsx:96 — `!form.getFieldState("code").isTouched || !form.getValues("code")` appears character-identically in 2 files — packages/admin/dashboard/src/routes/refund-reasons/refund-reason-create/components/refund-reason-create-form/refund-reason-create-form.tsx, packages/admin/dashboard/src/routes/shipping-option-types/shipping-option-type-create/components/create-shipping-option-type-form/create-shipping-option-type-form.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/cli/http-types-generator/src/core/schema-extractor.ts:262 — `!initializer || !ts.isCallExpression(initializer)` appears character-identically in 2 files — packages/cli/http-types-generator/src/core/schema-extractor.ts, packages/cli/http-types-generator/src/utils/ts-helpers.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/admin/dashboard/src/components/data-grid/hooks/use-data-grid-cell.tsx:143 — `!inputRef.current || !validateKeyStroke(e.key) || !showOverlay` appears character-identically in 2 files — packages/admin/dashboard/src/components/data-grid/hooks/use-data-grid-cell.tsx, packages/plugins/loyalty/src/admin/components/data-grid/hooks/use-data-grid-cell.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/modules/workflow-engine-inmemory/src/utils/workflow-orchestrator-storage.ts:493 — `!isInitialCheckpoint && !isPresent(latestUpdatedFlow) && !data.flow.metadata?.parentStepIdempotencyKey` appears character-identically in 2 files — packages/modules/workflow-engine-inmemory/src/utils/workflow-orchestrator-storage.ts, packages/modules/workflow-engine-redis/src/utils/workflow-orchestrator-storage.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/admin/dashboard/src/routes/locations/location-service-zone-create/location-service-zone-create.tsx:26 — `!isPending && !isFetching && !fulfillmentSet` appears character-identically in 2 files — packages/admin/dashboard/src/routes/locations/location-service-zone-create/location-service-zone-create.tsx, packages/admin/dashboard/src/routes/locations/location-service-zone-shipping-option-create/location-service-zone-shipping-option-create.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 www/packages/docs-ui/src/components/Sidebar/Item/Link/index.tsx:106 — `!item.hideChildren && (item.children?.length || 0) > 0` appears character-identically in 2 files — www/packages/docs-ui/src/components/Sidebar/Item/Link/index.tsx, www/packages/docs-ui/src/components/Sidebar/Item/SubCategory/index.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.

D12 · Dependency Hygiene · Outdated (npm) · ×23

Outdated (npm): @inquirer/checkbox packages/medusa/package.json:59 — @inquirer/checkbox is pinned at 2.5.0; registry.npmjs.org publishes 5.2.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @inquirer/confirm packages/medusa/package.json:60 — @inquirer/confirm is pinned at 2.0.17; registry.npmjs.org publishes 6.3.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @inquirer/input packages/medusa/package.json:61 — @inquirer/input is pinned at 2.3.0; registry.npmjs.org publishes 5.1.8 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @linear/sdk www/utils/packages/scripts/package.json:24 — @linear/sdk is pinned at 52.1.0; registry.npmjs.org publishes 99.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @readme/openapi-parser REDACTED:41 — @readme/openapi-parser is pinned at 3.0.1; registry.npmjs.org publishes 10.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): awilix integration-tests/package.json:24 — awilix is pinned at 8.0.1; registry.npmjs.org publishes 13.0.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): boxen packages/cli/create-medusa-app/package.json:19 — boxen is pinned at 5.1.2; registry.npmjs.org publishes 9.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): commander packages/cli/create-medusa-app/package.json:21 — commander is pinned at 11.1.0; registry.npmjs.org publishes 15.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): configstore REDACTED:72 — configstore is pinned at 5.0.1; registry.npmjs.org publishes 8.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): connect-redis packages/core/framework/package.json:98 — connect-redis is pinned at 5.2.0; registry.npmjs.org publishes 10.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): dotenv-expand packages/core/utils/package.json:48 — dotenv-expand is pinned at 11.0.7; registry.npmjs.org publishes 1000.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): execa packages/cli/medusa-cli/package.json:49 — execa is pinned at 5.1.1; registry.npmjs.org publishes 10.2.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): framer-motion www/packages/docs-ui/package.json:91 — framer-motion is pinned at 11.11.9; registry.npmjs.org publishes 14.6.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): hosted-git-info packages/cli/medusa-cli/package.json:54 — hosted-git-info is pinned at 4.1.0; registry.npmjs.org publishes 10.1.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): i18next packages/admin/dashboard/package.json:89 — i18next is pinned at 23.7.11; registry.npmjs.org publishes 26.5.11 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): inquirer packages/cli/create-medusa-app/package.json:22 — inquirer is pinned at 8.2.7; registry.npmjs.org publishes 14.2.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): jsdom REDACTED:92 — jsdom is pinned at 27.1.0; registry.npmjs.org publishes 30.1.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): openai www/utils/packages/docs-generator/package.json:30 — openai is pinned at 4.104.0; registry.npmjs.org publishes 7.45.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): ora packages/cli/create-medusa-app/package.json:25 — ora is pinned at 5.4.1; registry.npmjs.org publishes 9.4.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-i18next packages/admin/dashboard/package.json:104 — react-i18next is pinned at 13.5.0; registry.npmjs.org publishes 17.1.9 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): stripe packages/modules/payment/package.json:53 — stripe is pinned at 19.1.0; registry.npmjs.org publishes 23.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): tsconfig www/apps/book/package.json:59 — tsconfig is pinned at 0.0.0-use.local; registry.npmjs.org publishes 7.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): uuid REDACTED:122 — uuid is pinned at 11.1.1; registry.npmjs.org publishes 14.0.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.

AX6 · Interface segregation · Fat interface · ×18

Fat interface: Logger (16 required operations) packages/core/types/src/logger/index.ts:1 — `Logger` declares 16 required operations: `panic`, `shouldLog`, `setLogLevel`, `unsetLogLevel`, `activity`, `progress`, `error`, `failure`, `success`, `silly`, `debug`, `verbose`, `http`, `info`, `warn`, `log`. 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.
Fat interface: ICartModuleService (84 required operations) packages/core/types/src/cart/service.ts:50 — `ICartModuleService` declares 84 required operations: `retrieveCart`, `listCarts`, `listAndCountCarts`, `createCarts`, `createCarts`, `updateCarts`, `updateCarts`, `updateCarts`, `deleteCarts`, `deleteCarts`, `listAddresses`, `createAddresses`, `createAddresses`, `updateAddresses`, `updateAddresses`, `deleteAddresses`, `deleteAddresses`, `retrieveLineItem`, `listLineItems`, `addLineItems`, `addLineItems`, `addLineItems`, `updateLineItems`, `updateLineItems`, `updateLineItems`, `updateLineItems`, `listShippingMethods`, `addShippingMethods`, `addShippingMethods`, `addShippingMethods`, `updateShippingMethods`, `updateShippingMethods`, `listLineItemAdjustments`, `addLineItemAdjustments`, `addLineItemAdjustments`, `addLineItemAdjustments`, `setLineItemAdjustments`, `listShippingMethodAdjustments`, `addShippingMethodAdjustments`, `addShippingMethodAdjustments`, and 44 more. 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. Those 84 declarations carry 55 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 55 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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.
Fat interface: ICustomerModuleService (41 required operations) packages/core/types/src/customer/service.ts:28 — `ICustomerModuleService` declares 41 required operations: `retrieveCustomer`, `createCustomers`, `createCustomers`, `updateCustomers`, `updateCustomers`, `updateCustomers`, `deleteCustomers`, `deleteCustomers`, `deleteCustomers`, `createCustomerGroups`, `createCustomerGroups`, `retrieveCustomerGroup`, `updateCustomerGroups`, `updateCustomerGroups`, `updateCustomerGroups`, `deleteCustomerGroups`, `deleteCustomerGroups`, `deleteCustomerGroups`, `addCustomerToGroup`, `addCustomerToGroup`, `removeCustomerFromGroup`, `removeCustomerFromGroup`, `createCustomerAddresses`, `createCustomerAddresses`, `updateCustomerAddresses`, `updateCustomerAddresses`, `updateCustomerAddresses`, `deleteCustomerAddresses`, `deleteCustomerAddresses`, `deleteCustomerAddresses`, `listCustomerAddresses`, `listAndCountCustomerAddresses`, `listCustomerGroupCustomers`, `listCustomers`, `listAndCountCustomers`, `listCustomerGroups`, `listAndCountCustomerGroups`, `softDeleteCustomers`, `restoreCustomers`, `softDeleteCustomerGroups`, and 1 more. 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. Those 41 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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.
Fat interface: IPaymentModuleService (52 required operations) packages/core/types/src/payment/service.ts:46 — `IPaymentModuleService` declares 52 required operations: `createPaymentCollections`, `createPaymentCollections`, `retrievePaymentCollection`, `listPaymentCollections`, `listAndCountPaymentCollections`, `updatePaymentCollections`, `updatePaymentCollections`, `upsertPaymentCollections`, `upsertPaymentCollections`, `deletePaymentCollections`, `deletePaymentCollections`, `softDeletePaymentCollections`, `restorePaymentCollections`, `completePaymentCollections`, `completePaymentCollections`, `retrievePaymentSession`, `retrievePayment`, `createPaymentSession`, `updatePaymentSession`, `deletePaymentSession`, `authorizePaymentSession`, `listPaymentSessions`, `listPayments`, `updatePayment`, `capturePayment`, `refundPayment`, `cancelPayment`, `listPaymentProviders`, `listAndCountPaymentProviders`, `createAccountHolder`, `updateAccountHolder`, `deleteAccountHolder`, `listPaymentMethods`, `listAndCountPaymentMethods`, `createPaymentMethods`, `createPaymentMethods`, `deletePaymentMethods`, `deletePaymentMethods`, `listCaptures`, `deleteCaptures`, and 12 more. 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. Those 52 declarations carry 42 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 42 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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.
Fat interface: IOrderModuleService (209 required operations) packages/core/types/src/order/service.ts:102 — `IOrderModuleService` declares 209 required operations: `retrieveOrder`, `listOrders`, `listAndCountOrders`, `retrieveReturn`, `listReturns`, `listAndCountReturns`, `retrieveOrderClaim`, `listOrderClaims`, `listAndCountOrderClaims`, `retrieveOrderExchange`, `listOrderExchanges`, `listAndCountOrderExchanges`, `createOrders`, `createOrders`, `updateOrders`, `updateOrders`, `updateOrders`, `deleteOrders`, `deleteOrders`, `softDeleteOrders`, `restoreOrders`, `listOrderAddresses`, `createOrderAddresses`, `createOrderAddresses`, `updateOrderAddresses`, `updateOrderAddresses`, `deleteOrderAddresses`, `deleteOrderAddresses`, `retrieveOrderLineItem`, `listOrderLineItems`, `createOrderLineItems`, `createOrderLineItems`, `createOrderLineItems`, `updateOrderLineItems`, `updateOrderLineItems`, `updateOrderLineItems`, `deleteOrderLineItems`, `deleteOrderLineItems`, `deleteOrderLineItems`, `updateOrderItem`, and 169 more. 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. Those 209 declarations carry 136 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 136 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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.
Fat interface: IRegionModuleService (16 required operations) packages/core/types/src/region/service.ts:16 — `IRegionModuleService` declares 16 required operations under just 12 distinct name(s): `createRegions`, `createRegions`, `upsertRegions`, `upsertRegions`, `updateRegions`, `updateRegions`, `deleteRegions`, `deleteRegions`, `retrieveRegion`, `listRegions`, `listAndCountRegions`, `retrieveCountry`, `listCountries`, `listAndCountCountries`, `softDeleteRegions`, `restoreRegions`. 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. That is an OVERLOAD SET, not 16 separate responsibilities: a caller binds to 12 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 16 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
Fat interface: IFulfillmentModuleService (99 required operations) packages/core/types/src/fulfillment/service.ts:53 — `IFulfillmentModuleService` declares 99 required operations: `retrieveFulfillmentSet`, `listFulfillmentSets`, `listAndCountFulfillmentSets`, `createFulfillmentSets`, `createFulfillmentSets`, `updateFulfillmentSets`, `updateFulfillmentSets`, `deleteFulfillmentSets`, `deleteFulfillmentSets`, `softDeleteFulfillmentSets`, `restoreFulfillmentSets`, `retrieveServiceZone`, `listServiceZones`, `listAndCountServiceZones`, `createServiceZones`, `createServiceZones`, `updateServiceZones`, `updateServiceZones`, `upsertServiceZones`, `upsertServiceZones`, `deleteServiceZones`, `deleteServiceZones`, `softDeleteServiceZones`, `restoreServiceZones`, `retrieveGeoZone`, `listGeoZones`, `listAndCountGeoZones`, `createGeoZones`, `createGeoZones`, `updateGeoZones`, `updateGeoZones`, `deleteGeoZones`, `deleteGeoZones`, `softDeleteGeoZones`, `restoreGeoZones`, `retrieveShippingOption`, `listShippingOptions`, `listShippingOptionsForContext`, `listAndCountShippingOptions`, `createShippingOptions`, and 59 more. 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. Those 99 declarations carry 74 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 74 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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.
Fat interface: IProductModuleService (102 required operations) packages/core/types/src/product/service.ts:53 — `IProductModuleService` declares 102 required operations: `retrieveProduct`, `listProducts`, `listAndCountProducts`, `createProducts`, `createProducts`, `upsertProducts`, `upsertProducts`, `updateProducts`, `updateProducts`, `deleteProducts`, `softDeleteProducts`, `restoreProducts`, `retrieveProductTag`, `listProductTags`, `listAndCountProductTags`, `createProductTags`, `createProductTags`, `upsertProductTags`, `upsertProductTags`, `updateProductTags`, `updateProductTags`, `deleteProductTags`, `softDeleteProductTags`, `restoreProductTags`, `retrieveProductType`, `listProductTypes`, `listAndCountProductTypes`, `createProductTypes`, `createProductTypes`, `upsertProductTypes`, `upsertProductTypes`, `updateProductTypes`, `updateProductTypes`, `deleteProductTypes`, `softDeleteProductTypes`, `restoreProductTypes`, `retrieveProductOption`, `listProductOptions`, `listAndCountProductOptions`, `createProductOptions`, and 62 more. 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. Those 102 declarations carry 76 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 76 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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.
Fat interface: IPromotionModuleService (35 required operations) packages/core/types/src/promotion/service.ts:31 — `IPromotionModuleService` declares 35 required operations: `registerUsage`, `revertUsage`, `computeActions`, `createPromotions`, `createPromotions`, `updatePromotions`, `updatePromotions`, `listPromotions`, `listAndCountPromotions`, `retrievePromotion`, `deletePromotions`, `deletePromotions`, `softDeletePromotions`, `restorePromotions`, `addPromotionRules`, `addPromotionTargetRules`, `addPromotionBuyRules`, `removePromotionRules`, `removePromotionTargetRules`, `removePromotionBuyRules`, `createCampaigns`, `createCampaigns`, `updateCampaigns`, `updateCampaigns`, `listPromotionRules`, `updatePromotionRules`, `listCampaigns`, `listAndCountCampaigns`, `retrieveCampaign`, `deleteCampaigns`, `deleteCampaigns`, `softDeleteCampaigns`, `restoreCampaigns`, `addPromotionsToCampaign`, `removePromotionsFromCampaign`. 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. Those 35 declarations carry 29 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 29 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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.
Fat interface: IPricingModuleService (51 required operations) packages/core/types/src/pricing/service.ts:43 — `IPricingModuleService` declares 51 required operations: `calculatePrices`, `retrievePriceSet`, `listPriceSets`, `listAndCountPriceSets`, `createPriceSets`, `createPriceSets`, `upsertPriceSets`, `upsertPriceSets`, `updatePriceSets`, `updatePriceSets`, `deletePriceSets`, `addPrices`, `addPrices`, `listPrices`, `softDeletePrices`, `restorePrices`, `listAndCountPrices`, `retrievePriceRule`, `listPriceRules`, `listAndCountPriceRules`, `createPriceRules`, `updatePriceRules`, `deletePriceRules`, `retrievePriceList`, `listPriceLists`, `listAndCountPriceLists`, `createPriceLists`, `updatePriceLists`, `deletePriceLists`, `softDeletePriceLists`, `restorePriceLists`, `retrievePriceListRule`, `listPriceListRules`, `listAndCountPriceListRules`, `deletePriceListRules`, `addPriceListPrices`, `updatePriceListPrices`, `setPriceListRules`, `removePriceListRules`, `removePrices`, and 11 more. 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. Those 51 declarations carry 44 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 44 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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.
Fat interface: IInventoryService (42 required operations) packages/core/types/src/inventory/service.ts:27 — `IInventoryService` declares 42 required operations: `listInventoryItems`, `listAndCountInventoryItems`, `listReservationItems`, `listAndCountReservationItems`, `listInventoryLevels`, `listAndCountInventoryLevels`, `retrieveInventoryItem`, `retrieveInventoryLevelByItemAndLocation`, `retrieveInventoryLevel`, `retrieveReservationItem`, `createReservationItems`, `createReservationItems`, `createInventoryItems`, `createInventoryItems`, `createInventoryLevels`, `createInventoryLevels`, `updateInventoryLevels`, `updateInventoryLevels`, `updateInventoryItems`, `updateInventoryItems`, `updateReservationItems`, `updateReservationItems`, `deleteReservationItemsByLineItem`, `restoreReservationItemsByLineItem`, `deleteReservationItems`, `softDeleteReservationItems`, `restoreReservationItems`, `deleteInventoryItems`, `softDeleteInventoryItems`, `restoreInventoryItems`, `deleteInventoryItemLevelByLocationId`, `deleteReservationItemByLocationId`, `deleteInventoryLevel`, `deleteInventoryLevels`, `softDeleteInventoryLevels`, `restoreInventoryLevels`, `adjustInventory`, `adjustInventory`, `confirmInventory`, `retrieveAvailableQuantity`, and 2 more. 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. Those 42 declarations carry 35 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 35 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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.
Fat interface: IRbacModuleService (41 required operations) packages/core/types/src/rbac/service.ts:26 — `IRbacModuleService` declares 41 required operations: `createRbacRoles`, `createRbacRoles`, `updateRbacRoles`, `updateRbacRoles`, `deleteRbacRoles`, `retrieveRbacRole`, `listRbacRoles`, `listAndCountRbacRoles`, `createRbacPolicies`, `createRbacPolicies`, `updateRbacPolicies`, `updateRbacPolicies`, `deleteRbacPolicies`, `retrieveRbacPolicy`, `listRbacPolicies`, `listAndCountRbacPolicies`, `createRbacRolePolicies`, `createRbacRolePolicies`, `updateRbacRolePolicies`, `updateRbacRolePolicies`, `deleteRbacRolePolicies`, `retrieveRbacRolePolicy`, `listRbacRolePolicies`, `listAndCountRbacRolePolicies`, `createRbacRoleParents`, `createRbacRoleParents`, `updateRbacRoleParents`, `updateRbacRoleParents`, `deleteRbacRoleParents`, `retrieveRbacRoleParent`, `listRbacRoleParents`, `listAndCountRbacRoleParents`, `listPoliciesForRole`, `softDeleteRbacRoles`, `restoreRbacRoles`, `softDeleteRbacPolicies`, `restoreRbacPolicies`, `softDeleteRbacRolePolicies`, `restoreRbacRolePolicies`, `softDeleteRbacRoleParents`, and 1 more. 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. Those 41 declarations carry 33 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 33 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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.
Fat interface: ISettingsModuleService (47 required operations) packages/core/types/src/settings/service.ts:28 — `ISettingsModuleService` declares 47 required operations: `retrieveViewConfiguration`, `listViewConfigurations`, `listAndCountViewConfigurations`, `createViewConfigurations`, `createViewConfigurations`, `updateViewConfigurations`, `updateViewConfigurations`, `deleteViewConfigurations`, `retrieveUserPreference`, `listUserPreferences`, `listAndCountUserPreferences`, `createUserPreferences`, `createUserPreferences`, `updateUserPreferences`, `getUserPreference`, `setUserPreference`, `deleteUserPreferences`, `getActiveViewConfiguration`, `setActiveViewConfiguration`, `getSystemDefaultViewConfiguration`, `clearActiveViewConfiguration`, `retrieveLayoutConfiguration`, `listLayoutConfigurations`, `listAndCountLayoutConfigurations`, `createLayoutConfigurations`, `createLayoutConfigurations`, `deleteLayoutConfigurations`, `getSystemDefaultLayoutConfiguration`, `setLayoutConfiguration`, `setSystemDefaultLayoutConfiguration`, `clearLayoutConfiguration`, `getActiveLayoutScope`, `setActiveLayoutScope`, `retrievePropertyLabel`, `listPropertyLabels`, `listAndCountPropertyLabels`, `createPropertyLabels`, `createPropertyLabels`, `updatePropertyLabels`, `updatePropertyLabels`, and 7 more. 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. Those 47 declarations carry 40 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 40 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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.
Fat interface: ITaxModuleService (33 required operations) packages/core/types/src/tax/service.ts:33 — `ITaxModuleService` declares 33 required operations: `retrieveTaxRate`, `listTaxRates`, `listAndCountTaxRates`, `createTaxRates`, `createTaxRates`, `updateTaxRates`, `updateTaxRates`, `updateTaxRates`, `upsertTaxRates`, `upsertTaxRates`, `deleteTaxRates`, `deleteTaxRates`, `restoreTaxRates`, `createTaxRegions`, `createTaxRegions`, `updateTaxRegions`, `updateTaxRegions`, `deleteTaxRegions`, `deleteTaxRegions`, `listTaxRegions`, `createTaxRateRules`, `listTaxProviders`, `createTaxRateRules`, `deleteTaxRateRules`, `deleteTaxRateRules`, `listTaxRateRules`, `getTaxLines`, `softDeleteTaxRates`, `softDeleteTaxRegions`, `restoreTaxRegions`, `softDeleteTaxRateRules`, `restoreTaxRateRules`, `getProvider`. 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. Those 33 declarations carry 23 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 23 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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.
Fat interface: ITranslationModuleService (31 required operations) packages/core/types/src/translation/service.ts:32 — `ITranslationModuleService` declares 31 required operations: `retrieveLocale`, `listLocales`, `listAndCountLocales`, `createLocales`, `createLocales`, `updateLocales`, `updateLocales`, `deleteLocales`, `softDeleteLocales`, `restoreLocales`, `retrieveTranslation`, `listTranslations`, `listAndCountTranslations`, `createTranslations`, `createTranslations`, `updateTranslations`, `updateTranslations`, `deleteTranslations`, `softDeleteTranslations`, `restoreTranslations`, `getStatistics`, `getTranslatableFields`, `getInactiveTranslatableFields`, `createTranslationSettings`, `createTranslationSettings`, `updateTranslationSettings`, `updateTranslationSettings`, `deleteTranslationSettings`, `listTranslationSettings`, `listAndCountTranslationSettings`, `retrieveTranslationSettings`. 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. Those 31 declarations carry 25 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 25 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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.
Fat interface: IUserModuleService (22 required operations) packages/core/types/src/user/service.ts:16 — `IUserModuleService` declares 22 required operations: `validateInviteToken`, `refreshInviteTokens`, `retrieveUser`, `listUsers`, `listAndCountUsers`, `createUsers`, `createUsers`, `updateUsers`, `updateUsers`, `deleteUsers`, `softDeleteUsers`, `restoreUsers`, `retrieveInvite`, `listInvites`, `listAndCountInvites`, `createInvites`, `createInvites`, `updateInvites`, `updateInvites`, `deleteInvites`, `softDeleteInvites`, `restoreInvites`. 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. Those 22 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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.
Fat interface: IAuthModuleService (37 required operations) packages/core/types/src/auth/service.ts:44 — `IAuthModuleService` declares 37 required operations: `authenticate`, `listAuthProviders`, `register`, `updateProvider`, `createPasswordResetToken`, `consumePasswordResetToken`, `validateCallback`, `validateAuthIdentity`, `startAuthMfa`, `verifyAuthMfa`, `createAuthMfaChallenge`, `verifyAuthMfaChallenge`, `disableAuthMfa`, `retrieveAuthMfa`, `listAuthMfa`, `generateAuthMfaRecoveryCodes`, `useAuthMfaRecoveryCode`, `requestAuthVerification`, `confirmAuthVerification`, `retrieveAuthVerification`, `listAuthVerifications`, `listAndCountAuthVerifications`, `retrieveAuthIdentity`, `listAuthIdentities`, `listAndCountAuthIdentities`, `createAuthIdentities`, `createAuthIdentities`, `updateAuthIdentities`, `updateAuthIdentities`, `deleteAuthIdentities`, `retrieveProviderIdentity`, `listProviderIdentities`, `createProviderIdentities`, `createProviderIdentities`, `updateProviderIdentities`, `updateProviderIdentities`, `deleteProviderIdentities`. 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. Those 37 declarations carry 33 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 33 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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.
Fat interface: IMedusaInternalService (20 required operations) packages/core/types/src/modules-sdk/medusa-internal-service.ts:12 — `IMedusaInternalService` declares 20 required operations under just 10 distinct name(s): `retrieve`, `retrieve`, `list`, `listAndCount`, `create`, `create`, `update`, `update`, `update`, `update`, `delete`, `delete`, `delete`, `delete`, `delete`, `softDelete`, `restore`, `upsert`, `upsert`, `upsertWithReplace`. 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. That is an OVERLOAD SET, not 20 separate responsibilities: a caller binds to 10 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 20 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.

D30 · Dependency Vulnerabilities · Low CVE · ×7

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

Silent fallback default in catch packages/medusa/src/commands/plugin/add.ts:145 — `yarnMajorVersion` swallows every exception into `return 1` — 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 scripts/deps-update/state.mjs:25 — `parseStateBody` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch www/apps/api-reference/utils/get-spec-versions.ts:195 — `listVersionsFromFs` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch www/apps/resources/app/md-content/[[...slug]]/route.ts:183 — `docPageToMarkdown_` swallows every exception into `return ""` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch www/utils/packages/docs-automator/src/classes/diff-analyzer.ts:87 — `getCommitFiles` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch www/utils/packages/typedoc-plugin-medusa-theme/src/utils/build-doc-page.ts:551 — `badgeBlocks` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.

D34 · Knowledge Freshness · Orphaned file · ×2

Orphaned file integration-tests/modules/medusa-config.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 integration-tests/helpers/wait-for-index.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.

X9 · Subsumed condition operand · Subsumed condition operand · ×2

Subsumed condition operand www/utils/packages/docs-automator/src/classes/diff-analyzer.ts:117 — `packagePath.startsWith("packages/core/framework")` can never decide this `||` — every value satisfying `packagePath.startsWith("packages/core/framework")` also satisfies `packagePath.startsWith("packages/core/")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Subsumed condition operand www/utils/packages/docs-automator/src/classes/diff-analyzer.ts:117 — `packagePath.startsWith("packages/core/utils")` can never decide this `||` — every value satisfying `packagePath.startsWith("packages/core/utils")` also satisfies `packagePath.startsWith("packages/core/")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.

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

Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 1 significant file(s) lose their only recent owner: integration-tests/http/src/utils/providers/payment-account-holder/services/account-holder-payment.ts. Pair on, review, or document these before any departure.

D20 · ADR Quality · No ADRs found · ×1

No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.

D30 · Dependency Vulnerabilities · Low vulnerability · ×1

REDACTED

D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1

Orphaned files with no living knowledge — 2 of 7 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (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; 7 of the 40 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: integration-tests/modules/medusa-config.ts, integration-tests/helpers/wait-for-index.ts. 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

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

REDACTED

DM9 · Scattered domain decisions · Rule about [exportName, httpTypeName] decided in 2 places · ×1

Rule about [exportName, httpTypeName] decided in 2 places — packages.cli.http-types-generator.src.core.schema-extractor.ExtractedSchema's [exportName, httpTypeName] are judged in packages.cli.http-types-generator.src.commands.generate, packages.cli.http-types-generator.src.commands.validate — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.

M2 · Architecture documentation · No ADRs · ×1

No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

P3 · Security & performance tooling · No SAST · ×1

No SAST — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 488335 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

R8 · Dependency Hygiene · Type-only dependency '@dnd-kit/core' in production deps · ×1

Type-only dependency '@dnd-kit/core' in production deps packages/admin/dashboard/src/routes/products/product-media/components/edit-product-media-form/edit-product-media-form.spec.tsx:34 — Every import is type-only — move it to devDependencies.

R8 · Dependency Hygiene · Test-only dependency 'jsonwebtoken' in production deps · ×1

Test-only dependency 'jsonwebtoken' in production deps integration-tests/package.json:22 — Only test files import it (first: integration-tests/http/__tests__/auth/admin/auth-asymetric.spec.ts:4) — move it to devDependencies.

S1 · Web-Security Posture · No security response headers detected · ×1

No security response headers detected www/apps/user-guide/public/_headers:1 — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `_headers` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)

Minor — 226 finding(s)

D12 · Dependency Hygiene · Outdated (npm) · ×222

Outdated (npm): @actions/core — @actions/core is pinned at 1.11.1; registry.npmjs.org publishes 3.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @aws-sdk/client-dynamodb — @aws-sdk/client-dynamodb is pinned at 3.1089.0; registry.npmjs.org publishes 3.1157.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @aws-sdk/client-s3 — @aws-sdk/client-s3 is pinned at 3.1089.0; registry.npmjs.org publishes 3.1157.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @aws-sdk/lib-storage — @aws-sdk/lib-storage is pinned at 3.1089.0; registry.npmjs.org publishes 3.1157.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @aws-sdk/s3-request-presigner — @aws-sdk/s3-request-presigner is pinned at 3.1089.0; registry.npmjs.org publishes 3.1157.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/core — @babel/core is pinned at 7.29.0; registry.npmjs.org publishes 8.0.9 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/eslint-parser — @babel/eslint-parser is pinned at 7.28.6; registry.npmjs.org publishes 8.0.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/parser — @babel/parser is pinned at 7.25.6; registry.npmjs.org publishes 8.0.8 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/runtime — @babel/runtime is pinned at 7.29.10; registry.npmjs.org publishes 8.0.8 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/traverse — @babel/traverse is pinned at 7.25.6; registry.npmjs.org publishes 8.0.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/types — @babel/types is pinned at 7.25.6; registry.npmjs.org publishes 8.0.8 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @changesets/changelog-github — @changesets/changelog-github is pinned at 0.4.8; registry.npmjs.org publishes 1.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @changesets/cli — @changesets/cli is pinned at 2.31.1; registry.npmjs.org publishes 3.0.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @cloudinary/url-gen — @cloudinary/url-gen is pinned at 1.17.0; registry.npmjs.org publishes 1.22.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @dnd-kit/sortable — @dnd-kit/sortable is pinned at 8.0.0; registry.npmjs.org publishes 10.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @emotion/is-prop-valid — @emotion/is-prop-valid is pinned at 1.3.1; registry.npmjs.org publishes 1.4.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @faker-js/faker — @faker-js/faker is pinned at 9.9.0; registry.npmjs.org publishes 10.6.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @graphql-codegen/core — @graphql-codegen/core is pinned at 4.0.2; registry.npmjs.org publishes 6.2.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @graphql-codegen/typescript — @graphql-codegen/typescript is pinned at 4.1.6; registry.npmjs.org publishes 6.1.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @graphql-tools/merge — @graphql-tools/merge is pinned at 9.2.8; registry.npmjs.org publishes 10.0.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @graphql-tools/schema — @graphql-tools/schema is pinned at 10.1.5; registry.npmjs.org publishes 11.0.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @hookform/resolvers — @hookform/resolvers is pinned at 5.5.7; registry.npmjs.org publishes 6.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @kapaai/react-sdk — @kapaai/react-sdk is pinned at 0.9.0; registry.npmjs.org publishes 0.17.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @mdx-js/loader — @mdx-js/loader is pinned at 3.1.0; registry.npmjs.org publishes 3.1.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @mdx-js/mdx — @mdx-js/mdx is pinned at 3.1.0; registry.npmjs.org publishes 3.1.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
+ 197 more in this group — see findings.md.

D10 · Test Quality · Skipped (documented) · ×4

Skipped (documented): should not allow unregistered customers to add store credits to a cart integration-tests/http/__tests__/loyalty/store/carts.spec.ts:1131 — Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): should throw if adding more credit to the cart than the store account has balance integration-tests/http/__tests__/loyalty/store/carts.spec.ts:1135 — Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): should complete cart with store credit and gift card added integration-tests/http/__tests__/loyalty/store/carts.spec.ts:1139 — Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): should only use credit first order if store credits are added to two carts active at the same time integration-tests/http/__tests__/loyalty/store/carts.spec.ts:1252 — Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing

Appendix B — Reproduction & audit trail

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

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b3419633f4e84d7b9c74ea6dce8ad762/history.json --exit-code 0 --source .	0	—
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --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 --exclude integration-tests/http/__fixtures__/feature-flag/src/modules/custom/migrations --exclude integration-tests/modules/__tests__/__fixtures__/testing-module/models --exclude integration-tests/modules/__tests__/__fixtures__/translation-test/src/modules/translation/migrations --exclude integration-tests/modules/__tests__/__fixtures__/translation-test/src/modules/translation/models --exclude integration-tests/modules/src/modules/brand/migrations --exclude integration-tests/modules/src/modules/brand/models --exclude packages/admin/admin-bundler --exclude packages/admin/admin-sdk --exclude packages/admin/admin-shared --exclude packages/admin/admin-vite-plugin --exclude packages/admin/dashboard/scripts --exclude packages/admin/dashboard/src/__tests__ --exclude packages/admin/dashboard/src/common --exclude packages/admin/dashboard/src/components --exclude packages/admin/dashboard/src/dashboard-app --exclude packages/admin/dashboard/src/exports --exclude packages/admin/dashboard/src/hooks --exclude packages/admin/dashboard/src/i18n --exclude packages/admin/dashboard/src/lib --exclude packages/admin/dashboard/src/providers --exclude packages/admin/dashboard/src/routes --exclude packages/admin/dashboard/src/utils --exclude packages/cli/create-medusa-app/src --exclude packages/cli/http-types-generator --exclude packages/cli/medusa-cli/scripts --exclude packages/cli/medusa-cli/src/codemods --exclude packages/cli/medusa-cli/src/commands --exclude packages/cli/medusa-cli/src/util --exclude packages/cli/oas/medusa-oas-cli/oas --exclude packages/cli/oas/medusa-oas-cli/redocly --exclude packages/cli/oas/medusa-oas-cli/src --exclude packages/cli/oas/oas-github-ci/scripts --exclude packages/core/core-flows/src --exclude packages/core/framework/src/build-tools --exclude packages/core/framework/src/config --exclude packages/core/framework/src/database --exclude packages/core/framework/src/deps --exclude packages/core/framework/src/feature-flags --exclude packages/core/framework/src/http --exclude packages/core/framework/src/jobs/__fixtures__/plugin/jobs --exclude packages/core/framework/src/jobs/__tests__ --exclude packages/core/framework/src/links --exclude packages/core/framework/src/logger --exclude packages/core/framework/src/migrations --exclude packages/core/framework/src/mikro-orm-cli --exclude packages/core/framework/src/modules-sdk --exclude packages/core/framework/src/orchestration --exclude packages/core/framework/src/policies --exclude packages/core/framework/src/search --exclude packages/core/framework/src/subscribers/__mocks__ --exclude packages/core/framework/src/subscribers/__tests__ --exclude packages/core/framework/src/telemetry --exclude packages/core/framework/src/types --exclude packages/core/framework/src/utils --exclude packages/core/framework/src/workflows --exclude packages/core/framework/src/workflows-sdk --exclude packages/core/framework/src/zod --exclude packages/core/instantsearch-adapter/src --exclude packages/core/js-sdk/src --exclude packages/core/modules-sdk --exclude packages/core/orchestration --exclude packages/core/query --exclude packages/core/types/src --exclude packages/core/utils/src/analytics --exclude packages/core/utils/src/api-key --exclude packages/core/utils/src/auth --exclude packages/core/utils/src/caching --exclude packages/core/utils/src/common --exclude packages/core/utils/src/core-flows --exclude packages/core/utils/src/dal --exclude packages/core/utils/src/defaults --exclude packages/core/utils/src/dev-server --exclude packages/core/utils/src/dml --exclude packages/core/utils/src/event-bus --exclude packages/core/utils/src/exceptions --exclude packages/core/utils/src/feature-flags --exclude packages/core/utils/src/file --exclude packages/core/utils/src/fulfillment --exclude packages/core/utils/src/graphql/__tests__/utils --exclude packages/core/utils/src/inventory --exclude packages/core/utils/src/license --exclude packages/core/utils/src/link --exclude packages/core/utils/src/migrations --exclude packages/core/utils/src/modules-sdk --exclude packages/core/utils/src/notification --exclude packages/core/utils/src/orchestration --exclude packages/core/utils/src/order --exclude packages/core/utils/src/payment --exclude packages/core/utils/src/pg --exclude packages/core/utils/src/policies --exclude packages/core/utils/src/pricing --exclude packages/core/utils/src/product --exclude packages/core/utils/src/promotion --exclude packages/core/utils/src/schema --exclude packages/core/utils/src/search --exclude packages/core/utils/src/shipping --exclude packages/core/utils/src/totals --exclude packages/core/utils/src/translations --exclude packages/core/utils/src/user --exclude packages/core/workflows-sdk --exclude packages/deps/src --exclude packages/design-system/icons/src --exclude packages/design-system/toolbox --exclude packages/design-system/ui/.storybook --exclude packages/design-system/ui/src --exclude packages/design-system/ui-preset/src --exclude packages/eslint-plugin --exclude packages/medusa/src/api --exclude packages/medusa/src/commands --exclude packages/medusa/src/core-flows --exclude packages/medusa/src/feature-flags --exclude packages/medusa/src/instrumentation --exclude packages/medusa/src/loaders --exclude packages/medusa/src/migration-scripts --exclude packages/medusa/src/modules --exclude packages/medusa/src/policies --exclude packages/medusa/src/subscribers --exclude packages/medusa/src/types --exclude packages/medusa/src/utils --exclude packages/medusa-telemetry/src --exclude packages/medusa-test-utils/src --exclude packages/modules/analytics/integration-tests --exclude packages/modules/analytics/src --exclude packages/modules/api-key/integration-tests --exclude packages/modules/api-key/src --exclude packages/modules/auth/integration-tests --exclude packages/modules/auth/src --exclude packages/modules/cache-inmemory/src --exclude packages/modules/cache-redis/src --exclude packages/modules/caching/integration-tests --exclude packages/modules/caching/src --exclude packages/modules/cart/integration-tests --exclude packages/modules/cart/src --exclude packages/modules/currency/integration-tests --exclude packages/modules/currency/src --exclude packages/modules/customer/integration-tests --exclude packages/modules/customer/src --exclude packages/modules/event-bus-local/integration-tests --exclude packages/modules/event-bus-local/src --exclude packages/modules/event-bus-redis/integration-tests --exclude packages/modules/event-bus-redis/src --exclude packages/modules/file/integration-tests --exclude packages/modules/file/src --exclude packages/modules/fulfillment/integration-tests --exclude packages/modules/fulfillment/src --exclude packages/modules/index/integration-tests --exclude packages/modules/index/src --exclude packages/modules/inventory/integration-tests --exclude packages/modules/inventory/src --exclude packages/modules/link-modules/integration-tests --exclude packages/modules/link-modules/src --exclude packages/modules/locking/integration-tests --exclude packages/modules/locking/src --exclude packages/modules/notification/integration-tests --exclude packages/modules/notification/src --exclude packages/modules/order/integration-tests --exclude packages/modules/order/src --exclude packages/modules/payment/integration-tests --exclude packages/modules/payment/src --exclude packages/modules/pricing/integration-tests --exclude packages/modules/pricing/src --exclude packages/modules/product/integration-tests --exclude packages/modules/product/src --exclude packages/modules/promotion/integration-tests --exclude packages/modules/promotion/src --exclude packages/modules/providers/analytics-local/src --exclude packages/modules/providers/analytics-posthog/src --exclude packages/modules/providers/auth-emailpass/integration-tests --exclude packages/modules/providers/auth-emailpass/src --exclude packages/modules/providers/auth-github/integration-tests --exclude packages/modules/providers/auth-github/src --exclude packages/modules/providers/auth-google/integration-tests --exclude packages/modules/providers/auth-google/src --exclude packages/modules/providers/auth-oidc/integration-tests --exclude packages/modules/providers/auth-oidc/src --exclude packages/modules/providers/caching-redis --exclude packages/modules/providers/file-local/integration-tests/__tests__ --exclude packages/modules/providers/file-local/src --exclude packages/modules/providers/file-s3/integration-tests/__tests__ --exclude packages/modules/providers/file-s3/src --exclude packages/modules/providers/fulfillment-manual/src --exclude packages/modules/providers/locking-postgres/integration-tests --exclude packages/modules/providers/locking-postgres/src --exclude packages/modules/providers/locking-redis/integration-tests --exclude packages/modules/providers/locking-redis/src --exclude packages/modules/providers/notification-local/integration-tests --exclude packages/modules/providers/notification-local/src --exclude packages/modules/providers/notification-sendgrid/integration-tests --exclude packages/modules/providers/notification-sendgrid/src --exclude packages/modules/providers/payment-stripe/src --exclude packages/modules/providers/search-postgres/integration-tests --exclude packages/modules/providers/search-postgres/src --exclude packages/modules/rbac/integration-tests --exclude packages/modules/rbac/src --exclude packages/modules/region/integration-tests --exclude packages/modules/region/src --exclude packages/modules/sales-channel/integration-tests --exclude packages/modules/sales-channel/src --exclude packages/modules/search/integration-tests --exclude packages/modules/search/src --exclude packages/modules/settings --exclude packages/modules/stock-location/integration-tests --exclude packages/modules/stock-location/src --exclude packages/modules/store/integration-tests --exclude packages/modules/store/src --exclude packages/modules/tax/integration-tests --exclude packages/modules/tax/src --exclude packages/modules/translation/integration-tests --exclude packages/modules/translation/src --exclude packages/modules/user/integration-tests --exclude packages/modules/user/src --exclude packages/modules/workflow-engine-inmemory/integration-tests --exclude packages/modules/workflow-engine-inmemory/src --exclude packages/modules/workflow-engine-redis/integration-tests --exclude packages/modules/workflow-engine-redis/src --exclude packages/plugins/draft-order --exclude packages/plugins/loyalty/src --exclude scripts/deps-update --exclude www/apps/api-reference/app/assets --exclude www/apps/api-reference/app/base-specs --exclude www/apps/api-reference/app/download --exclude www/apps/api-reference/app/md-content --exclude www/apps/api-reference/app/schema --exclude www/apps/api-reference/app/tag --exclude www/apps/api-reference/app/versions --exclude www/apps/api-reference/components --exclude www/apps/api-reference/config --exclude www/apps/api-reference/generated --exclude www/apps/api-reference/hooks --exclude www/apps/api-reference/layouts --exclude www/apps/api-reference/lib --exclude www/apps/api-reference/markdown --exclude www/apps/api-reference/providers --exclude www/apps/api-reference/scripts --exclude www/apps/api-reference/specs/admin/code_samples/JavaScript --exclude www/apps/api-reference/specs/admin/code_samples/TypeScript --exclude www/apps/api-reference/specs/admin/components --exclude www/apps/api-reference/specs/admin/paths --exclude www/apps/api-reference/specs/store/code_samples/JavaScript --exclude www/apps/api-reference/specs/store/code_samples/TypeScript --exclude www/apps/api-reference/specs/store/components --exclude www/apps/api-reference/specs/store/paths --exclude www/apps/api-reference/specs/versions --exclude www/apps/api-reference/types --exclude www/apps/api-reference/utils --exclude www/apps/book/app/.well-known --exclude www/apps/book/app/agents --exclude www/apps/book/app/learn --exclude www/apps/book/app/llms-content --exclude www/apps/book/app/md-content --exclude www/apps/book/app/robots.txt --exclude www/apps/book/app/start --exclude www/apps/book/components --exclude www/apps/book/config --exclude www/apps/book/generated --exclude www/apps/book/providers --exclude www/apps/book/scripts --exclude www/apps/book/utils --exclude www/apps/cloud/app/access-keys --exclude www/apps/cloud/app/agents --exclude www/apps/cloud/app/api --exclude www/apps/cloud/app/assistant --exclude www/apps/cloud/app/billing --exclude www/apps/cloud/app/cache --exclude www/apps/cloud/app/changelog --exclude www/apps/cloud/app/cli --exclude www/apps/cloud/app/command-palette --exclude www/apps/cloud/app/comparison --exclude www/apps/cloud/app/connect-storefront --exclude www/apps/cloud/app/database --exclude www/apps/cloud/app/deployments --exclude www/apps/cloud/app/emails --exclude www/apps/cloud/app/environments --exclude www/apps/cloud/app/faq --exclude www/apps/cloud/app/first-project --exclude www/apps/cloud/app/ip-addresses --exclude www/apps/cloud/app/logs --exclude www/apps/cloud/app/md-content --exclude www/apps/cloud/app/medusa-mcp --exclude www/apps/cloud/app/mermaid-icon-test --exclude www/apps/cloud/app/monitoring --exclude www/apps/cloud/app/notifications --exclude www/apps/cloud/app/organizations --exclude www/apps/cloud/app/pricing --exclude www/apps/cloud/app/projects --exclude www/apps/cloud/app/redis --exclude www/apps/cloud/app/s3 --exclude www/apps/cloud/app/search --exclude www/apps/cloud/app/sign-up --exclude www/apps/cloud/app/status --exclude www/apps/cloud/app/storefront --exclude www/apps/cloud/app/update-medusa --exclude www/apps/cloud/app/usage --exclude www/apps/cloud/app/user --exclude www/apps/cloud/app/webhooks --exclude www/apps/cloud/components --exclude www/apps/cloud/config --exclude www/apps/cloud/generated --exclude www/apps/cloud/providers --exclude www/apps/cloud/scripts --exclude www/apps/cloud/utils --exclude www/apps/docs --exclude www/apps/resources/app/admin-components --exclude www/apps/resources/app/admin-widget-injection-zones --exclude www/apps/resources/app/agents --exclude www/apps/resources/app/api --exclude www/apps/resources/app/commerce-modules --exclude www/apps/resources/app/create-medusa-app --exclude www/apps/resources/app/data-model-repository-reference --exclude www/apps/resources/app/deployment --exclude www/apps/resources/app/examples --exclude www/apps/resources/app/how-to-tutorials --exclude www/apps/resources/app/infrastructure-modules --exclude www/apps/resources/app/instantsearch --exclude www/apps/resources/app/integrations --exclude www/apps/resources/app/js-sdk --exclude www/apps/resources/app/lint --exclude www/apps/resources/app/md-content --exclude www/apps/resources/app/medusa-cli --exclude www/apps/resources/app/medusa-container-resources --exclude www/apps/resources/app/medusa-workflows-reference --exclude www/apps/resources/app/nextjs-starter --exclude www/apps/resources/app/plugins --exclude www/apps/resources/app/recipes --exclude www/apps/resources/app/references --exclude www/apps/resources/app/references-overview --exclude www/apps/resources/app/service-factory-reference --exclude www/apps/resources/app/storefront-development --exclude www/apps/resources/app/test-tools-reference --exclude www/apps/resources/app/tools --exclude www/apps/resources/app/troubleshooting --exclude www/apps/resources/components --exclude www/apps/resources/config --exclude www/apps/resources/generated --exclude www/apps/resources/providers --exclude www/apps/resources/references/analytics --exclude www/apps/resources/references/analytics_provider --exclude www/apps/resources/references/api_key --exclude www/apps/resources/references/api_key_models --exclude www/apps/resources/references/auth --exclude www/apps/resources/references/auth_models --exclude www/apps/resources/references/auth_provider --exclude www/apps/resources/references/cache --exclude www/apps/resources/references/caching --exclude www/apps/resources/references/cart --exclude www/apps/resources/references/cart_models --exclude www/apps/resources/references/core_flows --exclude www/apps/resources/references/currency --exclude www/apps/resources/references/currency_models --exclude www/apps/resources/references/customer --exclude www/apps/resources/references/customer_models --exclude www/apps/resources/references/dml --exclude www/apps/resources/references/event --exclude www/apps/resources/references/events --exclude www/apps/resources/references/file --exclude www/apps/resources/references/file_service --exclude www/apps/resources/references/fulfillment --exclude www/apps/resources/references/fulfillment_models --exclude www/apps/resources/references/fulfillment_provider --exclude www/apps/resources/references/helper_steps --exclude www/apps/resources/references/inventory_next --exclude www/apps/resources/references/inventory_next_models --exclude www/apps/resources/references/js_sdk --exclude www/apps/resources/references/locking --exclude www/apps/resources/references/loyalty --exclude www/apps/resources/references/loyalty_models --exclude www/apps/resources/references/medusa --exclude www/apps/resources/references/mfa --exclude www/apps/resources/references/module_events --exclude www/apps/resources/references/modules --exclude www/apps/resources/references/modules_sdk --exclude www/apps/resources/references/notification --exclude www/apps/resources/references/notification_service --exclude www/apps/resources/references/order --exclude www/apps/resources/references/order_models --exclude www/apps/resources/references/payment --exclude www/apps/resources/references/payment_models --exclude www/apps/resources/references/payment_provider --exclude www/apps/resources/references/pricing --exclude www/apps/resources/references/pricing_models --exclude www/apps/resources/references/product --exclude www/apps/resources/references/product_models --exclude www/apps/resources/references/promotion --exclude www/apps/resources/references/promotion_models --exclude www/apps/resources/references/region --exclude www/apps/resources/references/region_models --exclude www/apps/resources/references/sales_channel --exclude www/apps/resources/references/sales_channel_models --exclude www/apps/resources/references/search --exclude www/apps/resources/references/search_provider --exclude www/apps/resources/references/settings --exclude www/apps/resources/references/settings_models --exclude www/apps/resources/references/stock_location_next --exclude www/apps/resources/references/stock_location_next_models --exclude www/apps/resources/references/store --exclude www/apps/resources/references/store_credit --exclude www/apps/resources/references/store_credit_models --exclude www/apps/resources/references/store_models --exclude www/apps/resources/references/tax --exclude www/apps/resources/references/tax_models --exclude www/apps/resources/references/tax_provider --exclude www/apps/resources/references/translation --exclude www/apps/resources/references/translation_models --exclude www/apps/resources/references/types --exclude www/apps/resources/references/user --exclude www/apps/resources/references/user_models --exclude www/apps/resources/references/utils --exclude www/apps/resources/references/workflows --exclude www/apps/resources/scripts --exclude www/apps/resources/sidebars --exclude www/apps/resources/utils --exclude www/apps/ui/app/agents --exclude www/apps/ui/app/colors --exclude www/apps/ui/app/components --exclude www/apps/ui/app/hooks --exclude www/apps/ui/app/icons --exclude www/apps/ui/app/installation --exclude www/apps/ui/app/md-content --exclude www/apps/ui/app/utils --exclude www/apps/ui/components --exclude www/apps/ui/config --exclude www/apps/ui/generated --exclude www/apps/ui/providers --exclude www/apps/ui/scripts --exclude www/apps/ui/specs --exclude www/apps/ui/types --exclude www/apps/ui/utils --exclude www/apps/user-guide/app/agents --exclude www/apps/user-guide/app/customers --exclude www/apps/user-guide/app/inventory --exclude www/apps/user-guide/app/loyalty --exclude www/apps/user-guide/app/md-content --exclude www/apps/user-guide/app/orders --exclude www/apps/user-guide/app/price-lists --exclude www/apps/user-guide/app/products --exclude www/apps/user-guide/app/promotions --exclude www/apps/user-guide/app/reset-password --exclude www/apps/user-guide/app/settings --exclude www/apps/user-guide/app/tips --exclude www/apps/user-guide/components --exclude www/apps/user-guide/config --exclude www/apps/user-guide/generated --exclude www/apps/user-guide/providers --exclude www/apps/user-guide/scripts --exclude www/apps/user-guide/utils --exclude www/packages/build-scripts --exclude www/packages/docs-ui/src --exclude www/packages/docs-utils --exclude www/packages/remark-rehype-plugins --exclude www/packages/tags --exclude www/packages/tailwind --exclude www/packages/tsconfig --exclude www/packages/types --exclude www/utils/generated --exclude www/utils/packages/docs-automator --exclude www/utils/packages/docs-generator/src --exclude www/utils/packages/react-docs-generator --exclude www/utils/packages/release-banner/src --exclude www/utils/packages/scripts --exclude www/utils/packages/typedoc-config --exclude www/utils/packages/typedoc-generate-references --exclude www/utils/packages/typedoc-plugin-custom/src --exclude www/utils/packages/typedoc-plugin-medusa-theme/src --exclude www/utils/packages/typedoc-plugin-workflows/src --exclude www/utils/packages/types --exclude www/utils/packages/utils --exclude www/utils/packages/workflows-diagrams-generator --exclude www/vale/styles/docs --exclude www/vale/styles/write-good .	220	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	115	artifacts/raw/trivy-fs.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	4	artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—
D43 · Malicious Dependencies	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	0	artifacts/raw/trivy-fs.json

Run 01a17a27-0979-770a-868f-b934a713b4a1 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Findings by how serious they are

This survey was produced by

Executive summary

Top priorities

Diagnosis: what the measurements show together

Architecture: which parts of the code depend on which

At a glance — Code Health · 91% · Exemplary ·

At a glance — Architecture · 81% · Adequate · gated by D23 ·

At a glance — Maturity · 68% · Adequate · gated by M2 ·

At a glance — Readiness · 39% · Weak · gated by D12, R8, P2, P3 ·

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

At a glance — Domain Modelling · 17% · Critical · gated by DM6 ·

At a glance — Accessibility · 44% · Weak · gated by AC4 ·

At a glance — Performance · 100% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

Dimensions

Frontend & cross-cutting dimensions

WCAG coverage — what static analysis assessed

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts