Executive summary
ranky/media-bundle is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no access checks on the code's endpoints or handlers and 29 of the dependencies have a known vulnerability. It scores 39 out of 100, which the At risk rating leaves unchanged.
Security and Compliance, at 24, is the weakest lens and counts most in the score. The best first step is adding access checks, worth about 12 points. Updating the 29 dependencies with a known vulnerability comes next, worth about 4 points. Raising Security and Compliance to 70 would lift the score to about 50.
Thirty-three known security holes in the packages the code depends on can be used by attackers. Thirteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and seven form fields can't be read by a screen reader. Updating the vulnerable packages, pinning each tool to an exact version and labelling the form fields would close these risks. Limiting each secret to its own step would fix the three secrets exposed to more of the pipeline than needed, and the password or key in the code's history needs replacing, with the old one switched off. The button or link with no name needs a name, even when it only shows an icon.
The product code is 9,165 lines, about €15,000 to rebuild.
If Security and Compliance rose from 24 to 70, the lowest score rated Strong, the score would rise from 39 to about 50.
New since the last survey: 5 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Access Controls · No authorization src/Presentation/BackOffice/EmbedMediaBackOfficeController.php
Fixed since the last survey: 9 findings
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Access Controls · No authorization src/Presentation/Api/UploadMediaApiController.php
- Visual & motion safety · Animation without a prefers-reduced-motion guard assets/src/styles/media.scss
- Visual & motion safety · Animation without a prefers-reduced-motion guard assets/src/styles/water.scss
- Visual & motion safety · Animation without a prefers-reduced-motion guard assets/src/components/Common/Loader/loader.scss
- Visual & motion safety · Animation without a prefers-reduced-motion guard assets/src/components/Common/Loader/loader.scss
Rebuild cost: about €15,000 · Estimate
| Cost to rebuild | €4,900 to €25,000, for 82 to 260 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, 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 39. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 9,165 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 Ranky.MediaBundle.Domain.Criteria | 2 Ranky.MediaBundle.Domain.Event | 3 Ranky.MediaBundle.Domain.ValueObject | 4 assets.src.api.model.ApiProblemError | 5 assets.src.api.repository.BaseRepository | 6 Ranky.MediaBundle.Domain.Model | 7 Ranky.MediaBundle.Domain.Service | 8 assets.src.api.repository.MediaRepository | 9 App.Entity | 10 Ranky.MediaBundle.Application.DataTransformer.Response | 11 Ranky.MediaBundle.Application.FileManipulation.CompressFile | 12 Ranky.MediaBundle.Application.DataTransformer | 13 Ranky.MediaBundle.Application.CreateMedia | 14 Ranky.MediaBundle.Domain.Contract | 15 Ranky.MediaBundle.Infrastructure.Validation | 16 Ranky.MediaBundle.Application.FileManipulation.Thumbnails.DeleteThumbnails | 17 Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails | 18 Ranky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails | 19 Ranky.MediaBundle.Application.FindMedia | 20 Ranky.MediaBundle.Application.GetMedia | 21 Ranky.MediaBundle.Application.ListFilter.ListAvailableDatesFilter | 22 Ranky.MediaBundle.Application.ListFilter.ListMimeFilter | 23 Ranky.MediaBundle.Application.ListFilter.ListUserFilter | 24 Ranky.MediaBundle.Application.ListMediaCriteria | 25 Ranky.MediaBundle.Application.SafeFileName | 26 Ranky.MediaBundle.Application.UpdateMedia | 27 Ranky.MediaBundle.Infrastructure.FileManipulation.Compression | 28 Ranky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize | 29 Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository | 30 Ranky.MediaBundle.Presentation.Form | 31 Ranky.MediaBundle.Presentation.Form.DataTransformer | 32 Ranky.MediaBundle.Presentation.Twig | 33 App.Repository | 34 Ranky.MediaBundle.Application | 35 Ranky.MediaBundle.Application.DeleteMedia | 36 Ranky.MediaBundle.Application.FileManipulation.RenameFile | 37 Ranky.MediaBundle.Application.ListFilter | 38 Ranky.MediaBundle.Infrastructure.Event | 39 Ranky.MediaBundle.Infrastructure.Filesystem.Local | 40 Ranky.MediaBundle.Presentation.Api |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Ranky.MediaBundle.Domain.Criteria | ||||||||||||||||||||||||||||||||||||||||
| 2 Ranky.MediaBundle.Domain.Event | ||||||||||||||||||||||||||||||||||||||||
| 3 Ranky.MediaBundle.Domain.ValueObject | ||||||||||||||||||||||||||||||||||||||||
| 4 assets.src.api.model.ApiProblemError | ||||||||||||||||||||||||||||||||||||||||
| 5 assets.src.api.repository.BaseRepository | ||||||||||||||||||||||||||||||||||||||||
| 6 Ranky.MediaBundle.Domain.Model | 10 | |||||||||||||||||||||||||||||||||||||||
| 7 Ranky.MediaBundle.Domain.Service | 4 | |||||||||||||||||||||||||||||||||||||||
| 8 assets.src.api.repository.MediaRepository | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 App.Entity | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 Ranky.MediaBundle.Application.DataTransformer.Response | 5 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 Ranky.MediaBundle.Application.FileManipulation.CompressFile | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 12 Ranky.MediaBundle.Application.DataTransformer | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 13 Ranky.MediaBundle.Application.CreateMedia | 2 | 1 | 1 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||||
| 14 Ranky.MediaBundle.Domain.Contract | 7 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 15 Ranky.MediaBundle.Infrastructure.Validation | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 Ranky.MediaBundle.Application.FileManipulation.Thumbnails.DeleteThumbnails | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails | 5 | 1 | 6 | |||||||||||||||||||||||||||||||||||||
| 18 Ranky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 19 Ranky.MediaBundle.Application.FindMedia | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 20 Ranky.MediaBundle.Application.GetMedia | 3 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 21 Ranky.MediaBundle.Application.ListFilter.ListAvailableDatesFilter | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 Ranky.MediaBundle.Application.ListFilter.ListMimeFilter | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 Ranky.MediaBundle.Application.ListFilter.ListUserFilter | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 Ranky.MediaBundle.Application.ListMediaCriteria | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 Ranky.MediaBundle.Application.SafeFileName | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 Ranky.MediaBundle.Application.UpdateMedia | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 Ranky.MediaBundle.Infrastructure.FileManipulation.Compression | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 28 Ranky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize | 8 | 4 | ||||||||||||||||||||||||||||||||||||||
| 29 Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 30 Ranky.MediaBundle.Presentation.Form | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 Ranky.MediaBundle.Presentation.Form.DataTransformer | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 32 Ranky.MediaBundle.Presentation.Twig | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 App.Repository | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 Ranky.MediaBundle.Application | 1 | 1 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 35 Ranky.MediaBundle.Application.DeleteMedia | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 Ranky.MediaBundle.Application.FileManipulation.RenameFile | 3 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 Ranky.MediaBundle.Application.ListFilter | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 Ranky.MediaBundle.Infrastructure.Event | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 Ranky.MediaBundle.Infrastructure.Filesystem.Local | 2 | 1 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 Ranky.MediaBundle.Presentation.Api | 1 | 2 | 1 | 1 | 1 | 2 | 1 | 1 |
6→3 Ranky.MediaBundle.Domain.Model uses Ranky.MediaBundle.Domain.ValueObject✕
- Connections
- 10 pairs of types, where a type in Ranky.MediaBundle.Domain.Model uses a type in Ranky.MediaBundle.Domain.ValueObject.
- The types involved
Ranky.MediaBundle.Domain.Model.Media→Ranky.MediaBundle.Domain.ValueObject.DescriptionRanky.MediaBundle.Domain.Model.Media→Ranky.MediaBundle.Domain.ValueObject.DimensionRanky.MediaBundle.Domain.Model.Media→Ranky.MediaBundle.Domain.ValueObject.FileRanky.MediaBundle.Domain.Model.Media→Ranky.MediaBundle.Domain.ValueObject.MediaIdRanky.MediaBundle.Domain.Model.Media→Ranky.MediaBundle.Domain.ValueObject.ThumbnailsRanky.MediaBundle.Domain.Model.MediaInterface→Ranky.MediaBundle.Domain.ValueObject.DescriptionRanky.MediaBundle.Domain.Model.MediaInterface→Ranky.MediaBundle.Domain.ValueObject.DimensionRanky.MediaBundle.Domain.Model.MediaInterface→Ranky.MediaBundle.Domain.ValueObject.FileRanky.MediaBundle.Domain.Model.MediaInterface→Ranky.MediaBundle.Domain.ValueObject.MediaIdRanky.MediaBundle.Domain.Model.MediaInterface→Ranky.MediaBundle.Domain.ValueObject.Thumbnails
- Direction
- Ranky.MediaBundle.Domain.Model uses Ranky.MediaBundle.Domain.ValueObject, so a change to Ranky.MediaBundle.Domain.ValueObject can break Ranky.MediaBundle.Domain.Model, while a change to Ranky.MediaBundle.Domain.Model can't break Ranky.MediaBundle.Domain.ValueObject.
- Position
- Below the diagonal: Ranky.MediaBundle.Domain.Model uses a module listed above it, which is the healthy direction.
7→3 Ranky.MediaBundle.Domain.Service uses Ranky.MediaBundle.Domain.ValueObject✕
- Connections
- 4 pairs of types, where a type in Ranky.MediaBundle.Domain.Service uses a type in Ranky.MediaBundle.Domain.ValueObject.
- The types involved
Ranky.MediaBundle.Domain.Service.FileCompressHandler→Ranky.MediaBundle.Domain.ValueObject.FileRanky.MediaBundle.Domain.Service.FileResizeHandler→Ranky.MediaBundle.Domain.ValueObject.DimensionRanky.MediaBundle.Domain.Service.FileResizeHandler→Ranky.MediaBundle.Domain.ValueObject.FileRanky.MediaBundle.Domain.Service.GenerateThumbnailsHandler→Ranky.MediaBundle.Domain.ValueObject.File
- Direction
- Ranky.MediaBundle.Domain.Service uses Ranky.MediaBundle.Domain.ValueObject, so a change to Ranky.MediaBundle.Domain.ValueObject can break Ranky.MediaBundle.Domain.Service, while a change to Ranky.MediaBundle.Domain.Service can't break Ranky.MediaBundle.Domain.ValueObject.
- Position
- Below the diagonal: Ranky.MediaBundle.Domain.Service uses a module listed above it, which is the healthy direction.
8→5 assets.src.api.repository.MediaRepository uses assets.src.api.repository.BaseRepository✕
- Connections
- 1 pair of types, where a type in assets.src.api.repository.MediaRepository uses a type in assets.src.api.repository.BaseRepository.
- The types involved
assets.src.api.repository.MediaRepository.MediaRepository→assets.src.api.repository.BaseRepository.BaseRepository
- Direction
- assets.src.api.repository.MediaRepository uses assets.src.api.repository.BaseRepository, so a change to assets.src.api.repository.BaseRepository can break assets.src.api.repository.MediaRepository, while a change to assets.src.api.repository.MediaRepository can't break assets.src.api.repository.BaseRepository.
- Position
- Below the diagonal: assets.src.api.repository.MediaRepository uses a module listed above it, which is the healthy direction.
9→6 App.Entity uses Ranky.MediaBundle.Domain.Model✕
- Connections
- 1 pair of types, where a type in App.Entity uses a type in Ranky.MediaBundle.Domain.Model.
- The types involved
App.Entity.Media→Ranky.MediaBundle.Domain.Model.Media
- Direction
- App.Entity uses Ranky.MediaBundle.Domain.Model, so a change to Ranky.MediaBundle.Domain.Model can break App.Entity, while a change to App.Entity can't break Ranky.MediaBundle.Domain.Model.
- Position
- Below the diagonal: App.Entity uses a module listed above it, which is the healthy direction.
10→3 Ranky.MediaBundle.Application.DataTransformer.Response uses Ranky.MediaBundle.Domain.ValueObject✕
- Connections
- 5 pairs of types, where a type in Ranky.MediaBundle.Application.DataTransformer.Response uses a type in Ranky.MediaBundle.Domain.ValueObject.
- The types involved
Ranky.MediaBundle.Application.DataTransformer.Response.DescriptionResponse→Ranky.MediaBundle.Domain.ValueObject.DescriptionRanky.MediaBundle.Application.DataTransformer.Response.DimensionResponse→Ranky.MediaBundle.Domain.ValueObject.DimensionRanky.MediaBundle.Application.DataTransformer.Response.FileResponse→Ranky.MediaBundle.Domain.ValueObject.FileRanky.MediaBundle.Application.DataTransformer.Response.ThumbnailResponse→Ranky.MediaBundle.Domain.ValueObject.ThumbnailRanky.MediaBundle.Application.DataTransformer.Response.ThumbnailsResponse→Ranky.MediaBundle.Domain.ValueObject.Thumbnails
- Direction
- Ranky.MediaBundle.Application.DataTransformer.Response uses Ranky.MediaBundle.Domain.ValueObject, so a change to Ranky.MediaBundle.Domain.ValueObject can break Ranky.MediaBundle.Application.DataTransformer.Response, while a change to Ranky.MediaBundle.Application.DataTransformer.Response can't break Ranky.MediaBundle.Domain.ValueObject.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.DataTransformer.Response uses a module listed above it, which is the healthy direction.
10→6 Ranky.MediaBundle.Application.DataTransformer.Response uses Ranky.MediaBundle.Domain.Model✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.DataTransformer.Response uses a type in Ranky.MediaBundle.Domain.Model.
- The types involved
Ranky.MediaBundle.Application.DataTransformer.Response.MediaResponse→Ranky.MediaBundle.Domain.Model.MediaInterface
- Direction
- Ranky.MediaBundle.Application.DataTransformer.Response uses Ranky.MediaBundle.Domain.Model, so a change to Ranky.MediaBundle.Domain.Model can break Ranky.MediaBundle.Application.DataTransformer.Response, while a change to Ranky.MediaBundle.Application.DataTransformer.Response can't break Ranky.MediaBundle.Domain.Model.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.DataTransformer.Response uses a module listed above it, which is the healthy direction.
11→7 Ranky.MediaBundle.Application.FileManipulation.CompressFile uses Ranky.MediaBundle.Domain.Service✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.FileManipulation.CompressFile uses a type in Ranky.MediaBundle.Domain.Service.
- The types involved
Ranky.MediaBundle.Application.FileManipulation.CompressFile.CompressFile→Ranky.MediaBundle.Domain.Service.FileCompressHandler
- Direction
- Ranky.MediaBundle.Application.FileManipulation.CompressFile uses Ranky.MediaBundle.Domain.Service, so a change to Ranky.MediaBundle.Domain.Service can break Ranky.MediaBundle.Application.FileManipulation.CompressFile, while a change to Ranky.MediaBundle.Application.FileManipulation.CompressFile can't break Ranky.MediaBundle.Domain.Service.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.FileManipulation.CompressFile uses a module listed above it, which is the healthy direction.
11→14 Ranky.MediaBundle.Application.FileManipulation.CompressFile uses Ranky.MediaBundle.Domain.Contract part of a loop✕
- Connections
- 3 pairs of types, where a type in Ranky.MediaBundle.Application.FileManipulation.CompressFile uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Application.FileManipulation.CompressFile.CompressFile→Ranky.MediaBundle.Domain.Contract.FilePathResolverInterfaceRanky.MediaBundle.Application.FileManipulation.CompressFile.CompressFile→Ranky.MediaBundle.Domain.Contract.FileRepositoryInterfaceRanky.MediaBundle.Application.FileManipulation.CompressFile.CompressFile→Ranky.MediaBundle.Domain.Contract.MediaRepositoryInterface
- Direction
- Ranky.MediaBundle.Application.FileManipulation.CompressFile uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Application.FileManipulation.CompressFile, while a change to Ranky.MediaBundle.Application.FileManipulation.CompressFile can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→6 Ranky.MediaBundle.Application.DataTransformer uses Ranky.MediaBundle.Domain.Model✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.DataTransformer uses a type in Ranky.MediaBundle.Domain.Model.
- The types involved
Ranky.MediaBundle.Application.DataTransformer.MediaToResponseTransformer→Ranky.MediaBundle.Domain.Model.MediaInterface
- Direction
- Ranky.MediaBundle.Application.DataTransformer uses Ranky.MediaBundle.Domain.Model, so a change to Ranky.MediaBundle.Domain.Model can break Ranky.MediaBundle.Application.DataTransformer, while a change to Ranky.MediaBundle.Application.DataTransformer can't break Ranky.MediaBundle.Domain.Model.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.DataTransformer uses a module listed above it, which is the healthy direction.
12→10 Ranky.MediaBundle.Application.DataTransformer uses Ranky.MediaBundle.Application.DataTransformer.Response✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.DataTransformer uses a type in Ranky.MediaBundle.Application.DataTransformer.Response.
- The types involved
Ranky.MediaBundle.Application.DataTransformer.MediaToResponseTransformer→Ranky.MediaBundle.Application.DataTransformer.Response.MediaResponse
- Direction
- Ranky.MediaBundle.Application.DataTransformer uses Ranky.MediaBundle.Application.DataTransformer.Response, so a change to Ranky.MediaBundle.Application.DataTransformer.Response can break Ranky.MediaBundle.Application.DataTransformer, while a change to Ranky.MediaBundle.Application.DataTransformer can't break Ranky.MediaBundle.Application.DataTransformer.Response.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.DataTransformer uses a module listed above it, which is the healthy direction.
12→14 Ranky.MediaBundle.Application.DataTransformer uses Ranky.MediaBundle.Domain.Contract part of a loop✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.DataTransformer uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Application.DataTransformer.MediaToResponseTransformer→Ranky.MediaBundle.Domain.Contract.UserMediaRepositoryInterface
- Direction
- Ranky.MediaBundle.Application.DataTransformer uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Application.DataTransformer, while a change to Ranky.MediaBundle.Application.DataTransformer can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→2 Ranky.MediaBundle.Application.CreateMedia uses Ranky.MediaBundle.Domain.Event✕
- Connections
- 2 pairs of types, where a type in Ranky.MediaBundle.Application.CreateMedia uses a type in Ranky.MediaBundle.Domain.Event.
- The types involved
Ranky.MediaBundle.Application.CreateMedia.FileCompressOnMediaCreated→Ranky.MediaBundle.Domain.Event.MediaCreatedRanky.MediaBundle.Application.CreateMedia.GenerateThumbnailsOnMediaCreated→Ranky.MediaBundle.Domain.Event.MediaCreated
- Direction
- Ranky.MediaBundle.Application.CreateMedia uses Ranky.MediaBundle.Domain.Event, so a change to Ranky.MediaBundle.Domain.Event can break Ranky.MediaBundle.Application.CreateMedia, while a change to Ranky.MediaBundle.Application.CreateMedia can't break Ranky.MediaBundle.Domain.Event.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.CreateMedia uses a module listed above it, which is the healthy direction.
13→7 Ranky.MediaBundle.Application.CreateMedia uses Ranky.MediaBundle.Domain.Service✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.CreateMedia uses a type in Ranky.MediaBundle.Domain.Service.
- The types involved
Ranky.MediaBundle.Application.CreateMedia.GenerateThumbnailsOnMediaCreated→Ranky.MediaBundle.Domain.Service.GenerateThumbnailsHandler
- Direction
- Ranky.MediaBundle.Application.CreateMedia uses Ranky.MediaBundle.Domain.Service, so a change to Ranky.MediaBundle.Domain.Service can break Ranky.MediaBundle.Application.CreateMedia, while a change to Ranky.MediaBundle.Application.CreateMedia can't break Ranky.MediaBundle.Domain.Service.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.CreateMedia uses a module listed above it, which is the healthy direction.
13→10 Ranky.MediaBundle.Application.CreateMedia uses Ranky.MediaBundle.Application.DataTransformer.Response✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.CreateMedia uses a type in Ranky.MediaBundle.Application.DataTransformer.Response.
- The types involved
Ranky.MediaBundle.Application.CreateMedia.CreateMedia→Ranky.MediaBundle.Application.DataTransformer.Response.MediaResponse
- Direction
- Ranky.MediaBundle.Application.CreateMedia uses Ranky.MediaBundle.Application.DataTransformer.Response, so a change to Ranky.MediaBundle.Application.DataTransformer.Response can break Ranky.MediaBundle.Application.CreateMedia, while a change to Ranky.MediaBundle.Application.CreateMedia can't break Ranky.MediaBundle.Application.DataTransformer.Response.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.CreateMedia uses a module listed above it, which is the healthy direction.
13→11 Ranky.MediaBundle.Application.CreateMedia uses Ranky.MediaBundle.Application.FileManipulation.CompressFile✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.CreateMedia uses a type in Ranky.MediaBundle.Application.FileManipulation.CompressFile.
- The types involved
Ranky.MediaBundle.Application.CreateMedia.FileCompressOnMediaCreated→Ranky.MediaBundle.Application.FileManipulation.CompressFile.CompressFile
- Direction
- Ranky.MediaBundle.Application.CreateMedia uses Ranky.MediaBundle.Application.FileManipulation.CompressFile, so a change to Ranky.MediaBundle.Application.FileManipulation.CompressFile can break Ranky.MediaBundle.Application.CreateMedia, while a change to Ranky.MediaBundle.Application.CreateMedia can't break Ranky.MediaBundle.Application.FileManipulation.CompressFile.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.CreateMedia uses a module listed above it, which is the healthy direction.
13→12 Ranky.MediaBundle.Application.CreateMedia uses Ranky.MediaBundle.Application.DataTransformer✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.CreateMedia uses a type in Ranky.MediaBundle.Application.DataTransformer.
- The types involved
Ranky.MediaBundle.Application.CreateMedia.CreateMedia→Ranky.MediaBundle.Application.DataTransformer.MediaToResponseTransformer
- Direction
- Ranky.MediaBundle.Application.CreateMedia uses Ranky.MediaBundle.Application.DataTransformer, so a change to Ranky.MediaBundle.Application.DataTransformer can break Ranky.MediaBundle.Application.CreateMedia, while a change to Ranky.MediaBundle.Application.CreateMedia can't break Ranky.MediaBundle.Application.DataTransformer.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.CreateMedia uses a module listed above it, which is the healthy direction.
13→14 Ranky.MediaBundle.Application.CreateMedia uses Ranky.MediaBundle.Domain.Contract part of a loop✕
- Connections
- 4 pairs of types, where a type in Ranky.MediaBundle.Application.CreateMedia uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Application.CreateMedia.CreateMedia→Ranky.MediaBundle.Domain.Contract.FilePathResolverInterfaceRanky.MediaBundle.Application.CreateMedia.CreateMedia→Ranky.MediaBundle.Domain.Contract.FileRepositoryInterfaceRanky.MediaBundle.Application.CreateMedia.CreateMedia→Ranky.MediaBundle.Domain.Contract.MediaRepositoryInterfaceRanky.MediaBundle.Application.CreateMedia.GenerateThumbnailsOnMediaCreated→Ranky.MediaBundle.Domain.Contract.MediaRepositoryInterface
- Direction
- Ranky.MediaBundle.Application.CreateMedia uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Application.CreateMedia, while a change to Ranky.MediaBundle.Application.CreateMedia can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→3 Ranky.MediaBundle.Domain.Contract uses Ranky.MediaBundle.Domain.ValueObject✕
- Connections
- 7 pairs of types, where a type in Ranky.MediaBundle.Domain.Contract uses a type in Ranky.MediaBundle.Domain.ValueObject.
- The types involved
Ranky.MediaBundle.Domain.Contract.FileCompressInterface→Ranky.MediaBundle.Domain.ValueObject.FileRanky.MediaBundle.Domain.Contract.FileRepositoryInterface→Ranky.MediaBundle.Domain.ValueObject.DimensionRanky.MediaBundle.Domain.Contract.FileRepositoryInterface→Ranky.MediaBundle.Domain.ValueObject.FileRanky.MediaBundle.Domain.Contract.FileResizeInterface→Ranky.MediaBundle.Domain.ValueObject.DimensionRanky.MediaBundle.Domain.Contract.FileResizeInterface→Ranky.MediaBundle.Domain.ValueObject.FileRanky.MediaBundle.Domain.Contract.GenerateThumbnailsInterface→Ranky.MediaBundle.Domain.ValueObject.FileRanky.MediaBundle.Domain.Contract.MediaRepositoryInterface→Ranky.MediaBundle.Domain.ValueObject.MediaId
- Direction
- Ranky.MediaBundle.Domain.Contract uses Ranky.MediaBundle.Domain.ValueObject, so a change to Ranky.MediaBundle.Domain.ValueObject can break Ranky.MediaBundle.Domain.Contract, while a change to Ranky.MediaBundle.Domain.Contract can't break Ranky.MediaBundle.Domain.ValueObject.
- Position
- Below the diagonal: Ranky.MediaBundle.Domain.Contract uses a module listed above it, which is the healthy direction.
14→6 Ranky.MediaBundle.Domain.Contract uses Ranky.MediaBundle.Domain.Model✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Domain.Contract uses a type in Ranky.MediaBundle.Domain.Model.
- The types involved
Ranky.MediaBundle.Domain.Contract.MediaRepositoryInterface→Ranky.MediaBundle.Domain.Model.MediaInterface
- Direction
- Ranky.MediaBundle.Domain.Contract uses Ranky.MediaBundle.Domain.Model, so a change to Ranky.MediaBundle.Domain.Model can break Ranky.MediaBundle.Domain.Contract, while a change to Ranky.MediaBundle.Domain.Contract can't break Ranky.MediaBundle.Domain.Model.
- Position
- Below the diagonal: Ranky.MediaBundle.Domain.Contract uses a module listed above it, which is the healthy direction.
14→13 Ranky.MediaBundle.Domain.Contract uses Ranky.MediaBundle.Application.CreateMedia✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Domain.Contract uses a type in Ranky.MediaBundle.Application.CreateMedia.
- The types involved
Ranky.MediaBundle.Domain.Contract.FileRepositoryInterface→Ranky.MediaBundle.Application.CreateMedia.UploadedFileRequest
- Direction
- Ranky.MediaBundle.Domain.Contract uses Ranky.MediaBundle.Application.CreateMedia, so a change to Ranky.MediaBundle.Application.CreateMedia can break Ranky.MediaBundle.Domain.Contract, while a change to Ranky.MediaBundle.Domain.Contract can't break Ranky.MediaBundle.Application.CreateMedia.
- Position
- Below the diagonal: Ranky.MediaBundle.Domain.Contract uses a module listed above it, which is the healthy direction.
15→13 Ranky.MediaBundle.Infrastructure.Validation uses Ranky.MediaBundle.Application.CreateMedia✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Infrastructure.Validation uses a type in Ranky.MediaBundle.Application.CreateMedia.
- The types involved
Ranky.MediaBundle.Infrastructure.Validation.UploadedFileValidator→Ranky.MediaBundle.Application.CreateMedia.UploadedFileRequest
- Direction
- Ranky.MediaBundle.Infrastructure.Validation uses Ranky.MediaBundle.Application.CreateMedia, so a change to Ranky.MediaBundle.Application.CreateMedia can break Ranky.MediaBundle.Infrastructure.Validation, while a change to Ranky.MediaBundle.Infrastructure.Validation can't break Ranky.MediaBundle.Application.CreateMedia.
- Position
- Below the diagonal: Ranky.MediaBundle.Infrastructure.Validation uses a module listed above it, which is the healthy direction.
16→14 Ranky.MediaBundle.Application.FileManipulation.Thumbnails.DeleteThumbnails uses Ranky.MediaBundle.Domain.Contract✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.FileManipulation.Thumbnails.DeleteThumbnails uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Application.FileManipulation.Thumbnails.DeleteThumbnails.DeleteThumbnails→Ranky.MediaBundle.Domain.Contract.FileRepositoryInterface
- Direction
- Ranky.MediaBundle.Application.FileManipulation.Thumbnails.DeleteThumbnails uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Application.FileManipulation.Thumbnails.DeleteThumbnails, while a change to Ranky.MediaBundle.Application.FileManipulation.Thumbnails.DeleteThumbnails can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.FileManipulation.Thumbnails.DeleteThumbnails uses a module listed above it, which is the healthy direction.
17→3 Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails uses Ranky.MediaBundle.Domain.ValueObject✕
- Connections
- 5 pairs of types, where a type in Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails uses a type in Ranky.MediaBundle.Domain.ValueObject.
- The types involved
Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails.AbstractGenerateImageThumbnails→Ranky.MediaBundle.Domain.ValueObject.DimensionRanky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails.AbstractGenerateImageThumbnails→Ranky.MediaBundle.Domain.ValueObject.FileRanky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails.AbstractGenerateImageThumbnails→Ranky.MediaBundle.Domain.ValueObject.ThumbnailsRanky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails.GenerateGifImageThumbnails→Ranky.MediaBundle.Domain.ValueObject.FileRanky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails.GenerateImageThumbnails→Ranky.MediaBundle.Domain.ValueObject.File
- Direction
- Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails uses Ranky.MediaBundle.Domain.ValueObject, so a change to Ranky.MediaBundle.Domain.ValueObject can break Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails, while a change to Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails can't break Ranky.MediaBundle.Domain.ValueObject.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails uses a module listed above it, which is the healthy direction.
17→7 Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails uses Ranky.MediaBundle.Domain.Service✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails uses a type in Ranky.MediaBundle.Domain.Service.
- The types involved
Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails.AbstractGenerateImageThumbnails→Ranky.MediaBundle.Domain.Service.FileResizeHandler
- Direction
- Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails uses Ranky.MediaBundle.Domain.Service, so a change to Ranky.MediaBundle.Domain.Service can break Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails, while a change to Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails can't break Ranky.MediaBundle.Domain.Service.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails uses a module listed above it, which is the healthy direction.
17→14 Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails uses Ranky.MediaBundle.Domain.Contract✕
- Connections
- 6 pairs of types, where a type in Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails.AbstractGenerateImageThumbnails→Ranky.MediaBundle.Domain.Contract.FilePathResolverInterfaceRanky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails.AbstractGenerateImageThumbnails→Ranky.MediaBundle.Domain.Contract.FileRepositoryInterfaceRanky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails.AbstractGenerateImageThumbnails→Ranky.MediaBundle.Domain.Contract.FileUrlResolverInterfaceRanky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails.AbstractGenerateImageThumbnails→Ranky.MediaBundle.Domain.Contract.MediaRepositoryInterfaceRanky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails.GenerateGifImageThumbnails→Ranky.MediaBundle.Domain.Contract.GenerateThumbnailsInterfaceRanky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails.GenerateImageThumbnails→Ranky.MediaBundle.Domain.Contract.GenerateThumbnailsInterface
- Direction
- Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails, while a change to Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.FileManipulation.Thumbnails.GenerateThumbnails uses a module listed above it, which is the healthy direction.
18→3 Ranky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails uses Ranky.MediaBundle.Domain.ValueObject✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails uses a type in Ranky.MediaBundle.Domain.ValueObject.
- The types involved
Ranky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails.RenameThumbnails→Ranky.MediaBundle.Domain.ValueObject.Thumbnails
- Direction
- Ranky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails uses Ranky.MediaBundle.Domain.ValueObject, so a change to Ranky.MediaBundle.Domain.ValueObject can break Ranky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails, while a change to Ranky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails can't break Ranky.MediaBundle.Domain.ValueObject.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails uses a module listed above it, which is the healthy direction.
18→14 Ranky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails uses Ranky.MediaBundle.Domain.Contract✕
- Connections
- 3 pairs of types, where a type in Ranky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails.RenameThumbnails→Ranky.MediaBundle.Domain.Contract.FilePathResolverInterfaceRanky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails.RenameThumbnails→Ranky.MediaBundle.Domain.Contract.FileRepositoryInterfaceRanky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails.RenameThumbnails→Ranky.MediaBundle.Domain.Contract.FileUrlResolverInterface
- Direction
- Ranky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails, while a change to Ranky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails uses a module listed above it, which is the healthy direction.
19→12 Ranky.MediaBundle.Application.FindMedia uses Ranky.MediaBundle.Application.DataTransformer✕
- Connections
- 2 pairs of types, where a type in Ranky.MediaBundle.Application.FindMedia uses a type in Ranky.MediaBundle.Application.DataTransformer.
- The types involved
Ranky.MediaBundle.Application.FindMedia.FindMediaByIds→Ranky.MediaBundle.Application.DataTransformer.MediaToResponseTransformerRanky.MediaBundle.Application.FindMedia.FindMediaByPaths→Ranky.MediaBundle.Application.DataTransformer.MediaToResponseTransformer
- Direction
- Ranky.MediaBundle.Application.FindMedia uses Ranky.MediaBundle.Application.DataTransformer, so a change to Ranky.MediaBundle.Application.DataTransformer can break Ranky.MediaBundle.Application.FindMedia, while a change to Ranky.MediaBundle.Application.FindMedia can't break Ranky.MediaBundle.Application.DataTransformer.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.FindMedia uses a module listed above it, which is the healthy direction.
19→14 Ranky.MediaBundle.Application.FindMedia uses Ranky.MediaBundle.Domain.Contract✕
- Connections
- 2 pairs of types, where a type in Ranky.MediaBundle.Application.FindMedia uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Application.FindMedia.FindMediaByIds→Ranky.MediaBundle.Domain.Contract.MediaRepositoryInterfaceRanky.MediaBundle.Application.FindMedia.FindMediaByPaths→Ranky.MediaBundle.Domain.Contract.MediaRepositoryInterface
- Direction
- Ranky.MediaBundle.Application.FindMedia uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Application.FindMedia, while a change to Ranky.MediaBundle.Application.FindMedia can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.FindMedia uses a module listed above it, which is the healthy direction.
20→10 Ranky.MediaBundle.Application.GetMedia uses Ranky.MediaBundle.Application.DataTransformer.Response✕
- Connections
- 3 pairs of types, where a type in Ranky.MediaBundle.Application.GetMedia uses a type in Ranky.MediaBundle.Application.DataTransformer.Response.
- The types involved
Ranky.MediaBundle.Application.GetMedia.GetMediaByFileName→Ranky.MediaBundle.Application.DataTransformer.Response.MediaResponseRanky.MediaBundle.Application.GetMedia.GetMediaByFilePath→Ranky.MediaBundle.Application.DataTransformer.Response.MediaResponseRanky.MediaBundle.Application.GetMedia.GetMediaById→Ranky.MediaBundle.Application.DataTransformer.Response.MediaResponse
- Direction
- Ranky.MediaBundle.Application.GetMedia uses Ranky.MediaBundle.Application.DataTransformer.Response, so a change to Ranky.MediaBundle.Application.DataTransformer.Response can break Ranky.MediaBundle.Application.GetMedia, while a change to Ranky.MediaBundle.Application.GetMedia can't break Ranky.MediaBundle.Application.DataTransformer.Response.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.GetMedia uses a module listed above it, which is the healthy direction.
20→12 Ranky.MediaBundle.Application.GetMedia uses Ranky.MediaBundle.Application.DataTransformer✕
- Connections
- 3 pairs of types, where a type in Ranky.MediaBundle.Application.GetMedia uses a type in Ranky.MediaBundle.Application.DataTransformer.
- The types involved
Ranky.MediaBundle.Application.GetMedia.GetMediaByFileName→Ranky.MediaBundle.Application.DataTransformer.MediaToResponseTransformerRanky.MediaBundle.Application.GetMedia.GetMediaByFilePath→Ranky.MediaBundle.Application.DataTransformer.MediaToResponseTransformerRanky.MediaBundle.Application.GetMedia.GetMediaById→Ranky.MediaBundle.Application.DataTransformer.MediaToResponseTransformer
- Direction
- Ranky.MediaBundle.Application.GetMedia uses Ranky.MediaBundle.Application.DataTransformer, so a change to Ranky.MediaBundle.Application.DataTransformer can break Ranky.MediaBundle.Application.GetMedia, while a change to Ranky.MediaBundle.Application.GetMedia can't break Ranky.MediaBundle.Application.DataTransformer.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.GetMedia uses a module listed above it, which is the healthy direction.
20→14 Ranky.MediaBundle.Application.GetMedia uses Ranky.MediaBundle.Domain.Contract✕
- Connections
- 3 pairs of types, where a type in Ranky.MediaBundle.Application.GetMedia uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Application.GetMedia.GetMediaByFileName→Ranky.MediaBundle.Domain.Contract.MediaRepositoryInterfaceRanky.MediaBundle.Application.GetMedia.GetMediaByFilePath→Ranky.MediaBundle.Domain.Contract.MediaRepositoryInterfaceRanky.MediaBundle.Application.GetMedia.GetMediaById→Ranky.MediaBundle.Domain.Contract.MediaRepositoryInterface
- Direction
- Ranky.MediaBundle.Application.GetMedia uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Application.GetMedia, while a change to Ranky.MediaBundle.Application.GetMedia can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.GetMedia uses a module listed above it, which is the healthy direction.
21→14 Ranky.MediaBundle.Application.ListFilter.ListAvailableDatesFilter uses Ranky.MediaBundle.Domain.Contract✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.ListFilter.ListAvailableDatesFilter uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Application.ListFilter.ListAvailableDatesFilter.ListAvailableDatesFilter→Ranky.MediaBundle.Domain.Contract.AvailableDatesMediaRepositoryInterface
- Direction
- Ranky.MediaBundle.Application.ListFilter.ListAvailableDatesFilter uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Application.ListFilter.ListAvailableDatesFilter, while a change to Ranky.MediaBundle.Application.ListFilter.ListAvailableDatesFilter can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.ListFilter.ListAvailableDatesFilter uses a module listed above it, which is the healthy direction.
22→14 Ranky.MediaBundle.Application.ListFilter.ListMimeFilter uses Ranky.MediaBundle.Domain.Contract✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.ListFilter.ListMimeFilter uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Application.ListFilter.ListMimeFilter.ListMimeFilter→Ranky.MediaBundle.Domain.Contract.MimeMediaRepositoryInterface
- Direction
- Ranky.MediaBundle.Application.ListFilter.ListMimeFilter uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Application.ListFilter.ListMimeFilter, while a change to Ranky.MediaBundle.Application.ListFilter.ListMimeFilter can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.ListFilter.ListMimeFilter uses a module listed above it, which is the healthy direction.
23→14 Ranky.MediaBundle.Application.ListFilter.ListUserFilter uses Ranky.MediaBundle.Domain.Contract✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.ListFilter.ListUserFilter uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Application.ListFilter.ListUserFilter.ListUserFilter→Ranky.MediaBundle.Domain.Contract.UserMediaRepositoryInterface
- Direction
- Ranky.MediaBundle.Application.ListFilter.ListUserFilter uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Application.ListFilter.ListUserFilter, while a change to Ranky.MediaBundle.Application.ListFilter.ListUserFilter can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.ListFilter.ListUserFilter uses a module listed above it, which is the healthy direction.
24→12 Ranky.MediaBundle.Application.ListMediaCriteria uses Ranky.MediaBundle.Application.DataTransformer✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.ListMediaCriteria uses a type in Ranky.MediaBundle.Application.DataTransformer.
- The types involved
Ranky.MediaBundle.Application.ListMediaCriteria.ListMediaCriteria→Ranky.MediaBundle.Application.DataTransformer.MediaToResponseTransformer
- Direction
- Ranky.MediaBundle.Application.ListMediaCriteria uses Ranky.MediaBundle.Application.DataTransformer, so a change to Ranky.MediaBundle.Application.DataTransformer can break Ranky.MediaBundle.Application.ListMediaCriteria, while a change to Ranky.MediaBundle.Application.ListMediaCriteria can't break Ranky.MediaBundle.Application.DataTransformer.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.ListMediaCriteria uses a module listed above it, which is the healthy direction.
24→14 Ranky.MediaBundle.Application.ListMediaCriteria uses Ranky.MediaBundle.Domain.Contract✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.ListMediaCriteria uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Application.ListMediaCriteria.ListMediaCriteria→Ranky.MediaBundle.Domain.Contract.MediaRepositoryInterface
- Direction
- Ranky.MediaBundle.Application.ListMediaCriteria uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Application.ListMediaCriteria, while a change to Ranky.MediaBundle.Application.ListMediaCriteria can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.ListMediaCriteria uses a module listed above it, which is the healthy direction.
25→14 Ranky.MediaBundle.Application.SafeFileName uses Ranky.MediaBundle.Domain.Contract✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.SafeFileName uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Application.SafeFileName.SafeFileName→Ranky.MediaBundle.Domain.Contract.MediaRepositoryInterface
- Direction
- Ranky.MediaBundle.Application.SafeFileName uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Application.SafeFileName, while a change to Ranky.MediaBundle.Application.SafeFileName can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.SafeFileName uses a module listed above it, which is the healthy direction.
26→10 Ranky.MediaBundle.Application.UpdateMedia uses Ranky.MediaBundle.Application.DataTransformer.Response✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.UpdateMedia uses a type in Ranky.MediaBundle.Application.DataTransformer.Response.
- The types involved
Ranky.MediaBundle.Application.UpdateMedia.UpdateMedia→Ranky.MediaBundle.Application.DataTransformer.Response.MediaResponse
- Direction
- Ranky.MediaBundle.Application.UpdateMedia uses Ranky.MediaBundle.Application.DataTransformer.Response, so a change to Ranky.MediaBundle.Application.DataTransformer.Response can break Ranky.MediaBundle.Application.UpdateMedia, while a change to Ranky.MediaBundle.Application.UpdateMedia can't break Ranky.MediaBundle.Application.DataTransformer.Response.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.UpdateMedia uses a module listed above it, which is the healthy direction.
26→12 Ranky.MediaBundle.Application.UpdateMedia uses Ranky.MediaBundle.Application.DataTransformer✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.UpdateMedia uses a type in Ranky.MediaBundle.Application.DataTransformer.
- The types involved
Ranky.MediaBundle.Application.UpdateMedia.UpdateMedia→Ranky.MediaBundle.Application.DataTransformer.MediaToResponseTransformer
- Direction
- Ranky.MediaBundle.Application.UpdateMedia uses Ranky.MediaBundle.Application.DataTransformer, so a change to Ranky.MediaBundle.Application.DataTransformer can break Ranky.MediaBundle.Application.UpdateMedia, while a change to Ranky.MediaBundle.Application.UpdateMedia can't break Ranky.MediaBundle.Application.DataTransformer.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.UpdateMedia uses a module listed above it, which is the healthy direction.
26→14 Ranky.MediaBundle.Application.UpdateMedia uses Ranky.MediaBundle.Domain.Contract✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.UpdateMedia uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Application.UpdateMedia.UpdateMedia→Ranky.MediaBundle.Domain.Contract.MediaRepositoryInterface
- Direction
- Ranky.MediaBundle.Application.UpdateMedia uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Application.UpdateMedia, while a change to Ranky.MediaBundle.Application.UpdateMedia can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.UpdateMedia uses a module listed above it, which is the healthy direction.
26→36 Ranky.MediaBundle.Application.UpdateMedia uses Ranky.MediaBundle.Application.FileManipulation.RenameFile part of a loop✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.UpdateMedia uses a type in Ranky.MediaBundle.Application.FileManipulation.RenameFile.
- The types involved
Ranky.MediaBundle.Application.UpdateMedia.UpdateMedia→Ranky.MediaBundle.Application.FileManipulation.RenameFile.RenameFile
- Direction
- Ranky.MediaBundle.Application.UpdateMedia uses Ranky.MediaBundle.Application.FileManipulation.RenameFile, so a change to Ranky.MediaBundle.Application.FileManipulation.RenameFile can break Ranky.MediaBundle.Application.UpdateMedia, while a change to Ranky.MediaBundle.Application.UpdateMedia can't break Ranky.MediaBundle.Application.FileManipulation.RenameFile.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→3 Ranky.MediaBundle.Infrastructure.FileManipulation.Compression uses Ranky.MediaBundle.Domain.ValueObject✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Infrastructure.FileManipulation.Compression uses a type in Ranky.MediaBundle.Domain.ValueObject.
- The types involved
Ranky.MediaBundle.Infrastructure.FileManipulation.Compression.SpatieFileCompression→Ranky.MediaBundle.Domain.ValueObject.File
- Direction
- Ranky.MediaBundle.Infrastructure.FileManipulation.Compression uses Ranky.MediaBundle.Domain.ValueObject, so a change to Ranky.MediaBundle.Domain.ValueObject can break Ranky.MediaBundle.Infrastructure.FileManipulation.Compression, while a change to Ranky.MediaBundle.Infrastructure.FileManipulation.Compression can't break Ranky.MediaBundle.Domain.ValueObject.
- Position
- Below the diagonal: Ranky.MediaBundle.Infrastructure.FileManipulation.Compression uses a module listed above it, which is the healthy direction.
27→14 Ranky.MediaBundle.Infrastructure.FileManipulation.Compression uses Ranky.MediaBundle.Domain.Contract✕
- Connections
- 2 pairs of types, where a type in Ranky.MediaBundle.Infrastructure.FileManipulation.Compression uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Infrastructure.FileManipulation.Compression.SpatieFileCompression→Ranky.MediaBundle.Domain.Contract.FileCompressInterfaceRanky.MediaBundle.Infrastructure.FileManipulation.Compression.SpatieFileCompression→Ranky.MediaBundle.Domain.Contract.FileRepositoryInterface
- Direction
- Ranky.MediaBundle.Infrastructure.FileManipulation.Compression uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Infrastructure.FileManipulation.Compression, while a change to Ranky.MediaBundle.Infrastructure.FileManipulation.Compression can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Below the diagonal: Ranky.MediaBundle.Infrastructure.FileManipulation.Compression uses a module listed above it, which is the healthy direction.
28→3 Ranky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize uses Ranky.MediaBundle.Domain.ValueObject✕
- Connections
- 8 pairs of types, where a type in Ranky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize uses a type in Ranky.MediaBundle.Domain.ValueObject.
- The types involved
Ranky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize.FfmpegGifFileResize→Ranky.MediaBundle.Domain.ValueObject.DimensionRanky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize.FfmpegGifFileResize→Ranky.MediaBundle.Domain.ValueObject.FileRanky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize.GifsicleGifFileResize→Ranky.MediaBundle.Domain.ValueObject.DimensionRanky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize.GifsicleGifFileResize→Ranky.MediaBundle.Domain.ValueObject.FileRanky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize.ImagickGifFileResize→Ranky.MediaBundle.Domain.ValueObject.DimensionRanky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize.ImagickGifFileResize→Ranky.MediaBundle.Domain.ValueObject.FileRanky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize.InterventionFileResize→Ranky.MediaBundle.Domain.ValueObject.DimensionRanky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize.InterventionFileResize→Ranky.MediaBundle.Domain.ValueObject.File
- Direction
- Ranky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize uses Ranky.MediaBundle.Domain.ValueObject, so a change to Ranky.MediaBundle.Domain.ValueObject can break Ranky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize, while a change to Ranky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize can't break Ranky.MediaBundle.Domain.ValueObject.
- Position
- Below the diagonal: Ranky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize uses a module listed above it, which is the healthy direction.
28→14 Ranky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize uses Ranky.MediaBundle.Domain.Contract✕
- Connections
- 4 pairs of types, where a type in Ranky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize.FfmpegGifFileResize→Ranky.MediaBundle.Domain.Contract.FileResizeInterfaceRanky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize.GifsicleGifFileResize→Ranky.MediaBundle.Domain.Contract.FileResizeInterfaceRanky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize.ImagickGifFileResize→Ranky.MediaBundle.Domain.Contract.FileResizeInterfaceRanky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize.InterventionFileResize→Ranky.MediaBundle.Domain.Contract.FileResizeInterface
- Direction
- Ranky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize, while a change to Ranky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Below the diagonal: Ranky.MediaBundle.Infrastructure.FileManipulation.Thumbnails.Resize uses a module listed above it, which is the healthy direction.
29→3 Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository uses Ranky.MediaBundle.Domain.ValueObject✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository uses a type in Ranky.MediaBundle.Domain.ValueObject.
- The types involved
Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository.DoctrineOrmMediaRepository→Ranky.MediaBundle.Domain.ValueObject.MediaId
- Direction
- Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository uses Ranky.MediaBundle.Domain.ValueObject, so a change to Ranky.MediaBundle.Domain.ValueObject can break Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository, while a change to Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository can't break Ranky.MediaBundle.Domain.ValueObject.
- Position
- Below the diagonal: Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository uses a module listed above it, which is the healthy direction.
29→6 Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository uses Ranky.MediaBundle.Domain.Model✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository uses a type in Ranky.MediaBundle.Domain.Model.
- The types involved
Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository.DoctrineOrmMediaRepository→Ranky.MediaBundle.Domain.Model.MediaInterface
- Direction
- Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository uses Ranky.MediaBundle.Domain.Model, so a change to Ranky.MediaBundle.Domain.Model can break Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository, while a change to Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository can't break Ranky.MediaBundle.Domain.Model.
- Position
- Below the diagonal: Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository uses a module listed above it, which is the healthy direction.
29→14 Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository uses Ranky.MediaBundle.Domain.Contract✕
- Connections
- 4 pairs of types, where a type in Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository.DoctrineOrmAvailableDatesMediaRepository→Ranky.MediaBundle.Domain.Contract.AvailableDatesMediaRepositoryInterfaceRanky.MediaBundle.Infrastructure.Persistence.Orm.Repository.DoctrineOrmMediaRepository→Ranky.MediaBundle.Domain.Contract.MediaRepositoryInterfaceRanky.MediaBundle.Infrastructure.Persistence.Orm.Repository.DoctrineOrmMimeMediaRepository→Ranky.MediaBundle.Domain.Contract.MimeMediaRepositoryInterfaceRanky.MediaBundle.Infrastructure.Persistence.Orm.Repository.DoctrineOrmUserMediaRepository→Ranky.MediaBundle.Domain.Contract.UserMediaRepositoryInterface
- Direction
- Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository, while a change to Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Below the diagonal: Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository uses a module listed above it, which is the healthy direction.
30→14 Ranky.MediaBundle.Presentation.Form uses Ranky.MediaBundle.Domain.Contract✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Presentation.Form uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Presentation.Form.RankyMediaFileManagerType→Ranky.MediaBundle.Domain.Contract.MediaRepositoryInterface
- Direction
- Ranky.MediaBundle.Presentation.Form uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Presentation.Form, while a change to Ranky.MediaBundle.Presentation.Form can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Below the diagonal: Ranky.MediaBundle.Presentation.Form uses a module listed above it, which is the healthy direction.
31→3 Ranky.MediaBundle.Presentation.Form.DataTransformer uses Ranky.MediaBundle.Domain.ValueObject✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Presentation.Form.DataTransformer uses a type in Ranky.MediaBundle.Domain.ValueObject.
- The types involved
Ranky.MediaBundle.Presentation.Form.DataTransformer.MediaIdToStringTransformer→Ranky.MediaBundle.Domain.ValueObject.MediaId
- Direction
- Ranky.MediaBundle.Presentation.Form.DataTransformer uses Ranky.MediaBundle.Domain.ValueObject, so a change to Ranky.MediaBundle.Domain.ValueObject can break Ranky.MediaBundle.Presentation.Form.DataTransformer, while a change to Ranky.MediaBundle.Presentation.Form.DataTransformer can't break Ranky.MediaBundle.Domain.ValueObject.
- Position
- Below the diagonal: Ranky.MediaBundle.Presentation.Form.DataTransformer uses a module listed above it, which is the healthy direction.
31→6 Ranky.MediaBundle.Presentation.Form.DataTransformer uses Ranky.MediaBundle.Domain.Model✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Presentation.Form.DataTransformer uses a type in Ranky.MediaBundle.Domain.Model.
- The types involved
Ranky.MediaBundle.Presentation.Form.DataTransformer.MediaEntityTransformer→Ranky.MediaBundle.Domain.Model.MediaInterface
- Direction
- Ranky.MediaBundle.Presentation.Form.DataTransformer uses Ranky.MediaBundle.Domain.Model, so a change to Ranky.MediaBundle.Domain.Model can break Ranky.MediaBundle.Presentation.Form.DataTransformer, while a change to Ranky.MediaBundle.Presentation.Form.DataTransformer can't break Ranky.MediaBundle.Domain.Model.
- Position
- Below the diagonal: Ranky.MediaBundle.Presentation.Form.DataTransformer uses a module listed above it, which is the healthy direction.
31→14 Ranky.MediaBundle.Presentation.Form.DataTransformer uses Ranky.MediaBundle.Domain.Contract✕
- Connections
- 3 pairs of types, where a type in Ranky.MediaBundle.Presentation.Form.DataTransformer uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Presentation.Form.DataTransformer.MediaCollectionTransformer→Ranky.MediaBundle.Domain.Contract.MediaRepositoryInterfaceRanky.MediaBundle.Presentation.Form.DataTransformer.MediaEntityTransformer→Ranky.MediaBundle.Domain.Contract.MediaRepositoryInterfaceRanky.MediaBundle.Presentation.Form.DataTransformer.MediaPathTransformer→Ranky.MediaBundle.Domain.Contract.MediaRepositoryInterface
- Direction
- Ranky.MediaBundle.Presentation.Form.DataTransformer uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Presentation.Form.DataTransformer, while a change to Ranky.MediaBundle.Presentation.Form.DataTransformer can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Below the diagonal: Ranky.MediaBundle.Presentation.Form.DataTransformer uses a module listed above it, which is the healthy direction.
32→14 Ranky.MediaBundle.Presentation.Twig uses Ranky.MediaBundle.Domain.Contract✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Presentation.Twig uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Presentation.Twig.MediaTwigExtension→Ranky.MediaBundle.Domain.Contract.FileUrlResolverInterface
- Direction
- Ranky.MediaBundle.Presentation.Twig uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Presentation.Twig, while a change to Ranky.MediaBundle.Presentation.Twig can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Below the diagonal: Ranky.MediaBundle.Presentation.Twig uses a module listed above it, which is the healthy direction.
33→29 App.Repository uses Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository✕
- Connections
- 1 pair of types, where a type in App.Repository uses a type in Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository.
- The types involved
App.Repository.MediaRepository→Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository.DoctrineOrmMediaRepository
- Direction
- App.Repository uses Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository, so a change to Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository can break App.Repository, while a change to App.Repository can't break Ranky.MediaBundle.Infrastructure.Persistence.Orm.Repository.
- Position
- Below the diagonal: App.Repository uses a module listed above it, which is the healthy direction.
34→6 Ranky.MediaBundle.Application uses Ranky.MediaBundle.Domain.Model✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application uses a type in Ranky.MediaBundle.Domain.Model.
- The types involved
Ranky.MediaBundle.Application.MediaService→Ranky.MediaBundle.Domain.Model.MediaInterface
- Direction
- Ranky.MediaBundle.Application uses Ranky.MediaBundle.Domain.Model, so a change to Ranky.MediaBundle.Domain.Model can break Ranky.MediaBundle.Application, while a change to Ranky.MediaBundle.Application can't break Ranky.MediaBundle.Domain.Model.
- Position
- Below the diagonal: Ranky.MediaBundle.Application uses a module listed above it, which is the healthy direction.
34→10 Ranky.MediaBundle.Application uses Ranky.MediaBundle.Application.DataTransformer.Response✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application uses a type in Ranky.MediaBundle.Application.DataTransformer.Response.
- The types involved
Ranky.MediaBundle.Application.MediaService→Ranky.MediaBundle.Application.DataTransformer.Response.MediaResponse
- Direction
- Ranky.MediaBundle.Application uses Ranky.MediaBundle.Application.DataTransformer.Response, so a change to Ranky.MediaBundle.Application.DataTransformer.Response can break Ranky.MediaBundle.Application, while a change to Ranky.MediaBundle.Application can't break Ranky.MediaBundle.Application.DataTransformer.Response.
- Position
- Below the diagonal: Ranky.MediaBundle.Application uses a module listed above it, which is the healthy direction.
34→12 Ranky.MediaBundle.Application uses Ranky.MediaBundle.Application.DataTransformer✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application uses a type in Ranky.MediaBundle.Application.DataTransformer.
- The types involved
Ranky.MediaBundle.Application.MediaService→Ranky.MediaBundle.Application.DataTransformer.MediaToResponseTransformer
- Direction
- Ranky.MediaBundle.Application uses Ranky.MediaBundle.Application.DataTransformer, so a change to Ranky.MediaBundle.Application.DataTransformer can break Ranky.MediaBundle.Application, while a change to Ranky.MediaBundle.Application can't break Ranky.MediaBundle.Application.DataTransformer.
- Position
- Below the diagonal: Ranky.MediaBundle.Application uses a module listed above it, which is the healthy direction.
34→19 Ranky.MediaBundle.Application uses Ranky.MediaBundle.Application.FindMedia✕
- Connections
- 2 pairs of types, where a type in Ranky.MediaBundle.Application uses a type in Ranky.MediaBundle.Application.FindMedia.
- The types involved
Ranky.MediaBundle.Application.MediaService→Ranky.MediaBundle.Application.FindMedia.FindMediaByIdsRanky.MediaBundle.Application.MediaService→Ranky.MediaBundle.Application.FindMedia.FindMediaByPaths
- Direction
- Ranky.MediaBundle.Application uses Ranky.MediaBundle.Application.FindMedia, so a change to Ranky.MediaBundle.Application.FindMedia can break Ranky.MediaBundle.Application, while a change to Ranky.MediaBundle.Application can't break Ranky.MediaBundle.Application.FindMedia.
- Position
- Below the diagonal: Ranky.MediaBundle.Application uses a module listed above it, which is the healthy direction.
34→20 Ranky.MediaBundle.Application uses Ranky.MediaBundle.Application.GetMedia✕
- Connections
- 2 pairs of types, where a type in Ranky.MediaBundle.Application uses a type in Ranky.MediaBundle.Application.GetMedia.
- The types involved
Ranky.MediaBundle.Application.MediaService→Ranky.MediaBundle.Application.GetMedia.GetMediaByFilePathRanky.MediaBundle.Application.MediaService→Ranky.MediaBundle.Application.GetMedia.GetMediaById
- Direction
- Ranky.MediaBundle.Application uses Ranky.MediaBundle.Application.GetMedia, so a change to Ranky.MediaBundle.Application.GetMedia can break Ranky.MediaBundle.Application, while a change to Ranky.MediaBundle.Application can't break Ranky.MediaBundle.Application.GetMedia.
- Position
- Below the diagonal: Ranky.MediaBundle.Application uses a module listed above it, which is the healthy direction.
35→14 Ranky.MediaBundle.Application.DeleteMedia uses Ranky.MediaBundle.Domain.Contract✕
- Connections
- 2 pairs of types, where a type in Ranky.MediaBundle.Application.DeleteMedia uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Application.DeleteMedia.DeleteMedia→Ranky.MediaBundle.Domain.Contract.FileRepositoryInterfaceRanky.MediaBundle.Application.DeleteMedia.DeleteMedia→Ranky.MediaBundle.Domain.Contract.MediaRepositoryInterface
- Direction
- Ranky.MediaBundle.Application.DeleteMedia uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Application.DeleteMedia, while a change to Ranky.MediaBundle.Application.DeleteMedia can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.DeleteMedia uses a module listed above it, which is the healthy direction.
35→16 Ranky.MediaBundle.Application.DeleteMedia uses Ranky.MediaBundle.Application.FileManipulation.Thumbnails.DeleteThumbnails✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.DeleteMedia uses a type in Ranky.MediaBundle.Application.FileManipulation.Thumbnails.DeleteThumbnails.
- The types involved
Ranky.MediaBundle.Application.DeleteMedia.DeleteThumbnailsOnMediaDeleted→Ranky.MediaBundle.Application.FileManipulation.Thumbnails.DeleteThumbnails.DeleteThumbnails
- Direction
- Ranky.MediaBundle.Application.DeleteMedia uses Ranky.MediaBundle.Application.FileManipulation.Thumbnails.DeleteThumbnails, so a change to Ranky.MediaBundle.Application.FileManipulation.Thumbnails.DeleteThumbnails can break Ranky.MediaBundle.Application.DeleteMedia, while a change to Ranky.MediaBundle.Application.DeleteMedia can't break Ranky.MediaBundle.Application.FileManipulation.Thumbnails.DeleteThumbnails.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.DeleteMedia uses a module listed above it, which is the healthy direction.
36→14 Ranky.MediaBundle.Application.FileManipulation.RenameFile uses Ranky.MediaBundle.Domain.Contract✕
- Connections
- 3 pairs of types, where a type in Ranky.MediaBundle.Application.FileManipulation.RenameFile uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Application.FileManipulation.RenameFile.RenameFile→Ranky.MediaBundle.Domain.Contract.FilePathResolverInterfaceRanky.MediaBundle.Application.FileManipulation.RenameFile.RenameFile→Ranky.MediaBundle.Domain.Contract.FileRepositoryInterfaceRanky.MediaBundle.Application.FileManipulation.RenameFile.RenameFile→Ranky.MediaBundle.Domain.Contract.MediaRepositoryInterface
- Direction
- Ranky.MediaBundle.Application.FileManipulation.RenameFile uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Application.FileManipulation.RenameFile, while a change to Ranky.MediaBundle.Application.FileManipulation.RenameFile can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.FileManipulation.RenameFile uses a module listed above it, which is the healthy direction.
36→18 Ranky.MediaBundle.Application.FileManipulation.RenameFile uses Ranky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.FileManipulation.RenameFile uses a type in Ranky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails.
- The types involved
Ranky.MediaBundle.Application.FileManipulation.RenameFile.RenameFile→Ranky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails.RenameThumbnails
- Direction
- Ranky.MediaBundle.Application.FileManipulation.RenameFile uses Ranky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails, so a change to Ranky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails can break Ranky.MediaBundle.Application.FileManipulation.RenameFile, while a change to Ranky.MediaBundle.Application.FileManipulation.RenameFile can't break Ranky.MediaBundle.Application.FileManipulation.Thumbnails.RenameThumbnails.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.FileManipulation.RenameFile uses a module listed above it, which is the healthy direction.
36→25 Ranky.MediaBundle.Application.FileManipulation.RenameFile uses Ranky.MediaBundle.Application.SafeFileName✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.FileManipulation.RenameFile uses a type in Ranky.MediaBundle.Application.SafeFileName.
- The types involved
Ranky.MediaBundle.Application.FileManipulation.RenameFile.RenameFile→Ranky.MediaBundle.Application.SafeFileName.SafeFileName
- Direction
- Ranky.MediaBundle.Application.FileManipulation.RenameFile uses Ranky.MediaBundle.Application.SafeFileName, so a change to Ranky.MediaBundle.Application.SafeFileName can break Ranky.MediaBundle.Application.FileManipulation.RenameFile, while a change to Ranky.MediaBundle.Application.FileManipulation.RenameFile can't break Ranky.MediaBundle.Application.SafeFileName.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.FileManipulation.RenameFile uses a module listed above it, which is the healthy direction.
36→26 Ranky.MediaBundle.Application.FileManipulation.RenameFile uses Ranky.MediaBundle.Application.UpdateMedia✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.FileManipulation.RenameFile uses a type in Ranky.MediaBundle.Application.UpdateMedia.
- The types involved
Ranky.MediaBundle.Application.FileManipulation.RenameFile.RenameFile→Ranky.MediaBundle.Application.UpdateMedia.UpdateMediaRequest
- Direction
- Ranky.MediaBundle.Application.FileManipulation.RenameFile uses Ranky.MediaBundle.Application.UpdateMedia, so a change to Ranky.MediaBundle.Application.UpdateMedia can break Ranky.MediaBundle.Application.FileManipulation.RenameFile, while a change to Ranky.MediaBundle.Application.FileManipulation.RenameFile can't break Ranky.MediaBundle.Application.UpdateMedia.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.FileManipulation.RenameFile uses a module listed above it, which is the healthy direction.
37→21 Ranky.MediaBundle.Application.ListFilter uses Ranky.MediaBundle.Application.ListFilter.ListAvailableDatesFilter✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.ListFilter uses a type in Ranky.MediaBundle.Application.ListFilter.ListAvailableDatesFilter.
- The types involved
Ranky.MediaBundle.Application.ListFilter.ListFilter→Ranky.MediaBundle.Application.ListFilter.ListAvailableDatesFilter.ListAvailableDatesFilter
- Direction
- Ranky.MediaBundle.Application.ListFilter uses Ranky.MediaBundle.Application.ListFilter.ListAvailableDatesFilter, so a change to Ranky.MediaBundle.Application.ListFilter.ListAvailableDatesFilter can break Ranky.MediaBundle.Application.ListFilter, while a change to Ranky.MediaBundle.Application.ListFilter can't break Ranky.MediaBundle.Application.ListFilter.ListAvailableDatesFilter.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.ListFilter uses a module listed above it, which is the healthy direction.
37→22 Ranky.MediaBundle.Application.ListFilter uses Ranky.MediaBundle.Application.ListFilter.ListMimeFilter✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.ListFilter uses a type in Ranky.MediaBundle.Application.ListFilter.ListMimeFilter.
- The types involved
Ranky.MediaBundle.Application.ListFilter.ListFilter→Ranky.MediaBundle.Application.ListFilter.ListMimeFilter.ListMimeFilter
- Direction
- Ranky.MediaBundle.Application.ListFilter uses Ranky.MediaBundle.Application.ListFilter.ListMimeFilter, so a change to Ranky.MediaBundle.Application.ListFilter.ListMimeFilter can break Ranky.MediaBundle.Application.ListFilter, while a change to Ranky.MediaBundle.Application.ListFilter can't break Ranky.MediaBundle.Application.ListFilter.ListMimeFilter.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.ListFilter uses a module listed above it, which is the healthy direction.
37→23 Ranky.MediaBundle.Application.ListFilter uses Ranky.MediaBundle.Application.ListFilter.ListUserFilter✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Application.ListFilter uses a type in Ranky.MediaBundle.Application.ListFilter.ListUserFilter.
- The types involved
Ranky.MediaBundle.Application.ListFilter.ListFilter→Ranky.MediaBundle.Application.ListFilter.ListUserFilter.ListUserFilter
- Direction
- Ranky.MediaBundle.Application.ListFilter uses Ranky.MediaBundle.Application.ListFilter.ListUserFilter, so a change to Ranky.MediaBundle.Application.ListFilter.ListUserFilter can break Ranky.MediaBundle.Application.ListFilter, while a change to Ranky.MediaBundle.Application.ListFilter can't break Ranky.MediaBundle.Application.ListFilter.ListUserFilter.
- Position
- Below the diagonal: Ranky.MediaBundle.Application.ListFilter uses a module listed above it, which is the healthy direction.
38→3 Ranky.MediaBundle.Infrastructure.Event uses Ranky.MediaBundle.Domain.ValueObject✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Infrastructure.Event uses a type in Ranky.MediaBundle.Domain.ValueObject.
- The types involved
Ranky.MediaBundle.Infrastructure.Event.DeleteEvent→Ranky.MediaBundle.Domain.ValueObject.MediaId
- Direction
- Ranky.MediaBundle.Infrastructure.Event uses Ranky.MediaBundle.Domain.ValueObject, so a change to Ranky.MediaBundle.Domain.ValueObject can break Ranky.MediaBundle.Infrastructure.Event, while a change to Ranky.MediaBundle.Infrastructure.Event can't break Ranky.MediaBundle.Domain.ValueObject.
- Position
- Below the diagonal: Ranky.MediaBundle.Infrastructure.Event uses a module listed above it, which is the healthy direction.
38→10 Ranky.MediaBundle.Infrastructure.Event uses Ranky.MediaBundle.Application.DataTransformer.Response✕
- Connections
- 2 pairs of types, where a type in Ranky.MediaBundle.Infrastructure.Event uses a type in Ranky.MediaBundle.Application.DataTransformer.Response.
- The types involved
Ranky.MediaBundle.Infrastructure.Event.PostCreateEvent→Ranky.MediaBundle.Application.DataTransformer.Response.MediaResponseRanky.MediaBundle.Infrastructure.Event.PostUpdateEvent→Ranky.MediaBundle.Application.DataTransformer.Response.MediaResponse
- Direction
- Ranky.MediaBundle.Infrastructure.Event uses Ranky.MediaBundle.Application.DataTransformer.Response, so a change to Ranky.MediaBundle.Application.DataTransformer.Response can break Ranky.MediaBundle.Infrastructure.Event, while a change to Ranky.MediaBundle.Infrastructure.Event can't break Ranky.MediaBundle.Application.DataTransformer.Response.
- Position
- Below the diagonal: Ranky.MediaBundle.Infrastructure.Event uses a module listed above it, which is the healthy direction.
38→13 Ranky.MediaBundle.Infrastructure.Event uses Ranky.MediaBundle.Application.CreateMedia✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Infrastructure.Event uses a type in Ranky.MediaBundle.Application.CreateMedia.
- The types involved
Ranky.MediaBundle.Infrastructure.Event.PreCreateEvent→Ranky.MediaBundle.Application.CreateMedia.UploadedFileRequest
- Direction
- Ranky.MediaBundle.Infrastructure.Event uses Ranky.MediaBundle.Application.CreateMedia, so a change to Ranky.MediaBundle.Application.CreateMedia can break Ranky.MediaBundle.Infrastructure.Event, while a change to Ranky.MediaBundle.Infrastructure.Event can't break Ranky.MediaBundle.Application.CreateMedia.
- Position
- Below the diagonal: Ranky.MediaBundle.Infrastructure.Event uses a module listed above it, which is the healthy direction.
38→26 Ranky.MediaBundle.Infrastructure.Event uses Ranky.MediaBundle.Application.UpdateMedia✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Infrastructure.Event uses a type in Ranky.MediaBundle.Application.UpdateMedia.
- The types involved
Ranky.MediaBundle.Infrastructure.Event.PreUpdateEvent→Ranky.MediaBundle.Application.UpdateMedia.UpdateMediaRequest
- Direction
- Ranky.MediaBundle.Infrastructure.Event uses Ranky.MediaBundle.Application.UpdateMedia, so a change to Ranky.MediaBundle.Application.UpdateMedia can break Ranky.MediaBundle.Infrastructure.Event, while a change to Ranky.MediaBundle.Infrastructure.Event can't break Ranky.MediaBundle.Application.UpdateMedia.
- Position
- Below the diagonal: Ranky.MediaBundle.Infrastructure.Event uses a module listed above it, which is the healthy direction.
39→3 Ranky.MediaBundle.Infrastructure.Filesystem.Local uses Ranky.MediaBundle.Domain.ValueObject✕
- Connections
- 2 pairs of types, where a type in Ranky.MediaBundle.Infrastructure.Filesystem.Local uses a type in Ranky.MediaBundle.Domain.ValueObject.
- The types involved
Ranky.MediaBundle.Infrastructure.Filesystem.Local.LocalFileRepository→Ranky.MediaBundle.Domain.ValueObject.DimensionRanky.MediaBundle.Infrastructure.Filesystem.Local.LocalFileRepository→Ranky.MediaBundle.Domain.ValueObject.File
- Direction
- Ranky.MediaBundle.Infrastructure.Filesystem.Local uses Ranky.MediaBundle.Domain.ValueObject, so a change to Ranky.MediaBundle.Domain.ValueObject can break Ranky.MediaBundle.Infrastructure.Filesystem.Local, while a change to Ranky.MediaBundle.Infrastructure.Filesystem.Local can't break Ranky.MediaBundle.Domain.ValueObject.
- Position
- Below the diagonal: Ranky.MediaBundle.Infrastructure.Filesystem.Local uses a module listed above it, which is the healthy direction.
39→13 Ranky.MediaBundle.Infrastructure.Filesystem.Local uses Ranky.MediaBundle.Application.CreateMedia✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Infrastructure.Filesystem.Local uses a type in Ranky.MediaBundle.Application.CreateMedia.
- The types involved
Ranky.MediaBundle.Infrastructure.Filesystem.Local.LocalFileRepository→Ranky.MediaBundle.Application.CreateMedia.UploadedFileRequest
- Direction
- Ranky.MediaBundle.Infrastructure.Filesystem.Local uses Ranky.MediaBundle.Application.CreateMedia, so a change to Ranky.MediaBundle.Application.CreateMedia can break Ranky.MediaBundle.Infrastructure.Filesystem.Local, while a change to Ranky.MediaBundle.Infrastructure.Filesystem.Local can't break Ranky.MediaBundle.Application.CreateMedia.
- Position
- Below the diagonal: Ranky.MediaBundle.Infrastructure.Filesystem.Local uses a module listed above it, which is the healthy direction.
39→14 Ranky.MediaBundle.Infrastructure.Filesystem.Local uses Ranky.MediaBundle.Domain.Contract✕
- Connections
- 4 pairs of types, where a type in Ranky.MediaBundle.Infrastructure.Filesystem.Local uses a type in Ranky.MediaBundle.Domain.Contract.
- The types involved
Ranky.MediaBundle.Infrastructure.Filesystem.Local.LocalFilePathResolver→Ranky.MediaBundle.Domain.Contract.FilePathResolverInterfaceRanky.MediaBundle.Infrastructure.Filesystem.Local.LocalFileRepository→Ranky.MediaBundle.Domain.Contract.FilePathResolverInterfaceRanky.MediaBundle.Infrastructure.Filesystem.Local.LocalFileRepository→Ranky.MediaBundle.Domain.Contract.FileRepositoryInterfaceRanky.MediaBundle.Infrastructure.Filesystem.Local.LocalFileUrlResolver→Ranky.MediaBundle.Domain.Contract.FileUrlResolverInterface
- Direction
- Ranky.MediaBundle.Infrastructure.Filesystem.Local uses Ranky.MediaBundle.Domain.Contract, so a change to Ranky.MediaBundle.Domain.Contract can break Ranky.MediaBundle.Infrastructure.Filesystem.Local, while a change to Ranky.MediaBundle.Infrastructure.Filesystem.Local can't break Ranky.MediaBundle.Domain.Contract.
- Position
- Below the diagonal: Ranky.MediaBundle.Infrastructure.Filesystem.Local uses a module listed above it, which is the healthy direction.
39→25 Ranky.MediaBundle.Infrastructure.Filesystem.Local uses Ranky.MediaBundle.Application.SafeFileName✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Infrastructure.Filesystem.Local uses a type in Ranky.MediaBundle.Application.SafeFileName.
- The types involved
Ranky.MediaBundle.Infrastructure.Filesystem.Local.LocalFileRepository→Ranky.MediaBundle.Application.SafeFileName.SafeFileName
- Direction
- Ranky.MediaBundle.Infrastructure.Filesystem.Local uses Ranky.MediaBundle.Application.SafeFileName, so a change to Ranky.MediaBundle.Application.SafeFileName can break Ranky.MediaBundle.Infrastructure.Filesystem.Local, while a change to Ranky.MediaBundle.Infrastructure.Filesystem.Local can't break Ranky.MediaBundle.Application.SafeFileName.
- Position
- Below the diagonal: Ranky.MediaBundle.Infrastructure.Filesystem.Local uses a module listed above it, which is the healthy direction.
40→1 Ranky.MediaBundle.Presentation.Api uses Ranky.MediaBundle.Domain.Criteria✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Presentation.Api uses a type in Ranky.MediaBundle.Domain.Criteria.
- The types involved
Ranky.MediaBundle.Presentation.Api.ListMediaCriteriaApiController→Ranky.MediaBundle.Domain.Criteria.MediaCriteria
- Direction
- Ranky.MediaBundle.Presentation.Api uses Ranky.MediaBundle.Domain.Criteria, so a change to Ranky.MediaBundle.Domain.Criteria can break Ranky.MediaBundle.Presentation.Api, while a change to Ranky.MediaBundle.Presentation.Api can't break Ranky.MediaBundle.Domain.Criteria.
- Position
- Below the diagonal: Ranky.MediaBundle.Presentation.Api uses a module listed above it, which is the healthy direction.
40→13 Ranky.MediaBundle.Presentation.Api uses Ranky.MediaBundle.Application.CreateMedia✕
- Connections
- 2 pairs of types, where a type in Ranky.MediaBundle.Presentation.Api uses a type in Ranky.MediaBundle.Application.CreateMedia.
- The types involved
Ranky.MediaBundle.Presentation.Api.UploadMediaApiController→Ranky.MediaBundle.Application.CreateMedia.CreateMediaRanky.MediaBundle.Presentation.Api.UploadMediaApiController→Ranky.MediaBundle.Application.CreateMedia.UploadedFileRequest
- Direction
- Ranky.MediaBundle.Presentation.Api uses Ranky.MediaBundle.Application.CreateMedia, so a change to Ranky.MediaBundle.Application.CreateMedia can break Ranky.MediaBundle.Presentation.Api, while a change to Ranky.MediaBundle.Presentation.Api can't break Ranky.MediaBundle.Application.CreateMedia.
- Position
- Below the diagonal: Ranky.MediaBundle.Presentation.Api uses a module listed above it, which is the healthy direction.
40→15 Ranky.MediaBundle.Presentation.Api uses Ranky.MediaBundle.Infrastructure.Validation✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Presentation.Api uses a type in Ranky.MediaBundle.Infrastructure.Validation.
- The types involved
Ranky.MediaBundle.Presentation.Api.UploadMediaApiController→Ranky.MediaBundle.Infrastructure.Validation.UploadedFileValidator
- Direction
- Ranky.MediaBundle.Presentation.Api uses Ranky.MediaBundle.Infrastructure.Validation, so a change to Ranky.MediaBundle.Infrastructure.Validation can break Ranky.MediaBundle.Presentation.Api, while a change to Ranky.MediaBundle.Presentation.Api can't break Ranky.MediaBundle.Infrastructure.Validation.
- Position
- Below the diagonal: Ranky.MediaBundle.Presentation.Api uses a module listed above it, which is the healthy direction.
40→20 Ranky.MediaBundle.Presentation.Api uses Ranky.MediaBundle.Application.GetMedia✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Presentation.Api uses a type in Ranky.MediaBundle.Application.GetMedia.
- The types involved
Ranky.MediaBundle.Presentation.Api.GetMediaByIdApiController→Ranky.MediaBundle.Application.GetMedia.GetMediaById
- Direction
- Ranky.MediaBundle.Presentation.Api uses Ranky.MediaBundle.Application.GetMedia, so a change to Ranky.MediaBundle.Application.GetMedia can break Ranky.MediaBundle.Presentation.Api, while a change to Ranky.MediaBundle.Presentation.Api can't break Ranky.MediaBundle.Application.GetMedia.
- Position
- Below the diagonal: Ranky.MediaBundle.Presentation.Api uses a module listed above it, which is the healthy direction.
40→24 Ranky.MediaBundle.Presentation.Api uses Ranky.MediaBundle.Application.ListMediaCriteria✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Presentation.Api uses a type in Ranky.MediaBundle.Application.ListMediaCriteria.
- The types involved
Ranky.MediaBundle.Presentation.Api.ListMediaCriteriaApiController→Ranky.MediaBundle.Application.ListMediaCriteria.ListMediaCriteria
- Direction
- Ranky.MediaBundle.Presentation.Api uses Ranky.MediaBundle.Application.ListMediaCriteria, so a change to Ranky.MediaBundle.Application.ListMediaCriteria can break Ranky.MediaBundle.Presentation.Api, while a change to Ranky.MediaBundle.Presentation.Api can't break Ranky.MediaBundle.Application.ListMediaCriteria.
- Position
- Below the diagonal: Ranky.MediaBundle.Presentation.Api uses a module listed above it, which is the healthy direction.
40→26 Ranky.MediaBundle.Presentation.Api uses Ranky.MediaBundle.Application.UpdateMedia✕
- Connections
- 2 pairs of types, where a type in Ranky.MediaBundle.Presentation.Api uses a type in Ranky.MediaBundle.Application.UpdateMedia.
- The types involved
Ranky.MediaBundle.Presentation.Api.UpdateMediaApiController→Ranky.MediaBundle.Application.UpdateMedia.UpdateMediaRanky.MediaBundle.Presentation.Api.UpdateMediaApiController→Ranky.MediaBundle.Application.UpdateMedia.UpdateMediaRequest
- Direction
- Ranky.MediaBundle.Presentation.Api uses Ranky.MediaBundle.Application.UpdateMedia, so a change to Ranky.MediaBundle.Application.UpdateMedia can break Ranky.MediaBundle.Presentation.Api, while a change to Ranky.MediaBundle.Presentation.Api can't break Ranky.MediaBundle.Application.UpdateMedia.
- Position
- Below the diagonal: Ranky.MediaBundle.Presentation.Api uses a module listed above it, which is the healthy direction.
40→35 Ranky.MediaBundle.Presentation.Api uses Ranky.MediaBundle.Application.DeleteMedia✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Presentation.Api uses a type in Ranky.MediaBundle.Application.DeleteMedia.
- The types involved
Ranky.MediaBundle.Presentation.Api.DeleteMediaApiController→Ranky.MediaBundle.Application.DeleteMedia.DeleteMedia
- Direction
- Ranky.MediaBundle.Presentation.Api uses Ranky.MediaBundle.Application.DeleteMedia, so a change to Ranky.MediaBundle.Application.DeleteMedia can break Ranky.MediaBundle.Presentation.Api, while a change to Ranky.MediaBundle.Presentation.Api can't break Ranky.MediaBundle.Application.DeleteMedia.
- Position
- Below the diagonal: Ranky.MediaBundle.Presentation.Api uses a module listed above it, which is the healthy direction.
40→37 Ranky.MediaBundle.Presentation.Api uses Ranky.MediaBundle.Application.ListFilter✕
- Connections
- 1 pair of types, where a type in Ranky.MediaBundle.Presentation.Api uses a type in Ranky.MediaBundle.Application.ListFilter.
- The types involved
Ranky.MediaBundle.Presentation.Api.FiltersMediaApiController→Ranky.MediaBundle.Application.ListFilter.ListFilter
- Direction
- Ranky.MediaBundle.Presentation.Api uses Ranky.MediaBundle.Application.ListFilter, so a change to Ranky.MediaBundle.Application.ListFilter can break Ranky.MediaBundle.Presentation.Api, while a change to Ranky.MediaBundle.Presentation.Api can't break Ranky.MediaBundle.Application.ListFilter.
- Position
- Below the diagonal: Ranky.MediaBundle.Presentation.Api uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 62 | High / Critical |
| A05:2025 — Injection | 29 | High / Critical |
| A02:2025 — Security Misconfiguration | 7 | Medium |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do; Resolve the 29 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (29); 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do. | +11.8 pts | Medium | Access Controls |
| Resolve the 29 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (29). | +3.6 pts | Medium | Dependency Vulnerabilities |
| 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. | +2.7 pts | Medium | Visual & motion safety |
| Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. | +1.3 pts | Low | Secrets (history) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.3 pts | Low | Static Analysis (SAST) |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. | +1.3 pts | Low | Static Analysis (SAST) |
| Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. | +1.3 pts | Low | Dependency Vulnerabilities |
| Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). | +1.3 pts | Low | Dependency Vulnerabilities |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 6.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/Infrastructure/DependencyInjection/Configuration.php | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/Application/DataTransformer/Response/ThumbnailsResponse.php | 6.7 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| src/Infrastructure/Filesystem/Local/LocalFileRepository.php | 7.3 | Mixed | Explicit Debt: TodoComment |
| src/Infrastructure/FileManipulation/Thumbnails/Resize/InterventionFileResize.php | 7.8 | Mixed | Cyclomatic Complexity: InterventionFileResize.resize (cyclomatic 18) |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 86 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 86 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 231 of 248 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.php) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 15 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — 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 composer.json, but the licence verdict published here was taken over its npm package dependencies. Nothing was read about its Composer dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (6 contributor(s) across 152 commit(s) sampled, automation and bot accounts excluded). One of them holds 90% of the history; the other 5 hold 2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- 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 deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- 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 an ADMISSION gap, not an environment fault: it declares a published package (composer.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
- 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 364 sampled here came from .php files. This repository's .tsx 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.
- D31 IaC & Container Security — 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. Tools/docker/mariadb/ci.Dockerfile, REDACTED carries no `FROM` instruction, so it declares no build stage and every Dockerfile rule this engine owns — the runtime-hardening, key-material, mutable-clone, no-op-shim, build-context, trust-anchor, install-guard, setuid and world-writable-path rules — is outside its own premise there and returned nothing. That silence is deliberate and correct: with no base image there is no image to reason about. It is reported here because it is NOT the same fact as a clean file, and coverage is stated as 4 of 6 Infrastructure-as-Code manifest(s) fully judged rather than as 100%. The vendor scanners (trivy, checkov) do read these files and their findings above stand; only this engine's own stage-keyed rules are absent. No owner action: a build file with no FROM is a legitimate include fragment.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/Application/CreateMedia/CreateMedia.php`, `src/Application/CreateMedia/FileCompressOnMediaCreated.php`, `src/Application/CreateMedia/GenerateThumbnailsOnMediaCreated.php`, `src/Application/CreateMedia/UploadedFileRequest.php`, `src/Application/DataTransformer/MediaToResponseTransformer.php`, … (+60 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.
- AC6 Visual & motion safety — 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. 4 further occurrence(s) are not listed individually; the score already reflects all 44.
- 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 Symfony DependencyInjection and a PSR-11 container (Psr\Container) and an unrecognised PHP 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 (docker-compose.ci.yml). compose up failed (exit 1 — a container did not start, exited, or never became healthy) — mariadb Built php Built container ranky-media-bundle-mariadb-1 exited (1); runtime evidence skipped.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's PHP is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's PHP is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P8 Schema migrations — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- 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".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was InterventionFileResize.resize at 18.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with InterventionFileResize.resize (cyclomatic 18). — Refactoring it lifts Cyclomatic Complexity from 9.7 to about 10.0/10.
D2 · Cognitive Complexity
3 method(s) exceeded the cognitive complexity threshold of 15; the worst was InterventionFileResize.resize at 21.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cognitive Complexity — start with InterventionFileResize.resize (cognitive 21), MediaBundleExtension.checkConfiguration (cognitive 16), FormFilters.FormFilters (cognitive 16). — 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 3 together lifts Cognitive Complexity from 9.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
4 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 3 FunctionTooLong finding(s) in God Classes — start with ModalFileContent.tsx, PageListLayout.tsx, ModalFile.tsx. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with Configuration.php. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
6 duplicated block group(s) detected. Measured on part of this repository only: .tsx (25% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
What to do
- Resolve the 1 Duplicated block (26–29 lines × 2) finding(s) in Code Duplication — start with FfmpegGifFileResize.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (23 lines × 6) finding(s) in Code Duplication — start with MimeSubType.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with Month.php. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
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.
D6 · Cohesion (LCOM4)
1 of 35 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with DoctrineOrmMediaRepository.php. — One of this dimension's main actionable groups (1 warning-level).
D9 · Test Distribution
37 test methods: 37 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 37 tests.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 140 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 140 package(s) this repository's committed lockfile installs for a consumer — its 17 production, optional and peer dependency(ies), across 1 product package.json manifest(s), and everything those install in turn. Its 44 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 1 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. This repository publishes itself under MIT, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's npm package dependencies and nothing else. The repository also declares composer.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.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
8 deducted task-comment markers across 9165 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 8 TodoComment finding(s) in Explicit Debt — start with LocalFileRepository.php (2), User.php, DoctrineOrmUserMediaRepository.php. — One of this dimension's main actionable groups (8 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 2 unit(s).
D26 · Project Cohesion
1 of 3 build units (Composer, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
61 % of calls cross a namespace and 18 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated. Measured over the .php source only — this repository's .tsx was not sampled for call sites, so this score covers part of the tree, not all of it.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
29 finding(s): 0 critical, 17 high, 12 medium, 0 low. 13 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 67 file(s) — `public/ranky_media.vendors.js`, `public/react.18.3.1.js`, `src/Application/CreateMedia/CreateMedia.php` (line 23, line 24, line 25, …), `src/Application/CreateMedia/FileCompressOnMediaCreated.php` (line 14), `src/Application/CreateMedia/GenerateThumbnailsOnMediaCreated.php` (line 16, line 17), … (+62 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 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 13 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (13 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
52 finding(s): 3 critical, 30 high, 13 medium, 6 low.
What to do
- Resolve the 29 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (29). — One of this dimension's main actionable groups (29 issue-level).
- Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
7 finding(s): 0 critical, 0 high, 4 medium, 3 low.
What to do
- Resolve the 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Low IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).
D34 · Knowledge Freshness
36 of 36 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Infrastructure/DependencyInjection/MediaBundleExtension.php. Counted over 36 of the 209 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 36 Orphaned file finding(s) in Knowledge Freshness — start with MediaBundleExtension.php, Configuration.php, ModalFileContent.tsx. — One of this dimension's main actionable groups (36 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 15 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- 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). — templates/preview/mime-show/video.html.twig: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 & labels
- This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×7) — assets/src/components/Form/Filters/SelectFilter.tsx:17, assets/src/components/Layout/PageListLayout.tsx:87, assets/src/components/Layout/PageListLayout.tsx:97, …
- 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). — assets/src/components/Layout/PageSelectableLayout.tsx:80
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — templates/embed.html.twig:2
- user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. — templates/embed.html.twig:5
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- This <li> binds double-click and nothing else. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click. — assets/src/components/Layout/PageSelectableLayout.tsx:57
- This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — assets/src/components/Modal/File/ModalFile.tsx:93
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `.ranky-media .uppy-Root .uppy-StatusBar-actions button.uppy-StatusBar-actionBtn--done` sets color: #fff on background-color: #189c38 — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — public/ranky_media.css:9
- `.ranky-media__filters form#media-form-filter .sort-filter label input` 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. — public/ranky_media.css:9
- `.ranky-media__items .file-list .file-item:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — public/ranky_media.css:9
- `.ranky-media .uppy-Root button.uppy-DashboardContent-addMore` 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. — public/ranky_media.css:9
- `.ranky-media .ranky-media-modal-file` 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. — public/ranky_media.css:9
- `.ranky-media .ranky-media-modal-file__dialog__content` 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. — public/ranky_media.css:9
- `.ranky-media .ranky-media-modal-file__dialog__content__show__info form .input-group .input-group-text` 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. — public/ranky_media.css:9
- `.ranky-media-modal` 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. (×2) — public/ranky_media.css:9, assets/src/styles/media_modal.scss:12
- `.ranky-media-modal__btn-media-close` 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. (×2) — public/ranky_media.css:9, assets/src/styles/media_modal.scss:35
- `.ranky-media-modal__content` 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. (×2) — public/ranky_media.css:9, assets/src/styles/media_modal.scss:140
- `.uppy-ProviderBrowser-list:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — public/ranky_media.vendors.css:1
- `button.uppy-Dashboard-Item-progressIndicator:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — public/ranky_media.vendors.css:1
- `.uppy-Dashboard-inner` 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. — public/ranky_media.vendors.css:1
- `.uppy-Dashboard-close:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — public/ranky_media.vendors.css:1
- `.__filters form#media-form-filter .view-filter label input` 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. — assets/src/styles/media.scss:267
- `.__items .file-list .file-item:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — assets/src/styles/media.scss:331
- `. a:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — assets/src/styles/reset.scss:220
- `. .uppy-Root button.uppy-DashboardContent-back` 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. — assets/src/styles/uppy.scss:34
- `. .ranky-media-modal-file__dialog__content__show__info form .input-group .input-group-text` 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. — assets/src/components/Modal/File/modal_file.scss:372
- `. .ranky-media-modal-file__dialog__content` 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. — assets/src/components/Modal/File/modal_file.scss:178
- `. .ranky-media-modal-file` 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. — assets/src/components/Modal/File/modal_file.scss:30
- `.ranky-media #page-loader:after` moves (`animation: page-loader-inner 1.25s ease-out 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. — public/ranky_media.css:1
- `.ranky-media #page-loader:before` moves (`animation: page-loader-outer 1.25s ease-in 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. — public/ranky_media.css:1
- `.ranky-media button` moves (`transition: background-color .1s linear,border-color .1s linear,color .1s linear,box-shadow .1s linear,transform .1s 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. — public/ranky_media.css:9
- `.ranky-media__filters form#media-form-filter .sort-filter label span` moves (`transition: background-color .1s linear,border-color .1s linear,color .1s linear,box-shadow .1s linear,transform .1s 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. — public/ranky_media.css:9
- `.ranky-media-form-type__content__wrapper_checkbox input[type=checkbox]` moves (`transition: background-color .1s linear,border-color .1s linear,color .1s linear,box-shadow .1s linear,transform .1s 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. — public/ranky_media.css:9
- `.uppy-StatusBar` moves (`transition: height .2s`) 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. — public/ranky_media.vendors.css:1
- `.uppy-StatusBar-progress` moves (`transition: background-color,width .3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — public/ranky_media.vendors.css:1
- `.uppy-StatusBar-progress.is-indeterminate` moves (`animation: uppy-StatusBar-ProgressStripes 1s 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. — public/ranky_media.vendors.css:1
- `.uppy-StatusBar-spinner` moves (`animation-name: uppy-StatusBar-spinnerAnimation`) 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. — public/ranky_media.vendors.css:1
- `.uppy-transition-slideDownUp-enter` moves (`transition: transform .25s ease-in-out,opacity .25s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — public/ranky_media.vendors.css:1
- `.uppy-transition-slideDownUp-leave` moves (`transition: transform .25s ease-in-out,opacity .25s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — public/ranky_media.vendors.css:1
- `.uppy-Dashboard--modal.uppy-Dashboard--animateOpenClose>.uppy-Dashboard-inner` moves (`animation: uppy-Dashboard-slideDownAndFadeIn--small .3s cubic-bezier(0,0,.2,1)`) 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. — public/ranky_media.vendors.css:1
- `.uppy-Dashboard--modal.uppy-Dashboard--animateOpenClose>.uppy-Dashboard-inner` moves (`animation: uppy-Dashboard-slideDownAndFadeIn .3s cubic-bezier(0,0,.2,1)`) 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. — public/ranky_media.vendors.css:1
- `.uppy-Dashboard--modal.uppy-Dashboard--animateOpenClose.uppy-Dashboard--isClosing>.uppy-Dashboard-inner` moves (`animation: uppy-Dashboard-slideUpFadeOut--small .3s cubic-bezier(0,0,.2,1)`) 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. — public/ranky_media.vendors.css:1
- `.uppy-Dashboard--modal.uppy-Dashboard--animateOpenClose.uppy-Dashboard--isClosing>.uppy-Dashboard-inner` moves (`animation: uppy-Dashboard-slideUpFadeOut .3s cubic-bezier(0,0,.2,1)`) 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. — public/ranky_media.vendors.css:1
- `.uppy-DashboardTab-btn svg` moves (`transition: transform .15s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — public/ranky_media.vendors.css:1
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 53 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — assets/.eslintrc.json:60
What to do
- Accessibility linting is already configured — assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
C2 · Access Controls
- This repository serves requests — a Symfony controller action (#[Route]) (src/Presentation/BackOffice/EmbedMediaBackOfficeController.php:11) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — src/Presentation/BackOffice/EmbedMediaBackOfficeController.php:11
What to do
- Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
- `DeleteMedia.__invoke` saves `MediaRepositoryInterface`, `FileRepositoryInterface` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — src/Application/DeleteMedia/DeleteMedia.php:22
What to do
- Mutate one aggregate per operation and let the others follow from a domain event — the second aggregate reaching consistency a moment later is the design, not a compromise.
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM4 · Rich vs anemic model
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Describe the projects a newcomer cannot place from the root README: 3 of 4 have no README of their own, in their folder or in their family's project (`tools/behat`, `tools/php-cs-fixer`, `tools/phpstan`).
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P11 · BDD / executable specs
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling
- `assets/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — assets/package.json:38
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- assets/src/components/Modal/File/MimeShow/Image.tsx:6 · assets/src/components/Modal/File/MimeShow/ImageResponsive.tsx:7 — 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. — assets/src/components/Modal/File/MimeShow/Image.tsx:6
- assets/src/components/Layout/PageListLayout.tsx:140 · assets/src/components/Modal/File/ModalFileContent.tsx:124 — 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. — assets/src/components/Layout/PageListLayout.tsx:140
- assets/src/load.tsx:28 · assets/src/load.tsx:60 — the two spans are one implementation copied and then locally edited — 61 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — assets/src/load.tsx:28
- assets/src/components/Modal/File/MimeShow/Application.tsx:5 · assets/src/components/Modal/File/MimeShow/Text.tsx:5 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — assets/src/components/Modal/File/MimeShow/Application.tsx:5
- assets/src/components/Layout/MimeList/Application.tsx:5 · assets/src/components/Layout/MimeList/Audio.tsx:5 · assets/src/components/Layout/MimeList/Text.tsx:5 · assets/src/components/Layout/MimeList/Video.tsx:5 — the 4 copies are spread across 4 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — assets/src/components/Layout/MimeList/Application.tsx:5
- assets/src/components/Layout/MimeList/MimeList.tsx:12 · assets/src/components/Modal/File/MimeShow/MimeShow.tsx:15 — 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. — assets/src/components/Layout/MimeList/MimeList.tsx:12
- assets/src/components/Modal/File/MimeShow/Image.tsx:41 · assets/src/components/Modal/File/MimeShow/ImageSvg.tsx:9 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — assets/src/components/Modal/File/MimeShow/Image.tsx:41
- assets/src/api/hook/useMediaQuery.tsx:79 · assets/src/api/hook/useMediaQuery.tsx:100 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — assets/src/api/hook/useMediaQuery.tsx:79
- assets/src/components/Layout/MimeList/Image.tsx:14 · assets/src/components/Layout/MimeList/Image.tsx:29 · assets/src/components/Layout/MimeList/Image.tsx:51 — all 3 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — assets/src/components/Layout/MimeList/Image.tsx:14
- assets/src/components/Layout/PageGridLayout.tsx:11 · assets/src/components/Layout/PageSelectableLayout.tsx:53 — the two spans are one implementation copied and then locally edited — 69 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. — assets/src/components/Layout/PageGridLayout.tsx:11
- assets/src/components/Layout/MimeList/Image.tsx:28 · assets/src/components/Modal/File/MimeShow/Image.tsx:27 · assets/src/components/Modal/File/MimeShow/ImageResponsive.tsx:28 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — assets/src/components/Layout/MimeList/Image.tsx:28
- assets/src/components/Layout/MimeList/Image.tsx:6 · assets/src/components/Modal/File/MimeShow/Image.tsx:6 · assets/src/components/Modal/File/MimeShow/ImageResponsive.tsx:7 — the 3 copies are spread across 3 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. — assets/src/components/Layout/MimeList/Image.tsx:6
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.
R2 · Cyclomatic Complexity
R3 · Large Files
R4 · Test Coverage
- 0% of 65 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
R7 · Dead Code
R8 · Dependency Hygiene
- Declared in assets/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. (×3)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- assets/src/context/MediaContext.tsx → assets/src/types/PageLayout.ts → assets/src/components/Layout/PageGridLayout.tsx → assets/src/components/Layout/MimeList/MimeList.tsx → assets/src/components/Layout/MimeList/Application.tsx → assets/src/components/Common/Asset.tsx → assets/src/api/hook/useSettings.tsx → assets/src/context/MediaContext.tsx (one verified cycle inside a mutually-dependent group of 16 files) — assets/src/context/MediaContext.tsx:10
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 0/2 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.
- `fetcher` 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 })`. (×2) — assets/src/helpers/fetch.ts:14, assets/src/api/repository/BaseRepository.ts:16
What to do
- Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
- `translatedMessage` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:17
- `html.trim()` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — assets/src/helpers/html.js:8
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `catch (\Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — src/Presentation/Form/DataTransformer/MediaPathTransformer.php:53, src/Infrastructure/Persistence/Orm/Repository/DoctrineOrmUserMediaRepository.php:60
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
X5 · Nullable reference types
- This repository commits no PHPStan or Psalm configuration (`phpstan.neon[.dist]`, `phpstan.dist.neon`, `psalm.xml[.dist]`, or one a composer.json script names with `--configuration`), so nothing checks null: a `?Customer` reaches `->name()` silently and throws `Error: Call to a member function name() on null` the first time it is null. If the build passes a level on a command line instead, put it in a committed configuration — this check reads configuration, and configuration is all it can read.
What to do
- Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 58% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 78% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 50% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 55% | Adequate — gated by R4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 24% | Critical — gated by D29, D36, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 97% | Exemplary | Solid. |
| Accessibility | 43% | Weak — gated by AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 54 check(s) not relevant to this codebase
- 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).
- AX6 Interface segregation — no exported interface declares behaviour
- 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) — mariadb Built php Built container ranky-media-bundle-mariadb-1 exited (1); runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no data at rest for these controls to protect.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone_number, …) or stored credential in a Laravel migration, an Eloquent model's $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D11 Test Reliability — Test reliability not included — no .php test runner
- D12 Dependency Hygiene — Not scored — 15 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript, PHP not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (recipes), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .php source were not judged.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 65 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- 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
- 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 — applicable but not scored (2 of 3 signals for this style — below the bar we score at): a PHP event-sourcing aggregate base (broadway/prooph/EventSauce AggregateRoot); 1 PHP aggregate(s) recording domain events (recordThat/apply)
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript, PHP source (service entry point: src/Presentation/BackOffice/EmbedMediaBackOfficeController.php:11 (#[Route())
- P8 Schema migrations — Doctrine is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 62 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <input> without a programmatic label assets/src/components/Layout/PageListLayout.tsx:97
- <input> without a programmatic label assets/src/components/Layout/PageListLayout.tsx:116
- <input> without a programmatic label assets/src/components/Modal/File/ModalFileContent.tsx:154
- <input> without a programmatic label assets/src/components/Modal/File/ModalFileContent.tsx:158
- <input> without a programmatic label assets/src/components/Modal/File/ModalFileContent.tsx:160
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <select> without a programmatic label assets/src/components/Form/Filters/SelectFilter.tsx:17
- <select> without a programmatic label assets/src/components/Layout/PageListLayout.tsx:87
- <button> with no accessible text assets/src/components/Layout/PageSelectableLayout.tsx:80
- Viewport restricts zoom templates/embed.html.twig:5
- Double-click handler on a non-interactive <li> assets/src/components/Layout/PageSelectableLayout.tsx:57
- REDACTED
- REDACTED
- REDACTED
- Import cycle (7 files) assets/src/context/MediaContext.tsx:10
Serious — 124 finding(s)
- Focus outline removed in CSS without a :focus replacement public/ranky_media.css:9
- Focus outline removed in CSS without a :focus replacement public/ranky_media.css:9
- Focus outline removed in CSS without a :focus replacement public/ranky_media.css:9
- Focus outline removed in CSS without a :focus replacement public/ranky_media.css:9
- Focus outline removed in CSS without a :focus replacement public/ranky_media.css:9
- Focus outline removed in CSS without a :focus replacement public/ranky_media.css:9
- Focus outline removed in CSS without a :focus replacement public/ranky_media.css:9
- Focus outline removed in CSS without a :focus replacement public/ranky_media.css:9
- Focus outline removed in CSS without a :focus replacement public/ranky_media.css:9
- Focus outline removed in CSS without a :focus replacement public/ranky_media.vendors.css:1
- Focus outline removed in CSS without a :focus replacement public/ranky_media.vendors.css:1
- Focus outline removed in CSS without a :focus replacement public/ranky_media.vendors.css:1
- Focus outline removed in CSS without a :focus replacement public/ranky_media.vendors.css:1
- Focus outline removed in CSS without a :focus replacement assets/src/styles/media.scss:267
- Focus outline removed in CSS without a :focus replacement assets/src/styles/media.scss:331
- Focus outline removed in CSS without a :focus replacement assets/src/styles/media_modal.scss:35
- Focus outline removed in CSS without a :focus replacement assets/src/styles/media_modal.scss:140
- Focus outline removed in CSS without a :focus replacement assets/src/styles/media_modal.scss:12
- Focus outline removed in CSS without a :focus replacement assets/src/styles/reset.scss:220
- Focus outline removed in CSS without a :focus replacement assets/src/styles/uppy.scss:34
- Focus outline removed in CSS without a :focus replacement assets/src/components/Modal/File/modal_file.scss:372
- Focus outline removed in CSS without a :focus replacement assets/src/components/Modal/File/modal_file.scss:178
- Focus outline removed in CSS without a :focus replacement assets/src/components/Modal/File/modal_file.scss:30
- Animation without a prefers-reduced-motion guard public/ranky_media.css:1
- Animation without a prefers-reduced-motion guard public/ranky_media.css:1
- Animation without a prefers-reduced-motion guard public/ranky_media.css:9
- Animation without a prefers-reduced-motion guard public/ranky_media.css:9
- Animation without a prefers-reduced-motion guard public/ranky_media.css:9
- Animation without a prefers-reduced-motion guard public/ranky_media.vendors.css:1
- Animation without a prefers-reduced-motion guard public/ranky_media.vendors.css:1
- Animation without a prefers-reduced-motion guard public/ranky_media.vendors.css:1
- Animation without a prefers-reduced-motion guard public/ranky_media.vendors.css:1
- Animation without a prefers-reduced-motion guard public/ranky_media.vendors.css:1
- Animation without a prefers-reduced-motion guard public/ranky_media.vendors.css:1
- Animation without a prefers-reduced-motion guard public/ranky_media.vendors.css:1
- Animation without a prefers-reduced-motion guard public/ranky_media.vendors.css:1
- Animation without a prefers-reduced-motion guard public/ranky_media.vendors.css:1
- Animation without a prefers-reduced-motion guard public/ranky_media.vendors.css:1
- Animation without a prefers-reduced-motion guard public/ranky_media.vendors.css:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment tests/src/Dummy/User/Domain/User.php:92
- TodoComment src/Infrastructure/Persistence/Orm/Repository/DoctrineOrmUserMediaRepository.php:61
- TodoComment src/Infrastructure/Filesystem/Local/LocalFileRepository.php:32
- TodoComment src/Infrastructure/Filesystem/Local/LocalFileRepository.php:38
- TodoComment src/Application/FileManipulation/RenameFile/RenameFile.php:45
- TodoComment src/Infrastructure/DependencyInjection/Configuration.php:19
- TodoComment src/Application/DataTransformer/Response/ThumbnailsResponse.php:68
- TodoComment assets/src/components/Dropzone/UppyModalDashboard.tsx:54
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FunctionTooLong: ModalFileContent.ModalFileContent assets/src/components/Modal/File/ModalFileContent.tsx:23
- FunctionTooLong: PageListLayout.PageListLayout assets/src/components/Layout/PageListLayout.tsx:13
- FunctionTooLong: ModalFile.ModalFile assets/src/components/Modal/File/ModalFile.tsx:16
- Async function without AbortSignal: fetcher assets/src/helpers/fetch.ts:14
- Async function without AbortSignal: fetcher assets/src/api/repository/BaseRepository.ts:16
- Untrusted text written into markup unescaped REDACTED:17
- Untrusted text written into markup unescaped assets/src/helpers/html.js:8
- Swallowed exception (caught, then discarded) src/Presentation/Form/DataTransformer/MediaPathTransformer.php:53
- Swallowed exception (caught, then discarded) src/Infrastructure/Persistence/Orm/Repository/DoctrineOrmUserMediaRepository.php:60
- <video> without a captions track templates/preview/mime-show/video.html.twig:2
- Page without a main landmark templates/embed.html.twig:2
- Modal dialog does not manage focus assets/src/components/Modal/File/ModalFile.tsx:93
- Low contrast colour pair in CSS (3.6:1) public/ranky_media.css:9
- No authorization src/Presentation/BackOffice/EmbedMediaBackOfficeController.php:11
- InterventionFileResize.resize (cyclomatic 18) src/Infrastructure/FileManipulation/Thumbnails/Resize/InterventionFileResize.php:25
- InterventionFileResize.resize (cognitive 21) src/Infrastructure/FileManipulation/Thumbnails/Resize/InterventionFileResize.php:25
- MediaBundleExtension.checkConfiguration (cognitive 16) src/Infrastructure/DependencyInjection/MediaBundleExtension.php:180
- FormFilters.FormFilters (cognitive 16) assets/src/components/Form/Filters/FormFilters.tsx:16
- REDACTED
- REDACTED
- MethodTooLong: Configuration.getConfigTreeBuilder src/Infrastructure/DependencyInjection/Configuration.php:17
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (26–29 lines × 2) src/Infrastructure/FileManipulation/Thumbnails/Resize/FfmpegGifFileResize.php:26
- Duplicated block (23 lines × 6) src/Infrastructure/Persistence/Dql/Mysql/MimeSubType.php:22
- Duplicated block (16 lines × 2) src/Infrastructure/Persistence/Dql/Mysql/Month.php:22
- Duplicated block (19 lines × 2) src/Infrastructure/Persistence/Dql/Postgresql/Month.php:20
- Duplicated block (13 lines × 2) src/Application/DataTransformer/Response/ThumbnailsResponse.php:42
- Duplicated block (6 lines × 3) src/Domain/Service/FileCompressHandler.php:39
- Low cohesion: DoctrineOrmMediaRepository (LCOM4 7) src/Infrastructure/Persistence/Orm/Repository/DoctrineOrmMediaRepository.php:28
- One operation mutates 2 aggregates: DeleteMedia.__invoke src/Application/DeleteMedia/DeleteMedia.php:22
- Duplicated block (27 lines × 2 locations) assets/src/components/Modal/File/MimeShow/Image.tsx:6
- Duplicated block (18 lines × 2 locations) assets/src/components/Layout/PageListLayout.tsx:140
- Duplicated block with local edits (14 matched lines × 2 locations) assets/src/load.tsx:28
- Duplicated block (12 lines × 2 locations) assets/src/components/Modal/File/MimeShow/Application.tsx:5
- Duplicated block (11 lines × 4 locations) assets/src/components/Layout/MimeList/Application.tsx:5
- Duplicated block (11 lines × 2 locations) assets/src/components/Layout/MimeList/MimeList.tsx:12
- Duplicated block (10 lines × 2 locations) assets/src/components/Modal/File/MimeShow/Image.tsx:41
- Duplicated block (9 lines × 2 locations) assets/src/api/hook/useMediaQuery.tsx:79
- Duplicated block (8 lines × 3 locations) assets/src/components/Layout/MimeList/Image.tsx:14
- Duplicated block with local edits (8 matched lines × 2 locations) assets/src/components/Layout/PageGridLayout.tsx:11
- Duplicated block (7 lines × 3 locations) assets/src/components/Layout/MimeList/Image.tsx:28
- Duplicated block (5 lines × 3 locations) assets/src/components/Layout/MimeList/Image.tsx:6
- Test Coverage
- Unused dependency '@uppy/tus'
- Unused dependency 'html-react-parser'
- Unused dependency 'regenerator-runtime'
Minor — 62 finding(s)
- Orphaned file src/Infrastructure/DependencyInjection/MediaBundleExtension.php:1
- Orphaned file src/Infrastructure/DependencyInjection/Configuration.php:1
- Orphaned file assets/src/components/Modal/File/ModalFileContent.tsx:1
- Orphaned file assets/src/components/Layout/PageListLayout.tsx:1
- Orphaned file src/Infrastructure/Persistence/Orm/Repository/DoctrineOrmMediaRepository.php:1
- Orphaned file src/Domain/Model/Media.php:1
- Orphaned file assets/src/components/Modal/File/ModalFile.tsx:1
- Orphaned file assets/src/MediaFormPreview.tsx:1
- Orphaned file assets/src/components/Dropzone/UppyModalDashboard.tsx:1
- Orphaned file assets/src/MediaManagerModal.tsx:1
- Orphaned file src/Application/FileManipulation/Thumbnails/GenerateThumbnails/AbstractGenerateImageThumbnails.php:1
- Orphaned file assets/src/components/Layout/PageSelectableLayout.tsx:1
- Orphaned file config/services.php:1
- Orphaned file src/Infrastructure/FileManipulation/Thumbnails/Resize/InterventionFileResize.php:1
- Orphaned file assets/src/components/Form/Filters/FormFilters.tsx:1
- Orphaned file assets/src/load.tsx:1
- Orphaned file src/Presentation/Form/RankyMediaFileManagerType.php:1
- Orphaned file src/Application/DataTransformer/Response/MediaResponse.php:1
- Orphaned file src/Infrastructure/Filesystem/Local/LocalFileRepository.php:1
- Orphaned file assets/src/api/hook/useMediaQuery.tsx:1
- Orphaned file src/Presentation/Form/EasyAdmin/EARankyMediaFileManagerField.php:1
- Orphaned file assets/src/api/model/Settings.ts:1
- Orphaned file src/Infrastructure/Filesystem/Local/LocalFileUrlResolver.php:1
- Orphaned file src/Domain/ValueObject/File.php:1
- Orphaned file src/Application/FileManipulation/CompressFile/CompressFile.php:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Accessibility enforcement below the top rung assets/.eslintrc.json:60
- Projects may be oversized for their cohesion
- REDACTED
- Dormant codebase
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No dependency-update automation assets/package.json:38
- Duplicated predicate assets/src/components/Layout/MimeList/MimeList.tsx:20
- Not all async functions that make a request accept an AbortSignal
- PHP static analysis does not check null everywhere
- Pending state with no failure state assets/src/MediaManager.tsx:33
- Silent fallback default in catch src/Presentation/Form/DataTransformer/MediaPathTransformer.php:53
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-501abff1dfb442af81fcced77efcea18/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-501abff1dfb442af81fcced77efcea18/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude public/uppy . | 29 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 52 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 7 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 65 file(s) — `src/Application/CreateMedia/CreateMedia.php`, `src/Application/CreateMedia/FileCompressOnMediaCreated.php`, `src/Application/CreateMedia/GenerateThumbnailsOnMediaCreated.php`, `src/Application/CreateMedia/UploadedFileRequest.php`, `src/Application/DataTransformer/MediaToResponseTransformer.php`, … (+60 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |