Executive summary
boson-php/boson falls short of our standard for a preview release, in part because it has pipeline tools referenced by a changeable name. It scores 63.2 out of 100 and is rated Adequate, and 24 of its 25 critical findings are security problems in the packages it uses and in the build pipeline.
Security and Compliance, at 58.8, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is recording design decisions, worth about 5.0 points. Making the tests check their results comes next, worth about 2.9 points.
Twelve known security holes in the packages the code depends on can be used by attackers. Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and two secrets can leak from the build pipeline. Updating the vulnerable packages, pinning each tool to an exact version and limiting each secret to its own step would close these risks. The test that checks nothing needs to check the result it produces.
The product code is 36,645 lines, about €50,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
Rebuild cost: about €50,000 · Estimate
| Cost to rebuild | €17,000 to €83,000, for 275 to 873 hours of work, about 0.3 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 63. 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 | Medium: 36,645 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Component.Saucer | 2 Contracts.ValueObject | 3 Dispatcher | 4 Exception | 5 Component.Compiler.Target | 6 Component.CpuInfo | 7 Component.OsInfo | 8 Contracts.Http.Component | 9 Contracts.Id | 10 Contracts.Uri.Component | 11 Component.Compiler | 12 Contracts.Http.Component.StatusCode | 13 Contracts.Uri | 14 Extension | 15 Shared | 16 Api | 17 Api.OperatingSystem | 18 Component.Compiler.Configuration.Factory.JsonConfiguration | 19 Component.Uri.Factory | 20 Contracts.Http | 21 WebView.Api | 22 WebView.Event | 23 Api.Dialog | 24 WebView.Api.Schemes.Request | 25 WebView.Api.Scripts | 26 WebView.Api.Bindings | 27 WebView.Api.Schemes | 28 WebView.Api.Data | 29 WebView.Api.Security | 30 WebView.Api.WebComponents.Context | 31 WebView | 32 WebView.Api.Battery | 33 WebView.Api.Network | 34 Window | 35 Boson | 36 Api.Console | 37 Api.QuitOnClose | 38 Event | 39 WebView.Api.WebComponents.Internal | 40 WebView.Api.WebComponents |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Component.Saucer | ||||||||||||||||||||||||||||||||||||||||
| 2 Contracts.ValueObject | ||||||||||||||||||||||||||||||||||||||||
| 3 Dispatcher | ||||||||||||||||||||||||||||||||||||||||
| 4 Exception | ||||||||||||||||||||||||||||||||||||||||
| 5 Component.Compiler.Target | 7 | |||||||||||||||||||||||||||||||||||||||
| 6 Component.CpuInfo | 2 | |||||||||||||||||||||||||||||||||||||||
| 7 Component.OsInfo | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 Contracts.Http.Component | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 Contracts.Id | 3 | |||||||||||||||||||||||||||||||||||||||
| 10 Contracts.Uri.Component | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 Component.Compiler | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 Contracts.Http.Component.StatusCode | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 13 Contracts.Uri | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 14 Extension | 5 | 2 | ||||||||||||||||||||||||||||||||||||||
| 15 Shared | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 16 Api | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 17 Api.OperatingSystem | 1 | 5 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 18 Component.Compiler.Configuration.Factory.JsonConfiguration | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 19 Component.Uri.Factory | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 Contracts.Http | 3 | |||||||||||||||||||||||||||||||||||||||
| 21 WebView.Api | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 WebView.Event | 2 | 2 | 9 | |||||||||||||||||||||||||||||||||||||
| 23 Api.Dialog | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 24 WebView.Api.Schemes.Request | 3 | 2 | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 25 WebView.Api.Scripts | 1 | 2 | 2 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 26 WebView.Api.Bindings | 2 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 27 WebView.Api.Schemes | 2 | 1 | 1 | 1 | 3 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 28 WebView.Api.Data | 2 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 29 WebView.Api.Security | 2 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 30 WebView.Api.WebComponents.Context | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 WebView | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 32 WebView.Api.Battery | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||
| 33 WebView.Api.Network | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 34 Window | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 Boson | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 36 Api.Console | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 37 Api.QuitOnClose | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 38 Event | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 39 WebView.Api.WebComponents.Internal | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 40 WebView.Api.WebComponents | 2 | 1 | 1 | 1 | 2 | 1 | 3 | 3 | 2 | 2 |
5→11 Component.Compiler.Target uses Component.Compiler part of a loop✕
- Connections
- 7 pairs of types, where a type in Component.Compiler.Target uses a type in Component.Compiler.
- The types involved
Boson.Component.Compiler.Target.BuiltinTarget→Boson.Component.Compiler.ConfigurationBoson.Component.Compiler.Target.PharTarget→Boson.Component.Compiler.ConfigurationBoson.Component.Compiler.Target.Target→Boson.Component.Compiler.ConfigurationBoson.Component.Compiler.Target.TargetFactoryInterface→Boson.Component.Compiler.ConfigurationBoson.Component.Compiler.Target.TargetInterface→Boson.Component.Compiler.ConfigurationBoson.Component.Compiler.Target.UnixBuiltinTarget→Boson.Component.Compiler.ConfigurationBoson.Component.Compiler.Target.WindowsBuiltinTarget→Boson.Component.Compiler.Configuration
- Direction
- Component.Compiler.Target uses Component.Compiler, so a change to Component.Compiler can break Component.Compiler.Target, while a change to Component.Compiler.Target can't break Component.Compiler.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→2 Component.CpuInfo uses Contracts.ValueObject✕
- Connections
- 2 pairs of types, where a type in Component.CpuInfo uses a type in Contracts.ValueObject.
- The types involved
Boson.Component.CpuInfo.ArchitectureInterface→Boson.Contracts.ValueObject.StringValueObjectInterfaceBoson.Component.CpuInfo.InstructionSetInterface→Boson.Contracts.ValueObject.StringValueObjectInterface
- Direction
- Component.CpuInfo uses Contracts.ValueObject, so a change to Contracts.ValueObject can break Component.CpuInfo, while a change to Component.CpuInfo can't break Contracts.ValueObject.
- Position
- Below the diagonal: Component.CpuInfo uses a module listed above it, which is the healthy direction.
7→2 Component.OsInfo uses Contracts.ValueObject✕
- Connections
- 2 pairs of types, where a type in Component.OsInfo uses a type in Contracts.ValueObject.
- The types involved
Boson.Component.OsInfo.FamilyInterface→Boson.Contracts.ValueObject.StringValueObjectInterfaceBoson.Component.OsInfo.StandardInterface→Boson.Contracts.ValueObject.StringValueObjectInterface
- Direction
- Component.OsInfo uses Contracts.ValueObject, so a change to Contracts.ValueObject can break Component.OsInfo, while a change to Component.OsInfo can't break Contracts.ValueObject.
- Position
- Below the diagonal: Component.OsInfo uses a module listed above it, which is the healthy direction.
8→2 Contracts.Http.Component uses Contracts.ValueObject✕
- Connections
- 3 pairs of types, where a type in Contracts.Http.Component uses a type in Contracts.ValueObject.
- The types involved
Boson.Contracts.Http.Component.MethodInterface→Boson.Contracts.ValueObject.StringValueObjectInterfaceBoson.Contracts.Http.Component.StatusCodeInterface→Boson.Contracts.ValueObject.IntValueObjectInterfaceBoson.Contracts.Http.Component.StatusCodeInterface→Boson.Contracts.ValueObject.StringValueObjectInterface
- Direction
- Contracts.Http.Component uses Contracts.ValueObject, so a change to Contracts.ValueObject can break Contracts.Http.Component, while a change to Contracts.Http.Component can't break Contracts.ValueObject.
- Position
- Below the diagonal: Contracts.Http.Component uses a module listed above it, which is the healthy direction.
8→12 Contracts.Http.Component uses Contracts.Http.Component.StatusCode part of a loop✕
- Connections
- 1 pair of types, where a type in Contracts.Http.Component uses a type in Contracts.Http.Component.StatusCode.
- The types involved
Boson.Contracts.Http.Component.StatusCodeInterface→Boson.Contracts.Http.Component.StatusCode.StatusCodeCategoryInterface
- Direction
- Contracts.Http.Component uses Contracts.Http.Component.StatusCode, so a change to Contracts.Http.Component.StatusCode can break Contracts.Http.Component, while a change to Contracts.Http.Component can't break Contracts.Http.Component.StatusCode.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→2 Contracts.Id uses Contracts.ValueObject✕
- Connections
- 3 pairs of types, where a type in Contracts.Id uses a type in Contracts.ValueObject.
- The types involved
Boson.Contracts.Id.IdInterface→Boson.Contracts.ValueObject.ValueObjectInterfaceBoson.Contracts.Id.IntIdInterface→Boson.Contracts.ValueObject.IntValueObjectInterfaceBoson.Contracts.Id.StringIdInterface→Boson.Contracts.ValueObject.StringValueObjectInterface
- Direction
- Contracts.Id uses Contracts.ValueObject, so a change to Contracts.ValueObject can break Contracts.Id, while a change to Contracts.Id can't break Contracts.ValueObject.
- Position
- Below the diagonal: Contracts.Id uses a module listed above it, which is the healthy direction.
10→2 Contracts.Uri.Component uses Contracts.ValueObject✕
- Connections
- 1 pair of types, where a type in Contracts.Uri.Component uses a type in Contracts.ValueObject.
- The types involved
Boson.Contracts.Uri.Component.UriComponentInterface→Boson.Contracts.ValueObject.StringValueObjectInterface
- Direction
- Contracts.Uri.Component uses Contracts.ValueObject, so a change to Contracts.ValueObject can break Contracts.Uri.Component, while a change to Contracts.Uri.Component can't break Contracts.ValueObject.
- Position
- Below the diagonal: Contracts.Uri.Component uses a module listed above it, which is the healthy direction.
11→5 Component.Compiler uses Component.Compiler.Target✕
- Connections
- 1 pair of types, where a type in Component.Compiler uses a type in Component.Compiler.Target.
- The types involved
Boson.Component.Compiler.Configuration→Boson.Component.Compiler.Target.TargetInterface
- Direction
- Component.Compiler uses Component.Compiler.Target, so a change to Component.Compiler.Target can break Component.Compiler, while a change to Component.Compiler can't break Component.Compiler.Target.
- Position
- Below the diagonal: Component.Compiler uses a module listed above it, which is the healthy direction.
12→2 Contracts.Http.Component.StatusCode uses Contracts.ValueObject✕
- Connections
- 1 pair of types, where a type in Contracts.Http.Component.StatusCode uses a type in Contracts.ValueObject.
- The types involved
Boson.Contracts.Http.Component.StatusCode.StatusCodeCategoryInterface→Boson.Contracts.ValueObject.StringValueObjectInterface
- Direction
- Contracts.Http.Component.StatusCode uses Contracts.ValueObject, so a change to Contracts.ValueObject can break Contracts.Http.Component.StatusCode, while a change to Contracts.Http.Component.StatusCode can't break Contracts.ValueObject.
- Position
- Below the diagonal: Contracts.Http.Component.StatusCode uses a module listed above it, which is the healthy direction.
12→8 Contracts.Http.Component.StatusCode uses Contracts.Http.Component✕
- Connections
- 2 pairs of types, where a type in Contracts.Http.Component.StatusCode uses a type in Contracts.Http.Component.
- The types involved
Boson.Contracts.Http.Component.StatusCode.MutableStatusCodeProviderInterface→Boson.Contracts.Http.Component.StatusCodeInterfaceBoson.Contracts.Http.Component.StatusCode.StatusCodeProviderInterface→Boson.Contracts.Http.Component.StatusCodeInterface
- Direction
- Contracts.Http.Component.StatusCode uses Contracts.Http.Component, so a change to Contracts.Http.Component can break Contracts.Http.Component.StatusCode, while a change to Contracts.Http.Component.StatusCode can't break Contracts.Http.Component.
- Position
- Below the diagonal: Contracts.Http.Component.StatusCode uses a module listed above it, which is the healthy direction.
13→2 Contracts.Uri uses Contracts.ValueObject✕
- Connections
- 1 pair of types, where a type in Contracts.Uri uses a type in Contracts.ValueObject.
- The types involved
Boson.Contracts.Uri.UriInterface→Boson.Contracts.ValueObject.StringValueObjectInterface
- Direction
- Contracts.Uri uses Contracts.ValueObject, so a change to Contracts.ValueObject can break Contracts.Uri, while a change to Contracts.Uri can't break Contracts.ValueObject.
- Position
- Below the diagonal: Contracts.Uri uses a module listed above it, which is the healthy direction.
13→10 Contracts.Uri uses Contracts.Uri.Component✕
- Connections
- 4 pairs of types, where a type in Contracts.Uri uses a type in Contracts.Uri.Component.
- The types involved
Boson.Contracts.Uri.UriInterface→Boson.Contracts.Uri.Component.AuthorityInterfaceBoson.Contracts.Uri.UriInterface→Boson.Contracts.Uri.Component.PathInterfaceBoson.Contracts.Uri.UriInterface→Boson.Contracts.Uri.Component.QueryInterfaceBoson.Contracts.Uri.UriInterface→Boson.Contracts.Uri.Component.SchemeInterface
- Direction
- Contracts.Uri uses Contracts.Uri.Component, so a change to Contracts.Uri.Component can break Contracts.Uri, while a change to Contracts.Uri can't break Contracts.Uri.Component.
- Position
- Below the diagonal: Contracts.Uri uses a module listed above it, which is the healthy direction.
14→3 Extension uses Dispatcher✕
- Connections
- 5 pairs of types, where a type in Extension uses a type in Dispatcher.
- The types involved
Boson.Extension.ExtensionInterface→Boson.Dispatcher.EventListenerBoson.Extension.LoadedExtension→Boson.Dispatcher.EventBoson.Extension.LoadedExtension→Boson.Dispatcher.EventListenerBoson.Extension.LoadedExtension→Boson.Dispatcher.IntentionBoson.Extension.Registry→Boson.Dispatcher.EventListener
- Direction
- Extension uses Dispatcher, so a change to Dispatcher can break Extension, while a change to Extension can't break Dispatcher.
- Position
- Below the diagonal: Extension uses a module listed above it, which is the healthy direction.
14→9 Extension uses Contracts.Id✕
- Connections
- 2 pairs of types, where a type in Extension uses a type in Contracts.Id.
- The types involved
Boson.Extension.ExtensionInterface→Boson.Contracts.Id.IdentifiableInterfaceBoson.Extension.Registry→Boson.Contracts.Id.IdentifiableInterface
- Direction
- Extension uses Contracts.Id, so a change to Contracts.Id can break Extension, while a change to Extension can't break Contracts.Id.
- Position
- Below the diagonal: Extension uses a module listed above it, which is the healthy direction.
15→1 Shared uses Component.Saucer✕
- Connections
- 1 pair of types, where a type in Shared uses a type in Component.Saucer.
- The types involved
Boson.Shared.StructPointerId→Boson.Component.Saucer.SaucerInterface
- Direction
- Shared uses Component.Saucer, so a change to Component.Saucer can break Shared, while a change to Shared can't break Component.Saucer.
- Position
- Below the diagonal: Shared uses a module listed above it, which is the healthy direction.
15→9 Shared uses Contracts.Id✕
- Connections
- 2 pairs of types, where a type in Shared uses a type in Contracts.Id.
- The types involved
Boson.Shared.PositiveIntId→Boson.Contracts.Id.IntIdInterfaceBoson.Shared.StructPointerId→Boson.Contracts.Id.IntIdInterface
- Direction
- Shared uses Contracts.Id, so a change to Contracts.Id can break Shared, while a change to Shared can't break Contracts.Id.
- Position
- Below the diagonal: Shared uses a module listed above it, which is the healthy direction.
16→1 Api uses Component.Saucer✕
- Connections
- 1 pair of types, where a type in Api uses a type in Component.Saucer.
- The types involved
Boson.Api.LoadedApplicationExtension→Boson.Component.Saucer.SaucerInterface
- Direction
- Api uses Component.Saucer, so a change to Component.Saucer can break Api, while a change to Api can't break Component.Saucer.
- Position
- Below the diagonal: Api uses a module listed above it, which is the healthy direction.
16→3 Api uses Dispatcher✕
- Connections
- 1 pair of types, where a type in Api uses a type in Dispatcher.
- The types involved
Boson.Api.LoadedApplicationExtension→Boson.Dispatcher.EventListener
- Direction
- Api uses Dispatcher, so a change to Dispatcher can break Api, while a change to Api can't break Dispatcher.
- Position
- Below the diagonal: Api uses a module listed above it, which is the healthy direction.
16→14 Api uses Extension✕
- Connections
- 1 pair of types, where a type in Api uses a type in Extension.
- The types involved
Boson.Api.LoadedApplicationExtension→Boson.Extension.LoadedExtension
- Direction
- Api uses Extension, so a change to Extension can break Api, while a change to Api can't break Extension.
- Position
- Below the diagonal: Api uses a module listed above it, which is the healthy direction.
16→15 Api uses Shared✕
- Connections
- 1 pair of types, where a type in Api uses a type in Shared.
- The types involved
Boson.Api.LoadedApplicationExtension→Boson.Shared.StructPointerId
- Direction
- Api uses Shared, so a change to Shared can break Api, while a change to Api can't break Shared.
- Position
- Below the diagonal: Api uses a module listed above it, which is the healthy direction.
16→35 Api uses Boson part of a loop✕
- Connections
- 1 pair of types, where a type in Api uses a type in Boson.
- The types involved
Boson.Api.LoadedApplicationExtension→Boson.Application
- Direction
- Api uses Boson, so a change to Boson can break Api, while a change to Api can't break Boson.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→3 Api.OperatingSystem uses Dispatcher✕
- Connections
- 1 pair of types, where a type in Api.OperatingSystem uses a type in Dispatcher.
- The types involved
Boson.Api.OperatingSystem.OperatingSystemExtension→Boson.Dispatcher.EventListener
- Direction
- Api.OperatingSystem uses Dispatcher, so a change to Dispatcher can break Api.OperatingSystem, while a change to Api.OperatingSystem can't break Dispatcher.
- Position
- Below the diagonal: Api.OperatingSystem uses a module listed above it, which is the healthy direction.
17→7 Api.OperatingSystem uses Component.OsInfo✕
- Connections
- 5 pairs of types, where a type in Api.OperatingSystem uses a type in Component.OsInfo.
- The types involved
Boson.Api.OperatingSystem.OperatingSystemInfo→Boson.Component.OsInfo.FamilyInterfaceBoson.Api.OperatingSystem.OperatingSystemInfo→Boson.Component.OsInfo.OperatingSystemBoson.Api.OperatingSystem.OperatingSystemInfo→Boson.Component.OsInfo.StandardInterfaceBoson.Api.OperatingSystem.OperatingSystemInfoInterface→Boson.Component.OsInfo.FamilyInterfaceBoson.Api.OperatingSystem.OperatingSystemInfoInterface→Boson.Component.OsInfo.StandardInterface
- Direction
- Api.OperatingSystem uses Component.OsInfo, so a change to Component.OsInfo can break Api.OperatingSystem, while a change to Api.OperatingSystem can't break Component.OsInfo.
- Position
- Below the diagonal: Api.OperatingSystem uses a module listed above it, which is the healthy direction.
17→9 Api.OperatingSystem uses Contracts.Id✕
- Connections
- 1 pair of types, where a type in Api.OperatingSystem uses a type in Contracts.Id.
- The types involved
Boson.Api.OperatingSystem.OperatingSystemExtension→Boson.Contracts.Id.IdentifiableInterface
- Direction
- Api.OperatingSystem uses Contracts.Id, so a change to Contracts.Id can break Api.OperatingSystem, while a change to Api.OperatingSystem can't break Contracts.Id.
- Position
- Below the diagonal: Api.OperatingSystem uses a module listed above it, which is the healthy direction.
17→14 Api.OperatingSystem uses Extension✕
- Connections
- 1 pair of types, where a type in Api.OperatingSystem uses a type in Extension.
- The types involved
Boson.Api.OperatingSystem.OperatingSystemExtension→Boson.Extension.Extension
- Direction
- Api.OperatingSystem uses Extension, so a change to Extension can break Api.OperatingSystem, while a change to Api.OperatingSystem can't break Extension.
- Position
- Below the diagonal: Api.OperatingSystem uses a module listed above it, which is the healthy direction.
18→5 Component.Compiler.Configuration.Factory.JsonConfiguration uses Component.Compiler.Target✕
- Connections
- 1 pair of types, where a type in Component.Compiler.Configuration.Factory.JsonConfiguration uses a type in Component.Compiler.Target.
- The types involved
Boson.Component.Compiler.Configuration.Factory.JsonConfiguration.JsonConfigTargetFactory→Boson.Component.Compiler.Target.TargetInterface
- Direction
- Component.Compiler.Configuration.Factory.JsonConfiguration uses Component.Compiler.Target, so a change to Component.Compiler.Target can break Component.Compiler.Configuration.Factory.JsonConfiguration, while a change to Component.Compiler.Configuration.Factory.JsonConfiguration can't break Component.Compiler.Target.
- Position
- Below the diagonal: Component.Compiler.Configuration.Factory.JsonConfiguration uses a module listed above it, which is the healthy direction.
18→11 Component.Compiler.Configuration.Factory.JsonConfiguration uses Component.Compiler✕
- Connections
- 2 pairs of types, where a type in Component.Compiler.Configuration.Factory.JsonConfiguration uses a type in Component.Compiler.
- The types involved
Boson.Component.Compiler.Configuration.Factory.JsonConfiguration.JsonConfigLoader→Boson.Component.Compiler.ConfigurationBoson.Component.Compiler.Configuration.Factory.JsonConfiguration.JsonConfigTargetFactory→Boson.Component.Compiler.Configuration
- Direction
- Component.Compiler.Configuration.Factory.JsonConfiguration uses Component.Compiler, so a change to Component.Compiler can break Component.Compiler.Configuration.Factory.JsonConfiguration, while a change to Component.Compiler.Configuration.Factory.JsonConfiguration can't break Component.Compiler.
- Position
- Below the diagonal: Component.Compiler.Configuration.Factory.JsonConfiguration uses a module listed above it, which is the healthy direction.
19→10 Component.Uri.Factory uses Contracts.Uri.Component✕
- Connections
- 1 pair of types, where a type in Component.Uri.Factory uses a type in Contracts.Uri.Component.
- The types involved
Boson.Component.Uri.Factory.UriFactory→Boson.Contracts.Uri.Component.SchemeInterface
- Direction
- Component.Uri.Factory uses Contracts.Uri.Component, so a change to Contracts.Uri.Component can break Component.Uri.Factory, while a change to Component.Uri.Factory can't break Contracts.Uri.Component.
- Position
- Below the diagonal: Component.Uri.Factory uses a module listed above it, which is the healthy direction.
19→13 Component.Uri.Factory uses Contracts.Uri✕
- Connections
- 1 pair of types, where a type in Component.Uri.Factory uses a type in Contracts.Uri.
- The types involved
Boson.Component.Uri.Factory.UriFactory→Boson.Contracts.Uri.UriInterface
- Direction
- Component.Uri.Factory uses Contracts.Uri, so a change to Contracts.Uri can break Component.Uri.Factory, while a change to Component.Uri.Factory can't break Contracts.Uri.
- Position
- Below the diagonal: Component.Uri.Factory uses a module listed above it, which is the healthy direction.
20→12 Contracts.Http uses Contracts.Http.Component.StatusCode✕
- Connections
- 3 pairs of types, where a type in Contracts.Http uses a type in Contracts.Http.Component.StatusCode.
- The types involved
Boson.Contracts.Http.EvolvableResponseInterface→Boson.Contracts.Http.Component.StatusCode.EvolvableStatusCodeProviderInterfaceBoson.Contracts.Http.MutableResponseInterface→Boson.Contracts.Http.Component.StatusCode.MutableStatusCodeProviderInterfaceBoson.Contracts.Http.ResponseInterface→Boson.Contracts.Http.Component.StatusCode.StatusCodeProviderInterface
- Direction
- Contracts.Http uses Contracts.Http.Component.StatusCode, so a change to Contracts.Http.Component.StatusCode can break Contracts.Http, while a change to Contracts.Http can't break Contracts.Http.Component.StatusCode.
- Position
- Below the diagonal: Contracts.Http uses a module listed above it, which is the healthy direction.
21→3 WebView.Api uses Dispatcher✕
- Connections
- 1 pair of types, where a type in WebView.Api uses a type in Dispatcher.
- The types involved
Boson.WebView.Api.LoadedWebViewExtension→Boson.Dispatcher.EventListener
- Direction
- WebView.Api uses Dispatcher, so a change to Dispatcher can break WebView.Api, while a change to WebView.Api can't break Dispatcher.
- Position
- Below the diagonal: WebView.Api uses a module listed above it, which is the healthy direction.
21→15 WebView.Api uses Shared✕
- Connections
- 1 pair of types, where a type in WebView.Api uses a type in Shared.
- The types involved
Boson.WebView.Api.LoadedWebViewExtension→Boson.Shared.StructPointerId
- Direction
- WebView.Api uses Shared, so a change to Shared can break WebView.Api, while a change to WebView.Api can't break Shared.
- Position
- Below the diagonal: WebView.Api uses a module listed above it, which is the healthy direction.
21→31 WebView.Api uses WebView part of a loop✕
- Connections
- 1 pair of types, where a type in WebView.Api uses a type in WebView.
- The types involved
Boson.WebView.Api.LoadedWebViewExtension→Boson.WebView.WebView
- Direction
- WebView.Api uses WebView, so a change to WebView can break WebView.Api, while a change to WebView.Api can't break WebView.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→3 WebView.Event uses Dispatcher✕
- Connections
- 2 pairs of types, where a type in WebView.Event uses a type in Dispatcher.
- The types involved
Boson.WebView.Event.WebViewEvent→Boson.Dispatcher.EventBoson.WebView.Event.WebViewIntention→Boson.Dispatcher.Intention
- Direction
- WebView.Event uses Dispatcher, so a change to Dispatcher can break WebView.Event, while a change to WebView.Event can't break Dispatcher.
- Position
- Below the diagonal: WebView.Event uses a module listed above it, which is the healthy direction.
22→13 WebView.Event uses Contracts.Uri✕
- Connections
- 2 pairs of types, where a type in WebView.Event uses a type in Contracts.Uri.
- The types involved
Boson.WebView.Event.WebViewNavigated→Boson.Contracts.Uri.UriInterfaceBoson.WebView.Event.WebViewNavigating→Boson.Contracts.Uri.UriInterface
- Direction
- WebView.Event uses Contracts.Uri, so a change to Contracts.Uri can break WebView.Event, while a change to WebView.Event can't break Contracts.Uri.
- Position
- Below the diagonal: WebView.Event uses a module listed above it, which is the healthy direction.
22→31 WebView.Event uses WebView part of a loop✕
- Connections
- 9 pairs of types, where a type in WebView.Event uses a type in WebView.
- The types involved
Boson.WebView.Event.WebViewEvent→Boson.WebView.WebViewBoson.WebView.Event.WebViewIntention→Boson.WebView.WebViewBoson.WebView.Event.WebViewMessageReceived→Boson.WebView.WebViewBoson.WebView.Event.WebViewNavigated→Boson.WebView.WebViewBoson.WebView.Event.WebViewNavigating→Boson.WebView.WebViewBoson.WebView.Event.WebViewStateChanged→Boson.WebView.WebViewBoson.WebView.Event.WebViewStateChanged→Boson.WebView.WebViewStateBoson.WebView.Event.WebViewTitleChanged→Boson.WebView.WebViewBoson.WebView.Event.WebViewTitleChanging→Boson.WebView.WebView
- Direction
- WebView.Event uses WebView, so a change to WebView can break WebView.Event, while a change to WebView.Event can't break WebView.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→3 Api.Dialog uses Dispatcher✕
- Connections
- 2 pairs of types, where a type in Api.Dialog uses a type in Dispatcher.
- The types involved
Boson.Api.Dialog.DialogExtension→Boson.Dispatcher.EventListenerBoson.Api.Dialog.SaucerDialogApi→Boson.Dispatcher.EventListener
- Direction
- Api.Dialog uses Dispatcher, so a change to Dispatcher can break Api.Dialog, while a change to Api.Dialog can't break Dispatcher.
- Position
- Below the diagonal: Api.Dialog uses a module listed above it, which is the healthy direction.
23→9 Api.Dialog uses Contracts.Id✕
- Connections
- 1 pair of types, where a type in Api.Dialog uses a type in Contracts.Id.
- The types involved
Boson.Api.Dialog.DialogExtension→Boson.Contracts.Id.IdentifiableInterface
- Direction
- Api.Dialog uses Contracts.Id, so a change to Contracts.Id can break Api.Dialog, while a change to Api.Dialog can't break Contracts.Id.
- Position
- Below the diagonal: Api.Dialog uses a module listed above it, which is the healthy direction.
23→14 Api.Dialog uses Extension✕
- Connections
- 1 pair of types, where a type in Api.Dialog uses a type in Extension.
- The types involved
Boson.Api.Dialog.DialogExtension→Boson.Extension.Extension
- Direction
- Api.Dialog uses Extension, so a change to Extension can break Api.Dialog, while a change to Api.Dialog can't break Extension.
- Position
- Below the diagonal: Api.Dialog uses a module listed above it, which is the healthy direction.
23→16 Api.Dialog uses Api✕
- Connections
- 1 pair of types, where a type in Api.Dialog uses a type in Api.
- The types involved
Boson.Api.Dialog.SaucerDialogApi→Boson.Api.LoadedApplicationExtension
- Direction
- Api.Dialog uses Api, so a change to Api can break Api.Dialog, while a change to Api.Dialog can't break Api.
- Position
- Below the diagonal: Api.Dialog uses a module listed above it, which is the healthy direction.
23→35 Api.Dialog uses Boson part of a loop✕
- Connections
- 1 pair of types, where a type in Api.Dialog uses a type in Boson.
- The types involved
Boson.Api.Dialog.SaucerDialogApi→Boson.Application
- Direction
- Api.Dialog uses Boson, so a change to Boson can break Api.Dialog, while a change to Api.Dialog can't break Boson.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→1 WebView.Api.Schemes.Request uses Component.Saucer✕
- Connections
- 3 pairs of types, where a type in WebView.Api.Schemes.Request uses a type in Component.Saucer.
- The types involved
Boson.WebView.Api.Schemes.Request.SaucerRequest→Boson.Component.Saucer.SaucerInterfaceBoson.WebView.Api.Schemes.Request.SaucerRequestFactory→Boson.Component.Saucer.SaucerInterfaceBoson.WebView.Api.Schemes.Request.SaucerResponseFactory→Boson.Component.Saucer.SaucerInterface
- Direction
- WebView.Api.Schemes.Request uses Component.Saucer, so a change to Component.Saucer can break WebView.Api.Schemes.Request, while a change to WebView.Api.Schemes.Request can't break Component.Saucer.
- Position
- Below the diagonal: WebView.Api.Schemes.Request uses a module listed above it, which is the healthy direction.
24→8 WebView.Api.Schemes.Request uses Contracts.Http.Component✕
- Connections
- 2 pairs of types, where a type in WebView.Api.Schemes.Request uses a type in Contracts.Http.Component.
- The types involved
Boson.WebView.Api.Schemes.Request.SaucerRequest→Boson.Contracts.Http.Component.HeadersInterfaceBoson.WebView.Api.Schemes.Request.SaucerRequest→Boson.Contracts.Http.Component.MethodInterface
- Direction
- WebView.Api.Schemes.Request uses Contracts.Http.Component, so a change to Contracts.Http.Component can break WebView.Api.Schemes.Request, while a change to WebView.Api.Schemes.Request can't break Contracts.Http.Component.
- Position
- Below the diagonal: WebView.Api.Schemes.Request uses a module listed above it, which is the healthy direction.
24→13 WebView.Api.Schemes.Request uses Contracts.Uri✕
- Connections
- 1 pair of types, where a type in WebView.Api.Schemes.Request uses a type in Contracts.Uri.
- The types involved
Boson.WebView.Api.Schemes.Request.SaucerRequest→Boson.Contracts.Uri.UriInterface
- Direction
- WebView.Api.Schemes.Request uses Contracts.Uri, so a change to Contracts.Uri can break WebView.Api.Schemes.Request, while a change to WebView.Api.Schemes.Request can't break Contracts.Uri.
- Position
- Below the diagonal: WebView.Api.Schemes.Request uses a module listed above it, which is the healthy direction.
24→20 WebView.Api.Schemes.Request uses Contracts.Http✕
- Connections
- 3 pairs of types, where a type in WebView.Api.Schemes.Request uses a type in Contracts.Http.
- The types involved
Boson.WebView.Api.Schemes.Request.SaucerRequest→Boson.Contracts.Http.RequestInterfaceBoson.WebView.Api.Schemes.Request.SaucerRequestFactory→Boson.Contracts.Http.RequestInterfaceBoson.WebView.Api.Schemes.Request.SaucerResponseFactory→Boson.Contracts.Http.ResponseInterface
- Direction
- WebView.Api.Schemes.Request uses Contracts.Http, so a change to Contracts.Http can break WebView.Api.Schemes.Request, while a change to WebView.Api.Schemes.Request can't break Contracts.Http.
- Position
- Below the diagonal: WebView.Api.Schemes.Request uses a module listed above it, which is the healthy direction.
24→27 WebView.Api.Schemes.Request uses WebView.Api.Schemes part of a loop✕
- Connections
- 1 pair of types, where a type in WebView.Api.Schemes.Request uses a type in WebView.Api.Schemes.
- The types involved
Boson.WebView.Api.Schemes.Request.SaucerResponseFactory→Boson.WebView.Api.Schemes.MimeTypeReader
- Direction
- WebView.Api.Schemes.Request uses WebView.Api.Schemes, so a change to WebView.Api.Schemes can break WebView.Api.Schemes.Request, while a change to WebView.Api.Schemes.Request can't break WebView.Api.Schemes.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→1 WebView.Api.Scripts uses Component.Saucer✕
- Connections
- 1 pair of types, where a type in WebView.Api.Scripts uses a type in Component.Saucer.
- The types involved
Boson.WebView.Api.Scripts.LoadedScript→Boson.Component.Saucer.SaucerInterface
- Direction
- WebView.Api.Scripts uses Component.Saucer, so a change to Component.Saucer can break WebView.Api.Scripts, while a change to WebView.Api.Scripts can't break Component.Saucer.
- Position
- Below the diagonal: WebView.Api.Scripts uses a module listed above it, which is the healthy direction.
25→3 WebView.Api.Scripts uses Dispatcher✕
- Connections
- 2 pairs of types, where a type in WebView.Api.Scripts uses a type in Dispatcher.
- The types involved
Boson.WebView.Api.Scripts.ScriptsApi→Boson.Dispatcher.EventListenerBoson.WebView.Api.Scripts.ScriptsExtension→Boson.Dispatcher.EventListener
- Direction
- WebView.Api.Scripts uses Dispatcher, so a change to Dispatcher can break WebView.Api.Scripts, while a change to WebView.Api.Scripts can't break Dispatcher.
- Position
- Below the diagonal: WebView.Api.Scripts uses a module listed above it, which is the healthy direction.
25→9 WebView.Api.Scripts uses Contracts.Id✕
- Connections
- 2 pairs of types, where a type in WebView.Api.Scripts uses a type in Contracts.Id.
- The types involved
Boson.WebView.Api.Scripts.LoadedScript→Boson.Contracts.Id.IdentifiableInterfaceBoson.WebView.Api.Scripts.ScriptsExtension→Boson.Contracts.Id.IdentifiableInterface
- Direction
- WebView.Api.Scripts uses Contracts.Id, so a change to Contracts.Id can break WebView.Api.Scripts, while a change to WebView.Api.Scripts can't break Contracts.Id.
- Position
- Below the diagonal: WebView.Api.Scripts uses a module listed above it, which is the healthy direction.
25→14 WebView.Api.Scripts uses Extension✕
- Connections
- 1 pair of types, where a type in WebView.Api.Scripts uses a type in Extension.
- The types involved
Boson.WebView.Api.Scripts.ScriptsExtension→Boson.Extension.Extension
- Direction
- WebView.Api.Scripts uses Extension, so a change to Extension can break WebView.Api.Scripts, while a change to WebView.Api.Scripts can't break Extension.
- Position
- Below the diagonal: WebView.Api.Scripts uses a module listed above it, which is the healthy direction.
25→15 WebView.Api.Scripts uses Shared✕
- Connections
- 1 pair of types, where a type in WebView.Api.Scripts uses a type in Shared.
- The types involved
Boson.WebView.Api.Scripts.LoadedScriptId→Boson.Shared.PositiveIntId
- Direction
- WebView.Api.Scripts uses Shared, so a change to Shared can break WebView.Api.Scripts, while a change to WebView.Api.Scripts can't break Shared.
- Position
- Below the diagonal: WebView.Api.Scripts uses a module listed above it, which is the healthy direction.
25→21 WebView.Api.Scripts uses WebView.Api✕
- Connections
- 1 pair of types, where a type in WebView.Api.Scripts uses a type in WebView.Api.
- The types involved
Boson.WebView.Api.Scripts.ScriptsApi→Boson.WebView.Api.LoadedWebViewExtension
- Direction
- WebView.Api.Scripts uses WebView.Api, so a change to WebView.Api can break WebView.Api.Scripts, while a change to WebView.Api.Scripts can't break WebView.Api.
- Position
- Below the diagonal: WebView.Api.Scripts uses a module listed above it, which is the healthy direction.
25→31 WebView.Api.Scripts uses WebView part of a loop✕
- Connections
- 2 pairs of types, where a type in WebView.Api.Scripts uses a type in WebView.
- The types involved
Boson.WebView.Api.Scripts.LoadedScript→Boson.WebView.WebViewBoson.WebView.Api.Scripts.ScriptsApi→Boson.WebView.WebView
- Direction
- WebView.Api.Scripts uses WebView, so a change to WebView can break WebView.Api.Scripts, while a change to WebView.Api.Scripts can't break WebView.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→3 WebView.Api.Bindings uses Dispatcher✕
- Connections
- 2 pairs of types, where a type in WebView.Api.Bindings uses a type in Dispatcher.
- The types involved
Boson.WebView.Api.Bindings.BindingsApi→Boson.Dispatcher.EventListenerBoson.WebView.Api.Bindings.BindingsExtension→Boson.Dispatcher.EventListener
- Direction
- WebView.Api.Bindings uses Dispatcher, so a change to Dispatcher can break WebView.Api.Bindings, while a change to WebView.Api.Bindings can't break Dispatcher.
- Position
- Below the diagonal: WebView.Api.Bindings uses a module listed above it, which is the healthy direction.
26→9 WebView.Api.Bindings uses Contracts.Id✕
- Connections
- 1 pair of types, where a type in WebView.Api.Bindings uses a type in Contracts.Id.
- The types involved
Boson.WebView.Api.Bindings.BindingsExtension→Boson.Contracts.Id.IdentifiableInterface
- Direction
- WebView.Api.Bindings uses Contracts.Id, so a change to Contracts.Id can break WebView.Api.Bindings, while a change to WebView.Api.Bindings can't break Contracts.Id.
- Position
- Below the diagonal: WebView.Api.Bindings uses a module listed above it, which is the healthy direction.
26→14 WebView.Api.Bindings uses Extension✕
- Connections
- 1 pair of types, where a type in WebView.Api.Bindings uses a type in Extension.
- The types involved
Boson.WebView.Api.Bindings.BindingsExtension→Boson.Extension.Extension
- Direction
- WebView.Api.Bindings uses Extension, so a change to Extension can break WebView.Api.Bindings, while a change to WebView.Api.Bindings can't break Extension.
- Position
- Below the diagonal: WebView.Api.Bindings uses a module listed above it, which is the healthy direction.
26→21 WebView.Api.Bindings uses WebView.Api✕
- Connections
- 1 pair of types, where a type in WebView.Api.Bindings uses a type in WebView.Api.
- The types involved
Boson.WebView.Api.Bindings.BindingsApi→Boson.WebView.Api.LoadedWebViewExtension
- Direction
- WebView.Api.Bindings uses WebView.Api, so a change to WebView.Api can break WebView.Api.Bindings, while a change to WebView.Api.Bindings can't break WebView.Api.
- Position
- Below the diagonal: WebView.Api.Bindings uses a module listed above it, which is the healthy direction.
26→22 WebView.Api.Bindings uses WebView.Event✕
- Connections
- 1 pair of types, where a type in WebView.Api.Bindings uses a type in WebView.Event.
- The types involved
Boson.WebView.Api.Bindings.BindingsApi→Boson.WebView.Event.WebViewMessageReceived
- Direction
- WebView.Api.Bindings uses WebView.Event, so a change to WebView.Event can break WebView.Api.Bindings, while a change to WebView.Api.Bindings can't break WebView.Event.
- Position
- Below the diagonal: WebView.Api.Bindings uses a module listed above it, which is the healthy direction.
26→25 WebView.Api.Bindings uses WebView.Api.Scripts✕
- Connections
- 1 pair of types, where a type in WebView.Api.Bindings uses a type in WebView.Api.Scripts.
- The types involved
Boson.WebView.Api.Bindings.BindingsApi→Boson.WebView.Api.Scripts.ScriptsApiInterface
- Direction
- WebView.Api.Bindings uses WebView.Api.Scripts, so a change to WebView.Api.Scripts can break WebView.Api.Bindings, while a change to WebView.Api.Bindings can't break WebView.Api.Scripts.
- Position
- Below the diagonal: WebView.Api.Bindings uses a module listed above it, which is the healthy direction.
26→31 WebView.Api.Bindings uses WebView part of a loop✕
- Connections
- 1 pair of types, where a type in WebView.Api.Bindings uses a type in WebView.
- The types involved
Boson.WebView.Api.Bindings.BindingsApi→Boson.WebView.WebView
- Direction
- WebView.Api.Bindings uses WebView, so a change to WebView can break WebView.Api.Bindings, while a change to WebView.Api.Bindings can't break WebView.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→3 WebView.Api.Schemes uses Dispatcher✕
- Connections
- 2 pairs of types, where a type in WebView.Api.Schemes uses a type in Dispatcher.
- The types involved
Boson.WebView.Api.Schemes.SchemesExtension→Boson.Dispatcher.EventListenerBoson.WebView.Api.Schemes.SchemesProvider→Boson.Dispatcher.EventListener
- Direction
- WebView.Api.Schemes uses Dispatcher, so a change to Dispatcher can break WebView.Api.Schemes, while a change to WebView.Api.Schemes can't break Dispatcher.
- Position
- Below the diagonal: WebView.Api.Schemes uses a module listed above it, which is the healthy direction.
27→8 WebView.Api.Schemes uses Contracts.Http.Component✕
- Connections
- 1 pair of types, where a type in WebView.Api.Schemes uses a type in Contracts.Http.Component.
- The types involved
Boson.WebView.Api.Schemes.SchemesProvider→Boson.Contracts.Http.Component.StatusCodeInterface
- Direction
- WebView.Api.Schemes uses Contracts.Http.Component, so a change to Contracts.Http.Component can break WebView.Api.Schemes, while a change to WebView.Api.Schemes can't break Contracts.Http.Component.
- Position
- Below the diagonal: WebView.Api.Schemes uses a module listed above it, which is the healthy direction.
27→9 WebView.Api.Schemes uses Contracts.Id✕
- Connections
- 1 pair of types, where a type in WebView.Api.Schemes uses a type in Contracts.Id.
- The types involved
Boson.WebView.Api.Schemes.SchemesExtension→Boson.Contracts.Id.IdentifiableInterface
- Direction
- WebView.Api.Schemes uses Contracts.Id, so a change to Contracts.Id can break WebView.Api.Schemes, while a change to WebView.Api.Schemes can't break Contracts.Id.
- Position
- Below the diagonal: WebView.Api.Schemes uses a module listed above it, which is the healthy direction.
27→14 WebView.Api.Schemes uses Extension✕
- Connections
- 1 pair of types, where a type in WebView.Api.Schemes uses a type in Extension.
- The types involved
Boson.WebView.Api.Schemes.SchemesExtension→Boson.Extension.Extension
- Direction
- WebView.Api.Schemes uses Extension, so a change to Extension can break WebView.Api.Schemes, while a change to WebView.Api.Schemes can't break Extension.
- Position
- Below the diagonal: WebView.Api.Schemes uses a module listed above it, which is the healthy direction.
27→20 WebView.Api.Schemes uses Contracts.Http✕
- Connections
- 3 pairs of types, where a type in WebView.Api.Schemes uses a type in Contracts.Http.
- The types involved
Boson.WebView.Api.Schemes.MimeTypeReader→Boson.Contracts.Http.ResponseInterfaceBoson.WebView.Api.Schemes.SchemesProvider→Boson.Contracts.Http.RequestInterfaceBoson.WebView.Api.Schemes.SchemesProvider→Boson.Contracts.Http.ResponseInterface
- Direction
- WebView.Api.Schemes uses Contracts.Http, so a change to Contracts.Http can break WebView.Api.Schemes, while a change to WebView.Api.Schemes can't break Contracts.Http.
- Position
- Below the diagonal: WebView.Api.Schemes uses a module listed above it, which is the healthy direction.
27→21 WebView.Api.Schemes uses WebView.Api✕
- Connections
- 1 pair of types, where a type in WebView.Api.Schemes uses a type in WebView.Api.
- The types involved
Boson.WebView.Api.Schemes.SchemesProvider→Boson.WebView.Api.LoadedWebViewExtension
- Direction
- WebView.Api.Schemes uses WebView.Api, so a change to WebView.Api can break WebView.Api.Schemes, while a change to WebView.Api.Schemes can't break WebView.Api.
- Position
- Below the diagonal: WebView.Api.Schemes uses a module listed above it, which is the healthy direction.
27→24 WebView.Api.Schemes uses WebView.Api.Schemes.Request✕
- Connections
- 2 pairs of types, where a type in WebView.Api.Schemes uses a type in WebView.Api.Schemes.Request.
- The types involved
Boson.WebView.Api.Schemes.SchemesProvider→Boson.WebView.Api.Schemes.Request.SaucerRequestFactoryBoson.WebView.Api.Schemes.SchemesProvider→Boson.WebView.Api.Schemes.Request.SaucerResponseFactory
- Direction
- WebView.Api.Schemes uses WebView.Api.Schemes.Request, so a change to WebView.Api.Schemes.Request can break WebView.Api.Schemes, while a change to WebView.Api.Schemes can't break WebView.Api.Schemes.Request.
- Position
- Below the diagonal: WebView.Api.Schemes uses a module listed above it, which is the healthy direction.
27→31 WebView.Api.Schemes uses WebView part of a loop✕
- Connections
- 1 pair of types, where a type in WebView.Api.Schemes uses a type in WebView.
- The types involved
Boson.WebView.Api.Schemes.SchemesProvider→Boson.WebView.WebView
- Direction
- WebView.Api.Schemes uses WebView, so a change to WebView can break WebView.Api.Schemes, while a change to WebView.Api.Schemes can't break WebView.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→3 WebView.Api.Data uses Dispatcher✕
- Connections
- 2 pairs of types, where a type in WebView.Api.Data uses a type in Dispatcher.
- The types involved
Boson.WebView.Api.Data.DataExtension→Boson.Dispatcher.EventListenerBoson.WebView.Api.Data.DataRetriever→Boson.Dispatcher.EventListener
- Direction
- WebView.Api.Data uses Dispatcher, so a change to Dispatcher can break WebView.Api.Data, while a change to WebView.Api.Data can't break Dispatcher.
- Position
- Below the diagonal: WebView.Api.Data uses a module listed above it, which is the healthy direction.
28→9 WebView.Api.Data uses Contracts.Id✕
- Connections
- 1 pair of types, where a type in WebView.Api.Data uses a type in Contracts.Id.
- The types involved
Boson.WebView.Api.Data.DataExtension→Boson.Contracts.Id.IdentifiableInterface
- Direction
- WebView.Api.Data uses Contracts.Id, so a change to Contracts.Id can break WebView.Api.Data, while a change to WebView.Api.Data can't break Contracts.Id.
- Position
- Below the diagonal: WebView.Api.Data uses a module listed above it, which is the healthy direction.
28→14 WebView.Api.Data uses Extension✕
- Connections
- 1 pair of types, where a type in WebView.Api.Data uses a type in Extension.
- The types involved
Boson.WebView.Api.Data.DataExtension→Boson.Extension.Extension
- Direction
- WebView.Api.Data uses Extension, so a change to Extension can break WebView.Api.Data, while a change to WebView.Api.Data can't break Extension.
- Position
- Below the diagonal: WebView.Api.Data uses a module listed above it, which is the healthy direction.
28→21 WebView.Api.Data uses WebView.Api✕
- Connections
- 1 pair of types, where a type in WebView.Api.Data uses a type in WebView.Api.
- The types involved
Boson.WebView.Api.Data.DataRetriever→Boson.WebView.Api.LoadedWebViewExtension
- Direction
- WebView.Api.Data uses WebView.Api, so a change to WebView.Api can break WebView.Api.Data, while a change to WebView.Api.Data can't break WebView.Api.
- Position
- Below the diagonal: WebView.Api.Data uses a module listed above it, which is the healthy direction.
28→25 WebView.Api.Data uses WebView.Api.Scripts✕
- Connections
- 1 pair of types, where a type in WebView.Api.Data uses a type in WebView.Api.Scripts.
- The types involved
Boson.WebView.Api.Data.DataRetriever→Boson.WebView.Api.Scripts.ScriptsApiInterface
- Direction
- WebView.Api.Data uses WebView.Api.Scripts, so a change to WebView.Api.Scripts can break WebView.Api.Data, while a change to WebView.Api.Data can't break WebView.Api.Scripts.
- Position
- Below the diagonal: WebView.Api.Data uses a module listed above it, which is the healthy direction.
28→26 WebView.Api.Data uses WebView.Api.Bindings✕
- Connections
- 1 pair of types, where a type in WebView.Api.Data uses a type in WebView.Api.Bindings.
- The types involved
Boson.WebView.Api.Data.DataRetriever→Boson.WebView.Api.Bindings.BindingsApiInterface
- Direction
- WebView.Api.Data uses WebView.Api.Bindings, so a change to WebView.Api.Bindings can break WebView.Api.Data, while a change to WebView.Api.Data can't break WebView.Api.Bindings.
- Position
- Below the diagonal: WebView.Api.Data uses a module listed above it, which is the healthy direction.
28→31 WebView.Api.Data uses WebView part of a loop✕
- Connections
- 1 pair of types, where a type in WebView.Api.Data uses a type in WebView.
- The types involved
Boson.WebView.Api.Data.DataRetriever→Boson.WebView.WebView
- Direction
- WebView.Api.Data uses WebView, so a change to WebView can break WebView.Api.Data, while a change to WebView.Api.Data can't break WebView.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→3 WebView.Api.Security uses Dispatcher✕
- Connections
- 2 pairs of types, where a type in WebView.Api.Security uses a type in Dispatcher.
- The types involved
Boson.WebView.Api.Security.SecurityExtension→Boson.Dispatcher.EventListenerBoson.WebView.Api.Security.SecurityInfo→Boson.Dispatcher.EventListener
- Direction
- WebView.Api.Security uses Dispatcher, so a change to Dispatcher can break WebView.Api.Security, while a change to WebView.Api.Security can't break Dispatcher.
- Position
- Below the diagonal: WebView.Api.Security uses a module listed above it, which is the healthy direction.
29→9 WebView.Api.Security uses Contracts.Id✕
- Connections
- 1 pair of types, where a type in WebView.Api.Security uses a type in Contracts.Id.
- The types involved
Boson.WebView.Api.Security.SecurityExtension→Boson.Contracts.Id.IdentifiableInterface
- Direction
- WebView.Api.Security uses Contracts.Id, so a change to Contracts.Id can break WebView.Api.Security, while a change to WebView.Api.Security can't break Contracts.Id.
- Position
- Below the diagonal: WebView.Api.Security uses a module listed above it, which is the healthy direction.
29→14 WebView.Api.Security uses Extension✕
- Connections
- 1 pair of types, where a type in WebView.Api.Security uses a type in Extension.
- The types involved
Boson.WebView.Api.Security.SecurityExtension→Boson.Extension.Extension
- Direction
- WebView.Api.Security uses Extension, so a change to Extension can break WebView.Api.Security, while a change to WebView.Api.Security can't break Extension.
- Position
- Below the diagonal: WebView.Api.Security uses a module listed above it, which is the healthy direction.
29→21 WebView.Api.Security uses WebView.Api✕
- Connections
- 1 pair of types, where a type in WebView.Api.Security uses a type in WebView.Api.
- The types involved
Boson.WebView.Api.Security.SecurityInfo→Boson.WebView.Api.LoadedWebViewExtension
- Direction
- WebView.Api.Security uses WebView.Api, so a change to WebView.Api can break WebView.Api.Security, while a change to WebView.Api.Security can't break WebView.Api.
- Position
- Below the diagonal: WebView.Api.Security uses a module listed above it, which is the healthy direction.
29→28 WebView.Api.Security uses WebView.Api.Data✕
- Connections
- 1 pair of types, where a type in WebView.Api.Security uses a type in WebView.Api.Data.
- The types involved
Boson.WebView.Api.Security.SecurityInfo→Boson.WebView.Api.Data.DataRetrieverInterface
- Direction
- WebView.Api.Security uses WebView.Api.Data, so a change to WebView.Api.Data can break WebView.Api.Security, while a change to WebView.Api.Security can't break WebView.Api.Data.
- Position
- Below the diagonal: WebView.Api.Security uses a module listed above it, which is the healthy direction.
29→31 WebView.Api.Security uses WebView part of a loop✕
- Connections
- 1 pair of types, where a type in WebView.Api.Security uses a type in WebView.
- The types involved
Boson.WebView.Api.Security.SecurityInfo→Boson.WebView.WebView
- Direction
- WebView.Api.Security uses WebView, so a change to WebView can break WebView.Api.Security, while a change to WebView.Api.Security can't break WebView.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→25 WebView.Api.WebComponents.Context uses WebView.Api.Scripts✕
- Connections
- 1 pair of types, where a type in WebView.Api.WebComponents.Context uses a type in WebView.Api.Scripts.
- The types involved
Boson.WebView.Api.WebComponents.Context.ReactiveContext→Boson.WebView.Api.Scripts.ScriptEvaluatorInterface
- Direction
- WebView.Api.WebComponents.Context uses WebView.Api.Scripts, so a change to WebView.Api.Scripts can break WebView.Api.WebComponents.Context, while a change to WebView.Api.WebComponents.Context can't break WebView.Api.Scripts.
- Position
- Below the diagonal: WebView.Api.WebComponents.Context uses a module listed above it, which is the healthy direction.
30→28 WebView.Api.WebComponents.Context uses WebView.Api.Data✕
- Connections
- 1 pair of types, where a type in WebView.Api.WebComponents.Context uses a type in WebView.Api.Data.
- The types involved
Boson.WebView.Api.WebComponents.Context.ReactiveContext→Boson.WebView.Api.Data.DataRetrieverInterface
- Direction
- WebView.Api.WebComponents.Context uses WebView.Api.Data, so a change to WebView.Api.Data can break WebView.Api.WebComponents.Context, while a change to WebView.Api.WebComponents.Context can't break WebView.Api.Data.
- Position
- Below the diagonal: WebView.Api.WebComponents.Context uses a module listed above it, which is the healthy direction.
31→1 WebView uses Component.Saucer✕
- Connections
- 1 pair of types, where a type in WebView uses a type in Component.Saucer.
- The types involved
Boson.WebView.WebViewId→Boson.Component.Saucer.SaucerInterface
- Direction
- WebView uses Component.Saucer, so a change to Component.Saucer can break WebView, while a change to WebView can't break Component.Saucer.
- Position
- Below the diagonal: WebView uses a module listed above it, which is the healthy direction.
31→15 WebView uses Shared✕
- Connections
- 1 pair of types, where a type in WebView uses a type in Shared.
- The types involved
Boson.WebView.WebViewId→Boson.Shared.StructPointerId
- Direction
- WebView uses Shared, so a change to Shared can break WebView, while a change to WebView can't break Shared.
- Position
- Below the diagonal: WebView uses a module listed above it, which is the healthy direction.
31→25 WebView uses WebView.Api.Scripts✕
- Connections
- 1 pair of types, where a type in WebView uses a type in WebView.Api.Scripts.
- The types involved
Boson.WebView.WebView→Boson.WebView.Api.Scripts.ScriptsApiInterface
- Direction
- WebView uses WebView.Api.Scripts, so a change to WebView.Api.Scripts can break WebView, while a change to WebView can't break WebView.Api.Scripts.
- Position
- Below the diagonal: WebView uses a module listed above it, which is the healthy direction.
31→26 WebView uses WebView.Api.Bindings✕
- Connections
- 1 pair of types, where a type in WebView uses a type in WebView.Api.Bindings.
- The types involved
Boson.WebView.WebView→Boson.WebView.Api.Bindings.BindingsApiInterface
- Direction
- WebView uses WebView.Api.Bindings, so a change to WebView.Api.Bindings can break WebView, while a change to WebView can't break WebView.Api.Bindings.
- Position
- Below the diagonal: WebView uses a module listed above it, which is the healthy direction.
31→27 WebView uses WebView.Api.Schemes✕
- Connections
- 1 pair of types, where a type in WebView uses a type in WebView.Api.Schemes.
- The types involved
Boson.WebView.WebView→Boson.WebView.Api.Schemes.SchemesProviderInterface
- Direction
- WebView uses WebView.Api.Schemes, so a change to WebView.Api.Schemes can break WebView, while a change to WebView can't break WebView.Api.Schemes.
- Position
- Below the diagonal: WebView uses a module listed above it, which is the healthy direction.
31→28 WebView uses WebView.Api.Data✕
- Connections
- 1 pair of types, where a type in WebView uses a type in WebView.Api.Data.
- The types involved
Boson.WebView.WebView→Boson.WebView.Api.Data.DataRetrieverInterface
- Direction
- WebView uses WebView.Api.Data, so a change to WebView.Api.Data can break WebView, while a change to WebView can't break WebView.Api.Data.
- Position
- Below the diagonal: WebView uses a module listed above it, which is the healthy direction.
31→29 WebView uses WebView.Api.Security✕
- Connections
- 1 pair of types, where a type in WebView uses a type in WebView.Api.Security.
- The types involved
Boson.WebView.WebView→Boson.WebView.Api.Security.SecurityInfoInterface
- Direction
- WebView uses WebView.Api.Security, so a change to WebView.Api.Security can break WebView, while a change to WebView can't break WebView.Api.Security.
- Position
- Below the diagonal: WebView uses a module listed above it, which is the healthy direction.
32→3 WebView.Api.Battery uses Dispatcher✕
- Connections
- 2 pairs of types, where a type in WebView.Api.Battery uses a type in Dispatcher.
- The types involved
Boson.WebView.Api.Battery.BatteryApi→Boson.Dispatcher.EventListenerBoson.WebView.Api.Battery.BatteryExtension→Boson.Dispatcher.EventListener
- Direction
- WebView.Api.Battery uses Dispatcher, so a change to Dispatcher can break WebView.Api.Battery, while a change to WebView.Api.Battery can't break Dispatcher.
- Position
- Below the diagonal: WebView.Api.Battery uses a module listed above it, which is the healthy direction.
32→9 WebView.Api.Battery uses Contracts.Id✕
- Connections
- 1 pair of types, where a type in WebView.Api.Battery uses a type in Contracts.Id.
- The types involved
Boson.WebView.Api.Battery.BatteryExtension→Boson.Contracts.Id.IdentifiableInterface
- Direction
- WebView.Api.Battery uses Contracts.Id, so a change to Contracts.Id can break WebView.Api.Battery, while a change to WebView.Api.Battery can't break Contracts.Id.
- Position
- Below the diagonal: WebView.Api.Battery uses a module listed above it, which is the healthy direction.
32→14 WebView.Api.Battery uses Extension✕
- Connections
- 1 pair of types, where a type in WebView.Api.Battery uses a type in Extension.
- The types involved
Boson.WebView.Api.Battery.BatteryExtension→Boson.Extension.Extension
- Direction
- WebView.Api.Battery uses Extension, so a change to Extension can break WebView.Api.Battery, while a change to WebView.Api.Battery can't break Extension.
- Position
- Below the diagonal: WebView.Api.Battery uses a module listed above it, which is the healthy direction.
32→21 WebView.Api.Battery uses WebView.Api✕
- Connections
- 1 pair of types, where a type in WebView.Api.Battery uses a type in WebView.Api.
- The types involved
Boson.WebView.Api.Battery.BatteryApi→Boson.WebView.Api.LoadedWebViewExtension
- Direction
- WebView.Api.Battery uses WebView.Api, so a change to WebView.Api can break WebView.Api.Battery, while a change to WebView.Api.Battery can't break WebView.Api.
- Position
- Below the diagonal: WebView.Api.Battery uses a module listed above it, which is the healthy direction.
32→25 WebView.Api.Battery uses WebView.Api.Scripts✕
- Connections
- 1 pair of types, where a type in WebView.Api.Battery uses a type in WebView.Api.Scripts.
- The types involved
Boson.WebView.Api.Battery.BatteryApi→Boson.WebView.Api.Scripts.ScriptsApiInterface
- Direction
- WebView.Api.Battery uses WebView.Api.Scripts, so a change to WebView.Api.Scripts can break WebView.Api.Battery, while a change to WebView.Api.Battery can't break WebView.Api.Scripts.
- Position
- Below the diagonal: WebView.Api.Battery uses a module listed above it, which is the healthy direction.
32→26 WebView.Api.Battery uses WebView.Api.Bindings✕
- Connections
- 1 pair of types, where a type in WebView.Api.Battery uses a type in WebView.Api.Bindings.
- The types involved
Boson.WebView.Api.Battery.BatteryApi→Boson.WebView.Api.Bindings.BindingsApiInterface
- Direction
- WebView.Api.Battery uses WebView.Api.Bindings, so a change to WebView.Api.Bindings can break WebView.Api.Battery, while a change to WebView.Api.Battery can't break WebView.Api.Bindings.
- Position
- Below the diagonal: WebView.Api.Battery uses a module listed above it, which is the healthy direction.
32→28 WebView.Api.Battery uses WebView.Api.Data✕
- Connections
- 1 pair of types, where a type in WebView.Api.Battery uses a type in WebView.Api.Data.
- The types involved
Boson.WebView.Api.Battery.BatteryApi→Boson.WebView.Api.Data.DataRetrieverInterface
- Direction
- WebView.Api.Battery uses WebView.Api.Data, so a change to WebView.Api.Data can break WebView.Api.Battery, while a change to WebView.Api.Battery can't break WebView.Api.Data.
- Position
- Below the diagonal: WebView.Api.Battery uses a module listed above it, which is the healthy direction.
32→29 WebView.Api.Battery uses WebView.Api.Security✕
- Connections
- 1 pair of types, where a type in WebView.Api.Battery uses a type in WebView.Api.Security.
- The types involved
Boson.WebView.Api.Battery.BatteryApi→Boson.WebView.Api.Security.SecurityInfoInterface
- Direction
- WebView.Api.Battery uses WebView.Api.Security, so a change to WebView.Api.Security can break WebView.Api.Battery, while a change to WebView.Api.Battery can't break WebView.Api.Security.
- Position
- Below the diagonal: WebView.Api.Battery uses a module listed above it, which is the healthy direction.
32→31 WebView.Api.Battery uses WebView✕
- Connections
- 1 pair of types, where a type in WebView.Api.Battery uses a type in WebView.
- The types involved
Boson.WebView.Api.Battery.BatteryApi→Boson.WebView.WebView
- Direction
- WebView.Api.Battery uses WebView, so a change to WebView can break WebView.Api.Battery, while a change to WebView.Api.Battery can't break WebView.
- Position
- Below the diagonal: WebView.Api.Battery uses a module listed above it, which is the healthy direction.
33→3 WebView.Api.Network uses Dispatcher✕
- Connections
- 2 pairs of types, where a type in WebView.Api.Network uses a type in Dispatcher.
- The types involved
Boson.WebView.Api.Network.NetworkApi→Boson.Dispatcher.EventListenerBoson.WebView.Api.Network.NetworkExtension→Boson.Dispatcher.EventListener
- Direction
- WebView.Api.Network uses Dispatcher, so a change to Dispatcher can break WebView.Api.Network, while a change to WebView.Api.Network can't break Dispatcher.
- Position
- Below the diagonal: WebView.Api.Network uses a module listed above it, which is the healthy direction.
33→9 WebView.Api.Network uses Contracts.Id✕
- Connections
- 1 pair of types, where a type in WebView.Api.Network uses a type in Contracts.Id.
- The types involved
Boson.WebView.Api.Network.NetworkExtension→Boson.Contracts.Id.IdentifiableInterface
- Direction
- WebView.Api.Network uses Contracts.Id, so a change to Contracts.Id can break WebView.Api.Network, while a change to WebView.Api.Network can't break Contracts.Id.
- Position
- Below the diagonal: WebView.Api.Network uses a module listed above it, which is the healthy direction.
33→14 WebView.Api.Network uses Extension✕
- Connections
- 1 pair of types, where a type in WebView.Api.Network uses a type in Extension.
- The types involved
Boson.WebView.Api.Network.NetworkExtension→Boson.Extension.Extension
- Direction
- WebView.Api.Network uses Extension, so a change to Extension can break WebView.Api.Network, while a change to WebView.Api.Network can't break Extension.
- Position
- Below the diagonal: WebView.Api.Network uses a module listed above it, which is the healthy direction.
33→21 WebView.Api.Network uses WebView.Api✕
- Connections
- 1 pair of types, where a type in WebView.Api.Network uses a type in WebView.Api.
- The types involved
Boson.WebView.Api.Network.NetworkApi→Boson.WebView.Api.LoadedWebViewExtension
- Direction
- WebView.Api.Network uses WebView.Api, so a change to WebView.Api can break WebView.Api.Network, while a change to WebView.Api.Network can't break WebView.Api.
- Position
- Below the diagonal: WebView.Api.Network uses a module listed above it, which is the healthy direction.
33→25 WebView.Api.Network uses WebView.Api.Scripts✕
- Connections
- 1 pair of types, where a type in WebView.Api.Network uses a type in WebView.Api.Scripts.
- The types involved
Boson.WebView.Api.Network.NetworkApi→Boson.WebView.Api.Scripts.ScriptsApiInterface
- Direction
- WebView.Api.Network uses WebView.Api.Scripts, so a change to WebView.Api.Scripts can break WebView.Api.Network, while a change to WebView.Api.Network can't break WebView.Api.Scripts.
- Position
- Below the diagonal: WebView.Api.Network uses a module listed above it, which is the healthy direction.
33→26 WebView.Api.Network uses WebView.Api.Bindings✕
- Connections
- 1 pair of types, where a type in WebView.Api.Network uses a type in WebView.Api.Bindings.
- The types involved
Boson.WebView.Api.Network.NetworkApi→Boson.WebView.Api.Bindings.BindingsApiInterface
- Direction
- WebView.Api.Network uses WebView.Api.Bindings, so a change to WebView.Api.Bindings can break WebView.Api.Network, while a change to WebView.Api.Network can't break WebView.Api.Bindings.
- Position
- Below the diagonal: WebView.Api.Network uses a module listed above it, which is the healthy direction.
33→28 WebView.Api.Network uses WebView.Api.Data✕
- Connections
- 1 pair of types, where a type in WebView.Api.Network uses a type in WebView.Api.Data.
- The types involved
Boson.WebView.Api.Network.NetworkApi→Boson.WebView.Api.Data.DataRetrieverInterface
- Direction
- WebView.Api.Network uses WebView.Api.Data, so a change to WebView.Api.Data can break WebView.Api.Network, while a change to WebView.Api.Network can't break WebView.Api.Data.
- Position
- Below the diagonal: WebView.Api.Network uses a module listed above it, which is the healthy direction.
33→31 WebView.Api.Network uses WebView✕
- Connections
- 1 pair of types, where a type in WebView.Api.Network uses a type in WebView.
- The types involved
Boson.WebView.Api.Network.NetworkApi→Boson.WebView.WebView
- Direction
- WebView.Api.Network uses WebView, so a change to WebView can break WebView.Api.Network, while a change to WebView.Api.Network can't break WebView.
- Position
- Below the diagonal: WebView.Api.Network uses a module listed above it, which is the healthy direction.
34→1 Window uses Component.Saucer✕
- Connections
- 1 pair of types, where a type in Window uses a type in Component.Saucer.
- The types involved
Boson.Window.WindowId→Boson.Component.Saucer.SaucerInterface
- Direction
- Window uses Component.Saucer, so a change to Component.Saucer can break Window, while a change to Window can't break Component.Saucer.
- Position
- Below the diagonal: Window uses a module listed above it, which is the healthy direction.
34→15 Window uses Shared✕
- Connections
- 1 pair of types, where a type in Window uses a type in Shared.
- The types involved
Boson.Window.WindowId→Boson.Shared.StructPointerId
- Direction
- Window uses Shared, so a change to Shared can break Window, while a change to Window can't break Shared.
- Position
- Below the diagonal: Window uses a module listed above it, which is the healthy direction.
34→31 Window uses WebView✕
- Connections
- 1 pair of types, where a type in Window uses a type in WebView.
- The types involved
Boson.Window.WindowCreateInfo→Boson.WebView.WebViewCreateInfo
- Direction
- Window uses WebView, so a change to WebView can break Window, while a change to Window can't break WebView.
- Position
- Below the diagonal: Window uses a module listed above it, which is the healthy direction.
35→1 Boson uses Component.Saucer✕
- Connections
- 1 pair of types, where a type in Boson uses a type in Component.Saucer.
- The types involved
Boson.ApplicationId→Boson.Component.Saucer.SaucerInterface
- Direction
- Boson uses Component.Saucer, so a change to Component.Saucer can break Boson, while a change to Boson can't break Component.Saucer.
- Position
- Below the diagonal: Boson uses a module listed above it, which is the healthy direction.
35→15 Boson uses Shared✕
- Connections
- 1 pair of types, where a type in Boson uses a type in Shared.
- The types involved
Boson.ApplicationId→Boson.Shared.StructPointerId
- Direction
- Boson uses Shared, so a change to Shared can break Boson, while a change to Boson can't break Shared.
- Position
- Below the diagonal: Boson uses a module listed above it, which is the healthy direction.
35→17 Boson uses Api.OperatingSystem✕
- Connections
- 1 pair of types, where a type in Boson uses a type in Api.OperatingSystem.
- The types involved
Boson.Application→Boson.Api.OperatingSystem.OperatingSystemInfoInterface
- Direction
- Boson uses Api.OperatingSystem, so a change to Api.OperatingSystem can break Boson, while a change to Boson can't break Api.OperatingSystem.
- Position
- Below the diagonal: Boson uses a module listed above it, which is the healthy direction.
35→23 Boson uses Api.Dialog✕
- Connections
- 1 pair of types, where a type in Boson uses a type in Api.Dialog.
- The types involved
Boson.Application→Boson.Api.Dialog.DialogApiInterface
- Direction
- Boson uses Api.Dialog, so a change to Api.Dialog can break Boson, while a change to Boson can't break Api.Dialog.
- Position
- Below the diagonal: Boson uses a module listed above it, which is the healthy direction.
35→34 Boson uses Window✕
- Connections
- 1 pair of types, where a type in Boson uses a type in Window.
- The types involved
Boson.ApplicationCreateInfo→Boson.Window.WindowCreateInfo
- Direction
- Boson uses Window, so a change to Window can break Boson, while a change to Boson can't break Window.
- Position
- Below the diagonal: Boson uses a module listed above it, which is the healthy direction.
36→3 Api.Console uses Dispatcher✕
- Connections
- 1 pair of types, where a type in Api.Console uses a type in Dispatcher.
- The types involved
Boson.Api.Console.ConsoleExtension→Boson.Dispatcher.EventListener
- Direction
- Api.Console uses Dispatcher, so a change to Dispatcher can break Api.Console, while a change to Api.Console can't break Dispatcher.
- Position
- Below the diagonal: Api.Console uses a module listed above it, which is the healthy direction.
36→9 Api.Console uses Contracts.Id✕
- Connections
- 1 pair of types, where a type in Api.Console uses a type in Contracts.Id.
- The types involved
Boson.Api.Console.ConsoleExtension→Boson.Contracts.Id.IdentifiableInterface
- Direction
- Api.Console uses Contracts.Id, so a change to Contracts.Id can break Api.Console, while a change to Api.Console can't break Contracts.Id.
- Position
- Below the diagonal: Api.Console uses a module listed above it, which is the healthy direction.
36→14 Api.Console uses Extension✕
- Connections
- 1 pair of types, where a type in Api.Console uses a type in Extension.
- The types involved
Boson.Api.Console.ConsoleExtension→Boson.Extension.Extension
- Direction
- Api.Console uses Extension, so a change to Extension can break Api.Console, while a change to Api.Console can't break Extension.
- Position
- Below the diagonal: Api.Console uses a module listed above it, which is the healthy direction.
36→17 Api.Console uses Api.OperatingSystem✕
- Connections
- 1 pair of types, where a type in Api.Console uses a type in Api.OperatingSystem.
- The types involved
Boson.Api.Console.ConsoleExtension→Boson.Api.OperatingSystem.OperatingSystemInfoInterface
- Direction
- Api.Console uses Api.OperatingSystem, so a change to Api.OperatingSystem can break Api.Console, while a change to Api.Console can't break Api.OperatingSystem.
- Position
- Below the diagonal: Api.Console uses a module listed above it, which is the healthy direction.
36→35 Api.Console uses Boson✕
- Connections
- 1 pair of types, where a type in Api.Console uses a type in Boson.
- The types involved
Boson.Api.Console.ConsoleExtension→Boson.Application
- Direction
- Api.Console uses Boson, so a change to Boson can break Api.Console, while a change to Api.Console can't break Boson.
- Position
- Below the diagonal: Api.Console uses a module listed above it, which is the healthy direction.
37→3 Api.QuitOnClose uses Dispatcher✕
- Connections
- 1 pair of types, where a type in Api.QuitOnClose uses a type in Dispatcher.
- The types involved
Boson.Api.QuitOnClose.QuitOnCloseExtension→Boson.Dispatcher.EventListener
- Direction
- Api.QuitOnClose uses Dispatcher, so a change to Dispatcher can break Api.QuitOnClose, while a change to Api.QuitOnClose can't break Dispatcher.
- Position
- Below the diagonal: Api.QuitOnClose uses a module listed above it, which is the healthy direction.
37→9 Api.QuitOnClose uses Contracts.Id✕
- Connections
- 1 pair of types, where a type in Api.QuitOnClose uses a type in Contracts.Id.
- The types involved
Boson.Api.QuitOnClose.QuitOnCloseExtension→Boson.Contracts.Id.IdentifiableInterface
- Direction
- Api.QuitOnClose uses Contracts.Id, so a change to Contracts.Id can break Api.QuitOnClose, while a change to Api.QuitOnClose can't break Contracts.Id.
- Position
- Below the diagonal: Api.QuitOnClose uses a module listed above it, which is the healthy direction.
37→14 Api.QuitOnClose uses Extension✕
- Connections
- 1 pair of types, where a type in Api.QuitOnClose uses a type in Extension.
- The types involved
Boson.Api.QuitOnClose.QuitOnCloseExtension→Boson.Extension.Extension
- Direction
- Api.QuitOnClose uses Extension, so a change to Extension can break Api.QuitOnClose, while a change to Api.QuitOnClose can't break Extension.
- Position
- Below the diagonal: Api.QuitOnClose uses a module listed above it, which is the healthy direction.
37→35 Api.QuitOnClose uses Boson✕
- Connections
- 2 pairs of types, where a type in Api.QuitOnClose uses a type in Boson.
- The types involved
Boson.Api.QuitOnClose.QuitOnCloseExtension→Boson.ApplicationBoson.Api.QuitOnClose.QuitOnCloseHandler→Boson.Application
- Direction
- Api.QuitOnClose uses Boson, so a change to Boson can break Api.QuitOnClose, while a change to Api.QuitOnClose can't break Boson.
- Position
- Below the diagonal: Api.QuitOnClose uses a module listed above it, which is the healthy direction.
38→3 Event uses Dispatcher✕
- Connections
- 2 pairs of types, where a type in Event uses a type in Dispatcher.
- The types involved
Boson.Event.ApplicationEvent→Boson.Dispatcher.EventBoson.Event.ApplicationIntention→Boson.Dispatcher.Intention
- Direction
- Event uses Dispatcher, so a change to Dispatcher can break Event, while a change to Event can't break Dispatcher.
- Position
- Below the diagonal: Event uses a module listed above it, which is the healthy direction.
38→35 Event uses Boson✕
- Connections
- 2 pairs of types, where a type in Event uses a type in Boson.
- The types involved
Boson.Event.ApplicationEvent→Boson.ApplicationBoson.Event.ApplicationIntention→Boson.Application
- Direction
- Event uses Boson, so a change to Boson can break Event, while a change to Event can't break Boson.
- Position
- Below the diagonal: Event uses a module listed above it, which is the healthy direction.
39→25 WebView.Api.WebComponents.Internal uses WebView.Api.Scripts✕
- Connections
- 1 pair of types, where a type in WebView.Api.WebComponents.Internal uses a type in WebView.Api.Scripts.
- The types involved
Boson.WebView.Api.WebComponents.Internal.WebViewComponentInstances→Boson.WebView.Api.Scripts.ScriptsApiInterface
- Direction
- WebView.Api.WebComponents.Internal uses WebView.Api.Scripts, so a change to WebView.Api.Scripts can break WebView.Api.WebComponents.Internal, while a change to WebView.Api.WebComponents.Internal can't break WebView.Api.Scripts.
- Position
- Below the diagonal: WebView.Api.WebComponents.Internal uses a module listed above it, which is the healthy direction.
39→28 WebView.Api.WebComponents.Internal uses WebView.Api.Data✕
- Connections
- 1 pair of types, where a type in WebView.Api.WebComponents.Internal uses a type in WebView.Api.Data.
- The types involved
Boson.WebView.Api.WebComponents.Internal.WebViewComponentInstances→Boson.WebView.Api.Data.DataRetrieverInterface
- Direction
- WebView.Api.WebComponents.Internal uses WebView.Api.Data, so a change to WebView.Api.Data can break WebView.Api.WebComponents.Internal, while a change to WebView.Api.WebComponents.Internal can't break WebView.Api.Data.
- Position
- Below the diagonal: WebView.Api.WebComponents.Internal uses a module listed above it, which is the healthy direction.
39→30 WebView.Api.WebComponents.Internal uses WebView.Api.WebComponents.Context✕
- Connections
- 1 pair of types, where a type in WebView.Api.WebComponents.Internal uses a type in WebView.Api.WebComponents.Context.
- The types involved
Boson.WebView.Api.WebComponents.Internal.WebViewComponentInstances→Boson.WebView.Api.WebComponents.Context.ReactiveContext
- Direction
- WebView.Api.WebComponents.Internal uses WebView.Api.WebComponents.Context, so a change to WebView.Api.WebComponents.Context can break WebView.Api.WebComponents.Internal, while a change to WebView.Api.WebComponents.Internal can't break WebView.Api.WebComponents.Context.
- Position
- Below the diagonal: WebView.Api.WebComponents.Internal uses a module listed above it, which is the healthy direction.
39→31 WebView.Api.WebComponents.Internal uses WebView✕
- Connections
- 1 pair of types, where a type in WebView.Api.WebComponents.Internal uses a type in WebView.
- The types involved
Boson.WebView.Api.WebComponents.Internal.WebViewComponentInstances→Boson.WebView.WebView
- Direction
- WebView.Api.WebComponents.Internal uses WebView, so a change to WebView can break WebView.Api.WebComponents.Internal, while a change to WebView.Api.WebComponents.Internal can't break WebView.
- Position
- Below the diagonal: WebView.Api.WebComponents.Internal uses a module listed above it, which is the healthy direction.
39→35 WebView.Api.WebComponents.Internal uses Boson✕
- Connections
- 1 pair of types, where a type in WebView.Api.WebComponents.Internal uses a type in Boson.
- The types involved
Boson.WebView.Api.WebComponents.Internal.WebViewComponentBuilder→Boson.Application
- Direction
- WebView.Api.WebComponents.Internal uses Boson, so a change to Boson can break WebView.Api.WebComponents.Internal, while a change to WebView.Api.WebComponents.Internal can't break Boson.
- Position
- Below the diagonal: WebView.Api.WebComponents.Internal uses a module listed above it, which is the healthy direction.
40→3 WebView.Api.WebComponents uses Dispatcher✕
- Connections
- 2 pairs of types, where a type in WebView.Api.WebComponents uses a type in Dispatcher.
- The types involved
Boson.WebView.Api.WebComponents.WebComponentsApi→Boson.Dispatcher.EventListenerBoson.WebView.Api.WebComponents.WebComponentsExtension→Boson.Dispatcher.EventListener
- Direction
- WebView.Api.WebComponents uses Dispatcher, so a change to Dispatcher can break WebView.Api.WebComponents, while a change to WebView.Api.WebComponents can't break Dispatcher.
- Position
- Below the diagonal: WebView.Api.WebComponents uses a module listed above it, which is the healthy direction.
40→9 WebView.Api.WebComponents uses Contracts.Id✕
- Connections
- 1 pair of types, where a type in WebView.Api.WebComponents uses a type in Contracts.Id.
- The types involved
Boson.WebView.Api.WebComponents.WebComponentsExtension→Boson.Contracts.Id.IdentifiableInterface
- Direction
- WebView.Api.WebComponents uses Contracts.Id, so a change to Contracts.Id can break WebView.Api.WebComponents, while a change to WebView.Api.WebComponents can't break Contracts.Id.
- Position
- Below the diagonal: WebView.Api.WebComponents uses a module listed above it, which is the healthy direction.
40→14 WebView.Api.WebComponents uses Extension✕
- Connections
- 1 pair of types, where a type in WebView.Api.WebComponents uses a type in Extension.
- The types involved
Boson.WebView.Api.WebComponents.WebComponentsExtension→Boson.Extension.Extension
- Direction
- WebView.Api.WebComponents uses Extension, so a change to Extension can break WebView.Api.WebComponents, while a change to WebView.Api.WebComponents can't break Extension.
- Position
- Below the diagonal: WebView.Api.WebComponents uses a module listed above it, which is the healthy direction.
40→21 WebView.Api.WebComponents uses WebView.Api✕
- Connections
- 1 pair of types, where a type in WebView.Api.WebComponents uses a type in WebView.Api.
- The types involved
Boson.WebView.Api.WebComponents.WebComponentsApi→Boson.WebView.Api.LoadedWebViewExtension
- Direction
- WebView.Api.WebComponents uses WebView.Api, so a change to WebView.Api can break WebView.Api.WebComponents, while a change to WebView.Api.WebComponents can't break WebView.Api.
- Position
- Below the diagonal: WebView.Api.WebComponents uses a module listed above it, which is the healthy direction.
40→25 WebView.Api.WebComponents uses WebView.Api.Scripts✕
- Connections
- 2 pairs of types, where a type in WebView.Api.WebComponents uses a type in WebView.Api.Scripts.
- The types involved
Boson.WebView.Api.WebComponents.WebComponent→Boson.WebView.Api.Scripts.ScriptEvaluatorInterfaceBoson.WebView.Api.WebComponents.WebComponentsApi→Boson.WebView.Api.Scripts.ScriptsApiInterface
- Direction
- WebView.Api.WebComponents uses WebView.Api.Scripts, so a change to WebView.Api.Scripts can break WebView.Api.WebComponents, while a change to WebView.Api.WebComponents can't break WebView.Api.Scripts.
- Position
- Below the diagonal: WebView.Api.WebComponents uses a module listed above it, which is the healthy direction.
40→26 WebView.Api.WebComponents uses WebView.Api.Bindings✕
- Connections
- 1 pair of types, where a type in WebView.Api.WebComponents uses a type in WebView.Api.Bindings.
- The types involved
Boson.WebView.Api.WebComponents.WebComponentsApi→Boson.WebView.Api.Bindings.BindingsApiInterface
- Direction
- WebView.Api.WebComponents uses WebView.Api.Bindings, so a change to WebView.Api.Bindings can break WebView.Api.WebComponents, while a change to WebView.Api.WebComponents can't break WebView.Api.Bindings.
- Position
- Below the diagonal: WebView.Api.WebComponents uses a module listed above it, which is the healthy direction.
40→28 WebView.Api.WebComponents uses WebView.Api.Data✕
- Connections
- 3 pairs of types, where a type in WebView.Api.WebComponents uses a type in WebView.Api.Data.
- The types involved
Boson.WebView.Api.WebComponents.WebComponent→Boson.WebView.Api.Data.AsyncDataRetrieverInterfaceBoson.WebView.Api.WebComponents.WebComponent→Boson.WebView.Api.Data.SyncDataRetrieverInterfaceBoson.WebView.Api.WebComponents.WebComponentsApi→Boson.WebView.Api.Data.DataRetrieverInterface
- Direction
- WebView.Api.WebComponents uses WebView.Api.Data, so a change to WebView.Api.Data can break WebView.Api.WebComponents, while a change to WebView.Api.WebComponents can't break WebView.Api.Data.
- Position
- Below the diagonal: WebView.Api.WebComponents uses a module listed above it, which is the healthy direction.
40→30 WebView.Api.WebComponents uses WebView.Api.WebComponents.Context✕
- Connections
- 3 pairs of types, where a type in WebView.Api.WebComponents uses a type in WebView.Api.WebComponents.Context.
- The types involved
Boson.WebView.Api.WebComponents.WebComponent→Boson.WebView.Api.WebComponents.Context.MutableClassListInterfaceBoson.WebView.Api.WebComponents.WebComponent→Boson.WebView.Api.WebComponents.Context.MutableContentProviderInterfaceBoson.WebView.Api.WebComponents.WebComponent→Boson.WebView.Api.WebComponents.Context.ReactiveContext
- Direction
- WebView.Api.WebComponents uses WebView.Api.WebComponents.Context, so a change to WebView.Api.WebComponents.Context can break WebView.Api.WebComponents, while a change to WebView.Api.WebComponents can't break WebView.Api.WebComponents.Context.
- Position
- Below the diagonal: WebView.Api.WebComponents uses a module listed above it, which is the healthy direction.
40→31 WebView.Api.WebComponents uses WebView✕
- Connections
- 2 pairs of types, where a type in WebView.Api.WebComponents uses a type in WebView.
- The types involved
Boson.WebView.Api.WebComponents.WebComponent→Boson.WebView.WebViewBoson.WebView.Api.WebComponents.WebComponentsApi→Boson.WebView.WebView
- Direction
- WebView.Api.WebComponents uses WebView, so a change to WebView can break WebView.Api.WebComponents, while a change to WebView.Api.WebComponents can't break WebView.
- Position
- Below the diagonal: WebView.Api.WebComponents uses a module listed above it, which is the healthy direction.
40→39 WebView.Api.WebComponents uses WebView.Api.WebComponents.Internal✕
- Connections
- 2 pairs of types, where a type in WebView.Api.WebComponents uses a type in WebView.Api.WebComponents.Internal.
- The types involved
Boson.WebView.Api.WebComponents.WebComponentsApi→Boson.WebView.Api.WebComponents.Internal.WebViewComponentBuilderBoson.WebView.Api.WebComponents.WebComponentsApi→Boson.WebView.Api.WebComponents.Internal.WebViewComponentInstances
- Direction
- WebView.Api.WebComponents uses WebView.Api.WebComponents.Internal, so a change to WebView.Api.WebComponents.Internal can break WebView.Api.WebComponents, while a change to WebView.Api.WebComponents can't break WebView.Api.WebComponents.Internal.
- Position
- Below the diagonal: WebView.Api.WebComponents uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 22 | High / Critical |
| A05:2025 — Injection | 12 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them; Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with CompatibilityTest.php.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json. | +5.0 pts | Low | ADR Quality |
| Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with CompatibilityTest.php. | +2.9 pts | Low | Test Quality |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +4.7 pts | Medium | Architecture documentation |
| Resolve the 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.7 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 4 REDACTED finding(s) charged to Static Analysis (SAST) — the other 6 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. | +1.6 pts | Low | Static Analysis (SAST) |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +1.1 pts | Low | Static Analysis (SAST) |
| Resolve the 12 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (12). | +1.4 pts | Medium | Dependency Vulnerabilities |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.6 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.5 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| libs/component/runtime/src/Application.php | 6.3 | Mixed | Code Duplication: Duplicated block (8 lines × 3) |
| libs/component/runtime/src/Api/Dialog/SaucerDialogApi.php | 7.4 | Near-clean | Code Duplication: Edited copy of a member (23 corresponding lines) |
| libs/component/runtime/src/WebView/Api/LifecycleEvents/LifecycleEventsListener.php | 7.4 | Near-clean | Code Duplication: Edited copy of a member (24 corresponding lines) |
| libs/component/cpu-info/src/Factory/Driver/WindowsRegistryDriver.php | 7.8 | Near-clean | Code Duplication: Edited copy of a member (19 corresponding lines) |
| libs/component/compiler/src/Workflow/Task/CreateBoxConfigTask.php | 7.8 | Near-clean | Code Duplication: Edited copy of a member (19 corresponding lines) |
| libs/component/cpu-info/src/Factory/CentralProcessorFactory.php | 7.8 | Near-clean | Code Duplication: Edited copy of a member (4 corresponding lines) |
| libs/component/http/src/Exception/InvalidHeaderNameException.php | 7.8 | Near-clean | Code Duplication: Duplicated block (21 lines × 2) |
| REDACTED | 7.9 | Near-clean | Supply-chain Provenance & Signing: REDACTED |
| libs/contracts/http-contracts/tests/CompatibilityTest.php | 8.0 | Near-clean | Test Quality: No assertions (empty test): testInvalidComponentArgumentExceptionInterfaceCompatibility |
| libs/component/runtime/src/Window/Manager/WindowHandlerFactory.php | 8.2 | Near-clean | Explicit Debt: TodoComment |
| libs/component/os-info/src/Factory/Driver/WindowsRegistryDriver.php | 8.2 | Near-clean | Explicit Debt: TodoComment |
| libs/extension/webview-ext-web-components/src/WebComponentsApi.php | 8.5 | Near-clean | Cognitive Complexity: WebComponentsApi.add (cognitive 28) |
| libs/bridge/symfony-bundle/src/DependencyInjection/BosonExtension.php | 8.5 | Near-clean | Code Duplication: Edited copy of a member (17 corresponding lines) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 52 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 — 52 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, 158 of 173 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.php) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 30 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository declares a composer.json but commits no composer.lock this pass can read, so the set of packages it installs is not on disk: its composer.json states version CONSTRAINTS, and Composer's guidance is that a library leaves the lock uncommitted. Producing the graph needs Composer's solver, which this pass does not run, and grading whichever release happens to be newest today would be a verdict about a dependency graph nobody resolved. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- 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 (7 contributor(s) across 777 commit(s) sampled, automation and bot accounts excluded). One of them holds 95% of the history; the other 6 hold 0.8% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (composer.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `.php-cs-fixer.php`, `libs/bridge/http-bridge/src/HttpAdapter.php`, `libs/bridge/laravel-provider/src/Worker.php`, `libs/bridge/spiral-bridge/src/Bootloader/BosonBootloader.php`, `libs/bridge/spiral-bridge/src/Bootloader/HttpBootloader.php`, … (+386 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Laravel's service container and Spiral's container and Symfony DependencyInjection and a PSR-11 container (Psr\Container) and an unrecognised PHP container, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's , PHP is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's , PHP is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- P7 Outbound HTTP resilience — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check recognises outbound HTTP clients, their timeouts and resilience policies, and service entry points in .NET, Go, JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang. No service entry point was found in the JavaScript/TypeScript, PHP source it does read, and the rest of this repository's production source is , which it does not read yet — the service may well be there — a gap in this analyzer's language reach, not a finding about the code.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- 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.
- 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. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being LinuxProcCpuInfoDriver.tryGetInstructionSets at 18 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: libs/component/cpu-info/src/Factory/Driver/LinuxProcCpuInfoDriver.php (LinuxProcCpuInfoDriver.tryGetInstructionSets at 18). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was WebComponentsApi.add at 28.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with WebComponentsApi.add (cognitive 28). — Refactoring it lifts Cognitive Complexity from 9.3 to about 10.0/10.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
14 duplicated block group(s) detected. 2.8 % of the production lines (1,025 of 36,645) are in a reported copy. A further 23 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 3 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with SaucerDialogApi.php, WebViewHandlerFactory.php, CreateFileTask.php. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with SaucerDialogApi.php, CentralProcessorFactory.php, AVX2Detector.php. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with EnvArchitectureFactory.php, EnvDriver.php, WindowsRegistryDriver.php. — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
30 production modules (Composer), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 3 module(s) off the main sequence.
What to do
- Resolve the 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
D6 · Cohesion (LCOM4)
4 of 115 classes have LCOM4 above 3.
What to do
- Resolve the 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with Configuration.php, Application.php, HeadersMap.php. — One of this dimension's main actionable groups (4 warning-level).
D10 · Test Quality
0 skipped, 63 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 672 tests.
What to do
- Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with CompatibilityTest.php. — One of this dimension's main actionable groups (1 issue-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
2 deducted task-comment markers across 36645 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.
What to do
- Resolve the 2 TodoComment finding(s) in Explicit Debt — start with WindowHandlerFactory.php, WindowsRegistryDriver.php. — One of this dimension's main actionable groups (2 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 31 document(s) read across 3 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 31 build units (Composer, npm) flagged as possibly oversized/incoherent.
D27 · Navigability
39 % of calls cross a namespace and 7 % go through an interface, but 67 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
12 finding(s): 0 critical, 12 high, 0 medium, 0 low. 6 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 392 file(s) — `REDACTED`, `.php-cs-fixer.php` (line 284), `libs/bridge/http-bridge/src/HttpAdapter.php` (line 35), `libs/bridge/laravel-provider/src/Worker.php` (line 31, line 32), `libs/bridge/spiral-bridge/src/Bootloader/BosonBootloader.php` (line 42), … (+387 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 4 REDACTED finding(s) charged to Static Analysis (SAST) — the other 6 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (10 issue-level, 4 of them charged here).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D30 · Dependency Vulnerabilities
12 finding(s): 0 critical, 12 high, 0 medium, 0 low.
What to do
- Resolve the 12 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (12). — One of this dimension's main actionable groups (12 issue-level).
D34 · Knowledge Freshness
2 of 124 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is libs/bridge/spiral-bridge/src/Bootloader/HttpBootloader.php. Counted over 124 of the 736 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: Application.php↔DataExtension.php 64%; Application.php↔SchemesExtension.php 58%; DataExtension.php↔SchemesExtension.php 55%
What to do
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with DataExtension.php, WebView.php, WebViewComponentInstances.php. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with Application.php. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 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).
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 30 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
- `SaucerInterface` declares 189 methods: `new`, `cast`, `boson_version`, `boson_get_backend`, `boson_get_backend_str`, `boson_error_code_canceled`, `saucer_loop_free`, `saucer_loop_new`, `saucer_loop_run`, `saucer_loop_iteration`, `saucer_loop_quit`, `saucer_picker_options_new`, `saucer_picker_options_free`, `saucer_picker_options_set_initial`, `saucer_picker_options_set_filters`, `saucer_desktop_free`, `saucer_desktop_new`, `saucer_desktop_mouse_position`, `saucer_picker_pick_file`, `saucer_picker_pick_folder`, `saucer_picker_pick_files`, `saucer_picker_save`, `saucer_desktop_open`, `saucer_screen_free`, `saucer_screen_name`, `saucer_screen_size`, `saucer_screen_position`, `saucer_application_options_free`, `saucer_application_options_new`, `saucer_application_options_set_argc`, `saucer_application_options_set_argv`, `saucer_application_options_set_quit_on_last_window_closed`, `saucer_application_free`, `saucer_application_new`, `saucer_application_thread_safe`, `saucer_application_screens`, `saucer_application_post`, `saucer_application_quit`, `saucer_application_run`, `saucer_application_on`, and 149 more. Counted over its public instance methods, once per name; constants and static methods are not counted. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — libs/component/saucer/resources/stubs/saucer.stub.php:69
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
- 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
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `libs/component/compiler`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- `libs/component/runtime/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — libs/component/runtime/package.json:6
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
R1 · Type Safety
R10 · Code Duplication
R2 · Cyclomatic Complexity
R3 · Large Files
R5 · Dependency Freshness
R6 · Tooling
- test ✗ · lint ✓ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add a test runner (vitest / jest / playwright) as package.json scripts and run them in CI.
R7 · Dead Code
- No runtime consumer imports this binding — the only demand on it comes from a type-position import of its module, which asks for the module's type surface rather than for this name. If the value is genuinely unneeded, remove it; if a consumer needs only its TYPE, export that type (e.g. `export type X = typeof x`) and drop the value. A value export — a const, a function, a class — cannot itself be rewritten as `export type`. (×3) — libs/component/runtime/resources/src/id-generator/IdGeneratorInterface.ts:4, libs/component/runtime/resources/src/rpc/BosonRpcInterface.ts:9, libs/component/runtime/resources/src/rpc/BosonRpcResponderInterface.ts:3
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
R9 · Circular Imports
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X3 · Exception handling
- `catch (\Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×4) — libs/component/runtime/src/WebView/Api/Bindings/BindingsApi.php:94, libs/component/os-info/src/Factory/Driver/WindowsRegistryDriver.php:218, libs/component/os-info/src/Factory/Driver/WindowsRegistryDriver.php:231, …
What to do
- Swallowed exception (caught, then discarded)
X4 · Structured logging
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 88.4 | Exemplary | Solid. |
| Architecture | 90.3 | Exemplary | Strongest area. |
| Maturity | 59.7 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 62.0 | Adequate | Acceptable, with room to improve. |
| Security | 58.8 | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 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 analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route (no Laravel Route::…, no Symfony #[Route], no Filament panel, no WordPress REST route or AJAX action). Access control is therefore N/A here — a Composer library is authorized by the application that mounts it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone_number, …) or stored credential in a Laravel migration, an Eloquent model's $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D11 Test Reliability — Test reliability not included — no .php test runner
- D12 Dependency Hygiene — Not scored — 30 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — Composer package licences not graded — this repository commits no composer.lock and this pass does not run Composer's solver
- 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.
- D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .php source were not judged.
- D25 ADR Conformance — no ADRs to check
- 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) — 391 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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 — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 158 value object(s); 24 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 31 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (environment variable 1); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P8 Schema migrations — Laravel is declared, but this repository defines no table or model of its own, so there is no database schema here for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — the JS/TS workspace (9 production file(s)) has no JavaScript/TypeScript test, but it is 1.21% of this repository's production source and the other 98.79% carries 7,055 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X12 Unreachable branch — X12 reached only 1% of this repository's production lines — php (36,136 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — X17 reached only 1% of this repository's production lines — php (36,136 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's PHP was read and makes no request a caller can cancel (amphp's HttpClient or connect) — synchronous PHP offers its callers no cancellation to take
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — 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. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- 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
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 25 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
- No assertions (empty test): testInvalidComponentArgumentExceptionInterfaceCompatibility libs/contracts/http-contracts/tests/CompatibilityTest.php:506
Serious — 62 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Low cohesion: Configuration (LCOM4 11) libs/component/compiler/src/Configuration.php:13
- Low cohesion: Application (LCOM4 5) libs/component/runtime/src/Application.php:37
- Low cohesion: HeadersMap (LCOM4 4) libs/component/http/src/Component/HeadersMap.php:26
- Low cohesion: Request (LCOM4 4) libs/component/http/src/Request.php:38
- Swallowed exception (caught, then discarded) libs/component/runtime/src/WebView/Api/Bindings/BindingsApi.php:94
- Swallowed exception (caught, then discarded) libs/component/os-info/src/Factory/Driver/WindowsRegistryDriver.php:218
- Swallowed exception (caught, then discarded) libs/component/os-info/src/Factory/Driver/WindowsRegistryDriver.php:231
- Swallowed exception (caught, then discarded) libs/component/cpu-info/src/Factory/Driver/WindowsRegistryDriver.php:79
- Change coupling: DataExtension.php ↔ SchemesExtension.php libs/component/runtime/src/WebView/Api/Data/DataExtension.php:1
- Change coupling: WebView.php ↔ WindowManager.php libs/component/runtime/src/WebView/WebView.php:1
- Change coupling: WebViewComponentInstances.php ↔ WebComponentsExtension.php libs/extension/webview-ext-web-components/src/Internal/WebViewComponentInstances.php:1
- Edited copy of a member (13 corresponding lines) libs/component/runtime/src/Api/Dialog/SaucerDialogApi.php:166
- Edited copy of a member (13 corresponding lines) libs/component/runtime/src/WebView/Manager/WebViewHandlerFactory.php:62
- Edited copy of a member (13 corresponding lines) libs/component/compiler/src/Workflow/Task/CreateFileTask.php:46
- Duplicated block (13 lines × 2) libs/component/runtime/src/Api/Dialog/SaucerDialogApi.php:91
- Duplicated block (13 lines × 2) libs/component/cpu-info/src/Factory/CentralProcessorFactory.php:69
- Duplicated block (13 lines × 2) libs/component/cpu-info/src/Factory/Driver/CpuId/AVX2Detector.php:15
- Duplicated block (9 lines × 2) libs/component/cpu-info/src/Architecture/Factory/EnvArchitectureFactory.php:41
- Duplicated block (9 lines × 2) libs/component/cpu-info/src/Factory/Driver/EnvDriver.php:113
- Duplicated block (9 lines × 2) libs/component/cpu-info/src/Factory/Driver/WindowsRegistryDriver.php:75
- Off the main sequence: boson-php/saucer
- Off the main sequence: boson-php/http
- Off the main sequence: boson-php/weak-types
- TodoComment libs/component/runtime/src/Window/Manager/WindowHandlerFactory.php:67
- TodoComment libs/component/os-info/src/Factory/Driver/WindowsRegistryDriver.php:136
- Edited copy of a member (19 corresponding lines) libs/component/cpu-info/src/Factory/Driver/WindowsRegistryDriver.php:93
- Edited copy of a member (19 corresponding lines) libs/component/compiler/src/Workflow/Task/CreateBoxConfigTask.php:25
- Edited copy of a member (7 corresponding lines) libs/extension/webview-ext-battery/src/BatteryExtension.php:34
- Edited copy of a member (7 corresponding lines) libs/component/runtime/src/Window/Size.php:23
- Edited copy of a member (10 corresponding lines) libs/component/compiler/src/Workflow/Task/DownloadTask.php:42
- Edited copy of a member (10 corresponding lines) libs/component/compiler/src/Workflow/Task/ApplyPermissionsTask.php:58
- Duplicated block (8 lines × 3) libs/component/http/src/Exception/InvalidHeaderNameException.php:11
- Duplicated block (8 lines × 3) libs/component/runtime/src/Application.php:502
- WebComponentsApi.add (cognitive 28) libs/extension/webview-ext-web-components/src/WebComponentsApi.php:281
- Change-coupling hub: Application.php → saucer.stub.php, DataExtension.php, SchemesExtension.php libs/component/runtime/src/Application.php
- REDACTED
- Edited copy of a member (23 corresponding lines) libs/component/runtime/src/Api/Dialog/SaucerDialogApi.php:91
- Edited copy of a member (24 corresponding lines) libs/component/runtime/src/WebView/Api/LifecycleEvents/LifecycleEventsListener.php:258
- Edited copy of a member (17 corresponding lines) libs/bridge/symfony-bundle/src/DependencyInjection/BosonExtension.php:201
- Edited copies of one member (3 members, 22+ corresponding lines) libs/component/runtime/src/WebView/Api/LifecycleEvents/LifecycleEventsListener.php:116
- Edited copies of one member (4 members, 11+ corresponding lines) libs/component/runtime/src/WebView/Api/LifecycleEvents/LifecycleEventsListener.php:368
- Edited copies of one member (4 members, 18+ corresponding lines) libs/component/runtime/src/Window/Api/LifecycleEvents/LifecycleEventsListener.php:92
- Edited copy of a member (14 corresponding lines) libs/component/runtime/src/WebView/Api/Scripts/ScriptsApi.php:48
- Edited copy of a member (20 corresponding lines) libs/component/pasm/src/Driver/LinuxDriver.php:90
- Edited copies of one member (3 members, 20+ corresponding lines) libs/component/http/src/Component/Method.php:692
- Edited copies of one member (3 members, 5+ corresponding lines) libs/component/pasm/src/Driver/Nix/Libc.php:46
- Edited copy of a member (8 corresponding lines) libs/component/runtime/src/WebView/Manager/WebViewManager.php:134
- Edited copy of a member (12 corresponding lines) libs/component/os-info/src/Factory/Driver/WindowsGenericDriver.php:34
- Edited copy of a member (4 corresponding lines) libs/component/cpu-info/src/Factory/CentralProcessorFactory.php:100
- Edited copy of a member (6 corresponding lines) libs/component/runtime/src/WebView/Api/Bindings/BindingsExtension.php:29
- Duplicated block (19 lines × 5) libs/component/cpu-info/src/Factory/Driver/WindowsRegistry/Advapi32.php:15
- Duplicated block (35 lines × 4) libs/component/cpu-info/src/InstructionSet.php:162
- Duplicated block (21 lines × 2) libs/component/http/src/Exception/InvalidHeaderNameException.php:11
- Duplicated block (5 lines × 2) libs/component/compiler/src/Workflow/Task/CreateBoxConfigTask.php:181
- Duplicated block (9 lines × 3) libs/component/runtime/src/ApplicationCreateInfo.php:138
- Duplicated block (14 lines × 2) libs/component/uri/src/Component/Authority.php:111
- No test script
Minor — 24 finding(s)
- Unused export 'default' libs/component/runtime/resources/src/id-generator/IdGeneratorInterface.ts:4
- Unused export 'default' libs/component/runtime/resources/src/rpc/BosonRpcInterface.ts:9
- Unused export 'default' libs/component/runtime/resources/src/rpc/BosonRpcResponderInterface.ts:3
- Silent fallback default in catch libs/component/cpu-info/src/Factory/Driver/WindowsRegistryDriver.php:79
- Silent fallback default in catch libs/component/os-info/src/Factory/Driver/WindowsRegistryDriver.php:218
- Silent fallback default in catch libs/component/os-info/src/Factory/Driver/WindowsRegistryDriver.php:231
- Orphaned file libs/bridge/spiral-bridge/src/Bootloader/HttpBootloader.php:1
- Orphaned file libs/bridge/laravel-provider/src/Worker.php:1
- Duplicated predicate libs/component/runtime/src/Shared/PositiveIntId.php:36
- Duplicated predicate libs/component/os-info/src/Factory/Driver/MacLicenseAwareDriver.php:49
- Fat interface: SaucerInterface (189 methods) libs/component/saucer/resources/stubs/saucer.stub.php:69
- No ADRs found libs/component/compiler/composer.json:21
- Projects may be oversized for their cohesion libs/component/runtime/package.json:1
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- CI build step not evidenced
- Logging is not universal
- No dependency-update automation libs/component/runtime/package.json:6
- No changelog
Minor — 62 finding(s)
- No assertions (declared): testRequestAdapterCompatibility libs/bridge/http-bridge/tests/CompatibilityTest.php:22
- No assertions (declared): testResponseAdapterCompatibility libs/bridge/http-bridge/tests/CompatibilityTest.php:30
- No assertions (declared): testArchitectureInterfaceCompatibility libs/component/cpu-info/tests/CompatibilityTest.php:25
- No assertions (declared): testInstructionSetInterfaceCompatibility libs/component/cpu-info/tests/CompatibilityTest.php:46
- No assertions (declared): testDetectorInterfaceCompatibility libs/component/cpu-info/tests/CompatibilityTest.php:62
- No assertions (declared): testArchitectureFactoryInterfaceCompatibility libs/component/cpu-info/tests/CompatibilityTest.php:72
- No assertions (declared): testCentralProcessorFactoryInterfaceCompatibility libs/component/cpu-info/tests/CompatibilityTest.php:80
- No assertions (declared): testServerGlobalsProviderInterfaceCompatibility libs/component/globals-provider/tests/CompatibilityTest.php:20
- No assertions (declared): testStaticProviderInterfaceCompatibility libs/component/http-static-provider/tests/CompatibilityTest.php:21
- No assertions (declared): testStandardInterfaceCompatibility libs/component/os-info/tests/CompatibilityTest.php:20
- No assertions (declared): testFamilyInterfaceCompatibility libs/component/os-info/tests/CompatibilityTest.php:41
- No assertions (declared): testExecutorInterfaceCompatibility libs/component/pasm/tests/CompatibilityTest.php:19
- No assertions (declared): testEventListenerCompatibility libs/contracts/event-listener-contracts/tests/CompatibilityTest.php:21
- No assertions (declared): testSubscriptionCompatibility libs/contracts/event-listener-contracts/tests/CompatibilityTest.php:35
- No assertions (declared): testCancellableSubscriptionCompatibility libs/contracts/event-listener-contracts/tests/CompatibilityTest.php:49
- No assertions (declared): testMessageInterfaceCompatibility libs/contracts/http-contracts/tests/CompatibilityTest.php:50
- No assertions (declared): testRequestInterfaceCompatibility libs/contracts/http-contracts/tests/CompatibilityTest.php:64
- No assertions (declared): testResponseInterfaceCompatibility libs/contracts/http-contracts/tests/CompatibilityTest.php:86
- No assertions (declared): testMutableMessageInterfaceCompatibility libs/contracts/http-contracts/tests/CompatibilityTest.php:104
- No assertions (declared): testEvolvableMessageInterfaceCompatibility libs/contracts/http-contracts/tests/CompatibilityTest.php:120
- No assertions (declared): testMutableRequestInterfaceCompatibility libs/contracts/http-contracts/tests/CompatibilityTest.php:138
- No assertions (declared): testEvolvableRequestInterfaceCompatibility libs/contracts/http-contracts/tests/CompatibilityTest.php:164
- No assertions (declared): testMutableResponseInterfaceCompatibility libs/contracts/http-contracts/tests/CompatibilityTest.php:194
- No assertions (declared): testEvolvableResponseInterfaceCompatibility libs/contracts/http-contracts/tests/CompatibilityTest.php:215
- No assertions (declared): testHeadersInterfaceCompatibility libs/contracts/http-contracts/tests/CompatibilityTest.php:239
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-ff2570971dba46a98650342851a0943e/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=577" --report-format json --report-path /tmp/watchdog-gitleaks-ff2570971dba46a98650342851a0943e/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.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-ff2570971dba46a98650342851a0943e/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude libs/component/http/resources/stubs --exclude libs/component/uri/resources . | 12 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 12 | artifacts/raw/trivy-fs.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. semgrep could not parse 391 file(s) — `.php-cs-fixer.php`, `libs/bridge/http-bridge/src/HttpAdapter.php`, `libs/bridge/laravel-provider/src/Worker.php`, `libs/bridge/spiral-bridge/src/Bootloader/BosonBootloader.php`, `libs/bridge/spiral-bridge/src/Bootloader/HttpBootloader.php`, … (+386 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |