Executive summary
ahaodev/shadmin falls short of our standard for a preview release because its Security dimensions are rated Critical, and nine passwords or keys sit in the current code. It scores 53 out of 100, which alone would earn Adequate, but it is rated Weak: a rating can't sit more than one step above its weakest group.
Production Readiness, at 36, is the weakest lens and counts most in the score. The best first step is replacing the nine exposed passwords or keys and switching the old ones off, worth about 15 points. Documenting the recovery plan comes next, worth about 6 points. Raising Production Readiness to 62 would lift the score to about 65.
Nine passwords or keys in the code and eight in the code's history are open to anyone who can read the repository. Nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and four settings leave the servers or containers unsafe. Replacing each exposed password or key, pinning each tool to an exact version and correcting the unsafe settings would close these risks. Limiting each secret to its own step would fix the two secrets exposed to more of the pipeline than needed, and the pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions.
The product code is 13,809 lines, about €20,000 to rebuild.
If Production Readiness rose from 36 to 62, the lowest score rated Strong, the score would rise from 53 to about 65.
New since the last survey: 2 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 60 findings
- Cyclomatic Complexity · Env.validate (cyclomatic 44) REDACTED
- Cyclomatic Complexity · Client.doWithRetry (cyclomatic 27) cli/internal/client/client.go
- Cyclomatic Complexity · loginLogUsecase.parseUserAgent (cyclomatic 23) usecase/loginlog_usecase.go
- Cyclomatic Complexity · deviceAuthUsecase.PollToken (cyclomatic 20) usecase/device_auth_usecase.go
- Cyclomatic Complexity · entUserRepository.Query (cyclomatic 19) repository/user_repository.go
- Cyclomatic Complexity · departmentUsecase.Update (cyclomatic 18) usecase/department_usecase.go
- Cyclomatic Complexity · entUserInvitationRepository.CreateOrRotate (cyclomatic 17) repository/user_invitation_repository.go
- Cyclomatic Complexity · entDictRepository.UpdateItem (cyclomatic 16) repository/dict_repository.go
- Cognitive Complexity · Env.validate (cognitive 45) REDACTED
- Cognitive Complexity · departmentUsecase.Update (cognitive 30) usecase/department_usecase.go
- Cognitive Complexity · Client.doWithRetry (cognitive 29) cli/internal/client/client.go
- Cognitive Complexity · deviceAuthUsecase.PollToken (cognitive 27) usecase/device_auth_usecase.go
- Cognitive Complexity · entUserRepository.Query (cognitive 26) repository/user_repository.go
- Cognitive Complexity · cmd.printObjects (cognitive 22) cli/cmd/resources.go
- Cognitive Complexity · LoginLogController.GetLoginLogs (cognitive 22) api/controller/loginlog_controller.go
- Cognitive Complexity · entDictRepository.UpdateItem (cognitive 21) repository/dict_repository.go
- Cognitive Complexity · entUserInvitationRepository.CreateOrRotate (cognitive 20) repository/user_invitation_repository.go
- Cognitive Complexity · bootstrap.restoreMenuApiResourceAssociations (cognitive 19) bootstrap/api_resources_init.go
- Cognitive Complexity · redisCache.Iterator (cognitive 19) internal/cacher/redis.go
- Cognitive Complexity · entUserRepository.update (cognitive 18) repository/user_repository.go
- Cognitive Complexity · config.Save (cognitive 17) cli/internal/config/config.go
- Cognitive Complexity · SyncService.rebuildLocked (cognitive 17) internal/casbin/sync.go
- Cognitive Complexity · loginUsecase.Refresh (cognitive 16) usecase/login_usecase.go
- God Classes · TooManyFields: Env REDACTED
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) ent/schema/dict_item.go
- Code Duplication · Duplicated block (14 lines × 2) ent/schema/dict_item.go
- Code Duplication · Duplicated block (13 lines × 3) cli/cmd/resources.go
- Code Duplication · Duplicated block (13 lines × 2) api/controller/dict_controller.go
- Code Duplication · Duplicated block (12 lines × 2) repository/dict_repository.go
- Code Duplication · Duplicated block (11 lines × 2) api/controller/dict_controller.go
- Code Duplication · Duplicated block (11 lines × 2) repository/menu_repository.go
- Code Duplication · Duplicated block (10 lines × 2) pkg/logger.go
- Code Duplication · Duplicated block (9 lines × 2) api/controller/menu_controller.go
- Code Duplication · Duplicated block (9 lines × 2) usecase/menu_usecase.go
- Code Duplication · Duplicated block (8 lines × 2) api/controller/dict_controller.go
- Code Duplication · Duplicated block (8 lines × 2) usecase/login_usecase.go
- Code Duplication · Duplicated block (7 lines × 2) usecase/resource_usecase.go
- Code Duplication · Duplicated block (5 lines × 2) usecase/login_usecase.go
- Code Duplication · Duplicated block (11 lines × 2) api/middleware/casbin_middleware.go
- Code Duplication · Duplicated block (10 lines × 2) repository/role_repository.go
- Code Duplication · Duplicated block (8 lines × 4) ent/schema/dict_item.go
- Code Duplication · Duplicated block (9 lines × 2) api/controller/dict_controller.go
- Code Duplication · Duplicated block (7 lines × 2) bootstrap/api_resources_init.go
- Dependency Hygiene · Dependency pinned to a stale untagged commit: github.com/lestrrat/go-file-rotatelogs
- Dependency Hygiene · Dependency pinned to a stale untagged commit: github.com/rifflock/lfshook
- Churn × Complexity Hotspots · Hotspot: REDACTED REDACTED
- Churn × Complexity Hotspots · Hotspot: repository/user_repository.go repository/user_repository.go
- Churn × Complexity Hotspots · Hotspot: usecase/device_auth_usecase.go usecase/device_auth_usecase.go
- Churn × Complexity Hotspots · Hotspot: usecase/department_usecase.go usecase/department_usecase.go
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: GO-2026-6599 cli/REDACTED
- Dependency Vulnerabilities · Medium CVE: GO-2026-6603 REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
- Exception handling · Swallowed exception (caught, then discarded) internal/contextutil/context_util.go
Rebuild cost: about €20,000 · Estimate
| Cost to rebuild | €6,500 to €33,000, for 108 to 342 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 53. 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: 13,809 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: which parts of the code depend on which
| uses → | 1 frontend.src.components.icon-picker | 2 frontend.src.components.sign-out-dialog | 3 frontend.src.components.ui.scroll-area | 4 frontend.src.features.auth.sign-in.components.user-auth-form | 5 frontend.src.features.system.api-resources.components.api-resources-provider | 6 frontend.src.features.system.departments.components.departments-action-dialog | 7 frontend.src.features.system.departments.components.departments-columns | 8 frontend.src.features.system.departments.components.departments-delete-dialog | 9 frontend.src.features.system.departments.components.departments-provider | 10 frontend.src.features.system.departments.hooks.use-department-form | 11 frontend.src.features.system.dicts.components.data-table-bulk-actions | 12 frontend.src.features.system.menus.components | 13 frontend.src.features.system.menus.components.form-sections | 14 frontend.src.lib.menu-utils | 15 frontend.src.services.apiResourceApi | 16 frontend.src.types.api | 17 frontend.src.types.dict | 18 frontend.src.types.layout | 19 frontend.src.types.menu | 20 shadmin-cli/internal/config | 21 frontend.src.components | 22 frontend.src.components.data-table | 23 frontend.src.components.layout | 24 frontend.src.components.ui | 25 frontend.src.features.auth.sign-in.components | 26 frontend.src.features.system.api-resources.components | 27 frontend.src.features.system.api-resources.hooks | 28 frontend.src.features.system.departments.components | 29 frontend.src.features.system.departments.hooks | 30 frontend.src.features.system.dicts.components | 31 frontend.src.features.system.menus.hooks | 32 frontend.src.features.system.menus.utils | 33 frontend.src.features.system.roles.components.menu-tree-section | 34 frontend.src.features.system.users.components | 35 frontend.src.features.system.users.hooks | 36 frontend.src.lib | 37 frontend.src.services | 38 shadmin-cli/internal/client | 39 frontend.src.features.system.roles.components | 40 shadmin-cli/cmd |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 frontend.src.components.icon-picker | ||||||||||||||||||||||||||||||||||||||||
| 2 frontend.src.components.sign-out-dialog | ||||||||||||||||||||||||||||||||||||||||
| 3 frontend.src.components.ui.scroll-area | ||||||||||||||||||||||||||||||||||||||||
| 4 frontend.src.features.auth.sign-in.components.user-auth-form | ||||||||||||||||||||||||||||||||||||||||
| 5 frontend.src.features.system.api-resources.components.api-resources-provider | ||||||||||||||||||||||||||||||||||||||||
| 6 frontend.src.features.system.departments.components.departments-action-dialog | ||||||||||||||||||||||||||||||||||||||||
| 7 frontend.src.features.system.departments.components.departments-columns | ||||||||||||||||||||||||||||||||||||||||
| 8 frontend.src.features.system.departments.components.departments-delete-dialog | ||||||||||||||||||||||||||||||||||||||||
| 9 frontend.src.features.system.departments.components.departments-provider | ||||||||||||||||||||||||||||||||||||||||
| 10 frontend.src.features.system.departments.hooks.use-department-form | ||||||||||||||||||||||||||||||||||||||||
| 11 frontend.src.features.system.dicts.components.data-table-bulk-actions | ||||||||||||||||||||||||||||||||||||||||
| 12 frontend.src.features.system.menus.components | ||||||||||||||||||||||||||||||||||||||||
| 13 frontend.src.features.system.menus.components.form-sections | ||||||||||||||||||||||||||||||||||||||||
| 14 frontend.src.lib.menu-utils | ||||||||||||||||||||||||||||||||||||||||
| 15 frontend.src.services.apiResourceApi | ||||||||||||||||||||||||||||||||||||||||
| 16 frontend.src.types.api | ||||||||||||||||||||||||||||||||||||||||
| 17 frontend.src.types.dict | ||||||||||||||||||||||||||||||||||||||||
| 18 frontend.src.types.layout | ||||||||||||||||||||||||||||||||||||||||
| 19 frontend.src.types.menu | ||||||||||||||||||||||||||||||||||||||||
| 20 shadmin-cli/internal/config | ||||||||||||||||||||||||||||||||||||||||
| 21 frontend.src.components | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 frontend.src.components.data-table | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 frontend.src.components.layout | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 frontend.src.components.ui | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 frontend.src.features.auth.sign-in.components | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 frontend.src.features.system.api-resources.components | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 frontend.src.features.system.api-resources.hooks | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 frontend.src.features.system.departments.components | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 frontend.src.features.system.departments.hooks | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 frontend.src.features.system.dicts.components | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 frontend.src.features.system.menus.hooks | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 frontend.src.features.system.menus.utils | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 frontend.src.features.system.roles.components.menu-tree-section | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 frontend.src.features.system.users.components | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 frontend.src.features.system.users.hooks | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 frontend.src.lib | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 frontend.src.services | 2 | 3 | 8 | 6 | ||||||||||||||||||||||||||||||||||||
| 38 shadmin-cli/internal/client | 2 | |||||||||||||||||||||||||||||||||||||||
| 39 frontend.src.features.system.roles.components | 3 | |||||||||||||||||||||||||||||||||||||||
| 40 shadmin-cli/cmd | 1 | 4 |
21→1 frontend.src.components uses frontend.src.components.icon-picker✕
- Connections
- 1 pair of types, where a type in frontend.src.components uses a type in frontend.src.components.icon-picker.
- The types involved
frontend.src.components.icon-picker→frontend.src.components.icon-picker.IconPickerProps
- Direction
- frontend.src.components uses frontend.src.components.icon-picker, so a change to frontend.src.components.icon-picker can break frontend.src.components, while a change to frontend.src.components can't break frontend.src.components.icon-picker.
- Position
- Below the diagonal: frontend.src.components uses a module listed above it, which is the healthy direction.
21→2 frontend.src.components uses frontend.src.components.sign-out-dialog✕
- Connections
- 1 pair of types, where a type in frontend.src.components uses a type in frontend.src.components.sign-out-dialog.
- The types involved
frontend.src.components.sign-out-dialog→frontend.src.components.sign-out-dialog.SignOutDialogProps
- Direction
- frontend.src.components uses frontend.src.components.sign-out-dialog, so a change to frontend.src.components.sign-out-dialog can break frontend.src.components, while a change to frontend.src.components can't break frontend.src.components.sign-out-dialog.
- Position
- Below the diagonal: frontend.src.components uses a module listed above it, which is the healthy direction.
22→11 frontend.src.components.data-table uses frontend.src.features.system.dicts.components.data-table-bulk-actions✕
- Connections
- 1 pair of types, where a type in frontend.src.components.data-table uses a type in frontend.src.features.system.dicts.components.data-table-bulk-actions.
- The types involved
frontend.src.components.data-table.bulk-actions→frontend.src.features.system.dicts.components.data-table-bulk-actions.DataTableBulkActionsProps
- Direction
- frontend.src.components.data-table uses frontend.src.features.system.dicts.components.data-table-bulk-actions, so a change to frontend.src.features.system.dicts.components.data-table-bulk-actions can break frontend.src.components.data-table, while a change to frontend.src.components.data-table can't break frontend.src.features.system.dicts.components.data-table-bulk-actions.
- Position
- Below the diagonal: frontend.src.components.data-table uses a module listed above it, which is the healthy direction.
23→18 frontend.src.components.layout uses frontend.src.types.layout✕
- Connections
- 1 pair of types, where a type in frontend.src.components.layout uses a type in frontend.src.types.layout.
- The types involved
frontend.src.components.layout.nav-group→frontend.src.types.layout.NavItem
- Direction
- frontend.src.components.layout uses frontend.src.types.layout, so a change to frontend.src.types.layout can break frontend.src.components.layout, while a change to frontend.src.components.layout can't break frontend.src.types.layout.
- Position
- Below the diagonal: frontend.src.components.layout uses a module listed above it, which is the healthy direction.
24→3 frontend.src.components.ui uses frontend.src.components.ui.scroll-area✕
- Connections
- 1 pair of types, where a type in frontend.src.components.ui uses a type in frontend.src.components.ui.scroll-area.
- The types involved
frontend.src.components.ui.scroll-area→frontend.src.components.ui.scroll-area.ScrollAreaProps
- Direction
- frontend.src.components.ui uses frontend.src.components.ui.scroll-area, so a change to frontend.src.components.ui.scroll-area can break frontend.src.components.ui, while a change to frontend.src.components.ui can't break frontend.src.components.ui.scroll-area.
- Position
- Below the diagonal: frontend.src.components.ui uses a module listed above it, which is the healthy direction.
25→4 frontend.src.features.auth.sign-in.components uses frontend.src.features.auth.sign-in.components.user-auth-form✕
- Connections
- 1 pair of types, where a type in frontend.src.features.auth.sign-in.components uses a type in frontend.src.features.auth.sign-in.components.user-auth-form.
- The types involved
frontend.src.features.auth.sign-in.components.user-auth-form→frontend.src.features.auth.sign-in.components.user-auth-form.UserAuthFormProps
- Direction
- frontend.src.features.auth.sign-in.components uses frontend.src.features.auth.sign-in.components.user-auth-form, so a change to frontend.src.features.auth.sign-in.components.user-auth-form can break frontend.src.features.auth.sign-in.components, while a change to frontend.src.features.auth.sign-in.components can't break frontend.src.features.auth.sign-in.components.user-auth-form.
- Position
- Below the diagonal: frontend.src.features.auth.sign-in.components uses a module listed above it, which is the healthy direction.
26→5 frontend.src.features.system.api-resources.components uses frontend.src.features.system.api-resources.components.api-resources-provider✕
- Connections
- 1 pair of types, where a type in frontend.src.features.system.api-resources.components uses a type in frontend.src.features.system.api-resources.components.api-resources-provider.
- The types involved
frontend.src.features.system.api-resources.components.api-resources-provider→frontend.src.features.system.api-resources.components.api-resources-provider.ApiResourcesProviderProps
- Direction
- frontend.src.features.system.api-resources.components uses frontend.src.features.system.api-resources.components.api-resources-provider, so a change to frontend.src.features.system.api-resources.components.api-resources-provider can break frontend.src.features.system.api-resources.components, while a change to frontend.src.features.system.api-resources.components can't break frontend.src.features.system.api-resources.components.api-resources-provider.
- Position
- Below the diagonal: frontend.src.features.system.api-resources.components uses a module listed above it, which is the healthy direction.
27→15 frontend.src.features.system.api-resources.hooks uses frontend.src.services.apiResourceApi✕
- Connections
- 1 pair of types, where a type in frontend.src.features.system.api-resources.hooks uses a type in frontend.src.services.apiResourceApi.
- The types involved
frontend.src.features.system.api-resources.hooks.use-api-resources→frontend.src.services.apiResourceApi.ApiResourceQueryParams
- Direction
- frontend.src.features.system.api-resources.hooks uses frontend.src.services.apiResourceApi, so a change to frontend.src.services.apiResourceApi can break frontend.src.features.system.api-resources.hooks, while a change to frontend.src.features.system.api-resources.hooks can't break frontend.src.services.apiResourceApi.
- Position
- Below the diagonal: frontend.src.features.system.api-resources.hooks uses a module listed above it, which is the healthy direction.
28→6 frontend.src.features.system.departments.components uses frontend.src.features.system.departments.components.departments-action-dialog✕
- Connections
- 1 pair of types, where a type in frontend.src.features.system.departments.components uses a type in frontend.src.features.system.departments.components.departments-action-dialog.
- The types involved
frontend.src.features.system.departments.components.departments-action-dialog→frontend.src.features.system.departments.components.departments-action-dialog.DepartmentsActionDialogProps
- Direction
- frontend.src.features.system.departments.components uses frontend.src.features.system.departments.components.departments-action-dialog, so a change to frontend.src.features.system.departments.components.departments-action-dialog can break frontend.src.features.system.departments.components, while a change to frontend.src.features.system.departments.components can't break frontend.src.features.system.departments.components.departments-action-dialog.
- Position
- Below the diagonal: frontend.src.features.system.departments.components uses a module listed above it, which is the healthy direction.
28→7 frontend.src.features.system.departments.components uses frontend.src.features.system.departments.components.departments-columns✕
- Connections
- 1 pair of types, where a type in frontend.src.features.system.departments.components uses a type in frontend.src.features.system.departments.components.departments-columns.
- The types involved
frontend.src.features.system.departments.components.departments-columns→frontend.src.features.system.departments.components.departments-columns.DepartmentColumnsProps
- Direction
- frontend.src.features.system.departments.components uses frontend.src.features.system.departments.components.departments-columns, so a change to frontend.src.features.system.departments.components.departments-columns can break frontend.src.features.system.departments.components, while a change to frontend.src.features.system.departments.components can't break frontend.src.features.system.departments.components.departments-columns.
- Position
- Below the diagonal: frontend.src.features.system.departments.components uses a module listed above it, which is the healthy direction.
28→8 frontend.src.features.system.departments.components uses frontend.src.features.system.departments.components.departments-delete-dialog✕
- Connections
- 1 pair of types, where a type in frontend.src.features.system.departments.components uses a type in frontend.src.features.system.departments.components.departments-delete-dialog.
- The types involved
frontend.src.features.system.departments.components.departments-delete-dialog→frontend.src.features.system.departments.components.departments-delete-dialog.DepartmentsDeleteDialogProps
- Direction
- frontend.src.features.system.departments.components uses frontend.src.features.system.departments.components.departments-delete-dialog, so a change to frontend.src.features.system.departments.components.departments-delete-dialog can break frontend.src.features.system.departments.components, while a change to frontend.src.features.system.departments.components can't break frontend.src.features.system.departments.components.departments-delete-dialog.
- Position
- Below the diagonal: frontend.src.features.system.departments.components uses a module listed above it, which is the healthy direction.
28→9 frontend.src.features.system.departments.components uses frontend.src.features.system.departments.components.departments-provider✕
- Connections
- 1 pair of types, where a type in frontend.src.features.system.departments.components uses a type in frontend.src.features.system.departments.components.departments-provider.
- The types involved
frontend.src.features.system.departments.components.departments-provider→frontend.src.features.system.departments.components.departments-provider.DepartmentsProviderProps
- Direction
- frontend.src.features.system.departments.components uses frontend.src.features.system.departments.components.departments-provider, so a change to frontend.src.features.system.departments.components.departments-provider can break frontend.src.features.system.departments.components, while a change to frontend.src.features.system.departments.components can't break frontend.src.features.system.departments.components.departments-provider.
- Position
- Below the diagonal: frontend.src.features.system.departments.components uses a module listed above it, which is the healthy direction.
29→10 frontend.src.features.system.departments.hooks uses frontend.src.features.system.departments.hooks.use-department-form✕
- Connections
- 1 pair of types, where a type in frontend.src.features.system.departments.hooks uses a type in frontend.src.features.system.departments.hooks.use-department-form.
- The types involved
frontend.src.features.system.departments.hooks.use-department-form→frontend.src.features.system.departments.hooks.use-department-form.UseDepartmentFormProps
- Direction
- frontend.src.features.system.departments.hooks uses frontend.src.features.system.departments.hooks.use-department-form, so a change to frontend.src.features.system.departments.hooks.use-department-form can break frontend.src.features.system.departments.hooks, while a change to frontend.src.features.system.departments.hooks can't break frontend.src.features.system.departments.hooks.use-department-form.
- Position
- Below the diagonal: frontend.src.features.system.departments.hooks uses a module listed above it, which is the healthy direction.
30→11 frontend.src.features.system.dicts.components uses frontend.src.features.system.dicts.components.data-table-bulk-actions✕
- Connections
- 1 pair of types, where a type in frontend.src.features.system.dicts.components uses a type in frontend.src.features.system.dicts.components.data-table-bulk-actions.
- The types involved
frontend.src.features.system.dicts.components.data-table-bulk-actions→frontend.src.features.system.dicts.components.data-table-bulk-actions.DataTableBulkActionsProps
- Direction
- frontend.src.features.system.dicts.components uses frontend.src.features.system.dicts.components.data-table-bulk-actions, so a change to frontend.src.features.system.dicts.components.data-table-bulk-actions can break frontend.src.features.system.dicts.components, while a change to frontend.src.features.system.dicts.components can't break frontend.src.features.system.dicts.components.data-table-bulk-actions.
- Position
- Below the diagonal: frontend.src.features.system.dicts.components uses a module listed above it, which is the healthy direction.
31→14 frontend.src.features.system.menus.hooks uses frontend.src.lib.menu-utils✕
- Connections
- 1 pair of types, where a type in frontend.src.features.system.menus.hooks uses a type in frontend.src.lib.menu-utils.
- The types involved
frontend.src.features.system.menus.hooks.use-menu-drag→frontend.src.lib.menu-utils.TableMenuItem
- Direction
- frontend.src.features.system.menus.hooks uses frontend.src.lib.menu-utils, so a change to frontend.src.lib.menu-utils can break frontend.src.features.system.menus.hooks, while a change to frontend.src.features.system.menus.hooks can't break frontend.src.lib.menu-utils.
- Position
- Below the diagonal: frontend.src.features.system.menus.hooks uses a module listed above it, which is the healthy direction.
32→14 frontend.src.features.system.menus.utils uses frontend.src.lib.menu-utils✕
- Connections
- 1 pair of types, where a type in frontend.src.features.system.menus.utils uses a type in frontend.src.lib.menu-utils.
- The types involved
frontend.src.features.system.menus.utils.menu-converter→frontend.src.lib.menu-utils.TableMenuItem
- Direction
- frontend.src.features.system.menus.utils uses frontend.src.lib.menu-utils, so a change to frontend.src.lib.menu-utils can break frontend.src.features.system.menus.utils, while a change to frontend.src.features.system.menus.utils can't break frontend.src.lib.menu-utils.
- Position
- Below the diagonal: frontend.src.features.system.menus.utils uses a module listed above it, which is the healthy direction.
32→19 frontend.src.features.system.menus.utils uses frontend.src.types.menu✕
- Connections
- 1 pair of types, where a type in frontend.src.features.system.menus.utils uses a type in frontend.src.types.menu.
- The types involved
frontend.src.features.system.menus.utils.menu-converter→frontend.src.types.menu.Menu
- Direction
- frontend.src.features.system.menus.utils uses frontend.src.types.menu, so a change to frontend.src.types.menu can break frontend.src.features.system.menus.utils, while a change to frontend.src.features.system.menus.utils can't break frontend.src.types.menu.
- Position
- Below the diagonal: frontend.src.features.system.menus.utils uses a module listed above it, which is the healthy direction.
33→14 frontend.src.features.system.roles.components.menu-tree-section uses frontend.src.lib.menu-utils✕
- Connections
- 1 pair of types, where a type in frontend.src.features.system.roles.components.menu-tree-section uses a type in frontend.src.lib.menu-utils.
- The types involved
frontend.src.features.system.roles.components.menu-tree-section.MenuTreeItemProps→frontend.src.lib.menu-utils.RoleMenuOption
- Direction
- frontend.src.features.system.roles.components.menu-tree-section uses frontend.src.lib.menu-utils, so a change to frontend.src.lib.menu-utils can break frontend.src.features.system.roles.components.menu-tree-section, while a change to frontend.src.features.system.roles.components.menu-tree-section can't break frontend.src.lib.menu-utils.
- Position
- Below the diagonal: frontend.src.features.system.roles.components.menu-tree-section uses a module listed above it, which is the healthy direction.
34→11 frontend.src.features.system.users.components uses frontend.src.features.system.dicts.components.data-table-bulk-actions✕
- Connections
- 1 pair of types, where a type in frontend.src.features.system.users.components uses a type in frontend.src.features.system.dicts.components.data-table-bulk-actions.
- The types involved
frontend.src.features.system.users.components.data-table-bulk-actions→frontend.src.features.system.dicts.components.data-table-bulk-actions.DataTableBulkActionsProps
- Direction
- frontend.src.features.system.users.components uses frontend.src.features.system.dicts.components.data-table-bulk-actions, so a change to frontend.src.features.system.dicts.components.data-table-bulk-actions can break frontend.src.features.system.users.components, while a change to frontend.src.features.system.users.components can't break frontend.src.features.system.dicts.components.data-table-bulk-actions.
- Position
- Below the diagonal: frontend.src.features.system.users.components uses a module listed above it, which is the healthy direction.
35→16 frontend.src.features.system.users.hooks uses frontend.src.types.api✕
- Connections
- 1 pair of types, where a type in frontend.src.features.system.users.hooks uses a type in frontend.src.types.api.
- The types involved
frontend.src.features.system.users.hooks.use-users→frontend.src.types.api.QueryParams
- Direction
- frontend.src.features.system.users.hooks uses frontend.src.types.api, so a change to frontend.src.types.api can break frontend.src.features.system.users.hooks, while a change to frontend.src.features.system.users.hooks can't break frontend.src.types.api.
- Position
- Below the diagonal: frontend.src.features.system.users.hooks uses a module listed above it, which is the healthy direction.
36→18 frontend.src.lib uses frontend.src.types.layout✕
- Connections
- 1 pair of types, where a type in frontend.src.lib uses a type in frontend.src.types.layout.
- The types involved
frontend.src.lib.backend-menu-adapter→frontend.src.types.layout.NavItem
- Direction
- frontend.src.lib uses frontend.src.types.layout, so a change to frontend.src.types.layout can break frontend.src.lib, while a change to frontend.src.lib can't break frontend.src.types.layout.
- Position
- Below the diagonal: frontend.src.lib uses a module listed above it, which is the healthy direction.
36→19 frontend.src.lib uses frontend.src.types.menu✕
- Connections
- 1 pair of types, where a type in frontend.src.lib uses a type in frontend.src.types.menu.
- The types involved
frontend.src.lib.backend-menu-adapter→frontend.src.types.menu.MenuTreeNode
- Direction
- frontend.src.lib uses frontend.src.types.menu, so a change to frontend.src.types.menu can break frontend.src.lib, while a change to frontend.src.lib can't break frontend.src.types.menu.
- Position
- Below the diagonal: frontend.src.lib uses a module listed above it, which is the healthy direction.
37→15 frontend.src.services uses frontend.src.services.apiResourceApi✕
- Connections
- 2 pairs of types, where a type in frontend.src.services uses a type in frontend.src.services.apiResourceApi.
- The types involved
frontend.src.services.apiResourceApi→frontend.src.services.apiResourceApi.ApiResourcePagedResultfrontend.src.services.apiResourceApi→frontend.src.services.apiResourceApi.ApiResourceQueryParams
- Direction
- frontend.src.services uses frontend.src.services.apiResourceApi, so a change to frontend.src.services.apiResourceApi can break frontend.src.services, while a change to frontend.src.services can't break frontend.src.services.apiResourceApi.
- Position
- Below the diagonal: frontend.src.services uses a module listed above it, which is the healthy direction.
37→16 frontend.src.services uses frontend.src.types.api✕
- Connections
- 3 pairs of types, where a type in frontend.src.services uses a type in frontend.src.types.api.
- The types involved
frontend.src.services.authApi→frontend.src.types.api.ApiResponsefrontend.src.services.roleApi→frontend.src.types.api.QueryParamsfrontend.src.services.userApi→frontend.src.types.api.QueryParams
- Direction
- frontend.src.services uses frontend.src.types.api, so a change to frontend.src.types.api can break frontend.src.services, while a change to frontend.src.services can't break frontend.src.types.api.
- Position
- Below the diagonal: frontend.src.services uses a module listed above it, which is the healthy direction.
37→17 frontend.src.services uses frontend.src.types.dict✕
- Connections
- 8 pairs of types, where a type in frontend.src.services uses a type in frontend.src.types.dict.
- The types involved
frontend.src.services.dictApi→frontend.src.types.dict.CreateDictItemRequestfrontend.src.services.dictApi→frontend.src.types.dict.CreateDictTypeRequestfrontend.src.services.dictApi→frontend.src.types.dict.DictItemPagedResultfrontend.src.services.dictApi→frontend.src.types.dict.DictItemQueryParamsfrontend.src.services.dictApi→frontend.src.types.dict.DictTypePagedResultfrontend.src.services.dictApi→frontend.src.types.dict.DictTypeQueryParamsfrontend.src.services.dictApi→frontend.src.types.dict.UpdateDictItemRequestfrontend.src.services.dictApi→frontend.src.types.dict.UpdateDictTypeRequest
- Direction
- frontend.src.services uses frontend.src.types.dict, so a change to frontend.src.types.dict can break frontend.src.services, while a change to frontend.src.services can't break frontend.src.types.dict.
- Position
- Below the diagonal: frontend.src.services uses a module listed above it, which is the healthy direction.
37→19 frontend.src.services uses frontend.src.types.menu✕
- Connections
- 6 pairs of types, where a type in frontend.src.services uses a type in frontend.src.types.menu.
- The types involved
frontend.src.services.menuApi→frontend.src.types.menu.CreateMenuRequestfrontend.src.services.menuApi→frontend.src.types.menu.Menufrontend.src.services.menuApi→frontend.src.types.menu.MenuPagedResultfrontend.src.services.menuApi→frontend.src.types.menu.MenuQueryParamsfrontend.src.services.menuApi→frontend.src.types.menu.UpdateMenuRequestfrontend.src.services.resourceApi→frontend.src.types.menu.ResourcesResponse
- Direction
- frontend.src.services uses frontend.src.types.menu, so a change to frontend.src.types.menu can break frontend.src.services, while a change to frontend.src.services can't break frontend.src.types.menu.
- Position
- Below the diagonal: frontend.src.services uses a module listed above it, which is the healthy direction.
38→20 shadmin-cli/internal/client uses shadmin-cli/internal/config✕
- Connections
- 2 pairs of types, where a type in shadmin-cli/internal/client uses a type in shadmin-cli/internal/config.
- The types involved
shadmin-cli/internal/client.Client→shadmin-cli/internal/config.Configshadmin-cli/internal/client.client→shadmin-cli/internal/config.Config
- Direction
- shadmin-cli/internal/client uses shadmin-cli/internal/config, so a change to shadmin-cli/internal/config can break shadmin-cli/internal/client, while a change to shadmin-cli/internal/client can't break shadmin-cli/internal/config.
- Position
- Below the diagonal: shadmin-cli/internal/client uses a module listed above it, which is the healthy direction.
39→33 frontend.src.features.system.roles.components uses frontend.src.features.system.roles.components.menu-tree-section✕
- Connections
- 3 pairs of types, where a type in frontend.src.features.system.roles.components uses a type in frontend.src.features.system.roles.components.menu-tree-section.
- The types involved
frontend.src.features.system.roles.components.menu-tree-section→frontend.src.features.system.roles.components.menu-tree-section.MenuTreeItemPropsfrontend.src.features.system.roles.components.menu-tree-section→frontend.src.features.system.roles.components.menu-tree-section.MenuTreePropsfrontend.src.features.system.roles.components.menu-tree-section→frontend.src.features.system.roles.components.menu-tree-section.MenuTreeSectionProps
- Direction
- frontend.src.features.system.roles.components uses frontend.src.features.system.roles.components.menu-tree-section, so a change to frontend.src.features.system.roles.components.menu-tree-section can break frontend.src.features.system.roles.components, while a change to frontend.src.features.system.roles.components can't break frontend.src.features.system.roles.components.menu-tree-section.
- Position
- Below the diagonal: frontend.src.features.system.roles.components uses a module listed above it, which is the healthy direction.
40→20 shadmin-cli/cmd uses shadmin-cli/internal/config✕
- Connections
- 1 pair of types, where a type in shadmin-cli/cmd uses a type in shadmin-cli/internal/config.
- The types involved
shadmin-cli/cmd.cmd→shadmin-cli/internal/config.Config
- Direction
- shadmin-cli/cmd uses shadmin-cli/internal/config, so a change to shadmin-cli/internal/config can break shadmin-cli/cmd, while a change to shadmin-cli/cmd can't break shadmin-cli/internal/config.
- Position
- Below the diagonal: shadmin-cli/cmd uses a module listed above it, which is the healthy direction.
40→38 shadmin-cli/cmd uses shadmin-cli/internal/client✕
- Connections
- 4 pairs of types, where a type in shadmin-cli/cmd uses a type in shadmin-cli/internal/client.
- The types involved
shadmin-cli/cmd.cmd→shadmin-cli/internal/client.Clientshadmin-cli/cmd.cmd→shadmin-cli/internal/client.DeviceCodeResponseshadmin-cli/cmd.cmd→shadmin-cli/internal/client.ListParamsshadmin-cli/cmd.cmd→shadmin-cli/internal/client.LoginTokenResponse
- Direction
- shadmin-cli/cmd uses shadmin-cli/internal/client, so a change to shadmin-cli/internal/client can break shadmin-cli/cmd, while a change to shadmin-cli/cmd can't break shadmin-cli/internal/client.
- Position
- Below the diagonal: shadmin-cli/cmd 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 |
|---|---|---|
| A07:2025 — Authentication Failures | 18 | High / Critical |
| A02:2025 — Security Misconfiguration | 15 | High / Critical |
| A05:2025 — Injection | 14 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 9 | Medium |
Roadmap
Top priorities: Resolve the 9 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (6), REDACTED (3); Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery; Add a SAST step to CI running what this repository's stack ships: gosec / govulncheck (or golangci-lint) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 9 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (6), REDACTED (3). | +14.7 pts | Low | REDACTED Scanning |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +6.4 pts | Medium | DR & Backup |
| Add a SAST step to CI running what this repository's stack ships: gosec / govulncheck (or golangci-lint) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +5.5 pts | Medium | Security & performance tooling |
| Resolve the 8 REDACTED finding(s) in Secrets (history) — start with REDACTED (4), REDACTED (2), REDACTED (2). | +1.4 pts | Low | Secrets (history) |
| Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI. | +1.8 pts | Medium | A11y enforcement |
| Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. | +1.8 pts | Medium | Observability |
| 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. | +1.8 pts | Medium | Visual & motion safety |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +1.4 pts | Medium | Forms & labels |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 0.9 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 2.3 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 2.3 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 5.2 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| REDACTED | 7.2 | Near-clean | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 7.9 | Near-clean | Dependency Vulnerabilities: Medium vulnerability: REDACTED |
| api/controller/auth_controller.go | 8.5 | Near-clean | Change Coupling: Change coupling: auth_controller.go ↔ jwt_auth_middleware.go |
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 51 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 51 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, 71 of 84 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
- D1 Cyclomatic Complexity — 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. Most of this repository's production source (.go) had no cyclomatic complexity computed for it: no function bodies were exposed for those file kinds by any language model this pass could load.
- D2 Cognitive Complexity — 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. Most of this repository's production source (.go) had no cognitive complexity computed for it: no function bodies were exposed for those file kinds by any language model this pass could load.
- D4 Code Duplication — 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. Most of this repository's production source (.go) was not read by duplication detection: no source of those file kinds was exposed to the token comparison by any language model this pass could load.
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for frontend/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
- 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 8 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 41 test source file(s) (.go) 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 MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for frontend/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the node:test suite in frontend/ was NOT MEASURED: the dependency install for frontend/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D15 Churn × Complexity Hotspots — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. A hotspot is churn × complexity. Churn was measured (23202 line(s) across the 90-day window), but no complexity could be computed for .go, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, not a finding about this repository.
- D16 Bus Factor — 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. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 372 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 1 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- 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 (REDACTED), 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 — 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 the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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 17 — an image could not be built) — failed to solve: process "/bin/sh -c pnpm install --frozen-lockfile" did not complete successfully: exit code: 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. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — 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 authorization 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 authorization controls.
- 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. These audit 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 audit controls.
- 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. These retention 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 retention controls.
- 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. These data-subject rights 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 data-subject rights controls.
- 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 and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Go 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 and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Go 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. A badge or prose version claim scored 9/17 in its adjudication (docs/plans/deterministic-engine/adjudication/M4-v3.md: badges 9/9, prose 0/8, where prose versions are minimums or history), short of the 95 % precision gate, 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. The .NET and Node.js version checks are a different kind and still publish.
- 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.
- P8 Schema migrations — 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. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
- 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 reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, 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.
- 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 reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- X18 Disposal-pattern 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 reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, 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.
- X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, 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.
- X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Go 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.
- X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, 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.
- 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 reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, 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.
- X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, 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.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's Go 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.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 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").
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- 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
D5 · Coupling
2 production modules (Go), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 1 of the 2 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 1 classes have LCOM4 above 3.
D9 · Test Distribution
147 test methods: 147 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 8 `it`/`test` case(s) across 1 test file(s) declaring at least one; its tier split is read from package names and paths only. The Go suite contributes 139 test case(s) across 39 `_test.go` file(s) declaring at least one — every `func Test…(t *testing.T)` that `go test` would collect, plus the suite methods a testify-style runner reaches; a table-driven case list counts once, so this is a floor. Its tier split is INFERRED from file names, paths and build constraints, not declared: 1 of those file(s) use Go's external test package (`package x_test`), which is a visibility boundary rather than a pyramid tier and was not read as one.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 8 tests. Measured on the JavaScript/TypeScript suite only — at least 41 test source file(s) (.go) went unread, so its test quality is unmeasured and is not in these counts.
D12 · Dependency Hygiene
2 outdated, 0 author-deprecated direct Go module(s), 0 pinning or checksum defect(s). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.
D13 · REDACTED Scanning
7 secret(s) detected.
What to do
- Resolve the 9 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (6), REDACTED (3). — One of this dimension's main actionable groups (9 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D17 · Explicit Debt
0 deducted task-comment markers across 13809 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 13 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 2 build units (Go) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
24 % of calls cross a namespace and 0 % go through an interface, but 58 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
8 finding(s): 0 critical, 8 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 8 REDACTED finding(s) in Secrets (history) — start with REDACTED (4), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (8 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)
14 finding(s): 0 critical, 12 high, 2 medium, 0 low. 9 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.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 9 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 (9 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
3 finding(s): 0 critical, 0 high, 3 medium, 0 low.
What to do
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
15 finding(s): 0 critical, 4 high, 10 medium, 1 low.
What to do
- Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 10 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED (4). — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 73 of the 140 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: auth_controller.go↔jwt_auth_middleware.go 70%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with auth_controller.go. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
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 2 platform declaration(s) and 0 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
AC2 · Forms & labels
- This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it. (×2) — frontend/src/components/data-table/pagination.tsx:45, frontend/src/features/settings/components/sidebar-nav.tsx:35
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
AC5 · ARIA correctness
AC6 · Visual & motion safety
- <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — frontend/src/components/ui/input.tsx:6
- <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — frontend/src/components/ui/textarea.tsx:6
- `.CollapsibleContent[data-state='open']` moves (`animation: slideDown 300ms ease-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. — frontend/src/styles/index.css:65
- `.CollapsibleContent[data-state='closed']` moves (`animation: slideUp 300ms ease-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. — frontend/src/styles/index.css:68
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.
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 186 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — frontend/package.json:68
What to do
- Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
AX7 · Slice cohesion
M1 · Documentation (README)
What to do
- Add a README to the 1 of 2 project(s) that lack one — worth up to 1 pts.
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.
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.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `cli`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add OpenTelemetry tracing/metrics (go.opentelemetry.io/otel) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add gosec / govulncheck (or golangci-lint) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 3608 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:19
- `frontend/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — frontend/package.json:22
What to do
- Add a SAST step to CI running what this repository's stack ships: gosec / govulncheck (or golangci-lint) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P6 · Release Hygiene
P7 · Outbound HTTP resilience
PF1 · Benchmark discipline
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — frontend/netlify.toml:1
What to do
- Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X2 · Cancellation propagation
X26 · Unsynchronised callback handoff
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `if err := dfr.validatePath(filePath); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — REDACTED:304
- `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — REDACTED:308
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
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 |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 91% | Checked 3 of 9 | Strongest area. |
| Architecture | 81% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 81% | Strong | Solid. |
| Readiness | 36% | Weak — gated by D13, P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 63% | Adequate — gated by D28, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 60% | Adequate | Acceptable, with room to improve. |
| Performance | 90% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit 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 audit 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.
- C4 Data Retention — Not assessed: these retention 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 retention 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.
- C5 Data-Subject Rights — Not assessed: these data-subject rights 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 data-subject rights 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.
Not included — 65 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's Go imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Go request handler (a net/http, Gin, Echo, Fiber or fasthttp handler, or a gRPC service method) is declared as a method or function, and no handler function literal writes a value captured from outside it, so no state is shared between request goroutines. 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).
- AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
- 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 17 — an image could not be built) — failed to solve: process "/bin/sh -c pnpm install --frozen-lockfile" did not complete successfully: exit code: 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: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization 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 authorization 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.
- D1 Cyclomatic Complexity — cyclomatic complexity not measured — .go exposed no member bodies
- D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
- D14 License Compliance — Not scored — this repository's 229 shipped npm package(s) were resolved from its committed lockfile, but registry.npmjs.org could not be asked for the licence of 2 of them (registry returned 429), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- D15 Churn × Complexity Hotspots — complexity unreadable for .go — churn × complexity hotspots could not be measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- 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.
- D2 Cognitive Complexity — cognitive complexity not measured — .go exposed no member bodies
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Go 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"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .go, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D3 God Classes — Most of this repository's production source (.go) was not read by god-class detection, so type and module size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's type and module size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D4 Code Duplication — Duplication not measured — .go not exposed to the token comparison
- 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 — JavaScript/TypeScript suite
- DM1 Domain Modelling — not scored — this repository shows none of the 2 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 and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P8 Schema migrations — ent is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`go test -coverprofile=coverage.out ./...`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- 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.
- PF3 Async & latency hygiene — Not applicable: Go has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — 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
- X12 Unreachable branch — 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
- X13 Undrained process stream — 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
- X16 Unfloored truncation loop — 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
- X17 Uncapped recursion over a caller-supplied document — 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
- X18 Disposal-pattern correctness — 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
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X21 Side-effecting pattern guard — Not applicable: this check looks for a pattern guard or `case` label that increments, decrements or assigns while the switch is deciding whether it matches, and in this repository's languages none can. Go's `++`, `--` and assignments are STATEMENTS, not expressions, so none of them can appear in a `case` expression or anywhere else in a condition, and a type switch's cases are types. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — 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
- X23 Unguarded diagnostic materialisation — 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
- X24 Document value interpolated into markup unescaped — 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
- X25 Inert configuration knob — 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
- X27 Collection changed while being enumerated — 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
- X29 Per-element action decided by a fixed element — 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
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — Not applicable: this check asks whether the null-typed discipline a language offers is switched on, and how much of that the assertion operator takes back, and in this repository's languages there is no such switch and no such operator. Go's type system has no nullable and non-nullable types — every pointer, map, slice and interface is nil-able at every position, there is no switch that turns null checking on, and the compiler produces no nullability warning for an operator to silence. 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 — 33 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
Serious — 28 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <Select> field component without a label frontend/src/components/data-table/pagination.tsx:45
- <Select> field component without a label frontend/src/features/settings/components/sidebar-nav.tsx:35
- Focus outline removed inline frontend/src/components/ui/input.tsx:6
- Focus outline removed inline frontend/src/components/ui/textarea.tsx:6
- Animation without a prefers-reduced-motion guard frontend/src/styles/index.css:65
- Animation without a prefers-reduced-motion guard frontend/src/styles/index.css:68
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Swallowed exception (caught, then discarded) REDACTED:304
- Swallowed exception (caught, then discarded) REDACTED:308
- Accessibility enforcement below the top rung frontend/package.json:68
- REDACTED
- Change coupling: auth_controller.go ↔ jwt_auth_middleware.go api/controller/auth_controller.go:1
- REDACTED
- REDACTED
- No DR/backup evidence
Minor — 21 finding(s)
- Duplicated predicate frontend/src/features/auth/device-activate/components/device-activate-form.tsx:20
- Duplicated predicate frontend/src/features/system/dicts/components/items-dialogs.tsx:230
- Duplicated predicate frontend/src/features/system/menus/components/menus-table.tsx:81
- Duplicated predicate frontend/src/features/system/menus/components/menus-columns.tsx:47
- Duplicated predicate frontend/src/lib/backend-menu-adapter.ts:8
- Duplicated predicate frontend/src/features/system/departments/components/departments-table.tsx:162
- Duplicated predicate frontend/src/features/system/departments/components/departments-table.tsx:163
- Duplicated predicate frontend/src/features/system/dicts/components/dict-types-columns.tsx:74
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- No SAST REDACTED:19
- No dependency-update automation frontend/package.json:22
- No security response headers detected frontend/netlify.toml:1
Minor — 2 finding(s)
- Outdated: github.com/mattn/go-sqlite3
- Outdated: github.com/resend/resend-go/v4
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c92382a281e040ef9af9dc155994ec56/history.json --exit-code 0 --source . | 6 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c92382a281e040ef9af9dc155994ec56/tree.json --exit-code 0 --source . | 4 | 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 --exclude frontend/src/assets/brand-icons --exclude frontend/src/assets/custom --exclude frontend/src/components --exclude frontend/src/config --exclude frontend/src/constants --exclude frontend/src/context --exclude frontend/src/features --exclude frontend/src/hooks --exclude frontend/src/lib --exclude frontend/src/routes --exclude frontend/src/services --exclude frontend/src/stores --exclude frontend/src/styles --exclude frontend/src/types --exclude frontend/tests . | 14 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 3 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 15 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |