Executive summary
BookStackApp/BookStack falls short of our standard for production, in part because four passwords or keys sit in the current code. It scores 48 out of 100 and is rated Weak, and 29 of its 88 critical findings are security problems.
Production Readiness, at 43, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is replacing the four exposed passwords or keys and switching the old ones off, worth about 4 points. Fixing the package under a licence on your banned list comes next, worth about 3 points.
Twenty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four passwords or keys in the code and one in the code's history are open to anyone who can read the repository, and fourteen form fields can't be read by a screen reader. Pinning each tool to an exact version, replacing each exposed password or key and labelling the form fields 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 the three unsafe settings in infrastructure or container files need changing to safe values. The 26 labels or groups of fields with no name need connecting to their fields or naming.
The product code is 186,505 lines, about €240,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 12 findings
- Code Duplication · Duplicated block (11 lines × 2) database/factories/Entities/Models/PageRevisionFactory.php
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Change Coupling · Change coupling: PageRepo.php ↔ PageEditorData.php app/Entities/Repos/PageRepo.php
- Exception handling · Swallowed exception (empty catch) resources/js/wysiwyg/lexical/clipboard/clipboard.ts
- Exception handling · Swallowed exception (empty catch) resources/js/wysiwyg/lexical/clipboard/clipboard.ts
- Rich vs anemic model · Anemic entity: PageUpdateDraft app/Entities/Models/PageUpdateDraft.php
- Visual & motion safety · Low contrast colour pair in CSS (4.2:1) resources/sass/_buttons.scss
- Visual & motion safety · Low contrast colour pair in CSS (4.2:1) resources/sass/_editor.scss
- Visual & motion safety · Low contrast colour pair in CSS (4.2:1) resources/sass/_forms.scss
Fixed since the last survey: 210 findings
- Churn × Complexity Hotspots · Hotspot: app/Util/HtmlPurifier/SrcsetAttrDef.php app/Util/HtmlPurifier/SrcsetAttrDef.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/EmailConfirmationService.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/ExternalBaseUserProvider.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/GroupSyncService.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/LdapService.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/LdapService.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) REDACTED
- Boundary Type-Coupling · Cross-context type User (Users → Access) REDACTED
- Boundary Type-Coupling · Cross-context type User (Users → Access) REDACTED
- Boundary Type-Coupling · Cross-context type User (Users → Access) REDACTED
- Boundary Type-Coupling · Cross-context type User (Users → Access) REDACTED
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/Mfa/MfaSession.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/Mfa/MfaSession.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/Mfa/MfaSession.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/Mfa/MfaSession.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/Mfa/MfaValue.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/Mfa/MfaValue.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/Mfa/MfaVerificationLimiter.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/Mfa/MfaVerificationLimiter.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/Mfa/MfaVerificationLimiter.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/Mfa/TotpService.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/Notifications/ConfirmEmailNotification.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/Notifications/ResetPasswordNotification.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/Notifications/UserInviteNotification.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/Oidc/OidcService.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/RegistrationService.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/RegistrationService.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/Saml2Service.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/Saml2Service.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/Saml2Service.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/UserInviteService.php
- Boundary Type-Coupling · Cross-context type User (Users → Access) app/Access/UserTokenService.php
- Boundary Type-Coupling · Cross-context type Entity (Entities → Activity) app/Activity/ActivityQueries.php
- Boundary Type-Coupling · Cross-context type User (Users → Activity) app/Activity/ActivityQueries.php
- Boundary Type-Coupling · Cross-context type Entity (Entities → Activity) app/Activity/CommentRepo.php
- Boundary Type-Coupling · Cross-context type User (Users → Activity) app/Activity/Notifications/Handlers/CommentCreationNotificationHandler.php
- Boundary Type-Coupling · Cross-context type User (Users → Activity) app/Activity/Notifications/Handlers/CommentMentionNotificationHandler.php
- Boundary Type-Coupling · Cross-context type User (Users → Activity) app/Activity/Notifications/Handlers/NotificationHandler.php
- Boundary Type-Coupling · Cross-context type User (Users → Activity) app/Activity/Notifications/Handlers/PageCreationNotificationHandler.php
- Boundary Type-Coupling · Cross-context type User (Users → Activity) app/Activity/Notifications/Handlers/PageUpdateNotificationHandler.php
- Boundary Type-Coupling · Cross-context type Entity (Entities → Activity) app/Activity/Notifications/MessageParts/EntityLinkMessageLine.php
- Boundary Type-Coupling · Cross-context type User (Users → Activity) app/Activity/Notifications/Messages/BaseActivityNotification.php
- Boundary Type-Coupling · Cross-context type User (Users → Activity) app/Activity/Notifications/Messages/CommentCreationNotification.php
- Boundary Type-Coupling · Cross-context type User (Users → Activity) app/Activity/Notifications/Messages/CommentMentionNotification.php
- Boundary Type-Coupling · Cross-context type User (Users → Activity) app/Activity/Notifications/Messages/PageCreationNotification.php
- Boundary Type-Coupling · Cross-context type User (Users → Activity) app/Activity/Notifications/Messages/PageUpdateNotification.php
- Boundary Type-Coupling · Cross-context type User (Users → Activity) app/Activity/Notifications/NotificationManager.php
- Boundary Type-Coupling · Cross-context type Entity (Entities → Activity) app/Activity/TagRepo.php
- Boundary Type-Coupling · Cross-context type Entity (Entities → Activity) app/Activity/Tools/ActivityLogger.php
- Boundary Type-Coupling · Cross-context type Page (Entities → Activity) app/Activity/Tools/CommentTree.php
- Boundary Type-Coupling · Cross-context type Entity (Entities → Activity) app/Activity/Tools/EntityWatchers.php
- Boundary Type-Coupling · Cross-context type Entity (Entities → Activity) app/Activity/Tools/TagClassGenerator.php
- Boundary Type-Coupling · Cross-context type User (Users → Activity) app/Activity/Tools/UserEntityWatchOptions.php
- Boundary Type-Coupling · Cross-context type Entity (Entities → Activity) app/Activity/Tools/UserEntityWatchOptions.php
- Boundary Type-Coupling · Cross-context type User (Users → Activity) app/Activity/Tools/WebhookFormatter.php
- Boundary Type-Coupling · Cross-context type User (Users → Activity) app/Activity/Tools/WebhookFormatter.php
- Boundary Type-Coupling · Cross-context type Entity (Entities → Activity) app/Activity/WatchLevels.php
- Boundary Type-Coupling · Cross-context type User (Users → Entities) app/Entities/Tools/PageContent.php
- Boundary Type-Coupling · Cross-context type User (Users → Entities) app/Entities/Tools/PageContent.php
- Boundary Type-Coupling · Cross-context type User (Users → Entities) app/Entities/Tools/SlugGenerator.php
- Boundary Type-Coupling · Cross-context type Page (Entities → Exports) app/Exports/ExportFormatter.php
- Boundary Type-Coupling · Cross-context type Chapter (Entities → Exports) app/Exports/ExportFormatter.php
- Boundary Type-Coupling · Cross-context type Book (Entities → Exports) app/Exports/ExportFormatter.php
- Boundary Type-Coupling · Cross-context type Page (Entities → Exports) app/Exports/ExportFormatter.php
- Boundary Type-Coupling · Cross-context type Chapter (Entities → Exports) app/Exports/ExportFormatter.php
- Boundary Type-Coupling · Cross-context type Book (Entities → Exports) app/Exports/ExportFormatter.php
- Boundary Type-Coupling · Cross-context type Page (Entities → Exports) app/Exports/ExportFormatter.php
- Boundary Type-Coupling · Cross-context type Chapter (Entities → Exports) app/Exports/ExportFormatter.php
- Boundary Type-Coupling · Cross-context type Book (Entities → Exports) app/Exports/ExportFormatter.php
- Boundary Type-Coupling · Cross-context type Page (Entities → Exports) app/Exports/ExportFormatter.php
- Boundary Type-Coupling · Cross-context type Chapter (Entities → Exports) app/Exports/ExportFormatter.php
- Boundary Type-Coupling · Cross-context type Book (Entities → Exports) app/Exports/ExportFormatter.php
- Boundary Type-Coupling · Cross-context type Entity (Entities → Exports) app/Exports/ImportRepo.php
- Boundary Type-Coupling · Cross-context type Attachment (Uploads → Exports) app/Exports/ZipExports/Models/ZipExportAttachment.php
- Boundary Type-Coupling · Cross-context type Book (Entities → Exports) app/Exports/ZipExports/Models/ZipExportBook.php
- Boundary Type-Coupling · Cross-context type Chapter (Entities → Exports) app/Exports/ZipExports/Models/ZipExportChapter.php
- Boundary Type-Coupling · Cross-context type Image (Uploads → Exports) app/Exports/ZipExports/Models/ZipExportImage.php
- Boundary Type-Coupling · Cross-context type Page (Entities → Exports) app/Exports/ZipExports/Models/ZipExportPage.php
- Boundary Type-Coupling · Cross-context type Tag (Activity → Exports) app/Exports/ZipExports/Models/ZipExportTag.php
- Boundary Type-Coupling · Cross-context type Page (Entities → Exports) app/Exports/ZipExports/ZipExportBuilder.php
- Boundary Type-Coupling · Cross-context type Chapter (Entities → Exports) app/Exports/ZipExports/ZipExportBuilder.php
- Boundary Type-Coupling · Cross-context type Book (Entities → Exports) app/Exports/ZipExports/ZipExportBuilder.php
- Boundary Type-Coupling · Cross-context type Attachment (Uploads → Exports) app/Exports/ZipExports/ZipExportFiles.php
- Boundary Type-Coupling · Cross-context type Image (Uploads → Exports) app/Exports/ZipExports/ZipExportFiles.php
- Boundary Type-Coupling · Cross-context type Page (Entities → Exports) app/Exports/ZipExports/ZipImportReferences.php
- Boundary Type-Coupling · Cross-context type Chapter (Entities → Exports) app/Exports/ZipExports/ZipImportReferences.php
- Boundary Type-Coupling · Cross-context type Book (Entities → Exports) app/Exports/ZipExports/ZipImportReferences.php
- Boundary Type-Coupling · Cross-context type Attachment (Uploads → Exports) app/Exports/ZipExports/ZipImportReferences.php
- Boundary Type-Coupling · Cross-context type Image (Uploads → Exports) app/Exports/ZipExports/ZipImportReferences.php
- Boundary Type-Coupling · Cross-context type Entity (Entities → Exports) app/Exports/ZipExports/ZipImportRunner.php
- Boundary Type-Coupling · Cross-context type Entity (Entities → Permissions) app/Permissions/EntityPermissionEvaluator.php
- Boundary Type-Coupling · Cross-context type Entity (Entities → Permissions) app/Permissions/JointPermissionBuilder.php
- Boundary Type-Coupling · Cross-context type Role (Users → Permissions) app/Permissions/JointPermissionBuilder.php
- Boundary Type-Coupling · Cross-context type User (Users → Permissions) app/Permissions/PermissionApplicator.php
- Boundary Type-Coupling · Cross-context type Entity (Entities → Permissions) app/Permissions/PermissionFormData.php
- Boundary Type-Coupling · Cross-context type Role (Users → Permissions) app/Permissions/PermissionFormData.php
- Boundary Type-Coupling · Cross-context type Role (Users → Permissions) app/Permissions/PermissionsRepo.php
- Boundary Type-Coupling · Cross-context type Role (Users → Permissions) app/Permissions/PermissionsRepo.php
- Boundary Type-Coupling · Cross-context type Role (Users → Permissions) app/Permissions/PermissionsRepo.php
- Boundary Type-Coupling · Cross-context type Role (Users → Permissions) app/Permissions/PermissionsRepo.php
Rebuild cost: about €240,000 · Estimate
| Cost to rebuild | €81,000 to €410,000, for 1,352 to 4,289 hours of work, about 1.7 person-years for 1 to 4 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 48. 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 | Large: 186,505 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 BookStack.Http | 2 BookStack.Util | 3 resources.js.components.component | 4 resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode | 5 resources.js.wysiwyg.lexical.core.nodes.common | 6 resources.js.wysiwyg.ui.framework.core | 7 BookStack.Users.Models | 8 resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode | 9 resources.js.wysiwyg.ui.framework.buttons | 10 BookStack.Permissions | 11 resources.js.wysiwyg.lexical.core.LexicalSelection | 12 BookStack.Activity | 13 BookStack.References | 14 BookStack.Uploads | 15 resources.js.wysiwyg.lexical.core.LexicalNode | 16 BookStack.Entities.Repos | 17 resources.js.wysiwyg.lexical.core.LexicalEditor | 18 resources.js.wysiwyg.lexical.core.nodes | 19 resources.js.wysiwyg.ui.framework.decorator | 20 BookStack.Entities.Tools | 21 resources.js.wysiwyg.lexical.core | 22 resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode | 23 resources.js.wysiwyg.lexical.table.LexicalTableCellNode | 24 resources.js.wysiwyg.lexical.yjs | 25 BookStack.Entities.Models | 26 BookStack.Users | 27 resources.js.wysiwyg.lexical.rich-text | 28 resources.js.wysiwyg.lexical.table.LexicalTableNode | 29 BookStack.Entities.Queries | 30 resources.js.wysiwyg.lexical.table | 31 resources.js.wysiwyg.utils | 32 BookStack.App | 33 BookStack.Activity.Models | 34 BookStack.Exports.ZipExports | 35 BookStack.Search | 36 BookStack.Access | 37 BookStack.Console.Commands | 38 BookStack.Exports | 39 BookStack.Access.Controllers | 40 BookStack.Users.Controllers |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 BookStack.Http | ||||||||||||||||||||||||||||||||||||||||
| 2 BookStack.Util | ||||||||||||||||||||||||||||||||||||||||
| 3 resources.js.components.component | ||||||||||||||||||||||||||||||||||||||||
| 4 resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode | ||||||||||||||||||||||||||||||||||||||||
| 5 resources.js.wysiwyg.lexical.core.nodes.common | ||||||||||||||||||||||||||||||||||||||||
| 6 resources.js.wysiwyg.ui.framework.core | ||||||||||||||||||||||||||||||||||||||||
| 7 BookStack.Users.Models | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 8 resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 resources.js.wysiwyg.ui.framework.buttons | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 BookStack.Permissions | 2 | 4 | 2 | 6 | 2 | |||||||||||||||||||||||||||||||||||
| 11 resources.js.wysiwyg.lexical.core.LexicalSelection | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 12 BookStack.Activity | 1 | 1 | 2 | 2 | 1 | 4 | 3 | |||||||||||||||||||||||||||||||||
| 13 BookStack.References | 1 | 1 | 1 | 1 | 5 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 14 BookStack.Uploads | 1 | 3 | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 15 resources.js.wysiwyg.lexical.core.LexicalNode | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 BookStack.Entities.Repos | 2 | 4 | 2 | 9 | 11 | 6 | ||||||||||||||||||||||||||||||||||
| 17 resources.js.wysiwyg.lexical.core.LexicalEditor | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 resources.js.wysiwyg.lexical.core.nodes | 3 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 19 resources.js.wysiwyg.ui.framework.decorator | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 BookStack.Entities.Tools | 2 | 2 | 1 | 3 | 2 | 5 | 30 | 8 | ||||||||||||||||||||||||||||||||
| 21 resources.js.wysiwyg.lexical.core | 4 | 5 | 9 | 8 | 14 | |||||||||||||||||||||||||||||||||||
| 22 resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 resources.js.wysiwyg.lexical.table.LexicalTableCellNode | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 resources.js.wysiwyg.lexical.yjs | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 BookStack.Entities.Models | 1 | 8 | 6 | 5 | ||||||||||||||||||||||||||||||||||||
| 26 BookStack.Users | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 resources.js.wysiwyg.lexical.rich-text | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 28 resources.js.wysiwyg.lexical.table.LexicalTableNode | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 BookStack.Entities.Queries | 3 | 4 | 8 | |||||||||||||||||||||||||||||||||||||
| 30 resources.js.wysiwyg.lexical.table | 1 | 1 | 3 | 2 | 3 | 4 | ||||||||||||||||||||||||||||||||||
| 31 resources.js.wysiwyg.utils | 1 | 1 | 1 | 3 | 4 | 9 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||
| 32 BookStack.App | 3 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 33 BookStack.Activity.Models | 1 | 5 | ||||||||||||||||||||||||||||||||||||||
| 34 BookStack.Exports.ZipExports | 13 | 5 | 10 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||
| 35 BookStack.Search | 2 | 1 | 2 | 2 | 3 | 1 | ||||||||||||||||||||||||||||||||||
| 36 BookStack.Access | 10 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 37 BookStack.Console.Commands | 3 | 1 | 1 | 2 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 38 BookStack.Exports | 2 | 2 | 4 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 39 BookStack.Access.Controllers | 12 | 1 | 2 | 15 | ||||||||||||||||||||||||||||||||||||
| 40 BookStack.Users.Controllers | 8 | 2 | 3 | 1 | 2 | 5 | 2 |
7→32 BookStack.Users.Models uses BookStack.App part of a loop✕
- Connections
- 3 pairs of types, where a type in BookStack.Users.Models uses a type in BookStack.App.
- The types involved
BookStack.Users.Models.Role→BookStack.App.ModelBookStack.Users.Models.User→BookStack.App.ModelBookStack.Users.Models.User→BookStack.App.SluggableInterface
- Direction
- BookStack.Users.Models uses BookStack.App, so a change to BookStack.App can break BookStack.Users.Models, while a change to BookStack.Users.Models can't break BookStack.App.
- 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.
7→33 BookStack.Users.Models uses BookStack.Activity.Models part of a loop✕
- Connections
- 2 pairs of types, where a type in BookStack.Users.Models uses a type in BookStack.Activity.Models.
- The types involved
BookStack.Users.Models.Role→BookStack.Activity.Models.LoggableBookStack.Users.Models.User→BookStack.Activity.Models.Loggable
- Direction
- BookStack.Users.Models uses BookStack.Activity.Models, so a change to BookStack.Activity.Models can break BookStack.Users.Models, while a change to BookStack.Users.Models can't break BookStack.Activity.Models.
- 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.
8→4 resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode uses resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode uses a type in resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode.
- The types involved
resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode.TextNode→resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode.ElementNode
- Direction
- resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode uses resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode, so a change to resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode can break resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode, while a change to resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode can't break resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode uses a module listed above it, which is the healthy direction.
9→6 resources.js.wysiwyg.ui.framework.buttons uses resources.js.wysiwyg.ui.framework.core✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.ui.framework.buttons uses a type in resources.js.wysiwyg.ui.framework.core.
- The types involved
resources.js.wysiwyg.ui.framework.buttons.EditorButton→resources.js.wysiwyg.ui.framework.core.EditorUiElement
- Direction
- resources.js.wysiwyg.ui.framework.buttons uses resources.js.wysiwyg.ui.framework.core, so a change to resources.js.wysiwyg.ui.framework.core can break resources.js.wysiwyg.ui.framework.buttons, while a change to resources.js.wysiwyg.ui.framework.buttons can't break resources.js.wysiwyg.ui.framework.core.
- Position
- Below the diagonal: resources.js.wysiwyg.ui.framework.buttons uses a module listed above it, which is the healthy direction.
10→1 BookStack.Permissions uses BookStack.Http✕
- Connections
- 2 pairs of types, where a type in BookStack.Permissions uses a type in BookStack.Http.
- The types involved
BookStack.Permissions.ContentPermissionApiController→BookStack.Http.ApiControllerBookStack.Permissions.PermissionsController→BookStack.Http.Controller
- Direction
- BookStack.Permissions uses BookStack.Http, so a change to BookStack.Http can break BookStack.Permissions, while a change to BookStack.Permissions can't break BookStack.Http.
- Position
- Below the diagonal: BookStack.Permissions uses a module listed above it, which is the healthy direction.
10→7 BookStack.Permissions uses BookStack.Users.Models✕
- Connections
- 4 pairs of types, where a type in BookStack.Permissions uses a type in BookStack.Users.Models.
- The types involved
BookStack.Permissions.JointPermissionBuilder→BookStack.Users.Models.RoleBookStack.Permissions.PermissionApplicator→BookStack.Users.Models.UserBookStack.Permissions.PermissionFormData→BookStack.Users.Models.RoleBookStack.Permissions.PermissionsRepo→BookStack.Users.Models.Role
- Direction
- BookStack.Permissions uses BookStack.Users.Models, so a change to BookStack.Users.Models can break BookStack.Permissions, while a change to BookStack.Permissions can't break BookStack.Users.Models.
- Position
- Below the diagonal: BookStack.Permissions uses a module listed above it, which is the healthy direction.
10→20 BookStack.Permissions uses BookStack.Entities.Tools part of a loop✕
- Connections
- 2 pairs of types, where a type in BookStack.Permissions uses a type in BookStack.Entities.Tools.
- The types involved
BookStack.Permissions.ContentPermissionApiController→BookStack.Entities.Tools.PermissionsUpdaterBookStack.Permissions.PermissionsController→BookStack.Entities.Tools.PermissionsUpdater
- Direction
- BookStack.Permissions uses BookStack.Entities.Tools, so a change to BookStack.Entities.Tools can break BookStack.Permissions, while a change to BookStack.Permissions can't break BookStack.Entities.Tools.
- 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.
10→25 BookStack.Permissions uses BookStack.Entities.Models part of a loop✕
- Connections
- 6 pairs of types, where a type in BookStack.Permissions uses a type in BookStack.Entities.Models.
- The types involved
BookStack.Permissions.ContentPermissionApiController→BookStack.Entities.Models.EntityBookStack.Permissions.EntityPermissionEvaluator→BookStack.Entities.Models.EntityBookStack.Permissions.JointPermissionBuilder→BookStack.Entities.Models.EntityBookStack.Permissions.PermissionApplicator→BookStack.Entities.Models.EntityBookStack.Permissions.PermissionFormData→BookStack.Entities.Models.EntityBookStack.Permissions.SimpleEntityData→BookStack.Entities.Models.Entity
- Direction
- BookStack.Permissions uses BookStack.Entities.Models, so a change to BookStack.Entities.Models can break BookStack.Permissions, while a change to BookStack.Permissions can't break BookStack.Entities.Models.
- 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.
10→29 BookStack.Permissions uses BookStack.Entities.Queries part of a loop✕
- Connections
- 2 pairs of types, where a type in BookStack.Permissions uses a type in BookStack.Entities.Queries.
- The types involved
BookStack.Permissions.JointPermissionBuilder→BookStack.Entities.Queries.EntityQueriesBookStack.Permissions.PermissionsController→BookStack.Entities.Queries.EntityQueries
- Direction
- BookStack.Permissions uses BookStack.Entities.Queries, so a change to BookStack.Entities.Queries can break BookStack.Permissions, while a change to BookStack.Permissions can't break BookStack.Entities.Queries.
- 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.
11→8 resources.js.wysiwyg.lexical.core.LexicalSelection uses resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode✕
- Connections
- 2 pairs of types, where a type in resources.js.wysiwyg.lexical.core.LexicalSelection uses a type in resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode.
- The types involved
resources.js.wysiwyg.lexical.core.LexicalSelection.RangeSelection→resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode.TextFormatTyperesources.js.wysiwyg.lexical.core.LexicalSelection.RangeSelection→resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode.TextNode
- Direction
- resources.js.wysiwyg.lexical.core.LexicalSelection uses resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode, so a change to resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode can break resources.js.wysiwyg.lexical.core.LexicalSelection, while a change to resources.js.wysiwyg.lexical.core.LexicalSelection can't break resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.core.LexicalSelection uses a module listed above it, which is the healthy direction.
11→15 resources.js.wysiwyg.lexical.core.LexicalSelection uses resources.js.wysiwyg.lexical.core.LexicalNode part of a loop✕
- Connections
- 4 pairs of types, where a type in resources.js.wysiwyg.lexical.core.LexicalSelection uses a type in resources.js.wysiwyg.lexical.core.LexicalNode.
- The types involved
resources.js.wysiwyg.lexical.core.LexicalSelection.BaseSelection→resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNoderesources.js.wysiwyg.lexical.core.LexicalSelection.NodeSelection→resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNoderesources.js.wysiwyg.lexical.core.LexicalSelection.Point→resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNoderesources.js.wysiwyg.lexical.core.LexicalSelection.RangeSelection→resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNode
- Direction
- resources.js.wysiwyg.lexical.core.LexicalSelection uses resources.js.wysiwyg.lexical.core.LexicalNode, so a change to resources.js.wysiwyg.lexical.core.LexicalNode can break resources.js.wysiwyg.lexical.core.LexicalSelection, while a change to resources.js.wysiwyg.lexical.core.LexicalSelection can't break resources.js.wysiwyg.lexical.core.LexicalNode.
- 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.
12→1 BookStack.Activity uses BookStack.Http✕
- Connections
- 1 pair of types, where a type in BookStack.Activity uses a type in BookStack.Http.
- The types involved
BookStack.Activity.DispatchWebhookJob→BookStack.Http.HttpRequestService
- Direction
- BookStack.Activity uses BookStack.Http, so a change to BookStack.Http can break BookStack.Activity, while a change to BookStack.Activity can't break BookStack.Http.
- Position
- Below the diagonal: BookStack.Activity uses a module listed above it, which is the healthy direction.
12→2 BookStack.Activity uses BookStack.Util✕
- Connections
- 1 pair of types, where a type in BookStack.Activity uses a type in BookStack.Util.
- The types involved
BookStack.Activity.TagRepo→BookStack.Util.SimpleListOptions
- Direction
- BookStack.Activity uses BookStack.Util, so a change to BookStack.Util can break BookStack.Activity, while a change to BookStack.Activity can't break BookStack.Util.
- Position
- Below the diagonal: BookStack.Activity uses a module listed above it, which is the healthy direction.
12→7 BookStack.Activity uses BookStack.Users.Models✕
- Connections
- 2 pairs of types, where a type in BookStack.Activity uses a type in BookStack.Users.Models.
- The types involved
BookStack.Activity.ActivityQueries→BookStack.Users.Models.UserBookStack.Activity.DispatchWebhookJob→BookStack.Users.Models.User
- Direction
- BookStack.Activity uses BookStack.Users.Models, so a change to BookStack.Users.Models can break BookStack.Activity, while a change to BookStack.Activity can't break BookStack.Users.Models.
- Position
- Below the diagonal: BookStack.Activity uses a module listed above it, which is the healthy direction.
12→10 BookStack.Activity uses BookStack.Permissions✕
- Connections
- 2 pairs of types, where a type in BookStack.Activity uses a type in BookStack.Permissions.
- The types involved
BookStack.Activity.ActivityQueries→BookStack.Permissions.PermissionApplicatorBookStack.Activity.TagRepo→BookStack.Permissions.PermissionApplicator
- Direction
- BookStack.Activity uses BookStack.Permissions, so a change to BookStack.Permissions can break BookStack.Activity, while a change to BookStack.Activity can't break BookStack.Permissions.
- Position
- Below the diagonal: BookStack.Activity uses a module listed above it, which is the healthy direction.
12→20 BookStack.Activity uses BookStack.Entities.Tools part of a loop✕
- Connections
- 1 pair of types, where a type in BookStack.Activity uses a type in BookStack.Entities.Tools.
- The types involved
BookStack.Activity.ActivityQueries→BookStack.Entities.Tools.MixedEntityListLoader
- Direction
- BookStack.Activity uses BookStack.Entities.Tools, so a change to BookStack.Entities.Tools can break BookStack.Activity, while a change to BookStack.Activity can't break BookStack.Entities.Tools.
- 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.
12→25 BookStack.Activity uses BookStack.Entities.Models part of a loop✕
- Connections
- 4 pairs of types, where a type in BookStack.Activity uses a type in BookStack.Entities.Models.
- The types involved
BookStack.Activity.ActivityQueries→BookStack.Entities.Models.EntityBookStack.Activity.CommentRepo→BookStack.Entities.Models.EntityBookStack.Activity.TagRepo→BookStack.Entities.Models.EntityBookStack.Activity.WatchLevels→BookStack.Entities.Models.Entity
- Direction
- BookStack.Activity uses BookStack.Entities.Models, so a change to BookStack.Entities.Models can break BookStack.Activity, while a change to BookStack.Activity can't break BookStack.Entities.Models.
- 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.
12→33 BookStack.Activity uses BookStack.Activity.Models part of a loop✕
- Connections
- 3 pairs of types, where a type in BookStack.Activity uses a type in BookStack.Activity.Models.
- The types involved
BookStack.Activity.CommentRepo→BookStack.Activity.Models.CommentBookStack.Activity.DispatchWebhookJob→BookStack.Activity.Models.WebhookBookStack.Activity.TagRepo→BookStack.Activity.Models.Tag
- Direction
- BookStack.Activity uses BookStack.Activity.Models, so a change to BookStack.Activity.Models can break BookStack.Activity, while a change to BookStack.Activity can't break BookStack.Activity.Models.
- 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.
13→1 BookStack.References uses BookStack.Http✕
- Connections
- 1 pair of types, where a type in BookStack.References uses a type in BookStack.Http.
- The types involved
BookStack.References.ReferenceController→BookStack.Http.Controller
- Direction
- BookStack.References uses BookStack.Http, so a change to BookStack.Http can break BookStack.References, while a change to BookStack.References can't break BookStack.Http.
- Position
- Below the diagonal: BookStack.References uses a module listed above it, which is the healthy direction.
13→10 BookStack.References uses BookStack.Permissions✕
- Connections
- 1 pair of types, where a type in BookStack.References uses a type in BookStack.Permissions.
- The types involved
BookStack.References.ReferenceFetcher→BookStack.Permissions.PermissionApplicator
- Direction
- BookStack.References uses BookStack.Permissions, so a change to BookStack.Permissions can break BookStack.References, while a change to BookStack.References can't break BookStack.Permissions.
- Position
- Below the diagonal: BookStack.References uses a module listed above it, which is the healthy direction.
13→16 BookStack.References uses BookStack.Entities.Repos part of a loop✕
- Connections
- 1 pair of types, where a type in BookStack.References uses a type in BookStack.Entities.Repos.
- The types involved
BookStack.References.ReferenceUpdater→BookStack.Entities.Repos.RevisionRepo
- Direction
- BookStack.References uses BookStack.Entities.Repos, so a change to BookStack.Entities.Repos can break BookStack.References, while a change to BookStack.References can't break BookStack.Entities.Repos.
- 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.
13→20 BookStack.References uses BookStack.Entities.Tools part of a loop✕
- Connections
- 1 pair of types, where a type in BookStack.References uses a type in BookStack.Entities.Tools.
- The types involved
BookStack.References.ReferenceFetcher→BookStack.Entities.Tools.MixedEntityListLoader
- Direction
- BookStack.References uses BookStack.Entities.Tools, so a change to BookStack.Entities.Tools can break BookStack.References, while a change to BookStack.References can't break BookStack.Entities.Tools.
- 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.
13→25 BookStack.References uses BookStack.Entities.Models part of a loop✕
- Connections
- 5 pairs of types, where a type in BookStack.References uses a type in BookStack.Entities.Models.
- The types involved
BookStack.References.ReferenceChangeContext→BookStack.Entities.Models.EntityBookStack.References.ReferenceFetcher→BookStack.Entities.Models.EntityBookStack.References.ReferenceStore→BookStack.Entities.Models.EntityBookStack.References.ReferenceUpdater→BookStack.Entities.Models.EntityBookStack.References.ReferenceUpdater→BookStack.Entities.Models.Page
- Direction
- BookStack.References uses BookStack.Entities.Models, so a change to BookStack.Entities.Models can break BookStack.References, while a change to BookStack.References can't break BookStack.Entities.Models.
- 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.
13→29 BookStack.References uses BookStack.Entities.Queries part of a loop✕
- Connections
- 1 pair of types, where a type in BookStack.References uses a type in BookStack.Entities.Queries.
- The types involved
BookStack.References.ReferenceController→BookStack.Entities.Queries.EntityQueries
- Direction
- BookStack.References uses BookStack.Entities.Queries, so a change to BookStack.Entities.Queries can break BookStack.References, while a change to BookStack.References can't break BookStack.Entities.Queries.
- 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.
13→32 BookStack.References uses BookStack.App part of a loop✕
- Connections
- 2 pairs of types, where a type in BookStack.References uses a type in BookStack.App.
- The types involved
BookStack.References.CrossLinkParser→BookStack.App.ModelBookStack.References.Reference→BookStack.App.Model
- Direction
- BookStack.References uses BookStack.App, so a change to BookStack.App can break BookStack.References, while a change to BookStack.References can't break BookStack.App.
- 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.
14→1 BookStack.Uploads uses BookStack.Http✕
- Connections
- 1 pair of types, where a type in BookStack.Uploads uses a type in BookStack.Http.
- The types involved
BookStack.Uploads.UserAvatars→BookStack.Http.HttpRequestService
- Direction
- BookStack.Uploads uses BookStack.Http, so a change to BookStack.Http can break BookStack.Uploads, while a change to BookStack.Uploads can't break BookStack.Http.
- Position
- Below the diagonal: BookStack.Uploads uses a module listed above it, which is the healthy direction.
14→7 BookStack.Uploads uses BookStack.Users.Models✕
- Connections
- 3 pairs of types, where a type in BookStack.Uploads uses a type in BookStack.Users.Models.
- The types involved
BookStack.Uploads.Attachment→BookStack.Users.Models.OwnableInterfaceBookStack.Uploads.Image→BookStack.Users.Models.OwnableInterfaceBookStack.Uploads.UserAvatars→BookStack.Users.Models.User
- Direction
- BookStack.Uploads uses BookStack.Users.Models, so a change to BookStack.Users.Models can break BookStack.Uploads, while a change to BookStack.Uploads can't break BookStack.Users.Models.
- Position
- Below the diagonal: BookStack.Uploads uses a module listed above it, which is the healthy direction.
14→10 BookStack.Uploads uses BookStack.Permissions✕
- Connections
- 1 pair of types, where a type in BookStack.Uploads uses a type in BookStack.Permissions.
- The types involved
BookStack.Uploads.ImageRepo→BookStack.Permissions.PermissionApplicator
- Direction
- BookStack.Uploads uses BookStack.Permissions, so a change to BookStack.Permissions can break BookStack.Uploads, while a change to BookStack.Uploads can't break BookStack.Permissions.
- Position
- Below the diagonal: BookStack.Uploads uses a module listed above it, which is the healthy direction.
14→25 BookStack.Uploads uses BookStack.Entities.Models part of a loop✕
- Connections
- 1 pair of types, where a type in BookStack.Uploads uses a type in BookStack.Entities.Models.
- The types involved
BookStack.Uploads.Image→BookStack.Entities.Models.Page
- Direction
- BookStack.Uploads uses BookStack.Entities.Models, so a change to BookStack.Entities.Models can break BookStack.Uploads, while a change to BookStack.Uploads can't break BookStack.Entities.Models.
- 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.
14→29 BookStack.Uploads uses BookStack.Entities.Queries part of a loop✕
- Connections
- 2 pairs of types, where a type in BookStack.Uploads uses a type in BookStack.Entities.Queries.
- The types involved
BookStack.Uploads.ImageRepo→BookStack.Entities.Queries.PageQueriesBookStack.Uploads.ImageService→BookStack.Entities.Queries.EntityQueries
- Direction
- BookStack.Uploads uses BookStack.Entities.Queries, so a change to BookStack.Entities.Queries can break BookStack.Uploads, while a change to BookStack.Uploads can't break BookStack.Entities.Queries.
- 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.
14→32 BookStack.Uploads uses BookStack.App part of a loop✕
- Connections
- 2 pairs of types, where a type in BookStack.Uploads uses a type in BookStack.App.
- The types involved
BookStack.Uploads.Attachment→BookStack.App.ModelBookStack.Uploads.Image→BookStack.App.Model
- Direction
- BookStack.Uploads uses BookStack.App, so a change to BookStack.App can break BookStack.Uploads, while a change to BookStack.Uploads can't break BookStack.App.
- 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.
15→4 resources.js.wysiwyg.lexical.core.LexicalNode uses resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.lexical.core.LexicalNode uses a type in resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode.
- The types involved
resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNode→resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode.ElementNode
- Direction
- resources.js.wysiwyg.lexical.core.LexicalNode uses resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode, so a change to resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode can break resources.js.wysiwyg.lexical.core.LexicalNode, while a change to resources.js.wysiwyg.lexical.core.LexicalNode can't break resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.core.LexicalNode uses a module listed above it, which is the healthy direction.
15→11 resources.js.wysiwyg.lexical.core.LexicalNode uses resources.js.wysiwyg.lexical.core.LexicalSelection✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.lexical.core.LexicalNode uses a type in resources.js.wysiwyg.lexical.core.LexicalSelection.
- The types involved
resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNode→resources.js.wysiwyg.lexical.core.LexicalSelection.RangeSelection
- Direction
- resources.js.wysiwyg.lexical.core.LexicalNode uses resources.js.wysiwyg.lexical.core.LexicalSelection, so a change to resources.js.wysiwyg.lexical.core.LexicalSelection can break resources.js.wysiwyg.lexical.core.LexicalNode, while a change to resources.js.wysiwyg.lexical.core.LexicalNode can't break resources.js.wysiwyg.lexical.core.LexicalSelection.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.core.LexicalNode uses a module listed above it, which is the healthy direction.
15→17 resources.js.wysiwyg.lexical.core.LexicalNode uses resources.js.wysiwyg.lexical.core.LexicalEditor part of a loop✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.lexical.core.LexicalNode uses a type in resources.js.wysiwyg.lexical.core.LexicalEditor.
- The types involved
resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNode→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditor
- Direction
- resources.js.wysiwyg.lexical.core.LexicalNode uses resources.js.wysiwyg.lexical.core.LexicalEditor, so a change to resources.js.wysiwyg.lexical.core.LexicalEditor can break resources.js.wysiwyg.lexical.core.LexicalNode, while a change to resources.js.wysiwyg.lexical.core.LexicalNode can't break resources.js.wysiwyg.lexical.core.LexicalEditor.
- 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.
16→12 BookStack.Entities.Repos uses BookStack.Activity✕
- Connections
- 2 pairs of types, where a type in BookStack.Entities.Repos uses a type in BookStack.Activity.
- The types involved
BookStack.Entities.Repos.BaseRepo→BookStack.Activity.TagRepoBookStack.Entities.Repos.BookRepo→BookStack.Activity.TagRepo
- Direction
- BookStack.Entities.Repos uses BookStack.Activity, so a change to BookStack.Activity can break BookStack.Entities.Repos, while a change to BookStack.Entities.Repos can't break BookStack.Activity.
- Position
- Below the diagonal: BookStack.Entities.Repos uses a module listed above it, which is the healthy direction.
16→13 BookStack.Entities.Repos uses BookStack.References✕
- Connections
- 4 pairs of types, where a type in BookStack.Entities.Repos uses a type in BookStack.References.
- The types involved
BookStack.Entities.Repos.BaseRepo→BookStack.References.ReferenceStoreBookStack.Entities.Repos.BaseRepo→BookStack.References.ReferenceUpdaterBookStack.Entities.Repos.PageRepo→BookStack.References.ReferenceStoreBookStack.Entities.Repos.PageRepo→BookStack.References.ReferenceUpdater
- Direction
- BookStack.Entities.Repos uses BookStack.References, so a change to BookStack.References can break BookStack.Entities.Repos, while a change to BookStack.Entities.Repos can't break BookStack.References.
- Position
- Below the diagonal: BookStack.Entities.Repos uses a module listed above it, which is the healthy direction.
16→14 BookStack.Entities.Repos uses BookStack.Uploads✕
- Connections
- 2 pairs of types, where a type in BookStack.Entities.Repos uses a type in BookStack.Uploads.
- The types involved
BookStack.Entities.Repos.BaseRepo→BookStack.Uploads.ImageRepoBookStack.Entities.Repos.BookRepo→BookStack.Uploads.ImageRepo
- Direction
- BookStack.Entities.Repos uses BookStack.Uploads, so a change to BookStack.Uploads can break BookStack.Entities.Repos, while a change to BookStack.Entities.Repos can't break BookStack.Uploads.
- Position
- Below the diagonal: BookStack.Entities.Repos uses a module listed above it, which is the healthy direction.
16→20 BookStack.Entities.Repos uses BookStack.Entities.Tools part of a loop✕
- Connections
- 9 pairs of types, where a type in BookStack.Entities.Repos uses a type in BookStack.Entities.Tools.
- The types involved
BookStack.Entities.Repos.BaseRepo→BookStack.Entities.Tools.SlugGeneratorBookStack.Entities.Repos.BaseRepo→BookStack.Entities.Tools.SlugHistoryBookStack.Entities.Repos.BookRepo→BookStack.Entities.Tools.TrashCanBookStack.Entities.Repos.BookshelfRepo→BookStack.Entities.Tools.TrashCanBookStack.Entities.Repos.ChapterRepo→BookStack.Entities.Tools.ParentChangerBookStack.Entities.Repos.ChapterRepo→BookStack.Entities.Tools.TrashCanBookStack.Entities.Repos.DeletionRepo→BookStack.Entities.Tools.TrashCanBookStack.Entities.Repos.PageRepo→BookStack.Entities.Tools.ParentChangerBookStack.Entities.Repos.PageRepo→BookStack.Entities.Tools.TrashCan
- Direction
- BookStack.Entities.Repos uses BookStack.Entities.Tools, so a change to BookStack.Entities.Tools can break BookStack.Entities.Repos, while a change to BookStack.Entities.Repos can't break BookStack.Entities.Tools.
- 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.
16→25 BookStack.Entities.Repos uses BookStack.Entities.Models part of a loop✕
- Connections
- 11 pairs of types, where a type in BookStack.Entities.Repos uses a type in BookStack.Entities.Models.
- The types involved
BookStack.Entities.Repos.BaseRepo→BookStack.Entities.Models.EntityBookStack.Entities.Repos.BookRepo→BookStack.Entities.Models.BookBookStack.Entities.Repos.BookshelfRepo→BookStack.Entities.Models.BookshelfBookStack.Entities.Repos.ChapterRepo→BookStack.Entities.Models.BookBookStack.Entities.Repos.ChapterRepo→BookStack.Entities.Models.ChapterBookStack.Entities.Repos.PageRepo→BookStack.Entities.Models.EntityBookStack.Entities.Repos.PageRepo→BookStack.Entities.Models.PageBookStack.Entities.Repos.PageUpdateDraftRepo→BookStack.Entities.Models.PageBookStack.Entities.Repos.PageUpdateDraftRepo→BookStack.Entities.Models.PageUpdateDraftBookStack.Entities.Repos.RevisionRepo→BookStack.Entities.Models.PageBookStack.Entities.Repos.RevisionRepo→BookStack.Entities.Models.PageRevision
- Direction
- BookStack.Entities.Repos uses BookStack.Entities.Models, so a change to BookStack.Entities.Models can break BookStack.Entities.Repos, while a change to BookStack.Entities.Repos can't break BookStack.Entities.Models.
- 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.
16→29 BookStack.Entities.Repos uses BookStack.Entities.Queries part of a loop✕
- Connections
- 6 pairs of types, where a type in BookStack.Entities.Repos uses a type in BookStack.Entities.Queries.
- The types involved
BookStack.Entities.Repos.BaseRepo→BookStack.Entities.Queries.PageQueriesBookStack.Entities.Repos.BookshelfRepo→BookStack.Entities.Queries.BookQueriesBookStack.Entities.Repos.ChapterRepo→BookStack.Entities.Queries.EntityQueriesBookStack.Entities.Repos.PageRepo→BookStack.Entities.Queries.EntityQueriesBookStack.Entities.Repos.PageUpdateDraftRepo→BookStack.Entities.Queries.PageUpdateDraftQueriesBookStack.Entities.Repos.RevisionRepo→BookStack.Entities.Queries.PageRevisionQueries
- Direction
- BookStack.Entities.Repos uses BookStack.Entities.Queries, so a change to BookStack.Entities.Queries can break BookStack.Entities.Repos, while a change to BookStack.Entities.Repos can't break BookStack.Entities.Queries.
- 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.
17→15 resources.js.wysiwyg.lexical.core.LexicalEditor uses resources.js.wysiwyg.lexical.core.LexicalNode✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.lexical.core.LexicalEditor uses a type in resources.js.wysiwyg.lexical.core.LexicalNode.
- The types involved
resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditor→resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNode
- Direction
- resources.js.wysiwyg.lexical.core.LexicalEditor uses resources.js.wysiwyg.lexical.core.LexicalNode, so a change to resources.js.wysiwyg.lexical.core.LexicalNode can break resources.js.wysiwyg.lexical.core.LexicalEditor, while a change to resources.js.wysiwyg.lexical.core.LexicalEditor can't break resources.js.wysiwyg.lexical.core.LexicalNode.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.core.LexicalEditor uses a module listed above it, which is the healthy direction.
18→5 resources.js.wysiwyg.lexical.core.nodes uses resources.js.wysiwyg.lexical.core.nodes.common✕
- Connections
- 3 pairs of types, where a type in resources.js.wysiwyg.lexical.core.nodes uses a type in resources.js.wysiwyg.lexical.core.nodes.common.
- The types involved
resources.js.wysiwyg.lexical.core.nodes.common→resources.js.wysiwyg.lexical.core.nodes.common.CommonBlockAlignmentresources.js.wysiwyg.lexical.core.nodes.common→resources.js.wysiwyg.lexical.core.nodes.common.CommonBlockInterfaceresources.js.wysiwyg.lexical.core.nodes.common→resources.js.wysiwyg.lexical.core.nodes.common.EditorNodeDirection
- Direction
- resources.js.wysiwyg.lexical.core.nodes uses resources.js.wysiwyg.lexical.core.nodes.common, so a change to resources.js.wysiwyg.lexical.core.nodes.common can break resources.js.wysiwyg.lexical.core.nodes, while a change to resources.js.wysiwyg.lexical.core.nodes can't break resources.js.wysiwyg.lexical.core.nodes.common.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.core.nodes uses a module listed above it, which is the healthy direction.
18→8 resources.js.wysiwyg.lexical.core.nodes uses resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode✕
- Connections
- 2 pairs of types, where a type in resources.js.wysiwyg.lexical.core.nodes uses a type in resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode.
- The types involved
resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode→resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode.TextFormatTyperesources.js.wysiwyg.lexical.core.nodes.LexicalTextNode→resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode.TextNode
- Direction
- resources.js.wysiwyg.lexical.core.nodes uses resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode, so a change to resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode can break resources.js.wysiwyg.lexical.core.nodes, while a change to resources.js.wysiwyg.lexical.core.nodes can't break resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.core.nodes uses a module listed above it, which is the healthy direction.
18→11 resources.js.wysiwyg.lexical.core.nodes uses resources.js.wysiwyg.lexical.core.LexicalSelection✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.lexical.core.nodes uses a type in resources.js.wysiwyg.lexical.core.LexicalSelection.
- The types involved
resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode→resources.js.wysiwyg.lexical.core.LexicalSelection.PointType
- Direction
- resources.js.wysiwyg.lexical.core.nodes uses resources.js.wysiwyg.lexical.core.LexicalSelection, so a change to resources.js.wysiwyg.lexical.core.LexicalSelection can break resources.js.wysiwyg.lexical.core.nodes, while a change to resources.js.wysiwyg.lexical.core.nodes can't break resources.js.wysiwyg.lexical.core.LexicalSelection.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.core.nodes uses a module listed above it, which is the healthy direction.
18→15 resources.js.wysiwyg.lexical.core.nodes uses resources.js.wysiwyg.lexical.core.LexicalNode✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.lexical.core.nodes uses a type in resources.js.wysiwyg.lexical.core.LexicalNode.
- The types involved
resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode→resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNode
- Direction
- resources.js.wysiwyg.lexical.core.nodes uses resources.js.wysiwyg.lexical.core.LexicalNode, so a change to resources.js.wysiwyg.lexical.core.LexicalNode can break resources.js.wysiwyg.lexical.core.nodes, while a change to resources.js.wysiwyg.lexical.core.nodes can't break resources.js.wysiwyg.lexical.core.LexicalNode.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.core.nodes uses a module listed above it, which is the healthy direction.
19→15 resources.js.wysiwyg.ui.framework.decorator uses resources.js.wysiwyg.lexical.core.LexicalNode✕
- Connections
- 2 pairs of types, where a type in resources.js.wysiwyg.ui.framework.decorator uses a type in resources.js.wysiwyg.lexical.core.LexicalNode.
- The types involved
resources.js.wysiwyg.ui.framework.decorator.EditorDecorator→resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNoderesources.js.wysiwyg.ui.framework.decorator.EditorDecoratorAdapter→resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNode
- Direction
- resources.js.wysiwyg.ui.framework.decorator uses resources.js.wysiwyg.lexical.core.LexicalNode, so a change to resources.js.wysiwyg.lexical.core.LexicalNode can break resources.js.wysiwyg.ui.framework.decorator, while a change to resources.js.wysiwyg.ui.framework.decorator can't break resources.js.wysiwyg.lexical.core.LexicalNode.
- Position
- Below the diagonal: resources.js.wysiwyg.ui.framework.decorator uses a module listed above it, which is the healthy direction.
20→2 BookStack.Entities.Tools uses BookStack.Util✕
- Connections
- 2 pairs of types, where a type in BookStack.Entities.Tools uses a type in BookStack.Util.
- The types involved
BookStack.Entities.Tools.PageContent→BookStack.Util.HtmlDocumentBookStack.Entities.Tools.PageIncludeParser→BookStack.Util.HtmlDocument
- Direction
- BookStack.Entities.Tools uses BookStack.Util, so a change to BookStack.Util can break BookStack.Entities.Tools, while a change to BookStack.Entities.Tools can't break BookStack.Util.
- Position
- Below the diagonal: BookStack.Entities.Tools uses a module listed above it, which is the healthy direction.
20→7 BookStack.Entities.Tools uses BookStack.Users.Models✕
- Connections
- 2 pairs of types, where a type in BookStack.Entities.Tools uses a type in BookStack.Users.Models.
- The types involved
BookStack.Entities.Tools.PageContent→BookStack.Users.Models.UserBookStack.Entities.Tools.SlugGenerator→BookStack.Users.Models.User
- Direction
- BookStack.Entities.Tools uses BookStack.Users.Models, so a change to BookStack.Users.Models can break BookStack.Entities.Tools, while a change to BookStack.Entities.Tools can't break BookStack.Users.Models.
- Position
- Below the diagonal: BookStack.Entities.Tools uses a module listed above it, which is the healthy direction.
20→10 BookStack.Entities.Tools uses BookStack.Permissions✕
- Connections
- 1 pair of types, where a type in BookStack.Entities.Tools uses a type in BookStack.Permissions.
- The types involved
BookStack.Entities.Tools.SlugHistory→BookStack.Permissions.PermissionApplicator
- Direction
- BookStack.Entities.Tools uses BookStack.Permissions, so a change to BookStack.Permissions can break BookStack.Entities.Tools, while a change to BookStack.Entities.Tools can't break BookStack.Permissions.
- Position
- Below the diagonal: BookStack.Entities.Tools uses a module listed above it, which is the healthy direction.
20→13 BookStack.Entities.Tools uses BookStack.References✕
- Connections
- 3 pairs of types, where a type in BookStack.Entities.Tools uses a type in BookStack.References.
- The types involved
BookStack.Entities.Tools.Cloner→BookStack.References.ReferenceChangeContextBookStack.Entities.Tools.Cloner→BookStack.References.ReferenceUpdaterBookStack.Entities.Tools.ParentChanger→BookStack.References.ReferenceUpdater
- Direction
- BookStack.Entities.Tools uses BookStack.References, so a change to BookStack.References can break BookStack.Entities.Tools, while a change to BookStack.Entities.Tools can't break BookStack.References.
- Position
- Below the diagonal: BookStack.Entities.Tools uses a module listed above it, which is the healthy direction.
20→14 BookStack.Entities.Tools uses BookStack.Uploads✕
- Connections
- 2 pairs of types, where a type in BookStack.Entities.Tools uses a type in BookStack.Uploads.
- The types involved
BookStack.Entities.Tools.Cloner→BookStack.Uploads.ImageBookStack.Entities.Tools.Cloner→BookStack.Uploads.ImageService
- Direction
- BookStack.Entities.Tools uses BookStack.Uploads, so a change to BookStack.Uploads can break BookStack.Entities.Tools, while a change to BookStack.Entities.Tools can't break BookStack.Uploads.
- Position
- Below the diagonal: BookStack.Entities.Tools uses a module listed above it, which is the healthy direction.
20→16 BookStack.Entities.Tools uses BookStack.Entities.Repos✕
- Connections
- 5 pairs of types, where a type in BookStack.Entities.Tools uses a type in BookStack.Entities.Repos.
- The types involved
BookStack.Entities.Tools.Cloner→BookStack.Entities.Repos.BookRepoBookStack.Entities.Tools.Cloner→BookStack.Entities.Repos.ChapterRepoBookStack.Entities.Tools.Cloner→BookStack.Entities.Repos.PageRepoBookStack.Entities.Tools.HierarchyTransformer→BookStack.Entities.Repos.BookRepoBookStack.Entities.Tools.HierarchyTransformer→BookStack.Entities.Repos.BookshelfRepo
- Direction
- BookStack.Entities.Tools uses BookStack.Entities.Repos, so a change to BookStack.Entities.Repos can break BookStack.Entities.Tools, while a change to BookStack.Entities.Tools can't break BookStack.Entities.Repos.
- Position
- Below the diagonal: BookStack.Entities.Tools uses a module listed above it, which is the healthy direction.
20→25 BookStack.Entities.Tools uses BookStack.Entities.Models part of a loop✕
- Connections
- 30 pairs of types, where a type in BookStack.Entities.Tools uses a type in BookStack.Entities.Models. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
BookStack.Entities.Tools.BookContents→BookStack.Entities.Models.BookBookStack.Entities.Tools.Cloner→BookStack.Entities.Models.BookBookStack.Entities.Tools.Cloner→BookStack.Entities.Models.ChapterBookStack.Entities.Tools.Cloner→BookStack.Entities.Models.EntityBookStack.Entities.Tools.Cloner→BookStack.Entities.Models.PageBookStack.Entities.Tools.HierarchyTransformer→BookStack.Entities.Models.BookBookStack.Entities.Tools.HierarchyTransformer→BookStack.Entities.Models.BookshelfBookStack.Entities.Tools.HierarchyTransformer→BookStack.Entities.Models.ChapterBookStack.Entities.Tools.MixedEntityRequestHelper→BookStack.Entities.Models.EntityBookStack.Entities.Tools.NextPreviousContentLocator→BookStack.Entities.Models.BookChildBookStack.Entities.Tools.NextPreviousContentLocator→BookStack.Entities.Models.EntityBookStack.Entities.Tools.PageContent→BookStack.Entities.Models.PageBookStack.Entities.Tools.PageEditActivity→BookStack.Entities.Models.PageBookStack.Entities.Tools.PageEditActivity→BookStack.Entities.Models.PageUpdateDraftBookStack.Entities.Tools.PageEditorData→BookStack.Entities.Models.PageBookStack.Entities.Tools.PageEditorType→BookStack.Entities.Models.PageBookStack.Entities.Tools.ParentChanger→BookStack.Entities.Models.BookChildBookStack.Entities.Tools.PermissionsUpdater→BookStack.Entities.Models.BookshelfBookStack.Entities.Tools.PermissionsUpdater→BookStack.Entities.Models.EntityBookStack.Entities.Tools.ShelfContext→BookStack.Entities.Models.BookBookStack.Entities.Tools.ShelfContext→BookStack.Entities.Models.BookshelfBookStack.Entities.Tools.SlugGenerator→BookStack.Entities.Models.EntityBookStack.Entities.Tools.SlugHistory→BookStack.Entities.Models.BookBookStack.Entities.Tools.SlugHistory→BookStack.Entities.Models.EntityBookStack.Entities.Tools.TrashCan→BookStack.Entities.Models.Book
- Direction
- BookStack.Entities.Tools uses BookStack.Entities.Models, so a change to BookStack.Entities.Models can break BookStack.Entities.Tools, while a change to BookStack.Entities.Tools can't break BookStack.Entities.Models.
- 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.
20→29 BookStack.Entities.Tools uses BookStack.Entities.Queries part of a loop✕
- Connections
- 8 pairs of types, where a type in BookStack.Entities.Tools uses a type in BookStack.Entities.Queries.
- The types involved
BookStack.Entities.Tools.BookContents→BookStack.Entities.Queries.EntityQueriesBookStack.Entities.Tools.EntityHydrator→BookStack.Entities.Queries.EntityQueriesBookStack.Entities.Tools.MixedEntityListLoader→BookStack.Entities.Queries.EntityQueriesBookStack.Entities.Tools.PageContent→BookStack.Entities.Queries.PageQueriesBookStack.Entities.Tools.PageEditorData→BookStack.Entities.Queries.EntityQueriesBookStack.Entities.Tools.ShelfContext→BookStack.Entities.Queries.BookshelfQueriesBookStack.Entities.Tools.SiblingFetcher→BookStack.Entities.Queries.EntityQueriesBookStack.Entities.Tools.TrashCan→BookStack.Entities.Queries.EntityQueries
- Direction
- BookStack.Entities.Tools uses BookStack.Entities.Queries, so a change to BookStack.Entities.Queries can break BookStack.Entities.Tools, while a change to BookStack.Entities.Tools can't break BookStack.Entities.Queries.
- 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.
21→4 resources.js.wysiwyg.lexical.core uses resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode✕
- Connections
- 4 pairs of types, where a type in resources.js.wysiwyg.lexical.core uses a type in resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode.
- The types involved
resources.js.wysiwyg.lexical.core.LexicalGC→resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode.ElementNoderesources.js.wysiwyg.lexical.core.LexicalReconciler→resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode.ElementNoderesources.js.wysiwyg.lexical.core.LexicalSelection→resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode.ElementNoderesources.js.wysiwyg.lexical.core.LexicalUtils→resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode.ElementNode
- Direction
- resources.js.wysiwyg.lexical.core uses resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode, so a change to resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode can break resources.js.wysiwyg.lexical.core, while a change to resources.js.wysiwyg.lexical.core can't break resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.core uses a module listed above it, which is the healthy direction.
21→8 resources.js.wysiwyg.lexical.core uses resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode✕
- Connections
- 5 pairs of types, where a type in resources.js.wysiwyg.lexical.core uses a type in resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode.
- The types involved
resources.js.wysiwyg.lexical.core.LexicalMutations→resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode.TextNoderesources.js.wysiwyg.lexical.core.LexicalNormalization→resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode.TextNoderesources.js.wysiwyg.lexical.core.LexicalSelection→resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode.TextNoderesources.js.wysiwyg.lexical.core.LexicalUtils→resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode.TextFormatTyperesources.js.wysiwyg.lexical.core.LexicalUtils→resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode.TextNode
- Direction
- resources.js.wysiwyg.lexical.core uses resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode, so a change to resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode can break resources.js.wysiwyg.lexical.core, while a change to resources.js.wysiwyg.lexical.core can't break resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.core uses a module listed above it, which is the healthy direction.
21→11 resources.js.wysiwyg.lexical.core uses resources.js.wysiwyg.lexical.core.LexicalSelection✕
- Connections
- 9 pairs of types, where a type in resources.js.wysiwyg.lexical.core uses a type in resources.js.wysiwyg.lexical.core.LexicalSelection.
- The types involved
resources.js.wysiwyg.lexical.core.LexicalEvents→resources.js.wysiwyg.lexical.core.LexicalSelection.RangeSelectionresources.js.wysiwyg.lexical.core.LexicalNormalization→resources.js.wysiwyg.lexical.core.LexicalSelection.PointTyperesources.js.wysiwyg.lexical.core.LexicalNormalization→resources.js.wysiwyg.lexical.core.LexicalSelection.RangeSelectionresources.js.wysiwyg.lexical.core.LexicalSelection→resources.js.wysiwyg.lexical.core.LexicalSelection.BaseSelectionresources.js.wysiwyg.lexical.core.LexicalSelection→resources.js.wysiwyg.lexical.core.LexicalSelection.NodeSelectionresources.js.wysiwyg.lexical.core.LexicalSelection→resources.js.wysiwyg.lexical.core.LexicalSelection.PointTyperesources.js.wysiwyg.lexical.core.LexicalSelection→resources.js.wysiwyg.lexical.core.LexicalSelection.RangeSelectionresources.js.wysiwyg.lexical.core.LexicalUtils→resources.js.wysiwyg.lexical.core.LexicalSelection.PointTyperesources.js.wysiwyg.lexical.core.LexicalUtils→resources.js.wysiwyg.lexical.core.LexicalSelection.RangeSelection
- Direction
- resources.js.wysiwyg.lexical.core uses resources.js.wysiwyg.lexical.core.LexicalSelection, so a change to resources.js.wysiwyg.lexical.core.LexicalSelection can break resources.js.wysiwyg.lexical.core, while a change to resources.js.wysiwyg.lexical.core can't break resources.js.wysiwyg.lexical.core.LexicalSelection.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.core uses a module listed above it, which is the healthy direction.
21→15 resources.js.wysiwyg.lexical.core uses resources.js.wysiwyg.lexical.core.LexicalNode✕
- Connections
- 8 pairs of types, where a type in resources.js.wysiwyg.lexical.core uses a type in resources.js.wysiwyg.lexical.core.LexicalNode.
- The types involved
resources.js.wysiwyg.lexical.core.LexicalEditorState→resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNoderesources.js.wysiwyg.lexical.core.LexicalGC→resources.js.wysiwyg.lexical.core.LexicalNode.NodeMapresources.js.wysiwyg.lexical.core.LexicalNode→resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNoderesources.js.wysiwyg.lexical.core.LexicalReconciler→resources.js.wysiwyg.lexical.core.LexicalNode.NodeMapresources.js.wysiwyg.lexical.core.LexicalSelection→resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNoderesources.js.wysiwyg.lexical.core.LexicalUpdates→resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNoderesources.js.wysiwyg.lexical.core.LexicalUtils→resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNoderesources.js.wysiwyg.lexical.core.LexicalUtils→resources.js.wysiwyg.lexical.core.LexicalNode.NodeMap
- Direction
- resources.js.wysiwyg.lexical.core uses resources.js.wysiwyg.lexical.core.LexicalNode, so a change to resources.js.wysiwyg.lexical.core.LexicalNode can break resources.js.wysiwyg.lexical.core, while a change to resources.js.wysiwyg.lexical.core can't break resources.js.wysiwyg.lexical.core.LexicalNode.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.core uses a module listed above it, which is the healthy direction.
21→17 resources.js.wysiwyg.lexical.core uses resources.js.wysiwyg.lexical.core.LexicalEditor✕
- Connections
- 14 pairs of types, where a type in resources.js.wysiwyg.lexical.core uses a type in resources.js.wysiwyg.lexical.core.LexicalEditor.
- The types involved
resources.js.wysiwyg.lexical.core.LexicalEditor→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditorresources.js.wysiwyg.lexical.core.LexicalEditorState→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditorresources.js.wysiwyg.lexical.core.LexicalEvents→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditorresources.js.wysiwyg.lexical.core.LexicalGC→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditorresources.js.wysiwyg.lexical.core.LexicalMutations→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditorresources.js.wysiwyg.lexical.core.LexicalReconciler→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditorresources.js.wysiwyg.lexical.core.LexicalReconciler→resources.js.wysiwyg.lexical.core.LexicalEditor.MutatedNodesresources.js.wysiwyg.lexical.core.LexicalSelection→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditorresources.js.wysiwyg.lexical.core.LexicalUpdates→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditorresources.js.wysiwyg.lexical.core.LexicalUpdates→resources.js.wysiwyg.lexical.core.LexicalEditor.MutatedNodesresources.js.wysiwyg.lexical.core.LexicalUtils→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditorresources.js.wysiwyg.lexical.core.LexicalUtils→resources.js.wysiwyg.lexical.core.LexicalEditor.MutatedNodesresources.js.wysiwyg.lexical.core.LexicalUtils→resources.js.wysiwyg.lexical.core.LexicalEditor.MutationListenersresources.js.wysiwyg.lexical.core.LexicalUtils→resources.js.wysiwyg.lexical.core.LexicalEditor.NodeMutation
- Direction
- resources.js.wysiwyg.lexical.core uses resources.js.wysiwyg.lexical.core.LexicalEditor, so a change to resources.js.wysiwyg.lexical.core.LexicalEditor can break resources.js.wysiwyg.lexical.core, while a change to resources.js.wysiwyg.lexical.core can't break resources.js.wysiwyg.lexical.core.LexicalEditor.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.core uses a module listed above it, which is the healthy direction.
22→11 resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode uses resources.js.wysiwyg.lexical.core.LexicalSelection✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode uses a type in resources.js.wysiwyg.lexical.core.LexicalSelection.
- The types involved
resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode.HeadingNode→resources.js.wysiwyg.lexical.core.LexicalSelection.RangeSelection
- Direction
- resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode uses resources.js.wysiwyg.lexical.core.LexicalSelection, so a change to resources.js.wysiwyg.lexical.core.LexicalSelection can break resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode, while a change to resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode can't break resources.js.wysiwyg.lexical.core.LexicalSelection.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode uses a module listed above it, which is the healthy direction.
22→17 resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode uses resources.js.wysiwyg.lexical.core.LexicalEditor✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode uses a type in resources.js.wysiwyg.lexical.core.LexicalEditor.
- The types involved
resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode.HeadingNode→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditor
- Direction
- resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode uses resources.js.wysiwyg.lexical.core.LexicalEditor, so a change to resources.js.wysiwyg.lexical.core.LexicalEditor can break resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode, while a change to resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode can't break resources.js.wysiwyg.lexical.core.LexicalEditor.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode uses a module listed above it, which is the healthy direction.
23→4 resources.js.wysiwyg.lexical.table.LexicalTableCellNode uses resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.lexical.table.LexicalTableCellNode uses a type in resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode.
- The types involved
resources.js.wysiwyg.lexical.table.LexicalTableCellNode.TableCellNode→resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode.ElementNode
- Direction
- resources.js.wysiwyg.lexical.table.LexicalTableCellNode uses resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode, so a change to resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode can break resources.js.wysiwyg.lexical.table.LexicalTableCellNode, while a change to resources.js.wysiwyg.lexical.table.LexicalTableCellNode can't break resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.table.LexicalTableCellNode uses a module listed above it, which is the healthy direction.
23→5 resources.js.wysiwyg.lexical.table.LexicalTableCellNode uses resources.js.wysiwyg.lexical.core.nodes.common✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.lexical.table.LexicalTableCellNode uses a type in resources.js.wysiwyg.lexical.core.nodes.common.
- The types involved
resources.js.wysiwyg.lexical.table.LexicalTableCellNode.TableCellNode→resources.js.wysiwyg.lexical.core.nodes.common.CommonBlockAlignment
- Direction
- resources.js.wysiwyg.lexical.table.LexicalTableCellNode uses resources.js.wysiwyg.lexical.core.nodes.common, so a change to resources.js.wysiwyg.lexical.core.nodes.common can break resources.js.wysiwyg.lexical.table.LexicalTableCellNode, while a change to resources.js.wysiwyg.lexical.table.LexicalTableCellNode can't break resources.js.wysiwyg.lexical.core.nodes.common.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.table.LexicalTableCellNode uses a module listed above it, which is the healthy direction.
23→17 resources.js.wysiwyg.lexical.table.LexicalTableCellNode uses resources.js.wysiwyg.lexical.core.LexicalEditor✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.lexical.table.LexicalTableCellNode uses a type in resources.js.wysiwyg.lexical.core.LexicalEditor.
- The types involved
resources.js.wysiwyg.lexical.table.LexicalTableCellNode.TableCellNode→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditor
- Direction
- resources.js.wysiwyg.lexical.table.LexicalTableCellNode uses resources.js.wysiwyg.lexical.core.LexicalEditor, so a change to resources.js.wysiwyg.lexical.core.LexicalEditor can break resources.js.wysiwyg.lexical.table.LexicalTableCellNode, while a change to resources.js.wysiwyg.lexical.table.LexicalTableCellNode can't break resources.js.wysiwyg.lexical.core.LexicalEditor.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.table.LexicalTableCellNode uses a module listed above it, which is the healthy direction.
24→11 resources.js.wysiwyg.lexical.yjs uses resources.js.wysiwyg.lexical.core.LexicalSelection✕
- Connections
- 2 pairs of types, where a type in resources.js.wysiwyg.lexical.yjs uses a type in resources.js.wysiwyg.lexical.core.LexicalSelection.
- The types involved
resources.js.wysiwyg.lexical.yjs.SyncCursors→resources.js.wysiwyg.lexical.core.LexicalSelection.Pointresources.js.wysiwyg.lexical.yjs.Utils→resources.js.wysiwyg.lexical.core.LexicalSelection.RangeSelection
- Direction
- resources.js.wysiwyg.lexical.yjs uses resources.js.wysiwyg.lexical.core.LexicalSelection, so a change to resources.js.wysiwyg.lexical.core.LexicalSelection can break resources.js.wysiwyg.lexical.yjs, while a change to resources.js.wysiwyg.lexical.yjs can't break resources.js.wysiwyg.lexical.core.LexicalSelection.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.yjs uses a module listed above it, which is the healthy direction.
24→15 resources.js.wysiwyg.lexical.yjs uses resources.js.wysiwyg.lexical.core.LexicalNode✕
- Connections
- 2 pairs of types, where a type in resources.js.wysiwyg.lexical.yjs uses a type in resources.js.wysiwyg.lexical.core.LexicalNode.
- The types involved
resources.js.wysiwyg.lexical.yjs.SyncCursors→resources.js.wysiwyg.lexical.core.LexicalNode.NodeMapresources.js.wysiwyg.lexical.yjs.Utils→resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNode
- Direction
- resources.js.wysiwyg.lexical.yjs uses resources.js.wysiwyg.lexical.core.LexicalNode, so a change to resources.js.wysiwyg.lexical.core.LexicalNode can break resources.js.wysiwyg.lexical.yjs, while a change to resources.js.wysiwyg.lexical.yjs can't break resources.js.wysiwyg.lexical.core.LexicalNode.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.yjs uses a module listed above it, which is the healthy direction.
24→17 resources.js.wysiwyg.lexical.yjs uses resources.js.wysiwyg.lexical.core.LexicalEditor✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.lexical.yjs uses a type in resources.js.wysiwyg.lexical.core.LexicalEditor.
- The types involved
resources.js.wysiwyg.lexical.yjs.Bindings→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditor
- Direction
- resources.js.wysiwyg.lexical.yjs uses resources.js.wysiwyg.lexical.core.LexicalEditor, so a change to resources.js.wysiwyg.lexical.core.LexicalEditor can break resources.js.wysiwyg.lexical.yjs, while a change to resources.js.wysiwyg.lexical.yjs can't break resources.js.wysiwyg.lexical.core.LexicalEditor.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.yjs uses a module listed above it, which is the healthy direction.
25→7 BookStack.Entities.Models uses BookStack.Users.Models✕
- Connections
- 1 pair of types, where a type in BookStack.Entities.Models uses a type in BookStack.Users.Models.
- The types involved
BookStack.Entities.Models.Entity→BookStack.Users.Models.OwnableInterface
- Direction
- BookStack.Entities.Models uses BookStack.Users.Models, so a change to BookStack.Users.Models can break BookStack.Entities.Models, while a change to BookStack.Entities.Models can't break BookStack.Users.Models.
- Position
- Below the diagonal: BookStack.Entities.Models uses a module listed above it, which is the healthy direction.
25→20 BookStack.Entities.Models uses BookStack.Entities.Tools✕
- Connections
- 8 pairs of types, where a type in BookStack.Entities.Models uses a type in BookStack.Entities.Tools.
- The types involved
BookStack.Entities.Models.Book→BookStack.Entities.Tools.EntityCoverBookStack.Entities.Models.Book→BookStack.Entities.Tools.EntityDefaultTemplateBookStack.Entities.Models.Bookshelf→BookStack.Entities.Tools.EntityCoverBookStack.Entities.Models.Chapter→BookStack.Entities.Tools.EntityDefaultTemplateBookStack.Entities.Models.ContainerTrait→BookStack.Entities.Tools.EntityHtmlDescriptionBookStack.Entities.Models.HasCoverInterface→BookStack.Entities.Tools.EntityCoverBookStack.Entities.Models.HasDefaultTemplateInterface→BookStack.Entities.Tools.EntityDefaultTemplateBookStack.Entities.Models.HasDescriptionInterface→BookStack.Entities.Tools.EntityHtmlDescription
- Direction
- BookStack.Entities.Models uses BookStack.Entities.Tools, so a change to BookStack.Entities.Tools can break BookStack.Entities.Models, while a change to BookStack.Entities.Models can't break BookStack.Entities.Tools.
- Position
- Below the diagonal: BookStack.Entities.Models uses a module listed above it, which is the healthy direction.
25→32 BookStack.Entities.Models uses BookStack.App part of a loop✕
- Connections
- 6 pairs of types, where a type in BookStack.Entities.Models uses a type in BookStack.App.
- The types involved
BookStack.Entities.Models.Entity→BookStack.App.ModelBookStack.Entities.Models.Entity→BookStack.App.SluggableInterfaceBookStack.Entities.Models.EntityTable→BookStack.App.ModelBookStack.Entities.Models.PageRevision→BookStack.App.ModelBookStack.Entities.Models.PageUpdateDraft→BookStack.App.ModelBookStack.Entities.Models.SlugHistory→BookStack.App.Model
- Direction
- BookStack.Entities.Models uses BookStack.App, so a change to BookStack.App can break BookStack.Entities.Models, while a change to BookStack.Entities.Models can't break BookStack.App.
- 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.
25→33 BookStack.Entities.Models uses BookStack.Activity.Models part of a loop✕
- Connections
- 5 pairs of types, where a type in BookStack.Entities.Models uses a type in BookStack.Activity.Models.
- The types involved
BookStack.Entities.Models.Deletion→BookStack.Activity.Models.LoggableBookStack.Entities.Models.Entity→BookStack.Activity.Models.FavouritableBookStack.Entities.Models.Entity→BookStack.Activity.Models.LoggableBookStack.Entities.Models.Entity→BookStack.Activity.Models.ViewableBookStack.Entities.Models.PageRevision→BookStack.Activity.Models.Loggable
- Direction
- BookStack.Entities.Models uses BookStack.Activity.Models, so a change to BookStack.Activity.Models can break BookStack.Entities.Models, while a change to BookStack.Entities.Models can't break BookStack.Activity.Models.
- 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.
26→7 BookStack.Users uses BookStack.Users.Models✕
- Connections
- 1 pair of types, where a type in BookStack.Users uses a type in BookStack.Users.Models.
- The types involved
BookStack.Users.UserRepo→BookStack.Users.Models.User
- Direction
- BookStack.Users uses BookStack.Users.Models, so a change to BookStack.Users.Models can break BookStack.Users, while a change to BookStack.Users can't break BookStack.Users.Models.
- Position
- Below the diagonal: BookStack.Users uses a module listed above it, which is the healthy direction.
26→14 BookStack.Users uses BookStack.Uploads✕
- Connections
- 1 pair of types, where a type in BookStack.Users uses a type in BookStack.Uploads.
- The types involved
BookStack.Users.UserRepo→BookStack.Uploads.UserAvatars
- Direction
- BookStack.Users uses BookStack.Uploads, so a change to BookStack.Uploads can break BookStack.Users, while a change to BookStack.Users can't break BookStack.Uploads.
- Position
- Below the diagonal: BookStack.Users uses a module listed above it, which is the healthy direction.
26→20 BookStack.Users uses BookStack.Entities.Tools✕
- Connections
- 1 pair of types, where a type in BookStack.Users uses a type in BookStack.Entities.Tools.
- The types involved
BookStack.Users.UserRepo→BookStack.Entities.Tools.SlugGenerator
- Direction
- BookStack.Users uses BookStack.Entities.Tools, so a change to BookStack.Entities.Tools can break BookStack.Users, while a change to BookStack.Users can't break BookStack.Entities.Tools.
- Position
- Below the diagonal: BookStack.Users uses a module listed above it, which is the healthy direction.
26→36 BookStack.Users uses BookStack.Access part of a loop✕
- Connections
- 1 pair of types, where a type in BookStack.Users uses a type in BookStack.Access.
- The types involved
BookStack.Users.UserRepo→BookStack.Access.UserInviteService
- Direction
- BookStack.Users uses BookStack.Access, so a change to BookStack.Access can break BookStack.Users, while a change to BookStack.Users can't break BookStack.Access.
- 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.
27→17 resources.js.wysiwyg.lexical.rich-text uses resources.js.wysiwyg.lexical.core.LexicalEditor✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.lexical.rich-text uses a type in resources.js.wysiwyg.lexical.core.LexicalEditor.
- The types involved
resources.js.wysiwyg.lexical.rich-text.LexicalCodeBlockNode→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditor
- Direction
- resources.js.wysiwyg.lexical.rich-text uses resources.js.wysiwyg.lexical.core.LexicalEditor, so a change to resources.js.wysiwyg.lexical.core.LexicalEditor can break resources.js.wysiwyg.lexical.rich-text, while a change to resources.js.wysiwyg.lexical.rich-text can't break resources.js.wysiwyg.lexical.core.LexicalEditor.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.rich-text uses a module listed above it, which is the healthy direction.
27→22 resources.js.wysiwyg.lexical.rich-text uses resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode✕
- Connections
- 2 pairs of types, where a type in resources.js.wysiwyg.lexical.rich-text uses a type in resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode.
- The types involved
resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode→resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode.HeadingNoderesources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode→resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode.HeadingTagType
- Direction
- resources.js.wysiwyg.lexical.rich-text uses resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode, so a change to resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode can break resources.js.wysiwyg.lexical.rich-text, while a change to resources.js.wysiwyg.lexical.rich-text can't break resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.rich-text uses a module listed above it, which is the healthy direction.
28→17 resources.js.wysiwyg.lexical.table.LexicalTableNode uses resources.js.wysiwyg.lexical.core.LexicalEditor✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.lexical.table.LexicalTableNode uses a type in resources.js.wysiwyg.lexical.core.LexicalEditor.
- The types involved
resources.js.wysiwyg.lexical.table.LexicalTableNode.TableNode→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditor
- Direction
- resources.js.wysiwyg.lexical.table.LexicalTableNode uses resources.js.wysiwyg.lexical.core.LexicalEditor, so a change to resources.js.wysiwyg.lexical.core.LexicalEditor can break resources.js.wysiwyg.lexical.table.LexicalTableNode, while a change to resources.js.wysiwyg.lexical.table.LexicalTableNode can't break resources.js.wysiwyg.lexical.core.LexicalEditor.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.table.LexicalTableNode uses a module listed above it, which is the healthy direction.
28→23 resources.js.wysiwyg.lexical.table.LexicalTableNode uses resources.js.wysiwyg.lexical.table.LexicalTableCellNode✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.lexical.table.LexicalTableNode uses a type in resources.js.wysiwyg.lexical.table.LexicalTableCellNode.
- The types involved
resources.js.wysiwyg.lexical.table.LexicalTableNode.TableNode→resources.js.wysiwyg.lexical.table.LexicalTableCellNode.TableCellNode
- Direction
- resources.js.wysiwyg.lexical.table.LexicalTableNode uses resources.js.wysiwyg.lexical.table.LexicalTableCellNode, so a change to resources.js.wysiwyg.lexical.table.LexicalTableCellNode can break resources.js.wysiwyg.lexical.table.LexicalTableNode, while a change to resources.js.wysiwyg.lexical.table.LexicalTableNode can't break resources.js.wysiwyg.lexical.table.LexicalTableCellNode.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.table.LexicalTableNode uses a module listed above it, which is the healthy direction.
29→10 BookStack.Entities.Queries uses BookStack.Permissions✕
- Connections
- 3 pairs of types, where a type in BookStack.Entities.Queries uses a type in BookStack.Permissions.
- The types involved
BookStack.Entities.Queries.QueryPopular→BookStack.Permissions.PermissionApplicatorBookStack.Entities.Queries.QueryRecentlyViewed→BookStack.Permissions.PermissionApplicatorBookStack.Entities.Queries.QueryTopFavourites→BookStack.Permissions.PermissionApplicator
- Direction
- BookStack.Entities.Queries uses BookStack.Permissions, so a change to BookStack.Permissions can break BookStack.Entities.Queries, while a change to BookStack.Entities.Queries can't break BookStack.Permissions.
- Position
- Below the diagonal: BookStack.Entities.Queries uses a module listed above it, which is the healthy direction.
29→20 BookStack.Entities.Queries uses BookStack.Entities.Tools✕
- Connections
- 4 pairs of types, where a type in BookStack.Entities.Queries uses a type in BookStack.Entities.Tools.
- The types involved
BookStack.Entities.Queries.EntityQueries→BookStack.Entities.Tools.SlugHistoryBookStack.Entities.Queries.QueryPopular→BookStack.Entities.Tools.MixedEntityListLoaderBookStack.Entities.Queries.QueryRecentlyViewed→BookStack.Entities.Tools.MixedEntityListLoaderBookStack.Entities.Queries.QueryTopFavourites→BookStack.Entities.Tools.MixedEntityListLoader
- Direction
- BookStack.Entities.Queries uses BookStack.Entities.Tools, so a change to BookStack.Entities.Tools can break BookStack.Entities.Queries, while a change to BookStack.Entities.Queries can't break BookStack.Entities.Tools.
- Position
- Below the diagonal: BookStack.Entities.Queries uses a module listed above it, which is the healthy direction.
29→25 BookStack.Entities.Queries uses BookStack.Entities.Models✕
- Connections
- 8 pairs of types, where a type in BookStack.Entities.Queries uses a type in BookStack.Entities.Models.
- The types involved
BookStack.Entities.Queries.BookQueries→BookStack.Entities.Models.BookBookStack.Entities.Queries.BookshelfQueries→BookStack.Entities.Models.BookshelfBookStack.Entities.Queries.ChapterQueries→BookStack.Entities.Models.ChapterBookStack.Entities.Queries.EntityQueries→BookStack.Entities.Models.EntityBookStack.Entities.Queries.PageQueries→BookStack.Entities.Models.PageBookStack.Entities.Queries.PageRevisionQueries→BookStack.Entities.Models.PageRevisionBookStack.Entities.Queries.PageUpdateDraftQueries→BookStack.Entities.Models.PageUpdateDraftBookStack.Entities.Queries.ProvidesEntityQueries→BookStack.Entities.Models.Entity
- Direction
- BookStack.Entities.Queries uses BookStack.Entities.Models, so a change to BookStack.Entities.Models can break BookStack.Entities.Queries, while a change to BookStack.Entities.Queries can't break BookStack.Entities.Models.
- Position
- Below the diagonal: BookStack.Entities.Queries uses a module listed above it, which is the healthy direction.
30→4 resources.js.wysiwyg.lexical.table uses resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.lexical.table uses a type in resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode.
- The types involved
resources.js.wysiwyg.lexical.table.LexicalTableUtils→resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode.ElementNode
- Direction
- resources.js.wysiwyg.lexical.table uses resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode, so a change to resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode can break resources.js.wysiwyg.lexical.table, while a change to resources.js.wysiwyg.lexical.table can't break resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.table uses a module listed above it, which is the healthy direction.
30→11 resources.js.wysiwyg.lexical.table uses resources.js.wysiwyg.lexical.core.LexicalSelection✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.lexical.table uses a type in resources.js.wysiwyg.lexical.core.LexicalSelection.
- The types involved
resources.js.wysiwyg.lexical.table.LexicalTableSelectionHelpers→resources.js.wysiwyg.lexical.core.LexicalSelection.RangeSelection
- Direction
- resources.js.wysiwyg.lexical.table uses resources.js.wysiwyg.lexical.core.LexicalSelection, so a change to resources.js.wysiwyg.lexical.core.LexicalSelection can break resources.js.wysiwyg.lexical.table, while a change to resources.js.wysiwyg.lexical.table can't break resources.js.wysiwyg.lexical.core.LexicalSelection.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.table uses a module listed above it, which is the healthy direction.
30→15 resources.js.wysiwyg.lexical.table uses resources.js.wysiwyg.lexical.core.LexicalNode✕
- Connections
- 3 pairs of types, where a type in resources.js.wysiwyg.lexical.table uses a type in resources.js.wysiwyg.lexical.core.LexicalNode.
- The types involved
resources.js.wysiwyg.lexical.table.LexicalTableSelection→resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNoderesources.js.wysiwyg.lexical.table.LexicalTableSelectionHelpers→resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNoderesources.js.wysiwyg.lexical.table.LexicalTableUtils→resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNode
- Direction
- resources.js.wysiwyg.lexical.table uses resources.js.wysiwyg.lexical.core.LexicalNode, so a change to resources.js.wysiwyg.lexical.core.LexicalNode can break resources.js.wysiwyg.lexical.table, while a change to resources.js.wysiwyg.lexical.table can't break resources.js.wysiwyg.lexical.core.LexicalNode.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.table uses a module listed above it, which is the healthy direction.
30→17 resources.js.wysiwyg.lexical.table uses resources.js.wysiwyg.lexical.core.LexicalEditor✕
- Connections
- 2 pairs of types, where a type in resources.js.wysiwyg.lexical.table uses a type in resources.js.wysiwyg.lexical.core.LexicalEditor.
- The types involved
resources.js.wysiwyg.lexical.table.LexicalTableNode→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditorresources.js.wysiwyg.lexical.table.LexicalTableSelectionHelpers→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditor
- Direction
- resources.js.wysiwyg.lexical.table uses resources.js.wysiwyg.lexical.core.LexicalEditor, so a change to resources.js.wysiwyg.lexical.core.LexicalEditor can break resources.js.wysiwyg.lexical.table, while a change to resources.js.wysiwyg.lexical.table can't break resources.js.wysiwyg.lexical.core.LexicalEditor.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.table uses a module listed above it, which is the healthy direction.
30→23 resources.js.wysiwyg.lexical.table uses resources.js.wysiwyg.lexical.table.LexicalTableCellNode✕
- Connections
- 3 pairs of types, where a type in resources.js.wysiwyg.lexical.table uses a type in resources.js.wysiwyg.lexical.table.LexicalTableCellNode.
- The types involved
resources.js.wysiwyg.lexical.table.LexicalTableCellNode→resources.js.wysiwyg.lexical.table.LexicalTableCellNode.TableCellNoderesources.js.wysiwyg.lexical.table.LexicalTableSelectionHelpers→resources.js.wysiwyg.lexical.table.LexicalTableCellNode.TableCellNoderesources.js.wysiwyg.lexical.table.LexicalTableUtils→resources.js.wysiwyg.lexical.table.LexicalTableCellNode.TableCellNode
- Direction
- resources.js.wysiwyg.lexical.table uses resources.js.wysiwyg.lexical.table.LexicalTableCellNode, so a change to resources.js.wysiwyg.lexical.table.LexicalTableCellNode can break resources.js.wysiwyg.lexical.table, while a change to resources.js.wysiwyg.lexical.table can't break resources.js.wysiwyg.lexical.table.LexicalTableCellNode.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.table uses a module listed above it, which is the healthy direction.
30→28 resources.js.wysiwyg.lexical.table uses resources.js.wysiwyg.lexical.table.LexicalTableNode✕
- Connections
- 4 pairs of types, where a type in resources.js.wysiwyg.lexical.table uses a type in resources.js.wysiwyg.lexical.table.LexicalTableNode.
- The types involved
resources.js.wysiwyg.lexical.table.LexicalCaptionNode→resources.js.wysiwyg.lexical.table.LexicalTableNode.TableNoderesources.js.wysiwyg.lexical.table.LexicalTableNode→resources.js.wysiwyg.lexical.table.LexicalTableNode.TableNoderesources.js.wysiwyg.lexical.table.LexicalTableSelectionHelpers→resources.js.wysiwyg.lexical.table.LexicalTableNode.TableNoderesources.js.wysiwyg.lexical.table.LexicalTableUtils→resources.js.wysiwyg.lexical.table.LexicalTableNode.TableNode
- Direction
- resources.js.wysiwyg.lexical.table uses resources.js.wysiwyg.lexical.table.LexicalTableNode, so a change to resources.js.wysiwyg.lexical.table.LexicalTableNode can break resources.js.wysiwyg.lexical.table, while a change to resources.js.wysiwyg.lexical.table can't break resources.js.wysiwyg.lexical.table.LexicalTableNode.
- Position
- Below the diagonal: resources.js.wysiwyg.lexical.table uses a module listed above it, which is the healthy direction.
31→4 resources.js.wysiwyg.utils uses resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.utils uses a type in resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode.
- The types involved
resources.js.wysiwyg.utils.nodes→resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode.ElementNode
- Direction
- resources.js.wysiwyg.utils uses resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode, so a change to resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode can break resources.js.wysiwyg.utils, while a change to resources.js.wysiwyg.utils can't break resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode.
- Position
- Below the diagonal: resources.js.wysiwyg.utils uses a module listed above it, which is the healthy direction.
31→5 resources.js.wysiwyg.utils uses resources.js.wysiwyg.lexical.core.nodes.common✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.utils uses a type in resources.js.wysiwyg.lexical.core.nodes.common.
- The types involved
resources.js.wysiwyg.utils.selection→resources.js.wysiwyg.lexical.core.nodes.common.CommonBlockAlignment
- Direction
- resources.js.wysiwyg.utils uses resources.js.wysiwyg.lexical.core.nodes.common, so a change to resources.js.wysiwyg.lexical.core.nodes.common can break resources.js.wysiwyg.utils, while a change to resources.js.wysiwyg.utils can't break resources.js.wysiwyg.lexical.core.nodes.common.
- Position
- Below the diagonal: resources.js.wysiwyg.utils uses a module listed above it, which is the healthy direction.
31→8 resources.js.wysiwyg.utils uses resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.utils uses a type in resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode.
- The types involved
resources.js.wysiwyg.utils.selection→resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode.TextFormatType
- Direction
- resources.js.wysiwyg.utils uses resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode, so a change to resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode can break resources.js.wysiwyg.utils, while a change to resources.js.wysiwyg.utils can't break resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode.
- Position
- Below the diagonal: resources.js.wysiwyg.utils uses a module listed above it, which is the healthy direction.
31→11 resources.js.wysiwyg.utils uses resources.js.wysiwyg.lexical.core.LexicalSelection✕
- Connections
- 3 pairs of types, where a type in resources.js.wysiwyg.utils uses a type in resources.js.wysiwyg.lexical.core.LexicalSelection.
- The types involved
resources.js.wysiwyg.utils.nodes→resources.js.wysiwyg.lexical.core.LexicalSelection.RangeSelectionresources.js.wysiwyg.utils.selection→resources.js.wysiwyg.lexical.core.LexicalSelection.BaseSelectionresources.js.wysiwyg.utils.selection→resources.js.wysiwyg.lexical.core.LexicalSelection.NodeSelection
- Direction
- resources.js.wysiwyg.utils uses resources.js.wysiwyg.lexical.core.LexicalSelection, so a change to resources.js.wysiwyg.lexical.core.LexicalSelection can break resources.js.wysiwyg.utils, while a change to resources.js.wysiwyg.utils can't break resources.js.wysiwyg.lexical.core.LexicalSelection.
- Position
- Below the diagonal: resources.js.wysiwyg.utils uses a module listed above it, which is the healthy direction.
31→15 resources.js.wysiwyg.utils uses resources.js.wysiwyg.lexical.core.LexicalNode✕
- Connections
- 4 pairs of types, where a type in resources.js.wysiwyg.utils uses a type in resources.js.wysiwyg.lexical.core.LexicalNode.
- The types involved
resources.js.wysiwyg.utils.images→resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNoderesources.js.wysiwyg.utils.node-clipboard→resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNoderesources.js.wysiwyg.utils.nodes→resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNoderesources.js.wysiwyg.utils.selection→resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNode
- Direction
- resources.js.wysiwyg.utils uses resources.js.wysiwyg.lexical.core.LexicalNode, so a change to resources.js.wysiwyg.lexical.core.LexicalNode can break resources.js.wysiwyg.utils, while a change to resources.js.wysiwyg.utils can't break resources.js.wysiwyg.lexical.core.LexicalNode.
- Position
- Below the diagonal: resources.js.wysiwyg.utils uses a module listed above it, which is the healthy direction.
31→17 resources.js.wysiwyg.utils uses resources.js.wysiwyg.lexical.core.LexicalEditor✕
- Connections
- 9 pairs of types, where a type in resources.js.wysiwyg.utils uses a type in resources.js.wysiwyg.lexical.core.LexicalEditor.
- The types involved
resources.js.wysiwyg.utils.actions→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditorresources.js.wysiwyg.utils.diagrams→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditorresources.js.wysiwyg.utils.formats→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditorresources.js.wysiwyg.utils.lists→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditorresources.js.wysiwyg.utils.node-clipboard→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditorresources.js.wysiwyg.utils.nodes→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditorresources.js.wysiwyg.utils.selection→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditorresources.js.wysiwyg.utils.table-copy-paste→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditorresources.js.wysiwyg.utils.tables→resources.js.wysiwyg.lexical.core.LexicalEditor.LexicalEditor
- Direction
- resources.js.wysiwyg.utils uses resources.js.wysiwyg.lexical.core.LexicalEditor, so a change to resources.js.wysiwyg.lexical.core.LexicalEditor can break resources.js.wysiwyg.utils, while a change to resources.js.wysiwyg.utils can't break resources.js.wysiwyg.lexical.core.LexicalEditor.
- Position
- Below the diagonal: resources.js.wysiwyg.utils uses a module listed above it, which is the healthy direction.
31→22 resources.js.wysiwyg.utils uses resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.utils uses a type in resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode.
- The types involved
resources.js.wysiwyg.utils.formats→resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode.HeadingTagType
- Direction
- resources.js.wysiwyg.utils uses resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode, so a change to resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode can break resources.js.wysiwyg.utils, while a change to resources.js.wysiwyg.utils can't break resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode.
- Position
- Below the diagonal: resources.js.wysiwyg.utils uses a module listed above it, which is the healthy direction.
31→23 resources.js.wysiwyg.utils uses resources.js.wysiwyg.lexical.table.LexicalTableCellNode✕
- Connections
- 1 pair of types, where a type in resources.js.wysiwyg.utils uses a type in resources.js.wysiwyg.lexical.table.LexicalTableCellNode.
- The types involved
resources.js.wysiwyg.utils.tables→resources.js.wysiwyg.lexical.table.LexicalTableCellNode.TableCellNode
- Direction
- resources.js.wysiwyg.utils uses resources.js.wysiwyg.lexical.table.LexicalTableCellNode, so a change to resources.js.wysiwyg.lexical.table.LexicalTableCellNode can break resources.js.wysiwyg.utils, while a change to resources.js.wysiwyg.utils can't break resources.js.wysiwyg.lexical.table.LexicalTableCellNode.
- Position
- Below the diagonal: resources.js.wysiwyg.utils uses a module listed above it, which is the healthy direction.
31→28 resources.js.wysiwyg.utils uses resources.js.wysiwyg.lexical.table.LexicalTableNode✕
- Connections
- 2 pairs of types, where a type in resources.js.wysiwyg.utils uses a type in resources.js.wysiwyg.lexical.table.LexicalTableNode.
- The types involved
resources.js.wysiwyg.utils.table-copy-paste→resources.js.wysiwyg.lexical.table.LexicalTableNode.TableNoderesources.js.wysiwyg.utils.tables→resources.js.wysiwyg.lexical.table.LexicalTableNode.TableNode
- Direction
- resources.js.wysiwyg.utils uses resources.js.wysiwyg.lexical.table.LexicalTableNode, so a change to resources.js.wysiwyg.lexical.table.LexicalTableNode can break resources.js.wysiwyg.utils, while a change to resources.js.wysiwyg.utils can't break resources.js.wysiwyg.lexical.table.LexicalTableNode.
- Position
- Below the diagonal: resources.js.wysiwyg.utils uses a module listed above it, which is the healthy direction.
32→1 BookStack.App uses BookStack.Http✕
- Connections
- 3 pairs of types, where a type in BookStack.App uses a type in BookStack.Http.
- The types involved
BookStack.App.HomeController→BookStack.Http.ControllerBookStack.App.MetaController→BookStack.Http.ControllerBookStack.App.SystemApiController→BookStack.Http.ApiController
- Direction
- BookStack.App uses BookStack.Http, so a change to BookStack.Http can break BookStack.App, while a change to BookStack.App can't break BookStack.Http.
- Position
- Below the diagonal: BookStack.App uses a module listed above it, which is the healthy direction.
32→7 BookStack.App uses BookStack.Users.Models✕
- Connections
- 1 pair of types, where a type in BookStack.App uses a type in BookStack.Users.Models.
- The types involved
BookStack.App.MailNotification→BookStack.Users.Models.User
- Direction
- BookStack.App uses BookStack.Users.Models, so a change to BookStack.Users.Models can break BookStack.App, while a change to BookStack.App can't break BookStack.Users.Models.
- Position
- Below the diagonal: BookStack.App uses a module listed above it, which is the healthy direction.
32→14 BookStack.App uses BookStack.Uploads✕
- Connections
- 1 pair of types, where a type in BookStack.App uses a type in BookStack.Uploads.
- The types involved
BookStack.App.MetaController→BookStack.Uploads.FaviconHandler
- Direction
- BookStack.App uses BookStack.Uploads, so a change to BookStack.Uploads can break BookStack.App, while a change to BookStack.App can't break BookStack.Uploads.
- Position
- Below the diagonal: BookStack.App uses a module listed above it, which is the healthy direction.
32→29 BookStack.App uses BookStack.Entities.Queries✕
- Connections
- 1 pair of types, where a type in BookStack.App uses a type in BookStack.Entities.Queries.
- The types involved
BookStack.App.HomeController→BookStack.Entities.Queries.EntityQueries
- Direction
- BookStack.App uses BookStack.Entities.Queries, so a change to BookStack.Entities.Queries can break BookStack.App, while a change to BookStack.App can't break BookStack.Entities.Queries.
- Position
- Below the diagonal: BookStack.App uses a module listed above it, which is the healthy direction.
33→7 BookStack.Activity.Models uses BookStack.Users.Models✕
- Connections
- 1 pair of types, where a type in BookStack.Activity.Models uses a type in BookStack.Users.Models.
- The types involved
BookStack.Activity.Models.Comment→BookStack.Users.Models.OwnableInterface
- Direction
- BookStack.Activity.Models uses BookStack.Users.Models, so a change to BookStack.Users.Models can break BookStack.Activity.Models, while a change to BookStack.Activity.Models can't break BookStack.Users.Models.
- Position
- Below the diagonal: BookStack.Activity.Models uses a module listed above it, which is the healthy direction.
33→32 BookStack.Activity.Models uses BookStack.App✕
- Connections
- 5 pairs of types, where a type in BookStack.Activity.Models uses a type in BookStack.App.
- The types involved
BookStack.Activity.Models.Activity→BookStack.App.ModelBookStack.Activity.Models.Comment→BookStack.App.ModelBookStack.Activity.Models.Favourite→BookStack.App.ModelBookStack.Activity.Models.Tag→BookStack.App.ModelBookStack.Activity.Models.View→BookStack.App.Model
- Direction
- BookStack.Activity.Models uses BookStack.App, so a change to BookStack.App can break BookStack.Activity.Models, while a change to BookStack.Activity.Models can't break BookStack.App.
- Position
- Below the diagonal: BookStack.Activity.Models uses a module listed above it, which is the healthy direction.
34→14 BookStack.Exports.ZipExports uses BookStack.Uploads✕
- Connections
- 13 pairs of types, where a type in BookStack.Exports.ZipExports uses a type in BookStack.Uploads.
- The types involved
BookStack.Exports.ZipExports.ZipExportFiles→BookStack.Uploads.AttachmentBookStack.Exports.ZipExports.ZipExportFiles→BookStack.Uploads.AttachmentServiceBookStack.Exports.ZipExports.ZipExportFiles→BookStack.Uploads.ImageBookStack.Exports.ZipExports.ZipExportFiles→BookStack.Uploads.ImageServiceBookStack.Exports.ZipExports.ZipExportReferences→BookStack.Uploads.ImageServiceBookStack.Exports.ZipExports.ZipImportReferences→BookStack.Uploads.AttachmentBookStack.Exports.ZipExports.ZipImportReferences→BookStack.Uploads.ImageBookStack.Exports.ZipExports.ZipImportReferences→BookStack.Uploads.ImageResizerBookStack.Exports.ZipExports.ZipImportRunner→BookStack.Uploads.AttachmentBookStack.Exports.ZipExports.ZipImportRunner→BookStack.Uploads.AttachmentServiceBookStack.Exports.ZipExports.ZipImportRunner→BookStack.Uploads.FileStorageBookStack.Exports.ZipExports.ZipImportRunner→BookStack.Uploads.ImageBookStack.Exports.ZipExports.ZipImportRunner→BookStack.Uploads.ImageService
- Direction
- BookStack.Exports.ZipExports uses BookStack.Uploads, so a change to BookStack.Uploads can break BookStack.Exports.ZipExports, while a change to BookStack.Exports.ZipExports can't break BookStack.Uploads.
- Position
- Below the diagonal: BookStack.Exports.ZipExports uses a module listed above it, which is the healthy direction.
34→16 BookStack.Exports.ZipExports uses BookStack.Entities.Repos✕
- Connections
- 5 pairs of types, where a type in BookStack.Exports.ZipExports uses a type in BookStack.Entities.Repos.
- The types involved
BookStack.Exports.ZipExports.ZipImportReferences→BookStack.Entities.Repos.BaseRepoBookStack.Exports.ZipExports.ZipImportReferences→BookStack.Entities.Repos.PageRepoBookStack.Exports.ZipExports.ZipImportRunner→BookStack.Entities.Repos.BookRepoBookStack.Exports.ZipExports.ZipImportRunner→BookStack.Entities.Repos.ChapterRepoBookStack.Exports.ZipExports.ZipImportRunner→BookStack.Entities.Repos.PageRepo
- Direction
- BookStack.Exports.ZipExports uses BookStack.Entities.Repos, so a change to BookStack.Entities.Repos can break BookStack.Exports.ZipExports, while a change to BookStack.Exports.ZipExports can't break BookStack.Entities.Repos.
- Position
- Below the diagonal: BookStack.Exports.ZipExports uses a module listed above it, which is the healthy direction.
34→25 BookStack.Exports.ZipExports uses BookStack.Entities.Models✕
- Connections
- 10 pairs of types, where a type in BookStack.Exports.ZipExports uses a type in BookStack.Entities.Models.
- The types involved
BookStack.Exports.ZipExports.ZipExportBuilder→BookStack.Entities.Models.BookBookStack.Exports.ZipExports.ZipExportBuilder→BookStack.Entities.Models.ChapterBookStack.Exports.ZipExports.ZipExportBuilder→BookStack.Entities.Models.PageBookStack.Exports.ZipExports.ZipImportReferences→BookStack.Entities.Models.BookBookStack.Exports.ZipExports.ZipImportReferences→BookStack.Entities.Models.ChapterBookStack.Exports.ZipExports.ZipImportReferences→BookStack.Entities.Models.PageBookStack.Exports.ZipExports.ZipImportRunner→BookStack.Entities.Models.BookBookStack.Exports.ZipExports.ZipImportRunner→BookStack.Entities.Models.ChapterBookStack.Exports.ZipExports.ZipImportRunner→BookStack.Entities.Models.EntityBookStack.Exports.ZipExports.ZipImportRunner→BookStack.Entities.Models.Page
- Direction
- BookStack.Exports.ZipExports uses BookStack.Entities.Models, so a change to BookStack.Entities.Models can break BookStack.Exports.ZipExports, while a change to BookStack.Exports.ZipExports can't break BookStack.Entities.Models.
- Position
- Below the diagonal: BookStack.Exports.ZipExports uses a module listed above it, which is the healthy direction.
34→29 BookStack.Exports.ZipExports uses BookStack.Entities.Queries✕
- Connections
- 1 pair of types, where a type in BookStack.Exports.ZipExports uses a type in BookStack.Entities.Queries.
- The types involved
BookStack.Exports.ZipExports.ZipReferenceParser→BookStack.Entities.Queries.EntityQueries
- Direction
- BookStack.Exports.ZipExports uses BookStack.Entities.Queries, so a change to BookStack.Entities.Queries can break BookStack.Exports.ZipExports, while a change to BookStack.Exports.ZipExports can't break BookStack.Entities.Queries.
- Position
- Below the diagonal: BookStack.Exports.ZipExports uses a module listed above it, which is the healthy direction.
34→32 BookStack.Exports.ZipExports uses BookStack.App✕
- Connections
- 3 pairs of types, where a type in BookStack.Exports.ZipExports uses a type in BookStack.App.
- The types involved
BookStack.Exports.ZipExports.ZipExportReferences→BookStack.App.ModelBookStack.Exports.ZipExports.ZipImportReferences→BookStack.App.ModelBookStack.Exports.ZipExports.ZipReferenceParser→BookStack.App.Model
- Direction
- BookStack.Exports.ZipExports uses BookStack.App, so a change to BookStack.App can break BookStack.Exports.ZipExports, while a change to BookStack.Exports.ZipExports can't break BookStack.App.
- Position
- Below the diagonal: BookStack.Exports.ZipExports uses a module listed above it, which is the healthy direction.
34→38 BookStack.Exports.ZipExports uses BookStack.Exports part of a loop✕
- Connections
- 1 pair of types, where a type in BookStack.Exports.ZipExports uses a type in BookStack.Exports.
- The types involved
BookStack.Exports.ZipExports.ZipImportRunner→BookStack.Exports.Import
- Direction
- BookStack.Exports.ZipExports uses BookStack.Exports, so a change to BookStack.Exports can break BookStack.Exports.ZipExports, while a change to BookStack.Exports.ZipExports can't break BookStack.Exports.
- 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.
35→1 BookStack.Search uses BookStack.Http✕
- Connections
- 2 pairs of types, where a type in BookStack.Search uses a type in BookStack.Http.
- The types involved
BookStack.Search.SearchApiController→BookStack.Http.ApiControllerBookStack.Search.SearchController→BookStack.Http.Controller
- Direction
- BookStack.Search uses BookStack.Http, so a change to BookStack.Http can break BookStack.Search, while a change to BookStack.Search can't break BookStack.Http.
- Position
- Below the diagonal: BookStack.Search uses a module listed above it, which is the healthy direction.
35→10 BookStack.Search uses BookStack.Permissions✕
- Connections
- 1 pair of types, where a type in BookStack.Search uses a type in BookStack.Permissions.
- The types involved
BookStack.Search.SearchRunner→BookStack.Permissions.PermissionApplicator
- Direction
- BookStack.Search uses BookStack.Permissions, so a change to BookStack.Permissions can break BookStack.Search, while a change to BookStack.Search can't break BookStack.Permissions.
- Position
- Below the diagonal: BookStack.Search uses a module listed above it, which is the healthy direction.
35→20 BookStack.Search uses BookStack.Entities.Tools✕
- Connections
- 2 pairs of types, where a type in BookStack.Search uses a type in BookStack.Entities.Tools.
- The types involved
BookStack.Search.SearchController→BookStack.Entities.Tools.SiblingFetcherBookStack.Search.SearchRunner→BookStack.Entities.Tools.EntityHydrator
- Direction
- BookStack.Search uses BookStack.Entities.Tools, so a change to BookStack.Entities.Tools can break BookStack.Search, while a change to BookStack.Search can't break BookStack.Entities.Tools.
- Position
- Below the diagonal: BookStack.Search uses a module listed above it, which is the healthy direction.
35→25 BookStack.Search uses BookStack.Entities.Models✕
- Connections
- 2 pairs of types, where a type in BookStack.Search uses a type in BookStack.Entities.Models.
- The types involved
BookStack.Search.SearchIndex→BookStack.Entities.Models.EntityBookStack.Search.SearchResultsFormatter→BookStack.Entities.Models.Entity
- Direction
- BookStack.Search uses BookStack.Entities.Models, so a change to BookStack.Entities.Models can break BookStack.Search, while a change to BookStack.Search can't break BookStack.Entities.Models.
- Position
- Below the diagonal: BookStack.Search uses a module listed above it, which is the healthy direction.
35→29 BookStack.Search uses BookStack.Entities.Queries✕
- Connections
- 3 pairs of types, where a type in BookStack.Search uses a type in BookStack.Entities.Queries.
- The types involved
BookStack.Search.SearchController→BookStack.Entities.Queries.PageQueriesBookStack.Search.SearchController→BookStack.Entities.Queries.QueryPopularBookStack.Search.SearchRunner→BookStack.Entities.Queries.EntityQueries
- Direction
- BookStack.Search uses BookStack.Entities.Queries, so a change to BookStack.Entities.Queries can break BookStack.Search, while a change to BookStack.Search can't break BookStack.Entities.Queries.
- Position
- Below the diagonal: BookStack.Search uses a module listed above it, which is the healthy direction.
35→32 BookStack.Search uses BookStack.App✕
- Connections
- 1 pair of types, where a type in BookStack.Search uses a type in BookStack.App.
- The types involved
BookStack.Search.SearchTerm→BookStack.App.Model
- Direction
- BookStack.Search uses BookStack.App, so a change to BookStack.App can break BookStack.Search, while a change to BookStack.Search can't break BookStack.App.
- Position
- Below the diagonal: BookStack.Search uses a module listed above it, which is the healthy direction.
36→7 BookStack.Access uses BookStack.Users.Models✕
- Connections
- 10 pairs of types, where a type in BookStack.Access uses a type in BookStack.Users.Models.
- The types involved
BookStack.Access.EmailConfirmationService→BookStack.Users.Models.UserBookStack.Access.ExternalBaseUserProvider→BookStack.Users.Models.UserBookStack.Access.GroupSyncService→BookStack.Users.Models.RoleBookStack.Access.GroupSyncService→BookStack.Users.Models.UserBookStack.Access.LdapService→BookStack.Users.Models.UserBookStack.Access.LoginService→BookStack.Users.Models.UserBookStack.Access.RegistrationService→BookStack.Users.Models.UserBookStack.Access.Saml2Service→BookStack.Users.Models.UserBookStack.Access.UserInviteService→BookStack.Users.Models.UserBookStack.Access.UserTokenService→BookStack.Users.Models.User
- Direction
- BookStack.Access uses BookStack.Users.Models, so a change to BookStack.Users.Models can break BookStack.Access, while a change to BookStack.Access can't break BookStack.Users.Models.
- Position
- Below the diagonal: BookStack.Access uses a module listed above it, which is the healthy direction.
36→14 BookStack.Access uses BookStack.Uploads✕
- Connections
- 1 pair of types, where a type in BookStack.Access uses a type in BookStack.Uploads.
- The types involved
BookStack.Access.LdapService→BookStack.Uploads.UserAvatars
- Direction
- BookStack.Access uses BookStack.Uploads, so a change to BookStack.Uploads can break BookStack.Access, while a change to BookStack.Access can't break BookStack.Uploads.
- Position
- Below the diagonal: BookStack.Access uses a module listed above it, which is the healthy direction.
36→26 BookStack.Access uses BookStack.Users✕
- Connections
- 2 pairs of types, where a type in BookStack.Access uses a type in BookStack.Users.
- The types involved
BookStack.Access.ExternalBaseUserProvider→BookStack.Users.UserRepoBookStack.Access.RegistrationService→BookStack.Users.UserRepo
- Direction
- BookStack.Access uses BookStack.Users, so a change to BookStack.Users can break BookStack.Access, while a change to BookStack.Access can't break BookStack.Users.
- Position
- Below the diagonal: BookStack.Access uses a module listed above it, which is the healthy direction.
36→32 BookStack.Access uses BookStack.App✕
- Connections
- 1 pair of types, where a type in BookStack.Access uses a type in BookStack.App.
- The types involved
BookStack.Access.SocialAccount→BookStack.App.Model
- Direction
- BookStack.Access uses BookStack.App, so a change to BookStack.App can break BookStack.Access, while a change to BookStack.Access can't break BookStack.App.
- Position
- Below the diagonal: BookStack.Access uses a module listed above it, which is the healthy direction.
36→33 BookStack.Access uses BookStack.Activity.Models✕
- Connections
- 1 pair of types, where a type in BookStack.Access uses a type in BookStack.Activity.Models.
- The types involved
BookStack.Access.SocialAccount→BookStack.Activity.Models.Loggable
- Direction
- BookStack.Access uses BookStack.Activity.Models, so a change to BookStack.Activity.Models can break BookStack.Access, while a change to BookStack.Access can't break BookStack.Activity.Models.
- Position
- Below the diagonal: BookStack.Access uses a module listed above it, which is the healthy direction.
37→7 BookStack.Console.Commands uses BookStack.Users.Models✕
- Connections
- 3 pairs of types, where a type in BookStack.Console.Commands uses a type in BookStack.Users.Models.
- The types involved
BookStack.Console.Commands.CreateAdminCommand→BookStack.Users.Models.RoleBookStack.Console.Commands.HandlesSingleUser→BookStack.Users.Models.UserBookStack.Console.Commands.RefreshAvatarCommand→BookStack.Users.Models.User
- Direction
- BookStack.Console.Commands uses BookStack.Users.Models, so a change to BookStack.Users.Models can break BookStack.Console.Commands, while a change to BookStack.Console.Commands can't break BookStack.Users.Models.
- Position
- Below the diagonal: BookStack.Console.Commands uses a module listed above it, which is the healthy direction.
37→10 BookStack.Console.Commands uses BookStack.Permissions✕
- Connections
- 1 pair of types, where a type in BookStack.Console.Commands uses a type in BookStack.Permissions.
- The types involved
BookStack.Console.Commands.RegeneratePermissionsCommand→BookStack.Permissions.JointPermissionBuilder
- Direction
- BookStack.Console.Commands uses BookStack.Permissions, so a change to BookStack.Permissions can break BookStack.Console.Commands, while a change to BookStack.Console.Commands can't break BookStack.Permissions.
- Position
- Below the diagonal: BookStack.Console.Commands uses a module listed above it, which is the healthy direction.
37→13 BookStack.Console.Commands uses BookStack.References✕
- Connections
- 1 pair of types, where a type in BookStack.Console.Commands uses a type in BookStack.References.
- The types involved
BookStack.Console.Commands.RegenerateReferencesCommand→BookStack.References.ReferenceStore
- Direction
- BookStack.Console.Commands uses BookStack.References, so a change to BookStack.References can break BookStack.Console.Commands, while a change to BookStack.Console.Commands can't break BookStack.References.
- Position
- Below the diagonal: BookStack.Console.Commands uses a module listed above it, which is the healthy direction.
37→14 BookStack.Console.Commands uses BookStack.Uploads✕
- Connections
- 2 pairs of types, where a type in BookStack.Console.Commands uses a type in BookStack.Uploads.
- The types involved
BookStack.Console.Commands.CleanupImagesCommand→BookStack.Uploads.ImageServiceBookStack.Console.Commands.RefreshAvatarCommand→BookStack.Uploads.UserAvatars
- Direction
- BookStack.Console.Commands uses BookStack.Uploads, so a change to BookStack.Uploads can break BookStack.Console.Commands, while a change to BookStack.Console.Commands can't break BookStack.Uploads.
- Position
- Below the diagonal: BookStack.Console.Commands uses a module listed above it, which is the healthy direction.
37→20 BookStack.Console.Commands uses BookStack.Entities.Tools✕
- Connections
- 1 pair of types, where a type in BookStack.Console.Commands uses a type in BookStack.Entities.Tools.
- The types involved
BookStack.Console.Commands.CopyShelfPermissionsCommand→BookStack.Entities.Tools.PermissionsUpdater
- Direction
- BookStack.Console.Commands uses BookStack.Entities.Tools, so a change to BookStack.Entities.Tools can break BookStack.Console.Commands, while a change to BookStack.Console.Commands can't break BookStack.Entities.Tools.
- Position
- Below the diagonal: BookStack.Console.Commands uses a module listed above it, which is the healthy direction.
37→26 BookStack.Console.Commands uses BookStack.Users✕
- Connections
- 2 pairs of types, where a type in BookStack.Console.Commands uses a type in BookStack.Users.
- The types involved
BookStack.Console.Commands.CreateAdminCommand→BookStack.Users.UserRepoBookStack.Console.Commands.DeleteUsersCommand→BookStack.Users.UserRepo
- Direction
- BookStack.Console.Commands uses BookStack.Users, so a change to BookStack.Users can break BookStack.Console.Commands, while a change to BookStack.Console.Commands can't break BookStack.Users.
- Position
- Below the diagonal: BookStack.Console.Commands uses a module listed above it, which is the healthy direction.
37→29 BookStack.Console.Commands uses BookStack.Entities.Queries✕
- Connections
- 1 pair of types, where a type in BookStack.Console.Commands uses a type in BookStack.Entities.Queries.
- The types involved
BookStack.Console.Commands.CopyShelfPermissionsCommand→BookStack.Entities.Queries.BookshelfQueries
- Direction
- BookStack.Console.Commands uses BookStack.Entities.Queries, so a change to BookStack.Entities.Queries can break BookStack.Console.Commands, while a change to BookStack.Console.Commands can't break BookStack.Entities.Queries.
- Position
- Below the diagonal: BookStack.Console.Commands uses a module listed above it, which is the healthy direction.
37→35 BookStack.Console.Commands uses BookStack.Search✕
- Connections
- 1 pair of types, where a type in BookStack.Console.Commands uses a type in BookStack.Search.
- The types involved
BookStack.Console.Commands.RegenerateSearchCommand→BookStack.Search.SearchIndex
- Direction
- BookStack.Console.Commands uses BookStack.Search, so a change to BookStack.Search can break BookStack.Console.Commands, while a change to BookStack.Console.Commands can't break BookStack.Search.
- Position
- Below the diagonal: BookStack.Console.Commands uses a module listed above it, which is the healthy direction.
38→2 BookStack.Exports uses BookStack.Util✕
- Connections
- 2 pairs of types, where a type in BookStack.Exports uses a type in BookStack.Util.
- The types involved
BookStack.Exports.ExportFormatter→BookStack.Util.CspServiceBookStack.Exports.ExportFormatter→BookStack.Util.HtmlDocument
- Direction
- BookStack.Exports uses BookStack.Util, so a change to BookStack.Util can break BookStack.Exports, while a change to BookStack.Exports can't break BookStack.Util.
- Position
- Below the diagonal: BookStack.Exports uses a module listed above it, which is the healthy direction.
38→14 BookStack.Exports uses BookStack.Uploads✕
- Connections
- 2 pairs of types, where a type in BookStack.Exports uses a type in BookStack.Uploads.
- The types involved
BookStack.Exports.ExportFormatter→BookStack.Uploads.ImageServiceBookStack.Exports.ImportRepo→BookStack.Uploads.FileStorage
- Direction
- BookStack.Exports uses BookStack.Uploads, so a change to BookStack.Uploads can break BookStack.Exports, while a change to BookStack.Exports can't break BookStack.Uploads.
- Position
- Below the diagonal: BookStack.Exports uses a module listed above it, which is the healthy direction.
38→25 BookStack.Exports uses BookStack.Entities.Models✕
- Connections
- 4 pairs of types, where a type in BookStack.Exports uses a type in BookStack.Entities.Models.
- The types involved
BookStack.Exports.ExportFormatter→BookStack.Entities.Models.BookBookStack.Exports.ExportFormatter→BookStack.Entities.Models.ChapterBookStack.Exports.ExportFormatter→BookStack.Entities.Models.PageBookStack.Exports.ImportRepo→BookStack.Entities.Models.Entity
- Direction
- BookStack.Exports uses BookStack.Entities.Models, so a change to BookStack.Entities.Models can break BookStack.Exports, while a change to BookStack.Exports can't break BookStack.Entities.Models.
- Position
- Below the diagonal: BookStack.Exports uses a module listed above it, which is the healthy direction.
38→29 BookStack.Exports uses BookStack.Entities.Queries✕
- Connections
- 1 pair of types, where a type in BookStack.Exports uses a type in BookStack.Entities.Queries.
- The types involved
BookStack.Exports.ImportRepo→BookStack.Entities.Queries.EntityQueries
- Direction
- BookStack.Exports uses BookStack.Entities.Queries, so a change to BookStack.Entities.Queries can break BookStack.Exports, while a change to BookStack.Exports can't break BookStack.Entities.Queries.
- Position
- Below the diagonal: BookStack.Exports uses a module listed above it, which is the healthy direction.
38→33 BookStack.Exports uses BookStack.Activity.Models✕
- Connections
- 1 pair of types, where a type in BookStack.Exports uses a type in BookStack.Activity.Models.
- The types involved
BookStack.Exports.Import→BookStack.Activity.Models.Loggable
- Direction
- BookStack.Exports uses BookStack.Activity.Models, so a change to BookStack.Activity.Models can break BookStack.Exports, while a change to BookStack.Exports can't break BookStack.Activity.Models.
- Position
- Below the diagonal: BookStack.Exports uses a module listed above it, which is the healthy direction.
38→34 BookStack.Exports uses BookStack.Exports.ZipExports✕
- Connections
- 1 pair of types, where a type in BookStack.Exports uses a type in BookStack.Exports.ZipExports.
- The types involved
BookStack.Exports.ImportRepo→BookStack.Exports.ZipExports.ZipImportRunner
- Direction
- BookStack.Exports uses BookStack.Exports.ZipExports, so a change to BookStack.Exports.ZipExports can break BookStack.Exports, while a change to BookStack.Exports can't break BookStack.Exports.ZipExports.
- Position
- Below the diagonal: BookStack.Exports uses a module listed above it, which is the healthy direction.
39→1 BookStack.Access.Controllers uses BookStack.Http✕
- Connections
- 12 pairs of types, where a type in BookStack.Access.Controllers uses a type in BookStack.Http.
- The types involved
BookStack.Access.Controllers.ConfirmEmailController→BookStack.Http.ControllerBookStack.Access.Controllers.ForgotPasswordController→BookStack.Http.ControllerBookStack.Access.Controllers.LoginController→BookStack.Http.ControllerBookStack.Access.Controllers.MfaBackupCodesController→BookStack.Http.ControllerBookStack.Access.Controllers.MfaController→BookStack.Http.ControllerBookStack.Access.Controllers.MfaTotpController→BookStack.Http.ControllerBookStack.Access.Controllers.OidcController→BookStack.Http.ControllerBookStack.Access.Controllers.RegisterController→BookStack.Http.ControllerBookStack.Access.Controllers.ResetPasswordController→BookStack.Http.ControllerBookStack.Access.Controllers.Saml2Controller→BookStack.Http.ControllerBookStack.Access.Controllers.SocialController→BookStack.Http.ControllerBookStack.Access.Controllers.UserInviteController→BookStack.Http.Controller
- Direction
- BookStack.Access.Controllers uses BookStack.Http, so a change to BookStack.Http can break BookStack.Access.Controllers, while a change to BookStack.Access.Controllers can't break BookStack.Http.
- Position
- Below the diagonal: BookStack.Access.Controllers uses a module listed above it, which is the healthy direction.
39→7 BookStack.Access.Controllers uses BookStack.Users.Models✕
- Connections
- 1 pair of types, where a type in BookStack.Access.Controllers uses a type in BookStack.Users.Models.
- The types involved
BookStack.Access.Controllers.HandlesPartialLogins→BookStack.Users.Models.User
- Direction
- BookStack.Access.Controllers uses BookStack.Users.Models, so a change to BookStack.Users.Models can break BookStack.Access.Controllers, while a change to BookStack.Access.Controllers can't break BookStack.Users.Models.
- Position
- Below the diagonal: BookStack.Access.Controllers uses a module listed above it, which is the healthy direction.
39→26 BookStack.Access.Controllers uses BookStack.Users✕
- Connections
- 2 pairs of types, where a type in BookStack.Access.Controllers uses a type in BookStack.Users.
- The types involved
BookStack.Access.Controllers.ConfirmEmailController→BookStack.Users.UserRepoBookStack.Access.Controllers.UserInviteController→BookStack.Users.UserRepo
- Direction
- BookStack.Access.Controllers uses BookStack.Users, so a change to BookStack.Users can break BookStack.Access.Controllers, while a change to BookStack.Access.Controllers can't break BookStack.Users.
- Position
- Below the diagonal: BookStack.Access.Controllers uses a module listed above it, which is the healthy direction.
39→36 BookStack.Access.Controllers uses BookStack.Access✕
- Connections
- 15 pairs of types, where a type in BookStack.Access.Controllers uses a type in BookStack.Access.
- The types involved
BookStack.Access.Controllers.ConfirmEmailController→BookStack.Access.EmailConfirmationServiceBookStack.Access.Controllers.ConfirmEmailController→BookStack.Access.LoginServiceBookStack.Access.Controllers.LoginController→BookStack.Access.LoginServiceBookStack.Access.Controllers.LoginController→BookStack.Access.SocialDriverManagerBookStack.Access.Controllers.MfaBackupCodesController→BookStack.Access.LoginServiceBookStack.Access.Controllers.MfaTotpController→BookStack.Access.LoginServiceBookStack.Access.Controllers.RegisterController→BookStack.Access.LoginServiceBookStack.Access.Controllers.RegisterController→BookStack.Access.RegistrationServiceBookStack.Access.Controllers.RegisterController→BookStack.Access.SocialDriverManagerBookStack.Access.Controllers.ResetPasswordController→BookStack.Access.LoginServiceBookStack.Access.Controllers.Saml2Controller→BookStack.Access.Saml2ServiceBookStack.Access.Controllers.SocialController→BookStack.Access.LoginServiceBookStack.Access.Controllers.SocialController→BookStack.Access.RegistrationServiceBookStack.Access.Controllers.SocialController→BookStack.Access.SocialAuthServiceBookStack.Access.Controllers.UserInviteController→BookStack.Access.UserInviteService
- Direction
- BookStack.Access.Controllers uses BookStack.Access, so a change to BookStack.Access can break BookStack.Access.Controllers, while a change to BookStack.Access.Controllers can't break BookStack.Access.
- Position
- Below the diagonal: BookStack.Access.Controllers uses a module listed above it, which is the healthy direction.
40→1 BookStack.Users.Controllers uses BookStack.Http✕
- Connections
- 8 pairs of types, where a type in BookStack.Users.Controllers uses a type in BookStack.Http.
- The types involved
BookStack.Users.Controllers.RoleApiController→BookStack.Http.ApiControllerBookStack.Users.Controllers.RoleController→BookStack.Http.ControllerBookStack.Users.Controllers.UserAccountController→BookStack.Http.ControllerBookStack.Users.Controllers.UserApiController→BookStack.Http.ApiControllerBookStack.Users.Controllers.UserController→BookStack.Http.ControllerBookStack.Users.Controllers.UserPreferencesController→BookStack.Http.ControllerBookStack.Users.Controllers.UserProfileController→BookStack.Http.ControllerBookStack.Users.Controllers.UserSearchController→BookStack.Http.Controller
- Direction
- BookStack.Users.Controllers uses BookStack.Http, so a change to BookStack.Http can break BookStack.Users.Controllers, while a change to BookStack.Users.Controllers can't break BookStack.Http.
- Position
- Below the diagonal: BookStack.Users.Controllers uses a module listed above it, which is the healthy direction.
40→7 BookStack.Users.Controllers uses BookStack.Users.Models✕
- Connections
- 2 pairs of types, where a type in BookStack.Users.Controllers uses a type in BookStack.Users.Models.
- The types involved
BookStack.Users.Controllers.RoleApiController→BookStack.Users.Models.RoleBookStack.Users.Controllers.UserApiController→BookStack.Users.Models.User
- Direction
- BookStack.Users.Controllers uses BookStack.Users.Models, so a change to BookStack.Users.Models can break BookStack.Users.Controllers, while a change to BookStack.Users.Controllers can't break BookStack.Users.Models.
- Position
- Below the diagonal: BookStack.Users.Controllers uses a module listed above it, which is the healthy direction.
40→10 BookStack.Users.Controllers uses BookStack.Permissions✕
- Connections
- 3 pairs of types, where a type in BookStack.Users.Controllers uses a type in BookStack.Permissions.
- The types involved
BookStack.Users.Controllers.RoleApiController→BookStack.Permissions.PermissionsRepoBookStack.Users.Controllers.RoleController→BookStack.Permissions.PermissionsRepoBookStack.Users.Controllers.UserAccountController→BookStack.Permissions.PermissionApplicator
- Direction
- BookStack.Users.Controllers uses BookStack.Permissions, so a change to BookStack.Permissions can break BookStack.Users.Controllers, while a change to BookStack.Users.Controllers can't break BookStack.Permissions.
- Position
- Below the diagonal: BookStack.Users.Controllers uses a module listed above it, which is the healthy direction.
40→12 BookStack.Users.Controllers uses BookStack.Activity✕
- Connections
- 1 pair of types, where a type in BookStack.Users.Controllers uses a type in BookStack.Activity.
- The types involved
BookStack.Users.Controllers.UserProfileController→BookStack.Activity.ActivityQueries
- Direction
- BookStack.Users.Controllers uses BookStack.Activity, so a change to BookStack.Activity can break BookStack.Users.Controllers, while a change to BookStack.Users.Controllers can't break BookStack.Activity.
- Position
- Below the diagonal: BookStack.Users.Controllers uses a module listed above it, which is the healthy direction.
40→14 BookStack.Users.Controllers uses BookStack.Uploads✕
- Connections
- 2 pairs of types, where a type in BookStack.Users.Controllers uses a type in BookStack.Uploads.
- The types involved
BookStack.Users.Controllers.UserAccountController→BookStack.Uploads.ImageRepoBookStack.Users.Controllers.UserController→BookStack.Uploads.ImageRepo
- Direction
- BookStack.Users.Controllers uses BookStack.Uploads, so a change to BookStack.Uploads can break BookStack.Users.Controllers, while a change to BookStack.Users.Controllers can't break BookStack.Uploads.
- Position
- Below the diagonal: BookStack.Users.Controllers uses a module listed above it, which is the healthy direction.
40→26 BookStack.Users.Controllers uses BookStack.Users✕
- Connections
- 5 pairs of types, where a type in BookStack.Users.Controllers uses a type in BookStack.Users.
- The types involved
BookStack.Users.Controllers.UserAccountController→BookStack.Users.UserRepoBookStack.Users.Controllers.UserApiController→BookStack.Users.UserRepoBookStack.Users.Controllers.UserController→BookStack.Users.UserRepoBookStack.Users.Controllers.UserPreferencesController→BookStack.Users.UserRepoBookStack.Users.Controllers.UserProfileController→BookStack.Users.UserRepo
- Direction
- BookStack.Users.Controllers uses BookStack.Users, so a change to BookStack.Users can break BookStack.Users.Controllers, while a change to BookStack.Users.Controllers can't break BookStack.Users.
- Position
- Below the diagonal: BookStack.Users.Controllers uses a module listed above it, which is the healthy direction.
40→36 BookStack.Users.Controllers uses BookStack.Access✕
- Connections
- 2 pairs of types, where a type in BookStack.Users.Controllers uses a type in BookStack.Access.
- The types involved
BookStack.Users.Controllers.UserAccountController→BookStack.Access.SocialDriverManagerBookStack.Users.Controllers.UserController→BookStack.Access.SocialDriverManager
- Direction
- BookStack.Users.Controllers uses BookStack.Access, so a change to BookStack.Access can break BookStack.Users.Controllers, while a change to BookStack.Users.Controllers can't break BookStack.Access.
- Position
- Below the diagonal: BookStack.Users.Controllers 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 — Domain Modelling
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 21 | High / Critical |
| A02:2025 — Security Misconfiguration | 10 | High / Critical |
| A07:2025 — Authentication Failures | 6 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
Roadmap
Top priorities: Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED; Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery; Resolve the 1 Banned license finding(s) in License Compliance.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED. | +4.4 pts | Low | REDACTED Scanning |
| Resolve the 1 Banned license finding(s) in License Compliance. | +2.6 pts | Low | License Compliance |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +3.3 pts | Medium | DR & Backup |
| Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate. | +2.2 pts | Medium | Security & performance tooling |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.6 pts | Medium | Release Hygiene |
| 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. | +1.5 pts | Medium | Nullable reference types |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +0.7 pts | Low | ADR Quality |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +1.1 pts | Medium | Visual & motion safety |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| app/Entities/Controllers/BookController.php | 2.5 | Slop | Change Coupling: Boundary-crossing change coupling: BookController.php ↔ edit.blade.php |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.5 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.4 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| app/Entities/Controllers/BookApiController.php | 5.9 | Mixed | Code Duplication: Duplicated block (9 lines × 2) |
| app/Entities/Controllers/ChapterController.php | 6.3 | Mixed | Code Duplication: Duplicated block (9 lines × 2) |
| app/Entities/Repos/PageRepo.php | 7.0 | Mixed | Cyclomatic Complexity: PageRepo.updateTemplateStatusAndContentFromInput (cyclomatic 17) |
| app/Search/SearchRunner.php | 7.0 | Mixed | Code Duplication: Duplicated block (5 lines × 3) |
| app/Activity/ActivityType.php | 7.0 | Mixed | Change Coupling: Boundary-crossing change coupling: ActivityType.php ↔ activities.php |
| app/Util/HtmlPurifier/SrcsetAttrDef.php | 7.2 | Mixed | Cyclomatic Complexity: SrcsetAttrDef.formatDescriptor (cyclomatic 25) |
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 86 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 86 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, 506 of 530 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 2 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 53 test source file(s) (.ts) that it cannot: it reads the test types the .php frontend declared, so a suite in any other language is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the jest run in the repository root produced no per-test report (Error: Jest: Failed to parse the TypeScript config file jest.config.ts). This is OUR limitation, not a defect in the repo — it is excluded from the score.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in the repository root was NOT MEASURED: the jest run in the repository root produced no per-test report (Error: Jest: Failed to parse the TypeScript config file jest.config.ts). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its Composer package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- 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 (237 contributor(s) across 5637 commit(s) sampled, automation and bot accounts excluded). One of them holds 84% of the history; the other 236 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.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — 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. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- 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)` (53423 LoC, 919 module-visible types across 100 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.
- 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. `app/Access/Guards/ExternalBaseSessionGuard.php`, `app/App/helpers.php`, `app/Entities/Controllers/RecycleBinApiController.php`, `app/Entities/Repos/BaseRepo.php`, `app/Entities/Tools/SlugGenerator.php`, … (+15 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.
- AC2 Forms & labels — 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. 3 further occurrence(s) are not listed individually; the score already reflects all 43.
- 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, 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.
- AX6 Interface segregation — 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.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c docker-php-ext-configure ldap --with-libdir=\"lib/$(gcc -dumpmachine)\" && docker-php-ext-configure gd --with-freetype --with-jpeg && docker-php-ext-install -j$(nproc) pdo_mysql gd ldap zip && pecl install xdebug && docker-php-ext-enable xdebug" did not complete successfully: exit code: 1; runtime evidence skipped.
- DM8 Value-object opportunities — 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 finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and 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 and Scala 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 54 further occurrence(s) are not listed individually; the score already reflects all 94.
- R7 Dead Code — 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. 41 further occurrence(s) are not listed individually; the score already reflects all 81.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's PHP 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.
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.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (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.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
10 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was BookSorter.isSortChangePermissible at 28.
What to do
- Bring the 9 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with BookSorter.isSortChangePermissible (cyclomatic 28), SrcsetAttrDef.formatDescriptor (cyclomatic 25), SrcsetAttrDef.parseImageSources (cyclomatic 23). — 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 9 together lifts Cyclomatic Complexity from 8.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
14 method(s) exceeded the cognitive complexity threshold of 15; the worst was SrcsetAttrDef.parseImageSources at 111.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with SrcsetAttrDef.parseImageSources (cognitive 111). — Refactoring it lifts Cognitive Complexity from 6.8 to about 7.4/10.
D3 · God Classes
2 god class(es) detected.
What to do
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with Entity.php, actions.ts. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
33 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 5 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with EntityWatchers.php, HomeController.php, Favourite.php. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with BookApiController.php, ChapterController.php, PageContent.php. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with PageController.php, BookApiController.php, BooksIndexNew.php. — One of this dimension's main actionable groups (4 warning-level).
D6 · Cohesion (LCOM4)
6 of 189 classes have LCOM4 above 3.
What to do
- Resolve the 6 Low cohesion finding(s) in Cohesion (LCOM4) — start with User.php, SearchRunner.php, ConfiguredHtmlPurifier.php. — One of this dimension's main actionable groups (6 warning-level).
D9 · Test Distribution
503 test methods: 503 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 501 `it`/`test` case(s) across 50 test file(s) declaring at least one beside 2 .NET test method(s); its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 2 tests. Measured on the .php suite only — at least 53 test source file(s) (.ts) went unread, so its test quality is unmeasured and is not in these counts.
D12 · Dependency Hygiene
6 outdated, 0 abandoned direct Composer dependencies. PLATFORM requirements (php, ext-*, lib-*) are deliberately not graded here: they name the runtime rather than a Packagist package, so there is no release for them to be behind — whether that runtime is still supported is a separate question with a separate remedy. Development requirements are excluded, because a consumer never installs them. A newer release is reported only where this repository's OWN constraint already admits it, so the remedy is `composer update` and never a manifest edit. Known CVEs in this dependency graph are D30's question.
D13 · REDACTED Scanning
4 secret(s) detected.
What to do
- Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
D14 · License Compliance
1 of 113 locked Composer package(s) use a banned license. Licences were read from this repository's composer.lock, which records the `license` each package declares, over every package in its production `packages` list, direct and transitive, at the locked version; the 36 package(s) under `packages-dev` are not installed for a consumer and are excluded. ★ COVERAGE OF THIS VERDICT: it grades this repository's Composer package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
2 deducted task-comment markers across 186505 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 PageRevisionController.php (2). — One of this dimension's main actionable groups (2 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 16 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
132 domain type(s) cross context boundaries across 12 contexts; they are measured and withheld (not published, not scored). Contexts: Access, Activity, Api, Entities, Exports, Permissions, References, Search, Settings, Sorting, Uploads, Users.
D24 · Comment Value
17 of 745 judged comments only repeat the code they sit on (2.3 %). 10 comment(s) in another language or script were not judged.
What to do
- Resolve the 17 redundant comment finding(s) in Comment Value — start with shortcuts.ts (4), image-manager.js (3), pointer.ts (2). — One of this dimension's main actionable groups (17 recommendation-level).
D27 · Navigability
39 % of calls cross a namespace and 1 % go through an interface, but 61 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
21 finding(s): 0 critical, 21 high, 0 medium, 0 low. 20 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 20 file(s) — `app/Access/Guards/ExternalBaseSessionGuard.php` (line 28), `app/App/helpers.php` (line 44), `app/Entities/Controllers/RecycleBinApiController.php` (line 44, line 84, line 86), `app/Entities/Repos/BaseRepo.php` (line 116), `app/Entities/Tools/SlugGenerator.php` (line 18, line 65), … (+15 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).
- No action in Static Analysis (SAST) — all 20 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 (20 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
5 finding(s): 0 critical, 0 high, 4 medium, 1 low.
What to do
- Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D31 · IaC & Container Security
10 finding(s): 0 critical, 3 high, 7 medium, 0 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 7 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (7 warning-level).
D34 · Knowledge Freshness
1 of 351 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is resources/js/components/index.ts. Counted over 351 of the 1110 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: OidcService.php↔oidc.php 87%; ChapterRepo.php↔PageRepo.php 81%; common.php↔common.php 80%
What to do
- Resolve the 7 Boundary-crossing change coupling finding(s) in Change Coupling — start with BookController.php (2), ActivityType.php (2), OidcService.php. — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 13 Change coupling finding(s) in Change Coupling — start with BookController.php (2), ChapterRepo.php, create.blade.php. — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with common.php. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (.forgejo/SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 46 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×5) — resources/views/misc/opensearch.blade.php:5, resources/views/misc/opensearch.blade.php:6, resources/views/misc/opensearch.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
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×7) — resources/views/api-docs/index.blade.php:13, resources/views/form/role-select.blade.php:2, resources/views/search/all.blade.php:16, …
- 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. (×26) — resources/views/books/parts/form.blade.php:14, resources/views/exports/import-show.blade.php:12, resources/views/exports/import-show.blade.php:22, …
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×7) — resources/views/mfa/parts/verify-backup_codes.blade.php:7, resources/views/mfa/parts/verify-totp.blade.php:7, resources/views/pages/parts/template-manager.blade.php:15, …
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>. (×5) — resources/views/api-docs/download.blade.php:2, resources/views/errors/debug.blade.php:2, resources/views/layouts/base.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. (×2) — resources/views/api-docs/download.blade.php:5, resources/views/errors/debug.blade.php:5
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×9) — REDACTED:28, resources/views/errors/500.blade.php:10, resources/views/errors/debug.blade.php:110, …
- A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×2) — REDACTED:172, resources/views/search/parts/date-filter.blade.php:5
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.
AC5 · ARIA correctness
- A plain <div> has the implicit role "generic", which supports no ARIA states, so this aria-expanded is dropped and assistive tech is never told the state at all. Put aria-expanded on the element that owns the behaviour (the button or control the user operates), or give this <div> a role that supports aria-expanded. — resources/views/form/user-select.blade.php:5
What to do
- Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
AC6 · Visual & motion safety
- `&:active` sets color: #666 on background-color: #DDD — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×3) — resources/sass/_buttons.scss:64, resources/sass/_editor.scss:620, resources/sass/_forms.scss:589
- `.cm-copy-button:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — resources/sass/_codemirror.scss:68
- `.popup-body:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — resources/sass/_components.scss:143
- `.tab-container [role="tablist"] button[role="tab"][aria-selected="true"]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — resources/sass/_components.scss:556
- `.tab-container [role="tabpanel"].no-outline:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — resources/sass/_components.scss:573
- `.editor-content-area:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — resources/sass/_editor.scss:45
- `#markdown-editor #markdown-editor-input:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — resources/sass/_forms.scss:70
- `.page-content.mce-content-body` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — resources/sass/_tinymce.scss:25
- `.wysiwyg-input.mce-content-body` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — resources/sass/_tinymce.scss:33
- `.search-suggestions-animation` moves (`animation-name: searchSuggestions`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — resources/sass/_animations.scss:20
- `.anim.pointer` moves (`animation-name: pointer`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — resources/sass/_animations.scss:66
- `.notification` moves (`transition: transform ease-in-out 280ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — resources/sass/_components.scss:22
- `.dropzone-overlay` moves (`animation: dzAnimIn 240ms ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — resources/sass/_components.scss:229
- `.dropzone-file-item` moves (`animation: dzFileItemIn ease-in-out 240ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — resources/sass/_components.scss:288
- `.dropzone-file-item` moves (`transition: transform ease-in-out 120ms, box-shadow ease-in-out 120ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — resources/sass/_components.scss:289
- `.dropzone-file-item.dismiss` moves (`animation: dzFileItemOut ease-in-out 240ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — resources/sass/_components.scss:297
- `.dropzone-file-item-progress` moves (`transition: width ease-in-out 240ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — resources/sass/_components.scss:327
- `.tri-layout-container .tri-layout-middle` moves (`transition: transform ease-in-out 240ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — resources/sass/_layout.scss:505
- `details.sort-box summary .caret-container svg` moves (`transition: transform ease-in-out 120ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — resources/sass/_lists.scss:332
- `.draft-notification` moves (`transition: transform ease-in-out 120ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — resources/sass/_pages.scss:137
- `.content-comment-marker` moves (`transition: transform ease-in-out 120ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — resources/sass/_pages.scss:301
- `.floating-toolbox .toolbox-toggle svg` moves (`transition: transform ease-in-out 180ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — resources/sass/_pages.scss:334
- `.loading-container > div` moves (`animation-name: loadingBob`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — resources/sass/styles.scss:83
- `.list-sort-container .list-sort-dir .svg-icon` moves (`transition: transform ease-in-out 120ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — resources/sass/styles.scss:251
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have) and no axe/pa11y/Lighthouse in tests or CI. Start by running that check over your rendered pages in CI. What was searched, so you can tell an absence from a miss: the 308 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — package.json:21
What to do
- Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, then assert with jest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
C1 · Data Protection
- No in-app HTTPS enforcement, but trusted proxies are configured (TrustProxies $proxies / trustProxies(at: …) / setTrustedProxies) — a reverse-proxy topology, where forcing HTTPS in the app would be wrong. Verify the reverse proxy enforces TLS. — app/Http/Middleware/TrustProxies.php:39
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.
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.
C3 · Audit Trail
- An audit mechanism is present, but the trail is not yet complete — missing: a write-side hook every change flows through (a change-history library's model trait, an Eloquent model event or observer, or a Doctrine lifecycle listener recording each change), per-model coverage (LogsActivity / Auditable / RevisionableTrait or #[Gedmo\Loggable] on each model that needs a who-changed-what trail).
What to do
- Back the audit convention with a structural mechanism: a change-history library on each model that needs a who-changed-what trail (spatie/laravel-activitylog's LogsActivity, owen-it/laravel-auditing's Auditable) or an Eloquent observer / Doctrine listener writing each sensitive change to an audit-log table, with the acting user and time on every entry.
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM4 · Rich vs anemic model
- `SocialAccount` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Access/SocialAccount.php:15
- `Comment` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Activity/Models/Comment.php:30
- `Favourite` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Activity/Models/Favourite.php:11
- `MentionHistory` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Activity/Models/MentionHistory.php:17
- `Tag` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Activity/Models/Tag.php:19
- `Watch` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Activity/Models/Watch.php:22
- `Webhook` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Activity/Models/Webhook.php:23
- `WebhookTrackedEvent` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Activity/Models/WebhookTrackedEvent.php:13
- `ApiToken` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Api/ApiToken.php:22
- `Book` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Entities/Models/Book.php:29
- `Bookshelf` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Entities/Models/Bookshelf.php:15
- `Chapter` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Entities/Models/Chapter.php:16
- `Deletion` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Entities/Models/Deletion.php:19
- `EntityContainerData` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Entities/Models/EntityContainerData.php:17
- `EntityPageData` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Entities/Models/EntityPageData.php:10
- `EntityTable` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Entities/Models/EntityTable.php:19
- `Page` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Entities/Models/Page.php:31
- `PageRevision` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Entities/Models/PageRevision.php:31
- `PageUpdateDraft` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Entities/Models/PageUpdateDraft.php:25
- `SlugHistory` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Entities/Models/SlugHistory.php:17
- `Import` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Exports/Import.php:27
- `EntityPermission` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Permissions/Models/EntityPermission.php:19
- `JointPermission` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Permissions/Models/JointPermission.php:11
- `Reference` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/References/Reference.php:16
- `SearchTerm` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Search/SearchTerm.php:7
- `Setting` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Settings/Setting.php:7
- `Attachment` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Uploads/Attachment.php:32
- `Image` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Uploads/Image.php:25
- `Role` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Users/Models/Role.php:26
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
- `Book` exposes publicly writable state (searchFactor). — app/Entities/Models/Book.php:29
- `Bookshelf` exposes publicly writable state (searchFactor). — app/Entities/Models/Bookshelf.php:15
- `Chapter` exposes publicly writable state (searchFactor). — app/Entities/Models/Chapter.php:16
- `Entity` exposes publicly writable state (textField, htmlField, searchFactor, commonFields). — app/Entities/Models/Entity.php:55
- `EntityContainerData` exposes publicly writable state (timestamps, incrementing, fields). — app/Entities/Models/EntityContainerData.php:17
- `EntityPageData` exposes publicly writable state (timestamps, incrementing, fields). — app/Entities/Models/EntityPageData.php:10
- `Page` exposes publicly writable state (textField, htmlField). — app/Entities/Models/Page.php:31
- `EntityPermission` exposes publicly writable state (timestamps). — app/Permissions/Models/EntityPermission.php:19
- `JointPermission` exposes publicly writable state (timestamps). — app/Permissions/Models/JointPermission.php:11
- `Reference` exposes publicly writable state (timestamps). — app/References/Reference.php:16
- `SearchTerm` exposes publicly writable state (timestamps). — app/Search/SearchTerm.php:7
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM9 · Scattered domain decisions
- resources.js.wysiwyg.lexical.core.LexicalSelection.RangeSelection's [anchor, focus] are judged in resources.js.wysiwyg.lexical.core.LexicalEvents, resources.js.wysiwyg.lexical.core.LexicalNode.LexicalNode, resources.js.wysiwyg.lexical.core.LexicalUtils, resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode.TextNode — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
- resources.js.wysiwyg.lexical.core.LexicalSelection.RangeSelection's [format, style] are judged in resources.js.wysiwyg.lexical.core.LexicalEvents, resources.js.wysiwyg.lexical.core.LexicalSelection — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
What to do
- Move each repeated judgement onto the type that owns the members it reads, so the rule has one home and cannot drift.
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (opentelemetry-php) and a health-check endpoint (Laravel's /up health route or a /health route) for operability.
P3 · Security & performance tooling
- `REDACTED` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.
- `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:21
What to do
- Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
P8 · Schema migrations
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- 24 duplicated blocks under resources/js/wysiwyg/lexical/ have copies in at least two of the sibling directories clipboard, core, html, link, list, rich-text (+4 more sibling(s) not listed) — 18 of them are reported below, and 6 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 24 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 24 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 24 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — resources/js/wysiwyg/lexical/core/nodes/LexicalParagraphNode.ts:118
- resources/js/wysiwyg/lexical/rich-text/LexicalCodeBlockNode.ts:31 · resources/js/wysiwyg/lexical/rich-text/LexicalDiagramNode.ts:22 — the two spans are one implementation copied and then locally edited — 497 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/wysiwyg/lexical/rich-text/LexicalCodeBlockNode.ts:31
- resources/js/wysiwyg/ui/defaults/buttons/tables.ts:177 · resources/js/wysiwyg/ui/defaults/buttons/tables.ts:263 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — resources/js/wysiwyg/ui/defaults/buttons/tables.ts:177
- resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts:60 · resources/js/wysiwyg/lexical/yjs/CollabTextNode.ts:65 — the two spans are one implementation copied and then locally edited — 194 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/wysiwyg/lexical/yjs/CollabElementNode.ts:60
- resources/js/wysiwyg/utils/table-copy-paste.ts:26 · resources/js/wysiwyg/utils/table-copy-paste.ts:159 — the two spans are one implementation copied and then locally edited — 162 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — resources/js/wysiwyg/utils/table-copy-paste.ts:26
- resources/js/wysiwyg/ui/defaults/forms/tables.ts:78 · resources/js/wysiwyg/ui/defaults/forms/tables.ts:183 — the two spans are one implementation copied and then locally edited — 271 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — resources/js/wysiwyg/ui/defaults/forms/tables.ts:78
- resources/js/wysiwyg/lexical/core/nodes/LexicalParagraphNode.ts:118 · resources/js/wysiwyg/lexical/rich-text/LexicalQuoteNode.ts:50 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — resources/js/wysiwyg/lexical/core/nodes/LexicalParagraphNode.ts:118
- resources/js/wysiwyg/lexical/rich-text/index.ts:340 · resources/js/wysiwyg/lexical/rich-text/index.ts:373 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — resources/js/wysiwyg/lexical/rich-text/index.ts:340
- resources/js/wysiwyg/lexical/clipboard/clipboard.ts:240 · resources/js/wysiwyg/lexical/core/LexicalEditorState.ts:58 — the two spans are one implementation copied and then locally edited — 90 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/wysiwyg/lexical/clipboard/clipboard.ts:240
- resources/js/wysiwyg/lexical/core/LexicalUtils.ts:1657 · resources/js/wysiwyg/lexical/selection/range-selection.ts:575 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — resources/js/wysiwyg/lexical/core/LexicalUtils.ts:1657
- resources/js/wysiwyg/lexical/table/LexicalTableUtils.ts:266 · resources/js/wysiwyg/lexical/table/LexicalTableUtils.ts:293 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — resources/js/wysiwyg/lexical/table/LexicalTableUtils.ts:266
- resources/js/wysiwyg/index.ts:105 · resources/js/wysiwyg/index.ts:139 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — resources/js/wysiwyg/index.ts:105
- resources/js/wysiwyg/lexical/core/LexicalUtils.ts:321 · resources/js/wysiwyg/lexical/core/LexicalUtils.ts:340 · resources/js/wysiwyg/lexical/yjs/Utils.ts:485 · resources/js/wysiwyg/lexical/yjs/Utils.ts:504 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — resources/js/wysiwyg/lexical/core/LexicalUtils.ts:321
- resources/js/wysiwyg/lexical/core/nodes/CommonBlockNode.ts:23 · resources/js/wysiwyg/lexical/rich-text/LexicalCalloutNode.ts:64 · resources/js/wysiwyg/lexical/rich-text/LexicalMediaNode.ts:183 — the 3 copies are spread across 3 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — resources/js/wysiwyg/lexical/core/nodes/CommonBlockNode.ts:23
- resources/js/wysiwyg/lexical/table/LexicalTableUtils.ts:498 · resources/js/wysiwyg/lexical/table/LexicalTableUtils.ts:574 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — resources/js/wysiwyg/lexical/table/LexicalTableUtils.ts:498
- resources/js/wysiwyg/lexical/clipboard/clipboard.ts:271 · resources/js/wysiwyg/lexical/html/index.ts:115 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — resources/js/wysiwyg/lexical/clipboard/clipboard.ts:271
- resources/js/wysiwyg/lexical/core/LexicalUtils.ts:933 · resources/js/wysiwyg/lexical/core/LexicalUtils.ts:952 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — resources/js/wysiwyg/lexical/core/LexicalUtils.ts:933
- resources/js/wysiwyg/lexical/core/nodes/LexicalElementNode.ts:261 · resources/js/wysiwyg/lexical/core/nodes/LexicalElementNode.ts:278 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — resources/js/wysiwyg/lexical/core/nodes/LexicalElementNode.ts:261
- resources/js/wysiwyg/lexical/rich-text/index.ts:264 · resources/js/wysiwyg/lexical/rich-text/index.ts:300 · resources/js/wysiwyg/lexical/rich-text/index.ts:503 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — resources/js/wysiwyg/lexical/rich-text/index.ts:264
- resources/js/wysiwyg-tinymce/plugin-codeeditor.js:247 · resources/js/wysiwyg-tinymce/plugins-details.js:249 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — resources/js/wysiwyg-tinymce/plugin-codeeditor.js:247
- resources/js/wysiwyg/lexical/core/LexicalNormalization.ts:48 · resources/js/wysiwyg/lexical/core/LexicalNormalization.ts:67 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — resources/js/wysiwyg/lexical/core/LexicalNormalization.ts:48
- resources/js/components/book-sort.js:80 · resources/js/components/book-sort.js:95 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — resources/js/components/book-sort.js:80
- resources/js/wysiwyg/lexical/core/LexicalUtils.ts:888 · resources/js/wysiwyg/lexical/core/LexicalUtils.ts:904 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — resources/js/wysiwyg/lexical/core/LexicalUtils.ts:888
- resources/js/wysiwyg/lexical/rich-text/index.ts:320 · resources/js/wysiwyg/lexical/rich-text/index.ts:412 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — resources/js/wysiwyg/lexical/rich-text/index.ts:320
- resources/js/wysiwyg/lexical/rich-text/index.ts:442 · resources/js/wysiwyg/lexical/rich-text/index.ts:458 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — resources/js/wysiwyg/lexical/rich-text/index.ts:442
- resources/js/wysiwyg/lexical/yjs/SyncCursors.ts:312 · resources/js/wysiwyg/lexical/yjs/SyncCursors.ts:426 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — resources/js/wysiwyg/lexical/yjs/SyncCursors.ts:312
- resources/js/wysiwyg/ui/defaults/buttons/controls.ts:19 · resources/js/wysiwyg/ui/defaults/buttons/controls.ts:39 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — resources/js/wysiwyg/ui/defaults/buttons/controls.ts:19
- resources/js/wysiwyg/lexical/core/LexicalSelection.ts:2444 · resources/js/wysiwyg/lexical/core/LexicalSelection.ts:2458 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — resources/js/wysiwyg/lexical/core/LexicalSelection.ts:2444
- resources/js/wysiwyg/lexical/core/LexicalUtils.ts:350 · resources/js/wysiwyg/lexical/yjs/Utils.ts:514 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — resources/js/wysiwyg/lexical/core/LexicalUtils.ts:350
- resources/js/wysiwyg/lexical/core/nodes/CommonBlockNode.ts:17 · resources/js/wysiwyg/lexical/rich-text/LexicalCalloutNode.ts:48 · resources/js/wysiwyg/lexical/rich-text/LexicalCalloutNode.ts:68 · resources/js/wysiwyg/lexical/rich-text/LexicalCodeBlockNode.ts:61 · +3 more site(s) not listed — the 6 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — resources/js/wysiwyg/lexical/core/nodes/CommonBlockNode.ts:17
- resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts:180 · resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts:197 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts:180
- resources/js/wysiwyg/lexical/utils/index.ts:192 · resources/js/wysiwyg/lexical/utils/index.ts:243 — the two spans are one implementation copied and then locally edited — 73 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — resources/js/wysiwyg/lexical/utils/index.ts:192
- resources/js/services/dom.ts:21 · resources/js/wysiwyg/utils/dom.ts:6 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — resources/js/services/dom.ts:21
- resources/js/wysiwyg/lexical/core/LexicalReconciler.ts:611 · resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts:463 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — resources/js/wysiwyg/lexical/core/LexicalReconciler.ts:611
- resources/js/wysiwyg/lexical/core/LexicalSelection.ts:2388 · resources/js/wysiwyg/lexical/core/LexicalSelection.ts:2401 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — resources/js/wysiwyg/lexical/core/LexicalSelection.ts:2388
- resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts:1610 · resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts:1636 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts:1610
- resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts:540 · resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts:592 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts:540
- resources/js/wysiwyg/ui/defaults/buttons/tables.ts:67 · resources/js/wysiwyg/ui/defaults/buttons/tables.ts:87 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — resources/js/wysiwyg/ui/defaults/buttons/tables.ts:67
- resources/js/wysiwyg/utils/table-copy-paste.ts:77 · resources/js/wysiwyg/utils/table-copy-paste.ts:91 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — resources/js/wysiwyg/utils/table-copy-paste.ts:77
- resources/js/components/shelf-sort.js:21 · resources/js/components/sort-rule-manager.ts:24 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — resources/js/components/shelf-sort.js:21
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/services/vdom.ts:7 imports snabbdom/build/vnode, 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/services/vdom.ts:7
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
- insertText has cyclomatic complexity 92 and cognitive complexity 158; 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/wysiwyg/lexical/core/LexicalSelection.ts:717
- $handleArrowKey has cyclomatic complexity 62 and cognitive complexity 146; 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/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts:1267
- (anonymous) has cyclomatic complexity 56 and cognitive complexity 45; 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/wysiwyg/lexical/core/LexicalEvents.ts:542
- updateDOMSelection has cyclomatic complexity 47 and cognitive complexity 52; 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/wysiwyg/lexical/core/LexicalSelection.ts:2558
- (anonymous) has cyclomatic complexity 45 and cognitive complexity 97; 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/wysiwyg/lexical/core/LexicalMutations.ts:111
- $patchStyleText has cyclomatic complexity 44 and cognitive complexity 75; 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/wysiwyg/lexical/selection/lexical-node.ts:279
- deleteCharacter has cyclomatic complexity 41 and cognitive complexity 58; 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/wysiwyg/lexical/core/LexicalSelection.ts:1594
- (anonymous) has cyclomatic complexity 41 and cognitive complexity 58; 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/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts:675
- $wrapNodesImpl has cyclomatic complexity 36 and cognitive complexity 76; 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/wysiwyg/lexical/selection/range-selection.ts:200
- onKeyDown has cyclomatic complexity 34 and cognitive complexity 41; 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/wysiwyg/lexical/core/LexicalEvents.ts:992
- createEditor has cyclomatic complexity 33 and cognitive complexity 68; 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/wysiwyg/lexical/core/LexicalEditor.ts:420
- $commitPendingUpdates has cyclomatic complexity 33 and cognitive complexity 45; 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/wysiwyg/lexical/core/LexicalUpdates.ts:477
- $updateTextNodeFromDOMContent has cyclomatic complexity 33 and cognitive complexity 39; 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/wysiwyg/lexical/core/LexicalUtils.ts:642
- (anonymous) has cyclomatic complexity 33 and cognitive complexity 26; 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/wysiwyg/lexical/selection/__tests__/utils/index.ts:655
- modify has cyclomatic complexity 32 and cognitive complexity 74; 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/wysiwyg/lexical/core/LexicalSelection.ts:1413
- (anonymous) has cyclomatic complexity 32 and cognitive complexity 62; 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/wysiwyg/lexical/core/LexicalEvents.ts:291
- $trimTextContentFromAnchor has cyclomatic complexity 31 and cognitive complexity 71; 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/wysiwyg/lexical/selection/lexical-node.ts:113
- modify has cyclomatic complexity 30 and cognitive complexity 74; 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/wysiwyg/lexical/selection/__tests__/utils/index.ts:89
- getChangeType has cyclomatic complexity 30 and cognitive complexity 22; 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/wysiwyg/lexical/history/index.ts:80
- formatText has cyclomatic complexity 28 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — resources/js/wysiwyg/lexical/core/LexicalSelection.ts:1073
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files
- resources/js/wysiwyg/lexical/core/LexicalSelection.ts has 2648 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/wysiwyg/lexical/core/LexicalSelection.ts:1
- resources/js/wysiwyg/lexical/core/LexicalUtils.ts has 1603 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/wysiwyg/lexical/core/LexicalUtils.ts:1
- resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts has 1583 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/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts:1
- resources/js/wysiwyg/lexical/core/nodes/LexicalTextNode.ts has 1324 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/wysiwyg/lexical/core/nodes/LexicalTextNode.ts:1
- resources/js/wysiwyg/lexical/core/LexicalEvents.ts has 1246 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/wysiwyg/lexical/core/LexicalEvents.ts:1
- resources/js/wysiwyg/lexical/core/LexicalEditor.ts has 1200 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/wysiwyg/lexical/core/LexicalEditor.ts:1
- resources/js/wysiwyg/lexical/core/LexicalNode.ts has 1170 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/wysiwyg/lexical/core/LexicalNode.ts:1
- resources/js/wysiwyg/lexical/core/LexicalUpdates.ts has 905 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/wysiwyg/lexical/core/LexicalUpdates.ts:1
- resources/js/wysiwyg/lexical/table/LexicalTableUtils.ts has 810 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/wysiwyg/lexical/table/LexicalTableUtils.ts:1
- resources/js/wysiwyg/lexical/core/LexicalReconciler.ts has 675 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/wysiwyg/lexical/core/LexicalReconciler.ts:1
- resources/js/wysiwyg/lexical/rich-text/index.ts has 628 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/wysiwyg/lexical/rich-text/index.ts:1
- resources/js/wysiwyg/lexical/core/nodes/LexicalElementNode.ts has 589 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/wysiwyg/lexical/core/nodes/LexicalElementNode.ts:1
- resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts has 586 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/wysiwyg/lexical/yjs/CollabElementNode.ts:1
- resources/js/wysiwyg/lexical/utils/index.ts has 545 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/wysiwyg/lexical/utils/index.ts:1
- resources/js/wysiwyg/lexical/clipboard/clipboard.ts has 535 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/wysiwyg/lexical/clipboard/clipboard.ts:1
- resources/js/wysiwyg/lexical/selection/range-selection.ts has 532 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/wysiwyg/lexical/selection/range-selection.ts:1
- resources/js/wysiwyg/lexical/link/index.ts has 513 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/wysiwyg/lexical/link/index.ts:1
- resources/js/wysiwyg/lexical/yjs/Utils.ts 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. — resources/js/wysiwyg/lexical/yjs/Utils.ts:1
- resources/js/wysiwyg/lexical/yjs/SyncCursors.ts has 464 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/wysiwyg/lexical/yjs/SyncCursors.ts:1
- resources/js/wysiwyg/lexical/list/formatList.ts has 458 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/wysiwyg/lexical/list/formatList.ts:1
- resources/js/wysiwyg/lexical/history/index.ts has 428 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/wysiwyg/lexical/history/index.ts:1
- resources/js/markdown/actions.ts has 424 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/markdown/actions.ts:1
- resources/js/wysiwyg/lexical/list/LexicalListItemNode.ts has 410 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/wysiwyg/lexical/list/LexicalListItemNode.ts:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×34) — resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts:1, resources/js/wysiwyg/lexical/yjs/Utils.ts:1, resources/js/wysiwyg/lexical/yjs/SyncCursors.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
R7 · Dead Code
- Unreachable from the 5 application, 6 tooling and 54 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (5 application, 6 tooling, 54 test roots considered), but 8 in-repo import(s) from 7 other file(s) do name it (resources/js/wysiwyg/lexical/yjs/Bindings.ts, resources/js/wysiwyg/lexical/yjs/CollabDecoratorNode.ts, resources/js/wysiwyg/lexical/yjs/CollabLineBreakNode.ts and 4 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts
- no import path from any entry point (5 application, 6 tooling, 54 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (resources/js/wysiwyg/lexical/yjs/CollabDecoratorNode.ts, resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts, resources/js/wysiwyg/lexical/yjs/CollabTextNode.ts and 2 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — resources/js/wysiwyg/lexical/yjs/Utils.ts
- no import path from any entry point (5 application, 6 tooling, 54 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (resources/js/wysiwyg/lexical/yjs/Bindings.ts, resources/js/wysiwyg/lexical/yjs/SyncEditorStates.ts, resources/js/wysiwyg/lexical/yjs/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — resources/js/wysiwyg/lexical/yjs/SyncCursors.ts
- no import path from any entry point (5 application, 6 tooling, 54 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (resources/js/markdown/index.mts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×8) — resources/js/markdown/actions.ts, resources/js/markdown/inputs/textarea.ts, resources/js/markdown/inputs/codemirror.ts, …
- no import path from any entry point (5 application, 6 tooling, 54 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (resources/js/wysiwyg/lexical/yjs/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — resources/js/wysiwyg/lexical/yjs/SyncEditorStates.ts
- no import path from any entry point (5 application, 6 tooling, 54 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (resources/js/wysiwyg/lexical/yjs/Bindings.ts, resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts, resources/js/wysiwyg/lexical/yjs/SyncCursors.ts and 2 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — resources/js/wysiwyg/lexical/yjs/CollabTextNode.ts, resources/js/wysiwyg/lexical/yjs/CollabDecoratorNode.ts
- no import path from any entry point (5 application, 6 tooling, 54 test roots considered), but 8 in-repo import(s) from 8 other file(s) do name it (resources/js/wysiwyg/lexical/yjs/Bindings.ts, resources/js/wysiwyg/lexical/yjs/CollabDecoratorNode.ts, resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts and 5 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — resources/js/wysiwyg/lexical/yjs/index.ts
- no import path from any entry point (5 application, 6 tooling, 54 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (resources/js/markdown/actions.ts, resources/js/markdown/index.mts, resources/js/markdown/inputs/codemirror.ts and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — resources/js/markdown/inputs/interface.ts
- no import path from any entry point (5 application, 6 tooling, 54 test roots considered), but 4 in-repo import(s) from 2 other file(s) do name it (resources/js/wysiwyg/lexical/yjs/SyncCursors.ts, resources/js/wysiwyg/lexical/yjs/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — resources/js/wysiwyg/lexical/yjs/Bindings.ts
- no import path from any entry point (5 application, 6 tooling, 54 test roots considered), but 5 in-repo import(s) from 5 other file(s) do name it (resources/js/markdown/actions.ts, resources/js/markdown/common-events.ts, resources/js/markdown/display.ts and 2 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — resources/js/markdown/index.mts
- no import path from any entry point (5 application, 6 tooling, 54 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (resources/js/wysiwyg/lexical/yjs/Bindings.ts, resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts, resources/js/wysiwyg/lexical/yjs/SyncCursors.ts and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — resources/js/wysiwyg/lexical/yjs/CollabLineBreakNode.ts
- no import path from any entry point (5 application, 6 tooling, 54 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (resources/js/markdown/codemirror.ts, resources/js/markdown/index.mts, resources/js/markdown/inputs/textarea.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — resources/js/markdown/dom-handlers.ts, resources/js/markdown/shortcuts.ts
- no import path from any entry point (5 application, 6 tooling, 54 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (resources/js/wysiwyg/lexical/yjs/CollabTextNode.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — resources/js/wysiwyg/lexical/core/shared/simpleDiffWithCursor.ts
- no import path from any entry point (5 application, 6 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×5) — resources/js/code/legacy-modes.mjs, resources/js/wysiwyg/lexical/yjs/types.ts, resources/js/wysiwyg/lexical/core/shared/warnOnlyOnce.ts, …
- Nothing imports this binding — it is safe to review for removal. (×9) — resources/js/services/dates.ts:1, resources/js/wysiwyg/lexical/core/LexicalConstants.ts:62, resources/js/wysiwyg/lexical/core/LexicalConstants.ts:63, …
- Nothing ultimately consumes this binding: its only referrer is the re-export in resources/js/wysiwyg/lexical/core/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in resources/js/wysiwyg/lexical/core/index.ts in the same commit, or the barrel will import a name that no longer exists. (×3) — resources/js/wysiwyg/lexical/core/LexicalCommands.ts:87, resources/js/wysiwyg/lexical/core/LexicalCommands.ts:90, resources/js/wysiwyg/lexical/core/LexicalSelection.ts:2744
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- resources/js/wysiwyg/ui/framework/core.ts → resources/js/wysiwyg/ui/framework/manager.ts → resources/js/wysiwyg/ui/framework/core.ts (one verified cycle inside a mutually-dependent group of 90 files) — resources/js/wysiwyg/ui/framework/core.ts:2
- resources/js/wysiwyg/lexical/core/LexicalEditor.ts → resources/js/wysiwyg/lexical/core/LexicalEditorState.ts → resources/js/wysiwyg/lexical/core/LexicalUpdates.ts → resources/js/wysiwyg/lexical/core/LexicalEditor.ts (one verified cycle inside a mutually-dependent group of 19 files) — resources/js/wysiwyg/lexical/core/LexicalEditor.ts:22
- resources/js/wysiwyg/lexical/yjs/CollabDecoratorNode.ts → resources/js/wysiwyg/lexical/yjs/Utils.ts → resources/js/wysiwyg/lexical/yjs/CollabDecoratorNode.ts (one verified cycle inside a mutually-dependent group of 4 files) — resources/js/wysiwyg/lexical/yjs/CollabDecoratorNode.ts:17
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `REDACTED` builds the web-server image that serves this application, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — REDACTED:1
What to do
- Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X1 · Async correctness
X12 · Unreachable branch
X14 · Bypassable address classification
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `$getAllNodesOfType` is exported and takes `root: ElementNode` from its caller, and it calls itself at line 66 (`$getAllNodesOfType`) with a piece of `root` — and nowhere in `$getAllNodesOfType` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `$getAllNodesOfType` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — resources/js/wysiwyg/utils/nodes.ts:66
- `$sortNodes` is exported, takes a document from its caller (line 132) and hands it to `addIds`, which calls itself at line 138 (`addIds`) with a piece of `n` — and nowhere in `addIds` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `addIds` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — resources/js/wysiwyg/utils/nodes.ts:138
- `$generateNodesFromDOM` is exported, takes a document from its caller (line 39) and hands it to `$createNodesFromDOM`, which calls itself at line 289 (`$createNodesFromDOM`) with a piece of `node` — and nowhere in `$createNodesFromDOM` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `$createNodesFromDOM` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — resources/js/wysiwyg/lexical/html/index.ts:289
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `request` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — resources/js/services/http.ts:80
What to do
- Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard
X24 · Document value interpolated into markup unescaped
- `elem.innerHTML.replace(/<br\s*\/?>/gi,'\n')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — resources/js/code/index.mjs:64
- `resp.data` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×8) — resources/js/components/ajax-form.js:66, resources/js/components/attachments.js:64, resources/js/components/attachments.js:80, …
- `err.data` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — resources/js/components/ajax-form.js:71
- `key` is text this program did not author, and it is written into a quoted attribute value through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — resources/js/components/code-editor.js:205
- `resp.data as string` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — resources/js/components/entity-selector.ts:141, resources/js/components/entity-selector.ts:159
- `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×3) — resources/js/components/image-manager.js:187, resources/js/services/dom.ts:176, resources/js/services/vdom.ts:26
- `loadMore.innerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — resources/js/components/image-manager.js:192
- `formHtml` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — resources/js/components/image-manager.js:274
- `(closeIcon as string)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — resources/js/components/page-comment-reference.ts:202
- `this.draftText` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — resources/js/components/page-editor.js:56
- `userEl.innerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — resources/js/components/user-select.js:17
- `customHeadHtml` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — resources/js/wysiwyg-tinymce/config.js:167
- `code.innerHTML.replace(/\ufeff/g,'')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — resources/js/wysiwyg-tinymce/plugin-codeeditor.js:103
- `content` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — resources/js/wysiwyg-tinymce/plugins-details.js:237
- `searchIcon` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — resources/js/wysiwyg/ui/decorators/MentionDecorator.ts:99
- `removeIcon` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — resources/js/wysiwyg/ui/framework/blocks/color-picker.ts:68
- `selectIcon` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — resources/js/wysiwyg/ui/framework/blocks/color-picker.ts:77
- `arrowIcon` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — resources/js/wysiwyg/ui/framework/blocks/menu-button.ts:10
- `this.definition.icon||''` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — resources/js/wysiwyg/ui/framework/buttons.ts:64
- `closeIcon` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — resources/js/wysiwyg/ui/framework/modals.ts:60
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
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. (×4) — resources/js/wysiwyg/lexical/clipboard/clipboard.ts:161, resources/js/wysiwyg/lexical/clipboard/clipboard.ts:173, database/migrations/2018_08_04_115700_create_bookshelves_table.php:26, …
- `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — app/Users/Models/User.php:235, app/Uploads/ImageRepo.php:231, app/Entities/Tools/EntityCover.php:59
- `catch (\Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — app/Settings/StatusController.php:49, app/Exceptions/BookStackExceptionHandlerPage.php:24
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `error` at line 103 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->error('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::error('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Users/Controllers/UserController.php:103
- `warning` at line 99 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->warning('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::warning('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Uploads/ImageStorageDisk.php:99
- `error` at line 69 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->error('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::error('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Activity/DispatchWebhookJob.php:69
- `error` at line 73 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->error('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::error('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Activity/DispatchWebhookJob.php:73
- `error` at line 45 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->error('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::error('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Activity/Notifications/Handlers/BaseNotificationHandler.php:45
- `info` at line 256 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->info('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::info('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Access/LdapService.php:256
- `info` at line 486 is handed a double-quoted string with variables interpolated into it as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass a constant message and the values in the PSR-3 context array instead: `$logger->info('Order {order_id} moved to {status}', ['order_id' => $orderId, 'status' => $status])`, which Monolog and every PSR-3 handler keep as fields beside the message (Monolog's PsrLogMessageProcessor fills the placeholders), or `Log::info('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Access/LdapService.php:486
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- 0/1 of this repository's PHPStan/Psalm configuration(s) run at a level that checks null — PHPStan level 8 or above (`max` included), or Psalm `errorLevel` 3 or below (Psalm's default, with none stated, is 1). A PHPStan level written neither in the file nor in an include inside the repository is 0, PHPStan's own default. Below those levels the checker removes `null` from a union before any rule looks, so `$order->customer()->name()` on a `?Customer` passes, and the first null reaching it is an `Error: Call to a member function name() on null` in production.
What to do
- Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 46% | Weak — gated by X4, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 64% | Adequate — gated by R9 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 61% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 43% | Weak — gated by D13, P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 73% | Strong | Solid. |
| Domain Modelling | 64% | Adequate — gated by DM4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 48% | Weak — gated by AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 8 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.
- X10 Duplicated predicate — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- 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.
Not included — 52 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX1 Captive dependencies — not 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
- AX6 Interface segregation — AX6 reached only 20% of this repository's production lines — php (42,965 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c docker-php-ext-configure ldap --with-libdir=\"lib/$(gcc -dumpmachine)\" && docker-php-ext-configure gd --with-freetype --with-jpeg && docker-php-ext-install -j$(nproc) pdo_mysql gd ldap zip && pecl install xdebug && docker-php-ext-enable xdebug" did not complete successfully: exit code: 1; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
- 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.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript, PHP not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- 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.
- D32 Data Compliance (PII/GDPR) — 20 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- 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.
- D5 Coupling — Not applicable — this Composer build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in the repository root ran and not one test passed (Error: Jest: Failed to parse the TypeScript config file jest.config.ts), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
- DM12 Ambient inputs in the domain — no domain-layer types detected — ambient-input check not applicable
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM6 Domain ↔ infrastructure boundary — no domain-layer types detected — domain↔infrastructure boundary check not applicable
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- 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
- 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
- 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.
- X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 88 finding(s)
- <label> that labels no control resources/views/books/parts/form.blade.php:14
- <label> that labels no control resources/views/exports/import-show.blade.php:12
- <label> that labels no control resources/views/exports/import-show.blade.php:22
- <label> that labels no control resources/views/exports/import-show.blade.php:47
- <label> that labels no control resources/views/settings/categories/customization.blade.php:42
- <label> that labels no control resources/views/settings/categories/customization.blade.php:59
- <label> that labels no control resources/views/settings/categories/customization.blade.php:81
- <label> that labels no control resources/views/settings/categories/features.blade.php:33
- <label> that labels no control resources/views/settings/categories/features.blade.php:47
- <label> that labels no control resources/views/settings/categories/registration.blade.php:12
- <label> that labels no control resources/views/settings/categories/registration.blade.php:59
- <label> that labels no control resources/views/settings/categories/sorting.blade.php:16
- <label> that labels no control resources/views/settings/roles/parts/form.blade.php:5
- <label> that labels no control resources/views/settings/roles/parts/form.blade.php:30
- <label> that labels no control resources/views/settings/roles/parts/form.blade.php:58
- <label> that labels no control resources/views/settings/sort-rules/parts/form.blade.php:4
- <label> that labels no control resources/views/settings/sort-rules/parts/form.blade.php:16
- <label> that labels no control resources/views/settings/webhooks/edit.blade.php:15
- <label> that labels no control resources/views/settings/webhooks/parts/form.blade.php:5
- <label> that labels no control resources/views/settings/webhooks/parts/form.blade.php:33
- <label> that labels no control resources/views/shelves/parts/form.blade.php:63
- <label> that labels no control resources/views/users/account/delete.blade.php:20
- <label> that labels no control resources/views/users/api-tokens/edit.blade.php:18
- <label> that labels no control resources/views/users/api-tokens/edit.blade.php:30
- <label> that labels no control resources/views/users/api-tokens/parts/form.blade.php:5
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <input> without a programmatic label resources/views/mfa/parts/verify-backup_codes.blade.php:7
- <input> without a programmatic label resources/views/mfa/parts/verify-totp.blade.php:7
- <input> without a programmatic label resources/views/pages/parts/template-manager.blade.php:15
- <input> without a programmatic label resources/views/search/all.blade.php:16
- <input> without a programmatic label resources/views/search/all.blade.php:78
- <input> without a programmatic label resources/views/search/parts/date-filter.blade.php:14
- <input> without a programmatic label resources/views/search/parts/term-list.blade.php:13
- <input> without a programmatic label resources/views/settings/webhooks/index.blade.php:26
- <input> without a programmatic label resources/views/shelves/parts/form.blade.php:48
- <input> without a programmatic label resources/views/tags/index.blade.php:16
- <input> without a programmatic label resources/views/users/api-tokens/edit.blade.php:34
- Boundary-crossing change coupling: OidcService.php ↔ oidc.php app/Access/Oidc/OidcService.php:1
- Boundary-crossing change coupling: BookController.php ↔ edit.blade.php app/Entities/Controllers/BookController.php:1
- Boundary-crossing change coupling: ActivityType.php ↔ activities.php app/Activity/ActivityType.php:1
- Boundary-crossing change coupling: ApiController.php ↔ api.php app/Http/ApiController.php:1
- Boundary-crossing change coupling: BookController.php ↔ create.blade.php app/Entities/Controllers/BookController.php:1
- Boundary-crossing change coupling: ActivityType.php ↔ web.php app/Activity/ActivityType.php:1
- Boundary-crossing change coupling: REDACTED ↔ form.blade.php lang/en/settings.php:1
- <img> without a text alternative resources/views/misc/opensearch.blade.php:5
- <img> without a text alternative resources/views/misc/opensearch.blade.php:6
- <img> without a text alternative resources/views/misc/opensearch.blade.php:7
- <img> without a text alternative resources/views/misc/opensearch.blade.php:8
- <img> without a text alternative resources/views/misc/opensearch.blade.php:9
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <select> without a programmatic label resources/views/api-docs/index.blade.php:13
- <select> without a programmatic label resources/views/form/role-select.blade.php:2
- <select> without a programmatic label resources/views/users/account/parts/display-mode-option-row.blade.php:13
- REDACTED
- REDACTED
- REDACTED
- Viewport restricts zoom resources/views/api-docs/download.blade.php:5
- Viewport restricts zoom resources/views/errors/debug.blade.php:5
- Import cycle (2 files) resources/js/wysiwyg/ui/framework/core.ts:2
- Import cycle (2 files) resources/js/wysiwyg/lexical/yjs/CollabDecoratorNode.ts:17
- aria-expanded on a <div> with no role to carry it resources/views/form/user-select.blade.php:5
- Banned license: dompdf/php-svg-lib
- REDACTED
- REDACTED
- Import cycle (3 files) resources/js/wysiwyg/lexical/core/LexicalEditor.ts:22
Serious — 376 finding(s)
- No test reaches this file resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts:1
- No test reaches this file resources/js/wysiwyg/lexical/yjs/Utils.ts:1
- No test reaches this file resources/js/wysiwyg/lexical/yjs/SyncCursors.ts:1
- No test reaches this file resources/js/markdown/actions.ts:1
- No test reaches this file resources/js/markdown/inputs/textarea.ts:1
- No test reaches this file resources/js/wysiwyg/lexical/yjs/SyncEditorStates.ts:1
- No test reaches this file resources/js/code/index.mjs:1
- No test reaches this file resources/js/wysiwyg/lexical/yjs/CollabTextNode.ts:1
- No test reaches this file resources/js/services/components.ts:1
- No test reaches this file resources/js/markdown/inputs/codemirror.ts:1
- No test reaches this file resources/js/code/themes.js:1
- No test reaches this file resources/js/code/languages.js:1
- No test reaches this file resources/js/wysiwyg/lexical/yjs/index.ts:1
- No test reaches this file resources/js/markdown/display.ts:1
- No test reaches this file resources/js/wysiwyg/lexical/yjs/CollabDecoratorNode.ts:1
- No test reaches this file resources/js/services/events.ts:1
- No test reaches this file resources/js/code/setups.js:1
- No test reaches this file resources/js/markdown/settings.ts:1
- No test reaches this file resources/js/wysiwyg/lexical/yjs/Bindings.ts:1
- No test reaches this file resources/js/markdown/index.mts:1
- No test reaches this file resources/js/wysiwyg/lexical/yjs/CollabLineBreakNode.ts:1
- No test reaches this file resources/js/markdown/dom-handlers.ts:1
- No test reaches this file resources/js/markdown/codemirror.ts:1
- No test reaches this file resources/js/code/views.js:1
- No test reaches this file resources/js/wysiwyg/lexical/core/shared/simpleDiffWithCursor.ts:1
- Untrusted text written into markup unescaped resources/js/code/index.mjs:64
- Untrusted text written into markup unescaped resources/js/components/ajax-form.js:66
- Untrusted text written into markup unescaped resources/js/components/ajax-form.js:71
- Untrusted text written into markup unescaped resources/js/components/attachments.js:64
- Untrusted text written into markup unescaped resources/js/components/attachments.js:80
- Untrusted text written into markup unescaped resources/js/components/code-editor.js:205
- Untrusted text written into markup unescaped resources/js/components/dropdown-search.js:57
- Untrusted text written into markup unescaped resources/js/components/entity-search.js:44
- Untrusted text written into markup unescaped resources/js/components/entity-selector.ts:141
- Untrusted text written into markup unescaped resources/js/components/entity-selector.ts:159
- Untrusted text written into markup unescaped resources/js/components/image-manager.js:187
- Untrusted text written into markup unescaped resources/js/components/image-manager.js:192
- Untrusted text written into markup unescaped resources/js/components/image-manager.js:274
- Untrusted text written into markup unescaped resources/js/components/page-comment-reference.ts:202
- Untrusted text written into markup unescaped resources/js/components/page-editor.js:56
- Untrusted text written into markup unescaped resources/js/components/template-manager.js:77
- Untrusted text written into markup unescaped resources/js/components/template-manager.js:86
- Untrusted text written into markup unescaped resources/js/components/user-select.js:17
- Untrusted text written into markup unescaped resources/js/services/dom.ts:176
- Untrusted text written into markup unescaped resources/js/services/vdom.ts:26
- Untrusted text written into markup unescaped resources/js/wysiwyg-tinymce/config.js:167
- Untrusted text written into markup unescaped resources/js/wysiwyg-tinymce/plugin-codeeditor.js:103
- Untrusted text written into markup unescaped resources/js/wysiwyg-tinymce/plugins-details.js:237
- Untrusted text written into markup unescaped resources/js/wysiwyg/ui/decorators/MentionDecorator.ts:99
- Untrusted text written into markup unescaped resources/js/wysiwyg/ui/framework/blocks/color-picker.ts:68
- Anemic entity: SocialAccount app/Access/SocialAccount.php:15
- Anemic entity: Comment app/Activity/Models/Comment.php:30
- Anemic entity: Favourite app/Activity/Models/Favourite.php:11
- Anemic entity: MentionHistory app/Activity/Models/MentionHistory.php:17
- Anemic entity: Tag app/Activity/Models/Tag.php:19
- Anemic entity: Watch app/Activity/Models/Watch.php:22
- Anemic entity: Webhook app/Activity/Models/Webhook.php:23
- Anemic entity: WebhookTrackedEvent app/Activity/Models/WebhookTrackedEvent.php:13
- Anemic entity: ApiToken app/Api/ApiToken.php:22
- Anemic entity: Book app/Entities/Models/Book.php:29
- Anemic entity: Bookshelf app/Entities/Models/Bookshelf.php:15
- Anemic entity: Chapter app/Entities/Models/Chapter.php:16
- Anemic entity: Deletion app/Entities/Models/Deletion.php:19
- Anemic entity: EntityContainerData app/Entities/Models/EntityContainerData.php:17
- Anemic entity: EntityPageData app/Entities/Models/EntityPageData.php:10
- Anemic entity: EntityTable app/Entities/Models/EntityTable.php:19
- Anemic entity: Page app/Entities/Models/Page.php:31
- Anemic entity: PageRevision app/Entities/Models/PageRevision.php:31
- Anemic entity: PageUpdateDraft app/Entities/Models/PageUpdateDraft.php:25
- Anemic entity: SlugHistory app/Entities/Models/SlugHistory.php:17
- Anemic entity: Import app/Exports/Import.php:27
- Anemic entity: EntityPermission app/Permissions/Models/EntityPermission.php:19
- Anemic entity: JointPermission app/Permissions/Models/JointPermission.php:11
- Anemic entity: Reference app/References/Reference.php:16
- Anemic entity: SearchTerm app/Search/SearchTerm.php:7
- Animation without a prefers-reduced-motion guard resources/sass/_animations.scss:20
- Animation without a prefers-reduced-motion guard resources/sass/_animations.scss:66
- Animation without a prefers-reduced-motion guard resources/sass/_components.scss:22
- Animation without a prefers-reduced-motion guard resources/sass/_components.scss:229
- Animation without a prefers-reduced-motion guard resources/sass/_components.scss:288
- Animation without a prefers-reduced-motion guard resources/sass/_components.scss:289
- Animation without a prefers-reduced-motion guard resources/sass/_components.scss:297
- Animation without a prefers-reduced-motion guard resources/sass/_components.scss:327
- Animation without a prefers-reduced-motion guard resources/sass/_layout.scss:505
- Animation without a prefers-reduced-motion guard resources/sass/_lists.scss:332
- Animation without a prefers-reduced-motion guard resources/sass/_pages.scss:137
- Animation without a prefers-reduced-motion guard resources/sass/_pages.scss:301
- Animation without a prefers-reduced-motion guard resources/sass/_pages.scss:334
- Animation without a prefers-reduced-motion guard resources/sass/styles.scss:83
- Animation without a prefers-reduced-motion guard resources/sass/styles.scss:251
- Change coupling: ChapterRepo.php ↔ PageRepo.php app/Entities/Repos/ChapterRepo.php:1
- Change coupling: create.blade.php ↔ form.blade.php resources/views/books/create.blade.php:1
- Change coupling: edit.blade.php ↔ form.blade.php resources/views/books/edit.blade.php:1
- Change coupling: BookController.php ↔ ChapterController.php app/Entities/Controllers/BookController.php:1
- Change coupling: page-comment.ts ↔ comment.blade.php resources/js/components/page-comment.ts:1
- Change coupling: ChapterController.php ↔ PageController.php app/Entities/Controllers/ChapterController.php:1
- Change coupling: entity-selector.ts ↔ selector.blade.php resources/js/components/entity-selector.ts:1
- Change coupling: BookApiController.php ↔ BookshelfApiController.php app/Entities/Controllers/BookApiController.php:1
- Change coupling: Bookshelf.php ↔ Chapter.php app/Entities/Models/Bookshelf.php:1
- Change coupling: PageRepo.php ↔ PageEditorData.php app/Entities/Repos/PageRepo.php:1
- Change coupling: BookRepo.php ↔ BookshelfRepo.php app/Entities/Repos/BookRepo.php:1
- Change coupling: BookController.php ↔ BookshelfController.php app/Entities/Controllers/BookController.php:1
- Change coupling: tri-layout.ts ↔ tri.blade.php resources/js/components/tri-layout.ts:1
- Mutable entity: Book app/Entities/Models/Book.php:29
- Mutable entity: Bookshelf app/Entities/Models/Bookshelf.php:15
- Mutable entity: Chapter app/Entities/Models/Chapter.php:16
- Mutable entity: Entity app/Entities/Models/Entity.php:55
- Mutable entity: EntityContainerData app/Entities/Models/EntityContainerData.php:17
- Mutable entity: EntityPageData app/Entities/Models/EntityPageData.php:10
- Mutable entity: Page app/Entities/Models/Page.php:31
- Mutable entity: EntityPermission app/Permissions/Models/EntityPermission.php:19
- Mutable entity: JointPermission app/Permissions/Models/JointPermission.php:11
- Mutable entity: Reference app/References/Reference.php:16
- Mutable entity: SearchTerm app/Search/SearchTerm.php:7
- Focus outline removed in CSS without a :focus replacement resources/sass/_codemirror.scss:68
- Focus outline removed in CSS without a :focus replacement resources/sass/_components.scss:143
- Focus outline removed in CSS without a :focus replacement resources/sass/_components.scss:556
- Focus outline removed in CSS without a :focus replacement resources/sass/_components.scss:573
- Focus outline removed in CSS without a :focus replacement resources/sass/_editor.scss:45
- Focus outline removed in CSS without a :focus replacement resources/sass/_forms.scss:70
- Focus outline removed in CSS without a :focus replacement resources/sass/_tinymce.scss:25
- Focus outline removed in CSS without a :focus replacement resources/sass/_tinymce.scss:33
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (13 lines × 2 locations) resources/js/services/dom.ts:21
- Duplicated block (13 lines × 2 locations) resources/js/wysiwyg/lexical/core/LexicalReconciler.ts:611
- Duplicated block (13 lines × 2 locations) resources/js/wysiwyg/lexical/core/LexicalSelection.ts:2388
- Duplicated block (13 lines × 2 locations) resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts:1610
- Duplicated block (13 lines × 2 locations) resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts:540
- Duplicated block (13 lines × 2 locations) resources/js/wysiwyg/ui/defaults/buttons/tables.ts:67
- Duplicated block (13 lines × 2 locations) resources/js/wysiwyg/utils/table-copy-paste.ts:77
- Low cohesion: User (LCOM4 7) app/Users/Models/User.php:48
- Low cohesion: SearchRunner (LCOM4 6) app/Search/SearchRunner.php:22
- Low cohesion: ConfiguredHtmlPurifier (LCOM4 5) app/Util/HtmlPurifier/ConfiguredHtmlPurifier.php:24
- Low cohesion: CommentTree (LCOM4 4) app/Activity/Tools/CommentTree.php:9
- Low cohesion: TrashCan (LCOM4 4) app/Entities/Tools/TrashCan.php:25
- Low cohesion: ThemeService (LCOM4 4) app/Theming/ThemeService.php:11
- Duplicated block (15 lines × 2 locations) resources/js/components/book-sort.js:80
- Duplicated block (15 lines × 2 locations) resources/js/wysiwyg/lexical/core/LexicalUtils.ts:888
- Duplicated block (15 lines × 2 locations) resources/js/wysiwyg/lexical/rich-text/index.ts:320
- Duplicated block (15 lines × 2 locations) resources/js/wysiwyg/lexical/rich-text/index.ts:442
- Duplicated block (15 lines × 2 locations) resources/js/wysiwyg/lexical/yjs/SyncCursors.ts:312
- Duplicated block (15 lines × 2 locations) resources/js/wysiwyg/ui/defaults/buttons/controls.ts:19
- Page without a main landmark resources/views/api-docs/download.blade.php:2
- Page without a main landmark resources/views/errors/debug.blade.php:2
- Page without a main landmark resources/views/layouts/base.blade.php:2
- Page without a main landmark resources/views/layouts/export.blade.php:2
- Page without a main landmark resources/views/layouts/plain.blade.php:2
- Duplicated block (7 lines × 2) app/Activity/Tools/EntityWatchers.php:74
- Duplicated block (7 lines × 2) app/App/HomeController.php:53
- Duplicated block (7 lines × 2) app/Activity/Models/Favourite.php:22
- Duplicated block (7 lines × 2) app/Entities/Controllers/ChapterController.php:226
- Duplicated block (7 lines × 2) app/Entities/Queries/BookshelfQueries.php:34
- Swallowed exception (caught, then discarded) app/Users/Models/User.php:235
- Swallowed exception (caught, then discarded) app/Uploads/ImageRepo.php:231
- Swallowed exception (caught, then discarded) app/Settings/StatusController.php:49
- Swallowed exception (caught, then discarded) app/Exceptions/BookStackExceptionHandlerPage.php:24
- Swallowed exception (caught, then discarded) app/Entities/Tools/EntityCover.php:59
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (9 lines × 2) app/Entities/Controllers/BookApiController.php:132
- Duplicated block (9 lines × 2) app/Entities/Controllers/ChapterController.php:77
- Duplicated block (9 lines × 2) app/Entities/Tools/PageContent.php:43
- Duplicated block (9 lines × 2) app/References/ModelResolvers/ImageModelResolver.php:24
- Duplicated block (8 lines × 2) app/Entities/Controllers/PageController.php:284
- Duplicated block (8 lines × 2) app/Entities/Controllers/BookApiController.php:35
- Duplicated block (8 lines × 2) app/View/ViewBlocks/BooksIndexNew.php:21
- Duplicated block (8 lines × 2) app/View/ViewBlocks/BooksIndexRecents.php:21
- Swallowed exception (empty catch) resources/js/wysiwyg/lexical/clipboard/clipboard.ts:161
- Swallowed exception (empty catch) resources/js/wysiwyg/lexical/clipboard/clipboard.ts:173
- Swallowed exception (empty catch) database/migrations/2018_08_04_115700_create_bookshelves_table.php:26
- Swallowed exception (empty catch) app/Access/Controllers/Saml2Controller.php:109
- Heading level jumps from h2 to h5 REDACTED:28
- Heading level jumps from h2 to h5 resources/views/settings/recycle-bin/destroy.blade.php:20
- Heading level jumps from h2 to h5 resources/views/settings/recycle-bin/restore.blade.php:19
- Low contrast colour pair in CSS (4.2:1) resources/sass/_buttons.scss:64
- Low contrast colour pair in CSS (4.2:1) resources/sass/_editor.scss:620
- Low contrast colour pair in CSS (4.2:1) resources/sass/_forms.scss:589
- Duplicated block (12 lines × 2) app/Entities/Controllers/BookController.php:172
- Duplicated block (12 lines × 2) app/Exports/ZipExports/Models/ZipExportBook.php:86
- Duplicated block (12 lines × 2) app/Console/Commands/RegeneratePermissionsCommand.php:31
- Duplicated block (17 lines × 2 locations) resources/js/wysiwyg/lexical/clipboard/clipboard.ts:271
- Duplicated block (17 lines × 2 locations) resources/js/wysiwyg/lexical/core/LexicalUtils.ts:933
- Duplicated block (17 lines × 2 locations) resources/js/wysiwyg/lexical/core/nodes/LexicalElementNode.ts:261
- Duplicated block (14 lines × 2 locations) resources/js/wysiwyg/lexical/core/LexicalSelection.ts:2444
- Duplicated block (14 lines × 2 locations) resources/js/wysiwyg/lexical/core/LexicalUtils.ts:350
- Duplicated block (14 lines × 2 locations) resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts:180
- Recursive walk over a caller-supplied document has no depth cap resources/js/wysiwyg/utils/nodes.ts:66
- Recursive walk over a caller-supplied document has no depth cap resources/js/wysiwyg/utils/nodes.ts:138
- Recursive walk over a caller-supplied document has no depth cap resources/js/wysiwyg/lexical/html/index.ts:289
- Data table has no header cells REDACTED:172
- Data table has no header cells resources/views/search/parts/date-filter.blade.php:5
- Heading level jumps from h1 to h5 resources/views/errors/parts/not-found-text.blade.php:4
- Heading level jumps from h1 to h5 resources/views/mfa/verify.blade.php:12
- TodoComment app/Entities/Controllers/PageRevisionController.php:102
- TodoComment app/Entities/Controllers/PageRevisionController.php:148
- TooManyMethods: Entity app/Entities/Models/Entity.php:55
- TooManyMethods: Actions resources/js/markdown/actions.ts:13
- Members sharing a duplicated core (4 members, 50+ identical tokens) app/Activity/Notifications/Messages/CommentCreationNotification.php:17
- Members sharing a duplicated core (4 members, 50+ identical tokens) app/Permissions/PermissionsController.php:41
- Duplicated block (13 lines × 2) app/References/ModelResolvers/BookLinkModelResolver.php:18
- Duplicated block (13 lines × 2) database/migrations/2023_12_02_104541_add_default_template_to_books.php:14
- Duplicated block (11 lines × 2) app/Entities/Queries/ChapterQueries.php:40
- Duplicated block (11 lines × 2) database/factories/Entities/Models/PageRevisionFactory.php:23
- Duplicated block (16 lines × 2 locations) resources/js/wysiwyg-tinymce/plugin-codeeditor.js:247
- Duplicated block (16 lines × 2 locations) resources/js/wysiwyg/lexical/core/LexicalNormalization.ts:48
- Dead file (~27 LoC) resources/js/markdown/markdown.ts
- Dead file (~27 LoC) resources/js/wysiwyg/lexical/yjs/types.ts
- Heading level jumps from h3 to h5 resources/views/errors/500.blade.php:10
- Heading level jumps from h1 to h4 resources/views/errors/debug.blade.php:110
- Heading level jumps from h1 to h3 resources/views/help/licenses.blade.php:23
- Heading level jumps from h1 to h6 resources/views/search/all.blade.php:85
- Accessibility enforcement below the top rung package.json:21
- BookSorter.isSortChangePermissible (cyclomatic 28) app/Sorting/BookSorter.php:184
- SrcsetAttrDef.formatDescriptor (cyclomatic 25) app/Util/HtmlPurifier/SrcsetAttrDef.php:157
- SrcsetAttrDef.parseImageSources (cyclomatic 23) app/Util/HtmlPurifier/SrcsetAttrDef.php:57
- ZipExportReferences.handleModelReference (cyclomatic 21) app/Exports/ZipExports/ZipExportReferences.php:113
- ZipImportRunner.ensurePermissionsPermitImport (cyclomatic 19) app/Exports/ZipExports/ZipImportRunner.php:296
- SearchResultsFormatter.formatTextUsingMatchPositions (cyclomatic 19) app/Search/SearchResultsFormatter.php:143
- PageRepo.updateTemplateStatusAndContentFromInput (cyclomatic 17) app/Entities/Repos/PageRepo.php:153
- plugin-codeeditor.register (cyclomatic 17) resources/js/wysiwyg-tinymce/plugin-codeeditor.js:158
- BookSorter.applySortUpdates (cyclomatic 16) app/Sorting/BookSorter.php:126
- SrcsetAttrDef.parseImageSources (cognitive 111) app/Util/HtmlPurifier/SrcsetAttrDef.php:57
- SrcsetAttrDef.formatDescriptor (cognitive 43) app/Util/HtmlPurifier/SrcsetAttrDef.php:157
- BookSorter.isSortChangePermissible (cognitive 33) app/Sorting/BookSorter.php:184
- ZipImportRunner.ensurePermissionsPermitImport (cognitive 32) app/Exports/ZipExports/ZipImportRunner.php:296
- ZipExportReferences.handleModelReference (cognitive 31) app/Exports/ZipExports/ZipExportReferences.php:113
- InstallModuleCommand.downloadModuleFile (cognitive 26) app/Console/Commands/InstallModuleCommand.php:199
- SearchResultsFormatter.formatTextUsingMatchPositions (cognitive 22) app/Search/SearchResultsFormatter.php:143
- register (cognitive 22) resources/js/wysiwyg-tinymce/plugin-codeeditor.js:158
- AssignSortRuleCommand.handle (cognitive 21) app/Console/Commands/AssignSortRuleCommand.php:33
- ZipImportRunner.run (cognitive 19) app/Exports/ZipExports/ZipImportRunner.php:51
- ThemeModuleZip.extractTo (cognitive 18) app/Theming/ThemeModuleZip.php:15
- EntityHydrator.loadParentsIntoModels (cognitive 17) app/Entities/Tools/EntityHydrator.php:96
- CreateAdminCommand.gatherDetails (cognitive 16) app/Console/Commands/CreateAdminCommand.php:118
- Change coupling clique: common.php, common.php, common.php lang/de/common.php
- Duplicated block (21 lines × 2) app/Users/Controllers/UserSearchController.php:23
- Duplicated block (19–20 lines × 2) app/Entities/Controllers/BookController.php:42
- Duplicated block (19 lines × 2) app/Uploads/Controllers/DrawioImageController.php:31
- Duplicated block (15 lines × 2) app/Activity/Notifications/Messages/CommentCreationNotification.php:17
- Duplicated block (14 lines × 2) app/References/ModelResolvers/ChapterLinkModelResolver.php:18
- Duplicated block (12–13 lines × 4) app/Activity/Notifications/Messages/CommentCreationNotification.php:21
- Duplicated block (9 lines × 4) app/Permissions/PermissionsController.php:42
- Duplicated block (9 lines × 3) app/Activity/Queries/WebhooksAllPaginatedAndSorted.php:20
- Duplicated block (6 lines × 2) app/Entities/Controllers/RecycleBinApiController.php:19
- Duplicated block (10 lines × 2) app/Entities/Queries/BookQueries.php:40
- Duplicated block (5 lines × 2) app/Entities/Queries/ChapterQueries.php:55
- Duplicated block (6 lines × 4) app/Entities/Controllers/BookApiController.php:122
- Duplicated block (5 lines × 3) app/Search/SearchRunner.php:361
- Coverage not measured — JavaScript/TypeScript suite
- SAST runs, but gates no merge
- No DR/backup evidence
- Duplication concentrated across 10 sibling directories (24 clone groups) resources/js/wysiwyg/lexical/core/nodes/LexicalParagraphNode.ts:118
- Duplicated block with local edits (86 matched lines × 2 locations) resources/js/wysiwyg/lexical/rich-text/LexicalCodeBlockNode.ts:31
- Duplicated block (54 lines × 2 locations) resources/js/wysiwyg/ui/defaults/buttons/tables.ts:177
- Duplicated block with local edits (39 matched lines × 2 locations) resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts:60
- Duplicated block with local edits (30 matched lines × 2 locations) resources/js/wysiwyg/utils/table-copy-paste.ts:26
- Duplicated block with local edits (29 matched lines × 2 locations) resources/js/wysiwyg/ui/defaults/forms/tables.ts:78
- Duplicated block (25 lines × 2 locations) resources/js/wysiwyg/lexical/core/nodes/LexicalParagraphNode.ts:118
- Duplicated block (24 lines × 2 locations) resources/js/wysiwyg/lexical/rich-text/index.ts:340
- Duplicated block with local edits (23 matched lines × 2 locations) resources/js/wysiwyg/lexical/clipboard/clipboard.ts:240
- Duplicated block (23 lines × 2 locations) resources/js/wysiwyg/lexical/core/LexicalUtils.ts:1657
- Duplicated block (21 lines × 2 locations) resources/js/wysiwyg/lexical/table/LexicalTableUtils.ts:266
- Duplicated block (19 lines × 2 locations) resources/js/wysiwyg/index.ts:105
- Duplicated block (19 lines × 4 locations) resources/js/wysiwyg/lexical/core/LexicalUtils.ts:321
- Duplicated block (19 lines × 3 locations) resources/js/wysiwyg/lexical/core/nodes/CommonBlockNode.ts:23
- Duplicated block (18 lines × 2 locations) resources/js/wysiwyg/lexical/table/LexicalTableUtils.ts:498
- Duplicated block (17 lines × 3 locations) resources/js/wysiwyg/lexical/rich-text/index.ts:264
- Duplicated block (14 lines × 7 locations) resources/js/wysiwyg/lexical/core/nodes/CommonBlockNode.ts:17
- Duplicated block with local edits (14 matched lines × 2 locations) resources/js/wysiwyg/lexical/utils/index.ts:192
- Duplicated block (12 lines × 2 locations) resources/js/components/shelf-sort.js:21
- Boundary violation [package:third-party-deep-import] resources/js/services/vdom.ts:7
- Complex function insertText (cyclomatic 92, cognitive 158) resources/js/wysiwyg/lexical/core/LexicalSelection.ts:717
- Complex function $handleArrowKey (cyclomatic 62, cognitive 146) resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts:1267
- Complex function (anonymous) (cyclomatic 56, cognitive 45) resources/js/wysiwyg/lexical/core/LexicalEvents.ts:542
- Complex function updateDOMSelection (cyclomatic 47, cognitive 52) resources/js/wysiwyg/lexical/core/LexicalSelection.ts:2558
- Complex function (anonymous) (cyclomatic 45, cognitive 97) resources/js/wysiwyg/lexical/core/LexicalMutations.ts:111
- Complex function $patchStyleText (cyclomatic 44, cognitive 75) resources/js/wysiwyg/lexical/selection/lexical-node.ts:279
- Complex function deleteCharacter (cyclomatic 41, cognitive 58) resources/js/wysiwyg/lexical/core/LexicalSelection.ts:1594
- Complex function (anonymous) (cyclomatic 41, cognitive 58) resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts:675
- Complex function $wrapNodesImpl (cyclomatic 36, cognitive 76) resources/js/wysiwyg/lexical/selection/range-selection.ts:200
- Complex function onKeyDown (cyclomatic 34, cognitive 41) resources/js/wysiwyg/lexical/core/LexicalEvents.ts:992
- Complex function createEditor (cyclomatic 33, cognitive 68) resources/js/wysiwyg/lexical/core/LexicalEditor.ts:420
- Complex function $commitPendingUpdates (cyclomatic 33, cognitive 45) resources/js/wysiwyg/lexical/core/LexicalUpdates.ts:477
- Complex function $updateTextNodeFromDOMContent (cyclomatic 33, cognitive 39) resources/js/wysiwyg/lexical/core/LexicalUtils.ts:642
- Complex function (anonymous) (cyclomatic 33, cognitive 26) resources/js/wysiwyg/lexical/selection/__tests__/utils/index.ts:655
- Complex function modify (cyclomatic 32, cognitive 74) resources/js/wysiwyg/lexical/core/LexicalSelection.ts:1413
- Complex function (anonymous) (cyclomatic 32, cognitive 62) resources/js/wysiwyg/lexical/core/LexicalEvents.ts:291
- Complex function $trimTextContentFromAnchor (cyclomatic 31, cognitive 71) resources/js/wysiwyg/lexical/selection/lexical-node.ts:113
- Complex function modify (cyclomatic 30, cognitive 74) resources/js/wysiwyg/lexical/selection/__tests__/utils/index.ts:89
- Complex function getChangeType (cyclomatic 30, cognitive 22) resources/js/wysiwyg/lexical/history/index.ts:80
- Complex function formatText (cyclomatic 28, cognitive 38) resources/js/wysiwyg/lexical/core/LexicalSelection.ts:1073
- resources/js/wysiwyg/lexical/core/LexicalSelection.ts: 2648 lines of code resources/js/wysiwyg/lexical/core/LexicalSelection.ts:1
- resources/js/wysiwyg/lexical/core/LexicalUtils.ts: 1603 lines of code resources/js/wysiwyg/lexical/core/LexicalUtils.ts:1
- resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts: 1583 lines of code resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts:1
- resources/js/wysiwyg/lexical/core/nodes/LexicalTextNode.ts: 1324 lines of code resources/js/wysiwyg/lexical/core/nodes/LexicalTextNode.ts:1
- resources/js/wysiwyg/lexical/core/LexicalEvents.ts: 1246 lines of code resources/js/wysiwyg/lexical/core/LexicalEvents.ts:1
- resources/js/wysiwyg/lexical/core/LexicalEditor.ts: 1200 lines of code resources/js/wysiwyg/lexical/core/LexicalEditor.ts:1
- resources/js/wysiwyg/lexical/core/LexicalNode.ts: 1170 lines of code resources/js/wysiwyg/lexical/core/LexicalNode.ts:1
- resources/js/wysiwyg/lexical/core/LexicalUpdates.ts: 905 lines of code resources/js/wysiwyg/lexical/core/LexicalUpdates.ts:1
- resources/js/wysiwyg/lexical/table/LexicalTableUtils.ts: 810 lines of code resources/js/wysiwyg/lexical/table/LexicalTableUtils.ts:1
- resources/js/wysiwyg/lexical/core/LexicalReconciler.ts: 675 lines of code resources/js/wysiwyg/lexical/core/LexicalReconciler.ts:1
- resources/js/wysiwyg/lexical/rich-text/index.ts: 628 lines of code resources/js/wysiwyg/lexical/rich-text/index.ts:1
- resources/js/wysiwyg/lexical/core/nodes/LexicalElementNode.ts: 589 lines of code resources/js/wysiwyg/lexical/core/nodes/LexicalElementNode.ts:1
- resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts: 586 lines of code resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts:1
- resources/js/wysiwyg/lexical/utils/index.ts: 545 lines of code resources/js/wysiwyg/lexical/utils/index.ts:1
- resources/js/wysiwyg/lexical/clipboard/clipboard.ts: 535 lines of code resources/js/wysiwyg/lexical/clipboard/clipboard.ts:1
- resources/js/wysiwyg/lexical/selection/range-selection.ts: 532 lines of code resources/js/wysiwyg/lexical/selection/range-selection.ts:1
- resources/js/wysiwyg/lexical/link/index.ts: 513 lines of code resources/js/wysiwyg/lexical/link/index.ts:1
- resources/js/wysiwyg/lexical/yjs/Utils.ts: 500 lines of code resources/js/wysiwyg/lexical/yjs/Utils.ts:1
- resources/js/wysiwyg/lexical/yjs/SyncCursors.ts: 464 lines of code resources/js/wysiwyg/lexical/yjs/SyncCursors.ts:1
- resources/js/wysiwyg/lexical/list/formatList.ts: 458 lines of code resources/js/wysiwyg/lexical/list/formatList.ts:1
- resources/js/wysiwyg/lexical/history/index.ts: 428 lines of code resources/js/wysiwyg/lexical/history/index.ts:1
- resources/js/markdown/actions.ts: 424 lines of code resources/js/markdown/actions.ts:1
- resources/js/wysiwyg/lexical/list/LexicalListItemNode.ts: 410 lines of code resources/js/wysiwyg/lexical/list/LexicalListItemNode.ts:1
- Dead file (~666 LoC) resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts
- Dead file (~560 LoC) resources/js/wysiwyg/lexical/yjs/Utils.ts
- Dead file (~536 LoC) resources/js/wysiwyg/lexical/yjs/SyncCursors.ts
- Dead file (~490 LoC) resources/js/markdown/actions.ts
- Dead file (~329 LoC) resources/js/markdown/inputs/textarea.ts
- Dead file (~247 LoC) resources/js/wysiwyg/lexical/yjs/SyncEditorStates.ts
- Dead file (~178 LoC) resources/js/wysiwyg/lexical/yjs/CollabTextNode.ts
- Dead file (~141 LoC) resources/js/markdown/inputs/codemirror.ts
- Dead file (~116 LoC) resources/js/wysiwyg/lexical/yjs/index.ts
- Dead file (~115 LoC) resources/js/markdown/display.ts
- Dead file (~110 LoC) resources/js/wysiwyg/lexical/yjs/CollabDecoratorNode.ts
- Dead file (~87 LoC) resources/js/markdown/inputs/interface.ts
- Dead file (~82 LoC) resources/js/markdown/settings.ts
- Dead file (~78 LoC) resources/js/wysiwyg/lexical/yjs/Bindings.ts
- Dead file (~69 LoC) resources/js/markdown/index.mts
- Dead file (~68 LoC) resources/js/wysiwyg/lexical/yjs/CollabLineBreakNode.ts
- Dead file (~62 LoC) resources/js/markdown/dom-handlers.ts
- Dead file (~54 LoC) resources/js/markdown/codemirror.ts
- Dead file (~49 LoC) resources/js/wysiwyg/lexical/core/shared/simpleDiffWithCursor.ts
- Dead file (~43 LoC) resources/js/markdown/shortcuts.ts
- Dead file (~40 LoC) resources/js/markdown/common-events.ts
- Dead file (~36 LoC) resources/js/code/legacy-modes.mjs
- Dead file (~20 LoC) resources/js/wysiwyg/lexical/core/shared/warnOnlyOnce.ts
- Dead file (~15 LoC) resources/js/wysiwyg-tinymce/plugins-stub.js
- Dead file (~13 LoC) resources/js/wysiwyg/lexical/table/constants.ts
- Unused dependency '@lezer/generator'
- Unused dependency 'esbuild'
- Async function without AbortSignal: request resources/js/services/http.ts:80
Minor — 59 finding(s)
- redundant comment resources/js/components/entity-permissions.js:36
- redundant comment resources/js/components/image-manager.js:67
- redundant comment resources/js/components/image-manager.js:70
- redundant comment resources/js/components/image-manager.js:93
- redundant comment resources/js/components/page-editor.js:63
- redundant comment resources/js/components/pointer.ts:41
- redundant comment resources/js/components/pointer.ts:62
- redundant comment resources/js/components/template-manager.js:24
- redundant comment resources/js/components/template-manager.js:27
- redundant comment resources/js/markdown/shortcuts.ts:11
- redundant comment resources/js/markdown/shortcuts.ts:20
- redundant comment resources/js/wysiwyg-tinymce/plugins-tasklist.js:38
- redundant comment resources/js/wysiwyg/lexical/selection/__tests__/unit/LexicalSelection.test.ts:1489
- redundant comment resources/js/wysiwyg/services/shortcuts.ts:200
- redundant comment resources/js/wysiwyg/services/shortcuts.ts:202
- redundant comment resources/js/wysiwyg/ui/defaults/buttons/alignments.ts:22
- redundant comment resources/js/wysiwyg/ui/framework/manager.ts:281
- Duplicated predicate resources/js/markdown/dom-handlers.ts:52
- Duplicated predicate resources/js/markdown/actions.ts:405
- Duplicated predicate app/Entities/Controllers/ChapterController.php:202
- Duplicated predicate app/Entities/Controllers/BookController.php:182
- Duplicated predicate resources/views/entities/book-tree.blade.php:18
- Duplicated predicate resources/views/auth/login.blade.php:28
- Duplicated predicate app/References/ModelResolvers/ImageModelResolver.php:25
- Interpolated log message defeats structured logging app/Users/Controllers/UserController.php:103
- Interpolated log message defeats structured logging app/Uploads/ImageStorageDisk.php:99
- Interpolated log message defeats structured logging app/Activity/DispatchWebhookJob.php:69
- Interpolated log message defeats structured logging app/Activity/DispatchWebhookJob.php:73
- Interpolated log message defeats structured logging app/Activity/Notifications/Handlers/BaseNotificationHandler.php:45
- Interpolated log message defeats structured logging app/Access/LdapService.php:256
- Interpolated log message defeats structured logging app/Access/LdapService.php:486
- No named authorization policies
- Partial audit-trail evidence
- No ADRs found
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- Orphaned file resources/js/components/index.ts:1
- Rule about [anchor, focus] decided in 4 places
- Rule about [format, style] decided in 2 places
- No ADRs
- No architecture diagram/doc
- No dependency-update automation package.json:21
- No changelog
- Unused export 'getCurrentDay' resources/js/services/dates.ts:1
- Unused export 'INDENT_CONTENT_COMMAND' resources/js/wysiwyg/lexical/core/LexicalCommands.ts:87
- Unused export 'OUTDENT_CONTENT_COMMAND' resources/js/wysiwyg/lexical/core/LexicalCommands.ts:90
- Unused export 'IS_ALIGN_LEFT' resources/js/wysiwyg/lexical/core/LexicalConstants.ts:62
- Unused export 'IS_ALIGN_CENTER' resources/js/wysiwyg/lexical/core/LexicalConstants.ts:63
- Unused export 'IS_ALIGN_RIGHT' resources/js/wysiwyg/lexical/core/LexicalConstants.ts:64
- Unused export 'IS_ALIGN_JUSTIFY' resources/js/wysiwyg/lexical/core/LexicalConstants.ts:65
- Unused export 'IS_ALIGN_START' resources/js/wysiwyg/lexical/core/LexicalConstants.ts:66
- Unused export 'IS_ALIGN_END' resources/js/wysiwyg/lexical/core/LexicalConstants.ts:67
- Unused export 'ListenerType' resources/js/wysiwyg/lexical/core/LexicalEditor.ts:316
- Unused export 'TransformerType' resources/js/wysiwyg/lexical/core/LexicalEditor.ts:324
- Unused export '$getTextContent' resources/js/wysiwyg/lexical/core/LexicalSelection.ts:2744
- No security response headers detected REDACTED:1
- Not all async functions that make a request accept an AbortSignal
- PHP static analysis does not check null everywhere
Minor — 7 finding(s)
- Outdated: laravel/framework
- Outdated: laravel/socialite
- Outdated: league/commonmark
- Outdated: league/html-to-markdown
- Outdated: onelogin/php-saml
- Outdated: predis/predis
- doc comments repeat the names resources/js/components/auto-suggest.js:9
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e48a28df41da449d8675e80383763b41/history.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e48a28df41da449d8675e80383763b41/tree.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude public/libs/tinymce/icons --exclude public/libs/tinymce/models --exclude public/libs/tinymce/plugins --exclude public/libs/tinymce/themes . | 21 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 5 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 10 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 20 file(s) — `app/Access/Guards/ExternalBaseSessionGuard.php`, `app/App/helpers.php`, `app/Entities/Controllers/RecycleBinApiController.php`, `app/Entities/Repos/BaseRepo.php`, `app/Entities/Tools/SlugGenerator.php`, … (+15 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |