Executive summary
orchidsoftware/platform falls short of our standard for production because it has images with no text description. It scores 49.7 out of 100 and is rated Weak, and 32 of its 45 critical findings are security problems.
Accessibility, at 45.7, is the weakest lens and counts most in the score. The best first step for the work it takes is improving the documentation, worth about 1.6 points. Making the controls keyboard-usable would lift Accessibility itself, worth about 2.9 points. Raising Accessibility to 70 would lift the score to about 52.9.
Twenty-eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two passwords or keys are open to anyone who can read the repository, and four buttons or links have no name a screen reader can say. Pinning each tool to an exact version, replacing each exposed password or key and naming the buttons and links would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and limiting each secret to its own step would deal with the secret exposed to more of the pipeline than needed. The two images with no text description need a text description.
The product code is 21,937 lines, about €34,000 to rebuild.
If Accessibility rose from 45.7 to 70, the lowest score rated Strong, the score would rise from 49.7 to about 52.9.
New since the last survey: 14 findings
- Code Duplication · Edited copy of a member (15 corresponding lines) src/Screen/Fields/Attach.php
- Code Duplication · Edited copy of a member (7 corresponding lines) src/Access/RoleAccess.php
- Code Duplication · Edited copy of a member (10 corresponding lines) stubs/app/Orchid/Screens/User/UserListScreen.php
- Coupling · Circular dependency src/Access/RoleAccess.php
- Coupling · Off the main sequence: src/Metrics
- Explicit Debt · TodoComment tests/App/RouteSolving.php
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Dependency Hygiene · Unused dependency '@codemirror/lang-cpp' package.json
- Dependency Hygiene · Unused dependency '@codemirror/search' package.json
- Dependency Hygiene · Unused dependency '@popperjs/core' package.json
- Dependency Hygiene · Unused dependency 'laravel-vite-plugin' package.json
- Dependency Hygiene · Unused dependency 'rtlcss' package.json
Fixed since the last survey: 32 findings
- Code Duplication · Duplicated block (61 lines × 2) stubs/app/Orchid/Screens/Examples/ExampleCardsScreen.php
- REDACTED Scanning · Leaked secret: hardcoded-credential src/Platform/Http/Controllers/LoginController.php
- REDACTED Scanning · Leaked secret: hardcoded-credential REDACTED
- REDACTED Scanning · Leaked secret: hardcoded-credential REDACTED
- Explicit Debt · TodoComment tests/Unit/Screen/Screens/ParentScreen.php
- Explicit Debt · TodoComment tests/App/RouteSolving.php
- Explicit Debt · TodoComment tests/App/RouteSolving.php
- Explicit Debt · TodoComment tests/App/RouteSolving.php
- Secrets (history) · High secret: WD-SECRET-0005 app/Http/Controllers/Auth/RegisterController.php
- Secrets (history) · REDACTED: generic-api-key public/js/orchid.js.map
- Secrets (history) · REDACTED: generic-api-key resources/assets/dist/js/orchid.js
- Secrets (history) · REDACTED: generic-api-key resources/assets/dist/js/orchid.js.map
- Secrets (history) · High secret: WD-SECRET-0005 src/Foundation/Http/Controllers/Auth/RegisterController.php
- Secrets (history) · High secret: WD-SECRET-0005 src/Foundation/Http/Forms/Systems/Users/BaseUserForm.php
- Secrets (history) · High secret: WD-SECRET-0005 src/Foundation/Http/Forms/Systems/Users/BaseUserForm.php
- Secrets (history) · REDACTED: generic-api-key src/Foundation/Resources/assets/dist/js/orchid.js
- Secrets (history) · REDACTED: generic-api-key src/Foundation/Resources/dist/js/orchid.js
- Secrets (history) · REDACTED: generic-api-key src/Foundation/Resources/dist/js/orchid.js.map
- Secrets (history) · High secret: WD-SECRET-0005 src/Http/Controllers/Auth/RegisterController.php
- Secrets (history) · High secret: WD-SECRET-0005 src/Orchid/Http/Controllers/Auth/RegisterController.php
- Secrets (history) · High secret: WD-SECRET-0005 src/Platform/Http/Controllers/Auth/RegisterController.php
- Secrets (history) · High secret: WD-SECRET-0005 REDACTED
- Secrets (history) · High secret: WD-SECRET-0005 REDACTED
- Secrets (history) · REDACTED: square-access-token tatus
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: REDACTED REDACTED
- Static Analysis (SAST) · High: canine-unverified-download-in-run REDACTED
- Supply-chain Provenance & Signing · CI installs an unverified third-party binary REDACTED
- Dependency Hygiene · Unused dependency '@codemirror/lang-cpp'
- Dependency Hygiene · Unused dependency '@codemirror/search'
- Dependency Hygiene · Unused dependency '@popperjs/core'
- A11y enforcement · Accessibility enforcement below the top rung package.json
Rebuild cost: about €34,000 · Estimate
| Cost to rebuild | €11,000 to €57,000, for 190 to 602 hours of work, about 0.2 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 50. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 21,937 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Orchid.Access | 2 Orchid.Attachment | 3 Orchid.Attachment.Contracts | 4 Orchid.Attachment.Models | 5 Orchid.Filters | 6 Orchid.Platform.Models | 7 Orchid.Presenter | 8 Orchid.Screen.Fields.Support | 9 resources.js.controllers.application_controller | 10 App.Orchid.Filters | 11 Orchid.Attachment.Engines | 12 Orchid.Filters.Types | 13 Orchid.Platform | 14 Orchid.Platform.Events | 15 Orchid.Platform.Http.Requests | 16 Orchid.Support | 17 resources.js.controllers.attach_controller | 18 resources.js.controllers.block_editor_controller | 19 resources.js.controllers.browsing_controller | 20 resources.js.controllers.button_controller | 21 resources.js.controllers.chart_controller | 22 resources.js.controllers.checkbox_controller | 23 resources.js.controllers.code_controller | 24 App.Orchid | 25 Orchid.Alert | 26 Orchid.Platform.Http.Controllers | 27 Orchid.Platform.Notifications | 28 Orchid.Platform.Providers | 29 Orchid.Screen.Actions | 30 Orchid.Screen.Contracts | 31 App.Orchid.Presenters | 32 Orchid.Screen.Layouts | 33 Orchid.Screen | 34 App.Orchid.Screens | 35 App.Orchid.Screens.Role | 36 App.Orchid.Screens.User | 37 Orchid.Platform.Configuration | 38 Orchid.Screen.Concerns | 39 Orchid.Screen.Fields | 40 App.Orchid.Layouts.User |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Orchid.Access | ||||||||||||||||||||||||||||||||||||||||
| 2 Orchid.Attachment | ||||||||||||||||||||||||||||||||||||||||
| 3 Orchid.Attachment.Contracts | ||||||||||||||||||||||||||||||||||||||||
| 4 Orchid.Attachment.Models | ||||||||||||||||||||||||||||||||||||||||
| 5 Orchid.Filters | ||||||||||||||||||||||||||||||||||||||||
| 6 Orchid.Platform.Models | ||||||||||||||||||||||||||||||||||||||||
| 7 Orchid.Presenter | ||||||||||||||||||||||||||||||||||||||||
| 8 Orchid.Screen.Fields.Support | ||||||||||||||||||||||||||||||||||||||||
| 9 resources.js.controllers.application_controller | ||||||||||||||||||||||||||||||||||||||||
| 10 App.Orchid.Filters | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 Orchid.Attachment.Engines | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 Orchid.Filters.Types | 8 | |||||||||||||||||||||||||||||||||||||||
| 13 Orchid.Platform | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 Orchid.Platform.Events | 3 | |||||||||||||||||||||||||||||||||||||||
| 15 Orchid.Platform.Http.Requests | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 Orchid.Support | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 resources.js.controllers.attach_controller | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 resources.js.controllers.block_editor_controller | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 resources.js.controllers.browsing_controller | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 resources.js.controllers.button_controller | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 resources.js.controllers.chart_controller | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 resources.js.controllers.checkbox_controller | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 resources.js.controllers.code_controller | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 App.Orchid | 2 | |||||||||||||||||||||||||||||||||||||||
| 25 Orchid.Alert | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 Orchid.Platform.Http.Controllers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 Orchid.Platform.Notifications | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 Orchid.Platform.Providers | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 Orchid.Screen.Actions | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 30 Orchid.Screen.Contracts | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 App.Orchid.Presenters | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 32 Orchid.Screen.Layouts | 1 | 2 | 44 | |||||||||||||||||||||||||||||||||||||
| 33 Orchid.Screen | 1 | 1 | 4 | 19 | ||||||||||||||||||||||||||||||||||||
| 34 App.Orchid.Screens | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 App.Orchid.Screens.Role | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 36 App.Orchid.Screens.User | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 37 Orchid.Platform.Configuration | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 Orchid.Screen.Concerns | 4 | |||||||||||||||||||||||||||||||||||||||
| 39 Orchid.Screen.Fields | 1 | 2 | 26 | 3 | ||||||||||||||||||||||||||||||||||||
| 40 App.Orchid.Layouts.User | 1 | 7 | 1 |
10→5 App.Orchid.Filters uses Orchid.Filters✕
- Connections
- 1 pair of types, where a type in App.Orchid.Filters uses a type in Orchid.Filters.
- The types involved
App.Orchid.Filters.RoleFilter→Orchid.Filters.Filter
- Direction
- App.Orchid.Filters uses Orchid.Filters, so a change to Orchid.Filters can break App.Orchid.Filters, while a change to App.Orchid.Filters can't break Orchid.Filters.
- Position
- Below the diagonal: App.Orchid.Filters uses a module listed above it, which is the healthy direction.
11→2 Orchid.Attachment.Engines uses Orchid.Attachment✕
- Connections
- 1 pair of types, where a type in Orchid.Attachment.Engines uses a type in Orchid.Attachment.
- The types involved
Orchid.Attachment.Engines.Generator→Orchid.Attachment.MimeTypes
- Direction
- Orchid.Attachment.Engines uses Orchid.Attachment, so a change to Orchid.Attachment can break Orchid.Attachment.Engines, while a change to Orchid.Attachment.Engines can't break Orchid.Attachment.
- Position
- Below the diagonal: Orchid.Attachment.Engines uses a module listed above it, which is the healthy direction.
11→3 Orchid.Attachment.Engines uses Orchid.Attachment.Contracts✕
- Connections
- 1 pair of types, where a type in Orchid.Attachment.Engines uses a type in Orchid.Attachment.Contracts.
- The types involved
Orchid.Attachment.Engines.Generator→Orchid.Attachment.Contracts.Engine
- Direction
- Orchid.Attachment.Engines uses Orchid.Attachment.Contracts, so a change to Orchid.Attachment.Contracts can break Orchid.Attachment.Engines, while a change to Orchid.Attachment.Engines can't break Orchid.Attachment.Contracts.
- Position
- Below the diagonal: Orchid.Attachment.Engines uses a module listed above it, which is the healthy direction.
12→5 Orchid.Filters.Types uses Orchid.Filters✕
- Connections
- 8 pairs of types, where a type in Orchid.Filters.Types uses a type in Orchid.Filters.
- The types involved
Orchid.Filters.Types.Ilike→Orchid.Filters.BaseHttpEloquentFilterOrchid.Filters.Types.Like→Orchid.Filters.BaseHttpEloquentFilterOrchid.Filters.Types.Where→Orchid.Filters.BaseHttpEloquentFilterOrchid.Filters.Types.WhereBetween→Orchid.Filters.BaseHttpEloquentFilterOrchid.Filters.Types.WhereDate→Orchid.Filters.BaseHttpEloquentFilterOrchid.Filters.Types.WhereDateStartEnd→Orchid.Filters.BaseHttpEloquentFilterOrchid.Filters.Types.WhereIn→Orchid.Filters.BaseHttpEloquentFilterOrchid.Filters.Types.WhereMaxMin→Orchid.Filters.BaseHttpEloquentFilter
- Direction
- Orchid.Filters.Types uses Orchid.Filters, so a change to Orchid.Filters can break Orchid.Filters.Types, while a change to Orchid.Filters.Types can't break Orchid.Filters.
- Position
- Below the diagonal: Orchid.Filters.Types uses a module listed above it, which is the healthy direction.
13→1 Orchid.Platform uses Orchid.Access✕
- Connections
- 1 pair of types, where a type in Orchid.Platform uses a type in Orchid.Access.
- The types involved
Orchid.Platform.ItemPermission→Orchid.Access.PermissionGroup
- Direction
- Orchid.Platform uses Orchid.Access, so a change to Orchid.Access can break Orchid.Platform, while a change to Orchid.Platform can't break Orchid.Access.
- Position
- Below the diagonal: Orchid.Platform uses a module listed above it, which is the healthy direction.
14→4 Orchid.Platform.Events uses Orchid.Attachment.Models✕
- Connections
- 3 pairs of types, where a type in Orchid.Platform.Events uses a type in Orchid.Attachment.Models.
- The types involved
Orchid.Platform.Events.ReplicateFileEvent→Orchid.Attachment.Models.AttachmentOrchid.Platform.Events.UploadFileEvent→Orchid.Attachment.Models.AttachmentOrchid.Platform.Events.UploadedFileEvent→Orchid.Attachment.Models.Attachment
- Direction
- Orchid.Platform.Events uses Orchid.Attachment.Models, so a change to Orchid.Attachment.Models can break Orchid.Platform.Events, while a change to Orchid.Platform.Events can't break Orchid.Attachment.Models.
- Position
- Below the diagonal: Orchid.Platform.Events uses a module listed above it, which is the healthy direction.
15→8 Orchid.Platform.Http.Requests uses Orchid.Screen.Fields.Support✕
- Connections
- 1 pair of types, where a type in Orchid.Platform.Http.Requests uses a type in Orchid.Screen.Fields.Support.
- The types involved
Orchid.Platform.Http.Requests.ChoicesRequest→Orchid.Screen.Fields.Support.ChoicePayload
- Direction
- Orchid.Platform.Http.Requests uses Orchid.Screen.Fields.Support, so a change to Orchid.Screen.Fields.Support can break Orchid.Platform.Http.Requests, while a change to Orchid.Platform.Http.Requests can't break Orchid.Screen.Fields.Support.
- Position
- Below the diagonal: Orchid.Platform.Http.Requests uses a module listed above it, which is the healthy direction.
16→7 Orchid.Support uses Orchid.Presenter✕
- Connections
- 1 pair of types, where a type in Orchid.Support uses a type in Orchid.Presenter.
- The types involved
Orchid.Support.Presenter→Orchid.Presenter.Presenter
- Direction
- Orchid.Support uses Orchid.Presenter, so a change to Orchid.Presenter can break Orchid.Support, while a change to Orchid.Support can't break Orchid.Presenter.
- Position
- Below the diagonal: Orchid.Support uses a module listed above it, which is the healthy direction.
17→9 resources.js.controllers.attach_controller uses resources.js.controllers.application_controller✕
- Connections
- 1 pair of types, where a type in resources.js.controllers.attach_controller uses a type in resources.js.controllers.application_controller.
- The types involved
resources.js.controllers.attach_controller.attach_controller→resources.js.controllers.application_controller.ApplicationController
- Direction
- resources.js.controllers.attach_controller uses resources.js.controllers.application_controller, so a change to resources.js.controllers.application_controller can break resources.js.controllers.attach_controller, while a change to resources.js.controllers.attach_controller can't break resources.js.controllers.application_controller.
- Position
- Below the diagonal: resources.js.controllers.attach_controller uses a module listed above it, which is the healthy direction.
18→9 resources.js.controllers.block_editor_controller uses resources.js.controllers.application_controller✕
- Connections
- 1 pair of types, where a type in resources.js.controllers.block_editor_controller uses a type in resources.js.controllers.application_controller.
- The types involved
resources.js.controllers.block_editor_controller.block_editor_controller→resources.js.controllers.application_controller.ApplicationController
- Direction
- resources.js.controllers.block_editor_controller uses resources.js.controllers.application_controller, so a change to resources.js.controllers.application_controller can break resources.js.controllers.block_editor_controller, while a change to resources.js.controllers.block_editor_controller can't break resources.js.controllers.application_controller.
- Position
- Below the diagonal: resources.js.controllers.block_editor_controller uses a module listed above it, which is the healthy direction.
19→9 resources.js.controllers.browsing_controller uses resources.js.controllers.application_controller✕
- Connections
- 1 pair of types, where a type in resources.js.controllers.browsing_controller uses a type in resources.js.controllers.application_controller.
- The types involved
resources.js.controllers.browsing_controller.browsing_controller→resources.js.controllers.application_controller.ApplicationController
- Direction
- resources.js.controllers.browsing_controller uses resources.js.controllers.application_controller, so a change to resources.js.controllers.application_controller can break resources.js.controllers.browsing_controller, while a change to resources.js.controllers.browsing_controller can't break resources.js.controllers.application_controller.
- Position
- Below the diagonal: resources.js.controllers.browsing_controller uses a module listed above it, which is the healthy direction.
20→9 resources.js.controllers.button_controller uses resources.js.controllers.application_controller✕
- Connections
- 1 pair of types, where a type in resources.js.controllers.button_controller uses a type in resources.js.controllers.application_controller.
- The types involved
resources.js.controllers.button_controller.button_controller→resources.js.controllers.application_controller.ApplicationController
- Direction
- resources.js.controllers.button_controller uses resources.js.controllers.application_controller, so a change to resources.js.controllers.application_controller can break resources.js.controllers.button_controller, while a change to resources.js.controllers.button_controller can't break resources.js.controllers.application_controller.
- Position
- Below the diagonal: resources.js.controllers.button_controller uses a module listed above it, which is the healthy direction.
21→9 resources.js.controllers.chart_controller uses resources.js.controllers.application_controller✕
- Connections
- 1 pair of types, where a type in resources.js.controllers.chart_controller uses a type in resources.js.controllers.application_controller.
- The types involved
resources.js.controllers.chart_controller.chart_controller→resources.js.controllers.application_controller.ApplicationController
- Direction
- resources.js.controllers.chart_controller uses resources.js.controllers.application_controller, so a change to resources.js.controllers.application_controller can break resources.js.controllers.chart_controller, while a change to resources.js.controllers.chart_controller can't break resources.js.controllers.application_controller.
- Position
- Below the diagonal: resources.js.controllers.chart_controller uses a module listed above it, which is the healthy direction.
22→9 resources.js.controllers.checkbox_controller uses resources.js.controllers.application_controller✕
- Connections
- 1 pair of types, where a type in resources.js.controllers.checkbox_controller uses a type in resources.js.controllers.application_controller.
- The types involved
resources.js.controllers.checkbox_controller.checkbox_controller→resources.js.controllers.application_controller.ApplicationController
- Direction
- resources.js.controllers.checkbox_controller uses resources.js.controllers.application_controller, so a change to resources.js.controllers.application_controller can break resources.js.controllers.checkbox_controller, while a change to resources.js.controllers.checkbox_controller can't break resources.js.controllers.application_controller.
- Position
- Below the diagonal: resources.js.controllers.checkbox_controller uses a module listed above it, which is the healthy direction.
23→9 resources.js.controllers.code_controller uses resources.js.controllers.application_controller✕
- Connections
- 1 pair of types, where a type in resources.js.controllers.code_controller uses a type in resources.js.controllers.application_controller.
- The types involved
resources.js.controllers.code_controller.code_controller→resources.js.controllers.application_controller.ApplicationController
- Direction
- resources.js.controllers.code_controller uses resources.js.controllers.application_controller, so a change to resources.js.controllers.application_controller can break resources.js.controllers.code_controller, while a change to resources.js.controllers.code_controller can't break resources.js.controllers.application_controller.
- Position
- Below the diagonal: resources.js.controllers.code_controller uses a module listed above it, which is the healthy direction.
24→13 App.Orchid uses Orchid.Platform✕
- Connections
- 2 pairs of types, where a type in App.Orchid uses a type in Orchid.Platform.
- The types involved
App.Orchid.PlatformProvider→Orchid.Platform.OrchidApp.Orchid.PlatformProvider→Orchid.Platform.OrchidServiceProvider
- Direction
- App.Orchid uses Orchid.Platform, so a change to Orchid.Platform can break App.Orchid, while a change to App.Orchid can't break Orchid.Platform.
- Position
- Below the diagonal: App.Orchid uses a module listed above it, which is the healthy direction.
25→16 Orchid.Alert uses Orchid.Support✕
- Connections
- 1 pair of types, where a type in Orchid.Alert uses a type in Orchid.Support.
- The types involved
Orchid.Alert.Alert→Orchid.Support.Color
- Direction
- Orchid.Alert uses Orchid.Support, so a change to Orchid.Support can break Orchid.Alert, while a change to Orchid.Alert can't break Orchid.Support.
- Position
- Below the diagonal: Orchid.Alert uses a module listed above it, which is the healthy direction.
26→8 Orchid.Platform.Http.Controllers uses Orchid.Screen.Fields.Support✕
- Connections
- 1 pair of types, where a type in Orchid.Platform.Http.Controllers uses a type in Orchid.Screen.Fields.Support.
- The types involved
Orchid.Platform.Http.Controllers.ChoicesController→Orchid.Screen.Fields.Support.ChoicePayload
- Direction
- Orchid.Platform.Http.Controllers uses Orchid.Screen.Fields.Support, so a change to Orchid.Screen.Fields.Support can break Orchid.Platform.Http.Controllers, while a change to Orchid.Platform.Http.Controllers can't break Orchid.Screen.Fields.Support.
- Position
- Below the diagonal: Orchid.Platform.Http.Controllers uses a module listed above it, which is the healthy direction.
26→15 Orchid.Platform.Http.Controllers uses Orchid.Platform.Http.Requests✕
- Connections
- 1 pair of types, where a type in Orchid.Platform.Http.Controllers uses a type in Orchid.Platform.Http.Requests.
- The types involved
Orchid.Platform.Http.Controllers.ChoicesController→Orchid.Platform.Http.Requests.ChoicesRequest
- Direction
- Orchid.Platform.Http.Controllers uses Orchid.Platform.Http.Requests, so a change to Orchid.Platform.Http.Requests can break Orchid.Platform.Http.Controllers, while a change to Orchid.Platform.Http.Controllers can't break Orchid.Platform.Http.Requests.
- Position
- Below the diagonal: Orchid.Platform.Http.Controllers uses a module listed above it, which is the healthy direction.
27→16 Orchid.Platform.Notifications uses Orchid.Support✕
- Connections
- 1 pair of types, where a type in Orchid.Platform.Notifications uses a type in Orchid.Support.
- The types involved
Orchid.Platform.Notifications.OrchidMessage→Orchid.Support.Color
- Direction
- Orchid.Platform.Notifications uses Orchid.Support, so a change to Orchid.Support can break Orchid.Platform.Notifications, while a change to Orchid.Platform.Notifications can't break Orchid.Support.
- Position
- Below the diagonal: Orchid.Platform.Notifications uses a module listed above it, which is the healthy direction.
28→1 Orchid.Platform.Providers uses Orchid.Access✕
- Connections
- 1 pair of types, where a type in Orchid.Platform.Providers uses a type in Orchid.Access.
- The types involved
Orchid.Platform.Providers.PlatformServiceProvider→Orchid.Access.PermissionGroup
- Direction
- Orchid.Platform.Providers uses Orchid.Access, so a change to Orchid.Access can break Orchid.Platform.Providers, while a change to Orchid.Platform.Providers can't break Orchid.Access.
- Position
- Below the diagonal: Orchid.Platform.Providers uses a module listed above it, which is the healthy direction.
28→13 Orchid.Platform.Providers uses Orchid.Platform✕
- Connections
- 1 pair of types, where a type in Orchid.Platform.Providers uses a type in Orchid.Platform.
- The types involved
Orchid.Platform.Providers.PlatformServiceProvider→Orchid.Platform.Orchid
- Direction
- Orchid.Platform.Providers uses Orchid.Platform, so a change to Orchid.Platform can break Orchid.Platform.Providers, while a change to Orchid.Platform.Providers can't break Orchid.Platform.
- Position
- Below the diagonal: Orchid.Platform.Providers uses a module listed above it, which is the healthy direction.
29→16 Orchid.Screen.Actions uses Orchid.Support✕
- Connections
- 1 pair of types, where a type in Orchid.Screen.Actions uses a type in Orchid.Support.
- The types involved
Orchid.Screen.Actions.Menu→Orchid.Support.Color
- Direction
- Orchid.Screen.Actions uses Orchid.Support, so a change to Orchid.Support can break Orchid.Screen.Actions, while a change to Orchid.Screen.Actions can't break Orchid.Support.
- Position
- Below the diagonal: Orchid.Screen.Actions uses a module listed above it, which is the healthy direction.
29→33 Orchid.Screen.Actions uses Orchid.Screen part of a loop✕
- Connections
- 5 pairs of types, where a type in Orchid.Screen.Actions uses a type in Orchid.Screen.
- The types involved
Orchid.Screen.Actions.Button→Orchid.Screen.ActionOrchid.Screen.Actions.DropDown→Orchid.Screen.ActionOrchid.Screen.Actions.DropDown→Orchid.Screen.RepositoryOrchid.Screen.Actions.Link→Orchid.Screen.ActionOrchid.Screen.Actions.Menu→Orchid.Screen.Repository
- Direction
- Orchid.Screen.Actions uses Orchid.Screen, so a change to Orchid.Screen can break Orchid.Screen.Actions, while a change to Orchid.Screen.Actions can't break Orchid.Screen.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→16 Orchid.Screen.Contracts uses Orchid.Support✕
- Connections
- 1 pair of types, where a type in Orchid.Screen.Contracts uses a type in Orchid.Support.
- The types involved
Orchid.Screen.Contracts.Cardable→Orchid.Support.Color
- Direction
- Orchid.Screen.Contracts uses Orchid.Support, so a change to Orchid.Support can break Orchid.Screen.Contracts, while a change to Orchid.Screen.Contracts can't break Orchid.Support.
- Position
- Below the diagonal: Orchid.Screen.Contracts uses a module listed above it, which is the healthy direction.
30→33 Orchid.Screen.Contracts uses Orchid.Screen part of a loop✕
- Connections
- 1 pair of types, where a type in Orchid.Screen.Contracts uses a type in Orchid.Screen.
- The types involved
Orchid.Screen.Contracts.Actionable→Orchid.Screen.Repository
- Direction
- Orchid.Screen.Contracts uses Orchid.Screen, so a change to Orchid.Screen can break Orchid.Screen.Contracts, while a change to Orchid.Screen.Contracts can't break Orchid.Screen.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→16 App.Orchid.Presenters uses Orchid.Support✕
- Connections
- 1 pair of types, where a type in App.Orchid.Presenters uses a type in Orchid.Support.
- The types involved
App.Orchid.Presenters.UserPresenter→Orchid.Support.Presenter
- Direction
- App.Orchid.Presenters uses Orchid.Support, so a change to Orchid.Support can break App.Orchid.Presenters, while a change to App.Orchid.Presenters can't break Orchid.Support.
- Position
- Below the diagonal: App.Orchid.Presenters uses a module listed above it, which is the healthy direction.
31→30 App.Orchid.Presenters uses Orchid.Screen.Contracts✕
- Connections
- 2 pairs of types, where a type in App.Orchid.Presenters uses a type in Orchid.Screen.Contracts.
- The types involved
App.Orchid.Presenters.UserPresenter→Orchid.Screen.Contracts.PersonableApp.Orchid.Presenters.UserPresenter→Orchid.Screen.Contracts.Searchable
- Direction
- App.Orchid.Presenters uses Orchid.Screen.Contracts, so a change to Orchid.Screen.Contracts can break App.Orchid.Presenters, while a change to App.Orchid.Presenters can't break Orchid.Screen.Contracts.
- Position
- Below the diagonal: App.Orchid.Presenters uses a module listed above it, which is the healthy direction.
32→29 Orchid.Screen.Layouts uses Orchid.Screen.Actions✕
- Connections
- 1 pair of types, where a type in Orchid.Screen.Layouts uses a type in Orchid.Screen.Actions.
- The types involved
Orchid.Screen.Layouts.SideMenu→Orchid.Screen.Actions.Menu
- Direction
- Orchid.Screen.Layouts uses Orchid.Screen.Actions, so a change to Orchid.Screen.Actions can break Orchid.Screen.Layouts, while a change to Orchid.Screen.Layouts can't break Orchid.Screen.Actions.
- Position
- Below the diagonal: Orchid.Screen.Layouts uses a module listed above it, which is the healthy direction.
32→30 Orchid.Screen.Layouts uses Orchid.Screen.Contracts✕
- Connections
- 2 pairs of types, where a type in Orchid.Screen.Layouts uses a type in Orchid.Screen.Contracts.
- The types involved
Orchid.Screen.Layouts.Card→Orchid.Screen.Contracts.CardableOrchid.Screen.Layouts.Persona→Orchid.Screen.Contracts.Personable
- Direction
- Orchid.Screen.Layouts uses Orchid.Screen.Contracts, so a change to Orchid.Screen.Contracts can break Orchid.Screen.Layouts, while a change to Orchid.Screen.Layouts can't break Orchid.Screen.Contracts.
- Position
- Below the diagonal: Orchid.Screen.Layouts uses a module listed above it, which is the healthy direction.
32→33 Orchid.Screen.Layouts uses Orchid.Screen part of a loop✕
- Connections
- 44 pairs of types, where a type in Orchid.Screen.Layouts uses a type in Orchid.Screen. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Orchid.Screen.Layouts.Accordion→Orchid.Screen.LayoutOrchid.Screen.Layouts.Accordion→Orchid.Screen.RepositoryOrchid.Screen.Layouts.Blank→Orchid.Screen.LayoutOrchid.Screen.Layouts.Blank→Orchid.Screen.RepositoryOrchid.Screen.Layouts.Block→Orchid.Screen.LayoutOrchid.Screen.Layouts.Block→Orchid.Screen.RepositoryOrchid.Screen.Layouts.Browsing→Orchid.Screen.LayoutOrchid.Screen.Layouts.Browsing→Orchid.Screen.RepositoryOrchid.Screen.Layouts.Chart→Orchid.Screen.LayoutOrchid.Screen.Layouts.Chart→Orchid.Screen.RepositoryOrchid.Screen.Layouts.Columns→Orchid.Screen.LayoutOrchid.Screen.Layouts.Columns→Orchid.Screen.RepositoryOrchid.Screen.Layouts.Component→Orchid.Screen.LayoutOrchid.Screen.Layouts.Component→Orchid.Screen.RepositoryOrchid.Screen.Layouts.Content→Orchid.Screen.LayoutOrchid.Screen.Layouts.Content→Orchid.Screen.RepositoryOrchid.Screen.Layouts.Legend→Orchid.Screen.LayoutOrchid.Screen.Layouts.Legend→Orchid.Screen.RepositoryOrchid.Screen.Layouts.Listener→Orchid.Screen.LayoutOrchid.Screen.Layouts.Listener→Orchid.Screen.RepositoryOrchid.Screen.Layouts.Metric→Orchid.Screen.LayoutOrchid.Screen.Layouts.Metric→Orchid.Screen.RepositoryOrchid.Screen.Layouts.Modal→Orchid.Screen.LayoutOrchid.Screen.Layouts.Modal→Orchid.Screen.RepositoryOrchid.Screen.Layouts.Rows→Orchid.Screen.Layout
- Direction
- Orchid.Screen.Layouts uses Orchid.Screen, so a change to Orchid.Screen can break Orchid.Screen.Layouts, while a change to Orchid.Screen.Layouts can't break Orchid.Screen.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→16 Orchid.Screen uses Orchid.Support✕
- Connections
- 1 pair of types, where a type in Orchid.Screen uses a type in Orchid.Support.
- The types involved
Orchid.Screen.Action→Orchid.Support.Color
- Direction
- Orchid.Screen uses Orchid.Support, so a change to Orchid.Support can break Orchid.Screen, while a change to Orchid.Screen can't break Orchid.Support.
- Position
- Below the diagonal: Orchid.Screen uses a module listed above it, which is the healthy direction.
33→26 Orchid.Screen uses Orchid.Platform.Http.Controllers✕
- Connections
- 1 pair of types, where a type in Orchid.Screen uses a type in Orchid.Platform.Http.Controllers.
- The types involved
Orchid.Screen.Screen→Orchid.Platform.Http.Controllers.Controller
- Direction
- Orchid.Screen uses Orchid.Platform.Http.Controllers, so a change to Orchid.Platform.Http.Controllers can break Orchid.Screen, while a change to Orchid.Screen can't break Orchid.Platform.Http.Controllers.
- Position
- Below the diagonal: Orchid.Screen uses a module listed above it, which is the healthy direction.
33→30 Orchid.Screen uses Orchid.Screen.Contracts✕
- Connections
- 4 pairs of types, where a type in Orchid.Screen uses a type in Orchid.Screen.Contracts.
- The types involved
Orchid.Screen.Action→Orchid.Screen.Contracts.ActionableOrchid.Screen.Builder→Orchid.Screen.Contracts.FieldableOrchid.Screen.Builder→Orchid.Screen.Contracts.GroupableOrchid.Screen.Field→Orchid.Screen.Contracts.Fieldable
- Direction
- Orchid.Screen uses Orchid.Screen.Contracts, so a change to Orchid.Screen.Contracts can break Orchid.Screen, while a change to Orchid.Screen can't break Orchid.Screen.Contracts.
- Position
- Below the diagonal: Orchid.Screen uses a module listed above it, which is the healthy direction.
33→32 Orchid.Screen uses Orchid.Screen.Layouts✕
- Connections
- 19 pairs of types, where a type in Orchid.Screen uses a type in Orchid.Screen.Layouts.
- The types involved
Orchid.Screen.LayoutFactory→Orchid.Screen.Layouts.AccordionOrchid.Screen.LayoutFactory→Orchid.Screen.Layouts.BlankOrchid.Screen.LayoutFactory→Orchid.Screen.Layouts.BlockOrchid.Screen.LayoutFactory→Orchid.Screen.Layouts.BrowsingOrchid.Screen.LayoutFactory→Orchid.Screen.Layouts.ChartOrchid.Screen.LayoutFactory→Orchid.Screen.Layouts.ColumnsOrchid.Screen.LayoutFactory→Orchid.Screen.Layouts.ComponentOrchid.Screen.LayoutFactory→Orchid.Screen.Layouts.LegendOrchid.Screen.LayoutFactory→Orchid.Screen.Layouts.MetricOrchid.Screen.LayoutFactory→Orchid.Screen.Layouts.ModalOrchid.Screen.LayoutFactory→Orchid.Screen.Layouts.RowsOrchid.Screen.LayoutFactory→Orchid.Screen.Layouts.SelectionOrchid.Screen.LayoutFactory→Orchid.Screen.Layouts.SortableOrchid.Screen.LayoutFactory→Orchid.Screen.Layouts.SplitOrchid.Screen.LayoutFactory→Orchid.Screen.Layouts.TableOrchid.Screen.LayoutFactory→Orchid.Screen.Layouts.TabsOrchid.Screen.LayoutFactory→Orchid.Screen.Layouts.ViewOrchid.Screen.LayoutFactory→Orchid.Screen.Layouts.WrapperOrchid.Screen.Screen→Orchid.Screen.Layouts.Listener
- Direction
- Orchid.Screen uses Orchid.Screen.Layouts, so a change to Orchid.Screen.Layouts can break Orchid.Screen, while a change to Orchid.Screen can't break Orchid.Screen.Layouts.
- Position
- Below the diagonal: Orchid.Screen uses a module listed above it, which is the healthy direction.
34→33 App.Orchid.Screens uses Orchid.Screen✕
- Connections
- 1 pair of types, where a type in App.Orchid.Screens uses a type in Orchid.Screen.
- The types involved
App.Orchid.Screens.WelcomeScreen→Orchid.Screen.Screen
- Direction
- App.Orchid.Screens uses Orchid.Screen, so a change to Orchid.Screen can break App.Orchid.Screens, while a change to App.Orchid.Screens can't break Orchid.Screen.
- Position
- Below the diagonal: App.Orchid.Screens uses a module listed above it, which is the healthy direction.
35→6 App.Orchid.Screens.Role uses Orchid.Platform.Models✕
- Connections
- 1 pair of types, where a type in App.Orchid.Screens.Role uses a type in Orchid.Platform.Models.
- The types involved
App.Orchid.Screens.Role.RoleEditScreen→Orchid.Platform.Models.Role
- Direction
- App.Orchid.Screens.Role uses Orchid.Platform.Models, so a change to Orchid.Platform.Models can break App.Orchid.Screens.Role, while a change to App.Orchid.Screens.Role can't break Orchid.Platform.Models.
- Position
- Below the diagonal: App.Orchid.Screens.Role uses a module listed above it, which is the healthy direction.
35→33 App.Orchid.Screens.Role uses Orchid.Screen✕
- Connections
- 2 pairs of types, where a type in App.Orchid.Screens.Role uses a type in Orchid.Screen.
- The types involved
App.Orchid.Screens.Role.RoleEditScreen→Orchid.Screen.ScreenApp.Orchid.Screens.Role.RoleListScreen→Orchid.Screen.Screen
- Direction
- App.Orchid.Screens.Role uses Orchid.Screen, so a change to Orchid.Screen can break App.Orchid.Screens.Role, while a change to App.Orchid.Screens.Role can't break Orchid.Screen.
- Position
- Below the diagonal: App.Orchid.Screens.Role uses a module listed above it, which is the healthy direction.
36→6 App.Orchid.Screens.User uses Orchid.Platform.Models✕
- Connections
- 2 pairs of types, where a type in App.Orchid.Screens.User uses a type in Orchid.Platform.Models.
- The types involved
App.Orchid.Screens.User.UserEditScreen→Orchid.Platform.Models.UserApp.Orchid.Screens.User.UserListScreen→Orchid.Platform.Models.User
- Direction
- App.Orchid.Screens.User uses Orchid.Platform.Models, so a change to Orchid.Platform.Models can break App.Orchid.Screens.User, while a change to App.Orchid.Screens.User can't break Orchid.Platform.Models.
- Position
- Below the diagonal: App.Orchid.Screens.User uses a module listed above it, which is the healthy direction.
36→33 App.Orchid.Screens.User uses Orchid.Screen✕
- Connections
- 3 pairs of types, where a type in App.Orchid.Screens.User uses a type in Orchid.Screen.
- The types involved
App.Orchid.Screens.User.UserEditScreen→Orchid.Screen.ScreenApp.Orchid.Screens.User.UserListScreen→Orchid.Screen.ScreenApp.Orchid.Screens.User.UserProfileScreen→Orchid.Screen.Screen
- Direction
- App.Orchid.Screens.User uses Orchid.Screen, so a change to Orchid.Screen can break App.Orchid.Screens.User, while a change to App.Orchid.Screens.User can't break Orchid.Screen.
- Position
- Below the diagonal: App.Orchid.Screens.User uses a module listed above it, which is the healthy direction.
37→1 Orchid.Platform.Configuration uses Orchid.Access✕
- Connections
- 2 pairs of types, where a type in Orchid.Platform.Configuration uses a type in Orchid.Access.
- The types involved
Orchid.Platform.Configuration.ManagesPermissions→Orchid.Access.PermissionGroupOrchid.Platform.Configuration.ManagesPermissions→Orchid.Access.Permissions
- Direction
- Orchid.Platform.Configuration uses Orchid.Access, so a change to Orchid.Access can break Orchid.Platform.Configuration, while a change to Orchid.Platform.Configuration can't break Orchid.Access.
- Position
- Below the diagonal: Orchid.Platform.Configuration uses a module listed above it, which is the healthy direction.
37→29 Orchid.Platform.Configuration uses Orchid.Screen.Actions✕
- Connections
- 1 pair of types, where a type in Orchid.Platform.Configuration uses a type in Orchid.Screen.Actions.
- The types involved
Orchid.Platform.Configuration.ManagesMenu→Orchid.Screen.Actions.Menu
- Direction
- Orchid.Platform.Configuration uses Orchid.Screen.Actions, so a change to Orchid.Screen.Actions can break Orchid.Platform.Configuration, while a change to Orchid.Platform.Configuration can't break Orchid.Screen.Actions.
- Position
- Below the diagonal: Orchid.Platform.Configuration uses a module listed above it, which is the healthy direction.
37→33 Orchid.Platform.Configuration uses Orchid.Screen✕
- Connections
- 1 pair of types, where a type in Orchid.Platform.Configuration uses a type in Orchid.Screen.
- The types involved
Orchid.Platform.Configuration.ManagesScreens→Orchid.Screen.Screen
- Direction
- Orchid.Platform.Configuration uses Orchid.Screen, so a change to Orchid.Screen can break Orchid.Platform.Configuration, while a change to Orchid.Platform.Configuration can't break Orchid.Screen.
- Position
- Below the diagonal: Orchid.Platform.Configuration uses a module listed above it, which is the healthy direction.
38→33 Orchid.Screen.Concerns uses Orchid.Screen✕
- Connections
- 4 pairs of types, where a type in Orchid.Screen.Concerns uses a type in Orchid.Screen.
- The types involved
Orchid.Screen.Concerns.HasCommandBar→Orchid.Screen.RepositoryOrchid.Screen.Concerns.HasEmptyState→Orchid.Screen.ActionOrchid.Screen.Concerns.HasFillablePublicProperties→Orchid.Screen.RepositoryOrchid.Screen.Concerns.InteractsWithEncryptedState→Orchid.Screen.Repository
- Direction
- Orchid.Screen.Concerns uses Orchid.Screen, so a change to Orchid.Screen can break Orchid.Screen.Concerns, while a change to Orchid.Screen.Concerns can't break Orchid.Screen.
- Position
- Below the diagonal: Orchid.Screen.Concerns uses a module listed above it, which is the healthy direction.
39→8 Orchid.Screen.Fields uses Orchid.Screen.Fields.Support✕
- Connections
- 1 pair of types, where a type in Orchid.Screen.Fields uses a type in Orchid.Screen.Fields.Support.
- The types involved
Orchid.Screen.Fields.Select→Orchid.Screen.Fields.Support.ChoicePayload
- Direction
- Orchid.Screen.Fields uses Orchid.Screen.Fields.Support, so a change to Orchid.Screen.Fields.Support can break Orchid.Screen.Fields, while a change to Orchid.Screen.Fields can't break Orchid.Screen.Fields.Support.
- Position
- Below the diagonal: Orchid.Screen.Fields uses a module listed above it, which is the healthy direction.
39→30 Orchid.Screen.Fields uses Orchid.Screen.Contracts✕
- Connections
- 2 pairs of types, where a type in Orchid.Screen.Fields uses a type in Orchid.Screen.Contracts.
- The types involved
Orchid.Screen.Fields.Group→Orchid.Screen.Contracts.FieldableOrchid.Screen.Fields.Group→Orchid.Screen.Contracts.Groupable
- Direction
- Orchid.Screen.Fields uses Orchid.Screen.Contracts, so a change to Orchid.Screen.Contracts can break Orchid.Screen.Fields, while a change to Orchid.Screen.Fields can't break Orchid.Screen.Contracts.
- Position
- Below the diagonal: Orchid.Screen.Fields uses a module listed above it, which is the healthy direction.
39→33 Orchid.Screen.Fields uses Orchid.Screen✕
- Connections
- 26 pairs of types, where a type in Orchid.Screen.Fields uses a type in Orchid.Screen. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Orchid.Screen.Fields.Attach→Orchid.Screen.FieldOrchid.Screen.Fields.BlockEditor→Orchid.Screen.FieldOrchid.Screen.Fields.CheckBox→Orchid.Screen.FieldOrchid.Screen.Fields.Code→Orchid.Screen.FieldOrchid.Screen.Fields.DateRange→Orchid.Screen.FieldOrchid.Screen.Fields.DateTimer→Orchid.Screen.FieldOrchid.Screen.Fields.Input→Orchid.Screen.FieldOrchid.Screen.Fields.KeyValue→Orchid.Screen.FieldOrchid.Screen.Fields.Label→Orchid.Screen.FieldOrchid.Screen.Fields.Map→Orchid.Screen.FieldOrchid.Screen.Fields.Markdown→Orchid.Screen.FieldOrchid.Screen.Fields.Matrix→Orchid.Screen.FieldOrchid.Screen.Fields.NumberRange→Orchid.Screen.FieldOrchid.Screen.Fields.Password→Orchid.Screen.FieldOrchid.Screen.Fields.Picture→Orchid.Screen.FieldOrchid.Screen.Fields.Quill→Orchid.Screen.FieldOrchid.Screen.Fields.Radio→Orchid.Screen.FieldOrchid.Screen.Fields.RadioButtons→Orchid.Screen.FieldOrchid.Screen.Fields.Range→Orchid.Screen.FieldOrchid.Screen.Fields.Repeater→Orchid.Screen.FieldOrchid.Screen.Fields.Select→Orchid.Screen.FieldOrchid.Screen.Fields.Switcher→Orchid.Screen.FieldOrchid.Screen.Fields.TextArea→Orchid.Screen.FieldOrchid.Screen.Fields.TimeZone→Orchid.Screen.FieldOrchid.Screen.Fields.UTM→Orchid.Screen.Field
- Direction
- Orchid.Screen.Fields uses Orchid.Screen, so a change to Orchid.Screen can break Orchid.Screen.Fields, while a change to Orchid.Screen.Fields can't break Orchid.Screen.
- Position
- Below the diagonal: Orchid.Screen.Fields uses a module listed above it, which is the healthy direction.
39→38 Orchid.Screen.Fields uses Orchid.Screen.Concerns✕
- Connections
- 3 pairs of types, where a type in Orchid.Screen.Fields uses a type in Orchid.Screen.Concerns.
- The types involved
Orchid.Screen.Fields.DateRange→Orchid.Screen.Concerns.ComplexFieldConcernOrchid.Screen.Fields.NumberRange→Orchid.Screen.Concerns.ComplexFieldConcernOrchid.Screen.Fields.Select→Orchid.Screen.Concerns.ComplexFieldConcern
- Direction
- Orchid.Screen.Fields uses Orchid.Screen.Concerns, so a change to Orchid.Screen.Concerns can break Orchid.Screen.Fields, while a change to Orchid.Screen.Fields can't break Orchid.Screen.Concerns.
- Position
- Below the diagonal: Orchid.Screen.Fields uses a module listed above it, which is the healthy direction.
40→6 App.Orchid.Layouts.User uses Orchid.Platform.Models✕
- Connections
- 1 pair of types, where a type in App.Orchid.Layouts.User uses a type in Orchid.Platform.Models.
- The types involved
App.Orchid.Layouts.User.PermissionLayout→Orchid.Platform.Models.User
- Direction
- App.Orchid.Layouts.User uses Orchid.Platform.Models, so a change to Orchid.Platform.Models can break App.Orchid.Layouts.User, while a change to App.Orchid.Layouts.User can't break Orchid.Platform.Models.
- Position
- Below the diagonal: App.Orchid.Layouts.User uses a module listed above it, which is the healthy direction.
40→32 App.Orchid.Layouts.User uses Orchid.Screen.Layouts✕
- Connections
- 7 pairs of types, where a type in App.Orchid.Layouts.User uses a type in Orchid.Screen.Layouts.
- The types involved
App.Orchid.Layouts.User.PermissionLayout→Orchid.Screen.Layouts.RowsApp.Orchid.Layouts.User.ProfilePasswordLayout→Orchid.Screen.Layouts.RowsApp.Orchid.Layouts.User.UserEditLayout→Orchid.Screen.Layouts.RowsApp.Orchid.Layouts.User.UserFiltersLayout→Orchid.Screen.Layouts.SelectionApp.Orchid.Layouts.User.UserListLayout→Orchid.Screen.Layouts.TableApp.Orchid.Layouts.User.UserPasswordLayout→Orchid.Screen.Layouts.RowsApp.Orchid.Layouts.User.UserRoleLayout→Orchid.Screen.Layouts.Rows
- Direction
- App.Orchid.Layouts.User uses Orchid.Screen.Layouts, so a change to Orchid.Screen.Layouts can break App.Orchid.Layouts.User, while a change to App.Orchid.Layouts.User can't break Orchid.Screen.Layouts.
- Position
- Below the diagonal: App.Orchid.Layouts.User uses a module listed above it, which is the healthy direction.
40→39 App.Orchid.Layouts.User uses Orchid.Screen.Fields✕
- Connections
- 1 pair of types, where a type in App.Orchid.Layouts.User uses a type in Orchid.Screen.Fields.
- The types involved
App.Orchid.Layouts.User.PermissionLayout→Orchid.Screen.Fields.CheckBox
- Direction
- App.Orchid.Layouts.User uses Orchid.Screen.Fields, so a change to Orchid.Screen.Fields can break App.Orchid.Layouts.User, while a change to App.Orchid.Layouts.User can't break Orchid.Screen.Fields.
- Position
- Below the diagonal: App.Orchid.Layouts.User uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 34 | High / Critical |
| A07:2025 — Authentication Failures | 3 | High / Critical |
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up; Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with readme.md. | +1.6 pts | Low | Documentation Quality |
| Resolve the 4 redundant comment finding(s) in Comment Value — start with modal_controller.js (2), browsing_controller.js, form_controller.js. | +1.6 pts | Low | Comment Value |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +2.9 pts | Medium | Keyboard semantics |
| Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. | +2.6 pts | Medium | Type Safety |
| Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive. | +2.4 pts | Medium | Nullable reference types |
| Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. | +2.2 pts | Medium | Text alternatives |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +1.7 pts | Medium | Page structure |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +1.7 pts | Medium | Forms & labels |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Access/RoleAccess.php | 6.5 | Mixed | Coupling: Circular dependency |
| resources/js/controllers/block_editor_controller.js | 7.1 | Mixed | Cyclomatic Complexity: #normalize (cyclomatic 18) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Screen/Layouts/Chart.php | 7.8 | Mixed | Cyclomatic Complexity: Chart.build (cyclomatic 34) |
| src/Screen/Fields/KeyValue.php | 7.8 | Mixed | Cyclomatic Complexity: KeyValue.updateFieldValue (cyclomatic 18) |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| tests/App/RouteSolving.php | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/Screen/Concerns/Multipliable.php | 8.2 | Near-clean | Explicit Debt: TodoComment |
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 57 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
What we checked — 57 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, 124 of 133 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.php) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- 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 source is present (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 6 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository declares a composer.json but commits no composer.lock this pass can read, so the set of packages it installs is not on disk: its composer.json states version CONSTRAINTS, and Composer's guidance is that a library leaves the lock uncommitted. Producing the graph needs Composer's solver, which this pass does not run, and grading whichever release happens to be newest today would be a verdict about a dependency graph nobody resolved. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- 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 (186 contributor(s) across 6356 commit(s) sampled, automation and bot accounts excluded). One of them holds 86% of the history; the other 185 hold 0.1% 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.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D26 Project Cohesion — 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. `(repository root)` (24091 LoC, 293 module-visible types across 50 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/Filters/AllowedFilters.php`, `src/Filters/AllowedSorts.php`, `src/Filters/HttpFilter.php`, `src/Platform/Components/Breadcrumbs.php`, `src/Platform/Http/Middleware/BladeIcons.php`, … (+5 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D34 Knowledge Freshness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 47 commits in the last 90 days, yet 44 of 76 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- D43 Malicious Dependencies — measured, with a gap in what it reached — 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. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
- AC6 Visual & motion safety — 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. Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentOutOfRangeException: startIndex cannot be larger than length of string. (Parameter 'startIndex').
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Laravel's service container and a PSR-11 container (Psr\Container), whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 104 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C1 Data Protection — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- C2 Access Controls — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's PHP is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's PHP is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X27 Collection changed while being enumerated — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- 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, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- 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.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- 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.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Chart.build at 34.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Chart.build (cyclomatic 34), KeyValue.updateFieldValue (cyclomatic 18), #normalize (cyclomatic 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
7 method(s) exceeded the cognitive complexity threshold of 15; the worst was Chart.build at 33.
What to do
- Bring the 6 bodies over 15 down to 15 or less in Cognitive Complexity — start with Chart.build (cognitive 33), KeyValue.updateFieldValue (cognitive 26), ModelStateRetrievable.__serialize (cognitive 20). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cognitive Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
3 god class(es) detected.
What to do
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with block_editor_controller.js, Field.php. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with block_editor_controller.js. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
0 duplicated block group(s) detected. 0.2 % of the production lines (48 of 21,937) are in a reported copy. A further 3 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 1 Edited copy of a member (15 corresponding lines) finding(s) in Code Duplication — start with Attach.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with RoleAccess.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with UserListScreen.php. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
16 production modules (source-import), 1 dependency cycle(s), 0 unstable depended-on module(s). No manifest declares this repository's modules, so the modules are its top-level source directories and the edges the imports between them; 1 module(s) off the main sequence, with abstractness counted on 11 of the 16 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Circular dependency finding(s) in Coupling — start with RoleAccess.php. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
1 of 42 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with Orchid.php. — One of this dimension's main actionable groups (1 warning-level).
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 8 tests.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
D15 · Churn × Complexity Hotspots
Top hotspots: src/Screen/Layouts/Chart.php (3×34=102); resources/js/controllers/repeater_controller.js (3×17=51) Repeated repair below the complexity floor: resources/js/controllers/attach_controller.js (3 of 3 changes were fixes)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with Chart.php, repeater_controller.js. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with attach_controller.js. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
2 deducted task-comment markers across 21937 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.
What to do
- Resolve the 2 TodoComment finding(s) in Explicit Debt — start with RouteSolving.php, Multipliable.php. — One of this dimension's main actionable groups (2 warning-level).
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 1 document(s) read across 1 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with readme.md. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
6 domain type(s) cross context boundaries across 2 contexts; they are measured and withheld (not published, not scored). Contexts: Attachment, Platform.
D24 · Comment Value
4 of 46 judged comments only repeat the code they sit on (8.7 %).
What to do
- Resolve the 4 redundant comment finding(s) in Comment Value — start with modal_controller.js (2), browsing_controller.js, form_controller.js. — One of this dimension's main actionable groups (4 recommendation-level).
D27 · Navigability
21 % of calls cross a namespace and 2 % go through an interface, but 73 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
2 finding(s): 0 critical, 2 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 2 REDACTED finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 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)
34 finding(s): 0 critical, 30 high, 4 medium, 0 low. 27 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 10 file(s) — `src/Filters/AllowedFilters.php` (line 13), `src/Filters/AllowedSorts.php` (line 13), `src/Filters/HttpFilter.php` (line 24), `src/Platform/Components/Breadcrumbs.php` (line 18, line 23, line 28, …), `src/Platform/Http/Middleware/BladeIcons.php` (line 14), … (+5 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 26 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 (26 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D35 · Change Coupling
Strongest change-coupling: Role.php↔User.php 93%; RoleEditScreen.php↔RoleListScreen.php 71%; cropper_controller.js↔cropper.blade.php 71%
What to do
- Resolve the 7 Change coupling finding(s) in Change Coupling — start with Role.php, RoleEditScreen.php, cropper_controller.js. — One of this dimension's main actionable groups (7 warning-level).
D43 · Malicious Dependencies
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 45 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- An svg presented as an image needs a name — add a <title> child or an aria-label/aria-labelledby. — resources/views/footer.blade.php:0
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — resources/views/layouts/card.blade.php:7
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×4) — resources/views/components/breadcrumbs.blade.php:11, resources/views/layouts/card.blade.php:25, resources/views/partials/layouts/filter.blade.php:2, …
- This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×2) — resources/views/fields/datetime.blade.php:23, resources/views/fields/map.blade.php:29
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — resources/views/fields/map.blade.php:30
- A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one. (×5) — resources/views/layouts/block.blade.php:1, resources/views/layouts/legend.blade.php:1, resources/views/layouts/row.blade.php:1, …
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — resources/views/app.blade.php:2
- user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. — resources/views/app.blade.php:9
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. (×4) — resources/views/fields/cropper.blade.php:57, resources/views/layouts/modal.blade.php:2, resources/views/partials/confirm.blade.php:1, …
- This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — resources/views/partials/search/modal.blade.php:1
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AX10 · Code composition
AX3 · Project dependency cycles
- The projects src/Access → src/Platform → src/Access (one cycle inside a mutually-dependent group of 8 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference. — src/Access/RoleAccess.php:10
What to do
- Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / REDACTED Manager, HashiCorp Vault — not only APP_KEY in .env) and encrypt the most sensitive columns (Eloquent 'encrypted' casts, CipherSweet) — partial coverage still leaves gaps.
- Enforce HTTPS (URL::forceScheme('https') / URL::forceHttps() in Laravel, or requires_channel: https / route schemes in Symfony) so data in transit is always encrypted.
C2 · Access Controls
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
What to do
- Name the access rules — Gate abilities and policy classes (Gate::define, a UserPolicy), spatie/laravel-permission roles and permissions, or a Symfony Voter — and consult them where access is checked ($this->authorize, a can: middleware, #[IsGranted]), so the rule set is reviewable and testable on its own.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
P8 · Schema migrations
PF3 · Async & latency hygiene
R1 · Type Safety
- 0 typed · 45 plain JS — the untyped files are resources/js/app.js, resources/js/controllers/application_controller.js, resources/js/controllers/attach_controller.js, resources/js/controllers/block_editor_controller.js, resources/js/controllers/browsing_controller.js, resources/js/controllers/button_controller.js (+39 more).
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
- resources/js/controllers/cropper_controller.js:26 · resources/js/controllers/picture_controller.js:9 — the two spans are one implementation copied and then locally edited — 424 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — resources/js/controllers/cropper_controller.js:26
- resources/js/controllers/code_controller.js:57 · REDACTED:161 — the two spans are one implementation copied and then locally edited — 167 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — resources/js/controllers/code_controller.js:57
- resources/js/controllers/key_value_controller.js:35 · resources/js/controllers/repeater_controller.js:168 — the two spans are one implementation copied and then locally edited — 94 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — resources/js/controllers/key_value_controller.js:35
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries
- resources/js/controllers/datetime_controller.js:2 imports flatpickr/dist/plugins/rangePlugin, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — resources/js/controllers/datetime_controller.js:2
- resources/js/controllers/datetime_controller.js:4 imports flatpickr/dist/l10n, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — resources/js/controllers/datetime_controller.js:4
What to do
- Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity
- #normalize has cyclomatic complexity 18 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — resources/js/controllers/block_editor_controller.js:775
- #embedSrc has cyclomatic complexity 14 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — resources/js/controllers/block_editor_controller.js:1129
- render has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — resources/js/controllers/chart_controller.js:73
- (anonymous) has cyclomatic complexity 13 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — resources/js/controllers/repeater_controller.js:32
- #supportedBlock has cyclomatic complexity 13 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — resources/js/controllers/block_editor_controller.js:739
- #convertBlock has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — resources/js/controllers/block_editor_controller.js:844
R3 · Large Files
- resources/js/controllers/block_editor_controller.js has 1075 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — resources/js/controllers/block_editor_controller.js:1
- REDACTED has 500 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- 0% of 45 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
- test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
R7 · Dead Code
R8 · Dependency Hygiene
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. — resources/js/controllers/code_controller.js:25
- Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×5) — package.json:11, package.json:17, package.json:23, …
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — resources/js/controllers/block_editor_controller.js:732
What to do
- Swallowed exception (empty catch)
X5 · Nullable reference types
- 0/1 of this repository's PHPStan/Psalm configuration(s) run at a level that checks null — PHPStan level 8 or above (`max` included), or Psalm `errorLevel` 3 or below (Psalm's default, with none stated, is 1). A PHPStan level written neither in the file nor in an include inside the repository is 0, PHPStan's own default. Below those levels the checker removes `null` from a union before any rule looks, so `$order->customer()->name()` on a `?Customer` passes, and the first null reaching it is an `Error: Call to a member function name() on null` in production.
What to do
- Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 46.5 | Weak — gated by R1, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 75.5 | Adequate — gated by D5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 54.3 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 56.3 | Adequate — gated by R4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 56.3 | Adequate — gated by C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 45.7 | Weak — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 5 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model, a change-history library on the models — spatie/laravel-activitylog's LogsActivity, owen-it/laravel-auditing's Auditable, venturecraft/revisionable, Gedmo Loggable — or an Eloquent model event, observer or Doctrine listener that records each change) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 64 check(s) not relevant to this codebase
- AC6 Visual & motion safety — Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- D11 Test Reliability — Test reliability not included — no .php test runner
- D12 Dependency Hygiene — Not scored — 6 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — Composer package licences not graded — this repository commits no composer.lock and this pass does not run Composer's solver
- 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.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
- D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed PHP surface was not measured.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 10 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 3 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 5 value object(s); its 3 aggregate(s) are ORM models only — persistence, not behaviour: a CRUD model, measured, not claimed as DDD
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P2 Observability — This repository's JavaScript/TypeScript, PHP source (2 module(s), 408 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript, PHP source (service entry point: workbench/routes/web.php:8 (Route::get())
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — X1 reached only 22% of this repository's production lines — php (18,848 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X12 Unreachable branch — X12 reached only 22% of this repository's production lines — php (18,848 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's PHP was read and makes no request a caller can cancel (amphp's HttpClient or connect) — synchronous PHP offers its callers no cancellation to take
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — X24 reached only 22% of this repository's production lines — php (18,848 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 45 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
- <button> with no accessible text resources/views/components/breadcrumbs.blade.php:11
- <button> with no accessible text resources/views/layouts/card.blade.php:25
- <button> with no accessible text resources/views/partials/layouts/filter.blade.php:2
- <button> with no accessible text resources/views/partials/notification/item.blade.php:2
- <label> that labels no control resources/views/fields/datetime.blade.php:23
- <label> that labels no control resources/views/fields/map.blade.php:29
- REDACTED
- REDACTED
- <svg role="img"> without an accessible name resources/views/footer.blade.php
- <img> without a text alternative resources/views/layouts/card.blade.php:7
- <input> without a programmatic label resources/views/fields/map.blade.php:30
- Viewport restricts zoom resources/views/app.blade.php:9
- Project dependency cycle src/Access/RoleAccess.php:10
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Circular dependency src/Access/RoleAccess.php:10
- Unlisted import '@lezer/highlight' resources/js/controllers/code_controller.js:25
Serious — 73 finding(s)
- Change coupling: Role.php ↔ User.php src/Platform/Models/Role.php:1
- Change coupling: RoleEditScreen.php ↔ RoleListScreen.php stubs/app/Orchid/Screens/Role/RoleEditScreen.php:1
- Change coupling: cropper_controller.js ↔ cropper.blade.php resources/js/controllers/cropper_controller.js:1
- Change coupling: attach_controller.js ↔ attach.blade.php resources/js/controllers/attach_controller.js:1
- Change coupling: row.blade.php ↔ table.blade.php resources/views/layouts/row.blade.php:1
- Change coupling: quill_controller.js ↔ quill.blade.php resources/js/controllers/quill_controller.js:1
- Change coupling: RoleListScreen.php ↔ UserEditScreen.php stubs/app/Orchid/Screens/Role/RoleListScreen.php:1
- <fieldset> without a <legend> resources/views/layouts/block.blade.php:1
- <fieldset> without a <legend> resources/views/layouts/legend.blade.php:1
- <fieldset> without a <legend> resources/views/layouts/row.blade.php:1
- <fieldset> without a <legend> resources/views/layouts/sortable.blade.php:2
- <fieldset> without a <legend> resources/views/layouts/table.blade.php:2
- Modal dialog does not manage focus resources/views/fields/cropper.blade.php:57
- Modal dialog does not manage focus resources/views/layouts/modal.blade.php:2
- Modal dialog does not manage focus resources/views/partials/confirm.blade.php:1
- Modal dialog does not manage focus resources/views/partials/notification/modal.blade.php:1
- Modal dialog does not manage focus resources/views/partials/search/modal.blade.php:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Hotspot: src/Screen/Layouts/Chart.php src/Screen/Layouts/Chart.php:149
- Hotspot: resources/js/controllers/repeater_controller.js resources/js/controllers/repeater_controller.js:17
- TodoComment tests/App/RouteSolving.php:17
- TodoComment src/Screen/Concerns/Multipliable.php:17
- REDACTED
- REDACTED
- TooManyMethods: block_editor_controller resources/js/controllers/block_editor_controller.js:44
- TooManyMethods: Field src/Screen/Field.php:49
- Boundary violation [package:third-party-deep-import] resources/js/controllers/datetime_controller.js:2
- Boundary violation [package:third-party-deep-import] resources/js/controllers/datetime_controller.js:4
- Page without a main landmark resources/views/app.blade.php:2
- Chart.build (cyclomatic 34) src/Screen/Layouts/Chart.php:149
- KeyValue.updateFieldValue (cyclomatic 18) src/Screen/Fields/KeyValue.php:76
- #normalize (cyclomatic 18) resources/js/controllers/block_editor_controller.js:775
- repeater_controller.appendReadonlyValues (cyclomatic 17) resources/js/controllers/repeater_controller.js:17
- Repeated repair: resources/js/controllers/attach_controller.js resources/js/controllers/attach_controller.js:123
- Chart.build (cognitive 33) src/Screen/Layouts/Chart.php:149
- KeyValue.updateFieldValue (cognitive 26) src/Screen/Fields/KeyValue.php:76
- ModelStateRetrievable.__serialize (cognitive 20) src/Screen/Concerns/ModelStateRetrievable.php:30
- block_editor_controller.#embedSrc (cognitive 18) resources/js/controllers/block_editor_controller.js:1129
- #normalize (cognitive 18) resources/js/controllers/block_editor_controller.js:775
- #convertBlock (cognitive 16) resources/js/controllers/block_editor_controller.js:844
- REDACTED
- REDACTED
- FileTooLong: controllers/block_editor_controller.js resources/js/controllers/block_editor_controller.js
- REDACTED
- Edited copy of a member (15 corresponding lines) src/Screen/Fields/Attach.php:127
- Edited copy of a member (7 corresponding lines) src/Access/RoleAccess.php:48
- Edited copy of a member (10 corresponding lines) stubs/app/Orchid/Screens/User/UserListScreen.php:103
- Off the main sequence: src/Metrics
- Low cohesion: Orchid (LCOM4 8) src/Platform/Orchid.php:11
- Type Safety
- Duplicated block with local edits (57 matched lines × 2 locations) resources/js/controllers/cropper_controller.js:26
- Duplicated block with local edits (38 matched lines × 2 locations) resources/js/controllers/code_controller.js:57
- Duplicated block with local edits (17 matched lines × 2 locations) resources/js/controllers/key_value_controller.js:35
- Complex function #normalize (cyclomatic 18, cognitive 18) resources/js/controllers/block_editor_controller.js:775
- Complex function #embedSrc (cyclomatic 14, cognitive 17) resources/js/controllers/block_editor_controller.js:1129
- Complex function render (cyclomatic 13, cognitive 12) resources/js/controllers/chart_controller.js:73
- Complex function (anonymous) (cyclomatic 13, cognitive 11) resources/js/controllers/repeater_controller.js:32
- Complex function #supportedBlock (cyclomatic 13, cognitive 9) resources/js/controllers/block_editor_controller.js:739
- Complex function #convertBlock (cyclomatic 12, cognitive 16) resources/js/controllers/block_editor_controller.js:844
- resources/js/controllers/block_editor_controller.js: 1075 lines of code resources/js/controllers/block_editor_controller.js:1
- REDACTED: 500 lines of code REDACTED:1
- Test Coverage
- No typecheck script
- Unused dependency '@codemirror/lang-cpp' package.json:11
- Unused dependency '@codemirror/search' package.json:17
- Unused dependency '@popperjs/core' package.json:23
- Unused dependency 'laravel-vite-plugin' package.json:31
- Unused dependency 'rtlcss' package.json:37
- JavaScript dependencies are not locked package.json:6
- Swallowed exception (empty catch) resources/js/controllers/block_editor_controller.js:732
Minor — 14 finding(s)
- redundant comment resources/js/controllers/browsing_controller.js:13
- redundant comment resources/js/controllers/form_controller.js:237
- redundant comment resources/js/controllers/modal_controller.js:42
- redundant comment resources/js/controllers/modal_controller.js:111
- Duplicated predicate resources/js/controllers/code_controller.js:87
- Duplicated predicate resources/js/controllers/code_controller.js:114
- Duplicated predicate resources/views/fields/keyValue.blade.php:16
- Duplicated predicate resources/views/fields/checkbox.blade.php:8
- No named authorization policies
- Documentation: no build, run or usage example readme.md:1
- REDACTED
- No ADRs
- No architecture diagram/doc
- PHP static analysis does not check null everywhere
Minor — 1 finding(s)
- doc comments repeat the names resources/js/controllers/application_controller.js:8
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-60d74c82e2254402ab5e1557d8369a82/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-60d74c82e2254402ab5e1557d8369a82/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=3200" --report-format json --report-path /tmp/watchdog-gitleaks-60d74c82e2254402ab5e1557d8369a82/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=4200 --max-count=2790" --report-format json --report-path /tmp/watchdog-gitleaks-60d74c82e2254402ab5e1557d8369a82/history-3.json --exit-code 0 --source . | 75 | artifacts/raw/gitleaks-history-3.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-60d74c82e2254402ab5e1557d8369a82/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 34 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | — |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 10 file(s) — `src/Filters/AllowedFilters.php`, `src/Filters/AllowedSorts.php`, `src/Filters/HttpFilter.php`, `src/Platform/Components/Breadcrumbs.php`, `src/Platform/Http/Middleware/BladeIcons.php`, … (+5 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |