Executive summary
coil-kt/coil is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 56 out of 100, which the At risk rating leaves unchanged.
Code Health, at 45, is the weakest lens and counts most in the score. The best first steps are adding type checking and removing the unused code, each worth about 6 points. Raising Code Health to 70 would lift the score to about 63.
Twenty-six known security holes in the packages the code depends on can be used by attackers. Twenty-four 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. Passing outside input through environment variables would fix the pipeline step that puts outside input straight into a shell command. The loop of parts of the code that depend on each other needs breaking by moving the shared parts into a project of their own.
The product code is 20,655 lines, about €36,000 to rebuild.
If Code Health rose from 45 to 70, the lowest score rated Strong, the score would rise from 56 to about 63.
New since the last survey: 30 findings
- Code Duplication · Edited copy of a member (44 corresponding lines) coil-core/src/androidMain/kotlin/coil3/decode/StaticImageDecoder.kt
- Code Duplication · Edited copy of a member (27 corresponding lines) coil-core/src/androidMain/kotlin/coil3/size/ScaleDrawable.kt
- Code Duplication · Edited copy of a member (26 corresponding lines) coil-compose-core/src/androidMain/kotlin/coil3/compose/AsyncImagePainter.android.kt
- Code Duplication · Edited copy of a member (16 corresponding lines) coil-core/src/androidMain/kotlin/coil3/decode/StaticImageDecoder.kt
- Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) coil-compose/src/commonMain/kotlin/coil3/compose/SingletonAsyncImage.kt
- Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) coil-compose-core/src/commonMain/kotlin/coil3/compose/internal/ContentPainterModifier.kt
- Code Duplication · Edited copy of a member (13 corresponding lines) coil-compose-core/src/commonMain/kotlin/coil3/compose/AsyncImage.kt
- Code Duplication · Edited copy of a member (13 corresponding lines) coil-compose-core/src/commonMain/kotlin/coil3/compose/AsyncImage.kt
- Code Duplication · Edited copy of a member (12 corresponding lines) coil-compose/src/commonMain/kotlin/coil3/compose/SingletonAsyncImage.kt
- Code Duplication · Edited copy of a member (14 corresponding lines) coil-core/src/androidMain/kotlin/coil3/request/RequestService.android.kt
- Code Duplication · Duplicated block (33 lines × 2) coil-core/src/androidMain/kotlin/coil3/decode/StaticImageDecoder.kt
- Code Duplication · Duplicated block (23 lines × 2) coil-core/src/jsCommonMain/kotlin/coil3/decode/SkiaImageDecoder.jsCommon.kt
- Code Duplication · Duplicated block (15–16 lines × 2) coil-core/src/androidMain/kotlin/coil3/size/ScaleDrawable.kt
- Code Duplication · Duplicated block (16 lines × 2) coil-core/src/commonMain/kotlin/coil3/decode/DecodeUtils.kt
- Code Duplication · Duplicated block (15 lines × 2) coil-compose/src/commonMain/kotlin/coil3/compose/SingletonAsyncImage.kt
- Code Duplication · Duplicated block (13 lines × 3) coil-compose/src/commonMain/kotlin/coil3/compose/SingletonAsyncImage.kt
- Code Duplication · Duplicated block (11 lines × 2) coil-core/src/androidMain/kotlin/coil3/ColorImage.kt
- Code Duplication · Duplicated block (56 lines × 2) coil-network-ktor2/src/commonMain/kotlin/coil3/network/ktor2/KtorNetworkFetcher.kt
- Code Duplication · Duplicated block (61 lines × 2) coil-network-ktor2/src/commonMain/kotlin/coil3/network/ktor2/internal/utils.kt
- Code Duplication · Duplicated block (17 lines × 2) coil-network-ktor2/src/jvmCommonMain/kotlin/coil3/network/ktor2/internal/utils.jvmCommon.kt
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dead Code · Dead file (~34 LoC) karma.config.d/10-timeouts.js
- Exception handling · Swallowed exception (empty catch) coil-network-httpengine/src/androidMain/kotlin/coil3/network/httpengine/internal/HttpEngineNetworkClient.kt
- Exception handling · Swallowed exception (empty catch) coil-network-httpengine/src/androidMain/kotlin/coil3/network/httpengine/internal/HttpEngineUrlRequestCallback.kt
Fixed since the last survey: 15 findings
- Code Duplication · Duplicated block (33 lines × 2) coil-core/src/androidMain/kotlin/coil3/decode/StaticImageDecoder.kt
- Code Duplication · Duplicated block (23 lines × 2) coil-core/src/jsCommonMain/kotlin/coil3/decode/SkiaImageDecoder.jsCommon.kt
- Code Duplication · Duplicated block (16 lines × 2) coil-core/src/commonMain/kotlin/coil3/decode/DecodeUtils.kt
- Code Duplication · Duplicated block (11 lines × 2) coil-core/src/androidMain/kotlin/coil3/ColorImage.kt
- Code Duplication · Duplicated block (56 lines × 2) coil-network-ktor2/src/commonMain/kotlin/coil3/network/ktor2/KtorNetworkFetcher.kt
- Code Duplication · Duplicated block (61 lines × 2) coil-network-ktor2/src/commonMain/kotlin/coil3/network/ktor2/internal/utils.kt
- Code Duplication · Duplicated block (17 lines × 2) coil-network-ktor2/src/jvmCommonMain/kotlin/coil3/network/ktor2/internal/utils.jvmCommon.kt
- Secret Scanning · Leaked secret: private-key-store .github/debug.keystore
- Secrets (history) · High secret: WD-SECRET-0004 .github/debug.keystore
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dead Code · Dead file (~33 LoC) karma.config.d/10-timeouts.js
Rebuild cost: about €36,000 · Estimate
| Cost to rebuild | €12,000 to €61,000, for 201 to 637 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 56. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 20,655 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 disk | 2 size | 3 EventListener | 4 Extras | 5 fetch | 6 network.CacheStrategy | 7 fetch.Fetcher | 8 request.ImageRequest | 9 util | 10 transform | 11 intercept.EngineInterceptor | 12 memory | 13 RealImageLoader | 14 ImageLoader | 15 request | 16 decode | 17 intercept | 18 transition | 19 decode.Decoder | 20 gif | 21 transition.Transition | 22 video | 23 ComponentRegistry | 24 coil3 | 25 compose.AsyncImagePainter | 26 decode.BitmapFactoryDecoder | 27 decode.BlackholeDecoder | 28 decode.SkiaImageDecoder | 29 decode.StaticImageDecoder | 30 fetch.BlobUriFetcher | 31 network | 32 svg | 33 svg.SvgDecoder | 34 video.MediaDataSourceFetcher | 35 video.VideoFrameDecoder | 36 compose.internal | 37 network.NetworkFetcher | 38 network.httpengine | 39 svg.internal | 40 compose |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 disk | ||||||||||||||||||||||||||||||||||||||||
| 2 size | ||||||||||||||||||||||||||||||||||||||||
| 3 EventListener | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 4 Extras | 2 | |||||||||||||||||||||||||||||||||||||||
| 5 fetch | 10 | 3 | 8 | |||||||||||||||||||||||||||||||||||||
| 6 network.CacheStrategy | 4 | |||||||||||||||||||||||||||||||||||||||
| 7 fetch.Fetcher | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 8 request.ImageRequest | 11 | 1 | 1 | 11 | 1 | 5 | ||||||||||||||||||||||||||||||||||
| 9 util | 5 | 2 | 4 | 2 | 1 | 5 | ||||||||||||||||||||||||||||||||||
| 10 transform | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 intercept.EngineInterceptor | 2 | 2 | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 12 memory | 2 | 1 | 1 | 4 | 8 | |||||||||||||||||||||||||||||||||||
| 13 RealImageLoader | 1 | 1 | 1 | 1 | 1 | 6 | 6 | 4 | ||||||||||||||||||||||||||||||||
| 14 ImageLoader | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 5 | |||||||||||||||||||||||||||||
| 15 request | 13 | 1 | 1 | 5 | 5 | 1 | 1 | 1 | 1 | 13 | ||||||||||||||||||||||||||||||
| 16 decode | 2 | 1 | 5 | 3 | ||||||||||||||||||||||||||||||||||||
| 17 intercept | 1 | 2 | 3 | 1 | 2 | 1 | 9 | 6 | ||||||||||||||||||||||||||||||||
| 18 transition | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 19 decode.Decoder | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 20 gif | 1 | 1 | 1 | 1 | 2 | 6 | ||||||||||||||||||||||||||||||||||
| 21 transition.Transition | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 22 video | 1 | 1 | 2 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 23 ComponentRegistry | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 coil3 | 2 | 2 | 5 | 4 | 1 | 3 | 1 | 2 | 2 | 3 | 16 | 3 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||
| 25 compose.AsyncImagePainter | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 26 decode.BitmapFactoryDecoder | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 27 decode.BlackholeDecoder | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 28 decode.SkiaImageDecoder | 1 | 1 | 4 | 4 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 29 decode.StaticImageDecoder | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 30 fetch.BlobUriFetcher | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 31 network | 1 | 1 | 5 | 2 | 1 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||
| 32 svg | 2 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 33 svg.SvgDecoder | 1 | 1 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||
| 34 video.MediaDataSourceFetcher | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 video.VideoFrameDecoder | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 36 compose.internal | 3 | 2 | 3 | 2 | 7 | |||||||||||||||||||||||||||||||||||
| 37 network.NetworkFetcher | 1 | 1 | 1 | 3 | 4 | |||||||||||||||||||||||||||||||||||
| 38 network.httpengine | 1 | 2 | 1 | 5 | 9 | |||||||||||||||||||||||||||||||||||
| 39 svg.internal | 1 | 2 | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 40 compose | 4 | 1 | 1 | 1 | 3 | 10 | 9 | 3 |
3→15 EventListener uses request part of a loop✕
- Connections
- 1 pair of types, where a type in EventListener uses a type in request.
- The types involved
coil3.EventListener.Factory→coil3.request.ImageRequest
- Direction
- EventListener uses request, so a change to request can break EventListener, while a change to EventListener can't break request.
- 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→24 EventListener uses coil3 part of a loop✕
- Connections
- 2 pairs of types, where a type in EventListener uses a type in coil3.
- The types involved
coil3.EventListener.Companion→coil3.EventListenercoil3.EventListener.Factory→coil3.EventListener
- Direction
- EventListener uses coil3, so a change to coil3 can break EventListener, while a change to EventListener can't break coil3.
- 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→24 Extras uses coil3 part of a loop✕
- Connections
- 2 pairs of types, where a type in Extras uses a type in coil3.
- The types involved
coil3.Extras.Builder→coil3.Extrascoil3.Extras.Companion→coil3.Extras
- Direction
- Extras uses coil3, so a change to coil3 can break Extras, while a change to Extras can't break coil3.
- 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→15 fetch uses request part of a loop✕
- Connections
- 10 pairs of types, where a type in fetch uses a type in request.
- The types involved
coil3.fetch.AssetUriFetcher→coil3.request.Optionscoil3.fetch.BlobUriFetcher→coil3.request.Optionscoil3.fetch.ByteArrayFetcher→coil3.request.Optionscoil3.fetch.ByteBufferFetcher→coil3.request.Optionscoil3.fetch.ContentUriFetcher→coil3.request.Optionscoil3.fetch.DataUriFetcher→coil3.request.Optionscoil3.fetch.DrawableFetcher→coil3.request.Optionscoil3.fetch.FileUriFetcher→coil3.request.Optionscoil3.fetch.JarFileFetcher→coil3.request.Optionscoil3.fetch.ResourceUriFetcher→coil3.request.Options
- Direction
- fetch uses request, so a change to request can break fetch, while a change to fetch can't break request.
- 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→16 fetch uses decode part of a loop✕
- Connections
- 3 pairs of types, where a type in fetch uses a type in decode.
- The types involved
coil3.fetch.ImageFetchResult→coil3.decode.DataSourcecoil3.fetch.SourceFetchResult→coil3.decode.DataSourcecoil3.fetch.SourceFetchResult→coil3.decode.ImageSource
- Direction
- fetch uses decode, so a change to decode can break fetch, while a change to fetch can't break decode.
- 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→24 fetch uses coil3 part of a loop✕
- Connections
- 8 pairs of types, where a type in fetch uses a type in coil3.
- The types involved
coil3.fetch.AssetUriFetcher→coil3.Uricoil3.fetch.BlobUriFetcher→coil3.Uricoil3.fetch.ContentUriFetcher→coil3.Uricoil3.fetch.DataUriFetcher→coil3.Uricoil3.fetch.FileUriFetcher→coil3.Uricoil3.fetch.ImageFetchResult→coil3.Imagecoil3.fetch.JarFileFetcher→coil3.Uricoil3.fetch.ResourceUriFetcher→coil3.Uri
- Direction
- fetch uses coil3, so a change to coil3 can break fetch, while a change to fetch can't break coil3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→31 network.CacheStrategy uses network part of a loop✕
- Connections
- 4 pairs of types, where a type in network.CacheStrategy uses a type in network.
- The types involved
coil3.network.CacheStrategy.Companion→coil3.network.CacheStrategycoil3.network.CacheStrategy.ReadResult→coil3.network.NetworkRequestcoil3.network.CacheStrategy.ReadResult→coil3.network.NetworkResponsecoil3.network.CacheStrategy.WriteResult→coil3.network.NetworkResponse
- Direction
- network.CacheStrategy uses network, so a change to network can break network.CacheStrategy, while a change to network.CacheStrategy can't break network.
- 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→5 fetch.Fetcher uses fetch✕
- Connections
- 1 pair of types, where a type in fetch.Fetcher uses a type in fetch.
- The types involved
coil3.fetch.Fetcher.Factory→coil3.fetch.Fetcher
- Direction
- fetch.Fetcher uses fetch, so a change to fetch can break fetch.Fetcher, while a change to fetch.Fetcher can't break fetch.
- Position
- Below the diagonal: fetch.Fetcher uses a module listed above it, which is the healthy direction.
7→15 fetch.Fetcher uses request part of a loop✕
- Connections
- 1 pair of types, where a type in fetch.Fetcher uses a type in request.
- The types involved
coil3.fetch.Fetcher.Factory→coil3.request.Options
- Direction
- fetch.Fetcher uses request, so a change to request can break fetch.Fetcher, while a change to fetch.Fetcher can't break request.
- 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→24 fetch.Fetcher uses coil3 part of a loop✕
- Connections
- 1 pair of types, where a type in fetch.Fetcher uses a type in coil3.
- The types involved
coil3.fetch.Fetcher.Factory→coil3.ImageLoader
- Direction
- fetch.Fetcher uses coil3, so a change to coil3 can break fetch.Fetcher, while a change to fetch.Fetcher can't break coil3.
- 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 request.ImageRequest uses size✕
- Connections
- 11 pairs of types, where a type in request.ImageRequest uses a type in size.
- The types involved
coil3.request.ImageRequest.Builder→coil3.size.Dimensioncoil3.request.ImageRequest.Builder→coil3.size.Precisioncoil3.request.ImageRequest.Builder→coil3.size.Scalecoil3.request.ImageRequest.Builder→coil3.size.Sizecoil3.request.ImageRequest.Builder→coil3.size.SizeResolvercoil3.request.ImageRequest.Defaults→coil3.size.Precisioncoil3.request.ImageRequest.Defaults→coil3.size.Scalecoil3.request.ImageRequest.Defaults→coil3.size.SizeResolvercoil3.request.ImageRequest.Defined→coil3.size.Precisioncoil3.request.ImageRequest.Defined→coil3.size.Scalecoil3.request.ImageRequest.Defined→coil3.size.SizeResolver
- Direction
- request.ImageRequest uses size, so a change to size can break request.ImageRequest, while a change to request.ImageRequest can't break size.
- Position
- Below the diagonal: request.ImageRequest uses a module listed above it, which is the healthy direction.
8→4 request.ImageRequest uses Extras✕
- Connections
- 1 pair of types, where a type in request.ImageRequest uses a type in Extras.
- The types involved
coil3.request.ImageRequest.Builder→coil3.Extras.Builder
- Direction
- request.ImageRequest uses Extras, so a change to Extras can break request.ImageRequest, while a change to request.ImageRequest can't break Extras.
- Position
- Below the diagonal: request.ImageRequest uses a module listed above it, which is the healthy direction.
8→7 request.ImageRequest uses fetch.Fetcher✕
- Connections
- 1 pair of types, where a type in request.ImageRequest uses a type in fetch.Fetcher.
- The types involved
coil3.request.ImageRequest.Builder→coil3.fetch.Fetcher.Factory
- Direction
- request.ImageRequest uses fetch.Fetcher, so a change to fetch.Fetcher can break request.ImageRequest, while a change to request.ImageRequest can't break fetch.Fetcher.
- Position
- Below the diagonal: request.ImageRequest uses a module listed above it, which is the healthy direction.
8→15 request.ImageRequest uses request part of a loop✕
- Connections
- 11 pairs of types, where a type in request.ImageRequest uses a type in request.
- The types involved
coil3.request.ImageRequest.Builder→coil3.request.CachePolicycoil3.request.ImageRequest.Builder→coil3.request.ErrorResultcoil3.request.ImageRequest.Builder→coil3.request.ImageRequestcoil3.request.ImageRequest.Builder→coil3.request.SuccessResultcoil3.request.ImageRequest.Defaults→coil3.request.CachePolicycoil3.request.ImageRequest.Defaults→coil3.request.ImageRequestcoil3.request.ImageRequest.Defined→coil3.request.CachePolicycoil3.request.ImageRequest.Defined→coil3.request.ImageRequestcoil3.request.ImageRequest.Listener→coil3.request.ErrorResultcoil3.request.ImageRequest.Listener→coil3.request.ImageRequestcoil3.request.ImageRequest.Listener→coil3.request.SuccessResult
- Direction
- request.ImageRequest uses request, so a change to request can break request.ImageRequest, while a change to request.ImageRequest can't break request.
- 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→19 request.ImageRequest uses decode.Decoder part of a loop✕
- Connections
- 1 pair of types, where a type in request.ImageRequest uses a type in decode.Decoder.
- The types involved
coil3.request.ImageRequest.Builder→coil3.decode.Decoder.Factory
- Direction
- request.ImageRequest uses decode.Decoder, so a change to decode.Decoder can break request.ImageRequest, while a change to request.ImageRequest can't break decode.Decoder.
- 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→24 request.ImageRequest uses coil3 part of a loop✕
- Connections
- 5 pairs of types, where a type in request.ImageRequest uses a type in coil3.
- The types involved
coil3.request.ImageRequest.Builder→coil3.Imagecoil3.request.ImageRequest.Builder→coil3.PlatformContextcoil3.request.ImageRequest.Defaults→coil3.Extrascoil3.request.ImageRequest.Defaults→coil3.Imagecoil3.request.ImageRequest.Defined→coil3.Image
- Direction
- request.ImageRequest uses coil3, so a change to coil3 can break request.ImageRequest, while a change to request.ImageRequest can't break coil3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→2 util uses size✕
- Connections
- 5 pairs of types, where a type in util uses a type in size.
- The types involved
coil3.util.DrawableUtils→coil3.size.Scalecoil3.util.DrawableUtils→coil3.size.Sizecoil3.util.HardwareBitmapService→coil3.size.Sizecoil3.util.ImmutableHardwareBitmapService→coil3.size.Sizecoil3.util.LimitedFileDescriptorHardwareBitmapService→coil3.size.Size
- Direction
- util uses size, so a change to size can break util, while a change to util can't break size.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
9→7 util uses fetch.Fetcher✕
- Connections
- 2 pairs of types, where a type in util uses a type in fetch.Fetcher.
- The types involved
coil3.util.FetcherServiceLoaderTarget→coil3.fetch.Fetcher.Factorycoil3.util.UtilsKt→coil3.fetch.Fetcher.Factory
- Direction
- util uses fetch.Fetcher, so a change to fetch.Fetcher can break util, while a change to util can't break fetch.Fetcher.
- Position
- Below the diagonal: util uses a module listed above it, which is the healthy direction.
9→15 util uses request part of a loop✕
- Connections
- 4 pairs of types, where a type in util uses a type in request.
- The types involved
coil3.util.CoilUtils→coil3.request.ImageResultcoil3.util.UtilsKt→coil3.request.ErrorResultcoil3.util.UtilsKt→coil3.request.ImageRequestcoil3.util.UtilsKt→coil3.request.Options
- Direction
- util uses request, so a change to request can break util, while a change to util can't break request.
- 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→19 util uses decode.Decoder part of a loop✕
- Connections
- 2 pairs of types, where a type in util uses a type in decode.Decoder.
- The types involved
coil3.util.DecoderServiceLoaderTarget→coil3.decode.Decoder.Factorycoil3.util.UtilsKt→coil3.decode.Decoder.Factory
- Direction
- util uses decode.Decoder, so a change to decode.Decoder can break util, while a change to util can't break decode.Decoder.
- 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→23 util uses ComponentRegistry part of a loop✕
- Connections
- 1 pair of types, where a type in util uses a type in ComponentRegistry.
- The types involved
coil3.util.UtilsKt→coil3.ComponentRegistry.Builder
- Direction
- util uses ComponentRegistry, so a change to ComponentRegistry can break util, while a change to util can't break ComponentRegistry.
- 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→24 util uses coil3 part of a loop✕
- Connections
- 5 pairs of types, where a type in util uses a type in coil3.
- The types involved
coil3.util.AndroidSystemCallbacks→coil3.RealImageLoadercoil3.util.SystemCallbacksKt→coil3.RealImageLoadercoil3.util.UtilsKt→coil3.EventListenercoil3.util.UtilsKt→coil3.Imagecoil3.util.UtilsKt→coil3.Uri
- Direction
- util uses coil3, so a change to coil3 can break util, while a change to util can't break coil3.
- 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→2 transform uses size✕
- Connections
- 3 pairs of types, where a type in transform uses a type in size.
- The types involved
coil3.transform.CircleCropTransformation→coil3.size.Sizecoil3.transform.RoundedCornersTransformation→coil3.size.Sizecoil3.transform.Transformation→coil3.size.Size
- Direction
- transform uses size, so a change to size can break transform, while a change to transform can't break size.
- Position
- Below the diagonal: transform uses a module listed above it, which is the healthy direction.
10→9 transform uses util✕
- Connections
- 1 pair of types, where a type in transform uses a type in util.
- The types involved
coil3.transform.RoundedCornersTransformation→coil3.util.IntPair
- Direction
- transform uses util, so a change to util can break transform, while a change to transform can't break util.
- Position
- Below the diagonal: transform uses a module listed above it, which is the healthy direction.
11→9 intercept.EngineInterceptor uses util✕
- Connections
- 2 pairs of types, where a type in intercept.EngineInterceptor uses a type in util.
- The types involved
coil3.intercept.EngineInterceptor.androidKt→coil3.util.Loggercoil3.intercept.EngineInterceptor.nonAndroidKt→coil3.util.Logger
- Direction
- intercept.EngineInterceptor uses util, so a change to util can break intercept.EngineInterceptor, while a change to intercept.EngineInterceptor can't break util.
- Position
- Below the diagonal: intercept.EngineInterceptor uses a module listed above it, which is the healthy direction.
11→10 intercept.EngineInterceptor uses transform✕
- Connections
- 2 pairs of types, where a type in intercept.EngineInterceptor uses a type in transform.
- The types involved
coil3.intercept.EngineInterceptor.androidKt→coil3.transform.Transformationcoil3.intercept.EngineInterceptor.nonAndroidKt→coil3.transform.Transformation
- Direction
- intercept.EngineInterceptor uses transform, so a change to transform can break intercept.EngineInterceptor, while a change to intercept.EngineInterceptor can't break transform.
- Position
- Below the diagonal: intercept.EngineInterceptor uses a module listed above it, which is the healthy direction.
11→15 intercept.EngineInterceptor uses request part of a loop✕
- Connections
- 2 pairs of types, where a type in intercept.EngineInterceptor uses a type in request.
- The types involved
coil3.intercept.EngineInterceptor.androidKt→coil3.request.Optionscoil3.intercept.EngineInterceptor.nonAndroidKt→coil3.request.Options
- Direction
- intercept.EngineInterceptor uses request, so a change to request can break intercept.EngineInterceptor, while a change to intercept.EngineInterceptor can't break request.
- 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→16 intercept.EngineInterceptor uses decode part of a loop✕
- Connections
- 1 pair of types, where a type in intercept.EngineInterceptor uses a type in decode.
- The types involved
coil3.intercept.EngineInterceptor.ExecuteResult→coil3.decode.DataSource
- Direction
- intercept.EngineInterceptor uses decode, so a change to decode can break intercept.EngineInterceptor, while a change to intercept.EngineInterceptor can't break decode.
- 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→24 intercept.EngineInterceptor uses coil3 part of a loop✕
- Connections
- 3 pairs of types, where a type in intercept.EngineInterceptor uses a type in coil3.
- The types involved
coil3.intercept.EngineInterceptor.ExecuteResult→coil3.Imagecoil3.intercept.EngineInterceptor.androidKt→coil3.Imagecoil3.intercept.EngineInterceptor.nonAndroidKt→coil3.Image
- Direction
- intercept.EngineInterceptor uses coil3, so a change to coil3 can break intercept.EngineInterceptor, while a change to intercept.EngineInterceptor can't break coil3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→2 memory uses size✕
- Connections
- 2 pairs of types, where a type in memory uses a type in size.
- The types involved
coil3.memory.MemoryCacheService→coil3.size.Scalecoil3.memory.MemoryCacheService→coil3.size.Size
- Direction
- memory uses size, so a change to size can break memory, while a change to memory can't break size.
- Position
- Below the diagonal: memory uses a module listed above it, which is the healthy direction.
12→9 memory uses util✕
- Connections
- 1 pair of types, where a type in memory uses a type in util.
- The types involved
coil3.memory.MemoryCacheService→coil3.util.Logger
- Direction
- memory uses util, so a change to util can break memory, while a change to memory can't break util.
- Position
- Below the diagonal: memory uses a module listed above it, which is the healthy direction.
12→11 memory uses intercept.EngineInterceptor✕
- Connections
- 1 pair of types, where a type in memory uses a type in intercept.EngineInterceptor.
- The types involved
coil3.memory.MemoryCacheService→coil3.intercept.EngineInterceptor.ExecuteResult
- Direction
- memory uses intercept.EngineInterceptor, so a change to intercept.EngineInterceptor can break memory, while a change to memory can't break intercept.EngineInterceptor.
- Position
- Below the diagonal: memory uses a module listed above it, which is the healthy direction.
12→15 memory uses request part of a loop✕
- Connections
- 4 pairs of types, where a type in memory uses a type in request.
- The types involved
coil3.memory.MemoryCacheService→coil3.request.ImageRequestcoil3.memory.MemoryCacheService→coil3.request.Optionscoil3.memory.MemoryCacheService→coil3.request.RequestServicecoil3.memory.MemoryCacheService→coil3.request.SuccessResult
- Direction
- memory uses request, so a change to request can break memory, while a change to memory can't break request.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→24 memory uses coil3 part of a loop✕
- Connections
- 8 pairs of types, where a type in memory uses a type in coil3.
- The types involved
coil3.memory.EmptyStrongMemoryCache→coil3.Imagecoil3.memory.EmptyWeakMemoryCache→coil3.Imagecoil3.memory.MemoryCacheService→coil3.EventListenercoil3.memory.MemoryCacheService→coil3.ImageLoadercoil3.memory.RealStrongMemoryCache→coil3.Imagecoil3.memory.RealWeakMemoryCache→coil3.Imagecoil3.memory.StrongMemoryCache→coil3.Imagecoil3.memory.WeakMemoryCache→coil3.Image
- Direction
- memory uses coil3, so a change to coil3 can break memory, while a change to memory can't break coil3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→1 RealImageLoader uses disk✕
- Connections
- 1 pair of types, where a type in RealImageLoader uses a type in disk.
- The types involved
coil3.RealImageLoader.Options→coil3.disk.DiskCache
- Direction
- RealImageLoader uses disk, so a change to disk can break RealImageLoader, while a change to RealImageLoader can't break disk.
- Position
- Below the diagonal: RealImageLoader uses a module listed above it, which is the healthy direction.
13→3 RealImageLoader uses EventListener✕
- Connections
- 1 pair of types, where a type in RealImageLoader uses a type in EventListener.
- The types involved
coil3.RealImageLoader.Options→coil3.EventListener.Factory
- Direction
- RealImageLoader uses EventListener, so a change to EventListener can break RealImageLoader, while a change to RealImageLoader can't break EventListener.
- Position
- Below the diagonal: RealImageLoader uses a module listed above it, which is the healthy direction.
13→8 RealImageLoader uses request.ImageRequest✕
- Connections
- 1 pair of types, where a type in RealImageLoader uses a type in request.ImageRequest.
- The types involved
coil3.RealImageLoader.Options→coil3.request.ImageRequest.Defaults
- Direction
- RealImageLoader uses request.ImageRequest, so a change to request.ImageRequest can break RealImageLoader, while a change to RealImageLoader can't break request.ImageRequest.
- Position
- Below the diagonal: RealImageLoader uses a module listed above it, which is the healthy direction.
13→9 RealImageLoader uses util✕
- Connections
- 1 pair of types, where a type in RealImageLoader uses a type in util.
- The types involved
coil3.RealImageLoader.Options→coil3.util.Logger
- Direction
- RealImageLoader uses util, so a change to util can break RealImageLoader, while a change to RealImageLoader can't break util.
- Position
- Below the diagonal: RealImageLoader uses a module listed above it, which is the healthy direction.
13→12 RealImageLoader uses memory✕
- Connections
- 1 pair of types, where a type in RealImageLoader uses a type in memory.
- The types involved
coil3.RealImageLoader.Options→coil3.memory.MemoryCache
- Direction
- RealImageLoader uses memory, so a change to memory can break RealImageLoader, while a change to RealImageLoader can't break memory.
- Position
- Below the diagonal: RealImageLoader uses a module listed above it, which is the healthy direction.
13→15 RealImageLoader uses request part of a loop✕
- Connections
- 6 pairs of types, where a type in RealImageLoader uses a type in request.
- The types involved
coil3.RealImageLoader.androidKt→coil3.request.Disposablecoil3.RealImageLoader.androidKt→coil3.request.ImageRequestcoil3.RealImageLoader.androidKt→coil3.request.ImageResultcoil3.RealImageLoader.nonAndroidKt→coil3.request.Disposablecoil3.RealImageLoader.nonAndroidKt→coil3.request.ImageRequestcoil3.RealImageLoader.nonAndroidKt→coil3.request.ImageResult
- Direction
- RealImageLoader uses request, so a change to request can break RealImageLoader, while a change to RealImageLoader can't break request.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→23 RealImageLoader uses ComponentRegistry part of a loop✕
- Connections
- 6 pairs of types, where a type in RealImageLoader uses a type in ComponentRegistry.
- The types involved
coil3.RealImageLoader.androidKt→coil3.ComponentRegistry.Buildercoil3.RealImageLoader.appleKt→coil3.ComponentRegistry.Buildercoil3.RealImageLoader.jvmCommonKt→coil3.ComponentRegistry.Buildercoil3.RealImageLoader.nonAndroidKt→coil3.ComponentRegistry.Buildercoil3.RealImageLoader.nonAppleKt→coil3.ComponentRegistry.Buildercoil3.RealImageLoader.nonJvmCommonKt→coil3.ComponentRegistry.Builder
- Direction
- RealImageLoader uses ComponentRegistry, so a change to ComponentRegistry can break RealImageLoader, while a change to RealImageLoader can't break ComponentRegistry.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→24 RealImageLoader uses coil3 part of a loop✕
- Connections
- 4 pairs of types, where a type in RealImageLoader uses a type in coil3.
- The types involved
coil3.RealImageLoader.Options→coil3.ComponentRegistrycoil3.RealImageLoader.Options→coil3.PlatformContextcoil3.RealImageLoader.androidKt→coil3.EventListenercoil3.RealImageLoader.nonAndroidKt→coil3.EventListener
- Direction
- RealImageLoader uses coil3, so a change to coil3 can break RealImageLoader, while a change to RealImageLoader can't break coil3.
- 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→1 ImageLoader uses disk✕
- Connections
- 1 pair of types, where a type in ImageLoader uses a type in disk.
- The types involved
coil3.ImageLoader.Builder→coil3.disk.DiskCache
- Direction
- ImageLoader uses disk, so a change to disk can break ImageLoader, while a change to ImageLoader can't break disk.
- Position
- Below the diagonal: ImageLoader uses a module listed above it, which is the healthy direction.
14→2 ImageLoader uses size✕
- Connections
- 1 pair of types, where a type in ImageLoader uses a type in size.
- The types involved
coil3.ImageLoader.Builder→coil3.size.Precision
- Direction
- ImageLoader uses size, so a change to size can break ImageLoader, while a change to ImageLoader can't break size.
- Position
- Below the diagonal: ImageLoader uses a module listed above it, which is the healthy direction.
14→3 ImageLoader uses EventListener✕
- Connections
- 1 pair of types, where a type in ImageLoader uses a type in EventListener.
- The types involved
coil3.ImageLoader.Builder→coil3.EventListener.Factory
- Direction
- ImageLoader uses EventListener, so a change to EventListener can break ImageLoader, while a change to ImageLoader can't break EventListener.
- Position
- Below the diagonal: ImageLoader uses a module listed above it, which is the healthy direction.
14→4 ImageLoader uses Extras✕
- Connections
- 1 pair of types, where a type in ImageLoader uses a type in Extras.
- The types involved
coil3.ImageLoader.Builder→coil3.Extras.Builder
- Direction
- ImageLoader uses Extras, so a change to Extras can break ImageLoader, while a change to ImageLoader can't break Extras.
- Position
- Below the diagonal: ImageLoader uses a module listed above it, which is the healthy direction.
14→8 ImageLoader uses request.ImageRequest✕
- Connections
- 1 pair of types, where a type in ImageLoader uses a type in request.ImageRequest.
- The types involved
coil3.ImageLoader.Builder→coil3.request.ImageRequest.Defaults
- Direction
- ImageLoader uses request.ImageRequest, so a change to request.ImageRequest can break ImageLoader, while a change to ImageLoader can't break request.ImageRequest.
- Position
- Below the diagonal: ImageLoader uses a module listed above it, which is the healthy direction.
14→9 ImageLoader uses util✕
- Connections
- 1 pair of types, where a type in ImageLoader uses a type in util.
- The types involved
coil3.ImageLoader.Builder→coil3.util.Logger
- Direction
- ImageLoader uses util, so a change to util can break ImageLoader, while a change to ImageLoader can't break util.
- Position
- Below the diagonal: ImageLoader uses a module listed above it, which is the healthy direction.
14→12 ImageLoader uses memory✕
- Connections
- 1 pair of types, where a type in ImageLoader uses a type in memory.
- The types involved
coil3.ImageLoader.Builder→coil3.memory.MemoryCache
- Direction
- ImageLoader uses memory, so a change to memory can break ImageLoader, while a change to ImageLoader can't break memory.
- Position
- Below the diagonal: ImageLoader uses a module listed above it, which is the healthy direction.
14→13 ImageLoader uses RealImageLoader✕
- Connections
- 1 pair of types, where a type in ImageLoader uses a type in RealImageLoader.
- The types involved
coil3.ImageLoader.Builder→coil3.RealImageLoader.Options
- Direction
- ImageLoader uses RealImageLoader, so a change to RealImageLoader can break ImageLoader, while a change to ImageLoader can't break RealImageLoader.
- Position
- Below the diagonal: ImageLoader uses a module listed above it, which is the healthy direction.
14→15 ImageLoader uses request part of a loop✕
- Connections
- 2 pairs of types, where a type in ImageLoader uses a type in request.
- The types involved
coil3.ImageLoader.Builder→coil3.request.CachePolicycoil3.ImageLoader.Builder→coil3.request.ImageRequest
- Direction
- ImageLoader uses request, so a change to request can break ImageLoader, while a change to ImageLoader can't break request.
- 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→23 ImageLoader uses ComponentRegistry part of a loop✕
- Connections
- 1 pair of types, where a type in ImageLoader uses a type in ComponentRegistry.
- The types involved
coil3.ImageLoader.Builder→coil3.ComponentRegistry.Builder
- Direction
- ImageLoader uses ComponentRegistry, so a change to ComponentRegistry can break ImageLoader, while a change to ImageLoader can't break ComponentRegistry.
- 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→24 ImageLoader uses coil3 part of a loop✕
- Connections
- 5 pairs of types, where a type in ImageLoader uses a type in coil3.
- The types involved
coil3.ImageLoader.Builder→coil3.ComponentRegistrycoil3.ImageLoader.Builder→coil3.EventListenercoil3.ImageLoader.Builder→coil3.Imagecoil3.ImageLoader.Builder→coil3.ImageLoadercoil3.ImageLoader.Builder→coil3.PlatformContext
- Direction
- ImageLoader uses coil3, so a change to coil3 can break ImageLoader, while a change to ImageLoader can't break coil3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→2 request uses size✕
- Connections
- 13 pairs of types, where a type in request uses a type in size.
- The types involved
coil3.request.AndroidRequestService→coil3.size.Precisioncoil3.request.AndroidRequestService→coil3.size.Scalecoil3.request.AndroidRequestService→coil3.size.Sizecoil3.request.AndroidRequestService→coil3.size.SizeResolvercoil3.request.ImageRequest→coil3.size.Precisioncoil3.request.ImageRequest→coil3.size.Scalecoil3.request.ImageRequest→coil3.size.SizeResolvercoil3.request.ImageRequestsKt→coil3.size.Sizecoil3.request.NonAndroidRequestService→coil3.size.Sizecoil3.request.Options→coil3.size.Precisioncoil3.request.Options→coil3.size.Scalecoil3.request.Options→coil3.size.Sizecoil3.request.RequestService→coil3.size.Size
- Direction
- request uses size, so a change to size can break request, while a change to request can't break size.
- Position
- Below the diagonal: request uses a module listed above it, which is the healthy direction.
15→4 request uses Extras✕
- Connections
- 1 pair of types, where a type in request uses a type in Extras.
- The types involved
coil3.request.ImageRequestsKt→coil3.Extras.Key
- Direction
- request uses Extras, so a change to Extras can break request, while a change to request can't break Extras.
- Position
- Below the diagonal: request uses a module listed above it, which is the healthy direction.
15→7 request uses fetch.Fetcher✕
- Connections
- 1 pair of types, where a type in request uses a type in fetch.Fetcher.
- The types involved
coil3.request.ImageRequest→coil3.fetch.Fetcher.Factory
- Direction
- request uses fetch.Fetcher, so a change to fetch.Fetcher can break request, while a change to request can't break fetch.Fetcher.
- Position
- Below the diagonal: request uses a module listed above it, which is the healthy direction.
15→8 request uses request.ImageRequest✕
- Connections
- 5 pairs of types, where a type in request uses a type in request.ImageRequest.
- The types involved
coil3.request.ImageRequest→coil3.request.ImageRequest.Buildercoil3.request.ImageRequest→coil3.request.ImageRequest.Defaultscoil3.request.ImageRequest→coil3.request.ImageRequest.Definedcoil3.request.ImageRequest→coil3.request.ImageRequest.Listenercoil3.request.ImageRequestsKt→coil3.request.ImageRequest.Builder
- Direction
- request uses request.ImageRequest, so a change to request.ImageRequest can break request, while a change to request can't break request.ImageRequest.
- Position
- Below the diagonal: request uses a module listed above it, which is the healthy direction.
15→9 request uses util✕
- Connections
- 5 pairs of types, where a type in request uses a type in util.
- The types involved
coil3.request.AndroidRequestService→coil3.util.HardwareBitmapServicecoil3.request.AndroidRequestService→coil3.util.Loggercoil3.request.AndroidRequestService→coil3.util.SystemCallbackscoil3.request.RequestServiceKt→coil3.util.Loggercoil3.request.RequestServiceKt→coil3.util.SystemCallbacks
- Direction
- request uses util, so a change to util can break request, while a change to request can't break util.
- Position
- Below the diagonal: request uses a module listed above it, which is the healthy direction.
15→10 request uses transform✕
- Connections
- 1 pair of types, where a type in request uses a type in transform.
- The types involved
coil3.request.ImageRequestsKt→coil3.transform.Transformation
- Direction
- request uses transform, so a change to transform can break request, while a change to request can't break transform.
- Position
- Below the diagonal: request uses a module listed above it, which is the healthy direction.
15→14 request uses ImageLoader✕
- Connections
- 1 pair of types, where a type in request uses a type in ImageLoader.
- The types involved
coil3.request.ImageRequestsKt→coil3.ImageLoader.Builder
- Direction
- request uses ImageLoader, so a change to ImageLoader can break request, while a change to request can't break ImageLoader.
- Position
- Below the diagonal: request uses a module listed above it, which is the healthy direction.
15→16 request uses decode part of a loop✕
- Connections
- 1 pair of types, where a type in request uses a type in decode.
- The types involved
coil3.request.SuccessResult→coil3.decode.DataSource
- Direction
- request uses decode, so a change to decode can break request, while a change to request can't break decode.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→19 request uses decode.Decoder part of a loop✕
- Connections
- 1 pair of types, where a type in request uses a type in decode.Decoder.
- The types involved
coil3.request.ImageRequest→coil3.decode.Decoder.Factory
- Direction
- request uses decode.Decoder, so a change to decode.Decoder can break request, while a change to request can't break decode.Decoder.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→24 request uses coil3 part of a loop✕
- Connections
- 13 pairs of types, where a type in request uses a type in coil3.
- The types involved
coil3.request.AndroidRequestService→coil3.Extrascoil3.request.AndroidRequestService→coil3.ImageLoadercoil3.request.ErrorResult→coil3.Imagecoil3.request.ImageRequest→coil3.Extrascoil3.request.ImageRequest→coil3.Imagecoil3.request.ImageRequest→coil3.PlatformContextcoil3.request.ImageResult→coil3.Imagecoil3.request.NonAndroidRequestService→coil3.ImageLoadercoil3.request.Options→coil3.Extrascoil3.request.Options→coil3.PlatformContextcoil3.request.RequestServiceKt→coil3.ImageLoadercoil3.request.SuccessResult→coil3.Imagecoil3.request.ViewTargetRequestDelegate→coil3.ImageLoader
- Direction
- request uses coil3, so a change to coil3 can break request, while a change to request can't break coil3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→2 decode uses size✕
- Connections
- 2 pairs of types, where a type in decode uses a type in size.
- The types involved
coil3.decode.DecodeUtils→coil3.size.Scalecoil3.decode.DecodeUtils→coil3.size.Size
- Direction
- decode uses size, so a change to size can break decode, while a change to decode can't break size.
- Position
- Below the diagonal: decode uses a module listed above it, which is the healthy direction.
16→9 decode uses util✕
- Connections
- 1 pair of types, where a type in decode uses a type in util.
- The types involved
coil3.decode.DecodeUtils→coil3.util.IntPair
- Direction
- decode uses util, so a change to util can break decode, while a change to decode can't break util.
- Position
- Below the diagonal: decode uses a module listed above it, which is the healthy direction.
16→15 decode uses request✕
- Connections
- 5 pairs of types, where a type in decode uses a type in request.
- The types involved
coil3.decode.BitmapFactoryDecoder→coil3.request.Optionscoil3.decode.SkiaImageDecoder→coil3.request.Optionscoil3.decode.SkiaImageDecoderKt→coil3.request.Optionscoil3.decode.StaticImageDecoder→coil3.request.Optionscoil3.decode.StaticImageDecoderKt→coil3.request.Options
- Direction
- decode uses request, so a change to request can break decode, while a change to decode can't break request.
- Position
- Below the diagonal: decode uses a module listed above it, which is the healthy direction.
16→24 decode uses coil3 part of a loop✕
- Connections
- 3 pairs of types, where a type in decode uses a type in coil3.
- The types involved
coil3.decode.BlackholeDecoder→coil3.Imagecoil3.decode.ContentMetadata→coil3.Uricoil3.decode.DecodeResult→coil3.Image
- Direction
- decode uses coil3, so a change to coil3 can break decode, while a change to decode can't break coil3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→2 intercept uses size✕
- Connections
- 1 pair of types, where a type in intercept uses a type in size.
- The types involved
coil3.intercept.RealInterceptorChain→coil3.size.Size
- Direction
- intercept uses size, so a change to size can break intercept, while a change to intercept can't break size.
- Position
- Below the diagonal: intercept uses a module listed above it, which is the healthy direction.
17→5 intercept uses fetch✕
- Connections
- 2 pairs of types, where a type in intercept uses a type in fetch.
- The types involved
coil3.intercept.EngineInterceptor→coil3.fetch.FetchResultcoil3.intercept.EngineInterceptor→coil3.fetch.SourceFetchResult
- Direction
- intercept uses fetch, so a change to fetch can break intercept, while a change to intercept can't break fetch.
- Position
- Below the diagonal: intercept uses a module listed above it, which is the healthy direction.
17→9 intercept uses util✕
- Connections
- 3 pairs of types, where a type in intercept uses a type in util.
- The types involved
coil3.intercept.EngineInterceptor→coil3.util.Loggercoil3.intercept.EngineInterceptor→coil3.util.SystemCallbackscoil3.intercept.EngineInterceptorKt→coil3.util.Logger
- Direction
- intercept uses util, so a change to util can break intercept, while a change to intercept can't break util.
- Position
- Below the diagonal: intercept uses a module listed above it, which is the healthy direction.
17→10 intercept uses transform✕
- Connections
- 1 pair of types, where a type in intercept uses a type in transform.
- The types involved
coil3.intercept.EngineInterceptorKt→coil3.transform.Transformation
- Direction
- intercept uses transform, so a change to transform can break intercept, while a change to intercept can't break transform.
- Position
- Below the diagonal: intercept uses a module listed above it, which is the healthy direction.
17→11 intercept uses intercept.EngineInterceptor✕
- Connections
- 2 pairs of types, where a type in intercept uses a type in intercept.EngineInterceptor.
- The types involved
coil3.intercept.EngineInterceptor→coil3.intercept.EngineInterceptor.ExecuteResultcoil3.intercept.EngineInterceptorKt→coil3.intercept.EngineInterceptor.ExecuteResult
- Direction
- intercept uses intercept.EngineInterceptor, so a change to intercept.EngineInterceptor can break intercept, while a change to intercept can't break intercept.EngineInterceptor.
- Position
- Below the diagonal: intercept uses a module listed above it, which is the healthy direction.
17→12 intercept uses memory✕
- Connections
- 1 pair of types, where a type in intercept uses a type in memory.
- The types involved
coil3.intercept.EngineInterceptor→coil3.memory.MemoryCacheService
- Direction
- intercept uses memory, so a change to memory can break intercept, while a change to intercept can't break memory.
- Position
- Below the diagonal: intercept uses a module listed above it, which is the healthy direction.
17→15 intercept uses request✕
- Connections
- 9 pairs of types, where a type in intercept uses a type in request.
- The types involved
coil3.intercept.EngineInterceptor→coil3.request.ImageRequestcoil3.intercept.EngineInterceptor→coil3.request.ImageResultcoil3.intercept.EngineInterceptor→coil3.request.Optionscoil3.intercept.EngineInterceptor→coil3.request.RequestServicecoil3.intercept.EngineInterceptorKt→coil3.request.ImageRequestcoil3.intercept.EngineInterceptorKt→coil3.request.Optionscoil3.intercept.Interceptor→coil3.request.ImageResultcoil3.intercept.RealInterceptorChain→coil3.request.ImageRequestcoil3.intercept.RealInterceptorChain→coil3.request.ImageResult
- Direction
- intercept uses request, so a change to request can break intercept, while a change to intercept can't break request.
- Position
- Below the diagonal: intercept uses a module listed above it, which is the healthy direction.
17→24 intercept uses coil3 part of a loop✕
- Connections
- 6 pairs of types, where a type in intercept uses a type in coil3.
- The types involved
coil3.intercept.EngineInterceptor→coil3.ComponentRegistrycoil3.intercept.EngineInterceptor→coil3.EventListenercoil3.intercept.EngineInterceptor→coil3.ImageLoadercoil3.intercept.EngineInterceptorKt→coil3.EventListenercoil3.intercept.EngineInterceptorKt→coil3.Imagecoil3.intercept.RealInterceptorChain→coil3.EventListener
- Direction
- intercept uses coil3, so a change to coil3 can break intercept, while a change to intercept can't break coil3.
- 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→2 transition uses size✕
- Connections
- 1 pair of types, where a type in transition uses a type in size.
- The types involved
coil3.transition.CrossfadeDrawable→coil3.size.Scale
- Direction
- transition uses size, so a change to size can break transition, while a change to transition can't break size.
- Position
- Below the diagonal: transition uses a module listed above it, which is the healthy direction.
18→15 transition uses request✕
- Connections
- 2 pairs of types, where a type in transition uses a type in request.
- The types involved
coil3.transition.CrossfadeTransition→coil3.request.ImageResultcoil3.transition.NoneTransition→coil3.request.ImageResult
- Direction
- transition uses request, so a change to request can break transition, while a change to transition can't break request.
- Position
- Below the diagonal: transition uses a module listed above it, which is the healthy direction.
19→5 decode.Decoder uses fetch✕
- Connections
- 1 pair of types, where a type in decode.Decoder uses a type in fetch.
- The types involved
coil3.decode.Decoder.Factory→coil3.fetch.SourceFetchResult
- Direction
- decode.Decoder uses fetch, so a change to fetch can break decode.Decoder, while a change to decode.Decoder can't break fetch.
- Position
- Below the diagonal: decode.Decoder uses a module listed above it, which is the healthy direction.
19→15 decode.Decoder uses request✕
- Connections
- 1 pair of types, where a type in decode.Decoder uses a type in request.
- The types involved
coil3.decode.Decoder.Factory→coil3.request.Options
- Direction
- decode.Decoder uses request, so a change to request can break decode.Decoder, while a change to decode.Decoder can't break request.
- Position
- Below the diagonal: decode.Decoder uses a module listed above it, which is the healthy direction.
19→16 decode.Decoder uses decode✕
- Connections
- 1 pair of types, where a type in decode.Decoder uses a type in decode.
- The types involved
coil3.decode.Decoder.Factory→coil3.decode.Decoder
- Direction
- decode.Decoder uses decode, so a change to decode can break decode.Decoder, while a change to decode.Decoder can't break decode.
- Position
- Below the diagonal: decode.Decoder uses a module listed above it, which is the healthy direction.
19→24 decode.Decoder uses coil3 part of a loop✕
- Connections
- 1 pair of types, where a type in decode.Decoder uses a type in coil3.
- The types involved
coil3.decode.Decoder.Factory→coil3.ImageLoader
- Direction
- decode.Decoder uses coil3, so a change to coil3 can break decode.Decoder, while a change to decode.Decoder can't break coil3.
- 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.
20→2 gif uses size✕
- Connections
- 1 pair of types, where a type in gif uses a type in size.
- The types involved
coil3.gif.MovieDrawable→coil3.size.Scale
- Direction
- gif uses size, so a change to size can break gif, while a change to gif can't break size.
- Position
- Below the diagonal: gif uses a module listed above it, which is the healthy direction.
20→4 gif uses Extras✕
- Connections
- 1 pair of types, where a type in gif uses a type in Extras.
- The types involved
coil3.gif.ImageRequestsKt→coil3.Extras.Key
- Direction
- gif uses Extras, so a change to Extras can break gif, while a change to gif can't break Extras.
- Position
- Below the diagonal: gif uses a module listed above it, which is the healthy direction.
20→8 gif uses request.ImageRequest✕
- Connections
- 1 pair of types, where a type in gif uses a type in request.ImageRequest.
- The types involved
coil3.gif.ImageRequestsKt→coil3.request.ImageRequest.Builder
- Direction
- gif uses request.ImageRequest, so a change to request.ImageRequest can break gif, while a change to gif can't break request.ImageRequest.
- Position
- Below the diagonal: gif uses a module listed above it, which is the healthy direction.
20→14 gif uses ImageLoader✕
- Connections
- 1 pair of types, where a type in gif uses a type in ImageLoader.
- The types involved
coil3.gif.ImageRequestsKt→coil3.ImageLoader.Builder
- Direction
- gif uses ImageLoader, so a change to ImageLoader can break gif, while a change to gif can't break ImageLoader.
- Position
- Below the diagonal: gif uses a module listed above it, which is the healthy direction.
20→15 gif uses request✕
- Connections
- 2 pairs of types, where a type in gif uses a type in request.
- The types involved
coil3.gif.AnimatedImageDecoder→coil3.request.Optionscoil3.gif.GifDecoder→coil3.request.Options
- Direction
- gif uses request, so a change to request can break gif, while a change to gif can't break request.
- Position
- Below the diagonal: gif uses a module listed above it, which is the healthy direction.
20→16 gif uses decode✕
- Connections
- 6 pairs of types, where a type in gif uses a type in decode.
- The types involved
coil3.gif.AnimatedImageDecoder→coil3.decode.DecodeResultcoil3.gif.AnimatedImageDecoder→coil3.decode.Decodercoil3.gif.AnimatedImageDecoder→coil3.decode.ImageSourcecoil3.gif.GifDecoder→coil3.decode.DecodeResultcoil3.gif.GifDecoder→coil3.decode.Decodercoil3.gif.GifDecoder→coil3.decode.ImageSource
- Direction
- gif uses decode, so a change to decode can break gif, while a change to gif can't break decode.
- Position
- Below the diagonal: gif uses a module listed above it, which is the healthy direction.
21→15 transition.Transition uses request✕
- Connections
- 1 pair of types, where a type in transition.Transition uses a type in request.
- The types involved
coil3.transition.Transition.Factory→coil3.request.ImageResult
- Direction
- transition.Transition uses request, so a change to request can break transition.Transition, while a change to transition.Transition can't break request.
- Position
- Below the diagonal: transition.Transition uses a module listed above it, which is the healthy direction.
21→18 transition.Transition uses transition✕
- Connections
- 2 pairs of types, where a type in transition.Transition uses a type in transition.
- The types involved
coil3.transition.Transition.Factory→coil3.transition.Transitioncoil3.transition.Transition.Factory→coil3.transition.TransitionTarget
- Direction
- transition.Transition uses transition, so a change to transition can break transition.Transition, while a change to transition.Transition can't break transition.
- Position
- Below the diagonal: transition.Transition uses a module listed above it, which is the healthy direction.
22→2 video uses size✕
- Connections
- 1 pair of types, where a type in video uses a type in size.
- The types involved
coil3.video.VideoFrameDecoder→coil3.size.Size
- Direction
- video uses size, so a change to size can break video, while a change to video can't break size.
- Position
- Below the diagonal: video uses a module listed above it, which is the healthy direction.
22→4 video uses Extras✕
- Connections
- 1 pair of types, where a type in video uses a type in Extras.
- The types involved
coil3.video.ImageRequestsKt→coil3.Extras.Key
- Direction
- video uses Extras, so a change to Extras can break video, while a change to video can't break Extras.
- Position
- Below the diagonal: video uses a module listed above it, which is the healthy direction.
22→5 video uses fetch✕
- Connections
- 2 pairs of types, where a type in video uses a type in fetch.
- The types involved
coil3.video.MediaDataSourceFetcher→coil3.fetch.FetchResultcoil3.video.MediaDataSourceFetcher→coil3.fetch.Fetcher
- Direction
- video uses fetch, so a change to fetch can break video, while a change to video can't break fetch.
- Position
- Below the diagonal: video uses a module listed above it, which is the healthy direction.
22→8 video uses request.ImageRequest✕
- Connections
- 1 pair of types, where a type in video uses a type in request.ImageRequest.
- The types involved
coil3.video.ImageRequestsKt→coil3.request.ImageRequest.Builder
- Direction
- video uses request.ImageRequest, so a change to request.ImageRequest can break video, while a change to video can't break request.ImageRequest.
- Position
- Below the diagonal: video uses a module listed above it, which is the healthy direction.
22→15 video uses request✕
- Connections
- 2 pairs of types, where a type in video uses a type in request.
- The types involved
coil3.video.MediaDataSourceFetcher→coil3.request.Optionscoil3.video.VideoFrameDecoder→coil3.request.Options
- Direction
- video uses request, so a change to request can break video, while a change to video can't break request.
- Position
- Below the diagonal: video uses a module listed above it, which is the healthy direction.
22→16 video uses decode✕
- Connections
- 2 pairs of types, where a type in video uses a type in decode.
- The types involved
coil3.video.VideoFrameDecoder→coil3.decode.Decodercoil3.video.VideoFrameDecoder→coil3.decode.ImageSource
- Direction
- video uses decode, so a change to decode can break video, while a change to video can't break decode.
- Position
- Below the diagonal: video uses a module listed above it, which is the healthy direction.
23→7 ComponentRegistry uses fetch.Fetcher✕
- Connections
- 1 pair of types, where a type in ComponentRegistry uses a type in fetch.Fetcher.
- The types involved
coil3.ComponentRegistry.Builder→coil3.fetch.Fetcher.Factory
- Direction
- ComponentRegistry uses fetch.Fetcher, so a change to fetch.Fetcher can break ComponentRegistry, while a change to ComponentRegistry can't break fetch.Fetcher.
- Position
- Below the diagonal: ComponentRegistry uses a module listed above it, which is the healthy direction.
23→17 ComponentRegistry uses intercept✕
- Connections
- 1 pair of types, where a type in ComponentRegistry uses a type in intercept.
- The types involved
coil3.ComponentRegistry.Builder→coil3.intercept.Interceptor
- Direction
- ComponentRegistry uses intercept, so a change to intercept can break ComponentRegistry, while a change to ComponentRegistry can't break intercept.
- Position
- Below the diagonal: ComponentRegistry uses a module listed above it, which is the healthy direction.
23→19 ComponentRegistry uses decode.Decoder✕
- Connections
- 1 pair of types, where a type in ComponentRegistry uses a type in decode.Decoder.
- The types involved
coil3.ComponentRegistry.Builder→coil3.decode.Decoder.Factory
- Direction
- ComponentRegistry uses decode.Decoder, so a change to decode.Decoder can break ComponentRegistry, while a change to ComponentRegistry can't break decode.Decoder.
- Position
- Below the diagonal: ComponentRegistry uses a module listed above it, which is the healthy direction.
23→24 ComponentRegistry uses coil3 part of a loop✕
- Connections
- 1 pair of types, where a type in ComponentRegistry uses a type in coil3.
- The types involved
coil3.ComponentRegistry.Builder→coil3.ComponentRegistry
- Direction
- ComponentRegistry uses coil3, so a change to coil3 can break ComponentRegistry, while a change to ComponentRegistry can't break coil3.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→1 coil3 uses disk✕
- Connections
- 2 pairs of types, where a type in coil3 uses a type in disk.
- The types involved
coil3.ImageLoader→coil3.disk.DiskCachecoil3.RealImageLoader→coil3.disk.DiskCache
- Direction
- coil3 uses disk, so a change to disk can break coil3, while a change to coil3 can't break disk.
- Position
- Below the diagonal: coil3 uses a module listed above it, which is the healthy direction.
24→2 coil3 uses size✕
- Connections
- 2 pairs of types, where a type in coil3 uses a type in size.
- The types involved
coil3.EventListener→coil3.size.Sizecoil3.EventListener→coil3.size.SizeResolver
- Direction
- coil3 uses size, so a change to size can break coil3, while a change to coil3 can't break size.
- Position
- Below the diagonal: coil3 uses a module listed above it, which is the healthy direction.
24→4 coil3 uses Extras✕
- Connections
- 5 pairs of types, where a type in coil3 uses a type in Extras.
- The types involved
coil3.Extras→coil3.Extras.Buildercoil3.Extras→coil3.Extras.Keycoil3.ExtrasKt→coil3.Extras.Keycoil3.ImageLoadersKt→coil3.Extras.Keycoil3.SingletonImageLoaderKt→coil3.Extras.Key
- Direction
- coil3 uses Extras, so a change to Extras can break coil3, while a change to coil3 can't break Extras.
- Position
- Below the diagonal: coil3 uses a module listed above it, which is the healthy direction.
24→5 coil3 uses fetch✕
- Connections
- 4 pairs of types, where a type in coil3 uses a type in fetch.
- The types involved
coil3.ComponentRegistry→coil3.fetch.Fetchercoil3.ComponentRegistry→coil3.fetch.SourceFetchResultcoil3.EventListener→coil3.fetch.FetchResultcoil3.EventListener→coil3.fetch.Fetcher
- Direction
- coil3 uses fetch, so a change to fetch can break coil3, while a change to coil3 can't break fetch.
- Position
- Below the diagonal: coil3 uses a module listed above it, which is the healthy direction.
24→7 coil3 uses fetch.Fetcher✕
- Connections
- 1 pair of types, where a type in coil3 uses a type in fetch.Fetcher.
- The types involved
coil3.ComponentRegistry→coil3.fetch.Fetcher.Factory
- Direction
- coil3 uses fetch.Fetcher, so a change to fetch.Fetcher can break coil3, while a change to coil3 can't break fetch.Fetcher.
- Position
- Below the diagonal: coil3 uses a module listed above it, which is the healthy direction.
24→8 coil3 uses request.ImageRequest✕
- Connections
- 3 pairs of types, where a type in coil3 uses a type in request.ImageRequest.
- The types involved
coil3.EventListener→coil3.request.ImageRequest.Listenercoil3.ImageLoader→coil3.request.ImageRequest.Defaultscoil3.RealImageLoader→coil3.request.ImageRequest.Defaults
- Direction
- coil3 uses request.ImageRequest, so a change to request.ImageRequest can break coil3, while a change to coil3 can't break request.ImageRequest.
- Position
- Below the diagonal: coil3 uses a module listed above it, which is the healthy direction.
24→9 coil3 uses util✕
- Connections
- 1 pair of types, where a type in coil3 uses a type in util.
- The types involved
coil3.RealImageLoaderKt→coil3.util.Logger
- Direction
- coil3 uses util, so a change to util can break coil3, while a change to coil3 can't break util.
- Position
- Below the diagonal: coil3 uses a module listed above it, which is the healthy direction.
24→12 coil3 uses memory✕
- Connections
- 2 pairs of types, where a type in coil3 uses a type in memory.
- The types involved
coil3.ImageLoader→coil3.memory.MemoryCachecoil3.RealImageLoader→coil3.memory.MemoryCache
- Direction
- coil3 uses memory, so a change to memory can break coil3, while a change to coil3 can't break memory.
- Position
- Below the diagonal: coil3 uses a module listed above it, which is the healthy direction.
24→13 coil3 uses RealImageLoader✕
- Connections
- 2 pairs of types, where a type in coil3 uses a type in RealImageLoader.
- The types involved
coil3.RealImageLoader→coil3.RealImageLoader.Optionscoil3.RealImageLoaderKt→coil3.RealImageLoader.Options
- Direction
- coil3 uses RealImageLoader, so a change to RealImageLoader can break coil3, while a change to coil3 can't break RealImageLoader.
- Position
- Below the diagonal: coil3 uses a module listed above it, which is the healthy direction.
24→14 coil3 uses ImageLoader✕
- Connections
- 3 pairs of types, where a type in coil3 uses a type in ImageLoader.
- The types involved
coil3.ImageLoader→coil3.ImageLoader.Buildercoil3.ImageLoadersKt→coil3.ImageLoader.Buildercoil3.RealImageLoader→coil3.ImageLoader.Builder
- Direction
- coil3 uses ImageLoader, so a change to ImageLoader can break coil3, while a change to coil3 can't break ImageLoader.
- Position
- Below the diagonal: coil3 uses a module listed above it, which is the healthy direction.
24→15 coil3 uses request✕
- Connections
- 16 pairs of types, where a type in coil3 uses a type in request.
- The types involved
coil3.ComponentRegistry→coil3.request.Optionscoil3.EventListener→coil3.request.ErrorResultcoil3.EventListener→coil3.request.ImageRequestcoil3.EventListener→coil3.request.Optionscoil3.EventListener→coil3.request.SuccessResultcoil3.ImageLoader→coil3.request.Disposablecoil3.ImageLoader→coil3.request.ImageRequestcoil3.ImageLoader→coil3.request.ImageResultcoil3.RealImageLoader→coil3.request.Disposablecoil3.RealImageLoader→coil3.request.ErrorResultcoil3.RealImageLoader→coil3.request.ImageRequestcoil3.RealImageLoader→coil3.request.ImageResultcoil3.RealImageLoader→coil3.request.SuccessResultcoil3.RealImageLoaderKt→coil3.request.Disposablecoil3.RealImageLoaderKt→coil3.request.ImageRequestcoil3.RealImageLoaderKt→coil3.request.ImageResult
- Direction
- coil3 uses request, so a change to request can break coil3, while a change to coil3 can't break request.
- Position
- Below the diagonal: coil3 uses a module listed above it, which is the healthy direction.
24→16 coil3 uses decode✕
- Connections
- 3 pairs of types, where a type in coil3 uses a type in decode.
- The types involved
coil3.ComponentRegistry→coil3.decode.Decodercoil3.EventListener→coil3.decode.DecodeResultcoil3.EventListener→coil3.decode.Decoder
- Direction
- coil3 uses decode, so a change to decode can break coil3, while a change to coil3 can't break decode.
- Position
- Below the diagonal: coil3 uses a module listed above it, which is the healthy direction.
24→17 coil3 uses intercept✕
- Connections
- 1 pair of types, where a type in coil3 uses a type in intercept.
- The types involved
coil3.ComponentRegistry→coil3.intercept.Interceptor
- Direction
- coil3 uses intercept, so a change to intercept can break coil3, while a change to coil3 can't break intercept.
- Position
- Below the diagonal: coil3 uses a module listed above it, which is the healthy direction.
24→18 coil3 uses transition✕
- Connections
- 1 pair of types, where a type in coil3 uses a type in transition.
- The types involved
coil3.EventListener→coil3.transition.Transition
- Direction
- coil3 uses transition, so a change to transition can break coil3, while a change to coil3 can't break transition.
- Position
- Below the diagonal: coil3 uses a module listed above it, which is the healthy direction.
24→19 coil3 uses decode.Decoder✕
- Connections
- 1 pair of types, where a type in coil3 uses a type in decode.Decoder.
- The types involved
coil3.ComponentRegistry→coil3.decode.Decoder.Factory
- Direction
- coil3 uses decode.Decoder, so a change to decode.Decoder can break coil3, while a change to coil3 can't break decode.Decoder.
- Position
- Below the diagonal: coil3 uses a module listed above it, which is the healthy direction.
24→23 coil3 uses ComponentRegistry✕
- Connections
- 2 pairs of types, where a type in coil3 uses a type in ComponentRegistry.
- The types involved
coil3.ComponentRegistry→coil3.ComponentRegistry.Buildercoil3.RealImageLoaderKt→coil3.ComponentRegistry.Builder
- Direction
- coil3 uses ComponentRegistry, so a change to ComponentRegistry can break coil3, while a change to coil3 can't break ComponentRegistry.
- Position
- Below the diagonal: coil3 uses a module listed above it, which is the healthy direction.
25→15 compose.AsyncImagePainter uses request✕
- Connections
- 1 pair of types, where a type in compose.AsyncImagePainter uses a type in request.
- The types involved
coil3.compose.AsyncImagePainter.Input→coil3.request.ImageRequest
- Direction
- compose.AsyncImagePainter uses request, so a change to request can break compose.AsyncImagePainter, while a change to compose.AsyncImagePainter can't break request.
- Position
- Below the diagonal: compose.AsyncImagePainter uses a module listed above it, which is the healthy direction.
25→24 compose.AsyncImagePainter uses coil3✕
- Connections
- 1 pair of types, where a type in compose.AsyncImagePainter uses a type in coil3.
- The types involved
coil3.compose.AsyncImagePainter.Input→coil3.ImageLoader
- Direction
- compose.AsyncImagePainter uses coil3, so a change to coil3 can break compose.AsyncImagePainter, while a change to compose.AsyncImagePainter can't break coil3.
- Position
- Below the diagonal: compose.AsyncImagePainter uses a module listed above it, which is the healthy direction.
25→40 compose.AsyncImagePainter uses compose part of a loop✕
- Connections
- 3 pairs of types, where a type in compose.AsyncImagePainter uses a type in compose.
- The types involved
coil3.compose.AsyncImagePainter.Input→coil3.compose.AsyncImageModelEqualityDelegatecoil3.compose.AsyncImagePainter.androidKt→coil3.compose.CrossfadePaintercoil3.compose.AsyncImagePainter.nonAndroidKt→coil3.compose.CrossfadePainter
- Direction
- compose.AsyncImagePainter uses compose, so a change to compose can break compose.AsyncImagePainter, while a change to compose.AsyncImagePainter can't break compose.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→5 decode.BitmapFactoryDecoder uses fetch✕
- Connections
- 1 pair of types, where a type in decode.BitmapFactoryDecoder uses a type in fetch.
- The types involved
coil3.decode.BitmapFactoryDecoder.Factory→coil3.fetch.SourceFetchResult
- Direction
- decode.BitmapFactoryDecoder uses fetch, so a change to fetch can break decode.BitmapFactoryDecoder, while a change to decode.BitmapFactoryDecoder can't break fetch.
- Position
- Below the diagonal: decode.BitmapFactoryDecoder uses a module listed above it, which is the healthy direction.
26→15 decode.BitmapFactoryDecoder uses request✕
- Connections
- 1 pair of types, where a type in decode.BitmapFactoryDecoder uses a type in request.
- The types involved
coil3.decode.BitmapFactoryDecoder.Factory→coil3.request.Options
- Direction
- decode.BitmapFactoryDecoder uses request, so a change to request can break decode.BitmapFactoryDecoder, while a change to decode.BitmapFactoryDecoder can't break request.
- Position
- Below the diagonal: decode.BitmapFactoryDecoder uses a module listed above it, which is the healthy direction.
26→16 decode.BitmapFactoryDecoder uses decode✕
- Connections
- 2 pairs of types, where a type in decode.BitmapFactoryDecoder uses a type in decode.
- The types involved
coil3.decode.BitmapFactoryDecoder.Factory→coil3.decode.Decodercoil3.decode.BitmapFactoryDecoder.Factory→coil3.decode.ExifOrientationStrategy
- Direction
- decode.BitmapFactoryDecoder uses decode, so a change to decode can break decode.BitmapFactoryDecoder, while a change to decode.BitmapFactoryDecoder can't break decode.
- Position
- Below the diagonal: decode.BitmapFactoryDecoder uses a module listed above it, which is the healthy direction.
26→19 decode.BitmapFactoryDecoder uses decode.Decoder✕
- Connections
- 1 pair of types, where a type in decode.BitmapFactoryDecoder uses a type in decode.Decoder.
- The types involved
coil3.decode.BitmapFactoryDecoder.Factory→coil3.decode.Decoder.Factory
- Direction
- decode.BitmapFactoryDecoder uses decode.Decoder, so a change to decode.Decoder can break decode.BitmapFactoryDecoder, while a change to decode.BitmapFactoryDecoder can't break decode.Decoder.
- Position
- Below the diagonal: decode.BitmapFactoryDecoder uses a module listed above it, which is the healthy direction.
26→24 decode.BitmapFactoryDecoder uses coil3✕
- Connections
- 1 pair of types, where a type in decode.BitmapFactoryDecoder uses a type in coil3.
- The types involved
coil3.decode.BitmapFactoryDecoder.Factory→coil3.ImageLoader
- Direction
- decode.BitmapFactoryDecoder uses coil3, so a change to coil3 can break decode.BitmapFactoryDecoder, while a change to decode.BitmapFactoryDecoder can't break coil3.
- Position
- Below the diagonal: decode.BitmapFactoryDecoder uses a module listed above it, which is the healthy direction.
27→5 decode.BlackholeDecoder uses fetch✕
- Connections
- 1 pair of types, where a type in decode.BlackholeDecoder uses a type in fetch.
- The types involved
coil3.decode.BlackholeDecoder.Factory→coil3.fetch.SourceFetchResult
- Direction
- decode.BlackholeDecoder uses fetch, so a change to fetch can break decode.BlackholeDecoder, while a change to decode.BlackholeDecoder can't break fetch.
- Position
- Below the diagonal: decode.BlackholeDecoder uses a module listed above it, which is the healthy direction.
27→15 decode.BlackholeDecoder uses request✕
- Connections
- 1 pair of types, where a type in decode.BlackholeDecoder uses a type in request.
- The types involved
coil3.decode.BlackholeDecoder.Factory→coil3.request.Options
- Direction
- decode.BlackholeDecoder uses request, so a change to request can break decode.BlackholeDecoder, while a change to decode.BlackholeDecoder can't break request.
- Position
- Below the diagonal: decode.BlackholeDecoder uses a module listed above it, which is the healthy direction.
27→16 decode.BlackholeDecoder uses decode✕
- Connections
- 1 pair of types, where a type in decode.BlackholeDecoder uses a type in decode.
- The types involved
coil3.decode.BlackholeDecoder.Factory→coil3.decode.BlackholeDecoder
- Direction
- decode.BlackholeDecoder uses decode, so a change to decode can break decode.BlackholeDecoder, while a change to decode.BlackholeDecoder can't break decode.
- Position
- Below the diagonal: decode.BlackholeDecoder uses a module listed above it, which is the healthy direction.
27→19 decode.BlackholeDecoder uses decode.Decoder✕
- Connections
- 1 pair of types, where a type in decode.BlackholeDecoder uses a type in decode.Decoder.
- The types involved
coil3.decode.BlackholeDecoder.Factory→coil3.decode.Decoder.Factory
- Direction
- decode.BlackholeDecoder uses decode.Decoder, so a change to decode.Decoder can break decode.BlackholeDecoder, while a change to decode.BlackholeDecoder can't break decode.Decoder.
- Position
- Below the diagonal: decode.BlackholeDecoder uses a module listed above it, which is the healthy direction.
27→24 decode.BlackholeDecoder uses coil3✕
- Connections
- 2 pairs of types, where a type in decode.BlackholeDecoder uses a type in coil3.
- The types involved
coil3.decode.BlackholeDecoder.Factory→coil3.Imagecoil3.decode.BlackholeDecoder.Factory→coil3.ImageLoader
- Direction
- decode.BlackholeDecoder uses coil3, so a change to coil3 can break decode.BlackholeDecoder, while a change to decode.BlackholeDecoder can't break coil3.
- Position
- Below the diagonal: decode.BlackholeDecoder uses a module listed above it, which is the healthy direction.
28→5 decode.SkiaImageDecoder uses fetch✕
- Connections
- 1 pair of types, where a type in decode.SkiaImageDecoder uses a type in fetch.
- The types involved
coil3.decode.SkiaImageDecoder.Factory→coil3.fetch.SourceFetchResult
- Direction
- decode.SkiaImageDecoder uses fetch, so a change to fetch can break decode.SkiaImageDecoder, while a change to decode.SkiaImageDecoder can't break fetch.
- Position
- Below the diagonal: decode.SkiaImageDecoder uses a module listed above it, which is the healthy direction.
28→9 decode.SkiaImageDecoder uses util✕
- Connections
- 1 pair of types, where a type in decode.SkiaImageDecoder uses a type in util.
- The types involved
coil3.decode.SkiaImageDecoder.jsCommonKt→coil3.util.IntPair
- Direction
- decode.SkiaImageDecoder uses util, so a change to util can break decode.SkiaImageDecoder, while a change to decode.SkiaImageDecoder can't break util.
- Position
- Below the diagonal: decode.SkiaImageDecoder uses a module listed above it, which is the healthy direction.
28→15 decode.SkiaImageDecoder uses request✕
- Connections
- 4 pairs of types, where a type in decode.SkiaImageDecoder uses a type in request.
- The types involved
coil3.decode.SkiaImageDecoder.Factory→coil3.request.Optionscoil3.decode.SkiaImageDecoder.jsCommonKt→coil3.request.Optionscoil3.decode.SkiaImageDecoder.jvmKt→coil3.request.Optionscoil3.decode.SkiaImageDecoder.nativeKt→coil3.request.Options
- Direction
- decode.SkiaImageDecoder uses request, so a change to request can break decode.SkiaImageDecoder, while a change to decode.SkiaImageDecoder can't break request.
- Position
- Below the diagonal: decode.SkiaImageDecoder uses a module listed above it, which is the healthy direction.
28→16 decode.SkiaImageDecoder uses decode✕
- Connections
- 4 pairs of types, where a type in decode.SkiaImageDecoder uses a type in decode.
- The types involved
coil3.decode.SkiaImageDecoder.Factory→coil3.decode.Decodercoil3.decode.SkiaImageDecoder.jsCommonKt→coil3.decode.DecodeResultcoil3.decode.SkiaImageDecoder.jvmKt→coil3.decode.DecodeResultcoil3.decode.SkiaImageDecoder.nativeKt→coil3.decode.DecodeResult
- Direction
- decode.SkiaImageDecoder uses decode, so a change to decode can break decode.SkiaImageDecoder, while a change to decode.SkiaImageDecoder can't break decode.
- Position
- Below the diagonal: decode.SkiaImageDecoder uses a module listed above it, which is the healthy direction.
28→19 decode.SkiaImageDecoder uses decode.Decoder✕
- Connections
- 1 pair of types, where a type in decode.SkiaImageDecoder uses a type in decode.Decoder.
- The types involved
coil3.decode.SkiaImageDecoder.Factory→coil3.decode.Decoder.Factory
- Direction
- decode.SkiaImageDecoder uses decode.Decoder, so a change to decode.Decoder can break decode.SkiaImageDecoder, while a change to decode.SkiaImageDecoder can't break decode.Decoder.
- Position
- Below the diagonal: decode.SkiaImageDecoder uses a module listed above it, which is the healthy direction.
28→24 decode.SkiaImageDecoder uses coil3✕
- Connections
- 1 pair of types, where a type in decode.SkiaImageDecoder uses a type in coil3.
- The types involved
coil3.decode.SkiaImageDecoder.Factory→coil3.ImageLoader
- Direction
- decode.SkiaImageDecoder uses coil3, so a change to coil3 can break decode.SkiaImageDecoder, while a change to decode.SkiaImageDecoder can't break coil3.
- Position
- Below the diagonal: decode.SkiaImageDecoder uses a module listed above it, which is the healthy direction.
29→5 decode.StaticImageDecoder uses fetch✕
- Connections
- 1 pair of types, where a type in decode.StaticImageDecoder uses a type in fetch.
- The types involved
coil3.decode.StaticImageDecoder.Factory→coil3.fetch.SourceFetchResult
- Direction
- decode.StaticImageDecoder uses fetch, so a change to fetch can break decode.StaticImageDecoder, while a change to decode.StaticImageDecoder can't break fetch.
- Position
- Below the diagonal: decode.StaticImageDecoder uses a module listed above it, which is the healthy direction.
29→15 decode.StaticImageDecoder uses request✕
- Connections
- 1 pair of types, where a type in decode.StaticImageDecoder uses a type in request.
- The types involved
coil3.decode.StaticImageDecoder.Factory→coil3.request.Options
- Direction
- decode.StaticImageDecoder uses request, so a change to request can break decode.StaticImageDecoder, while a change to decode.StaticImageDecoder can't break request.
- Position
- Below the diagonal: decode.StaticImageDecoder uses a module listed above it, which is the healthy direction.
29→16 decode.StaticImageDecoder uses decode✕
- Connections
- 1 pair of types, where a type in decode.StaticImageDecoder uses a type in decode.
- The types involved
coil3.decode.StaticImageDecoder.Factory→coil3.decode.Decoder
- Direction
- decode.StaticImageDecoder uses decode, so a change to decode can break decode.StaticImageDecoder, while a change to decode.StaticImageDecoder can't break decode.
- Position
- Below the diagonal: decode.StaticImageDecoder uses a module listed above it, which is the healthy direction.
29→19 decode.StaticImageDecoder uses decode.Decoder✕
- Connections
- 1 pair of types, where a type in decode.StaticImageDecoder uses a type in decode.Decoder.
- The types involved
coil3.decode.StaticImageDecoder.Factory→coil3.decode.Decoder.Factory
- Direction
- decode.StaticImageDecoder uses decode.Decoder, so a change to decode.Decoder can break decode.StaticImageDecoder, while a change to decode.StaticImageDecoder can't break decode.Decoder.
- Position
- Below the diagonal: decode.StaticImageDecoder uses a module listed above it, which is the healthy direction.
29→24 decode.StaticImageDecoder uses coil3✕
- Connections
- 1 pair of types, where a type in decode.StaticImageDecoder uses a type in coil3.
- The types involved
coil3.decode.StaticImageDecoder.Factory→coil3.ImageLoader
- Direction
- decode.StaticImageDecoder uses coil3, so a change to coil3 can break decode.StaticImageDecoder, while a change to decode.StaticImageDecoder can't break coil3.
- Position
- Below the diagonal: decode.StaticImageDecoder uses a module listed above it, which is the healthy direction.
30→5 fetch.BlobUriFetcher uses fetch✕
- Connections
- 1 pair of types, where a type in fetch.BlobUriFetcher uses a type in fetch.
- The types involved
coil3.fetch.BlobUriFetcher.Factory→coil3.fetch.Fetcher
- Direction
- fetch.BlobUriFetcher uses fetch, so a change to fetch can break fetch.BlobUriFetcher, while a change to fetch.BlobUriFetcher can't break fetch.
- Position
- Below the diagonal: fetch.BlobUriFetcher uses a module listed above it, which is the healthy direction.
30→7 fetch.BlobUriFetcher uses fetch.Fetcher✕
- Connections
- 1 pair of types, where a type in fetch.BlobUriFetcher uses a type in fetch.Fetcher.
- The types involved
coil3.fetch.BlobUriFetcher.Factory→coil3.fetch.Fetcher.Factory
- Direction
- fetch.BlobUriFetcher uses fetch.Fetcher, so a change to fetch.Fetcher can break fetch.BlobUriFetcher, while a change to fetch.BlobUriFetcher can't break fetch.Fetcher.
- Position
- Below the diagonal: fetch.BlobUriFetcher uses a module listed above it, which is the healthy direction.
30→15 fetch.BlobUriFetcher uses request✕
- Connections
- 1 pair of types, where a type in fetch.BlobUriFetcher uses a type in request.
- The types involved
coil3.fetch.BlobUriFetcher.Factory→coil3.request.Options
- Direction
- fetch.BlobUriFetcher uses request, so a change to request can break fetch.BlobUriFetcher, while a change to fetch.BlobUriFetcher can't break request.
- Position
- Below the diagonal: fetch.BlobUriFetcher uses a module listed above it, which is the healthy direction.
30→24 fetch.BlobUriFetcher uses coil3✕
- Connections
- 2 pairs of types, where a type in fetch.BlobUriFetcher uses a type in coil3.
- The types involved
coil3.fetch.BlobUriFetcher.Factory→coil3.ImageLoadercoil3.fetch.BlobUriFetcher.Factory→coil3.Uri
- Direction
- fetch.BlobUriFetcher uses coil3, so a change to coil3 can break fetch.BlobUriFetcher, while a change to fetch.BlobUriFetcher can't break coil3.
- Position
- Below the diagonal: fetch.BlobUriFetcher uses a module listed above it, which is the healthy direction.
31→1 network uses disk✕
- Connections
- 1 pair of types, where a type in network uses a type in disk.
- The types involved
coil3.network.NetworkFetcher→coil3.disk.DiskCache
- Direction
- network uses disk, so a change to disk can break network, while a change to network can't break disk.
- Position
- Below the diagonal: network uses a module listed above it, which is the healthy direction.
31→4 network uses Extras✕
- Connections
- 1 pair of types, where a type in network uses a type in Extras.
- The types involved
coil3.network.ImageRequestsKt→coil3.Extras.Key
- Direction
- network uses Extras, so a change to Extras can break network, while a change to network can't break Extras.
- Position
- Below the diagonal: network uses a module listed above it, which is the healthy direction.
31→5 network uses fetch✕
- Connections
- 5 pairs of types, where a type in network uses a type in fetch.
- The types involved
coil3.network.ConcurrentRequestStrategy→coil3.fetch.FetchResultcoil3.network.DeDupeConcurrentRequestStrategy→coil3.fetch.FetchResultcoil3.network.NetworkFetcher→coil3.fetch.FetchResultcoil3.network.NetworkFetcher→coil3.fetch.Fetchercoil3.network.UncoordinatedConcurrentRequestStrategy→coil3.fetch.FetchResult
- Direction
- network uses fetch, so a change to fetch can break network, while a change to network can't break fetch.
- Position
- Below the diagonal: network uses a module listed above it, which is the healthy direction.
31→6 network uses network.CacheStrategy✕
- Connections
- 2 pairs of types, where a type in network uses a type in network.CacheStrategy.
- The types involved
coil3.network.CacheStrategy→coil3.network.CacheStrategy.ReadResultcoil3.network.CacheStrategy→coil3.network.CacheStrategy.WriteResult
- Direction
- network uses network.CacheStrategy, so a change to network.CacheStrategy can break network, while a change to network can't break network.CacheStrategy.
- Position
- Below the diagonal: network uses a module listed above it, which is the healthy direction.
31→8 network uses request.ImageRequest✕
- Connections
- 1 pair of types, where a type in network uses a type in request.ImageRequest.
- The types involved
coil3.network.ImageRequestsKt→coil3.request.ImageRequest.Builder
- Direction
- network uses request.ImageRequest, so a change to request.ImageRequest can break network, while a change to network can't break request.ImageRequest.
- Position
- Below the diagonal: network uses a module listed above it, which is the healthy direction.
31→15 network uses request✕
- Connections
- 2 pairs of types, where a type in network uses a type in request.
- The types involved
coil3.network.CacheStrategy→coil3.request.Optionscoil3.network.NetworkFetcher→coil3.request.Options
- Direction
- network uses request, so a change to request can break network, while a change to network can't break request.
- Position
- Below the diagonal: network uses a module listed above it, which is the healthy direction.
31→16 network uses decode✕
- Connections
- 1 pair of types, where a type in network uses a type in decode.
- The types involved
coil3.network.NetworkFetcher→coil3.decode.ImageSource
- Direction
- network uses decode, so a change to decode can break network, while a change to network can't break decode.
- Position
- Below the diagonal: network uses a module listed above it, which is the healthy direction.
31→24 network uses coil3✕
- Connections
- 2 pairs of types, where a type in network uses a type in coil3.
- The types involved
coil3.network.ConnectivityCheckerKt→coil3.PlatformContextcoil3.network.NetworkRequest→coil3.Extras
- Direction
- network uses coil3, so a change to coil3 can break network, while a change to network can't break coil3.
- Position
- Below the diagonal: network uses a module listed above it, which is the healthy direction.
32→15 svg uses request✕
- Connections
- 2 pairs of types, where a type in svg uses a type in request.
- The types involved
coil3.svg.Svg→coil3.request.Optionscoil3.svg.SvgDecoder→coil3.request.Options
- Direction
- svg uses request, so a change to request can break svg, while a change to svg can't break request.
- Position
- Below the diagonal: svg uses a module listed above it, which is the healthy direction.
32→16 svg uses decode✕
- Connections
- 2 pairs of types, where a type in svg uses a type in decode.
- The types involved
coil3.svg.SvgDecoder→coil3.decode.Decodercoil3.svg.SvgDecoder→coil3.decode.ImageSource
- Direction
- svg uses decode, so a change to decode can break svg, while a change to svg can't break decode.
- Position
- Below the diagonal: svg uses a module listed above it, which is the healthy direction.
32→24 svg uses coil3✕
- Connections
- 3 pairs of types, where a type in svg uses a type in coil3.
- The types involved
coil3.svg.Svg→coil3.Imagecoil3.svg.SvgDecoder→coil3.PlatformContextcoil3.svg.SvgImage→coil3.Image
- Direction
- svg uses coil3, so a change to coil3 can break svg, while a change to svg can't break coil3.
- Position
- Below the diagonal: svg uses a module listed above it, which is the healthy direction.
33→5 svg.SvgDecoder uses fetch✕
- Connections
- 1 pair of types, where a type in svg.SvgDecoder uses a type in fetch.
- The types involved
coil3.svg.SvgDecoder.Factory→coil3.fetch.SourceFetchResult
- Direction
- svg.SvgDecoder uses fetch, so a change to fetch can break svg.SvgDecoder, while a change to svg.SvgDecoder can't break fetch.
- Position
- Below the diagonal: svg.SvgDecoder uses a module listed above it, which is the healthy direction.
33→15 svg.SvgDecoder uses request✕
- Connections
- 1 pair of types, where a type in svg.SvgDecoder uses a type in request.
- The types involved
coil3.svg.SvgDecoder.Factory→coil3.request.Options
- Direction
- svg.SvgDecoder uses request, so a change to request can break svg.SvgDecoder, while a change to svg.SvgDecoder can't break request.
- Position
- Below the diagonal: svg.SvgDecoder uses a module listed above it, which is the healthy direction.
33→16 svg.SvgDecoder uses decode✕
- Connections
- 1 pair of types, where a type in svg.SvgDecoder uses a type in decode.
- The types involved
coil3.svg.SvgDecoder.Factory→coil3.decode.Decoder
- Direction
- svg.SvgDecoder uses decode, so a change to decode can break svg.SvgDecoder, while a change to svg.SvgDecoder can't break decode.
- Position
- Below the diagonal: svg.SvgDecoder uses a module listed above it, which is the healthy direction.
33→19 svg.SvgDecoder uses decode.Decoder✕
- Connections
- 1 pair of types, where a type in svg.SvgDecoder uses a type in decode.Decoder.
- The types involved
coil3.svg.SvgDecoder.Factory→coil3.decode.Decoder.Factory
- Direction
- svg.SvgDecoder uses decode.Decoder, so a change to decode.Decoder can break svg.SvgDecoder, while a change to svg.SvgDecoder can't break decode.Decoder.
- Position
- Below the diagonal: svg.SvgDecoder uses a module listed above it, which is the healthy direction.
33→24 svg.SvgDecoder uses coil3✕
- Connections
- 3 pairs of types, where a type in svg.SvgDecoder uses a type in coil3.
- The types involved
coil3.svg.SvgDecoder.Companion→coil3.PlatformContextcoil3.svg.SvgDecoder.Factory→coil3.ImageLoadercoil3.svg.SvgDecoder.Factory→coil3.PlatformContext
- Direction
- svg.SvgDecoder uses coil3, so a change to coil3 can break svg.SvgDecoder, while a change to svg.SvgDecoder can't break coil3.
- Position
- Below the diagonal: svg.SvgDecoder uses a module listed above it, which is the healthy direction.
34→5 video.MediaDataSourceFetcher uses fetch✕
- Connections
- 1 pair of types, where a type in video.MediaDataSourceFetcher uses a type in fetch.
- The types involved
coil3.video.MediaDataSourceFetcher.Factory→coil3.fetch.Fetcher
- Direction
- video.MediaDataSourceFetcher uses fetch, so a change to fetch can break video.MediaDataSourceFetcher, while a change to video.MediaDataSourceFetcher can't break fetch.
- Position
- Below the diagonal: video.MediaDataSourceFetcher uses a module listed above it, which is the healthy direction.
34→7 video.MediaDataSourceFetcher uses fetch.Fetcher✕
- Connections
- 1 pair of types, where a type in video.MediaDataSourceFetcher uses a type in fetch.Fetcher.
- The types involved
coil3.video.MediaDataSourceFetcher.Factory→coil3.fetch.Fetcher.Factory
- Direction
- video.MediaDataSourceFetcher uses fetch.Fetcher, so a change to fetch.Fetcher can break video.MediaDataSourceFetcher, while a change to video.MediaDataSourceFetcher can't break fetch.Fetcher.
- Position
- Below the diagonal: video.MediaDataSourceFetcher uses a module listed above it, which is the healthy direction.
34→15 video.MediaDataSourceFetcher uses request✕
- Connections
- 1 pair of types, where a type in video.MediaDataSourceFetcher uses a type in request.
- The types involved
coil3.video.MediaDataSourceFetcher.Factory→coil3.request.Options
- Direction
- video.MediaDataSourceFetcher uses request, so a change to request can break video.MediaDataSourceFetcher, while a change to video.MediaDataSourceFetcher can't break request.
- Position
- Below the diagonal: video.MediaDataSourceFetcher uses a module listed above it, which is the healthy direction.
34→24 video.MediaDataSourceFetcher uses coil3✕
- Connections
- 1 pair of types, where a type in video.MediaDataSourceFetcher uses a type in coil3.
- The types involved
coil3.video.MediaDataSourceFetcher.Factory→coil3.ImageLoader
- Direction
- video.MediaDataSourceFetcher uses coil3, so a change to coil3 can break video.MediaDataSourceFetcher, while a change to video.MediaDataSourceFetcher can't break coil3.
- Position
- Below the diagonal: video.MediaDataSourceFetcher uses a module listed above it, which is the healthy direction.
35→5 video.VideoFrameDecoder uses fetch✕
- Connections
- 1 pair of types, where a type in video.VideoFrameDecoder uses a type in fetch.
- The types involved
coil3.video.VideoFrameDecoder.Factory→coil3.fetch.SourceFetchResult
- Direction
- video.VideoFrameDecoder uses fetch, so a change to fetch can break video.VideoFrameDecoder, while a change to video.VideoFrameDecoder can't break fetch.
- Position
- Below the diagonal: video.VideoFrameDecoder uses a module listed above it, which is the healthy direction.
35→15 video.VideoFrameDecoder uses request✕
- Connections
- 1 pair of types, where a type in video.VideoFrameDecoder uses a type in request.
- The types involved
coil3.video.VideoFrameDecoder.Factory→coil3.request.Options
- Direction
- video.VideoFrameDecoder uses request, so a change to request can break video.VideoFrameDecoder, while a change to video.VideoFrameDecoder can't break request.
- Position
- Below the diagonal: video.VideoFrameDecoder uses a module listed above it, which is the healthy direction.
35→16 video.VideoFrameDecoder uses decode✕
- Connections
- 1 pair of types, where a type in video.VideoFrameDecoder uses a type in decode.
- The types involved
coil3.video.VideoFrameDecoder.Factory→coil3.decode.Decoder
- Direction
- video.VideoFrameDecoder uses decode, so a change to decode can break video.VideoFrameDecoder, while a change to video.VideoFrameDecoder can't break decode.
- Position
- Below the diagonal: video.VideoFrameDecoder uses a module listed above it, which is the healthy direction.
35→19 video.VideoFrameDecoder uses decode.Decoder✕
- Connections
- 1 pair of types, where a type in video.VideoFrameDecoder uses a type in decode.Decoder.
- The types involved
coil3.video.VideoFrameDecoder.Factory→coil3.decode.Decoder.Factory
- Direction
- video.VideoFrameDecoder uses decode.Decoder, so a change to decode.Decoder can break video.VideoFrameDecoder, while a change to video.VideoFrameDecoder can't break decode.Decoder.
- Position
- Below the diagonal: video.VideoFrameDecoder uses a module listed above it, which is the healthy direction.
35→24 video.VideoFrameDecoder uses coil3✕
- Connections
- 1 pair of types, where a type in video.VideoFrameDecoder uses a type in coil3.
- The types involved
coil3.video.VideoFrameDecoder.Factory→coil3.ImageLoader
- Direction
- video.VideoFrameDecoder uses coil3, so a change to coil3 can break video.VideoFrameDecoder, while a change to video.VideoFrameDecoder can't break coil3.
- Position
- Below the diagonal: video.VideoFrameDecoder uses a module listed above it, which is the healthy direction.
36→2 compose.internal uses size✕
- Connections
- 3 pairs of types, where a type in compose.internal uses a type in size.
- The types involved
coil3.compose.internal.UtilsKt→coil3.size.Dimensioncoil3.compose.internal.UtilsKt→coil3.size.Sizecoil3.compose.internal.UtilsKt→coil3.size.SizeResolver
- Direction
- compose.internal uses size, so a change to size can break compose.internal, while a change to compose.internal can't break size.
- Position
- Below the diagonal: compose.internal uses a module listed above it, which is the healthy direction.
36→15 compose.internal uses request✕
- Connections
- 2 pairs of types, where a type in compose.internal uses a type in request.
- The types involved
coil3.compose.internal.ContentPainterElement→coil3.request.ImageRequestcoil3.compose.internal.UtilsKt→coil3.request.ImageRequest
- Direction
- compose.internal uses request, so a change to request can break compose.internal, while a change to compose.internal can't break request.
- Position
- Below the diagonal: compose.internal uses a module listed above it, which is the healthy direction.
36→24 compose.internal uses coil3✕
- Connections
- 3 pairs of types, where a type in compose.internal uses a type in coil3.
- The types involved
coil3.compose.internal.AsyncImageState→coil3.ImageLoadercoil3.compose.internal.ContentPainterElement→coil3.ImageLoadercoil3.compose.internal.UtilsKt→coil3.ImageLoader
- Direction
- compose.internal uses coil3, so a change to coil3 can break compose.internal, while a change to compose.internal can't break coil3.
- Position
- Below the diagonal: compose.internal uses a module listed above it, which is the healthy direction.
36→25 compose.internal uses compose.AsyncImagePainter✕
- Connections
- 2 pairs of types, where a type in compose.internal uses a type in compose.AsyncImagePainter.
- The types involved
coil3.compose.internal.ContentPainterElement→coil3.compose.AsyncImagePainter.Statecoil3.compose.internal.UtilsKt→coil3.compose.AsyncImagePainter.State
- Direction
- compose.internal uses compose.AsyncImagePainter, so a change to compose.AsyncImagePainter can break compose.internal, while a change to compose.internal can't break compose.AsyncImagePainter.
- Position
- Below the diagonal: compose.internal uses a module listed above it, which is the healthy direction.
36→40 compose.internal uses compose part of a loop✕
- Connections
- 7 pairs of types, where a type in compose.internal uses a type in compose.
- The types involved
coil3.compose.internal.AbstractContentPainterNode→coil3.compose.ConstraintsSizeResolvercoil3.compose.internal.AsyncImageState→coil3.compose.AsyncImageModelEqualityDelegatecoil3.compose.internal.ContentPainterElement→coil3.compose.AsyncImageModelEqualityDelegatecoil3.compose.internal.ContentPainterElement→coil3.compose.AsyncImagePreviewHandlercoil3.compose.internal.ContentPainterNode→coil3.compose.AsyncImagePaintercoil3.compose.internal.ContentPainterNode→coil3.compose.ConstraintsSizeResolvercoil3.compose.internal.UtilsKt→coil3.compose.AsyncImagePreviewHandler
- Direction
- compose.internal uses compose, so a change to compose can break compose.internal, while a change to compose.internal can't break compose.
- 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.
37→5 network.NetworkFetcher uses fetch✕
- Connections
- 1 pair of types, where a type in network.NetworkFetcher uses a type in fetch.
- The types involved
coil3.network.NetworkFetcher.Factory→coil3.fetch.Fetcher
- Direction
- network.NetworkFetcher uses fetch, so a change to fetch can break network.NetworkFetcher, while a change to network.NetworkFetcher can't break fetch.
- Position
- Below the diagonal: network.NetworkFetcher uses a module listed above it, which is the healthy direction.
37→7 network.NetworkFetcher uses fetch.Fetcher✕
- Connections
- 1 pair of types, where a type in network.NetworkFetcher uses a type in fetch.Fetcher.
- The types involved
coil3.network.NetworkFetcher.Factory→coil3.fetch.Fetcher.Factory
- Direction
- network.NetworkFetcher uses fetch.Fetcher, so a change to fetch.Fetcher can break network.NetworkFetcher, while a change to network.NetworkFetcher can't break fetch.Fetcher.
- Position
- Below the diagonal: network.NetworkFetcher uses a module listed above it, which is the healthy direction.
37→15 network.NetworkFetcher uses request✕
- Connections
- 1 pair of types, where a type in network.NetworkFetcher uses a type in request.
- The types involved
coil3.network.NetworkFetcher.Factory→coil3.request.Options
- Direction
- network.NetworkFetcher uses request, so a change to request can break network.NetworkFetcher, while a change to network.NetworkFetcher can't break request.
- Position
- Below the diagonal: network.NetworkFetcher uses a module listed above it, which is the healthy direction.
37→24 network.NetworkFetcher uses coil3✕
- Connections
- 3 pairs of types, where a type in network.NetworkFetcher uses a type in coil3.
- The types involved
coil3.network.NetworkFetcher.Factory→coil3.ImageLoadercoil3.network.NetworkFetcher.Factory→coil3.PlatformContextcoil3.network.NetworkFetcher.Factory→coil3.Uri
- Direction
- network.NetworkFetcher uses coil3, so a change to coil3 can break network.NetworkFetcher, while a change to network.NetworkFetcher can't break coil3.
- Position
- Below the diagonal: network.NetworkFetcher uses a module listed above it, which is the healthy direction.
37→31 network.NetworkFetcher uses network✕
- Connections
- 4 pairs of types, where a type in network.NetworkFetcher uses a type in network.
- The types involved
coil3.network.NetworkFetcher.Factory→coil3.network.CacheStrategycoil3.network.NetworkFetcher.Factory→coil3.network.ConcurrentRequestStrategycoil3.network.NetworkFetcher.Factory→coil3.network.ConnectivityCheckercoil3.network.NetworkFetcher.Factory→coil3.network.NetworkClient
- Direction
- network.NetworkFetcher uses network, so a change to network can break network.NetworkFetcher, while a change to network.NetworkFetcher can't break network.
- Position
- Below the diagonal: network.NetworkFetcher uses a module listed above it, which is the healthy direction.
38→5 network.httpengine uses fetch✕
- Connections
- 1 pair of types, where a type in network.httpengine uses a type in fetch.
- The types involved
coil3.network.httpengine.HttpEngineFetcherFactory→coil3.fetch.Fetcher
- Direction
- network.httpengine uses fetch, so a change to fetch can break network.httpengine, while a change to network.httpengine can't break fetch.
- Position
- Below the diagonal: network.httpengine uses a module listed above it, which is the healthy direction.
38→7 network.httpengine uses fetch.Fetcher✕
- Connections
- 2 pairs of types, where a type in network.httpengine uses a type in fetch.Fetcher.
- The types involved
coil3.network.httpengine.HttpEngineFetcherFactory→coil3.fetch.Fetcher.Factorycoil3.network.httpengine.HttpEngineNetworkFetcherKt→coil3.fetch.Fetcher.Factory
- Direction
- network.httpengine uses fetch.Fetcher, so a change to fetch.Fetcher can break network.httpengine, while a change to network.httpengine can't break fetch.Fetcher.
- Position
- Below the diagonal: network.httpengine uses a module listed above it, which is the healthy direction.
38→15 network.httpengine uses request✕
- Connections
- 1 pair of types, where a type in network.httpengine uses a type in request.
- The types involved
coil3.network.httpengine.HttpEngineFetcherFactory→coil3.request.Options
- Direction
- network.httpengine uses request, so a change to request can break network.httpengine, while a change to network.httpengine can't break request.
- Position
- Below the diagonal: network.httpengine uses a module listed above it, which is the healthy direction.
38→24 network.httpengine uses coil3✕
- Connections
- 5 pairs of types, where a type in network.httpengine uses a type in coil3.
- The types involved
coil3.network.httpengine.HttpEngineFetcherFactory→coil3.ImageLoadercoil3.network.httpengine.HttpEngineFetcherFactory→coil3.PlatformContextcoil3.network.httpengine.HttpEngineFetcherFactory→coil3.Uricoil3.network.httpengine.HttpEngineNetworkFetcherKt→coil3.PlatformContextcoil3.network.httpengine.HttpEngineNetworkFetcherKt→coil3.Uri
- Direction
- network.httpengine uses coil3, so a change to coil3 can break network.httpengine, while a change to network.httpengine can't break coil3.
- Position
- Below the diagonal: network.httpengine uses a module listed above it, which is the healthy direction.
38→31 network.httpengine uses network✕
- Connections
- 9 pairs of types, where a type in network.httpengine uses a type in network.
- The types involved
coil3.network.httpengine.CrossOriginHttpEngineRedirectPolicy→coil3.network.NetworkRequestcoil3.network.httpengine.HttpEngineFetcherFactory→coil3.network.CacheStrategycoil3.network.httpengine.HttpEngineFetcherFactory→coil3.network.ConcurrentRequestStrategycoil3.network.httpengine.HttpEngineFetcherFactory→coil3.network.ConnectivityCheckercoil3.network.httpengine.HttpEngineNetworkFetcherKt→coil3.network.CacheStrategycoil3.network.httpengine.HttpEngineNetworkFetcherKt→coil3.network.ConcurrentRequestStrategycoil3.network.httpengine.HttpEngineNetworkFetcherKt→coil3.network.ConnectivityCheckercoil3.network.httpengine.HttpEngineNetworkFetcherKt→coil3.network.NetworkClientcoil3.network.httpengine.HttpEngineRedirectPolicy→coil3.network.NetworkRequest
- Direction
- network.httpengine uses network, so a change to network can break network.httpengine, while a change to network.httpengine can't break network.
- Position
- Below the diagonal: network.httpengine uses a module listed above it, which is the healthy direction.
39→9 svg.internal uses util✕
- Connections
- 1 pair of types, where a type in svg.internal uses a type in util.
- The types involved
coil3.svg.internal.SvgDecoderServiceLoaderTarget→coil3.util.DecoderServiceLoaderTarget
- Direction
- svg.internal uses util, so a change to util can break svg.internal, while a change to svg.internal can't break util.
- Position
- Below the diagonal: svg.internal uses a module listed above it, which is the healthy direction.
39→15 svg.internal uses request✕
- Connections
- 2 pairs of types, where a type in svg.internal uses a type in request.
- The types involved
coil3.svg.internal.AndroidSvg→coil3.request.Optionscoil3.svg.internal.SkiaSvg→coil3.request.Options
- Direction
- svg.internal uses request, so a change to request can break svg.internal, while a change to svg.internal can't break request.
- Position
- Below the diagonal: svg.internal uses a module listed above it, which is the healthy direction.
39→24 svg.internal uses coil3✕
- Connections
- 2 pairs of types, where a type in svg.internal uses a type in coil3.
- The types involved
coil3.svg.internal.AndroidSvg→coil3.Imagecoil3.svg.internal.SkiaSvg→coil3.Image
- Direction
- svg.internal uses coil3, so a change to coil3 can break svg.internal, while a change to svg.internal can't break coil3.
- Position
- Below the diagonal: svg.internal uses a module listed above it, which is the healthy direction.
39→32 svg.internal uses svg✕
- Connections
- 3 pairs of types, where a type in svg.internal uses a type in svg.
- The types involved
coil3.svg.internal.AndroidSvg→coil3.svg.Svgcoil3.svg.internal.ParseSvgKt→coil3.svg.Svgcoil3.svg.internal.SkiaSvg→coil3.svg.Svg
- Direction
- svg.internal uses svg, so a change to svg can break svg.internal, while a change to svg.internal can't break svg.
- Position
- Below the diagonal: svg.internal uses a module listed above it, which is the healthy direction.
39→33 svg.internal uses svg.SvgDecoder✕
- Connections
- 1 pair of types, where a type in svg.internal uses a type in svg.SvgDecoder.
- The types involved
coil3.svg.internal.SvgDecoderServiceLoaderTarget→coil3.svg.SvgDecoder.Factory
- Direction
- svg.internal uses svg.SvgDecoder, so a change to svg.SvgDecoder can break svg.internal, while a change to svg.internal can't break svg.SvgDecoder.
- Position
- Below the diagonal: svg.internal uses a module listed above it, which is the healthy direction.
40→2 compose uses size✕
- Connections
- 4 pairs of types, where a type in compose uses a type in size.
- The types involved
coil3.compose.ConstraintsSizeResolver→coil3.size.Sizecoil3.compose.ConstraintsSizeResolver→coil3.size.SizeResolvercoil3.compose.DrawScopeSizeResolver→coil3.size.SizeResolvercoil3.compose.RealDrawScopeSizeResolver→coil3.size.Size
- Direction
- compose uses size, so a change to size can break compose, while a change to compose can't break size.
- Position
- Below the diagonal: compose uses a module listed above it, which is the healthy direction.
40→4 compose uses Extras✕
- Connections
- 1 pair of types, where a type in compose uses a type in Extras.
- The types involved
coil3.compose.ImageRequestsKt→coil3.Extras.Key
- Direction
- compose uses Extras, so a change to Extras can break compose, while a change to compose can't break Extras.
- Position
- Below the diagonal: compose uses a module listed above it, which is the healthy direction.
40→8 compose uses request.ImageRequest✕
- Connections
- 1 pair of types, where a type in compose uses a type in request.ImageRequest.
- The types involved
coil3.compose.ImageRequestsKt→coil3.request.ImageRequest.Builder
- Direction
- compose uses request.ImageRequest, so a change to request.ImageRequest can break compose, while a change to compose can't break request.ImageRequest.
- Position
- Below the diagonal: compose uses a module listed above it, which is the healthy direction.
40→14 compose uses ImageLoader✕
- Connections
- 1 pair of types, where a type in compose uses a type in ImageLoader.
- The types involved
coil3.compose.ImageRequestsKt→coil3.ImageLoader.Builder
- Direction
- compose uses ImageLoader, so a change to ImageLoader can break compose, while a change to compose can't break ImageLoader.
- Position
- Below the diagonal: compose uses a module listed above it, which is the healthy direction.
40→15 compose uses request✕
- Connections
- 3 pairs of types, where a type in compose uses a type in request.
- The types involved
coil3.compose.AsyncImagePainter→coil3.request.ImageRequestcoil3.compose.AsyncImagePreviewHandler→coil3.request.ImageRequestcoil3.compose.LocalAsyncImagePreviewHandlerKt→coil3.request.ImageRequest
- Direction
- compose uses request, so a change to request can break compose, while a change to compose can't break request.
- Position
- Below the diagonal: compose uses a module listed above it, which is the healthy direction.
40→24 compose uses coil3✕
- Connections
- 10 pairs of types, where a type in compose uses a type in coil3.
- The types involved
coil3.compose.AsyncImageKt→coil3.ImageLoadercoil3.compose.AsyncImagePainterKt→coil3.ImageLoadercoil3.compose.AsyncImagePreviewHandler→coil3.ImageLoadercoil3.compose.ImagePainter→coil3.Imagecoil3.compose.ImagePainterKt→coil3.PlatformContextcoil3.compose.LocalAsyncImagePreviewHandlerKt→coil3.Imagecoil3.compose.LocalPlatformContextKt→coil3.PlatformContextcoil3.compose.SingletonImageLoadersKt→coil3.ImageLoadercoil3.compose.SingletonImageLoadersKt→coil3.PlatformContextcoil3.compose.SubcomposeAsyncImageKt→coil3.ImageLoader
- Direction
- compose uses coil3, so a change to coil3 can break compose, while a change to compose can't break coil3.
- Position
- Below the diagonal: compose uses a module listed above it, which is the healthy direction.
40→25 compose uses compose.AsyncImagePainter✕
- Connections
- 9 pairs of types, where a type in compose uses a type in compose.AsyncImagePainter.
- The types involved
coil3.compose.AsyncImageKt→coil3.compose.AsyncImagePainter.Statecoil3.compose.AsyncImagePainter→coil3.compose.AsyncImagePainter.Inputcoil3.compose.AsyncImagePainter→coil3.compose.AsyncImagePainter.Statecoil3.compose.AsyncImagePainterKt→coil3.compose.AsyncImagePainter.Statecoil3.compose.AsyncImagePreviewHandler→coil3.compose.AsyncImagePainter.Statecoil3.compose.SingletonAsyncImageKt→coil3.compose.AsyncImagePainter.Statecoil3.compose.SingletonAsyncImagePainterKt→coil3.compose.AsyncImagePainter.Statecoil3.compose.SingletonSubcomposeAsyncImageKt→coil3.compose.AsyncImagePainter.Statecoil3.compose.SubcomposeAsyncImageKt→coil3.compose.AsyncImagePainter.State
- Direction
- compose uses compose.AsyncImagePainter, so a change to compose.AsyncImagePainter can break compose, while a change to compose can't break compose.AsyncImagePainter.
- Position
- Below the diagonal: compose uses a module listed above it, which is the healthy direction.
40→36 compose uses compose.internal✕
- Connections
- 3 pairs of types, where a type in compose uses a type in compose.internal.
- The types involved
coil3.compose.AsyncImageKt→coil3.compose.internal.AsyncImageStatecoil3.compose.AsyncImagePainterKt→coil3.compose.internal.AsyncImageStatecoil3.compose.SubcomposeAsyncImageKt→coil3.compose.internal.AsyncImageState
- Direction
- compose uses compose.internal, so a change to compose.internal can break compose, while a change to compose can't break compose.internal.
- Position
- Below the diagonal: compose uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 32 | High / Critical |
| A05:2025 — Injection | 27 | High / Critical |
Roadmap
Top priorities: Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up; Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. | +5.6 pts | Medium | Type Safety |
| Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value. | +5.6 pts | Medium | Dead Code |
| 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. | +4.4 pts | Medium | Security & performance tooling |
| 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. | +3.7 pts | Medium | Architecture documentation |
| Swallowed exception (empty catch) | +3.3 pts | Medium | Exception handling |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +2.1 pts | Medium | Deployment & Rollback |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +1.1 pts | Medium | Documentation (README) |
| Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with UriKt.parseUri (cyclomatic 26), MemoryCacheService.isCacheValueValidForSize (cyclomatic 18). | +0.9 pts | Medium | Cyclomatic Complexity |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| coil-core/src/androidMain/kotlin/coil3/size/ScaleDrawable.kt | 6.3 | Mixed | Code Duplication: Edited copy of a member (27 corresponding lines) |
| coil-compose-core/src/commonMain/kotlin/coil3/compose/AsyncImage.kt | 6.3 | Mixed | Code Duplication: Edited copy of a member (13 corresponding lines) |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| coil-core/src/commonMain/kotlin/coil3/ImageLoader.kt | 7.2 | Mixed | God Classes: MethodTooLong: ImageLoader.enqueue |
| coil-compose/src/commonMain/kotlin/coil3/compose/SingletonAsyncImage.kt | 7.2 | Mixed | Code Duplication: Edited copies of one member (3 members, 15+ corresponding lines) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| coil-core/src/androidMain/kotlin/coil3/decode/StaticImageDecoder.kt | 7.4 | Mixed | Code Duplication: Edited copy of a member (44 corresponding lines) |
| coil-core/src/commonMain/kotlin/coil3/Uri.kt | 7.8 | Mixed | Cyclomatic Complexity: UriKt.parseUri (cyclomatic 26) |
| coil-core/src/commonMain/kotlin/coil3/memory/MemoryCacheService.kt | 7.8 | Mixed | Cyclomatic Complexity: MemoryCacheService.isCacheValueValidForSize (cyclomatic 18) |
| coil-core/src/commonMain/kotlin/coil3/disk/DiskLruCache.kt | 7.8 | Mixed | Cognitive Complexity: DiskLruCache.completeEdit (cognitive 23) |
| coil-compose-core/src/commonMain/kotlin/coil3/compose/internal/ContentPainterModifier.kt | 7.8 | Mixed | Cognitive Complexity: AbstractContentPainterNode.modifyConstraints (cognitive 19) |
| coil-svg/src/nonAndroidMain/kotlin/coil3/svg/SvgImage.nonAndroid.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| coil-gif/src/androidTest/java/coil3/gif/AnimatedTransformationTest.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| coil-core/src/androidDeviceTest/kotlin/coil3/decode/AndroidDecoderTest.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| coil-core/src/nonJvmCommonMain/kotlin/coil3/util/fileSystems.nonJvmCommon.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| coil-core/src/nonAndroidMain/kotlin/coil3/util/SystemCallbacks.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| coil-lint/src/main/kotlin/coil3/lint/ErrorFunctionDetector.kt | 8.5 | Near-clean | Cognitive Complexity: ErrorFunctionDetector.isInsideImageRequestBuilderLambda (cognitive 41) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 51 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 51 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, 151 of 608 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.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.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not included — the Java/Kotlin suite (repository root, Gradle) did not finish re-running within its budget: the JVM suite did not finish re-running within its tier budget.
- D12 Dependency Hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (121 contributor(s) across 2515 commit(s) sampled, automation and bot accounts excluded). One of them holds 88% of the history; the other 120 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated 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. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `build.gradle.kts`, `coil-compose-core/src/commonMain/kotlin/coil3/compose/LocalAsyncImagePreviewHandler.kt`, `coil-core/src/androidMain/kotlin/coil3/EventListener.kt`, `coil-core/src/androidMain/kotlin/coil3/decode/ExifOrientationStrategy.kt`, `coil-core/src/androidMain/kotlin/coil3/transition/Transition.kt`, … (+25 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.
- D34 Knowledge Freshness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 103 commits in the last 90 days, yet 58 of 90 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing 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.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (REDACTED). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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.
- 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
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was UriKt.parseUri at 26.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with UriKt.parseUri (cyclomatic 26), MemoryCacheService.isCacheValueValidForSize (cyclomatic 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
9 method(s) exceeded the cognitive complexity threshold of 15; the worst was UriKt.parseUri at 50.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with UriKt.parseUri (cognitive 50), ErrorFunctionDetector.isInsideImageRequestBuilderLambda (cognitive 41). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 8.0 to about 8.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
6 god class(es) detected.
What to do
- Resolve the 4 MethodTooLong finding(s) in God Classes — start with ImageLoader.kt (4). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with ImageRequest.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with DiskLruCache.kt. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
11 duplicated block group(s) detected. A further 10 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 2 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with AsyncImage.kt (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (44 corresponding lines) finding(s) in Code Duplication — start with StaticImageDecoder.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (27 corresponding lines) finding(s) in Code Duplication — start with ScaleDrawable.kt. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
24 production modules (Gradle), 1 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 13 of the 24 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Circular dependency finding(s) in Coupling. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
3 of 64 classes have LCOM4 above 3.
What to do
- Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with AsyncImagePainter.kt, CrossfadePainter.kt, ComponentRegistry.kt. — One of this dimension's main actionable groups (3 warning-level).
D12 · Dependency Hygiene
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 933 artifact(s) resolved, 648 of them gradable against Maven Central, and 450 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.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 30 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 31 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. 5 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 13 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.
D17 · Explicit Debt
5 deducted task-comment markers across 20655 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 5 TodoComment finding(s) in Explicit Debt — start with SvgImage.nonAndroid.kt, AnimatedTransformationTest.kt, AndroidDecoderTest.kt. — One of this dimension's main actionable groups (5 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 24 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 16 build units (Gradle) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
27 finding(s): 0 critical, 25 high, 2 medium, 0 low. 24 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 2 file(s) — `build.gradle.kts` (lines 234–312), `gradlew` (line 74, line 178) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 24 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 (24 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
32 finding(s): 2 critical, 24 high, 4 medium, 2 low.
What to do
- Resolve the 23 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (23). — One of this dimension's main actionable groups (23 issue-level).
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 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).
D35 · Change Coupling
Strongest change-coupling: AsyncImage.kt↔SubcomposeAsyncImage.kt 67%; ScaleDrawable.kt↔CrossfadeDrawable.kt 50%
What to do
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with AsyncImage.kt, ScaleDrawable.kt. — One of this dimension's main actionable groups (2 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 43 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
- The projects :coil-core → :internal:test-utils → :coil-core (one cycle inside a mutually-dependent group of 3 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference.
What to do
- Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
AX4 · Dependency direction
AX8 · Test isolation
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
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.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
- 2 public types in `coil3.compose.internal.Utils` are marked as implementation by their own namespace, folder or name: `androidKt` (coil-compose-core/src/androidMain/kotlin/coil3/compose/internal/utils.android.kt:1, `internal`), `nonAndroidKt` (coil-compose-core/src/nonAndroidMain/kotlin/coil3/compose/internal/utils.nonAndroid.kt:1, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — coil-compose-core/src/androidMain/kotlin/coil3/compose/internal/utils.android.kt:1
- 2 public types in `coil3.compose.internal` are marked as implementation by their own namespace, folder or name: `DeferredDispatchKt` (coil-compose-core/src/commonMain/kotlin/coil3/compose/internal/DeferredDispatch.kt:1, `internal`), `UtilsKt` (coil-compose-core/src/commonMain/kotlin/coil3/compose/internal/utils.kt:1, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — coil-compose-core/src/commonMain/kotlin/coil3/compose/internal/DeferredDispatch.kt:1
- 2 public types in `coil3.fetch.internal.BlobUriFetcherServiceLoaderTarget` are marked as implementation by their own namespace, folder or name: `jsKt` (coil-core/src/jsMain/kotlin/coil3/fetch/internal/BlobUriFetcherServiceLoaderTarget.js.kt:1, `internal`), `wasmJsKt` (coil-core/src/wasmJsMain/kotlin/coil3/fetch/internal/BlobUriFetcherServiceLoaderTarget.wasmJs.kt:1, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — coil-core/src/jsMain/kotlin/coil3/fetch/internal/BlobUriFetcherServiceLoaderTarget.js.kt:1
- 2 public types in `coil3.gif.internal` are marked as implementation by their own namespace, folder or name: `FrameDelayRewritingSourceKt` (coil-gif/src/main/java/coil3/gif/internal/FrameDelayRewritingSource.kt:1, `internal`), `UtilsKt` (coil-gif/src/main/java/coil3/gif/internal/utils.kt:1, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — coil-gif/src/main/java/coil3/gif/internal/FrameDelayRewritingSource.kt:1
- 1 public type in `coil3.network.cachecontrol.internal.CacheControl` is marked as implementation by its own namespace, folder or name: `Companion` (coil-network-cache-control/src/commonMain/kotlin/coil3/network/cachecontrol/internal/CacheControl.kt:54, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — coil-network-cache-control/src/commonMain/kotlin/coil3/network/cachecontrol/internal/CacheControl.kt:54
- 1 public type in `coil3.network.cachecontrol.internal` is marked as implementation by its own namespace, folder or name: `UtilsKt` (coil-network-cache-control/src/commonMain/kotlin/coil3/network/cachecontrol/internal/utils.kt:1, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — coil-network-cache-control/src/commonMain/kotlin/coil3/network/cachecontrol/internal/utils.kt:1
- 2 public types in `coil3.network.internal.Utils` are marked as implementation by their own namespace, folder or name: `androidKt` (coil-network-core/src/androidMain/kotlin/coil3/network/internal/utils.android.kt:1, `internal`), `nonAndroidKt` (coil-network-core/src/nonAndroidMain/kotlin/coil3/network/internal/utils.nonAndroid.kt:1, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — coil-network-core/src/androidMain/kotlin/coil3/network/internal/utils.android.kt:1
- 3 public types in `coil3.network.internal` are marked as implementation by their own namespace, folder or name: `SingleParameterLazyKt` (coil-network-core/src/commonMain/kotlin/coil3/network/internal/SingleParameterLazy.kt:1, `internal`), `SingleParameterLazy` (coil-network-core/src/commonMain/kotlin/coil3/network/internal/SingleParameterLazy.kt:11, `internal`), `UtilsKt` (coil-network-core/src/commonMain/kotlin/coil3/network/internal/utils.kt:1, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — coil-network-core/src/commonMain/kotlin/coil3/network/internal/SingleParameterLazy.kt:1
- 1 public type in `coil3.network.httpengine.internal` is marked as implementation by its own namespace, folder or name: `UtilsKt` (coil-network-httpengine/src/androidMain/kotlin/coil3/network/httpengine/internal/utils.kt:1, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — coil-network-httpengine/src/androidMain/kotlin/coil3/network/httpengine/internal/utils.kt:1
- 1 public type in `coil3.network.ktor2.internal` is marked as implementation by its own namespace, folder or name: `UtilsKt` (coil-network-ktor2/src/commonMain/kotlin/coil3/network/ktor2/internal/utils.kt:1, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — coil-network-ktor2/src/commonMain/kotlin/coil3/network/ktor2/internal/utils.kt:1
- 2 public types in `coil3.network.ktor2.internal.KtorNetworkFetcherServiceLoaderTarget` are marked as implementation by their own namespace, folder or name: `jsKt` (coil-network-ktor2/src/jsMain/kotlin/coil3/network/ktor2/internal/KtorNetworkFetcherServiceLoaderTarget.js.kt:1, `internal`), `nativeKt` (coil-network-ktor2/src/nativeMain/kotlin/coil3/network/ktor2/internal/KtorNetworkFetcherServiceLoaderTarget.native.kt:1, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — coil-network-ktor2/src/jsMain/kotlin/coil3/network/ktor2/internal/KtorNetworkFetcherServiceLoaderTarget.js.kt:1
- 2 public types in `coil3.network.ktor2.internal.Utils` are marked as implementation by their own namespace, folder or name: `jvmCommonKt` (coil-network-ktor2/src/jvmCommonMain/kotlin/coil3/network/ktor2/internal/utils.jvmCommon.kt:1, `internal`), `nonJvmCommonKt` (coil-network-ktor2/src/nonJvmCommonMain/kotlin/coil3/network/ktor2/internal/utils.nonJvmCommon.kt:1, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — coil-network-ktor2/src/jvmCommonMain/kotlin/coil3/network/ktor2/internal/utils.jvmCommon.kt:1
- 1 public type in `coil3.network.ktor3.internal` is marked as implementation by its own namespace, folder or name: `UtilsKt` (coil-network-ktor3/src/commonMain/kotlin/coil3/network/ktor3/internal/utils.kt:1, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — coil-network-ktor3/src/commonMain/kotlin/coil3/network/ktor3/internal/utils.kt:1
- 3 public types in `coil3.network.ktor3.internal.KtorNetworkFetcherServiceLoaderTarget` are marked as implementation by their own namespace, folder or name: `jsKt` (coil-network-ktor3/src/jsMain/kotlin/coil3/network/ktor3/internal/KtorNetworkFetcherServiceLoaderTarget.js.kt:1, `internal`), `nativeKt` (coil-network-ktor3/src/nativeMain/kotlin/coil3/network/ktor3/internal/KtorNetworkFetcherServiceLoaderTarget.native.kt:1, `internal`), `wasmJsKt` (coil-network-ktor3/src/wasmJsMain/kotlin/coil3/network/ktor3/internal/KtorNetworkFetcherServiceLoaderTarget.wasmJs.kt:1, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — coil-network-ktor3/src/jsMain/kotlin/coil3/network/ktor3/internal/KtorNetworkFetcherServiceLoaderTarget.js.kt:1
- 2 public types in `coil3.network.ktor3.internal.Utils` are marked as implementation by their own namespace, folder or name: `jvmCommonKt` (coil-network-ktor3/src/jvmCommonMain/kotlin/coil3/network/ktor3/internal/utils.jvmCommon.kt:1, `internal`), `nonJvmCommonKt` (coil-network-ktor3/src/nonJvmCommonMain/kotlin/coil3/network/ktor3/internal/utils.nonJvmCommon.kt:1, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — coil-network-ktor3/src/jvmCommonMain/kotlin/coil3/network/ktor3/internal/utils.jvmCommon.kt:1
- 3 public types in `coil3.network.okhttp.internal` are marked as implementation by their own namespace, folder or name: `CallFactoryNetworkClientKt` (coil-network-okhttp/src/commonMain/kotlin/coil3/network/okhttp/internal/CallFactoryNetworkClient.kt:1, `internal`), `CallsKt` (coil-network-okhttp/src/commonMain/kotlin/coil3/network/okhttp/internal/calls.kt:1, `internal`), `UtilsKt` (coil-network-okhttp/src/commonMain/kotlin/coil3/network/okhttp/internal/utils.kt:1, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — coil-network-okhttp/src/commonMain/kotlin/coil3/network/okhttp/internal/CallFactoryNetworkClient.kt:1
- 2 public types in `coil3.svg.internal.ParseSvg` are marked as implementation by their own namespace, folder or name: `androidKt` (coil-svg/src/androidMain/kotlin/coil3/svg/internal/parseSvg.android.kt:1, `internal`), `nonAndroidKt` (coil-svg/src/nonAndroidMain/kotlin/coil3/svg/internal/parseSvg.nonAndroid.kt:1, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — coil-svg/src/androidMain/kotlin/coil3/svg/internal/parseSvg.android.kt:1
- 4 public types in `coil3.svg.internal.Utils` are marked as implementation by their own namespace, folder or name: `androidKt` (coil-svg/src/androidMain/kotlin/coil3/svg/internal/utils.android.kt:1, `internal`), `jvmCommonKt` (coil-svg/src/jvmCommonMain/kotlin/coil3/svg/internal/utils.jvmCommon.kt:1, `internal`), `nonAndroidKt` (coil-svg/src/nonAndroidMain/kotlin/coil3/svg/internal/utils.nonAndroid.kt:1, `internal`), `nonJvmCommonKt` (coil-svg/src/nonJvmCommonMain/kotlin/coil3/svg/internal/utils.nonJvmCommon.kt:1, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — coil-svg/src/androidMain/kotlin/coil3/svg/internal/utils.android.kt:1
- 2 public types in `coil3.svg.internal` are marked as implementation by their own namespace, folder or name: `ParseSvgKt` (coil-svg/src/commonMain/kotlin/coil3/svg/internal/parseSvg.kt:1, `internal`), `UtilsKt` (coil-svg/src/commonMain/kotlin/coil3/svg/internal/utils.kt:1, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — coil-svg/src/commonMain/kotlin/coil3/svg/internal/parseSvg.kt:1
- 3 public types in `coil3.svg.internal.SvgDecoderServiceLoaderTarget` are marked as implementation by their own namespace, folder or name: `jsKt` (coil-svg/src/jsMain/kotlin/coil3/svg/internal/SvgDecoderServiceLoaderTarget.js.kt:1, `internal`), `nativeKt` (coil-svg/src/nativeMain/kotlin/coil3/svg/internal/SvgDecoderServiceLoaderTarget.native.kt:1, `internal`), `wasmJsKt` (coil-svg/src/wasmJsMain/kotlin/coil3/svg/internal/SvgDecoderServiceLoaderTarget.wasmJs.kt:1, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — coil-svg/src/jsMain/kotlin/coil3/svg/internal/SvgDecoderServiceLoaderTarget.js.kt:1
- 1 public type in `coil3.video.internal` is marked as implementation by its own namespace, folder or name: `UtilsKt` (coil-video/src/main/java/coil3/video/internal/utils.kt:1, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — coil-video/src/main/java/coil3/video/internal/utils.kt:1
What to do
- Hide `coil3.compose.internal.Utils` (`androidKt`, `nonAndroidKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `coil3.compose.internal` (`DeferredDispatchKt`, `UtilsKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `coil3.fetch.internal.BlobUriFetcherServiceLoaderTarget` (`jsKt`, `wasmJsKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `coil3.gif.internal` (`FrameDelayRewritingSourceKt`, `UtilsKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `coil3.network.cachecontrol.internal.CacheControl` (`Companion`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `coil3.network.cachecontrol.internal` (`UtilsKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `coil3.network.internal.Utils` (`androidKt`, `nonAndroidKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `coil3.network.internal` (`SingleParameterLazyKt`, `SingleParameterLazy`, `UtilsKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `coil3.network.httpengine.internal` (`UtilsKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `coil3.network.ktor2.internal` (`UtilsKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `coil3.network.ktor2.internal.KtorNetworkFetcherServiceLoaderTarget` (`jsKt`, `nativeKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `coil3.network.ktor2.internal.Utils` (`jvmCommonKt`, `nonJvmCommonKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `coil3.network.ktor3.internal` (`UtilsKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `coil3.network.ktor3.internal.KtorNetworkFetcherServiceLoaderTarget` (`jsKt`, `nativeKt`, `wasmJsKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `coil3.network.ktor3.internal.Utils` (`jvmCommonKt`, `nonJvmCommonKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `coil3.network.okhttp.internal` (`CallFactoryNetworkClientKt`, `CallsKt`, `UtilsKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `coil3.svg.internal.ParseSvg` (`androidKt`, `nonAndroidKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `coil3.svg.internal.Utils` (`androidKt`, `jvmCommonKt`, `nonAndroidKt`, `nonJvmCommonKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `coil3.svg.internal` (`ParseSvgKt`, `UtilsKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `coil3.svg.internal.SvgDecoderServiceLoaderTarget` (`jsKt`, `nativeKt`, `wasmJsKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `coil3.video.internal` (`UtilsKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
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 1 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. — REDACTED:6
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
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
R1 · Type Safety
- 0 typed · 6 plain JS — the untyped files are coil-core/karma.config.d/karma.conf.js, coil-core/karma.config.d/timeout.js, gradle/nodejs/registerSkikoMjsWorkaround.cjs, karma.browser.d/00-disable-wasm-streaming.js, karma.config.d/00-disable-wasm-streaming.js, karma.config.d/10-timeouts.js.
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
R2 · Cyclomatic Complexity
R3 · Large Files
R7 · Dead Code
- Unreachable from the 1 application, 1 tooling and 0 test entry point(s) detected in this repo. This repository declares no build, type-check or test script, so nothing here would fail on a wrong deletion — confirm by hand that nothing loads each file (including by a path built at runtime) before removing it. An undetected custom entry would make these reachable.
- no import path from any entry point (1 application, 1 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×4) — gradle/nodejs/registerSkikoMjsWorkaround.cjs, karma.config.d/10-timeouts.js, coil-core/karma.config.d/timeout.js, …
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X2 · Cancellation propagation
X21 · Side-effecting pattern guard
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×6) — coil-network-okhttp/src/commonMain/kotlin/coil3/network/okhttp/internal/utils.kt:8, coil-network-httpengine/src/androidMain/kotlin/coil3/network/httpengine/internal/HttpEngineNetworkClient.kt:76, coil-network-core/src/commonMain/kotlin/coil3/network/internal/utils.kt:18, …
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `close()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: narrow the catch to the exception this release can actually raise, and record it through whatever this codebase already uses to report problems — or, if it truly cannot matter, say why in a comment on the catch. — coil-network-httpengine/src/androidMain/kotlin/coil3/network/httpengine/internal/HttpEngineUrlRequestCallback.kt:165
- `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×5) — coil-network-core/src/androidMain/kotlin/coil3/network/ConnectivityChecker.kt:25, coil-core/src/commonMain/kotlin/coil3/disk/DiskCache.kt:197, coil-core/src/androidMain/kotlin/coil3/util/bitmaps.kt:33, …
- `catch (_: Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — coil-core/src/commonMain/kotlin/coil3/util/coroutines.kt:13
What to do
- Swallowed exception (empty catch)
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 45% | Weak — gated by R1, R7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 96% | Exemplary | Strongest area. |
| Maturity | 63% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 52% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 94% | Exemplary | Solid. |
| Performance | 94% | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
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 — 74 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Swift imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, 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 — ~14939 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.
- D11 Test Reliability — Test reliability not included
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 2 candidate(s) found and not reported.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Kotlin surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .kt, .swift source were not judged.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- 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) — 30 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 28 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- 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 24 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JavaScript/TypeScript, JVM source (17 module(s), 309 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — the JS/TS workspace (5 production file(s)) has no JavaScript/TypeScript test, but it is 0.67% of this repository's production source and the other 99.33% carries 14,939 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
- R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
- R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
- 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.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — 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 — 53 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Project dependency cycle
- REDACTED
- REDACTED
- Circular dependency
Serious — 74 finding(s)
- Swallowed exception (empty catch) coil-network-okhttp/src/commonMain/kotlin/coil3/network/okhttp/internal/utils.kt:8
- Swallowed exception (empty catch) coil-network-httpengine/src/androidMain/kotlin/coil3/network/httpengine/internal/HttpEngineNetworkClient.kt:76
- Swallowed exception (empty catch) coil-network-httpengine/src/androidMain/kotlin/coil3/network/httpengine/internal/HttpEngineUrlRequestCallback.kt:165
- Swallowed exception (empty catch) coil-network-core/src/commonMain/kotlin/coil3/network/internal/utils.kt:18
- Swallowed exception (empty catch) coil-network-core/src/commonMain/kotlin/coil3/network/internal/utils.kt:53
- Swallowed exception (empty catch) coil-core/src/commonMain/kotlin/coil3/util/utils.kt:40
- Swallowed exception (empty catch) coil-core/src/commonMain/kotlin/coil3/util/utils.kt:48
- Swallowed exception (caught, then discarded) coil-network-core/src/androidMain/kotlin/coil3/network/ConnectivityChecker.kt:25
- Swallowed exception (caught, then discarded) coil-core/src/commonMain/kotlin/coil3/util/coroutines.kt:13
- Swallowed exception (caught, then discarded) coil-core/src/commonMain/kotlin/coil3/disk/DiskCache.kt:197
- Swallowed exception (caught, then discarded) coil-core/src/androidMain/kotlin/coil3/util/bitmaps.kt:33
- Swallowed exception (caught, then discarded) coil-core/src/androidMain/kotlin/coil3/util/contexts.kt:34
- Swallowed exception (caught, then discarded) coil-core/src/androidMain/kotlin/coil3/util/contexts.kt:46
- TodoComment coil-svg/src/nonAndroidMain/kotlin/coil3/svg/SvgImage.nonAndroid.kt:17
- TodoComment coil-gif/src/androidTest/java/coil3/gif/AnimatedTransformationTest.kt:61
- TodoComment coil-core/src/androidDeviceTest/kotlin/coil3/decode/AndroidDecoderTest.kt:368
- TodoComment coil-core/src/nonJvmCommonMain/kotlin/coil3/util/fileSystems.nonJvmCommon.kt:7
- TodoComment coil-core/src/nonAndroidMain/kotlin/coil3/util/SystemCallbacks.kt:10
- MethodTooLong: ImageLoader.enqueue coil-core/src/commonMain/kotlin/coil3/ImageLoader.kt:59
- MethodTooLong: ImageLoader.execute coil-core/src/commonMain/kotlin/coil3/ImageLoader.kt:68
- MethodTooLong: ImageLoader.shutdown coil-core/src/commonMain/kotlin/coil3/ImageLoader.kt:74
- MethodTooLong: ImageLoader.newBuilder coil-core/src/commonMain/kotlin/coil3/ImageLoader.kt:80
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Low cohesion: AsyncImagePainter (LCOM4 4) coil-compose-core/src/commonMain/kotlin/coil3/compose/AsyncImagePainter.kt:154
- Low cohesion: CrossfadePainter (LCOM4 4) coil-compose-core/src/commonMain/kotlin/coil3/compose/CrossfadePainter.kt:46
- Low cohesion: ComponentRegistry (LCOM4 4) coil-core/src/commonMain/kotlin/coil3/ComponentRegistry.kt:22
- REDACTED
- REDACTED
- Change coupling: AsyncImage.kt ↔ SubcomposeAsyncImage.kt coil-compose-core/src/commonMain/kotlin/coil3/compose/AsyncImage.kt:1
- Change coupling: ScaleDrawable.kt ↔ CrossfadeDrawable.kt coil-core/src/androidMain/kotlin/coil3/size/ScaleDrawable.kt:1
- Edited copy of a member (13 corresponding lines) coil-compose-core/src/commonMain/kotlin/coil3/compose/AsyncImage.kt:73
- Edited copy of a member (13 corresponding lines) coil-compose-core/src/commonMain/kotlin/coil3/compose/AsyncImage.kt:126
- UriKt.parseUri (cyclomatic 26) coil-core/src/commonMain/kotlin/coil3/Uri.kt:202
- MemoryCacheService.isCacheValueValidForSize (cyclomatic 18) coil-core/src/commonMain/kotlin/coil3/memory/MemoryCacheService.kt:104
- UriKt.parseUri (cognitive 50) coil-core/src/commonMain/kotlin/coil3/Uri.kt:202
- ErrorFunctionDetector.isInsideImageRequestBuilderLambda (cognitive 41) coil-lint/src/main/kotlin/coil3/lint/ErrorFunctionDetector.kt:66
- MemoryCacheService.isCacheValueValidForSize (cognitive 28) coil-core/src/commonMain/kotlin/coil3/memory/MemoryCacheService.kt:104
- UtilsKt.transformOf (cognitive 24) coil-compose-core/src/commonMain/kotlin/coil3/compose/internal/utils.kt:101
- DiskLruCache.completeEdit (cognitive 23) coil-core/src/commonMain/kotlin/coil3/disk/DiskLruCache.kt:447
- VideoFrameDecoder.decode (cognitive 20) coil-video/src/main/java/coil3/video/VideoFrameDecoder.kt:53
- AbstractContentPainterNode.modifyConstraints (cognitive 19) coil-compose-core/src/commonMain/kotlin/coil3/compose/internal/ContentPainterModifier.kt:381
- SvgDecoder.decode (cognitive 18) coil-svg/src/commonMain/kotlin/coil3/svg/SvgDecoder.kt:68
- SubcomposeAsyncImageKt.contentOf (cognitive 16) coil-compose-core/src/commonMain/kotlin/coil3/compose/SubcomposeAsyncImage.kt:292
- TooManyMethods: Builder coil-core/src/commonMain/kotlin/coil3/request/ImageRequest.kt:299
- ClassTooLong: DiskLruCache coil-core/src/commonMain/kotlin/coil3/disk/DiskLruCache.kt:86
- REDACTED
- Edited copy of a member (44 corresponding lines) coil-core/src/androidMain/kotlin/coil3/decode/StaticImageDecoder.kt:42
- Edited copy of a member (27 corresponding lines) coil-core/src/androidMain/kotlin/coil3/size/ScaleDrawable.kt:64
- Edited copy of a member (26 corresponding lines) coil-compose-core/src/androidMain/kotlin/coil3/compose/AsyncImagePainter.android.kt:18
- Edited copy of a member (16 corresponding lines) coil-core/src/androidMain/kotlin/coil3/decode/StaticImageDecoder.kt:87
- Edited copies of one member (3 members, 15+ corresponding lines) coil-compose/src/commonMain/kotlin/coil3/compose/SingletonAsyncImage.kt:62
- Edited copies of one member (4 members, 12+ corresponding lines) coil-compose-core/src/commonMain/kotlin/coil3/compose/internal/ContentPainterModifier.kt:298
- Edited copy of a member (12 corresponding lines) coil-compose/src/commonMain/kotlin/coil3/compose/SingletonAsyncImage.kt:118
- Edited copy of a member (14 corresponding lines) coil-core/src/androidMain/kotlin/coil3/request/RequestService.android.kt:93
- Duplicated block (33 lines × 2) coil-core/src/androidMain/kotlin/coil3/decode/StaticImageDecoder.kt:47
- Duplicated block (23 lines × 2) coil-core/src/jsCommonMain/kotlin/coil3/decode/SkiaImageDecoder.jsCommon.kt:19
- Duplicated block (15–16 lines × 2) coil-core/src/androidMain/kotlin/coil3/size/ScaleDrawable.kt:72
- Duplicated block (16 lines × 2) coil-core/src/commonMain/kotlin/coil3/decode/DecodeUtils.kt:103
- Duplicated block (15 lines × 2) coil-compose/src/commonMain/kotlin/coil3/compose/SingletonAsyncImage.kt:63
- Duplicated block (13 lines × 3) coil-compose/src/commonMain/kotlin/coil3/compose/SingletonAsyncImage.kt:63
- Duplicated block (11 lines × 2) coil-core/src/androidMain/kotlin/coil3/ColorImage.kt:17
- Duplicated block (49 lines × 2) coil-core/src/androidMain/kotlin/coil3/EventListener.kt:19
- Duplicated block (56 lines × 2) coil-network-ktor2/src/commonMain/kotlin/coil3/network/ktor2/KtorNetworkFetcher.kt:16
- Duplicated block (61 lines × 2) coil-network-ktor2/src/commonMain/kotlin/coil3/network/ktor2/internal/utils.kt:34
- Duplicated block (17 lines × 2) coil-network-ktor2/src/jvmCommonMain/kotlin/coil3/network/ktor2/internal/utils.jvmCommon.kt:10
- Off the main sequence: :coil-core
- Type Safety
- Dead file (~53 LoC) gradle/nodejs/registerSkikoMjsWorkaround.cjs
- Dead file (~34 LoC) karma.config.d/10-timeouts.js
- Dead file (~20 LoC) coil-core/karma.config.d/timeout.js
- Dead file (~19 LoC) karma.browser.d/00-disable-wasm-streaming.js
Minor — 31 finding(s)
- Implementation type on the public API coil-compose-core/src/androidMain/kotlin/coil3/compose/internal/utils.android.kt:1
- Implementation type on the public API coil-compose-core/src/commonMain/kotlin/coil3/compose/internal/DeferredDispatch.kt:1
- Implementation type on the public API coil-core/src/jsMain/kotlin/coil3/fetch/internal/BlobUriFetcherServiceLoaderTarget.js.kt:1
- Implementation type on the public API coil-gif/src/main/java/coil3/gif/internal/FrameDelayRewritingSource.kt:1
- Implementation type on the public API coil-network-cache-control/src/commonMain/kotlin/coil3/network/cachecontrol/internal/CacheControl.kt:54
- Implementation type on the public API coil-network-cache-control/src/commonMain/kotlin/coil3/network/cachecontrol/internal/utils.kt:1
- Implementation type on the public API coil-network-core/src/androidMain/kotlin/coil3/network/internal/utils.android.kt:1
- Implementation type on the public API coil-network-core/src/commonMain/kotlin/coil3/network/internal/SingleParameterLazy.kt:1
- Implementation type on the public API coil-network-httpengine/src/androidMain/kotlin/coil3/network/httpengine/internal/utils.kt:1
- Implementation type on the public API coil-network-ktor2/src/commonMain/kotlin/coil3/network/ktor2/internal/utils.kt:1
- Implementation type on the public API coil-network-ktor2/src/jsMain/kotlin/coil3/network/ktor2/internal/KtorNetworkFetcherServiceLoaderTarget.js.kt:1
- Implementation type on the public API coil-network-ktor2/src/jvmCommonMain/kotlin/coil3/network/ktor2/internal/utils.jvmCommon.kt:1
- Implementation type on the public API coil-network-ktor3/src/commonMain/kotlin/coil3/network/ktor3/internal/utils.kt:1
- Implementation type on the public API coil-network-ktor3/src/jsMain/kotlin/coil3/network/ktor3/internal/KtorNetworkFetcherServiceLoaderTarget.js.kt:1
- Implementation type on the public API coil-network-ktor3/src/jvmCommonMain/kotlin/coil3/network/ktor3/internal/utils.jvmCommon.kt:1
- Implementation type on the public API coil-network-okhttp/src/commonMain/kotlin/coil3/network/okhttp/internal/CallFactoryNetworkClient.kt:1
- Implementation type on the public API coil-svg/src/androidMain/kotlin/coil3/svg/internal/parseSvg.android.kt:1
- Implementation type on the public API coil-svg/src/androidMain/kotlin/coil3/svg/internal/utils.android.kt:1
- Implementation type on the public API coil-svg/src/commonMain/kotlin/coil3/svg/internal/parseSvg.kt:1
- Implementation type on the public API coil-svg/src/jsMain/kotlin/coil3/svg/internal/SvgDecoderServiceLoaderTarget.js.kt:1
- Implementation type on the public API coil-video/src/main/java/coil3/video/internal/utils.kt:1
- Duplicated predicate coil-network-core/src/commonMain/kotlin/coil3/network/NetworkFetcher.kt:332
- Duplicated predicate coil-core/src/androidMain/kotlin/coil3/decode/StaticImageDecoder.kt:70
- Duplicated predicate coil-compose-core/src/androidMain/kotlin/coil3/compose/AsyncImagePainter.android.kt:35
- Duplicated predicate coil-core/src/androidMain/kotlin/coil3/decode/StaticImageDecoder.kt:55
- REDACTED
- REDACTED
- Projects may be oversized for their cohesion
- No ADRs
- No SAST REDACTED:6
- No release approval gate
Minor — 450 finding(s)
- Outdated (compile): org.jetbrains.skiko:skiko-js-wasm-runtime
- Outdated (compile): org.jetbrains.skiko:skiko
- Outdated (compile): org.jetbrains.compose.foundation:foundation
- Outdated (compile): org.jetbrains.compose.animation:animation
- Outdated (compile): org.jetbrains.compose.animation:animation-core
- Outdated (compile): org.jetbrains.compose.collection-internal:collection
- Outdated (compile): org.jetbrains.compose.runtime:runtime
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-test
- Outdated (compile): org.jetbrains.compose.runtime:runtime-saveable
- Outdated (compile): org.jetbrains.compose.ui:ui
- Outdated (compile): org.jetbrains.androidx.lifecycle:lifecycle-common
- Outdated (compile): org.jetbrains.androidx.lifecycle:lifecycle-runtime
- Outdated (compile): org.jetbrains.androidx.lifecycle:lifecycle-runtime-compose
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-serialization-core
- Outdated (compile): org.jetbrains.androidx.savedstate:savedstate
- Outdated (compile): org.jetbrains.androidx.lifecycle:lifecycle-viewmodel
- Outdated (compile): org.jetbrains.androidx.lifecycle:lifecycle-viewmodel-savedstate
- Outdated (compile): org.jetbrains.compose.annotation-internal:annotation
- Outdated (compile): org.jetbrains.androidx.savedstate:savedstate-compose
- Outdated (compile): org.jetbrains.compose.ui:ui-backhandler
- Outdated (compile): org.jetbrains.compose.ui:ui-util
- Outdated (compile): org.jetbrains.compose.ui:ui-uikit
- Outdated (compile): org.jetbrains.compose.ui:ui-geometry
- Outdated (compile): org.jetbrains.compose.ui:ui-graphics
- Outdated (compile): org.jetbrains.compose.ui:ui-text
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8f38f3aaad3b43869e2affeb9ec07f24/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/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-8f38f3aaad3b43869e2affeb9ec07f24/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude kotlin-js-store . | 27 | 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/** . | 32 | 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 30 file(s) — `build.gradle.kts`, `coil-compose-core/src/commonMain/kotlin/coil3/compose/LocalAsyncImagePreviewHandler.kt`, `coil-core/src/androidMain/kotlin/coil3/EventListener.kt`, `coil-core/src/androidMain/kotlin/coil3/decode/ExifOrientationStrategy.kt`, `coil-core/src/androidMain/kotlin/coil3/transition/Transition.kt`, … (+25 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |