Public report of BookStackApp/BookStack, published 23 October 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 23 October 2026, 01:36 UTC · Survey ID cd_4d97f6fc9d94444f85f444e3f234a2ed

BookStackApp/BookStack

Measured 23 October 2026, 01:32 UTC, at code version 045c6a9

Regression: 2 dimensions fell since the last survey Code coverage: not measuredSupply-chain provenance & signing: not measured

A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.

Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureTestRunFailed).

Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.

CAI score 47out of 100 Weak
CriticalWeakAdequateStrongExemplary
Down 2 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

Performance 100 Exemplary Security and Compliance 72 Adequate Domain Modelling 64 Adequate Architecture 61 Adequate Maturity 54 Adequate Accessibility 48 Weak Code Health 46 Weak Production Readiness 43 Weak

A large codebase: 186,143 lines of product code in 1 project, tests not counted · Estimated rebuild effort: about 1.7 person-years · Weakest lens: Production Readiness, 43

Findings by how serious they are

104 critical 499 serious 59 minor

8 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
23 October 2026, 01:32 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that implements it, and today Watchdog is the only one that does.

The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

90of 93 dimensions measured by tools. The other 3 are advisory notes from an AI model, which explain the code but don't count towards the score.
638of 662 findings point to an exact file and line, so you can open each one in the code. The other 24 concern the repository as a whole, such as missing documentation.
93dimensions across 8 lenses, read from 186,143 lines of product code in 1 project.
Chapters

Executive summary

BookStackApp/BookStack scores 47 out of 100 and is rated Weak, while six of its eight lenses score higher still: Performance at 100, rated Exemplary, Security and Compliance at 72, Domain Modelling at 64, Architecture at 61 and Maturity at 54, all rated Adequate, and Accessibility at 48, rated Weak.

The score is lower than those six because the weakest lens counts most, and here that is Production Readiness, which scores 43 and is rated Weak. Its REDACTED Scanning dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 4 Leaked secret finding(s) in REDACTED Scanning and to resolve the 1 Banned license finding(s) in License Compliance, and if Production Readiness rose to 70, the score would rise from 47 to about 51.

104 findings are critical: 40 in Forms & labels, 21 in Static Analysis (SAST), 17 in Secrets (history), seven in Change Coupling, five in Text alternatives, four in REDACTED Scanning, three in Circular Imports, three in IaC & Container Security, two in Page structure, one in ARIA correctness and one in License Compliance.

Watchdog couldn't measure 6 dimensions in this code, among them Test Reliability, Collection changed while being enumerated and Incompleteness & stubs, so they are left out of the score. The product code is 186,143 lines, which would take an estimated 1.7 person-years, around €240,000, to rebuild.

Code Health 46 Weak, capped by Structured logging and Nullable reference types Architecture 61 Adequate, capped by Project Cohesion and Circular Imports Maturity 54 Adequate, capped by Architecture documentation Production Readiness 43 Weak, capped by REDACTED Scanning, Security & performance tooling and DR & Backup Security and Compliance 72 Adequate, capped by Secrets (history) Domain Modelling 64 Adequate, capped by Rich vs anemic model Accessibility 48 Weak, capped by Visual & motion safety Performance 100 ★ Exemplary

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

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 43 · counts for 45%Code Health 46 · counts for 25%Accessibility 48 · counts for 14%Maturity 54 · counts for 8%Architecture 61 · counts for 4%Domain Modelling 64 · counts for 2%Security and Compliance 72 · counts for 1%Performance 100 · counts for 1%

If Production Readiness rose from 43 to 70, the lowest score rated Strong, the score would rise from 47 to about 51.

Code composition: what the lines of code are
Product code 80%Tests 20%
New since the last survey: 191 findings

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

  • Code Coverage · Coverage not measured — JavaScript/TypeScript suite
  • REDACTED Scanning · REDACTED
  • REDACTED Scanning · REDACTED
  • REDACTED Scanning · REDACTED
  • 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

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

Fixed since the last survey: 71 findings

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

  • Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • IaC & Container Security · High IaC: REDACTED dev/docker/db-testing/Dockerfile
  • IaC & Container Security · Medium IaC: REDACTED dev/docker/db-testing/Dockerfile
  • IaC & Container Security · Medium IaC: REDACTED dev/docker/db-testing/Dockerfile
  • IaC & Container Security · Medium IaC: REDACTED dev/docker/db-testing/Dockerfile
  • IaC & Container Security · Medium IaC: REDACTED dev/docker/db-testing/Dockerfile
  • Change Coupling · Change coupling: UserApiTokenController.php ↔ REDACTED app/Api/UserApiTokenController.php
  • Change Coupling · Change coupling: UserApiTokenController.php ↔ edit.blade.php app/Api/UserApiTokenController.php
  • Supply-chain Provenance & Signing · REDACTED
  • Code Duplication · Duplicated block (12 lines × 2 locations) resources/js/wysiwyg/lexical/core/LexicalReconciler.ts
  • Code Duplication · Duplicated block (12 lines × 3 locations) resources/js/wysiwyg/lexical/core/LexicalSelection.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) resources/js/wysiwyg/lexical/history/index.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) resources/js/wysiwyg/lexical/link/index.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) resources/js/wysiwyg/lexical/list/LexicalListNode.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) resources/js/wysiwyg/lexical/rich-text/LexicalHeadingNode.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) resources/js/wysiwyg/lexical/rich-text/index.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts
  • Code Duplication · Duplicated block (11 lines × 3 locations) resources/js/components/entity-permissions.js
  • Code Duplication · Duplicated block (11 lines × 2 locations) resources/js/wysiwyg/lexical/core/LexicalSelection.ts
  • Code Duplication · Duplicated block (11 lines × 3 locations) resources/js/wysiwyg/lexical/core/LexicalSelection.ts
  • Code Duplication · Duplicated block (11 lines × 2 locations) resources/js/wysiwyg/lexical/core/LexicalUpdates.ts
  • Code Duplication · Duplicated block (11 lines × 2 locations) resources/js/wysiwyg/lexical/rich-text/LexicalDetailsNode.ts
  • Code Duplication · Duplicated block (11 lines × 3 locations) resources/js/wysiwyg/lexical/table/LexicalTableCellNode.ts
  • Code Duplication · Duplicated block (11 lines × 2 locations) resources/js/wysiwyg/lexical/table/LexicalTableObserver.ts
  • Code Duplication · Duplicated block (11 lines × 2 locations) resources/js/wysiwyg/lexical/table/LexicalTableObserver.ts
  • Code Duplication · Duplicated block (11 lines × 2 locations) resources/js/wysiwyg/lexical/table/LexicalTableUtils.ts
  • Code Duplication · Duplicated block (10 lines × 3 locations) resources/js/components/add-remove-rows.js
  • Code Duplication · Duplicated block with local edits (10 matched lines × 2 locations) resources/js/components/page-comment-reference.ts
  • Code Duplication · Duplicated block with local edits (10 matched lines × 2 locations) resources/js/wysiwyg/lexical/core/LexicalSelection.ts
  • Code Duplication · Duplicated block (10 lines × 2 locations) resources/js/wysiwyg/lexical/core/LexicalUtils.ts
  • Code Duplication · Duplicated block (10 lines × 2 locations) resources/js/wysiwyg/lexical/core/nodes/LexicalLineBreakNode.ts
  • Code Duplication · Duplicated block with local edits (10 matched lines × 2 locations) resources/js/wysiwyg/lexical/core/nodes/LexicalParagraphNode.ts
  • Code Duplication · Duplicated block (10 lines × 2 locations) resources/js/wysiwyg/lexical/rich-text/LexicalCalloutNode.ts
  • Code Duplication · Duplicated block (10 lines × 2 locations) resources/js/wysiwyg/lexical/selection/range-selection.ts
  • Code Duplication · Duplicated block (10 lines × 3 locations) resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts
  • Code Duplication · Duplicated block (10 lines × 2 locations) resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts
  • Code Duplication · Duplicated block (10 lines × 2 locations) resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts
  • Code Duplication · Duplicated block (10 lines × 2 locations) resources/js/wysiwyg/ui/decorators/CodeBlockDecorator.ts
  • Code Duplication · Duplicated block with local edits (9 matched lines × 2 locations) resources/js/services/keyboard-navigation.ts
  • Code Duplication · Duplicated block (9 lines × 2 locations) resources/js/wysiwyg-tinymce/drop-paste-handling.js
  • Code Duplication · Duplicated block (9 lines × 2 locations) resources/js/wysiwyg-tinymce/plugin-drawio.js
  • Code Duplication · Duplicated block (9 lines × 2 locations) resources/js/wysiwyg/lexical/core/LexicalSelection.ts
  • Code Duplication · Duplicated block (9 lines × 2 locations) resources/js/wysiwyg/lexical/link/index.ts
  • Code Duplication · Duplicated block (9 lines × 3 locations) resources/js/wysiwyg/lexical/rich-text/LexicalCalloutNode.ts
  • Code Duplication · Duplicated block (9 lines × 3 locations) resources/js/wysiwyg/lexical/table/LexicalTableUtils.ts
  • Code Duplication · Duplicated block (9 lines × 2 locations) resources/js/wysiwyg/lexical/table/LexicalTableUtils.ts
  • Code Duplication · Duplicated block (9 lines × 2 locations) resources/js/wysiwyg/lexical/utils/index.ts
  • Code Duplication · Duplicated block (8 lines × 6 locations) resources/js/components/add-remove-rows.js
  • Code Duplication · Duplicated block (8 lines × 3 locations) resources/js/components/add-remove-rows.js
  • Code Duplication · Duplicated block (8 lines × 5 locations) resources/js/components/attachments.js
  • Code Duplication · Duplicated block (8 lines × 9 locations) resources/js/components/attachments.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) resources/js/markdown/common-events.ts
  • Code Duplication · Duplicated block (8 lines × 2 locations) resources/js/services/animations.ts
  • Code Duplication · Duplicated block (8 lines × 2 locations) resources/js/wysiwyg/index.ts
  • Code Duplication · Duplicated block (8 lines × 2 locations) resources/js/wysiwyg/services/common-events.ts
  • Code Duplication · Duplicated block (7 lines × 4 locations) resources/js/components/add-remove-rows.js
  • Code Duplication · Duplicated block (7 lines × 11 locations) resources/js/components/attachments.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) resources/js/wysiwyg/lexical/clipboard/clipboard.ts
  • Code Duplication · Duplicated block with local edits (7 matched lines × 2 locations) resources/js/wysiwyg/lexical/list/formatList.ts
  • Code Duplication · Duplicated block (7 lines × 2 locations) resources/js/wysiwyg/utils/diagrams.ts
  • Code Duplication · Duplicated block (6 lines × 2 locations) resources/js/components/page-comments.ts
  • Code Duplication · Duplicated block (6 lines × 2 locations) resources/js/markdown/inputs/textarea.ts
  • Code Duplication · Duplicated block (5 lines × 2 locations) resources/js/wysiwyg/ui/defaults/toolbars.ts
  • Dependency Hygiene · Unused dependency 'chokidar-cli'
  • Forms & labels · <label> that labels no control resources/views/users/delete.blade.php
  • Forms & labels · <label> that labels no control resources/views/users/parts/form.blade.php
  • Forms & labels · <label> that labels no control resources/views/users/parts/form.blade.php
Rebuild cost: about €240,000 · Estimate
Cost to rebuild€80,000 to €400,000, for 1,341 to 4,255 hours of work, about 1.7 person-years for 1 to 4 engineers
Difficulty of the problemStandard, 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 47. 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.
SizeLarge: 186,143 lines of product code

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

Top priorities

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

1
Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED.
Raises the score by about 4 points · Low effort · REDACTED Scanning
2
Resolve the 1 Banned license finding(s) in License Compliance.
Raises the score by about 3 points · Low effort · License Compliance
3
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
Raises the score by about 3 points · Medium effort · DR & Backup

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €240,000 to build again, about 1.7 person-years of work. Its weakest lens is Production Readiness, at 43 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
One cause behind 39 Domain Modelling findings · Common cause
39 findings in the Domain Modelling lens come from the same cause. The code models the business as objects, such as an order or a customer, and each object should guard its own rules: an order, for example, should refuse to be shipped before it has been paid. Here the objects don't do that. Other code can change an object's data directly, so it can put an order into a state the rules forbid. Some objects only hold data, while the rules that should keep that data valid sit elsewhere in the code. Because all of these findings have the same cause, fixing it once, in the business objects themselves, deals with them together.
Based on: Encapsulated state (11 findings) · Rich vs anemic model (28 findings)
What to do: Give each business object the methods that enforce its rules, such as a method for shipping an order that first checks it has been paid, and let only those methods change its data. Give each kind of identifier a type of its own, so an order number can't be used where a customer number belongs.
If you do one thing first · First action
Resolve the 4 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for low effort, because it clears the 4 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

260 modules, with 534 dependencies between them. 4 loops run through 30 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 220 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 BookStack.Http2 BookStack.Util3 resources.js.components.component4 resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode5 resources.js.wysiwyg.lexical.core.nodes.common6 resources.js.wysiwyg.ui.framework.core7 BookStack.Users.Models8 resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode9 resources.js.wysiwyg.ui.framework.buttons10 BookStack.Permissions11 resources.js.wysiwyg.lexical.core.LexicalSelection12 BookStack.Activity13 BookStack.References14 BookStack.Uploads15 resources.js.wysiwyg.lexical.core.LexicalNode16 resources.js.wysiwyg.lexical.core.nodes17 BookStack.Entities.Repos18 resources.js.wysiwyg.lexical.core.LexicalEditor19 resources.js.wysiwyg.ui.framework.decorator20 BookStack.Entities.Tools21 resources.js.wysiwyg.lexical.core22 resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode23 resources.js.wysiwyg.lexical.table.LexicalTableCellNode24 resources.js.wysiwyg.lexical.yjs25 BookStack.Entities.Models26 BookStack.Users27 resources.js.wysiwyg.lexical.rich-text28 resources.js.wysiwyg.lexical.table.LexicalTableNode29 BookStack.Entities.Queries30 resources.js.wysiwyg.lexical.table31 resources.js.wysiwyg.utils32 BookStack.App33 BookStack.Activity.Models34 BookStack.Exports.ZipExports35 BookStack.Search36 BookStack.Access37 BookStack.Console.Commands38 BookStack.Exports39 BookStack.Access.Controllers40 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.Models32
8 resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode1
9 resources.js.wysiwyg.ui.framework.buttons1
10 BookStack.Permissions24262
11 resources.js.wysiwyg.lexical.core.LexicalSelection24
12 BookStack.Activity1122143
13 BookStack.References1111512
14 BookStack.Uploads131122
15 resources.js.wysiwyg.lexical.core.LexicalNode111
16 resources.js.wysiwyg.lexical.core.nodes321
17 BookStack.Entities.Repos242995
18 resources.js.wysiwyg.lexical.core.LexicalEditor1
19 resources.js.wysiwyg.ui.framework.decorator2
20 BookStack.Entities.Tools221325308
21 resources.js.wysiwyg.lexical.core459814
22 resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode11
23 resources.js.wysiwyg.lexical.table.LexicalTableCellNode111
24 resources.js.wysiwyg.lexical.yjs221
25 BookStack.Entities.Models1855
26 BookStack.Users1111
27 resources.js.wysiwyg.lexical.rich-text12
28 resources.js.wysiwyg.lexical.table.LexicalTableNode11
29 BookStack.Entities.Queries347
30 resources.js.wysiwyg.lexical.table113234
31 resources.js.wysiwyg.utils111349112
32 BookStack.App3111
33 BookStack.Activity.Models15
34 BookStack.Exports.ZipExports13510131
35 BookStack.Search212231
36 BookStack.Access101211
37 BookStack.Console.Commands31121211
38 BookStack.Exports224111
39 BookStack.Access.Controllers121215
40 BookStack.Users.Controllers8231252
Uses a module listed above itPart of a loopThe module itself
1 BookStack.Http2 BookStack.Util3 resources.js.components.component4 resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode5 resources.js.wysiwyg.lexical.core.nodes.common6 resources.js.wysiwyg.ui.framework.core7 BookStack.Users.Models8 resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode9 resources.js.wysiwyg.ui.framework.buttons10 BookStack.Permissions11 resources.js.wysiwyg.lexical.core.LexicalSelection12 BookStack.Activity13 BookStack.References14 BookStack.Uploads15 resources.js.wysiwyg.lexical.core.LexicalNode16 resources.js.wysiwyg.lexical.core.nodes17 BookStack.Entities.Repos18 resources.js.wysiwyg.lexical.core.LexicalEditor19 resources.js.wysiwyg.ui.framework.decorator20 BookStack.Entities.Tools21 resources.js.wysiwyg.lexical.core22 resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode23 resources.js.wysiwyg.lexical.table.LexicalTableCellNode24 resources.js.wysiwyg.lexical.yjs25 BookStack.Entities.Models26 BookStack.Users27 resources.js.wysiwyg.lexical.rich-text28 resources.js.wysiwyg.lexical.table.LexicalTableNode29 BookStack.Entities.Queries30 resources.js.wysiwyg.lexical.table31 resources.js.wysiwyg.utils32 BookStack.App33 BookStack.Activity.Models34 BookStack.Exports.ZipExports35 BookStack.Search36 BookStack.Access37 BookStack.Console.Commands38 BookStack.Exports39 BookStack.Access.Controllers40 BookStack.Users.ControllersBookStack.Http1BookStack.Util2resources.js.components.component3resources.js.wysiwyg.lexical.core.nodes.LexicalElementNode4resources.js.wysiwyg.lexical.core.nodes.common5resources.js.wysiwyg.ui.framework.core6BookStack.Users.Models7resources.js.wysiwyg.lexical.core.nodes.LexicalTextNode8resources.js.wysiwyg.ui.framework.buttons9BookStack.Permissions10resources.js.wysiwyg.lexical.core.LexicalSelection11BookStack.Activity12BookStack.References13BookStack.Uploads14resources.js.wysiwyg.lexical.core.LexicalNode15resources.js.wysiwyg.lexical.core.nodes16BookStack.Entities.Repos17resources.js.wysiwyg.lexical.core.LexicalEditor18resources.js.wysiwyg.ui.framework.decorator19BookStack.Entities.Tools20resources.js.wysiwyg.lexical.core21resources.js.wysiwyg.lexical.rich-text.LexicalHeadingNode22resources.js.wysiwyg.lexical.table.LexicalTableCellNode23resources.js.wysiwyg.lexical.yjs24BookStack.Entities.Models25BookStack.Users26resources.js.wysiwyg.lexical.rich-text27resources.js.wysiwyg.lexical.table.LexicalTableNode28BookStack.Entities.Queries29resources.js.wysiwyg.lexical.table30resources.js.wysiwyg.utils31BookStack.App32BookStack.Activity.Models33BookStack.Exports.ZipExports34BookStack.Search35BookStack.Access36BookStack.Console.Commands37BookStack.Exports38BookStack.Access.Controllers39BookStack.Users.Controllers403211242622411221431111512131122111321242995122213253084598141111122118551111121134711323411134911231111513510131212231101211311212112241111212158231252+220 more modules (most-connected shown)

At a glance — Code Health · 46% · Weak · gated by X4, X5 ·

The Good
D1 · PHP Cyclomatic Complexity 8.5 D3 · PHP God Classes 9.9 D4 · PHP Code Duplication 9.9 D17 · PHP Explicit Debt 10.0 R1 · React / TS Type Safety 7.7 R10 · React / TS Code Duplication 9.1 R2 · React / TS Cyclomatic Complexity 7.0 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0
The Bad
D2 · PHP Cognitive Complexity 6.8 R3 · React / TS Large Files 6.7 R7 · React / TS Dead Code 5.8 X3 · Repo Exception handling 6.2
The Ugly
X2 · Repo Cancellation propagation 4.0 X4 · Repo Structured logging 3.7 X5 · Repo Nullable reference types 2.0

At a glance — Architecture · 61% · Adequate · gated by D26, R9 ·

The Good
D6 · PHP Cohesion (LCOM4) 9.6 D23 · PHP Boundary Type-Coupling 8.6 D27 · PHP Navigability 9.2 D35 · PHP Change Coupling 9.8 AX10 · Repo Code composition 9.3 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX6 · Repo Interface segregation 10.0 R11 · React / TS Import Boundaries 9.6
The Ugly
D26 · PHP Project Cohesion 0.0 R9 · React / TS Circular Imports 0.0

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

The Good
D15 · PHP Churn × Complexity Hotspots 10.0 D19 · PHP Documentation Quality 9.0 D21 · PHP Naming Consistency 10.0 D34 · PHP Knowledge Freshness 10.0 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0
The Bad
M1 · Repo Documentation (README) 6.7
The Ugly
D20 · PHP ADR Quality 0.0 M2 · Repo Architecture documentation 0.0

At a glance — Readiness · 43% · Weak · gated by D13, P3, P5 ·

The Good
D9 · PHP Test Distribution 10.0 D10 · PHP Test Quality 10.0 D12 · PHP Dependency Hygiene 9.8 D14 · PHP License Compliance 8.0 P1 · Repo CI/CD gates 10.0 P2 · Repo Observability 7.0 P4 · Repo Deployment & Rollback 8.0 P7 · Repo Outbound HTTP resilience 10.0 P8 · Repo Schema migrations 10.0 R4 · React / TS Test Coverage 8.7 R5 · React / TS Dependency Freshness 9.6 R6 · React / TS Tooling 10.0 R8 · React / TS Dependency Hygiene 9.0
The Bad
P6 · Repo Release Hygiene 5.0
The Ugly
D13 · PHP REDACTED Scanning 0.0 P3 · Repo Security & performance tooling 3.0 P5 · Repo DR & Backup 0.0

At a glance — Security · 72% · Adequate · gated by D28 ·

The Good
D29 · PHP Static Analysis (SAST) 8.4 D30 · PHP Dependency Vulnerabilities 10.0 D31 · PHP IaC & Container Security 8.3 D37 · PHP Vulnerability-disclosure Policy 10.0 D43 · PHP Malicious Dependencies 10.0 D44 · PHP Platform End-of-Life 10.0 C2 · Repo Access Controls 7.0 C3 · Repo Audit Trail 7.5 S1 · Repo Web-Security Posture 8.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0
The Bad
C1 · Repo Data Protection 6.5
The Ugly
D28 · PHP Secrets (history) 0.0 X17 · Repo Uncapped recursion over a caller-supplied document 3.5 X24 · Repo Document value interpolated into markup unescaped 3.1

At a glance — Domain Modelling · 64% · Adequate · gated by DM4 ·

The Good
DM1 · Repo Aggregate boundaries 10.0 DM10 · Repo One transaction, one aggregate 10.0 DM11 · Repo Constructible invalid state 10.0 DM8 · Repo Value-object opportunities 10.0 DM9 · Repo Scattered domain decisions 9.2
The Ugly
DM4 · Repo Rich vs anemic model 3.2 DM5 · Repo Encapsulated state 4.5

At a glance — Accessibility · 48% · Weak · gated by AC6 ·

The Good
AC5 · Repo ARIA correctness 7.7
The Bad
AC2 · Repo Forms & labels 6.3 AC3 · Repo Page structure 6.0
The Ugly
AC1 · Repo Text alternatives 4.8 AC6 · Repo Visual & motion safety 3.8 AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 100% · Exemplary ·

The Good
PF3 · Repo Async & latency hygiene 10.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A07:2025 — Authentication Failures22High / Critical
A05:2025 — Injection21High / Critical
A02:2025 — Security Misconfiguration10High / Critical

Roadmap

Immediately resolve the four leaked secrets in configuration and service files, and address the single banned license violation to secure the codebase. Establish a robust disaster recovery strategy by codifying backups and geo-recovery in infrastructure as code, while ensuring SAST scans gate pull requests rather than running on a schedule. Finally, maintain a clear changelog to document release contents and improve overall release hygiene.

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

Do thisHelpsEffortDimension
Resolve the 4 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED.+3.9 ptsLowREDACTED Scanning
Resolve the 1 Banned license finding(s) in License Compliance.+2.6 ptsLowLicense Compliance
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.+3.1 ptsMediumDR & Backup
Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate.+2.2 ptsMediumSecurity & performance tooling
Resolve the 1 No ADRs found finding(s) in ADR Quality.+1.0 ptsLowADR Quality
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.+1.6 ptsMediumRelease 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 ptsMediumNullable reference types
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.+1.0 ptsMediumArchitecture documentation

File quality

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

FileScoreBandWorst signal
REDACTED1.5SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED2.5SlopStatic Analysis (SAST): High: REDACTED
app/Entities/Controllers/BookController.php2.5SlopChange Coupling: Boundary-crossing change coupling: BookController.php ↔ edit.blade.php
REDACTED3.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.5SlopIaC & Container Security: High IaC: REDACTED
REDACTED3.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.1MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.1MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.5MixedSecrets (history): High secret: REDACTED
REDACTED5.1MixedSecrets (history): High secret: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedSecrets (history): High secret: REDACTED
REDACTED5.8MixedSecrets (history): High secret: REDACTED
REDACTED5.8MixedSecrets (history): High secret: REDACTED
app/Sorting/BookSorter.php5.9MixedCyclomatic Complexity: BookSorter.isSortChangePermissible (cyclomatic 28)
app/Exports/ZipExports/ZipImportRunner.php5.9MixedCyclomatic Complexity: ZipImportRunner.ensurePermissionsPermitImport (cyclomatic 19)

How the grades work

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

Critical — 104

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 499

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 59

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 8

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

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

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

What we checked — 93 dimensions across the health lenses
D1D2D3D4D6D9D10D12D13D14D15D17D19D20D21D23D26D27D28D29D30D31D34D35D37D43D44AC1AC2AC3AC5AC6AC7AX10AX3AX4AX6C1C2C3DM1DM10DM11DM4DM5DM8DM9M1M2M3M4P1P2P3P4P5P6P7P8PF3R1R10R11R2R3R4R5R6R7R8R9S1X1X12X13X14X15X16X17X18X19X2X21X22X23X24X25X28X29X3X30X4X5

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

How to trust any code-health report — three questions
  1. 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, 638 of 662 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

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

Tools & methods

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

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a16663-428c-77ce-b1ba-b6d3a636f736.

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

Run transparency — what happened this run

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

  • D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 5628 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.
  • 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.
  • D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 3 further occurrence(s) are not listed individually; the score already reflects all 43.
  • AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads 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.
  • AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — node Pulling db Pulling mailhog Pulling db Error Get "https://registry-1.docker.io/v2/": Forbidden node Error Get "https://registry-1.docker.io/v2/": Forbidden mailhog Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: app Skipped - No image to be pulled db Pulling node Pulling mailhog Pulling db Error Get "https://registry-1.docker.io/v2/": Forbidden node Error Get "https://registry-1.docker.io/v2/": Forbidden mailhog Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
  • DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
  • DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's 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.
  • R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 41 further occurrence(s) are not listed individually; the score already reflects all 81.
  • X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and 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.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • 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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • 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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • 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.

The LLM boundary

LLM-set scores this run (3): D19, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity8.5 / 10Strong✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

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

10 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was BookSorter.isSortChangePermissible at 28.

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

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

What to do

  1. Bring the 10 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 10 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.
  2. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D2 · Cognitive Complexity6.8 / 10Adequate✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

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

14 method(s) exceeded the cognitive complexity threshold of 15; the worst was SrcsetAttrDef.parseImageSources at 111.

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

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

What to do

  1. 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.
  2. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D3 · God Classes9.9 / 10Stronggated by 2 serious findings✓ Tool-verified

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

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

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

2 god class(es) detected.

TooManyMethods: Entity · ×2app/Entities/Models/Entity.php:55

What to do

  1. 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).
  2. Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D4 · Code Duplication9.9 / 10Stronggated by 34 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

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

32 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.

Duplicated block (7 lines × 2) · ×5app/Activity/Tools/EntityWatchers.php:74
Duplicated block (9 lines × 2) · ×4app/Entities/Controllers/BookApiController.php:132
Duplicated block (8 lines × 2) · ×4app/Entities/Controllers/PageController.php:284
Duplicated block (12 lines × 2) · ×3app/Entities/Controllers/BookController.php:172
Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2app/Activity/Notifications/Messages/CommentCreationNotification.php:17

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

What to do

  1. 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).
  2. 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).
  3. 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).
  4. Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

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

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

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

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

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

6 of 188 classes have LCOM4 above 3.

Low cohesion: User (LCOM4 7) · ×6app/Users/Models/User.php:48

What to do

  1. 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).
  2. Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

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

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

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

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

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.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

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

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.

✓ On the Gold path — maintain.

Detailed fixes: d10_recommendation.md.

D12 · Dependency Hygiene9.8 / 10Exemplary✓ Tool-verified

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

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

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

4 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.

Outdated: laravel/framework · ×4

✓ On the Gold path — maintain.

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

D13 · REDACTED Scanning0.0 / 10Critical✓ Tool-verified

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

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

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

4 secret(s) detected.

REDACTED

What to do

  1. 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).
  2. Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D14 · License Compliance8.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

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.

Banned license: dompdf/php-svg-lib

What to do

  1. Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
  2. Enforce License Compliance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D15 · Churn × Complexity Hotspots10.0 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

Top hotspots: app/Util/HtmlPurifier/SrcsetAttrDef.php (2×23=46)

Hotspot: app/Util/HtmlPurifier/SrcsetAttrDef.phpapp/Util/HtmlPurifier/SrcsetAttrDef.php:57

What to do

  1. Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with SrcsetAttrDef.php. — One of this dimension's main actionable groups (1 warning-level).

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

D17 · Explicit Debt10.0 / 10Stronggated by 2 serious findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

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

2 deducted task-comment markers across 186143 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.

TodoComment · ×2app/Entities/Controllers/PageRevisionController.php:79

What to do

  1. 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).
  2. Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D19 · Documentation QualityExemplary◐ Sampled · advisory

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

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

The repository's root README (bookstack) and its subdirectories are all well written: the bookstack README states what the project is for, links to the official site, and lists installation, documentation, a demo instance, and screenshots. The resources/views/readme.md README documents views in the resources/views/ directory rather than the repository, so it is not judged on the root-level overview; similarly for the dev/docker/db-testing/, public/libs/tinymce/langs/, and resources/js/wysiwyg/lexical/ directories. The main document with the most scope is the dev/docs/development.md file, which covers installation (Node.js v22+), building CSS & JS assets, automated app testing, code standards (PHP_CodeSniffer, PHPStan, ESLint), and a full development requirements list; it also links to companion documents like javascript-code.md and php-testing.md. The architecture/design docs are present as markdown files but not shown in the summary, so they fall outside visible scope and cannot be flagged. The repository's documentation is comprehensive and well-structured across READMEs and architecture/Docs markdown files. The Portable ZIP File Format document gives an overview of the format with a Stability section that explains when changes are considered breaking, plus a full outline; Release Versioning & Process covers versioning, milestone planning, announcements, and release steps; Theme System Modules documents module location, format, metadata, and customization order; Visual Theme System guides getting started, view/file overriding, icon/customization; WYSIWYG JS API explains the post-init event, UI modules, createButton, getMainToolbar, and insertHtml. All sections are present in the outline and the document is clipped mid-sentence.

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

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

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

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

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

No architecture decision records were found.

No ADRs found

What to do

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

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

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

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

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

D23 · Boundary Type-Coupling8.6 / 10Strong✓ Tool-verified

What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.

Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.

Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.

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

132 domain type(s) cross context boundaries across 12 contexts.

Cross-context type User (Users → Access) · ×31app/Access/EmailConfirmationService.php:22
Cross-context type User (Users → Activity) · ×15app/Activity/ActivityQueries.php:86
Cross-context type Entity (Entities → Sorting) · ×10app/Sorting/SortSetOperationComparisons.php:15
Cross-context type Entity (Entities → Activity) · ×9app/Activity/ActivityQueries.php:49
Cross-context type Page (Entities → Exports) · ×7app/Exports/ExportFormatter.php:34

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

What to do

  1. Resolve the 31 Cross-context type User (Users → Access) finding(s) in Boundary Type-Coupling — start with REDACTED (5), MfaSession.php (4), MfaVerificationLimiter.php (3). — One of this dimension's main actionable groups (31 warning-level).
  2. Resolve the 15 Cross-context type User (Users → Activity) finding(s) in Boundary Type-Coupling — start with WebhookFormatter.php (2), ActivityQueries.php, CommentCreationNotificationHandler.php. — One of this dimension's main actionable groups (15 warning-level).
  3. Resolve the 10 Cross-context type Entity (Entities → Sorting) finding(s) in Boundary Type-Coupling — start with SortSetOperationComparisons.php (10). — One of this dimension's main actionable groups (10 warning-level).
  4. Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D26 · Project Cohesion0.0 / 10Critical✓ Tool-verified

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

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

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

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

Projects may be oversized for their cohesion

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

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

D27 · Navigability9.2 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

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

39 % of calls cross a namespace and 1 % go through an interface, but 60 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)0.0 / 10Critical✓ Tool-verified

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

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

17 finding(s): 0 critical, 17 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 16 High secret finding(s) in Secrets (history) — start with REDACTED (6), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (16 issue-level).
  2. Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

D29 · Static Analysis (SAST)8.4 / 10Adequategated by 21 critical findings✓ Tool-verified

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

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

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

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

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.

REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. 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).

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

D30 · Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

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

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

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

No known-vulnerable dependencies in any ecosystem this repository declares.

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

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

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

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

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

10 finding(s): 0 critical, 3 high, 7 medium, 0 low.

REDACTED
REDACTED

What to do

  1. 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).
  2. 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).

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

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

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

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 1103 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned files with no living knowledge
Orphaned fileresources/js/components/index.ts:1

✓ On the Gold path — maintain.

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

D35 · Change Coupling9.8 / 10Adequategated by 7 critical findings✓ Tool-verified

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

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

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

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

Strongest change-coupling: OidcService.php↔oidc.php 87%; ChapterRepo.php↔PageRepo.php 81%; index.blade.php↔index.blade.php 80%

Boundary-crossing change coupling: OidcService.php ↔ oidc.php · ×7app/Access/Oidc/OidcService.php:1
Change coupling: ChapterRepo.php ↔ PageRepo.php · ×14app/Entities/Repos/ChapterRepo.php:1
Change coupling clique: common.php, common.php, common.phplang/de/common.php

What to do

  1. 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).
  2. Resolve the 14 Change coupling finding(s) in Change Coupling — start with index.blade.php (2), BookController.php (2), ChapterRepo.php. — One of this dimension's main actionable groups (14 warning-level).
  3. 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).

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

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

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

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

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 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.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

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

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

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

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

  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×5) — 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 & labels6.3 / 10Adequate✓ Tool-verified

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

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

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

  • This 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 structure6.0 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • 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 correctness7.7 / 10Strong✓ Tool-verified

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

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

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

  • 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 safety3.8 / 10Weak✓ Tool-verified

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

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

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

  • `.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 enforcement4.0 / 10Weak✓ Tool-verified

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

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

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

  • No accessibility enforcement found — no a11y linter (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 307 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

  • Enforce accessibility in the toolchain: add 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 composition9.3 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

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

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

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

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

C1 · Data Protection6.5 / 10Adequate✓ Tool-verified

Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.

Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.

  • 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/Config/app.php:162

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 Controls7.0 / 10Strong✓ Tool-verified

Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.

Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.

  • 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 Trail7.5 / 10Strong✓ Tool-verified

Other · Security — Whether changes to sensitive data are recorded (who, what, when) for compliance + incident response.

Method: Roslyn scan: audit-trail mechanism graded (SaveChanges interceptor/immutable AuditLog/[Audited] strong; bare IAuditable/AddAuditing weak). Deterministic.

  • 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 boundaries10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.

Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.

Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.

DM10 · One transaction, one aggregate10.0 / 10Exemplary○ Nothing flagged

Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.

Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.

DM11 · Constructible invalid state10.0 / 10Exemplary○ Nothing flagged

Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.

Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule), on a type that also offers no static Create/Of/From/New factory. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.

DM4 · Rich vs anemic model3.2 / 10Weak✓ Tool-verified

Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.

Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.

Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.

  • `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:32
  • `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 state4.5 / 10Weak✓ Tool-verified

Other · Domain Modelling — Whether entities protect their state — private/init-only setters, and collections handed out as read-only views rather than the mutable backing collection — instead of exposing writable state that bypasses invariants. Softened when a rehydration framework (Marten/EF) is present.

Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.

Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.

  • `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).
DM8 · Value-object opportunities10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.

Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.

DM9 · Scattered domain decisions9.2 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.

Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.

  • 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)6.7 / 10Adequate✓ Tool-verified

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

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

What to do

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

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

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

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

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

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

M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

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

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

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

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

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

P2 · Observability7.0 / 10Strong✓ Tool-verified

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

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

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 tooling3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • `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.

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 & Rollback8.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

What to do

  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

  • 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 Hygiene5.0 / 10Adequate✓ Tool-verified

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

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

  • 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 resilience10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.

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

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

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

R1 · Type Safety7.7 / 10Strong✓ Tool-verified

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

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

What to do

  • Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication9.1 / 10Exemplary✓ Tool-verified

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

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

  • 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 Boundaries9.6 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).

Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.

  • 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 Complexity7.0 / 10Strong✓ Tool-verified

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

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

  • 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 Files6.7 / 10Adequate✓ Tool-verified

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

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

  • 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 Coverage8.7 / 10Strong✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • 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 Freshness9.6 / 10Exemplary✓ Tool-verified

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

What to do

  • Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

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

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

R7 · Dead Code5.8 / 10Adequate✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

  • 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 Hygiene9.0 / 10Exemplary✓ Tool-verified

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

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

  • 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 Imports0.0 / 10Critical✓ Tool-verified

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

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

  • 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 Posture8.0 / 10Strong✓ Tool-verified

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

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

  • None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `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 correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

X17 · Uncapped recursion over a caller-supplied document3.5 / 10Weak✓ Tool-verified

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

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

  • `$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 correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

X2 · Cancellation propagation4.0 / 10Weak✓ Tool-verified

Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

  • Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch) 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 guard10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

X24 · Document value interpolated into markup unescaped3.1 / 10Weak✓ Tool-verified

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

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

  • `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 knob10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

X3 · Exception handling6.2 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • 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) — app/Access/Controllers/Saml2Controller.php:109, database/migrations/2018_08_04_115700_create_bookshelves_table.php:26, resources/js/wysiwyg/lexical/clipboard/clipboard.ts:161, …
  • `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/Entities/Tools/EntityCover.php:59, app/Uploads/ImageRepo.php:231, app/Users/Models/User.php:235
  • `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/Exceptions/BookStackExceptionHandlerPage.php:24, app/Settings/StatusController.php:49

What to do

  • Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

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

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

X4 · Structured logging3.7 / 10Weak✓ Tool-verified

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

  • `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
  • `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
  • `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 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

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether PHP's static analysis checks null and is not undermined by a nullness baseline — PHPStan from level 8 (`checkNullables`) or Psalm at `errorLevel` 3 or stricter is what makes `?User` a type whose method call is an error, and the null entries of a baseline, `@psalm-suppress PossiblyNull…` and `@phpstan-ignore *.nonObject` are what silence it.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • 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

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

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only
AC7 · A11y enforcementenforcement — no page criterionEnforcement posture (process)

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

Reference — by lens

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

LensScoreRatingImpact
Code Health46%Weak — gated by X4, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture61%Adequate — gated by D26, R9Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity54%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness43%Weak — gated by D13, P3, P5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security72%Adequate — gated by D28Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling64%Adequate — gated by DM4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility48%Weak — gated by AC6Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored — 2 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • D36 Supply-chain Provenance & Signing — 8 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). 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 — 21 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

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • 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 — 45 check(s) not relevant to this codebase

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

  • 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
  • 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 18 — an image could not be pulled) — node Pulling db Pulling mailhog Pulling db Error Get "https://registry-1.docker.io/v2/": Forbidden node Error Get "https://registry-1.docker.io/v2/": Forbidden mailhog Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: app Skipped - No image to be pulled db Pulling node Pulling mailhog Pulling db Error Get "https://registry-1.docker.io/v2/": Forbidden node Error Get "https://registry-1.docker.io/v2/": Forbidden mailhog Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; 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.
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D24 Comment Value — No inline comments to assess — comment value is not applicable here.
  • D25 ADR Conformance — no ADRs to check
  • 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)
  • 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 applicable: PHP and TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • 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.
  • 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)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 104 finding(s)
AC2 · Forms & labels · <label> that labels no control · ×26
  • <label> that labels no control resources/views/books/parts/form.blade.php:14 — 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.
  • <label> that labels no control resources/views/exports/import-show.blade.php:12 — 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.
  • <label> that labels no control resources/views/exports/import-show.blade.php:22 — 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.
  • <label> that labels no control resources/views/exports/import-show.blade.php:47 — 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.
  • <label> that labels no control resources/views/settings/categories/customization.blade.php:42 — 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.
  • <label> that labels no control resources/views/settings/categories/customization.blade.php:59 — 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.
  • <label> that labels no control resources/views/settings/categories/customization.blade.php:81 — 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.
  • <label> that labels no control resources/views/settings/categories/features.blade.php:33 — 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.
  • <label> that labels no control resources/views/settings/categories/features.blade.php:47 — 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.
  • <label> that labels no control resources/views/settings/categories/registration.blade.php:12 — 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.
  • <label> that labels no control resources/views/settings/categories/registration.blade.php:59 — 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.
  • <label> that labels no control resources/views/settings/categories/sorting.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.
  • <label> that labels no control resources/views/settings/roles/parts/form.blade.php:5 — 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.
  • <label> that labels no control resources/views/settings/roles/parts/form.blade.php:30 — 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.
  • <label> that labels no control resources/views/settings/roles/parts/form.blade.php:58 — 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.
  • <label> that labels no control resources/views/settings/sort-rules/parts/form.blade.php:4 — 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.
  • <label> that labels no control resources/views/settings/sort-rules/parts/form.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.
  • <label> that labels no control resources/views/settings/webhooks/edit.blade.php:15 — 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.
  • <label> that labels no control resources/views/settings/webhooks/parts/form.blade.php:5 — 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.
  • <label> that labels no control resources/views/settings/webhooks/parts/form.blade.php:33 — 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.
  • <label> that labels no control resources/views/shelves/parts/form.blade.php:63 — 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.
  • <label> that labels no control resources/views/users/account/delete.blade.php:20 — 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.
  • <label> that labels no control resources/views/users/api-tokens/edit.blade.php:18 — 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.
  • <label> that labels no control resources/views/users/api-tokens/edit.blade.php:30 — 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.
  • <label> that labels no control resources/views/users/api-tokens/parts/form.blade.php:5 — 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.
  • + 1 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D28 · Secrets (history) · High secret · ×16
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <input> without a programmatic label · ×11
  • <input> without a programmatic label resources/views/mfa/parts/verify-backup_codes.blade.php:7 — 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.
  • <input> without a programmatic label resources/views/mfa/parts/verify-totp.blade.php:7 — 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.
  • <input> without a programmatic label resources/views/pages/parts/template-manager.blade.php:15 — 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.
  • <input> without a programmatic label resources/views/search/all.blade.php:16 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label resources/views/search/all.blade.php:78 — 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.
  • <input> without a programmatic label resources/views/search/parts/date-filter.blade.php:14 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label resources/views/search/parts/term-list.blade.php:13 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label resources/views/settings/webhooks/index.blade.php:26 — 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.
  • <input> without a programmatic label resources/views/shelves/parts/form.blade.php:48 — 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.
  • <input> without a programmatic label resources/views/tags/index.blade.php:16 — 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.
  • <input> without a programmatic label resources/views/users/api-tokens/edit.blade.php:34 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
D35 · Change Coupling · Boundary-crossing change coupling · ×7
  • Boundary-crossing change coupling: OidcService.php ↔ oidc.php app/Access/Oidc/OidcService.php:1 — `app/Access/Oidc/OidcService.php` (context Access) and `app/Config/oidc.php` (context Config) sit in DIFFERENT parts of the tree yet change together 87% of the time (13 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `30bf0ce6` OIDC: Updated avatar fetching to run on each login; `f9dbbe5d` OIDC: Updated picture fetch implementation during review; `da82e70c` Add optional OIDC avatar fetching from the “picture” claim — run `git show` on any of them.
  • Boundary-crossing change coupling: BookController.php ↔ edit.blade.php app/Entities/Controllers/BookController.php:1 — `app/Entities/Controllers/BookController.php` (context Entities) and `resources/views/books/edit.blade.php` (context resources) sit in DIFFERENT parts of the tree yet change together 73% of the time (11 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `d61f42a3` Default Templates: Started review and updates from PR code; `1dbc3588` Add default_template as Book setting (at that commit the file was still `app/Http/Controllers/BookController.php`); `8c67011a` Got book to shelf conversions working (at that commit the file was still `app/Http/Controllers/BookController.php`) — run `git show` on any of them.
  • Boundary-crossing change coupling: ApiController.php ↔ api.php app/Http/ApiController.php:1 — `app/Http/ApiController.php` (context Http) and `routes/api.php` (context routes) sit in DIFFERENT parts of the tree yet change together 69% of the time (9 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `f14fc68b` API: Added new tags API endpoints; `73025719` ZIP Imports: Added API test cases; `723f108b` Aded roles API controller methods (at that commit the file was still `app/Http/Controllers/Api/ApiController.php`) — run `git show` on any of them.
  • Boundary-crossing change coupling: ActivityType.php ↔ activities.php app/Activity/ActivityType.php:1 — `app/Activity/ActivityType.php` (context Activity) and `lang/en/activities.php` (context lang) sit in DIFFERENT parts of the tree yet change together 69% of the time (9 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `39a14cff` User MFA: Reviewed addition of reset, added tests; `b897af2e` Sorting: Finished main sort set CRUD work; `c6109c70` ZIP Imports: Added listing, show view, delete, activity — run `git show` on any of them.
  • Boundary-crossing change coupling: BookController.php ↔ create.blade.php app/Entities/Controllers/BookController.php:1 — `app/Entities/Controllers/BookController.php` (context Entities) and `resources/views/books/create.blade.php` (context resources) sit in DIFFERENT parts of the tree yet change together 62% of the time (10 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `d61f42a3` Default Templates: Started review and updates from PR code; `1dbc3588` Add default_template as Book setting (at that commit the file was still `app/Http/Controllers/BookController.php`); `79f6dc00` Change image-selector to not use manager (at that commit the file was still `app/Http/Controllers/BookController.php`) — run `git show` on any of them.
  • Boundary-crossing change coupling: ActivityType.php ↔ web.php app/Activity/ActivityType.php:1 — `app/Activity/ActivityType.php` (context Activity) and `routes/web.php` (context routes) sit in DIFFERENT parts of the tree yet change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `39a14cff` User MFA: Reviewed addition of reset, added tests; `c6109c70` ZIP Imports: Added listing, show view, delete, activity; `8c67011a` Got book to shelf conversions working (at that commit the file was still `app/Actions/ActivityType.php`) — run `git show` on any of them.
  • Boundary-crossing change coupling: REDACTED ↔ form.blade.php lang/en/settings.php:1 — `lang/en/settings.php` (context lang) and `resources/views/settings/roles/parts/form.blade.php` (context resources) sit in DIFFERENT parts of the tree yet change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `befa3a8f` Permissions: Started addition of revision-view permission; `51f9b63d` Comment Mentions: Fixed and tweaks during review of changes; `4051d5b8` ZIP Exports: Added new import permission — run `git show` on any of them.
AC1 · Text alternatives · <img> without a text alternative · ×5
  • <img> without a text alternative resources/views/misc/opensearch.blade.php:5 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative resources/views/misc/opensearch.blade.php:6 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative resources/views/misc/opensearch.blade.php:7 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative resources/views/misc/opensearch.blade.php:8 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative resources/views/misc/opensearch.blade.php:9 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
D13 · REDACTED Scanning · Leaked secret · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <select> without a programmatic label · ×3
  • <select> without a programmatic label resources/views/api-docs/index.blade.php:13 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label resources/views/form/role-select.blade.php:2 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label resources/views/users/account/parts/display-mode-option-row.blade.php:13 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
D31 · IaC & Container Security · High IaC · ×3
  • REDACTED
  • REDACTED
  • REDACTED
AC3 · Page structure · Viewport restricts zoom · ×2
  • Viewport restricts zoom resources/views/api-docs/download.blade.php:5 — 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.
  • Viewport restricts zoom resources/views/errors/debug.blade.php:5 — 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.
R9 · Circular Imports · Import cycle (2 files) · ×2
  • Import cycle (2 files) resources/js/wysiwyg/ui/framework/core.ts:2 — 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)
  • Import cycle (2 files) resources/js/wysiwyg/lexical/yjs/CollabDecoratorNode.ts:17 — 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)
AC5 · ARIA correctness · aria-expanded on a <div> with no role to carry it · ×1
  • aria-expanded on a <div> with no role to carry it resources/views/form/user-select.blade.php:5 — 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.
D14 · License Compliance · Banned license · ×1
  • Banned license: dompdf/php-svg-lib — `dompdf/php-svg-lib` 1.0.2 is in the production `packages` list of this repository's composer.lock — what a `composer install --no-dev` puts in vendor/ — and every licence it declares is one this policy bans (`LGPL-3.0-or-later`). Where a package declares several licences it is charged only when all of them are banned. Replace the package, or record an accepted exception.
D28 · Secrets (history) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
R9 · Circular Imports · Import cycle (3 files) · ×1
  • Import cycle (3 files) resources/js/wysiwyg/lexical/core/LexicalEditor.ts:22 — 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)
Serious — 499 finding(s)
R4 · Test Coverage · No test reaches this file · ×34
  • No test reaches this file resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts:1 — 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.
  • No test reaches this file resources/js/wysiwyg/lexical/yjs/Utils.ts:1 — 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.
  • No test reaches this file resources/js/wysiwyg/lexical/yjs/SyncCursors.ts:1 — 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.
  • No test reaches this file resources/js/markdown/actions.ts:1 — 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.
  • No test reaches this file resources/js/markdown/inputs/textarea.ts:1 — 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.
  • No test reaches this file resources/js/wysiwyg/lexical/yjs/SyncEditorStates.ts:1 — 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.
  • No test reaches this file resources/js/code/index.mjs:1 — 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.
  • No test reaches this file resources/js/wysiwyg/lexical/yjs/CollabTextNode.ts:1 — 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.
  • No test reaches this file resources/js/services/components.ts:1 — 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.
  • No test reaches this file resources/js/markdown/inputs/codemirror.ts:1 — 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.
  • No test reaches this file resources/js/code/themes.js:1 — 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.
  • No test reaches this file resources/js/code/languages.js:1 — 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.
  • No test reaches this file resources/js/wysiwyg/lexical/yjs/index.ts:1 — 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.
  • No test reaches this file resources/js/markdown/display.ts:1 — 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.
  • No test reaches this file resources/js/wysiwyg/lexical/yjs/CollabDecoratorNode.ts:1 — 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.
  • No test reaches this file resources/js/services/events.ts:1 — 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.
  • No test reaches this file resources/js/code/setups.js:1 — 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.
  • No test reaches this file resources/js/markdown/settings.ts:1 — 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.
  • No test reaches this file resources/js/wysiwyg/lexical/yjs/Bindings.ts:1 — 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.
  • No test reaches this file resources/js/markdown/index.mts:1 — 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.
  • No test reaches this file resources/js/wysiwyg/lexical/yjs/CollabLineBreakNode.ts:1 — 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.
  • No test reaches this file resources/js/markdown/dom-handlers.ts:1 — 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.
  • No test reaches this file resources/js/markdown/codemirror.ts:1 — 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.
  • No test reaches this file resources/js/code/views.js:1 — 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.
  • No test reaches this file resources/js/wysiwyg/lexical/core/shared/simpleDiffWithCursor.ts:1 — 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.
  • + 9 more in this group — see findings.md.
D23 · Boundary Type-Coupling · Cross-context type User (Users → Access) · ×31
  • Cross-context type User (Users → Access) app/Access/EmailConfirmationService.php:22 — User (context Users) is exposed in Access's public surface via EmailConfirmationService.sendConfirmation — couples the contexts.
  • Cross-context type User (Users → Access) app/Access/ExternalBaseUserProvider.php:51 — User (context Users) is exposed in Access's public surface via ExternalBaseUserProvider.retrieveByCredentials — couples the contexts.
  • Cross-context type User (Users → Access) app/Access/GroupSyncService.php:73 — User (context Users) is exposed in Access's public surface via GroupSyncService.syncUserWithFoundGroups — couples the contexts.
  • Cross-context type User (Users → Access) app/Access/LdapService.php:466 — User (context Users) is exposed in Access's public surface via LdapService.syncGroups — couples the contexts.
  • Cross-context type User (Users → Access) app/Access/LdapService.php:476 — User (context Users) is exposed in Access's public surface via LdapService.saveAndAttachAvatar — couples the contexts.
  • Cross-context type User (Users → Access) REDACTED:38 — User (context Users) is exposed in Access's public surface via LoginService.login — couples the contexts.
  • Cross-context type User (Users → Access) REDACTED:69 — User (context Users) is exposed in Access's public surface via LoginService.reattemptLoginFor — couples the contexts.
  • Cross-context type User (Users → Access) REDACTED:84 — User (context Users) is exposed in Access's public surface via LoginService.getLastLoginAttemptUser — couples the contexts.
  • Cross-context type User (Users → Access) REDACTED:139 — User (context Users) is exposed in Access's public surface via LoginService.needsMfaVerification — couples the contexts.
  • Cross-context type User (Users → Access) REDACTED:147 — User (context Users) is exposed in Access's public surface via LoginService.awaitingEmailConfirmation — couples the contexts.
  • Cross-context type User (Users → Access) app/Access/Mfa/MfaSession.php:12 — User (context Users) is exposed in Access's public surface via MfaSession.isRequiredForUser — couples the contexts.
  • Cross-context type User (Users → Access) app/Access/Mfa/MfaSession.php:21 — User (context Users) is exposed in Access's public surface via MfaSession.isPendingMfaSetup — couples the contexts.
  • Cross-context type User (Users → Access) app/Access/Mfa/MfaSession.php:39 — User (context Users) is exposed in Access's public surface via MfaSession.isVerifiedForUser — couples the contexts.
  • Cross-context type User (Users → Access) app/Access/Mfa/MfaSession.php:47 — User (context Users) is exposed in Access's public surface via MfaSession.markVerifiedForUser — couples the contexts.
  • Cross-context type User (Users → Access) app/Access/Mfa/MfaValue.php:39 — User (context Users) is exposed in Access's public surface via MfaValue.upsertWithValue — couples the contexts.
  • Cross-context type User (Users → Access) app/Access/Mfa/MfaValue.php:53 — User (context Users) is exposed in Access's public surface via MfaValue.getValueForUser — couples the contexts.
  • Cross-context type User (Users → Access) app/Access/Mfa/MfaVerificationLimiter.php:35 — User (context Users) is exposed in Access's public surface via MfaVerificationLimiter.incrementAttempts — couples the contexts.
  • Cross-context type User (Users → Access) app/Access/Mfa/MfaVerificationLimiter.php:41 — User (context Users) is exposed in Access's public surface via MfaVerificationLimiter.decrementAttempts — couples the contexts.
  • Cross-context type User (Users → Access) app/Access/Mfa/MfaVerificationLimiter.php:47 — User (context Users) is exposed in Access's public surface via MfaVerificationLimiter.hasHitLimit — couples the contexts.
  • Cross-context type User (Users → Access) app/Access/Mfa/TotpService.php:39 — User (context Users) is exposed in Access's public surface via TotpService.generateUrl — couples the contexts.
  • Cross-context type User (Users → Access) app/Access/Notifications/ConfirmEmailNotification.php:16 — User (context Users) is exposed in Access's public surface via ConfirmEmailNotification.toMail — couples the contexts.
  • Cross-context type User (Users → Access) app/Access/Notifications/ResetPasswordNotification.php:16 — User (context Users) is exposed in Access's public surface via ResetPasswordNotification.toMail — couples the contexts.
  • Cross-context type User (Users → Access) app/Access/Notifications/UserInviteNotification.php:16 — User (context Users) is exposed in Access's public surface via UserInviteNotification.toMail — couples the contexts.
  • Cross-context type User (Users → Access) app/Access/Oidc/OidcService.php:73 — User (context Users) is exposed in Access's public surface via OidcService.processAuthorizeResponse — couples the contexts.
  • Cross-context type User (Users → Access) app/Access/RegistrationService.php:53 — User (context Users) is exposed in Access's public surface via RegistrationService.findOrRegister — couples the contexts.
  • + 6 more in this group — see findings.md.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×30
  • Untrusted text written into markup unescaped resources/js/code/index.mjs:64 — `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.
  • Untrusted text written into markup unescaped resources/js/components/ajax-form.js:66 — `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.
  • Untrusted text written into markup unescaped resources/js/components/ajax-form.js:71 — `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.
  • Untrusted text written into markup unescaped resources/js/components/attachments.js: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.
  • Untrusted text written into markup unescaped resources/js/components/attachments.js:80 — `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.
  • Untrusted text written into markup unescaped resources/js/components/code-editor.js:205 — `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.
  • Untrusted text written into markup unescaped resources/js/components/dropdown-search.js:57 — `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.
  • Untrusted text written into markup unescaped resources/js/components/entity-search.js:44 — `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.
  • Untrusted text written into markup unescaped resources/js/components/entity-selector.ts:141 — `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.
  • Untrusted text written into markup unescaped resources/js/components/entity-selector.ts:159 — `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.
  • Untrusted text written into markup unescaped resources/js/components/image-manager.js:187 — `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.
  • Untrusted text written into markup unescaped resources/js/components/image-manager.js:192 — `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.
  • Untrusted text written into markup unescaped resources/js/components/image-manager.js:274 — `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.
  • Untrusted text written into markup unescaped resources/js/components/page-comment-reference.ts:202 — `(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.
  • Untrusted text written into markup unescaped resources/js/components/page-editor.js:56 — `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.
  • Untrusted text written into markup unescaped resources/js/components/template-manager.js:77 — `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.
  • Untrusted text written into markup unescaped resources/js/components/template-manager.js:86 — `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.
  • Untrusted text written into markup unescaped resources/js/components/user-select.js:17 — `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.
  • Untrusted text written into markup unescaped resources/js/services/dom.ts:176 — `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.
  • Untrusted text written into markup unescaped resources/js/services/vdom.ts:26 — `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.
  • Untrusted text written into markup unescaped resources/js/wysiwyg-tinymce/config.js:167 — `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.
  • Untrusted text written into markup unescaped resources/js/wysiwyg-tinymce/plugin-codeeditor.js:103 — `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.
  • Untrusted text written into markup unescaped resources/js/wysiwyg-tinymce/plugins-details.js:237 — `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.
  • Untrusted text written into markup unescaped resources/js/wysiwyg/ui/decorators/MentionDecorator.ts:99 — `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.
  • Untrusted text written into markup unescaped resources/js/wysiwyg/ui/framework/blocks/color-picker.ts:68 — `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.
  • + 5 more in this group — see findings.md.
DM4 · Rich vs anemic model · Anemic entity · ×28
  • Anemic entity: SocialAccount app/Access/SocialAccount.php:15 — `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.
  • Anemic entity: Comment app/Activity/Models/Comment.php:30 — `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.
  • Anemic entity: Favourite app/Activity/Models/Favourite.php:11 — `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.
  • Anemic entity: MentionHistory app/Activity/Models/MentionHistory.php:17 — `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.
  • Anemic entity: Tag app/Activity/Models/Tag.php:19 — `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.
  • Anemic entity: Watch app/Activity/Models/Watch.php:22 — `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.
  • Anemic entity: Webhook app/Activity/Models/Webhook.php:23 — `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.
  • Anemic entity: WebhookTrackedEvent app/Activity/Models/WebhookTrackedEvent.php:13 — `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.
  • Anemic entity: ApiToken app/Api/ApiToken.php:22 — `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.
  • Anemic entity: Book app/Entities/Models/Book.php:29 — `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.
  • Anemic entity: Bookshelf app/Entities/Models/Bookshelf.php:15 — `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.
  • Anemic entity: Chapter app/Entities/Models/Chapter.php:16 — `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.
  • Anemic entity: Deletion app/Entities/Models/Deletion.php:19 — `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.
  • Anemic entity: EntityContainerData app/Entities/Models/EntityContainerData.php:17 — `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.
  • Anemic entity: EntityPageData app/Entities/Models/EntityPageData.php:10 — `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.
  • Anemic entity: EntityTable app/Entities/Models/EntityTable.php:19 — `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.
  • Anemic entity: Page app/Entities/Models/Page.php:31 — `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.
  • Anemic entity: PageRevision app/Entities/Models/PageRevision.php:32 — `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.
  • Anemic entity: SlugHistory app/Entities/Models/SlugHistory.php:17 — `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.
  • Anemic entity: Import app/Exports/Import.php:27 — `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.
  • Anemic entity: EntityPermission app/Permissions/Models/EntityPermission.php:19 — `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.
  • Anemic entity: JointPermission app/Permissions/Models/JointPermission.php:11 — `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.
  • Anemic entity: Reference app/References/Reference.php:16 — `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.
  • Anemic entity: SearchTerm app/Search/SearchTerm.php:7 — `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.
  • Anemic entity: Setting app/Settings/Setting.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.
  • + 3 more in this group — see findings.md.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×15
  • Animation without a prefers-reduced-motion guard resources/sass/_animations.scss:20 — `.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.
  • Animation without a prefers-reduced-motion guard resources/sass/_animations.scss:66 — `.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.
  • Animation without a prefers-reduced-motion guard resources/sass/_components.scss:22 — `.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.
  • Animation without a prefers-reduced-motion guard resources/sass/_components.scss:229 — `.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.
  • Animation without a prefers-reduced-motion guard resources/sass/_components.scss:288 — `.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.
  • Animation without a prefers-reduced-motion guard resources/sass/_components.scss:289 — `.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.
  • Animation without a prefers-reduced-motion guard resources/sass/_components.scss:297 — `.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.
  • Animation without a prefers-reduced-motion guard resources/sass/_components.scss:327 — `.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.
  • Animation without a prefers-reduced-motion guard resources/sass/_layout.scss:505 — `.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.
  • Animation without a prefers-reduced-motion guard resources/sass/_lists.scss:332 — `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.
  • Animation without a prefers-reduced-motion guard resources/sass/_pages.scss:137 — `.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.
  • Animation without a prefers-reduced-motion guard resources/sass/_pages.scss:301 — `.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.
  • Animation without a prefers-reduced-motion guard resources/sass/_pages.scss:334 — `.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.
  • Animation without a prefers-reduced-motion guard resources/sass/styles.scss:83 — `.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.
  • Animation without a prefers-reduced-motion guard resources/sass/styles.scss:251 — `.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.
D23 · Boundary Type-Coupling · Cross-context type User (Users → Activity) · ×15
  • Cross-context type User (Users → Activity) app/Activity/ActivityQueries.php:86 — User (context Users) is exposed in Activity's public surface via ActivityQueries.userActivity — couples the contexts.
  • Cross-context type User (Users → Activity) app/Activity/Notifications/Handlers/CommentCreationNotificationHandler.php:17 — User (context Users) is exposed in Activity's public surface via CommentCreationNotificationHandler.handle — couples the contexts.
  • Cross-context type User (Users → Activity) app/Activity/Notifications/Handlers/CommentMentionNotificationHandler.php:20 — User (context Users) is exposed in Activity's public surface via CommentMentionNotificationHandler.handle — couples the contexts.
  • Cross-context type User (Users → Activity) app/Activity/Notifications/Handlers/NotificationHandler.php:16 — User (context Users) is exposed in Activity's public surface via NotificationHandler.handle — couples the contexts.
  • Cross-context type User (Users → Activity) app/Activity/Notifications/Handlers/PageCreationNotificationHandler.php:15 — User (context Users) is exposed in Activity's public surface via PageCreationNotificationHandler.handle — couples the contexts.
  • Cross-context type User (Users → Activity) app/Activity/Notifications/Handlers/PageUpdateNotificationHandler.php:17 — User (context Users) is exposed in Activity's public surface via PageUpdateNotificationHandler.handle — couples the contexts.
  • Cross-context type User (Users → Activity) app/Activity/Notifications/Messages/BaseActivityNotification.php:20 — User (context Users) is exposed in Activity's public surface via BaseActivityNotification.__construct — couples the contexts.
  • Cross-context type User (Users → Activity) app/Activity/Notifications/Messages/CommentCreationNotification.php:14 — User (context Users) is exposed in Activity's public surface via CommentCreationNotification.toMail — couples the contexts.
  • Cross-context type User (Users → Activity) app/Activity/Notifications/Messages/CommentMentionNotification.php:14 — User (context Users) is exposed in Activity's public surface via CommentMentionNotification.toMail — couples the contexts.
  • Cross-context type User (Users → Activity) app/Activity/Notifications/Messages/PageCreationNotification.php:13 — User (context Users) is exposed in Activity's public surface via PageCreationNotification.toMail — couples the contexts.
  • Cross-context type User (Users → Activity) app/Activity/Notifications/Messages/PageUpdateNotification.php:13 — User (context Users) is exposed in Activity's public surface via PageUpdateNotification.toMail — couples the contexts.
  • Cross-context type User (Users → Activity) app/Activity/Notifications/NotificationManager.php:22 — User (context Users) is exposed in Activity's public surface via NotificationManager.handle — couples the contexts.
  • Cross-context type User (Users → Activity) app/Activity/Tools/UserEntityWatchOptions.php:18 — User (context Users) is exposed in Activity's public surface via UserEntityWatchOptions.__construct — couples the contexts.
  • Cross-context type User (Users → Activity) app/Activity/Tools/WebhookFormatter.php:27 — User (context Users) is exposed in Activity's public surface via WebhookFormatter.__construct — couples the contexts.
  • Cross-context type User (Users → Activity) app/Activity/Tools/WebhookFormatter.php:119 — User (context Users) is exposed in Activity's public surface via WebhookFormatter.getDefault — couples the contexts.
D35 · Change Coupling · Change coupling · ×14
  • Change coupling: ChapterRepo.php ↔ PageRepo.php app/Entities/Repos/ChapterRepo.php:1 — `app/Entities/Repos/ChapterRepo.php` and `app/Entities/Repos/PageRepo.php` change together 81% of the time (13 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `291a807d` Slugs: Added slug recording at points of generation; `a70c733f` Permissions: Cleanup after review of enum implementation PR; `47fd578e` Perms: Added transactions around permission effecting actions — run `git show` on any of them.
  • Change coupling: index.blade.php ↔ index.blade.php resources/views/books/index.blade.php:1 — `resources/views/books/index.blade.php` and `resources/views/shelves/index.blade.php` change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `9b4f1fb9` Styles: Aligned empty state alignment & consistency; `78b64500` Distributed shortcut actions to common ui elements; `ec4cbbd0` Refactored common list handling operations to new class — run `git show` on any of them.
  • Change coupling: create.blade.php ↔ form.blade.php resources/views/books/create.blade.php:1 — `resources/views/books/create.blade.php` and `resources/views/books/parts/form.blade.php` change together 69% of the time (11 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `d61f42a3` Default Templates: Started review and updates from PR code; `1dbc3588` Add default_template as Book setting; `4b9618cd` Update book form so cancel URL is explicitly passed in (at that commit the file was still `resources/views/books/form.blade.php`) — run `git show` on any of them.
  • Change coupling: edit.blade.php ↔ form.blade.php resources/views/books/edit.blade.php:1 — `resources/views/books/edit.blade.php` and `resources/views/books/parts/form.blade.php` change together 67% of the time (10 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `d61f42a3` Default Templates: Started review and updates from PR code; `1dbc3588` Add default_template as Book setting; `4b9618cd` Update book form so cancel URL is explicitly passed in (at that commit the file was still `resources/views/books/form.blade.php`) — run `git show` on any of them.
  • Change coupling: BookController.php ↔ ChapterController.php app/Entities/Controllers/BookController.php:1 — `app/Entities/Controllers/BookController.php` and `app/Entities/Controllers/ChapterController.php` change together 66% of the time (39 of the 59 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 39 shared commits counted here, the most recent 3 are `c9081698` Slugs: Rolled out history lookup to other types; `47fd578e` Perms: Added transactions around permission effecting actions; `307fae39` Input WYSIWYG: Added reference store & fetch handling — run `git show` on any of them.
  • Change coupling: page-comment.ts ↔ comment.blade.php resources/js/components/page-comment.ts:1 — `resources/js/components/page-comment.ts` and `resources/views/comments/comment.blade.php` change together 65% of the time (13 of the 20 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `c82fa332` Comments: Further range of content reference ux improvements; `099f6104` Comments: Started archive display, created mode for tree node; `8bdf9487` Comments: Added archive endpoints, messages, Js actions and tests — run `git show` on any of them.
  • Change coupling: ChapterController.php ↔ PageController.php app/Entities/Controllers/ChapterController.php:1 — `app/Entities/Controllers/ChapterController.php` and `app/Entities/Controllers/PageController.php` change together 64% of the time (38 of the 59 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 38 shared commits counted here, the most recent 3 are `70bfebcd` Added Default Templates for Chapters; `307fae39` Input WYSIWYG: Added reference store & fetch handling; `45ce7a71` URL Handling: Removed referrer-based redirect handling — run `git show` on any of them.
  • Change coupling: index.blade.php ↔ list.blade.php resources/views/books/index.blade.php:1 — `resources/views/books/index.blade.php` and `resources/views/books/parts/list.blade.php` change together 62% of the time (8 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `9b4f1fb9` Styles: Aligned empty state alignment & consistency; `ec4cbbd0` Refactored common list handling operations to new class; `60d175a9` Cleaned up sidebar book tree and moved details (at that commit the file was still `resources/views/books/list.blade.php`) — run `git show` on any of them.
  • Change coupling: BookApiController.php ↔ BookshelfApiController.php app/Entities/Controllers/BookApiController.php:1 — `app/Entities/Controllers/BookApiController.php` and `app/Entities/Controllers/BookshelfApiController.php` change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `7e1a8e5e` API: Added cover to book/shelf list endpoints; `00ae04e0` Input WYSIWYG: Updated API to show/accept html descriptions; `0e94fd44` Added contents to book-show endpoint (at that commit the files were still `app/Http/Controllers/Api/BookApiController.php` and `app/Http/Controllers/Api/BookshelfApiController.php`) — run `git show` on any of them.
  • Change coupling: entity-selector.ts ↔ selector.blade.php resources/js/components/entity-selector.ts:1 — `resources/js/components/entity-selector.ts` and `resources/views/entities/selector.blade.php` change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `7ebe7d4e` Default templates: Added page picker and working forms (at that commit the file was still `resources/js/components/entity-selector.js`); `b6497387` Made book-sort changes based on screen reader testing (at that commit the file was still `resources/js/components/entity-selector.js`); `c9d0e221` Updated entity-selector-popup to reset on selection (at that commit the file was still `resources/js/components/entity-selector.js`) — run `git show` on any of them.
  • Change coupling: Bookshelf.php ↔ Chapter.php app/Entities/Models/Bookshelf.php:1 — `app/Entities/Models/Bookshelf.php` and `app/Entities/Models/Chapter.php` change together 56% of the time (10 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `081069cb` Laravel 13: Updated ordered relations with delete modifier; `00ae04e0` Input WYSIWYG: Updated API to show/accept html descriptions; `307fae39` Input WYSIWYG: Added reference store & fetch handling — run `git show` on any of them.
  • Change coupling: BookRepo.php ↔ BookshelfRepo.php app/Entities/Repos/BookRepo.php:1 — `app/Entities/Repos/BookRepo.php` and `app/Entities/Repos/BookshelfRepo.php` change together 53% of the time (9 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `47fd578e` Perms: Added transactions around permission effecting actions; `d676e1e8` Started work on hierachy conversion actions; `90797001` Refactored the activity service — run `git show` on any of them.
  • Change coupling: BookController.php ↔ BookshelfController.php app/Entities/Controllers/BookController.php:1 — `app/Entities/Controllers/BookController.php` and `app/Entities/Controllers/BookshelfController.php` change together 52% of the time (23 of the 44 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 23 shared commits counted here, the most recent 3 are `10f5ceee` List page settings: Review of #5606; `c9081698` Slugs: Rolled out history lookup to other types; `b6110ed3` Add settings for number of books/shelves that will be displayed per page — run `git show` on any of them.
  • Change coupling: tri-layout.ts ↔ tri.blade.php resources/js/components/tri-layout.ts:1 — `resources/js/components/tri-layout.ts` and `resources/views/layouts/tri.blade.php` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `9186e77d` Layout: Added scroll fade to the sidebars (at that commit the file was still `resources/js/components/tri-layout.js`); `9df4dee1` Improved header element accessibility when at mobile sizes (at that commit the files were still `resources/js/components/tri-layout.js` and `resources/views/tri-layout.blade.php`); `8d358e48` Updated tri-layout on mobile to be tab based (at that commit the files were still `resources/assets/js/components/tri-layout.js` and `resources/views/tri-layout.blade.php`) — run `git show` on any of them.
DM5 · Encapsulated state · Mutable entity · ×11
  • Mutable entity: Book app/Entities/Models/Book.php:29 — `Book` exposes publicly writable state (searchFactor).
  • Mutable entity: Bookshelf app/Entities/Models/Bookshelf.php:15 — `Bookshelf` exposes publicly writable state (searchFactor).
  • Mutable entity: Chapter app/Entities/Models/Chapter.php:16 — `Chapter` exposes publicly writable state (searchFactor).
  • Mutable entity: Entity app/Entities/Models/Entity.php:55 — `Entity` exposes publicly writable state (textField, htmlField, searchFactor, commonFields).
  • Mutable entity: EntityContainerData app/Entities/Models/EntityContainerData.php:17 — `EntityContainerData` exposes publicly writable state (timestamps, incrementing, fields).
  • Mutable entity: EntityPageData app/Entities/Models/EntityPageData.php:10 — `EntityPageData` exposes publicly writable state (timestamps, incrementing, fields).
  • Mutable entity: Page app/Entities/Models/Page.php:31 — `Page` exposes publicly writable state (textField, htmlField).
  • Mutable entity: EntityPermission app/Permissions/Models/EntityPermission.php:19 — `EntityPermission` exposes publicly writable state (timestamps).
  • Mutable entity: JointPermission app/Permissions/Models/JointPermission.php:11 — `JointPermission` exposes publicly writable state (timestamps).
  • Mutable entity: Reference app/References/Reference.php:16 — `Reference` exposes publicly writable state (timestamps).
  • Mutable entity: SearchTerm app/Search/SearchTerm.php:7 — `SearchTerm` exposes publicly writable state (timestamps).
D23 · Boundary Type-Coupling · Cross-context type Entity (Entities → Sorting) · ×10
  • Cross-context type Entity (Entities → Sorting) app/Sorting/SortSetOperationComparisons.php:15 — Entity (context Entities) is exposed in Sorting's public surface via SortSetOperationComparisons.nameAsc — couples the contexts.
  • Cross-context type Entity (Entities → Sorting) app/Sorting/SortSetOperationComparisons.php:20 — Entity (context Entities) is exposed in Sorting's public surface via SortSetOperationComparisons.nameDesc — couples the contexts.
  • Cross-context type Entity (Entities → Sorting) app/Sorting/SortSetOperationComparisons.php:25 — Entity (context Entities) is exposed in Sorting's public surface via SortSetOperationComparisons.nameNumericAsc — couples the contexts.
  • Cross-context type Entity (Entities → Sorting) app/Sorting/SortSetOperationComparisons.php:38 — Entity (context Entities) is exposed in Sorting's public surface via SortSetOperationComparisons.nameNumericDesc — couples the contexts.
  • Cross-context type Entity (Entities → Sorting) app/Sorting/SortSetOperationComparisons.php:43 — Entity (context Entities) is exposed in Sorting's public surface via SortSetOperationComparisons.createdDateAsc — couples the contexts.
  • Cross-context type Entity (Entities → Sorting) app/Sorting/SortSetOperationComparisons.php:48 — Entity (context Entities) is exposed in Sorting's public surface via SortSetOperationComparisons.createdDateDesc — couples the contexts.
  • Cross-context type Entity (Entities → Sorting) app/Sorting/SortSetOperationComparisons.php:53 — Entity (context Entities) is exposed in Sorting's public surface via SortSetOperationComparisons.updatedDateAsc — couples the contexts.
  • Cross-context type Entity (Entities → Sorting) app/Sorting/SortSetOperationComparisons.php:58 — Entity (context Entities) is exposed in Sorting's public surface via SortSetOperationComparisons.updatedDateDesc — couples the contexts.
  • Cross-context type Entity (Entities → Sorting) app/Sorting/SortSetOperationComparisons.php:63 — Entity (context Entities) is exposed in Sorting's public surface via SortSetOperationComparisons.chaptersFirst — couples the contexts.
  • Cross-context type Entity (Entities → Sorting) app/Sorting/SortSetOperationComparisons.php:68 — Entity (context Entities) is exposed in Sorting's public surface via SortSetOperationComparisons.chaptersLast — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type Entity (Entities → Activity) · ×9
  • Cross-context type Entity (Entities → Activity) app/Activity/ActivityQueries.php:49 — Entity (context Entities) is exposed in Activity's public surface via ActivityQueries.entityActivity — couples the contexts.
  • Cross-context type Entity (Entities → Activity) app/Activity/CommentRepo.php:44 — Entity (context Entities) is exposed in Activity's public surface via CommentRepo.create — couples the contexts.
  • Cross-context type Entity (Entities → Activity) app/Activity/Notifications/MessageParts/EntityLinkMessageLine.php:14 — Entity (context Entities) is exposed in Activity's public surface via EntityLinkMessageLine.__construct — couples the contexts.
  • Cross-context type Entity (Entities → Activity) app/Activity/TagRepo.php:132 — Entity (context Entities) is exposed in Activity's public surface via TagRepo.saveTagsToEntity — couples the contexts.
  • Cross-context type Entity (Entities → Activity) app/Activity/Tools/ActivityLogger.php:64 — Entity (context Entities) is exposed in Activity's public surface via ActivityLogger.removeEntity — couples the contexts.
  • Cross-context type Entity (Entities → Activity) app/Activity/Tools/EntityWatchers.php:23 — Entity (context Entities) is exposed in Activity's public surface via EntityWatchers.__construct — couples the contexts.
  • Cross-context type Entity (Entities → Activity) app/Activity/Tools/TagClassGenerator.php:13 — Entity (context Entities) is exposed in Activity's public surface via TagClassGenerator.__construct — couples the contexts.
  • Cross-context type Entity (Entities → Activity) app/Activity/Tools/UserEntityWatchOptions.php:18 — Entity (context Entities) is exposed in Activity's public surface via UserEntityWatchOptions.__construct — couples the contexts.
  • Cross-context type Entity (Entities → Activity) app/Activity/WatchLevels.php:55 — Entity (context Entities) is exposed in Activity's public surface via WatchLevels.allSuitedFor — couples the contexts.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×8
  • Focus outline removed in CSS without a :focus replacement resources/sass/_codemirror.scss:68 — `.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.
  • Focus outline removed in CSS without a :focus replacement resources/sass/_components.scss:143 — `.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.
  • Focus outline removed in CSS without a :focus replacement resources/sass/_components.scss:556 — `.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.
  • Focus outline removed in CSS without a :focus replacement resources/sass/_components.scss:573 — `.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.
  • Focus outline removed in CSS without a :focus replacement resources/sass/_editor.scss:45 — `.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.
  • Focus outline removed in CSS without a :focus replacement resources/sass/_forms.scss:70 — `#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.
  • Focus outline removed in CSS without a :focus replacement resources/sass/_tinymce.scss:25 — `.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.
  • Focus outline removed in CSS without a :focus replacement resources/sass/_tinymce.scss:33 — `.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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D23 · Boundary Type-Coupling · Cross-context type Page (Entities → Exports) · ×7
  • Cross-context type Page (Entities → Exports) app/Exports/ExportFormatter.php:34 — Page (context Entities) is exposed in Exports's public surface via ExportFormatter.pageToContainedHtml — couples the contexts.
  • Cross-context type Page (Entities → Exports) app/Exports/ExportFormatter.php:93 — Page (context Entities) is exposed in Exports's public surface via ExportFormatter.pageToPdf — couples the contexts.
  • Cross-context type Page (Entities → Exports) app/Exports/ExportFormatter.php:248 — Page (context Entities) is exposed in Exports's public surface via ExportFormatter.pageToPlainText — couples the contexts.
  • Cross-context type Page (Entities → Exports) app/Exports/ExportFormatter.php:295 — Page (context Entities) is exposed in Exports's public surface via ExportFormatter.pageToMarkdown — couples the contexts.
  • Cross-context type Page (Entities → Exports) app/Exports/ZipExports/Models/ZipExportPage.php:39 — Page (context Entities) is exposed in Exports's public surface via ZipExportPage.fromModel — couples the contexts.
  • Cross-context type Page (Entities → Exports) app/Exports/ZipExports/ZipExportBuilder.php:28 — Page (context Entities) is exposed in Exports's public surface via ZipExportBuilder.buildForPage — couples the contexts.
  • Cross-context type Page (Entities → Exports) app/Exports/ZipExports/ZipImportReferences.php:61 — Page (context Entities) is exposed in Exports's public surface via ZipImportReferences.addPage — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type Chapter (Entities → Exports) · ×7
  • Cross-context type Chapter (Entities → Exports) app/Exports/ExportFormatter.php:52 — Chapter (context Entities) is exposed in Exports's public surface via ExportFormatter.chapterToContainedHtml — couples the contexts.
  • Cross-context type Chapter (Entities → Exports) app/Exports/ExportFormatter.php:111 — Chapter (context Entities) is exposed in Exports's public surface via ExportFormatter.chapterToPdf — couples the contexts.
  • Cross-context type Chapter (Entities → Exports) app/Exports/ExportFormatter.php:258 — Chapter (context Entities) is exposed in Exports's public surface via ExportFormatter.chapterToPlainText — couples the contexts.
  • Cross-context type Chapter (Entities → Exports) app/Exports/ExportFormatter.php:307 — Chapter (context Entities) is exposed in Exports's public surface via ExportFormatter.chapterToMarkdown — couples the contexts.
  • Cross-context type Chapter (Entities → Exports) app/Exports/ZipExports/Models/ZipExportChapter.php:38 — Chapter (context Entities) is exposed in Exports's public surface via ZipExportChapter.fromModel — couples the contexts.
  • Cross-context type Chapter (Entities → Exports) app/Exports/ZipExports/ZipExportBuilder.php:41 — Chapter (context Entities) is exposed in Exports's public surface via ZipExportBuilder.buildForChapter — couples the contexts.
  • Cross-context type Chapter (Entities → Exports) app/Exports/ZipExports/ZipImportReferences.php:68 — Chapter (context Entities) is exposed in Exports's public surface via ZipImportReferences.addChapter — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type Book (Entities → Exports) · ×7
  • Cross-context type Book (Entities → Exports) app/Exports/ExportFormatter.php:74 — Book (context Entities) is exposed in Exports's public surface via ExportFormatter.bookToContainedHtml — couples the contexts.
  • Cross-context type Book (Entities → Exports) app/Exports/ExportFormatter.php:134 — Book (context Entities) is exposed in Exports's public surface via ExportFormatter.bookToPdf — couples the contexts.
  • Cross-context type Book (Entities → Exports) app/Exports/ExportFormatter.php:274 — Book (context Entities) is exposed in Exports's public surface via ExportFormatter.bookToPlainText — couples the contexts.
  • Cross-context type Book (Entities → Exports) app/Exports/ExportFormatter.php:326 — Book (context Entities) is exposed in Exports's public surface via ExportFormatter.bookToMarkdown — couples the contexts.
  • Cross-context type Book (Entities → Exports) app/Exports/ZipExports/Models/ZipExportBook.php:53 — Book (context Entities) is exposed in Exports's public surface via ZipExportBook.fromModel — couples the contexts.
  • Cross-context type Book (Entities → Exports) app/Exports/ZipExports/ZipExportBuilder.php:54 — Book (context Entities) is exposed in Exports's public surface via ZipExportBuilder.buildForBook — couples the contexts.
  • Cross-context type Book (Entities → Exports) app/Exports/ZipExports/ZipImportReferences.php:75 — Book (context Entities) is exposed in Exports's public surface via ZipImportReferences.addBook — couples the contexts.
D31 · IaC & Container Security · Medium IaC · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
R10 · Code Duplication · Duplicated block (13 lines × 2 locations) · ×7
  • Duplicated block (13 lines × 2 locations) resources/js/services/dom.ts:21 — 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.
  • Duplicated block (13 lines × 2 locations) resources/js/wysiwyg/lexical/core/LexicalReconciler.ts:611 — 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.
  • Duplicated block (13 lines × 2 locations) resources/js/wysiwyg/lexical/core/LexicalSelection.ts:2388 — 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.
  • Duplicated block (13 lines × 2 locations) resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts:1610 — 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.
  • Duplicated block (13 lines × 2 locations) resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts:540 — 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.
  • Duplicated block (13 lines × 2 locations) resources/js/wysiwyg/ui/defaults/buttons/tables.ts:67 — 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.
  • Duplicated block (13 lines × 2 locations) resources/js/wysiwyg/utils/table-copy-paste.ts:77 — 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.
D23 · Boundary Type-Coupling · Cross-context type Role (Users → Permissions) · ×6
  • Cross-context type Role (Users → Permissions) app/Permissions/JointPermissionBuilder.php:88 — Role (context Users) is exposed in Permissions's public surface via JointPermissionBuilder.rebuildForRole — couples the contexts.
  • Cross-context type Role (Users → Permissions) app/Permissions/PermissionFormData.php:61 — Role (context Users) is exposed in Permissions's public surface via PermissionFormData.everyoneElseRole — couples the contexts.
  • Cross-context type Role (Users → Permissions) app/Permissions/PermissionsRepo.php:34 — Role (context Users) is exposed in Permissions's public surface via PermissionsRepo.getAllRolesExcept — couples the contexts.
  • Cross-context type Role (Users → Permissions) app/Permissions/PermissionsRepo.php:42 — Role (context Users) is exposed in Permissions's public surface via PermissionsRepo.getRoleById — couples the contexts.
  • Cross-context type Role (Users → Permissions) app/Permissions/PermissionsRepo.php:50 — Role (context Users) is exposed in Permissions's public surface via PermissionsRepo.saveNewRole — couples the contexts.
  • Cross-context type Role (Users → Permissions) app/Permissions/PermissionsRepo.php:71 — Role (context Users) is exposed in Permissions's public surface via PermissionsRepo.updateRole — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type Entity (Entities → References) · ×6
  • Cross-context type Entity (Entities → References) app/References/ReferenceChangeContext.php:15 — Entity (context Entities) is exposed in References's public surface via ReferenceChangeContext.add — couples the contexts.
  • Cross-context type Entity (Entities → References) app/References/ReferenceChangeContext.php:36 — Entity (context Entities) is exposed in References's public surface via ReferenceChangeContext.getNewForOld — couples the contexts.
  • Cross-context type Entity (Entities → References) app/References/ReferenceFetcher.php:23 — Entity (context Entities) is exposed in References's public surface via ReferenceFetcher.getReferencesToEntity — couples the contexts.
  • Cross-context type Entity (Entities → References) app/References/ReferenceFetcher.php:36 — Entity (context Entities) is exposed in References's public surface via ReferenceFetcher.getReferenceCountToEntity — couples the contexts.
  • Cross-context type Entity (Entities → References) app/References/ReferenceStore.php:19 — Entity (context Entities) is exposed in References's public surface via ReferenceStore.updateForEntity — couples the contexts.
  • Cross-context type Entity (Entities → References) app/References/ReferenceUpdater.php:20 — Entity (context Entities) is exposed in References's public surface via ReferenceUpdater.updateEntityReferences — couples the contexts.
D6 · Cohesion (LCOM4) · Low cohesion · ×6
  • Low cohesion: User (LCOM4 7) app/Users/Models/User.php:48 — User's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: SearchRunner (LCOM4 6) app/Search/SearchRunner.php:22 — SearchRunner's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ConfiguredHtmlPurifier (LCOM4 5) app/Util/HtmlPurifier/ConfiguredHtmlPurifier.php:24 — ConfiguredHtmlPurifier's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: CommentTree (LCOM4 4) app/Activity/Tools/CommentTree.php:9 — CommentTree's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: TrashCan (LCOM4 4) app/Entities/Tools/TrashCan.php:25 — TrashCan's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ThemeService (LCOM4 4) app/Theming/ThemeService.php:11 — ThemeService's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
R10 · Code Duplication · Duplicated block (15 lines × 2 locations) · ×6
  • Duplicated block (15 lines × 2 locations) resources/js/components/book-sort.js:80 — 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.
  • Duplicated block (15 lines × 2 locations) resources/js/wysiwyg/lexical/core/LexicalUtils.ts:888 — 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.
  • Duplicated block (15 lines × 2 locations) resources/js/wysiwyg/lexical/rich-text/index.ts:320 — 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.
  • Duplicated block (15 lines × 2 locations) resources/js/wysiwyg/lexical/rich-text/index.ts:442 — 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.
  • Duplicated block (15 lines × 2 locations) resources/js/wysiwyg/lexical/yjs/SyncCursors.ts:312 — 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.
  • Duplicated block (15 lines × 2 locations) resources/js/wysiwyg/ui/defaults/buttons/controls.ts:19 — 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.
AC3 · Page structure · Page without a main landmark · ×5
  • Page without a main landmark resources/views/api-docs/download.blade.php:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark resources/views/errors/debug.blade.php:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark resources/views/layouts/base.blade.php:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark resources/views/layouts/export.blade.php:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark resources/views/layouts/plain.blade.php:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×5
  • Duplicated block (7 lines × 2) app/Activity/Tools/EntityWatchers.php:74 — app/Activity/Tools/EntityWatchers.php:74-80 | app/Activity/Tools/UserEntityWatchOptions.php:88-94 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/Activity/Tools/EntityWatchers.php:74` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) app/App/HomeController.php:53 — app/App/HomeController.php:53-59 | app/App/HomeController.php:62-68 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/App/HomeController.php:53` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) app/Activity/Models/Favourite.php:22 — app/Activity/Models/Favourite.php:22-28 | app/Activity/Models/Watch.php:30-46 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/Activity/Models/Favourite.php:22` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (7 lines × 2) app/Entities/Controllers/ChapterController.php:226 — app/Entities/Controllers/ChapterController.php:226-233 | app/Entities/Controllers/PageController.php:442-448 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) app/Entities/Queries/BookshelfQueries.php:34 — app/Entities/Queries/BookshelfQueries.php:34-40 | app/Entities/Queries/PageQueries.php:39-45 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×5
  • Swallowed exception (caught, then discarded) 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.
  • Swallowed exception (caught, then discarded) app/Exceptions/BookStackExceptionHandlerPage.php:24 — `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.
  • Swallowed exception (caught, then discarded) app/Settings/StatusController.php:49 — `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.
  • Swallowed exception (caught, then discarded) app/Uploads/ImageRepo.php:231 — `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.
  • Swallowed exception (caught, then discarded) app/Users/Models/User.php:235 — `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.
D23 · Boundary Type-Coupling · Cross-context type Entity (Entities → Permissions) · ×4
  • Cross-context type Entity (Entities → Permissions) app/Permissions/EntityPermissionEvaluator.php:17 — Entity (context Entities) is exposed in Permissions's public surface via EntityPermissionEvaluator.evaluateEntityForUser — couples the contexts.
  • Cross-context type Entity (Entities → Permissions) app/Permissions/JointPermissionBuilder.php:54 — Entity (context Entities) is exposed in Permissions's public surface via JointPermissionBuilder.rebuildForEntity — couples the contexts.
  • Cross-context type Entity (Entities → Permissions) app/Permissions/PermissionFormData.php:13 — Entity (context Entities) is exposed in Permissions's public surface via PermissionFormData.__construct — couples the contexts.
  • Cross-context type Entity (Entities → Permissions) app/Permissions/SimpleEntityData.php:15 — Entity (context Entities) is exposed in Permissions's public surface via SimpleEntityData.fromEntity — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type User (Users → Settings) · ×4
  • Cross-context type User (Users → Settings) app/Settings/SettingService.php:59 — User (context Users) is exposed in Settings's public surface via SettingService.getUser — couples the contexts.
  • Cross-context type User (Users → Settings) app/Settings/SettingService.php:222 — User (context Users) is exposed in Settings's public surface via SettingService.putUser — couples the contexts.
  • Cross-context type User (Users → Settings) app/Settings/TestEmailNotification.php:11 — User (context Users) is exposed in Settings's public surface via TestEmailNotification.toMail — couples the contexts.
  • Cross-context type User (Users → Settings) app/Settings/UserNotificationPreferences.php:9 — User (context Users) is exposed in Settings's public surface via UserNotificationPreferences.__construct — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type User (Users → Uploads) · ×4
  • Cross-context type User (Users → Uploads) app/Uploads/UserAvatars.php:26 — User (context Users) is exposed in Uploads's public surface via UserAvatars.fetchAndAssignToUser — couples the contexts.
  • Cross-context type User (Users → Uploads) app/Uploads/UserAvatars.php:45 — User (context Users) is exposed in Uploads's public surface via UserAvatars.assignToUserFromExistingData — couples the contexts.
  • Cross-context type User (Users → Uploads) app/Uploads/UserAvatars.php:60 — User (context Users) is exposed in Uploads's public surface via UserAvatars.assignToUserFromUrl — couples the contexts.
  • Cross-context type User (Users → Uploads) app/Uploads/UserAvatars.php:87 — User (context Users) is exposed in Uploads's public surface via UserAvatars.destroyAllForUser — couples the contexts.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×4
  • Duplicated block (9 lines × 2) app/Entities/Controllers/BookApiController.php:132 — app/Entities/Controllers/BookApiController.php:132-140 | app/Entities/Controllers/BookshelfApiController.php:116-124 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) app/Entities/Controllers/ChapterController.php:77 — app/Entities/Controllers/ChapterController.php:77-85 | app/Entities/Controllers/PageController.php:141-150 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) app/Entities/Tools/PageContent.php:43 — app/Entities/Tools/PageContent.php:43-51 | app/Entities/Tools/PageContent.php:63-71 — 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.
  • Duplicated block (9 lines × 2) app/References/ModelResolvers/ImageModelResolver.php:24 — app/References/ModelResolvers/ImageModelResolver.php:24-32 | app/Uploads/ImageService.php:322-330 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×4
  • Duplicated block (8 lines × 2) app/Entities/Controllers/PageController.php:284 — app/Entities/Controllers/PageController.php:284-291 | app/Entities/Controllers/PageController.php:309-316 — 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.
  • Duplicated block (8 lines × 2) app/Entities/Controllers/BookApiController.php:35 — app/Entities/Controllers/BookApiController.php:35-42 | app/Entities/Controllers/BookshelfApiController.php:28-35 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) app/View/ViewBlocks/BooksIndexNew.php:21 — app/View/ViewBlocks/BooksIndexNew.php:21-28 | app/View/ViewBlocks/ShelvesIndexNew.php:21-28 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (8 lines × 2) app/View/ViewBlocks/BooksIndexRecents.php:21 — app/View/ViewBlocks/BooksIndexRecents.php:21-28 | app/View/ViewBlocks/ShelvesIndexRecents.php:21-28 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
X3 · Exception handling · Swallowed exception (empty catch) · ×4
  • Swallowed exception (empty catch) app/Access/Controllers/Saml2Controller.php:109 — 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.
  • Swallowed exception (empty catch) database/migrations/2018_08_04_115700_create_bookshelves_table.php:26 — 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.
  • Swallowed exception (empty catch) resources/js/wysiwyg/lexical/clipboard/clipboard.ts:161 — 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.
  • Swallowed exception (empty catch) resources/js/wysiwyg/lexical/clipboard/clipboard.ts:173 — 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.
AC3 · Page structure · Heading level jumps from h2 to h5 · ×3
  • Heading level jumps from h2 to h5 REDACTED:28 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h2 to h5 resources/views/settings/recycle-bin/destroy.blade.php:20 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h2 to h5 resources/views/settings/recycle-bin/restore.blade.php:19 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
D23 · Boundary Type-Coupling · Cross-context type User (Users → Entities) · ×3
  • Cross-context type User (Users → Entities) app/Entities/Tools/PageContent.php:40 — User (context Users) is exposed in Entities's public surface via PageContent.setNewHTML — couples the contexts.
  • Cross-context type User (Users → Entities) app/Entities/Tools/PageContent.php:58 — User (context Users) is exposed in Entities's public surface via PageContent.setNewMarkdown — couples the contexts.
  • Cross-context type User (Users → Entities) app/Entities/Tools/SlugGenerator.php:41 — User (context Users) is exposed in Entities's public surface via SlugGenerator.regenerateForUser — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type Attachment (Uploads → Exports) · ×3
  • Cross-context type Attachment (Uploads → Exports) app/Exports/ZipExports/Models/ZipExportAttachment.php:21 — Attachment (context Uploads) is exposed in Exports's public surface via ZipExportAttachment.fromModel — couples the contexts.
  • Cross-context type Attachment (Uploads → Exports) app/Exports/ZipExports/ZipExportFiles.php:36 — Attachment (context Uploads) is exposed in Exports's public surface via ZipExportFiles.referenceForAttachment — couples the contexts.
  • Cross-context type Attachment (Uploads → Exports) app/Exports/ZipExports/ZipImportReferences.php:82 — Attachment (context Uploads) is exposed in Exports's public surface via ZipImportReferences.addAttachment — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type Image (Uploads → Exports) · ×3
  • Cross-context type Image (Uploads → Exports) app/Exports/ZipExports/Models/ZipExportImage.php:17 — Image (context Uploads) is exposed in Exports's public surface via ZipExportImage.fromModel — couples the contexts.
  • Cross-context type Image (Uploads → Exports) app/Exports/ZipExports/ZipExportFiles.php:57 — Image (context Uploads) is exposed in Exports's public surface via ZipExportFiles.referenceForImage — couples the contexts.
  • Cross-context type Image (Uploads → Exports) app/Exports/ZipExports/ZipImportReferences.php:88 — Image (context Uploads) is exposed in Exports's public surface via ZipImportReferences.addImage — couples the contexts.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×3
  • Duplicated block (12 lines × 2) app/Entities/Controllers/BookController.php:172 — app/Entities/Controllers/BookController.php:172-184 | app/Entities/Controllers/BookshelfController.php:172-183 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (12 lines × 2) app/Exports/ZipExports/Models/ZipExportBook.php:86 — app/Exports/ZipExports/Models/ZipExportBook.php:86-98 | app/Exports/ZipExports/Models/ZipExportChapter.php:66-77 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/Exports/ZipExports/Models/ZipExportBook.php:99` calls `validateRelations` and `app/Exports/ZipExports/Models/ZipExportChapter.php:79` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (12 lines × 2) app/Console/Commands/RegeneratePermissionsCommand.php:31 — app/Console/Commands/RegeneratePermissionsCommand.php:31-42 | app/Console/Commands/RegenerateReferencesCommand.php:31-43 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
R10 · Code Duplication · Duplicated block (17 lines × 2 locations) · ×3
  • Duplicated block (17 lines × 2 locations) resources/js/wysiwyg/lexical/clipboard/clipboard.ts:271 — 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.
  • Duplicated block (17 lines × 2 locations) resources/js/wysiwyg/lexical/core/LexicalUtils.ts:933 — 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.
  • Duplicated block (17 lines × 2 locations) resources/js/wysiwyg/lexical/core/nodes/LexicalElementNode.ts:261 — 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.
R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×3
  • Duplicated block (14 lines × 2 locations) resources/js/wysiwyg/lexical/core/LexicalSelection.ts:2444 — 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.
  • Duplicated block (14 lines × 2 locations) resources/js/wysiwyg/lexical/core/LexicalUtils.ts:350 — 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.
  • Duplicated block (14 lines × 2 locations) resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts:180 — 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.
AC3 · Page structure · Data table has no header cells · ×2
  • Data table has no header cells REDACTED:172 — 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).
  • Data table has no header cells resources/views/search/parts/date-filter.blade.php:5 — 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).
AC3 · Page structure · Heading level jumps from h1 to h5 · ×2
  • Heading level jumps from h1 to h5 resources/views/errors/parts/not-found-text.blade.php:4 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h1 to h5 resources/views/mfa/verify.blade.php:12 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
D17 · Explicit Debt · TodoComment · ×2
  • TodoComment app/Entities/Controllers/PageRevisionController.php:79 — // TODO - Refactor PageContent so we don't need to juggle this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment app/Entities/Controllers/PageRevisionController.php:112 — // TODO - Refactor PageContent so we can de-dupe these steps — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D23 · Boundary Type-Coupling · Cross-context type Entity (Entities → Exports) · ×2
  • Cross-context type Entity (Entities → Exports) app/Exports/ImportRepo.php:119 — Entity (context Entities) is exposed in Exports's public surface via ImportRepo.runImport — couples the contexts.
  • Cross-context type Entity (Entities → Exports) app/Exports/ZipExports/ZipImportRunner.php:51 — Entity (context Entities) is exposed in Exports's public surface via ZipImportRunner.run — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type Entity (Entities → Search) · ×2
  • Cross-context type Entity (Entities → Search) app/Search/SearchIndex.php:35 — Entity (context Entities) is exposed in Search's public surface via SearchIndex.indexEntity — couples the contexts.
  • Cross-context type Entity (Entities → Search) app/Search/SearchIndex.php:100 — Entity (context Entities) is exposed in Search's public surface via SearchIndex.deleteEntityTerms — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type RolePermission (Permissions → Users) · ×2
  • Cross-context type RolePermission (Permissions → Users) app/Users/Models/Role.php:91 — RolePermission (context Permissions) is exposed in Users's public surface via Role.attachPermission — couples the contexts.
  • Cross-context type RolePermission (Permissions → Users) app/Users/Models/Role.php:99 — RolePermission (context Permissions) is exposed in Users's public surface via Role.detachPermission — couples the contexts.
D3 · God Classes · TooManyMethods · ×2
  • TooManyMethods: Entity app/Entities/Models/Entity.php:55 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Actions resources/js/markdown/actions.ts:13 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (4 members, 50+ identical tokens) app/Activity/Notifications/Messages/CommentCreationNotification.php:17 — app/Activity/Notifications/Messages/CommentCreationNotification.php:17-35 | app/Activity/Notifications/Messages/CommentMentionNotification.php:17-35 | app/Activity/Notifications/Messages/PageCreationNotification.php:16-31 | app/Activity/Notifications/Messages/PageUpdateNotification.php:16-32 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) app/Permissions/PermissionsController.php:41 — app/Permissions/PermissionsController.php:41-50 | app/Permissions/PermissionsController.php:73-82 | app/Permissions/PermissionsController.php:105-114 | app/Permissions/PermissionsController.php:137-146 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×2
  • Duplicated block (13 lines × 2) app/References/ModelResolvers/BookLinkModelResolver.php:18 — app/References/ModelResolvers/BookLinkModelResolver.php:18-30 | app/References/ModelResolvers/BookshelfLinkModelResolver.php:17-29 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/References/ModelResolvers/BookLinkModelResolver.php:18` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) database/migrations/2023_12_02_104541_add_default_template_to_books.php:14 — database/migrations/2023_12_02_104541_add_default_template_to_books.php:14-26 | database/migrations/2024_01_01_104542_add_default_template_to_chapters.php:14-26 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `database/migrations/2023_12_02_104541_add_default_template_to_books.php:14` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
R10 · Code Duplication · Duplicated block (16 lines × 2 locations) · ×2
  • Duplicated block (16 lines × 2 locations) resources/js/wysiwyg-tinymce/plugin-codeeditor.js:247 — 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.
  • Duplicated block (16 lines × 2 locations) resources/js/wysiwyg/lexical/core/LexicalNormalization.ts:48 — 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.
R7 · Dead Code · Dead file (~27 LoC) · ×2
  • Dead file (~27 LoC) resources/js/markdown/markdown.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
  • Dead file (~27 LoC) resources/js/wysiwyg/lexical/yjs/types.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
AC3 · Page structure · Heading level jumps from h3 to h5 · ×1
  • Heading level jumps from h3 to h5 resources/views/errors/500.blade.php:10 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC3 · Page structure · Heading level jumps from h1 to h4 · ×1
  • Heading level jumps from h1 to h4 resources/views/errors/debug.blade.php:110 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC3 · Page structure · Heading level jumps from h1 to h3 · ×1
  • Heading level jumps from h1 to h3 resources/views/help/licenses.blade.php:23 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC3 · Page structure · Heading level jumps from h1 to h6 · ×1
  • Heading level jumps from h1 to h6 resources/views/search/all.blade.php:85 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — 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 307 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.
D1 · Cyclomatic Complexity · BookSorter.isSortChangePermissible (cyclomatic 28) · ×1
  • BookSorter.isSortChangePermissible (cyclomatic 28) app/Sorting/BookSorter.php:184 — BookSorter.isSortChangePermissible has cyclomatic complexity 28 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · SrcsetAttrDef.formatDescriptor (cyclomatic 25) · ×1
  • SrcsetAttrDef.formatDescriptor (cyclomatic 25) app/Util/HtmlPurifier/SrcsetAttrDef.php:157 — SrcsetAttrDef.formatDescriptor has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SrcsetAttrDef.parseImageSources (cyclomatic 23) · ×1
  • SrcsetAttrDef.parseImageSources (cyclomatic 23) app/Util/HtmlPurifier/SrcsetAttrDef.php:57 — SrcsetAttrDef.parseImageSources has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ZipExportReferences.handleModelReference (cyclomatic 21) · ×1
  • ZipExportReferences.handleModelReference (cyclomatic 21) app/Exports/ZipExports/ZipExportReferences.php:113 — ZipExportReferences.handleModelReference has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ZipImportRunner.ensurePermissionsPermitImport (cyclomatic 19) · ×1
  • ZipImportRunner.ensurePermissionsPermitImport (cyclomatic 19) app/Exports/ZipExports/ZipImportRunner.php:296 — ZipImportRunner.ensurePermissionsPermitImport has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SearchResultsFormatter.formatTextUsingMatchPositions (cyclomatic 19) · ×1
  • SearchResultsFormatter.formatTextUsingMatchPositions (cyclomatic 19) app/Search/SearchResultsFormatter.php:143 — SearchResultsFormatter.formatTextUsingMatchPositions has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PageRepo.updateTemplateStatusAndContentFromInput (cyclomatic 17) · ×1
  • PageRepo.updateTemplateStatusAndContentFromInput (cyclomatic 17) app/Entities/Repos/PageRepo.php:151 — PageRepo.updateTemplateStatusAndContentFromInput has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · plugin-codeeditor.register (cyclomatic 17) · ×1
  • plugin-codeeditor.register (cyclomatic 17) resources/js/wysiwyg-tinymce/plugin-codeeditor.js:158 — plugin-codeeditor.register has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 208, 235, 177, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · BookSorter.applySortUpdates (cyclomatic 16) · ×1
  • BookSorter.applySortUpdates (cyclomatic 16) app/Sorting/BookSorter.php:126 — BookSorter.applySortUpdates has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D15 · Churn × Complexity Hotspots · Hotspot · ×1
  • Hotspot: app/Util/HtmlPurifier/SrcsetAttrDef.php app/Util/HtmlPurifier/SrcsetAttrDef.php:57 — app/Util/HtmlPurifier/SrcsetAttrDef.php changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in SrcsetAttrDef.parseImageSources at line 57. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-20..2026-10-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-20 19:33:04 +01:00' --until='2026-10-18 19:33:04 +01:00' --full-history --no-merges -- app/Util/HtmlPurifier/SrcsetAttrDef.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D2 · Cognitive Complexity · SrcsetAttrDef.parseImageSources (cognitive 111) · ×1
  • SrcsetAttrDef.parseImageSources (cognitive 111) app/Util/HtmlPurifier/SrcsetAttrDef.php:57 — SrcsetAttrDef.parseImageSources has cognitive complexity 111 (threshold 15). Drivers by points: if/else 29 (104 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 77). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: app/Util/HtmlPurifier/SrcsetAttrDef.php holds 2 of the 13 methods over the threshold — including the worst — and 124 of the 216 points over it (57%), 5.9× the next-largest file (app/Exports/ZipExports/ZipImportRunner.php at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · SrcsetAttrDef.formatDescriptor (cognitive 43) · ×1
  • SrcsetAttrDef.formatDescriptor (cognitive 43) app/Util/HtmlPurifier/SrcsetAttrDef.php:157 — SrcsetAttrDef.formatDescriptor has cognitive complexity 43 (threshold 15). Drivers by points: if/else 14 (30 pts), boolean chains 12, loops 1 (nesting depth added 16). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: app/Util/HtmlPurifier/SrcsetAttrDef.php holds 2 of the 13 methods over the threshold — including the worst — and 124 of the 216 points over it (57%), 5.9× the next-largest file (app/Exports/ZipExports/ZipImportRunner.php at 21). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · BookSorter.isSortChangePermissible (cognitive 33) · ×1
  • BookSorter.isSortChangePermissible (cognitive 33) app/Sorting/BookSorter.php:184 — BookSorter.isSortChangePermissible has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 18, if/else 6 (9 pts), ternaries 3 (6 pts) (nesting depth added 6). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · ZipImportRunner.ensurePermissionsPermitImport (cognitive 32) · ×1
  • ZipImportRunner.ensurePermissionsPermitImport (cognitive 32) app/Exports/ZipExports/ZipImportRunner.php:296 — ZipImportRunner.ensurePermissionsPermitImport has cognitive complexity 32 (threshold 15). Drivers by points: if/else 17 (27 pts), loops 2, ternaries 1 (2 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ZipExportReferences.handleModelReference (cognitive 31) · ×1
  • ZipExportReferences.handleModelReference (cognitive 31) app/Exports/ZipExports/ZipExportReferences.php:113 — ZipExportReferences.handleModelReference has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (23 pts), boolean chains 8 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · InstallModuleCommand.downloadModuleFile (cognitive 26) · ×1
  • InstallModuleCommand.downloadModuleFile (cognitive 26) app/Console/Commands/InstallModuleCommand.php:199 — InstallModuleCommand.downloadModuleFile has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (17 pts), ternaries 1 (5 pts), boolean chains 2, loops 2 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · SearchResultsFormatter.formatTextUsingMatchPositions (cognitive 22) · ×1
  • SearchResultsFormatter.formatTextUsingMatchPositions (cognitive 22) app/Search/SearchResultsFormatter.php:143 — SearchResultsFormatter.formatTextUsingMatchPositions has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4, ternaries 3 (4 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · register (cognitive 22) · ×1
  • register (cognitive 22) resources/js/wysiwyg-tinymce/plugin-codeeditor.js:158 — register has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 5, loops 4 (5 pts), ternaries 1 (2 pts) (nesting depth added 5). None of this is in the body itself: all 22 points belong to 12 function items inside it that branch (a function literal at line 208, a function literal at line 235, a function literal at line 177, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · AssignSortRuleCommand.handle (cognitive 21) · ×1
  • AssignSortRuleCommand.handle (cognitive 21) app/Console/Commands/AssignSortRuleCommand.php:33 — AssignSortRuleCommand.handle has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (16 pts), ternaries 1 (4 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ZipImportRunner.run (cognitive 19) · ×1
  • ZipImportRunner.run (cognitive 19) app/Exports/ZipExports/ZipImportRunner.php:51 — ZipImportRunner.run has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 4, error handling 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ThemeModuleZip.extractTo (cognitive 18) · ×1
  • ThemeModuleZip.extractTo (cognitive 18) app/Theming/ThemeModuleZip.php:15 — ThemeModuleZip.extractTo has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EntityHydrator.loadParentsIntoModels (cognitive 17) · ×1
  • EntityHydrator.loadParentsIntoModels (cognitive 17) app/Entities/Tools/EntityHydrator.php:96 — EntityHydrator.loadParentsIntoModels has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 4, boolean chains 2, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CreateAdminCommand.gatherDetails (cognitive 16) · ×1
  • CreateAdminCommand.gatherDetails (cognitive 16) app/Console/Commands/CreateAdminCommand.php:118 — CreateAdminCommand.gatherDetails has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (16 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D23 · Boundary Type-Coupling · Cross-context type Page (Entities → Activity) · ×1
  • Cross-context type Page (Entities → Activity) app/Activity/Tools/CommentTree.php:23 — Page (context Entities) is exposed in Activity's public surface via CommentTree.__construct — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type Tag (Activity → Exports) · ×1
  • Cross-context type Tag (Activity → Exports) app/Exports/ZipExports/Models/ZipExportTag.php:18 — Tag (context Activity) is exposed in Exports's public surface via ZipExportTag.fromModel — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type User (Users → Permissions) · ×1
  • Cross-context type User (Users → Permissions) app/Permissions/PermissionApplicator.php:19 — User (context Users) is exposed in Permissions's public surface via PermissionApplicator.__construct — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type Attachment (Uploads → References) · ×1
  • Cross-context type Attachment (Uploads → References) app/References/ModelResolvers/AttachmentModelResolver.php:9 — Attachment (context Uploads) is exposed in References's public surface via AttachmentModelResolver.resolve — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type Image (Uploads → References) · ×1
  • Cross-context type Image (Uploads → References) app/References/ModelResolvers/ImageModelResolver.php:12 — Image (context Uploads) is exposed in References's public surface via ImageModelResolver.resolve — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type Book (Entities → Sorting) · ×1
  • Cross-context type Book (Entities → Sorting) app/Sorting/BookSorter.php:36 — Book (context Entities) is exposed in Sorting's public surface via BookSorter.runBookAutoSort — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type Page (Entities → Uploads) · ×1
  • Cross-context type Page (Entities → Uploads) app/Uploads/Image.php:66 — Page (context Entities) is exposed in Uploads's public surface via Image.getPage — couples the contexts.
D35 · Change Coupling · Change coupling clique · ×1
  • Change coupling clique: common.php, common.php, common.php lang/de/common.php — 3 files — `lang/de/common.php`, `lang/nl/common.php`, `lang/pt_BR/common.php` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) app/Users/Controllers/UserSearchController.php:23 — app/Users/Controllers/UserSearchController.php:23-43 | app/Users/Controllers/UserSearchController.php:55-75 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/Users/Controllers/UserSearchController.php:23` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/Users/Controllers/UserSearchController.php:21` calls `userCan` and `app/Users/Controllers/UserSearchController.php:53` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (19–20 lines × 2) · ×1
  • Duplicated block (19–20 lines × 2) app/Entities/Controllers/BookController.php:42 — app/Entities/Controllers/BookController.php:42-61 | app/Entities/Controllers/BookshelfController.php:36-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) app/Uploads/Controllers/DrawioImageController.php:31 — app/Uploads/Controllers/DrawioImageController.php:31-49 | app/Uploads/Controllers/GalleryImageController.php:30-48 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) app/Activity/Notifications/Messages/CommentCreationNotification.php:17 — app/Activity/Notifications/Messages/CommentCreationNotification.php:17-31 | app/Activity/Notifications/Messages/CommentMentionNotification.php:17-31 — before extracting anything, compare `app/Activity/Notifications/Messages/CommentCreationNotification.php` and `app/Activity/Notifications/Messages/CommentMentionNotification.php` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) app/References/ModelResolvers/ChapterLinkModelResolver.php:18 — app/References/ModelResolvers/ChapterLinkModelResolver.php:18-31 | app/References/ModelResolvers/PageLinkModelResolver.php:18-31 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/References/ModelResolvers/ChapterLinkModelResolver.php:18` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12–13 lines × 4) · ×1
  • Duplicated block (12–13 lines × 4) app/Activity/Notifications/Messages/CommentCreationNotification.php:21 — app/Activity/Notifications/Messages/CommentCreationNotification.php:21-33 | app/Activity/Notifications/Messages/CommentMentionNotification.php:21-33 | app/Activity/Notifications/Messages/PageCreationNotification.php:18-29 | app/Activity/Notifications/Messages/PageUpdateNotification.php:18-29 — before extracting anything, compare `app/Activity/Notifications/Messages/CommentCreationNotification.php` and `app/Activity/Notifications/Messages/CommentMentionNotification.php` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `app/Activity/Notifications/Messages/CommentCreationNotification.php:21` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/Activity/Notifications/Messages/PageUpdateNotification.php:30` calls `line`, `trans` and `app/Activity/Notifications/Messages/PageCreationNotification.php:30` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1
  • Duplicated block (11 lines × 2) app/Entities/Queries/ChapterQueries.php:40 — app/Entities/Queries/ChapterQueries.php:40-50 | app/Entities/Queries/PageQueries.php:53-63 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×1
  • Duplicated block (9 lines × 4) app/Permissions/PermissionsController.php:42 — app/Permissions/PermissionsController.php:42-50 | app/Permissions/PermissionsController.php:74-82 | app/Permissions/PermissionsController.php:106-114 | app/Permissions/PermissionsController.php:138-146 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×1
  • Duplicated block (9 lines × 3) app/Activity/Queries/WebhooksAllPaginatedAndSorted.php:20 — app/Activity/Queries/WebhooksAllPaginatedAndSorted.php:20-28 | app/Users/Queries/RolesAllPaginatedAndSorted.php:25-33 | app/Users/Queries/UsersAllPaginatedAndSorted.php:30-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) app/Entities/Controllers/RecycleBinApiController.php:19 — app/Entities/Controllers/RecycleBinApiController.php:19-24 | app/Entities/Controllers/RecycleBinController.php:23-28 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×1
  • Duplicated block (10 lines × 2) app/Entities/Queries/BookQueries.php:40 — app/Entities/Queries/BookQueries.php:40-49 | app/Entities/Queries/BookshelfQueries.php:46-55 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×1
  • Duplicated block (5 lines × 2) app/Entities/Queries/ChapterQueries.php:55 — app/Entities/Queries/ChapterQueries.php:55-59 | app/Entities/Queries/PageQueries.php:68-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×1
  • Duplicated block (6 lines × 4) app/Entities/Controllers/BookApiController.php:122 — app/Entities/Controllers/BookApiController.php:122-127 | app/Entities/Controllers/BookshelfApiController.php:106-111 | app/Entities/Controllers/ChapterApiController.php:132-137 | app/Entities/Controllers/PageApiController.php:172-177 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×1
  • Duplicated block (5 lines × 3) app/Search/SearchRunner.php:361 — app/Search/SearchRunner.php:361-365 | app/Search/SearchRunner.php:370-374 | app/Search/SearchRunner.php:379-383 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — JavaScript/TypeScript suite — 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.
P3 · Security & performance tooling · SAST runs, but gates no merge · ×1
  • SAST runs, but gates no merge — `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.
P5 · DR & Backup · No DR/backup evidence · ×1
  • No DR/backup evidence — 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.
R10 · Code Duplication · Duplication concentrated across 10 sibling directories (24 clone groups) · ×1
  • Duplication concentrated across 10 sibling directories (24 clone groups) resources/js/wysiwyg/lexical/core/nodes/LexicalParagraphNode.ts:118 — 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.
R10 · Code Duplication · Duplicated block with local edits (86 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (86 matched lines × 2 locations) resources/js/wysiwyg/lexical/rich-text/LexicalCodeBlockNode.ts:31 — 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.
R10 · Code Duplication · Duplicated block (54 lines × 2 locations) · ×1
  • Duplicated block (54 lines × 2 locations) resources/js/wysiwyg/ui/defaults/buttons/tables.ts:177 — 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.
R10 · Code Duplication · Duplicated block with local edits (39 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (39 matched lines × 2 locations) resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts:60 — 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.
R10 · Code Duplication · Duplicated block with local edits (30 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (30 matched lines × 2 locations) resources/js/wysiwyg/utils/table-copy-paste.ts:26 — 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.
R10 · Code Duplication · Duplicated block with local edits (29 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (29 matched lines × 2 locations) resources/js/wysiwyg/ui/defaults/forms/tables.ts:78 — 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.
R10 · Code Duplication · Duplicated block (25 lines × 2 locations) · ×1
  • Duplicated block (25 lines × 2 locations) resources/js/wysiwyg/lexical/core/nodes/LexicalParagraphNode.ts:118 — 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.
R10 · Code Duplication · Duplicated block (24 lines × 2 locations) · ×1
  • Duplicated block (24 lines × 2 locations) resources/js/wysiwyg/lexical/rich-text/index.ts:340 — 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.
R10 · Code Duplication · Duplicated block with local edits (23 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (23 matched lines × 2 locations) resources/js/wysiwyg/lexical/clipboard/clipboard.ts:240 — 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.
R10 · Code Duplication · Duplicated block (23 lines × 2 locations) · ×1
  • Duplicated block (23 lines × 2 locations) resources/js/wysiwyg/lexical/core/LexicalUtils.ts:1657 — 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.
R10 · Code Duplication · Duplicated block (21 lines × 2 locations) · ×1
  • Duplicated block (21 lines × 2 locations) resources/js/wysiwyg/lexical/table/LexicalTableUtils.ts:266 — 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.
R10 · Code Duplication · Duplicated block (19 lines × 2 locations) · ×1
  • Duplicated block (19 lines × 2 locations) resources/js/wysiwyg/index.ts:105 — 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.
R10 · Code Duplication · Duplicated block (19 lines × 4 locations) · ×1
  • Duplicated block (19 lines × 4 locations) resources/js/wysiwyg/lexical/core/LexicalUtils.ts:321 — 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.
R10 · Code Duplication · Duplicated block (19 lines × 3 locations) · ×1
  • Duplicated block (19 lines × 3 locations) resources/js/wysiwyg/lexical/core/nodes/CommonBlockNode.ts:23 — 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.
R10 · Code Duplication · Duplicated block (18 lines × 2 locations) · ×1
  • Duplicated block (18 lines × 2 locations) resources/js/wysiwyg/lexical/table/LexicalTableUtils.ts:498 — 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.
R10 · Code Duplication · Duplicated block (17 lines × 3 locations) · ×1
  • Duplicated block (17 lines × 3 locations) resources/js/wysiwyg/lexical/rich-text/index.ts:264 — 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.
R10 · Code Duplication · Duplicated block (14 lines × 7 locations) · ×1
  • Duplicated block (14 lines × 7 locations) resources/js/wysiwyg/lexical/core/nodes/CommonBlockNode.ts:17 — 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.
R10 · Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (14 matched lines × 2 locations) resources/js/wysiwyg/lexical/utils/index.ts:192 — 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.
R10 · Code Duplication · Duplicated block (12 lines × 2 locations) · ×1
  • Duplicated block (12 lines × 2 locations) resources/js/components/shelf-sort.js:21 — 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.
R11 · Import Boundaries · Boundary violation [package · ×1
  • Boundary violation [package:third-party-deep-import] resources/js/services/vdom.ts:7 — 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.
R2 · Cyclomatic Complexity · Complex function insertText (cyclomatic 92, cognitive 158) · ×1
  • Complex function insertText (cyclomatic 92, cognitive 158) resources/js/wysiwyg/lexical/core/LexicalSelection.ts:717 — 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.
R2 · Cyclomatic Complexity · Complex function $handleArrowKey (cyclomatic 62, cognitive 146) · ×1
  • Complex function $handleArrowKey (cyclomatic 62, cognitive 146) resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts:1267 — $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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 56, cognitive 45) · ×1
  • Complex function (anonymous) (cyclomatic 56, cognitive 45) resources/js/wysiwyg/lexical/core/LexicalEvents.ts:542 — (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.
R2 · Cyclomatic Complexity · Complex function updateDOMSelection (cyclomatic 47, cognitive 52) · ×1
  • Complex function updateDOMSelection (cyclomatic 47, cognitive 52) resources/js/wysiwyg/lexical/core/LexicalSelection.ts:2558 — 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 45, cognitive 97) · ×1
  • Complex function (anonymous) (cyclomatic 45, cognitive 97) resources/js/wysiwyg/lexical/core/LexicalMutations.ts:111 — (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.
R2 · Cyclomatic Complexity · Complex function $patchStyleText (cyclomatic 44, cognitive 75) · ×1
  • Complex function $patchStyleText (cyclomatic 44, cognitive 75) resources/js/wysiwyg/lexical/selection/lexical-node.ts:279 — $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.
R2 · Cyclomatic Complexity · Complex function deleteCharacter (cyclomatic 41, cognitive 58) · ×1
  • Complex function deleteCharacter (cyclomatic 41, cognitive 58) resources/js/wysiwyg/lexical/core/LexicalSelection.ts:1594 — 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 41, cognitive 58) · ×1
  • Complex function (anonymous) (cyclomatic 41, cognitive 58) resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts:675 — (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.
R2 · Cyclomatic Complexity · Complex function $wrapNodesImpl (cyclomatic 36, cognitive 76) · ×1
  • Complex function $wrapNodesImpl (cyclomatic 36, cognitive 76) resources/js/wysiwyg/lexical/selection/range-selection.ts:200 — $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.
R2 · Cyclomatic Complexity · Complex function onKeyDown (cyclomatic 34, cognitive 41) · ×1
  • Complex function onKeyDown (cyclomatic 34, cognitive 41) resources/js/wysiwyg/lexical/core/LexicalEvents.ts:992 — 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.
R2 · Cyclomatic Complexity · Complex function createEditor (cyclomatic 33, cognitive 68) · ×1
  • Complex function createEditor (cyclomatic 33, cognitive 68) resources/js/wysiwyg/lexical/core/LexicalEditor.ts:420 — 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.
R2 · Cyclomatic Complexity · Complex function $commitPendingUpdates (cyclomatic 33, cognitive 45) · ×1
  • Complex function $commitPendingUpdates (cyclomatic 33, cognitive 45) resources/js/wysiwyg/lexical/core/LexicalUpdates.ts:477 — $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.
R2 · Cyclomatic Complexity · Complex function $updateTextNodeFromDOMContent (cyclomatic 33, cognitive 39) · ×1
  • Complex function $updateTextNodeFromDOMContent (cyclomatic 33, cognitive 39) resources/js/wysiwyg/lexical/core/LexicalUtils.ts:642 — $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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 33, cognitive 26) · ×1
  • Complex function (anonymous) (cyclomatic 33, cognitive 26) resources/js/wysiwyg/lexical/selection/__tests__/utils/index.ts:655 — (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.
R2 · Cyclomatic Complexity · Complex function modify (cyclomatic 32, cognitive 74) · ×1
  • Complex function modify (cyclomatic 32, cognitive 74) resources/js/wysiwyg/lexical/core/LexicalSelection.ts:1413 — 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 32, cognitive 62) · ×1
  • Complex function (anonymous) (cyclomatic 32, cognitive 62) resources/js/wysiwyg/lexical/core/LexicalEvents.ts:291 — (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.
R2 · Cyclomatic Complexity · Complex function $trimTextContentFromAnchor (cyclomatic 31, cognitive 71) · ×1
  • Complex function $trimTextContentFromAnchor (cyclomatic 31, cognitive 71) resources/js/wysiwyg/lexical/selection/lexical-node.ts:113 — $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.
R2 · Cyclomatic Complexity · Complex function modify (cyclomatic 30, cognitive 74) · ×1
  • Complex function modify (cyclomatic 30, cognitive 74) resources/js/wysiwyg/lexical/selection/__tests__/utils/index.ts:89 — 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.
R2 · Cyclomatic Complexity · Complex function getChangeType (cyclomatic 30, cognitive 22) · ×1
  • Complex function getChangeType (cyclomatic 30, cognitive 22) resources/js/wysiwyg/lexical/history/index.ts:80 — 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.
R2 · Cyclomatic Complexity · Complex function formatText (cyclomatic 28, cognitive 38) · ×1
  • Complex function formatText (cyclomatic 28, cognitive 38) resources/js/wysiwyg/lexical/core/LexicalSelection.ts:1073 — 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.
R3 · Large Files · resources/js/wysiwyg/lexical/core/LexicalSelection.ts · ×1
  • resources/js/wysiwyg/lexical/core/LexicalSelection.ts: 2648 lines of code resources/js/wysiwyg/lexical/core/LexicalSelection.ts:1 — 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.
R3 · Large Files · resources/js/wysiwyg/lexical/core/LexicalUtils.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/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.
R3 · Large Files · resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.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/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.
R3 · Large Files · resources/js/wysiwyg/lexical/core/nodes/LexicalTextNode.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/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.
R3 · Large Files · resources/js/wysiwyg/lexical/core/LexicalEvents.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/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.
R3 · Large Files · resources/js/wysiwyg/lexical/core/LexicalEditor.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/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.
R3 · Large Files · resources/js/wysiwyg/lexical/core/LexicalNode.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/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.
R3 · Large Files · resources/js/wysiwyg/lexical/core/LexicalUpdates.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/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.
R3 · Large Files · resources/js/wysiwyg/lexical/table/LexicalTableUtils.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/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.
R3 · Large Files · resources/js/wysiwyg/lexical/core/LexicalReconciler.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/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.
R3 · Large Files · resources/js/wysiwyg/lexical/rich-text/index.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/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.
R3 · Large Files · resources/js/wysiwyg/lexical/core/nodes/LexicalElementNode.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/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.
R3 · Large Files · resources/js/wysiwyg/lexical/yjs/CollabElementNode.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/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.
R3 · Large Files · resources/js/wysiwyg/lexical/utils/index.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/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.
R3 · Large Files · resources/js/wysiwyg/lexical/clipboard/clipboard.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/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.
R3 · Large Files · resources/js/wysiwyg/lexical/selection/range-selection.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/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.
R3 · Large Files · resources/js/wysiwyg/lexical/link/index.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/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.
R3 · Large Files · resources/js/wysiwyg/lexical/yjs/Utils.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/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.
R3 · Large Files · resources/js/wysiwyg/lexical/yjs/SyncCursors.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/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.
R3 · Large Files · resources/js/wysiwyg/lexical/list/formatList.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/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.
R3 · Large Files · resources/js/wysiwyg/lexical/history/index.ts · ×1
  • resources/js/wysiwyg/lexical/history/index.ts: 428 lines of code resources/js/wysiwyg/lexical/history/index.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.
R3 · Large Files · resources/js/markdown/actions.ts · ×1
  • resources/js/markdown/actions.ts: 424 lines of code resources/js/markdown/actions.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.
R3 · Large Files · resources/js/wysiwyg/lexical/list/LexicalListItemNode.ts · ×1
  • resources/js/wysiwyg/lexical/list/LexicalListItemNode.ts: 410 lines of code resources/js/wysiwyg/lexical/list/LexicalListItemNode.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.
R7 · Dead Code · Dead file (~666 LoC) · ×1
  • Dead file (~666 LoC) resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts — 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
R7 · Dead Code · Dead file (~560 LoC) · ×1
  • Dead file (~560 LoC) resources/js/wysiwyg/lexical/yjs/Utils.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
R7 · Dead Code · Dead file (~536 LoC) · ×1
  • Dead file (~536 LoC) resources/js/wysiwyg/lexical/yjs/SyncCursors.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
R7 · Dead Code · Dead file (~490 LoC) · ×1
  • Dead file (~490 LoC) resources/js/markdown/actions.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
R7 · Dead Code · Dead file (~329 LoC) · ×1
  • Dead file (~329 LoC) resources/js/markdown/inputs/textarea.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
R7 · Dead Code · Dead file (~247 LoC) · ×1
  • Dead file (~247 LoC) resources/js/wysiwyg/lexical/yjs/SyncEditorStates.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
R7 · Dead Code · Dead file (~178 LoC) · ×1
  • Dead file (~178 LoC) resources/js/wysiwyg/lexical/yjs/CollabTextNode.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
R7 · Dead Code · Dead file (~141 LoC) · ×1
  • Dead file (~141 LoC) 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/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
R7 · Dead Code · Dead file (~116 LoC) · ×1
  • Dead file (~116 LoC) resources/js/wysiwyg/lexical/yjs/index.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
R7 · Dead Code · Dead file (~115 LoC) · ×1
  • Dead file (~115 LoC) resources/js/markdown/display.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
R7 · Dead Code · Dead file (~110 LoC) · ×1
  • Dead file (~110 LoC) resources/js/wysiwyg/lexical/yjs/CollabDecoratorNode.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
R7 · Dead Code · Dead file (~87 LoC) · ×1
  • Dead file (~87 LoC) 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 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
R7 · Dead Code · Dead file (~82 LoC) · ×1
  • Dead file (~82 LoC) resources/js/markdown/settings.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
R7 · Dead Code · Dead file (~78 LoC) · ×1
  • Dead file (~78 LoC) resources/js/wysiwyg/lexical/yjs/Bindings.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
R7 · Dead Code · Dead file (~69 LoC) · ×1
  • Dead file (~69 LoC) resources/js/markdown/index.mts — 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
R7 · Dead Code · Dead file (~68 LoC) · ×1
  • Dead file (~68 LoC) resources/js/wysiwyg/lexical/yjs/CollabLineBreakNode.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/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
R7 · Dead Code · Dead file (~62 LoC) · ×1
  • Dead file (~62 LoC) resources/js/markdown/dom-handlers.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
R7 · Dead Code · Dead file (~54 LoC) · ×1
  • Dead file (~54 LoC) resources/js/markdown/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/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
R7 · Dead Code · Dead file (~49 LoC) · ×1
  • Dead file (~49 LoC) resources/js/wysiwyg/lexical/core/shared/simpleDiffWithCursor.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
R7 · Dead Code · Dead file (~43 LoC) · ×1
  • Dead file (~43 LoC) resources/js/markdown/shortcuts.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
R7 · Dead Code · Dead file (~40 LoC) · ×1
  • Dead file (~40 LoC) resources/js/markdown/common-events.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
R7 · Dead Code · Dead file (~36 LoC) · ×1
  • Dead file (~36 LoC) resources/js/code/legacy-modes.mjs — 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
R7 · Dead Code · Dead file (~20 LoC) · ×1
  • Dead file (~20 LoC) resources/js/wysiwyg/lexical/core/shared/warnOnlyOnce.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
R7 · Dead Code · Dead file (~15 LoC) · ×1
  • Dead file (~15 LoC) resources/js/wysiwyg-tinymce/plugins-stub.js — 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
R7 · Dead Code · Dead file (~13 LoC) · ×1
  • Dead file (~13 LoC) resources/js/wysiwyg/lexical/table/constants.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
R8 · Dependency Hygiene · Unused dependency '@lezer/generator' · ×1
  • Unused dependency '@lezer/generator' — 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.
R8 · Dependency Hygiene · Unused dependency 'esbuild' · ×1
  • Unused dependency 'esbuild' — 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.
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×1
  • Recursive walk over a caller-supplied document has no depth cap resources/js/wysiwyg/lexical/html/index.ts:289 — `$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.
X2 · Cancellation propagation · Async function without AbortSignal · ×1
  • Async function without AbortSignal: request resources/js/services/http.ts:80 — `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 })`.
Minor — 55 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×21
  • Duplicated predicate resources/js/wysiwyg/lexical/core/LexicalUtils.ts:1659 — `!$isElementNode(node) || $isRootOrShadowRoot(node)` appears character-identically in 2 files — resources/js/wysiwyg/lexical/core/LexicalUtils.ts, resources/js/wysiwyg/lexical/selection/range-selection.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate resources/js/markdown/dom-handlers.ts:52 — `!clipboard.hasItems() || clipboard.containsTabularData()` appears character-identically in 3 files — resources/js/markdown/dom-handlers.ts, resources/js/wysiwyg-tinymce/drop-paste-handling.js, resources/js/wysiwyg/services/drop-paste-handling.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate resources/js/wysiwyg/lexical/core/LexicalUtils.ts:1670 — `!node.isInline() && node.canBeEmpty() !== false && isLeafElement` appears character-identically in 2 files — resources/js/wysiwyg/lexical/core/LexicalUtils.ts, resources/js/wysiwyg/lexical/selection/range-selection.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate resources/js/wysiwyg/services/keyboard-handling.ts:51 — `$getNearestNodeBlockParent(node) || node` appears character-identically in 2 files — resources/js/wysiwyg/services/keyboard-handling.ts, resources/js/wysiwyg/utils/nodes.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate resources/js/wysiwyg/lexical/core/LexicalSelection.ts:2736 — `$getSelection() || $getPreviousSelection()` appears character-identically in 2 files — resources/js/wysiwyg/lexical/core/LexicalSelection.ts, resources/js/wysiwyg/lexical/utils/index.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate resources/js/wysiwyg/lexical/clipboard/clipboard.ts:276 — `$isElementNode(currentNode) && currentNode.excludeFromCopy('html')` appears character-identically in 2 files — resources/js/wysiwyg/lexical/clipboard/clipboard.ts, resources/js/wysiwyg/lexical/html/index.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate resources/js/wysiwyg/lexical/core/LexicalSelection.ts:555 — `$isElementNode(node) && !node.isInline()` appears character-identically in 2 files — resources/js/wysiwyg/lexical/core/LexicalSelection.ts, resources/js/wysiwyg/lexical/utils/index.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts:1394 — `$isRangeSelection(selection) && selection.isCollapsed()` appears character-identically in 3 files — resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts, resources/js/wysiwyg/lexical/yjs/CollabTextNode.ts, resources/js/wysiwyg/services/mentions.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts:1194 — `$isRangeSelection(selection) || $isTableSelection(selection)` appears character-identically in 2 files — resources/js/wysiwyg/lexical/table/LexicalTableSelectionHelpers.ts, resources/js/wysiwyg/lexical/table/LexicalTableUtils.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate resources/js/wysiwyg/lexical/clipboard/clipboard.ts:282 — `$isTextNode(clone) && selection !== null` appears character-identically in 2 files — resources/js/wysiwyg/lexical/clipboard/clipboard.ts, resources/js/wysiwyg/lexical/html/index.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate resources/js/markdown/actions.ts:405 — `file === null || file.type.indexOf('image') !== 0` appears character-identically in 3 files — resources/js/markdown/actions.ts, resources/js/wysiwyg-tinymce/drop-paste-handling.js, resources/js/wysiwyg/utils/images.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate resources/js/wysiwyg/lexical/core/LexicalUtils.ts:1665 — `firstChild === null || $isLineBreakNode(firstChild) || $isTextNode(firstChild) || firstChild.isInline()` appears character-identically in 2 files — resources/js/wysiwyg/lexical/core/LexicalUtils.ts, resources/js/wysiwyg/lexical/selection/range-selection.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate resources/js/wysiwyg/lexical/core/LexicalUtils.ts:1678 — `parent !== null && parent.getParent() !== null && !predicate(parent)` appears character-identically in 3 files — resources/js/wysiwyg/lexical/core/LexicalUtils.ts, resources/js/wysiwyg/lexical/link/index.ts, resources/js/wysiwyg/lexical/selection/range-selection.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate resources/js/wysiwyg/lexical/core/LexicalReconciler.ts:606 — `prevIndex <= prevEndIndex && nextIndex <= nextEndIndex` appears character-identically in 2 files — resources/js/wysiwyg/lexical/core/LexicalReconciler.ts, resources/js/wysiwyg/lexical/yjs/CollabElementNode.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate resources/js/wysiwyg/lexical/core/nodes/LexicalTextNode.ts:205 — `right + left < aLength && right + left < bLength && a[aLength - right - 1] === b[bLength - right - 1]` appears character-identically in 2 files — resources/js/wysiwyg/lexical/core/nodes/LexicalTextNode.ts, resources/js/wysiwyg/lexical/core/shared/simpleDiffWithCursor.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate resources/js/wysiwyg/lexical/core/LexicalSelection.ts:1164 — `startOffset !== 0 && !$isTokenOrSegmented(firstNode)` appears character-identically in 2 files — resources/js/wysiwyg/lexical/core/LexicalSelection.ts, resources/js/wysiwyg/lexical/selection/lexical-node.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate app/Entities/Controllers/ChapterController.php:202 — `$entitySelection === null || $entitySelection === ''` appears character-identically in 2 files — app/Entities/Controllers/ChapterController.php, app/Entities/Controllers/PageController.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate app/Entities/Controllers/BookController.php:182 — `array_key_exists('image', $validated) && is_null($validated['image'])` appears character-identically in 2 files — app/Entities/Controllers/BookController.php, app/Entities/Controllers/BookshelfController.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate resources/views/entities/book-tree.blade.php:18 — `isA('chapter') && count($bookChild->visible_pages) > 0` appears character-identically in 2 files — resources/views/entities/book-tree.blade.php, resources/views/exports/parts/book-contents-menu.blade.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate resources/views/auth/login.blade.php:28 — `setting('registration-enabled') && config('auth.method') === 'standard'` appears character-identically in 2 files — resources/views/auth/login.blade.php, resources/views/layouts/parts/header-links.blade.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate app/References/ModelResolvers/ImageModelResolver.php:25 — `str_starts_with($part, 'thumbs-') || str_starts_with($part, 'scaled-')` appears character-identically in 2 files — app/References/ModelResolvers/ImageModelResolver.php, app/Uploads/ImageService.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
X4 · Structured logging · Interpolated log message defeats structured logging · ×7
  • Interpolated log message defeats structured logging app/Access/LdapService.php:256 — `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.
  • Interpolated log message defeats structured logging app/Access/LdapService.php:486 — `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.
  • Interpolated log message defeats structured logging app/Activity/DispatchWebhookJob.php:69 — `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.
  • Interpolated log message defeats structured logging app/Activity/DispatchWebhookJob.php:73 — `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.
  • Interpolated log message defeats structured logging app/Activity/Notifications/Handlers/BaseNotificationHandler.php:45 — `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.
  • Interpolated log message defeats structured logging app/Uploads/ImageStorageDisk.php:99 — `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.
  • Interpolated log message defeats structured logging app/Users/Controllers/UserController.php:103 — `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.
C2 · Access Controls · No named authorization policies · ×1
  • No named authorization policies — 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.
C3 · Audit Trail · Partial audit-trail evidence · ×1
  • Partial audit-trail evidence — 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).
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 1 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `(repository root)` (53055 LoC, 914 module-visible types across 100 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 1 of 351 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 351 of the 1103 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: resources/js/components/index.ts. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D34 · Knowledge Freshness · Orphaned file · ×1
  • Orphaned file resources/js/components/index.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
DM9 · Scattered domain decisions · Rule about [anchor, focus] decided in 4 places · ×1
  • Rule about [anchor, focus] decided in 4 places — 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.
DM9 · Scattered domain decisions · Rule about [format, style] decided in 2 places · ×1
  • Rule about [format, style] decided in 2 places — 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.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — 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.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — 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.)
R7 · Dead Code · Unused export 'getCurrentDay' · ×1
  • Unused export 'getCurrentDay' resources/js/services/dates.ts:1 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'INDENT_CONTENT_COMMAND' · ×1
  • Unused export 'INDENT_CONTENT_COMMAND' resources/js/wysiwyg/lexical/core/LexicalCommands.ts:87 — 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.
R7 · Dead Code · Unused export 'OUTDENT_CONTENT_COMMAND' · ×1
  • Unused export 'OUTDENT_CONTENT_COMMAND' resources/js/wysiwyg/lexical/core/LexicalCommands.ts:90 — 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.
R7 · Dead Code · Unused export 'IS_ALIGN_LEFT' · ×1
  • Unused export 'IS_ALIGN_LEFT' resources/js/wysiwyg/lexical/core/LexicalConstants.ts:62 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'IS_ALIGN_CENTER' · ×1
  • Unused export 'IS_ALIGN_CENTER' resources/js/wysiwyg/lexical/core/LexicalConstants.ts:63 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'IS_ALIGN_RIGHT' · ×1
  • Unused export 'IS_ALIGN_RIGHT' resources/js/wysiwyg/lexical/core/LexicalConstants.ts:64 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'IS_ALIGN_JUSTIFY' · ×1
  • Unused export 'IS_ALIGN_JUSTIFY' resources/js/wysiwyg/lexical/core/LexicalConstants.ts:65 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'IS_ALIGN_START' · ×1
  • Unused export 'IS_ALIGN_START' resources/js/wysiwyg/lexical/core/LexicalConstants.ts:66 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'IS_ALIGN_END' · ×1
  • Unused export 'IS_ALIGN_END' resources/js/wysiwyg/lexical/core/LexicalConstants.ts:67 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'ListenerType' · ×1
  • Unused export 'ListenerType' resources/js/wysiwyg/lexical/core/LexicalEditor.ts:316 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'TransformerType' · ×1
  • Unused export 'TransformerType' resources/js/wysiwyg/lexical/core/LexicalEditor.ts:324 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export '$getTextContent' · ×1
  • Unused export '$getTextContent' resources/js/wysiwyg/lexical/core/LexicalSelection.ts:2744 — 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.
S1 · Web-Security Posture · No security response headers detected · ×1
  • No security response headers detected REDACTED:1 — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `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.)
X2 · Cancellation propagation · Not all async functions that make a request accept an AbortSignal · ×1
  • Not all async functions that make a request accept an AbortSignal — Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch) 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.
X5 · Nullable reference types · PHP static analysis does not check null everywhere · ×1
  • PHP static analysis does not check null everywhere — 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.
Minor — 4 finding(s)
D12 · Dependency Hygiene · Outdated · ×4
  • Outdated: laravel/framework — `laravel/framework` is locked at v13.35.0 but v13.38.0 is the current stable release on Packagist, and it already satisfies the `^v13.35.0` constraint declared in composer.json — so the lockfile is behind this repository's own declared range. Run `composer update laravel/framework` and commit the updated composer.lock.
  • Outdated: laravel/socialite — `laravel/socialite` is locked at v5.30.0 but v5.31.0 is the current stable release on Packagist, and it already satisfies the `^5.10` constraint declared in composer.json — so the lockfile is behind this repository's own declared range. Run `composer update laravel/socialite` and commit the updated composer.lock.
  • Outdated: league/commonmark — `league/commonmark` is locked at 2.10.3 but 2.10.4 is the current stable release on Packagist, and it already satisfies the `^2.3` constraint declared in composer.json — so the lockfile is behind this repository's own declared range. Run `composer update league/commonmark` and commit the updated composer.lock.
  • Outdated: league/html-to-markdown — `league/html-to-markdown` is locked at 5.1.3 but 5.2.3 is the current stable release on Packagist, and it already satisfies the `^5.0.0` constraint declared in composer.json — so the lockfile is behind this repository's own declared range. Run `composer update league/html-to-markdown` and commit the updated composer.lock.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-41763a4489ed46febf3dcb17a6965751/history.json --exit-code 0 --source .1artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-41763a4489ed46febf3dcb17a6965751/tree.json --exit-code 0 --source .1artifacts/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/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .21artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .10artifacts/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 Confinementruntime-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 Confinementruntime-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 Enforcementruntime-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 Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json

Run 01a16663-428c-77ce-b1ba-b6d3a636f736 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 104 · Warnings: 499 · Recommendations: 55 · Info: 4 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 23-10-2026 @ 01:32 UTC.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md