Executive summary
kosi-libs/Kodein falls short of our standard for production because we found no automated security scanning of the code, its secrets or its dependencies. It scores 60 out of 100 and is rated Adequate, and all 30 of its critical findings are security problems in the packages it uses and in the build pipeline.
Production Readiness, at 50, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 7 points. Adding build and run instructions to the README comes next, worth about 3 points. Raising Production Readiness to 70 would lift the score to about 65.
Twenty-two known security holes in the packages the code depends on can be used by attackers. Eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Updating the vulnerable packages and pinning each tool to an exact version would close both risks.
The product code is 10,866 lines, about €21,000 to rebuild.
If Production Readiness rose from 50 to 70, the lowest score rated Strong, the score would rise from 60 to about 65.
New since the last survey: 7 findings
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 3 findings
- Static Analysis (SAST) · High: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €21,000 · Estimate
| Cost to rebuild | €6,900 to €35,000, for 115 to 365 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 60. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 10,866 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 internal.DIContainerBuilderImpl | 2 DI.Builder | 3 DIContainer | 4 SearchDSL | 5 internal.DIContainerBuilderImpl.OverrideMode | 6 internal.TypeChecker | 7 bindings.DIBinding | 8 bindings | 9 DI.BindBuilder | 10 android.ActivityRetainedScope | 11 bindings.DIBinding.Copier | 12 bindings.WeakContextScope | 13 DI | 14 android.ActivityRetainedScope.RegistryType | 15 org.kodein.di | 16 bindings.ExternalSource | 17 internal.DIBuilderImpl | 18 internal.DIContainerImpl | 19 Copy.BaseDSL | 20 DIContext | 21 SearchDSL.Spec | 22 Typed | 23 android | 24 compose | 25 compose.CompositionLocal | 26 compose.android | 27 compose.viewmodel | 28 conf | 29 internal | 30 jxinject.internal | 31 ktor | 32 tornadofx | 33 Copy | 34 android.support | 35 android.x | 36 internal.DIImpl | 37 jxinject | 38 ktor.DIPlugin | 39 android.support.AndroidLifecycleScope | 40 android.x.AndroidLifecycleScope |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 internal.DIContainerBuilderImpl | ||||||||||||||||||||||||||||||||||||||||
| 2 DI.Builder | 7 | |||||||||||||||||||||||||||||||||||||||
| 3 DIContainer | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 4 SearchDSL | 2 | |||||||||||||||||||||||||||||||||||||||
| 5 internal.DIContainerBuilderImpl.OverrideMode | 4 | |||||||||||||||||||||||||||||||||||||||
| 6 internal.TypeChecker | 2 | |||||||||||||||||||||||||||||||||||||||
| 7 bindings.DIBinding | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 8 bindings | 2 | 1 | 6 | 11 | 10 | |||||||||||||||||||||||||||||||||||
| 9 DI.BindBuilder | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 10 android.ActivityRetainedScope | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 11 bindings.DIBinding.Copier | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 12 bindings.WeakContextScope | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 DI | 6 | 1 | 3 | 1 | 8 | |||||||||||||||||||||||||||||||||||
| 14 android.ActivityRetainedScope.RegistryType | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 15 org.kodein.di | 4 | 3 | 30 | 1 | 7 | |||||||||||||||||||||||||||||||||||
| 16 bindings.ExternalSource | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 internal.DIBuilderImpl | 6 | 11 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 18 internal.DIContainerImpl | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 Copy.BaseDSL | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 20 DIContext | 3 | |||||||||||||||||||||||||||||||||||||||
| 21 SearchDSL.Spec | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 Typed | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 android | 2 | 2 | 3 | 9 | ||||||||||||||||||||||||||||||||||||
| 24 compose | 3 | 9 | ||||||||||||||||||||||||||||||||||||||
| 25 compose.CompositionLocal | 4 | |||||||||||||||||||||||||||||||||||||||
| 26 compose.android | 3 | |||||||||||||||||||||||||||||||||||||||
| 27 compose.viewmodel | 3 | |||||||||||||||||||||||||||||||||||||||
| 28 conf | 2 | 5 | ||||||||||||||||||||||||||||||||||||||
| 29 internal | 1 | 2 | 1 | 1 | 11 | 8 | 36 | 3 | 1 | |||||||||||||||||||||||||||||||
| 30 jxinject.internal | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 ktor | 4 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 32 tornadofx | 2 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 33 Copy | 6 | 13 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 android.support | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 35 android.x | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 36 internal.DIImpl | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 jxinject | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 ktor.DIPlugin | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 android.support.AndroidLifecycleScope | 2 | |||||||||||||||||||||||||||||||||||||||
| 40 android.x.AndroidLifecycleScope | 2 |
2→8 DI.Builder uses bindings part of a loop✕
- Connections
- 7 pairs of types, where a type in DI.Builder uses a type in bindings.
- The types involved
org.kodein.di.DI.Builder.ArgSetBinder→org.kodein.di.bindings.BindingDIorg.kodein.di.DI.Builder.ArgSetBinder→org.kodein.di.bindings.DIBindingorg.kodein.di.DI.Builder.ArgSetBinder→org.kodein.di.bindings.RefMakerorg.kodein.di.DI.Builder.SetBinder→org.kodein.di.bindings.DIBindingorg.kodein.di.DI.Builder.SetBinder→org.kodein.di.bindings.NoArgBindingDIorg.kodein.di.DI.Builder.SetBinder→org.kodein.di.bindings.RefMakerorg.kodein.di.DI.Builder.TypeBinder→org.kodein.di.bindings.DIBinding
- Direction
- DI.Builder uses bindings, so a change to bindings can break DI.Builder, while a change to DI.Builder can't break bindings.
- 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.
3→8 DIContainer uses bindings part of a loop✕
- Connections
- 2 pairs of types, where a type in DIContainer uses a type in bindings.
- The types involved
org.kodein.di.DIContainer.Builder→org.kodein.di.bindings.ContextTranslatororg.kodein.di.DIContainer.Builder→org.kodein.di.bindings.DIBinding
- Direction
- DIContainer uses bindings, so a change to bindings can break DIContainer, while a change to DIContainer can't break bindings.
- 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.
3→13 DIContainer uses DI part of a loop✕
- Connections
- 1 pair of types, where a type in DIContainer uses a type in DI.
- The types involved
org.kodein.di.DIContainer.Builder→org.kodein.di.DI.Key
- Direction
- DIContainer uses DI, so a change to DI can break DIContainer, while a change to DIContainer can't break DI.
- 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.
3→15 DIContainer uses org.kodein.di part of a loop✕
- Connections
- 2 pairs of types, where a type in DIContainer uses a type in org.kodein.di.
- The types involved
org.kodein.di.DIContainer.Builder→org.kodein.di.DIContainerorg.kodein.di.DIContainer.Builder→org.kodein.di.DirectDI
- Direction
- DIContainer uses org.kodein.di, so a change to org.kodein.di can break DIContainer, while a change to DIContainer can't break org.kodein.di.
- 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.
4→15 SearchDSL uses org.kodein.di part of a loop✕
- Connections
- 2 pairs of types, where a type in SearchDSL uses a type in org.kodein.di.
- The types involved
org.kodein.di.SearchDSL.Binding→org.kodein.di.SearchSpecsorg.kodein.di.SearchDSL.Spec→org.kodein.di.SearchSpecs
- Direction
- SearchDSL uses org.kodein.di, so a change to org.kodein.di can break SearchDSL, while a change to SearchDSL can't break org.kodein.di.
- 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.
5→1 internal.DIContainerBuilderImpl.OverrideMode uses internal.DIContainerBuilderImpl✕
- Connections
- 4 pairs of types, where a type in internal.DIContainerBuilderImpl.OverrideMode uses a type in internal.DIContainerBuilderImpl.
- The types involved
org.kodein.di.internal.DIContainerBuilderImpl.OverrideMode.ALLOW_EXPLICIT→org.kodein.di.internal.DIContainerBuilderImpl.OverrideModeorg.kodein.di.internal.DIContainerBuilderImpl.OverrideMode.ALLOW_SILENT→org.kodein.di.internal.DIContainerBuilderImpl.OverrideModeorg.kodein.di.internal.DIContainerBuilderImpl.OverrideMode.Companion→org.kodein.di.internal.DIContainerBuilderImpl.OverrideModeorg.kodein.di.internal.DIContainerBuilderImpl.OverrideMode.FORBID→org.kodein.di.internal.DIContainerBuilderImpl.OverrideMode
- Direction
- internal.DIContainerBuilderImpl.OverrideMode uses internal.DIContainerBuilderImpl, so a change to internal.DIContainerBuilderImpl can break internal.DIContainerBuilderImpl.OverrideMode, while a change to internal.DIContainerBuilderImpl.OverrideMode can't break internal.DIContainerBuilderImpl.
- Position
- Below the diagonal: internal.DIContainerBuilderImpl.OverrideMode uses a module listed above it, which is the healthy direction.
6→29 internal.TypeChecker uses internal part of a loop✕
- Connections
- 2 pairs of types, where a type in internal.TypeChecker uses a type in internal.
- The types involved
org.kodein.di.internal.TypeChecker.Down→org.kodein.di.internal.TypeCheckerorg.kodein.di.internal.TypeChecker.Up→org.kodein.di.internal.TypeChecker
- Direction
- internal.TypeChecker uses internal, so a change to internal can break internal.TypeChecker, while a change to internal.TypeChecker can't break internal.
- 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.
7→3 bindings.DIBinding uses DIContainer✕
- Connections
- 1 pair of types, where a type in bindings.DIBinding uses a type in DIContainer.
- The types involved
org.kodein.di.bindings.DIBinding.Copier→org.kodein.di.DIContainer.Builder
- Direction
- bindings.DIBinding uses DIContainer, so a change to DIContainer can break bindings.DIBinding, while a change to bindings.DIBinding can't break DIContainer.
- Position
- Below the diagonal: bindings.DIBinding uses a module listed above it, which is the healthy direction.
7→8 bindings.DIBinding uses bindings part of a loop✕
- Connections
- 1 pair of types, where a type in bindings.DIBinding uses a type in bindings.
- The types involved
org.kodein.di.bindings.DIBinding.Copier→org.kodein.di.bindings.DIBinding
- Direction
- bindings.DIBinding uses bindings, so a change to bindings can break bindings.DIBinding, while a change to bindings.DIBinding can't break bindings.
- 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.
8→2 bindings uses DI.Builder✕
- Connections
- 2 pairs of types, where a type in bindings uses a type in DI.Builder.
- The types involved
org.kodein.di.bindings.TypeBinderInSet→org.kodein.di.DI.Builder.TypeBinderorg.kodein.di.bindings.TypeBinderSubTypes→org.kodein.di.DI.Builder.TypeBinder
- Direction
- bindings uses DI.Builder, so a change to DI.Builder can break bindings, while a change to bindings can't break DI.Builder.
- Position
- Below the diagonal: bindings uses a module listed above it, which is the healthy direction.
8→3 bindings uses DIContainer✕
- Connections
- 1 pair of types, where a type in bindings uses a type in DIContainer.
- The types involved
org.kodein.di.bindings.EagerSingleton→org.kodein.di.DIContainer.Builder
- Direction
- bindings uses DIContainer, so a change to DIContainer can break bindings, while a change to bindings can't break DIContainer.
- Position
- Below the diagonal: bindings uses a module listed above it, which is the healthy direction.
8→7 bindings uses bindings.DIBinding✕
- Connections
- 6 pairs of types, where a type in bindings uses a type in bindings.DIBinding.
- The types involved
org.kodein.di.bindings.ArgSetBinding→org.kodein.di.bindings.DIBinding.Copierorg.kodein.di.bindings.DIBinding→org.kodein.di.bindings.DIBinding.Copierorg.kodein.di.bindings.EagerSingleton→org.kodein.di.bindings.DIBinding.Copierorg.kodein.di.bindings.Multiton→org.kodein.di.bindings.DIBinding.Copierorg.kodein.di.bindings.SetBinding→org.kodein.di.bindings.DIBinding.Copierorg.kodein.di.bindings.Singleton→org.kodein.di.bindings.DIBinding.Copier
- Direction
- bindings uses bindings.DIBinding, so a change to bindings.DIBinding can break bindings, while a change to bindings can't break bindings.DIBinding.
- Position
- Below the diagonal: bindings uses a module listed above it, which is the healthy direction.
8→13 bindings uses DI part of a loop✕
- Connections
- 11 pairs of types, where a type in bindings uses a type in DI.
- The types involved
org.kodein.di.bindings.ArgSetBinding→org.kodein.di.DI.Keyorg.kodein.di.bindings.Binding→org.kodein.di.DI.Keyorg.kodein.di.bindings.EagerSingleton→org.kodein.di.DI.Keyorg.kodein.di.bindings.ExternalSource→org.kodein.di.DI.Keyorg.kodein.di.bindings.Factory→org.kodein.di.DI.Keyorg.kodein.di.bindings.InstanceBinding→org.kodein.di.DI.Keyorg.kodein.di.bindings.Multiton→org.kodein.di.DI.Keyorg.kodein.di.bindings.Provider→org.kodein.di.DI.Keyorg.kodein.di.bindings.SetBinding→org.kodein.di.DI.Keyorg.kodein.di.bindings.Singleton→org.kodein.di.DI.Keyorg.kodein.di.bindings.SubTypes→org.kodein.di.DI.Key
- Direction
- bindings uses DI, so a change to DI can break bindings, while a change to bindings can't break DI.
- 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.
8→15 bindings uses org.kodein.di part of a loop✕
- Connections
- 10 pairs of types, where a type in bindings uses a type in org.kodein.di.
- The types involved
org.kodein.di.bindings.BindingDI→org.kodein.di.DirectDIorg.kodein.di.bindings.CompositeContextTranslator→org.kodein.di.DirectDIorg.kodein.di.bindings.ContextTranslator→org.kodein.di.DirectDIorg.kodein.di.bindings.ErasedContext→org.kodein.di.DIContextorg.kodein.di.bindings.NoArgBindingDI→org.kodein.di.DirectDIorg.kodein.di.bindings.NoArgBindingDIWrap→org.kodein.di.DirectDIorg.kodein.di.bindings.ScopesKt→org.kodein.di.DIContextorg.kodein.di.bindings.ScopesKt→org.kodein.di.DirectDIorg.kodein.di.bindings.SimpleAutoContextTranslator→org.kodein.di.DirectDIorg.kodein.di.bindings.SimpleContextTranslator→org.kodein.di.DirectDI
- Direction
- bindings uses org.kodein.di, so a change to org.kodein.di can break bindings, while a change to bindings can't break org.kodein.di.
- 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→8 DI.BindBuilder uses bindings✕
- Connections
- 2 pairs of types, where a type in DI.BindBuilder uses a type in bindings.
- The types involved
org.kodein.di.DI.BindBuilder.ImplWithScope→org.kodein.di.bindings.Scopeorg.kodein.di.DI.BindBuilder.WithScope→org.kodein.di.bindings.Scope
- Direction
- DI.BindBuilder uses bindings, so a change to bindings can break DI.BindBuilder, while a change to DI.BindBuilder can't break bindings.
- Position
- Below the diagonal: DI.BindBuilder uses a module listed above it, which is the healthy direction.
9→13 DI.BindBuilder uses DI part of a loop✕
- Connections
- 2 pairs of types, where a type in DI.BindBuilder uses a type in DI.
- The types involved
org.kodein.di.DI.BindBuilder.ImplWithContext→org.kodein.di.DI.BindBuilderorg.kodein.di.DI.BindBuilder.WithScope→org.kodein.di.DI.BindBuilder
- Direction
- DI.BindBuilder uses DI, so a change to DI can break DI.BindBuilder, while a change to DI.BindBuilder can't break DI.
- 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.
10→8 android.ActivityRetainedScope uses bindings✕
- Connections
- 2 pairs of types, where a type in android.ActivityRetainedScope uses a type in bindings.
- The types involved
org.kodein.di.android.ActivityRetainedScope.RegistryType→org.kodein.di.bindings.ScopeRegistryorg.kodein.di.android.ActivityRetainedScope.RetainedScopeFragment→org.kodein.di.bindings.ScopeRegistry
- Direction
- android.ActivityRetainedScope uses bindings, so a change to bindings can break android.ActivityRetainedScope, while a change to android.ActivityRetainedScope can't break bindings.
- Position
- Below the diagonal: android.ActivityRetainedScope uses a module listed above it, which is the healthy direction.
10→23 android.ActivityRetainedScope uses android part of a loop✕
- Connections
- 2 pairs of types, where a type in android.ActivityRetainedScope uses a type in android.
- The types involved
org.kodein.di.android.ActivityRetainedScope.MultiItem→org.kodein.di.android.ActivityRetainedScopeorg.kodein.di.android.ActivityRetainedScope.SingleItem→org.kodein.di.android.ActivityRetainedScope
- Direction
- android.ActivityRetainedScope uses android, so a change to android can break android.ActivityRetainedScope, while a change to android.ActivityRetainedScope can't break android.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→3 bindings.DIBinding.Copier uses DIContainer✕
- Connections
- 1 pair of types, where a type in bindings.DIBinding.Copier uses a type in DIContainer.
- The types involved
org.kodein.di.bindings.DIBinding.Copier.Companion→org.kodein.di.DIContainer.Builder
- Direction
- bindings.DIBinding.Copier uses DIContainer, so a change to DIContainer can break bindings.DIBinding.Copier, while a change to bindings.DIBinding.Copier can't break DIContainer.
- Position
- Below the diagonal: bindings.DIBinding.Copier uses a module listed above it, which is the healthy direction.
11→7 bindings.DIBinding.Copier uses bindings.DIBinding✕
- Connections
- 1 pair of types, where a type in bindings.DIBinding.Copier uses a type in bindings.DIBinding.
- The types involved
org.kodein.di.bindings.DIBinding.Copier.Companion→org.kodein.di.bindings.DIBinding.Copier
- Direction
- bindings.DIBinding.Copier uses bindings.DIBinding, so a change to bindings.DIBinding can break bindings.DIBinding.Copier, while a change to bindings.DIBinding.Copier can't break bindings.DIBinding.
- Position
- Below the diagonal: bindings.DIBinding.Copier uses a module listed above it, which is the healthy direction.
11→8 bindings.DIBinding.Copier uses bindings✕
- Connections
- 1 pair of types, where a type in bindings.DIBinding.Copier uses a type in bindings.
- The types involved
org.kodein.di.bindings.DIBinding.Copier.Companion→org.kodein.di.bindings.DIBinding
- Direction
- bindings.DIBinding.Copier uses bindings, so a change to bindings can break bindings.DIBinding.Copier, while a change to bindings.DIBinding.Copier can't break bindings.
- Position
- Below the diagonal: bindings.DIBinding.Copier uses a module listed above it, which is the healthy direction.
12→8 bindings.WeakContextScope uses bindings✕
- Connections
- 2 pairs of types, where a type in bindings.WeakContextScope uses a type in bindings.
- The types involved
org.kodein.di.bindings.WeakContextScope.Of→org.kodein.di.bindings.Scopeorg.kodein.di.bindings.WeakContextScope.Of→org.kodein.di.bindings.WeakContextScope
- Direction
- bindings.WeakContextScope uses bindings, so a change to bindings can break bindings.WeakContextScope, while a change to bindings.WeakContextScope can't break bindings.
- Position
- Below the diagonal: bindings.WeakContextScope uses a module listed above it, which is the healthy direction.
13→2 DI uses DI.Builder✕
- Connections
- 6 pairs of types, where a type in DI uses a type in DI.Builder.
- The types involved
org.kodein.di.DI.Builder→org.kodein.di.DI.Builder.ArgSetBinderorg.kodein.di.DI.Builder→org.kodein.di.DI.Builder.ConstantBinderorg.kodein.di.DI.Builder→org.kodein.di.DI.Builder.DelegateBinderorg.kodein.di.DI.Builder→org.kodein.di.DI.Builder.DirectBinderorg.kodein.di.DI.Builder→org.kodein.di.DI.Builder.SetBinderorg.kodein.di.DI.Builder→org.kodein.di.DI.Builder.TypeBinder
- Direction
- DI uses DI.Builder, so a change to DI.Builder can break DI, while a change to DI can't break DI.Builder.
- Position
- Below the diagonal: DI uses a module listed above it, which is the healthy direction.
13→3 DI uses DIContainer✕
- Connections
- 1 pair of types, where a type in DI uses a type in DIContainer.
- The types involved
org.kodein.di.DI.Builder→org.kodein.di.DIContainer.Builder
- Direction
- DI uses DIContainer, so a change to DIContainer can break DI, while a change to DI can't break DIContainer.
- Position
- Below the diagonal: DI uses a module listed above it, which is the healthy direction.
13→8 DI uses bindings✕
- Connections
- 3 pairs of types, where a type in DI uses a type in bindings.
- The types involved
org.kodein.di.DI.Builder→org.kodein.di.bindings.ContextTranslatororg.kodein.di.DI.Builder→org.kodein.di.bindings.DIBindingorg.kodein.di.DI.MainBuilder→org.kodein.di.bindings.ExternalSource
- Direction
- DI uses bindings, so a change to bindings can break DI, while a change to DI can't break bindings.
- Position
- Below the diagonal: DI uses a module listed above it, which is the healthy direction.
13→9 DI uses DI.BindBuilder✕
- Connections
- 1 pair of types, where a type in DI uses a type in DI.BindBuilder.
- The types involved
org.kodein.di.DI.Builder→org.kodein.di.DI.BindBuilder.WithScope
- Direction
- DI uses DI.BindBuilder, so a change to DI.BindBuilder can break DI, while a change to DI can't break DI.BindBuilder.
- Position
- Below the diagonal: DI uses a module listed above it, which is the healthy direction.
13→15 DI uses org.kodein.di part of a loop✕
- Connections
- 8 pairs of types, where a type in DI uses a type in org.kodein.di.
- The types involved
org.kodein.di.DI.Builder→org.kodein.di.DirectDIorg.kodein.di.DI.Companion→org.kodein.di.DIorg.kodein.di.DI.Companion→org.kodein.di.DirectDIorg.kodein.di.DI.Companion→org.kodein.di.LazyDIorg.kodein.di.DI.MainBuilder→org.kodein.di.Copyorg.kodein.di.DI.MainBuilder→org.kodein.di.DIorg.kodein.di.DI.MainBuilder→org.kodein.di.DirectDIorg.kodein.di.DI.NoResultException→org.kodein.di.SearchSpecs
- Direction
- DI uses org.kodein.di, so a change to org.kodein.di can break DI, while a change to DI can't break org.kodein.di.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→8 android.ActivityRetainedScope.RegistryType uses bindings✕
- Connections
- 2 pairs of types, where a type in android.ActivityRetainedScope.RegistryType uses a type in bindings.
- The types involved
org.kodein.di.android.ActivityRetainedScope.RegistryType.SingleItem→org.kodein.di.bindings.SingleItemScopeRegistryorg.kodein.di.android.ActivityRetainedScope.RegistryType.Standard→org.kodein.di.bindings.StandardScopeRegistry
- Direction
- android.ActivityRetainedScope.RegistryType uses bindings, so a change to bindings can break android.ActivityRetainedScope.RegistryType, while a change to android.ActivityRetainedScope.RegistryType can't break bindings.
- Position
- Below the diagonal: android.ActivityRetainedScope.RegistryType uses a module listed above it, which is the healthy direction.
14→10 android.ActivityRetainedScope.RegistryType uses android.ActivityRetainedScope✕
- Connections
- 2 pairs of types, where a type in android.ActivityRetainedScope.RegistryType uses a type in android.ActivityRetainedScope.
- The types involved
org.kodein.di.android.ActivityRetainedScope.RegistryType.SingleItem→org.kodein.di.android.ActivityRetainedScope.RegistryTypeorg.kodein.di.android.ActivityRetainedScope.RegistryType.Standard→org.kodein.di.android.ActivityRetainedScope.RegistryType
- Direction
- android.ActivityRetainedScope.RegistryType uses android.ActivityRetainedScope, so a change to android.ActivityRetainedScope can break android.ActivityRetainedScope.RegistryType, while a change to android.ActivityRetainedScope.RegistryType can't break android.ActivityRetainedScope.
- Position
- Below the diagonal: android.ActivityRetainedScope.RegistryType uses a module listed above it, which is the healthy direction.
15→2 org.kodein.di uses DI.Builder✕
- Connections
- 4 pairs of types, where a type in org.kodein.di uses a type in DI.Builder.
- The types involved
org.kodein.di.DIBuilderKt→org.kodein.di.DI.Builder.DelegateBinderorg.kodein.di.DIBuilderKt→org.kodein.di.DI.Builder.TypeBinderorg.kodein.di.SetBindingsKt→org.kodein.di.DI.Builder.ArgSetBinderorg.kodein.di.SetBindingsKt→org.kodein.di.DI.Builder.SetBinder
- Direction
- org.kodein.di uses DI.Builder, so a change to DI.Builder can break org.kodein.di, while a change to org.kodein.di can't break DI.Builder.
- Position
- Below the diagonal: org.kodein.di uses a module listed above it, which is the healthy direction.
15→4 org.kodein.di uses SearchDSL✕
- Connections
- 3 pairs of types, where a type in org.kodein.di uses a type in SearchDSL.
- The types involved
org.kodein.di.DIBuilderKt→org.kodein.di.SearchDSL.Bindingorg.kodein.di.DIBuilderKt→org.kodein.di.SearchDSL.Specorg.kodein.di.SearchDSL→org.kodein.di.SearchDSL.Spec
- Direction
- org.kodein.di uses SearchDSL, so a change to SearchDSL can break org.kodein.di, while a change to org.kodein.di can't break SearchDSL.
- Position
- Below the diagonal: org.kodein.di uses a module listed above it, which is the healthy direction.
15→8 org.kodein.di uses bindings✕
- Connections
- 30 pairs of types, where a type in org.kodein.di uses a type in bindings. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.kodein.di.BindFactoryKt→org.kodein.di.bindings.BindingDIorg.kodein.di.BindFactoryKt→org.kodein.di.bindings.Factoryorg.kodein.di.BindInstanceKt→org.kodein.di.bindings.InstanceBindingorg.kodein.di.BindMultitonKt→org.kodein.di.bindings.BindingDIorg.kodein.di.BindMultitonKt→org.kodein.di.bindings.Multitonorg.kodein.di.BindMultitonKt→org.kodein.di.bindings.RefMakerorg.kodein.di.BindProviderKt→org.kodein.di.bindings.NoArgBindingDIorg.kodein.di.BindProviderKt→org.kodein.di.bindings.Providerorg.kodein.di.BindSingletonKt→org.kodein.di.bindings.EagerSingletonorg.kodein.di.BindSingletonKt→org.kodein.di.bindings.NoArgBindingDIorg.kodein.di.BindSingletonKt→org.kodein.di.bindings.RefMakerorg.kodein.di.BindSingletonKt→org.kodein.di.bindings.Singletonorg.kodein.di.BindingsMapKt→org.kodein.di.bindings.DIBindingorg.kodein.di.DIBuilderKt→org.kodein.di.bindings.ContextTranslatororg.kodein.di.DIBuilderKt→org.kodein.di.bindings.DIBindingorg.kodein.di.DIBuilderKt→org.kodein.di.bindings.Scopeorg.kodein.di.DIDefining→org.kodein.di.bindings.DIBindingorg.kodein.di.DIDefinition→org.kodein.di.bindings.DIBindingorg.kodein.di.DITree→org.kodein.di.bindings.ContextTranslatororg.kodein.di.DITree→org.kodein.di.bindings.ExternalSourceorg.kodein.di.SearchKt→org.kodein.di.bindings.ContextTranslatororg.kodein.di.SetBindingsKt→org.kodein.di.bindings.DIBindingorg.kodein.di.SetBindingsKt→org.kodein.di.bindings.TypeBinderInSetorg.kodein.di.SubTypesKt→org.kodein.di.bindings.DIBindingorg.kodein.di.softReference→org.kodein.di.bindings.RefMaker
- Direction
- org.kodein.di uses bindings, so a change to bindings can break org.kodein.di, while a change to org.kodein.di can't break bindings.
- Position
- Below the diagonal: org.kodein.di uses a module listed above it, which is the healthy direction.
15→9 org.kodein.di uses DI.BindBuilder✕
- Connections
- 1 pair of types, where a type in org.kodein.di uses a type in DI.BindBuilder.
- The types involved
org.kodein.di.DIBuilderKt→org.kodein.di.DI.BindBuilder.WithScope
- Direction
- org.kodein.di uses DI.BindBuilder, so a change to DI.BindBuilder can break org.kodein.di, while a change to org.kodein.di can't break DI.BindBuilder.
- Position
- Below the diagonal: org.kodein.di uses a module listed above it, which is the healthy direction.
15→13 org.kodein.di uses DI✕
- Connections
- 7 pairs of types, where a type in org.kodein.di uses a type in DI.
- The types involved
org.kodein.di.BindingsMapKt→org.kodein.di.DI.Keyorg.kodein.di.Copy→org.kodein.di.DI.Keyorg.kodein.di.DIBuilderKt→org.kodein.di.DI.BindBuilderorg.kodein.di.DIContainer→org.kodein.di.DI.Keyorg.kodein.di.DITree→org.kodein.di.DI.Keyorg.kodein.di.SearchKt→org.kodein.di.DI.Keyorg.kodein.di.SubsKt→org.kodein.di.DI.MainBuilder
- Direction
- org.kodein.di uses DI, so a change to DI can break org.kodein.di, while a change to org.kodein.di can't break DI.
- Position
- Below the diagonal: org.kodein.di uses a module listed above it, which is the healthy direction.
16→8 bindings.ExternalSource uses bindings✕
- Connections
- 2 pairs of types, where a type in bindings.ExternalSource uses a type in bindings.
- The types involved
org.kodein.di.bindings.ExternalSource.Companion→org.kodein.di.bindings.BindingDIorg.kodein.di.bindings.ExternalSource.Companion→org.kodein.di.bindings.ExternalSource
- Direction
- bindings.ExternalSource uses bindings, so a change to bindings can break bindings.ExternalSource, while a change to bindings.ExternalSource can't break bindings.
- Position
- Below the diagonal: bindings.ExternalSource uses a module listed above it, which is the healthy direction.
16→13 bindings.ExternalSource uses DI✕
- Connections
- 1 pair of types, where a type in bindings.ExternalSource uses a type in DI.
- The types involved
org.kodein.di.bindings.ExternalSource.Companion→org.kodein.di.DI.Key
- Direction
- bindings.ExternalSource uses DI, so a change to DI can break bindings.ExternalSource, while a change to bindings.ExternalSource can't break DI.
- Position
- Below the diagonal: bindings.ExternalSource uses a module listed above it, which is the healthy direction.
17→2 internal.DIBuilderImpl uses DI.Builder✕
- Connections
- 6 pairs of types, where a type in internal.DIBuilderImpl uses a type in DI.Builder.
- The types involved
org.kodein.di.internal.DIBuilderImpl.ArgSetBinder→org.kodein.di.DI.Builder.ArgSetBinderorg.kodein.di.internal.DIBuilderImpl.ConstantBinder→org.kodein.di.DI.Builder.ConstantBinderorg.kodein.di.internal.DIBuilderImpl.DelegateBinder→org.kodein.di.DI.Builder.DelegateBinderorg.kodein.di.internal.DIBuilderImpl.DirectBinder→org.kodein.di.DI.Builder.DirectBinderorg.kodein.di.internal.DIBuilderImpl.SetBinder→org.kodein.di.DI.Builder.SetBinderorg.kodein.di.internal.DIBuilderImpl.TypeBinder→org.kodein.di.DI.Builder.TypeBinder
- Direction
- internal.DIBuilderImpl uses DI.Builder, so a change to DI.Builder can break internal.DIBuilderImpl, while a change to internal.DIBuilderImpl can't break DI.Builder.
- Position
- Below the diagonal: internal.DIBuilderImpl uses a module listed above it, which is the healthy direction.
17→8 internal.DIBuilderImpl uses bindings✕
- Connections
- 11 pairs of types, where a type in internal.DIBuilderImpl uses a type in bindings.
- The types involved
org.kodein.di.internal.DIBuilderImpl.ArgSetBinder→org.kodein.di.bindings.BaseMultiBindingorg.kodein.di.internal.DIBuilderImpl.ArgSetBinder→org.kodein.di.bindings.BindingDIorg.kodein.di.internal.DIBuilderImpl.ArgSetBinder→org.kodein.di.bindings.DIBindingorg.kodein.di.internal.DIBuilderImpl.ArgSetBinder→org.kodein.di.bindings.RefMakerorg.kodein.di.internal.DIBuilderImpl.ArgSetBinder→org.kodein.di.bindings.Scopeorg.kodein.di.internal.DIBuilderImpl.SetBinder→org.kodein.di.bindings.BaseMultiBindingorg.kodein.di.internal.DIBuilderImpl.SetBinder→org.kodein.di.bindings.DIBindingorg.kodein.di.internal.DIBuilderImpl.SetBinder→org.kodein.di.bindings.NoArgBindingDIorg.kodein.di.internal.DIBuilderImpl.SetBinder→org.kodein.di.bindings.RefMakerorg.kodein.di.internal.DIBuilderImpl.SetBinder→org.kodein.di.bindings.Scopeorg.kodein.di.internal.DIBuilderImpl.TypeBinder→org.kodein.di.bindings.DIBinding
- Direction
- internal.DIBuilderImpl uses bindings, so a change to bindings can break internal.DIBuilderImpl, while a change to internal.DIBuilderImpl can't break bindings.
- Position
- Below the diagonal: internal.DIBuilderImpl uses a module listed above it, which is the healthy direction.
17→13 internal.DIBuilderImpl uses DI✕
- Connections
- 1 pair of types, where a type in internal.DIBuilderImpl uses a type in DI.
- The types involved
org.kodein.di.internal.DIBuilderImpl.DelegateBinder→org.kodein.di.DI.Builder
- Direction
- internal.DIBuilderImpl uses DI, so a change to DI can break internal.DIBuilderImpl, while a change to internal.DIBuilderImpl can't break DI.
- Position
- Below the diagonal: internal.DIBuilderImpl uses a module listed above it, which is the healthy direction.
17→29 internal.DIBuilderImpl uses internal part of a loop✕
- Connections
- 1 pair of types, where a type in internal.DIBuilderImpl uses a type in internal.
- The types involved
org.kodein.di.internal.DIBuilderImpl.TypeBinder→org.kodein.di.internal.DIContainerBuilderImpl
- Direction
- internal.DIBuilderImpl uses internal, so a change to internal can break internal.DIBuilderImpl, while a change to internal.DIBuilderImpl can't break internal.
- 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.
18→13 internal.DIContainerImpl uses DI✕
- Connections
- 1 pair of types, where a type in internal.DIContainerImpl uses a type in DI.
- The types involved
org.kodein.di.internal.DIContainerImpl.Node→org.kodein.di.DI.Key
- Direction
- internal.DIContainerImpl uses DI, so a change to DI can break internal.DIContainerImpl, while a change to internal.DIContainerImpl can't break DI.
- Position
- Below the diagonal: internal.DIContainerImpl uses a module listed above it, which is the healthy direction.
19→4 Copy.BaseDSL uses SearchDSL✕
- Connections
- 2 pairs of types, where a type in Copy.BaseDSL uses a type in SearchDSL.
- The types involved
org.kodein.di.Copy.BaseDSL.Sentence→org.kodein.di.SearchDSL.Bindingorg.kodein.di.Copy.BaseDSL.Sentence→org.kodein.di.SearchDSL.Spec
- Direction
- Copy.BaseDSL uses SearchDSL, so a change to SearchDSL can break Copy.BaseDSL, while a change to Copy.BaseDSL can't break SearchDSL.
- Position
- Below the diagonal: Copy.BaseDSL uses a module listed above it, which is the healthy direction.
19→15 Copy.BaseDSL uses org.kodein.di✕
- Connections
- 2 pairs of types, where a type in Copy.BaseDSL uses a type in org.kodein.di.
- The types involved
org.kodein.di.Copy.BaseDSL.Sentence→org.kodein.di.CopySpecsorg.kodein.di.Copy.BaseDSL.Sentence→org.kodein.di.SearchSpecs
- Direction
- Copy.BaseDSL uses org.kodein.di, so a change to org.kodein.di can break Copy.BaseDSL, while a change to Copy.BaseDSL can't break org.kodein.di.
- Position
- Below the diagonal: Copy.BaseDSL uses a module listed above it, which is the healthy direction.
20→15 DIContext uses org.kodein.di✕
- Connections
- 3 pairs of types, where a type in DIContext uses a type in org.kodein.di.
- The types involved
org.kodein.di.DIContext.Companion→org.kodein.di.DIContextorg.kodein.di.DIContext.Lazy→org.kodein.di.DIContextorg.kodein.di.DIContext.Value→org.kodein.di.DIContext
- Direction
- DIContext uses org.kodein.di, so a change to org.kodein.di can break DIContext, while a change to DIContext can't break org.kodein.di.
- Position
- Below the diagonal: DIContext uses a module listed above it, which is the healthy direction.
21→4 SearchDSL.Spec uses SearchDSL✕
- Connections
- 1 pair of types, where a type in SearchDSL.Spec uses a type in SearchDSL.
- The types involved
org.kodein.di.SearchDSL.Spec.Companion→org.kodein.di.SearchDSL.Spec
- Direction
- SearchDSL.Spec uses SearchDSL, so a change to SearchDSL can break SearchDSL.Spec, while a change to SearchDSL.Spec can't break SearchDSL.
- Position
- Below the diagonal: SearchDSL.Spec uses a module listed above it, which is the healthy direction.
21→15 SearchDSL.Spec uses org.kodein.di✕
- Connections
- 1 pair of types, where a type in SearchDSL.Spec uses a type in org.kodein.di.
- The types involved
org.kodein.di.SearchDSL.Spec.Companion→org.kodein.di.SearchSpecs
- Direction
- SearchDSL.Spec uses org.kodein.di, so a change to org.kodein.di can break SearchDSL.Spec, while a change to SearchDSL.Spec can't break org.kodein.di.
- Position
- Below the diagonal: SearchDSL.Spec uses a module listed above it, which is the healthy direction.
22→15 Typed uses org.kodein.di✕
- Connections
- 1 pair of types, where a type in Typed uses a type in org.kodein.di.
- The types involved
org.kodein.di.Typed.Companion→org.kodein.di.Typed
- Direction
- Typed uses org.kodein.di, so a change to org.kodein.di can break Typed, while a change to Typed can't break org.kodein.di.
- Position
- Below the diagonal: Typed uses a module listed above it, which is the healthy direction.
23→8 android uses bindings✕
- Connections
- 2 pairs of types, where a type in android uses a type in bindings.
- The types involved
org.kodein.di.android.ActivityRetainedScope→org.kodein.di.bindings.Scopeorg.kodein.di.android.ActivityRetainedScope→org.kodein.di.bindings.ScopeRegistry
- Direction
- android uses bindings, so a change to bindings can break android, while a change to android can't break bindings.
- Position
- Below the diagonal: android uses a module listed above it, which is the healthy direction.
23→10 android uses android.ActivityRetainedScope✕
- Connections
- 2 pairs of types, where a type in android uses a type in android.ActivityRetainedScope.
- The types involved
org.kodein.di.android.ActivityRetainedScope→org.kodein.di.android.ActivityRetainedScope.RegistryTypeorg.kodein.di.android.ActivityRetainedScope→org.kodein.di.android.ActivityRetainedScope.RetainedScopeFragment
- Direction
- android uses android.ActivityRetainedScope, so a change to android.ActivityRetainedScope can break android, while a change to android can't break android.ActivityRetainedScope.
- Position
- Below the diagonal: android uses a module listed above it, which is the healthy direction.
23→13 android uses DI✕
- Connections
- 3 pairs of types, where a type in android uses a type in DI.
- The types involved
org.kodein.di.android.ModuleKt→org.kodein.di.DI.Moduleorg.kodein.di.android.RetainedKt→org.kodein.di.DI.MainBuilderorg.kodein.di.android.SubKt→org.kodein.di.DI.MainBuilder
- Direction
- android uses DI, so a change to DI can break android, while a change to android can't break DI.
- Position
- Below the diagonal: android uses a module listed above it, which is the healthy direction.
23→15 android uses org.kodein.di✕
- Connections
- 9 pairs of types, where a type in android uses a type in org.kodein.di.
- The types involved
org.kodein.di.android.ClosestKt→org.kodein.di.DIorg.kodein.di.android.ContextDIPropertyDelegateProvider→org.kodein.di.DIorg.kodein.di.android.DIPropertyDelegateProvider→org.kodein.di.DIorg.kodein.di.android.LazyContextDIPropertyDelegateProvider→org.kodein.di.DIorg.kodein.di.android.RetainedDIFragment→org.kodein.di.DIorg.kodein.di.android.RetainedKt→org.kodein.di.DIorg.kodein.di.android.SubKt→org.kodein.di.Copyorg.kodein.di.android.SubKt→org.kodein.di.DIorg.kodein.di.android.SubKt→org.kodein.di.LazyDI
- Direction
- android uses org.kodein.di, so a change to org.kodein.di can break android, while a change to android can't break org.kodein.di.
- Position
- Below the diagonal: android uses a module listed above it, which is the healthy direction.
24→13 compose uses DI✕
- Connections
- 3 pairs of types, where a type in compose uses a type in DI.
- The types involved
org.kodein.di.compose.SubDIKt→org.kodein.di.DI.MainBuilderorg.kodein.di.compose.WithDIKt→org.kodein.di.DI.MainBuilderorg.kodein.di.compose.WithDIKt→org.kodein.di.DI.Module
- Direction
- compose uses DI, so a change to DI can break compose, while a change to compose can't break DI.
- Position
- Below the diagonal: compose uses a module listed above it, which is the healthy direction.
24→15 compose uses org.kodein.di✕
- Connections
- 9 pairs of types, where a type in compose uses a type in org.kodein.di.
- The types involved
org.kodein.di.compose.AndroidContextKt→org.kodein.di.DIorg.kodein.di.compose.ComposableDILazyDelegate→org.kodein.di.LazyDelegateorg.kodein.di.compose.CompositionLocalKt→org.kodein.di.DIorg.kodein.di.compose.RetrievingKt→org.kodein.di.DIorg.kodein.di.compose.RetrievingKt→org.kodein.di.LazyDelegateorg.kodein.di.compose.SubDIKt→org.kodein.di.Copyorg.kodein.di.compose.SubDIKt→org.kodein.di.DIorg.kodein.di.compose.WithDIKt→org.kodein.di.DIorg.kodein.di.compose.WithDIKt→org.kodein.di.DIContext
- Direction
- compose uses org.kodein.di, so a change to org.kodein.di can break compose, while a change to compose can't break org.kodein.di.
- Position
- Below the diagonal: compose uses a module listed above it, which is the healthy direction.
25→15 compose.CompositionLocal uses org.kodein.di✕
- Connections
- 4 pairs of types, where a type in compose.CompositionLocal uses a type in org.kodein.di.
- The types involved
org.kodein.di.compose.CompositionLocal.androidKt→org.kodein.di.DIorg.kodein.di.compose.CompositionLocal.jsBasedKt→org.kodein.di.DIorg.kodein.di.compose.CompositionLocal.jvmKt→org.kodein.di.DIorg.kodein.di.compose.CompositionLocal.nativeKt→org.kodein.di.DI
- Direction
- compose.CompositionLocal uses org.kodein.di, so a change to org.kodein.di can break compose.CompositionLocal, while a change to compose.CompositionLocal can't break org.kodein.di.
- Position
- Below the diagonal: compose.CompositionLocal uses a module listed above it, which is the healthy direction.
26→15 compose.android uses org.kodein.di✕
- Connections
- 3 pairs of types, where a type in compose.android uses a type in org.kodein.di.
- The types involved
org.kodein.di.compose.android.KodeinViewModelScopedFactory→org.kodein.di.DIorg.kodein.di.compose.android.KodeinViewModelScopedFactoryKt→org.kodein.di.DIorg.kodein.di.compose.android.KodeinViewModelScopedSingleton→org.kodein.di.DI
- Direction
- compose.android uses org.kodein.di, so a change to org.kodein.di can break compose.android, while a change to compose.android can't break org.kodein.di.
- Position
- Below the diagonal: compose.android uses a module listed above it, which is the healthy direction.
27→15 compose.viewmodel uses org.kodein.di✕
- Connections
- 3 pairs of types, where a type in compose.viewmodel uses a type in org.kodein.di.
- The types involved
org.kodein.di.compose.viewmodel.KodeinViewModelScopeKt→org.kodein.di.DIorg.kodein.di.compose.viewmodel.KodeinViewModelScopedFactory→org.kodein.di.DIorg.kodein.di.compose.viewmodel.KodeinViewModelScopedSingleton→org.kodein.di.DI
- Direction
- compose.viewmodel uses org.kodein.di, so a change to org.kodein.di can break compose.viewmodel, while a change to compose.viewmodel can't break org.kodein.di.
- Position
- Below the diagonal: compose.viewmodel uses a module listed above it, which is the healthy direction.
28→13 conf uses DI✕
- Connections
- 2 pairs of types, where a type in conf uses a type in DI.
- The types involved
org.kodein.di.conf.ConfigurableDI→org.kodein.di.DI.MainBuilderorg.kodein.di.conf.ConfigurableDI→org.kodein.di.DI.Module
- Direction
- conf uses DI, so a change to DI can break conf, while a change to conf can't break DI.
- Position
- Below the diagonal: conf uses a module listed above it, which is the healthy direction.
28→15 conf uses org.kodein.di✕
- Connections
- 5 pairs of types, where a type in conf uses a type in org.kodein.di.
- The types involved
org.kodein.di.conf.ConfigurableDI→org.kodein.di.Copyorg.kodein.di.conf.ConfigurableDI→org.kodein.di.DIorg.kodein.di.conf.ConfigurableDI→org.kodein.di.DIContainerorg.kodein.di.conf.DIGlobalAware→org.kodein.di.DIorg.kodein.di.conf.DIGlobalAware→org.kodein.di.DIAware
- Direction
- conf uses org.kodein.di, so a change to org.kodein.di can break conf, while a change to conf can't break org.kodein.di.
- Position
- Below the diagonal: conf uses a module listed above it, which is the healthy direction.
29→1 internal uses internal.DIContainerBuilderImpl✕
- Connections
- 1 pair of types, where a type in internal uses a type in internal.DIContainerBuilderImpl.
- The types involved
org.kodein.di.internal.DIContainerBuilderImpl→org.kodein.di.internal.DIContainerBuilderImpl.OverrideMode
- Direction
- internal uses internal.DIContainerBuilderImpl, so a change to internal.DIContainerBuilderImpl can break internal, while a change to internal can't break internal.DIContainerBuilderImpl.
- Position
- Below the diagonal: internal uses a module listed above it, which is the healthy direction.
29→2 internal uses DI.Builder✕
- Connections
- 2 pairs of types, where a type in internal uses a type in DI.Builder.
- The types involved
org.kodein.di.internal.DIBuilderImpl→org.kodein.di.DI.Builder.ArgSetBinderorg.kodein.di.internal.DIBuilderImpl→org.kodein.di.DI.Builder.SetBinder
- Direction
- internal uses DI.Builder, so a change to DI.Builder can break internal, while a change to internal can't break DI.Builder.
- Position
- Below the diagonal: internal uses a module listed above it, which is the healthy direction.
29→3 internal uses DIContainer✕
- Connections
- 1 pair of types, where a type in internal uses a type in DIContainer.
- The types involved
org.kodein.di.internal.DIContainerBuilderImpl→org.kodein.di.DIContainer.Builder
- Direction
- internal uses DIContainer, so a change to DIContainer can break internal, while a change to internal can't break DIContainer.
- Position
- Below the diagonal: internal uses a module listed above it, which is the healthy direction.
29→6 internal uses internal.TypeChecker✕
- Connections
- 1 pair of types, where a type in internal uses a type in internal.TypeChecker.
- The types involved
org.kodein.di.internal.DITreeImpl→org.kodein.di.internal.TypeChecker.Down
- Direction
- internal uses internal.TypeChecker, so a change to internal.TypeChecker can break internal, while a change to internal can't break internal.TypeChecker.
- Position
- Below the diagonal: internal uses a module listed above it, which is the healthy direction.
29→8 internal uses bindings✕
- Connections
- 11 pairs of types, where a type in internal uses a type in bindings.
- The types involved
org.kodein.di.internal.BindingDIImpl→org.kodein.di.bindings.BindingDIorg.kodein.di.internal.DIBuilderImpl→org.kodein.di.bindings.ContextTranslatororg.kodein.di.internal.DIBuilderImpl→org.kodein.di.bindings.DIBindingorg.kodein.di.internal.DIBuilderImpl→org.kodein.di.bindings.Scopeorg.kodein.di.internal.DIContainerBuilderImpl→org.kodein.di.bindings.ContextTranslatororg.kodein.di.internal.DIContainerBuilderImpl→org.kodein.di.bindings.DIBindingorg.kodein.di.internal.DIContainerImpl→org.kodein.di.bindings.BindingDIorg.kodein.di.internal.DIContainerImpl→org.kodein.di.bindings.ExternalSourceorg.kodein.di.internal.DIMainBuilderImpl→org.kodein.di.bindings.ExternalSourceorg.kodein.di.internal.DITreeImpl→org.kodein.di.bindings.ContextTranslatororg.kodein.di.internal.DITreeImpl→org.kodein.di.bindings.ExternalSource
- Direction
- internal uses bindings, so a change to bindings can break internal, while a change to internal can't break bindings.
- Position
- Below the diagonal: internal uses a module listed above it, which is the healthy direction.
29→13 internal uses DI✕
- Connections
- 8 pairs of types, where a type in internal uses a type in DI.
- The types involved
org.kodein.di.internal.BindingDIImpl→org.kodein.di.DI.Keyorg.kodein.di.internal.DIBuilderImpl→org.kodein.di.DI.Builderorg.kodein.di.internal.DIBuilderImpl→org.kodein.di.DI.Moduleorg.kodein.di.internal.DIContainerBuilderImpl→org.kodein.di.DI.Keyorg.kodein.di.internal.DIContainerImpl→org.kodein.di.DI.Keyorg.kodein.di.internal.DIImpl→org.kodein.di.DI.MainBuilderorg.kodein.di.internal.DIMainBuilderImpl→org.kodein.di.DI.MainBuilderorg.kodein.di.internal.DITreeImpl→org.kodein.di.DI.Key
- Direction
- internal uses DI, so a change to DI can break internal, while a change to internal can't break DI.
- Position
- Below the diagonal: internal uses a module listed above it, which is the healthy direction.
29→15 internal uses org.kodein.di✕
- Connections
- 36 pairs of types, where a type in internal uses a type in org.kodein.di. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.kodein.di.internal.BindingDIImpl→org.kodein.di.DirectDIorg.kodein.di.internal.DIBuilderImpl→org.kodein.di.DirectDIorg.kodein.di.internal.DIContainerBuilderImpl→org.kodein.di.DIContainerorg.kodein.di.internal.DIContainerBuilderImpl→org.kodein.di.DIDefiningorg.kodein.di.internal.DIContainerBuilderImpl→org.kodein.di.DirectDIorg.kodein.di.internal.DIContainerImpl→org.kodein.di.DIContainerorg.kodein.di.internal.DIContainerImpl→org.kodein.di.DIContextorg.kodein.di.internal.DIContainerImpl→org.kodein.di.DITreeorg.kodein.di.internal.DIImpl→org.kodein.di.DIorg.kodein.di.internal.DIImpl→org.kodein.di.DIContainerorg.kodein.di.internal.DIMainBuilderImpl→org.kodein.di.Copyorg.kodein.di.internal.DIMainBuilderImpl→org.kodein.di.DIorg.kodein.di.internal.DIMainBuilderImpl→org.kodein.di.DirectDIorg.kodein.di.internal.DITreeImpl→org.kodein.di.DIDefiningorg.kodein.di.internal.DITreeImpl→org.kodein.di.DIDefinitionorg.kodein.di.internal.DITreeImpl→org.kodein.di.DITreeorg.kodein.di.internal.DITreeImpl→org.kodein.di.SearchSpecsorg.kodein.di.internal.DirectDIBaseImpl→org.kodein.di.DIorg.kodein.di.internal.DirectDIBaseImpl→org.kodein.di.DIContainerorg.kodein.di.internal.DirectDIBaseImpl→org.kodein.di.DIContextorg.kodein.di.internal.DirectDIBaseImpl→org.kodein.di.DirectDIorg.kodein.di.internal.DirectDIImpl→org.kodein.di.DIContainerorg.kodein.di.internal.DirectDIImpl→org.kodein.di.DIContextorg.kodein.di.internal.DirectDIImpl→org.kodein.di.DirectDIorg.kodein.di.internal.DirectDIImplKt→org.kodein.di.DIContainer
- Direction
- internal uses org.kodein.di, so a change to org.kodein.di can break internal, while a change to internal can't break org.kodein.di.
- Position
- Below the diagonal: internal uses a module listed above it, which is the healthy direction.
29→17 internal uses internal.DIBuilderImpl✕
- Connections
- 3 pairs of types, where a type in internal uses a type in internal.DIBuilderImpl.
- The types involved
org.kodein.di.internal.DIBuilderImpl→org.kodein.di.internal.DIBuilderImpl.ConstantBinderorg.kodein.di.internal.DIBuilderImpl→org.kodein.di.internal.DIBuilderImpl.DelegateBinderorg.kodein.di.internal.DIBuilderImpl→org.kodein.di.internal.DIBuilderImpl.DirectBinder
- Direction
- internal uses internal.DIBuilderImpl, so a change to internal.DIBuilderImpl can break internal, while a change to internal can't break internal.DIBuilderImpl.
- Position
- Below the diagonal: internal uses a module listed above it, which is the healthy direction.
29→18 internal uses internal.DIContainerImpl✕
- Connections
- 1 pair of types, where a type in internal uses a type in internal.DIContainerImpl.
- The types involved
org.kodein.di.internal.DIContainerImpl→org.kodein.di.internal.DIContainerImpl.Node
- Direction
- internal uses internal.DIContainerImpl, so a change to internal.DIContainerImpl can break internal, while a change to internal can't break internal.DIContainerImpl.
- Position
- Below the diagonal: internal uses a module listed above it, which is the healthy direction.
30→15 jxinject.internal uses org.kodein.di✕
- Connections
- 1 pair of types, where a type in jxinject.internal uses a type in org.kodein.di.
- The types involved
org.kodein.di.jxinject.internal.JxInjectorContainer→org.kodein.di.DirectDI
- Direction
- jxinject.internal uses org.kodein.di, so a change to org.kodein.di can break jxinject.internal, while a change to jxinject.internal can't break org.kodein.di.
- Position
- Below the diagonal: jxinject.internal uses a module listed above it, which is the healthy direction.
31→8 ktor uses bindings✕
- Connections
- 4 pairs of types, where a type in ktor uses a type in bindings.
- The types involved
org.kodein.di.ktor.CallScope→org.kodein.di.bindings.ScopeRegistryorg.kodein.di.ktor.CallScope→org.kodein.di.bindings.WeakContextScopeorg.kodein.di.ktor.SessionScope→org.kodein.di.bindings.Scopeorg.kodein.di.ktor.SessionScope→org.kodein.di.bindings.ScopeRegistry
- Direction
- ktor uses bindings, so a change to bindings can break ktor, while a change to ktor can't break bindings.
- Position
- Below the diagonal: ktor uses a module listed above it, which is the healthy direction.
31→13 ktor uses DI✕
- Connections
- 2 pairs of types, where a type in ktor uses a type in DI.
- The types involved
org.kodein.di.ktor.PluginKt→org.kodein.di.DI.MainBuilderorg.kodein.di.ktor.SubsKt→org.kodein.di.DI.MainBuilder
- Direction
- ktor uses DI, so a change to DI can break ktor, while a change to ktor can't break DI.
- Position
- Below the diagonal: ktor uses a module listed above it, which is the healthy direction.
31→15 ktor uses org.kodein.di✕
- Connections
- 3 pairs of types, where a type in ktor uses a type in org.kodein.di.
- The types involved
org.kodein.di.ktor.ClosestKt→org.kodein.di.DIorg.kodein.di.ktor.ClosestKt→org.kodein.di.LazyDIorg.kodein.di.ktor.SubsKt→org.kodein.di.Copy
- Direction
- ktor uses org.kodein.di, so a change to org.kodein.di can break ktor, while a change to ktor can't break org.kodein.di.
- Position
- Below the diagonal: ktor uses a module listed above it, which is the healthy direction.
32→8 tornadofx uses bindings✕
- Connections
- 2 pairs of types, where a type in tornadofx uses a type in bindings.
- The types involved
org.kodein.di.tornadofx.ComponentScope→org.kodein.di.bindings.WeakContextScopeorg.kodein.di.tornadofx.NodeScope→org.kodein.di.bindings.WeakContextScope
- Direction
- tornadofx uses bindings, so a change to bindings can break tornadofx, while a change to tornadofx can't break bindings.
- Position
- Below the diagonal: tornadofx uses a module listed above it, which is the healthy direction.
32→13 tornadofx uses DI✕
- Connections
- 2 pairs of types, where a type in tornadofx uses a type in DI.
- The types involved
org.kodein.di.tornadofx.ClosestKt→org.kodein.di.DI.MainBuilderorg.kodein.di.tornadofx.SubsKt→org.kodein.di.DI.MainBuilder
- Direction
- tornadofx uses DI, so a change to DI can break tornadofx, while a change to tornadofx can't break DI.
- Position
- Below the diagonal: tornadofx uses a module listed above it, which is the healthy direction.
32→15 tornadofx uses org.kodein.di✕
- Connections
- 4 pairs of types, where a type in tornadofx uses a type in org.kodein.di.
- The types involved
org.kodein.di.tornadofx.ClosestKt→org.kodein.di.DIorg.kodein.di.tornadofx.ClosestKt→org.kodein.di.LazyDIorg.kodein.di.tornadofx.SubsKt→org.kodein.di.Copyorg.kodein.di.tornadofx.SubsKt→org.kodein.di.LazyDI
- Direction
- tornadofx uses org.kodein.di, so a change to org.kodein.di can break tornadofx, while a change to tornadofx can't break org.kodein.di.
- Position
- Below the diagonal: tornadofx uses a module listed above it, which is the healthy direction.
33→13 Copy uses DI✕
- Connections
- 6 pairs of types, where a type in Copy uses a type in DI.
- The types involved
org.kodein.di.Copy.All→org.kodein.di.DI.Keyorg.kodein.di.Copy.AllButDSL→org.kodein.di.DI.Keyorg.kodein.di.Copy.Companion→org.kodein.di.DI.Keyorg.kodein.di.Copy.DSL→org.kodein.di.DI.Keyorg.kodein.di.Copy.NonCached→org.kodein.di.DI.Keyorg.kodein.di.Copy.None→org.kodein.di.DI.Key
- Direction
- Copy uses DI, so a change to DI can break Copy, while a change to Copy can't break DI.
- Position
- Below the diagonal: Copy uses a module listed above it, which is the healthy direction.
33→15 Copy uses org.kodein.di✕
- Connections
- 13 pairs of types, where a type in Copy uses a type in org.kodein.di.
- The types involved
org.kodein.di.Copy.All→org.kodein.di.Copyorg.kodein.di.Copy.All→org.kodein.di.DITreeorg.kodein.di.Copy.AllButDSL→org.kodein.di.DITreeorg.kodein.di.Copy.BaseDSL→org.kodein.di.Copyorg.kodein.di.Copy.BaseDSL→org.kodein.di.CopySpecsorg.kodein.di.Copy.BaseDSL→org.kodein.di.SearchDSLorg.kodein.di.Copy.Companion→org.kodein.di.CopySpecsorg.kodein.di.Copy.Companion→org.kodein.di.DITreeorg.kodein.di.Copy.DSL→org.kodein.di.DITreeorg.kodein.di.Copy.NonCached→org.kodein.di.Copyorg.kodein.di.Copy.NonCached→org.kodein.di.DITreeorg.kodein.di.Copy.None→org.kodein.di.Copyorg.kodein.di.Copy.None→org.kodein.di.DITree
- Direction
- Copy uses org.kodein.di, so a change to org.kodein.di can break Copy, while a change to Copy can't break org.kodein.di.
- Position
- Below the diagonal: Copy uses a module listed above it, which is the healthy direction.
33→19 Copy uses Copy.BaseDSL✕
- Connections
- 1 pair of types, where a type in Copy uses a type in Copy.BaseDSL.
- The types involved
org.kodein.di.Copy.BaseDSL→org.kodein.di.Copy.BaseDSL.Sentence
- Direction
- Copy uses Copy.BaseDSL, so a change to Copy.BaseDSL can break Copy, while a change to Copy can't break Copy.BaseDSL.
- Position
- Below the diagonal: Copy uses a module listed above it, which is the healthy direction.
34→8 android.support uses bindings✕
- Connections
- 2 pairs of types, where a type in android.support uses a type in bindings.
- The types involved
org.kodein.di.android.support.AndroidLifecycleScope→org.kodein.di.bindings.Scopeorg.kodein.di.android.support.AndroidLifecycleScope→org.kodein.di.bindings.ScopeRegistry
- Direction
- android.support uses bindings, so a change to bindings can break android.support, while a change to android.support can't break bindings.
- Position
- Below the diagonal: android.support uses a module listed above it, which is the healthy direction.
34→13 android.support uses DI✕
- Connections
- 1 pair of types, where a type in android.support uses a type in DI.
- The types involved
org.kodein.di.android.support.ModuleKt→org.kodein.di.DI.Module
- Direction
- android.support uses DI, so a change to DI can break android.support, while a change to android.support can't break DI.
- Position
- Below the diagonal: android.support uses a module listed above it, which is the healthy direction.
34→23 android.support uses android✕
- Connections
- 2 pairs of types, where a type in android.support uses a type in android.
- The types involved
org.kodein.di.android.support.ClosestKt→org.kodein.di.android.DIPropertyDelegateProviderorg.kodein.di.android.support.ClosestKt→org.kodein.di.android.LazyContextDIPropertyDelegateProvider
- Direction
- android.support uses android, so a change to android can break android.support, while a change to android.support can't break android.
- Position
- Below the diagonal: android.support uses a module listed above it, which is the healthy direction.
35→8 android.x uses bindings✕
- Connections
- 2 pairs of types, where a type in android.x uses a type in bindings.
- The types involved
org.kodein.di.android.x.AndroidLifecycleScope→org.kodein.di.bindings.Scopeorg.kodein.di.android.x.AndroidLifecycleScope→org.kodein.di.bindings.ScopeRegistry
- Direction
- android.x uses bindings, so a change to bindings can break android.x, while a change to android.x can't break bindings.
- Position
- Below the diagonal: android.x uses a module listed above it, which is the healthy direction.
35→13 android.x uses DI✕
- Connections
- 1 pair of types, where a type in android.x uses a type in DI.
- The types involved
org.kodein.di.android.x.ModuleKt→org.kodein.di.DI.Module
- Direction
- android.x uses DI, so a change to DI can break android.x, while a change to android.x can't break DI.
- Position
- Below the diagonal: android.x uses a module listed above it, which is the healthy direction.
35→23 android.x uses android✕
- Connections
- 2 pairs of types, where a type in android.x uses a type in android.
- The types involved
org.kodein.di.android.x.ClosestKt→org.kodein.di.android.DIPropertyDelegateProviderorg.kodein.di.android.x.ClosestKt→org.kodein.di.android.LazyContextDIPropertyDelegateProvider
- Direction
- android.x uses android, so a change to android can break android.x, while a change to android.x can't break android.
- Position
- Below the diagonal: android.x uses a module listed above it, which is the healthy direction.
36→13 internal.DIImpl uses DI✕
- Connections
- 1 pair of types, where a type in internal.DIImpl uses a type in DI.
- The types involved
org.kodein.di.internal.DIImpl.Companion→org.kodein.di.DI.MainBuilder
- Direction
- internal.DIImpl uses DI, so a change to DI can break internal.DIImpl, while a change to internal.DIImpl can't break DI.
- Position
- Below the diagonal: internal.DIImpl uses a module listed above it, which is the healthy direction.
36→15 internal.DIImpl uses org.kodein.di✕
- Connections
- 1 pair of types, where a type in internal.DIImpl uses a type in org.kodein.di.
- The types involved
org.kodein.di.internal.DIImpl.Companion→org.kodein.di.DI
- Direction
- internal.DIImpl uses org.kodein.di, so a change to org.kodein.di can break internal.DIImpl, while a change to internal.DIImpl can't break org.kodein.di.
- Position
- Below the diagonal: internal.DIImpl uses a module listed above it, which is the healthy direction.
36→29 internal.DIImpl uses internal✕
- Connections
- 1 pair of types, where a type in internal.DIImpl uses a type in internal.
- The types involved
org.kodein.di.internal.DIImpl.Companion→org.kodein.di.internal.DIMainBuilderImpl
- Direction
- internal.DIImpl uses internal, so a change to internal can break internal.DIImpl, while a change to internal.DIImpl can't break internal.
- Position
- Below the diagonal: internal.DIImpl uses a module listed above it, which is the healthy direction.
37→13 jxinject uses DI✕
- Connections
- 1 pair of types, where a type in jxinject uses a type in DI.
- The types involved
org.kodein.di.jxinject.JxInjectorModuleKt→org.kodein.di.DI.Module
- Direction
- jxinject uses DI, so a change to DI can break jxinject, while a change to jxinject can't break DI.
- Position
- Below the diagonal: jxinject uses a module listed above it, which is the healthy direction.
37→15 jxinject uses org.kodein.di✕
- Connections
- 3 pairs of types, where a type in jxinject uses a type in org.kodein.di.
- The types involved
org.kodein.di.jxinject.Jx→org.kodein.di.DIorg.kodein.di.jxinject.Jx→org.kodein.di.DirectDIorg.kodein.di.jxinject.JxInjector→org.kodein.di.DirectDI
- Direction
- jxinject uses org.kodein.di, so a change to org.kodein.di can break jxinject, while a change to jxinject can't break org.kodein.di.
- Position
- Below the diagonal: jxinject uses a module listed above it, which is the healthy direction.
37→30 jxinject uses jxinject.internal✕
- Connections
- 1 pair of types, where a type in jxinject uses a type in jxinject.internal.
- The types involved
org.kodein.di.jxinject.JxInjector→org.kodein.di.jxinject.internal.JxInjectorContainer
- Direction
- jxinject uses jxinject.internal, so a change to jxinject.internal can break jxinject, while a change to jxinject can't break jxinject.internal.
- Position
- Below the diagonal: jxinject uses a module listed above it, which is the healthy direction.
38→13 ktor.DIPlugin uses DI✕
- Connections
- 1 pair of types, where a type in ktor.DIPlugin uses a type in DI.
- The types involved
org.kodein.di.ktor.DIPlugin.Plugin→org.kodein.di.DI.MainBuilder
- Direction
- ktor.DIPlugin uses DI, so a change to DI can break ktor.DIPlugin, while a change to ktor.DIPlugin can't break DI.
- Position
- Below the diagonal: ktor.DIPlugin uses a module listed above it, which is the healthy direction.
38→31 ktor.DIPlugin uses ktor✕
- Connections
- 1 pair of types, where a type in ktor.DIPlugin uses a type in ktor.
- The types involved
org.kodein.di.ktor.DIPlugin.Plugin→org.kodein.di.ktor.DIPlugin
- Direction
- ktor.DIPlugin uses ktor, so a change to ktor can break ktor.DIPlugin, while a change to ktor.DIPlugin can't break ktor.
- Position
- Below the diagonal: ktor.DIPlugin uses a module listed above it, which is the healthy direction.
39→34 android.support.AndroidLifecycleScope uses android.support✕
- Connections
- 2 pairs of types, where a type in android.support.AndroidLifecycleScope uses a type in android.support.
- The types involved
org.kodein.di.android.support.AndroidLifecycleScope.multiItem→org.kodein.di.android.support.AndroidLifecycleScopeorg.kodein.di.android.support.AndroidLifecycleScope.singleItem→org.kodein.di.android.support.AndroidLifecycleScope
- Direction
- android.support.AndroidLifecycleScope uses android.support, so a change to android.support can break android.support.AndroidLifecycleScope, while a change to android.support.AndroidLifecycleScope can't break android.support.
- Position
- Below the diagonal: android.support.AndroidLifecycleScope uses a module listed above it, which is the healthy direction.
40→35 android.x.AndroidLifecycleScope uses android.x✕
- Connections
- 2 pairs of types, where a type in android.x.AndroidLifecycleScope uses a type in android.x.
- The types involved
org.kodein.di.android.x.AndroidLifecycleScope.multiItem→org.kodein.di.android.x.AndroidLifecycleScopeorg.kodein.di.android.x.AndroidLifecycleScope.singleItem→org.kodein.di.android.x.AndroidLifecycleScope
- Direction
- android.x.AndroidLifecycleScope uses android.x, so a change to android.x can break android.x.AndroidLifecycleScope, while a change to android.x.AndroidLifecycleScope can't break android.x.
- Position
- Below the diagonal: android.x.AndroidLifecycleScope 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 | 35 | High / Critical |
| A05:2025 — Injection | 8 | High / Critical |
Roadmap
Begin by documenting significant design decisions in a dedicated folder and adding a quick-start section to the root README to support new contributors. Simultaneously, address the 21 high-severity dependency vulnerabilities and restrict workflow token permissions to secure the supply chain. Finally, extend structured logging to all runnable modules to ensure full observability and diagnosability in production.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +6.9 pts | Medium | Architecture documentation |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +2.8 pts | Medium | Documentation (README) |
| Resolve the 21 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (21). | +1.7 pts | Medium | Dependency Vulnerabilities |
| Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. | +1.6 pts | Medium | Observability |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +0.6 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +0.6 pts | Low | Bus Factor |
| Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. | +0.5 pts | Low | Dependency Vulnerabilities |
| Resolve the 3 Orphaned file finding(s) in Knowledge Freshness — start with DIAware.kt (2), ParameterizedNew.kt. | +0.4 pts | Low | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| kodein-di-jxinject-jvm/src/main/kotlin/org/kodein/di/jxinject/internal/JxInjectorContainer.kt | 7.8 | Mixed | Cyclomatic Complexity: JxInjectorContainer.getter (cyclomatic 18) |
| kodein-di/src/commonMain/kotlin/org/kodein/di/internal/DIContainerImpl.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (12 corresponding lines) |
| kodein-di-conf/src/commonMain/kotlin/org/kodein/di/conf/ConfigurableDI.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| kodein-di/src/commonMain/kotlin/org/kodein/di/properties.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| framework/android/kodein-di-framework-android-core/src/main/java/org/kodein/di/android/module.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| compiler/kodein-resolver-test/src/commonTest/kotlin/org/kodein/di/resolver/CheckKSP.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| compiler/kodein-resolver-processor/src/main/kotlin/org/kodein/di/resolver/visitor/FunctionResolver.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| kodein-di/src/commonMain/kotlin/org/kodein/di/New.kt | 8.5 | Near-clean | God Classes: FileTooLong: di/New.kt |
| kodein-di/src/commonMain/kotlin/org/kodein/di/ParameterizedNew.kt | 8.5 | Near-clean | God Classes: FileTooLong: di/ParameterizedNew.kt |
| framework/compose/kodein-di-framework-android-x-compose/src/main/kotlin/org/kodein/di/compose/android/viewModel.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (14–15 lines × 2) |
| framework/compose/kodein-di-framework-compose/src/androidMain/kotlin/org/kodein/di/compose/viewModel.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (11 lines × 2) |
| framework/android/kodein-di-framework-android-x-viewmodel-savedstate/src/main/java/org/kodein/di/android/x/viewmodel/savedstate/DIAware.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (5 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog 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. 55 of 55 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 55 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, 56 of 449 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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 |
| Watchdog 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 |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog 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 (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D12 Dependency Hygiene — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Gradle tree, and its score reflects currency alone.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D20 ADR Quality — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The ADR expectation is gated on whether a repository ships a deployable product. Our repo-kind classifier reads .NET project files and the host and package markers of the other ecosystems it knows (a Go `package main`, a Cargo binary, a package.json `bin`, `start` script or application dev server such as Vite or Next, Python console scripts or a Django/WSGI entry point, a Spring Boot / WAR / Gradle application build, a Rack or Rails app, a Composer project, an OTP release or escript, a Dockerfile, a Procfile, a Platform.sh `.platform/routes.yaml`, and the corresponding published-package manifests, including an OTP `*.app.src`, a Drupal module's `*.info` and a Claude Code `.claude-plugin/plugin.json`), and found none here, so we could not tell what kind of repository this is and did not assess its ADR log. This is a gap in our analyzer, not a finding about this repository.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog 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: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog 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. `framework/android/kodein-di-framework-android-core/src/main/java/org/kodein/di/android/retained.kt`, `framework/android/kodein-di-framework-android-core/src/main/java/org/kodein/di/android/sub.kt`, `framework/compose/kodein-di-framework-compose-runtime/src/commonMain/kotlin/org/kodein/di/compose/subDI.kt`, `framework/compose/kodein-di-framework-compose-runtime/src/commonMain/kotlin/org/kodein/di/compose/withDI.kt`, `framework/ktor/kodein-di-framework-ktor-server-jvm/src/main/kotlin/org/kodein/di/ktor/plugin.kt`, … (+14 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 — Watchdog 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 Kodein, 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.
- C2 Access Controls — not measured this run — Watchdog 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 authorization 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 authorization controls.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Kotlin 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — Watchdog 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.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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.
- 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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was JxInjectorContainer.getter at 18.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with JxInjectorContainer.getter (cyclomatic 18). — Refactoring it lifts Cyclomatic Complexity from 9.7 to about 10.0/10.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was JxInjectorContainer.getter at 19.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with JxInjectorContainer.getter (cognitive 19). — Refactoring it lifts Cognitive Complexity from 9.7 to about 10.0/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 FileTooLong finding(s) in God Classes — start with New.kt, ParameterizedNew.kt. — One of this dimension's main actionable groups (2 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
4 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 1 Edited copy of a member (12 corresponding lines) finding(s) in Code Duplication — start with DIContainerImpl.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (14–15 lines × 2) finding(s) in Code Duplication — start with viewModel.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with viewModel.kt. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
19 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence, with abstractness counted on 17 of the 19 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 20 classes have LCOM4 above 3.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Java/Kotlin (repository root, Gradle): measured (0 flaky).
D12 · Dependency Hygiene
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 724 artifact(s) resolved, 476 of them gradable against Maven Central, and 381 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 20 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 20 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 1 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 11 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
3 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is kodein-di/src/commonMain/kotlin/org/kodein/di/DI.kt. Counted over 44 of the 129 production source files in this repository: 83 are under the ~2,400-byte size floor this dimension measures over, and the remaining 2 have no attributable history left to measure.
D17 · Explicit Debt
5 deducted task-comment markers across 10866 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 5 TodoComment finding(s) in Explicit Debt — start with ConfigurableDI.kt, properties.kt, module.kt. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 23 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 16 build units (Gradle) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
8 finding(s): 0 critical, 8 high, 0 medium, 0 low. 8 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `gradlew` (line 74, line 180) — 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
- No action in Static Analysis (SAST) — all 4 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (4 issue-level, 0 of them charged here).
- No action in Static Analysis (SAST) — all 4 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (4 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
29 finding(s): 0 critical, 22 high, 4 medium, 3 low.
What to do
- Resolve the 21 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (21). — One of this dimension's main actionable groups (21 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
D34 · Knowledge Freshness
3 of 46 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is kodein-di/src/commonMain/kotlin/org/kodein/di/ParameterizedNew.kt. Counted over 46 of the 129 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 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 31 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
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 18 of 18 project(s) that lack one — worth up to 2 pts.
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
P2 · Observability
- Only 2/4 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `framework/ktor/kodein-di-framework-ktor-server-controller-jvm`, `framework/ktor/kodein-di-framework-ktor-server-jvm`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Consider OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) and a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1903 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 98% | Exemplary | Solid. |
| Architecture | 99% | Exemplary | Strongest area. |
| Maturity | 52% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 50% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 71% | Adequate — gated by D30, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 63 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.
- AC7 A11y enforcement — 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 — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean.
- 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
- AX6 Interface segregation — no public interfaces
- 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, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — Not assessed: these authorization 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 authorization 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.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store 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, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported 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, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~8594 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — Repository kind not determined
- D21 Naming Consistency — Naming consistency is measured on C# only; Java, Kotlin 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+ projects each declaring an entity of their own. 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# and Visual Basic comments only — this repository's production source is .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.kt), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 19 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- D9 Test Distribution — Test source is present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (28 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 23 current-state document(s) make no claim of a kind M4 checks. 2 claim(s) of kinds M4 does not check were not checked (path 1, environment variable 1); M4 checks only links and versions.
- 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 applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, 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 applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Kotlin code has 12,124 production line(s), 6 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Kotlin was read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Kotlin request outside a suspend function has no caller's cancellation to honour
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 30 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 22 finding(s)
- TodoComment kodein-di-conf/src/commonMain/kotlin/org/kodein/di/conf/ConfigurableDI.kt:18
- TodoComment kodein-di/src/commonMain/kotlin/org/kodein/di/properties.kt:42
- TodoComment framework/android/kodein-di-framework-android-core/src/main/java/org/kodein/di/android/module.kt:115
- TodoComment compiler/kodein-resolver-test/src/commonTest/kotlin/org/kodein/di/resolver/CheckKSP.kt:10
- TodoComment compiler/kodein-resolver-processor/src/main/kotlin/org/kodein/di/resolver/visitor/FunctionResolver.kt:67
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileTooLong: di/New.kt kodein-di/src/commonMain/kotlin/org/kodein/di/New.kt
- FileTooLong: di/ParameterizedNew.kt kodein-di/src/commonMain/kotlin/org/kodein/di/ParameterizedNew.kt
- REDACTED
- REDACTED
- JxInjectorContainer.getter (cyclomatic 18) kodein-di-jxinject-jvm/src/main/kotlin/org/kodein/di/jxinject/internal/JxInjectorContainer.kt:54
- JxInjectorContainer.getter (cognitive 19) kodein-di-jxinject-jvm/src/main/kotlin/org/kodein/di/jxinject/internal/JxInjectorContainer.kt:54
- REDACTED
- Edited copy of a member (12 corresponding lines) kodein-di/src/commonMain/kotlin/org/kodein/di/internal/DIContainerImpl.kt:144
- Duplicated block (14–15 lines × 2) framework/compose/kodein-di-framework-android-x-compose/src/main/kotlin/org/kodein/di/compose/android/viewModel.kt:94
- Duplicated block (11 lines × 2) framework/compose/kodein-di-framework-compose/src/androidMain/kotlin/org/kodein/di/compose/viewModel.kt:24
- Duplicated block (5 lines × 2) framework/android/kodein-di-framework-android-x-viewmodel-savedstate/src/main/java/org/kodein/di/android/x/viewmodel/savedstate/DIAware.kt:42
- Duplicated block (3–5 lines × 3) kodein-di/src/commonMain/kotlin/org/kodein/di/internal/DIContainerImpl.kt:150
- Off the main sequence: :framework:android:kodein-di-framework-android-x
Minor — 16 finding(s)
- REDACTED
- REDACTED
- REDACTED
- Orphaned file kodein-di/src/commonMain/kotlin/org/kodein/di/ParameterizedNew.kt:1
- Orphaned file framework/android/kodein-di-framework-android-x-viewmodel-savedstate/src/main/java/org/kodein/di/android/x/viewmodel/savedstate/DIAware.kt:1
- Orphaned file framework/android/kodein-di-framework-android-x-viewmodel/src/main/java/org/kodein/di/android/x/viewmodel/DIAware.kt:1
- Off-boarding risk: anonymized user #1
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No SAST
Minor — 381 finding(s)
- Outdated (compile): com.google.guava:guava
- Outdated (compile): com.google.guava:failureaccess
- Outdated (compile): org.checkerframework:checker-qual
- Outdated (compile): com.google.errorprone:error_prone_annotations
- Outdated (compile): com.google.j2objc:j2objc-annotations
- Outdated (compile): net.java.dev.jna:jna-platform
- Outdated (compile): net.java.dev.jna:jna
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk8
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib
- Outdated (compile): org.jetbrains:annotations
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk7
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-common
- Outdated (compile): com.google.protobuf:protobuf-java
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-core
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-bom
- Outdated (compile): com.google.api.grpc:proto-google-common-protos
- Outdated (compile): com.google.auto:auto-common
- Outdated (compile): com.google.dagger:dagger
- Outdated (compile): com.google.protobuf:protobuf-kotlin
- Outdated (compile): org.jetbrains.kotlin:kotlin-reflect
- Outdated (compile): com.google.protobuf:protobuf-java-util
- Outdated (compile): com.google.code.gson:gson
- Outdated (compile): org.jetbrains.kotlinx:atomicfu
- Outdated (compile): org.jetbrains.kotlinx:atomicfu-jvm
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b6869b42d3f340e08cc93a54b9bb4eb6/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b6869b42d3f340e08cc93a54b9bb4eb6/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/watchdog-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 kotlin-js-store . | 8 | 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/** . --skip-db-update | 29 | 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 19 file(s) — `framework/android/kodein-di-framework-android-core/src/main/java/org/kodein/di/android/retained.kt`, `framework/android/kodein-di-framework-android-core/src/main/java/org/kodein/di/android/sub.kt`, `framework/compose/kodein-di-framework-compose-runtime/src/commonMain/kotlin/org/kodein/di/compose/subDI.kt`, `framework/compose/kodein-di-framework-compose-runtime/src/commonMain/kotlin/org/kodein/di/compose/withDI.kt`, `framework/ktor/kodein-di-framework-ktor-server-jvm/src/main/kotlin/org/kodein/di/ktor/plugin.kt`, … (+14 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/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |