Executive summary
spatie/laravel-medialibrary falls short of our standard for production because we found no recorded design decisions and no architecture document or diagram. It scores 64.4 out of 100 and is rated Adequate, and 13 of its 15 critical findings are security problems in the build pipeline and in its automatic dependency updates.
Maturity, at 58.0, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 5.7 points. Adding build and run instructions to the README comes next, worth about 3.6 points. Raising Maturity to 70 would lift the score to about 68.8.
Eleven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One automatic update takes new releases before a bad one can be spotted, and one secret can leak from the build pipeline. Pinning each tool to an exact version, setting a waiting period for automatic updates and limiting the secret to its own step would close these risks. The loop of parts of the code that depend on each other needs breaking by moving the shared parts into a project of their own.
The product code is 5,872 lines, about €17,000 to rebuild.
If Maturity rose from 58.0 to 70, the lowest score rated Strong, the score would rise from 64.4 to about 68.8.
New since the last survey: 7 findings
- Code Duplication · Edited copy of a member (21 corresponding lines) src/Support/FileRemover/DefaultFileRemover.php
- Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) src/InteractsWithMedia.php
- Code Duplication · Edited copy of a member (19 corresponding lines) src/Conversions/FileManipulator.php
- Code Duplication · Edited copy of a member (10 corresponding lines) src/MediaCollections/Filesystem.php
- Code Duplication · Edited copy of a member (15 corresponding lines) src/MediaCollections/Filesystem.php
- Code Duplication · Duplicated block (13 lines × 2) src/MediaCollections/Filesystem.php
- Coupling · Circular dependency src/HasMedia.php
Rebuild cost: about €17,000 · Estimate
| Cost to rebuild | €5,500 to €28,000, for 92 to 292 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 64. 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: 5,872 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Downloaders | 2 Enums | 3 MediaCollections.Contracts | 4 MediaCollections.Models.Collections | 5 MediaCollections.Models.Concerns | 6 ResponsiveImages.Exceptions | 7 ResponsiveImages.TinyPlaceholderGenerator | 8 ResponsiveImages.WidthCalculator | 9 Support | 10 Support.Factories | 11 MediaCollections | 12 Support.FileNamer | 13 Support.PathGenerator | 14 ResponsiveImages | 15 Support.UrlGenerator | 16 MediaCollections.Models | 17 Conversions | 18 MediaCollections.Models.Observers | 19 ResponsiveImages.Events | 20 ResponsiveImages.Jobs | 21 Support.FileRemover | 22 Spatie.MediaLibrary | 23 Conversions.Actions | 24 Conversions.Commands | 25 Conversions.Events | 26 Conversions.ImageGenerators | 27 Conversions.Jobs | 28 MediaCollections.Commands | 29 MediaCollections.Events | 30 MediaCollections.Exceptions |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Downloaders | ||||||||||||||||||||||||||||||
| 2 Enums | ||||||||||||||||||||||||||||||
| 3 MediaCollections.Contracts | ||||||||||||||||||||||||||||||
| 4 MediaCollections.Models.Collections | ||||||||||||||||||||||||||||||
| 5 MediaCollections.Models.Concerns | ||||||||||||||||||||||||||||||
| 6 ResponsiveImages.Exceptions | ||||||||||||||||||||||||||||||
| 7 ResponsiveImages.TinyPlaceholderGenerator | ||||||||||||||||||||||||||||||
| 8 ResponsiveImages.WidthCalculator | ||||||||||||||||||||||||||||||
| 9 Support | ||||||||||||||||||||||||||||||
| 10 Support.Factories | ||||||||||||||||||||||||||||||
| 11 MediaCollections | 1 | 4 | 2 | |||||||||||||||||||||||||||
| 12 Support.FileNamer | 1 | 2 | ||||||||||||||||||||||||||||
| 13 Support.PathGenerator | 3 | |||||||||||||||||||||||||||||
| 14 ResponsiveImages | 1 | 1 | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||
| 15 Support.UrlGenerator | 2 | 3 | 2 | |||||||||||||||||||||||||||
| 16 MediaCollections.Models | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||
| 17 Conversions | 1 | 1 | 3 | |||||||||||||||||||||||||||
| 18 MediaCollections.Models.Observers | 1 | |||||||||||||||||||||||||||||
| 19 ResponsiveImages.Events | 1 | |||||||||||||||||||||||||||||
| 20 ResponsiveImages.Jobs | 1 | |||||||||||||||||||||||||||||
| 21 Support.FileRemover | 2 | 4 | ||||||||||||||||||||||||||||
| 22 Spatie.MediaLibrary | 1 | 1 | 5 | 2 | 2 | |||||||||||||||||||||||||
| 23 Conversions.Actions | 2 | 2 | ||||||||||||||||||||||||||||
| 24 Conversions.Commands | 1 | 1 | ||||||||||||||||||||||||||||
| 25 Conversions.Events | 2 | 2 | ||||||||||||||||||||||||||||
| 26 Conversions.ImageGenerators | 2 | 7 | ||||||||||||||||||||||||||||
| 27 Conversions.Jobs | 1 | 2 | ||||||||||||||||||||||||||||
| 28 MediaCollections.Commands | 2 | 1 | 1 | |||||||||||||||||||||||||||
| 29 MediaCollections.Events | 1 | 1 | ||||||||||||||||||||||||||||
| 30 MediaCollections.Exceptions | 2 | 1 | 1 |
11→9 MediaCollections uses Support✕
- Connections
- 1 pair of types, where a type in MediaCollections uses a type in Support.
- The types involved
Spatie.MediaLibrary.MediaCollections.Filesystem→Spatie.MediaLibrary.Support.RemoteFile
- Direction
- MediaCollections uses Support, so a change to Support can break MediaCollections, while a change to MediaCollections can't break Support.
- Position
- Below the diagonal: MediaCollections uses a module listed above it, which is the healthy direction.
11→16 MediaCollections uses MediaCollections.Models part of a loop✕
- Connections
- 4 pairs of types, where a type in MediaCollections uses a type in MediaCollections.Models.
- The types involved
Spatie.MediaLibrary.MediaCollections.FileAdder→Spatie.MediaLibrary.MediaCollections.Models.MediaSpatie.MediaLibrary.MediaCollections.Filesystem→Spatie.MediaLibrary.MediaCollections.Models.MediaSpatie.MediaLibrary.MediaCollections.HtmlableMedia→Spatie.MediaLibrary.MediaCollections.Models.MediaSpatie.MediaLibrary.MediaCollections.MediaRepository→Spatie.MediaLibrary.MediaCollections.Models.Media
- Direction
- MediaCollections uses MediaCollections.Models, so a change to MediaCollections.Models can break MediaCollections, while a change to MediaCollections can't break MediaCollections.Models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→22 MediaCollections uses Spatie.MediaLibrary part of a loop✕
- Connections
- 2 pairs of types, where a type in MediaCollections uses a type in Spatie.MediaLibrary.
- The types involved
Spatie.MediaLibrary.MediaCollections.FileAdder→Spatie.MediaLibrary.HasMediaSpatie.MediaLibrary.MediaCollections.MediaRepository→Spatie.MediaLibrary.HasMedia
- Direction
- MediaCollections uses Spatie.MediaLibrary, so a change to Spatie.MediaLibrary can break MediaCollections, while a change to MediaCollections can't break Spatie.MediaLibrary.
- 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→16 Support.FileNamer uses MediaCollections.Models part of a loop✕
- Connections
- 1 pair of types, where a type in Support.FileNamer uses a type in MediaCollections.Models.
- The types involved
Spatie.MediaLibrary.Support.FileNamer.FileNamer→Spatie.MediaLibrary.MediaCollections.Models.Media
- Direction
- Support.FileNamer uses MediaCollections.Models, so a change to MediaCollections.Models can break Support.FileNamer, while a change to Support.FileNamer can't break MediaCollections.Models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→17 Support.FileNamer uses Conversions part of a loop✕
- Connections
- 2 pairs of types, where a type in Support.FileNamer uses a type in Conversions.
- The types involved
Spatie.MediaLibrary.Support.FileNamer.DefaultFileNamer→Spatie.MediaLibrary.Conversions.ConversionSpatie.MediaLibrary.Support.FileNamer.FileNamer→Spatie.MediaLibrary.Conversions.Conversion
- Direction
- Support.FileNamer uses Conversions, so a change to Conversions can break Support.FileNamer, while a change to Support.FileNamer can't break Conversions.
- 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→16 Support.PathGenerator uses MediaCollections.Models part of a loop✕
- Connections
- 3 pairs of types, where a type in Support.PathGenerator uses a type in MediaCollections.Models.
- The types involved
Spatie.MediaLibrary.Support.PathGenerator.DefaultPathGenerator→Spatie.MediaLibrary.MediaCollections.Models.MediaSpatie.MediaLibrary.Support.PathGenerator.PathGenerator→Spatie.MediaLibrary.MediaCollections.Models.MediaSpatie.MediaLibrary.Support.PathGenerator.PathGeneratorFactory→Spatie.MediaLibrary.MediaCollections.Models.Media
- Direction
- Support.PathGenerator uses MediaCollections.Models, so a change to MediaCollections.Models can break Support.PathGenerator, while a change to Support.PathGenerator can't break MediaCollections.Models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→7 ResponsiveImages uses ResponsiveImages.TinyPlaceholderGenerator✕
- Connections
- 1 pair of types, where a type in ResponsiveImages uses a type in ResponsiveImages.TinyPlaceholderGenerator.
- The types involved
Spatie.MediaLibrary.ResponsiveImages.ResponsiveImageGenerator→Spatie.MediaLibrary.ResponsiveImages.TinyPlaceholderGenerator.TinyPlaceholderGenerator
- Direction
- ResponsiveImages uses ResponsiveImages.TinyPlaceholderGenerator, so a change to ResponsiveImages.TinyPlaceholderGenerator can break ResponsiveImages, while a change to ResponsiveImages can't break ResponsiveImages.TinyPlaceholderGenerator.
- Position
- Below the diagonal: ResponsiveImages uses a module listed above it, which is the healthy direction.
14→8 ResponsiveImages uses ResponsiveImages.WidthCalculator✕
- Connections
- 1 pair of types, where a type in ResponsiveImages uses a type in ResponsiveImages.WidthCalculator.
- The types involved
Spatie.MediaLibrary.ResponsiveImages.ResponsiveImageGenerator→Spatie.MediaLibrary.ResponsiveImages.WidthCalculator.WidthCalculator
- Direction
- ResponsiveImages uses ResponsiveImages.WidthCalculator, so a change to ResponsiveImages.WidthCalculator can break ResponsiveImages, while a change to ResponsiveImages can't break ResponsiveImages.WidthCalculator.
- Position
- Below the diagonal: ResponsiveImages uses a module listed above it, which is the healthy direction.
14→11 ResponsiveImages uses MediaCollections✕
- Connections
- 1 pair of types, where a type in ResponsiveImages uses a type in MediaCollections.
- The types involved
Spatie.MediaLibrary.ResponsiveImages.ResponsiveImageGenerator→Spatie.MediaLibrary.MediaCollections.Filesystem
- Direction
- ResponsiveImages uses MediaCollections, so a change to MediaCollections can break ResponsiveImages, while a change to ResponsiveImages can't break MediaCollections.
- Position
- Below the diagonal: ResponsiveImages uses a module listed above it, which is the healthy direction.
14→12 ResponsiveImages uses Support.FileNamer✕
- Connections
- 1 pair of types, where a type in ResponsiveImages uses a type in Support.FileNamer.
- The types involved
Spatie.MediaLibrary.ResponsiveImages.ResponsiveImageGenerator→Spatie.MediaLibrary.Support.FileNamer.FileNamer
- Direction
- ResponsiveImages uses Support.FileNamer, so a change to Support.FileNamer can break ResponsiveImages, while a change to ResponsiveImages can't break Support.FileNamer.
- Position
- Below the diagonal: ResponsiveImages uses a module listed above it, which is the healthy direction.
14→16 ResponsiveImages uses MediaCollections.Models part of a loop✕
- Connections
- 3 pairs of types, where a type in ResponsiveImages uses a type in MediaCollections.Models.
- The types involved
Spatie.MediaLibrary.ResponsiveImages.RegisteredResponsiveImages→Spatie.MediaLibrary.MediaCollections.Models.MediaSpatie.MediaLibrary.ResponsiveImages.ResponsiveImage→Spatie.MediaLibrary.MediaCollections.Models.MediaSpatie.MediaLibrary.ResponsiveImages.ResponsiveImageGenerator→Spatie.MediaLibrary.MediaCollections.Models.Media
- Direction
- ResponsiveImages uses MediaCollections.Models, so a change to MediaCollections.Models can break ResponsiveImages, while a change to ResponsiveImages can't break MediaCollections.Models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→17 ResponsiveImages uses Conversions part of a loop✕
- Connections
- 1 pair of types, where a type in ResponsiveImages uses a type in Conversions.
- The types involved
Spatie.MediaLibrary.ResponsiveImages.ResponsiveImageGenerator→Spatie.MediaLibrary.Conversions.Conversion
- Direction
- ResponsiveImages uses Conversions, so a change to Conversions can break ResponsiveImages, while a change to ResponsiveImages can't break Conversions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→13 Support.UrlGenerator uses Support.PathGenerator✕
- Connections
- 2 pairs of types, where a type in Support.UrlGenerator uses a type in Support.PathGenerator.
- The types involved
Spatie.MediaLibrary.Support.UrlGenerator.BaseUrlGenerator→Spatie.MediaLibrary.Support.PathGenerator.PathGeneratorSpatie.MediaLibrary.Support.UrlGenerator.UrlGenerator→Spatie.MediaLibrary.Support.PathGenerator.PathGenerator
- Direction
- Support.UrlGenerator uses Support.PathGenerator, so a change to Support.PathGenerator can break Support.UrlGenerator, while a change to Support.UrlGenerator can't break Support.PathGenerator.
- Position
- Below the diagonal: Support.UrlGenerator uses a module listed above it, which is the healthy direction.
15→16 Support.UrlGenerator uses MediaCollections.Models part of a loop✕
- Connections
- 3 pairs of types, where a type in Support.UrlGenerator uses a type in MediaCollections.Models.
- The types involved
Spatie.MediaLibrary.Support.UrlGenerator.BaseUrlGenerator→Spatie.MediaLibrary.MediaCollections.Models.MediaSpatie.MediaLibrary.Support.UrlGenerator.UrlGenerator→Spatie.MediaLibrary.MediaCollections.Models.MediaSpatie.MediaLibrary.Support.UrlGenerator.UrlGeneratorFactory→Spatie.MediaLibrary.MediaCollections.Models.Media
- Direction
- Support.UrlGenerator uses MediaCollections.Models, so a change to MediaCollections.Models can break Support.UrlGenerator, while a change to Support.UrlGenerator can't break MediaCollections.Models.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→17 Support.UrlGenerator uses Conversions part of a loop✕
- Connections
- 2 pairs of types, where a type in Support.UrlGenerator uses a type in Conversions.
- The types involved
Spatie.MediaLibrary.Support.UrlGenerator.BaseUrlGenerator→Spatie.MediaLibrary.Conversions.ConversionSpatie.MediaLibrary.Support.UrlGenerator.UrlGenerator→Spatie.MediaLibrary.Conversions.Conversion
- Direction
- Support.UrlGenerator uses Conversions, so a change to Conversions can break Support.UrlGenerator, while a change to Support.UrlGenerator can't break Conversions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→4 MediaCollections.Models uses MediaCollections.Models.Collections✕
- Connections
- 1 pair of types, where a type in MediaCollections.Models uses a type in MediaCollections.Models.Collections.
- The types involved
Spatie.MediaLibrary.MediaCollections.Models.Media→Spatie.MediaLibrary.MediaCollections.Models.Collections.MediaCollection
- Direction
- MediaCollections.Models uses MediaCollections.Models.Collections, so a change to MediaCollections.Models.Collections can break MediaCollections.Models, while a change to MediaCollections.Models can't break MediaCollections.Models.Collections.
- Position
- Below the diagonal: MediaCollections.Models uses a module listed above it, which is the healthy direction.
16→11 MediaCollections.Models uses MediaCollections✕
- Connections
- 1 pair of types, where a type in MediaCollections.Models uses a type in MediaCollections.
- The types involved
Spatie.MediaLibrary.MediaCollections.Models.Media→Spatie.MediaLibrary.MediaCollections.HtmlableMedia
- Direction
- MediaCollections.Models uses MediaCollections, so a change to MediaCollections can break MediaCollections.Models, while a change to MediaCollections.Models can't break MediaCollections.
- Position
- Below the diagonal: MediaCollections.Models uses a module listed above it, which is the healthy direction.
16→14 MediaCollections.Models uses ResponsiveImages✕
- Connections
- 1 pair of types, where a type in MediaCollections.Models uses a type in ResponsiveImages.
- The types involved
Spatie.MediaLibrary.MediaCollections.Models.Media→Spatie.MediaLibrary.ResponsiveImages.RegisteredResponsiveImages
- Direction
- MediaCollections.Models uses ResponsiveImages, so a change to ResponsiveImages can break MediaCollections.Models, while a change to MediaCollections.Models can't break ResponsiveImages.
- Position
- Below the diagonal: MediaCollections.Models uses a module listed above it, which is the healthy direction.
16→15 MediaCollections.Models uses Support.UrlGenerator✕
- Connections
- 1 pair of types, where a type in MediaCollections.Models uses a type in Support.UrlGenerator.
- The types involved
Spatie.MediaLibrary.MediaCollections.Models.Media→Spatie.MediaLibrary.Support.UrlGenerator.UrlGenerator
- Direction
- MediaCollections.Models uses Support.UrlGenerator, so a change to Support.UrlGenerator can break MediaCollections.Models, while a change to MediaCollections.Models can't break Support.UrlGenerator.
- Position
- Below the diagonal: MediaCollections.Models uses a module listed above it, which is the healthy direction.
16→22 MediaCollections.Models uses Spatie.MediaLibrary part of a loop✕
- Connections
- 1 pair of types, where a type in MediaCollections.Models uses a type in Spatie.MediaLibrary.
- The types involved
Spatie.MediaLibrary.MediaCollections.Models.Media→Spatie.MediaLibrary.HasMedia
- Direction
- MediaCollections.Models uses Spatie.MediaLibrary, so a change to Spatie.MediaLibrary can break MediaCollections.Models, while a change to MediaCollections.Models can't break Spatie.MediaLibrary.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→8 Conversions uses ResponsiveImages.WidthCalculator✕
- Connections
- 1 pair of types, where a type in Conversions uses a type in ResponsiveImages.WidthCalculator.
- The types involved
Spatie.MediaLibrary.Conversions.Conversion→Spatie.MediaLibrary.ResponsiveImages.WidthCalculator.WidthCalculator
- Direction
- Conversions uses ResponsiveImages.WidthCalculator, so a change to ResponsiveImages.WidthCalculator can break Conversions, while a change to Conversions can't break ResponsiveImages.WidthCalculator.
- Position
- Below the diagonal: Conversions uses a module listed above it, which is the healthy direction.
17→12 Conversions uses Support.FileNamer✕
- Connections
- 1 pair of types, where a type in Conversions uses a type in Support.FileNamer.
- The types involved
Spatie.MediaLibrary.Conversions.Conversion→Spatie.MediaLibrary.Support.FileNamer.FileNamer
- Direction
- Conversions uses Support.FileNamer, so a change to Support.FileNamer can break Conversions, while a change to Conversions can't break Support.FileNamer.
- Position
- Below the diagonal: Conversions uses a module listed above it, which is the healthy direction.
17→16 Conversions uses MediaCollections.Models✕
- Connections
- 3 pairs of types, where a type in Conversions uses a type in MediaCollections.Models.
- The types involved
Spatie.MediaLibrary.Conversions.Conversion→Spatie.MediaLibrary.MediaCollections.Models.MediaSpatie.MediaLibrary.Conversions.ConversionCollection→Spatie.MediaLibrary.MediaCollections.Models.MediaSpatie.MediaLibrary.Conversions.FileManipulator→Spatie.MediaLibrary.MediaCollections.Models.Media
- Direction
- Conversions uses MediaCollections.Models, so a change to MediaCollections.Models can break Conversions, while a change to Conversions can't break MediaCollections.Models.
- Position
- Below the diagonal: Conversions uses a module listed above it, which is the healthy direction.
18→16 MediaCollections.Models.Observers uses MediaCollections.Models✕
- Connections
- 1 pair of types, where a type in MediaCollections.Models.Observers uses a type in MediaCollections.Models.
- The types involved
Spatie.MediaLibrary.MediaCollections.Models.Observers.MediaObserver→Spatie.MediaLibrary.MediaCollections.Models.Media
- Direction
- MediaCollections.Models.Observers uses MediaCollections.Models, so a change to MediaCollections.Models can break MediaCollections.Models.Observers, while a change to MediaCollections.Models.Observers can't break MediaCollections.Models.
- Position
- Below the diagonal: MediaCollections.Models.Observers uses a module listed above it, which is the healthy direction.
19→16 ResponsiveImages.Events uses MediaCollections.Models✕
- Connections
- 1 pair of types, where a type in ResponsiveImages.Events uses a type in MediaCollections.Models.
- The types involved
Spatie.MediaLibrary.ResponsiveImages.Events.ResponsiveImagesGeneratedEvent→Spatie.MediaLibrary.MediaCollections.Models.Media
- Direction
- ResponsiveImages.Events uses MediaCollections.Models, so a change to MediaCollections.Models can break ResponsiveImages.Events, while a change to ResponsiveImages.Events can't break MediaCollections.Models.
- Position
- Below the diagonal: ResponsiveImages.Events uses a module listed above it, which is the healthy direction.
20→16 ResponsiveImages.Jobs uses MediaCollections.Models✕
- Connections
- 1 pair of types, where a type in ResponsiveImages.Jobs uses a type in MediaCollections.Models.
- The types involved
Spatie.MediaLibrary.ResponsiveImages.Jobs.GenerateResponsiveImagesJob→Spatie.MediaLibrary.MediaCollections.Models.Media
- Direction
- ResponsiveImages.Jobs uses MediaCollections.Models, so a change to MediaCollections.Models can break ResponsiveImages.Jobs, while a change to ResponsiveImages.Jobs can't break MediaCollections.Models.
- Position
- Below the diagonal: ResponsiveImages.Jobs uses a module listed above it, which is the healthy direction.
21→11 Support.FileRemover uses MediaCollections✕
- Connections
- 2 pairs of types, where a type in Support.FileRemover uses a type in MediaCollections.
- The types involved
Spatie.MediaLibrary.Support.FileRemover.DefaultFileRemover→Spatie.MediaLibrary.MediaCollections.FilesystemSpatie.MediaLibrary.Support.FileRemover.FileRemover→Spatie.MediaLibrary.MediaCollections.Filesystem
- Direction
- Support.FileRemover uses MediaCollections, so a change to MediaCollections can break Support.FileRemover, while a change to Support.FileRemover can't break MediaCollections.
- Position
- Below the diagonal: Support.FileRemover uses a module listed above it, which is the healthy direction.
21→16 Support.FileRemover uses MediaCollections.Models✕
- Connections
- 4 pairs of types, where a type in Support.FileRemover uses a type in MediaCollections.Models.
- The types involved
Spatie.MediaLibrary.Support.FileRemover.DefaultFileRemover→Spatie.MediaLibrary.MediaCollections.Models.MediaSpatie.MediaLibrary.Support.FileRemover.FileBaseFileRemover→Spatie.MediaLibrary.MediaCollections.Models.MediaSpatie.MediaLibrary.Support.FileRemover.FileRemover→Spatie.MediaLibrary.MediaCollections.Models.MediaSpatie.MediaLibrary.Support.FileRemover.FileRemoverFactory→Spatie.MediaLibrary.MediaCollections.Models.Media
- Direction
- Support.FileRemover uses MediaCollections.Models, so a change to MediaCollections.Models can break Support.FileRemover, while a change to Support.FileRemover can't break MediaCollections.Models.
- Position
- Below the diagonal: Support.FileRemover uses a module listed above it, which is the healthy direction.
22→2 Spatie.MediaLibrary uses Enums✕
- Connections
- 1 pair of types, where a type in Spatie.MediaLibrary uses a type in Enums.
- The types involved
Spatie.MediaLibrary.InteractsWithMedia→Spatie.MediaLibrary.Enums.CollectionPosition
- Direction
- Spatie.MediaLibrary uses Enums, so a change to Enums can break Spatie.MediaLibrary, while a change to Spatie.MediaLibrary can't break Enums.
- Position
- Below the diagonal: Spatie.MediaLibrary uses a module listed above it, which is the healthy direction.
22→4 Spatie.MediaLibrary uses MediaCollections.Models.Collections✕
- Connections
- 1 pair of types, where a type in Spatie.MediaLibrary uses a type in MediaCollections.Models.Collections.
- The types involved
Spatie.MediaLibrary.InteractsWithMedia→Spatie.MediaLibrary.MediaCollections.Models.Collections.MediaCollection
- Direction
- Spatie.MediaLibrary uses MediaCollections.Models.Collections, so a change to MediaCollections.Models.Collections can break Spatie.MediaLibrary, while a change to Spatie.MediaLibrary can't break MediaCollections.Models.Collections.
- Position
- Below the diagonal: Spatie.MediaLibrary uses a module listed above it, which is the healthy direction.
22→11 Spatie.MediaLibrary uses MediaCollections✕
- Connections
- 5 pairs of types, where a type in Spatie.MediaLibrary uses a type in MediaCollections.
- The types involved
Spatie.MediaLibrary.HasMedia→Spatie.MediaLibrary.MediaCollections.FileAdderSpatie.MediaLibrary.HasMedia→Spatie.MediaLibrary.MediaCollections.MediaCollectionSpatie.MediaLibrary.InteractsWithMedia→Spatie.MediaLibrary.MediaCollections.FileAdderSpatie.MediaLibrary.InteractsWithMedia→Spatie.MediaLibrary.MediaCollections.MediaCollectionSpatie.MediaLibrary.InteractsWithMedia→Spatie.MediaLibrary.MediaCollections.MediaRepository
- Direction
- Spatie.MediaLibrary uses MediaCollections, so a change to MediaCollections can break Spatie.MediaLibrary, while a change to Spatie.MediaLibrary can't break MediaCollections.
- Position
- Below the diagonal: Spatie.MediaLibrary uses a module listed above it, which is the healthy direction.
22→16 Spatie.MediaLibrary uses MediaCollections.Models✕
- Connections
- 2 pairs of types, where a type in Spatie.MediaLibrary uses a type in MediaCollections.Models.
- The types involved
Spatie.MediaLibrary.HasMedia→Spatie.MediaLibrary.MediaCollections.Models.MediaSpatie.MediaLibrary.InteractsWithMedia→Spatie.MediaLibrary.MediaCollections.Models.Media
- Direction
- Spatie.MediaLibrary uses MediaCollections.Models, so a change to MediaCollections.Models can break Spatie.MediaLibrary, while a change to Spatie.MediaLibrary can't break MediaCollections.Models.
- Position
- Below the diagonal: Spatie.MediaLibrary uses a module listed above it, which is the healthy direction.
22→17 Spatie.MediaLibrary uses Conversions✕
- Connections
- 2 pairs of types, where a type in Spatie.MediaLibrary uses a type in Conversions.
- The types involved
Spatie.MediaLibrary.HasMedia→Spatie.MediaLibrary.Conversions.ConversionSpatie.MediaLibrary.InteractsWithMedia→Spatie.MediaLibrary.Conversions.Conversion
- Direction
- Spatie.MediaLibrary uses Conversions, so a change to Conversions can break Spatie.MediaLibrary, while a change to Spatie.MediaLibrary can't break Conversions.
- Position
- Below the diagonal: Spatie.MediaLibrary uses a module listed above it, which is the healthy direction.
23→16 Conversions.Actions uses MediaCollections.Models✕
- Connections
- 2 pairs of types, where a type in Conversions.Actions uses a type in MediaCollections.Models.
- The types involved
Spatie.MediaLibrary.Conversions.Actions.PerformConversionAction→Spatie.MediaLibrary.MediaCollections.Models.MediaSpatie.MediaLibrary.Conversions.Actions.PerformManipulationsAction→Spatie.MediaLibrary.MediaCollections.Models.Media
- Direction
- Conversions.Actions uses MediaCollections.Models, so a change to MediaCollections.Models can break Conversions.Actions, while a change to Conversions.Actions can't break MediaCollections.Models.
- Position
- Below the diagonal: Conversions.Actions uses a module listed above it, which is the healthy direction.
23→17 Conversions.Actions uses Conversions✕
- Connections
- 2 pairs of types, where a type in Conversions.Actions uses a type in Conversions.
- The types involved
Spatie.MediaLibrary.Conversions.Actions.PerformConversionAction→Spatie.MediaLibrary.Conversions.ConversionSpatie.MediaLibrary.Conversions.Actions.PerformManipulationsAction→Spatie.MediaLibrary.Conversions.Conversion
- Direction
- Conversions.Actions uses Conversions, so a change to Conversions can break Conversions.Actions, while a change to Conversions.Actions can't break Conversions.
- Position
- Below the diagonal: Conversions.Actions uses a module listed above it, which is the healthy direction.
24→11 Conversions.Commands uses MediaCollections✕
- Connections
- 1 pair of types, where a type in Conversions.Commands uses a type in MediaCollections.
- The types involved
Spatie.MediaLibrary.Conversions.Commands.RegenerateCommand→Spatie.MediaLibrary.MediaCollections.MediaRepository
- Direction
- Conversions.Commands uses MediaCollections, so a change to MediaCollections can break Conversions.Commands, while a change to Conversions.Commands can't break MediaCollections.
- Position
- Below the diagonal: Conversions.Commands uses a module listed above it, which is the healthy direction.
24→17 Conversions.Commands uses Conversions✕
- Connections
- 1 pair of types, where a type in Conversions.Commands uses a type in Conversions.
- The types involved
Spatie.MediaLibrary.Conversions.Commands.RegenerateCommand→Spatie.MediaLibrary.Conversions.FileManipulator
- Direction
- Conversions.Commands uses Conversions, so a change to Conversions can break Conversions.Commands, while a change to Conversions.Commands can't break Conversions.
- Position
- Below the diagonal: Conversions.Commands uses a module listed above it, which is the healthy direction.
25→16 Conversions.Events uses MediaCollections.Models✕
- Connections
- 2 pairs of types, where a type in Conversions.Events uses a type in MediaCollections.Models.
- The types involved
Spatie.MediaLibrary.Conversions.Events.ConversionHasBeenCompletedEvent→Spatie.MediaLibrary.MediaCollections.Models.MediaSpatie.MediaLibrary.Conversions.Events.ConversionWillStartEvent→Spatie.MediaLibrary.MediaCollections.Models.Media
- Direction
- Conversions.Events uses MediaCollections.Models, so a change to MediaCollections.Models can break Conversions.Events, while a change to Conversions.Events can't break MediaCollections.Models.
- Position
- Below the diagonal: Conversions.Events uses a module listed above it, which is the healthy direction.
25→17 Conversions.Events uses Conversions✕
- Connections
- 2 pairs of types, where a type in Conversions.Events uses a type in Conversions.
- The types involved
Spatie.MediaLibrary.Conversions.Events.ConversionHasBeenCompletedEvent→Spatie.MediaLibrary.Conversions.ConversionSpatie.MediaLibrary.Conversions.Events.ConversionWillStartEvent→Spatie.MediaLibrary.Conversions.Conversion
- Direction
- Conversions.Events uses Conversions, so a change to Conversions can break Conversions.Events, while a change to Conversions.Events can't break Conversions.
- Position
- Below the diagonal: Conversions.Events uses a module listed above it, which is the healthy direction.
26→16 Conversions.ImageGenerators uses MediaCollections.Models✕
- Connections
- 2 pairs of types, where a type in Conversions.ImageGenerators uses a type in MediaCollections.Models.
- The types involved
Spatie.MediaLibrary.Conversions.ImageGenerators.ImageGenerator→Spatie.MediaLibrary.MediaCollections.Models.MediaSpatie.MediaLibrary.Conversions.ImageGenerators.ImageGeneratorFactory→Spatie.MediaLibrary.MediaCollections.Models.Media
- Direction
- Conversions.ImageGenerators uses MediaCollections.Models, so a change to MediaCollections.Models can break Conversions.ImageGenerators, while a change to Conversions.ImageGenerators can't break MediaCollections.Models.
- Position
- Below the diagonal: Conversions.ImageGenerators uses a module listed above it, which is the healthy direction.
26→17 Conversions.ImageGenerators uses Conversions✕
- Connections
- 7 pairs of types, where a type in Conversions.ImageGenerators uses a type in Conversions.
- The types involved
Spatie.MediaLibrary.Conversions.ImageGenerators.Avif→Spatie.MediaLibrary.Conversions.ConversionSpatie.MediaLibrary.Conversions.ImageGenerators.Image→Spatie.MediaLibrary.Conversions.ConversionSpatie.MediaLibrary.Conversions.ImageGenerators.ImageGenerator→Spatie.MediaLibrary.Conversions.ConversionSpatie.MediaLibrary.Conversions.ImageGenerators.Pdf→Spatie.MediaLibrary.Conversions.ConversionSpatie.MediaLibrary.Conversions.ImageGenerators.Svg→Spatie.MediaLibrary.Conversions.ConversionSpatie.MediaLibrary.Conversions.ImageGenerators.Video→Spatie.MediaLibrary.Conversions.ConversionSpatie.MediaLibrary.Conversions.ImageGenerators.Webp→Spatie.MediaLibrary.Conversions.Conversion
- Direction
- Conversions.ImageGenerators uses Conversions, so a change to Conversions can break Conversions.ImageGenerators, while a change to Conversions.ImageGenerators can't break Conversions.
- Position
- Below the diagonal: Conversions.ImageGenerators uses a module listed above it, which is the healthy direction.
27→16 Conversions.Jobs uses MediaCollections.Models✕
- Connections
- 1 pair of types, where a type in Conversions.Jobs uses a type in MediaCollections.Models.
- The types involved
Spatie.MediaLibrary.Conversions.Jobs.PerformConversionsJob→Spatie.MediaLibrary.MediaCollections.Models.Media
- Direction
- Conversions.Jobs uses MediaCollections.Models, so a change to MediaCollections.Models can break Conversions.Jobs, while a change to Conversions.Jobs can't break MediaCollections.Models.
- Position
- Below the diagonal: Conversions.Jobs uses a module listed above it, which is the healthy direction.
27→17 Conversions.Jobs uses Conversions✕
- Connections
- 2 pairs of types, where a type in Conversions.Jobs uses a type in Conversions.
- The types involved
Spatie.MediaLibrary.Conversions.Jobs.PerformConversionsJob→Spatie.MediaLibrary.Conversions.ConversionCollectionSpatie.MediaLibrary.Conversions.Jobs.PerformConversionsJob→Spatie.MediaLibrary.Conversions.FileManipulator
- Direction
- Conversions.Jobs uses Conversions, so a change to Conversions can break Conversions.Jobs, while a change to Conversions.Jobs can't break Conversions.
- Position
- Below the diagonal: Conversions.Jobs uses a module listed above it, which is the healthy direction.
28→11 MediaCollections.Commands uses MediaCollections✕
- Connections
- 2 pairs of types, where a type in MediaCollections.Commands uses a type in MediaCollections.
- The types involved
Spatie.MediaLibrary.MediaCollections.Commands.CleanCommand→Spatie.MediaLibrary.MediaCollections.MediaRepositorySpatie.MediaLibrary.MediaCollections.Commands.ClearCommand→Spatie.MediaLibrary.MediaCollections.MediaRepository
- Direction
- MediaCollections.Commands uses MediaCollections, so a change to MediaCollections can break MediaCollections.Commands, while a change to MediaCollections.Commands can't break MediaCollections.
- Position
- Below the diagonal: MediaCollections.Commands uses a module listed above it, which is the healthy direction.
28→16 MediaCollections.Commands uses MediaCollections.Models✕
- Connections
- 1 pair of types, where a type in MediaCollections.Commands uses a type in MediaCollections.Models.
- The types involved
Spatie.MediaLibrary.MediaCollections.Commands.CleanCommand→Spatie.MediaLibrary.MediaCollections.Models.Media
- Direction
- MediaCollections.Commands uses MediaCollections.Models, so a change to MediaCollections.Models can break MediaCollections.Commands, while a change to MediaCollections.Commands can't break MediaCollections.Models.
- Position
- Below the diagonal: MediaCollections.Commands uses a module listed above it, which is the healthy direction.
28→17 MediaCollections.Commands uses Conversions✕
- Connections
- 1 pair of types, where a type in MediaCollections.Commands uses a type in Conversions.
- The types involved
Spatie.MediaLibrary.MediaCollections.Commands.CleanCommand→Spatie.MediaLibrary.Conversions.FileManipulator
- Direction
- MediaCollections.Commands uses Conversions, so a change to Conversions can break MediaCollections.Commands, while a change to MediaCollections.Commands can't break Conversions.
- Position
- Below the diagonal: MediaCollections.Commands uses a module listed above it, which is the healthy direction.
29→16 MediaCollections.Events uses MediaCollections.Models✕
- Connections
- 1 pair of types, where a type in MediaCollections.Events uses a type in MediaCollections.Models.
- The types involved
Spatie.MediaLibrary.MediaCollections.Events.MediaHasBeenAddedEvent→Spatie.MediaLibrary.MediaCollections.Models.Media
- Direction
- MediaCollections.Events uses MediaCollections.Models, so a change to MediaCollections.Models can break MediaCollections.Events, while a change to MediaCollections.Events can't break MediaCollections.Models.
- Position
- Below the diagonal: MediaCollections.Events uses a module listed above it, which is the healthy direction.
29→22 MediaCollections.Events uses Spatie.MediaLibrary✕
- Connections
- 1 pair of types, where a type in MediaCollections.Events uses a type in Spatie.MediaLibrary.
- The types involved
Spatie.MediaLibrary.MediaCollections.Events.CollectionHasBeenClearedEvent→Spatie.MediaLibrary.HasMedia
- Direction
- MediaCollections.Events uses Spatie.MediaLibrary, so a change to Spatie.MediaLibrary can break MediaCollections.Events, while a change to MediaCollections.Events can't break Spatie.MediaLibrary.
- Position
- Below the diagonal: MediaCollections.Events uses a module listed above it, which is the healthy direction.
30→11 MediaCollections.Exceptions uses MediaCollections✕
- Connections
- 2 pairs of types, where a type in MediaCollections.Exceptions uses a type in MediaCollections.
- The types involved
Spatie.MediaLibrary.MediaCollections.Exceptions.FileUnacceptableForCollection→Spatie.MediaLibrary.MediaCollections.FileSpatie.MediaLibrary.MediaCollections.Exceptions.FileUnacceptableForCollection→Spatie.MediaLibrary.MediaCollections.MediaCollection
- Direction
- MediaCollections.Exceptions uses MediaCollections, so a change to MediaCollections can break MediaCollections.Exceptions, while a change to MediaCollections.Exceptions can't break MediaCollections.
- Position
- Below the diagonal: MediaCollections.Exceptions uses a module listed above it, which is the healthy direction.
30→16 MediaCollections.Exceptions uses MediaCollections.Models✕
- Connections
- 1 pair of types, where a type in MediaCollections.Exceptions uses a type in MediaCollections.Models.
- The types involved
Spatie.MediaLibrary.MediaCollections.Exceptions.MediaCannotBeUpdated→Spatie.MediaLibrary.MediaCollections.Models.Media
- Direction
- MediaCollections.Exceptions uses MediaCollections.Models, so a change to MediaCollections.Models can break MediaCollections.Exceptions, while a change to MediaCollections.Exceptions can't break MediaCollections.Models.
- Position
- Below the diagonal: MediaCollections.Exceptions uses a module listed above it, which is the healthy direction.
30→22 MediaCollections.Exceptions uses Spatie.MediaLibrary✕
- Connections
- 1 pair of types, where a type in MediaCollections.Exceptions uses a type in Spatie.MediaLibrary.
- The types involved
Spatie.MediaLibrary.MediaCollections.Exceptions.FileUnacceptableForCollection→Spatie.MediaLibrary.HasMedia
- Direction
- MediaCollections.Exceptions uses Spatie.MediaLibrary, so a change to Spatie.MediaLibrary can break MediaCollections.Exceptions, while a change to MediaCollections.Exceptions can't break Spatie.MediaLibrary.
- Position
- Below the diagonal: MediaCollections.Exceptions 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 14 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | Medium |
Roadmap
Top priorities: 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 build/run (quick start) section to the root README — the first thing a newcomer needs; Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| 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. | +5.7 pts | Medium | Architecture documentation |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +3.6 pts | Medium | Documentation (README) |
| Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive. | +2.1 pts | Medium | Nullable reference types |
| Resolve the 2 Orphaned file finding(s) in Knowledge Freshness — start with DefaultFileRemover.php, Manipulations.php. | +0.9 pts | Low | Knowledge Freshness |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +0.7 pts | Low | Bus Factor |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +0.7 pts | Low | Bus Factor |
| Give every client an explicit bound: `new Client(['timeout' => 10, 'connect_timeout' => 3])` for Guzzle (whose default is to wait forever), `CURLOPT_TIMEOUT`/`CURLOPT_CONNECTTIMEOUT` before `curl_exec`, `timeout`/`max_duration` on Symfony HttpClient (or `framework.http_client.default_options`), and a stream-context `timeout` or `connection_timeout` for `file_get_contents`/`SoapClient`. In Drupal, use the `http_client` service, which carries core's site-wide timeout, rather than `new Client()`. Add retries with back-off (Guzzle `Middleware::retry`, Symfony `RetryableHttpClient`, Laravel `->retry()`) around dependencies that fail. | +1.4 pts | Medium | Outbound HTTP resilience |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +0.6 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| tests/TestSupport/TestImageGeneratorWithConfig.php | 6.6 | Mixed | Explicit Debt: TodoComment |
| src/Conversions/Conversion.php | 7.0 | Mixed | God Classes: TooManyMethods: Conversion |
| src/MediaCollections/FileAdder.php | 7.2 | Mixed | Cognitive Complexity: FileAdder.processMediaItem (cognitive 20) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/InteractsWithMedia.php | 7.4 | Mixed | God Classes: TooManyMethods: InteractsWithMedia |
| src/MediaCollections/Filesystem.php | 7.4 | Mixed | Code Duplication: Edited copy of a member (10 corresponding lines) |
| src/Conversions/Manipulations.php | 7.8 | Mixed | Cyclomatic Complexity: Manipulations.transformParameters (cyclomatic 30) |
| src/Support/FileRemover/DefaultFileRemover.php | 7.8 | Mixed | Code Duplication: Edited copy of a member (21 corresponding lines) |
| src/HasMedia.php | 8.0 | Near-clean | Coupling: Circular dependency |
| src/MediaCollections/Models/Media.php | 8.5 | Near-clean | God Classes: TooManyMethods: Media |
| src/Conversions/FileManipulator.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (19 corresponding lines) |
| src/MediaCollections/Commands/CleanCommand.php | 8.5 | Near-clean | Code Duplication: Duplicated block (19 lines × 2) |
| src/Conversions/ImageGenerators/Avif.php | 8.5 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
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 43 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
What we checked — 43 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, 49 of 60 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.php) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 12 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository declares a composer.json but commits no composer.lock this pass can read, so the set of packages it installs is not on disk: its composer.json states version CONSTRAINTS, and Composer's guidance is that a library leaves the lock uncommitted. Producing the graph needs Composer's solver, which this pass does not run, and grading whichever release happens to be newest today would be a verdict about a dependency graph nobody resolved. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is 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.
- 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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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/Support/UrlGenerator/BaseUrlGenerator.php` 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.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- 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 — 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 measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java 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.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust 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.
- 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.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, 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.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Java and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Java or Rust was found in this repository, 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.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust and Java source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust or Java was found in this repository, 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.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, 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.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, 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.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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").
- 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.
- 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.
- 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.
- 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.
- 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 Manipulations.transformParameters at 30.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with Manipulations.transformParameters (cyclomatic 30). — Refactoring it lifts Cyclomatic Complexity from 9.2 to about 10.0/10.
D2 · Cognitive Complexity
2 method(s) exceeded the cognitive complexity threshold of 15; the worst was Manipulations.transformParameters at 32.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with Manipulations.transformParameters (cognitive 32), FileAdder.processMediaItem (cognitive 20). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 9.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
4 god class(es) detected.
What to do
- Resolve the 4 TooManyMethods finding(s) in God Classes — start with Media.php, InteractsWithMedia.php, FileAdder.php. — One of this dimension's main actionable groups (4 warning-level).
D4 · Code Duplication
7 duplicated block group(s) detected. 3.6 % of the production lines (214 of 5,872) are in a reported copy. A further 5 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 1 Edited copy of a member (21 corresponding lines) finding(s) in Code Duplication — start with DefaultFileRemover.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copies of one member (3 members, 13+ corresponding lines) finding(s) in Code Duplication — start with InteractsWithMedia.php. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (19 corresponding lines) finding(s) in Code Duplication — start with FileManipulator.php. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
9 production modules (source-import), 1 dependency cycle(s), 0 unstable depended-on module(s). No manifest declares this repository's modules, so the modules are its top-level source directories and the edges the imports between them; 0 module(s) off the main sequence, with abstractness counted on 6 of the 9 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Circular dependency finding(s) in Coupling — start with HasMedia.php. — One of this dimension's main actionable groups (1 issue-level).
D6 · Cohesion (LCOM4)
1 of 16 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with Conversion.php. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/HasMedia.php. Counted over 22 of the 98 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
4 deducted task-comment markers across 5872 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 4 TodoComment finding(s) in Explicit Debt — start with TestImageGeneratorWithConfig.php (4). — One of this dimension's main actionable groups (4 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 56 document(s) read across 1 unit(s).
D27 · Navigability
33 % of calls cross a namespace and 1 % 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.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
14 finding(s): 0 critical, 13 high, 1 medium, 0 low. 11 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 1 file(s) — `src/Support/UrlGenerator/BaseUrlGenerator.php` (line 84) — 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 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 11 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 (11 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
2 of 22 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Support/FileRemover/DefaultFileRemover.php. Counted over 22 of the 98 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
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 12 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
AX10 · Code composition
AX3 · Project dependency cycles
- The projects src → src/Conversions → src (one cycle inside a mutually-dependent group of 6 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference. — src/HasMedia.php:9
What to do
- Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
DM1 · Aggregate boundaries
DM11 · Constructible invalid state
DM4 · Rich vs anemic model
DM5 · Encapsulated state
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
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
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `composer`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:3
What to do
- Dependabot is configured but does not watch `composer` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `Http::withUserAgent(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — src/Downloaders/HttpFacadeDownloader.php:14
What to do
- Give every client an explicit bound: `new Client(['timeout' => 10, 'connect_timeout' => 3])` for Guzzle (whose default is to wait forever), `CURLOPT_TIMEOUT`/`CURLOPT_CONNECTTIMEOUT` before `curl_exec`, `timeout`/`max_duration` on Symfony HttpClient (or `framework.http_client.default_options`), and a stream-context `timeout` or `connection_timeout` for `file_get_contents`/`SoapClient`. In Drupal, use the `http_client` service, which carries core's site-wide timeout, rather than `new Client()`. Add retries with back-off (Guzzle `Middleware::retry`, Symfony `RetryableHttpClient`, Laravel `->retry()`) around dependencies that fail.
P8 · Schema migrations
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X5 · Nullable reference types
- 0/1 of this repository's PHPStan/Psalm configuration(s) run at a level that checks null — PHPStan level 8 or above (`max` included), or Psalm `errorLevel` 3 or below (Psalm's default, with none stated, is 1). A PHPStan level written neither in the file nor in an include inside the repository is 0, PHPStan's own default. Below those levels the checker removes `null` from a union before any rule looks, so `$order->customer()->name()` on a `?Customer` passes, and the first null reaching it is an `Error: Call to a member function name() on null` in production.
What to do
- Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 66.6 | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 87.7 | Adequate — gated by D5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 58.0 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 68.4 | Adequate — gated by P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 66.8 | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100.0 | Exemplary | Strongest area. |
Unscored — 1 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.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 81 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (2 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — Not applicable: this repository's PHP imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route (no Laravel Route::…, no Symfony #[Route], no Filament panel, no WordPress REST route or AJAX action). Access control is therefore N/A here — a Composer library is authorized by the application that mounts it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- 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.
- D10 Test Quality — ~6535 lines of test source are present (.php) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — no .php test runner
- D12 Dependency Hygiene — Not scored — 12 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — Composer package licences not graded — this repository commits no composer.lock and this pass does not run Composer's solver
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
- D22 Internal API Consistency — 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 (MediaCollections), 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 — this repository's production source is .php, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (5537 LoC, 93 module-visible types across 30 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 1 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.
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
- 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
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM12 Ambient inputs in the domain — no domain-layer types detected — ambient-input check not applicable
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM6 Domain ↔ infrastructure boundary — no domain-layer types detected — domain↔infrastructure boundary check not applicable
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — 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'.
- P2 Observability — This repository's PHP source (1 module(s), 99 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — 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
- X12 Unreachable branch — 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
- X13 Undrained process stream — 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
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not 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
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's PHP was read and makes no request a caller can cancel (amphp's HttpClient or connect) — synchronous PHP offers its callers no cancellation to take
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — 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
- 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. Not a gap in the analyzer and not a finding about your code.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 15 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Project dependency cycle src/HasMedia.php:9
- REDACTED
- REDACTED
- Circular dependency src/HasMedia.php:9
Serious — 31 finding(s)
- TodoComment tests/TestSupport/TestImageGeneratorWithConfig.php:18
- TodoComment tests/TestSupport/TestImageGeneratorWithConfig.php:23
- TodoComment tests/TestSupport/TestImageGeneratorWithConfig.php:28
- TodoComment tests/TestSupport/TestImageGeneratorWithConfig.php:33
- TooManyMethods: Media src/MediaCollections/Models/Media.php:67
- TooManyMethods: InteractsWithMedia src/InteractsWithMedia.php:37
- TooManyMethods: FileAdder src/MediaCollections/FileAdder.php:30
- TooManyMethods: Conversion src/Conversions/Conversion.php:14
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Manipulations.transformParameters (cyclomatic 30) src/Conversions/Manipulations.php:97
- Manipulations.transformParameters (cognitive 32) src/Conversions/Manipulations.php:97
- FileAdder.processMediaItem (cognitive 20) src/MediaCollections/FileAdder.php:597
- REDACTED
- REDACTED
- Edited copy of a member (21 corresponding lines) src/Support/FileRemover/DefaultFileRemover.php:33
- Edited copies of one member (3 members, 13+ corresponding lines) src/InteractsWithMedia.php:322
- Edited copy of a member (19 corresponding lines) src/Conversions/FileManipulator.php:136
- Edited copy of a member (10 corresponding lines) src/MediaCollections/Filesystem.php:271
- Edited copy of a member (15 corresponding lines) src/MediaCollections/Filesystem.php:31
- Duplicated block (19 lines × 2) src/MediaCollections/Commands/CleanCommand.php:77
- Duplicated block (16 lines × 2) src/MediaCollections/FileAdder.php:334
- Duplicated block (11–13 lines × 3) src/Support/FileRemover/DefaultFileRemover.php:42
- Duplicated block (13 lines × 2) src/MediaCollections/Filesystem.php:33
- Duplicated block (9 lines × 2) src/InteractsWithMedia.php:322
- Duplicated block (8 lines × 2) src/MediaCollections/FileAdder.php:323
- Duplicated block (7 lines × 2) src/Conversions/ImageGenerators/Avif.php:12
- Low cohesion: Conversion (LCOM4 8) src/Conversions/Conversion.php:14
- Outbound HTTP without resilience src/Downloaders/HttpFacadeDownloader.php:14
Minor — 14 finding(s)
- Orphaned file src/Support/FileRemover/DefaultFileRemover.php:1
- Orphaned file src/Conversions/Manipulations.php:1
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- CI build step not evidenced
- Dependabot does not watch composer REDACTED:3
- Duplicated predicate src/MediaCollections/Commands/CleanCommand.php:80
- PHP static analysis does not check null everywhere
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-ebf6d430172944e8bca028506fad28be/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-ebf6d430172944e8bca028506fad28be/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=1770" --report-format json --report-path /tmp/watchdog-gitleaks-ebf6d430172944e8bca028506fad28be/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ebf6d430172944e8bca028506fad28be/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 database . | 14 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `src/Support/UrlGenerator/BaseUrlGenerator.php` — 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 | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet). | 0 | — |