Public report of LycheeOrg/Lychee, published 17 November 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.11.4). Assert 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, 17 November 2026, 16:49 UTC · Survey ID cd_fb92b3a260424693b42788a9080ef3e2

LycheeOrg/Lychee

Measured 17 November 2026, 16:45 UTC, at code version a4bb5af

CAI score 43.1out of 100 Weak
CriticalWeakAdequateStrongExemplary
Up 2.7 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.

A large codebase: 282,590 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 2.6 person-years · Weakest lens: Code Health, 37.5

Findings by how serious they are

105 critical 766 serious 222 minor

14 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look 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

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 16:45 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 the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work 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 ▸

87of 87 dimensions measured by tools.
1077of 1093 findings point to an exact file and line, so you can open each one in the code. The other 16 concern the repository as a whole, such as missing documentation.
87dimensions across 8 lenses, read from 282,590 lines of product code in 2 projects.
Chapters

Executive summary

LycheeOrg/Lychee falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 43.1 out of 100 and is rated Weak, and ten of its 105 critical findings are security problems.

Code Health, at 37.5, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is removing the copied code, worth about 2.7 points. Making the controls keyboard-usable comes next, worth about 2.4 points.

Seven settings leave the servers or containers unsafe. Two known security holes in the packages the code depends on can be used by attackers, and twenty-seven controls can't be used without a mouse. Making the controls work with a keyboard, correcting the unsafe settings and updating the vulnerable packages would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once. The 19 buttons or links with no name need a name, even when they only show an icon.

The product code is 282,590 lines, about €380,000 to rebuild.

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.
Code Health 37.5 · counts for 45%Accessibility 39.6 · counts for 25%Production Readiness 41.1 · counts for 14%Domain Modelling 55.3 · counts for 8%Security and Compliance 70.3 · counts for 4%Architecture 75.3 · counts for 2%Maturity 82.7 · counts for 1%Performance 100.0 · counts for 1%

The weakest lenses score close to each other, so improving any of them moves the score.

Code composition: what the lines of code are
Product code 74%Tests 26%
New since the last survey: 180 findings

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

  • Code Duplication · Edited copy of a member (58 corresponding lines) app/Actions/Album/StructOfArrays/BuildAlbumDataResource.php
  • Code Duplication · Edited copy of a member (64 corresponding lines) app/Console/Commands/RecomputeAlbumSizes.php
  • Code Duplication · Edited copy of a member (47 corresponding lines) app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php
  • Code Duplication · Edited copy of a member (31 corresponding lines) app/Http/Requests/Album/UpdatePersonAlbumRequest.php
  • Code Duplication · Edited copy of a member (33 corresponding lines) app/Http/Requests/ShopManagement/PurchasableAlbumRequest.php
  • Code Duplication · Edited copy of a member (22 corresponding lines) app/Http/Resources/Models/HeadPersonAlbumResource.php
  • Code Duplication · Edited copy of a member (42 corresponding lines) app/Actions/Statistics/Spaces.php
  • Code Duplication · Edited copy of a member (28 corresponding lines) app/Http/Controllers/Gallery/AlbumController.php
  • Code Duplication · Edited copy of a member (39 corresponding lines) app/Jobs/DispatchFaceScanJob.php
  • Code Duplication · Edited copy of a member (45 corresponding lines) app/Actions/Statistics/Spaces.php
  • Code Duplication · Edited copy of a member (27 corresponding lines) app/Actions/Renamer/PreviewAlbums.php
  • Code Duplication · Edited copy of a member (30 corresponding lines) app/Repositories/AlbumRepository.php
  • Code Duplication · Edited copy of a member (15 corresponding lines) app/Actions/Album/Delete.php
  • Code Duplication · Edited copy of a member (35 corresponding lines) app/Console/Commands/ImageProcessing/MoveToS3.php
  • Code Duplication · Edited copy of a member (38 corresponding lines) app/Console/Commands/RecomputeAlbumSizes.php
  • Code Duplication · Edited copy of a member (33 corresponding lines) app/Actions/Diagnostics/Pipes/Checks/AiVisionFaceRecognitionServiceCheck.php
  • Code Duplication · Edited copy of a member (31 corresponding lines) app/Policies/PhotoPolicy.php
  • Code Duplication · Edited copy of a member (14 corresponding lines) app/Http/Requests/UserManagement/AddUserRequest.php
  • Code Duplication · Edited copy of a member (16 corresponding lines) app/Http/Controllers/Admin/LandingFeaturedItemController.php
  • Code Duplication · Edited copy of a member (17 corresponding lines) app/Http/Requests/Search/GetSearchRequest.php
  • Code Duplication · Edited copy of a member (18 corresponding lines) app/Actions/Renamer/RenameAlbums.php
  • Code Duplication · Edited copy of a member (14 corresponding lines) app/Actions/Import/Pipes/DeleteMissingPhotos.php
  • Code Duplication · Edited copy of a member (9 corresponding lines) app/Http/Requests/Renamer/CreateRenamerRuleRequest.php
  • Code Duplication · Edited copy of a member (22 corresponding lines) app/Http/Controllers/Admin/Maintenance/BackfillAlbumSizes.php
  • Code Duplication · Edited copy of a member (20 corresponding lines) app/DTO/BulkAlbumPatchData.php
  • Code Duplication · Edited copy of a member (12 corresponding lines) app/Http/Controllers/AiVision/FaceClusterController.php
  • Code Duplication · Edited copy of a member (11 corresponding lines) app/Actions/Album/StructOfArrays/QueryChildrenForPerson.php
  • Code Duplication · Edited copy of a member (11 corresponding lines) app/Http/Requests/Traits/Authorize/AuthorizeCanMergeAlbumsTrait.php
  • Code Duplication · Edited copy of a member (19 corresponding lines) app/Policies/AlbumPolicy.php
  • Code Duplication · Edited copies of one member (5 members, 21+ corresponding lines) app/Http/Controllers/Gallery/AlbumListing/AlbumChildrenController.php
  • Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) app/Http/Controllers/Gallery/AlbumListController.php
  • Code Duplication · Edited copy of a member (18 corresponding lines) app/Actions/Album/CreatePersonAlbum.php
  • Code Duplication · Edited copy of a member (20 corresponding lines) app/Image/Files/NativeLocalFile.php
  • Code Duplication · Edited copy of a member (13 corresponding lines) app/Http/Requests/Face/AssignFaceRequest.php
  • Code Duplication · Edited copy of a member (14 corresponding lines) app/Http/Resources/Models/ThumbAlbumResource.php
  • Code Duplication · Edited copy of a member (29 corresponding lines) app/Image/ColourExtractor/ImageFactoryForColourExtraction.php
  • Code Duplication · Edited copy of a member (9 corresponding lines) app/Jobs/UploadSizeVariantToS3Job.php
  • Code Duplication · Edited copy of a member (14 corresponding lines) app/Http/Controllers/Gallery/FlowListController.php
  • Code Duplication · Edited copy of a member (16 corresponding lines) app/DTO/Delete/PhotosToBeDeletedDTO.php
  • Code Duplication · Edited copy of a member (15 corresponding lines) app/Http/Controllers/Admin/ShopManagementController.php
  • Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php
  • Code Duplication · Edited copy of a member (13 corresponding lines) app/Http/Controllers/StatisticsController.php
  • Code Duplication · Edited copy of a member (9 corresponding lines) app/Services/BucketKeys.php
  • Code Duplication · Edited copy of a member (19 corresponding lines) app/DTO/Delete/PhotosToBeDeletedDTO.php
  • Code Duplication · Edited copy of a member (16 corresponding lines) app/DTO/WebhookPayload.php
  • Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) app/Http/Middleware/AdminUserStatus.php
  • Code Duplication · Edited copy of a member (13 corresponding lines) app/Http/Controllers/Admin/UserManagementController.php
  • Code Duplication · Edited copy of a member (18 corresponding lines) app/Http/Controllers/Admin/Maintenance/PurgeOrphanFaceEmbeddings.php
  • Code Duplication · Edited copy of a member (22 corresponding lines) app/Image/Files/LoadTemporaryFileTrait.php
  • Code Duplication · Edited copy of a member (15 corresponding lines) app/Http/Controllers/Gallery/AlbumTracksController.php
  • Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) app/Http/Resources/Collections/PaginatedModerationResource.php
  • Code Duplication · Edited copy of a member (7 corresponding lines) app/Http/Resources/Flow/FlowResource.php
  • Code Duplication · Edited copy of a member (10 corresponding lines) app/Policies/AlbumPolicy.php
  • Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) app/Http/Controllers/Gallery/SearchListingController.php
  • Code Duplication · Edited copy of a member (10 corresponding lines) app/Http/Resources/Models/Utils/PreComputedPhotoData.php
  • Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) app/Relations/HasManyBidirectionally.php
  • Code Duplication · Edited copy of a member (12 corresponding lines) app/Http/Resources/Shop/PurchasablePixelSizeResource.php
  • Code Duplication · Edited copy of a member (14 corresponding lines) app/Http/Resources/GalleryConfigs/InitConfig.php
  • Code Duplication · Edited copy of a member (12 corresponding lines) app/Http/Requests/Album/SetAsCoverRequest.php
  • Code Duplication · Edited copy of a member (8 corresponding lines) app/Actions/Album/StructOfArrays/QueryRightsForAlbum.php
  • Code Duplication · Edited copy of a member (21 corresponding lines) app/Policies/AlbumPolicy.php
  • Code Duplication · Edited copy of a member (9 corresponding lines) app/Http/Resources/Search/ResultsResource.php
  • Code Duplication · Edited copy of a member (6 corresponding lines) app/Actions/Diagnostics/Pipes/Checks/AuthDisabledCheck.php
  • Code Duplication · Edited copy of a member (8 corresponding lines) app/Actions/Shop/PurchasableService.php
  • Code Duplication · Edited copy of a member (6 corresponding lines) app/Http/Requests/ShopManagement/PrintSize/CreatePrintSizeRequest.php
  • Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) app/Listeners/ManagedCacheAlbumListingInvalidator.php
  • Code Duplication · Edited copy of a member (14 corresponding lines) app/Models/Extensions/ThrowsConsistentExceptions.php
  • Code Duplication · Edited copy of a member (11 corresponding lines) app/Models/PersonAlbum.php
  • Code Duplication · Edited copy of a member (11 corresponding lines) app/SmartAlbums/BaseSmartAlbum.php
  • Code Duplication · Edited copies of one member (3 members, 26+ corresponding lines) app/Actions/Shop/OrderService.php
  • Code Duplication · Edited copy of a member (7 corresponding lines) app/Jobs/ImportImageJob.php
  • Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) app/Http/Requests/Basket/AddPhotoToBasketRequest.php
  • Code Duplication · Edited copy of a member (6 corresponding lines) app/Actions/Albums/Top.php
  • Code Duplication · Edited copy of a member (10 corresponding lines) app/DTO/AlbumSortingCriterion.php
  • Code Duplication · Edited copy of a member (8 corresponding lines) app/Services/BucketKeys.php
  • Code Duplication · Edited copy of a member (6 corresponding lines) app/Http/Requests/Album/RenameAlbumTrackRequest.php
  • Code Duplication · Edited copy of a member (15 corresponding lines) app/Relations/HasManyChildAlbums.php
  • Code Duplication · Edited copy of a member (11 corresponding lines) app/Http/Requests/Photo/GetPhotoRatiosRequest.php
  • Code Duplication · Edited copy of a member (7 corresponding lines) app/Http/Requests/Photo/MovePhotosRequest.php
  • Code Duplication · Edited copies of one member (4 members, 5+ corresponding lines) app/Http/Resources/Admin/PaginatedBulkAlbumResource.php
  • Code Duplication · Edited copies of one member (5 members, 10+ corresponding lines) app/Policies/AlbumPolicy.php
  • Code Duplication · Edited copy of a member (5 corresponding lines) app/Actions/WebAuthn/VerifyLogin.php
  • Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) app/Exceptions/Handlers/AdminSetterHandler.php
  • Code Duplication · Edited copy of a member (6 corresponding lines) app/Http/Requests/Photo/RotatePhotoRequest.php
  • Code Duplication · Edited copies of one member (4 members, 8+ corresponding lines) app/Policies/PhotoPolicy.php
  • Code Duplication · Edited copy of a member (6 corresponding lines) app/Models/Extensions/FiltersUploadValidation.php
  • Code Duplication · Edited copy of a member (10 corresponding lines) app/Actions/Diagnostics/Pipes/Checks/ForeignKeyListInfo.php
  • Code Duplication · Edited copy of a member (5 corresponding lines) app/Http/Requests/LandingLink/PatchLandingLinkRequest.php
  • Code Duplication · Edited copy of a member (4 corresponding lines) app/Http/Controllers/Gallery/AlbumTracksController.php
  • Code Duplication · Edited copy of a member (10 corresponding lines) app/Http/Requests/Flow/FlowRequest.php
  • Code Duplication · Edited copy of a member (3 corresponding lines) app/Models/PersonAlbum.php
  • Code Duplication · Edited copy of a member (4 corresponding lines) app/Http/Requests/ShopManagement/PixelSize/CreatePixelSizeRequest.php
  • Code Duplication · Edited copy of a member (7 corresponding lines) app/SmartAlbums/OneStarAlbum.php
  • Code Duplication · Edited copy of a member (5 corresponding lines) database/factories/AlbumFactory.php
  • Code Duplication · Edited copy of a member (6 corresponding lines) app/Enum/TimelineAlbumGranularity.php
  • Code Duplication · Edited copy of a member (4 corresponding lines) app/Http/Requests/Face/GetFaceQueueRequest.php
  • Code Duplication · Edited copy of a member (5 corresponding lines) app/Http/Controllers/AiVision/FaceDetectionController.php
  • Code Duplication · Edited copy of a member (7 corresponding lines) app/Http/Resources/Shop/PixelSizeResource.php
  • Code Duplication · Edited copy of a member (3 corresponding lines) app/Actions/Photo/Pipes/Init/AbstractInitPipe.php
  • Code Duplication · Edited copy of a member (2 corresponding lines) app/Http/Requests/Album/SetPinnedRequest.php

We compare 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: 1579 findings

These 1579 critical or serious findings were in the previous survey, on 5 November 2026, and are gone from this one. The first 100 are listed here.

  • Cognitive Complexity · dragAndSelect.useDragAndSelect.getPhotoBoxesV3 (cognitive 19) resources/js/composables/album/dragAndSelect.ts
  • Cognitive Complexity · check_translations.checkFile (cognitive 18) scripts/check_translations.php
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) app/Services/Image/FacialRecognitionService.php
  • Code Duplication · Duplicated block (18 lines × 2) app/Actions/Import/Pipes/DeleteMissingAlbums.php
  • Code Duplication · Duplicated block (16 lines × 2) app/Services/Image/FacialRecognitionService.php
  • Code Duplication · Duplicated block (14 lines × 2) app/Services/Image/FacialRecognitionService.php
  • Code Duplication · Duplicated block (13 lines × 2) app/Relations/HasManyPhotosByTag.php
  • Code Duplication · Duplicated block (12 lines × 2) database/factories/OrderItemFactory.php
  • Code Duplication · Duplicated block (11 lines × 2) app/Actions/Tag/DeleteTag.php
  • Code Duplication · Duplicated block (8 lines × 2) app/Image/SizeVariantDimensionHelpers.php
  • Code Duplication · Duplicated block (7 lines × 2) app/Actions/Import/Pipes/DeleteMissingAlbums.php
  • Code Duplication · Duplicated block (6 lines × 2) app/Actions/Tag/ListTags.php
  • Code Duplication · Duplicated block (62 lines × 2) database/factories/PaletteFactory.php
  • Code Duplication · Duplicated block (28 lines × 3) database/factories/PaletteFactory.php
  • Code Duplication · Duplicated block (5 lines × 2) app/Http/Requests/ShopManagement/PixelSize/DeletePixelSizeRequest.php
  • Code Duplication · Duplicated block (8 lines × 2) app/Models/Album.php
  • REDACTED Scanning · Leaked secret: hardcoded-credential database/factories/UserFactory.php
  • REDACTED Scanning · Leaked secret: REDACTED REDACTED
  • REDACTED Scanning · Leaked secret: REDACTED REDACTED
  • Churn × Complexity Hotspots · Hotspot: resources/js/v8/components/gallery/albumModule/AlbumPanel.vue resources/js/v8/components/gallery/albumModule/AlbumPanel.vue
  • Churn × Complexity Hotspots · Hotspot: resources/js/v8/utils/phpDateFormat.ts resources/js/v8/utils/phpDateFormat.ts
  • Churn × Complexity Hotspots · Hotspot: app/Models/Configs.php app/Models/Configs.php
  • Churn × Complexity Hotspots · Hotspot: app/Console/Commands/ImageProcessing/Takedate.php app/Console/Commands/ImageProcessing/Takedate.php
  • Churn × Complexity Hotspots · Hotspot: resources/js/composables/useAdminTiles.ts resources/js/composables/useAdminTiles.ts
  • Churn × Complexity Hotspots · Repeated repair: resources/js/v8/components/gallery/albumModule/Virtualized/AlbumRootGridVirtual.vue resources/js/v8/components/gallery/albumModule/Virtualized/AlbumRootGridVirtual.vue
  • Churn × Complexity Hotspots · Repeated repair: app/Http/Requests/Photo/UploadPhotoRequest.php app/Http/Requests/Photo/UploadPhotoRequest.php
  • Secrets (history) · High secret: WD-SECRET-0005 app/Http/Controllers/Administration/UserController.php
  • Secrets (history) · High secret: WD-SECRET-0005 app/Http/Controllers/AlbumController.php
  • Secrets (history) · High secret: WD-SECRET-0005 app/Http/Controllers/AlbumController.php
  • Secrets (history) · High secret: WD-SECRET-0005 app/Http/Controllers/AlbumController.php
  • Secrets (history) · High secret: WD-SECRET-0005 app/Http/Controllers/AlbumController.php
  • Secrets (history) · High secret: WD-SECRET-0005 app/Http/Controllers/AlbumController.php
  • Secrets (history) · High secret: WD-SECRET-0005 app/Http/Controllers/AlbumController.php
  • Secrets (history) · High secret: WD-SECRET-0005 app/Http/Controllers/AlbumController.php
  • Secrets (history) · High secret: WD-SECRET-0005 app/Http/Controllers/AlbumController.php
  • Secrets (history) · High secret: WD-SECRET-0005 app/Http/Controllers/AlbumController.php
  • Secrets (history) · High secret: WD-SECRET-0005 app/Http/Controllers/Auth/RegisterController.php
  • Secrets (history) · High secret: WD-SECRET-0005 app/Http/Controllers/SettingsController.php
  • Secrets (history) · High secret: WD-SECRET-0005 app/Http/Controllers/SettingsController.php
  • Secrets (history) · High secret: WD-SECRET-0005 app/Http/Controllers/SettingsController.php
  • Secrets (history) · High secret: WD-SECRET-0005 app/Http/Controllers/UserController.php
  • Secrets (history) · High secret: WD-SECRET-0005 app/Http/Controllers/UserController.php
  • Secrets (history) · High secret: WD-SECRET-0005 app/Http/Controllers/UserController.php
  • Secrets (history) · High secret: WD-SECRET-0005 app/Http/Requests/UserRequests/UsernamePasswordRequest.php
  • Secrets (history) · REDACTED: REDACTED database/factories/UserFactory.php
  • Secrets (history) · High secret: WD-SECRET-0005 REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Supply-chain Provenance & Signing · Workflow token grant is wider than its jobs use .github/workflows/docker_build.yml
  • Code Duplication · Duplication concentrated across 3 sibling directories (5 clone groups) resources/js/v8/components/gallery/albumModule/AlbumPanel.vue
  • Code Duplication · Duplicated block with local edits (288 matched lines × 2 locations) resources/js/v7/views/gallery-panels/Search.vue
  • Code Duplication · Duplicated block with local edits (249 matched lines × 2 locations) resources/js/v7/components/gallery/albumModule/AlbumPanel.vue
  • Code Duplication · Duplicated block with local edits (195 matched lines × 2 locations) resources/js/v7/views/gallery-panels/Timeline.vue
  • Code Duplication · Duplicated block with local edits (138 matched lines × 2 locations) resources/js/v7/components/drawers/LiveMetrics.vue
  • Code Duplication · Duplicated block with local edits (126 matched lines × 2 locations) resources/js/v7/views/gallery-panels/Albums.vue
  • Code Duplication · Duplicated block (97 lines × 2 locations) resources/js/v7/views/admin/Jobs.vue
  • Code Duplication · Duplicated block with local edits (83 matched lines × 2 locations) resources/js/v7/views/gallery-panels/Flow.vue
  • Code Duplication · Wholesale file copy (75 identical lines × 2 files) resources/js/v7/views/Contact.vue
  • Code Duplication · Wholesale file copy (70 identical lines × 2 files) resources/js/v7/components/forms/gallery-dialogs/DeleteDialog.vue
  • Code Duplication · Wholesale file copy (68 identical lines × 2 files) resources/js/v7/components/forms/card/CardForm.vue
  • Code Duplication · Wholesale file copy (68 identical lines × 2 files) resources/js/v7/components/gallery/albumModule/AlbumHero.vue
  • Code Duplication · Wholesale file copy (68 identical lines × 2 files) resources/js/v7/components/modals/DownloadPhoto.vue
  • Code Duplication · Duplicated block with local edits (68 matched lines × 2 locations) resources/js/v7/views/face-recog/People.vue
  • Code Duplication · Duplicated block with local edits (67 matched lines × 2 locations) resources/js/layouts/PhotoLayout.ts
  • Code Duplication · Wholesale file copy (67 identical lines × 2 files) resources/js/v7/components/modals/ImportFromServer.vue
  • Code Duplication · Duplicated block with local edits (66 matched lines × 2 locations) resources/js/v7/components/forms/group/AddUserGroupModal.vue
  • Code Duplication · Duplicated block with local edits (65 matched lines × 2 locations) resources/js/v7/components/forms/bulk-album-edit/BulkEditFieldsDialog.vue
  • Code Duplication · Wholesale file copy (65 identical lines × 2 files) resources/js/v7/components/forms/sharing/BulkSharingModal.vue
  • Code Duplication · Duplicated block (65 lines × 2 locations) resources/js/v7/views/RenamerRules.vue
  • Code Duplication · Wholesale file copy (63 identical lines × 2 files) resources/js/v7/components/gallery/photoModule/Dock.vue
  • Code Duplication · Duplicated block (62 lines × 2 locations) resources/js/v7/components/forms/upload/DropBoxChooser.vue
  • Code Duplication · Wholesale file copy (61 identical lines × 2 files) resources/js/v7/components/gallery/photoModule/PhotoPanel.vue
  • Code Duplication · Wholesale file copy (60 identical lines × 2 files) resources/js/v7/components/forms/profile/SetLogin.vue
  • Code Duplication · Duplicated block (60 lines × 2 locations) resources/js/v7/components/gallery/albumModule/HeaderFocusPicker.vue
  • Code Duplication · Wholesale file copy (58 identical lines × 2 files) resources/js/v7/components/forms/album/Unlock.vue
  • Code Duplication · Duplicated block (58 lines × 2 locations) resources/js/v7/components/gallery/tagModule/TagPanel.vue
  • Code Duplication · Wholesale file copy (57 identical lines × 2 files) resources/js/v7/components/forms/auth/LoginForm.vue
  • Code Duplication · Duplicated block (57 lines × 2 locations) resources/js/v7/components/modals/faceRecog/SelfieClaimModal.vue
  • Code Duplication · Wholesale file copy (57 identical lines × 2 files) resources/js/v7/views/DuplicatesFinder.vue
  • Code Duplication · Wholesale file copy (56 identical lines × 2 files) resources/js/v7/components/forms/gallery-dialogs/AlbumMergeDialog.vue
  • Code Duplication · Wholesale file copy (55 identical lines × 2 files) resources/js/v7/components/forms/profile/SetSharedAlbumsVisibility.vue
  • Code Duplication · Wholesale file copy (55 identical lines × 2 files) resources/js/v7/components/gallery/albumModule/PhotoThumbPanelList.vue
  • Code Duplication · Duplicated block (54 lines × 2 locations) resources/js/composables/selections/selections.ts
  • Code Duplication · Duplicated block (53 lines × 2 locations) resources/js/v7/components/forms/photo/PhotoCopyDialog.vue
  • Code Duplication · Duplicated block (52 lines × 2 locations) resources/js/v7/components/forms/webhooks/WebhookFormDialog.vue
  • Code Duplication · Wholesale file copy (51 identical lines × 2 files) resources/js/v7/components/forms/gallery-dialogs/RenameDialog.vue
  • Code Duplication · Wholesale file copy (51 identical lines × 2 files) resources/js/v7/components/maintenance/MaintenanceGenSizevariants.vue
  • Code Duplication · Wholesale file copy (51 identical lines × 2 files) resources/js/v7/components/modals/DownloadAlbum.vue
  • Code Duplication · Wholesale file copy (50 identical lines × 2 files) resources/js/composables/album/uploadEvents.ts
  • Code Duplication · Duplicated block (50 lines × 2 locations) resources/js/v7/components/forms/album/AlbumCreateShareDialog.vue
  • Code Duplication · Wholesale file copy (50 identical lines × 2 files) resources/js/v7/components/forms/card/Card.vue
  • Code Duplication · Duplicated block (49 lines × 2 locations) resources/js/v7/components/forms/sharing/ShareLine.vue
  • Code Duplication · Duplicated block with local edits (48 matched lines × 2 locations) resources/js/stores/AlbumState.ts
  • Code Duplication · Duplicated block (48 lines × 2 locations) resources/js/v7/components/forms/photo/PhotoTagDialog.vue
  • Code Duplication · Duplicated block with local edits (47 matched lines × 2 locations) resources/js/services/album-service.ts
  • Code Duplication · Duplicated block (47 lines × 2 locations) resources/js/v7/views/admin/shop/PrintPixelSizesAdmin.vue
  • Code Duplication · Duplicated block (47 lines × 2 locations) resources/js/v7/views/face-recog/People.vue
  • Code Duplication · Duplicated block (46 lines × 2 locations) resources/js/composables/contextMenus/leftMenu.ts
  • Code Duplication · Duplicated block (46 lines × 3 locations) resources/js/v7/components/forms/album/AlbumCreateShareDialog.vue
  • Code Duplication · Duplicated block (46 lines × 2 locations) resources/js/v7/components/forms/search/SearchBox.vue
Rebuild cost: about €380,000 · Estimate
Cost to rebuild€130,000 to €640,000, for 2,109 to 6,689 hours of work, about 2.6 person-years for 1 to 5 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 43. 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: 282,590 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price 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
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.
Raises the score by about 2.7 points · Medium effort · Code Duplication
2
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Raises the score by about 2.4 points · Medium effort · Keyboard semantics
3
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.
Raises the score by about 2.0 points · Medium effort · Nullable reference types

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 €380,000 to build again, about 2.6 person-years of work. Its weakest lens is Code Health, at 37.5 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
One cause behind 75 Domain Modelling findings · Common cause
75 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 (35 findings) · Rich vs anemic model (40 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
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Of all the actions in this report, it raises the score most for the work it takes: about 2.7 points for medium effort. 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.

304 modules, with 735 dependencies between them. One loop runs through 32 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 264 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 Models.Builders2 Image3 Models.Extensions4 Policies5 Http.Resources.GalleryConfigs6 Image.Files7 SmartAlbums8 Http.Resources.Models.Utils9 Http.Resources.V310 Http.Resources.Models11 Models12 Contracts.PhotoCreate13 Services14 Repositories15 Enum16 DTO.PhotoCreate17 Factories18 Listeners19 Services.Image20 Actions.Shop21 Http.Requests22 Actions.Photo23 DTO24 Actions.Diagnostics.Pipes.Checks25 Actions.User26 Contracts.Models27 Http.Resources.Collections28 Jobs29 Actions.Album30 Actions.Albums31 Actions.Photo.StructOfArrays32 Contracts.Http.Requests33 Http.Controllers34 Http.Controllers.Admin35 Http.Controllers.Admin.Maintenance36 Http.Controllers.AiVision37 Actions.Search.StructOfArrays38 Http.Requests.Photo39 Http.Controllers.Gallery40 Http.Controllers.Gallery.AlbumListing
1 Models.Builders
2 Image241232
3 Models.Extensions4332
4 Policies111531
5 Http.Resources.GalleryConfigs111331
6 Image.Files41
7 SmartAlbums112111
8 Http.Resources.Models.Utils114351
9 Http.Resources.V31
10 Http.Resources.Models111123611431
11 Models17511923
12 Contracts.PhotoCreate15
13 Services1149124
14 Repositories1212
15 Enum1
16 DTO.PhotoCreate444224
17 Factories111221
18 Listeners2111
19 Services.Image1132
20 Actions.Shop11511511
21 Http.Requests1
22 Actions.Photo127141243
23 DTO21911
24 Actions.Diagnostics.Pipes.Checks1151311
25 Actions.User15321
26 Contracts.Models1321
27 Http.Resources.Collections122
28 Jobs114253243
29 Actions.Album3311181231
30 Actions.Albums13132221
31 Actions.Photo.StructOfArrays11148331115
32 Contracts.Http.Requests1112822
33 Http.Controllers113231
34 Http.Controllers.Admin119131126
35 Http.Controllers.Admin.Maintenance21112111
36 Http.Controllers.AiVision11261357
37 Actions.Search.StructOfArrays24101121
38 Http.Requests.Photo2119133
39 Http.Controllers.Gallery12471211241024434144415
40 Http.Controllers.Gallery.AlbumListing516635512144
Uses a module listed above itPart of a loopThe module itself
1 Models.Builders2 Image3 Models.Extensions4 Policies5 Http.Resources.GalleryConfigs6 Image.Files7 SmartAlbums8 Http.Resources.Models.Utils9 Http.Resources.V310 Http.Resources.Models11 Models12 Contracts.PhotoCreate13 Services14 Repositories15 Enum16 DTO.PhotoCreate17 Factories18 Listeners19 Services.Image20 Actions.Shop21 Http.Requests22 Actions.Photo23 DTO24 Actions.Diagnostics.Pipes.Checks25 Actions.User26 Contracts.Models27 Http.Resources.Collections28 Jobs29 Actions.Album30 Actions.Albums31 Actions.Photo.StructOfArrays32 Contracts.Http.Requests33 Http.Controllers34 Http.Controllers.Admin35 Http.Controllers.Admin.Maintenance36 Http.Controllers.AiVision37 Actions.Search.StructOfArrays38 Http.Requests.Photo39 Http.Controllers.Gallery40 Http.Controllers.Gallery.AlbumListingModels.Builders1Image2Models.Extensions3Policies4Http.Resources.GalleryConfigs5Image.Files6SmartAlbums7Http.Resources.Models.Utils8Http.Resources.V39Http.Resources.Models10Models11Contracts.PhotoCreate12Services13Repositories14Enum15DTO.PhotoCreate16Factories17Listeners18Services.Image19Actions.Shop20Http.Requests21Actions.Photo22DTO23Actions.Diagnostics.Pipes.Checks24Actions.User25Contracts.Models26Http.Resources.Collections27Jobs28Actions.Album29Actions.Albums30Actions.Photo.StructOfArrays31Contracts.Http.Requests32Http.Controllers33Http.Controllers.Admin34Http.Controllers.Admin.Maintenance35Http.Controllers.AiVision36Actions.Search.StructOfArrays37Http.Requests.Photo38Http.Controllers.Gallery39Http.Controllers.Gallery.AlbumListing402412324332111531111331411121111143511111123611431175119231511491241212144422411122121111132115115111127141243219111151311153211321122114253243331118123113132221111483311151112822113231119131126211121111126135724101121211913312471211241024434144415516635512144+264 more modules (most-connected shown)

At a glance — Code Health · 37.5 · Weak · gated by R10, X5 ·

At a glance — Architecture · 75.3 · Strong ·

At a glance — Maturity · 82.7 · Strong ·

At a glance — Readiness · 41.1 · Weak · gated by R8, P5 ·

At a glance — Security · 70.3 · Strong ·

At a glance — Domain Modelling · 55.3 · Adequate · gated by DM4, DM5 ·

At a glance — Accessibility · 39.6 · Weak · gated by AC2, AC4 ·

At a glance — Performance · 100.0 · Exemplary ·

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
A02:2025 — Security Misconfiguration12High / Critical
A03:2025 — Software Supply Chain Failures9High / Critical
A05:2025 — Injection8High / Critical
A07:2025 — Authentication Failures4Medium

Roadmap

Top priorities: 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; Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; 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.

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

Do thisHelpsEffortDimension
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.+2.7 ptsMediumCode Duplication
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.+2.4 ptsMediumKeyboard semantics
Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.+2.0 ptsMediumNullable reference types
Resolve the 1 finding(s) in DR & Backup.+1.9 ptsMediumDR & Backup
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.+1.9 ptsMediumDependency Hygiene
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.+1.5 ptsMediumCancellation propagation
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.+1.4 ptsMediumForms & labels
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).+1.4 ptsMediumEncapsulated state

File quality

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

FileScoreBandWorst signal
REDACTED2.7SlopIaC & Container Security: High IaC: REDACTED
REDACTED4.1MixedIaC & Container Security: High IaC: REDACTED
app/Http/Resources/GalleryConfigs/InitConfig.php4.9MixedCyclomatic Complexity: InitConfig.__construct (cyclomatic 18)
REDACTED5.1MixedDependency Vulnerabilities: High CVE: REDACTED
REDACTED5.1MixedIaC & Container Security: High IaC: REDACTED
REDACTED5.1MixedIaC & Container Security: High IaC: REDACTED
app/Metadata/Extractor.php6.0MixedExplicit Debt: TodoComment
app/Actions/Album/BaseArchive.php6.0MixedExplicit Debt: TodoComment
app/Console/Commands/ImageProcessing/VideoData.php6.7MixedExplicit Debt: TodoComment
app/Policies/AlbumQueryPolicy.php6.7MixedExplicit Debt: TodoComment
app/Metadata/DiskUsage.php6.9MixedExplicit Debt: TodoComment
app/Actions/Shop/OrderService.php7.0MixedCode Duplication: Edited copies of one member (3 members, 26+ corresponding lines)
app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php7.0MixedCyclomatic Complexity: QueryPhotoRatios.buildResource (cyclomatic 20)
app/Actions/Statistics/Spaces.php7.0MixedCode Duplication: Edited copy of a member (42 corresponding lines)
app/Console/Commands/RecomputeAlbumSizes.php7.0MixedCode Duplication: Edited copy of a member (64 corresponding lines)
app/Policies/AlbumPolicy.php7.1MixedGod Classes: TooManyMethods: AlbumPolicy
app/Actions/Album/StructOfArrays/BuildAlbumDataResource.php7.1MixedCode Duplication: Edited copy of a member (58 corresponding lines)
resources/js/embed/config.ts7.2MixedCyclomatic Complexity: config.parseDataAttributes (cyclomatic 28)
resources/js/composables/contextMenus/leftMenu.ts7.2MixedCyclomatic Complexity: leftMenu.useLeftMenu.items (cyclomatic 23)
resources/js/composables/useSearchTokenAssembler.ts7.2MixedCyclomatic Complexity: useSearchTokenAssembler.parseTokens (cyclomatic 20)

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 — 105

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 — 766

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 — 222

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

Could not be resolved — 14

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

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 87 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

Every figure here is one of two 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. 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.

What we checked — 87 dimensions across the health lenses
D1D2D3D4D5D6D7D10D12D13D14D15D16D17D19D20D23D24D25D27D28D29D30D31D34D35D36D37D43D44AC1AC2AC3AC4AC5AC6AX10AX3AX4AX6C1C2C4DM1DM11DM4DM5DM9M1M2M3M4P1P2P3P4P5P6P7P8PF3R1R10R11R2R3R4R5R6R7R8R9S1X14X16X19X2X21X23X25X27X28X29X3X30X4X5

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, 1077 of 1093 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 or a scanner, 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
Canine Code Analyzer 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

Every finding is locatable in findings.md. Run 01a1ea66-4b28-7f59-802e-69b31309adc4.

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.

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — the repository root (@playwright/test) — a gap in the analyzer, not something this repository is missing. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
  • D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 239 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 711 test source file(s) (.php) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.php, .ts) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its Composer package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (composer.json), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
  • D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
  • D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (180148 LoC, 1980 module-visible types across 258 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
  • D27 Navigability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Tracing effort is measured over resolved call sites, and all 1059 sampled here came from .php files. This repository's .ts source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `app/Actions/Album/Breadcrumb.php`, `app/Actions/Album/Create.php`, `app/Actions/Album/ListAlbums.php`, `app/Actions/Album/StructOfArrays/QueryChildrenForAlbum.php`, `app/Actions/Album/StructOfArrays/QueryChildrenForPerson.php`, … (+132 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • AC2 Forms & labels — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 196 further occurrence(s) are not listed individually; the score already reflects all 236.
  • AC4 Keyboard semantics — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 46 further occurrence(s) are not listed individually; the score already reflects all 86.
  • AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Laravel's service container and a PSR-11 container (Psr\Container), whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 1 — a container did not start, exited, or never became healthy) — container lychee-facial-recognition is unhealthy; runtime evidence skipped.
  • C1 Data Protection — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • C2 Access Controls — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • C4 Data Retention — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • DM4 Rich vs anemic model — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 8 further occurrence(s) are not listed individually; the score already reflects all 48.
  • DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
  • DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
  • DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
  • GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's PHP, Vue components is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's PHP, Vue components is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A badge or prose version claim scored 9/17 in its adjudication (docs/plans/deterministic-engine/adjudication/M4-v3.md: badges 9/9, prose 0/8, where prose versions are minimums or history), short of the 95 % precision gate, so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them. The .NET and Node.js version checks are a different kind and still publish.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 399 further occurrence(s) are not listed individually; the score already reflects all 439.
  • R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 37 further occurrence(s) are not listed individually; the score already reflects all 77.
  • R3 Large Files — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 3 further occurrence(s) are not listed individually; the score already reflects all 43.
  • R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 274 further occurrence(s) are not listed individually; the score already reflects all 314.
  • X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X10 Duplicated predicate — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 24 further occurrence(s) are not listed individually; the score already reflects all 64.
  • X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 140 further occurrence(s) are not listed individually; the score already reflects all 180.
  • X27 Collection changed while being enumerated — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 14 further occurrence(s) are not listed individually; the score already reflects all 54.
  • X4 Structured logging — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 23 further occurrence(s) are not listed individually; the score already reflects all 63.
  • X7 Silent fallback defaults — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 78 further occurrence(s) are not listed individually; the score already reflects all 118.

Repo exclusion declarations: 3 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

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

Per-dimension blind spots

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.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D25 ADR Conformance: ADR conformance checks only decisions stated in a checkable form (a ruled-out element, package or dependency, an adr-rules block, a declared delivery status): a decision written only as prose is unverifiable, and decisions never written down are not checked.
  • 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.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
  • DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity6.4 / 10Adequate✓ 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 6.4 / 10 · rule-coverage 100% · ceiling Prevented

34 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Extractor.createFromFile at 67. A further 3 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being phpDateFormat.phpDateFormat at 56 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: resources/js/v8/utils/phpDateFormat.ts (phpDateFormat.phpDateFormat at 56), app/Enum/SmartAlbumType.php (SmartAlbumType.is_enabled at 20). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

contextMenu.useContextMenu.photoMenu (cyclomatic 17) · ×2resources/js/composables/contextMenus/contextMenu.ts:103
Extractor.createFromFile (cyclomatic 67)app/Metadata/Extractor.php:79
useSpotlightGalleryActions.useSpotlightGalleryActions (cyclomatic 43)resources/js/v8/composables/spotlight/useSpotlightGalleryActions.ts:36
Configs.sanity (cyclomatic 41)app/Models/Configs.php:98
ExifLens.handle (cyclomatic 36)app/Console/Commands/ImageProcessing/ExifLens.php:46

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

What to do

  1. Bring the 6 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with Extractor.createFromFile (cyclomatic 67), useSpotlightGalleryActions.useSpotlightGalleryActions (cyclomatic 43), Configs.sanity (cyclomatic 41). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cyclomatic Complexity from 6.4 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.

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

D2 · Cognitive Complexity6.2 / 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.2 / 10 · rule-coverage 100% · ceiling Prevented

47 method(s) exceeded the cognitive complexity threshold of 15; the worst was Extractor.createFromFile at 84.

contextMenu.useContextMenu.photoMenu (cognitive 17) · ×2resources/js/composables/contextMenus/contextMenu.ts:103
uploadEvents.useMouseEvents.onPaste (cognitive 16) · ×2resources/js/composables/album/uploadEvents.ts:79
Extractor.createFromFile (cognitive 84)app/Metadata/Extractor.php:79
Ghostbuster.handle (cognitive 56)app/Console/Commands/Ghostbuster.php:65
ExifLens.handle (cognitive 46)app/Console/Commands/ImageProcessing/ExifLens.php:46

+ 40 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 Extractor.createFromFile (cognitive 84). — Refactoring it lifts Cognitive Complexity from 6.2 to about 6.5/10.

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

D3 · God Classes9.6 / 10Stronggated by 25 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.6 / 10 · rule-coverage 100% · ceiling Prevented

25 god class(es) detected.

FunctionTooLong: useSphereViewer.useSphereViewer · ×19resources/js/v8/composables/useSphereViewer.ts:125
TooManyMethods: CacheKeyProvider · ×3app/Services/Cache/CacheKeyProvider.php:30
MethodTooLong: InitConfig.__construct · ×3app/Http/Resources/GalleryConfigs/InitConfig.php:229

What to do

  1. Resolve the 19 FunctionTooLong finding(s) in God Classes — start with leftMenu.ts (3), contextMenu.ts (2), useAdminTiles.ts (2). — One of this dimension's main actionable groups (19 warning-level).
  2. Resolve the 3 TooManyMethods finding(s) in God Classes — start with CacheKeyProvider.php, AlbumPolicy.php, Album.php. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 3 MethodTooLong finding(s) in God Classes — start with InitConfig.php, QueryPhotoDetails.php, Extractor.php. — One of this dimension's main actionable groups (3 warning-level).

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

D4 · Code Duplication9.2 / 10Stronggated by 241 serious findings✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

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

127 duplicated block group(s) detected. 1.9 % of the production lines (5,434 of 282,590) are in a reported copy. A further 114 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Duplicated block (8 lines × 2) · ×14app/Actions/Import/Pipes/DeleteMissingAlbums.php:152
Edited copy of a member (6 corresponding lines) · ×8app/Actions/Diagnostics/Pipes/Checks/AuthDisabledCheck.php:63
Duplicated block (10 lines × 2) · ×8app/Actions/Photo/BaseArchive.php:291
Duplicated block (7 lines × 2) · ×7app/Actions/Photo/Pipes/Standalone/PlacePhoto.php:82
Duplicated block (6 lines × 2) · ×7app/Http/Requests/ShopManagement/PrintSize/CreatePrintSizeRequest.php:57

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

What to do

  1. Resolve the 14 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with DeleteMissingAlbums.php, LandingFeaturedItemController.php, MapListingController.php. — One of this dimension's main actionable groups (14 warning-level).
  2. Resolve the 8 Edited copy of a member (6 corresponding lines) finding(s) in Code Duplication — start with AuthDisabledCheck.php, CreatePrintSizeRequest.php, Top.php. — One of this dimension's main actionable groups (8 warning-level).
  3. Resolve the 8 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with BaseArchive.php, Spaces.php, MoveToS3.php. — One of this dimension's main actionable groups (8 warning-level).

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

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

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

2 production modules (npm+Composer), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 1 of the 2 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)9.8 / 10Stronggated by 5 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.8 / 10 · rule-coverage 100% · ceiling Verified

5 of 276 classes have LCOM4 above 3.

Low cohesion: Photo (LCOM4 12) · ×5app/Models/Photo.php:149

What to do

  1. Resolve the 5 Low cohesion finding(s) in Cohesion (LCOM4) — start with Photo.php, BaseAlbumImpl.php, OrderService.php. — One of this dimension's main actionable groups (5 warning-level).

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

D7 · Architectural Integrity6.0 / 10Adequate✓ Tool-verified

What it measures: Whether the code respects its intended layering / architecture rules.

Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.

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

No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).

Detailed fixes: d7_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 239 tests. Measured on the JavaScript/TypeScript suite only — at least 711 test source file(s) (.php) 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 9.4 / 10Exemplary✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.4 / 10 · rule-coverage 96% · ceiling Verified

5 outdated, 0 abandoned direct Composer dependencies. 49 of 51 direct production requirements were graded against Packagist (1 not published there, which is what a private Satis repository looks like, 1 with no release resolution). 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: dedoc/scramble · ×5

✓ On the Gold path — maintain.

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

D13 · REDACTED Scanning10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

REDACTED scan ran and found no leaked secrets. 2 password hash(es) are listed to check and are not counted as leaked credentials.

REDACTED

✓ On the Gold path — maintain.

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

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 187 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 79 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.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.9 / 10Stronggated by 24 serious findings✓ 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 9.9 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: app/Actions/Photo/StructOfArrays/QueryPhotoDetails.php (8×35=280); app/Http/Resources/GalleryConfigs/InitConfig.php (14×18=252); resources/js/composables/album/dragAndSelect.ts (8×20=160) Repeated repair below the complexity floor: resources/js/v8/components/drawers/PhotoDetails.vue (5 of 7 changes were fixes); resources/js/v8/utils/adaptPhotoTile.ts (4 of 7 changes were fixes); resources/js/v8/components/forms/auth/LoginForm.vue (4 of 6 changes were fixes)

Hotspot: app/Actions/Photo/StructOfArrays/QueryPhotoDetails.php · ×16app/Actions/Photo/StructOfArrays/QueryPhotoDetails.php:105
Repeated repair: resources/js/v8/components/drawers/PhotoDetails.vue · ×8resources/js/v8/components/drawers/PhotoDetails.vue:324

What to do

  1. Resolve the 16 Hotspot finding(s) in Churn × Complexity Hotspots — start with AlbumProperties.vue (2), contextMenu.ts (2), QueryPhotoDetails.php. — One of this dimension's main actionable groups (16 warning-level).
  2. Resolve the 8 Repeated repair finding(s) in Churn × Complexity Hotspots — start with LoginForm.vue (2), PhotoDetails.vue, adaptPhotoTile.ts. — One of this dimension's main actionable groups (8 warning-level).

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

D16 · Bus Factor8.0 / 10Strong✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

125 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is app/Policies/AlbumQueryPolicy.php. Counted over 645 of the 2627 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1

What to do

  1. Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).

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

D17 · Explicit Debt10.0 / 10Stronggated by 22 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

22 deducted task-comment markers across 282590 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 · ×22.php-cs-fixer.php:4

What to do

  1. Resolve the 22 TodoComment finding(s) in Explicit Debt — start with DiskUsage.php (3), Extractor.php (3), MoveAlbumsRequestTest.php (2). — One of this dimension's main actionable groups (22 warning-level).

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

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

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

1 of 1 documentation facets pass in full. 502 document(s) read across 1 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality9.9 / 10Exemplary✓ Tool-verified

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

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

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

1 of 39 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.

ADR decides a question another record already decideddocs/specs/6-decisions/ADR-102-01-direct-tile-urls.md:1detected by adr-integrity

✓ On the Gold path — maintain.

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

D23 · Boundary Type-Coupling10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Verified

128 domain type(s) cross context boundaries across 2 contexts; they are measured and withheld (not published, not scored). Contexts: Http, Models.

✓ On the Gold path — maintain.

Detailed fixes: d23_recommendation.md.

D24 · Comment Value9.4 9.1 / 10Exemplary✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 9.1 / 10 · rule-coverage 97% · ceiling Documented

3 of 493 judged comments only repeat the code they sit on (0.6 %). 19 comment(s) in another language or script were not judged.

redundant comment · ×3resources/js/composables/album/buyMeActions.ts:20
doc comments repeat the namesresources/js/embed/api.ts:218

✓ On the Gold path — maintain.

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

D25 · ADR Conformance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the code actually follows the decisions recorded in the project's ADRs.

Method: Each binding ADR read for checkable forms: a backticked element its Decision section rules out, a ruled-out package the manifests declare, a forbidden module dependency, an opt-in adr-rules block, and a declared delivery status the code does not yet carry. A prose decision with no checkable form is unverifiable, neither a finding nor a pass. Deterministic, no model. Advisory.

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

0 of 8 checkable records are broken by the code or by their own declared delivery (8 of 38 binding records state a rule in checkable form or declare their delivery; prose decisions are unverifiable).

✓ On the Gold path — maintain.

Detailed fixes: d25_recommendation.md.

D27 · Navigability7.2 / 10Strong✓ 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 7.2 / 10 · rule-coverage 100% · ceiling Documented

64 % of calls cross a namespace and 1 % go through an interface, but 13 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated. Measured over the .php source only — this repository's .ts was not sampled for call sites, so this score covers part of the tree, not all of it.

Scattered collaborators

What to do

  1. Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).

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

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Documented

2 finding(s): 0 critical, 0 high, 0 medium, 0 low.

REDACTED

✓ On the Gold path — maintain.

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

D29 · Static Analysis (SAST)6.7 / 10Adequate✓ 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 6.7 / 10 · rule-coverage 100% · ceiling Documented

9 finding(s): 0 critical, 1 high, 3 medium, 5 low. semgrep hit a parse error in 139 file(s) — `app/Actions/Album/Breadcrumb.php` (line 22), `app/Actions/Album/Create.php` (line 41), `app/Actions/Album/ListAlbums.php` (line 29), `app/Actions/Album/StructOfArrays/QueryChildrenForAlbum.php` (line 21, line 22, line 23), `app/Actions/Album/StructOfArrays/QueryChildrenForPerson.php` (line 24, line 25, line 26, …), … (+134 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 3 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
REDACTED
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. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

D30 · Dependency Vulnerabilities8.7 / 10Adequategated by 2 critical findings✓ Tool-verified

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. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

7 finding(s): 0 critical, 2 high, 0 medium, 1 low. 5 advisory suppression(s) declared in REDACTED, 4 stale.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 4 Stale vulnerability suppression finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 recommendation-level).
  3. Resolve the 1 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

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

D31 · IaC & Container Security7.2 / 10Adequategated by 7 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 7.2 / 10 · rule-coverage 100% · ceiling Documented

12 finding(s): 0 critical, 7 high, 5 medium, 0 low.

REDACTED
REDACTED

What to do

  1. Resolve the 7 High IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED, REDACTED. — One of this dimension's main actionable groups (7 issue-level).
  2. Resolve the 5 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 warning-level).

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

D34 · Knowledge Freshness9.2 / 10Adequategated by 2 critical findings✓ 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 9.2 / 10 · rule-coverage 100% · ceiling Documented

50 of 645 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is database/migrations/2021_12_04_181200_refactor_models.php. Counted over 645 of the 2627 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledge · ×2database/migrations/2021_12_04_181200_refactor_models.php:1
Orphaned file · ×48app/Models/Extensions/ForwardsToParentImplementation.php:1
Further orphaned files (smaller)

What to do

  1. Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with 2021_12_04_181200_refactor_models.php, 2021_06_01_181900_refactor_timestamps_anew.php. — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 48 Orphaned file finding(s) in Knowledge Freshness — start with ForwardsToParentImplementation.php, SessionOrTokenGuard.php, UTCBasedTimes.php. — One of this dimension's main actionable groups (48 recommendation-level).
  3. Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling9.4 / 10Stronggated by 14 serious 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.4 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: all_settings.php↔all_settings.php 100%; all_settings.php↔all_settings.php 100%; all_settings.php↔all_settings.php 100%

Change-coupling hub: all_settings.php → all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php · ×10lang/nl/all_settings.php
Change coupling: all_settings.php ↔ all_settings.php · ×3lang/ja/all_settings.php:1
Change coupling clique: maintenance.php, maintenance.php, maintenance.php, maintenance.php, maintenance.php, maintenance.phplang/de/maintenance.php

What to do

  1. Resolve the 10 Change-coupling hub finding(s) in Change Coupling — start with dialogs.php (8), all_settings.php (2). — One of this dimension's main actionable groups (10 warning-level).
  2. Resolve the 3 Change coupling finding(s) in Change Coupling — start with all_settings.php (2), InitConfig.php. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with maintenance.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.

D36 · Supply-chain Provenance & Signing7.5 / 10Strong✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

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

3/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d36_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 (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. Reported 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. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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. 5 advisory suppression(s) declared in REDACTED, 4 stale.

✓ 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 97 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.9 / 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.

  • Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation). (×3) — resources/js/embed/components/Lightbox.vue:40, resources/js/v7/components/gallery/photoModule/PhotoBox.vue:13, resources/js/v8/components/gallery/photoModule/PhotoBox.vue:32
  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×18) — resources/js/v7/components/drawers/LiveMetrics.vue:38, resources/js/v7/components/forms/card/Card.vue:8, resources/js/v7/components/forms/card/Card.vue:11, …
  • A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. (×2) — resources/js/v7/components/webshop/QrCodeLink.vue:2, resources/js/v8/components/webshop/QrCodeLink.vue:2

What to do

  • Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels3.5 / 10Weak✓ 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.

  • A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×9) — resources/js/v7/components/faceRecog/FaceRecognitionWarning.vue:25, resources/js/v7/components/forms/basic/rating.vue:4, resources/js/v7/components/forms/search/AdvancedSearchPanel.vue:6, …
  • A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. (×10) — resources/js/v7/components/footers/GalleryFooter.vue:9, resources/js/v7/components/footers/GalleryFooter.vue:17, resources/js/v7/components/footers/GalleryFooter.vue:25, …
  • 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. (×5) — resources/js/v7/components/forms/album/SearchTargetAlbum.vue:2, resources/js/v7/components/forms/album/SearchTargetUser.vue:2, resources/js/v7/components/forms/basic/PersonInput.vue:6, …
  • A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one. (×5) — resources/js/v7/components/forms/basic/Fieldset.vue:2, resources/js/v7/components/forms/profile/SetLogin.vue:2, resources/js/v7/components/forms/profile/SetOauth.vue:2, …
  • This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×10) — resources/js/v7/components/forms/basic/PersonInput.vue:5, resources/js/v7/components/forms/basic/PersonInput.vue:35, resources/js/v7/components/forms/search/AdvancedSearchPanel.vue:13, …
  • This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — resources/js/v7/components/forms/profile/SetSharedAlbumsVisibility.vue:13

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 structure5.5 / 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>. (×9) — resources/views/error/error.blade.php:2, resources/views/error/v1-is-dead.blade.php:2, resources/views/health-up.blade.php:2, …
  • A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×2) — resources/views/vueapp.blade.php:2, vite/index.html:2
  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — vite/index.html:2

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics1.1 / 10Critical✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

  • This <img> carries tabindex="0", so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler. — resources/js/embed/components/EmbedWidget.vue:43
  • This <div> carries tabindex="0", so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler. (×3) — resources/js/embed/components/EmbedWidget.vue:110, resources/js/embed/components/EmbedWidget.vue:151, resources/js/v7/components/gallery/albumModule/PhotoListItem.vue:2
  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×27) — resources/js/v7/components/drawers/AlbumEdit.vue:7, resources/js/v7/components/drawers/AlbumEdit.vue:19, resources/js/v7/components/drawers/AlbumEdit.vue:32, …
  • An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×8) — resources/js/v7/components/forms/auth/LoginForm.vue:10, resources/js/v7/components/gallery/albumModule/PhotoThumbPanelControl.vue:42, resources/js/v7/components/gallery/albumModule/PhotoThumbPanelControl.vue:45, …
  • This <span> carries its own click handler, but it sits inside a <button> that performs a different action. A keyboard user reaches the <button> and activating it runs the <button>'s handler, never this one, so this action has no keyboard path at all. Role and tabindex cannot supply one: HTML forbids a <button> from containing interactive content or any descendant with a tabindex, so the browser will not put this element in the tab order however it is marked up. Move it out of the <button> and make it a sibling <button>, so each action has its own control. — resources/js/v7/views/BulkAlbumEdit.vue:145

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

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.

AC6 · Visual & motion safety6.2 / 10Adequate✓ 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.

  • <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — resources/js/v7/components/gallery/albumModule/PhotoThumbPanelControl.vue:27
  • This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade. (×2) — resources/js/v7/components/gallery/photoModule/PhotoRatingWidget.vue:22, resources/js/v8/components/gallery/photoModule/PhotoRatingWidget.vue:22
  • <uicon> moves — its `animate-bounce` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — resources/js/v8/views/landing/LandingPortfolio.vue:60
  • <span> moves — its `animate-ping` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — resources/views/health-up.blade.php:16
  • `html, body` sets color: #777777 on background-color: #1d1d1d — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — simple_error_template.html:14
  • `.p-overlaybadge .p-badge` 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/js/v7/menus/LeftMenu.vue:200
  • `.lychee-page-enter-active` moves (`transition: opacity 0.18s ease, transform 0.18s ease`) 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/js/v8/views/App.vue:63
  • `.animate-landingAnimateDown` moves (`animation-name: landingAnimateDown`) 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. (×2) — resources/js/v8/views/landing/LandingClassic.vue:144, resources/js/v7/views/Landing.vue:133
  • `.loading-ring` moves (`animation: loading-ring-spin 0.9s linear infinite`) 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/js/v8/components/LycheeLoadingIcon.vue:75
  • `.slide-next-leave-active` moves (`transition: transform 0.5s cubic-bezier(0.165, 0.84, 0.44, 1), opacity 0.2s cubic-bezier(0.445, 0.05, 0.55, 0.95)`) 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/js/v8/components/gallery/photoModule/PhotoPanel.vue:201
  • `.slide-previous-leave-active` moves (`transition: transform 0.5s cubic-bezier(0.165, 0.84, 0.44, 1), opacity 0.2s cubic-bezier(0.445, 0.05, 0.55, 0.95)`) 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/js/v8/components/gallery/photoModule/PhotoPanel.vue:221
  • `.animate-landingAnimateUp` moves (`animation-name: landingAnimateUp`) 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/js/v8/components/footers/LandingFooter.vue:97

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition7.3 / 10Strong✓ 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 Protection8.0 / 10Strong✓ 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.

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

  • Public opt-outs and open tables (6) outweigh guarded routes and protected tables (4) — review whether the open surface is intended.

What to do

  • Review the open surface — keep public routes deliberate and documented so the open surface stays intentional.
C4 · Data Retention6.5 / 10Adequate✓ Tool-verified

Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).

Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.

  • A retention mechanism is present, but the data-lifecycle is not yet complete — missing: an expiry limit — a declared maximum age / TTL after which the data is no longer kept, a documented retention period / data-expiry.

What to do

  • Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
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.

DM11 · Constructible invalid state9.9 / 10Exemplary✓ Tool-verified

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 / an XException.ThrowIf* helper). C#: a static factory beside a public constructor does not exempt it, and a public parameterless constructor followed by public raw-primitive setters that refuse nothing is charged when the type also declares a validating way in (a guarded constructor or a guarding static method returning the type); TypeScript: a static Create/Of/From/New factory exempts the type. 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.

  • `PhotoResource`'s public constructor takes `album_id` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `PhotoResource` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/Http/Resources/Models/PhotoResource.php:65

What to do

  • Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM4 · Rich vs anemic model3.5 / 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.

  • `Album` 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/Http/Controllers/Admin/Maintenance/Model/Album.php:21
  • `PhotoResource` is an aggregate/entity with 30 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Http/Resources/Models/PhotoResource.php:26
  • `AccessPermission` 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/Models/AccessPermission.php:68
  • `AlbumSizeStatistics` 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/Models/AlbumSizeStatistics.php:40
  • `AlbumUserThumb` 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/Models/AlbumUserThumb.php:38
  • `Colour` 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/Models/Colour.php:22
  • `ConfigCategory` 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/Models/ConfigCategory.php:45
  • `Configs` 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/Models/Configs.php:64
  • `ContactMessage` 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/Models/ContactMessage.php:29
  • `Face` 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/Models/Face.php:47
  • `FaceSuggestion` 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/Models/FaceSuggestion.php:23
  • `JobHistory` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — app/Models/JobHistory.php:49
  • `LandingFeaturedItem` 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/Models/LandingFeaturedItem.php:30
  • `LandingLink` 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/Models/LandingLink.php:33
  • `LiveMetrics` 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/Models/LiveMetrics.php:47
  • `NsfwDetection` 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/Models/NsfwDetection.php:31
  • `OauthCredential` 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/Models/OauthCredential.php:29
  • `Order` 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/Models/Order.php:71
  • `OrderItem` 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/Models/OrderItem.php:69
  • `Palette` 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/Models/Palette.php:25
  • `Person` 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/Models/Person.php:38
  • `PersonAlbum` 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/Models/PersonAlbum.php:62
  • `PhotoModerationEvent` 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/Models/PhotoModerationEvent.php:30
  • `PhotoRating` 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/Models/PhotoRating.php:35
  • `PixelSize` 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/Models/PixelSize.php:28
  • `PrintSize` 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/Models/PrintSize.php:30
  • `Purchasable` 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/Models/Purchasable.php:37
  • `PurchasablePixelSize` 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/Models/PurchasablePixelSize.php:33
  • `PurchasablePrice` 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/Models/PurchasablePrice.php:29
  • `PurchasablePrintSize` 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/Models/PurchasablePrintSize.php:31
  • `RenamerRule` 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/Models/RenamerRule.php:39
  • `SizeVariant` 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/Models/SizeVariant.php:71
  • `Statistics` 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/Models/Statistics.php:46
  • `Tag` 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/Models/Tag.php:27
  • `TagAlbum` 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/Models/TagAlbum.php:65
  • `Track` 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/Models/Track.php:31
  • `UserGroup` 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/Models/UserGroup.php:32
  • `WebAuthnCredential` 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/Models/WebAuthnCredential.php:50
  • `Webhook` 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/Models/Webhook.php:44
  • `BucketKeyAlbum` 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. — database/migrations/TemporaryModels/BucketKeyAlbum.php:14

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 state2.7 / 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.

  • `Album` exposes publicly writable state (timestamps). — app/Http/Controllers/Admin/Maintenance/Model/Album.php:21
  • `PhotoResource` exposes publicly writable state (id, album_id, checksum, created_at, description, is_highlighted, and 24 more). — app/Http/Resources/Models/PhotoResource.php:26
  • `ThumbAlbumResource` exposes publicly writable state (id, title, description, thumb, is_nsfw, is_pinned, and 14 more). — app/Http/Resources/Models/ThumbAlbumResource.php:27
  • `AlbumSizeStatistics` exposes publicly writable state (incrementing, timestamps). — app/Models/AlbumSizeStatistics.php:40
  • `AlbumUserThumb` exposes publicly writable state (timestamps). — app/Models/AlbumUserThumb.php:38
  • `BaseAlbumImpl` exposes publicly writable state (incrementing). — app/Models/BaseAlbumImpl.php:152
  • `Colour` exposes publicly writable state (incrementing, timestamps). — app/Models/Colour.php:22
  • `Configs` exposes publicly writable state (timestamps). — app/Models/Configs.php:64
  • `BaseAlbum` exposes publicly writable state (incrementing). — app/Models/Extensions/BaseAlbum.php:62
  • `Face` exposes publicly writable state (incrementing). — app/Models/Face.php:47
  • `FaceSuggestion` exposes publicly writable state (timestamps, incrementing). — app/Models/FaceSuggestion.php:23
  • `LandingFeaturedItem` exposes publicly writable state (incrementing). — app/Models/LandingFeaturedItem.php:30
  • `LandingLink` exposes publicly writable state (incrementing). — app/Models/LandingLink.php:33
  • `OrderItem` exposes publicly writable state (timestamps). — app/Models/OrderItem.php:69
  • `Palette` exposes publicly writable state (timestamps). — app/Models/Palette.php:25
  • `Person` exposes publicly writable state (incrementing). — app/Models/Person.php:38
  • `Photo` exposes publicly writable state (incrementing). — app/Models/Photo.php:149
  • `PhotoRating` exposes publicly writable state (timestamps). — app/Models/PhotoRating.php:35
  • `PixelSize` exposes publicly writable state (timestamps). — app/Models/PixelSize.php:28
  • `PrintSize` exposes publicly writable state (timestamps). — app/Models/PrintSize.php:30
  • `Purchasable` exposes publicly writable state (timestamps). — app/Models/Purchasable.php:37
  • `PurchasablePixelSize` exposes publicly writable state (timestamps). — app/Models/PurchasablePixelSize.php:33
  • `PurchasablePrice` exposes publicly writable state (timestamps). — app/Models/PurchasablePrice.php:29
  • `PurchasablePrintSize` exposes publicly writable state (timestamps). — app/Models/PurchasablePrintSize.php:31
  • `RenamerRule` exposes publicly writable state (timestamps). — app/Models/RenamerRule.php:39
  • `SizeVariant` exposes publicly writable state (timestamps). — app/Models/SizeVariant.php:71
  • `Statistics` exposes publicly writable state (timestamps). — app/Models/Statistics.php:46
  • `Tag` exposes publicly writable state (timestamps). — app/Models/Tag.php:27
  • `WebAuthnCredential` exposes publicly writable state (incrementing). — app/Models/WebAuthnCredential.php:50
  • `Webhook` exposes publicly writable state (incrementing). — app/Models/Webhook.php:44
  • `BucketKeyAlbum` exposes publicly writable state (timestamps). — database/migrations/TemporaryModels/BucketKeyAlbum.php:14
  • `BucketKeyPhoto` exposes publicly writable state (timestamps). — database/migrations/TemporaryModels/BucketKeyPhoto.php:15
  • `RefactorAlbumModel_AlbumModel` exposes publicly writable state (timestamps). — database/migrations/TemporaryModels/RefactorAlbumModel_AlbumModel.php:29
  • `TitleSplitBaseAlbum` exposes publicly writable state (timestamps). — database/migrations/TemporaryModels/TitleSplitBaseAlbum.php:17
  • `TitleSplitPhoto` exposes publicly writable state (timestamps). — database/migrations/TemporaryModels/TitleSplitPhoto.php:17

What to do

  • Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM9 · Scattered domain decisions10.0 / 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.

M1 · Documentation (README)7.3 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

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

M2 · Architecture documentation8.0 / 10Strong✓ 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.

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

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

M4 · Documentation accuracy8.8 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

  • docs/specs/4-architecture/features/012-embeds/IMPLEMENTATION.md names TypeScript 5, but the manifest declares `typescript` ^6.0.3. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/specs/4-architecture/features/012-embeds/IMPLEMENTATION.md:75
  • docs/specs/4-architecture/features/012-embeds/README.md names TypeScript 5, but the manifest declares `typescript` ^6.0.3. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/specs/4-architecture/features/012-embeds/README.md:80

What to do

  • Reconcile the README with reality: docs/specs/4-architecture/features/012-embeds/IMPLEMENTATION.md names TypeScript 5, but the manifest declares `typescript` ^6.0.3; docs/specs/4-architecture/features/012-embeds/README.md names TypeScript 5, but the manifest declares `typescript` ^6.0.3.
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 · Observability10.0 / 10Exemplary○ Nothing flagged

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.

P3 · Security & performance tooling7.0 / 10Strong✓ 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` schedules updates, but no `package-ecosystem` entry covers `gitsubmodule`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2

What to do

  • Dependabot is configured but does not watch `gitsubmodule` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • 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.

  • Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it. — .github/workflows/docker_build.yml:97

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.
P6 · Release Hygiene10.0 / 10Exemplary✓ 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.

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 each language's code 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 Safety9.9 / 10Exemplary✓ 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.

R10 · Code Duplication0.0 / 10Critical✓ Tool-verified

React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): 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. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.

  • 318 duplicated blocks under resources/js/ have copies in at least two of the sibling directories composables, layouts, services, stores, utils, v7 (+1 more sibling(s) not listed) — 292 of them are reported below, and 26 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 318 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 318 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 318 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/v7/views/face-recog/PersonDetail.vue:181
  • 7 duplicated blocks under resources/js/v8/ have copies in at least two of the sibling directories components, composables, utils, views — 5 of them are reported below, and 2 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 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 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/v8/components/gallery/tagModule/TagPanel.vue:135
  • 5 duplicated blocks under resources/js/v8/components/ have copies in at least two of the sibling directories drawers, forms, gallery, headers, modals, renamer — 2 of them are reported below, and 3 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 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/v8/components/drawers/PhotoEdit.vue:133
  • resources/js/v7/views/face-recog/PersonDetail.vue:181 · resources/js/v8/views/face-recog/PersonDetail.vue:187 — these 2 files are line-for-line copies of one another — 299 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — resources/js/v7/views/face-recog/PersonDetail.vue:181
  • resources/js/v7/views/gallery-panels/Search.vue:175 · resources/js/v8/views/gallery-panels/Search.vue:167 — the two spans are one implementation copied and then locally edited — 1920 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/v7/views/gallery-panels/Search.vue:175
  • resources/js/composables/contextMenus/contextMenu.ts:1 · resources/js/v8/composables/contextMenus/contextMenu.ts:1 — these 2 files are line-for-line copies of one another — 267 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — resources/js/composables/contextMenus/contextMenu.ts:1
  • resources/js/v7/components/gallery/albumModule/AlbumPanel.vue:217 · resources/js/v8/components/gallery/albumModule/AlbumPanel.vue:288 — the two spans are one implementation copied and then locally edited — 1679 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/v7/components/gallery/albumModule/AlbumPanel.vue:217
  • resources/js/v7/components/forms/album/AlbumProperties.vue:393 · resources/js/v8/components/forms/album/AlbumProperties.vue:273 — the two spans are one implementation copied and then locally edited — 1902 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/v7/components/forms/album/AlbumProperties.vue:393
  • resources/js/v7/views/gallery-panels/Album.vue:174 · resources/js/v8/views/gallery-panels/Album.vue:178 — the two spans are one implementation copied and then locally edited — 1664 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/v7/views/gallery-panels/Album.vue:174
  • resources/js/v7/views/face-recog/FaceMaintenance.vue:266 · resources/js/v8/views/face-recog/FaceMaintenance.vue:273 — these 2 files are line-for-line copies of one another — 203 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — resources/js/v7/views/face-recog/FaceMaintenance.vue:266
  • resources/js/v7/components/forms/album/EmbedCodeDialog.vue:138 · resources/js/v8/components/forms/album/EmbedCodeDialog.vue:152 — these 2 files are line-for-line copies of one another — 188 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — resources/js/v7/components/forms/album/EmbedCodeDialog.vue:138
  • resources/js/v7/views/gallery-panels/Timeline.vue:217 · resources/js/v8/views/gallery-panels/Timeline.vue:245 — the two spans are one implementation copied and then locally edited — 1047 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/v7/views/gallery-panels/Timeline.vue:217
  • resources/js/v7/views/face-recog/FaceClusters.vue:229 · resources/js/v8/views/face-recog/FaceClusters.vue:292 — the two spans are one implementation copied and then locally edited — 1267 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/v7/views/face-recog/FaceClusters.vue:229
  • resources/js/v7/components/settings/General.vue:236 · resources/js/v8/components/settings/General.vue:254 — these 2 files are line-for-line copies of one another — 136 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — resources/js/v7/components/settings/General.vue:236
  • resources/js/v7/views/gallery-panels/Tag.vue:122 · resources/js/v8/views/gallery-panels/Tag.vue:120 — the two spans are one implementation copied and then locally edited — 872 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/v7/views/gallery-panels/Tag.vue:122
  • resources/js/v7/components/forms/upload/UploadingLine.vue:57 · resources/js/v8/components/forms/upload/UploadingLine.vue:118 — the two spans are one implementation copied and then locally edited — 852 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/v7/components/forms/upload/UploadingLine.vue:57
  • resources/js/v7/views/face-recog/FaceClusters.vue:437 · resources/js/v8/views/face-recog/FaceClusters.vue:607 — the two spans are one implementation copied and then locally edited — 965 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/v7/views/face-recog/FaceClusters.vue:437
  • resources/js/v7/components/drawers/LiveMetrics.vue:58 · resources/js/v8/components/drawers/LiveMetrics.vue:71 — the two spans are one implementation copied and then locally edited — 947 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/v7/components/drawers/LiveMetrics.vue:58
  • resources/js/v7/components/gallery/albumModule/AlbumHeaderPanel.vue:123 · resources/js/v8/components/gallery/albumModule/AlbumHeaderPanel.vue:137 — these 2 files are line-for-line copies of one another — 121 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — resources/js/v7/components/gallery/albumModule/AlbumHeaderPanel.vue:123
  • resources/js/v7/views/gallery-panels/Albums.vue:274 · resources/js/v8/views/gallery-panels/Albums.vue:241 — the two spans are one implementation copied and then locally edited — 786 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/v7/views/gallery-panels/Albums.vue:274
  • resources/js/v7/components/renamer/RenamerRuleModal.vue:174 · resources/js/v8/components/renamer/RenamerRuleModal.vue:139 — these 2 files are line-for-line copies of one another — 116 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — resources/js/v7/components/renamer/RenamerRuleModal.vue:174
  • resources/js/v7/views/admin/Jobs.vue:51 · resources/js/v8/views/admin/Jobs.vue:103 — the two spans are one implementation copied and then locally edited — 744 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/v7/views/admin/Jobs.vue:51
  • resources/js/v7/components/forms/gallery-dialogs/MoveDialog.vue:33 · resources/js/v8/components/forms/gallery-dialogs/MoveDialog.vue:45 — these 2 files are line-for-line copies of one another — 108 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — resources/js/v7/components/forms/gallery-dialogs/MoveDialog.vue:33
  • resources/js/v7/components/modals/UploadPanel.vue:122 · resources/js/v8/components/modals/UploadPanel.vue:125 — the two spans are one implementation copied and then locally edited — 869 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/v7/components/modals/UploadPanel.vue:122
  • resources/js/v7/views/admin/Moderation.vue:167 · resources/js/v8/views/admin/Moderation.vue:180 — 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/v7/views/admin/Moderation.vue:167
  • resources/js/v7/views/admin/Settings.vue:79 · resources/js/v8/views/admin/Settings.vue:108 — the two spans are one implementation copied and then locally edited — 715 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/v7/views/admin/Settings.vue:79
  • resources/js/v7/views/webshop/OrderDownload.vue:206 · resources/js/v8/views/webshop/OrderDownload.vue:214 — these 2 files are line-for-line copies of one another — 97 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — resources/js/v7/views/webshop/OrderDownload.vue:206
  • resources/js/v7/components/forms/album/AlbumPurchasable.vue:59 · resources/js/v8/components/forms/album/AlbumPurchasable.vue:60 — these 2 files are line-for-line copies of one another — 96 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — resources/js/v7/components/forms/album/AlbumPurchasable.vue:59
  • resources/js/v7/components/forms/users/CreateEditUser.vue:91 · resources/js/v8/components/forms/users/CreateEditUser.vue:84 — these 2 files are line-for-line copies of one another — 95 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — resources/js/v7/components/forms/users/CreateEditUser.vue:91
  • resources/js/v7/components/forms/search/AdvancedSearchPanel.vue:222 · resources/js/v8/components/forms/search/AdvancedSearchPanel.vue:275 — 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/v7/components/forms/search/AdvancedSearchPanel.vue:222
  • resources/js/v7/components/modals/CameraCapture.vue:70 · resources/js/v8/components/modals/CameraCapture.vue:82 — these 2 files are line-for-line copies of one another — 89 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — resources/js/v7/components/modals/CameraCapture.vue:70
  • resources/js/v7/views/admin/UserGroups.vue:126 · resources/js/v8/views/admin/UserGroups.vue:118 — the two spans are one implementation copied and then locally edited — 702 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/v7/views/admin/UserGroups.vue:126
  • resources/js/v7/components/forms/album/ApplyRenamerDialog.vue:121 · resources/js/v8/components/forms/album/ApplyRenamerDialog.vue:157 — the two spans are one implementation copied and then locally edited — 609 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/v7/components/forms/album/ApplyRenamerDialog.vue:121
  • resources/js/v7/components/pagination/PaginationInfiniteScroll.vue:8 · resources/js/v8/components/pagination/PaginationInfiniteScroll.vue:8 — these 2 files are line-for-line copies of one another — 87 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — resources/js/v7/components/pagination/PaginationInfiniteScroll.vue:8
  • resources/js/v7/components/drawers/PhotoDetails.vue:321 · resources/js/v8/components/drawers/PhotoDetails.vue:311 — 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/v7/components/drawers/PhotoDetails.vue:321
  • resources/js/v8/components/gallery/albumModule/Virtualized/AlbumListViewVirtual.vue:59 · resources/js/v8/components/gallery/albumModule/Virtualized/AlbumThumbGridVirtual.vue:85 — these 2 files are line-for-line copies of one another — 82 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — resources/js/v8/components/gallery/albumModule/Virtualized/AlbumListViewVirtual.vue:59
  • resources/js/v8/components/gallery/albumModule/Virtualized/AlbumRootGridVirtual.vue:89 · resources/js/v8/components/gallery/albumModule/Virtualized/AlbumRootListViewVirtual.vue:60 — these 2 files are line-for-line copies of one another — 80 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — resources/js/v8/components/gallery/albumModule/Virtualized/AlbumRootGridVirtual.vue:89
  • resources/js/v7/views/RegisterPage.vue:61 · resources/js/v8/views/RegisterPage.vue:54 — these 2 files are line-for-line copies of one another — 78 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — resources/js/v7/views/RegisterPage.vue:61
  • resources/js/v7/components/drawers/PhotoEdit.vue:123 · resources/js/v8/components/drawers/PhotoEdit.vue:94 — the two spans are one implementation copied and then locally edited — 754 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/v7/components/drawers/PhotoEdit.vue:123
  • resources/js/v7/views/admin/AdminDashboard.vue:172 · resources/js/v8/views/admin/AdminDashboard.vue:134 — these 2 files are line-for-line copies of one another — 76 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — resources/js/v7/views/admin/AdminDashboard.vue:172

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/sidebar-map.ts:3 imports leaflet.markercluster/dist/leaflet.markercluster.js, 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/sidebar-map.ts:3
  • resources/js/v7/views/gallery-panels/Map.vue:31 imports leaflet.markercluster/dist/leaflet.markercluster.js, 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/v7/views/gallery-panels/Map.vue:31
  • resources/js/v8/views/gallery-panels/Map.vue:33 imports leaflet.markercluster/dist/leaflet.markercluster.js, 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/v8/views/gallery-panels/Map.vue:33

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

  • phpDateFormat has cyclomatic complexity 56 and cognitive complexity 35; 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/v8/utils/phpDateFormat.ts:261
  • (anonymous) has cyclomatic complexity 48 and cognitive complexity 47; 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/composables/contextMenus/leftMenu.ts:66
  • (anonymous) has cyclomatic complexity 40 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/v8/composables/spotlight/useSpotlightGalleryActions.ts:75
  • (anonymous) has cyclomatic complexity 40 and cognitive complexity 13; 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/v8/views/admin/LandingConfig.vue:673
  • mergePhotoDetail has cyclomatic complexity 38 and cognitive complexity 35; 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/v8/utils/adaptPhotoTile.ts:225
  • validateConfig has cyclomatic complexity 36 and cognitive complexity 35; 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/embed/config.ts:30
  • photoMenu has cyclomatic complexity 35 and cognitive complexity 35; 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. (×2) — resources/js/composables/contextMenus/contextMenu.ts:103, resources/js/v8/composables/contextMenus/contextMenu.ts:107
  • parseDataAttributes has cyclomatic complexity 28 and cognitive complexity 34; 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/embed/config.ts:131
  • parse has cyclomatic complexity 26 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/utils/sprintf.ts:100
  • (anonymous) has cyclomatic complexity 26 and cognitive complexity 25; 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/v8/composables/contextMenus/leftMenu.ts:169
  • (anonymous) has cyclomatic complexity 25 and cognitive complexity 19; 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/v7/components/headers/AlbumsHeader.vue:284
  • decideKey has cyclomatic complexity 24 and cognitive complexity 27; 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/v8/utils/quickNaming.ts:132
  • (anonymous) has cyclomatic complexity 24 and cognitive complexity 24; 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/v8/views/admin/WatermarkPreview.vue:513
  • (anonymous) has cyclomatic complexity 24 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/v8/components/headers/AlbumsHeader.vue:271
  • (anonymous) has cyclomatic complexity 24 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/config/axios-config.ts:107
  • photosMenu has cyclomatic complexity 23 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. (×2) — resources/js/composables/contextMenus/contextMenu.ts:236, resources/js/v8/composables/contextMenus/contextMenu.ts:240
  • (anonymous) has cyclomatic complexity 22 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/v8/components/gallery/timelineModule/TimelineDatesV3.vue:319
  • convertNumber has cyclomatic complexity 21 and cognitive complexity 15; 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/utils/sprintf.ts:298
  • getStatistics has cyclomatic complexity 20 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/composables/album/albumStatistics.ts:22
  • parseTokens has cyclomatic complexity 20 and cognitive complexity 21; 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/composables/useSearchTokenAssembler.ts:149
  • saveAlbum has cyclomatic complexity 20 and cognitive complexity 19; 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/v8/components/forms/album/AlbumProperties.vue:582
  • (anonymous) has cyclomatic complexity 19 and cognitive complexity 21; 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/v7/views/gallery-panels/Map.vue:199
  • assembleTokens has cyclomatic complexity 19 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/composables/useSearchTokenAssembler.ts:81
  • (anonymous) has cyclomatic complexity 19 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/v8/composables/contextMenus/leftMenu.ts:82
  • (anonymous) has cyclomatic complexity 18 and cognitive complexity 20; 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/composables/album/dragAndSelect.ts:352
  • albumMenu has cyclomatic complexity 18 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — resources/js/composables/contextMenus/contextMenu.ts:328, resources/js/v8/composables/contextMenus/contextMenu.ts:332
  • toggleBuyMe has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/composables/album/buyMeActions.ts:30
  • calculateLayout has cyclomatic complexity 18 and cognitive complexity 14; 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/embed/components/EmbedWidget.vue:291
  • (anonymous) has cyclomatic complexity 16 and cognitive complexity 19; 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/stores/AlbumState.ts:864
  • saveAlbum has cyclomatic complexity 16 and cognitive complexity 15; 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/v7/components/forms/album/AlbumProperties.vue:564
  • setAsHeader has cyclomatic complexity 15 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — resources/js/v8/components/gallery/albumModule/AlbumPanel.vue:421
  • setAsHeader has cyclomatic complexity 14 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — resources/js/v7/components/gallery/albumModule/AlbumPanel.vue:361
  • (anonymous) has cyclomatic complexity 14 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — resources/js/v7/components/headers/TimelineHeader.vue:242
  • (anonymous) has cyclomatic complexity 14 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — resources/js/v7/components/gallery/albumModule/thumbs/AlbumThumbOverlay.vue:46, resources/js/v8/components/gallery/albumModule/thumbs/AlbumThumbOverlay.vue:49
  • computeTimelinePhotoLayout has cyclomatic complexity 13 and cognitive complexity 27; 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/v8/composables/photo/analyticPhotoLayout.ts:307
  • (anonymous) has cyclomatic complexity 13 and cognitive complexity 15; 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/composables/album/photoActions.ts:68
R3 · Large Files8.1 / 10Strong✓ 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/v8/views/admin/LandingConfig.vue has 1124 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/v8/views/admin/LandingConfig.vue:1
  • resources/js/stores/AlbumState.ts has 971 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/stores/AlbumState.ts:1
  • resources/js/v8/views/face-recog/FaceClusters.vue has 775 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/v8/views/face-recog/FaceClusters.vue:1
  • resources/js/v8/components/gallery/albumModule/Virtualized/PhotoGridVirtual.vue has 716 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/v8/components/gallery/albumModule/Virtualized/PhotoGridVirtual.vue:1
  • resources/js/v8/components/forms/album/AlbumProperties.vue has 685 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/v8/components/forms/album/AlbumProperties.vue:1
  • resources/js/v8/views/BulkAlbumEdit.vue has 663 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/v8/views/BulkAlbumEdit.vue:1
  • resources/js/v8/components/gallery/albumModule/AlbumPanel.vue has 647 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/v8/components/gallery/albumModule/AlbumPanel.vue:1
  • resources/js/v8/views/gallery-panels/Map.vue has 643 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/v8/views/gallery-panels/Map.vue:1
  • resources/js/v8/components/gallery/photoModule/PhotoBox.vue has 639 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/v8/components/gallery/photoModule/PhotoBox.vue:1
  • resources/js/v7/components/forms/album/AlbumProperties.vue has 629 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/v7/components/forms/album/AlbumProperties.vue:1
  • resources/js/v8/views/face-recog/PersonDetail.vue has 626 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/v8/views/face-recog/PersonDetail.vue:1
  • resources/js/embed/components/EmbedWidget.vue has 605 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/embed/components/EmbedWidget.vue:1
  • resources/js/v7/views/face-recog/PersonDetail.vue has 598 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/v7/views/face-recog/PersonDetail.vue:1
  • resources/js/v7/views/BulkAlbumEdit.vue has 576 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/v7/views/BulkAlbumEdit.vue:1
  • resources/js/v7/views/gallery-panels/Search.vue has 576 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/v7/views/gallery-panels/Search.vue:1
  • resources/js/v8/views/gallery-panels/Search.vue has 575 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/v8/views/gallery-panels/Search.vue:1
  • resources/js/v7/views/face-recog/FaceClusters.vue has 555 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/v7/views/face-recog/FaceClusters.vue:1
  • resources/js/v8/composables/useSphereViewer.ts has 544 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/v8/composables/useSphereViewer.ts:1
  • resources/js/v8/views/face-recog/FaceMaintenance.vue has 543 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/v8/views/face-recog/FaceMaintenance.vue:1
  • resources/js/v7/components/gallery/albumModule/AlbumPanel.vue 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/v7/components/gallery/albumModule/AlbumPanel.vue:1
  • resources/js/v8/views/gallery-panels/Timeline.vue 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/v8/views/gallery-panels/Timeline.vue:1
  • resources/js/embed/components/Lightbox.vue has 524 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/embed/components/Lightbox.vue:1
  • resources/js/v7/views/gallery-panels/Album.vue has 520 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/v7/views/gallery-panels/Album.vue:1
  • resources/js/v7/views/face-recog/FaceMaintenance.vue has 515 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/v7/views/face-recog/FaceMaintenance.vue:1
  • resources/js/v8/views/gallery-panels/Album.vue has 514 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/v8/views/gallery-panels/Album.vue:1
  • resources/js/v8/views/admin/WatermarkPreview.vue has 506 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/v8/views/admin/WatermarkPreview.vue:1
  • resources/js/composables/album/dragAndSelect.ts has 496 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/composables/album/dragAndSelect.ts:1
  • resources/js/v7/views/admin/NsfwConfig.vue has 486 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/v7/views/admin/NsfwConfig.vue:1
  • resources/js/v7/views/gallery-panels/Timeline.vue has 481 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/v7/views/gallery-panels/Timeline.vue:1
  • resources/js/v8/components/gallery/timelineModule/TimelineDatesV3.vue has 467 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/v8/components/gallery/timelineModule/TimelineDatesV3.vue:1
  • resources/js/v8/utils/phpDateFormat.ts has 459 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/v8/utils/phpDateFormat.ts:1
  • resources/js/v8/views/admin/NsfwConfig.vue has 452 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/v8/views/admin/NsfwConfig.vue:1
  • resources/js/v8/composables/contextMenus/contextMenu.ts has 451 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/v8/composables/contextMenus/contextMenu.ts:1
  • resources/js/v7/views/gallery-panels/Albums.vue has 450 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/v7/views/gallery-panels/Albums.vue:1
  • resources/js/composables/contextMenus/contextMenu.ts has 448 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/composables/contextMenus/contextMenu.ts:1
  • resources/js/v8/components/settings/General.vue has 442 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/v8/components/settings/General.vue:1
  • resources/js/v8/views/gallery-panels/Albums.vue has 442 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/v8/views/gallery-panels/Albums.vue:1
  • resources/js/v7/components/drawers/PhotoDetails.vue has 439 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/v7/components/drawers/PhotoDetails.vue:1
  • resources/js/v8/components/drawers/PhotoDetails.vue has 420 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/v8/components/drawers/PhotoDetails.vue:1
  • resources/js/v7/components/settings/General.vue has 417 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/v7/components/settings/General.vue:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage6.6 / 10Adequate✓ 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. (×40) — resources/js/v7/style/preset.ts:1, resources/js/v7/views/face-recog/PersonDetail.vue:1, resources/js/v7/components/forms/album/AlbumProperties.vue:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness5.1 / 10Adequate✓ 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.

  • 49 outdated package(s); JS/npm CVEs scored in D30
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 Code9.1 / 10Exemplary✓ 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 22 application, 8 tooling and 35 test entry point(s) detected in this repo. Gate removals on `npm run typecheck` — an undetected custom entry would make these reachable.
  • no import path from any entry point (22 application, 8 tooling, 35 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 (×7) — resources/js/v7/components/forms/basic/Password.vue, resources/js/composables/pagination/usePagination.ts, resources/js/v7/components/forms/sharing/CreateSharing.vue, …
  • Nothing ultimately consumes this binding: its only referrer is the re-export in resources/js/embed/main.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/embed/main.ts in the same commit, or the barrel will import a name that no longer exists. (×4) — resources/js/embed/utils/columns.ts:28, resources/js/embed/utils/columns.ts:74, resources/js/embed/utils/columns.ts:99, …
  • Nothing imports this binding — it is safe to review for removal. (×11) — resources/js/stores/FavouriteState.ts:6, resources/js/stores/FlowState.ts:8, resources/js/stores/ImportState.ts:4, …

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 Hygiene0.0 / 10Critical✓ 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.

  • Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×2) — resources/js/v8/components/forms/settings/ColorField.vue:36, resources/js/v8/icons.ts:1
  • Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json. — resources/js/v7/components/forms/basic/InputPassword.vue:19
  • 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. (×8) — package.json:34, package.json:39, package.json:44, …

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports4.7 / 10Weak✓ 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/composables/album/folderDrop.ts → resources/js/composables/album/uploadEvents.ts → resources/js/composables/album/folderDrop.ts — resources/js/composables/album/folderDrop.ts:4
  • resources/js/layouts/PhotoLayout.ts → resources/js/layouts/useGrid.ts → resources/js/layouts/PhotoLayout.ts (one verified cycle inside a mutually-dependent group of 3 files) — resources/js/layouts/PhotoLayout.ts:5
  • resources/js/v8/layouts/PhotoLayout.ts → resources/js/v8/layouts/useGrid.ts → resources/js/v8/layouts/PhotoLayout.ts (one verified cycle inside a mutually-dependent group of 3 files) — resources/js/v8/layouts/PhotoLayout.ts:5

What to do

  • Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture6.0 / 10Adequate✓ Tool-verified

Other · Security — Only what this repository's own non-C# files could be read for was assessed — markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin — 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.

  • `https://js.mollie.com/v1/mollie.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. — resources/views/components/webshop.blade.php:3
  • 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` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — REDACTED:58

What to do

  • Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
  • Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X14 · Bypassable address 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.

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.

X19 · Unrestored process-global state2.3 / 10Critical✓ Tool-verified

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.

  • `write` changes state that belongs to the whole PROCESS and changes it back at the end of the same body — the process umask (changed at line 83, put back at line 87) — which says the change was meant to last no longer than this call. But the restore is an ordinary statement on the straight-line path, not a `finally`, so it is skipped by any exception thrown in between: PHP then keeps the overwritten value for the rest of the request — and in a CLI command, a queue worker or a long-running server (Octane, Swoole, RoadRunner, FrankenPHP) for the rest of the process's life — and every later relative path, child-process launch, date, number format, XML parse or error report in ANY class reads it. That failure is silent and remote from its cause: the function that breaks is not the function that moved the value. The durable fix is not to widen the restore but to stop mutating the global: pass the value to the operation that needs it — `cwd` and `env` to Symfony `Process` (`new Process($command, $cwd, $env)`) or `proc_open($command, $spec, $pipes, $cwd, $env)`, absolute paths instead of `chdir`, an explicit `DateTimeZone` or locale to `DateTimeImmutable`/`IntlDateFormatter`/`NumberFormatter`, an explicit encoding to the `mb_*` call, `LIBXML_NOERROR`/`libxml_get_errors` handling in one place. Where the global genuinely must move, wrap it `try`/`finally` so the restore runs on every path. — app/Image/Files/FlysystemFile.php:59
  • `handle` changes state that belongs to the whole PROCESS and changes it back at the end of the same body — the process umask (changed at line 84, put back at line 86) — which says the change was meant to last no longer than this call. But the restore is an ordinary statement on the straight-line path, not a `finally`, so it is skipped by any exception thrown in between: PHP then keeps the overwritten value for the rest of the request — and in a CLI command, a queue worker or a long-running server (Octane, Swoole, RoadRunner, FrankenPHP) for the rest of the process's life — and every later relative path, child-process launch, date, number format, XML parse or error report in ANY class reads it. That failure is silent and remote from its cause: the function that breaks is not the function that moved the value. The durable fix is not to widen the restore but to stop mutating the global: pass the value to the operation that needs it — `cwd` and `env` to Symfony `Process` (`new Process($command, $cwd, $env)`) or `proc_open($command, $spec, $pipes, $cwd, $env)`, absolute paths instead of `chdir`, an explicit `DateTimeZone` or locale to `DateTimeImmutable`/`IntlDateFormatter`/`NumberFormatter`, an explicit encoding to the `mb_*` call, `LIBXML_NOERROR`/`libxml_get_errors` handling in one place. Where the global genuinely must move, wrap it `try`/`finally` so the restore runs on every path. — app/Actions/Photo/Pipes/VideoPartner/PlaceVideo.php:56
  • `putSourceIntoFinalDestination` changes state that belongs to the whole PROCESS and changes it back at the end of the same body — the process umask (changed at line 84, put back at line 86) — which says the change was meant to last no longer than this call. But the restore is an ordinary statement on the straight-line path, not a `finally`, so it is skipped by any exception thrown in between: PHP then keeps the overwritten value for the rest of the request — and in a CLI command, a queue worker or a long-running server (Octane, Swoole, RoadRunner, FrankenPHP) for the rest of the process's life — and every later relative path, child-process launch, date, number format, XML parse or error report in ANY class reads it. That failure is silent and remote from its cause: the function that breaks is not the function that moved the value. The durable fix is not to widen the restore but to stop mutating the global: pass the value to the operation that needs it — `cwd` and `env` to Symfony `Process` (`new Process($command, $cwd, $env)`) or `proc_open($command, $spec, $pipes, $cwd, $env)`, absolute paths instead of `chdir`, an explicit `DateTimeZone` or locale to `DateTimeImmutable`/`IntlDateFormatter`/`NumberFormatter`, an explicit encoding to the `mb_*` call, `LIBXML_NOERROR`/`libxml_get_errors` handling in one place. Where the global genuinely must move, wrap it `try`/`finally` so the restore runs on every path. — app/Actions/Photo/Pipes/Standalone/PlacePhoto.php:70

What to do

  • Each finding names the statement that changes the process-global value and the statement that puts it back. Confirm from the two that nothing between them is protected — then prefer removing the mutation over widening the restore: a working directory or an environment variable passed to the operation that needs it (the `cwd` and `env` options of `child_process`, or of `Deno.Command`) is scoped to that operation, which is what the save-and-restore was trying to approximate. Where the global genuinely must move, a `try`/`finally` is the least that makes the restore unconditional. In PHP the same holds for `chdir`, `putenv`, `setlocale`, `date_default_timezone_set`, `ini_set` and the error-handler stack: pass the value to the operation (`Process` with `cwd`/`env`, an explicit `DateTimeZone`) or restore in a `finally`.
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/4 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
  • `load` 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/utils/detailRequests.ts:20
  • `batchAssign` awaits `axios.post(…)` 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: `axios.post(url, { signal })`. — resources/js/services/face-batch-service.ts:16
  • `batchUnassign` awaits `axios.post(…)` 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: `axios.post(url, { signal })`. — resources/js/services/face-batch-service.ts:46
  • `batchUnassignByPhotos` awaits `axios.post(…)` 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: `axios.post(url, { signal })`. — resources/js/services/face-batch-service.ts:61

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.

X23 · Unguarded diagnostic materialisation6.6 / 10Adequate✓ Tool-verified

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.

  • `debug` at line 308 is called with an argument built by `array_keys($result)` (line 312), whose cost grows with the collection it walks. PHP evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isHandling` test, no debug flag, and no placeholder context array that lets the logger build the text only when the level is on. — app/Services/Auth/LdapService.php:308

What to do

  • In PHP, put the construction behind the logger's own check (`if ($logger->isHandling(Logger::DEBUG))` for Monolog, a debug flag for a line only a debug build needs), or pass the collection through the PSR-3 context array with a `{placeholder}` (`$logger->debug('rows: {rows}', ['rows' => $rows])`) so the handler renders it only when the record is written. Concatenating or interpolating the value into the message is not the fix: PHP builds the string, and every `array_map`, `implode` or `json_encode` inside it, before the call is entered.
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.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `foreach` leaves the array or collection it is walking alone — PHP raises nothing, but the loop's view and the collection part: an array walked by value (and a Doctrine or Laravel collection) is walked as the snapshot taken when the loop began, so an element added in the body is never visited and one removed is visited anyway; an array walked by reference (`as &$v`) and an SPL container (`SplObjectStorage`, `ArrayObject`, `SplQueue`) are walked live, so an added element is walked too and a removal skips the next one; and after an `array_splice`, `array_shift` or sort every later key names a different element.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. 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.5 / 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. (×9) — resources/js/v8/views/gallery-panels/Frame.vue:80, resources/js/v8/views/gallery-panels/Frame.vue:90, resources/js/v8/composables/useDarkMode.ts:55, …
  • `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×31) — resources/js/v8/views/gallery-panels/Map.vue:383, resources/js/v8/views/face-recog/FaceClusters.vue:603, resources/js/v8/views/face-recog/FaceClusters.vue:663, …

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

  • `warning` at line 47 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. (×3) — app/Services/Image/NsfwActionService.php:47, app/Jobs/DispatchFaceScanJob.php:47, app/Jobs/DispatchNsfwScanJob.php:47
  • `info` at line 115 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/Services/Image/NsfwActionService.php:115
  • `info` at line 123 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/Services/Image/NsfwActionService.php:123
  • `info` at line 130 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/Services/Image/NsfwActionService.php:130
  • `info` at line 144 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/Services/Image/NsfwActionService.php:144
  • `info` at line 151 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/Services/Image/NsfwActionService.php:151
  • `info` at line 175 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/Services/Image/NsfwActionService.php:175
  • `info` at line 195 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/Services/Image/NsfwActionService.php:195
  • `warning` at line 209 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/Services/Image/NsfwActionService.php:209
  • `info` at line 216 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/Services/Image/NsfwActionService.php:216
  • `info` at line 154 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/Services/Image/NsfwDetectionService.php:154
  • `info` at line 38 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/Listeners/RecomputeAlbumSizeOnAlbumChange.php:38
  • `info` at line 59 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/Listeners/RecomputeAlbumSizeOnAlbumChange.php:59
  • `debug` at line 55 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->debug('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::debug('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Listeners/RecomputeAlbumSizeOnPhotoMutation.php:55
  • `debug` at line 74 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->debug('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::debug('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Listeners/RecomputeAlbumSizeOnPhotoMutation.php:74
  • `info` at line 29 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/Listeners/RecomputeAlbumStatsOnAlbumChange.php:29
  • `info` at line 50 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/Listeners/RecomputeAlbumStatsOnAlbumChange.php:50
  • `info` at line 60 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/Listeners/RecomputeAlbumStatsOnPhotoChange.php:60
  • `info` at line 53 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/Jobs/ApplyNsfwAlbumSensitivityJob.php:53
  • `info` at line 62 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/Jobs/ApplyNsfwAlbumSensitivityJob.php:62
  • `warning` at line 53 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/Jobs/DispatchFaceScanJob.php:53
  • `warning` at line 63 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/Jobs/DispatchFaceScanJob.php:63
  • `warning` at line 74 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/Jobs/DispatchFaceScanJob.php:74
  • `warning` at line 41 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/Jobs/DispatchNsfwScanJob.php:41
  • `warning` at line 57 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/Jobs/DispatchNsfwScanJob.php:57
  • `warning` at line 71 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/Jobs/DispatchNsfwScanJob.php:71
  • `info` at line 67 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/Jobs/ExtractColoursJob.php:67
  • `info` at line 87 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/Jobs/ExtractZip.php:87
  • `debug` 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->debug('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::debug('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Jobs/FileDeleterJob.php:69
  • `debug` at line 89 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->debug('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::debug('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Jobs/FileDeleterJob.php:89
  • `info` at line 77 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/Jobs/GeodecodeLocationJob.php:77
  • `info` at line 84 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/Jobs/RecomputeAlbumSizeJob.php:84
  • `warning` at line 90 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/Jobs/RecomputeAlbumSizeJob.php:90
  • `debug` at line 112 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->debug('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::debug('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Jobs/RecomputeAlbumSizeJob.php:112
  • `debug` at line 118 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->debug('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::debug('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Jobs/RecomputeAlbumSizeJob.php:118
  • `info` at line 98 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/Jobs/RecomputeAlbumStatsJob.php:98
  • `critical` 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->critical('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::critical('order moved', ['order_id' => $orderId])` with Laravel's facade. — app/Jobs/RecomputeAlbumStatsJob.php:103
  • `warning` at line 112 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/Jobs/RecomputeAlbumStatsJob.php:112

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 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 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
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only

Not statically assessed — these 40 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.2, 2.1.4, 2.2.2, 2.3.1, 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 Health37.5Weak — gated by R10, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture75.3StrongSolid.
Maturity82.7StrongSolid.
Readiness41.1Weak — gated by R8, P5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security70.3StrongSolid.
Domain Modelling55.3Adequate — gated by DM4, DM5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility39.6Weak — gated by AC2, AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100.0ExemplaryStrongest area.
Unscored — 3 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.

  • X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X6 Hand-rolled structured-format parsing — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 40 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.

  • C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model, a change-history library on the models — spatie/laravel-activitylog's LogsActivity, owen-it/laravel-auditing's Auditable, venturecraft/revisionable, Gedmo Loggable — or an Eloquent model event, observer or Doctrine listener that records each change) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
  • 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. A delete/anonymise identifier was seen but did not co-occur with GDPR vocabulary or a subject-id shape, so it was not credited (e.g. a save-slot DeleteAccount()). Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 47 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.

  • 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 1 — a container did not start, exited, or never became healthy) — container lychee-facial-recognition is unhealthy; 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 included — no .php test runner
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D21 Naming Consistency — Naming consistency does not read PHP, html yet; not measured.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) — 137 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • 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.
  • D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
  • DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
  • DM12 Ambient inputs in the domain — no domain-layer types detected — ambient-input check not applicable
  • DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
  • DM3 Integration-event coupling — no integration events detected — coupling check not applicable
  • DM6 Domain ↔ infrastructure boundary — no domain-layer types detected — domain↔infrastructure boundary check not applicable
  • DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
  • DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X1 Async correctness — X1 reached only 42% of this repository's production lines — php (152,857 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X12 Unreachable branch — X12 reached only 42% of this repository's production lines — php (152,857 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — X24 reached only 42% of this repository's production lines — php (152,857 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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.
  • 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.
  • 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 — 105 finding(s)
AC1 · Text alternatives · <img> without a text alternative · ×18
  • <img> without a text alternative resources/js/v7/components/drawers/LiveMetrics.vue:38 — 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/js/v7/components/forms/card/Card.vue: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/js/v7/components/forms/card/Card.vue:11 — 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/js/v7/components/forms/card/Card.vue:84 — 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/js/v7/components/gallery/albumModule/AlbumHeaderImage.vue:3 — 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/js/v7/components/headers/AlbumsHeader.vue:118 — 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/js/v7/views/DuplicatesFinder.vue:85 — 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/js/v7/views/face-recog/FaceClusters.vue:157 — 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/js/v8/components/drawers/PhotoDetails.vue:135 — 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/js/v8/components/drawers/PhotoDetails.vue:141 — 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/js/v8/components/drawers/PhotoDetails.vue:153 — 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/js/v8/components/drawers/PhotoDetails.vue:164 — 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/js/v8/components/forms/card/Card.vue: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/js/v8/components/forms/card/Card.vue:11 — 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/js/v8/components/forms/card/Card.vue:84 — 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/js/v8/components/gallery/albumModule/AlbumHeaderImage.vue:3 — 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/js/v8/components/headers/AlbumsHeader.vue:87 — 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/js/v8/views/DuplicatesFinder.vue:78 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC2 · Forms & labels · Link with no accessible name · ×10
  • Link with no accessible name resources/js/v7/components/footers/GalleryFooter.vue:9 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name resources/js/v7/components/footers/GalleryFooter.vue:17 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name resources/js/v7/components/footers/GalleryFooter.vue:25 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name resources/js/v7/components/footers/GalleryFooter.vue:33 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name resources/js/v7/components/footers/GalleryFooter.vue:41 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name resources/js/v7/components/footers/LandingFooter.vue:4 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name resources/js/v7/components/footers/LandingFooter.vue:12 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name resources/js/v7/components/footers/LandingFooter.vue:20 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name resources/js/v7/components/footers/LandingFooter.vue:28 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
  • Link with no accessible name resources/js/v7/components/footers/LandingFooter.vue:36 — A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
AC2 · Forms & labels · <label> that labels no control · ×10
  • <label> that labels no control resources/js/v7/components/forms/basic/PersonInput.vue: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/js/v7/components/forms/basic/PersonInput.vue:35 — 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/js/v7/components/forms/search/AdvancedSearchPanel.vue:13 — 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/js/v7/components/forms/search/AdvancedSearchPanel.vue: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/js/v7/components/forms/search/AdvancedSearchPanel.vue: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/js/v7/components/forms/search/AdvancedSearchPanel.vue:29 — 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/js/v7/components/forms/search/AdvancedSearchPanel.vue:40 — 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/js/v7/components/forms/search/AdvancedSearchPanel.vue:51 — 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/js/v7/components/forms/search/AdvancedSearchPanel.vue: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/js/v7/components/forms/search/AdvancedSearchPanel.vue:107 — 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.
AC2 · Forms & labels · <button> with no accessible text · ×9
  • <button> with no accessible text resources/js/v7/components/faceRecog/FaceRecognitionWarning.vue:25 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text resources/js/v7/components/forms/basic/rating.vue:4 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text resources/js/v7/components/forms/search/AdvancedSearchPanel.vue:6 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text resources/js/v7/components/forms/search/AdvancedSearchPanel.vue:60 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text resources/js/v7/components/forms/search/AdvancedSearchPanel.vue:71 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text resources/js/v7/components/forms/search/AdvancedSearchPanel.vue:82 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text resources/js/v7/components/forms/search/AdvancedSearchPanel.vue:93 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text resources/js/v7/components/forms/search/AdvancedSearchPanel.vue:109 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text resources/js/v7/components/forms/search/AdvancedSearchPanel.vue:118 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×9
  • Click handler on a non-interactive <div> resources/js/v7/components/gallery/PersonCard.vue:2 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> resources/js/v7/components/gallery/albumModule/AlbumListItem.vue:2 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> resources/js/v7/components/gallery/albumModule/SensitiveWarning.vue:2 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> resources/js/v7/components/gallery/albumModule/thumbs/ThumbBuyMe.vue:16 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> resources/js/v7/components/gallery/albumModule/thumbs/ThumbFavourite.vue:19 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> resources/js/v7/components/gallery/flowModule/Blur.vue:2 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> resources/js/v7/components/gallery/photoModule/ColourSquare.vue:2 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> resources/js/v7/components/gallery/photoModule/PhotoBox.vue:2 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> resources/js/v7/components/modals/faceRecog/SelfieClaimModal.vue:7 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
D31 · IaC & Container Security · High IaC · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC4 · Keyboard semantics · Click handler on a non-interactive <span> · ×6
  • Click handler on a non-interactive <span> resources/js/v7/components/forms/sharing/CreateSharing.vue:8 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <span> resources/js/v7/components/forms/upload/UploadingLine.vue:10 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <span> resources/js/v7/components/gallery/timelineModule/TimelineDates.vue:25 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <span> resources/js/v7/components/statistics/Activity.vue:21 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <span> resources/js/v7/components/webshop/OrderDate.vue:5 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <span> resources/js/v7/components/webshop/OrderDate.vue:8 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC2 · Forms & labels · <select> without a programmatic label · ×5
  • <select> without a programmatic label resources/js/v7/components/forms/album/SearchTargetAlbum.vue:2 — 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.
  • <select> without a programmatic label resources/js/v7/components/forms/album/SearchTargetUser.vue:2 — 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.
  • <select> without a programmatic label resources/js/v7/components/forms/basic/PersonInput.vue:6 — 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.
  • <select> without a programmatic label resources/js/v7/components/forms/card/CardForm.vue:27 — 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.
  • <select> without a programmatic label resources/js/v7/components/forms/profile/SetSharedAlbumsVisibility.vue:13 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC4 · Keyboard semantics · Click handler on a non-interactive <li> · ×5
  • Click handler on a non-interactive <li> resources/js/v7/components/drawers/AlbumEdit.vue:7 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <li> resources/js/v7/components/drawers/AlbumEdit.vue:19 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <li> resources/js/v7/components/drawers/AlbumEdit.vue:32 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <li> resources/js/v7/components/drawers/AlbumEdit.vue:45 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <li> resources/js/v7/components/drawers/AlbumEdit.vue:58 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC4 · Keyboard semantics · Click handler on a non-interactive <i> · ×4
  • Click handler on a non-interactive <i> resources/js/v7/components/settings/ConfirmSave.vue:42 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <i> resources/js/v7/components/webshop/OrderLegend.vue:3 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <i> resources/js/v7/components/webshop/OrderLegend.vue — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <i> resources/js/v7/components/webshop/TransactionIdLink.vue:12 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC4 · Keyboard semantics · Focusable <div> isn't keyboard-operable · ×3
  • Focusable <div> isn't keyboard-operable resources/js/embed/components/EmbedWidget.vue:110 — This <div> carries tabindex="0", so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler.
  • Focusable <div> isn't keyboard-operable resources/js/embed/components/EmbedWidget.vue:151 — This <div> carries tabindex="0", so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler.
  • Focusable <div> isn't keyboard-operable resources/js/v7/components/gallery/albumModule/PhotoListItem.vue:2 — This <div> carries tabindex="0", so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler.
AC4 · Keyboard semantics · Click handler on a non-interactive <img> · ×3
  • Click handler on a non-interactive <img> resources/js/v7/components/gallery/flowModule/CarouselImages.vue:4 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <img> resources/js/v7/components/gallery/flowModule/HeaderImage.vue:21 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <img> resources/js/v7/components/gallery/flowModule/TopImages.vue:16 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
R9 · Circular Imports · Import cycle (2 files) · ×3
  • Import cycle (2 files) resources/js/composables/album/folderDrop.ts:4 — resources/js/composables/album/folderDrop.ts → resources/js/composables/album/uploadEvents.ts → resources/js/composables/album/folderDrop.ts
  • Import cycle (2 files) resources/js/layouts/PhotoLayout.ts:5 — resources/js/layouts/PhotoLayout.ts → resources/js/layouts/useGrid.ts → resources/js/layouts/PhotoLayout.ts (one verified cycle inside a mutually-dependent group of 3 files)
  • Import cycle (2 files) resources/js/v8/layouts/PhotoLayout.ts:5 — resources/js/v8/layouts/PhotoLayout.ts → resources/js/v8/layouts/useGrid.ts → resources/js/v8/layouts/PhotoLayout.ts (one verified cycle inside a mutually-dependent group of 3 files)
AC3 · Page structure · Document without a <title> · ×2
  • Document without a <title> resources/views/vueapp.blade.php:2 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> vite/index.html:2 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
D30 · Dependency Vulnerabilities · High CVE · ×2
  • REDACTED
  • REDACTED
D34 · Knowledge Freshness · Orphaned knowledge · ×2
  • Orphaned knowledge database/migrations/2021_12_04_181200_refactor_models.php:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge database/migrations/2021_06_01_181900_refactor_timestamps_anew.php:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
AC2 · Forms & labels · <textarea> without a programmatic label · ×1
  • <textarea> without a programmatic label resources/js/v7/components/forms/basic/Textarea.vue:2 — 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.
AC3 · Page structure · <html> without a lang · ×1
  • <html> without a lang vite/index.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC4 · Keyboard semantics · Focusable <img> isn't keyboard-operable · ×1
  • Focusable <img> isn't keyboard-operable resources/js/embed/components/EmbedWidget.vue:43 — This <img> carries tabindex="0", so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler.
AC4 · Keyboard semantics · Click handler on a <span> nested inside <button> · ×1
  • Click handler on a <span> nested inside <button> resources/js/v7/views/BulkAlbumEdit.vue:145 — This <span> carries its own click handler, but it sits inside a <button> that performs a different action. A keyboard user reaches the <button> and activating it runs the <button>'s handler, never this one, so this action has no keyboard path at all. Role and tabindex cannot supply one: HTML forbids a <button> from containing interactive content or any descendant with a tabindex, so the browser will not put this element in the tab order however it is marked up. Move it out of the <button> and make it a sibling <button>, so each action has its own control.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
R8 · Dependency Hygiene · Unlisted import '@dayflow/blossom-color-picker' · ×1
  • Unlisted import '@dayflow/blossom-color-picker' resources/js/v8/components/forms/settings/ColorField.vue:36 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@iconify/vue' · ×1
  • Unlisted import '@iconify/vue' resources/js/v8/icons.ts:1 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Serious — 766 finding(s)
DM4 · Rich vs anemic model · Anemic entity · ×40
  • Anemic entity: Album app/Http/Controllers/Admin/Maintenance/Model/Album.php:21 — `Album` 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: PhotoResource app/Http/Resources/Models/PhotoResource.php:26 — `PhotoResource` is an aggregate/entity with 30 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: AccessPermission app/Models/AccessPermission.php:68 — `AccessPermission` 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: AlbumSizeStatistics app/Models/AlbumSizeStatistics.php:40 — `AlbumSizeStatistics` 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: AlbumUserThumb app/Models/AlbumUserThumb.php:38 — `AlbumUserThumb` 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: Colour app/Models/Colour.php:22 — `Colour` 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: ConfigCategory app/Models/ConfigCategory.php:45 — `ConfigCategory` 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: Configs app/Models/Configs.php:64 — `Configs` 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: ContactMessage app/Models/ContactMessage.php:29 — `ContactMessage` 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: Face app/Models/Face.php:47 — `Face` 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: FaceSuggestion app/Models/FaceSuggestion.php:23 — `FaceSuggestion` 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: JobHistory app/Models/JobHistory.php:49 — `JobHistory` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: LandingFeaturedItem app/Models/LandingFeaturedItem.php:30 — `LandingFeaturedItem` 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: LandingLink app/Models/LandingLink.php:33 — `LandingLink` 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: LiveMetrics app/Models/LiveMetrics.php:47 — `LiveMetrics` 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: NsfwDetection app/Models/NsfwDetection.php:31 — `NsfwDetection` 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: OauthCredential app/Models/OauthCredential.php:29 — `OauthCredential` 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: Order app/Models/Order.php:71 — `Order` 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: OrderItem app/Models/OrderItem.php:69 — `OrderItem` 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: Palette app/Models/Palette.php:25 — `Palette` 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: Person app/Models/Person.php:38 — `Person` 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: PersonAlbum app/Models/PersonAlbum.php:62 — `PersonAlbum` 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: PhotoModerationEvent app/Models/PhotoModerationEvent.php:30 — `PhotoModerationEvent` 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: PhotoRating app/Models/PhotoRating.php:35 — `PhotoRating` 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: PixelSize app/Models/PixelSize.php:28 — `PixelSize` 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.
  • + 15 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×40
  • No test reaches this file resources/js/v7/style/preset.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/v7/views/face-recog/PersonDetail.vue: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/v7/components/forms/album/AlbumProperties.vue: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/v7/views/BulkAlbumEdit.vue: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/v7/views/gallery-panels/Search.vue: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/v7/views/face-recog/FaceClusters.vue: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/v7/views/gallery-panels/Album.vue: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/v7/views/face-recog/FaceMaintenance.vue: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/v7/components/gallery/albumModule/AlbumPanel.vue: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/v7/views/gallery-panels/Timeline.vue: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/v7/views/admin/NsfwConfig.vue: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/v7/views/gallery-panels/Albums.vue: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/v7/components/drawers/PhotoDetails.vue: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/v7/components/settings/General.vue: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/embed/components/EmbedWidget.vue: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/v7/components/forms/album/EmbedCodeDialog.vue: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/v7/components/headers/AlbumsHeader.vue: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/embed/components/Lightbox.vue: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/composables/contextMenus/leftMenu.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/v7/components/renamer/RenamerRuleModal.vue: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/v7/views/gallery-panels/Tag.vue: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/v7/views/webshop/OrderDownload.vue: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/v7/components/forms/search/AdvancedSearchPanel.vue: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/v7/components/forms/bulk-album-edit/BulkEditFieldsDialog.vue: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/v7/components/gallery/albumModule/AlbumHeaderPanel.vue: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.
  • + 15 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×40
  • Swallowed exception (empty catch) resources/js/v8/views/gallery-panels/Frame.vue:80 — 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/v8/views/gallery-panels/Frame.vue:90 — 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/v8/views/gallery-panels/Map.vue:383 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) resources/js/v8/views/face-recog/FaceClusters.vue:603 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) resources/js/v8/views/face-recog/FaceClusters.vue:663 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) resources/js/v8/views/face-recog/FaceClusters.vue:735 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) resources/js/v8/views/face-recog/FaceClusters.vue:823 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) resources/js/v8/views/face-recog/FaceClusters.vue:836 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) resources/js/v8/views/face-recog/People.vue:214 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) resources/js/v8/views/admin/AdminDashboard.vue:220 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) resources/js/v8/views/admin/AdminDashboard.vue:230 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) resources/js/v8/views/admin/NsfwConfig.vue:318 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) resources/js/v8/menus/LeftMenu.vue:174 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) resources/js/v8/menus/LeftMenu.vue:205 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) resources/js/v8/composables/useDarkMode.ts:55 — 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/v8/composables/useDarkMode.ts:84 — 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/v8/composables/useQuickNamingSession.ts:123 — 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/v8/composables/useQuickNamingSession.ts:263 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) resources/js/v8/composables/useQuickNamingSession.ts:344 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) resources/js/v8/composables/album/albumDateScrubberState.ts:28 — 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/v8/components/modals/SpotlightSearch.vue:112 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) resources/js/v8/components/modals/WebauthnModal.vue:81 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) resources/js/v8/components/forms/auth/LoginForm.vue:151 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) resources/js/v7/views/gallery-panels/Frame.vue:71 — 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/v7/views/gallery-panels/Frame.vue:81 — 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.
  • + 15 more in this group — see findings.md.
DM5 · Encapsulated state · Mutable entity · ×35
  • Mutable entity: Album app/Http/Controllers/Admin/Maintenance/Model/Album.php:21 — `Album` exposes publicly writable state (timestamps).
  • Mutable entity: PhotoResource app/Http/Resources/Models/PhotoResource.php:26 — `PhotoResource` exposes publicly writable state (id, album_id, checksum, created_at, description, is_highlighted, and 24 more).
  • Mutable entity: ThumbAlbumResource app/Http/Resources/Models/ThumbAlbumResource.php:27 — `ThumbAlbumResource` exposes publicly writable state (id, title, description, thumb, is_nsfw, is_pinned, and 14 more).
  • Mutable entity: AlbumSizeStatistics app/Models/AlbumSizeStatistics.php:40 — `AlbumSizeStatistics` exposes publicly writable state (incrementing, timestamps).
  • Mutable entity: AlbumUserThumb app/Models/AlbumUserThumb.php:38 — `AlbumUserThumb` exposes publicly writable state (timestamps).
  • Mutable entity: BaseAlbumImpl app/Models/BaseAlbumImpl.php:152 — `BaseAlbumImpl` exposes publicly writable state (incrementing).
  • Mutable entity: Colour app/Models/Colour.php:22 — `Colour` exposes publicly writable state (incrementing, timestamps).
  • Mutable entity: Configs app/Models/Configs.php:64 — `Configs` exposes publicly writable state (timestamps).
  • Mutable entity: BaseAlbum app/Models/Extensions/BaseAlbum.php:62 — `BaseAlbum` exposes publicly writable state (incrementing).
  • Mutable entity: Face app/Models/Face.php:47 — `Face` exposes publicly writable state (incrementing).
  • Mutable entity: FaceSuggestion app/Models/FaceSuggestion.php:23 — `FaceSuggestion` exposes publicly writable state (timestamps, incrementing).
  • Mutable entity: LandingFeaturedItem app/Models/LandingFeaturedItem.php:30 — `LandingFeaturedItem` exposes publicly writable state (incrementing).
  • Mutable entity: LandingLink app/Models/LandingLink.php:33 — `LandingLink` exposes publicly writable state (incrementing).
  • Mutable entity: OrderItem app/Models/OrderItem.php:69 — `OrderItem` exposes publicly writable state (timestamps).
  • Mutable entity: Palette app/Models/Palette.php:25 — `Palette` exposes publicly writable state (timestamps).
  • Mutable entity: Person app/Models/Person.php:38 — `Person` exposes publicly writable state (incrementing).
  • Mutable entity: Photo app/Models/Photo.php:149 — `Photo` exposes publicly writable state (incrementing).
  • Mutable entity: PhotoRating app/Models/PhotoRating.php:35 — `PhotoRating` exposes publicly writable state (timestamps).
  • Mutable entity: PixelSize app/Models/PixelSize.php:28 — `PixelSize` exposes publicly writable state (timestamps).
  • Mutable entity: PrintSize app/Models/PrintSize.php:30 — `PrintSize` exposes publicly writable state (timestamps).
  • Mutable entity: Purchasable app/Models/Purchasable.php:37 — `Purchasable` exposes publicly writable state (timestamps).
  • Mutable entity: PurchasablePixelSize app/Models/PurchasablePixelSize.php:33 — `PurchasablePixelSize` exposes publicly writable state (timestamps).
  • Mutable entity: PurchasablePrice app/Models/PurchasablePrice.php:29 — `PurchasablePrice` exposes publicly writable state (timestamps).
  • Mutable entity: PurchasablePrintSize app/Models/PurchasablePrintSize.php:31 — `PurchasablePrintSize` exposes publicly writable state (timestamps).
  • Mutable entity: RenamerRule app/Models/RenamerRule.php:39 — `RenamerRule` exposes publicly writable state (timestamps).
  • + 10 more in this group — see findings.md.
D17 · Explicit Debt · TodoComment · ×22
  • TodoComment .php-cs-fixer.php:4 — // Todo: later create automation that applies formatting on PR (and create a pull request on top if not formatted properly) — 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 tests/Unit/Http/Requests/Album/MergeAlbumRequestTest.php:37 — // TODO:// not only the times, but make sure the right arguments are passed, but this is hard to do find with mockery — 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 tests/Unit/Http/Requests/Album/MoveAlbumsRequestTest.php:43 — // TODO: not only the times, but make sure the right arguments are passed, but this is hard to do find with mockery — 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 tests/Unit/Http/Requests/Album/MoveAlbumsRequestTest.php:82 — // TODO: refactor the MergeAlbumRequest to use the AlbumFactory or a Repo so that the test can be written without talking to DB — 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 routes/api_v2.php:450 — // TODO: Those should require admin no ??? — 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 resources/js/services/metrics-service.ts:24 — // TODO: figure out why this sometimes happens... — 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 config/filesystems.php:115 — // TODO: Maybe we should drop this Flysystem disk, because neither the driver nor the root must be changed and hence the whole point of using the Flysystem abstraction is gone. — 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/Policies/AlbumQueryPolicy.php:135 — // TODO: move the owner to ACCESS PERMISSIONS so that we do not need to join base_album anymore — 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/Models/OrderItem.php:228 — // TODO: later consider how to handle albums. — 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/Metadata/DiskUsage.php:73 — // TODO : FIX TO USE STORAGE FACADE => uploads may not be in public/uploads — 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/Metadata/DiskUsage.php:84 — // TODO : FIX TO USE STORAGE FACADE => uploads may not be in public/uploads — 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/Metadata/DiskUsage.php:95 — // TODO : FIX TO USE STORAGE FACADE => uploads may not be in public/uploads — 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/Metadata/Extractor.php:101 — // TODO: This may fail for files without an extension. — 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/Metadata/Extractor.php:264 — // TODO: Implement timezone derivation from location data. — 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/Metadata/Extractor.php:481 — // TODO: If we add the suffix " s" here, we should also normalize the fraction here. — 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/Image/Handlers/GdHandler.php:211 — // TODO: Replace `exif_read_data` by `\Safe\exif_read_data` after https://github.com/thecodingmachine/safe/issues/215 has been resolved
  • TodoComment app/Http/Resources/Models/HeadAlbumResource.php:83 — // TODO: Investigate later why this string is 24 characters long. — 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/Http/Controllers/Admin/Maintenance/MissingFileSizes.php:79 — // TODO: remove s3 support here. — 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/Console/Commands/ImageProcessing/VideoData.php:115 — // TODO: Fix this line before PR; init needs more parameters — 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/Actions/Shop/BasketService.php:156 — // TODO: it is worth wondering if it is the full album that is bought or if it is just a collection of photos — 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/Actions/Import/Pipes/BuildTree.php:156 — // TODO: Consider to use a modern OO-approach using [`DirectoryIterator`](https://www.php.net/manual/en/class.directoryiterator.php) and [`SplFileInfo`](https://www.php.net/manual/en/class.splfileinfo.php)
  • TodoComment app/Actions/Album/BaseArchive.php:182 — // TODO: For higher efficiency, ensure that the photos of each child album together with the original size variant are eagerly loaded. — 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.
D3 · God Classes · FunctionTooLong · ×19
  • FunctionTooLong: useSphereViewer.useSphereViewer resources/js/v8/composables/useSphereViewer.ts:125 — FunctionTooLong — useSphereViewer runs 329 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 229 over it, 3.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: dragAndSelect.useDragAndSelect resources/js/composables/album/dragAndSelect.ts:41 — FunctionTooLong — useDragAndSelect runs 296 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 196 over it, 2.96× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: contextMenu.useContextMenu resources/js/composables/contextMenus/contextMenu.ts:81 — FunctionTooLong — useContextMenu runs 256 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 156 over it, 2.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: contextMenu.useContextMenu resources/js/v8/composables/contextMenus/contextMenu.ts:85 — FunctionTooLong — useContextMenu runs 256 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 156 over it, 2.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: usePanZoom.usePanZoom resources/js/v8/composables/usePanZoom.ts:67 — FunctionTooLong — usePanZoom runs 256 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 156 over it, 2.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: useQuickNamingSession.useQuickNamingSession resources/js/v8/composables/useQuickNamingSession.ts:38 — FunctionTooLong — useQuickNamingSession runs 241 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 141 over it, 2.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: leftMenu.useLeftMenu resources/js/composables/contextMenus/leftMenu.ts:28 — FunctionTooLong — useLeftMenu runs 218 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 118 over it, 2.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: leftMenu.useLeftMenu resources/js/v8/composables/contextMenus/leftMenu.ts:46 — FunctionTooLong — useLeftMenu runs 186 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 86 over it, 1.86× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: useAdminTiles.useAdminTiles resources/js/v8/composables/useAdminTiles.ts:27 — FunctionTooLong — useAdminTiles runs 185 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 85 over it, 1.85× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: selections.useSelection resources/js/composables/selections/selections.ts:9 — FunctionTooLong — useSelection runs 174 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 74 over it, 1.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: treeOperations.useTreeOperations resources/js/composables/album/treeOperations.ts:22 — FunctionTooLong — useTreeOperations runs 167 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 67 over it, 1.67× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: leftMenu.useLeftMenu.items resources/js/composables/contextMenus/leftMenu.ts:66 — FunctionTooLong — useLeftMenu.items runs 152 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: phpDateFormat.phpDateFormat resources/js/v8/utils/phpDateFormat.ts:261 — FunctionTooLong — phpDateFormat runs 148 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 48 over it, 1.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: getPreviewInfo.usePreviewData resources/js/composables/preview/getPreviewInfo.ts:3 — FunctionTooLong — usePreviewData runs 143 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 43 over it, 1.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: useSpotlightGalleryActions.useSpotlightGalleryActions resources/js/v8/composables/spotlight/useSpotlightGalleryActions.ts:36 — FunctionTooLong — useSpotlightGalleryActions runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: buyMeActions.useBuyMeActions resources/js/composables/album/buyMeActions.ts:23 — FunctionTooLong — useBuyMeActions runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: useAdminTiles.useAdminTiles resources/js/composables/useAdminTiles.ts:25 — FunctionTooLong — useAdminTiles runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: galleryModals.useGalleryModals resources/js/composables/modalsTriggers/galleryModals.ts:4 — FunctionTooLong — useGalleryModals runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: getPreviewInfo.usePreviewData.getInsightsData resources/js/composables/preview/getPreviewInfo.ts:66 — FunctionTooLong — usePreviewData.getInsightsData runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D15 · Churn × Complexity Hotspots · Hotspot · ×16
  • Hotspot: app/Actions/Photo/StructOfArrays/QueryPhotoDetails.php app/Actions/Photo/StructOfArrays/QueryPhotoDetails.php:105 — app/Actions/Photo/StructOfArrays/QueryPhotoDetails.php changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in QueryPhotoDetails.buildResource at line 105. 3 of those changes were fix/bug commits, and the other 5 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-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- app/Actions/Photo/StructOfArrays/QueryPhotoDetails.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.
  • Hotspot: app/Http/Resources/GalleryConfigs/InitConfig.php app/Http/Resources/GalleryConfigs/InitConfig.php:229 — app/Http/Resources/GalleryConfigs/InitConfig.php changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in InitConfig.__construct at line 229. 1 of those changes was a fix/bug commit, and the other 13 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-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- app/Http/Resources/GalleryConfigs/InitConfig.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.
  • Hotspot: resources/js/composables/album/dragAndSelect.ts resources/js/composables/album/dragAndSelect.ts:348 — resources/js/composables/album/dragAndSelect.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in dragAndSelect.useDragAndSelect.getAlbumBoxesV3 at line 348. 2 of those changes were fix/bug commits, and the other 6 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-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- resources/js/composables/album/dragAndSelect.ts`: 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.
  • Hotspot: resources/js/v8/composables/useAdminTiles.ts resources/js/v8/composables/useAdminTiles.ts:27 — resources/js/v8/composables/useAdminTiles.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in useAdminTiles.useAdminTiles at line 27. 2 of those changes were fix/bug commits, and the other 5 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-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- resources/js/v8/composables/useAdminTiles.ts`: 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.
  • Hotspot: resources/js/v8/components/forms/album/AlbumProperties.vue resources/js/v8/components/forms/album/AlbumProperties.vue:582 — resources/js/v8/components/forms/album/AlbumProperties.vue changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in saveAlbum at line 582. 2 of those changes were fix/bug commits, and the other 5 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-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- resources/js/v8/components/forms/album/AlbumProperties.vue`: 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.
  • Hotspot: app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php:175 — app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in QueryPhotoRatios.buildResource at line 175. 1 of those changes was a fix/bug commit, and the other 6 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-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- app/Actions/Photo/StructOfArrays/QueryPhotoRatios.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.
  • Hotspot: resources/js/v8/composables/spotlight/useSpotlightGalleryActions.ts resources/js/v8/composables/spotlight/useSpotlightGalleryActions.ts:36 — resources/js/v8/composables/spotlight/useSpotlightGalleryActions.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in useSpotlightGalleryActions.useSpotlightGalleryActions at line 36. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- resources/js/v8/composables/spotlight/useSpotlightGalleryActions.ts`: 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.
  • Hotspot: resources/js/v8/composables/contextMenus/contextMenu.ts resources/js/v8/composables/contextMenus/contextMenu.ts:107 — resources/js/v8/composables/contextMenus/contextMenu.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in contextMenu.useContextMenu.photoMenu at line 107. 2 of those changes were fix/bug commits, and the other 4 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-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- resources/js/v8/composables/contextMenus/contextMenu.ts`: 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.
  • Hotspot: app/Http/Resources/GalleryConfigs/AlbumConfig.php app/Http/Resources/GalleryConfigs/AlbumConfig.php:54 — app/Http/Resources/GalleryConfigs/AlbumConfig.php changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in AlbumConfig.__construct at line 54. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- app/Http/Resources/GalleryConfigs/AlbumConfig.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.
  • Hotspot: resources/js/stores/AlbumState.ts resources/js/stores/AlbumState.ts:864 — resources/js/stores/AlbumState.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in (anonymous) at line 864. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- resources/js/stores/AlbumState.ts`: 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.
  • Hotspot: resources/js/v8/components/gallery/timelineModule/TimelineDatesV3.vue resources/js/v8/components/gallery/timelineModule/TimelineDatesV3.vue:319 — resources/js/v8/components/gallery/timelineModule/TimelineDatesV3.vue changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in (anonymous) at line 319. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- resources/js/v8/components/gallery/timelineModule/TimelineDatesV3.vue`: 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.
  • Hotspot: resources/js/composables/contextMenus/contextMenu.ts resources/js/composables/contextMenus/contextMenu.ts:103 — resources/js/composables/contextMenus/contextMenu.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in contextMenu.useContextMenu.photoMenu at line 103. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- resources/js/composables/contextMenus/contextMenu.ts`: 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.
  • Hotspot: app/Actions/Admin/BulkEditAlbumsAction.php app/Actions/Admin/BulkEditAlbumsAction.php:48 — app/Actions/Admin/BulkEditAlbumsAction.php changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in BulkEditAlbumsAction.do at line 48. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- app/Actions/Admin/BulkEditAlbumsAction.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.
  • Hotspot: app/Actions/Photo/Pipes/Shared/HydrateMetadata.php app/Actions/Photo/Pipes/Shared/HydrateMetadata.php:34 — app/Actions/Photo/Pipes/Shared/HydrateMetadata.php changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in HydrateMetadata.handle at line 34. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- app/Actions/Photo/Pipes/Shared/HydrateMetadata.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.
  • Hotspot: resources/js/composables/contextMenus/leftMenu.ts resources/js/composables/contextMenus/leftMenu.ts:66 — resources/js/composables/contextMenus/leftMenu.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in leftMenu.useLeftMenu.items at line 66. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- resources/js/composables/contextMenus/leftMenu.ts`: 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.
  • Hotspot: resources/js/v7/components/forms/album/AlbumProperties.vue resources/js/v7/components/forms/album/AlbumProperties.vue:564 — resources/js/v7/components/forms/album/AlbumProperties.vue changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in saveAlbum at line 564. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- resources/js/v7/components/forms/album/AlbumProperties.vue`: 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.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×14
  • Duplicated block (8 lines × 2) app/Actions/Import/Pipes/DeleteMissingAlbums.php:152 — app/Actions/Import/Pipes/DeleteMissingAlbums.php:152-159 | app/Actions/Import/Pipes/DeleteMissingPhotos.php:160-168 — 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. Note first that the copies are not typed on the same thing: `Delete` names `App\Actions\Album\Delete` in one and `App\Actions\Photo\Delete` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (8 lines × 2) app/Http/Controllers/Admin/LandingFeaturedItemController.php:75 — app/Http/Controllers/Admin/LandingFeaturedItemController.php:75-82 | app/Http/Controllers/Admin/LandingLinkController.php:75-82 — 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/Http/Controllers/Admin/LandingFeaturedItemController.php:75` 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 (8 lines × 2) app/Http/Controllers/Gallery/MapListingController.php:52 — app/Http/Controllers/Gallery/MapListingController.php:52-60 | app/Http/Controllers/Gallery/MapListingController.php:82-89 — 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/Http/Resources/Models/HeadPersonAlbumResource.php:62 — app/Http/Resources/Models/HeadPersonAlbumResource.php:62-69 | app/Http/Resources/Models/HeadTagAlbumResource.php:60-67 — 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/Jobs/UploadSizeVariantToS3Job.php:39 — app/Jobs/UploadSizeVariantToS3Job.php:39-46 | app/Jobs/WatermarkerJob.php:55-62 — 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/Repositories/AlbumRepository.php:122 — app/Repositories/AlbumRepository.php:122-129 | app/Repositories/AlbumRepository.php:222-229 — 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/Actions/Search/Strategies/Album/AlbumTagStrategy.php:35 — app/Actions/Search/Strategies/Album/AlbumTagStrategy.php:35-42 | app/Actions/Search/Strategies/TagStrategy.php:31-38 — 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.
  • Duplicated block (8 lines × 2) app/Actions/Album/BaseArchive.php:83 — app/Actions/Album/BaseArchive.php:83-91 | app/Actions/Photo/BaseArchive.php:77-84 — 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.
  • Duplicated block (8 lines × 2) app/Actions/Diagnostics/Pipes/Checks/OpCacheCheck.php:54 — app/Actions/Diagnostics/Pipes/Checks/OpCacheCheck.php:54-61 | app/Assets/Helpers.php:144-151 — 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. 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/Console/Commands/RecomputeAlbumSizes.php:41 — app/Console/Commands/RecomputeAlbumSizes.php:41-48 | app/Console/Commands/RecomputeAlbumStats.php:41-48 — before extracting anything, compare `app/Console/Commands/RecomputeAlbumSizes.php` and `app/Console/Commands/RecomputeAlbumStats.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. 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/Http/Requests/Renamer/DeleteRenamerRuleRequest.php:28 — app/Http/Requests/Renamer/DeleteRenamerRuleRequest.php:28-35 | app/Http/Requests/Renamer/UpdateRenamerRuleRequest.php:44-51 — 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/Relations/HasManyPhotosByPerson.php:89 — app/Relations/HasManyPhotosByPerson.php:89-96 | app/Relations/HasManyPhotosByTag.php:194-201 — 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.
  • Duplicated block (8 lines × 2) app/Listeners/RecomputeAlbumSizeOnAlbumChange.php:53 — app/Listeners/RecomputeAlbumSizeOnAlbumChange.php:53-60 | app/Listeners/RecomputeAlbumStatsOnAlbumChange.php:44-51 — before extracting anything, compare `app/Listeners/RecomputeAlbumSizeOnAlbumChange.php` and `app/Listeners/RecomputeAlbumStatsOnAlbumChange.php` as WHOLE FILES: 86% 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 1 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.
  • Duplicated block (8 lines × 2) database/factories/PhotoFactory.php:141 — database/factories/PhotoFactory.php:141-148 | database/factories/TagAlbumFactory.php:54-61 — 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.
D35 · Change Coupling · Change-coupling hub · ×10
  • Change-coupling hub: all_settings.php → all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php lang/nl/all_settings.php — `lang/nl/all_settings.php` changes together with 19 other files — `lang/ar/all_settings.php`, `lang/bg/all_settings.php`, `lang/cz/all_settings.php`, `lang/de/all_settings.php`, `lang/el/all_settings.php`, `lang/es/all_settings.php`, `lang/fa/all_settings.php`, `lang/hu/all_settings.php`, `lang/it/all_settings.php`, `lang/ja/all_settings.php`, `lang/no/all_settings.php`, `lang/pl/all_settings.php`, `lang/ru/all_settings.php`, `lang/sk/all_settings.php`, `lang/sv/all_settings.php`, `lang/tr/all_settings.php`, `lang/vi/all_settings.php`, `lang/zh_CN/all_settings.php`, `lang/zh_TW/all_settings.php` — none of which declares a dependency on it: one file is the hub of 19 separate couplings, not 19 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 19.
  • Change-coupling hub: all_settings.php → all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php, all_settings.php lang/en/all_settings.php — `lang/en/all_settings.php` changes together with 9 other files — `lang/ar/all_settings.php`, `lang/bg/all_settings.php`, `lang/es/all_settings.php`, `lang/fa/all_settings.php`, `lang/ja/all_settings.php`, `lang/no/all_settings.php`, `lang/ru/all_settings.php`, `lang/sv/all_settings.php`, `lang/tr/all_settings.php` — none of which declares a dependency on it: one file is the hub of 9 separate couplings, not 9 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 9.
  • Change-coupling hub: dialogs.php → dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php lang/ja/dialogs.php — `lang/ja/dialogs.php` changes together with 16 other files — `lang/cz/dialogs.php`, `lang/de/dialogs.php`, `lang/en/dialogs.php`, `lang/fr/dialogs.php`, `lang/hu/dialogs.php`, `lang/it/dialogs.php`, `lang/nl/dialogs.php`, `lang/no/dialogs.php`, `lang/pl/dialogs.php`, `lang/pt/dialogs.php`, `lang/ru/dialogs.php`, `lang/sk/dialogs.php`, `lang/sv/dialogs.php`, `lang/vi/dialogs.php`, `lang/zh_CN/dialogs.php`, `lang/zh_TW/dialogs.php` — none of which declares a dependency on it: one file is the hub of 16 separate couplings, not 16 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 16.
  • Change-coupling hub: dialogs.php → dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php lang/pt/dialogs.php — `lang/pt/dialogs.php` changes together with 15 other files — `lang/cz/dialogs.php`, `lang/de/dialogs.php`, `lang/en/dialogs.php`, `lang/fr/dialogs.php`, `lang/hu/dialogs.php`, `lang/it/dialogs.php`, `lang/nl/dialogs.php`, `lang/no/dialogs.php`, `lang/pl/dialogs.php`, `lang/ru/dialogs.php`, `lang/sk/dialogs.php`, `lang/sv/dialogs.php`, `lang/vi/dialogs.php`, `lang/zh_CN/dialogs.php`, `lang/zh_TW/dialogs.php` — none of which declares a dependency on it: one file is the hub of 15 separate couplings, not 15 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 15.
  • Change-coupling hub: dialogs.php → dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php lang/el/dialogs.php — `lang/el/dialogs.php` changes together with 19 other files — `lang/cz/dialogs.php`, `lang/de/dialogs.php`, `lang/en/dialogs.php`, `lang/es/dialogs.php`, `lang/fa/dialogs.php`, `lang/fr/dialogs.php`, `lang/hu/dialogs.php`, `lang/it/dialogs.php`, `lang/ja/dialogs.php`, `lang/nl/dialogs.php`, `lang/no/dialogs.php`, `lang/pl/dialogs.php`, `lang/pt/dialogs.php`, `lang/ru/dialogs.php`, `lang/sk/dialogs.php`, `lang/sv/dialogs.php`, `lang/vi/dialogs.php`, `lang/zh_CN/dialogs.php`, `lang/zh_TW/dialogs.php` — none of which declares a dependency on it: one file is the hub of 19 separate couplings, not 19 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 19.
  • Change-coupling hub: dialogs.php → dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php lang/zh_TW/dialogs.php — `lang/zh_TW/dialogs.php` changes together with 12 other files — `lang/cz/dialogs.php`, `lang/de/dialogs.php`, `lang/en/dialogs.php`, `lang/fr/dialogs.php`, `lang/hu/dialogs.php`, `lang/it/dialogs.php`, `lang/nl/dialogs.php`, `lang/no/dialogs.php`, `lang/pl/dialogs.php`, `lang/sk/dialogs.php`, `lang/sv/dialogs.php`, `lang/vi/dialogs.php` — none of which declares a dependency on it: one file is the hub of 12 separate couplings, not 12 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 12.
  • Change-coupling hub: dialogs.php → dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php lang/zh_CN/dialogs.php — `lang/zh_CN/dialogs.php` changes together with 13 other files — `lang/cz/dialogs.php`, `lang/de/dialogs.php`, `lang/en/dialogs.php`, `lang/fr/dialogs.php`, `lang/hu/dialogs.php`, `lang/it/dialogs.php`, `lang/nl/dialogs.php`, `lang/no/dialogs.php`, `lang/pl/dialogs.php`, `lang/sk/dialogs.php`, `lang/sv/dialogs.php`, `lang/vi/dialogs.php`, `lang/zh_TW/dialogs.php` — none of which declares a dependency on it: one file is the hub of 13 separate couplings, not 13 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 13.
  • Change-coupling hub: dialogs.php → dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php lang/ru/dialogs.php — `lang/ru/dialogs.php` changes together with 14 other files — `lang/cz/dialogs.php`, `lang/de/dialogs.php`, `lang/en/dialogs.php`, `lang/fr/dialogs.php`, `lang/hu/dialogs.php`, `lang/it/dialogs.php`, `lang/nl/dialogs.php`, `lang/no/dialogs.php`, `lang/pl/dialogs.php`, `lang/sk/dialogs.php`, `lang/sv/dialogs.php`, `lang/vi/dialogs.php`, `lang/zh_CN/dialogs.php`, `lang/zh_TW/dialogs.php` — none of which declares a dependency on it: one file is the hub of 14 separate couplings, not 14 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 14.
  • Change-coupling hub: dialogs.php → dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php lang/es/dialogs.php — `lang/es/dialogs.php` changes together with 18 other files — `lang/cz/dialogs.php`, `lang/de/dialogs.php`, `lang/en/dialogs.php`, `lang/fa/dialogs.php`, `lang/fr/dialogs.php`, `lang/hu/dialogs.php`, `lang/it/dialogs.php`, `lang/ja/dialogs.php`, `lang/nl/dialogs.php`, `lang/no/dialogs.php`, `lang/pl/dialogs.php`, `lang/pt/dialogs.php`, `lang/ru/dialogs.php`, `lang/sk/dialogs.php`, `lang/sv/dialogs.php`, `lang/vi/dialogs.php`, `lang/zh_CN/dialogs.php`, `lang/zh_TW/dialogs.php` — none of which declares a dependency on it: one file is the hub of 18 separate couplings, not 18 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 18.
  • Change-coupling hub: dialogs.php → dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php, dialogs.php lang/fa/dialogs.php — `lang/fa/dialogs.php` changes together with 17 other files — `lang/cz/dialogs.php`, `lang/de/dialogs.php`, `lang/en/dialogs.php`, `lang/fr/dialogs.php`, `lang/hu/dialogs.php`, `lang/it/dialogs.php`, `lang/ja/dialogs.php`, `lang/nl/dialogs.php`, `lang/no/dialogs.php`, `lang/pl/dialogs.php`, `lang/pt/dialogs.php`, `lang/ru/dialogs.php`, `lang/sk/dialogs.php`, `lang/sv/dialogs.php`, `lang/vi/dialogs.php`, `lang/zh_CN/dialogs.php`, `lang/zh_TW/dialogs.php` — none of which declares a dependency on it: one file is the hub of 17 separate couplings, not 17 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 17.
AC3 · Page structure · Page without a main landmark · ×9
  • Page without a main landmark resources/views/error/error.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/error/v1-is-dead.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/health-up.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/install/view.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/update/error.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/update/results.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/vueapp.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 simple_error_template.html: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 vite/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×9
  • Animation without a prefers-reduced-motion guard resources/js/v8/views/landing/LandingPortfolio.vue:60 — <uicon> moves — its `animate-bounce` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard resources/views/health-up.blade.php:16 — <span> moves — its `animate-ping` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard resources/js/v8/views/App.vue:63 — `.lychee-page-enter-active` moves (`transition: opacity 0.18s ease, transform 0.18s ease`) 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/js/v8/views/landing/LandingClassic.vue:144 — `.animate-landingAnimateDown` moves (`animation-name: landingAnimateDown`) 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/js/v8/components/LycheeLoadingIcon.vue:75 — `.loading-ring` moves (`animation: loading-ring-spin 0.9s linear infinite`) 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/js/v8/components/gallery/photoModule/PhotoPanel.vue:201 — `.slide-next-leave-active` moves (`transition: transform 0.5s cubic-bezier(0.165, 0.84, 0.44, 1), opacity 0.2s cubic-bezier(0.445, 0.05, 0.55, 0.95)`) 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/js/v8/components/gallery/photoModule/PhotoPanel.vue:221 — `.slide-previous-leave-active` moves (`transition: transform 0.5s cubic-bezier(0.165, 0.84, 0.44, 1), opacity 0.2s cubic-bezier(0.445, 0.05, 0.55, 0.95)`) 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/js/v8/components/footers/LandingFooter.vue:97 — `.animate-landingAnimateUp` moves (`animation-name: landingAnimateUp`) 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/js/v7/views/Landing.vue:133 — `.animate-landingAnimateDown` moves (`animation-name: landingAnimateDown`) 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.
AC4 · Keyboard semantics · Anchor without href · ×8
  • Anchor without href resources/js/v7/components/forms/auth/LoginForm.vue:10 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href resources/js/v7/components/gallery/albumModule/PhotoThumbPanelControl.vue:42 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href resources/js/v7/components/gallery/albumModule/PhotoThumbPanelControl.vue:45 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href resources/js/v7/components/gallery/albumModule/PhotoThumbPanelControl.vue:48 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href resources/js/v7/components/gallery/albumModule/PhotoThumbPanelControl.vue:51 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href resources/js/v7/components/gallery/albumModule/PhotoThumbPanelControl.vue:54 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href resources/js/v7/components/gallery/albumModule/thumbs/PhotoThumb.vue:2 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href resources/js/v7/components/webshop/TransactionIdLink.vue:2 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
D15 · Churn × Complexity Hotspots · Repeated repair · ×8
  • Repeated repair: resources/js/v8/components/drawers/PhotoDetails.vue resources/js/v8/components/drawers/PhotoDetails.vue:324 — resources/js/v8/components/drawers/PhotoDetails.vue changed 7 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is getModel at line 324), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “More fixes on v8: missing data due to StructofArrays and visuals (#4858)”; “Fix person attributions (#4802)”; “Fix map on first sidebar load (#4761)”; “Fix photo ordering on albums (#4685)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- resources/js/v8/components/drawers/PhotoDetails.vue`: 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.
  • Repeated repair: resources/js/v8/utils/adaptPhotoTile.ts resources/js/v8/utils/adaptPhotoTile.ts:225 — resources/js/v8/utils/adaptPhotoTile.ts changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is adaptPhotoTile.mergePhotoDetail at line 225), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “More fixes on v8: missing data due to StructofArrays and visuals (#4858)”; “Fix unsanized description of photos (#4824)”; “Implement search v3 + fixes search v2 (#4777)”; “Fix dock on smart album (#4741)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- resources/js/v8/utils/adaptPhotoTile.ts`: 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.
  • Repeated repair: resources/js/v8/components/forms/auth/LoginForm.vue resources/js/v8/components/forms/auth/LoginForm.vue:170 — resources/js/v8/components/forms/auth/LoginForm.vue changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is redirectToOauth at line 170), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(auth): show inline feedback for throttled password logins (#4964)”; “fix(auth): clear front-end stores on login and logout instead of Clear-Site-Data (#4932)”; “More fixes on v8: missing data due to StructofArrays and visuals (#4858)”; “Fix sprintf vulnerability (#4856)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- resources/js/v8/components/forms/auth/LoginForm.vue`: 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.
  • Repeated repair: resources/js/v8/components/headers/PhotoHeader.vue resources/js/v8/components/headers/PhotoHeader.vue:178 — resources/js/v8/components/headers/PhotoHeader.vue changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is (anonymous) at line 178), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(photo): scroll PDF pages instead of changing photo (#4898)”; “Fix dock on smart album (#4741)”; “Fix photo ordering on albums (#4685)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- resources/js/v8/components/headers/PhotoHeader.vue`: 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.
  • Repeated repair: resources/js/v8/components/gallery/albumModule/Virtualized/AlbumListViewVirtual.vue resources/js/v8/components/gallery/albumModule/Virtualized/AlbumListViewVirtual.vue:175 — resources/js/v8/components/gallery/albumModule/Virtualized/AlbumListViewVirtual.vue changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is (anonymous) at line 175), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix missing padding (#4797)”; “Fix display in non-timeline mode (#4738)”; “Refactoring and fixes on API v3 (#4728)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- resources/js/v8/components/gallery/albumModule/Virtualized/AlbumListViewVirtual.vue`: 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.
  • Repeated repair: resources/js/v7/components/forms/auth/LoginForm.vue resources/js/v7/components/forms/auth/LoginForm.vue:186 — resources/js/v7/components/forms/auth/LoginForm.vue changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is redirectToOauth at line 186), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(auth): show inline feedback for throttled password logins (#4964)”; “fix(auth): clear front-end stores on login and logout instead of Clear-Site-Data (#4932)”; “Fix sprintf vulnerability (#4856)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- resources/js/v7/components/forms/auth/LoginForm.vue`: 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.
  • Repeated repair: resources/js/v8/components/drawers/PhotoEdit.vue resources/js/v8/components/drawers/PhotoEdit.vue:188 — resources/js/v8/components/drawers/PhotoEdit.vue changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is save at line 188), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(photo): scroll PDF pages instead of changing photo (#4898)”; “Fix sprintf vulnerability (#4856)”; “Fix time always changing when editing pictures. (#4646)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- resources/js/v8/components/drawers/PhotoEdit.vue`: 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.
  • Repeated repair: resources/js/v8/components/gallery/albumModule/Virtualized/AlbumRootListViewVirtual.vue resources/js/v8/components/gallery/albumModule/Virtualized/AlbumRootListViewVirtual.vue:171 — resources/js/v8/components/gallery/albumModule/Virtualized/AlbumRootListViewVirtual.vue changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is (anonymous) at line 171), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix missing padding (#4797)”; “Fix display in non-timeline mode (#4738)”; “Refactoring and fixes on API v3 (#4728)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 20:12:27 +01:00' --until='2026-11-15 20:12:27 +01:00' --full-history --no-merges -- resources/js/v8/components/gallery/albumModule/Virtualized/AlbumRootListViewVirtual.vue`: 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.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×8
  • Edited copy of a member (6 corresponding lines) app/Actions/Diagnostics/Pipes/Checks/AuthDisabledCheck.php:63 — app/Actions/Diagnostics/Pipes/Checks/AuthDisabledCheck.php:63-68 | app/Actions/Diagnostics/Pipes/Checks/AuthDisabledCheck.php:78-83 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) app/Http/Requests/ShopManagement/PrintSize/CreatePrintSizeRequest.php:57 — app/Http/Requests/ShopManagement/PrintSize/CreatePrintSizeRequest.php:57-62 | app/Http/Requests/ShopManagement/PrintSize/UpdatePrintSizeRequest.php:60-66 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) app/Actions/Albums/Top.php:164 — app/Actions/Albums/Top.php:164-169 | app/Actions/Albums/Top.php:174-179 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) app/Http/Requests/Album/RenameAlbumTrackRequest.php:49 — app/Http/Requests/Album/RenameAlbumTrackRequest.php:49-58 | app/Http/Requests/Album/DeleteAlbumTrackRequest.php:47-52 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) app/Http/Requests/Photo/RotatePhotoRequest.php:48 — app/Http/Requests/Photo/RotatePhotoRequest.php:48-54 | app/Http/Requests/Photo/SetPhotosTagsRequest.php:49-54 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) app/Models/Extensions/FiltersUploadValidation.php:29 — app/Models/Extensions/FiltersUploadValidation.php:29-34 | app/Models/Person.php:140-145 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) app/Enum/TimelineAlbumGranularity.php:31 — app/Enum/TimelineAlbumGranularity.php:31-36 | app/Enum/TimelinePhotoGranularity.php:32-38 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) app/Image/Files/DownloadedFile.php:70 — app/Image/Files/DownloadedFile.php:70-75 | app/Image/Files/UploadedFile.php:68-73 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×8
  • Duplicated block (10 lines × 2) app/Actions/Photo/BaseArchive.php:291 — app/Actions/Photo/BaseArchive.php:291-300 | app/Actions/Photo/BaseArchive.php:401-410 — 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/Actions/Photo/BaseArchive.php:291` 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 (10 lines × 2) app/Actions/Statistics/Spaces.php:195 — app/Actions/Statistics/Spaces.php:195-204 | app/Actions/Statistics/Spaces.php:330-339 — 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/Actions/Statistics/Spaces.php:195` 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 (10 lines × 2) app/Console/Commands/ImageProcessing/MoveToS3.php:66 — app/Console/Commands/ImageProcessing/MoveToS3.php:66-75 | app/Console/Commands/ImageProcessing/TrackS3Migrate.php:68-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. Read the line range as the matched WINDOW rather than a finished unit: at `app/Console/Commands/ImageProcessing/MoveToS3.php:66` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/Console/Commands/ImageProcessing/MoveToS3.php:65` calls `whereNot` and `app/Console/Commands/ImageProcessing/TrackS3Migrate.php:67` 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 (10 lines × 2) app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php:309 — app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php:309-318 | app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php:331-340 — 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/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php:309` 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 (10 lines × 2) app/Policies/AlbumPolicy.php:857 — app/Policies/AlbumPolicy.php:857-866 | app/Policies/PhotoPolicy.php:405-414 — 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 (10 lines × 2) app/Actions/Renamer/PreviewAlbums.php:55 — app/Actions/Renamer/PreviewAlbums.php:55-64 | app/Actions/Renamer/PreviewPhotos.php:63-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.
  • Duplicated block (10 lines × 2) app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php:156 — app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php:156-169 | app/Actions/Search/StructOfArrays/QuerySearchPhotos.php:171-180 — before extracting anything, compare `app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php` and `app/Actions/Search/StructOfArrays/QuerySearchPhotos.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 2) app/Actions/Import/Pipes/DeleteMissingAlbums.php:35 — app/Actions/Import/Pipes/DeleteMissingAlbums.php:35-44 | app/Actions/Import/Pipes/DeleteMissingPhotos.php:36-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 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. Note first that the copies are not typed on the same thing: `Delete` names `App\Actions\Album\Delete` in one and `App\Actions\Photo\Delete` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×7
  • Duplicated block (7 lines × 2) app/Actions/Photo/Pipes/Standalone/PlacePhoto.php:82 — app/Actions/Photo/Pipes/Standalone/PlacePhoto.php:82-88 | app/Actions/Photo/Pipes/VideoPartner/PlaceVideo.php:82-88 — 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.
  • Duplicated block (7 lines × 2) app/Http/Requests/Face/AssignFaceRequest.php:43 — app/Http/Requests/Face/AssignFaceRequest.php:43-52 | app/Http/Requests/Face/BatchAssignFacesRequest.php:46-52 — 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/Http/Requests/Face/AssignFaceRequest.php:43` 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 (7 lines × 2) app/Http/Requests/Search/GetSearchRequest.php:79 — app/Http/Requests/Search/GetSearchRequest.php:79-85 | app/Http/Requests/Search/GetSearchV3Request.php:116-122 — 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/Http/Requests/Search/GetSearchRequest.php:79` 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. 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/Http/Resources/Search/ResultsResource.php:57 — app/Http/Resources/Search/ResultsResource.php:57-63 | app/Http/Resources/Timeline/TimelineResource.php:50-56 — 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.
  • Duplicated block (7 lines × 2) app/Http/Controllers/Gallery/AlbumListing/AlbumPersonController.php:107 — app/Http/Controllers/Gallery/AlbumListing/AlbumPersonController.php:107-113 | app/Http/Controllers/Gallery/AlbumListing/AlbumPinnedController.php:106-112 — 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/Http/Requests/Traits/Authorize/AuthorizeCanEditPhotosTrait.php:26 — app/Http/Requests/Traits/Authorize/AuthorizeCanEditPhotosTrait.php:26-32 | app/Http/Requests/Traits/Authorize/AuthorizeCanHighlightPhotosTrait.php:26-32 — 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 (7 lines × 2) app/Services/AlbumBucketComputer.php:42 — app/Services/AlbumBucketComputer.php:42-48 | app/Services/PhotoBucketComputer.php:46-52 — 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.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×7
  • Duplicated block (6 lines × 2) app/Http/Requests/ShopManagement/PrintSize/CreatePrintSizeRequest.php:57 — app/Http/Requests/ShopManagement/PrintSize/CreatePrintSizeRequest.php:57-62 | app/Http/Requests/ShopManagement/PrintSize/UpdatePrintSizeRequest.php:61-66 — before extracting anything, compare `app/Http/Requests/ShopManagement/PrintSize/CreatePrintSizeRequest.php` and `app/Http/Requests/ShopManagement/PrintSize/UpdatePrintSizeRequest.php` as WHOLE FILES: 95% 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/Http/Requests/ShopManagement/PrintSize/UpdatePrintSizeRequest.php:60` calls `findOrFail` and `app/Http/Requests/ShopManagement/PrintSize/CreatePrintSizeRequest.php:56` 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 (6 lines × 2) app/Http/Requests/Traits/Authorize/AuthorizeCanMergeAlbumsTrait.php:32 — app/Http/Requests/Traits/Authorize/AuthorizeCanMergeAlbumsTrait.php:32-37 | app/Http/Requests/Traits/Authorize/AuthorizeCanMoveAlbumsTrait.php:31-36 — 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 (6 lines × 2) app/Jobs/UploadSizeVariantToS3Job.php:69 — app/Jobs/UploadSizeVariantToS3Job.php:69-74 | app/Jobs/WatermarkerJob.php:98-103 — 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/Jobs/UploadSizeVariantToS3Job.php:69` 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 (6 lines × 2) app/Actions/Album/SetProtectionPolicy.php:90 — app/Actions/Album/SetProtectionPolicy.php:90-95 | app/Http/Controllers/Gallery/AlbumController.php:434-439 — 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.
  • Duplicated block (6 lines × 2) app/Jobs/RecomputeAlbumPhotoBucketsJob.php:60 — app/Jobs/RecomputeAlbumPhotoBucketsJob.php:60-65 | app/Jobs/RecomputeChildAlbumBucketsJob.php:64-70 — 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 (6 lines × 2) app/Models/User.php:289 — app/Models/User.php:289-294 | app/Models/UserGroup.php:93-98 — 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 (6 lines × 2) app/SmartAlbums/MyBestPicturesAlbum.php:38 — app/SmartAlbums/MyBestPicturesAlbum.php:38-43 | app/SmartAlbums/MyRatedPicturesAlbum.php:34-39 — 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 · Edited copy of a member (14 corresponding lines) · ×6
  • Edited copy of a member (14 corresponding lines) app/Http/Requests/UserManagement/AddUserRequest.php:76 — app/Http/Requests/UserManagement/AddUserRequest.php:76-89 | app/Http/Requests/UserManagement/SetUserSettingsRequest.php:81-100 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) app/Actions/Import/Pipes/DeleteMissingPhotos.php:112 — app/Actions/Import/Pipes/DeleteMissingPhotos.php:112-128 | app/Actions/Import/Pipes/ImportPhotos.php:155-168 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) app/Http/Resources/Models/ThumbAlbumResource.php:145 — app/Http/Resources/Models/ThumbAlbumResource.php:145-158 | app/Http/Resources/Models/Utils/PreFormattedAlbumData.php:84-97 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) app/Http/Controllers/Gallery/FlowListController.php:164 — app/Http/Controllers/Gallery/FlowListController.php:164-177 | app/Http/Resources/Flow/FlowItemResource.php:148-163 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) app/Http/Resources/GalleryConfigs/InitConfig.php:453 — app/Http/Resources/GalleryConfigs/InitConfig.php:453-466 | app/Http/Resources/Rights/ModulesRightsResource.php:272-285 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) app/Models/Extensions/ThrowsConsistentExceptions.php:62 — app/Models/Extensions/ThrowsConsistentExceptions.php:62-75 | app/Models/Extensions/ThrowsConsistentExceptions.php:87-105 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×6
  • Duplicated block (11 lines × 2) app/Console/Commands/RecomputeAlbumSizes.php:74 — app/Console/Commands/RecomputeAlbumSizes.php:74-84 | app/Console/Commands/RecomputeAlbumStats.php:74-84 — before extracting anything, compare `app/Console/Commands/RecomputeAlbumSizes.php` and `app/Console/Commands/RecomputeAlbumStats.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/Console/Commands/RecomputeAlbumSizes.php:74` 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 (11 lines × 2) app/DTO/BulkAlbumPatchData.php:108 — app/DTO/BulkAlbumPatchData.php:108-118 | app/Http/Resources/Admin/BulkAlbumResource.php:89-99 — 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.
  • Duplicated block (11 lines × 2) app/DTO/Delete/PhotosToBeDeletedDTO.php:208 — app/DTO/Delete/PhotosToBeDeletedDTO.php:208-218 | app/DTO/Delete/PhotosToBeDeletedDTO.php:242-252 — 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/DTO/Delete/PhotosToBeDeletedDTO.php:208` 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 (11 lines × 2) app/Http/Controllers/Admin/UserManagementController.php:58 — app/Http/Controllers/Admin/UserManagementController.php:58-68 | app/Http/Controllers/Admin/UserManagementController.php:93-103 — 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/Http/Controllers/Admin/UserManagementController.php:58` 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.
  • Duplicated block (11 lines × 2) app/Http/Controllers/Gallery/MapListingController.php:62 — app/Http/Controllers/Gallery/MapListingController.php:62-72 | app/Http/Controllers/Gallery/MapListingController.php:91-101 — 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/Http/Controllers/Gallery/MapListingController.php:62` 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 (11 lines × 2) app/Rules/AlbumIDListRule.php:24 — app/Rules/AlbumIDListRule.php:24-34 | app/Rules/RandomIDListRule.php:23-33 — 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.
AC2 · Forms & labels · <fieldset> without a <legend> · ×5
  • <fieldset> without a <legend> resources/js/v7/components/forms/basic/Fieldset.vue:2 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
  • <fieldset> without a <legend> resources/js/v7/components/forms/profile/SetLogin.vue:2 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
  • <fieldset> without a <legend> resources/js/v7/components/forms/profile/SetOauth.vue:2 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
  • <fieldset> without a <legend> resources/js/v7/components/forms/profile/SetSecondFactor.vue:2 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
  • <fieldset> without a <legend> resources/js/v7/components/forms/profile/SetSharedAlbumsVisibility.vue:2 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
D31 · IaC & Container Security · Medium IaC · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×5
  • Edited copy of a member (11 corresponding lines) app/Actions/Album/StructOfArrays/QueryChildrenForPerson.php:33 — app/Actions/Album/StructOfArrays/QueryChildrenForPerson.php:33-43 | app/Actions/Album/StructOfArrays/QueryChildrenForTag.php:33-50 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) app/Http/Requests/Traits/Authorize/AuthorizeCanMergeAlbumsTrait.php:32 — app/Http/Requests/Traits/Authorize/AuthorizeCanMergeAlbumsTrait.php:32-45 | app/Http/Requests/Traits/Authorize/AuthorizeCanMoveAlbumsTrait.php:31-41 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) app/Models/PersonAlbum.php:133 — app/Models/PersonAlbum.php:133-143 | app/Models/TagAlbum.php:183-200 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) app/SmartAlbums/BaseSmartAlbum.php:180 — app/SmartAlbums/BaseSmartAlbum.php:180-190 | app/SmartAlbums/OneStarAlbum.php:52-66 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) app/Http/Requests/Photo/GetPhotoRatiosRequest.php:129 — app/Http/Requests/Photo/GetPhotoRatiosRequest.php:129-143 | app/Http/Requests/Photo/GetPhotoDetailsRequest.php:101-111 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×5
  • Edited copy of a member (7 corresponding lines) app/Http/Resources/Flow/FlowResource.php:43 — app/Http/Resources/Flow/FlowResource.php:43-49 | app/Http/Resources/Search/ResultsResource.php:56-65 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) app/Jobs/ImportImageJob.php:57 — app/Jobs/ImportImageJob.php:57-65 | app/Jobs/UploadTrackToS3Job.php:40-46 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) app/Http/Requests/Photo/MovePhotosRequest.php:71 — app/Http/Requests/Photo/MovePhotosRequest.php:71-78 | app/Http/Requests/Photo/CopyPhotosRequest.php:46-52 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) app/SmartAlbums/OneStarAlbum.php:33 — app/SmartAlbums/OneStarAlbum.php:33-39 | app/SmartAlbums/TwoStarsAlbum.php:34-40 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) app/Http/Resources/Shop/PixelSizeResource.php:36 — app/Http/Resources/Shop/PixelSizeResource.php:36-42 | app/Http/Resources/Shop/PrintSizeResource.php:38-46 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×5
  • Edited copy of a member (10 corresponding lines) app/Policies/AlbumPolicy.php:853 — app/Policies/AlbumPolicy.php:853-866 | app/Policies/PhotoPolicy.php:405-414 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) app/Http/Resources/Models/Utils/PreComputedPhotoData.php:72 — app/Http/Resources/Models/Utils/PreComputedPhotoData.php:72-81 | app/Http/Resources/Models/Utils/PreformattedPhotoData.php:80-89 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) app/DTO/AlbumSortingCriterion.php:25 — app/DTO/AlbumSortingCriterion.php:25-34 | app/DTO/PhotoSortingCriterion.php:25-34 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) app/Actions/Diagnostics/Pipes/Checks/ForeignKeyListInfo.php:26 — app/Actions/Diagnostics/Pipes/Checks/ForeignKeyListInfo.php:26-37 | app/Actions/Diagnostics/Pipes/Infos/CountForeignKeyInfo.php:25-34 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) app/Http/Requests/Flow/FlowRequest.php:23 — app/Http/Requests/Flow/FlowRequest.php:23-32 | app/Http/Requests/Flow/GetFlowListRequest.php:26-37 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×5
  • Edited copy of a member (5 corresponding lines) app/Actions/WebAuthn/VerifyLogin.php:86 — app/Actions/WebAuthn/VerifyLogin.php:86-96 | app/Actions/WebAuthn/StoreCredential.php:74-78 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) app/Http/Requests/LandingLink/PatchLandingLinkRequest.php:52 — app/Http/Requests/LandingLink/PatchLandingLinkRequest.php:52-56 | app/Http/Requests/LandingLink/UpdateLandingLinkRequest.php:52-56 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) database/factories/AlbumFactory.php:87 — database/factories/AlbumFactory.php:87-92 | database/factories/TagAlbumFactory.php:70-74 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) app/Http/Controllers/AiVision/FaceDetectionController.php:331 — app/Http/Controllers/AiVision/FaceDetectionController.php:331-336 | app/Models/Face.php:124-128 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) app/Http/Controllers/Admin/Maintenance/DestroyDismissedFaces.php:32 — app/Http/Controllers/Admin/Maintenance/DestroyDismissedFaces.php:32-36 | app/Http/Controllers/Admin/Maintenance/RunFaceClustering.php:33-38 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×5
  • Duplicated block (5 lines × 2) app/Http/Requests/Search/GetSearchRequest.php:46 — app/Http/Requests/Search/GetSearchRequest.php:46-50 | app/Http/Requests/Search/InitSearchRequest.php:30-34 — 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 (5 lines × 2) app/Http/Requests/Timeline/GetTimelineRequest.php:21 — app/Http/Requests/Timeline/GetTimelineRequest.php:21-25 | app/Http/Requests/Timeline/IdOrDatedTimelineRequest.php:51-55 — before extracting anything, compare `app/Http/Requests/Timeline/GetTimelineRequest.php` and `app/Http/Requests/Timeline/IdOrDatedTimelineRequest.php` as WHOLE FILES: 82% 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 1 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.
  • Duplicated block (5 lines × 2) app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php:68 — app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php:68-72 | app/Actions/Search/StructOfArrays/QuerySearchPhotos.php:72-76 — before extracting anything, compare `app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php` and `app/Actions/Search/StructOfArrays/QuerySearchPhotos.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) app/Http/Requests/Renamer/CreateRenamerRuleRequest.php:74 — app/Http/Requests/Renamer/CreateRenamerRuleRequest.php:74-78 | app/Http/Requests/Renamer/UpdateRenamerRuleRequest.php:83-87 — 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 (5 lines × 2) app/Metadata/Renamer/Renamer.php:87 — app/Metadata/Renamer/Renamer.php:87-91 | app/Metadata/Renamer/Renamer.php:95-99 — 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×5
  • Low cohesion: Photo (LCOM4 12) app/Models/Photo.php:149 — Photo's methods fall into 12 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 12 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: BaseAlbumImpl (LCOM4 8) app/Models/BaseAlbumImpl.php:152 — BaseAlbumImpl's methods fall into 8 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 8 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: OrderService (LCOM4 6) app/Actions/Shop/OrderService.php:62 — OrderService'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: InitConfig (LCOM4 5) app/Http/Resources/GalleryConfigs/InitConfig.php:37 — InitConfig'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: QueryPhotoUrls (LCOM4 4) app/Actions/Photo/StructOfArrays/QueryPhotoUrls.php:32 — QueryPhotoUrls'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.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×4
  • Edited copy of a member (15 corresponding lines) app/Actions/Album/Delete.php:134 — app/Actions/Album/Delete.php:134-148 | app/Actions/Album/Delete.php:160-174 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) app/Http/Controllers/Admin/ShopManagementController.php:69 — app/Http/Controllers/Admin/ShopManagementController.php:69-83 | app/Http/Controllers/Admin/ShopManagementController.php:95-109 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) app/Http/Controllers/Gallery/AlbumTracksController.php:73 — app/Http/Controllers/Gallery/AlbumTracksController.php:73-87 | app/Models/Album.php:632-646 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) app/Relations/HasManyChildAlbums.php:90 — app/Relations/HasManyChildAlbums.php:90-104 | app/Relations/HasManyChildPhotos.php:117-131 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×4
  • Edited copy of a member (9 corresponding lines) app/Http/Requests/Renamer/CreateRenamerRuleRequest.php:70 — app/Http/Requests/Renamer/CreateRenamerRuleRequest.php:70-78 | app/Http/Requests/Renamer/UpdateRenamerRuleRequest.php:78-87 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) app/Jobs/UploadSizeVariantToS3Job.php:69 — app/Jobs/UploadSizeVariantToS3Job.php:69-77 | app/Jobs/UploadTrackToS3Job.php:67-75 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) app/Services/BucketKeys.php:88 — app/Services/BucketKeys.php:88-106 | database/migrations/TemporaryModels/BucketKeyBackfill.php:41-49 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) app/Http/Resources/Search/ResultsResource.php:82 — app/Http/Resources/Search/ResultsResource.php:82-94 | app/Http/Resources/Timeline/TimelineResource.php:82-90 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×4
  • Edited copy of a member (8 corresponding lines) app/Actions/Album/StructOfArrays/QueryRightsForAlbum.php:58 — app/Actions/Album/StructOfArrays/QueryRightsForAlbum.php:58-69 | app/Policies/AlbumPolicy.php:676-683 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) app/Actions/Shop/PurchasableService.php:273 — app/Actions/Shop/PurchasableService.php:273-282 | app/Actions/Shop/PurchasableService.php:294-301 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) app/Services/BucketKeys.php:44 — app/Services/BucketKeys.php:44-51 | database/migrations/TemporaryModels/BucketKeyBackfill.php:29-36 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) app/Exceptions/Handler.php:277 — app/Exceptions/Handler.php:277-286 | app/Exceptions/Handlers/NoEncryptionKey.php:29-36 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×4
  • Duplicated block (17 lines × 2) app/Actions/Album/StructOfArrays/BuildAlbumDataResource.php:110 — app/Actions/Album/StructOfArrays/BuildAlbumDataResource.php:110-126 | app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php:188-204 — before extracting anything, compare `app/Actions/Album/StructOfArrays/BuildAlbumDataResource.php` and `app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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/Actions/Album/StructOfArrays/BuildAlbumDataResource.php:110` 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 (17 lines × 2) app/Http/Requests/Album/GetAlbumChildrenRequest.php:68 — app/Http/Requests/Album/GetAlbumChildrenRequest.php:68-84 | app/Http/Requests/Album/GetAlbumPhotosRequest.php:111-127 — 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 (17 lines × 2) app/Models/Extensions/ForwardsToParentImplementation.php:132 — app/Models/Extensions/ForwardsToParentImplementation.php:132-148 | app/Models/Extensions/ThrowsConsistentExceptions.php:87-103 — 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 (17 lines × 2) app/Services/TitleSplitter.php:56 — app/Services/TitleSplitter.php:56-72 | database/migrations/TemporaryModels/TitleSplitter.php:50-66 — 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. 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.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×4
  • Duplicated block (16 lines × 2) app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php:194 — app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php:194-209 | app/Actions/Search/StructOfArrays/QuerySearchPhotos.php:207-222 — before extracting anything, compare `app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php` and `app/Actions/Search/StructOfArrays/QuerySearchPhotos.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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/Actions/Photo/StructOfArrays/QueryPhotoRatios.php:194` 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 (16 lines × 2) app/Console/Commands/RecomputeAlbumSizes.php:56 — app/Console/Commands/RecomputeAlbumSizes.php:56-71 | app/Console/Commands/RecomputeAlbumStats.php:56-71 — before extracting anything, compare `app/Console/Commands/RecomputeAlbumSizes.php` and `app/Console/Commands/RecomputeAlbumStats.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/Console/Commands/RecomputeAlbumSizes.php:56` 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 (16 lines × 2) app/Image/Files/NativeLocalFile.php:86 — app/Image/Files/NativeLocalFile.php:86-101 | app/Image/Files/NativeLocalFile.php:121-136 — 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/Image/Files/NativeLocalFile.php:86` 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. 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 (16 lines × 2) app/Models/Builders/PersonAlbumBuilder.php:34 — app/Models/Builders/PersonAlbumBuilder.php:34-49 | app/Models/Builders/TagAlbumBuilder.php:45-60 — 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 (14 lines × 2) · ×4
  • Duplicated block (14 lines × 2) app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php:100 — app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php:100-113 | app/Actions/Search/StructOfArrays/QuerySearchPhotos.php:99-112 — before extracting anything, compare `app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php` and `app/Actions/Search/StructOfArrays/QuerySearchPhotos.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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/Actions/Photo/StructOfArrays/QueryPhotoRatios.php:100` 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 (14 lines × 2) app/Console/Commands/ImageProcessing/Detect360.php:63 — app/Console/Commands/ImageProcessing/Detect360.php:63-76 | app/Console/Commands/ImageProcessing/ExtractMotionPhotos.php:101-114 — 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/Console/Commands/ImageProcessing/Detect360.php:63` 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 (14 lines × 2) app/Http/Controllers/Gallery/AlbumListing/AlbumChildrenController.php:136 — app/Http/Controllers/Gallery/AlbumListing/AlbumChildrenController.php:136-149 | app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php:104-117 — 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 (14 lines × 2) app/Http/Controllers/Gallery/AlbumListing/AlbumChildrenController.php:181 — app/Http/Controllers/Gallery/AlbumListing/AlbumChildrenController.php:181-194 | app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php:356-369 — 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 × 2) · ×4
  • Duplicated block (9 lines × 2) app/Console/Commands/RescanFailedFaces.php:73 — app/Console/Commands/RescanFailedFaces.php:73-81 | app/Console/Commands/ScanFaces.php:60-68 — 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/Console/Commands/RescanFailedFaces.php:73` 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.
  • Duplicated block (9 lines × 2) app/Http/Controllers/AiVision/PersonClaimController.php:40 — app/Http/Controllers/AiVision/PersonClaimController.php:40-48 | app/Http/Controllers/AiVision/SelfieClaimController.php:84-92 — 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/Relations/HasManyBidirectionally.php:58 — app/Relations/HasManyBidirectionally.php:58-66 | app/Relations/HasManySizeVariants.php:112-121 — 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/Relations/HasManyBidirectionally.php:58` 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 (9 lines × 2) app/Actions/Album/Delete.php:134 — app/Actions/Album/Delete.php:134-142 | app/Actions/Album/Delete.php:160-168 — 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.
X2 · Cancellation propagation · Async function without AbortSignal · ×4
  • Async function without AbortSignal: load resources/js/utils/detailRequests.ts:20 — `load` 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 })`.
  • Async function without AbortSignal: batchAssign resources/js/services/face-batch-service.ts:16 — `batchAssign` awaits `axios.post(…)` 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: `axios.post(url, { signal })`.
  • Async function without AbortSignal: batchUnassign resources/js/services/face-batch-service.ts:46 — `batchUnassign` awaits `axios.post(…)` 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: `axios.post(url, { signal })`.
  • Async function without AbortSignal: batchUnassignByPhotos resources/js/services/face-batch-service.ts:61 — `batchUnassignByPhotos` awaits `axios.post(…)` 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: `axios.post(url, { signal })`.
AC1 · Text alternatives · <video> without a captions track · ×3
  • <video> without a captions track resources/js/embed/components/Lightbox.vue:40 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
  • <video> without a captions track resources/js/v7/components/gallery/photoModule/PhotoBox.vue:13 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
  • <video> without a captions track resources/js/v8/components/gallery/photoModule/PhotoBox.vue:32 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
D3 · God Classes · TooManyMethods · ×3
  • TooManyMethods: CacheKeyProvider app/Services/Cache/CacheKeyProvider.php:30 — TooManyMethods — 58 methods. The bar is 30 methods; this is 28 over it, 1.93× 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: AlbumPolicy app/Policies/AlbumPolicy.php:30 — TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× 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: Album app/Models/Album.php:161 — TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× 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.
D3 · God Classes · MethodTooLong · ×3
  • MethodTooLong: InitConfig.__construct app/Http/Resources/GalleryConfigs/InitConfig.php:229 — MethodTooLong — __construct runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: QueryPhotoDetails.buildResource app/Actions/Photo/StructOfArrays/QueryPhotoDetails.php:105 — MethodTooLong — buildResource runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Extractor.createFromFile app/Metadata/Extractor.php:79 — MethodTooLong — createFromFile runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D35 · Change Coupling · Change coupling · ×3
  • Change coupling: all_settings.php ↔ all_settings.php lang/ja/all_settings.php:1 — `lang/ja/all_settings.php` and `lang/pt/all_settings.php` change together 100% of the time (14 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) 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 14 shared commits counted here, the most recent 3 are `9071f8bd` Ensure that config always have translation keys (#4872); `cea5c725` Fix: Don't show sensitive photos in landing (#4821); `01d64381` Add support for video loop attribute (#4807) — run `git show` on any of them.
  • Change coupling: all_settings.php ↔ all_settings.php lang/fr/all_settings.php:1 — `lang/fr/all_settings.php` and `lang/ja/all_settings.php` change together 93% of the time (13 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) 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 13 shared commits counted here, the most recent 3 are `9071f8bd` Ensure that config always have translation keys (#4872); `cea5c725` Fix: Don't show sensitive photos in landing (#4821); `01d64381` Add support for video loop attribute (#4807) — run `git show` on any of them.
  • Change coupling: InitConfig.php ↔ LycheeState.ts app/Http/Resources/GalleryConfigs/InitConfig.php:1 — `app/Http/Resources/GalleryConfigs/InitConfig.php` and `resources/js/stores/LycheeState.ts` change together 88% of the time (22 of the 25 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 22 shared commits counted here, the most recent 3 are `01d64381` Add support for video loop attribute (#4807); `9fe1d715` Add setting to show highest-quality image in the full-screen viewer (…; `c8769e6f` Add more configuration settings... (#4643) — run `git show` on any of them.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
  • Members sharing a duplicated core (4 members, 50+ identical tokens) app/Actions/Album/BaseArchive.php:267 — app/Actions/Album/BaseArchive.php:267-289 | app/Actions/Album/BaseArchive.php:311-353 | app/Actions/Photo/BaseArchive.php:199-261 | app/Actions/Photo/BaseArchive.php:332-465 — 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/Actions/Tag/DeleteTag.php:41 — app/Actions/Tag/DeleteTag.php:41-69 | app/Actions/Tag/MergeTag.php:71-111 | app/Actions/Tag/MergeTag.php:117-157 | app/Actions/Tag/MergeTag.php:169-211 — 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/Rules/BooleanRequireSupportRule.php:32 — app/Rules/BooleanRequireSupportRule.php:32-48 | app/Rules/EnumRequireSupportRule.php:42-68 | app/Rules/IntegerRequireSupportRule.php:33-48 | app/Rules/StringRequireSupportRule.php:34-50 — 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 · Edited copy of a member (22 corresponding lines) · ×3
  • Edited copy of a member (22 corresponding lines) app/Http/Resources/Models/HeadPersonAlbumResource.php:49 — app/Http/Resources/Models/HeadPersonAlbumResource.php:49-73 | app/Http/Resources/Models/HeadTagAlbumResource.php:50-71 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) app/Http/Controllers/Admin/Maintenance/BackfillAlbumSizes.php:51 — app/Http/Controllers/Admin/Maintenance/BackfillAlbumSizes.php:51-72 | app/Http/Controllers/Admin/Maintenance/FulfillPreCompute.php:53-76 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) app/Image/Files/LoadTemporaryFileTrait.php:33 — app/Image/Files/LoadTemporaryFileTrait.php:33-56 | app/Image/Files/TemporaryJobFile.php:45-66 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×3
  • Edited copy of a member (16 corresponding lines) app/Http/Controllers/Admin/LandingFeaturedItemController.php:74 — app/Http/Controllers/Admin/LandingFeaturedItemController.php:74-89 | app/Http/Controllers/Admin/LandingLinkController.php:74-89 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) app/DTO/Delete/PhotosToBeDeletedDTO.php:278 — app/DTO/Delete/PhotosToBeDeletedDTO.php:278-293 | app/DTO/Delete/PhotosToBeDeletedDTO.php:310-327 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) app/DTO/WebhookPayload.php:40 — app/DTO/WebhookPayload.php:40-55 | app/DTO/WebhookPayload.php:70-88 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×3
  • Edited copy of a member (18 corresponding lines) app/Actions/Renamer/RenameAlbums.php:36 — app/Actions/Renamer/RenameAlbums.php:36-58 | app/Actions/Renamer/RenamePhotos.php:36-53 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) app/Actions/Album/CreatePersonAlbum.php:35 — app/Actions/Album/CreatePersonAlbum.php:35-52 | app/Actions/Album/CreateTagAlbum.php:36-54 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) app/Http/Controllers/Admin/Maintenance/PurgeOrphanFaceEmbeddings.php:38 — app/Http/Controllers/Admin/Maintenance/PurgeOrphanFaceEmbeddings.php:38-55 | app/Http/Controllers/Admin/Maintenance/SyncFaceEmbeddings.php:34-51 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×3
  • Edited copy of a member (12 corresponding lines) app/Http/Controllers/AiVision/FaceClusterController.php:109 — app/Http/Controllers/AiVision/FaceClusterController.php:109-120 | app/Http/Controllers/AiVision/PersonClaimController.php:83-97 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) app/Http/Resources/Shop/PurchasablePixelSizeResource.php:40 — app/Http/Resources/Shop/PurchasablePixelSizeResource.php:40-51 | app/Http/Resources/Shop/PurchasablePrintSizeResource.php:40-52 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) app/Http/Requests/Album/SetAsCoverRequest.php:59 — app/Http/Requests/Album/SetAsCoverRequest.php:59-70 | app/Http/Requests/Album/SetAsHeaderRequest.php:65-82 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×3
  • Edited copy of a member (13 corresponding lines) app/Http/Requests/Face/AssignFaceRequest.php:43 — app/Http/Requests/Face/AssignFaceRequest.php:43-57 | app/Http/Requests/Face/BatchAssignFacesRequest.php:46-58 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) app/Http/Controllers/StatisticsController.php:49 — app/Http/Controllers/StatisticsController.php:49-62 | app/Http/Controllers/StatisticsController.php:73-85 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) app/Http/Controllers/Admin/UserManagementController.php:56 — app/Http/Controllers/Admin/UserManagementController.php:56-68 | app/Http/Controllers/Admin/UserManagementController.php:92-105 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×3
  • Edited copy of a member (4 corresponding lines) app/Http/Controllers/Gallery/AlbumTracksController.php:97 — app/Http/Controllers/Gallery/AlbumTracksController.php:97-100 | app/Models/Album.php:614-617 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) app/Http/Requests/ShopManagement/PixelSize/CreatePixelSizeRequest.php:53 — app/Http/Requests/ShopManagement/PixelSize/CreatePixelSizeRequest.php:53-56 | app/Http/Requests/ShopManagement/PixelSize/UpdatePixelSizeRequest.php:56-60 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) app/Http/Requests/Face/GetFaceQueueRequest.php:53 — app/Http/Requests/Face/GetFaceQueueRequest.php:53-57 | app/Http/Requests/Person/GetPeopleListRequest.php:27-30 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×3
  • Edited copy of a member (3 corresponding lines) app/Models/PersonAlbum.php:121 — app/Models/PersonAlbum.php:121-123 | app/Models/TagAlbum.php:140-142 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) app/Actions/Photo/Pipes/Init/AbstractInitPipe.php:25 — app/Actions/Photo/Pipes/Init/AbstractInitPipe.php:25-27 | app/Actions/Photo/Pipes/Standalone/AbstractStandalonePipe.php:25-27 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) app/Http/Requests/Face/AssignFaceRequest.php:68 — app/Http/Requests/Face/AssignFaceRequest.php:68-70 | app/Http/Requests/Face/BatchAssignFacesRequest.php:63-65 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×3
  • Duplicated block (12 lines × 2) app/Actions/Statistics/Counts.php:33 — app/Actions/Statistics/Counts.php:33-44 | app/Actions/Statistics/Counts.php:58-69 — 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 (12 lines × 2) app/DTO/WebhookPayload.php:40 — app/DTO/WebhookPayload.php:40-51 | app/DTO/WebhookPayload.php:70-81 — 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/DTO/WebhookPayload.php:40` 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 (12 lines × 2) app/Jobs/RecomputeAlbumSizeJob.php:114 — app/Jobs/RecomputeAlbumSizeJob.php:114-125 | app/Jobs/RecomputeAlbumStatsJob.php:141-152 — 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/Jobs/RecomputeAlbumSizeJob.php:114` 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.
R11 · Import Boundaries · Boundary violation [package · ×3
  • Boundary violation [package:third-party-deep-import] resources/js/services/sidebar-map.ts:3 — resources/js/services/sidebar-map.ts:3 imports leaflet.markercluster/dist/leaflet.markercluster.js, 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.
  • Boundary violation [package:third-party-deep-import] resources/js/v7/views/gallery-panels/Map.vue:31 — resources/js/v7/views/gallery-panels/Map.vue:31 imports leaflet.markercluster/dist/leaflet.markercluster.js, 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.
  • Boundary violation [package:third-party-deep-import] resources/js/v8/views/gallery-panels/Map.vue:33 — resources/js/v8/views/gallery-panels/Map.vue:33 imports leaflet.markercluster/dist/leaflet.markercluster.js, 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.
X19 · Unrestored process-global state · Process-global state is restored only on the happy path · ×3
  • Process-global state is restored only on the happy path app/Image/Files/FlysystemFile.php:59 — `write` changes state that belongs to the whole PROCESS and changes it back at the end of the same body — the process umask (changed at line 83, put back at line 87) — which says the change was meant to last no longer than this call. But the restore is an ordinary statement on the straight-line path, not a `finally`, so it is skipped by any exception thrown in between: PHP then keeps the overwritten value for the rest of the request — and in a CLI command, a queue worker or a long-running server (Octane, Swoole, RoadRunner, FrankenPHP) for the rest of the process's life — and every later relative path, child-process launch, date, number format, XML parse or error report in ANY class reads it. That failure is silent and remote from its cause: the function that breaks is not the function that moved the value. The durable fix is not to widen the restore but to stop mutating the global: pass the value to the operation that needs it — `cwd` and `env` to Symfony `Process` (`new Process($command, $cwd, $env)`) or `proc_open($command, $spec, $pipes, $cwd, $env)`, absolute paths instead of `chdir`, an explicit `DateTimeZone` or locale to `DateTimeImmutable`/`IntlDateFormatter`/`NumberFormatter`, an explicit encoding to the `mb_*` call, `LIBXML_NOERROR`/`libxml_get_errors` handling in one place. Where the global genuinely must move, wrap it `try`/`finally` so the restore runs on every path.
  • Process-global state is restored only on the happy path app/Actions/Photo/Pipes/VideoPartner/PlaceVideo.php:56 — `handle` changes state that belongs to the whole PROCESS and changes it back at the end of the same body — the process umask (changed at line 84, put back at line 86) — which says the change was meant to last no longer than this call. But the restore is an ordinary statement on the straight-line path, not a `finally`, so it is skipped by any exception thrown in between: PHP then keeps the overwritten value for the rest of the request — and in a CLI command, a queue worker or a long-running server (Octane, Swoole, RoadRunner, FrankenPHP) for the rest of the process's life — and every later relative path, child-process launch, date, number format, XML parse or error report in ANY class reads it. That failure is silent and remote from its cause: the function that breaks is not the function that moved the value. The durable fix is not to widen the restore but to stop mutating the global: pass the value to the operation that needs it — `cwd` and `env` to Symfony `Process` (`new Process($command, $cwd, $env)`) or `proc_open($command, $spec, $pipes, $cwd, $env)`, absolute paths instead of `chdir`, an explicit `DateTimeZone` or locale to `DateTimeImmutable`/`IntlDateFormatter`/`NumberFormatter`, an explicit encoding to the `mb_*` call, `LIBXML_NOERROR`/`libxml_get_errors` handling in one place. Where the global genuinely must move, wrap it `try`/`finally` so the restore runs on every path.
  • Process-global state is restored only on the happy path app/Actions/Photo/Pipes/Standalone/PlacePhoto.php:70 — `putSourceIntoFinalDestination` changes state that belongs to the whole PROCESS and changes it back at the end of the same body — the process umask (changed at line 84, put back at line 86) — which says the change was meant to last no longer than this call. But the restore is an ordinary statement on the straight-line path, not a `finally`, so it is skipped by any exception thrown in between: PHP then keeps the overwritten value for the rest of the request — and in a CLI command, a queue worker or a long-running server (Octane, Swoole, RoadRunner, FrankenPHP) for the rest of the process's life — and every later relative path, child-process launch, date, number format, XML parse or error report in ANY class reads it. That failure is silent and remote from its cause: the function that breaks is not the function that moved the value. The durable fix is not to widen the restore but to stop mutating the global: pass the value to the operation that needs it — `cwd` and `env` to Symfony `Process` (`new Process($command, $cwd, $env)`) or `proc_open($command, $spec, $pipes, $cwd, $env)`, absolute paths instead of `chdir`, an explicit `DateTimeZone` or locale to `DateTimeImmutable`/`IntlDateFormatter`/`NumberFormatter`, an explicit encoding to the `mb_*` call, `LIBXML_NOERROR`/`libxml_get_errors` handling in one place. Where the global genuinely must move, wrap it `try`/`finally` so the restore runs on every path.
AC1 · Text alternatives · <canvas> without a text alternative · ×2
  • <canvas> without a text alternative resources/js/v7/components/webshop/QrCodeLink.vue:2 — A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
  • <canvas> without a text alternative resources/js/v8/components/webshop/QrCodeLink.vue:2 — A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (3.3 · ×2
  • Low contrast Tailwind colour pair (3.3:1) resources/js/v7/components/gallery/photoModule/PhotoRatingWidget.vue:22 — This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
  • Low contrast Tailwind colour pair (3.3:1) resources/js/v8/components/gallery/photoModule/PhotoRatingWidget.vue:22 — This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
D1 · Cyclomatic Complexity · contextMenu.useContextMenu.photoMenu (cyclomatic 17) · ×2
  • contextMenu.useContextMenu.photoMenu (cyclomatic 17) resources/js/composables/contextMenus/contextMenu.ts:103 — contextMenu.useContextMenu.photoMenu has cyclomatic complexity 17 (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.
  • contextMenu.useContextMenu.photoMenu (cyclomatic 17) resources/js/v8/composables/contextMenus/contextMenu.ts:107 — contextMenu.useContextMenu.photoMenu has cyclomatic complexity 17 (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.
D2 · Cognitive Complexity · contextMenu.useContextMenu.photoMenu (cognitive 17) · ×2
  • contextMenu.useContextMenu.photoMenu (cognitive 17) resources/js/composables/contextMenus/contextMenu.ts:103 — contextMenu.useContextMenu.photoMenu has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 7, ternaries 1 (2 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
  • contextMenu.useContextMenu.photoMenu (cognitive 17) resources/js/v8/composables/contextMenus/contextMenu.ts:107 — contextMenu.useContextMenu.photoMenu has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 7, ternaries 1 (2 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · uploadEvents.useMouseEvents.onPaste (cognitive 16) · ×2
  • uploadEvents.useMouseEvents.onPaste (cognitive 16) resources/js/composables/album/uploadEvents.ts:79 — uploadEvents.useMouseEvents.onPaste has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 7). 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.
  • uploadEvents.useMouseEvents.onPaste (cognitive 16) resources/js/v8/composables/album/uploadEvents.ts:71 — uploadEvents.useMouseEvents.onPaste has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 7). 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (5 members, 50+ identical tokens) app/Exceptions/Handlers/AccessDBDenied.php:44 — app/Exceptions/Handlers/AccessDBDenied.php:44-56 | app/Exceptions/Handlers/AdminSetterHandler.php:58-85 | app/Exceptions/Handlers/InstallationHandler.php:58-74 | app/Exceptions/Handlers/MigrationHandler.php:59-71 | app/Exceptions/Handlers/NoEncryptionKey.php:44-56 — These 5 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 5 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 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) app/SmartAlbums/FiveStarsAlbum.php:50 — app/SmartAlbums/FiveStarsAlbum.php:50-64 | app/SmartAlbums/FourStarsAlbum.php:51-65 | app/SmartAlbums/ThreeStarsAlbum.php:51-65 | app/SmartAlbums/TwoStarsAlbum.php:53-67 | app/SmartAlbums/UnratedAlbum.php:50-64 — These 5 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 5 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 5 times.
D4 · Code Duplication · Edited copy of a member (31 corresponding lines) · ×2
  • Edited copy of a member (31 corresponding lines) app/Http/Requests/Album/UpdatePersonAlbumRequest.php:98 — app/Http/Requests/Album/UpdatePersonAlbumRequest.php:98-128 | app/Http/Requests/Album/UpdateTagAlbumRequest.php:98-128 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (31 corresponding lines) app/Policies/PhotoPolicy.php:281 — app/Policies/PhotoPolicy.php:281-323 | app/Policies/PhotoPolicy.php:362-392 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (33 corresponding lines) · ×2
  • Edited copy of a member (33 corresponding lines) app/Http/Requests/ShopManagement/PurchasableAlbumRequest.php:86 — app/Http/Requests/ShopManagement/PurchasableAlbumRequest.php:86-127 | app/Http/Requests/ShopManagement/UpdatePurchasablePriceRequest.php:80-112 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (33 corresponding lines) app/Actions/Diagnostics/Pipes/Checks/AiVisionFaceRecognitionServiceCheck.php:35 — app/Actions/Diagnostics/Pipes/Checks/AiVisionFaceRecognitionServiceCheck.php:35-67 | app/Actions/Diagnostics/Pipes/Checks/AiVisionNsfwServiceCheck.php:33-74 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×2
  • Edited copy of a member (20 corresponding lines) app/DTO/BulkAlbumPatchData.php:106 — app/DTO/BulkAlbumPatchData.php:106-125 | app/Http/Resources/Admin/BulkAlbumResource.php:85-108 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) app/Image/Files/NativeLocalFile.php:79 — app/Image/Files/NativeLocalFile.php:79-101 | app/Image/Files/NativeLocalFile.php:117-136 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×2
  • Edited copy of a member (19 corresponding lines) app/Policies/AlbumPolicy.php:353 — app/Policies/AlbumPolicy.php:353-371 | app/Policies/AlbumPolicy.php:386-410 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) app/DTO/Delete/PhotosToBeDeletedDTO.php:208 — app/DTO/Delete/PhotosToBeDeletedDTO.php:208-230 | app/DTO/Delete/PhotosToBeDeletedDTO.php:242-260 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 15+ corresponding lines) app/Relations/HasManyBidirectionally.php:58 — app/Relations/HasManyBidirectionally.php:58-77 | app/Relations/HasManyChildAlbums.php:122-141 | app/Relations/HasManySizeVariants.php:112-126 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) app/Exceptions/Handlers/AdminSetterHandler.php:36 — app/Exceptions/Handlers/AdminSetterHandler.php:36-50 | app/Exceptions/Handlers/InstallationHandler.php:36-50 | app/Exceptions/Handlers/MigrationHandler.php:37-51 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 4+ corresponding lines) app/Http/Requests/Face/ClusterResultsRequest.php:30 — app/Http/Requests/Face/ClusterResultsRequest.php:30-33 | app/Http/Requests/Face/FaceDetectionResultsRequest.php:35-38 | app/Http/Requests/Nsfw/NsfwDetectionResultsRequest.php:29-32 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 4+ corresponding lines) app/SmartAlbums/FiveStarsAlbum.php:34 — app/SmartAlbums/FiveStarsAlbum.php:34-37 | app/SmartAlbums/FourStarsAlbum.php:35-38 | app/SmartAlbums/ThreeStarsAlbum.php:35-38 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (33 lines × 2) · ×2
  • Duplicated block (33 lines × 2) app/Actions/Album/StructOfArrays/BuildAlbumDataResource.php:128 — app/Actions/Album/StructOfArrays/BuildAlbumDataResource.php:128-160 | app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php:210-242 — before extracting anything, compare `app/Actions/Album/StructOfArrays/BuildAlbumDataResource.php` and `app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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/Actions/Album/StructOfArrays/BuildAlbumDataResource.php:128` 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. 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 (33 lines × 2) app/Console/Commands/RecomputeAlbumSizes.php:101 — app/Console/Commands/RecomputeAlbumSizes.php:101-133 | app/Console/Commands/RecomputeAlbumStats.php:101-133 — before extracting anything, compare `app/Console/Commands/RecomputeAlbumSizes.php` and `app/Console/Commands/RecomputeAlbumStats.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
D4 · Code Duplication · Duplicated block (32 lines × 2) · ×2
  • Duplicated block (32 lines × 2) app/Actions/Album/StructOfArrays/BuildAlbumDataResource.php:49 — app/Actions/Album/StructOfArrays/BuildAlbumDataResource.php:49-80 | app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php:137-168 — before extracting anything, compare `app/Actions/Album/StructOfArrays/BuildAlbumDataResource.php` and `app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (32 lines × 2) app/Repositories/ConfigManager.php:207 — app/Repositories/ConfigManager.php:207-238 | app/Repositories/ConfigManager.php:251-282 — 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. 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 (25 lines × 2) · ×2
  • Duplicated block (25 lines × 2) app/Console/Commands/RecomputeAlbumSizes.php:140 — app/Console/Commands/RecomputeAlbumSizes.php:140-164 | app/Console/Commands/RecomputeAlbumStats.php:141-165 — before extracting anything, compare `app/Console/Commands/RecomputeAlbumSizes.php` and `app/Console/Commands/RecomputeAlbumStats.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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/Console/Commands/RecomputeAlbumSizes.php:140` 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. 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.
  • Duplicated block (25 lines × 2) app/Http/Requests/LandingFeaturedItem/PatchLandingFeaturedItemRequest.php:26 — app/Http/Requests/LandingFeaturedItem/PatchLandingFeaturedItemRequest.php:26-52 | app/Http/Requests/LandingFeaturedItem/UpdateLandingFeaturedItemRequest.php:26-50 — before extracting anything, compare `app/Http/Requests/LandingFeaturedItem/PatchLandingFeaturedItemRequest.php` and `app/Http/Requests/LandingFeaturedItem/UpdateLandingFeaturedItemRequest.php` as WHOLE FILES: 90% 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 1 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/Http/Requests/LandingFeaturedItem/PatchLandingFeaturedItemRequest.php:26` 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.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×2
  • Duplicated block (21 lines × 2) app/Http/Controllers/Gallery/AlbumController.php:194 — app/Http/Controllers/Gallery/AlbumController.php:194-214 | app/Http/Controllers/Gallery/AlbumController.php:231-251 — 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 (21 lines × 2) app/Http/Controllers/Gallery/AlbumTagsController.php:104 — app/Http/Controllers/Gallery/AlbumTagsController.php:104-124 | app/Http/Controllers/Gallery/AlbumTagsController.php:137-157 — 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.
D4 · Code Duplication · Duplicated block (13 lines × 4) · ×2
  • Duplicated block (13 lines × 4) app/Services/Image/FacialRecognitionService.php:117 — app/Services/Image/FacialRecognitionService.php:117-129 | app/Services/Image/FacialRecognitionService.php:149-161 | app/Services/Image/NsfwDetectionService.php:47-59 | app/Services/Image/NsfwDetectionService.php:77-89 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `app/Services/Image/FacialRecognitionService.php:117` 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 × 4) app/SmartAlbums/FiveStarsAlbum.php:50 — app/SmartAlbums/FiveStarsAlbum.php:50-62 | app/SmartAlbums/FourStarsAlbum.php:51-63 | app/SmartAlbums/ThreeStarsAlbum.php:51-63 | app/SmartAlbums/TwoStarsAlbum.php:53-65 — before extracting anything, compare `app/SmartAlbums/FiveStarsAlbum.php` and `app/SmartAlbums/FourStarsAlbum.php` as WHOLE FILES: 84% 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.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×2
  • Duplicated block (12–13 lines × 2) app/Actions/Album/BaseArchive.php:164 — app/Actions/Album/BaseArchive.php:164-175 | app/Actions/Album/BaseArchive.php:450-462 — 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. 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 (12–13 lines × 2) app/Http/Controllers/Install/SetUpAdminController.php:47 — app/Http/Controllers/Install/SetUpAdminController.php:47-58 | app/Http/Controllers/ProfileController.php:62-74 — 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 (13 lines × 2) · ×2
  • Duplicated block (13 lines × 2) app/Actions/Statistics/Spaces.php:260 — app/Actions/Statistics/Spaces.php:260-272 | app/Actions/Statistics/Spaces.php:376-388 — 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) app/Http/Controllers/Admin/Maintenance/PurgeOrphanFaceEmbeddings.php:38 — app/Http/Controllers/Admin/Maintenance/PurgeOrphanFaceEmbeddings.php:38-50 | app/Http/Controllers/Admin/Maintenance/SyncFaceEmbeddings.php:34-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.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×2
  • Duplicated block (12 lines × 3) app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php:193 — app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php:193-204 | app/Actions/Search/StructOfArrays/QuerySearchPhotos.php:206-217 | app/Http/Controllers/Gallery/AlbumAccessPermissionListController.php:105-116 — before extracting anything, compare `app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php` and `app/Actions/Search/StructOfArrays/QuerySearchPhotos.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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/Actions/Photo/StructOfArrays/QueryPhotoRatios.php:193` 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 (12 lines × 3) app/Legacy/BaseConfigMigration.php:37 — app/Legacy/BaseConfigMigration.php:37-48 | app/Models/Extensions/BaseConfigMigration.php:22-33 | app/Models/Extensions/BaseConfigMigrationReversed.php:22-33 — before extracting anything, compare `app/Models/Extensions/BaseConfigMigration.php` and `app/Models/Extensions/BaseConfigMigrationReversed.php` as WHOLE FILES: 83% 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 1 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/Legacy/BaseConfigMigration.php:37` 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.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×2
  • Duplicated block (11 lines × 3) app/Actions/Album/StructOfArrays/BuildAlbumDataResource.php:114 — app/Actions/Album/StructOfArrays/BuildAlbumDataResource.php:114-124 | app/Http/Controllers/Gallery/AlbumListController.php:151-161 | app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php:192-202 — before extracting anything, compare `app/Actions/Album/StructOfArrays/BuildAlbumDataResource.php` and `app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 93 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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/Actions/Album/StructOfArrays/BuildAlbumDataResource.php:114` 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 (11 lines × 3) app/Exceptions/Handlers/AccessDBDenied.php:46 — app/Exceptions/Handlers/AccessDBDenied.php:46-56 | app/Exceptions/Handlers/MigrationHandler.php:61-71 | app/Exceptions/Handlers/NoEncryptionKey.php:46-56 — before extracting anything, compare `app/Exceptions/Handlers/AccessDBDenied.php` and `app/Exceptions/Handlers/NoEncryptionKey.php` as WHOLE FILES: 83% 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/Exceptions/Handlers/AccessDBDenied.php:46` 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. 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.
D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×2
  • Duplicated block (9–10 lines × 2) app/Actions/Statistics/Spaces.php:84 — app/Actions/Statistics/Spaces.php:84-93 | app/Actions/Statistics/Spaces.php:204-212 — 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/Actions/Statistics/Spaces.php:204` 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. 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 (9–10 lines × 2) app/Image/Handlers/GoogleMotionPictureHandler.php:105 — app/Image/Handlers/GoogleMotionPictureHandler.php:105-113 | app/Image/Handlers/VideoHandler.php:59-68 — 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/Image/Handlers/GoogleMotionPictureHandler.php:105` 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. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/Image/Handlers/GoogleMotionPictureHandler.php:113` calls `MediaFileOperationException` and `app/Image/Handlers/VideoHandler.php:68` does not — after which the two agree again for 2 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 (8–10 lines × 2) · ×2
  • Duplicated block (8–10 lines × 2) app/Actions/Statistics/Spaces.php:271 — app/Actions/Statistics/Spaces.php:271-280 | app/Actions/Statistics/Spaces.php:322-329 — 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/Actions/Statistics/Spaces.php:271` 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.
  • Duplicated block (8–10 lines × 2) app/Http/Resources/GalleryConfigs/LandingPageResource.php:191 — app/Http/Resources/GalleryConfigs/LandingPageResource.php:191-198 | app/Http/Resources/GalleryConfigs/LandingPageResource.php:325-334 — 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.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×2
  • Duplicated block (24 lines × 2) app/Http/Requests/Map/GetMapBucketsRequest.php:37 — app/Http/Requests/Map/GetMapBucketsRequest.php:37-60 | app/Http/Requests/Map/GetMapPhotosRequest.php:36-59 — before extracting anything, compare `app/Http/Requests/Map/GetMapBucketsRequest.php` and `app/Http/Requests/Map/GetMapPhotosRequest.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 1 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/Http/Requests/Map/GetMapBucketsRequest.php:37` 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.
  • Duplicated block (24 lines × 2) app/Http/Requests/Moderation/ApproveModerationRequest.php:30 — app/Http/Requests/Moderation/ApproveModerationRequest.php:30-53 | app/Http/Requests/Nsfw/DeleteNsfwFindingsByPhotosRequest.php:30-53 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/Http/Requests/Moderation/ApproveModerationRequest.php:30` 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 with local edits (124 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (124 matched lines × 2 locations) resources/js/v7/components/forms/upload/UploadingLine.vue:57 — resources/js/v7/components/forms/upload/UploadingLine.vue:57 · resources/js/v8/components/forms/upload/UploadingLine.vue:118 — the two spans are one implementation copied and then locally edited — 852 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.
  • Duplicated block with local edits (124 matched lines × 2 locations) resources/js/v7/views/face-recog/FaceClusters.vue:437 — resources/js/v7/views/face-recog/FaceClusters.vue:437 · resources/js/v8/views/face-recog/FaceClusters.vue:607 — the two spans are one implementation copied and then locally edited — 965 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.
R2 · Cyclomatic Complexity · Complex function photoMenu (cyclomatic 35, cognitive 35) · ×2
  • Complex function photoMenu (cyclomatic 35, cognitive 35) resources/js/composables/contextMenus/contextMenu.ts:103 — photoMenu has cyclomatic complexity 35 and cognitive complexity 35; 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.
  • Complex function photoMenu (cyclomatic 35, cognitive 35) resources/js/v8/composables/contextMenus/contextMenu.ts:107 — photoMenu has cyclomatic complexity 35 and cognitive complexity 35; 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 photosMenu (cyclomatic 23, cognitive 22) · ×2
  • Complex function photosMenu (cyclomatic 23, cognitive 22) resources/js/composables/contextMenus/contextMenu.ts:236 — photosMenu has cyclomatic complexity 23 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.
  • Complex function photosMenu (cyclomatic 23, cognitive 22) resources/js/v8/composables/contextMenus/contextMenu.ts:240 — photosMenu has cyclomatic complexity 23 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 albumMenu (cyclomatic 18, cognitive 18) · ×2
  • Complex function albumMenu (cyclomatic 18, cognitive 18) resources/js/composables/contextMenus/contextMenu.ts:328 — albumMenu has cyclomatic complexity 18 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function albumMenu (cyclomatic 18, cognitive 18) resources/js/v8/composables/contextMenus/contextMenu.ts:332 — albumMenu has cyclomatic complexity 18 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 14, cognitive 9) · ×2
  • Complex function (anonymous) (cyclomatic 14, cognitive 9) resources/js/v7/components/gallery/albumModule/thumbs/AlbumThumbOverlay.vue:46 — (anonymous) has cyclomatic complexity 14 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function (anonymous) (cyclomatic 14, cognitive 9) resources/js/v8/components/gallery/albumModule/thumbs/AlbumThumbOverlay.vue:49 — (anonymous) has cyclomatic complexity 14 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
AC6 · Visual & motion safety · Focus outline removed inline · ×1
  • Focus outline removed inline resources/js/v7/components/gallery/albumModule/PhotoThumbPanelControl.vue:27 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.8 · ×1
  • Low contrast colour pair in CSS (3.8:1) simple_error_template.html:14 — `html, body` sets color: #777777 on background-color: #1d1d1d — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×1
  • Focus outline removed in CSS without a :focus replacement resources/js/v7/menus/LeftMenu.vue:200 — `.p-overlaybadge .p-badge` 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.
D1 · Cyclomatic Complexity · Extractor.createFromFile (cyclomatic 67) · ×1
  • Extractor.createFromFile (cyclomatic 67) app/Metadata/Extractor.php:79 — Extractor.createFromFile has cyclomatic complexity 67 (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 · useSpotlightGalleryActions.useSpotlightGalleryActions (cyclomatic 43) · ×1
  • useSpotlightGalleryActions.useSpotlightGalleryActions (cyclomatic 43) resources/js/v8/composables/spotlight/useSpotlightGalleryActions.ts:36 — useSpotlightGalleryActions.useSpotlightGalleryActions has cyclomatic complexity 43 (threshold 15). Most of this is not in the body itself: 1 of the 43 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 75, 49, 63, …). 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 · Configs.sanity (cyclomatic 41) · ×1
  • Configs.sanity (cyclomatic 41) app/Models/Configs.php:98 — Configs.sanity has cyclomatic complexity 41 (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 · ExifLens.handle (cyclomatic 36) · ×1
  • ExifLens.handle (cyclomatic 36) app/Console/Commands/ImageProcessing/ExifLens.php:46 — ExifLens.handle has cyclomatic complexity 36 (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 · QueryPhotoDetails.buildResource (cyclomatic 35) · ×1
  • QueryPhotoDetails.buildResource (cyclomatic 35) app/Actions/Photo/StructOfArrays/QueryPhotoDetails.php:105 — QueryPhotoDetails.buildResource has cyclomatic complexity 35 (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 · Ghostbuster.handle (cyclomatic 31) · ×1
  • Ghostbuster.handle (cyclomatic 31) app/Console/Commands/Ghostbuster.php:65 — Ghostbuster.handle has cyclomatic complexity 31 (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 · BulkEditAlbumsAction.do (cyclomatic 30) · ×1
  • BulkEditAlbumsAction.do (cyclomatic 30) app/Actions/Admin/BulkEditAlbumsAction.php:48 — BulkEditAlbumsAction.do has cyclomatic complexity 30 (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 · config.parseDataAttributes (cyclomatic 28) · ×1
  • config.parseDataAttributes (cyclomatic 28) resources/js/embed/config.ts:131 — config.parseDataAttributes has cyclomatic complexity 28 (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 · config.validateConfig (cyclomatic 27) · ×1
  • config.validateConfig (cyclomatic 27) resources/js/embed/config.ts:30 — config.validateConfig has cyclomatic complexity 27 (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 · sprintf.parse (cyclomatic 26) · ×1
  • sprintf.parse (cyclomatic 26) resources/js/utils/sprintf.ts:100 — sprintf.parse has cyclomatic complexity 26 (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 · IniSettingsCheck.handle (cyclomatic 25) · ×1
  • IniSettingsCheck.handle (cyclomatic 25) app/Actions/Diagnostics/Pipes/Checks/IniSettingsCheck.php:35 — IniSettingsCheck.handle has cyclomatic complexity 25 (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 · SecurityAdvisoriesService.getMatchingAdvisories (cyclomatic 24) · ×1
  • SecurityAdvisoriesService.getMatchingAdvisories (cyclomatic 24) app/Services/SecurityAdvisoriesService.php:42 — SecurityAdvisoriesService.getMatchingAdvisories has cyclomatic complexity 24 (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 · quickNaming.decideKey (cyclomatic 24) · ×1
  • quickNaming.decideKey (cyclomatic 24) resources/js/v8/utils/quickNaming.ts:132 — quickNaming.decideKey has cyclomatic complexity 24 (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 · BasicPermissionCheck.checkDirectoryPermissionsRecursively (cyclomatic 23) · ×1
  • BasicPermissionCheck.checkDirectoryPermissionsRecursively (cyclomatic 23) app/Actions/Diagnostics/Pipes/Checks/BasicPermissionCheck.php:201 — BasicPermissionCheck.checkDirectoryPermissionsRecursively 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 · HydrateMetadata.handle (cyclomatic 23) · ×1
  • HydrateMetadata.handle (cyclomatic 23) app/Actions/Photo/Pipes/Shared/HydrateMetadata.php:34 — HydrateMetadata.handle has cyclomatic complexity 23 (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 · leftMenu.useLeftMenu.items (cyclomatic 23) · ×1
  • leftMenu.useLeftMenu.items (cyclomatic 23) resources/js/composables/contextMenus/leftMenu.ts:66 — leftMenu.useLeftMenu.items has cyclomatic complexity 23 (threshold 15). Of this number, 22 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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 · sprintf.convertNumber (cyclomatic 21) · ×1
  • sprintf.convertNumber (cyclomatic 21) resources/js/utils/sprintf.ts:298 — sprintf.convertNumber has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · QueryPhotoRatios.buildResource (cyclomatic 20) · ×1
  • QueryPhotoRatios.buildResource (cyclomatic 20) app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php:175 — QueryPhotoRatios.buildResource has cyclomatic complexity 20 (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 · QuerySearchPhotos.buildResource (cyclomatic 20) · ×1
  • QuerySearchPhotos.buildResource (cyclomatic 20) app/Actions/Search/StructOfArrays/QuerySearchPhotos.php:187 — QuerySearchPhotos.buildResource has cyclomatic complexity 20 (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 · AlbumConfig.__construct (cyclomatic 20) · ×1
  • AlbumConfig.__construct (cyclomatic 20) app/Http/Resources/GalleryConfigs/AlbumConfig.php:54 — AlbumConfig.__construct has cyclomatic complexity 20 (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 · albumStatistics.useAlbumsStatistics.getStatistics (cyclomatic 20) · ×1
  • albumStatistics.useAlbumsStatistics.getStatistics (cyclomatic 20) resources/js/composables/album/albumStatistics.ts:22 — albumStatistics.useAlbumsStatistics.getStatistics has cyclomatic complexity 20 (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 · dragAndSelect.useDragAndSelect.getAlbumBoxesV3 (cyclomatic 20) · ×1
  • dragAndSelect.useDragAndSelect.getAlbumBoxesV3 (cyclomatic 20) resources/js/composables/album/dragAndSelect.ts:348 — dragAndSelect.useDragAndSelect.getAlbumBoxesV3 has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 352, 408, 423). 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 · useSearchTokenAssembler.parseTokens (cyclomatic 20) · ×1
  • useSearchTokenAssembler.parseTokens (cyclomatic 20) resources/js/composables/useSearchTokenAssembler.ts:149 — useSearchTokenAssembler.parseTokens has cyclomatic complexity 20 (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 · useAdminTiles.useAdminTiles (cyclomatic 20) · ×1
  • useAdminTiles.useAdminTiles (cyclomatic 20) resources/js/v8/composables/useAdminTiles.ts:27 — useAdminTiles.useAdminTiles has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 10 function literals inside it that branch (lines 110, 215, 163, …). 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 · SafeZipExtractor.extract (cyclomatic 19) · ×1
  • SafeZipExtractor.extract (cyclomatic 19) app/Services/Zip/SafeZipExtractor.php:109 — SafeZipExtractor.extract 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 · useSearchTokenAssembler.assembleTokens (cyclomatic 19) · ×1
  • useSearchTokenAssembler.assembleTokens (cyclomatic 19) resources/js/composables/useSearchTokenAssembler.ts:81 — useSearchTokenAssembler.assembleTokens has cyclomatic complexity 19 (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 · BulkAlbumPatchData.fromValidated (cyclomatic 18) · ×1
  • BulkAlbumPatchData.fromValidated (cyclomatic 18) app/DTO/BulkAlbumPatchData.php:137 — BulkAlbumPatchData.fromValidated has cyclomatic complexity 18 (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 · BatchFaceRequest.withValidator (cyclomatic 18) · ×1
  • BatchFaceRequest.withValidator (cyclomatic 18) app/Http/Requests/Face/BatchFaceRequest.php:97 — BatchFaceRequest.withValidator has cyclomatic complexity 18 (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 · InitConfig.__construct (cyclomatic 18) · ×1
  • InitConfig.__construct (cyclomatic 18) app/Http/Resources/GalleryConfigs/InitConfig.php:229 — InitConfig.__construct has cyclomatic complexity 18 (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 · buyMeActions.useBuyMeActions.toggleBuyMe (cyclomatic 17) · ×1
  • buyMeActions.useBuyMeActions.toggleBuyMe (cyclomatic 17) resources/js/composables/album/buyMeActions.ts:30 — buyMeActions.useBuyMeActions.toggleBuyMe has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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 · ExtractMotionPhotos.handle (cyclomatic 16) · ×1
  • ExtractMotionPhotos.handle (cyclomatic 16) app/Console/Commands/ImageProcessing/ExtractMotionPhotos.php:64 — ExtractMotionPhotos.handle 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.
D1 · Cyclomatic Complexity · Order.canProcessPayment (cyclomatic 16) · ×1
  • Order.canProcessPayment (cyclomatic 16) app/Models/Order.php:303 — Order.canProcessPayment has cyclomatic complexity 16 (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.
D2 · Cognitive Complexity · Extractor.createFromFile (cognitive 84) · ×1
  • Extractor.createFromFile (cognitive 84) app/Metadata/Extractor.php:79 — Extractor.createFromFile has cognitive complexity 84 (threshold 15). Drivers by points: if/else 25 (36 pts), ternaries 23 (28 pts), boolean chains 12, error handling 4 (7 pts), match/switch 1 (nesting depth added 19). 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 · Ghostbuster.handle (cognitive 56) · ×1
  • Ghostbuster.handle (cognitive 56) app/Console/Commands/Ghostbuster.php:65 — Ghostbuster.handle has cognitive complexity 56 (threshold 15). Drivers by points: if/else 20 (34 pts), loops 4 (11 pts), boolean chains 5, ternaries 3 (5 pts), error handling 1 (nesting depth added 23). 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 · ExifLens.handle (cognitive 46) · ×1
  • ExifLens.handle (cognitive 46) app/Console/Commands/ImageProcessing/ExifLens.php:46 — ExifLens.handle has cognitive complexity 46 (threshold 15). Drivers by points: boolean chains 21, if/else 11 (20 pts), error handling 3 (4 pts), loops 1 (nesting depth added 10). 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 · Configs.sanity (cognitive 46) · ×1
  • Configs.sanity (cognitive 46) app/Models/Configs.php:98 — Configs.sanity has cognitive complexity 46 (threshold 15). Drivers by points: if/else 15 (30 pts), boolean chains 7, error handling 3 (6 pts), loops 1 (2 pts), match/switch 1 (nesting depth added 19). 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 · sprintf.parse (cognitive 45) · ×1
  • sprintf.parse (cognitive 45) resources/js/utils/sprintf.ts:100 — sprintf.parse has cognitive complexity 45 (threshold 15). Drivers by points: if/else 15 (29 pts), loops 4 (9 pts), boolean chains 5, ternaries 1 (2 pts) (nesting depth added 20). 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 · BulkEditAlbumsAction.do (cognitive 43) · ×1
  • BulkEditAlbumsAction.do (cognitive 43) app/Actions/Admin/BulkEditAlbumsAction.php:48 — BulkEditAlbumsAction.do has cognitive complexity 43 (threshold 15). Drivers by points: ternaries 7 (20 pts), if/else 17, boolean chains 4, loops 1 (2 pts) (nesting depth added 14). 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 · QueryPhotoDetails.buildResource (cognitive 40) · ×1
  • QueryPhotoDetails.buildResource (cognitive 40) app/Actions/Photo/StructOfArrays/QueryPhotoDetails.php:105 — QueryPhotoDetails.buildResource has cognitive complexity 40 (threshold 15). Drivers by points: ternaries 17 (22 pts), boolean chains 9, if/else 3 (6 pts), match/switch 1 (2 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 · SecurityAdvisoriesService.getMatchingAdvisories (cognitive 40) · ×1
  • SecurityAdvisoriesService.getMatchingAdvisories (cognitive 40) app/Services/SecurityAdvisoriesService.php:42 — SecurityAdvisoriesService.getMatchingAdvisories has cognitive complexity 40 (threshold 15). Drivers by points: if/else 15 (28 pts), boolean chains 4, ternaries 1 (4 pts), loops 2 (3 pts), error handling 1 (nesting depth added 17). 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 · QueryPhotoRatios.buildResource (cognitive 34) · ×1
  • QueryPhotoRatios.buildResource (cognitive 34) app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php:175 — QueryPhotoRatios.buildResource has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 9 (19 pts), if/else 4 (9 pts), boolean chains 5, loops 1 (nesting depth added 15). 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 · QuerySearchPhotos.buildResource (cognitive 34) · ×1
  • QuerySearchPhotos.buildResource (cognitive 34) app/Actions/Search/StructOfArrays/QuerySearchPhotos.php:187 — QuerySearchPhotos.buildResource has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 9 (19 pts), if/else 4 (9 pts), boolean chains 5, loops 1 (nesting depth added 15). 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 · config.parseDataAttributes (cognitive 34) · ×1
  • config.parseDataAttributes (cognitive 34) resources/js/embed/config.ts:131 — config.parseDataAttributes has cognitive complexity 34 (threshold 15). Drivers by points: if/else 24 (30 pts), boolean chains 4 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · SafeZipExtractor.extract (cognitive 33) · ×1
  • SafeZipExtractor.extract (cognitive 33) app/Services/Zip/SafeZipExtractor.php:109 — SafeZipExtractor.extract has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (25 pts), error handling 2 (4 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 15). 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 · useSpotlightGalleryActions.useSpotlightGalleryActions (cognitive 30) · ×1
  • useSpotlightGalleryActions.useSpotlightGalleryActions (cognitive 30) resources/js/v8/composables/spotlight/useSpotlightGalleryActions.ts:36 — useSpotlightGalleryActions.useSpotlightGalleryActions has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 17, if/else 13. None of this is in the body itself: all 30 points belong to 4 function literals inside it that branch (lines 75, 49, 63, …). 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.
D2 · Cognitive Complexity · BasicPermissionCheck.checkDirectoryPermissionsRecursively (cognitive 28) · ×1
  • BasicPermissionCheck.checkDirectoryPermissionsRecursively (cognitive 28) app/Actions/Diagnostics/Pipes/Checks/BasicPermissionCheck.php:201 — BasicPermissionCheck.checkDirectoryPermissionsRecursively has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (15 pts), error handling 4 (5 pts), boolean chains 3, match/switch 1 (3 pts), loops 1, ternaries 1 (nesting depth added 7). 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 · IniSettingsCheck.handle (cognitive 27) · ×1
  • IniSettingsCheck.handle (cognitive 27) app/Actions/Diagnostics/Pipes/Checks/IniSettingsCheck.php:35 — IniSettingsCheck.handle has cognitive complexity 27 (threshold 15). Drivers by points: if/else 18 (19 pts), boolean chains 5, ternaries 1 (2 pts), error handling 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · config.validateConfig (cognitive 27) · ×1
  • config.validateConfig (cognitive 27) resources/js/embed/config.ts:30 — config.validateConfig has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 11, if/else 10, ternaries 5 (6 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. 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.
D2 · Cognitive Complexity · quickNaming.decideKey (cognitive 27) · ×1
  • quickNaming.decideKey (cognitive 27) resources/js/v8/utils/quickNaming.ts:132 — quickNaming.decideKey has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 7 (15 pts), if/else 4 (7 pts), boolean chains 4, match/switch 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 · analyticPhotoLayout.computeTimelinePhotoLayout (cognitive 26) · ×1
  • analyticPhotoLayout.computeTimelinePhotoLayout (cognitive 26) resources/js/v8/composables/photo/analyticPhotoLayout.ts:307 — analyticPhotoLayout.computeTimelinePhotoLayout has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 3 (8 pts), ternaries 2 (3 pts), boolean chains 1 (nesting depth added 14). 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 · FileDeleterJob.handle (cognitive 25) · ×1
  • FileDeleterJob.handle (cognitive 25) app/Jobs/FileDeleterJob.php:53 — FileDeleterJob.handle has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (14 pts), error handling 2 (6 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 13). 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 · PhotosAddedNotification.handle (cognitive 24) · ×1
  • PhotosAddedNotification.handle (cognitive 24) app/Console/Commands/PhotosAddedNotification.php:48 — PhotosAddedNotification.handle has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 2 (3 pts), error handling 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 · HydrateMetadata.handle (cognitive 23) · ×1
  • HydrateMetadata.handle (cognitive 23) app/Actions/Photo/Pipes/Shared/HydrateMetadata.php:34 — HydrateMetadata.handle has cognitive complexity 23 (threshold 15). Drivers by points: if/else 21, ternaries 1 (2 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. 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.
D2 · Cognitive Complexity · Takedate.handle (cognitive 23) · ×1
  • Takedate.handle (cognitive 23) app/Console/Commands/ImageProcessing/Takedate.php:148 — Takedate.handle has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 2, error handling 2, loops 1, ternaries 1 (nesting depth added 6). 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 · VideoData.handle (cognitive 22) · ×1
  • VideoData.handle (cognitive 22) app/Console/Commands/ImageProcessing/VideoData.php:49 — VideoData.handle has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 2, error handling 2, loops 1 (nesting depth added 8). 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 · FaceDetectionController.processFaceResults (cognitive 22) · ×1
  • FaceDetectionController.processFaceResults (cognitive 22) app/Http/Controllers/AiVision/FaceDetectionController.php:197 — FaceDetectionController.processFaceResults has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 5 (7 pts), error handling 1 (3 pts), boolean chains 1 (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 · leftMenu.useLeftMenu.items (cognitive 22) · ×1
  • leftMenu.useLeftMenu.items (cognitive 22) resources/js/composables/contextMenus/leftMenu.ts:66 — leftMenu.useLeftMenu.items has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 19, if/else 2, ternaries 1. Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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 · useSearchTokenAssembler.parseTokens (cognitive 21) · ×1
  • useSearchTokenAssembler.parseTokens (cognitive 21) resources/js/composables/useSearchTokenAssembler.ts:149 — useSearchTokenAssembler.parseTokens has cognitive complexity 21 (threshold 15). Drivers by points: if/else 19 (20 pts), loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. 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.
D2 · Cognitive Complexity · PlaceVideo.handle (cognitive 20) · ×1
  • PlaceVideo.handle (cognitive 20) app/Actions/Photo/Pipes/VideoPartner/PlaceVideo.php:56 — PlaceVideo.handle has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (15 pts), error handling 2 (5 pts) (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 · AlbumConfig.__construct (cognitive 20) · ×1
  • AlbumConfig.__construct (cognitive 20) app/Http/Resources/GalleryConfigs/AlbumConfig.php:54 — AlbumConfig.__construct has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 14, if/else 4, ternaries 2. 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 · dragAndSelect.useDragAndSelect.getAlbumBoxesV3 (cognitive 20) · ×1
  • dragAndSelect.useDragAndSelect.getAlbumBoxesV3 (cognitive 20) resources/js/composables/album/dragAndSelect.ts:348 — dragAndSelect.useDragAndSelect.getAlbumBoxesV3 has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 8 (11 pts), boolean chains 7, if/else 2 (nesting depth added 3). None of this is in the body itself: all 20 points belong to 3 function literals inside it that branch (lines 352, 408, 423). 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.
D2 · Cognitive Complexity · BaseArchive.gatherFilenames (cognitive 19) · ×1
  • BaseArchive.gatherFilenames (cognitive 19) app/Actions/Album/BaseArchive.php:448 — BaseArchive.gatherFilenames has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (9 pts), error handling 1 (3 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 7). 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 · FixPermissions.fixPermissionsRecursively (cognitive 19) · ×1
  • FixPermissions.fixPermissionsRecursively (cognitive 19) app/Console/Commands/FixPermissions.php:95 — FixPermissions.fixPermissionsRecursively has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 2, error handling 2, loops 1 (2 pts), match/switch 1 (nesting depth added 6). 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 · Sync.executeImport (cognitive 19) · ×1
  • Sync.executeImport (cognitive 19) app/Console/Commands/Sync.php:291 — Sync.executeImport has cognitive complexity 19 (threshold 15). Drivers by points: error handling 2 (6 pts), if/else 6, boolean chains 5, loops 1 (2 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.
D2 · Cognitive Complexity · AlbumAccessPermissionListController.buildResource (cognitive 19) · ×1
  • AlbumAccessPermissionListController.buildResource (cognitive 19) app/Http/Controllers/Gallery/AlbumAccessPermissionListController.php:96 — AlbumAccessPermissionListController.buildResource has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 9 (18 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 · BatchFaceRequest.withValidator (cognitive 18) · ×1
  • BatchFaceRequest.withValidator (cognitive 18) app/Http/Requests/Face/BatchFaceRequest.php:97 — BatchFaceRequest.withValidator has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 11, if/else 6 (7 pts) (nesting depth added 1). 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 · albumStatistics.useAlbumsStatistics.getStatistics (cognitive 18) · ×1
  • albumStatistics.useAlbumsStatistics.getStatistics (cognitive 18) resources/js/composables/album/albumStatistics.ts:22 — albumStatistics.useAlbumsStatistics.getStatistics has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 1, loops 1 (nesting depth added 8). 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 · useSearchTokenAssembler.assembleTokens (cognitive 18) · ×1
  • useSearchTokenAssembler.assembleTokens (cognitive 18) resources/js/composables/useSearchTokenAssembler.ts:81 — useSearchTokenAssembler.assembleTokens has cognitive complexity 18 (threshold 15). Drivers by points: if/else 16, boolean chains 1, loops 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. 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.
D2 · Cognitive Complexity · photoView.imageViewModeOf (cognitive 18) · ×1
  • photoView.imageViewModeOf (cognitive 18) resources/js/utils/photoView.ts:34 — photoView.imageViewModeOf has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 4 (8 pts) (nesting depth added 7). 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 · PlacePhoto.putSourceIntoFinalDestination (cognitive 17) · ×1
  • PlacePhoto.putSourceIntoFinalDestination (cognitive 17) app/Actions/Photo/Pipes/Standalone/PlacePhoto.php:70 — PlacePhoto.putSourceIntoFinalDestination has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 2 (4 pts), boolean chains 2 (nesting depth added 6). 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 · BulkAlbumPatchData.fromValidated (cognitive 17) · ×1
  • BulkAlbumPatchData.fromValidated (cognitive 17) app/DTO/BulkAlbumPatchData.php:137 — BulkAlbumPatchData.fromValidated has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 16, boolean chains 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. 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.
D2 · Cognitive Complexity · InitConfig.__construct (cognitive 17) · ×1
  • InitConfig.__construct (cognitive 17) app/Http/Resources/GalleryConfigs/InitConfig.php:229 — InitConfig.__construct has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 15, if/else 1, ternaries 1. 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 · RequirementsChecker.check (cognitive 16) · ×1
  • RequirementsChecker.check (cognitive 16) app/Actions/InstallUpdate/RequirementsChecker.php:28 — RequirementsChecker.check has cognitive complexity 16 (threshold 15). Drivers by points: loops 3 (7 pts), if/else 3 (6 pts), boolean chains 3 (nesting depth added 7). 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 · ExtractMotionPhotos.handle (cognitive 16) · ×1
  • ExtractMotionPhotos.handle (cognitive 16) app/Console/Commands/ImageProcessing/ExtractMotionPhotos.php:64 — ExtractMotionPhotos.handle has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (6 pts), boolean chains 4, ternaries 2 (3 pts), error handling 1, loops 1, match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · ExtractZip.validate_zip (cognitive 16) · ×1
  • ExtractZip.validate_zip (cognitive 16) app/Jobs/ExtractZip.php:232 — ExtractZip.validate_zip has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), error handling 1 (2 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 8). 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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D35 · Change Coupling · Change coupling clique · ×1
  • Change coupling clique: maintenance.php, maintenance.php, maintenance.php, maintenance.php, maintenance.php, maintenance.php lang/de/maintenance.php — 6 files — `lang/de/maintenance.php`, `lang/en/maintenance.php`, `lang/es/maintenance.php`, `lang/fr/maintenance.php`, `lang/no/maintenance.php`, `lang/zh_TW/maintenance.php` — all change together with no explicit dependency: a fully-connected co-change clique, not 15 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 · Edited copy of a member (24 corresponding lines) · ×1
  • Edited copy of a member (24 corresponding lines) app/Services/TitleSplitter.php:56 — app/Services/TitleSplitter.php:56-79 | database/migrations/TemporaryModels/TitleSplitter.php:50-73 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (7 members, 50+ identical tokens) app/Actions/Face/QueryFaceQueue.php:123 — app/Actions/Face/QueryFaceQueue.php:123-164 | app/Actions/Photo/StructOfArrays/QueryPhotoDetails.php:107-256 | app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php:184-263 | app/Actions/Search/StructOfArrays/QuerySearchPhotos.php:197-282 | app/Http/Controllers/Gallery/AlbumAccessPermissionListController.php:98-156 | app/Http/Controllers/Gallery/AlbumListController.php:222-295 | app/Http/Controllers/Gallery/FlowListController.php:88-155 — These 7 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 7 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 7 times.
D4 · Code Duplication · Edited copy of a member (58 corresponding lines) · ×1
  • Edited copy of a member (58 corresponding lines) app/Actions/Album/StructOfArrays/BuildAlbumDataResource.php:103 — app/Actions/Album/StructOfArrays/BuildAlbumDataResource.php:103-160 | app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php:181-242 — These two members are one piece of code written twice and then edited apart: 58 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (64 corresponding lines) · ×1
  • Edited copy of a member (64 corresponding lines) app/Console/Commands/RecomputeAlbumSizes.php:101 — app/Console/Commands/RecomputeAlbumSizes.php:101-164 | app/Console/Commands/RecomputeAlbumStats.php:101-165 — These two members are one piece of code written twice and then edited apart: 64 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (47 corresponding lines) · ×1
  • Edited copy of a member (47 corresponding lines) app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php:382 — app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php:382-437 | app/Http/Controllers/Gallery/AlbumListing/AlbumTagController.php:87-133 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (42 corresponding lines) · ×1
  • Edited copy of a member (42 corresponding lines) app/Actions/Statistics/Spaces.php:320 — app/Actions/Statistics/Spaces.php:320-361 | app/Actions/Statistics/Spaces.php:442-496 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) app/Http/Controllers/Gallery/AlbumController.php:194 — app/Http/Controllers/Gallery/AlbumController.php:194-223 | app/Http/Controllers/Gallery/AlbumController.php:231-258 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (39 corresponding lines) · ×1
  • Edited copy of a member (39 corresponding lines) app/Jobs/DispatchFaceScanJob.php:44 — app/Jobs/DispatchFaceScanJob.php:44-82 | app/Jobs/DispatchNsfwScanJob.php:38-79 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (45 corresponding lines) · ×1
  • Edited copy of a member (45 corresponding lines) app/Actions/Statistics/Spaces.php:260 — app/Actions/Statistics/Spaces.php:260-304 | app/Actions/Statistics/Spaces.php:376-426 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×1
  • Edited copy of a member (27 corresponding lines) app/Actions/Renamer/PreviewAlbums.php:38 — app/Actions/Renamer/PreviewAlbums.php:38-64 | app/Actions/Renamer/PreviewPhotos.php:39-72 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (30 corresponding lines) · ×1
  • Edited copy of a member (30 corresponding lines) app/Repositories/AlbumRepository.php:122 — app/Repositories/AlbumRepository.php:122-151 | app/Repositories/AlbumRepository.php:222-258 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (35 corresponding lines) · ×1
  • Edited copy of a member (35 corresponding lines) app/Console/Commands/ImageProcessing/MoveToS3.php:48 — app/Console/Commands/ImageProcessing/MoveToS3.php:48-83 | app/Console/Commands/ImageProcessing/TrackS3Migrate.php:51-85 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (38 corresponding lines) · ×1
  • Edited copy of a member (38 corresponding lines) app/Console/Commands/RecomputeAlbumSizes.php:56 — app/Console/Commands/RecomputeAlbumSizes.php:56-93 | app/Console/Commands/RecomputeAlbumStats.php:56-93 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×1
  • Edited copy of a member (17 corresponding lines) app/Http/Requests/Search/GetSearchRequest.php:75 — app/Http/Requests/Search/GetSearchRequest.php:75-91 | app/Http/Requests/Search/GetSearchV3Request.php:110-126 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 21+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 21+ corresponding lines) app/Http/Controllers/Gallery/AlbumListing/AlbumChildrenController.php:121 — app/Http/Controllers/Gallery/AlbumListing/AlbumChildrenController.php:121-149 | app/Http/Controllers/Gallery/AlbumListing/PhotoChildrenController.php:52-72 | app/Http/Controllers/Gallery/MapListingController.php:52-75 | app/Http/Controllers/Gallery/MapListingController.php:82-104 | app/Http/Controllers/Gallery/MapListingController.php:139-160 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 16+ corresponding lines) app/Http/Controllers/Gallery/AlbumListController.php:43 — app/Http/Controllers/Gallery/AlbumListController.php:43-58 | app/Http/Controllers/Gallery/AlbumListing/AlbumPinnedController.php:49-69 | app/Http/Controllers/Gallery/AlbumListing/AlbumTagController.php:48-66 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (29 corresponding lines) · ×1
  • Edited copy of a member (29 corresponding lines) app/Image/ColourExtractor/ImageFactoryForColourExtraction.php:53 — app/Image/ColourExtractor/ImageFactoryForColourExtraction.php:53-81 | app/Image/ColourExtractor/ImageFactoryForColourExtraction.php:95-125 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 19+ corresponding lines) app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php:98 — app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php:98-117 | app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php:249-269 | app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php:351-369 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 14+ corresponding lines) app/Http/Middleware/AdminUserStatus.php:53 — app/Http/Middleware/AdminUserStatus.php:53-66 | app/Http/Middleware/InstallationStatus.php:53-66 | app/Http/Middleware/MigrationStatus.php:55-68 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 6+ corresponding lines) app/Http/Resources/Collections/PaginatedModerationResource.php:36 — app/Http/Resources/Collections/PaginatedModerationResource.php:36-41 | app/Http/Resources/Collections/PaginatedPersonsResource.php:35-41 | app/Http/Resources/Collections/PaginatedWebhookResource.php:36-41 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 12+ corresponding lines) app/Http/Controllers/Gallery/SearchListingController.php:53 — app/Http/Controllers/Gallery/SearchListingController.php:53-65 | app/Http/Controllers/Gallery/SearchListingController.php:72-85 | app/Http/Controllers/Gallery/SearchListingController.php:92-104 | app/Http/Controllers/Gallery/SearchListingController.php:111-122 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×1
  • Edited copy of a member (21 corresponding lines) app/Policies/AlbumPolicy.php:501 — app/Policies/AlbumPolicy.php:501-521 | app/Policies/AlbumPolicy.php:750-770 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 13+ corresponding lines) app/Listeners/ManagedCacheAlbumListingInvalidator.php:208 — app/Listeners/ManagedCacheAlbumListingInvalidator.php:208-222 | app/Listeners/ManagedCachePhotoListingInvalidator.php:59-73 | app/Listeners/ManagedCachePhotoListingInvalidator.php:206-220 | app/Listeners/ManagedCachePhotoListingInvalidator.php:230-242 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 26+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 26+ corresponding lines) app/Actions/Shop/OrderService.php:153 — app/Actions/Shop/OrderService.php:153-178 | app/Actions/Shop/OrderService.php:202-237 | app/Actions/Shop/OrderService.php:262-293 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 5+ corresponding lines) app/Http/Requests/Basket/AddPhotoToBasketRequest.php:87 — app/Http/Requests/Basket/AddPhotoToBasketRequest.php:87-92 | app/Http/Requests/Basket/AddPixelItemRequest.php:62-67 | app/Http/Requests/Basket/AddPrintItemRequest.php:58-62 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 5+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 5+ corresponding lines) app/Http/Resources/Admin/PaginatedBulkAlbumResource.php:37 — app/Http/Resources/Admin/PaginatedBulkAlbumResource.php:37-41 | app/Http/Resources/Collections/PaginatedClustersResource.php:35-39 | app/Http/Resources/Collections/PaginatedFaceResource.php:35-39 | app/Http/Resources/Collections/PaginatedModerationHistoryResource.php:39-43 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 10+ corresponding lines) app/Policies/AlbumPolicy.php:949 — app/Policies/AlbumPolicy.php:949-958 | app/Policies/AlbumPolicy.php:995-1004 | app/Policies/PhotoPolicy.php:514-523 | app/Policies/PhotoPolicy.php:552-561 | app/Policies/PhotoPolicy.php:575-584 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 8+ corresponding lines) app/Policies/PhotoPolicy.php:99 — app/Policies/PhotoPolicy.php:99-107 | app/Policies/PhotoPolicy.php:127-135 | app/Policies/PhotoPolicy.php:151-158 | app/Policies/PhotoPolicy.php:338-346 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (2 corresponding lines) · ×1
  • Edited copy of a member (2 corresponding lines) app/Http/Requests/Album/SetPinnedRequest.php:51 — app/Http/Requests/Album/SetPinnedRequest.php:51-52 | app/Http/Requests/Sharing/PropagateSharingRequest.php:55-56 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 1+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 1+ corresponding lines) app/Http/Requests/Basket/AddPhotoToBasketRequest.php:57 — app/Http/Requests/Basket/AddPhotoToBasketRequest.php:57-57 | app/Http/Requests/Basket/AddPixelItemRequest.php:32-32 | app/Http/Requests/Basket/AddPrintItemRequest.php:29-29 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (41 lines × 3) · ×1
  • Duplicated block (41 lines × 3) app/Actions/Tag/MergeTag.php:71 — app/Actions/Tag/MergeTag.php:71-111 | app/Actions/Tag/MergeTag.php:117-157 | app/Actions/Tag/MergeTag.php:169-209 — 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.
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×1
  • Duplicated block (29 lines × 2) app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php:213 — app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php:213-241 | app/Actions/Search/StructOfArrays/QuerySearchPhotos.php:231-259 — before extracting anything, compare `app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php` and `app/Actions/Search/StructOfArrays/QuerySearchPhotos.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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/Actions/Photo/StructOfArrays/QueryPhotoRatios.php:213` 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/Actions/Photo/StructOfArrays/QueryPhotoRatios.php:212` calls `normalizeId` and `app/Actions/Search/StructOfArrays/QuerySearchPhotos.php:230` does not — after which the two agree again for 2 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 (20–29 lines × 2) · ×1
  • Duplicated block (20–29 lines × 2) app/Policies/AlbumQueryPolicy.php:367 — app/Policies/AlbumQueryPolicy.php:367-395 | app/Policies/AlbumQueryPolicy.php:459-478 — 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/Policies/AlbumQueryPolicy.php:367` 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. 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.
D4 · Code Duplication · Duplicated block (24–27 lines × 2) · ×1
  • Duplicated block (24–27 lines × 2) app/Policies/PhotoPolicy.php:293 — app/Policies/PhotoPolicy.php:293-319 | app/Policies/PhotoPolicy.php:364-387 — 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.
D4 · Code Duplication · Duplicated block (24–26 lines × 2) · ×1
  • Duplicated block (24–26 lines × 2) app/Actions/Photo/BaseArchive.php:226 — app/Actions/Photo/BaseArchive.php:226-249 | app/Actions/Photo/BaseArchive.php:427-452 — 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/Actions/Photo/BaseArchive.php:226` 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.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×1
  • Duplicated block (26 lines × 2) app/Rules/ExtensionRule.php:45 — app/Rules/ExtensionRule.php:45-70 | app/Rules/FileUuidRule.php:47-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. 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.
D4 · Code Duplication · Duplicated block (23–25 lines × 2) · ×1
  • Duplicated block (23–25 lines × 2) app/Actions/Album/BaseArchive.php:214 — app/Actions/Album/BaseArchive.php:214-238 | app/Actions/Album/BaseArchive.php:470-492 — 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.
D4 · Code Duplication · Duplicated block (23 lines × 3) · ×1
  • Duplicated block (23 lines × 3) app/Http/Requests/ShopManagement/PurchasableAlbumRequest.php:103 — app/Http/Requests/ShopManagement/PurchasableAlbumRequest.php:103-125 | app/Http/Requests/ShopManagement/PurchasablePhotoRequest.php:113-135 | app/Http/Requests/ShopManagement/UpdatePurchasablePriceRequest.php:90-112 — before extracting anything, compare `app/Http/Requests/ShopManagement/PurchasableAlbumRequest.php` and `app/Http/Requests/ShopManagement/UpdatePurchasablePriceRequest.php` as WHOLE FILES: 89% 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/Http/Requests/ShopManagement/PurchasableAlbumRequest.php:103` 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 after the matched lines, `app/Http/Requests/ShopManagement/PurchasableAlbumRequest.php:127` calls `toBoolean` and `app/Http/Requests/ShopManagement/PurchasablePhotoRequest.php:136` does not — after which the two agree again for 2 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 (22 lines × 3) · ×1
  • Duplicated block (22 lines × 3) app/Actions/Album/StructOfArrays/Traits/GrantsAlbumRights.php:79 — app/Actions/Album/StructOfArrays/Traits/GrantsAlbumRights.php:79-100 | app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php:404-425 | app/Http/Controllers/Gallery/AlbumListing/AlbumTagController.php:108-129 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/Actions/Album/StructOfArrays/Traits/GrantsAlbumRights.php:79` 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 (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) app/Actions/Diagnostics/Pipes/Checks/AiVisionFaceRecognitionServiceCheck.php:46 — app/Actions/Diagnostics/Pipes/Checks/AiVisionFaceRecognitionServiceCheck.php:46-67 | app/Actions/Diagnostics/Pipes/Checks/AiVisionNsfwServiceCheck.php:53-74 — 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/Actions/Diagnostics/Pipes/Checks/AiVisionFaceRecognitionServiceCheck.php:46` 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. 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 (4–20 lines × 3) · ×1
  • Duplicated block (4–20 lines × 3) app/Http/Requests/Album/UpdateAlbumRequest.php:235 — app/Http/Requests/Album/UpdateAlbumRequest.php:235-238 | app/Http/Requests/Album/UpdatePersonAlbumRequest.php:103-122 | app/Http/Requests/Album/UpdateTagAlbumRequest.php:103-122 — before extracting anything, compare `app/Http/Requests/Album/UpdatePersonAlbumRequest.php` and `app/Http/Requests/Album/UpdateTagAlbumRequest.php` as WHOLE FILES: 82% 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 1 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/Http/Requests/Album/UpdatePersonAlbumRequest.php:103` 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. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/Http/Requests/Album/UpdatePersonAlbumRequest.php:122` calls `array_key_exists` and `app/Http/Requests/Album/UpdateAlbumRequest.php:238` does not — after which the two agree again for 2 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 (15–19 lines × 2) · ×1
  • Duplicated block (15–19 lines × 2) app/SmartAlbums/BestPicturesAlbum.php:62 — app/SmartAlbums/BestPicturesAlbum.php:62-76 | app/SmartAlbums/MyBestPicturesAlbum.php:61-79 — 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. 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.
D4 · Code Duplication · Duplicated block (16–17 lines × 2) · ×1
  • Duplicated block (16–17 lines × 2) app/Http/Controllers/Admin/Maintenance/DestroyDismissedFaces.php:47 — app/Http/Controllers/Admin/Maintenance/DestroyDismissedFaces.php:47-62 | app/Http/Controllers/AiVision/FaceController.php:184-200 — 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 (11–15 lines × 4) · ×1
  • Duplicated block (11–15 lines × 4) app/Actions/Album/BaseArchive.php:275 — app/Actions/Album/BaseArchive.php:275-289 | app/Actions/Album/BaseArchive.php:342-353 | app/Actions/Photo/BaseArchive.php:251-261 | app/Actions/Photo/BaseArchive.php:453-465 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `app/Actions/Album/BaseArchive.php:275` 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. 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 (15 lines × 4) · ×1
  • Duplicated block (15 lines × 4) app/Rules/BooleanRequireSupportRule.php:34 — app/Rules/BooleanRequireSupportRule.php:34-48 | app/Rules/EnumRequireSupportRule.php:54-68 | app/Rules/IntegerRequireSupportRule.php:34-48 | app/Rules/StringRequireSupportRule.php:36-50 — before extracting anything, compare `app/Rules/BooleanRequireSupportRule.php` and `app/Rules/EnumRequireSupportRule.php` as WHOLE FILES: 85% 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 1 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/Rules/BooleanRequireSupportRule.php:34` 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.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×1
  • Duplicated block (13–14 lines × 2) app/Actions/Photo/Timeline.php:47 — app/Actions/Photo/Timeline.php:47-59 | app/Actions/Photo/Timeline.php:121-134 — 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/Actions/Photo/Timeline.php:47` 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. 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. 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.
D4 · Code Duplication · Duplicated block (11–14 lines × 2) · ×1
  • Duplicated block (11–14 lines × 2) app/Models/PersonAlbum.php:133 — app/Models/PersonAlbum.php:133-143 | app/Models/TagAlbum.php:187-200 — 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 before the matched lines, `app/Models/TagAlbum.php:184` calls `createFromPhoto` and `app/Models/PersonAlbum.php:132` does not — after which the two agree again for 2 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 × 7) · ×1
  • Duplicated block (11 lines × 7) app/Actions/Face/QueryFaceQueue.php:127 — app/Actions/Face/QueryFaceQueue.php:127-137 | app/Actions/Photo/StructOfArrays/QueryPhotoDetails.php:144-155 | app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php:193-204 | app/Actions/Search/StructOfArrays/QuerySearchPhotos.php:206-217 | app/Http/Controllers/Gallery/AlbumAccessPermissionListController.php:105-116 | app/Http/Controllers/Gallery/AlbumListController.php:234-245 | app/Http/Controllers/Gallery/FlowListController.php:100-111 — before extracting anything, compare `app/Actions/Photo/StructOfArrays/QueryPhotoRatios.php` and `app/Actions/Search/StructOfArrays/QuerySearchPhotos.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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/Actions/Face/QueryFaceQueue.php:127` 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 (9–11 lines × 2) · ×1
  • Duplicated block (9–11 lines × 2) app/Actions/Statistics/Spaces.php:387 — app/Actions/Statistics/Spaces.php:387-397 | app/Actions/Statistics/Spaces.php:444-452 — 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/Actions/Statistics/Spaces.php:387` 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.
D4 · Code Duplication · Duplicated block (8–9 lines × 5) · ×1
  • Duplicated block (8–9 lines × 5) app/Exceptions/Handlers/AccessDBDenied.php:46 — app/Exceptions/Handlers/AccessDBDenied.php:46-53 | app/Exceptions/Handlers/AdminSetterHandler.php:61-69 | app/Exceptions/Handlers/InstallationHandler.php:61-69 | app/Exceptions/Handlers/MigrationHandler.php:61-68 | app/Exceptions/Handlers/NoEncryptionKey.php:46-53 — before extracting anything, compare `app/Exceptions/Handlers/AccessDBDenied.php` and `app/Exceptions/Handlers/NoEncryptionKey.php` as WHOLE FILES: 83% 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/Exceptions/Handlers/AdminSetterHandler.php:61` 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. 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. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/Exceptions/Handlers/AdminSetterHandler.php:78` calls `request`, `routeIs`, `renderLegacyInstallerError` and `app/Exceptions/Handlers/InstallationHandler.php:71` does not — after which the two agree again for 2 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 (9 lines × 5) · ×1
  • Duplicated block (9 lines × 5) app/SmartAlbums/FiveStarsAlbum.php:56 — app/SmartAlbums/FiveStarsAlbum.php:56-64 | app/SmartAlbums/FourStarsAlbum.php:57-65 | app/SmartAlbums/ThreeStarsAlbum.php:57-65 | app/SmartAlbums/TwoStarsAlbum.php:59-67 | app/SmartAlbums/UnratedAlbum.php:56-64 — before extracting anything, compare `app/SmartAlbums/FiveStarsAlbum.php` and `app/SmartAlbums/FourStarsAlbum.php` as WHOLE FILES: 84% 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/SmartAlbums/FiveStarsAlbum.php:56` 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. 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 (8–9 lines × 2) · ×1
  • Duplicated block (8–9 lines × 2) app/Jobs/ExtractColoursJob.php:51 — app/Jobs/ExtractColoursJob.php:51-59 | app/Jobs/GeodecodeLocationJob.php:46-53 — 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 (8 lines × 5) · ×1
  • Duplicated block (8 lines × 5) app/Actions/Tag/DeleteTag.php:45 — app/Actions/Tag/DeleteTag.php:45-52 | app/Actions/Tag/DeleteTag.php:57-64 | app/Actions/Tag/MergeTag.php:73-81 | app/Actions/Tag/MergeTag.php:119-127 | app/Actions/Tag/MergeTag.php:171-179 — there are 5 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×1
  • Duplicated block (8 lines × 4) app/Actions/Statistics/Spaces.php:195 — app/Actions/Statistics/Spaces.php:195-202 | app/Actions/Statistics/Spaces.php:263-270 | app/Actions/Statistics/Spaces.php:330-337 | app/Actions/Statistics/Spaces.php:379-386 — 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 (7–8 lines × 2) · ×1
  • Duplicated block (7–8 lines × 2) app/Http/Controllers/Gallery/AlbumListing/AlbumChildrenController.php:108 — app/Http/Controllers/Gallery/AlbumListing/AlbumChildrenController.php:108-114 | app/Http/Controllers/Gallery/AlbumListing/AlbumRootController.php:280-287 — 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 × 3) · ×1
  • Duplicated block (6 lines × 3) app/Http/Resources/Flow/FlowResource.php:44 — app/Http/Resources/Flow/FlowResource.php:44-49 | app/Http/Resources/Search/ResultsResource.php:58-63 | app/Http/Resources/Timeline/TimelineResource.php:51-56 — 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 (37 lines × 2) · ×1
  • Duplicated block (37 lines × 2) app/Http/Requests/Album/GetAlbumChildrenDataRequest.php:44 — app/Http/Requests/Album/GetAlbumChildrenDataRequest.php:44-80 | app/Http/Requests/Album/GetAlbumChildrenRightsRequest.php:41-77 — before extracting anything, compare `app/Http/Requests/Album/GetAlbumChildrenDataRequest.php` and `app/Http/Requests/Album/GetAlbumChildrenRightsRequest.php` as WHOLE FILES: 86% 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 1 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/Http/Requests/Album/GetAlbumChildrenDataRequest.php:44` 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.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) app/Http/Requests/LandingFeaturedItem/DestroyLandingFeaturedItemRequest.php:23 — app/Http/Requests/LandingFeaturedItem/DestroyLandingFeaturedItemRequest.php:23-41 | app/Http/Requests/LandingFeaturedItem/ShowLandingFeaturedItemRequest.php:23-41 — before extracting anything, compare `app/Http/Requests/LandingFeaturedItem/DestroyLandingFeaturedItemRequest.php` and `app/Http/Requests/LandingFeaturedItem/ShowLandingFeaturedItemRequest.php` as WHOLE FILES: 95% 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 1 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/Http/Requests/LandingFeaturedItem/DestroyLandingFeaturedItemRequest.php:23` 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.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) app/Http/Requests/Moderation/GetModerationPhotoHistoryRequest.php:27 — app/Http/Requests/Moderation/GetModerationPhotoHistoryRequest.php:27-46 | app/Http/Requests/Moderation/GetModerationPhotoRequest.php:29-48 — before extracting anything, compare `app/Http/Requests/Moderation/GetModerationPhotoHistoryRequest.php` and `app/Http/Requests/Moderation/GetModerationPhotoRequest.php` as WHOLE FILES: 89% 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 1 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/Http/Requests/Moderation/GetModerationPhotoHistoryRequest.php:27` 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.
D4 · Code Duplication · Duplicated block (30 lines × 2) · ×1
  • Duplicated block (30 lines × 2) app/Http/Requests/Statistics/SpacePerAlbumRequest.php:35 — app/Http/Requests/Statistics/SpacePerAlbumRequest.php:35-64 | app/Http/Requests/Statistics/SpaceSizeVariantRequest.php:35-64 — before extracting anything, compare `app/Http/Requests/Statistics/SpacePerAlbumRequest.php` and `app/Http/Requests/Statistics/SpaceSizeVariantRequest.php` as WHOLE FILES: 97% 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 1 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/Http/Requests/Statistics/SpacePerAlbumRequest.php:35` 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.
D4 · Code Duplication · Duplicated block (28 lines × 4) · ×1
  • Duplicated block (28 lines × 4) app/Http/Requests/Webhook/DestroyWebhookRequest.php:29 — app/Http/Requests/Webhook/DestroyWebhookRequest.php:29-56 | app/Http/Requests/Webhook/PatchWebhookRequest.php:35-76 | app/Http/Requests/Webhook/ShowWebhookRequest.php:29-56 | app/Http/Requests/Webhook/UpdateWebhookRequest.php:34-75 — before extracting anything, compare `app/Http/Requests/Webhook/DestroyWebhookRequest.php` and `app/Http/Requests/Webhook/PatchWebhookRequest.php` as WHOLE FILES: 82% 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/Http/Requests/Webhook/DestroyWebhookRequest.php:29` 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.
D4 · Code Duplication · Duplicated block (28 lines × 5) · ×1
  • Duplicated block (28 lines × 5) app/Http/Requests/Webhook/DestroyWebhookRequest.php:29 — app/Http/Requests/Webhook/DestroyWebhookRequest.php:29-56 | app/Http/Requests/Webhook/PatchWebhookRequest.php:35-76 | app/Http/Requests/Webhook/ShowWebhookRequest.php:29-56 | app/Http/Requests/Webhook/StoreWebhookRequest.php:31-58 | app/Http/Requests/Webhook/UpdateWebhookRequest.php:34-75 — before extracting anything, compare `app/Http/Requests/Webhook/DestroyWebhookRequest.php` and `app/Http/Requests/Webhook/PatchWebhookRequest.php` as WHOLE FILES: 82% 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/Http/Requests/Webhook/DestroyWebhookRequest.php:29` 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.
D4 · Code Duplication · Duplicated block (25 lines × 3) · ×1
  • Duplicated block (25 lines × 3) database/factories/PurchasablePixelSizeFactory.php:35 — database/factories/PurchasablePixelSizeFactory.php:35-60 | database/factories/PurchasablePriceFactory.php:36-77 | database/factories/PurchasablePrintSizeFactory.php:34-58 — 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 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `database/factories/PurchasablePixelSizeFactory.php:35` 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.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) app/Http/Requests/Album/GetAlbumHeadRequest.php:31 — app/Http/Requests/Album/GetAlbumHeadRequest.php:31-45 | app/Http/Requests/Album/GetAlbumRequest.php:31-45 — before extracting anything, compare `app/Http/Requests/Album/GetAlbumHeadRequest.php` and `app/Http/Requests/Album/GetAlbumRequest.php` as WHOLE FILES: 95% 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 1 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. 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 (6 lines × 11) · ×1
  • Duplicated block (6 lines × 11) app/Http/Requests/ShopManagement/DeletePurchasablesRequest.php:28 — app/Http/Requests/ShopManagement/DeletePurchasablesRequest.php:28-33 | app/Http/Requests/ShopManagement/ListPurchasablesRequest.php:28-33 | app/Http/Requests/ShopManagement/PixelSize/CreatePixelSizeRequest.php:27-32 | app/Http/Requests/ShopManagement/PixelSize/DeletePixelSizeRequest.php:27-32 | app/Http/Requests/ShopManagement/PixelSize/UpdatePixelSizeRequest.php:29-34 | app/Http/Requests/ShopManagement/PrintSize/CreatePrintSizeRequest.php:29-34 | app/Http/Requests/ShopManagement/PrintSize/DeletePrintSizeRequest.php:27-32 | app/Http/Requests/ShopManagement/PrintSize/UpdatePrintSizeRequest.php:31-36 | app/Http/Requests/ShopManagement/PurchasableAlbumRequest.php:47-52 | app/Http/Requests/ShopManagement/PurchasablePhotoRequest.php:53-58 | app/Http/Requests/ShopManagement/UpdatePurchasablePriceRequest.php:44-49 — before extracting anything, compare `app/Http/Requests/ShopManagement/PixelSize/CreatePixelSizeRequest.php` and `app/Http/Requests/ShopManagement/PixelSize/UpdatePixelSizeRequest.php` as WHOLE FILES: 95% 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 1 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.
D4 · Code Duplication · Duplicated block (5 lines × 6) · ×1
  • Duplicated block (5 lines × 6) app/Http/Controllers/Admin/LandingFeaturedItemController.php:51 — app/Http/Controllers/Admin/LandingFeaturedItemController.php:51-55 | app/Http/Controllers/Admin/LandingFeaturedItemController.php:60-64 | app/Http/Controllers/Admin/LandingLinkController.php:51-55 | app/Http/Controllers/Admin/LandingLinkController.php:60-64 | app/Http/Controllers/Admin/WebhookController.php:66-71 | app/Http/Controllers/Admin/WebhookController.php:79-84 — there are 6 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×1
  • Duplicated block (7 lines × 3) app/Models/LandingFeaturedItem.php:60 — app/Models/LandingFeaturedItem.php:60-66 | app/Models/LandingLink.php:72-78 | app/Models/Webhook.php:103-109 — 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 3 call sites, so a change lands once.
DM11 · Constructible invalid state · Constructible in an invalid state · ×1
  • Constructible in an invalid state: PhotoResource app/Http/Resources/Models/PhotoResource.php:65 — `PhotoResource`'s public constructor takes `album_id` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `PhotoResource` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
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 7 sibling directories (318 clone groups) · ×1
  • Duplication concentrated across 7 sibling directories (318 clone groups) resources/js/v7/views/face-recog/PersonDetail.vue:181 — 318 duplicated blocks under resources/js/ have copies in at least two of the sibling directories composables, layouts, services, stores, utils, v7 (+1 more sibling(s) not listed) — 292 of them are reported below, and 26 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 318 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 318 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 318 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 · Duplication concentrated across 4 sibling directories (7 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (7 clone groups) resources/js/v8/components/gallery/tagModule/TagPanel.vue:135 — 7 duplicated blocks under resources/js/v8/ have copies in at least two of the sibling directories components, composables, utils, views — 5 of them are reported below, and 2 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 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 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 · Duplication concentrated across 6 sibling directories (5 clone groups) · ×1
  • Duplication concentrated across 6 sibling directories (5 clone groups) resources/js/v8/components/drawers/PhotoEdit.vue:133 — 5 duplicated blocks under resources/js/v8/components/ have copies in at least two of the sibling directories drawers, forms, gallery, headers, modals, renamer — 2 of them are reported below, and 3 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 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 · Wholesale file copy (299 identical lines × 2 files) · ×1
  • Wholesale file copy (299 identical lines × 2 files) resources/js/v7/views/face-recog/PersonDetail.vue:181 — resources/js/v7/views/face-recog/PersonDetail.vue:181 · resources/js/v8/views/face-recog/PersonDetail.vue:187 — these 2 files are line-for-line copies of one another — 299 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (273 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (273 matched lines × 2 locations) resources/js/v7/views/gallery-panels/Search.vue:175 — resources/js/v7/views/gallery-panels/Search.vue:175 · resources/js/v8/views/gallery-panels/Search.vue:167 — the two spans are one implementation copied and then locally edited — 1920 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 · Wholesale file copy (267 identical lines × 2 files) · ×1
  • Wholesale file copy (267 identical lines × 2 files) resources/js/composables/contextMenus/contextMenu.ts:1 — resources/js/composables/contextMenus/contextMenu.ts:1 · resources/js/v8/composables/contextMenus/contextMenu.ts:1 — these 2 files are line-for-line copies of one another — 267 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (234 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (234 matched lines × 2 locations) resources/js/v7/components/gallery/albumModule/AlbumPanel.vue:217 — resources/js/v7/components/gallery/albumModule/AlbumPanel.vue:217 · resources/js/v8/components/gallery/albumModule/AlbumPanel.vue:288 — the two spans are one implementation copied and then locally edited — 1679 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 (228 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (228 matched lines × 2 locations) resources/js/v7/components/forms/album/AlbumProperties.vue:393 — resources/js/v7/components/forms/album/AlbumProperties.vue:393 · resources/js/v8/components/forms/album/AlbumProperties.vue:273 — the two spans are one implementation copied and then locally edited — 1902 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 (216 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (216 matched lines × 2 locations) resources/js/v7/views/gallery-panels/Album.vue:174 — resources/js/v7/views/gallery-panels/Album.vue:174 · resources/js/v8/views/gallery-panels/Album.vue:178 — the two spans are one implementation copied and then locally edited — 1664 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 · Wholesale file copy (203 identical lines × 2 files) · ×1
  • Wholesale file copy (203 identical lines × 2 files) resources/js/v7/views/face-recog/FaceMaintenance.vue:266 — resources/js/v7/views/face-recog/FaceMaintenance.vue:266 · resources/js/v8/views/face-recog/FaceMaintenance.vue:273 — these 2 files are line-for-line copies of one another — 203 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (188 identical lines × 2 files) · ×1
  • Wholesale file copy (188 identical lines × 2 files) resources/js/v7/components/forms/album/EmbedCodeDialog.vue:138 — resources/js/v7/components/forms/album/EmbedCodeDialog.vue:138 · resources/js/v8/components/forms/album/EmbedCodeDialog.vue:152 — these 2 files are line-for-line copies of one another — 188 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (170 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (170 matched lines × 2 locations) resources/js/v7/views/gallery-panels/Timeline.vue:217 — resources/js/v7/views/gallery-panels/Timeline.vue:217 · resources/js/v8/views/gallery-panels/Timeline.vue:245 — the two spans are one implementation copied and then locally edited — 1047 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 (140 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (140 matched lines × 2 locations) resources/js/v7/views/face-recog/FaceClusters.vue:229 — resources/js/v7/views/face-recog/FaceClusters.vue:229 · resources/js/v8/views/face-recog/FaceClusters.vue:292 — the two spans are one implementation copied and then locally edited — 1267 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 · Wholesale file copy (136 identical lines × 2 files) · ×1
  • Wholesale file copy (136 identical lines × 2 files) resources/js/v7/components/settings/General.vue:236 — resources/js/v7/components/settings/General.vue:236 · resources/js/v8/components/settings/General.vue:254 — these 2 files are line-for-line copies of one another — 136 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (130 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (130 matched lines × 2 locations) resources/js/v7/views/gallery-panels/Tag.vue:122 — resources/js/v7/views/gallery-panels/Tag.vue:122 · resources/js/v8/views/gallery-panels/Tag.vue:120 — the two spans are one implementation copied and then locally edited — 872 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 (123 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (123 matched lines × 2 locations) resources/js/v7/components/drawers/LiveMetrics.vue:58 — resources/js/v7/components/drawers/LiveMetrics.vue:58 · resources/js/v8/components/drawers/LiveMetrics.vue:71 — the two spans are one implementation copied and then locally edited — 947 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 · Wholesale file copy (121 identical lines × 2 files) · ×1
  • Wholesale file copy (121 identical lines × 2 files) resources/js/v7/components/gallery/albumModule/AlbumHeaderPanel.vue:123 — resources/js/v7/components/gallery/albumModule/AlbumHeaderPanel.vue:123 · resources/js/v8/components/gallery/albumModule/AlbumHeaderPanel.vue:137 — these 2 files are line-for-line copies of one another — 121 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (120 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (120 matched lines × 2 locations) resources/js/v7/views/gallery-panels/Albums.vue:274 — resources/js/v7/views/gallery-panels/Albums.vue:274 · resources/js/v8/views/gallery-panels/Albums.vue:241 — the two spans are one implementation copied and then locally edited — 786 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 · Wholesale file copy (116 identical lines × 2 files) · ×1
  • Wholesale file copy (116 identical lines × 2 files) resources/js/v7/components/renamer/RenamerRuleModal.vue:174 — resources/js/v7/components/renamer/RenamerRuleModal.vue:174 · resources/js/v8/components/renamer/RenamerRuleModal.vue:139 — these 2 files are line-for-line copies of one another — 116 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (109 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (109 matched lines × 2 locations) resources/js/v7/views/admin/Jobs.vue:51 — resources/js/v7/views/admin/Jobs.vue:51 · resources/js/v8/views/admin/Jobs.vue:103 — the two spans are one implementation copied and then locally edited — 744 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 · Wholesale file copy (108 identical lines × 2 files) · ×1
  • Wholesale file copy (108 identical lines × 2 files) resources/js/v7/components/forms/gallery-dialogs/MoveDialog.vue:33 — resources/js/v7/components/forms/gallery-dialogs/MoveDialog.vue:33 · resources/js/v8/components/forms/gallery-dialogs/MoveDialog.vue:45 — these 2 files are line-for-line copies of one another — 108 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (107 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (107 matched lines × 2 locations) resources/js/v7/components/modals/UploadPanel.vue:122 — resources/js/v7/components/modals/UploadPanel.vue:122 · resources/js/v8/components/modals/UploadPanel.vue:125 — the two spans are one implementation copied and then locally edited — 869 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 (105 lines × 2 locations) · ×1
  • Duplicated block (105 lines × 2 locations) resources/js/v7/views/admin/Moderation.vue:167 — resources/js/v7/views/admin/Moderation.vue:167 · resources/js/v8/views/admin/Moderation.vue:180 — 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 with local edits (103 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (103 matched lines × 2 locations) resources/js/v7/views/admin/Settings.vue:79 — resources/js/v7/views/admin/Settings.vue:79 · resources/js/v8/views/admin/Settings.vue:108 — the two spans are one implementation copied and then locally edited — 715 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 · Wholesale file copy (97 identical lines × 2 files) · ×1
  • Wholesale file copy (97 identical lines × 2 files) resources/js/v7/views/webshop/OrderDownload.vue:206 — resources/js/v7/views/webshop/OrderDownload.vue:206 · resources/js/v8/views/webshop/OrderDownload.vue:214 — these 2 files are line-for-line copies of one another — 97 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (96 identical lines × 2 files) · ×1
  • Wholesale file copy (96 identical lines × 2 files) resources/js/v7/components/forms/album/AlbumPurchasable.vue:59 — resources/js/v7/components/forms/album/AlbumPurchasable.vue:59 · resources/js/v8/components/forms/album/AlbumPurchasable.vue:60 — these 2 files are line-for-line copies of one another — 96 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (95 identical lines × 2 files) · ×1
  • Wholesale file copy (95 identical lines × 2 files) resources/js/v7/components/forms/users/CreateEditUser.vue:91 — resources/js/v7/components/forms/users/CreateEditUser.vue:91 · resources/js/v8/components/forms/users/CreateEditUser.vue:84 — these 2 files are line-for-line copies of one another — 95 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block (90 lines × 2 locations) · ×1
  • Duplicated block (90 lines × 2 locations) resources/js/v7/components/forms/search/AdvancedSearchPanel.vue:222 — resources/js/v7/components/forms/search/AdvancedSearchPanel.vue:222 · resources/js/v8/components/forms/search/AdvancedSearchPanel.vue:275 — 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 · Wholesale file copy (89 identical lines × 2 files) · ×1
  • Wholesale file copy (89 identical lines × 2 files) resources/js/v7/components/modals/CameraCapture.vue:70 — resources/js/v7/components/modals/CameraCapture.vue:70 · resources/js/v8/components/modals/CameraCapture.vue:82 — these 2 files are line-for-line copies of one another — 89 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (89 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (89 matched lines × 2 locations) resources/js/v7/views/admin/UserGroups.vue:126 — resources/js/v7/views/admin/UserGroups.vue:126 · resources/js/v8/views/admin/UserGroups.vue:118 — the two spans are one implementation copied and then locally edited — 702 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 (88 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (88 matched lines × 2 locations) resources/js/v7/components/forms/album/ApplyRenamerDialog.vue:121 — resources/js/v7/components/forms/album/ApplyRenamerDialog.vue:121 · resources/js/v8/components/forms/album/ApplyRenamerDialog.vue:157 — the two spans are one implementation copied and then locally edited — 609 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 · Wholesale file copy (87 identical lines × 2 files) · ×1
  • Wholesale file copy (87 identical lines × 2 files) resources/js/v7/components/pagination/PaginationInfiniteScroll.vue:8 — resources/js/v7/components/pagination/PaginationInfiniteScroll.vue:8 · resources/js/v8/components/pagination/PaginationInfiniteScroll.vue:8 — these 2 files are line-for-line copies of one another — 87 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block (84 lines × 2 locations) · ×1
  • Duplicated block (84 lines × 2 locations) resources/js/v7/components/drawers/PhotoDetails.vue:321 — resources/js/v7/components/drawers/PhotoDetails.vue:321 · resources/js/v8/components/drawers/PhotoDetails.vue:311 — 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 · Wholesale file copy (82 identical lines × 2 files) · ×1
  • Wholesale file copy (82 identical lines × 2 files) resources/js/v8/components/gallery/albumModule/Virtualized/AlbumListViewVirtual.vue:59 — resources/js/v8/components/gallery/albumModule/Virtualized/AlbumListViewVirtual.vue:59 · resources/js/v8/components/gallery/albumModule/Virtualized/AlbumThumbGridVirtual.vue:85 — these 2 files are line-for-line copies of one another — 82 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (80 identical lines × 2 files) · ×1
  • Wholesale file copy (80 identical lines × 2 files) resources/js/v8/components/gallery/albumModule/Virtualized/AlbumRootGridVirtual.vue:89 — resources/js/v8/components/gallery/albumModule/Virtualized/AlbumRootGridVirtual.vue:89 · resources/js/v8/components/gallery/albumModule/Virtualized/AlbumRootListViewVirtual.vue:60 — these 2 files are line-for-line copies of one another — 80 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (78 identical lines × 2 files) · ×1
  • Wholesale file copy (78 identical lines × 2 files) resources/js/v7/views/RegisterPage.vue:61 — resources/js/v7/views/RegisterPage.vue:61 · resources/js/v8/views/RegisterPage.vue:54 — these 2 files are line-for-line copies of one another — 78 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (77 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (77 matched lines × 2 locations) resources/js/v7/components/drawers/PhotoEdit.vue:123 — resources/js/v7/components/drawers/PhotoEdit.vue:123 · resources/js/v8/components/drawers/PhotoEdit.vue:94 — the two spans are one implementation copied and then locally edited — 754 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 · Wholesale file copy (76 identical lines × 2 files) · ×1
  • Wholesale file copy (76 identical lines × 2 files) resources/js/v7/views/admin/AdminDashboard.vue:172 — resources/js/v7/views/admin/AdminDashboard.vue:172 · resources/js/v8/views/admin/AdminDashboard.vue:134 — these 2 files are line-for-line copies of one another — 76 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R2 · Cyclomatic Complexity · Complex function phpDateFormat (cyclomatic 56, cognitive 35) · ×1
  • Complex function phpDateFormat (cyclomatic 56, cognitive 35) resources/js/v8/utils/phpDateFormat.ts:261 — phpDateFormat has cyclomatic complexity 56 and cognitive complexity 35; 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 (anonymous) (cyclomatic 48, cognitive 47) · ×1
  • Complex function (anonymous) (cyclomatic 48, cognitive 47) resources/js/composables/contextMenus/leftMenu.ts:66 — (anonymous) has cyclomatic complexity 48 and cognitive complexity 47; 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 (anonymous) (cyclomatic 40, cognitive 26) · ×1
  • Complex function (anonymous) (cyclomatic 40, cognitive 26) resources/js/v8/composables/spotlight/useSpotlightGalleryActions.ts:75 — (anonymous) has cyclomatic complexity 40 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 (anonymous) (cyclomatic 40, cognitive 13) · ×1
  • Complex function (anonymous) (cyclomatic 40, cognitive 13) resources/js/v8/views/admin/LandingConfig.vue:673 — (anonymous) has cyclomatic complexity 40 and cognitive complexity 13; 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 mergePhotoDetail (cyclomatic 38, cognitive 35) · ×1
  • Complex function mergePhotoDetail (cyclomatic 38, cognitive 35) resources/js/v8/utils/adaptPhotoTile.ts:225 — mergePhotoDetail has cyclomatic complexity 38 and cognitive complexity 35; 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 validateConfig (cyclomatic 36, cognitive 35) · ×1
  • Complex function validateConfig (cyclomatic 36, cognitive 35) resources/js/embed/config.ts:30 — validateConfig has cyclomatic complexity 36 and cognitive complexity 35; 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 parseDataAttributes (cyclomatic 28, cognitive 34) · ×1
  • Complex function parseDataAttributes (cyclomatic 28, cognitive 34) resources/js/embed/config.ts:131 — parseDataAttributes has cyclomatic complexity 28 and cognitive complexity 34; 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 parse (cyclomatic 26, cognitive 45) · ×1
  • Complex function parse (cyclomatic 26, cognitive 45) resources/js/utils/sprintf.ts:100 — parse has cyclomatic complexity 26 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 (anonymous) (cyclomatic 26, cognitive 25) · ×1
  • Complex function (anonymous) (cyclomatic 26, cognitive 25) resources/js/v8/composables/contextMenus/leftMenu.ts:169 — (anonymous) has cyclomatic complexity 26 and cognitive complexity 25; 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 (anonymous) (cyclomatic 25, cognitive 19) · ×1
  • Complex function (anonymous) (cyclomatic 25, cognitive 19) resources/js/v7/components/headers/AlbumsHeader.vue:284 — (anonymous) has cyclomatic complexity 25 and cognitive complexity 19; 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 decideKey (cyclomatic 24, cognitive 27) · ×1
  • Complex function decideKey (cyclomatic 24, cognitive 27) resources/js/v8/utils/quickNaming.ts:132 — decideKey has cyclomatic complexity 24 and cognitive complexity 27; 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 24, cognitive 24) · ×1
  • Complex function (anonymous) (cyclomatic 24, cognitive 24) resources/js/v8/views/admin/WatermarkPreview.vue:513 — (anonymous) has cyclomatic complexity 24 and cognitive complexity 24; 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 24, cognitive 18) · ×1
  • Complex function (anonymous) (cyclomatic 24, cognitive 18) resources/js/v8/components/headers/AlbumsHeader.vue:271 — (anonymous) has cyclomatic complexity 24 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 (anonymous) (cyclomatic 24, cognitive 17) · ×1
  • Complex function (anonymous) (cyclomatic 24, cognitive 17) resources/js/config/axios-config.ts:107 — (anonymous) has cyclomatic complexity 24 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 (anonymous) (cyclomatic 22, cognitive 38) · ×1
  • Complex function (anonymous) (cyclomatic 22, cognitive 38) resources/js/v8/components/gallery/timelineModule/TimelineDatesV3.vue:319 — (anonymous) has cyclomatic complexity 22 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.
R2 · Cyclomatic Complexity · Complex function convertNumber (cyclomatic 21, cognitive 15) · ×1
  • Complex function convertNumber (cyclomatic 21, cognitive 15) resources/js/utils/sprintf.ts:298 — convertNumber has cyclomatic complexity 21 and cognitive complexity 15; 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 getStatistics (cyclomatic 20, cognitive 45) · ×1
  • Complex function getStatistics (cyclomatic 20, cognitive 45) resources/js/composables/album/albumStatistics.ts:22 — getStatistics has cyclomatic complexity 20 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 parseTokens (cyclomatic 20, cognitive 21) · ×1
  • Complex function parseTokens (cyclomatic 20, cognitive 21) resources/js/composables/useSearchTokenAssembler.ts:149 — parseTokens has cyclomatic complexity 20 and cognitive complexity 21; 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 saveAlbum (cyclomatic 20, cognitive 19) · ×1
  • Complex function saveAlbum (cyclomatic 20, cognitive 19) resources/js/v8/components/forms/album/AlbumProperties.vue:582 — saveAlbum has cyclomatic complexity 20 and cognitive complexity 19; 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 (anonymous) (cyclomatic 19, cognitive 21) · ×1
  • Complex function (anonymous) (cyclomatic 19, cognitive 21) resources/js/v7/views/gallery-panels/Map.vue:199 — (anonymous) has cyclomatic complexity 19 and cognitive complexity 21; 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 assembleTokens (cyclomatic 19, cognitive 18) · ×1
  • Complex function assembleTokens (cyclomatic 19, cognitive 18) resources/js/composables/useSearchTokenAssembler.ts:81 — assembleTokens has cyclomatic complexity 19 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 (anonymous) (cyclomatic 19, cognitive 18) · ×1
  • Complex function (anonymous) (cyclomatic 19, cognitive 18) resources/js/v8/composables/contextMenus/leftMenu.ts:82 — (anonymous) has cyclomatic complexity 19 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 (anonymous) (cyclomatic 18, cognitive 20) · ×1
  • Complex function (anonymous) (cyclomatic 18, cognitive 20) resources/js/composables/album/dragAndSelect.ts:352 — (anonymous) has cyclomatic complexity 18 and cognitive complexity 20; 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 toggleBuyMe (cyclomatic 18, cognitive 17) · ×1
  • Complex function toggleBuyMe (cyclomatic 18, cognitive 17) resources/js/composables/album/buyMeActions.ts:30 — toggleBuyMe has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 calculateLayout (cyclomatic 18, cognitive 14) · ×1
  • Complex function calculateLayout (cyclomatic 18, cognitive 14) resources/js/embed/components/EmbedWidget.vue:291 — calculateLayout has cyclomatic complexity 18 and cognitive complexity 14; 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 (anonymous) (cyclomatic 16, cognitive 19) · ×1
  • Complex function (anonymous) (cyclomatic 16, cognitive 19) resources/js/stores/AlbumState.ts:864 — (anonymous) has cyclomatic complexity 16 and cognitive complexity 19; 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 saveAlbum (cyclomatic 16, cognitive 15) · ×1
  • Complex function saveAlbum (cyclomatic 16, cognitive 15) resources/js/v7/components/forms/album/AlbumProperties.vue:564 — saveAlbum has cyclomatic complexity 16 and cognitive complexity 15; 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 setAsHeader (cyclomatic 15, cognitive 17) · ×1
  • Complex function setAsHeader (cyclomatic 15, cognitive 17) resources/js/v8/components/gallery/albumModule/AlbumPanel.vue:421 — setAsHeader has cyclomatic complexity 15 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function setAsHeader (cyclomatic 14, cognitive 16) · ×1
  • Complex function setAsHeader (cyclomatic 14, cognitive 16) resources/js/v7/components/gallery/albumModule/AlbumPanel.vue:361 — setAsHeader has cyclomatic complexity 14 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 14, cognitive 11) · ×1
  • Complex function (anonymous) (cyclomatic 14, cognitive 11) resources/js/v7/components/headers/TimelineHeader.vue:242 — (anonymous) has cyclomatic complexity 14 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function computeTimelinePhotoLayout (cyclomatic 13, cognitive 27) · ×1
  • Complex function computeTimelinePhotoLayout (cyclomatic 13, cognitive 27) resources/js/v8/composables/photo/analyticPhotoLayout.ts:307 — computeTimelinePhotoLayout has cyclomatic complexity 13 and cognitive complexity 27; 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 13, cognitive 15) · ×1
  • Complex function (anonymous) (cyclomatic 13, cognitive 15) resources/js/composables/album/photoActions.ts:68 — (anonymous) has cyclomatic complexity 13 and cognitive complexity 15; 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/v8/views/admin/LandingConfig.vue · ×1
  • resources/js/v8/views/admin/LandingConfig.vue: 1124 lines of code resources/js/v8/views/admin/LandingConfig.vue:1 — resources/js/v8/views/admin/LandingConfig.vue has 1124 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/stores/AlbumState.ts · ×1
  • resources/js/stores/AlbumState.ts: 971 lines of code resources/js/stores/AlbumState.ts:1 — resources/js/stores/AlbumState.ts has 971 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/v8/views/face-recog/FaceClusters.vue · ×1
  • resources/js/v8/views/face-recog/FaceClusters.vue: 775 lines of code resources/js/v8/views/face-recog/FaceClusters.vue:1 — resources/js/v8/views/face-recog/FaceClusters.vue has 775 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/v8/components/gallery/albumModule/Virtualized/PhotoGridVirtual.vue · ×1
  • resources/js/v8/components/gallery/albumModule/Virtualized/PhotoGridVirtual.vue: 716 lines of code resources/js/v8/components/gallery/albumModule/Virtualized/PhotoGridVirtual.vue:1 — resources/js/v8/components/gallery/albumModule/Virtualized/PhotoGridVirtual.vue has 716 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/v8/components/forms/album/AlbumProperties.vue · ×1
  • resources/js/v8/components/forms/album/AlbumProperties.vue: 685 lines of code resources/js/v8/components/forms/album/AlbumProperties.vue:1 — resources/js/v8/components/forms/album/AlbumProperties.vue has 685 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/v8/views/BulkAlbumEdit.vue · ×1
  • resources/js/v8/views/BulkAlbumEdit.vue: 663 lines of code resources/js/v8/views/BulkAlbumEdit.vue:1 — resources/js/v8/views/BulkAlbumEdit.vue has 663 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/v8/components/gallery/albumModule/AlbumPanel.vue · ×1
  • resources/js/v8/components/gallery/albumModule/AlbumPanel.vue: 647 lines of code resources/js/v8/components/gallery/albumModule/AlbumPanel.vue:1 — resources/js/v8/components/gallery/albumModule/AlbumPanel.vue has 647 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/v8/views/gallery-panels/Map.vue · ×1
  • resources/js/v8/views/gallery-panels/Map.vue: 643 lines of code resources/js/v8/views/gallery-panels/Map.vue:1 — resources/js/v8/views/gallery-panels/Map.vue has 643 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/v8/components/gallery/photoModule/PhotoBox.vue · ×1
  • resources/js/v8/components/gallery/photoModule/PhotoBox.vue: 639 lines of code resources/js/v8/components/gallery/photoModule/PhotoBox.vue:1 — resources/js/v8/components/gallery/photoModule/PhotoBox.vue has 639 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/v7/components/forms/album/AlbumProperties.vue · ×1
  • resources/js/v7/components/forms/album/AlbumProperties.vue: 629 lines of code resources/js/v7/components/forms/album/AlbumProperties.vue:1 — resources/js/v7/components/forms/album/AlbumProperties.vue has 629 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/v8/views/face-recog/PersonDetail.vue · ×1
  • resources/js/v8/views/face-recog/PersonDetail.vue: 626 lines of code resources/js/v8/views/face-recog/PersonDetail.vue:1 — resources/js/v8/views/face-recog/PersonDetail.vue has 626 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/embed/components/EmbedWidget.vue · ×1
  • resources/js/embed/components/EmbedWidget.vue: 605 lines of code resources/js/embed/components/EmbedWidget.vue:1 — resources/js/embed/components/EmbedWidget.vue has 605 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/v7/views/face-recog/PersonDetail.vue · ×1
  • resources/js/v7/views/face-recog/PersonDetail.vue: 598 lines of code resources/js/v7/views/face-recog/PersonDetail.vue:1 — resources/js/v7/views/face-recog/PersonDetail.vue has 598 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/v7/views/BulkAlbumEdit.vue · ×1
  • resources/js/v7/views/BulkAlbumEdit.vue: 576 lines of code resources/js/v7/views/BulkAlbumEdit.vue:1 — resources/js/v7/views/BulkAlbumEdit.vue has 576 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/v7/views/gallery-panels/Search.vue · ×1
  • resources/js/v7/views/gallery-panels/Search.vue: 576 lines of code resources/js/v7/views/gallery-panels/Search.vue:1 — resources/js/v7/views/gallery-panels/Search.vue has 576 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/v8/views/gallery-panels/Search.vue · ×1
  • resources/js/v8/views/gallery-panels/Search.vue: 575 lines of code resources/js/v8/views/gallery-panels/Search.vue:1 — resources/js/v8/views/gallery-panels/Search.vue has 575 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/v7/views/face-recog/FaceClusters.vue · ×1
  • resources/js/v7/views/face-recog/FaceClusters.vue: 555 lines of code resources/js/v7/views/face-recog/FaceClusters.vue:1 — resources/js/v7/views/face-recog/FaceClusters.vue has 555 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/v8/composables/useSphereViewer.ts · ×1
  • resources/js/v8/composables/useSphereViewer.ts: 544 lines of code resources/js/v8/composables/useSphereViewer.ts:1 — resources/js/v8/composables/useSphereViewer.ts has 544 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/v8/views/face-recog/FaceMaintenance.vue · ×1
  • resources/js/v8/views/face-recog/FaceMaintenance.vue: 543 lines of code resources/js/v8/views/face-recog/FaceMaintenance.vue:1 — resources/js/v8/views/face-recog/FaceMaintenance.vue has 543 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/v7/components/gallery/albumModule/AlbumPanel.vue · ×1
  • resources/js/v7/components/gallery/albumModule/AlbumPanel.vue: 532 lines of code resources/js/v7/components/gallery/albumModule/AlbumPanel.vue:1 — resources/js/v7/components/gallery/albumModule/AlbumPanel.vue 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/v8/views/gallery-panels/Timeline.vue · ×1
  • resources/js/v8/views/gallery-panels/Timeline.vue: 532 lines of code resources/js/v8/views/gallery-panels/Timeline.vue:1 — resources/js/v8/views/gallery-panels/Timeline.vue 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/embed/components/Lightbox.vue · ×1
  • resources/js/embed/components/Lightbox.vue: 524 lines of code resources/js/embed/components/Lightbox.vue:1 — resources/js/embed/components/Lightbox.vue has 524 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/v7/views/gallery-panels/Album.vue · ×1
  • resources/js/v7/views/gallery-panels/Album.vue: 520 lines of code resources/js/v7/views/gallery-panels/Album.vue:1 — resources/js/v7/views/gallery-panels/Album.vue has 520 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/v7/views/face-recog/FaceMaintenance.vue · ×1
  • resources/js/v7/views/face-recog/FaceMaintenance.vue: 515 lines of code resources/js/v7/views/face-recog/FaceMaintenance.vue:1 — resources/js/v7/views/face-recog/FaceMaintenance.vue has 515 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/v8/views/gallery-panels/Album.vue · ×1
  • resources/js/v8/views/gallery-panels/Album.vue: 514 lines of code resources/js/v8/views/gallery-panels/Album.vue:1 — resources/js/v8/views/gallery-panels/Album.vue has 514 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/v8/views/admin/WatermarkPreview.vue · ×1
  • resources/js/v8/views/admin/WatermarkPreview.vue: 506 lines of code resources/js/v8/views/admin/WatermarkPreview.vue:1 — resources/js/v8/views/admin/WatermarkPreview.vue has 506 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/composables/album/dragAndSelect.ts · ×1
  • resources/js/composables/album/dragAndSelect.ts: 496 lines of code resources/js/composables/album/dragAndSelect.ts:1 — resources/js/composables/album/dragAndSelect.ts has 496 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/v7/views/admin/NsfwConfig.vue · ×1
  • resources/js/v7/views/admin/NsfwConfig.vue: 486 lines of code resources/js/v7/views/admin/NsfwConfig.vue:1 — resources/js/v7/views/admin/NsfwConfig.vue has 486 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/v7/views/gallery-panels/Timeline.vue · ×1
  • resources/js/v7/views/gallery-panels/Timeline.vue: 481 lines of code resources/js/v7/views/gallery-panels/Timeline.vue:1 — resources/js/v7/views/gallery-panels/Timeline.vue has 481 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/v8/components/gallery/timelineModule/TimelineDatesV3.vue · ×1
  • resources/js/v8/components/gallery/timelineModule/TimelineDatesV3.vue: 467 lines of code resources/js/v8/components/gallery/timelineModule/TimelineDatesV3.vue:1 — resources/js/v8/components/gallery/timelineModule/TimelineDatesV3.vue has 467 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/v8/utils/phpDateFormat.ts · ×1
  • resources/js/v8/utils/phpDateFormat.ts: 459 lines of code resources/js/v8/utils/phpDateFormat.ts:1 — resources/js/v8/utils/phpDateFormat.ts has 459 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/v8/views/admin/NsfwConfig.vue · ×1
  • resources/js/v8/views/admin/NsfwConfig.vue: 452 lines of code resources/js/v8/views/admin/NsfwConfig.vue:1 — resources/js/v8/views/admin/NsfwConfig.vue has 452 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/v8/composables/contextMenus/contextMenu.ts · ×1
  • resources/js/v8/composables/contextMenus/contextMenu.ts: 451 lines of code resources/js/v8/composables/contextMenus/contextMenu.ts:1 — resources/js/v8/composables/contextMenus/contextMenu.ts has 451 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/v7/views/gallery-panels/Albums.vue · ×1
  • resources/js/v7/views/gallery-panels/Albums.vue: 450 lines of code resources/js/v7/views/gallery-panels/Albums.vue:1 — resources/js/v7/views/gallery-panels/Albums.vue has 450 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/composables/contextMenus/contextMenu.ts · ×1
  • resources/js/composables/contextMenus/contextMenu.ts: 448 lines of code resources/js/composables/contextMenus/contextMenu.ts:1 — resources/js/composables/contextMenus/contextMenu.ts has 448 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/v8/components/settings/General.vue · ×1
  • resources/js/v8/components/settings/General.vue: 442 lines of code resources/js/v8/components/settings/General.vue:1 — resources/js/v8/components/settings/General.vue has 442 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/v8/views/gallery-panels/Albums.vue · ×1
  • resources/js/v8/views/gallery-panels/Albums.vue: 442 lines of code resources/js/v8/views/gallery-panels/Albums.vue:1 — resources/js/v8/views/gallery-panels/Albums.vue has 442 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/v7/components/drawers/PhotoDetails.vue · ×1
  • resources/js/v7/components/drawers/PhotoDetails.vue: 439 lines of code resources/js/v7/components/drawers/PhotoDetails.vue:1 — resources/js/v7/components/drawers/PhotoDetails.vue has 439 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/v8/components/drawers/PhotoDetails.vue · ×1
  • resources/js/v8/components/drawers/PhotoDetails.vue: 420 lines of code resources/js/v8/components/drawers/PhotoDetails.vue:1 — resources/js/v8/components/drawers/PhotoDetails.vue has 420 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/v7/components/settings/General.vue · ×1
  • resources/js/v7/components/settings/General.vue: 417 lines of code resources/js/v7/components/settings/General.vue:1 — resources/js/v7/components/settings/General.vue has 417 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R5 · Dependency Freshness · Dependency Freshness · ×1
  • Dependency Freshness — 49 outdated package(s); JS/npm CVEs scored in D30
R7 · Dead Code · Dead file (~205 LoC) · ×1
  • Dead file (~205 LoC) resources/js/v7/components/forms/basic/Password.vue — no import path from any entry point (22 application, 8 tooling, 35 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 (~133 LoC) · ×1
  • Dead file (~133 LoC) resources/js/composables/pagination/usePagination.ts — no import path from any entry point (22 application, 8 tooling, 35 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 (~95 LoC) · ×1
  • Dead file (~95 LoC) resources/js/v7/components/forms/sharing/CreateSharing.vue — no import path from any entry point (22 application, 8 tooling, 35 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 (~87 LoC) · ×1
  • Dead file (~87 LoC) resources/js/v7/views/webshop/PurchasablesList.vue — no import path from any entry point (22 application, 8 tooling, 35 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 (~38 LoC) · ×1
  • Dead file (~38 LoC) resources/js/v7/components/forms/card/cardTypes.ts — no import path from any entry point (22 application, 8 tooling, 35 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 (~23 LoC) · ×1
  • Dead file (~23 LoC) resources/js/composables/photo/basePhoto.ts — no import path from any entry point (22 application, 8 tooling, 35 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 (~8 LoC) · ×1
  • Dead file (~8 LoC) resources/js/v7/components/forms/card/images.ts — no import path from any entry point (22 application, 8 tooling, 35 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 · Unlisted import '@primevue/core' · ×1
  • Unlisted import '@primevue/core' resources/js/v7/components/forms/basic/InputPassword.vue:19 — Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json.
R8 · Dependency Hygiene · Unused dependency '@fortawesome/fontawesome-free' · ×1
  • Unused dependency '@fortawesome/fontawesome-free' package.json:34 — 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 '@mollie/api-client' · ×1
  • Unused dependency '@mollie/api-client' package.json:39 — 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 '@stripe/stripe-js' · ×1
  • Unused dependency '@stripe/stripe-js' package.json:44 — 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 '@vue/tsconfig' · ×1
  • Unused dependency '@vue/tsconfig' package.json:26 — 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 'primeicons' · ×1
  • Unused dependency 'primeicons' package.json:65 — 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 'tailwindcss-primeui' · ×1
  • Unused dependency 'tailwindcss-primeui' package.json:69 — 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 'tinygesture' · ×1
  • Unused dependency 'tinygesture' package.json:70 — 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 'vue-i18n' · ×1
  • Unused dependency 'vue-i18n' package.json:77 — 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.
S1 · Web-Security Posture · Third-party script without Subresource Integrity · ×1
  • Third-party script without Subresource Integrity resources/views/components/webshop.blade.php:3 — `https://js.mollie.com/v1/mollie.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository.
Minor — 216 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×48
  • Orphaned file app/Models/Extensions/ForwardsToParentImplementation.php: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.
  • Orphaned file app/Services/Auth/SessionOrTokenGuard.php: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.
  • Orphaned file app/Models/Extensions/UTCBasedTimes.php: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.
  • Orphaned file database/migrations/2021_05_25_160600_post_revert_fixes.php: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.
  • Orphaned file app/Image/Files/NativeLocalFile.php: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.
  • Orphaned file database/migrations/2022_10_23_143201_make_wui_settings_public.php: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.
  • Orphaned file resources/js/embed/config.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.
  • Orphaned file app/Actions/Photo/Rotate.php: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.
  • Orphaned file resources/js/embed/api.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.
  • Orphaned file resources/js/embed/utils/columns.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.
  • Orphaned file app/Casts/DateTimeWithTimezoneCast.php: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.
  • Orphaned file database/migrations/2021_05_13_140700_refactor_size_variants.php: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.
  • Orphaned file app/Image/PlaceholderEncoder.php: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.
  • Orphaned file database/migrations/2026_02_28_000006_add_contact_form_configs.php: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.
  • Orphaned file app/Image/Handlers/GoogleMotionPictureHandler.php: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.
  • Orphaned file app/Models/Extensions/HasRandomIDAndLegacyTimeBasedID.php: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.
  • Orphaned file app/Image/Files/FlysystemFile.php: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.
  • Orphaned file app/Image/Files/BaseMediaFile.php: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.
  • Orphaned file resources/js/embed/layouts/filmstrip.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.
  • Orphaned file app/Relations/HasManySizeVariants.php: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.
  • Orphaned file app/Console/Commands/Laravel/Optimize.php: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.
  • Orphaned file app/Jobs/WebhookDispatchJob.php: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.
  • Orphaned file app/Http/Controllers/Contact/ContactController.php: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.
  • Orphaned file app/Services/SecurityAdvisoriesService.php: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.
  • Orphaned file app/Contracts/Models/SizeVariantFactory.php: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.
  • + 23 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×40
  • Duplicated predicate resources/js/composables/contextMenus/leftMenu.ts:88 — `!(route.name as string).includes("timeline") && is_timeline_page_enabled.value` appears character-identically in 2 files — resources/js/composables/contextMenus/leftMenu.ts, resources/js/v8/composables/contextMenus/leftMenu.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/composables/contextMenus/leftMenu.ts:75 — `!(route.name as string).startsWith("gallery") && user.value?.id === null` appears character-identically in 2 files — resources/js/composables/contextMenus/leftMenu.ts, resources/js/v8/composables/contextMenus/leftMenu.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/v8/composables/usePanZoom.ts:315 — `!gesture.moved && !isTap(gesture.start, point, 1)` appears character-identically in 2 files — resources/js/v8/composables/usePanZoom.ts, resources/js/v8/composables/useSphereViewer.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/composables/contextMenus/contextMenu.ts:74 — `accumulator && currentValue.rights.can_delete` appears character-identically in 2 files — resources/js/composables/contextMenus/contextMenu.ts, resources/js/v8/composables/contextMenus/contextMenu.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/composables/contextMenus/contextMenu.ts:78 — `accumulator && currentValue.rights.can_download` appears character-identically in 2 files — resources/js/composables/contextMenus/contextMenu.ts, resources/js/v8/composables/contextMenus/contextMenu.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/composables/contextMenus/contextMenu.ts:70 — `accumulator && currentValue.rights.can_move` appears character-identically in 2 files — resources/js/composables/contextMenus/contextMenu.ts, resources/js/v8/composables/contextMenus/contextMenu.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/composables/contextMenus/contextMenuAlbumAdd.ts:59 — `albumStore.rights?.can_import_from_server && albumStore.config?.is_model_album` appears character-identically in 2 files — resources/js/composables/contextMenus/contextMenuAlbumAdd.ts, resources/js/v8/composables/contextMenus/contextMenuAlbumAdd.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/services/metrics-service.ts:6 — `album_id === undefined || album_id === ALL` appears character-identically in 2 files — resources/js/services/metrics-service.ts, resources/js/services/search-service.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/composables/album/treeOperations.ts:266 — `albums.value === undefined || originalAlbums.value === undefined` appears character-identically in 2 files — resources/js/composables/album/treeOperations.ts, resources/js/v8/composables/album/treeOperations.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/stores/AlbumState.ts:209 — `error.response && error.response.status === 401` appears character-identically in 2 files — resources/js/stores/AlbumState.ts, resources/js/stores/AlbumsState.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/v8/composables/usePanZoom.ts:251 — `event.pointerType === "mouse" && event.button !== 0` appears character-identically in 2 files — resources/js/v8/composables/usePanZoom.ts, resources/js/v8/composables/useSphereViewer.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/composables/contextMenus/contextMenuAlbumAdd.ts:89 — `item.if === undefined || item.if !== false` appears character-identically in 4 files — resources/js/composables/contextMenus/contextMenuAlbumAdd.ts, resources/js/composables/contextMenus/contextMenuAlbumsAdd.ts, resources/js/v8/composables/contextMenus/contextMenuAlbumAdd.ts, resources/js/v8/composables/contextMenus/contextMenuAlbumsAdd.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/composables/album/uploadEvents.ts:96 — `items[i].type.indexOf("image") !== -1 || items[i].type.indexOf("video") !== -1` appears character-identically in 2 files — resources/js/composables/album/uploadEvents.ts, resources/js/v8/composables/album/uploadEvents.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/layouts/PhotoLayout.ts:26 — `photoListing === null || layoutState.config === undefined` appears character-identically in 2 files — resources/js/layouts/PhotoLayout.ts, resources/js/v8/layouts/PhotoLayout.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/stores/AlbumListState.ts:53 — `r.id !== target.id && r._lft < target._lft && r._rgt > target._rgt` appears character-identically in 2 files — resources/js/stores/AlbumListState.ts, resources/js/v8/composables/album/albumNavTree.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/composables/contextMenus/leftMenu.ts:140 — `rights.value.modules.is_contact_enabled && !canSeeAdmin.value` appears character-identically in 2 files — resources/js/composables/contextMenus/leftMenu.ts, resources/js/v8/composables/contextMenus/leftMenu.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/composables/contextMenus/leftMenu.ts:190 — `rights.value.modules.is_contact_enabled && canSeeAdmin.value` appears character-identically in 2 files — resources/js/composables/contextMenus/leftMenu.ts, resources/js/v8/composables/contextMenus/leftMenu.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/composables/contextMenus/leftMenu.ts:57 — `rights.value?.settings.can_edit || rights.value?.user_management.can_edit || rights.value?.settings.can_see_diagnostics || rights.value?.set…` appears character-identically in 2 files — resources/js/composables/contextMenus/leftMenu.ts, resources/js/v8/composables/contextMenus/leftMenu.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/composables/contextMenus/contextMenu.ts:138 — `selectors.album !== undefined && selectors.album.value !== undefined && (selectors.config?.value?.is_model_album === true || albumStore.tagA…` appears character-identically in 2 files — resources/js/composables/contextMenus/contextMenu.ts, resources/js/v8/composables/contextMenus/contextMenu.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/composables/contextMenus/contextMenu.ts:151 — `selectors.config?.value?.is_model_album === true && selectors.album !== undefined && selectors.album.value !== undefined` appears character-identically in 2 files — resources/js/composables/contextMenus/contextMenu.ts, resources/js/v8/composables/contextMenus/contextMenu.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/composables/contextMenus/contextMenu.ts:93 — `selectors.selectedAlbum !== undefined && selectors.selectedAlbum.value !== undefined` appears character-identically in 2 files — resources/js/composables/contextMenus/contextMenu.ts, resources/js/v8/composables/contextMenus/contextMenu.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/composables/contextMenus/contextMenu.ts:96 — `selectors.selectedAlbums !== undefined && selectors.selectedAlbums.value.length > 1` appears character-identically in 2 files — resources/js/composables/contextMenus/contextMenu.ts, resources/js/v8/composables/contextMenus/contextMenu.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/composables/contextMenus/contextMenu.ts:87 — `selectors.selectedPhoto !== undefined && selectors.selectedPhoto.value !== undefined` appears character-identically in 2 files — resources/js/composables/contextMenus/contextMenu.ts, resources/js/v8/composables/contextMenus/contextMenu.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/composables/contextMenus/contextMenu.ts:90 — `selectors.selectedPhotos !== undefined && selectors.selectedPhotos.value.length > 1` appears character-identically in 2 files — resources/js/composables/contextMenus/contextMenu.ts, resources/js/v8/composables/contextMenus/contextMenu.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/composables/album/uploadEvents.ts:52 — `upload_config.value !== undefined && upload_config.value.folder_upload_enabled === true && e.dataTransfer.items && hasDirectoryEntry(e.dataT…` appears character-identically in 2 files — resources/js/composables/album/uploadEvents.ts, resources/js/v8/composables/album/uploadEvents.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.
  • + 15 more in this group — see findings.md.
X4 · Structured logging · Interpolated log message defeats structured logging · ×40
  • Interpolated log message defeats structured logging app/Services/Image/NsfwActionService.php:47 — `warning` at line 47 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/Services/Image/NsfwActionService.php:115 — `info` at line 115 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/Services/Image/NsfwActionService.php:123 — `info` at line 123 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/Services/Image/NsfwActionService.php:130 — `info` at line 130 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/Services/Image/NsfwActionService.php:144 — `info` at line 144 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/Services/Image/NsfwActionService.php:151 — `info` at line 151 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/Services/Image/NsfwActionService.php:175 — `info` at line 175 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/Services/Image/NsfwActionService.php:195 — `info` at line 195 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/Services/Image/NsfwActionService.php:209 — `warning` at line 209 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/Services/Image/NsfwActionService.php:216 — `info` at line 216 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/Services/Image/NsfwDetectionService.php:154 — `info` at line 154 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/Listeners/RecomputeAlbumSizeOnAlbumChange.php:38 — `info` at line 38 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/Listeners/RecomputeAlbumSizeOnAlbumChange.php:59 — `info` at line 59 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/Listeners/RecomputeAlbumSizeOnPhotoMutation.php:55 — `debug` at line 55 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->debug('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::debug('order moved', ['order_id' => $orderId])` with Laravel's facade.
  • Interpolated log message defeats structured logging app/Listeners/RecomputeAlbumSizeOnPhotoMutation.php:74 — `debug` at line 74 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->debug('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::debug('order moved', ['order_id' => $orderId])` with Laravel's facade.
  • Interpolated log message defeats structured logging app/Listeners/RecomputeAlbumStatsOnAlbumChange.php:29 — `info` at line 29 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/Listeners/RecomputeAlbumStatsOnAlbumChange.php:50 — `info` at line 50 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/Listeners/RecomputeAlbumStatsOnPhotoChange.php:60 — `info` at line 60 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/Jobs/ApplyNsfwAlbumSensitivityJob.php:53 — `info` at line 53 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/Jobs/ApplyNsfwAlbumSensitivityJob.php:62 — `info` at line 62 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/Jobs/DispatchFaceScanJob.php:47 — `warning` at line 47 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/Jobs/DispatchFaceScanJob.php:53 — `warning` at line 53 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/Jobs/DispatchFaceScanJob.php:63 — `warning` at line 63 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/Jobs/DispatchFaceScanJob.php:74 — `warning` at line 74 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/Jobs/DispatchNsfwScanJob.php:41 — `warning` at line 41 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.
  • + 15 more in this group — see findings.md.
X7 · Silent fallback defaults · Pending state with no failure state · ×40
  • Pending state with no failure state resources/js/v8/views/TagsManagement.vue:85 — The view draws `{{ $t("tags.loading") }}` under `canEdit`, but `canEdit` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/views/webshop/OrderDownload.vue:10 — The view draws `<div v-if="loading" class="flex justify-center items-center p-8">` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/views/face-recog/FaceClusters.vue:188 — The view draws `<div v-if="detailHasMorePages || detailFacesLoadingMore" class="flex items-center justify-center w-24 h-24 shrink-0">` under `detailHasMorePages || detailFacesLoadingMore`, but `detailHasMorePages` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/views/face-recog/FaceMaintenance.vue:12 — The view draws `<div v-if="loading && faces.length === 0" class="flex justify-center py-12">` under `loading && faces.length === 0`, but `faces` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/views/face-recog/PersonDetail.vue:23 — The view draws `{{ person.name }} {{ person.photo_count }} {{ $t("people.photos_label") }} &bull; {{ person.face_count }} {{ $t("people.faces_label") }} {{ $t("people.not_searchable") }} { isMergeModalOpen = true; } " /> {{ $t("people.batch_selected", { count: String(selectedPhotoIds.length) }) }} {{ $t("search.no_results") }} ×` under `person`, but `person` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/views/face-recog/PersonDetail.vue:106 — The view draws `<div v-if="photos.length === 0 && photosLoading" class="flex justify-center items-center mt-10 p-4">` under `photos.length === 0 && photosLoading`, but `photos` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/views/admin/Moderation.vue:15 — The view draws `<div v-if="loading && photos.length === 0" class="flex justify-center py-12">` under `loading && photos.length === 0`, but `photos` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/views/admin/Moderation.vue:51 — The view draws `0" :data="photos" :columns="columns" sticky class="max-h-[65vh] text-sm"> toggleOne(row.original.photo_id)" /> {{ row.original.album_title }} — {{ new Date(row.original.created_at).toLocaleDateString() }} {{ $t("moderation.nsfw_review") }} 0" class="text-2xl" />` under `photos.length > 0`, but `photos` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/views/admin/Moderation.vue:111 — The view draws `0" class="text-2xl" />` under `loading && photos.length > 0`, but `photos` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/views/admin/NsfwFindings.vue:13 — The view draws `<div v-if="loading && rows.length === 0" class="flex justify-center py-12">` under `loading && rows.length === 0`, but `rows` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/views/admin/NsfwFindings.vue:39 — The view draws `0" :data="rows" :columns="columns" sticky class="max-h-[65vh] text-sm"> toggleOne(row.original.photo_id)" /> {{ row.original.title }} {{ row.original.owner_username }} {{ new Date(row.original.scanned_at).toLocaleDateString() }} {{ $t("moderation.findings_hidden") }} {{ $t("moderation.nsfw_review") }} {{ detection.label }} {{ Math.round(detection.confidence * 100) }}% 0" class="flex flex-col"> {{ album.title }} — 0" class="text-2xl" />` under `rows.length > 0`, but `rows` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/views/admin/NsfwFindings.vue:125 — The view draws `0" class="text-2xl" />` under `loading && rows.length > 0`, but `rows` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/views/admin/UserGroups.vue:28 — The view draws `{{ $t("user-groups.loading") }}` under `userGroups === undefined`, but `userGroups` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/components/modals/ImportFromServer.vue:4 — The view draws `{{ $t("import_from_server.importing_please_be_patient") }}` under `importing`, but `importing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/components/maintenance/MaintenanceBackfillAlbumSizes.vue:2 — The view draws `{{ $t("maintenance.backfill-album-sizes.title") }} {{ $t("maintenance.backfill-album-sizes.button") }}` under `data !== undefined && data !== 0`, but `data` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/components/maintenance/MaintenanceBackfillAlbumSizes.vue:5 — The view draws `<LycheeLoadingIcon fast v-if="loading" class="inline-block text-2xl" />` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/components/maintenance/MaintenanceBulkScanFaces.vue:2 — The view draws `{{ $t("people.scan_faces") }} {{ $t("people.scan_faces") }}` under `data !== undefined && data !== 0`, but `data` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/components/maintenance/MaintenanceBulkScanFaces.vue:5 — The view draws `<LycheeLoadingIcon fast v-if="loading" class="inline-block text-2xl" />` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/components/maintenance/MaintenanceCleaning.vue:2 — The view draws `{{ title }} {{ $t("maintenance.cleaning.button") }}` under `data !== undefined && data.is_not_empty`, but `data` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/components/maintenance/MaintenanceCleaning.vue:5 — The view draws `<LycheeLoadingIcon fast v-if="loading" class="inline-block text-2xl" />` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/components/maintenance/MaintenanceDestroyDismissedFaces.vue:2 — The view draws `{{ $t("maintenance.destroy-dismissed-faces.title") }} {{ $t("maintenance.destroy-dismissed-faces.action") }}` under `data !== undefined && data !== 0`, but `data` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/components/maintenance/MaintenanceDestroyDismissedFaces.vue:5 — The view draws `<LycheeLoadingIcon fast v-if="loading" class="inline-block text-2xl" />` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/components/maintenance/MaintenanceDuplicateChecker.vue:10 — The view draws `<LycheeLoadingIcon fast v-if="data === undefined && isLoaded" class="inline-block text-2xl" />` under `data === undefined && isLoaded`, but `data` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/components/maintenance/MaintenanceFilesize.vue:2 — The view draws `0"> {{ $t("maintenance.fill-filesize-sizevariants.title") }} 0 && !loading" color="primary" variant="soft" @click="exec"> {{ $t("maintenance.fill-filesize-sizevariants.button") }}` under `data !== undefined && data > 0`, but `data` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state resources/js/v8/components/maintenance/MaintenanceFilesize.vue:5 — The view draws `<LycheeLoadingIcon fast v-if="loading" class="inline-block text-2xl" />` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • + 15 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · Stale vulnerability suppression · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D24 · Comment Value · redundant comment · ×3
  • redundant comment resources/js/composables/album/buyMeActions.ts:20 — "Selected item type: 'digital' | 'print' | 'pixel'" repeats the code it sits on: 5 of its 6 words (item, type, digital, print, pixel) are already in `const buyMeItemType = ref<"digital" | "print" | "pixel">("digital");`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment resources/js/stores/PhotosState.ts:154 — "Connect the last old photo to the first new photo" repeats the code it sits on: 5 of its 6 words (last, old, photo, first, new) are already in `lastOldPhoto.next_photo_id = firstNewPhoto.id;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment resources/js/stores/PhotosState.ts:218 — "Connect the last prepended photo to the first existing photo" repeats the code it sits on: 5 of its 6 words (last, prepended, photo, first, existing) are already in `lastPrependedPhoto.next_photo_id = firstExistingPhoto.id;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D13 · REDACTED Scanning · REDACTED
  • REDACTED
  • REDACTED
D28 · Secrets (history) · REDACTED · ×2
  • REDACTED
  • REDACTED
M4 · Documentation accuracy · README/code drift · ×2
  • README/code drift docs/specs/4-architecture/features/012-embeds/IMPLEMENTATION.md:75 — docs/specs/4-architecture/features/012-embeds/IMPLEMENTATION.md names TypeScript 5, but the manifest declares `typescript` ^6.0.3. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/specs/4-architecture/features/012-embeds/README.md:80 — docs/specs/4-architecture/features/012-embeds/README.md names TypeScript 5, but the manifest declares `typescript` ^6.0.3. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
C2 · Access Controls · Anonymous-heavy surface · ×1
  • Anonymous-heavy surface — Public opt-outs and open tables (6) outweigh guarded routes and protected tables (4) — review whether the open surface is intended.
C4 · Data Retention · Partial data-retention evidence · ×1
  • Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: an expiry limit — a declared maximum age / TTL after which the data is no longer kept, a documented retention period / data-expiry.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 125 significant file(s) lose their only recent owner: app/Policies/AlbumQueryPolicy.php, app/Policies/AlbumPolicy.php, app/Services/Cache/CacheKeyProvider.php, routes/api_v2.php, app/Http/Resources/GalleryConfigs/InitConfig.php, app/Models/Album.php, app/Exceptions/Handler.php, resources/js/composables/album/dragAndSelect.ts (+117 more). Pair on, review, or document these before any departure.
D20 · ADR Quality · ADR decides a question another record already decided · ×1
  • ADR decides a question another record already decided docs/specs/6-decisions/ADR-102-01-direct-tile-urls.md:1 — docs/specs/6-decisions/ADR-102-01-direct-tile-urls.md and docs/specs/6-decisions/ADR-093-01-face-scoped-photo-asset-route.md are both in force and decide the same subject two ways: "This is the same rule as the queue" against "with the same rules as the album's other /Photos tiers", and neither names the other. If this record replaces the earlier one, say so ("Supersedes …") and mark the earlier one superseded; if both hold, state how they relate.
D27 · Navigability · Scattered collaborators · ×1
  • Scattered collaborators — 64 % of calls cross a namespace and only 13 % of collaborators are co-located — group each feature's code into a vertical slice so a call's collaborators sit together.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Low CVE · ×1
  • REDACTED
D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1
  • Further orphaned files (smaller) — 48 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: app/Models/Extensions/ForwardsToParentImplementation.php, app/Services/Auth/SessionOrTokenGuard.php, app/Models/Extensions/UTCBasedTimes.php, app/Image/Files/NativeLocalFile.php, app/Actions/Photo/Rotate.php, resources/js/embed/utils/columns.ts, app/Casts/DateTimeWithTimezoneCast.php, app/Image/PlaceholderEncoder.php (and 40 more) (50 orphaned of 645 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 645 of the 2627 production source files in this repository met that bar). 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
P3 · Security & performance tooling · Dependabot does not watch gitsubmodule · ×1
  • Dependabot does not watch gitsubmodule REDACTED:2 — `REDACTED` schedules updates, but no `package-ecosystem` entry covers `gitsubmodule`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list.
P4 · Deployment & Rollback · No release approval gate · ×1
  • No release approval gate .github/workflows/docker_build.yml:97 — Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
R7 · Dead Code · Unused export 'calculateColumns' · ×1
  • Unused export 'calculateColumns' resources/js/embed/utils/columns.ts:28 — Nothing ultimately consumes this binding: its only referrer is the re-export in resources/js/embed/main.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/embed/main.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'calculateColumnsFromBreakpoints' · ×1
  • Unused export 'calculateColumnsFromBreakpoints' resources/js/embed/utils/columns.ts:74 — Nothing ultimately consumes this binding: its only referrer is the re-export in resources/js/embed/main.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/embed/main.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'distributeColumnWidths' · ×1
  • Unused export 'distributeColumnWidths' resources/js/embed/utils/columns.ts:99 — Nothing ultimately consumes this binding: its only referrer is the re-export in resources/js/embed/main.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/embed/main.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'calculateJustifiedRowHeight' · ×1
  • Unused export 'calculateJustifiedRowHeight' resources/js/embed/utils/columns.ts:129 — Nothing ultimately consumes this binding: its only referrer is the re-export in resources/js/embed/main.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/embed/main.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'PhotoFavourite' · ×1
  • Unused export 'PhotoFavourite' resources/js/stores/FavouriteState.ts:6 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'FlowStateStore' · ×1
  • Unused export 'FlowStateStore' resources/js/stores/FlowState.ts:8 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'ImportState' · ×1
  • Unused export 'ImportState' resources/js/stores/ImportState.ts:4 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'MapStore' · ×1
  • Unused export 'MapStore' resources/js/stores/MapState.ts:60 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'NsfwConsentedStore' · ×1
  • Unused export 'NsfwConsentedStore' resources/js/stores/NsfwConsentedState.ts:3 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'SearchStore' · ×1
  • Unused export 'SearchStore' resources/js/stores/SearchState.ts:14 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'ShopManagementStateStore' · ×1
  • Unused export 'ShopManagementStateStore' resources/js/stores/ShopManagement.ts:5 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'TagStore' · ×1
  • Unused export 'TagStore' resources/js/stores/TagState.ts:5 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'TileUrlsStore' · ×1
  • Unused export 'TileUrlsStore' resources/js/stores/TileUrlsState.ts:15 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'isApple' · ×1
  • Unused export 'isApple' resources/js/utils/keybindings-utils.ts:44 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'vsprintf' · ×1
  • Unused export 'vsprintf' resources/js/utils/sprintf.ts:78 — Nothing imports this binding — it is safe to review for removal.
S1 · Web-Security Posture · No security response headers detected · ×1
  • No security response headers detected REDACTED:58 — 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` is committed to this repository and declares the server that serves it, 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/4 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X23 · Unguarded diagnostic materialisation · Diagnostic log message is built whether or not it is wanted · ×1
  • Diagnostic log message is built whether or not it is wanted app/Services/Auth/LdapService.php:308 — `debug` at line 308 is called with an argument built by `array_keys($result)` (line 312), whose cost grows with the collection it walks. PHP evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isHandling` test, no debug flag, and no placeholder context array that lets the logger build the text only when the level is on.
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.
X6 · Hand-rolled structured-format parsing · Hand-rolled JSON/XML parsing via regex · ×1
  • Hand-rolled JSON/XML parsing via regex app/Actions/Diagnostics/Pipes/Checks/ImagickPdfCheck.php:76 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This PHP code already uses a real parser in the same package; use it here too.
Minor — 6 finding(s)
D12 · Dependency Hygiene · Outdated · ×5
  • Outdated: dedoc/scramble — `dedoc/scramble` is locked at v0.13.54 but v0.13.55 is the current stable release on Packagist, and it already satisfies the `^0.13.1` constraint declared in composer.json — so the lockfile is behind this repository's own declared range. Run `composer update dedoc/scramble` and commit the updated composer.lock.
  • Outdated: directorytree/ldaprecord-laravel — `directorytree/ldaprecord-laravel` is locked at v4.0.5 but v4.0.6 is the current stable release on Packagist, and it already satisfies the `^4.0.0` constraint declared in composer.json — so the lockfile is behind this repository's own declared range. Run `composer update directorytree/ldaprecord-laravel` and commit the updated composer.lock.
  • Outdated: laravel/framework — `laravel/framework` is locked at v13.42.0 but v13.43.0 is the current stable release on Packagist, and it already satisfies the `^13.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/octane — `laravel/octane` is locked at v2.24.0 but v2.25.0 is the current stable release on Packagist, and it already satisfies the `^2.13` constraint declared in composer.json — so the lockfile is behind this repository's own declared range. Run `composer update laravel/octane` and commit the updated composer.lock.
  • Outdated: laravel/socialite — `laravel/socialite` is locked at v5.32.0 but v5.33.0 is the current stable release on Packagist, and it already satisfies the `^5.18` 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.
D24 · Comment Value · doc comments repeat the names · ×1
  • doc comments repeat the names resources/js/embed/api.ts:218 — 1 of 120 documented parameters and 6 of 667 summaries in `lychee` only repeat the member or parameter name (e.g. "Create a new API client instance" for `createApiClient`). Delete the restating tags, or add what the name does not say.

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/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-3acca3091e2c429ca574d8e206bf5a57/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-3acca3091e2c429ca574d8e206bf5a57/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=1962" --report-format json --report-path /tmp/watchdog-gitleaks-3acca3091e2c429ca574d8e206bf5a57/history-2.json --exit-code 0 --source .2artifacts/raw/gitleaks-history-2.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-3acca3091e2c429ca574d8e206bf5a57/tree.json --exit-code 0 --source .2artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude phpstan --exclude public/installer/assets/css --exclude resources/sass --exclude resources/views/vendor/mail .9artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .7artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .12artifacts/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 137 file(s) — `app/Actions/Album/Breadcrumb.php`, `app/Actions/Album/Create.php`, `app/Actions/Album/ListAlbums.php`, `app/Actions/Album/StructOfArrays/QueryChildrenForAlbum.php`, `app/Actions/Album/StructOfArrays/QueryChildrenForPerson.php`, … (+132 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/** .0artifacts/raw/trivy-fs.json

Run 01a1ea66-4b28-7f59-802e-69b31309adc4 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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