Executive summary
symplify/monorepo-builder falls short of our standard for production because we found no logging, tracing or health checks in the code. It scores 57.6 out of 100 and is rated Adequate, and 25 of its 27 critical findings are security problems in the build pipeline.
Production Readiness, at 49.5, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 8.3 points. Adding a diagnostic log would lift Production Readiness itself, worth about 5.9 points. Raising Production Readiness to 70 would lift the score to about 63.2.
Twenty-five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk. 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 9,156 lines, about €12,000 to rebuild.
If Production Readiness rose from 49.5 to 70, the lowest score rated Strong, the score would rise from 57.6 to about 63.2.
Rebuild cost: about €12,000 · Estimate
| Cost to rebuild | €4,000 to €20,000, for 67 to 214 hours of work, under 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.8 at a score of 58. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 9,156 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 AutowireArrayParameter.TypeResolver | 2 MonorepoBuilder.Contract.Git | 3 PackageBuilder.Parameter | 4 SmartFileSystem | 5 SymplifyKernel.HttpKernel | 6 AutowireArrayParameter.Skipper | 7 EasyTesting | 8 MonorepoBuilder.ComposerJsonManipulator.ValueObject | 9 MonorepoBuilder.Release.Guard | 10 MonorepoBuilder.Utils | 11 SmartFileSystem.Finder | 12 AutowireArrayParameter.DependencyInjection.CompilerPass | 13 MonorepoBuilder.ComposerJsonManipulator.FileSystem | 14 MonorepoBuilder.Finder | 15 MonorepoBuilder.Git | 16 MonorepoBuilder.Merge.Contract | 17 MonorepoBuilder.Release.Version | 18 PackageBuilder.Console.Command | 19 EasyTesting.Command | 20 MonorepoBuilder.ComposerJsonManipulator | 21 MonorepoBuilder.Merge.ComposerKeyMerger | 22 MonorepoBuilder.Merge.PathResolver | 23 MonorepoBuilder.Release.Configuration | 24 MonorepoBuilder.FileSystem | 25 MonorepoBuilder.Merge.Configuration | 26 MonorepoBuilder | 27 MonorepoBuilder.Merge | 28 MonorepoBuilder.Package | 29 MonorepoBuilder.Propagate.Command | 30 MonorepoBuilder.Testing.ComposerJson | 31 MonorepoBuilder.Validator | 32 MonorepoBuilder.Command | 33 MonorepoBuilder.Merge.Application | 34 MonorepoBuilder.Merge.ComposerJsonDecorator | 35 MonorepoBuilder.Merge.Guard | 36 MonorepoBuilder.Release.Command | 37 MonorepoBuilder.Release.ReleaseWorker | 38 MonorepoBuilder.Testing | 39 MonorepoBuilder.Merge.Command | 40 MonorepoBuilder.Testing.Command |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 AutowireArrayParameter.TypeResolver | ||||||||||||||||||||||||||||||||||||||||
| 2 MonorepoBuilder.Contract.Git | ||||||||||||||||||||||||||||||||||||||||
| 3 PackageBuilder.Parameter | ||||||||||||||||||||||||||||||||||||||||
| 4 SmartFileSystem | ||||||||||||||||||||||||||||||||||||||||
| 5 SymplifyKernel.HttpKernel | ||||||||||||||||||||||||||||||||||||||||
| 6 AutowireArrayParameter.Skipper | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 EasyTesting | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 MonorepoBuilder.ComposerJsonManipulator.ValueObject | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 MonorepoBuilder.Release.Guard | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 MonorepoBuilder.Utils | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 SmartFileSystem.Finder | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 AutowireArrayParameter.DependencyInjection.CompilerPass | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 MonorepoBuilder.ComposerJsonManipulator.FileSystem | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 MonorepoBuilder.Finder | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 15 MonorepoBuilder.Git | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 MonorepoBuilder.Merge.Contract | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 17 MonorepoBuilder.Release.Version | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 PackageBuilder.Console.Command | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 EasyTesting.Command | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 MonorepoBuilder.ComposerJsonManipulator | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 MonorepoBuilder.Merge.ComposerKeyMerger | 11 | 11 | ||||||||||||||||||||||||||||||||||||||
| 22 MonorepoBuilder.Merge.PathResolver | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 23 MonorepoBuilder.Release.Configuration | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 MonorepoBuilder.FileSystem | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 25 MonorepoBuilder.Merge.Configuration | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 MonorepoBuilder | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 MonorepoBuilder.Merge | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 MonorepoBuilder.Package | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 MonorepoBuilder.Propagate.Command | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 MonorepoBuilder.Testing.ComposerJson | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 MonorepoBuilder.Validator | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 MonorepoBuilder.Command | 1 | 1 | 3 | 2 | 3 | 3 | ||||||||||||||||||||||||||||||||||
| 33 MonorepoBuilder.Merge.Application | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 MonorepoBuilder.Merge.ComposerJsonDecorator | 1 | 7 | 7 | 4 | 1 | |||||||||||||||||||||||||||||||||||
| 35 MonorepoBuilder.Merge.Guard | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 MonorepoBuilder.Release.Command | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 MonorepoBuilder.Release.ReleaseWorker | 2 | 1 | 4 | 1 | 4 | 3 | 2 | |||||||||||||||||||||||||||||||||
| 38 MonorepoBuilder.Testing | 2 | 1 | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 39 MonorepoBuilder.Merge.Command | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 40 MonorepoBuilder.Testing.Command | 1 | 1 | 2 |
6→1 AutowireArrayParameter.Skipper uses AutowireArrayParameter.TypeResolver✕
- Connections
- 1 pair of types, where a type in AutowireArrayParameter.Skipper uses a type in AutowireArrayParameter.TypeResolver.
- The types involved
Symplify.AutowireArrayParameter.Skipper.ParameterSkipper→Symplify.AutowireArrayParameter.TypeResolver.ParameterTypeResolver
- Direction
- AutowireArrayParameter.Skipper uses AutowireArrayParameter.TypeResolver, so a change to AutowireArrayParameter.TypeResolver can break AutowireArrayParameter.Skipper, while a change to AutowireArrayParameter.Skipper can't break AutowireArrayParameter.TypeResolver.
- Position
- Below the diagonal: AutowireArrayParameter.Skipper uses a module listed above it, which is the healthy direction.
7→4 EasyTesting uses SmartFileSystem✕
- Connections
- 2 pairs of types, where a type in EasyTesting uses a type in SmartFileSystem.
- The types involved
Symplify.EasyTesting.MissplacedSkipPrefixResolver→Symplify.SmartFileSystem.SmartFileInfoSymplify.EasyTesting.StaticFixtureSplitter→Symplify.SmartFileSystem.SmartFileInfo
- Direction
- EasyTesting uses SmartFileSystem, so a change to SmartFileSystem can break EasyTesting, while a change to EasyTesting can't break SmartFileSystem.
- Position
- Below the diagonal: EasyTesting uses a module listed above it, which is the healthy direction.
8→4 MonorepoBuilder.ComposerJsonManipulator.ValueObject uses SmartFileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.ComposerJsonManipulator.ValueObject uses a type in SmartFileSystem.
- The types involved
Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJson→Symplify.SmartFileSystem.SmartFileInfo
- Direction
- MonorepoBuilder.ComposerJsonManipulator.ValueObject uses SmartFileSystem, so a change to SmartFileSystem can break MonorepoBuilder.ComposerJsonManipulator.ValueObject, while a change to MonorepoBuilder.ComposerJsonManipulator.ValueObject can't break SmartFileSystem.
- Position
- Below the diagonal: MonorepoBuilder.ComposerJsonManipulator.ValueObject uses a module listed above it, which is the healthy direction.
9→2 MonorepoBuilder.Release.Guard uses MonorepoBuilder.Contract.Git✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Release.Guard uses a type in MonorepoBuilder.Contract.Git.
- The types involved
Symplify.MonorepoBuilder.Release.Guard.ReleaseGuard→Symplify.MonorepoBuilder.Contract.Git.TagResolverInterface
- Direction
- MonorepoBuilder.Release.Guard uses MonorepoBuilder.Contract.Git, so a change to MonorepoBuilder.Contract.Git can break MonorepoBuilder.Release.Guard, while a change to MonorepoBuilder.Release.Guard can't break MonorepoBuilder.Contract.Git.
- Position
- Below the diagonal: MonorepoBuilder.Release.Guard uses a module listed above it, which is the healthy direction.
9→3 MonorepoBuilder.Release.Guard uses PackageBuilder.Parameter✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Release.Guard uses a type in PackageBuilder.Parameter.
- The types involved
Symplify.MonorepoBuilder.Release.Guard.ReleaseGuard→Symplify.PackageBuilder.Parameter.ParameterProvider
- Direction
- MonorepoBuilder.Release.Guard uses PackageBuilder.Parameter, so a change to PackageBuilder.Parameter can break MonorepoBuilder.Release.Guard, while a change to MonorepoBuilder.Release.Guard can't break PackageBuilder.Parameter.
- Position
- Below the diagonal: MonorepoBuilder.Release.Guard uses a module listed above it, which is the healthy direction.
10→3 MonorepoBuilder.Utils uses PackageBuilder.Parameter✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Utils uses a type in PackageBuilder.Parameter.
- The types involved
Symplify.MonorepoBuilder.Utils.VersionUtils→Symplify.PackageBuilder.Parameter.ParameterProvider
- Direction
- MonorepoBuilder.Utils uses PackageBuilder.Parameter, so a change to PackageBuilder.Parameter can break MonorepoBuilder.Utils, while a change to MonorepoBuilder.Utils can't break PackageBuilder.Parameter.
- Position
- Below the diagonal: MonorepoBuilder.Utils uses a module listed above it, which is the healthy direction.
11→4 SmartFileSystem.Finder uses SmartFileSystem✕
- Connections
- 1 pair of types, where a type in SmartFileSystem.Finder uses a type in SmartFileSystem.
- The types involved
Symplify.SmartFileSystem.Finder.SmartFinder→Symplify.SmartFileSystem.FileSystemFilter
- Direction
- SmartFileSystem.Finder uses SmartFileSystem, so a change to SmartFileSystem can break SmartFileSystem.Finder, while a change to SmartFileSystem.Finder can't break SmartFileSystem.
- Position
- Below the diagonal: SmartFileSystem.Finder uses a module listed above it, which is the healthy direction.
12→1 AutowireArrayParameter.DependencyInjection.CompilerPass uses AutowireArrayParameter.TypeResolver✕
- Connections
- 1 pair of types, where a type in AutowireArrayParameter.DependencyInjection.CompilerPass uses a type in AutowireArrayParameter.TypeResolver.
- The types involved
Symplify.AutowireArrayParameter.DependencyInjection.CompilerPass.AutowireArrayParameterCompilerPass→Symplify.AutowireArrayParameter.TypeResolver.ParameterTypeResolver
- Direction
- AutowireArrayParameter.DependencyInjection.CompilerPass uses AutowireArrayParameter.TypeResolver, so a change to AutowireArrayParameter.TypeResolver can break AutowireArrayParameter.DependencyInjection.CompilerPass, while a change to AutowireArrayParameter.DependencyInjection.CompilerPass can't break AutowireArrayParameter.TypeResolver.
- Position
- Below the diagonal: AutowireArrayParameter.DependencyInjection.CompilerPass uses a module listed above it, which is the healthy direction.
12→6 AutowireArrayParameter.DependencyInjection.CompilerPass uses AutowireArrayParameter.Skipper✕
- Connections
- 1 pair of types, where a type in AutowireArrayParameter.DependencyInjection.CompilerPass uses a type in AutowireArrayParameter.Skipper.
- The types involved
Symplify.AutowireArrayParameter.DependencyInjection.CompilerPass.AutowireArrayParameterCompilerPass→Symplify.AutowireArrayParameter.Skipper.ParameterSkipper
- Direction
- AutowireArrayParameter.DependencyInjection.CompilerPass uses AutowireArrayParameter.Skipper, so a change to AutowireArrayParameter.Skipper can break AutowireArrayParameter.DependencyInjection.CompilerPass, while a change to AutowireArrayParameter.DependencyInjection.CompilerPass can't break AutowireArrayParameter.Skipper.
- Position
- Below the diagonal: AutowireArrayParameter.DependencyInjection.CompilerPass uses a module listed above it, which is the healthy direction.
13→4 MonorepoBuilder.ComposerJsonManipulator.FileSystem uses SmartFileSystem✕
- Connections
- 2 pairs of types, where a type in MonorepoBuilder.ComposerJsonManipulator.FileSystem uses a type in SmartFileSystem.
- The types involved
Symplify.MonorepoBuilder.ComposerJsonManipulator.FileSystem.JsonFileManager→Symplify.SmartFileSystem.SmartFileInfoSymplify.MonorepoBuilder.ComposerJsonManipulator.FileSystem.JsonFileManager→Symplify.SmartFileSystem.SmartFileSystem
- Direction
- MonorepoBuilder.ComposerJsonManipulator.FileSystem uses SmartFileSystem, so a change to SmartFileSystem can break MonorepoBuilder.ComposerJsonManipulator.FileSystem, while a change to MonorepoBuilder.ComposerJsonManipulator.FileSystem can't break SmartFileSystem.
- Position
- Below the diagonal: MonorepoBuilder.ComposerJsonManipulator.FileSystem uses a module listed above it, which is the healthy direction.
13→8 MonorepoBuilder.ComposerJsonManipulator.FileSystem uses MonorepoBuilder.ComposerJsonManipulator.ValueObject✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.ComposerJsonManipulator.FileSystem uses a type in MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- The types involved
Symplify.MonorepoBuilder.ComposerJsonManipulator.FileSystem.JsonFileManager→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJson
- Direction
- MonorepoBuilder.ComposerJsonManipulator.FileSystem uses MonorepoBuilder.ComposerJsonManipulator.ValueObject, so a change to MonorepoBuilder.ComposerJsonManipulator.ValueObject can break MonorepoBuilder.ComposerJsonManipulator.FileSystem, while a change to MonorepoBuilder.ComposerJsonManipulator.FileSystem can't break MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- Position
- Below the diagonal: MonorepoBuilder.ComposerJsonManipulator.FileSystem uses a module listed above it, which is the healthy direction.
14→3 MonorepoBuilder.Finder uses PackageBuilder.Parameter✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Finder uses a type in PackageBuilder.Parameter.
- The types involved
Symplify.MonorepoBuilder.Finder.PackageComposerFinder→Symplify.PackageBuilder.Parameter.ParameterProvider
- Direction
- MonorepoBuilder.Finder uses PackageBuilder.Parameter, so a change to PackageBuilder.Parameter can break MonorepoBuilder.Finder, while a change to MonorepoBuilder.Finder can't break PackageBuilder.Parameter.
- Position
- Below the diagonal: MonorepoBuilder.Finder uses a module listed above it, which is the healthy direction.
14→4 MonorepoBuilder.Finder uses SmartFileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Finder uses a type in SmartFileSystem.
- The types involved
Symplify.MonorepoBuilder.Finder.PackageComposerFinder→Symplify.SmartFileSystem.SmartFileInfo
- Direction
- MonorepoBuilder.Finder uses SmartFileSystem, so a change to SmartFileSystem can break MonorepoBuilder.Finder, while a change to MonorepoBuilder.Finder can't break SmartFileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Finder uses a module listed above it, which is the healthy direction.
14→11 MonorepoBuilder.Finder uses SmartFileSystem.Finder✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Finder uses a type in SmartFileSystem.Finder.
- The types involved
Symplify.MonorepoBuilder.Finder.PackageComposerFinder→Symplify.SmartFileSystem.Finder.FinderSanitizer
- Direction
- MonorepoBuilder.Finder uses SmartFileSystem.Finder, so a change to SmartFileSystem.Finder can break MonorepoBuilder.Finder, while a change to MonorepoBuilder.Finder can't break SmartFileSystem.Finder.
- Position
- Below the diagonal: MonorepoBuilder.Finder uses a module listed above it, which is the healthy direction.
15→2 MonorepoBuilder.Git uses MonorepoBuilder.Contract.Git✕
- Connections
- 2 pairs of types, where a type in MonorepoBuilder.Git uses a type in MonorepoBuilder.Contract.Git.
- The types involved
Symplify.MonorepoBuilder.Git.BranchAwareTagResolver→Symplify.MonorepoBuilder.Contract.Git.TagResolverInterfaceSymplify.MonorepoBuilder.Git.MostRecentTagResolver→Symplify.MonorepoBuilder.Contract.Git.TagResolverInterface
- Direction
- MonorepoBuilder.Git uses MonorepoBuilder.Contract.Git, so a change to MonorepoBuilder.Contract.Git can break MonorepoBuilder.Git, while a change to MonorepoBuilder.Git can't break MonorepoBuilder.Contract.Git.
- Position
- Below the diagonal: MonorepoBuilder.Git uses a module listed above it, which is the healthy direction.
15→10 MonorepoBuilder.Git uses MonorepoBuilder.Utils✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Git uses a type in MonorepoBuilder.Utils.
- The types involved
Symplify.MonorepoBuilder.Git.ExpectedAliasResolver→Symplify.MonorepoBuilder.Utils.VersionUtils
- Direction
- MonorepoBuilder.Git uses MonorepoBuilder.Utils, so a change to MonorepoBuilder.Utils can break MonorepoBuilder.Git, while a change to MonorepoBuilder.Git can't break MonorepoBuilder.Utils.
- Position
- Below the diagonal: MonorepoBuilder.Git uses a module listed above it, which is the healthy direction.
16→4 MonorepoBuilder.Merge.Contract uses SmartFileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge.Contract uses a type in SmartFileSystem.
- The types involved
Symplify.MonorepoBuilder.Merge.Contract.ComposerPathNormalizerInterface→Symplify.SmartFileSystem.SmartFileInfo
- Direction
- MonorepoBuilder.Merge.Contract uses SmartFileSystem, so a change to SmartFileSystem can break MonorepoBuilder.Merge.Contract, while a change to MonorepoBuilder.Merge.Contract can't break SmartFileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Merge.Contract uses a module listed above it, which is the healthy direction.
16→8 MonorepoBuilder.Merge.Contract uses MonorepoBuilder.ComposerJsonManipulator.ValueObject✕
- Connections
- 3 pairs of types, where a type in MonorepoBuilder.Merge.Contract uses a type in MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- The types involved
Symplify.MonorepoBuilder.Merge.Contract.ComposerJsonDecoratorInterface→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJsonSymplify.MonorepoBuilder.Merge.Contract.ComposerKeyMergerInterface→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJsonSymplify.MonorepoBuilder.Merge.Contract.ComposerPathNormalizerInterface→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJson
- Direction
- MonorepoBuilder.Merge.Contract uses MonorepoBuilder.ComposerJsonManipulator.ValueObject, so a change to MonorepoBuilder.ComposerJsonManipulator.ValueObject can break MonorepoBuilder.Merge.Contract, while a change to MonorepoBuilder.Merge.Contract can't break MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- Position
- Below the diagonal: MonorepoBuilder.Merge.Contract uses a module listed above it, which is the healthy direction.
17→2 MonorepoBuilder.Release.Version uses MonorepoBuilder.Contract.Git✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Release.Version uses a type in MonorepoBuilder.Contract.Git.
- The types involved
Symplify.MonorepoBuilder.Release.Version.VersionFactory→Symplify.MonorepoBuilder.Contract.Git.TagResolverInterface
- Direction
- MonorepoBuilder.Release.Version uses MonorepoBuilder.Contract.Git, so a change to MonorepoBuilder.Contract.Git can break MonorepoBuilder.Release.Version, while a change to MonorepoBuilder.Release.Version can't break MonorepoBuilder.Contract.Git.
- Position
- Below the diagonal: MonorepoBuilder.Release.Version uses a module listed above it, which is the healthy direction.
17→9 MonorepoBuilder.Release.Version uses MonorepoBuilder.Release.Guard✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Release.Version uses a type in MonorepoBuilder.Release.Guard.
- The types involved
Symplify.MonorepoBuilder.Release.Version.VersionFactory→Symplify.MonorepoBuilder.Release.Guard.ReleaseGuard
- Direction
- MonorepoBuilder.Release.Version uses MonorepoBuilder.Release.Guard, so a change to MonorepoBuilder.Release.Guard can break MonorepoBuilder.Release.Version, while a change to MonorepoBuilder.Release.Version can't break MonorepoBuilder.Release.Guard.
- Position
- Below the diagonal: MonorepoBuilder.Release.Version uses a module listed above it, which is the healthy direction.
18→4 PackageBuilder.Console.Command uses SmartFileSystem✕
- Connections
- 2 pairs of types, where a type in PackageBuilder.Console.Command uses a type in SmartFileSystem.
- The types involved
Symplify.PackageBuilder.Console.Command.AbstractSymplifyCommand→Symplify.SmartFileSystem.FileSystemGuardSymplify.PackageBuilder.Console.Command.AbstractSymplifyCommand→Symplify.SmartFileSystem.SmartFileSystem
- Direction
- PackageBuilder.Console.Command uses SmartFileSystem, so a change to SmartFileSystem can break PackageBuilder.Console.Command, while a change to PackageBuilder.Console.Command can't break SmartFileSystem.
- Position
- Below the diagonal: PackageBuilder.Console.Command uses a module listed above it, which is the healthy direction.
18→11 PackageBuilder.Console.Command uses SmartFileSystem.Finder✕
- Connections
- 1 pair of types, where a type in PackageBuilder.Console.Command uses a type in SmartFileSystem.Finder.
- The types involved
Symplify.PackageBuilder.Console.Command.AbstractSymplifyCommand→Symplify.SmartFileSystem.Finder.SmartFinder
- Direction
- PackageBuilder.Console.Command uses SmartFileSystem.Finder, so a change to SmartFileSystem.Finder can break PackageBuilder.Console.Command, while a change to PackageBuilder.Console.Command can't break SmartFileSystem.Finder.
- Position
- Below the diagonal: PackageBuilder.Console.Command uses a module listed above it, which is the healthy direction.
19→7 EasyTesting.Command uses EasyTesting✕
- Connections
- 1 pair of types, where a type in EasyTesting.Command uses a type in EasyTesting.
- The types involved
Symplify.EasyTesting.Command.ValidateFixtureSkipNamingCommand→Symplify.EasyTesting.MissplacedSkipPrefixResolver
- Direction
- EasyTesting.Command uses EasyTesting, so a change to EasyTesting can break EasyTesting.Command, while a change to EasyTesting.Command can't break EasyTesting.
- Position
- Below the diagonal: EasyTesting.Command uses a module listed above it, which is the healthy direction.
19→18 EasyTesting.Command uses PackageBuilder.Console.Command✕
- Connections
- 1 pair of types, where a type in EasyTesting.Command uses a type in PackageBuilder.Console.Command.
- The types involved
Symplify.EasyTesting.Command.ValidateFixtureSkipNamingCommand→Symplify.PackageBuilder.Console.Command.AbstractSymplifyCommand
- Direction
- EasyTesting.Command uses PackageBuilder.Console.Command, so a change to PackageBuilder.Console.Command can break EasyTesting.Command, while a change to EasyTesting.Command can't break PackageBuilder.Console.Command.
- Position
- Below the diagonal: EasyTesting.Command uses a module listed above it, which is the healthy direction.
20→4 MonorepoBuilder.ComposerJsonManipulator uses SmartFileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.ComposerJsonManipulator uses a type in SmartFileSystem.
- The types involved
Symplify.MonorepoBuilder.ComposerJsonManipulator.ComposerJsonFactory→Symplify.SmartFileSystem.SmartFileInfo
- Direction
- MonorepoBuilder.ComposerJsonManipulator uses SmartFileSystem, so a change to SmartFileSystem can break MonorepoBuilder.ComposerJsonManipulator, while a change to MonorepoBuilder.ComposerJsonManipulator can't break SmartFileSystem.
- Position
- Below the diagonal: MonorepoBuilder.ComposerJsonManipulator uses a module listed above it, which is the healthy direction.
20→8 MonorepoBuilder.ComposerJsonManipulator uses MonorepoBuilder.ComposerJsonManipulator.ValueObject✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.ComposerJsonManipulator uses a type in MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- The types involved
Symplify.MonorepoBuilder.ComposerJsonManipulator.ComposerJsonFactory→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJson
- Direction
- MonorepoBuilder.ComposerJsonManipulator uses MonorepoBuilder.ComposerJsonManipulator.ValueObject, so a change to MonorepoBuilder.ComposerJsonManipulator.ValueObject can break MonorepoBuilder.ComposerJsonManipulator, while a change to MonorepoBuilder.ComposerJsonManipulator can't break MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- Position
- Below the diagonal: MonorepoBuilder.ComposerJsonManipulator uses a module listed above it, which is the healthy direction.
20→13 MonorepoBuilder.ComposerJsonManipulator uses MonorepoBuilder.ComposerJsonManipulator.FileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.ComposerJsonManipulator uses a type in MonorepoBuilder.ComposerJsonManipulator.FileSystem.
- The types involved
Symplify.MonorepoBuilder.ComposerJsonManipulator.ComposerJsonFactory→Symplify.MonorepoBuilder.ComposerJsonManipulator.FileSystem.JsonFileManager
- Direction
- MonorepoBuilder.ComposerJsonManipulator uses MonorepoBuilder.ComposerJsonManipulator.FileSystem, so a change to MonorepoBuilder.ComposerJsonManipulator.FileSystem can break MonorepoBuilder.ComposerJsonManipulator, while a change to MonorepoBuilder.ComposerJsonManipulator can't break MonorepoBuilder.ComposerJsonManipulator.FileSystem.
- Position
- Below the diagonal: MonorepoBuilder.ComposerJsonManipulator uses a module listed above it, which is the healthy direction.
21→8 MonorepoBuilder.Merge.ComposerKeyMerger uses MonorepoBuilder.ComposerJsonManipulator.ValueObject✕
- Connections
- 11 pairs of types, where a type in MonorepoBuilder.Merge.ComposerKeyMerger uses a type in MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- The types involved
Symplify.MonorepoBuilder.Merge.ComposerKeyMerger.AuthorComposerKeyMerger→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJsonSymplify.MonorepoBuilder.Merge.ComposerKeyMerger.AutoloadComposerKeyMerger→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJsonSymplify.MonorepoBuilder.Merge.ComposerKeyMerger.AutoloadDevComposerKeyMerger→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJsonSymplify.MonorepoBuilder.Merge.ComposerKeyMerger.ExtraComposerKeyMerger→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJsonSymplify.MonorepoBuilder.Merge.ComposerKeyMerger.MinimalStabilityKeyMerger→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJsonSymplify.MonorepoBuilder.Merge.ComposerKeyMerger.PreferStableKeyMerger→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJsonSymplify.MonorepoBuilder.Merge.ComposerKeyMerger.ProvideComposerKeyMerger→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJsonSymplify.MonorepoBuilder.Merge.ComposerKeyMerger.ReplaceComposerKeyMerger→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJsonSymplify.MonorepoBuilder.Merge.ComposerKeyMerger.RepositoriesComposerKeyMerger→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJsonSymplify.MonorepoBuilder.Merge.ComposerKeyMerger.RequireComposerKeyMerger→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJsonSymplify.MonorepoBuilder.Merge.ComposerKeyMerger.RequireDevComposerKeyMerger→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJson
- Direction
- MonorepoBuilder.Merge.ComposerKeyMerger uses MonorepoBuilder.ComposerJsonManipulator.ValueObject, so a change to MonorepoBuilder.ComposerJsonManipulator.ValueObject can break MonorepoBuilder.Merge.ComposerKeyMerger, while a change to MonorepoBuilder.Merge.ComposerKeyMerger can't break MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- Position
- Below the diagonal: MonorepoBuilder.Merge.ComposerKeyMerger uses a module listed above it, which is the healthy direction.
21→16 MonorepoBuilder.Merge.ComposerKeyMerger uses MonorepoBuilder.Merge.Contract✕
- Connections
- 11 pairs of types, where a type in MonorepoBuilder.Merge.ComposerKeyMerger uses a type in MonorepoBuilder.Merge.Contract.
- The types involved
Symplify.MonorepoBuilder.Merge.ComposerKeyMerger.AuthorComposerKeyMerger→Symplify.MonorepoBuilder.Merge.Contract.ComposerKeyMergerInterfaceSymplify.MonorepoBuilder.Merge.ComposerKeyMerger.AutoloadComposerKeyMerger→Symplify.MonorepoBuilder.Merge.Contract.ComposerKeyMergerInterfaceSymplify.MonorepoBuilder.Merge.ComposerKeyMerger.AutoloadDevComposerKeyMerger→Symplify.MonorepoBuilder.Merge.Contract.ComposerKeyMergerInterfaceSymplify.MonorepoBuilder.Merge.ComposerKeyMerger.ExtraComposerKeyMerger→Symplify.MonorepoBuilder.Merge.Contract.ComposerKeyMergerInterfaceSymplify.MonorepoBuilder.Merge.ComposerKeyMerger.MinimalStabilityKeyMerger→Symplify.MonorepoBuilder.Merge.Contract.ComposerKeyMergerInterfaceSymplify.MonorepoBuilder.Merge.ComposerKeyMerger.PreferStableKeyMerger→Symplify.MonorepoBuilder.Merge.Contract.ComposerKeyMergerInterfaceSymplify.MonorepoBuilder.Merge.ComposerKeyMerger.ProvideComposerKeyMerger→Symplify.MonorepoBuilder.Merge.Contract.ComposerKeyMergerInterfaceSymplify.MonorepoBuilder.Merge.ComposerKeyMerger.ReplaceComposerKeyMerger→Symplify.MonorepoBuilder.Merge.Contract.ComposerKeyMergerInterfaceSymplify.MonorepoBuilder.Merge.ComposerKeyMerger.RepositoriesComposerKeyMerger→Symplify.MonorepoBuilder.Merge.Contract.ComposerKeyMergerInterfaceSymplify.MonorepoBuilder.Merge.ComposerKeyMerger.RequireComposerKeyMerger→Symplify.MonorepoBuilder.Merge.Contract.ComposerKeyMergerInterfaceSymplify.MonorepoBuilder.Merge.ComposerKeyMerger.RequireDevComposerKeyMerger→Symplify.MonorepoBuilder.Merge.Contract.ComposerKeyMergerInterface
- Direction
- MonorepoBuilder.Merge.ComposerKeyMerger uses MonorepoBuilder.Merge.Contract, so a change to MonorepoBuilder.Merge.Contract can break MonorepoBuilder.Merge.ComposerKeyMerger, while a change to MonorepoBuilder.Merge.ComposerKeyMerger can't break MonorepoBuilder.Merge.Contract.
- Position
- Below the diagonal: MonorepoBuilder.Merge.ComposerKeyMerger uses a module listed above it, which is the healthy direction.
22→4 MonorepoBuilder.Merge.PathResolver uses SmartFileSystem✕
- Connections
- 2 pairs of types, where a type in MonorepoBuilder.Merge.PathResolver uses a type in SmartFileSystem.
- The types involved
Symplify.MonorepoBuilder.Merge.PathResolver.AutoloadPathNormalizer→Symplify.SmartFileSystem.SmartFileInfoSymplify.MonorepoBuilder.Merge.PathResolver.ComposerPatchesPathNormalizer→Symplify.SmartFileSystem.SmartFileInfo
- Direction
- MonorepoBuilder.Merge.PathResolver uses SmartFileSystem, so a change to SmartFileSystem can break MonorepoBuilder.Merge.PathResolver, while a change to MonorepoBuilder.Merge.PathResolver can't break SmartFileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Merge.PathResolver uses a module listed above it, which is the healthy direction.
22→8 MonorepoBuilder.Merge.PathResolver uses MonorepoBuilder.ComposerJsonManipulator.ValueObject✕
- Connections
- 2 pairs of types, where a type in MonorepoBuilder.Merge.PathResolver uses a type in MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- The types involved
Symplify.MonorepoBuilder.Merge.PathResolver.AutoloadPathNormalizer→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJsonSymplify.MonorepoBuilder.Merge.PathResolver.ComposerPatchesPathNormalizer→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJson
- Direction
- MonorepoBuilder.Merge.PathResolver uses MonorepoBuilder.ComposerJsonManipulator.ValueObject, so a change to MonorepoBuilder.ComposerJsonManipulator.ValueObject can break MonorepoBuilder.Merge.PathResolver, while a change to MonorepoBuilder.Merge.PathResolver can't break MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- Position
- Below the diagonal: MonorepoBuilder.Merge.PathResolver uses a module listed above it, which is the healthy direction.
22→16 MonorepoBuilder.Merge.PathResolver uses MonorepoBuilder.Merge.Contract✕
- Connections
- 2 pairs of types, where a type in MonorepoBuilder.Merge.PathResolver uses a type in MonorepoBuilder.Merge.Contract.
- The types involved
Symplify.MonorepoBuilder.Merge.PathResolver.AutoloadPathNormalizer→Symplify.MonorepoBuilder.Merge.Contract.ComposerPathNormalizerInterfaceSymplify.MonorepoBuilder.Merge.PathResolver.ComposerPatchesPathNormalizer→Symplify.MonorepoBuilder.Merge.Contract.ComposerPathNormalizerInterface
- Direction
- MonorepoBuilder.Merge.PathResolver uses MonorepoBuilder.Merge.Contract, so a change to MonorepoBuilder.Merge.Contract can break MonorepoBuilder.Merge.PathResolver, while a change to MonorepoBuilder.Merge.PathResolver can't break MonorepoBuilder.Merge.Contract.
- Position
- Below the diagonal: MonorepoBuilder.Merge.PathResolver uses a module listed above it, which is the healthy direction.
23→9 MonorepoBuilder.Release.Configuration uses MonorepoBuilder.Release.Guard✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Release.Configuration uses a type in MonorepoBuilder.Release.Guard.
- The types involved
Symplify.MonorepoBuilder.Release.Configuration.StageResolver→Symplify.MonorepoBuilder.Release.Guard.ReleaseGuard
- Direction
- MonorepoBuilder.Release.Configuration uses MonorepoBuilder.Release.Guard, so a change to MonorepoBuilder.Release.Guard can break MonorepoBuilder.Release.Configuration, while a change to MonorepoBuilder.Release.Configuration can't break MonorepoBuilder.Release.Guard.
- Position
- Below the diagonal: MonorepoBuilder.Release.Configuration uses a module listed above it, which is the healthy direction.
23→17 MonorepoBuilder.Release.Configuration uses MonorepoBuilder.Release.Version✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Release.Configuration uses a type in MonorepoBuilder.Release.Version.
- The types involved
Symplify.MonorepoBuilder.Release.Configuration.VersionResolver→Symplify.MonorepoBuilder.Release.Version.VersionFactory
- Direction
- MonorepoBuilder.Release.Configuration uses MonorepoBuilder.Release.Version, so a change to MonorepoBuilder.Release.Version can break MonorepoBuilder.Release.Configuration, while a change to MonorepoBuilder.Release.Configuration can't break MonorepoBuilder.Release.Version.
- Position
- Below the diagonal: MonorepoBuilder.Release.Configuration uses a module listed above it, which is the healthy direction.
24→4 MonorepoBuilder.FileSystem uses SmartFileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.FileSystem uses a type in SmartFileSystem.
- The types involved
Symplify.MonorepoBuilder.FileSystem.ComposerJsonProvider→Symplify.SmartFileSystem.SmartFileInfo
- Direction
- MonorepoBuilder.FileSystem uses SmartFileSystem, so a change to SmartFileSystem can break MonorepoBuilder.FileSystem, while a change to MonorepoBuilder.FileSystem can't break SmartFileSystem.
- Position
- Below the diagonal: MonorepoBuilder.FileSystem uses a module listed above it, which is the healthy direction.
24→8 MonorepoBuilder.FileSystem uses MonorepoBuilder.ComposerJsonManipulator.ValueObject✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.FileSystem uses a type in MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- The types involved
Symplify.MonorepoBuilder.FileSystem.ComposerJsonProvider→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJson
- Direction
- MonorepoBuilder.FileSystem uses MonorepoBuilder.ComposerJsonManipulator.ValueObject, so a change to MonorepoBuilder.ComposerJsonManipulator.ValueObject can break MonorepoBuilder.FileSystem, while a change to MonorepoBuilder.FileSystem can't break MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- Position
- Below the diagonal: MonorepoBuilder.FileSystem uses a module listed above it, which is the healthy direction.
24→13 MonorepoBuilder.FileSystem uses MonorepoBuilder.ComposerJsonManipulator.FileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.FileSystem uses a type in MonorepoBuilder.ComposerJsonManipulator.FileSystem.
- The types involved
Symplify.MonorepoBuilder.FileSystem.ComposerJsonProvider→Symplify.MonorepoBuilder.ComposerJsonManipulator.FileSystem.JsonFileManager
- Direction
- MonorepoBuilder.FileSystem uses MonorepoBuilder.ComposerJsonManipulator.FileSystem, so a change to MonorepoBuilder.ComposerJsonManipulator.FileSystem can break MonorepoBuilder.FileSystem, while a change to MonorepoBuilder.FileSystem can't break MonorepoBuilder.ComposerJsonManipulator.FileSystem.
- Position
- Below the diagonal: MonorepoBuilder.FileSystem uses a module listed above it, which is the healthy direction.
24→14 MonorepoBuilder.FileSystem uses MonorepoBuilder.Finder✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.FileSystem uses a type in MonorepoBuilder.Finder.
- The types involved
Symplify.MonorepoBuilder.FileSystem.ComposerJsonProvider→Symplify.MonorepoBuilder.Finder.PackageComposerFinder
- Direction
- MonorepoBuilder.FileSystem uses MonorepoBuilder.Finder, so a change to MonorepoBuilder.Finder can break MonorepoBuilder.FileSystem, while a change to MonorepoBuilder.FileSystem can't break MonorepoBuilder.Finder.
- Position
- Below the diagonal: MonorepoBuilder.FileSystem uses a module listed above it, which is the healthy direction.
24→20 MonorepoBuilder.FileSystem uses MonorepoBuilder.ComposerJsonManipulator✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.FileSystem uses a type in MonorepoBuilder.ComposerJsonManipulator.
- The types involved
Symplify.MonorepoBuilder.FileSystem.ComposerJsonProvider→Symplify.MonorepoBuilder.ComposerJsonManipulator.ComposerJsonFactory
- Direction
- MonorepoBuilder.FileSystem uses MonorepoBuilder.ComposerJsonManipulator, so a change to MonorepoBuilder.ComposerJsonManipulator can break MonorepoBuilder.FileSystem, while a change to MonorepoBuilder.FileSystem can't break MonorepoBuilder.ComposerJsonManipulator.
- Position
- Below the diagonal: MonorepoBuilder.FileSystem uses a module listed above it, which is the healthy direction.
25→3 MonorepoBuilder.Merge.Configuration uses PackageBuilder.Parameter✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge.Configuration uses a type in PackageBuilder.Parameter.
- The types involved
Symplify.MonorepoBuilder.Merge.Configuration.ModifyingComposerJsonProvider→Symplify.PackageBuilder.Parameter.ParameterProvider
- Direction
- MonorepoBuilder.Merge.Configuration uses PackageBuilder.Parameter, so a change to PackageBuilder.Parameter can break MonorepoBuilder.Merge.Configuration, while a change to MonorepoBuilder.Merge.Configuration can't break PackageBuilder.Parameter.
- Position
- Below the diagonal: MonorepoBuilder.Merge.Configuration uses a module listed above it, which is the healthy direction.
25→8 MonorepoBuilder.Merge.Configuration uses MonorepoBuilder.ComposerJsonManipulator.ValueObject✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge.Configuration uses a type in MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- The types involved
Symplify.MonorepoBuilder.Merge.Configuration.ModifyingComposerJsonProvider→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJson
- Direction
- MonorepoBuilder.Merge.Configuration uses MonorepoBuilder.ComposerJsonManipulator.ValueObject, so a change to MonorepoBuilder.ComposerJsonManipulator.ValueObject can break MonorepoBuilder.Merge.Configuration, while a change to MonorepoBuilder.Merge.Configuration can't break MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- Position
- Below the diagonal: MonorepoBuilder.Merge.Configuration uses a module listed above it, which is the healthy direction.
25→20 MonorepoBuilder.Merge.Configuration uses MonorepoBuilder.ComposerJsonManipulator✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge.Configuration uses a type in MonorepoBuilder.ComposerJsonManipulator.
- The types involved
Symplify.MonorepoBuilder.Merge.Configuration.ModifyingComposerJsonProvider→Symplify.MonorepoBuilder.ComposerJsonManipulator.ComposerJsonFactory
- Direction
- MonorepoBuilder.Merge.Configuration uses MonorepoBuilder.ComposerJsonManipulator, so a change to MonorepoBuilder.ComposerJsonManipulator can break MonorepoBuilder.Merge.Configuration, while a change to MonorepoBuilder.Merge.Configuration can't break MonorepoBuilder.ComposerJsonManipulator.
- Position
- Below the diagonal: MonorepoBuilder.Merge.Configuration uses a module listed above it, which is the healthy direction.
26→3 MonorepoBuilder uses PackageBuilder.Parameter✕
- Connections
- 2 pairs of types, where a type in MonorepoBuilder uses a type in PackageBuilder.Parameter.
- The types involved
Symplify.MonorepoBuilder.DevMasterAliasUpdater→Symplify.PackageBuilder.Parameter.ParameterProviderSymplify.MonorepoBuilder.VersionValidator→Symplify.PackageBuilder.Parameter.ParameterProvider
- Direction
- MonorepoBuilder uses PackageBuilder.Parameter, so a change to PackageBuilder.Parameter can break MonorepoBuilder, while a change to MonorepoBuilder can't break PackageBuilder.Parameter.
- Position
- Below the diagonal: MonorepoBuilder uses a module listed above it, which is the healthy direction.
26→13 MonorepoBuilder uses MonorepoBuilder.ComposerJsonManipulator.FileSystem✕
- Connections
- 3 pairs of types, where a type in MonorepoBuilder uses a type in MonorepoBuilder.ComposerJsonManipulator.FileSystem.
- The types involved
Symplify.MonorepoBuilder.DependencyUpdater→Symplify.MonorepoBuilder.ComposerJsonManipulator.FileSystem.JsonFileManagerSymplify.MonorepoBuilder.DevMasterAliasUpdater→Symplify.MonorepoBuilder.ComposerJsonManipulator.FileSystem.JsonFileManagerSymplify.MonorepoBuilder.VersionValidator→Symplify.MonorepoBuilder.ComposerJsonManipulator.FileSystem.JsonFileManager
- Direction
- MonorepoBuilder uses MonorepoBuilder.ComposerJsonManipulator.FileSystem, so a change to MonorepoBuilder.ComposerJsonManipulator.FileSystem can break MonorepoBuilder, while a change to MonorepoBuilder can't break MonorepoBuilder.ComposerJsonManipulator.FileSystem.
- Position
- Below the diagonal: MonorepoBuilder uses a module listed above it, which is the healthy direction.
26→25 MonorepoBuilder uses MonorepoBuilder.Merge.Configuration✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder uses a type in MonorepoBuilder.Merge.Configuration.
- The types involved
Symplify.MonorepoBuilder.VersionValidator→Symplify.MonorepoBuilder.Merge.Configuration.ModifyingComposerJsonProvider
- Direction
- MonorepoBuilder uses MonorepoBuilder.Merge.Configuration, so a change to MonorepoBuilder.Merge.Configuration can break MonorepoBuilder, while a change to MonorepoBuilder can't break MonorepoBuilder.Merge.Configuration.
- Position
- Below the diagonal: MonorepoBuilder uses a module listed above it, which is the healthy direction.
27→4 MonorepoBuilder.Merge uses SmartFileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge uses a type in SmartFileSystem.
- The types involved
Symplify.MonorepoBuilder.Merge.ComposerJsonMerger→Symplify.SmartFileSystem.SmartFileInfo
- Direction
- MonorepoBuilder.Merge uses SmartFileSystem, so a change to SmartFileSystem can break MonorepoBuilder.Merge, while a change to MonorepoBuilder.Merge can't break SmartFileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Merge uses a module listed above it, which is the healthy direction.
27→8 MonorepoBuilder.Merge uses MonorepoBuilder.ComposerJsonManipulator.ValueObject✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge uses a type in MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- The types involved
Symplify.MonorepoBuilder.Merge.ComposerJsonMerger→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJson
- Direction
- MonorepoBuilder.Merge uses MonorepoBuilder.ComposerJsonManipulator.ValueObject, so a change to MonorepoBuilder.ComposerJsonManipulator.ValueObject can break MonorepoBuilder.Merge, while a change to MonorepoBuilder.Merge can't break MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- Position
- Below the diagonal: MonorepoBuilder.Merge uses a module listed above it, which is the healthy direction.
27→20 MonorepoBuilder.Merge uses MonorepoBuilder.ComposerJsonManipulator✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge uses a type in MonorepoBuilder.ComposerJsonManipulator.
- The types involved
Symplify.MonorepoBuilder.Merge.ComposerJsonMerger→Symplify.MonorepoBuilder.ComposerJsonManipulator.ComposerJsonFactory
- Direction
- MonorepoBuilder.Merge uses MonorepoBuilder.ComposerJsonManipulator, so a change to MonorepoBuilder.ComposerJsonManipulator can break MonorepoBuilder.Merge, while a change to MonorepoBuilder.Merge can't break MonorepoBuilder.ComposerJsonManipulator.
- Position
- Below the diagonal: MonorepoBuilder.Merge uses a module listed above it, which is the healthy direction.
27→25 MonorepoBuilder.Merge uses MonorepoBuilder.Merge.Configuration✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge uses a type in MonorepoBuilder.Merge.Configuration.
- The types involved
Symplify.MonorepoBuilder.Merge.ComposerJsonMerger→Symplify.MonorepoBuilder.Merge.Configuration.MergedPackagesCollector
- Direction
- MonorepoBuilder.Merge uses MonorepoBuilder.Merge.Configuration, so a change to MonorepoBuilder.Merge.Configuration can break MonorepoBuilder.Merge, while a change to MonorepoBuilder.Merge can't break MonorepoBuilder.Merge.Configuration.
- Position
- Below the diagonal: MonorepoBuilder.Merge uses a module listed above it, which is the healthy direction.
28→4 MonorepoBuilder.Package uses SmartFileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Package uses a type in SmartFileSystem.
- The types involved
Symplify.MonorepoBuilder.Package.PackageNamesProvider→Symplify.SmartFileSystem.SmartFileInfo
- Direction
- MonorepoBuilder.Package uses SmartFileSystem, so a change to SmartFileSystem can break MonorepoBuilder.Package, while a change to MonorepoBuilder.Package can't break SmartFileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Package uses a module listed above it, which is the healthy direction.
28→13 MonorepoBuilder.Package uses MonorepoBuilder.ComposerJsonManipulator.FileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Package uses a type in MonorepoBuilder.ComposerJsonManipulator.FileSystem.
- The types involved
Symplify.MonorepoBuilder.Package.PackageNamesProvider→Symplify.MonorepoBuilder.ComposerJsonManipulator.FileSystem.JsonFileManager
- Direction
- MonorepoBuilder.Package uses MonorepoBuilder.ComposerJsonManipulator.FileSystem, so a change to MonorepoBuilder.ComposerJsonManipulator.FileSystem can break MonorepoBuilder.Package, while a change to MonorepoBuilder.Package can't break MonorepoBuilder.ComposerJsonManipulator.FileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Package uses a module listed above it, which is the healthy direction.
28→24 MonorepoBuilder.Package uses MonorepoBuilder.FileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Package uses a type in MonorepoBuilder.FileSystem.
- The types involved
Symplify.MonorepoBuilder.Package.PackageNamesProvider→Symplify.MonorepoBuilder.FileSystem.ComposerJsonProvider
- Direction
- MonorepoBuilder.Package uses MonorepoBuilder.FileSystem, so a change to MonorepoBuilder.FileSystem can break MonorepoBuilder.Package, while a change to MonorepoBuilder.Package can't break MonorepoBuilder.FileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Package uses a module listed above it, which is the healthy direction.
29→13 MonorepoBuilder.Propagate.Command uses MonorepoBuilder.ComposerJsonManipulator.FileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Propagate.Command uses a type in MonorepoBuilder.ComposerJsonManipulator.FileSystem.
- The types involved
Symplify.MonorepoBuilder.Propagate.Command.PropagateCommand→Symplify.MonorepoBuilder.ComposerJsonManipulator.FileSystem.JsonFileManager
- Direction
- MonorepoBuilder.Propagate.Command uses MonorepoBuilder.ComposerJsonManipulator.FileSystem, so a change to MonorepoBuilder.ComposerJsonManipulator.FileSystem can break MonorepoBuilder.Propagate.Command, while a change to MonorepoBuilder.Propagate.Command can't break MonorepoBuilder.ComposerJsonManipulator.FileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Propagate.Command uses a module listed above it, which is the healthy direction.
29→18 MonorepoBuilder.Propagate.Command uses PackageBuilder.Console.Command✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Propagate.Command uses a type in PackageBuilder.Console.Command.
- The types involved
Symplify.MonorepoBuilder.Propagate.Command.PropagateCommand→Symplify.PackageBuilder.Console.Command.AbstractSymplifyCommand
- Direction
- MonorepoBuilder.Propagate.Command uses PackageBuilder.Console.Command, so a change to PackageBuilder.Console.Command can break MonorepoBuilder.Propagate.Command, while a change to MonorepoBuilder.Propagate.Command can't break PackageBuilder.Console.Command.
- Position
- Below the diagonal: MonorepoBuilder.Propagate.Command uses a module listed above it, which is the healthy direction.
29→24 MonorepoBuilder.Propagate.Command uses MonorepoBuilder.FileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Propagate.Command uses a type in MonorepoBuilder.FileSystem.
- The types involved
Symplify.MonorepoBuilder.Propagate.Command.PropagateCommand→Symplify.MonorepoBuilder.FileSystem.ComposerJsonProvider
- Direction
- MonorepoBuilder.Propagate.Command uses MonorepoBuilder.FileSystem, so a change to MonorepoBuilder.FileSystem can break MonorepoBuilder.Propagate.Command, while a change to MonorepoBuilder.Propagate.Command can't break MonorepoBuilder.FileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Propagate.Command uses a module listed above it, which is the healthy direction.
30→3 MonorepoBuilder.Testing.ComposerJson uses PackageBuilder.Parameter✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Testing.ComposerJson uses a type in PackageBuilder.Parameter.
- The types involved
Symplify.MonorepoBuilder.Testing.ComposerJson.ComposerVersionManipulator→Symplify.PackageBuilder.Parameter.ParameterProvider
- Direction
- MonorepoBuilder.Testing.ComposerJson uses PackageBuilder.Parameter, so a change to PackageBuilder.Parameter can break MonorepoBuilder.Testing.ComposerJson, while a change to MonorepoBuilder.Testing.ComposerJson can't break PackageBuilder.Parameter.
- Position
- Below the diagonal: MonorepoBuilder.Testing.ComposerJson uses a module listed above it, which is the healthy direction.
30→4 MonorepoBuilder.Testing.ComposerJson uses SmartFileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Testing.ComposerJson uses a type in SmartFileSystem.
- The types involved
Symplify.MonorepoBuilder.Testing.ComposerJson.ComposerJsonSymlinker→Symplify.SmartFileSystem.SmartFileInfo
- Direction
- MonorepoBuilder.Testing.ComposerJson uses SmartFileSystem, so a change to SmartFileSystem can break MonorepoBuilder.Testing.ComposerJson, while a change to MonorepoBuilder.Testing.ComposerJson can't break SmartFileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Testing.ComposerJson uses a module listed above it, which is the healthy direction.
30→13 MonorepoBuilder.Testing.ComposerJson uses MonorepoBuilder.ComposerJsonManipulator.FileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Testing.ComposerJson uses a type in MonorepoBuilder.ComposerJsonManipulator.FileSystem.
- The types involved
Symplify.MonorepoBuilder.Testing.ComposerJson.ComposerJsonSymlinker→Symplify.MonorepoBuilder.ComposerJsonManipulator.FileSystem.JsonFileManager
- Direction
- MonorepoBuilder.Testing.ComposerJson uses MonorepoBuilder.ComposerJsonManipulator.FileSystem, so a change to MonorepoBuilder.ComposerJsonManipulator.FileSystem can break MonorepoBuilder.Testing.ComposerJson, while a change to MonorepoBuilder.Testing.ComposerJson can't break MonorepoBuilder.ComposerJsonManipulator.FileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Testing.ComposerJson uses a module listed above it, which is the healthy direction.
30→24 MonorepoBuilder.Testing.ComposerJson uses MonorepoBuilder.FileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Testing.ComposerJson uses a type in MonorepoBuilder.FileSystem.
- The types involved
Symplify.MonorepoBuilder.Testing.ComposerJson.ComposerJsonSymlinker→Symplify.MonorepoBuilder.FileSystem.ComposerJsonProvider
- Direction
- MonorepoBuilder.Testing.ComposerJson uses MonorepoBuilder.FileSystem, so a change to MonorepoBuilder.FileSystem can break MonorepoBuilder.Testing.ComposerJson, while a change to MonorepoBuilder.Testing.ComposerJson can't break MonorepoBuilder.FileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Testing.ComposerJson uses a module listed above it, which is the healthy direction.
31→3 MonorepoBuilder.Validator uses PackageBuilder.Parameter✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Validator uses a type in PackageBuilder.Parameter.
- The types involved
Symplify.MonorepoBuilder.Validator.SourcesPresenceValidator→Symplify.PackageBuilder.Parameter.ParameterProvider
- Direction
- MonorepoBuilder.Validator uses PackageBuilder.Parameter, so a change to PackageBuilder.Parameter can break MonorepoBuilder.Validator, while a change to MonorepoBuilder.Validator can't break PackageBuilder.Parameter.
- Position
- Below the diagonal: MonorepoBuilder.Validator uses a module listed above it, which is the healthy direction.
31→24 MonorepoBuilder.Validator uses MonorepoBuilder.FileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Validator uses a type in MonorepoBuilder.FileSystem.
- The types involved
Symplify.MonorepoBuilder.Validator.SourcesPresenceValidator→Symplify.MonorepoBuilder.FileSystem.ComposerJsonProvider
- Direction
- MonorepoBuilder.Validator uses MonorepoBuilder.FileSystem, so a change to MonorepoBuilder.FileSystem can break MonorepoBuilder.Validator, while a change to MonorepoBuilder.Validator can't break MonorepoBuilder.FileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Validator uses a module listed above it, which is the healthy direction.
32→14 MonorepoBuilder.Command uses MonorepoBuilder.Finder✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Command uses a type in MonorepoBuilder.Finder.
- The types involved
Symplify.MonorepoBuilder.Command.PackageAliasCommand→Symplify.MonorepoBuilder.Finder.PackageComposerFinder
- Direction
- MonorepoBuilder.Command uses MonorepoBuilder.Finder, so a change to MonorepoBuilder.Finder can break MonorepoBuilder.Command, while a change to MonorepoBuilder.Command can't break MonorepoBuilder.Finder.
- Position
- Below the diagonal: MonorepoBuilder.Command uses a module listed above it, which is the healthy direction.
32→15 MonorepoBuilder.Command uses MonorepoBuilder.Git✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Command uses a type in MonorepoBuilder.Git.
- The types involved
Symplify.MonorepoBuilder.Command.PackageAliasCommand→Symplify.MonorepoBuilder.Git.ExpectedAliasResolver
- Direction
- MonorepoBuilder.Command uses MonorepoBuilder.Git, so a change to MonorepoBuilder.Git can break MonorepoBuilder.Command, while a change to MonorepoBuilder.Command can't break MonorepoBuilder.Git.
- Position
- Below the diagonal: MonorepoBuilder.Command uses a module listed above it, which is the healthy direction.
32→18 MonorepoBuilder.Command uses PackageBuilder.Console.Command✕
- Connections
- 3 pairs of types, where a type in MonorepoBuilder.Command uses a type in PackageBuilder.Console.Command.
- The types involved
Symplify.MonorepoBuilder.Command.BumpInterdependencyCommand→Symplify.PackageBuilder.Console.Command.AbstractSymplifyCommandSymplify.MonorepoBuilder.Command.PackageAliasCommand→Symplify.PackageBuilder.Console.Command.AbstractSymplifyCommandSymplify.MonorepoBuilder.Command.ValidateCommand→Symplify.PackageBuilder.Console.Command.AbstractSymplifyCommand
- Direction
- MonorepoBuilder.Command uses PackageBuilder.Console.Command, so a change to PackageBuilder.Console.Command can break MonorepoBuilder.Command, while a change to MonorepoBuilder.Command can't break PackageBuilder.Console.Command.
- Position
- Below the diagonal: MonorepoBuilder.Command uses a module listed above it, which is the healthy direction.
32→24 MonorepoBuilder.Command uses MonorepoBuilder.FileSystem✕
- Connections
- 2 pairs of types, where a type in MonorepoBuilder.Command uses a type in MonorepoBuilder.FileSystem.
- The types involved
Symplify.MonorepoBuilder.Command.BumpInterdependencyCommand→Symplify.MonorepoBuilder.FileSystem.ComposerJsonProviderSymplify.MonorepoBuilder.Command.ValidateCommand→Symplify.MonorepoBuilder.FileSystem.ComposerJsonProvider
- Direction
- MonorepoBuilder.Command uses MonorepoBuilder.FileSystem, so a change to MonorepoBuilder.FileSystem can break MonorepoBuilder.Command, while a change to MonorepoBuilder.Command can't break MonorepoBuilder.FileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Command uses a module listed above it, which is the healthy direction.
32→26 MonorepoBuilder.Command uses MonorepoBuilder✕
- Connections
- 3 pairs of types, where a type in MonorepoBuilder.Command uses a type in MonorepoBuilder.
- The types involved
Symplify.MonorepoBuilder.Command.BumpInterdependencyCommand→Symplify.MonorepoBuilder.DependencyUpdaterSymplify.MonorepoBuilder.Command.PackageAliasCommand→Symplify.MonorepoBuilder.DevMasterAliasUpdaterSymplify.MonorepoBuilder.Command.ValidateCommand→Symplify.MonorepoBuilder.VersionValidator
- Direction
- MonorepoBuilder.Command uses MonorepoBuilder, so a change to MonorepoBuilder can break MonorepoBuilder.Command, while a change to MonorepoBuilder.Command can't break MonorepoBuilder.
- Position
- Below the diagonal: MonorepoBuilder.Command uses a module listed above it, which is the healthy direction.
32→31 MonorepoBuilder.Command uses MonorepoBuilder.Validator✕
- Connections
- 3 pairs of types, where a type in MonorepoBuilder.Command uses a type in MonorepoBuilder.Validator.
- The types involved
Symplify.MonorepoBuilder.Command.BumpInterdependencyCommand→Symplify.MonorepoBuilder.Validator.SourcesPresenceValidatorSymplify.MonorepoBuilder.Command.ValidateCommand→Symplify.MonorepoBuilder.Validator.ConflictingPackageVersionsReporterSymplify.MonorepoBuilder.Command.ValidateCommand→Symplify.MonorepoBuilder.Validator.SourcesPresenceValidator
- Direction
- MonorepoBuilder.Command uses MonorepoBuilder.Validator, so a change to MonorepoBuilder.Validator can break MonorepoBuilder.Command, while a change to MonorepoBuilder.Command can't break MonorepoBuilder.Validator.
- Position
- Below the diagonal: MonorepoBuilder.Command uses a module listed above it, which is the healthy direction.
33→8 MonorepoBuilder.Merge.Application uses MonorepoBuilder.ComposerJsonManipulator.ValueObject✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge.Application uses a type in MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- The types involved
Symplify.MonorepoBuilder.Merge.Application.MergedAndDecoratedComposerJsonFactory→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJson
- Direction
- MonorepoBuilder.Merge.Application uses MonorepoBuilder.ComposerJsonManipulator.ValueObject, so a change to MonorepoBuilder.ComposerJsonManipulator.ValueObject can break MonorepoBuilder.Merge.Application, while a change to MonorepoBuilder.Merge.Application can't break MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- Position
- Below the diagonal: MonorepoBuilder.Merge.Application uses a module listed above it, which is the healthy direction.
33→16 MonorepoBuilder.Merge.Application uses MonorepoBuilder.Merge.Contract✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge.Application uses a type in MonorepoBuilder.Merge.Contract.
- The types involved
Symplify.MonorepoBuilder.Merge.Application.MergedAndDecoratedComposerJsonFactory→Symplify.MonorepoBuilder.Merge.Contract.ComposerJsonDecoratorInterface
- Direction
- MonorepoBuilder.Merge.Application uses MonorepoBuilder.Merge.Contract, so a change to MonorepoBuilder.Merge.Contract can break MonorepoBuilder.Merge.Application, while a change to MonorepoBuilder.Merge.Application can't break MonorepoBuilder.Merge.Contract.
- Position
- Below the diagonal: MonorepoBuilder.Merge.Application uses a module listed above it, which is the healthy direction.
33→27 MonorepoBuilder.Merge.Application uses MonorepoBuilder.Merge✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge.Application uses a type in MonorepoBuilder.Merge.
- The types involved
Symplify.MonorepoBuilder.Merge.Application.MergedAndDecoratedComposerJsonFactory→Symplify.MonorepoBuilder.Merge.ComposerJsonMerger
- Direction
- MonorepoBuilder.Merge.Application uses MonorepoBuilder.Merge, so a change to MonorepoBuilder.Merge can break MonorepoBuilder.Merge.Application, while a change to MonorepoBuilder.Merge.Application can't break MonorepoBuilder.Merge.
- Position
- Below the diagonal: MonorepoBuilder.Merge.Application uses a module listed above it, which is the healthy direction.
34→3 MonorepoBuilder.Merge.ComposerJsonDecorator uses PackageBuilder.Parameter✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge.ComposerJsonDecorator uses a type in PackageBuilder.Parameter.
- The types involved
Symplify.MonorepoBuilder.Merge.ComposerJsonDecorator.SortComposerJsonDecorator→Symplify.PackageBuilder.Parameter.ParameterProvider
- Direction
- MonorepoBuilder.Merge.ComposerJsonDecorator uses PackageBuilder.Parameter, so a change to PackageBuilder.Parameter can break MonorepoBuilder.Merge.ComposerJsonDecorator, while a change to MonorepoBuilder.Merge.ComposerJsonDecorator can't break PackageBuilder.Parameter.
- Position
- Below the diagonal: MonorepoBuilder.Merge.ComposerJsonDecorator uses a module listed above it, which is the healthy direction.
34→8 MonorepoBuilder.Merge.ComposerJsonDecorator uses MonorepoBuilder.ComposerJsonManipulator.ValueObject✕
- Connections
- 7 pairs of types, where a type in MonorepoBuilder.Merge.ComposerJsonDecorator uses a type in MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- The types involved
Symplify.MonorepoBuilder.Merge.ComposerJsonDecorator.AppenderComposerJsonDecorator→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJsonSymplify.MonorepoBuilder.Merge.ComposerJsonDecorator.FilterOutDuplicatedRequireAndRequireDevJsonDecorator→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJsonSymplify.MonorepoBuilder.Merge.ComposerJsonDecorator.RemoverComposerJsonDecorator→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJsonSymplify.MonorepoBuilder.Merge.ComposerJsonDecorator.ReplaceSectionJsonDecorator→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJsonSymplify.MonorepoBuilder.Merge.ComposerJsonDecorator.RepositoryPathComposerJsonDecorator→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJsonSymplify.MonorepoBuilder.Merge.ComposerJsonDecorator.RootRemoveComposerJsonDecorator→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJsonSymplify.MonorepoBuilder.Merge.ComposerJsonDecorator.SortComposerJsonDecorator→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJson
- Direction
- MonorepoBuilder.Merge.ComposerJsonDecorator uses MonorepoBuilder.ComposerJsonManipulator.ValueObject, so a change to MonorepoBuilder.ComposerJsonManipulator.ValueObject can break MonorepoBuilder.Merge.ComposerJsonDecorator, while a change to MonorepoBuilder.Merge.ComposerJsonDecorator can't break MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- Position
- Below the diagonal: MonorepoBuilder.Merge.ComposerJsonDecorator uses a module listed above it, which is the healthy direction.
34→16 MonorepoBuilder.Merge.ComposerJsonDecorator uses MonorepoBuilder.Merge.Contract✕
- Connections
- 7 pairs of types, where a type in MonorepoBuilder.Merge.ComposerJsonDecorator uses a type in MonorepoBuilder.Merge.Contract.
- The types involved
Symplify.MonorepoBuilder.Merge.ComposerJsonDecorator.AppenderComposerJsonDecorator→Symplify.MonorepoBuilder.Merge.Contract.ComposerJsonDecoratorInterfaceSymplify.MonorepoBuilder.Merge.ComposerJsonDecorator.FilterOutDuplicatedRequireAndRequireDevJsonDecorator→Symplify.MonorepoBuilder.Merge.Contract.ComposerJsonDecoratorInterfaceSymplify.MonorepoBuilder.Merge.ComposerJsonDecorator.RemoverComposerJsonDecorator→Symplify.MonorepoBuilder.Merge.Contract.ComposerJsonDecoratorInterfaceSymplify.MonorepoBuilder.Merge.ComposerJsonDecorator.ReplaceSectionJsonDecorator→Symplify.MonorepoBuilder.Merge.Contract.ComposerJsonDecoratorInterfaceSymplify.MonorepoBuilder.Merge.ComposerJsonDecorator.RepositoryPathComposerJsonDecorator→Symplify.MonorepoBuilder.Merge.Contract.ComposerJsonDecoratorInterfaceSymplify.MonorepoBuilder.Merge.ComposerJsonDecorator.RootRemoveComposerJsonDecorator→Symplify.MonorepoBuilder.Merge.Contract.ComposerJsonDecoratorInterfaceSymplify.MonorepoBuilder.Merge.ComposerJsonDecorator.SortComposerJsonDecorator→Symplify.MonorepoBuilder.Merge.Contract.ComposerJsonDecoratorInterface
- Direction
- MonorepoBuilder.Merge.ComposerJsonDecorator uses MonorepoBuilder.Merge.Contract, so a change to MonorepoBuilder.Merge.Contract can break MonorepoBuilder.Merge.ComposerJsonDecorator, while a change to MonorepoBuilder.Merge.ComposerJsonDecorator can't break MonorepoBuilder.Merge.Contract.
- Position
- Below the diagonal: MonorepoBuilder.Merge.ComposerJsonDecorator uses a module listed above it, which is the healthy direction.
34→25 MonorepoBuilder.Merge.ComposerJsonDecorator uses MonorepoBuilder.Merge.Configuration✕
- Connections
- 4 pairs of types, where a type in MonorepoBuilder.Merge.ComposerJsonDecorator uses a type in MonorepoBuilder.Merge.Configuration.
- The types involved
Symplify.MonorepoBuilder.Merge.ComposerJsonDecorator.AppenderComposerJsonDecorator→Symplify.MonorepoBuilder.Merge.Configuration.ModifyingComposerJsonProviderSymplify.MonorepoBuilder.Merge.ComposerJsonDecorator.RemoverComposerJsonDecorator→Symplify.MonorepoBuilder.Merge.Configuration.ModifyingComposerJsonProviderSymplify.MonorepoBuilder.Merge.ComposerJsonDecorator.ReplaceSectionJsonDecorator→Symplify.MonorepoBuilder.Merge.Configuration.MergedPackagesCollectorSymplify.MonorepoBuilder.Merge.ComposerJsonDecorator.RootRemoveComposerJsonDecorator→Symplify.MonorepoBuilder.Merge.Configuration.MergedPackagesCollector
- Direction
- MonorepoBuilder.Merge.ComposerJsonDecorator uses MonorepoBuilder.Merge.Configuration, so a change to MonorepoBuilder.Merge.Configuration can break MonorepoBuilder.Merge.ComposerJsonDecorator, while a change to MonorepoBuilder.Merge.ComposerJsonDecorator can't break MonorepoBuilder.Merge.Configuration.
- Position
- Below the diagonal: MonorepoBuilder.Merge.ComposerJsonDecorator uses a module listed above it, which is the healthy direction.
34→27 MonorepoBuilder.Merge.ComposerJsonDecorator uses MonorepoBuilder.Merge✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge.ComposerJsonDecorator uses a type in MonorepoBuilder.Merge.
- The types involved
Symplify.MonorepoBuilder.Merge.ComposerJsonDecorator.AppenderComposerJsonDecorator→Symplify.MonorepoBuilder.Merge.ComposerJsonMerger
- Direction
- MonorepoBuilder.Merge.ComposerJsonDecorator uses MonorepoBuilder.Merge, so a change to MonorepoBuilder.Merge can break MonorepoBuilder.Merge.ComposerJsonDecorator, while a change to MonorepoBuilder.Merge.ComposerJsonDecorator can't break MonorepoBuilder.Merge.
- Position
- Below the diagonal: MonorepoBuilder.Merge.ComposerJsonDecorator uses a module listed above it, which is the healthy direction.
35→24 MonorepoBuilder.Merge.Guard uses MonorepoBuilder.FileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge.Guard uses a type in MonorepoBuilder.FileSystem.
- The types involved
Symplify.MonorepoBuilder.Merge.Guard.ConflictingVersionsGuard→Symplify.MonorepoBuilder.FileSystem.ComposerJsonProvider
- Direction
- MonorepoBuilder.Merge.Guard uses MonorepoBuilder.FileSystem, so a change to MonorepoBuilder.FileSystem can break MonorepoBuilder.Merge.Guard, while a change to MonorepoBuilder.Merge.Guard can't break MonorepoBuilder.FileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Merge.Guard uses a module listed above it, which is the healthy direction.
35→26 MonorepoBuilder.Merge.Guard uses MonorepoBuilder✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge.Guard uses a type in MonorepoBuilder.
- The types involved
Symplify.MonorepoBuilder.Merge.Guard.ConflictingVersionsGuard→Symplify.MonorepoBuilder.VersionValidator
- Direction
- MonorepoBuilder.Merge.Guard uses MonorepoBuilder, so a change to MonorepoBuilder can break MonorepoBuilder.Merge.Guard, while a change to MonorepoBuilder.Merge.Guard can't break MonorepoBuilder.
- Position
- Below the diagonal: MonorepoBuilder.Merge.Guard uses a module listed above it, which is the healthy direction.
35→31 MonorepoBuilder.Merge.Guard uses MonorepoBuilder.Validator✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge.Guard uses a type in MonorepoBuilder.Validator.
- The types involved
Symplify.MonorepoBuilder.Merge.Guard.ConflictingVersionsGuard→Symplify.MonorepoBuilder.Validator.ConflictingPackageVersionsReporter
- Direction
- MonorepoBuilder.Merge.Guard uses MonorepoBuilder.Validator, so a change to MonorepoBuilder.Validator can break MonorepoBuilder.Merge.Guard, while a change to MonorepoBuilder.Merge.Guard can't break MonorepoBuilder.Validator.
- Position
- Below the diagonal: MonorepoBuilder.Merge.Guard uses a module listed above it, which is the healthy direction.
36→18 MonorepoBuilder.Release.Command uses PackageBuilder.Console.Command✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Release.Command uses a type in PackageBuilder.Console.Command.
- The types involved
Symplify.MonorepoBuilder.Release.Command.ReleaseCommand→Symplify.PackageBuilder.Console.Command.AbstractSymplifyCommand
- Direction
- MonorepoBuilder.Release.Command uses PackageBuilder.Console.Command, so a change to PackageBuilder.Console.Command can break MonorepoBuilder.Release.Command, while a change to MonorepoBuilder.Release.Command can't break PackageBuilder.Console.Command.
- Position
- Below the diagonal: MonorepoBuilder.Release.Command uses a module listed above it, which is the healthy direction.
36→23 MonorepoBuilder.Release.Command uses MonorepoBuilder.Release.Configuration✕
- Connections
- 2 pairs of types, where a type in MonorepoBuilder.Release.Command uses a type in MonorepoBuilder.Release.Configuration.
- The types involved
Symplify.MonorepoBuilder.Release.Command.ReleaseCommand→Symplify.MonorepoBuilder.Release.Configuration.StageResolverSymplify.MonorepoBuilder.Release.Command.ReleaseCommand→Symplify.MonorepoBuilder.Release.Configuration.VersionResolver
- Direction
- MonorepoBuilder.Release.Command uses MonorepoBuilder.Release.Configuration, so a change to MonorepoBuilder.Release.Configuration can break MonorepoBuilder.Release.Command, while a change to MonorepoBuilder.Release.Command can't break MonorepoBuilder.Release.Configuration.
- Position
- Below the diagonal: MonorepoBuilder.Release.Command uses a module listed above it, which is the healthy direction.
36→31 MonorepoBuilder.Release.Command uses MonorepoBuilder.Validator✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Release.Command uses a type in MonorepoBuilder.Validator.
- The types involved
Symplify.MonorepoBuilder.Release.Command.ReleaseCommand→Symplify.MonorepoBuilder.Validator.SourcesPresenceValidator
- Direction
- MonorepoBuilder.Release.Command uses MonorepoBuilder.Validator, so a change to MonorepoBuilder.Validator can break MonorepoBuilder.Release.Command, while a change to MonorepoBuilder.Release.Command can't break MonorepoBuilder.Validator.
- Position
- Below the diagonal: MonorepoBuilder.Release.Command uses a module listed above it, which is the healthy direction.
37→3 MonorepoBuilder.Release.ReleaseWorker uses PackageBuilder.Parameter✕
- Connections
- 2 pairs of types, where a type in MonorepoBuilder.Release.ReleaseWorker uses a type in PackageBuilder.Parameter.
- The types involved
Symplify.MonorepoBuilder.Release.ReleaseWorker.PushNextDevReleaseWorker→Symplify.PackageBuilder.Parameter.ParameterProviderSymplify.MonorepoBuilder.Release.ReleaseWorker.TagVersionReleaseWorker→Symplify.PackageBuilder.Parameter.ParameterProvider
- Direction
- MonorepoBuilder.Release.ReleaseWorker uses PackageBuilder.Parameter, so a change to PackageBuilder.Parameter can break MonorepoBuilder.Release.ReleaseWorker, while a change to MonorepoBuilder.Release.ReleaseWorker can't break PackageBuilder.Parameter.
- Position
- Below the diagonal: MonorepoBuilder.Release.ReleaseWorker uses a module listed above it, which is the healthy direction.
37→4 MonorepoBuilder.Release.ReleaseWorker uses SmartFileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Release.ReleaseWorker uses a type in SmartFileSystem.
- The types involved
Symplify.MonorepoBuilder.Release.ReleaseWorker.AddTagToChangelogReleaseWorker→Symplify.SmartFileSystem.SmartFileSystem
- Direction
- MonorepoBuilder.Release.ReleaseWorker uses SmartFileSystem, so a change to SmartFileSystem can break MonorepoBuilder.Release.ReleaseWorker, while a change to MonorepoBuilder.Release.ReleaseWorker can't break SmartFileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Release.ReleaseWorker uses a module listed above it, which is the healthy direction.
37→10 MonorepoBuilder.Release.ReleaseWorker uses MonorepoBuilder.Utils✕
- Connections
- 4 pairs of types, where a type in MonorepoBuilder.Release.ReleaseWorker uses a type in MonorepoBuilder.Utils.
- The types involved
Symplify.MonorepoBuilder.Release.ReleaseWorker.PushNextDevReleaseWorker→Symplify.MonorepoBuilder.Utils.VersionUtilsSymplify.MonorepoBuilder.Release.ReleaseWorker.SetCurrentMutualDependenciesReleaseWorker→Symplify.MonorepoBuilder.Utils.VersionUtilsSymplify.MonorepoBuilder.Release.ReleaseWorker.SetNextMutualDependenciesReleaseWorker→Symplify.MonorepoBuilder.Utils.VersionUtilsSymplify.MonorepoBuilder.Release.ReleaseWorker.UpdateBranchAliasReleaseWorker→Symplify.MonorepoBuilder.Utils.VersionUtils
- Direction
- MonorepoBuilder.Release.ReleaseWorker uses MonorepoBuilder.Utils, so a change to MonorepoBuilder.Utils can break MonorepoBuilder.Release.ReleaseWorker, while a change to MonorepoBuilder.Release.ReleaseWorker can't break MonorepoBuilder.Utils.
- Position
- Below the diagonal: MonorepoBuilder.Release.ReleaseWorker uses a module listed above it, which is the healthy direction.
37→13 MonorepoBuilder.Release.ReleaseWorker uses MonorepoBuilder.ComposerJsonManipulator.FileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Release.ReleaseWorker uses a type in MonorepoBuilder.ComposerJsonManipulator.FileSystem.
- The types involved
Symplify.MonorepoBuilder.Release.ReleaseWorker.UpdateReplaceReleaseWorker→Symplify.MonorepoBuilder.ComposerJsonManipulator.FileSystem.JsonFileManager
- Direction
- MonorepoBuilder.Release.ReleaseWorker uses MonorepoBuilder.ComposerJsonManipulator.FileSystem, so a change to MonorepoBuilder.ComposerJsonManipulator.FileSystem can break MonorepoBuilder.Release.ReleaseWorker, while a change to MonorepoBuilder.Release.ReleaseWorker can't break MonorepoBuilder.ComposerJsonManipulator.FileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Release.ReleaseWorker uses a module listed above it, which is the healthy direction.
37→24 MonorepoBuilder.Release.ReleaseWorker uses MonorepoBuilder.FileSystem✕
- Connections
- 4 pairs of types, where a type in MonorepoBuilder.Release.ReleaseWorker uses a type in MonorepoBuilder.FileSystem.
- The types involved
Symplify.MonorepoBuilder.Release.ReleaseWorker.SetCurrentMutualDependenciesReleaseWorker→Symplify.MonorepoBuilder.FileSystem.ComposerJsonProviderSymplify.MonorepoBuilder.Release.ReleaseWorker.SetNextMutualDependenciesReleaseWorker→Symplify.MonorepoBuilder.FileSystem.ComposerJsonProviderSymplify.MonorepoBuilder.Release.ReleaseWorker.UpdateBranchAliasReleaseWorker→Symplify.MonorepoBuilder.FileSystem.ComposerJsonProviderSymplify.MonorepoBuilder.Release.ReleaseWorker.UpdateReplaceReleaseWorker→Symplify.MonorepoBuilder.FileSystem.ComposerJsonProvider
- Direction
- MonorepoBuilder.Release.ReleaseWorker uses MonorepoBuilder.FileSystem, so a change to MonorepoBuilder.FileSystem can break MonorepoBuilder.Release.ReleaseWorker, while a change to MonorepoBuilder.Release.ReleaseWorker can't break MonorepoBuilder.FileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Release.ReleaseWorker uses a module listed above it, which is the healthy direction.
37→26 MonorepoBuilder.Release.ReleaseWorker uses MonorepoBuilder✕
- Connections
- 3 pairs of types, where a type in MonorepoBuilder.Release.ReleaseWorker uses a type in MonorepoBuilder.
- The types involved
Symplify.MonorepoBuilder.Release.ReleaseWorker.SetCurrentMutualDependenciesReleaseWorker→Symplify.MonorepoBuilder.DependencyUpdaterSymplify.MonorepoBuilder.Release.ReleaseWorker.SetNextMutualDependenciesReleaseWorker→Symplify.MonorepoBuilder.DependencyUpdaterSymplify.MonorepoBuilder.Release.ReleaseWorker.UpdateBranchAliasReleaseWorker→Symplify.MonorepoBuilder.DevMasterAliasUpdater
- Direction
- MonorepoBuilder.Release.ReleaseWorker uses MonorepoBuilder, so a change to MonorepoBuilder can break MonorepoBuilder.Release.ReleaseWorker, while a change to MonorepoBuilder.Release.ReleaseWorker can't break MonorepoBuilder.
- Position
- Below the diagonal: MonorepoBuilder.Release.ReleaseWorker uses a module listed above it, which is the healthy direction.
37→28 MonorepoBuilder.Release.ReleaseWorker uses MonorepoBuilder.Package✕
- Connections
- 2 pairs of types, where a type in MonorepoBuilder.Release.ReleaseWorker uses a type in MonorepoBuilder.Package.
- The types involved
Symplify.MonorepoBuilder.Release.ReleaseWorker.SetCurrentMutualDependenciesReleaseWorker→Symplify.MonorepoBuilder.Package.PackageNamesProviderSymplify.MonorepoBuilder.Release.ReleaseWorker.SetNextMutualDependenciesReleaseWorker→Symplify.MonorepoBuilder.Package.PackageNamesProvider
- Direction
- MonorepoBuilder.Release.ReleaseWorker uses MonorepoBuilder.Package, so a change to MonorepoBuilder.Package can break MonorepoBuilder.Release.ReleaseWorker, while a change to MonorepoBuilder.Release.ReleaseWorker can't break MonorepoBuilder.Package.
- Position
- Below the diagonal: MonorepoBuilder.Release.ReleaseWorker uses a module listed above it, which is the healthy direction.
38→4 MonorepoBuilder.Testing uses SmartFileSystem✕
- Connections
- 2 pairs of types, where a type in MonorepoBuilder.Testing uses a type in SmartFileSystem.
- The types involved
Symplify.MonorepoBuilder.Testing.ComposerJsonRepositoriesUpdater→Symplify.SmartFileSystem.SmartFileInfoSymplify.MonorepoBuilder.Testing.ComposerJsonRequireUpdater→Symplify.SmartFileSystem.SmartFileInfo
- Direction
- MonorepoBuilder.Testing uses SmartFileSystem, so a change to SmartFileSystem can break MonorepoBuilder.Testing, while a change to MonorepoBuilder.Testing can't break SmartFileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Testing uses a module listed above it, which is the healthy direction.
38→8 MonorepoBuilder.Testing uses MonorepoBuilder.ComposerJsonManipulator.ValueObject✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Testing uses a type in MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- The types involved
Symplify.MonorepoBuilder.Testing.ComposerJsonRepositoriesUpdater→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJson
- Direction
- MonorepoBuilder.Testing uses MonorepoBuilder.ComposerJsonManipulator.ValueObject, so a change to MonorepoBuilder.ComposerJsonManipulator.ValueObject can break MonorepoBuilder.Testing, while a change to MonorepoBuilder.Testing can't break MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- Position
- Below the diagonal: MonorepoBuilder.Testing uses a module listed above it, which is the healthy direction.
38→13 MonorepoBuilder.Testing uses MonorepoBuilder.ComposerJsonManipulator.FileSystem✕
- Connections
- 2 pairs of types, where a type in MonorepoBuilder.Testing uses a type in MonorepoBuilder.ComposerJsonManipulator.FileSystem.
- The types involved
Symplify.MonorepoBuilder.Testing.ComposerJsonRepositoriesUpdater→Symplify.MonorepoBuilder.ComposerJsonManipulator.FileSystem.JsonFileManagerSymplify.MonorepoBuilder.Testing.ComposerJsonRequireUpdater→Symplify.MonorepoBuilder.ComposerJsonManipulator.FileSystem.JsonFileManager
- Direction
- MonorepoBuilder.Testing uses MonorepoBuilder.ComposerJsonManipulator.FileSystem, so a change to MonorepoBuilder.ComposerJsonManipulator.FileSystem can break MonorepoBuilder.Testing, while a change to MonorepoBuilder.Testing can't break MonorepoBuilder.ComposerJsonManipulator.FileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Testing uses a module listed above it, which is the healthy direction.
38→28 MonorepoBuilder.Testing uses MonorepoBuilder.Package✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Testing uses a type in MonorepoBuilder.Package.
- The types involved
Symplify.MonorepoBuilder.Testing.ComposerJsonRepositoriesUpdater→Symplify.MonorepoBuilder.Package.PackageNamesProvider
- Direction
- MonorepoBuilder.Testing uses MonorepoBuilder.Package, so a change to MonorepoBuilder.Package can break MonorepoBuilder.Testing, while a change to MonorepoBuilder.Testing can't break MonorepoBuilder.Package.
- Position
- Below the diagonal: MonorepoBuilder.Testing uses a module listed above it, which is the healthy direction.
38→30 MonorepoBuilder.Testing uses MonorepoBuilder.Testing.ComposerJson✕
- Connections
- 2 pairs of types, where a type in MonorepoBuilder.Testing uses a type in MonorepoBuilder.Testing.ComposerJson.
- The types involved
Symplify.MonorepoBuilder.Testing.ComposerJsonRepositoriesUpdater→Symplify.MonorepoBuilder.Testing.ComposerJson.ComposerJsonSymlinkerSymplify.MonorepoBuilder.Testing.ComposerJsonRequireUpdater→Symplify.MonorepoBuilder.Testing.ComposerJson.ComposerVersionManipulator
- Direction
- MonorepoBuilder.Testing uses MonorepoBuilder.Testing.ComposerJson, so a change to MonorepoBuilder.Testing.ComposerJson can break MonorepoBuilder.Testing, while a change to MonorepoBuilder.Testing can't break MonorepoBuilder.Testing.ComposerJson.
- Position
- Below the diagonal: MonorepoBuilder.Testing uses a module listed above it, which is the healthy direction.
39→8 MonorepoBuilder.Merge.Command uses MonorepoBuilder.ComposerJsonManipulator.ValueObject✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge.Command uses a type in MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- The types involved
Symplify.MonorepoBuilder.Merge.Command.MergeCommand→Symplify.MonorepoBuilder.ComposerJsonManipulator.ValueObject.ComposerJson
- Direction
- MonorepoBuilder.Merge.Command uses MonorepoBuilder.ComposerJsonManipulator.ValueObject, so a change to MonorepoBuilder.ComposerJsonManipulator.ValueObject can break MonorepoBuilder.Merge.Command, while a change to MonorepoBuilder.Merge.Command can't break MonorepoBuilder.ComposerJsonManipulator.ValueObject.
- Position
- Below the diagonal: MonorepoBuilder.Merge.Command uses a module listed above it, which is the healthy direction.
39→13 MonorepoBuilder.Merge.Command uses MonorepoBuilder.ComposerJsonManipulator.FileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge.Command uses a type in MonorepoBuilder.ComposerJsonManipulator.FileSystem.
- The types involved
Symplify.MonorepoBuilder.Merge.Command.MergeCommand→Symplify.MonorepoBuilder.ComposerJsonManipulator.FileSystem.JsonFileManager
- Direction
- MonorepoBuilder.Merge.Command uses MonorepoBuilder.ComposerJsonManipulator.FileSystem, so a change to MonorepoBuilder.ComposerJsonManipulator.FileSystem can break MonorepoBuilder.Merge.Command, while a change to MonorepoBuilder.Merge.Command can't break MonorepoBuilder.ComposerJsonManipulator.FileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Merge.Command uses a module listed above it, which is the healthy direction.
39→18 MonorepoBuilder.Merge.Command uses PackageBuilder.Console.Command✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge.Command uses a type in PackageBuilder.Console.Command.
- The types involved
Symplify.MonorepoBuilder.Merge.Command.MergeCommand→Symplify.PackageBuilder.Console.Command.AbstractSymplifyCommand
- Direction
- MonorepoBuilder.Merge.Command uses PackageBuilder.Console.Command, so a change to PackageBuilder.Console.Command can break MonorepoBuilder.Merge.Command, while a change to MonorepoBuilder.Merge.Command can't break PackageBuilder.Console.Command.
- Position
- Below the diagonal: MonorepoBuilder.Merge.Command uses a module listed above it, which is the healthy direction.
39→20 MonorepoBuilder.Merge.Command uses MonorepoBuilder.ComposerJsonManipulator✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge.Command uses a type in MonorepoBuilder.ComposerJsonManipulator.
- The types involved
Symplify.MonorepoBuilder.Merge.Command.MergeCommand→Symplify.MonorepoBuilder.ComposerJsonManipulator.ComposerJsonFactory
- Direction
- MonorepoBuilder.Merge.Command uses MonorepoBuilder.ComposerJsonManipulator, so a change to MonorepoBuilder.ComposerJsonManipulator can break MonorepoBuilder.Merge.Command, while a change to MonorepoBuilder.Merge.Command can't break MonorepoBuilder.ComposerJsonManipulator.
- Position
- Below the diagonal: MonorepoBuilder.Merge.Command uses a module listed above it, which is the healthy direction.
39→24 MonorepoBuilder.Merge.Command uses MonorepoBuilder.FileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge.Command uses a type in MonorepoBuilder.FileSystem.
- The types involved
Symplify.MonorepoBuilder.Merge.Command.MergeCommand→Symplify.MonorepoBuilder.FileSystem.ComposerJsonProvider
- Direction
- MonorepoBuilder.Merge.Command uses MonorepoBuilder.FileSystem, so a change to MonorepoBuilder.FileSystem can break MonorepoBuilder.Merge.Command, while a change to MonorepoBuilder.Merge.Command can't break MonorepoBuilder.FileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Merge.Command uses a module listed above it, which is the healthy direction.
39→31 MonorepoBuilder.Merge.Command uses MonorepoBuilder.Validator✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge.Command uses a type in MonorepoBuilder.Validator.
- The types involved
Symplify.MonorepoBuilder.Merge.Command.MergeCommand→Symplify.MonorepoBuilder.Validator.SourcesPresenceValidator
- Direction
- MonorepoBuilder.Merge.Command uses MonorepoBuilder.Validator, so a change to MonorepoBuilder.Validator can break MonorepoBuilder.Merge.Command, while a change to MonorepoBuilder.Merge.Command can't break MonorepoBuilder.Validator.
- Position
- Below the diagonal: MonorepoBuilder.Merge.Command uses a module listed above it, which is the healthy direction.
39→33 MonorepoBuilder.Merge.Command uses MonorepoBuilder.Merge.Application✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge.Command uses a type in MonorepoBuilder.Merge.Application.
- The types involved
Symplify.MonorepoBuilder.Merge.Command.MergeCommand→Symplify.MonorepoBuilder.Merge.Application.MergedAndDecoratedComposerJsonFactory
- Direction
- MonorepoBuilder.Merge.Command uses MonorepoBuilder.Merge.Application, so a change to MonorepoBuilder.Merge.Application can break MonorepoBuilder.Merge.Command, while a change to MonorepoBuilder.Merge.Command can't break MonorepoBuilder.Merge.Application.
- Position
- Below the diagonal: MonorepoBuilder.Merge.Command uses a module listed above it, which is the healthy direction.
39→35 MonorepoBuilder.Merge.Command uses MonorepoBuilder.Merge.Guard✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Merge.Command uses a type in MonorepoBuilder.Merge.Guard.
- The types involved
Symplify.MonorepoBuilder.Merge.Command.MergeCommand→Symplify.MonorepoBuilder.Merge.Guard.ConflictingVersionsGuard
- Direction
- MonorepoBuilder.Merge.Command uses MonorepoBuilder.Merge.Guard, so a change to MonorepoBuilder.Merge.Guard can break MonorepoBuilder.Merge.Command, while a change to MonorepoBuilder.Merge.Command can't break MonorepoBuilder.Merge.Guard.
- Position
- Below the diagonal: MonorepoBuilder.Merge.Command uses a module listed above it, which is the healthy direction.
40→18 MonorepoBuilder.Testing.Command uses PackageBuilder.Console.Command✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Testing.Command uses a type in PackageBuilder.Console.Command.
- The types involved
Symplify.MonorepoBuilder.Testing.Command.LocalizeComposerPathsCommand→Symplify.PackageBuilder.Console.Command.AbstractSymplifyCommand
- Direction
- MonorepoBuilder.Testing.Command uses PackageBuilder.Console.Command, so a change to PackageBuilder.Console.Command can break MonorepoBuilder.Testing.Command, while a change to MonorepoBuilder.Testing.Command can't break PackageBuilder.Console.Command.
- Position
- Below the diagonal: MonorepoBuilder.Testing.Command uses a module listed above it, which is the healthy direction.
40→24 MonorepoBuilder.Testing.Command uses MonorepoBuilder.FileSystem✕
- Connections
- 1 pair of types, where a type in MonorepoBuilder.Testing.Command uses a type in MonorepoBuilder.FileSystem.
- The types involved
Symplify.MonorepoBuilder.Testing.Command.LocalizeComposerPathsCommand→Symplify.MonorepoBuilder.FileSystem.ComposerJsonProvider
- Direction
- MonorepoBuilder.Testing.Command uses MonorepoBuilder.FileSystem, so a change to MonorepoBuilder.FileSystem can break MonorepoBuilder.Testing.Command, while a change to MonorepoBuilder.Testing.Command can't break MonorepoBuilder.FileSystem.
- Position
- Below the diagonal: MonorepoBuilder.Testing.Command uses a module listed above it, which is the healthy direction.
40→38 MonorepoBuilder.Testing.Command uses MonorepoBuilder.Testing✕
- Connections
- 2 pairs of types, where a type in MonorepoBuilder.Testing.Command uses a type in MonorepoBuilder.Testing.
- The types involved
Symplify.MonorepoBuilder.Testing.Command.LocalizeComposerPathsCommand→Symplify.MonorepoBuilder.Testing.ComposerJsonRepositoriesUpdaterSymplify.MonorepoBuilder.Testing.Command.LocalizeComposerPathsCommand→Symplify.MonorepoBuilder.Testing.ComposerJsonRequireUpdater
- Direction
- MonorepoBuilder.Testing.Command uses MonorepoBuilder.Testing, so a change to MonorepoBuilder.Testing can break MonorepoBuilder.Testing.Command, while a change to MonorepoBuilder.Testing.Command can't break MonorepoBuilder.Testing.
- Position
- Below the diagonal: MonorepoBuilder.Testing.Command 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 26 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 9 | Medium |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json; 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; Resolve the 35 Orphaned file finding(s) in Knowledge Freshness — start with RemoverComposerJsonDecorator.php (2), ComposerJsonFactory.php, AutowireArrayParameterCompilerPass.php.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json. | +8.3 pts | Low | ADR Quality |
| 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. | +7.2 pts | Medium | Architecture documentation |
| Resolve the 35 Orphaned file finding(s) in Knowledge Freshness — start with RemoverComposerJsonDecorator.php (2), ComposerJsonFactory.php, AutowireArrayParameterCompilerPass.php. | +6.7 pts | Medium | Knowledge Freshness |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +5.9 pts | Medium | Observability |
| Resolve the 2 No assertions finding(s) in Test Quality — start with PackageComposerJsonMergerTest.php (2). | +1.3 pts | Low | Test Quality |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.3 pts | Medium | Release Hygiene |
| Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.1 pts | Low | Supply-chain Provenance & Signing |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +1.2 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| packages/ComposerJsonManipulator/ComposerJsonFactory.php | 7.8 | Mixed | Cyclomatic Complexity: ComposerJsonFactory.createFromArray (cyclomatic 28) |
| packages/Testing/ComposerJsonRepositoriesUpdater.php | 7.8 | Mixed | Code Duplication: Edited copy of a member (31 corresponding lines) |
| packages/Merge/PathResolver/AutoloadPathNormalizer.php | 7.8 | Mixed | Code Duplication: Edited copy of a member (12 corresponding lines) |
| src/DependencyUpdater.php | 7.8 | Mixed | Code Duplication: Edited copy of a member (8 corresponding lines) |
| packages-tests/Merge/Package/PackageComposerJsonMergerTest.php | 7.8 | Mixed | Test Quality: No assertions: testUniqueRepositories |
| src-deps/package-builder/src/DependencyInjection/FileLoader/ParameterMergingPhpFileLoader.php | 8.5 | Near-clean | Cognitive Complexity: ParameterMergingPhpFileLoader.executeCallback (cognitive 22) |
| packages/ComposerJsonManipulator/ValueObject/ComposerJson.php | 8.5 | Near-clean | God Classes: TooManyMethods: ComposerJson |
| packages/Merge/ComposerJsonDecorator/RemoverComposerJsonDecorator.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (18 corresponding lines) |
| src-deps/package-builder/src/Yaml/ParametersMerger.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (17 corresponding lines) |
| src-deps/autowire-array-parameter/src/DependencyInjection/DefinitionFinder.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (13 corresponding lines) |
| packages/Merge/ComposerJsonDecorator/FilterOutDuplicatedRequireAndRequireDevJsonDecorator.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (12 corresponding lines) |
| packages/Release/ReleaseWorker/SetCurrentMutualDependenciesReleaseWorker.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (7 corresponding lines) |
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 40 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 40 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, 90 of 106 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 — 11 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 (templates/monorepo/packages/second-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. `packages/ComposerJsonManipulator/ComposerJsonFactory.php`, `packages/ComposerJsonManipulator/FileSystem/JsonFileManager.php`, `packages/ComposerJsonManipulator/Json/JsonInliner.php`, `packages/ComposerJsonManipulator/Printer/ComposerJsonPrinter.php`, `packages/ComposerJsonManipulator/ValueObject/ComposerJson.php`, … (+66 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Symfony DependencyInjection and a PSR-11 container (Psr\Container) and an unrecognised PHP container, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- P7 Outbound HTTP resilience — 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 recognises outbound HTTP clients, their timeouts and resilience policies, and service entry points in .NET, Go, JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang. No service entry point was found in the PHP source it does read, and the rest of this repository's production source is , which it does not read yet — the service may well be there — a gap in this analyzer's language reach, not a finding about the code.
- 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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- 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.
- 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 ComposerJsonFactory.createFromArray at 28.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with ComposerJsonFactory.createFromArray (cyclomatic 28). — Refactoring it lifts Cyclomatic Complexity from 9.3 to about 10.0/10.
D2 · Cognitive Complexity
2 method(s) exceeded the cognitive complexity threshold of 15; the worst was ComposerJsonFactory.createFromArray at 27.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with ComposerJsonFactory.createFromArray (cognitive 27), ParameterMergingPhpFileLoader.executeCallback (cognitive 22). — 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.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
1 god class(es) detected.
What to do
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with ComposerJson.php. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
2 duplicated block group(s) detected. 2.5 % of the production lines (231 of 9,156) are in a reported copy. A further 9 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 2 Edited copy of a member (12 corresponding lines) finding(s) in Code Duplication — start with AutoloadPathNormalizer.php, FilterOutDuplicatedRequireAndRequireDevJsonDecorator.php. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with DefinitionFinder.php, DependencyUpdater.php. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (31 corresponding lines) finding(s) in Code Duplication — start with ComposerJsonRepositoriesUpdater.php. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
7 production modules (Composer), 1 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 6 of the 7 (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 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Circular dependency finding(s) in Coupling. — One of this dimension's main actionable groups (1 issue-level).
D6 · Cohesion (LCOM4)
0 of 46 classes have LCOM4 above 3.
D10 · Test Quality
5 skipped (5 with a documented reason), 2 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 72 tests.
What to do
- Resolve the 2 No assertions finding(s) in Test Quality — start with PackageComposerJsonMergerTest.php (2). — One of this dimension's main actionable groups (2 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
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/Config/MBConfig.php. Counted over 41 of the 210 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
0 deducted task-comment markers across 9156 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 6 document(s) read across 19 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 7 build units (Composer) flagged as possibly oversized/incoherent.
D27 · Navigability
60 % of calls cross a namespace and 1 % go through an interface, but 78 % of collaborators are co-located — so following a call takes several hops. 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)
26 finding(s): 0 critical, 25 high, 1 medium, 0 low. 25 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 87 file(s) — `packages-tests/Release/DisableDefaultWorkers/Fixture/FetchTagsReleaseWorker.php` (line 10), `packages-tests/Release/DisableDefaultWorkers/Fixture/GenerateChangelogReleaseWorker.php` (line 10), `packages/ComposerJsonManipulator/ComposerJsonFactory.php` (line 17), `packages/ComposerJsonManipulator/FileSystem/JsonFileManager.php` (line 25, line 26, line 27), `packages/ComposerJsonManipulator/Json/JsonInliner.php` (line 11), … (+82 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 25 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 (25 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
36 of 41 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/ComposerJsonManipulator/ValueObject/ComposerJson.php. Counted over 41 of the 210 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 35 Orphaned file finding(s) in Knowledge Freshness — start with RemoverComposerJsonDecorator.php (2), ComposerJsonFactory.php, AutowireArrayParameterCompilerPass.php. — One of this dimension's main actionable groups (35 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with ComposerJson.php. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — 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 11 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 symplify/easy-testing → symplify/smart-file-system → symplify/easy-testing (one cycle inside a mutually-dependent group of 3 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.
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
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — src-deps/autowire-array-parameter/src/DependencyInjection/DefinitionFinder.php:70
What to do
- Swallowed exception (caught, then discarded)
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 81.3 | Strong | Strongest area. |
| Architecture | 91.3 | Adequate — gated by D5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 50.7 | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 49.5 | Weak — gated by P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 73.7 | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
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 — 74 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests.
- 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 — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- 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.
- D11 Test Reliability — Test reliability not included — no .php test runner
- D12 Dependency Hygiene — Not scored — 11 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.
- 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. 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
- 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) — 71 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
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (38 value object(s))
- 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
- M4 Documentation accuracy — Not applicable: the 7 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (path 1); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — 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
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- 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
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or collection is reachable from two threads at once. 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 — 27 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Project dependency cycle
- Circular dependency
Serious — 27 finding(s)
- REDACTED
- REDACTED
- REDACTED
- No assertions: testUniqueRepositories packages-tests/Merge/Package/PackageComposerJsonMergerTest.php:22
- No assertions: testComposerPatches packages-tests/Merge/Package/PackageComposerJsonMergerTest.php:29
- Edited copy of a member (12 corresponding lines) packages/Merge/PathResolver/AutoloadPathNormalizer.php:58
- Edited copy of a member (12 corresponding lines) packages/Merge/ComposerJsonDecorator/FilterOutDuplicatedRequireAndRequireDevJsonDecorator.php:14
- Edited copy of a member (13 corresponding lines) src-deps/autowire-array-parameter/src/DependencyInjection/DefinitionFinder.php:23
- Edited copy of a member (13 corresponding lines) src/DependencyUpdater.php:71
- Off the main sequence: symplify/autowire-array-parameter
- Off the main sequence: symplify/package-builder
- ComposerJsonFactory.createFromArray (cyclomatic 28) packages/ComposerJsonManipulator/ComposerJsonFactory.php:59
- ComposerJsonFactory.createFromArray (cognitive 27) packages/ComposerJsonManipulator/ComposerJsonFactory.php:59
- ParameterMergingPhpFileLoader.executeCallback (cognitive 22) src-deps/package-builder/src/DependencyInjection/FileLoader/ParameterMergingPhpFileLoader.php:136
- REDACTED
- TooManyMethods: ComposerJson packages/ComposerJsonManipulator/ValueObject/ComposerJson.php:17
- REDACTED
- REDACTED
- Edited copy of a member (31 corresponding lines) packages/Testing/ComposerJsonRepositoriesUpdater.php:31
- Edited copy of a member (18 corresponding lines) packages/Merge/ComposerJsonDecorator/RemoverComposerJsonDecorator.php:68
- Edited copy of a member (17 corresponding lines) src-deps/package-builder/src/Yaml/ParametersMerger.php:17
- Edited copy of a member (8 corresponding lines) src/DependencyUpdater.php:30
- Edited copy of a member (7 corresponding lines) packages/Release/ReleaseWorker/SetCurrentMutualDependenciesReleaseWorker.php:26
- Duplicated block (12–14 lines × 2) packages/Testing/ComposerJsonRepositoriesUpdater.php:58
- Duplicated block (9 lines × 2) packages/Merge/PathResolver/AutoloadPathNormalizer.php:41
- No structured logging
- Swallowed exception (caught, then discarded) src-deps/autowire-array-parameter/src/DependencyInjection/DefinitionFinder.php:70
Minor — 47 finding(s)
- Orphaned file packages/ComposerJsonManipulator/ComposerJsonFactory.php:1
- Orphaned file src-deps/autowire-array-parameter/src/DependencyInjection/CompilerPass/AutowireArrayParameterCompilerPass.php:1
- Orphaned file src-deps/package-builder/src/Testing/AbstractKernelTestCase.php:1
- Orphaned file packages/Testing/ComposerJson/ComposerJsonSymlinker.php:1
- Orphaned file src-deps/smart-file-system/src/SmartFileInfo.php:1
- Orphaned file src-deps/easy-testing/src/StaticFixtureSplitter.php:1
- Orphaned file packages/Release/Guard/ReleaseGuard.php:1
- Orphaned file src-deps/easy-testing/src/DataProvider/StaticFixtureFinder.php:1
- Orphaned file packages/Release/Command/ReleaseCommand.php:1
- Orphaned file packages/Merge/ComposerJsonDecorator/RemoverComposerJsonDecorator.php:1
- Orphaned file src/VersionValidator.php:1
- Orphaned file packages-tests/Merge/ComposerJsonDecorator/RemoverComposerJsonDecorator/RemoverComposerJsonDecorator.php:1
- Orphaned file src-deps/easy-testing/src/PHPUnit/Behavior/DirectoryAssertableTrait.php:1
- Orphaned file src/DependencyUpdater.php:1
- Orphaned file src-deps/symplify-kernel/src/ValueObject/KernelBootAndApplicationRun.php:1
- Orphaned file config/config.php:1
- Orphaned file packages-tests/Merge/ComposerJsonDecorator/AbstractComposerJsonDecorator.php:1
- Orphaned file packages/ComposerJsonManipulator/FileSystem/JsonFileManager.php:1
- Orphaned file packages-tests/Merge/ComposerJsonDecorator/RepositoryPathComposerJsonDecorator/RepositoryPathComposerJsonDecorator.php:1
- Orphaned file src-deps/package-builder/src/Console/Formatter/ColorConsoleDiffFormatter.php:1
- Orphaned file src-deps/autowire-array-parameter/src/Skipper/ParameterSkipper.php:1
- Orphaned file src/Finder/PackageComposerFinder.php:1
- Orphaned file src/FileSystem/ComposerJsonProvider.php:1
- Orphaned file packages/Merge/PathResolver/AutoloadPathNormalizer.php:1
- Orphaned file packages/Testing/ComposerJsonRepositoriesUpdater.php:1
- Off-boarding risk: anonymized user #1
- No ADRs found composer.json:5
- Dormant codebase
- Most significant orphaned file packages/ComposerJsonManipulator/ValueObject/ComposerJson.php:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No changelog
- Duplicated predicate src-deps/easy-testing/src/PHPUnit/StaticPHPUnitEnvironment.php:17
Minor — 5 finding(s)
- Skipped (documented): test packages-tests/Merge/Application/MergedAndDecoratedComposerJsonFactory.php:24
- Skipped (documented): testIdenticalNamespaces packages-tests/Merge/Package/CombineStringsToArrayJsonMerger/CombineStringsToArrayJsonMergerTest.php:11
- Skipped (documented): test packages-tests/Merge/Package/PackageComposerJsonMergerTest.php:9
- Skipped (documented): test packages-tests/Merge/PathResolver/AutoloadPathNormalizer.php:22
- Skipped (documented): test packages-tests/Merge/PathResolver/ComposerPatchesPathNormalizer.php:12
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-6ad20a1b379442298cb5abedb0cce73c/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-6ad20a1b379442298cb5abedb0cce73c/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=3200" --report-format json --report-path /tmp/watchdog-gitleaks-6ad20a1b379442298cb5abedb0cce73c/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=4200 --max-count=2062" --report-format json --report-path /tmp/watchdog-gitleaks-6ad20a1b379442298cb5abedb0cce73c/history-3.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-3.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-6ad20a1b379442298cb5abedb0cce73c/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 . | 26 | 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 71 file(s) — `packages/ComposerJsonManipulator/ComposerJsonFactory.php`, `packages/ComposerJsonManipulator/FileSystem/JsonFileManager.php`, `packages/ComposerJsonManipulator/Json/JsonInliner.php`, `packages/ComposerJsonManipulator/Printer/ComposerJsonPrinter.php`, `packages/ComposerJsonManipulator/ValueObject/ComposerJson.php`, … (+66 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | 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 | — |