Executive summary
Ocramius/ProxyManager falls short of our standard for production because 24 files are no longer known to anyone active in the project and we found no recorded design decisions and no architecture document or diagram. It scores 63.6 out of 100 and is rated Adequate, and all 42 of its critical findings are security problems in the build pipeline and in the packages it uses.
Maturity, at 48.8, is the weakest lens and counts most in the score. The best first step is having someone learn and document the 24 files no active contributor knows, worth about 13.1 points. Recording design decisions comes next, worth about 10.2 points. Raising Maturity to 70 would lift the score to about 72.6.
Twenty-three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Sixteen secrets can leak from the build pipeline, and three known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version, limiting each secret to its own step and updating the vulnerable packages would close these risks.
The product code is 6,379 lines, about €25,000 to rebuild.
If Maturity rose from 48.8 to 70, the lowest score rated Strong, the score would rise from 63.6 to about 72.6.
New since the last survey: 10 findings
- Code Duplication · Edited copy of a member (43 corresponding lines) src/ProxyManager/ProxyGenerator/AccessInterceptorValueHolderGenerator.php
- Code Duplication · Edited copy of a member (31 corresponding lines) src/ProxyManager/ProxyGenerator/AccessInterceptorScopeLocalizer/MethodGenerator/StaticProxyConstructor.php
- Code Duplication · Edited copies of one member (3 members, 26+ corresponding lines) src/ProxyManager/ProxyGenerator/LazyLoadingValueHolder/MethodGenerator/MagicIsset.php
- Code Duplication · Edited copies of one member (4 members, 28+ corresponding lines) src/ProxyManager/ProxyGenerator/AccessInterceptorValueHolder/MethodGenerator/MagicGet.php
- Code Duplication · Edited copy of a member (19 corresponding lines) src/ProxyManager/ProxyGenerator/LazyLoadingGhost/MethodGenerator/CallInitializer.php
- Code Duplication · Edited copies of one member (4 members, 24+ corresponding lines) src/ProxyManager/ProxyGenerator/LazyLoadingGhost/MethodGenerator/MagicGet.php
- Code Duplication · Edited copy of a member (17 corresponding lines) src/ProxyManager/ProxyGenerator/AccessInterceptorScopeLocalizer/MethodGenerator/InterceptedMethod.php
- Code Duplication · Edited copies of one member (4 members, 24+ corresponding lines) src/ProxyManager/ProxyGenerator/AccessInterceptorScopeLocalizer/MethodGenerator/MagicGet.php
- Code Duplication · Edited copy of a member (11 corresponding lines) src/ProxyManager/ProxyGenerator/LazyLoadingValueHolder/MethodGenerator/MagicClone.php
- Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) src/ProxyManager/ProxyGenerator/AccessInterceptorScopeLocalizerGenerator.php
Fixed since the last survey: 2 findings
- Code Duplication · Duplicated block (5 lines × 2) src/ProxyManager/ProxyGenerator/AccessInterceptor/PropertyGenerator/MethodPrefixInterceptors.php
- Code Duplication · Duplicated block (10 lines × 2) src/ProxyManager/ProxyGenerator/LazyLoadingGhost/PropertyGenerator/PrivatePropertiesMap.php
Rebuild cost: about €25,000 · Estimate
| Cost to rebuild | €8,300 to €42,000, for 138 to 438 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 64. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 6,379 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 Factory.RemoteObject | 2 FileLocator | 3 Generator | 4 Generator.Util | 5 Inflector.Util | 6 Proxy | 7 Proxy.Exception | 8 ProxyGenerator.AccessInterceptor.PropertyGenerator | 9 ProxyGenerator.Assertion | 10 ProxyGenerator.LazyLoadingValueHolder.PropertyGenerator | 11 ProxyGenerator.RemoteObject.PropertyGenerator | 12 ProxyGenerator.Util | 13 Signature.Exception | 14 Stub | 15 Exception | 16 Factory.RemoteObject.Adapter | 17 GeneratorStrategy | 18 Inflector | 19 ProxyGenerator | 20 ProxyGenerator.AccessInterceptor.MethodGenerator | 21 ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator | 22 ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator.Util | 23 ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator.Util | 24 ProxyGenerator.LazyLoading.MethodGenerator | 25 ProxyGenerator.LazyLoadingGhost.PropertyGenerator | 26 ProxyGenerator.NullObject.MethodGenerator | 27 ProxyGenerator.PropertyGenerator | 28 ProxyGenerator.RemoteObject.MethodGenerator | 29 ProxyGenerator.ValueHolder.MethodGenerator | 30 Signature | 31 Autoloader | 32 ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator | 33 ProxyGenerator.LazyLoadingGhost.MethodGenerator | 34 ProxyGenerator.LazyLoadingValueHolder.MethodGenerator | 35 ProxyManager | 36 Factory |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Factory.RemoteObject | ||||||||||||||||||||||||||||||||||||
| 2 FileLocator | ||||||||||||||||||||||||||||||||||||
| 3 Generator | ||||||||||||||||||||||||||||||||||||
| 4 Generator.Util | ||||||||||||||||||||||||||||||||||||
| 5 Inflector.Util | ||||||||||||||||||||||||||||||||||||
| 6 Proxy | ||||||||||||||||||||||||||||||||||||
| 7 Proxy.Exception | ||||||||||||||||||||||||||||||||||||
| 8 ProxyGenerator.AccessInterceptor.PropertyGenerator | ||||||||||||||||||||||||||||||||||||
| 9 ProxyGenerator.Assertion | ||||||||||||||||||||||||||||||||||||
| 10 ProxyGenerator.LazyLoadingValueHolder.PropertyGenerator | ||||||||||||||||||||||||||||||||||||
| 11 ProxyGenerator.RemoteObject.PropertyGenerator | ||||||||||||||||||||||||||||||||||||
| 12 ProxyGenerator.Util | ||||||||||||||||||||||||||||||||||||
| 13 Signature.Exception | ||||||||||||||||||||||||||||||||||||
| 14 Stub | ||||||||||||||||||||||||||||||||||||
| 15 Exception | 1 | |||||||||||||||||||||||||||||||||||
| 16 Factory.RemoteObject.Adapter | 1 | |||||||||||||||||||||||||||||||||||
| 17 GeneratorStrategy | 1 | |||||||||||||||||||||||||||||||||||
| 18 Inflector | 1 | |||||||||||||||||||||||||||||||||||
| 19 ProxyGenerator | 4 | 3 | ||||||||||||||||||||||||||||||||||
| 20 ProxyGenerator.AccessInterceptor.MethodGenerator | 3 | |||||||||||||||||||||||||||||||||||
| 21 ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator | 9 | |||||||||||||||||||||||||||||||||||
| 22 ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator.Util | 1 | |||||||||||||||||||||||||||||||||||
| 23 ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator.Util | 1 | |||||||||||||||||||||||||||||||||||
| 24 ProxyGenerator.LazyLoading.MethodGenerator | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 25 ProxyGenerator.LazyLoadingGhost.PropertyGenerator | 2 | |||||||||||||||||||||||||||||||||||
| 26 ProxyGenerator.NullObject.MethodGenerator | 2 | |||||||||||||||||||||||||||||||||||
| 27 ProxyGenerator.PropertyGenerator | 1 | |||||||||||||||||||||||||||||||||||
| 28 ProxyGenerator.RemoteObject.MethodGenerator | 6 | |||||||||||||||||||||||||||||||||||
| 29 ProxyGenerator.ValueHolder.MethodGenerator | 3 | |||||||||||||||||||||||||||||||||||
| 30 Signature | 2 | |||||||||||||||||||||||||||||||||||
| 31 Autoloader | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 32 ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator | 7 | 4 | ||||||||||||||||||||||||||||||||||
| 33 ProxyGenerator.LazyLoadingGhost.MethodGenerator | 11 | 1 | 9 | 4 | ||||||||||||||||||||||||||||||||
| 34 ProxyGenerator.LazyLoadingValueHolder.MethodGenerator | 11 | 4 | ||||||||||||||||||||||||||||||||||
| 35 ProxyManager | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||
| 36 Factory | 1 | 6 | 13 | 7 |
15→12 Exception uses ProxyGenerator.Util✕
- Connections
- 1 pair of types, where a type in Exception uses a type in ProxyGenerator.Util.
- The types involved
ProxyManager.Exception.UnsupportedProxiedClassException→ProxyManager.ProxyGenerator.Util.Properties
- Direction
- Exception uses ProxyGenerator.Util, so a change to ProxyGenerator.Util can break Exception, while a change to Exception can't break ProxyGenerator.Util.
- Position
- Below the diagonal: Exception uses a module listed above it, which is the healthy direction.
16→1 Factory.RemoteObject.Adapter uses Factory.RemoteObject✕
- Connections
- 1 pair of types, where a type in Factory.RemoteObject.Adapter uses a type in Factory.RemoteObject.
- The types involved
ProxyManager.Factory.RemoteObject.Adapter.BaseAdapter→ProxyManager.Factory.RemoteObject.AdapterInterface
- Direction
- Factory.RemoteObject.Adapter uses Factory.RemoteObject, so a change to Factory.RemoteObject can break Factory.RemoteObject.Adapter, while a change to Factory.RemoteObject.Adapter can't break Factory.RemoteObject.
- Position
- Below the diagonal: Factory.RemoteObject.Adapter uses a module listed above it, which is the healthy direction.
17→2 GeneratorStrategy uses FileLocator✕
- Connections
- 1 pair of types, where a type in GeneratorStrategy uses a type in FileLocator.
- The types involved
ProxyManager.GeneratorStrategy.FileWriterGeneratorStrategy→ProxyManager.FileLocator.FileLocatorInterface
- Direction
- GeneratorStrategy uses FileLocator, so a change to FileLocator can break GeneratorStrategy, while a change to GeneratorStrategy can't break FileLocator.
- Position
- Below the diagonal: GeneratorStrategy uses a module listed above it, which is the healthy direction.
18→5 Inflector uses Inflector.Util✕
- Connections
- 1 pair of types, where a type in Inflector uses a type in Inflector.Util.
- The types involved
ProxyManager.Inflector.ClassNameInflector→ProxyManager.Inflector.Util.ParameterHasher
- Direction
- Inflector uses Inflector.Util, so a change to Inflector.Util can break Inflector, while a change to Inflector can't break Inflector.Util.
- Position
- Below the diagonal: Inflector uses a module listed above it, which is the healthy direction.
19→8 ProxyGenerator uses ProxyGenerator.AccessInterceptor.PropertyGenerator✕
- Connections
- 4 pairs of types, where a type in ProxyGenerator uses a type in ProxyGenerator.AccessInterceptor.PropertyGenerator.
- The types involved
ProxyManager.ProxyGenerator.AccessInterceptorScopeLocalizerGenerator→ProxyManager.ProxyGenerator.AccessInterceptor.PropertyGenerator.MethodPrefixInterceptorsProxyManager.ProxyGenerator.AccessInterceptorScopeLocalizerGenerator→ProxyManager.ProxyGenerator.AccessInterceptor.PropertyGenerator.MethodSuffixInterceptorsProxyManager.ProxyGenerator.AccessInterceptorValueHolderGenerator→ProxyManager.ProxyGenerator.AccessInterceptor.PropertyGenerator.MethodPrefixInterceptorsProxyManager.ProxyGenerator.AccessInterceptorValueHolderGenerator→ProxyManager.ProxyGenerator.AccessInterceptor.PropertyGenerator.MethodSuffixInterceptors
- Direction
- ProxyGenerator uses ProxyGenerator.AccessInterceptor.PropertyGenerator, so a change to ProxyGenerator.AccessInterceptor.PropertyGenerator can break ProxyGenerator, while a change to ProxyGenerator can't break ProxyGenerator.AccessInterceptor.PropertyGenerator.
- Position
- Below the diagonal: ProxyGenerator uses a module listed above it, which is the healthy direction.
19→10 ProxyGenerator uses ProxyGenerator.LazyLoadingValueHolder.PropertyGenerator✕
- Connections
- 3 pairs of types, where a type in ProxyGenerator uses a type in ProxyGenerator.LazyLoadingValueHolder.PropertyGenerator.
- The types involved
ProxyManager.ProxyGenerator.AccessInterceptorValueHolderGenerator→ProxyManager.ProxyGenerator.LazyLoadingValueHolder.PropertyGenerator.ValueHolderPropertyProxyManager.ProxyGenerator.LazyLoadingValueHolderGenerator→ProxyManager.ProxyGenerator.LazyLoadingValueHolder.PropertyGenerator.InitializerPropertyProxyManager.ProxyGenerator.LazyLoadingValueHolderGenerator→ProxyManager.ProxyGenerator.LazyLoadingValueHolder.PropertyGenerator.ValueHolderProperty
- Direction
- ProxyGenerator uses ProxyGenerator.LazyLoadingValueHolder.PropertyGenerator, so a change to ProxyGenerator.LazyLoadingValueHolder.PropertyGenerator can break ProxyGenerator, while a change to ProxyGenerator can't break ProxyGenerator.LazyLoadingValueHolder.PropertyGenerator.
- Position
- Below the diagonal: ProxyGenerator uses a module listed above it, which is the healthy direction.
20→3 ProxyGenerator.AccessInterceptor.MethodGenerator uses Generator✕
- Connections
- 3 pairs of types, where a type in ProxyGenerator.AccessInterceptor.MethodGenerator uses a type in Generator.
- The types involved
ProxyManager.ProxyGenerator.AccessInterceptor.MethodGenerator.MagicWakeup→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.AccessInterceptor.MethodGenerator.SetMethodPrefixInterceptor→ProxyManager.Generator.MethodGeneratorProxyManager.ProxyGenerator.AccessInterceptor.MethodGenerator.SetMethodSuffixInterceptor→ProxyManager.Generator.MethodGenerator
- Direction
- ProxyGenerator.AccessInterceptor.MethodGenerator uses Generator, so a change to Generator can break ProxyGenerator.AccessInterceptor.MethodGenerator, while a change to ProxyGenerator.AccessInterceptor.MethodGenerator can't break Generator.
- Position
- Below the diagonal: ProxyGenerator.AccessInterceptor.MethodGenerator uses a module listed above it, which is the healthy direction.
21→3 ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator uses Generator✕
- Connections
- 9 pairs of types, where a type in ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator uses a type in Generator.
- The types involved
ProxyManager.ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator.BindProxyProperties→ProxyManager.Generator.MethodGeneratorProxyManager.ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator.InterceptedMethod→ProxyManager.Generator.MethodGeneratorProxyManager.ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator.MagicClone→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator.MagicGet→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator.MagicIsset→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator.MagicSet→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator.MagicSleep→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator.MagicUnset→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator.StaticProxyConstructor→ProxyManager.Generator.MethodGenerator
- Direction
- ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator uses Generator, so a change to Generator can break ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator, while a change to ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator can't break Generator.
- Position
- Below the diagonal: ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator uses a module listed above it, which is the healthy direction.
22→3 ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator.Util uses Generator✕
- Connections
- 1 pair of types, where a type in ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator.Util uses a type in Generator.
- The types involved
ProxyManager.ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator.Util.InterceptorGenerator→ProxyManager.Generator.MethodGenerator
- Direction
- ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator.Util uses Generator, so a change to Generator can break ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator.Util, while a change to ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator.Util can't break Generator.
- Position
- Below the diagonal: ProxyGenerator.AccessInterceptorScopeLocalizer.MethodGenerator.Util uses a module listed above it, which is the healthy direction.
23→3 ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator.Util uses Generator✕
- Connections
- 1 pair of types, where a type in ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator.Util uses a type in Generator.
- The types involved
ProxyManager.ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator.Util.InterceptorGenerator→ProxyManager.Generator.MethodGenerator
- Direction
- ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator.Util uses Generator, so a change to Generator can break ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator.Util, while a change to ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator.Util can't break Generator.
- Position
- Below the diagonal: ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator.Util uses a module listed above it, which is the healthy direction.
24→3 ProxyGenerator.LazyLoading.MethodGenerator uses Generator✕
- Connections
- 1 pair of types, where a type in ProxyGenerator.LazyLoading.MethodGenerator uses a type in Generator.
- The types involved
ProxyManager.ProxyGenerator.LazyLoading.MethodGenerator.StaticProxyConstructor→ProxyManager.Generator.MethodGenerator
- Direction
- ProxyGenerator.LazyLoading.MethodGenerator uses Generator, so a change to Generator can break ProxyGenerator.LazyLoading.MethodGenerator, while a change to ProxyGenerator.LazyLoading.MethodGenerator can't break Generator.
- Position
- Below the diagonal: ProxyGenerator.LazyLoading.MethodGenerator uses a module listed above it, which is the healthy direction.
24→12 ProxyGenerator.LazyLoading.MethodGenerator uses ProxyGenerator.Util✕
- Connections
- 1 pair of types, where a type in ProxyGenerator.LazyLoading.MethodGenerator uses a type in ProxyGenerator.Util.
- The types involved
ProxyManager.ProxyGenerator.LazyLoading.MethodGenerator.StaticProxyConstructor→ProxyManager.ProxyGenerator.Util.Properties
- Direction
- ProxyGenerator.LazyLoading.MethodGenerator uses ProxyGenerator.Util, so a change to ProxyGenerator.Util can break ProxyGenerator.LazyLoading.MethodGenerator, while a change to ProxyGenerator.LazyLoading.MethodGenerator can't break ProxyGenerator.Util.
- Position
- Below the diagonal: ProxyGenerator.LazyLoading.MethodGenerator uses a module listed above it, which is the healthy direction.
25→12 ProxyGenerator.LazyLoadingGhost.PropertyGenerator uses ProxyGenerator.Util✕
- Connections
- 2 pairs of types, where a type in ProxyGenerator.LazyLoadingGhost.PropertyGenerator uses a type in ProxyGenerator.Util.
- The types involved
ProxyManager.ProxyGenerator.LazyLoadingGhost.PropertyGenerator.PrivatePropertiesMap→ProxyManager.ProxyGenerator.Util.PropertiesProxyManager.ProxyGenerator.LazyLoadingGhost.PropertyGenerator.ProtectedPropertiesMap→ProxyManager.ProxyGenerator.Util.Properties
- Direction
- ProxyGenerator.LazyLoadingGhost.PropertyGenerator uses ProxyGenerator.Util, so a change to ProxyGenerator.Util can break ProxyGenerator.LazyLoadingGhost.PropertyGenerator, while a change to ProxyGenerator.LazyLoadingGhost.PropertyGenerator can't break ProxyGenerator.Util.
- Position
- Below the diagonal: ProxyGenerator.LazyLoadingGhost.PropertyGenerator uses a module listed above it, which is the healthy direction.
26→3 ProxyGenerator.NullObject.MethodGenerator uses Generator✕
- Connections
- 2 pairs of types, where a type in ProxyGenerator.NullObject.MethodGenerator uses a type in Generator.
- The types involved
ProxyManager.ProxyGenerator.NullObject.MethodGenerator.NullObjectMethodInterceptor→ProxyManager.Generator.MethodGeneratorProxyManager.ProxyGenerator.NullObject.MethodGenerator.StaticProxyConstructor→ProxyManager.Generator.MethodGenerator
- Direction
- ProxyGenerator.NullObject.MethodGenerator uses Generator, so a change to Generator can break ProxyGenerator.NullObject.MethodGenerator, while a change to ProxyGenerator.NullObject.MethodGenerator can't break Generator.
- Position
- Below the diagonal: ProxyGenerator.NullObject.MethodGenerator uses a module listed above it, which is the healthy direction.
27→12 ProxyGenerator.PropertyGenerator uses ProxyGenerator.Util✕
- Connections
- 1 pair of types, where a type in ProxyGenerator.PropertyGenerator uses a type in ProxyGenerator.Util.
- The types involved
ProxyManager.ProxyGenerator.PropertyGenerator.PublicPropertiesMap→ProxyManager.ProxyGenerator.Util.Properties
- Direction
- ProxyGenerator.PropertyGenerator uses ProxyGenerator.Util, so a change to ProxyGenerator.Util can break ProxyGenerator.PropertyGenerator, while a change to ProxyGenerator.PropertyGenerator can't break ProxyGenerator.Util.
- Position
- Below the diagonal: ProxyGenerator.PropertyGenerator uses a module listed above it, which is the healthy direction.
28→3 ProxyGenerator.RemoteObject.MethodGenerator uses Generator✕
- Connections
- 6 pairs of types, where a type in ProxyGenerator.RemoteObject.MethodGenerator uses a type in Generator.
- The types involved
ProxyManager.ProxyGenerator.RemoteObject.MethodGenerator.MagicGet→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.RemoteObject.MethodGenerator.MagicIsset→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.RemoteObject.MethodGenerator.MagicSet→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.RemoteObject.MethodGenerator.MagicUnset→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.RemoteObject.MethodGenerator.RemoteObjectMethod→ProxyManager.Generator.MethodGeneratorProxyManager.ProxyGenerator.RemoteObject.MethodGenerator.StaticProxyConstructor→ProxyManager.Generator.MethodGenerator
- Direction
- ProxyGenerator.RemoteObject.MethodGenerator uses Generator, so a change to Generator can break ProxyGenerator.RemoteObject.MethodGenerator, while a change to ProxyGenerator.RemoteObject.MethodGenerator can't break Generator.
- Position
- Below the diagonal: ProxyGenerator.RemoteObject.MethodGenerator uses a module listed above it, which is the healthy direction.
29→3 ProxyGenerator.ValueHolder.MethodGenerator uses Generator✕
- Connections
- 3 pairs of types, where a type in ProxyGenerator.ValueHolder.MethodGenerator uses a type in Generator.
- The types involved
ProxyManager.ProxyGenerator.ValueHolder.MethodGenerator.Constructor→ProxyManager.Generator.MethodGeneratorProxyManager.ProxyGenerator.ValueHolder.MethodGenerator.GetWrappedValueHolderValue→ProxyManager.Generator.MethodGeneratorProxyManager.ProxyGenerator.ValueHolder.MethodGenerator.MagicSleep→ProxyManager.Generator.MagicMethodGenerator
- Direction
- ProxyGenerator.ValueHolder.MethodGenerator uses Generator, so a change to Generator can break ProxyGenerator.ValueHolder.MethodGenerator, while a change to ProxyGenerator.ValueHolder.MethodGenerator can't break Generator.
- Position
- Below the diagonal: ProxyGenerator.ValueHolder.MethodGenerator uses a module listed above it, which is the healthy direction.
30→5 Signature uses Inflector.Util✕
- Connections
- 2 pairs of types, where a type in Signature uses a type in Inflector.Util.
- The types involved
ProxyManager.Signature.SignatureGenerator→ProxyManager.Inflector.Util.ParameterEncoderProxyManager.Signature.SignatureGenerator→ProxyManager.Inflector.Util.ParameterHasher
- Direction
- Signature uses Inflector.Util, so a change to Inflector.Util can break Signature, while a change to Signature can't break Inflector.Util.
- Position
- Below the diagonal: Signature uses a module listed above it, which is the healthy direction.
31→2 Autoloader uses FileLocator✕
- Connections
- 1 pair of types, where a type in Autoloader uses a type in FileLocator.
- The types involved
ProxyManager.Autoloader.Autoloader→ProxyManager.FileLocator.FileLocatorInterface
- Direction
- Autoloader uses FileLocator, so a change to FileLocator can break Autoloader, while a change to Autoloader can't break FileLocator.
- Position
- Below the diagonal: Autoloader uses a module listed above it, which is the healthy direction.
31→18 Autoloader uses Inflector✕
- Connections
- 1 pair of types, where a type in Autoloader uses a type in Inflector.
- The types involved
ProxyManager.Autoloader.Autoloader→ProxyManager.Inflector.ClassNameInflectorInterface
- Direction
- Autoloader uses Inflector, so a change to Inflector can break Autoloader, while a change to Autoloader can't break Inflector.
- Position
- Below the diagonal: Autoloader uses a module listed above it, which is the healthy direction.
32→3 ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator uses Generator✕
- Connections
- 7 pairs of types, where a type in ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator uses a type in Generator.
- The types involved
ProxyManager.ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator.InterceptedMethod→ProxyManager.Generator.MethodGeneratorProxyManager.ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator.MagicClone→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator.MagicGet→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator.MagicIsset→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator.MagicSet→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator.MagicUnset→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator.StaticProxyConstructor→ProxyManager.Generator.MethodGenerator
- Direction
- ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator uses Generator, so a change to Generator can break ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator, while a change to ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator can't break Generator.
- Position
- Below the diagonal: ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator uses a module listed above it, which is the healthy direction.
32→27 ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator uses ProxyGenerator.PropertyGenerator✕
- Connections
- 4 pairs of types, where a type in ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator uses a type in ProxyGenerator.PropertyGenerator.
- The types involved
ProxyManager.ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator.MagicGet→ProxyManager.ProxyGenerator.PropertyGenerator.PublicPropertiesMapProxyManager.ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator.MagicIsset→ProxyManager.ProxyGenerator.PropertyGenerator.PublicPropertiesMapProxyManager.ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator.MagicSet→ProxyManager.ProxyGenerator.PropertyGenerator.PublicPropertiesMapProxyManager.ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator.MagicUnset→ProxyManager.ProxyGenerator.PropertyGenerator.PublicPropertiesMap
- Direction
- ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator uses ProxyGenerator.PropertyGenerator, so a change to ProxyGenerator.PropertyGenerator can break ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator, while a change to ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator can't break ProxyGenerator.PropertyGenerator.
- Position
- Below the diagonal: ProxyGenerator.AccessInterceptorValueHolder.MethodGenerator uses a module listed above it, which is the healthy direction.
33→3 ProxyGenerator.LazyLoadingGhost.MethodGenerator uses Generator✕
- Connections
- 11 pairs of types, where a type in ProxyGenerator.LazyLoadingGhost.MethodGenerator uses a type in Generator.
- The types involved
ProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.CallInitializer→ProxyManager.Generator.MethodGeneratorProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.GetProxyInitializer→ProxyManager.Generator.MethodGeneratorProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.InitializeProxy→ProxyManager.Generator.MethodGeneratorProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.IsProxyInitialized→ProxyManager.Generator.MethodGeneratorProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.MagicClone→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.MagicGet→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.MagicIsset→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.MagicSet→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.MagicSleep→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.MagicUnset→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.SetProxyInitializer→ProxyManager.Generator.MethodGenerator
- Direction
- ProxyGenerator.LazyLoadingGhost.MethodGenerator uses Generator, so a change to Generator can break ProxyGenerator.LazyLoadingGhost.MethodGenerator, while a change to ProxyGenerator.LazyLoadingGhost.MethodGenerator can't break Generator.
- Position
- Below the diagonal: ProxyGenerator.LazyLoadingGhost.MethodGenerator uses a module listed above it, which is the healthy direction.
33→12 ProxyGenerator.LazyLoadingGhost.MethodGenerator uses ProxyGenerator.Util✕
- Connections
- 1 pair of types, where a type in ProxyGenerator.LazyLoadingGhost.MethodGenerator uses a type in ProxyGenerator.Util.
- The types involved
ProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.CallInitializer→ProxyManager.ProxyGenerator.Util.Properties
- Direction
- ProxyGenerator.LazyLoadingGhost.MethodGenerator uses ProxyGenerator.Util, so a change to ProxyGenerator.Util can break ProxyGenerator.LazyLoadingGhost.MethodGenerator, while a change to ProxyGenerator.LazyLoadingGhost.MethodGenerator can't break ProxyGenerator.Util.
- Position
- Below the diagonal: ProxyGenerator.LazyLoadingGhost.MethodGenerator uses a module listed above it, which is the healthy direction.
33→25 ProxyGenerator.LazyLoadingGhost.MethodGenerator uses ProxyGenerator.LazyLoadingGhost.PropertyGenerator✕
- Connections
- 9 pairs of types, where a type in ProxyGenerator.LazyLoadingGhost.MethodGenerator uses a type in ProxyGenerator.LazyLoadingGhost.PropertyGenerator.
- The types involved
ProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.MagicGet→ProxyManager.ProxyGenerator.LazyLoadingGhost.PropertyGenerator.InitializationTrackerProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.MagicGet→ProxyManager.ProxyGenerator.LazyLoadingGhost.PropertyGenerator.PrivatePropertiesMapProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.MagicGet→ProxyManager.ProxyGenerator.LazyLoadingGhost.PropertyGenerator.ProtectedPropertiesMapProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.MagicIsset→ProxyManager.ProxyGenerator.LazyLoadingGhost.PropertyGenerator.PrivatePropertiesMapProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.MagicIsset→ProxyManager.ProxyGenerator.LazyLoadingGhost.PropertyGenerator.ProtectedPropertiesMapProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.MagicSet→ProxyManager.ProxyGenerator.LazyLoadingGhost.PropertyGenerator.PrivatePropertiesMapProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.MagicSet→ProxyManager.ProxyGenerator.LazyLoadingGhost.PropertyGenerator.ProtectedPropertiesMapProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.MagicUnset→ProxyManager.ProxyGenerator.LazyLoadingGhost.PropertyGenerator.PrivatePropertiesMapProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.MagicUnset→ProxyManager.ProxyGenerator.LazyLoadingGhost.PropertyGenerator.ProtectedPropertiesMap
- Direction
- ProxyGenerator.LazyLoadingGhost.MethodGenerator uses ProxyGenerator.LazyLoadingGhost.PropertyGenerator, so a change to ProxyGenerator.LazyLoadingGhost.PropertyGenerator can break ProxyGenerator.LazyLoadingGhost.MethodGenerator, while a change to ProxyGenerator.LazyLoadingGhost.MethodGenerator can't break ProxyGenerator.LazyLoadingGhost.PropertyGenerator.
- Position
- Below the diagonal: ProxyGenerator.LazyLoadingGhost.MethodGenerator uses a module listed above it, which is the healthy direction.
33→27 ProxyGenerator.LazyLoadingGhost.MethodGenerator uses ProxyGenerator.PropertyGenerator✕
- Connections
- 4 pairs of types, where a type in ProxyGenerator.LazyLoadingGhost.MethodGenerator uses a type in ProxyGenerator.PropertyGenerator.
- The types involved
ProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.MagicGet→ProxyManager.ProxyGenerator.PropertyGenerator.PublicPropertiesMapProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.MagicIsset→ProxyManager.ProxyGenerator.PropertyGenerator.PublicPropertiesMapProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.MagicSet→ProxyManager.ProxyGenerator.PropertyGenerator.PublicPropertiesMapProxyManager.ProxyGenerator.LazyLoadingGhost.MethodGenerator.MagicUnset→ProxyManager.ProxyGenerator.PropertyGenerator.PublicPropertiesMap
- Direction
- ProxyGenerator.LazyLoadingGhost.MethodGenerator uses ProxyGenerator.PropertyGenerator, so a change to ProxyGenerator.PropertyGenerator can break ProxyGenerator.LazyLoadingGhost.MethodGenerator, while a change to ProxyGenerator.LazyLoadingGhost.MethodGenerator can't break ProxyGenerator.PropertyGenerator.
- Position
- Below the diagonal: ProxyGenerator.LazyLoadingGhost.MethodGenerator uses a module listed above it, which is the healthy direction.
34→3 ProxyGenerator.LazyLoadingValueHolder.MethodGenerator uses Generator✕
- Connections
- 11 pairs of types, where a type in ProxyGenerator.LazyLoadingValueHolder.MethodGenerator uses a type in Generator.
- The types involved
ProxyManager.ProxyGenerator.LazyLoadingValueHolder.MethodGenerator.GetProxyInitializer→ProxyManager.Generator.MethodGeneratorProxyManager.ProxyGenerator.LazyLoadingValueHolder.MethodGenerator.InitializeProxy→ProxyManager.Generator.MethodGeneratorProxyManager.ProxyGenerator.LazyLoadingValueHolder.MethodGenerator.IsProxyInitialized→ProxyManager.Generator.MethodGeneratorProxyManager.ProxyGenerator.LazyLoadingValueHolder.MethodGenerator.LazyLoadingMethodInterceptor→ProxyManager.Generator.MethodGeneratorProxyManager.ProxyGenerator.LazyLoadingValueHolder.MethodGenerator.MagicClone→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.LazyLoadingValueHolder.MethodGenerator.MagicGet→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.LazyLoadingValueHolder.MethodGenerator.MagicIsset→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.LazyLoadingValueHolder.MethodGenerator.MagicSet→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.LazyLoadingValueHolder.MethodGenerator.MagicSleep→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.LazyLoadingValueHolder.MethodGenerator.MagicUnset→ProxyManager.Generator.MagicMethodGeneratorProxyManager.ProxyGenerator.LazyLoadingValueHolder.MethodGenerator.SetProxyInitializer→ProxyManager.Generator.MethodGenerator
- Direction
- ProxyGenerator.LazyLoadingValueHolder.MethodGenerator uses Generator, so a change to Generator can break ProxyGenerator.LazyLoadingValueHolder.MethodGenerator, while a change to ProxyGenerator.LazyLoadingValueHolder.MethodGenerator can't break Generator.
- Position
- Below the diagonal: ProxyGenerator.LazyLoadingValueHolder.MethodGenerator uses a module listed above it, which is the healthy direction.
34→27 ProxyGenerator.LazyLoadingValueHolder.MethodGenerator uses ProxyGenerator.PropertyGenerator✕
- Connections
- 4 pairs of types, where a type in ProxyGenerator.LazyLoadingValueHolder.MethodGenerator uses a type in ProxyGenerator.PropertyGenerator.
- The types involved
ProxyManager.ProxyGenerator.LazyLoadingValueHolder.MethodGenerator.MagicGet→ProxyManager.ProxyGenerator.PropertyGenerator.PublicPropertiesMapProxyManager.ProxyGenerator.LazyLoadingValueHolder.MethodGenerator.MagicIsset→ProxyManager.ProxyGenerator.PropertyGenerator.PublicPropertiesMapProxyManager.ProxyGenerator.LazyLoadingValueHolder.MethodGenerator.MagicSet→ProxyManager.ProxyGenerator.PropertyGenerator.PublicPropertiesMapProxyManager.ProxyGenerator.LazyLoadingValueHolder.MethodGenerator.MagicUnset→ProxyManager.ProxyGenerator.PropertyGenerator.PublicPropertiesMap
- Direction
- ProxyGenerator.LazyLoadingValueHolder.MethodGenerator uses ProxyGenerator.PropertyGenerator, so a change to ProxyGenerator.PropertyGenerator can break ProxyGenerator.LazyLoadingValueHolder.MethodGenerator, while a change to ProxyGenerator.LazyLoadingValueHolder.MethodGenerator can't break ProxyGenerator.PropertyGenerator.
- Position
- Below the diagonal: ProxyGenerator.LazyLoadingValueHolder.MethodGenerator uses a module listed above it, which is the healthy direction.
35→17 ProxyManager uses GeneratorStrategy✕
- Connections
- 1 pair of types, where a type in ProxyManager uses a type in GeneratorStrategy.
- The types involved
ProxyManager.Configuration→ProxyManager.GeneratorStrategy.GeneratorStrategyInterface
- Direction
- ProxyManager uses GeneratorStrategy, so a change to GeneratorStrategy can break ProxyManager, while a change to ProxyManager can't break GeneratorStrategy.
- Position
- Below the diagonal: ProxyManager uses a module listed above it, which is the healthy direction.
35→18 ProxyManager uses Inflector✕
- Connections
- 1 pair of types, where a type in ProxyManager uses a type in Inflector.
- The types involved
ProxyManager.Configuration→ProxyManager.Inflector.ClassNameInflectorInterface
- Direction
- ProxyManager uses Inflector, so a change to Inflector can break ProxyManager, while a change to ProxyManager can't break Inflector.
- Position
- Below the diagonal: ProxyManager uses a module listed above it, which is the healthy direction.
35→30 ProxyManager uses Signature✕
- Connections
- 3 pairs of types, where a type in ProxyManager uses a type in Signature.
- The types involved
ProxyManager.Configuration→ProxyManager.Signature.ClassSignatureGeneratorInterfaceProxyManager.Configuration→ProxyManager.Signature.SignatureCheckerInterfaceProxyManager.Configuration→ProxyManager.Signature.SignatureGeneratorInterface
- Direction
- ProxyManager uses Signature, so a change to Signature can break ProxyManager, while a change to ProxyManager can't break Signature.
- Position
- Below the diagonal: ProxyManager uses a module listed above it, which is the healthy direction.
35→31 ProxyManager uses Autoloader✕
- Connections
- 1 pair of types, where a type in ProxyManager uses a type in Autoloader.
- The types involved
ProxyManager.Configuration→ProxyManager.Autoloader.AutoloaderInterface
- Direction
- ProxyManager uses Autoloader, so a change to Autoloader can break ProxyManager, while a change to ProxyManager can't break Autoloader.
- Position
- Below the diagonal: ProxyManager uses a module listed above it, which is the healthy direction.
36→1 Factory uses Factory.RemoteObject✕
- Connections
- 1 pair of types, where a type in Factory uses a type in Factory.RemoteObject.
- The types involved
ProxyManager.Factory.RemoteObjectFactory→ProxyManager.Factory.RemoteObject.AdapterInterface
- Direction
- Factory uses Factory.RemoteObject, so a change to Factory.RemoteObject can break Factory, while a change to Factory can't break Factory.RemoteObject.
- Position
- Below the diagonal: Factory uses a module listed above it, which is the healthy direction.
36→6 Factory uses Proxy✕
- Connections
- 6 pairs of types, where a type in Factory uses a type in Proxy.
- The types involved
ProxyManager.Factory.AccessInterceptorScopeLocalizerFactory→ProxyManager.Proxy.AccessInterceptorInterfaceProxyManager.Factory.AccessInterceptorValueHolderFactory→ProxyManager.Proxy.AccessInterceptorValueHolderInterfaceProxyManager.Factory.LazyLoadingGhostFactory→ProxyManager.Proxy.GhostObjectInterfaceProxyManager.Factory.LazyLoadingValueHolderFactory→ProxyManager.Proxy.VirtualProxyInterfaceProxyManager.Factory.NullObjectFactory→ProxyManager.Proxy.NullObjectInterfaceProxyManager.Factory.RemoteObjectFactory→ProxyManager.Proxy.RemoteObjectInterface
- Direction
- Factory uses Proxy, so a change to Proxy can break Factory, while a change to Factory can't break Proxy.
- Position
- Below the diagonal: Factory uses a module listed above it, which is the healthy direction.
36→19 Factory uses ProxyGenerator✕
- Connections
- 13 pairs of types, where a type in Factory uses a type in ProxyGenerator.
- The types involved
ProxyManager.Factory.AbstractBaseFactory→ProxyManager.ProxyGenerator.ProxyGeneratorInterfaceProxyManager.Factory.AccessInterceptorScopeLocalizerFactory→ProxyManager.ProxyGenerator.AccessInterceptorScopeLocalizerGeneratorProxyManager.Factory.AccessInterceptorScopeLocalizerFactory→ProxyManager.ProxyGenerator.ProxyGeneratorInterfaceProxyManager.Factory.AccessInterceptorValueHolderFactory→ProxyManager.ProxyGenerator.AccessInterceptorValueHolderGeneratorProxyManager.Factory.AccessInterceptorValueHolderFactory→ProxyManager.ProxyGenerator.ProxyGeneratorInterfaceProxyManager.Factory.LazyLoadingGhostFactory→ProxyManager.ProxyGenerator.LazyLoadingGhostGeneratorProxyManager.Factory.LazyLoadingGhostFactory→ProxyManager.ProxyGenerator.ProxyGeneratorInterfaceProxyManager.Factory.LazyLoadingValueHolderFactory→ProxyManager.ProxyGenerator.LazyLoadingValueHolderGeneratorProxyManager.Factory.LazyLoadingValueHolderFactory→ProxyManager.ProxyGenerator.ProxyGeneratorInterfaceProxyManager.Factory.NullObjectFactory→ProxyManager.ProxyGenerator.NullObjectGeneratorProxyManager.Factory.NullObjectFactory→ProxyManager.ProxyGenerator.ProxyGeneratorInterfaceProxyManager.Factory.RemoteObjectFactory→ProxyManager.ProxyGenerator.ProxyGeneratorInterfaceProxyManager.Factory.RemoteObjectFactory→ProxyManager.ProxyGenerator.RemoteObjectGenerator
- Direction
- Factory uses ProxyGenerator, so a change to ProxyGenerator can break Factory, while a change to Factory can't break ProxyGenerator.
- Position
- Below the diagonal: Factory uses a module listed above it, which is the healthy direction.
36→35 Factory uses ProxyManager✕
- Connections
- 7 pairs of types, where a type in Factory uses a type in ProxyManager.
- The types involved
ProxyManager.Factory.AbstractBaseFactory→ProxyManager.ConfigurationProxyManager.Factory.AccessInterceptorScopeLocalizerFactory→ProxyManager.ConfigurationProxyManager.Factory.AccessInterceptorValueHolderFactory→ProxyManager.ConfigurationProxyManager.Factory.LazyLoadingGhostFactory→ProxyManager.ConfigurationProxyManager.Factory.LazyLoadingValueHolderFactory→ProxyManager.ConfigurationProxyManager.Factory.NullObjectFactory→ProxyManager.ConfigurationProxyManager.Factory.RemoteObjectFactory→ProxyManager.Configuration
- Direction
- Factory uses ProxyManager, so a change to ProxyManager can break Factory, while a change to Factory can't break ProxyManager.
- Position
- Below the diagonal: Factory uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 41 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 13 | High / Critical |
Roadmap
Top priorities: Resolve the 24 Orphaned file finding(s) in Knowledge Freshness — start with InterceptorGenerator.php (2), PublicScopeSimulator.php, LazyLoadingGhostGenerator.php; 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; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 24 Orphaned file finding(s) in Knowledge Freshness — start with InterceptorGenerator.php (2), PublicScopeSimulator.php, LazyLoadingGhostGenerator.php. | +13.1 pts | Medium | Knowledge Freshness |
| 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. | +10.2 pts | Medium | Architecture documentation |
| Resolve the 7 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.9 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. | +2.8 pts | Medium | Documentation (README) |
| Resolve the 16 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (16). | +2.5 pts | Medium | Static Analysis (SAST) |
| Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. | +0.9 pts | Low | Knowledge Freshness |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +1.5 pts | Medium | Release Hygiene |
| Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). | +0.7 pts | Low | Dependency Vulnerabilities |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | 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.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 | 5.1 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| src/ProxyManager/ProxyGenerator/AccessInterceptorValueHolder/MethodGenerator/MagicGet.php | 6.3 | Mixed | Code Duplication: Edited copies of one member (4 members, 28+ corresponding lines) |
| src/ProxyManager/ProxyGenerator/AccessInterceptorValueHolderGenerator.php | 7.8 | Mixed | Code Duplication: Edited copy of a member (43 corresponding lines) |
| src/ProxyManager/ProxyGenerator/AccessInterceptorScopeLocalizer/MethodGenerator/StaticProxyConstructor.php | 7.8 | Mixed | Code Duplication: Edited copy of a member (31 corresponding lines) |
| src/ProxyManager/ProxyGenerator/AccessInterceptorScopeLocalizer/MethodGenerator/InterceptedMethod.php | 7.8 | Mixed | Code Duplication: Edited copy of a member (17 corresponding lines) |
| src/ProxyManager/ProxyGenerator/LazyLoadingValueHolder/MethodGenerator/MagicIsset.php | 8.5 | Near-clean | Code Duplication: Edited copies of one member (3 members, 26+ corresponding lines) |
| src/ProxyManager/ProxyGenerator/LazyLoadingGhost/MethodGenerator/CallInitializer.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (19 corresponding lines) |
| src/ProxyManager/ProxyGenerator/LazyLoadingGhost/MethodGenerator/MagicGet.php | 8.5 | Near-clean | Code Duplication: Edited copies of one member (4 members, 24+ corresponding lines) |
| src/ProxyManager/ProxyGenerator/AccessInterceptorScopeLocalizer/MethodGenerator/MagicGet.php | 8.5 | Near-clean | Code Duplication: Edited copies of one member (4 members, 24+ corresponding lines) |
| src/ProxyManager/ProxyGenerator/LazyLoadingValueHolder/MethodGenerator/MagicClone.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (11 corresponding lines) |
| src/ProxyManager/ProxyGenerator/AccessInterceptorScopeLocalizerGenerator.php | 8.5 | Near-clean | Code Duplication: Edited copies of one member (3 members, 5+ corresponding lines) |
| src/ProxyManager/ProxyGenerator/LazyLoadingGhost/MethodGenerator/MagicIsset.php | 8.5 | Near-clean | Code Duplication: Duplicated block (13–14 lines × 3) |
| src/ProxyManager/ProxyGenerator/AccessInterceptor/MethodGenerator/SetMethodPrefixInterceptor.php | 8.5 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 42 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 — 42 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, 98 of 108 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.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (53 contributor(s) across 2959 commit(s) sampled, automation and bot accounts excluded). One of them holds 83% of the history; the other 52 hold 0.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- 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's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- 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.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (6379 LoC, 146 module-visible types across 38 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- 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.
- 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.
- 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.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
8 duplicated block group(s) detected. 9.2 % of the production lines (586 of 6,379) are in a reported copy. A further 10 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 copies of one member (4 members, 24+ corresponding lines) finding(s) in Code Duplication — start with MagicGet.php (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with AccessInterceptorValueHolderGenerator.php, MagicSet.php. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (43 corresponding lines) finding(s) in Code Duplication — start with AccessInterceptorValueHolderGenerator.php. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 10 classes have LCOM4 above 3.
D10 · Test Quality
4 skipped (4 with a documented reason), 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 353 tests.
D12 · Dependency Hygiene
1 outdated, 0 abandoned direct Composer dependencies. PLATFORM requirements (php, ext-*, lib-*) are deliberately not graded here: they name the runtime rather than a Packagist package, so there is no release for them to be behind — whether that runtime is still supported is a separate question with a separate remedy. Development requirements are excluded, because a consumer never installs them. A newer release is reported only where this repository's OWN constraint already admits it, so the remedy is `composer update` and never a manifest edit. Known CVEs in this dependency graph are D30's question.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 2 locked Composer package(s) use a banned license. Licences were read from this repository's REDACTED, which records the `license` each package declares, over every package in its production `packages` list, direct and transitive, at the locked version; the 83 package(s) under `packages-dev` are not installed for a consumer and are excluded.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 6379 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
1 of 1 documentation facets pass in full. 15 document(s) read across 1 unit(s).
D27 · Navigability
53 % of calls cross a namespace and 6 % go through an interface, but 40 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
41 finding(s): 0 critical, 39 high, 2 medium, 0 low. 23 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.
What to do
- Resolve the 16 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (16). — One of this dimension's main actionable groups (16 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 23 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 (23 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
3 finding(s): 0 critical, 3 high, 0 medium, 0 low.
What to do
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
D34 · Knowledge Freshness
24 of 24 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/ProxyManager/ProxyGenerator/Util/PublicScopeSimulator.php. Counted over 24 of the 140 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 24 Orphaned file finding(s) in Knowledge Freshness — start with InterceptorGenerator.php (2), PublicScopeSimulator.php, LazyLoadingGhostGenerator.php. — One of this dimension's main actionable groups (24 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: MagicGet.php↔MagicUnset.php 60%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with MagicGet.php. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 7 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (7 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 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 2 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
AX4 · Dependency direction
AX6 · Interface segregation
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
M4 · Documentation accuracy
P1 · CI/CD gates
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
P10 · Library API & versioning
P3 · Security & performance tooling
What to do
- Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
- 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.
PF1 · Benchmark discipline
X16 · Unfloored truncation loop
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 96.6 | Exemplary | Solid. |
| Architecture | 97.5 | Exemplary | Solid. |
| Maturity | 48.8 | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 73.6 | Strong | Solid. |
| Security | 66.1 | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
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 — 73 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 applicable: this repository's PHP imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- 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
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
- D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed PHP surface was not measured.
- 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
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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) — 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.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this Composer build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's PHP source (1 module(s), 140 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the PHP source, so there is no service whose uptime a failing dependency could take down
- 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
- 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
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- 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
- X29 Per-element action decided by a fixed element — 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 — 42 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 29 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copies of one member (4 members, 24+ corresponding lines) src/ProxyManager/ProxyGenerator/LazyLoadingGhost/MethodGenerator/MagicGet.php:100
- Edited copies of one member (4 members, 24+ corresponding lines) src/ProxyManager/ProxyGenerator/AccessInterceptorScopeLocalizer/MethodGenerator/MagicGet.php:29
- Duplicated block (8 lines × 2) src/ProxyManager/ProxyGenerator/AccessInterceptorValueHolderGenerator.php:63
- Duplicated block (8 lines × 2) src/ProxyManager/ProxyGenerator/LazyLoadingValueHolder/MethodGenerator/MagicSet.php:35
- Change coupling: MagicGet.php ↔ MagicUnset.php src/ProxyManager/ProxyGenerator/AccessInterceptorValueHolder/MethodGenerator/MagicGet.php:1
- REDACTED
- Edited copy of a member (43 corresponding lines) src/ProxyManager/ProxyGenerator/AccessInterceptorValueHolderGenerator.php:58
- Edited copy of a member (31 corresponding lines) src/ProxyManager/ProxyGenerator/AccessInterceptorScopeLocalizer/MethodGenerator/StaticProxyConstructor.php:24
- Edited copies of one member (3 members, 26+ corresponding lines) src/ProxyManager/ProxyGenerator/LazyLoadingValueHolder/MethodGenerator/MagicIsset.php:31
- Edited copies of one member (4 members, 28+ corresponding lines) src/ProxyManager/ProxyGenerator/AccessInterceptorValueHolder/MethodGenerator/MagicGet.php:34
- Edited copy of a member (19 corresponding lines) src/ProxyManager/ProxyGenerator/LazyLoadingGhost/MethodGenerator/CallInitializer.php:87
- Edited copy of a member (17 corresponding lines) src/ProxyManager/ProxyGenerator/AccessInterceptorScopeLocalizer/MethodGenerator/InterceptedMethod.php:28
- Edited copy of a member (11 corresponding lines) src/ProxyManager/ProxyGenerator/LazyLoadingValueHolder/MethodGenerator/MagicClone.php:24
- Edited copies of one member (3 members, 5+ corresponding lines) src/ProxyManager/ProxyGenerator/AccessInterceptorScopeLocalizerGenerator.php:92
- Duplicated block (19 lines × 3) src/ProxyManager/ProxyGenerator/AccessInterceptorValueHolder/MethodGenerator/MagicGet.php:43
- Duplicated block (15–16 lines × 2) src/ProxyManager/ProxyGenerator/AccessInterceptorScopeLocalizer/MethodGenerator/StaticProxyConstructor.php:37
- Duplicated block (13–14 lines × 3) src/ProxyManager/ProxyGenerator/LazyLoadingGhost/MethodGenerator/MagicIsset.php:103
- Duplicated block (10 lines × 2) src/ProxyManager/ProxyGenerator/AccessInterceptor/MethodGenerator/SetMethodPrefixInterceptor.php:26
- Duplicated block (9 lines × 2) src/ProxyManager/ProxyGenerator/AccessInterceptorScopeLocalizer/MethodGenerator/InterceptedMethod.php:28
- Duplicated block (7 lines × 3) src/ProxyManager/ProxyGenerator/RemoteObject/MethodGenerator/MagicGet.php:27
Minor — 32 finding(s)
- Orphaned file src/ProxyManager/ProxyGenerator/Util/PublicScopeSimulator.php:1
- Orphaned file src/ProxyManager/ProxyGenerator/LazyLoadingGhostGenerator.php:1
- Orphaned file src/ProxyManager/ProxyGenerator/Util/Properties.php:1
- Orphaned file src/ProxyManager/ProxyGenerator/AccessInterceptorValueHolderGenerator.php:1
- Orphaned file src/ProxyManager/ProxyGenerator/LazyLoadingGhost/MethodGenerator/CallInitializer.php:1
- Orphaned file src/ProxyManager/ProxyGenerator/LazyLoadingValueHolderGenerator.php:1
- Orphaned file src/ProxyManager/ProxyGenerator/AccessInterceptorScopeLocalizerGenerator.php:1
- Orphaned file src/ProxyManager/Configuration.php:1
- Orphaned file src/ProxyManager/Factory/LazyLoadingGhostFactory.php:1
- Orphaned file src/ProxyManager/ProxyGenerator/LazyLoadingGhost/MethodGenerator/MagicGet.php:1
- Orphaned file src/ProxyManager/ProxyGenerator/LazyLoadingGhost/MethodGenerator/MagicSet.php:1
- Orphaned file src/ProxyManager/ProxyGenerator/LazyLoadingGhost/MethodGenerator/MagicUnset.php:1
- Orphaned file src/ProxyManager/Factory/AbstractBaseFactory.php:1
- Orphaned file src/ProxyManager/ProxyGenerator/LazyLoadingGhost/MethodGenerator/MagicIsset.php:1
- Orphaned file src/ProxyManager/ProxyGenerator/AccessInterceptorValueHolder/MethodGenerator/Util/InterceptorGenerator.php:1
- Orphaned file src/ProxyManager/ProxyGenerator/RemoteObjectGenerator.php:1
- Orphaned file src/ProxyManager/Factory/AccessInterceptorValueHolderFactory.php:1
- Orphaned file src/ProxyManager/ProxyGenerator/AccessInterceptorScopeLocalizer/MethodGenerator/Util/InterceptorGenerator.php:1
- Orphaned file src/ProxyManager/Factory/AccessInterceptorScopeLocalizerFactory.php:1
- Orphaned file src/ProxyManager/ProxyGenerator/AccessInterceptorScopeLocalizer/MethodGenerator/BindProxyProperties.php:1
- Orphaned file src/ProxyManager/ProxyGenerator/ValueHolder/MethodGenerator/Constructor.php:1
- Orphaned file src/ProxyManager/ProxyGenerator/Util/UnsetPropertiesGenerator.php:1
- Orphaned file src/ProxyManager/ProxyGenerator/AccessInterceptorValueHolder/MethodGenerator/StaticProxyConstructor.php:1
- Orphaned file src/ProxyManager/ProxyGenerator/RemoteObject/MethodGenerator/RemoteObjectMethod.php:1
- Scattered collaborators
- Dormant codebase
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- CI build step not evidenced
- No changelog
Minor — 5 finding(s)
- Skipped (documented): testPropertyUnset tests/ProxyManagerTest/Functional/AccessInterceptorScopeLocalizerFunctionalTest.php:251
- Skipped (documented): testPropertyAbsence tests/ProxyManagerTest/Functional/LazyLoadingGhostFunctionalTest.php:219
- Skipped (documented): testPropertyAbsence tests/ProxyManagerTest/Functional/LazyLoadingValueHolderFunctionalTest.php:189
- Skipped (documented): testGenerateWithDisabledEval tests/ProxyManagerTest/GeneratorStrategy/EvaluatingGeneratorStrategyTest.php:43
- Outdated: laminas/laminas-code
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-baaf49631c3147f18dc845aa5a3bd469/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-baaf49631c3147f18dc845aa5a3bd469/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=2051" --report-format json --report-path /tmp/watchdog-gitleaks-baaf49631c3147f18dc845aa5a3bd469/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-baaf49631c3147f18dc845aa5a3bd469/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 . | 41 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 3 | artifacts/raw/osv-scanner.json |
| 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. | 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |