Executive summary
myparcelnl/woocommerce falls short of our standard for production, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 46.0 out of 100 and is rated Weak, and 74 of its 87 critical findings are security problems.
Accessibility, at 30.4, is the weakest lens and counts most in the score. The best first step is adding text alternatives, worth about 7.4 points. Making the controls keyboard-usable comes next, worth about 4.9 points. Raising Accessibility to 70 would lift the score to about 58.7.
Thirty-six secrets can leak from the build pipeline. Thirty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Limiting each secret to its own step and pinning each tool to an exact version would close both risks. Updating the vulnerable packages would fix the three packages with a known security hole, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once. The seven uses of packages that aren't listed need adding to the project's list of dependencies.
The product code is 11,481 lines, about €20,000 to rebuild.
If Accessibility rose from 30.4 to 70, the lowest score rated Strong, the score would rise from 46.0 to about 58.7.
Rebuild cost: about €20,000 · Estimate
| Cost to rebuild | €6,700 to €34,000, for 112 to 354 hours of work, about 0.1 person-years for one engineer |
|---|---|
| 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 46. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 11,481 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 (global) | 2 MyParcelNL.WooCommerce.Adapter | 3 MyParcelNL.WooCommerce.Contract | 4 MyParcelNL.WooCommerce.Database.Contract | 5 MyParcelNL.WooCommerce.Facade | 6 MyParcelNL.WooCommerce.Hooks.Concern | 7 MyParcelNL.WooCommerce.Hooks.Contract | 8 MyParcelNL.WooCommerce.Integration | 9 MyParcelNL.WooCommerce.Logger | 10 MyParcelNL.WooCommerce.Pdk | 11 MyParcelNL.WooCommerce.Pdk.Context.Service | 12 MyParcelNL.WooCommerce.Pdk.Plugin.Action | 13 MyParcelNL.WooCommerce.Pdk.Plugin.Installer | 14 MyParcelNL.WooCommerce.Pdk.Plugin.Service | 15 MyParcelNL.WooCommerce.Pdk.Product.Repository | 16 MyParcelNL.WooCommerce.Pdk.Service | 17 MyParcelNL.WooCommerce.Pdk.Settings.Repository | 18 MyParcelNL.WooCommerce.Pdk.Webhook | 19 MyParcelNL.WooCommerce.WooCommerce.Contract | 20 views | 21 views.backend.admin.src | 22 views.backend.admin.src.composables | 23 views.backend.admin.src.hooks | 24 views.blocks.delivery-options.src | 25 views.blocks.delivery-options.src.types | 26 views.frontend.checkout-address-widget.src.utils | 27 views.frontend.checkout-core.src | 28 views.frontend.checkout-core.src.utils | 29 views.frontend.common.src.types | 30 MyParcelNL.WooCommerce.Database.Service | 31 MyParcelNL.WooCommerce.Migration.Pdk | 32 MyParcelNL.WooCommerce.Pdk.Audit.Repository | 33 MyParcelNL.WooCommerce.Pdk.Plugin | 34 MyParcelNL.WooCommerce.Pdk.Plugin.Repository | 35 MyParcelNL.WooCommerce.Service | 36 MyParcelNL.WooCommerce.WooCommerce.Repository | 37 views.frontend.common.src.utils.checkout | 38 MyParcelNL.WooCommerce.Hooks | 39 MyParcelNL.WooCommerce.Migration | 40 MyParcelNL.WooCommerce.Pdk.Hooks |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 MyParcelNL.WooCommerce.Adapter | ||||||||||||||||||||||||||||||||||||||||
| 3 MyParcelNL.WooCommerce.Contract | ||||||||||||||||||||||||||||||||||||||||
| 4 MyParcelNL.WooCommerce.Database.Contract | ||||||||||||||||||||||||||||||||||||||||
| 5 MyParcelNL.WooCommerce.Facade | ||||||||||||||||||||||||||||||||||||||||
| 6 MyParcelNL.WooCommerce.Hooks.Concern | ||||||||||||||||||||||||||||||||||||||||
| 7 MyParcelNL.WooCommerce.Hooks.Contract | ||||||||||||||||||||||||||||||||||||||||
| 8 MyParcelNL.WooCommerce.Integration | ||||||||||||||||||||||||||||||||||||||||
| 9 MyParcelNL.WooCommerce.Logger | ||||||||||||||||||||||||||||||||||||||||
| 10 MyParcelNL.WooCommerce.Pdk | ||||||||||||||||||||||||||||||||||||||||
| 11 MyParcelNL.WooCommerce.Pdk.Context.Service | ||||||||||||||||||||||||||||||||||||||||
| 12 MyParcelNL.WooCommerce.Pdk.Plugin.Action | ||||||||||||||||||||||||||||||||||||||||
| 13 MyParcelNL.WooCommerce.Pdk.Plugin.Installer | ||||||||||||||||||||||||||||||||||||||||
| 14 MyParcelNL.WooCommerce.Pdk.Plugin.Service | ||||||||||||||||||||||||||||||||||||||||
| 15 MyParcelNL.WooCommerce.Pdk.Product.Repository | ||||||||||||||||||||||||||||||||||||||||
| 16 MyParcelNL.WooCommerce.Pdk.Service | ||||||||||||||||||||||||||||||||||||||||
| 17 MyParcelNL.WooCommerce.Pdk.Settings.Repository | ||||||||||||||||||||||||||||||||||||||||
| 18 MyParcelNL.WooCommerce.Pdk.Webhook | ||||||||||||||||||||||||||||||||||||||||
| 19 MyParcelNL.WooCommerce.WooCommerce.Contract | ||||||||||||||||||||||||||||||||||||||||
| 20 views | ||||||||||||||||||||||||||||||||||||||||
| 21 views.backend.admin.src | ||||||||||||||||||||||||||||||||||||||||
| 22 views.backend.admin.src.composables | ||||||||||||||||||||||||||||||||||||||||
| 23 views.backend.admin.src.hooks | ||||||||||||||||||||||||||||||||||||||||
| 24 views.blocks.delivery-options.src | ||||||||||||||||||||||||||||||||||||||||
| 25 views.blocks.delivery-options.src.types | ||||||||||||||||||||||||||||||||||||||||
| 26 views.frontend.checkout-address-widget.src.utils | ||||||||||||||||||||||||||||||||||||||||
| 27 views.frontend.checkout-core.src | ||||||||||||||||||||||||||||||||||||||||
| 28 views.frontend.checkout-core.src.utils | ||||||||||||||||||||||||||||||||||||||||
| 29 views.frontend.common.src.types | ||||||||||||||||||||||||||||||||||||||||
| 30 MyParcelNL.WooCommerce.Database.Service | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 MyParcelNL.WooCommerce.Migration.Pdk | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 MyParcelNL.WooCommerce.Pdk.Audit.Repository | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 MyParcelNL.WooCommerce.Pdk.Plugin | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 MyParcelNL.WooCommerce.Pdk.Plugin.Repository | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 35 MyParcelNL.WooCommerce.Service | 3 | |||||||||||||||||||||||||||||||||||||||
| 36 MyParcelNL.WooCommerce.WooCommerce.Repository | 2 | |||||||||||||||||||||||||||||||||||||||
| 37 views.frontend.common.src.utils.checkout | 4 | |||||||||||||||||||||||||||||||||||||||
| 38 MyParcelNL.WooCommerce.Hooks | 14 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 MyParcelNL.WooCommerce.Migration | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 40 MyParcelNL.WooCommerce.Pdk.Hooks | 9 | 2 | 1 |
30→4 MyParcelNL.WooCommerce.Database.Service uses MyParcelNL.WooCommerce.Database.Contract✕
- Connections
- 1 pair of types, where a type in MyParcelNL.WooCommerce.Database.Service uses a type in MyParcelNL.WooCommerce.Database.Contract.
- The types involved
MyParcelNL.WooCommerce.Database.Service.WpDatabaseService→MyParcelNL.WooCommerce.Database.Contract.WpDatabaseServiceInterface
- Direction
- MyParcelNL.WooCommerce.Database.Service uses MyParcelNL.WooCommerce.Database.Contract, so a change to MyParcelNL.WooCommerce.Database.Contract can break MyParcelNL.WooCommerce.Database.Service, while a change to MyParcelNL.WooCommerce.Database.Service can't break MyParcelNL.WooCommerce.Database.Contract.
- Position
- Below the diagonal: MyParcelNL.WooCommerce.Database.Service uses a module listed above it, which is the healthy direction.
31→4 MyParcelNL.WooCommerce.Migration.Pdk uses MyParcelNL.WooCommerce.Database.Contract✕
- Connections
- 1 pair of types, where a type in MyParcelNL.WooCommerce.Migration.Pdk uses a type in MyParcelNL.WooCommerce.Database.Contract.
- The types involved
MyParcelNL.WooCommerce.Migration.Pdk.AuditsMigration→MyParcelNL.WooCommerce.Database.Contract.WpDatabaseServiceInterface
- Direction
- MyParcelNL.WooCommerce.Migration.Pdk uses MyParcelNL.WooCommerce.Database.Contract, so a change to MyParcelNL.WooCommerce.Database.Contract can break MyParcelNL.WooCommerce.Migration.Pdk, while a change to MyParcelNL.WooCommerce.Migration.Pdk can't break MyParcelNL.WooCommerce.Database.Contract.
- Position
- Below the diagonal: MyParcelNL.WooCommerce.Migration.Pdk uses a module listed above it, which is the healthy direction.
31→39 MyParcelNL.WooCommerce.Migration.Pdk uses MyParcelNL.WooCommerce.Migration part of a loop✕
- Connections
- 1 pair of types, where a type in MyParcelNL.WooCommerce.Migration.Pdk uses a type in MyParcelNL.WooCommerce.Migration.
- The types involved
MyParcelNL.WooCommerce.Migration.Pdk.AbstractPdkMigration→MyParcelNL.WooCommerce.Migration.AbstractMigration
- Direction
- MyParcelNL.WooCommerce.Migration.Pdk uses MyParcelNL.WooCommerce.Migration, so a change to MyParcelNL.WooCommerce.Migration can break MyParcelNL.WooCommerce.Migration.Pdk, while a change to MyParcelNL.WooCommerce.Migration.Pdk can't break MyParcelNL.WooCommerce.Migration.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→4 MyParcelNL.WooCommerce.Pdk.Audit.Repository uses MyParcelNL.WooCommerce.Database.Contract✕
- Connections
- 1 pair of types, where a type in MyParcelNL.WooCommerce.Pdk.Audit.Repository uses a type in MyParcelNL.WooCommerce.Database.Contract.
- The types involved
MyParcelNL.WooCommerce.Pdk.Audit.Repository.WcPdkAuditRepository→MyParcelNL.WooCommerce.Database.Contract.WpDatabaseServiceInterface
- Direction
- MyParcelNL.WooCommerce.Pdk.Audit.Repository uses MyParcelNL.WooCommerce.Database.Contract, so a change to MyParcelNL.WooCommerce.Database.Contract can break MyParcelNL.WooCommerce.Pdk.Audit.Repository, while a change to MyParcelNL.WooCommerce.Pdk.Audit.Repository can't break MyParcelNL.WooCommerce.Database.Contract.
- Position
- Below the diagonal: MyParcelNL.WooCommerce.Pdk.Audit.Repository uses a module listed above it, which is the healthy direction.
33→19 MyParcelNL.WooCommerce.Pdk.Plugin uses MyParcelNL.WooCommerce.WooCommerce.Contract✕
- Connections
- 1 pair of types, where a type in MyParcelNL.WooCommerce.Pdk.Plugin uses a type in MyParcelNL.WooCommerce.WooCommerce.Contract.
- The types involved
MyParcelNL.WooCommerce.Pdk.Plugin.WcShippingMethodRepository→MyParcelNL.WooCommerce.WooCommerce.Contract.WcShippingRepositoryInterface
- Direction
- MyParcelNL.WooCommerce.Pdk.Plugin uses MyParcelNL.WooCommerce.WooCommerce.Contract, so a change to MyParcelNL.WooCommerce.WooCommerce.Contract can break MyParcelNL.WooCommerce.Pdk.Plugin, while a change to MyParcelNL.WooCommerce.Pdk.Plugin can't break MyParcelNL.WooCommerce.WooCommerce.Contract.
- Position
- Below the diagonal: MyParcelNL.WooCommerce.Pdk.Plugin uses a module listed above it, which is the healthy direction.
34→2 MyParcelNL.WooCommerce.Pdk.Plugin.Repository uses MyParcelNL.WooCommerce.Adapter✕
- Connections
- 3 pairs of types, where a type in MyParcelNL.WooCommerce.Pdk.Plugin.Repository uses a type in MyParcelNL.WooCommerce.Adapter.
- The types involved
MyParcelNL.WooCommerce.Pdk.Plugin.Repository.PdkOrderRepository→MyParcelNL.WooCommerce.Adapter.LegacyDeliveryOptionsAdapterMyParcelNL.WooCommerce.Pdk.Plugin.Repository.PdkOrderRepository→MyParcelNL.WooCommerce.Adapter.WcAddressAdapterMyParcelNL.WooCommerce.Pdk.Plugin.Repository.WcCartRepository→MyParcelNL.WooCommerce.Adapter.WcAddressAdapter
- Direction
- MyParcelNL.WooCommerce.Pdk.Plugin.Repository uses MyParcelNL.WooCommerce.Adapter, so a change to MyParcelNL.WooCommerce.Adapter can break MyParcelNL.WooCommerce.Pdk.Plugin.Repository, while a change to MyParcelNL.WooCommerce.Pdk.Plugin.Repository can't break MyParcelNL.WooCommerce.Adapter.
- Position
- Below the diagonal: MyParcelNL.WooCommerce.Pdk.Plugin.Repository uses a module listed above it, which is the healthy direction.
34→19 MyParcelNL.WooCommerce.Pdk.Plugin.Repository uses MyParcelNL.WooCommerce.WooCommerce.Contract✕
- Connections
- 2 pairs of types, where a type in MyParcelNL.WooCommerce.Pdk.Plugin.Repository uses a type in MyParcelNL.WooCommerce.WooCommerce.Contract.
- The types involved
MyParcelNL.WooCommerce.Pdk.Plugin.Repository.PdkOrderRepository→MyParcelNL.WooCommerce.WooCommerce.Contract.WcOrderRepositoryInterfaceMyParcelNL.WooCommerce.Pdk.Plugin.Repository.WcOrderNoteRepository→MyParcelNL.WooCommerce.WooCommerce.Contract.WcOrderRepositoryInterface
- Direction
- MyParcelNL.WooCommerce.Pdk.Plugin.Repository uses MyParcelNL.WooCommerce.WooCommerce.Contract, so a change to MyParcelNL.WooCommerce.WooCommerce.Contract can break MyParcelNL.WooCommerce.Pdk.Plugin.Repository, while a change to MyParcelNL.WooCommerce.Pdk.Plugin.Repository can't break MyParcelNL.WooCommerce.WooCommerce.Contract.
- Position
- Below the diagonal: MyParcelNL.WooCommerce.Pdk.Plugin.Repository uses a module listed above it, which is the healthy direction.
35→3 MyParcelNL.WooCommerce.Service uses MyParcelNL.WooCommerce.Contract✕
- Connections
- 3 pairs of types, where a type in MyParcelNL.WooCommerce.Service uses a type in MyParcelNL.WooCommerce.Contract.
- The types involved
MyParcelNL.WooCommerce.Service.WooCommerceService→MyParcelNL.WooCommerce.Contract.WooCommerceServiceInterfaceMyParcelNL.WooCommerce.Service.WordPressService→MyParcelNL.WooCommerce.Contract.WordPressServiceInterfaceMyParcelNL.WooCommerce.Service.WpFilterService→MyParcelNL.WooCommerce.Contract.WpFilterServiceInterface
- Direction
- MyParcelNL.WooCommerce.Service uses MyParcelNL.WooCommerce.Contract, so a change to MyParcelNL.WooCommerce.Contract can break MyParcelNL.WooCommerce.Service, while a change to MyParcelNL.WooCommerce.Service can't break MyParcelNL.WooCommerce.Contract.
- Position
- Below the diagonal: MyParcelNL.WooCommerce.Service uses a module listed above it, which is the healthy direction.
36→19 MyParcelNL.WooCommerce.WooCommerce.Repository uses MyParcelNL.WooCommerce.WooCommerce.Contract✕
- Connections
- 2 pairs of types, where a type in MyParcelNL.WooCommerce.WooCommerce.Repository uses a type in MyParcelNL.WooCommerce.WooCommerce.Contract.
- The types involved
MyParcelNL.WooCommerce.WooCommerce.Repository.WcOrderRepository→MyParcelNL.WooCommerce.WooCommerce.Contract.WcOrderRepositoryInterfaceMyParcelNL.WooCommerce.WooCommerce.Repository.WcShippingRepository→MyParcelNL.WooCommerce.WooCommerce.Contract.WcShippingRepositoryInterface
- Direction
- MyParcelNL.WooCommerce.WooCommerce.Repository uses MyParcelNL.WooCommerce.WooCommerce.Contract, so a change to MyParcelNL.WooCommerce.WooCommerce.Contract can break MyParcelNL.WooCommerce.WooCommerce.Repository, while a change to MyParcelNL.WooCommerce.WooCommerce.Repository can't break MyParcelNL.WooCommerce.WooCommerce.Contract.
- Position
- Below the diagonal: MyParcelNL.WooCommerce.WooCommerce.Repository uses a module listed above it, which is the healthy direction.
37→29 views.frontend.common.src.utils.checkout uses views.frontend.common.src.types✕
- Connections
- 4 pairs of types, where a type in views.frontend.common.src.utils.checkout uses a type in views.frontend.common.src.types.
- The types involved
views.frontend.common.src.utils.checkout.getBlocksCheckoutConfig→views.frontend.common.src.types.CheckoutConfigviews.frontend.common.src.utils.checkout.getClassicCheckoutConfig→views.frontend.common.src.types.CheckoutConfigviews.frontend.common.src.utils.checkout.useWcCartStore→views.frontend.common.src.types.UseWcStoreviews.frontend.common.src.utils.checkout.useWcCheckoutStore→views.frontend.common.src.types.UseWcStore
- Direction
- views.frontend.common.src.utils.checkout uses views.frontend.common.src.types, so a change to views.frontend.common.src.types can break views.frontend.common.src.utils.checkout, while a change to views.frontend.common.src.utils.checkout can't break views.frontend.common.src.types.
- Position
- Below the diagonal: views.frontend.common.src.utils.checkout uses a module listed above it, which is the healthy direction.
38→7 MyParcelNL.WooCommerce.Hooks uses MyParcelNL.WooCommerce.Hooks.Contract✕
- Connections
- 14 pairs of types, where a type in MyParcelNL.WooCommerce.Hooks uses a type in MyParcelNL.WooCommerce.Hooks.Contract.
- The types involved
MyParcelNL.WooCommerce.Hooks.AbstractFieldsHooks→MyParcelNL.WooCommerce.Hooks.Contract.WordPressHooksInterfaceMyParcelNL.WooCommerce.Hooks.AutomaticOrderExportHooks→MyParcelNL.WooCommerce.Hooks.Contract.WordPressHooksInterfaceMyParcelNL.WooCommerce.Hooks.BlocksIntegrationHooks→MyParcelNL.WooCommerce.Hooks.Contract.WordPressHooksInterfaceMyParcelNL.WooCommerce.Hooks.CartFeesHooks→MyParcelNL.WooCommerce.Hooks.Contract.WooCommerceInitCallbacksInterfaceMyParcelNL.WooCommerce.Hooks.CartFeesHooks→MyParcelNL.WooCommerce.Hooks.Contract.WordPressHooksInterfaceMyParcelNL.WooCommerce.Hooks.CheckoutScriptHooks→MyParcelNL.WooCommerce.Hooks.Contract.WordPressHooksInterfaceMyParcelNL.WooCommerce.Hooks.OrderNotesHooks→MyParcelNL.WooCommerce.Hooks.Contract.WordPressHooksInterfaceMyParcelNL.WooCommerce.Hooks.PluginInfoHooks→MyParcelNL.WooCommerce.Hooks.Contract.WordPressHooksInterfaceMyParcelNL.WooCommerce.Hooks.RanWebhookActions→MyParcelNL.WooCommerce.Hooks.Contract.WordPressHooksInterfaceMyParcelNL.WooCommerce.Hooks.ScheduledMigrationHooks→MyParcelNL.WooCommerce.Hooks.Contract.WordPressHooksInterfaceMyParcelNL.WooCommerce.Hooks.SeparateAddressFieldsHooks→MyParcelNL.WooCommerce.Hooks.Contract.WooCommerceInitCallbacksInterfaceMyParcelNL.WooCommerce.Hooks.TaxFieldsHooks→MyParcelNL.WooCommerce.Hooks.Contract.WooCommerceInitCallbacksInterfaceMyParcelNL.WooCommerce.Hooks.TrackTraceHooks→MyParcelNL.WooCommerce.Hooks.Contract.WordPressHooksInterfaceMyParcelNL.WooCommerce.Hooks.WebhookActions→MyParcelNL.WooCommerce.Hooks.Contract.WordPressHooksInterface
- Direction
- MyParcelNL.WooCommerce.Hooks uses MyParcelNL.WooCommerce.Hooks.Contract, so a change to MyParcelNL.WooCommerce.Hooks.Contract can break MyParcelNL.WooCommerce.Hooks, while a change to MyParcelNL.WooCommerce.Hooks can't break MyParcelNL.WooCommerce.Hooks.Contract.
- Position
- Below the diagonal: MyParcelNL.WooCommerce.Hooks uses a module listed above it, which is the healthy direction.
38→16 MyParcelNL.WooCommerce.Hooks uses MyParcelNL.WooCommerce.Pdk.Service✕
- Connections
- 2 pairs of types, where a type in MyParcelNL.WooCommerce.Hooks uses a type in MyParcelNL.WooCommerce.Pdk.Service.
- The types involved
MyParcelNL.WooCommerce.Hooks.CartFeesHooks→MyParcelNL.WooCommerce.Pdk.Service.WcShippingClassMatrixServiceMyParcelNL.WooCommerce.Hooks.CartFeesHooks→MyParcelNL.WooCommerce.Pdk.Service.WcTaxService
- Direction
- MyParcelNL.WooCommerce.Hooks uses MyParcelNL.WooCommerce.Pdk.Service, so a change to MyParcelNL.WooCommerce.Pdk.Service can break MyParcelNL.WooCommerce.Hooks, while a change to MyParcelNL.WooCommerce.Hooks can't break MyParcelNL.WooCommerce.Pdk.Service.
- Position
- Below the diagonal: MyParcelNL.WooCommerce.Hooks uses a module listed above it, which is the healthy direction.
38→19 MyParcelNL.WooCommerce.Hooks uses MyParcelNL.WooCommerce.WooCommerce.Contract✕
- Connections
- 1 pair of types, where a type in MyParcelNL.WooCommerce.Hooks uses a type in MyParcelNL.WooCommerce.WooCommerce.Contract.
- The types involved
MyParcelNL.WooCommerce.Hooks.AutomaticOrderExportHooks→MyParcelNL.WooCommerce.WooCommerce.Contract.WcOrderRepositoryInterface
- Direction
- MyParcelNL.WooCommerce.Hooks uses MyParcelNL.WooCommerce.WooCommerce.Contract, so a change to MyParcelNL.WooCommerce.WooCommerce.Contract can break MyParcelNL.WooCommerce.Hooks, while a change to MyParcelNL.WooCommerce.Hooks can't break MyParcelNL.WooCommerce.WooCommerce.Contract.
- Position
- Below the diagonal: MyParcelNL.WooCommerce.Hooks uses a module listed above it, which is the healthy direction.
38→35 MyParcelNL.WooCommerce.Hooks uses MyParcelNL.WooCommerce.Service✕
- Connections
- 1 pair of types, where a type in MyParcelNL.WooCommerce.Hooks uses a type in MyParcelNL.WooCommerce.Service.
- The types involved
MyParcelNL.WooCommerce.Hooks.CheckoutScriptHooks→MyParcelNL.WooCommerce.Service.WpScriptService
- Direction
- MyParcelNL.WooCommerce.Hooks uses MyParcelNL.WooCommerce.Service, so a change to MyParcelNL.WooCommerce.Service can break MyParcelNL.WooCommerce.Hooks, while a change to MyParcelNL.WooCommerce.Hooks can't break MyParcelNL.WooCommerce.Service.
- Position
- Below the diagonal: MyParcelNL.WooCommerce.Hooks uses a module listed above it, which is the healthy direction.
39→4 MyParcelNL.WooCommerce.Migration uses MyParcelNL.WooCommerce.Database.Contract✕
- Connections
- 1 pair of types, where a type in MyParcelNL.WooCommerce.Migration uses a type in MyParcelNL.WooCommerce.Database.Contract.
- The types involved
MyParcelNL.WooCommerce.Migration.Migration5_3_2→MyParcelNL.WooCommerce.Database.Contract.WpDatabaseServiceInterface
- Direction
- MyParcelNL.WooCommerce.Migration uses MyParcelNL.WooCommerce.Database.Contract, so a change to MyParcelNL.WooCommerce.Database.Contract can break MyParcelNL.WooCommerce.Migration, while a change to MyParcelNL.WooCommerce.Migration can't break MyParcelNL.WooCommerce.Database.Contract.
- Position
- Below the diagonal: MyParcelNL.WooCommerce.Migration uses a module listed above it, which is the healthy direction.
39→31 MyParcelNL.WooCommerce.Migration uses MyParcelNL.WooCommerce.Migration.Pdk✕
- Connections
- 5 pairs of types, where a type in MyParcelNL.WooCommerce.Migration uses a type in MyParcelNL.WooCommerce.Migration.Pdk.
- The types involved
MyParcelNL.WooCommerce.Migration.Migration5_0_0→MyParcelNL.WooCommerce.Migration.Pdk.AbstractPdkMigrationMyParcelNL.WooCommerce.Migration.Migration5_0_0→MyParcelNL.WooCommerce.Migration.Pdk.AuditsMigrationMyParcelNL.WooCommerce.Migration.Migration5_0_0→MyParcelNL.WooCommerce.Migration.Pdk.OrdersMigrationMyParcelNL.WooCommerce.Migration.Migration5_0_0→MyParcelNL.WooCommerce.Migration.Pdk.ProductSettingsMigrationMyParcelNL.WooCommerce.Migration.Migration5_0_0→MyParcelNL.WooCommerce.Migration.Pdk.SettingsMigration
- Direction
- MyParcelNL.WooCommerce.Migration uses MyParcelNL.WooCommerce.Migration.Pdk, so a change to MyParcelNL.WooCommerce.Migration.Pdk can break MyParcelNL.WooCommerce.Migration, while a change to MyParcelNL.WooCommerce.Migration can't break MyParcelNL.WooCommerce.Migration.Pdk.
- Position
- Below the diagonal: MyParcelNL.WooCommerce.Migration uses a module listed above it, which is the healthy direction.
40→7 MyParcelNL.WooCommerce.Pdk.Hooks uses MyParcelNL.WooCommerce.Hooks.Contract✕
- Connections
- 9 pairs of types, where a type in MyParcelNL.WooCommerce.Pdk.Hooks uses a type in MyParcelNL.WooCommerce.Hooks.Contract.
- The types involved
MyParcelNL.WooCommerce.Pdk.Hooks.AbstractPdkEndpointHooks→MyParcelNL.WooCommerce.Hooks.Contract.WordPressHooksInterfaceMyParcelNL.WooCommerce.Pdk.Hooks.PdkCheckoutPlaceOrderHooks→MyParcelNL.WooCommerce.Hooks.Contract.WordPressHooksInterfaceMyParcelNL.WooCommerce.Pdk.Hooks.PdkCoreHooks→MyParcelNL.WooCommerce.Hooks.Contract.WordPressHooksInterfaceMyParcelNL.WooCommerce.Pdk.Hooks.PdkEndpointHooks→MyParcelNL.WooCommerce.Hooks.Contract.WordPressHooksInterfaceMyParcelNL.WooCommerce.Pdk.Hooks.PdkOrderHooks→MyParcelNL.WooCommerce.Hooks.Contract.WordPressHooksInterfaceMyParcelNL.WooCommerce.Pdk.Hooks.PdkOrderListHooks→MyParcelNL.WooCommerce.Hooks.Contract.WordPressHooksInterfaceMyParcelNL.WooCommerce.Pdk.Hooks.PdkPluginSettingsHooks→MyParcelNL.WooCommerce.Hooks.Contract.WordPressHooksInterfaceMyParcelNL.WooCommerce.Pdk.Hooks.PdkProductSettingsHooks→MyParcelNL.WooCommerce.Hooks.Contract.WordPressHooksInterfaceMyParcelNL.WooCommerce.Pdk.Hooks.PdkWebhookHooks→MyParcelNL.WooCommerce.Hooks.Contract.WordPressHooksInterface
- Direction
- MyParcelNL.WooCommerce.Pdk.Hooks uses MyParcelNL.WooCommerce.Hooks.Contract, so a change to MyParcelNL.WooCommerce.Hooks.Contract can break MyParcelNL.WooCommerce.Pdk.Hooks, while a change to MyParcelNL.WooCommerce.Pdk.Hooks can't break MyParcelNL.WooCommerce.Hooks.Contract.
- Position
- Below the diagonal: MyParcelNL.WooCommerce.Pdk.Hooks uses a module listed above it, which is the healthy direction.
40→19 MyParcelNL.WooCommerce.Pdk.Hooks uses MyParcelNL.WooCommerce.WooCommerce.Contract✕
- Connections
- 2 pairs of types, where a type in MyParcelNL.WooCommerce.Pdk.Hooks uses a type in MyParcelNL.WooCommerce.WooCommerce.Contract.
- The types involved
MyParcelNL.WooCommerce.Pdk.Hooks.PdkOrderHooks→MyParcelNL.WooCommerce.WooCommerce.Contract.WcOrderRepositoryInterfaceMyParcelNL.WooCommerce.Pdk.Hooks.PdkOrderListHooks→MyParcelNL.WooCommerce.WooCommerce.Contract.WcOrderRepositoryInterface
- Direction
- MyParcelNL.WooCommerce.Pdk.Hooks uses MyParcelNL.WooCommerce.WooCommerce.Contract, so a change to MyParcelNL.WooCommerce.WooCommerce.Contract can break MyParcelNL.WooCommerce.Pdk.Hooks, while a change to MyParcelNL.WooCommerce.Pdk.Hooks can't break MyParcelNL.WooCommerce.WooCommerce.Contract.
- Position
- Below the diagonal: MyParcelNL.WooCommerce.Pdk.Hooks uses a module listed above it, which is the healthy direction.
40→35 MyParcelNL.WooCommerce.Pdk.Hooks uses MyParcelNL.WooCommerce.Service✕
- Connections
- 1 pair of types, where a type in MyParcelNL.WooCommerce.Pdk.Hooks uses a type in MyParcelNL.WooCommerce.Service.
- The types involved
MyParcelNL.WooCommerce.Pdk.Hooks.PdkCoreHooks→MyParcelNL.WooCommerce.Service.WpScriptService
- Direction
- MyParcelNL.WooCommerce.Pdk.Hooks uses MyParcelNL.WooCommerce.Service, so a change to MyParcelNL.WooCommerce.Service can break MyParcelNL.WooCommerce.Pdk.Hooks, while a change to MyParcelNL.WooCommerce.Pdk.Hooks can't break MyParcelNL.WooCommerce.Service.
- Position
- Below the diagonal: MyParcelNL.WooCommerce.Pdk.Hooks uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 70 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 33 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
| A02:2025 — Security Misconfiguration | 2 | Medium |
Roadmap
Top priorities: 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; Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; 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 this | Helps | Effort | Dimension |
|---|---|---|---|
| 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. | +7.4 pts | Medium | Text alternatives |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +4.9 pts | Medium | Keyboard semantics |
| 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. | +3.0 pts | Medium | Visual & motion safety |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +2.9 pts | Medium | Dependency Hygiene |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +2.4 pts | Medium | Forms & labels |
| Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element. | +2.1 pts | Medium | ARIA correctness |
| 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. | +1.5 pts | Medium | Architecture documentation |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +1.4 pts | Medium | Deployment & Rollback |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.2 | Slop | Dependency Vulnerabilities: High 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.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 6.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| src/Hooks/SeparateAddressFieldsHooks.php | 7.2 | Mixed | Code Duplication: Edited copy of a member (22 corresponding lines) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 65 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 65 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 190 of 208 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .ts, .tsx, .php, and our analyzer cannot run the .php test suite(s) — so no coverage was collected for the repository as a whole. The JavaScript/TypeScript half did build and run, and its own line coverage came back at 88.7% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
- D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 42 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 112 test source file(s) (.php) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT SCORED: this repository's production source includes .php, and the built-in reliability runner cannot re-run the .php test suite(s) — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (vitest via `yarn install --immutable --mode=skip-build` in the repository root (159 tests); vitest via `yarn install --immutable --mode=skip-build` in views/vite-config/ (4 tests)): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its Composer package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (composer.json), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `views/frontend/common/src/index.ts`, `views/frontend/common/src/utils/checkout/getBlocksCheckoutConfig.ts`, `views/frontend/common/src/utils/checkout/getClassicCheckoutConfig.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D34 Knowledge Freshness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 100 commits in the last 90 days, yet 38 of 57 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 1 — a container did not start, exited, or never became healthy) — container .-test-1 exited (1); runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. '$wpdb' is imported (src/Migration/2026_08_04_101714_restore_v6_options.php:39), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C2 Access Controls — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. '$wpdb' is imported (src/Migration/2026_08_04_101714_restore_v6_options.php:39), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. '$wpdb' is imported (src/Migration/2026_08_04_101714_restore_v6_options.php:39), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. '$wpdb' is imported (src/Migration/2026_08_04_101714_restore_v6_options.php:39), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's PHP, Vue components 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's PHP, Vue components 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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security 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 web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X27 Collection changed while being enumerated — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- 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.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- 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 Complexity
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Migration6_5_1.normalizeCarrierOn at 18.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Migration6_5_1.normalizeCarrierOn (cyclomatic 18), WcContextService.resolveHighestShippingClass (cyclomatic 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
3 method(s) exceeded the cognitive complexity threshold of 15; the worst was Migration6_5_1.normalizeCarrierOn at 23.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cognitive Complexity — start with Migration6_5_1.normalizeCarrierOn (cognitive 23), WcContextService.resolveHighestShippingClass (cognitive 21), WcContextService.createCheckoutContext (cognitive 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 9.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with SettingsMigration.php, WcPdkBootstrapper.php. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
4 duplicated block group(s) detected. 1.6 % of the production lines (184 of 11,481) are in a reported copy. A further 2 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 1 Edited copy of a member (22 corresponding lines) finding(s) in Code Duplication — start with SeparateAddressFieldsHooks.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (26 corresponding lines) finding(s) in Code Duplication — start with OrdersMigration.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (32–33 lines × 2) finding(s) in Code Duplication — start with SeparateAddressFieldsHooks.php. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
11 production modules (npm+Composer), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 8 of the 11 (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).
D6 · Cohesion (LCOM4)
3 of 27 classes have LCOM4 above 3.
What to do
- Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with CartFeesHooks.php, AbstractUpgradeMigration.php, PdkOrderListHooks.php. — One of this dimension's main actionable groups (3 warning-level).
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 42 tests. Measured on the JavaScript/TypeScript suite only — at least 112 test source file(s) (.php) went unread, so its test quality is unmeasured and is not in these counts.
D12 · Dependency Hygiene
3 outdated, 0 abandoned direct Composer dependencies. PLATFORM requirements (php, ext-*, lib-*) are deliberately not graded here: they name the runtime rather than a Packagist package, so there is no release for them to be behind — whether that runtime is still supported is a separate question with a separate remedy. Development requirements are excluded, because a consumer never installs them. A newer release is reported only where this repository's OWN constraint already admits it, so the remedy is `composer update` and never a manifest edit. Known CVEs in this dependency graph are D30's question.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 20 locked Composer package(s) use a banned license. Licences were read from this repository's composer.lock, which records the `license` each package declares, over every package in its production `packages` list, direct and transitive, at the locked version; the 60 package(s) under `packages-dev` are not installed for a consumer and are excluded. ★ COVERAGE OF THIS VERDICT: it grades this repository's Composer package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: src/Migration/Migration6_5_1.php (4×18=72); src/Pdk/Context/Service/WcContextService.php (2×17=34)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with Migration6_5_1.php, WcContextService.php. — One of this dimension's main actionable groups (2 warning-level).
D16 · Bus Factor
3 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/Pdk/Product/Repository/WcPdkProductRepository.php. Counted over 57 of the 151 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
4 deducted task-comment markers across 11481 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 4 TodoComment finding(s) in Explicit Debt — start with WpScriptService.php (2), MockWcBlocksUtils.php, functions.php. — One of this dimension's main actionable groups (4 warning-level).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 3 document(s) read across 11 unit(s).
D24 · Comment Value
0 of 54 judged comments only repeat the code they sit on (0.0 %). 1 comment(s) in another language or script were not judged.
D26 · Project Cohesion
1 of 11 build units (npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with package.json. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
22 % of calls cross a namespace and 0 % go through an interface, but 26 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
70 finding(s): 0 critical, 70 high, 0 medium, 0 low. 32 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 3 file(s) — `views/frontend/common/src/index.ts` (line 1), `views/frontend/common/src/utils/checkout/getBlocksCheckoutConfig.ts` (line 163), `views/frontend/common/src/utils/checkout/getClassicCheckoutConfig.ts` (line 164) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 22 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (22 issue-level).
- Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (12 issue-level).
- No action in Static Analysis (SAST) — all 30 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (30 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
17 finding(s): 0 critical, 3 high, 13 medium, 1 low.
What to do
- Resolve the 13 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (13). — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
2 finding(s): 0 critical, 0 high, 2 medium, 0 low.
What to do
- 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).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 9 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (9 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 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 4 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — views/backend/admin/src/components/pdk/WcImage.vue:2
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.
AC2 · Forms & labels
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×3) — views/backend/admin/src/components/pdk/WcSelectInput.vue:2, views/backend/admin/src/components/pdk/WcTextArea.vue:2, views/backend/admin/src/components/pdk/WcTextInput.vue:2
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.
AC4 · Keyboard semantics
- This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — views/backend/admin/src/components/pdk/WcModal.vue:2
- 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. — views/backend/admin/src/components/pdk/WcToggleInput.vue:8
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
- The switch role requires aria-checked to convey its state. Add it. — views/backend/admin/src/components/pdk/WcToggleInput.vue:20
What to do
- Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
AC6 · Visual & motion safety
- `.woocommerce-input-toggle:before` moves (`transition: transform 0.2s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — views/backend/admin/src/assets/scss/_toggle.scss:6
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.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
C2 · Access Controls
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
What to do
- Name the access rules — Gate abilities and policy classes (Gate::define, a UserPolicy), spatie/laravel-permission roles and permissions, or a Symfony Voter — and consult them where access is checked ($this->authorize, a can: middleware, #[IsGranted]), so the rule set is reviewable and testable on its own.
M1 · Documentation (README)
M2 · Architecture documentation
- 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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
P8 · Schema migrations
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- views/frontend/checkout-address-widget/src/utils/showHide.ts:6 · views/frontend/checkout-address-widget/src/utils/showHide.ts:24 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — views/frontend/checkout-address-widget/src/utils/showHide.ts:6
- views/backend/admin/src/components/pdk/WcRadioInput.vue:38 · views/backend/admin/src/components/pdk/WcTextArea.vue:15 — the two spans are one implementation copied and then locally edited — 81 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — views/backend/admin/src/components/pdk/WcRadioInput.vue:38
- views/backend/admin/src/components/pdk/WcRadioInput.vue:39 · views/backend/admin/src/components/pdk/WcTextInput.vue:18 — the two spans are one implementation copied and then locally edited — 66 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — views/backend/admin/src/components/pdk/WcRadioInput.vue:39
- views/backend/admin/src/components/pdk/WcTextArea.vue:16 · views/backend/admin/src/components/pdk/WcTextInput.vue:18 — the two spans are one implementation copied and then locally edited — 68 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — views/backend/admin/src/components/pdk/WcTextArea.vue:16
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries
- views/frontend/common/src/types.ts:2 imports @wordpress/data/src/types, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — views/frontend/common/src/types.ts:2
- views/vite-config/index.d.ts:1 imports vitest/dist/config, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — views/vite-config/index.d.ts:1
What to do
- Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×29) — views/blocks/delivery-options/src/frontend.tsx:1, views/frontend/checkout-address-widget/src/utils/syncData.ts:1, views/backend/admin/src/initialize.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
- test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
- the root package is TypeScript, but a type error in it cannot fail anything this repository runs: its `ws:build` script (`vite build`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. Add a type check that can fail — a `typecheck` script running `tsc --noEmit` (or `vue-tsc`/`svelte-check`) that CI or the workspace pipeline runs, or a build step that checks before it bundles. — package.json:48
What to do
- Add `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code
- 4 file(s) (~183 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
- Unreachable from the 25 application, 19 tooling and 7 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 (25 application, 19 tooling, 7 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 — views/vite-config/test-setup.ts
- Nothing imports this binding — it is safe to review for removal. — views/frontend/checkout-address-widget/src/constants/fields.ts:24
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×7) — views/backend/admin/src/components/pdk/WcCheckboxInput.vue:28, views/frontend/checkout-address-widget/src/utils/init.ts:14, views/frontend/checkout-core/src/main.ts:7, …
- Declared in the root package.json 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. (×2) — package.json:90, package.json:103
- Declared in views/backend/admin/package.json 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. (×2) — views/backend/admin/package.json:20, views/backend/admin/package.json:28
- Declared in views/blocks/delivery-options/package.json but never imported anywhere in that package or its workspace members — while views/frontend/common/src/utils/checkout/getBlocksCheckoutConfig.ts DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it. — views/blocks/delivery-options/package.json:17
- Declared in views/frontend/checkout-delivery-options/package.json 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. — views/frontend/checkout-delivery-options/package.json:17
- Declared in views/frontend/checkout-separate-address-fields/package.json 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. — views/frontend/checkout-separate-address-fields/package.json:17
- Declared in views/frontend/checkout-tax-fields/package.json 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. — views/frontend/checkout-tax-fields/package.json:17
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- views/frontend/checkout-address-widget/src/utils/init.ts → views/frontend/checkout-address-widget/src/utils/syncData.ts → views/frontend/checkout-address-widget/src/utils/init.ts — views/frontend/checkout-address-widget/src/utils/init.ts:16
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
X16 · Unfloored truncation loop
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `doRequest` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — views/frontend/checkout-core/src/main.ts:53
What to do
- Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X4 · Structured logging
X5 · Nullable reference types
- 0/1 of this repository's PHPStan/Psalm configuration(s) run at a level that checks null — PHPStan level 8 or above (`max` included), or Psalm `errorLevel` 3 or below (Psalm's default, with none stated, is 1). A PHPStan level written neither in the file nor in an include inside the repository is 0, PHPStan's own default. Below those levels the checker removes `null` from a union before any rule looks, so `$order->customer()->name()` on a `?Customer` passes, and the first null reaching it is an `Error: Call to a member function name() on null` in production.
What to do
- Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
WCAG coverage — what static analysis assessed
| 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 |
| 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 |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 65.1 | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 86.0 | Strong | Solid. |
| Maturity | 60.6 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 51.7 | Adequate — gated by R8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 62.9 | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 30.4 | Weak — gated by AC1, AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through '$wpdb' (src/Migration/2026_08_04_101714_restore_v6_options.php:39) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through '$wpdb' (src/Migration/2026_08_04_101714_restore_v6_options.php:39) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through '$wpdb' (src/Migration/2026_08_04_101714_restore_v6_options.php:39) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 57 check(s) not relevant to this codebase
- AC3 Page structure — No structural check found in the parsed markup — AC3 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's PHP 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 — Not applicable: PHP builds its object graph per request and shares none of it between requests. 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
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 1 — a container did not start, exited, or never became healthy) — container .-test-1 exited (1); runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: this repository stores data through '$wpdb' (src/Migration/2026_08_04_101714_restore_v6_options.php:39) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
- D11 Test Reliability — Test reliability not scored — polyglot repository, one half has no runner
- 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.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 3 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- 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
- D8 Code Coverage — Coverage not measured — polyglot repository, one half has no runner
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- 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, Scala, Rust and Java, 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
- P2 Observability — This repository's JavaScript/TypeScript, PHP source (12 module(s), 158 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript, PHP source (service entry point: woocommerce-myparcel.php:51 (add_action())
- P9 Domain vs controller coverage — coverage data present for 40 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 PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — Not assessed: these web-security 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 web-security 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — X1 reached only 22% of this repository's production lines — php (9,661 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X12 Unreachable branch — X12 reached only 22% of this repository's production lines — php (9,661 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — X24 reached only 22% of this repository's production lines — php (9,661 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 87 finding(s)
- 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
- 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
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unlisted import '@myparcel-dev/pdk-checkout-common' views/frontend/checkout-core/src/main.ts:7
- Unlisted import '@myparcel-dev/pdk-checkout-common' views/frontend/checkout-separate-address-fields/src/main.ts:8
- Unlisted import '@myparcel-dev/pdk-checkout-common' views/frontend/common/src/types.ts:4
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unlisted import '@myparcel-dev/pdk-common' views/frontend/checkout-address-widget/src/utils/init.ts:14
- Unlisted import '@myparcel-dev/pdk-common' views/frontend/checkout-delivery-options/src/utils/init.ts:1
- <img> without a text alternative views/backend/admin/src/components/pdk/WcImage.vue:2
- <select> without a programmatic label views/backend/admin/src/components/pdk/WcSelectInput.vue:2
- <textarea> without a programmatic label views/backend/admin/src/components/pdk/WcTextArea.vue:2
- <input> without a programmatic label views/backend/admin/src/components/pdk/WcTextInput.vue:2
- role="switch" missing required aria-checked views/backend/admin/src/components/pdk/WcToggleInput.vue:20
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unlisted import '@vueuse/core' views/backend/admin/src/components/pdk/WcCheckboxInput.vue:28
- Unlisted import '@myparcel-dev/pdk-checkout' views/frontend/common/src/utils/checkout/getBlocksCheckoutConfig.ts:8
- Import cycle (2 files) views/frontend/checkout-address-widget/src/utils/init.ts:16
Serious — 101 finding(s)
- No test reaches this file views/blocks/delivery-options/src/frontend.tsx:1
- No test reaches this file views/frontend/checkout-address-widget/src/utils/syncData.ts:1
- No test reaches this file views/backend/admin/src/initialize.ts:1
- No test reaches this file views/frontend/checkout-address-widget/src/utils/init.ts:1
- No test reaches this file views/frontend/checkout-separate-address-fields/src/main.ts:1
- No test reaches this file views/frontend/checkout-core/src/main.ts:1
- No test reaches this file views/webpack-config/index.js:1
- No test reaches this file views/frontend/checkout-address-widget/src/utils/showHide.ts:1
- No test reaches this file views/backend/admin/src/components/pdk/WcChildProductSettingsFormGroup.vue:1
- No test reaches this file views/backend/admin/src/components/pdk/WcProductSettingsFormGroup.vue:1
- No test reaches this file views/backend/admin/src/hooks/listenForBulkActions.ts:1
- No test reaches this file views/frontend/checkout-core/src/utils/hideSeparateFields.ts:1
- No test reaches this file views/frontend/checkout-address-widget/src/constants/fields.ts:1
- No test reaches this file views/vite-config/test-setup.ts:1
- No test reaches this file views/backend/admin/src/hooks/closeModalOnEscape.ts:1
- No test reaches this file views/blocks/delivery-options/src/edit.tsx:1
- No test reaches this file views/blocks/delivery-options/src/index.tsx:1
- No test reaches this file views/blocks/delivery-options/src/save.tsx:1
- No test reaches this file views/frontend/checkout-core/src/utils/createFields.ts:1
- No test reaches this file views/frontend/common/src/utils/checkout/useWcCheckoutStore.ts:1
- No test reaches this file views/frontend/common/src/data/events/woocommerce.ts:1
- No test reaches this file views/frontend/checkout-address-widget/src/main.ts:1
- No test reaches this file views/frontend/checkout-delivery-options/src/main.ts:1
- No test reaches this file views/backend/admin/src/main.ts:1
- No test reaches this file views/frontend/checkout-tax-fields/src/main.ts:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment tests/Mock/MockWcBlocksUtils.php:21
- TodoComment src/functions.php:27
- TodoComment src/Service/WpScriptService.php:124
- TodoComment src/Service/WpScriptService.php:133
- Low cohesion: CartFeesHooks (LCOM4 5) src/Hooks/CartFeesHooks.php:35
- Low cohesion: AbstractUpgradeMigration (LCOM4 5) src/Migration/AbstractUpgradeMigration.php:11
- Low cohesion: PdkOrderListHooks (LCOM4 4) src/Pdk/Hooks/PdkOrderListHooks.php:17
- Unused dependency '@myparcel-dev/ts-utils' views/frontend/checkout-delivery-options/package.json:17
- Unused dependency '@myparcel-dev/ts-utils' views/frontend/checkout-separate-address-fields/package.json:17
- Unused dependency '@myparcel-dev/ts-utils' views/frontend/checkout-tax-fields/package.json:17
- Hotspot: src/Migration/Migration6_5_1.php src/Migration/Migration6_5_1.php:289
- Hotspot: src/Pdk/Context/Service/WcContextService.php src/Pdk/Context/Service/WcContextService.php:104
- MethodTooLong: SettingsMigration.getTransformationMap src/Migration/Pdk/SettingsMigration.php:257
- MethodTooLong: WcPdkBootstrapper.getAdditionalConfig src/Pdk/WcPdkBootstrapper.php:36
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block with local edits (5 matched lines × 2 locations) views/backend/admin/src/components/pdk/WcRadioInput.vue:39
- Duplicated block with local edits (5 matched lines × 2 locations) views/backend/admin/src/components/pdk/WcTextArea.vue:16
- Boundary violation [package:third-party-deep-import] views/frontend/common/src/types.ts:2
- Boundary violation [package:third-party-deep-import] views/vite-config/index.d.ts:1
- Modal dialog does not manage focus views/backend/admin/src/components/pdk/WcModal.vue:2
- Anchor without href views/backend/admin/src/components/pdk/WcToggleInput.vue:8
- Animation without a prefers-reduced-motion guard views/backend/admin/src/assets/scss/_toggle.scss:6
- Migration6_5_1.normalizeCarrierOn (cyclomatic 18) src/Migration/Migration6_5_1.php:289
- WcContextService.resolveHighestShippingClass (cyclomatic 17) src/Pdk/Context/Service/WcContextService.php:104
- Migration6_5_1.normalizeCarrierOn (cognitive 23) src/Migration/Migration6_5_1.php:289
- WcContextService.resolveHighestShippingClass (cognitive 21) src/Pdk/Context/Service/WcContextService.php:104
- WcContextService.createCheckoutContext (cognitive 18) src/Pdk/Context/Service/WcContextService.php:27
- REDACTED
- REDACTED
- Edited copy of a member (22 corresponding lines) src/Hooks/SeparateAddressFieldsHooks.php:54
- Edited copy of a member (26 corresponding lines) src/Migration/Pdk/OrdersMigration.php:80
- Duplicated block (32–33 lines × 2) src/Hooks/SeparateAddressFieldsHooks.php:312
- Duplicated block (20–21 lines × 2) src/Hooks/SeparateAddressFieldsHooks.php:162
- Duplicated block (17–19 lines × 2) src/Hooks/SeparateAddressFieldsHooks.php:54
- Duplicated block (9 lines × 2) src/Pdk/Plugin/Action/WcBackendEndpointService.php:17
- Coverage collected but not gated
- Duplicated block (15 lines × 2 locations) views/frontend/checkout-address-widget/src/utils/showHide.ts:6
- Duplicated block with local edits (6 matched lines × 2 locations) views/backend/admin/src/components/pdk/WcRadioInput.vue:38
- No typecheck script
- Type errors in this package cannot fail any build or CI step package.json:48
- Dead file (~24 LoC) views/vite-config/test-setup.ts
- Unused dependency 'array.prototype.flatmap' package.json:90
- Unused dependency 'semantic-release' package.json:103
- Unused dependency '@tanstack/vue-query' views/backend/admin/package.json:20
- Unused dependency '@vue/test-utils' views/backend/admin/package.json:28
- Unused dependency '@myparcel-dev/pdk-checkout' views/blocks/delivery-options/package.json:17
- Async function without AbortSignal: doRequest views/frontend/checkout-core/src/main.ts:53
Minor — 15 finding(s)
- No named authorization policies
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Projects may be oversized for their cohesion package.json:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Unused export 'WOOC_COUNTRY_FIELD' views/frontend/checkout-address-widget/src/constants/fields.ts:24
- Duplicated predicate views/frontend/common/src/utils/checkout/getBlocksCheckoutConfig.ts:49
- Not all async functions that make a request accept an AbortSignal
- PHP static analysis does not check null everywhere
Minor — 5 finding(s)
- Outdated: myparcelnl/pdk
- Outdated: myparcelnl/sdk
- Outdated: psr/log
- doc comments repeat the names views/frontend/checkout-address-widget/src/utils/showHide.ts:28
- Off the main sequence: @myparcel-woocommerce/frontend-common
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-87255bc876374e3293c9ec8c438e0a29/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-87255bc876374e3293c9ec8c438e0a29/history-1.json --exit-code 0 --source . | 7 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=3200" --report-format json --report-path /tmp/watchdog-gitleaks-87255bc876374e3293c9ec8c438e0a29/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=4200 --max-count=98" --report-format json --report-path /tmp/watchdog-gitleaks-87255bc876374e3293c9ec8c438e0a29/history-3.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-3.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-87255bc876374e3293c9ec8c438e0a29/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 70 | 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/** . | 17 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 2 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 3 file(s) — `views/frontend/common/src/index.ts`, `views/frontend/common/src/utils/checkout/getBlocksCheckoutConfig.ts`, `views/frontend/common/src/utils/checkout/getClassicCheckoutConfig.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |