Executive summary
mihonapp/mihon falls short of our standard for a preview release, in part because eight passwords or keys sit in the current code. It scores 59 out of 100 and is rated Adequate, and 17 of its 18 critical findings are security problems.
Production Readiness, at 53, is the weakest lens and counts most in the score. The best first step is replacing the eight exposed passwords or keys and switching the old ones off, worth about 6 points. Recording design decisions comes next, worth about 5 points. Raising Production Readiness to 62 would lift the score to about 61.
Eight passwords or keys in the code and eight in the code's history are open to anyone who can read the repository. One secret can leak from the build pipeline. Replacing each exposed password or key and limiting the secret to its own step would close both risks. The inner part of the code that depends on an outer part needs turning around so it points inward.
The product code is 87,407 lines, about €110,000 to rebuild.
If Production Readiness rose from 53 to 62, the lowest score rated Strong, the score would rise from 59 to about 61.
New since the last survey: 15 findings
- Cyclomatic Complexity · ReaderActivity.onCreate (cyclomatic 26) app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderActivity.kt
- Cyclomatic Complexity · ReaderActivity.onKeyEvent (cyclomatic 23) app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderActivity.kt
- Cyclomatic Complexity · WebGpuViewer.onPageSettingsChanged (cyclomatic 23) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt
- Cyclomatic Complexity · WebGpuViewerSettingsKt.WebGpuViewerSettings (cyclomatic 17) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewerSettings.kt
- Cognitive Complexity · ReaderActivity.onKeyEvent (cognitive 21) app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderActivity.kt
- Cognitive Complexity · WebGpuViewerSettingsKt.ShaderParams (cognitive 20) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewerSettings.kt
- Cognitive Complexity · ReaderActivity.onCreate (cognitive 18) app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderActivity.kt
- Cognitive Complexity · WebGpuViewerSettingsKt.WebGpuViewerSettings (cognitive 16) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewerSettings.kt
- God Classes · MethodTooLong: ReaderActivity.onCreate app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderActivity.kt
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) app/src/main/java/eu/kanade/tachiyomi/data/track/anilist/Anilist.kt
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) app/src/main/java/eu/kanade/tachiyomi/data/track/anilist/Anilist.kt
- Code Duplication · Duplicated block (15 lines × 2) app/src/main/java/eu/kanade/presentation/reader/settings/ReadingModePage.kt
- Code Duplication · Duplicated block (7–8 lines × 2) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt
- Churn × Complexity Hotspots · Hotspot: app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderActivity.kt app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderActivity.kt
- Churn × Complexity Hotspots · Hotspot: app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewerSettings.kt app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewerSettings.kt
Fixed since the last survey: 33 findings
- Cyclomatic Complexity · PagerViewer.handleKeyEvent (cyclomatic 27) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/pager/PagerViewer.kt
- Cyclomatic Complexity · WebGpuViewer.handleKeyEvent (cyclomatic 27) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt
- Cyclomatic Complexity · VerticalFastScrollerKt.VerticalFastScroller (cyclomatic 21) presentation-core/src/main/java/tachiyomi/presentation/core/components/VerticalFastScroller.kt
- Cyclomatic Complexity · WebtoonViewer.handleKeyEvent (cyclomatic 21) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webtoon/WebtoonViewer.kt
- Cognitive Complexity · PagerViewer.handleKeyEvent (cognitive 40) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/pager/PagerViewer.kt
- Cognitive Complexity · WebGpuViewer.handleKeyEvent (cognitive 40) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt
- Cognitive Complexity · VerticalFastScrollerKt.VerticalFastScroller (cognitive 24) presentation-core/src/main/java/tachiyomi/presentation/core/components/VerticalFastScroller.kt
- Cognitive Complexity · WebtoonViewer.handleKeyEvent (cognitive 24) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webtoon/WebtoonViewer.kt
- Cognitive Complexity · ScrollbarKt.onDrawScrollbar (cognitive 17) presentation-core/src/main/java/tachiyomi/presentation/core/util/Scrollbar.kt
- Code Duplication · Near-duplicate member pair (70 shared lines) presentation-core/src/main/java/tachiyomi/presentation/core/components/VerticalFastScroller.kt
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) app/src/main/java/eu/kanade/tachiyomi/data/track/anilist/Anilist.kt
- Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) app/src/main/java/eu/kanade/tachiyomi/data/track/anilist/Anilist.kt
- Code Duplication · Duplicated block (30 lines × 2) app/src/main/java/eu/kanade/presentation/reader/settings/ReadingModePage.kt
- Code Duplication · Duplicated block (20–24 lines × 2) presentation-core/src/main/java/tachiyomi/presentation/core/components/VerticalFastScroller.kt
- Code Duplication · Duplicated block (18 lines × 2) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/pager/PagerViewer.kt
- Code Duplication · Duplicated block (18 lines × 2) presentation-core/src/main/java/tachiyomi/presentation/core/components/VerticalFastScroller.kt
- Code Duplication · Duplicated block (16 lines × 2) presentation-core/src/main/java/tachiyomi/presentation/core/components/VerticalFastScroller.kt
- Code Duplication · Duplicated block (14 lines × 2) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/pager/PagerViewer.kt
- Code Duplication · Duplicated block (13 lines × 2) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/pager/PagerViewerAdapter.kt
- Code Duplication · Duplicated block (11 lines × 2) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/pager/PagerPageHolder.kt
- Code Duplication · Duplicated block (11 lines × 2) presentation-core/src/main/java/tachiyomi/presentation/core/components/VerticalFastScroller.kt
- Code Duplication · Duplicated block (10 lines × 2) app/src/main/java/eu/kanade/presentation/reader/settings/ReadingModePage.kt
- Code Duplication · Duplicated block (8 lines × 2) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/pager/PagerViewer.kt
- Code Duplication · Duplicated block (7–8 lines × 2) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt
- Code Duplication · Duplicated block (5 lines × 2) presentation-core/src/main/java/tachiyomi/presentation/core/components/VerticalFastScroller.kt
- Code Duplication · Duplicated block (4–5 lines × 3) presentation-core/src/main/java/tachiyomi/presentation/core/components/VerticalFastScroller.kt
- Code Duplication · Duplicated block (12 lines × 2) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/pager/PagerConfig.kt
- Code Duplication · Duplicated block (9 lines × 2) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/pager/PagerPageHolder.kt
- Code Duplication · Duplicated block (12 lines × 2) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/pager/PagerTransitionHolder.kt
- Churn × Complexity Hotspots · Hotspot: app/src/main/java/eu/kanade/tachiyomi/data/library/LibraryUpdateWorker.kt app/src/main/java/eu/kanade/tachiyomi/data/library/LibraryUpdateWorker.kt
- Explicit Debt · TodoComment presentation-core/src/main/java/tachiyomi/presentation/core/components/VerticalFastScroller.kt
- Explicit Debt · TodoComment presentation-core/src/main/java/tachiyomi/presentation/core/components/VerticalFastScroller.kt
- Knowledge Freshness · Orphaned knowledge presentation-core/src/main/java/tachiyomi/presentation/core/components/VerticalFastScroller.kt
Rebuild cost: about €110,000 · Estimate
| Cost to rebuild | €36,000 to €180,000, for 597 to 1,894 hours of work, about 0.7 person-years for 1 to 2 engineers |
|---|---|
| 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 59. 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: 87,407 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 eu.kanade.presentation.util | 2 eu.kanade.tachiyomi.data.database.models | 3 eu.kanade.tachiyomi.source.model | 4 eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences | 5 mihon.domain.extension.model | 6 tachiyomi.core.common.preference | 7 tachiyomi.domain.category.model | 8 tachiyomi.domain.chapter.model | 9 tachiyomi.domain.track.model | 10 eu.kanade.domain.base | 11 eu.kanade.domain.source.service | 12 eu.kanade.tachiyomi.data.track.model | 13 eu.kanade.tachiyomi.extension.model.Extension | 14 eu.kanade.tachiyomi.ui.reader.model | 15 tachiyomi.domain.manga.model | 16 tachiyomi.domain.source.model | 17 eu.kanade.tachiyomi.extension | 18 tachiyomi.domain.library.service | 19 tachiyomi.domain.manga.interactor | 20 tachiyomi.domain.source.service | 21 eu.kanade.tachiyomi.data.backup.create | 22 eu.kanade.tachiyomi.source | 23 tachiyomi.domain.category.interactor | 24 tachiyomi.domain.chapter.interactor | 25 eu.kanade.presentation.browse | 26 eu.kanade.tachiyomi.data.track | 27 eu.kanade.tachiyomi.ui.reader.viewer | 28 eu.kanade.domain.track.interactor | 29 eu.kanade.tachiyomi.ui.reader.setting | 30 eu.kanade.presentation.more.settings.screen | 31 eu.kanade.tachiyomi.ui.browse.source.browse | 32 eu.kanade.tachiyomi.ui.reader | 33 mihon.app.di | 34 eu.kanade.tachiyomi.data.download | 35 eu.kanade.domain.chapter.interactor | 36 eu.kanade.tachiyomi.ui.updates | 37 mihon.domain.source.interactor | 38 eu.kanade.tachiyomi.ui.manga | 39 eu.kanade.presentation.manga | 40 eu.kanade.tachiyomi.ui.library |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 eu.kanade.presentation.util | ||||||||||||||||||||||||||||||||||||||||
| 2 eu.kanade.tachiyomi.data.database.models | ||||||||||||||||||||||||||||||||||||||||
| 3 eu.kanade.tachiyomi.source.model | ||||||||||||||||||||||||||||||||||||||||
| 4 eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences | ||||||||||||||||||||||||||||||||||||||||
| 5 mihon.domain.extension.model | ||||||||||||||||||||||||||||||||||||||||
| 6 tachiyomi.core.common.preference | ||||||||||||||||||||||||||||||||||||||||
| 7 tachiyomi.domain.category.model | ||||||||||||||||||||||||||||||||||||||||
| 8 tachiyomi.domain.chapter.model | ||||||||||||||||||||||||||||||||||||||||
| 9 tachiyomi.domain.track.model | ||||||||||||||||||||||||||||||||||||||||
| 10 eu.kanade.domain.base | 4 | |||||||||||||||||||||||||||||||||||||||
| 11 eu.kanade.domain.source.service | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 12 eu.kanade.tachiyomi.data.track.model | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 eu.kanade.tachiyomi.extension.model.Extension | 7 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 eu.kanade.tachiyomi.ui.reader.model | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 tachiyomi.domain.manga.model | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 16 tachiyomi.domain.source.model | 6 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 eu.kanade.tachiyomi.extension | 1 | 1 | 4 | 1 | ||||||||||||||||||||||||||||||||||||
| 18 tachiyomi.domain.library.service | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 tachiyomi.domain.manga.interactor | 1 | 10 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 tachiyomi.domain.source.service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 eu.kanade.tachiyomi.data.backup.create | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 eu.kanade.tachiyomi.source | 12 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 23 tachiyomi.domain.category.interactor | 4 | 5 | ||||||||||||||||||||||||||||||||||||||
| 24 tachiyomi.domain.chapter.interactor | 7 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 25 eu.kanade.presentation.browse | 1 | 6 | 3 | 4 | 3 | |||||||||||||||||||||||||||||||||||
| 26 eu.kanade.tachiyomi.data.track | 2 | 4 | 2 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 27 eu.kanade.tachiyomi.ui.reader.viewer | 3 | 14 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 28 eu.kanade.domain.track.interactor | 1 | 1 | 1 | 1 | 3 | 6 | ||||||||||||||||||||||||||||||||||
| 29 eu.kanade.tachiyomi.ui.reader.setting | 7 | 3 | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||
| 30 eu.kanade.presentation.more.settings.screen | 2 | 1 | 3 | 1 | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||
| 31 eu.kanade.tachiyomi.ui.browse.source.browse | 2 | 3 | 1 | 1 | 1 | 2 | 1 | 2 | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||
| 32 eu.kanade.tachiyomi.ui.reader | 1 | 1 | 2 | 6 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 4 | 1 | 3 | |||||||||||||||||||||||||
| 33 mihon.app.di | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 3 | |||||||||||||||||||||||||||
| 34 eu.kanade.tachiyomi.data.download | 2 | 5 | 5 | 1 | 2 | 4 | 3 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||
| 35 eu.kanade.domain.chapter.interactor | 1 | 3 | 2 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 36 eu.kanade.tachiyomi.ui.updates | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||
| 37 mihon.domain.source.interactor | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 38 eu.kanade.tachiyomi.ui.manga | 2 | 1 | 1 | 2 | 1 | 1 | 3 | 1 | 4 | 1 | 2 | 2 | 2 | 1 | 3 | 1 | 2 | 2 | 1 | 1 | ||||||||||||||||||||
| 39 eu.kanade.presentation.manga | 1 | 1 | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 40 eu.kanade.tachiyomi.ui.library | 1 | 3 | 2 | 1 | 1 | 2 | 1 | 2 | 1 | 1 | 4 | 2 | 3 | 2 | 1 | 1 |
10→6 eu.kanade.domain.base uses tachiyomi.core.common.preference✕
- Connections
- 4 pairs of types, where a type in eu.kanade.domain.base uses a type in tachiyomi.core.common.preference.
- The types involved
eu.kanade.domain.base.BasePreferences→tachiyomi.core.common.preference.Preferenceeu.kanade.domain.base.BasePreferences→tachiyomi.core.common.preference.PreferenceStoreeu.kanade.domain.base.ExtensionInstallerPreference→tachiyomi.core.common.preference.Preferenceeu.kanade.domain.base.ExtensionInstallerPreference→tachiyomi.core.common.preference.PreferenceStore
- Direction
- eu.kanade.domain.base uses tachiyomi.core.common.preference, so a change to tachiyomi.core.common.preference can break eu.kanade.domain.base, while a change to eu.kanade.domain.base can't break tachiyomi.core.common.preference.
- Position
- Below the diagonal: eu.kanade.domain.base uses a module listed above it, which is the healthy direction.
11→5 eu.kanade.domain.source.service uses mihon.domain.extension.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.domain.source.service uses a type in mihon.domain.extension.model.
- The types involved
eu.kanade.domain.source.service.SourcePreferences→mihon.domain.extension.model.ContentWarning
- Direction
- eu.kanade.domain.source.service uses mihon.domain.extension.model, so a change to mihon.domain.extension.model can break eu.kanade.domain.source.service, while a change to eu.kanade.domain.source.service can't break mihon.domain.extension.model.
- Position
- Below the diagonal: eu.kanade.domain.source.service uses a module listed above it, which is the healthy direction.
11→6 eu.kanade.domain.source.service uses tachiyomi.core.common.preference✕
- Connections
- 2 pairs of types, where a type in eu.kanade.domain.source.service uses a type in tachiyomi.core.common.preference.
- The types involved
eu.kanade.domain.source.service.SourcePreferences→tachiyomi.core.common.preference.Preferenceeu.kanade.domain.source.service.SourcePreferences→tachiyomi.core.common.preference.PreferenceStore
- Direction
- eu.kanade.domain.source.service uses tachiyomi.core.common.preference, so a change to tachiyomi.core.common.preference can break eu.kanade.domain.source.service, while a change to eu.kanade.domain.source.service can't break tachiyomi.core.common.preference.
- Position
- Below the diagonal: eu.kanade.domain.source.service uses a module listed above it, which is the healthy direction.
12→2 eu.kanade.tachiyomi.data.track.model uses eu.kanade.tachiyomi.data.database.models✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.data.track.model uses a type in eu.kanade.tachiyomi.data.database.models.
- The types involved
eu.kanade.tachiyomi.data.track.model.TrackSearch→eu.kanade.tachiyomi.data.database.models.Track
- Direction
- eu.kanade.tachiyomi.data.track.model uses eu.kanade.tachiyomi.data.database.models, so a change to eu.kanade.tachiyomi.data.database.models can break eu.kanade.tachiyomi.data.track.model, while a change to eu.kanade.tachiyomi.data.track.model can't break eu.kanade.tachiyomi.data.database.models.
- Position
- Below the diagonal: eu.kanade.tachiyomi.data.track.model uses a module listed above it, which is the healthy direction.
13→5 eu.kanade.tachiyomi.extension.model.Extension uses mihon.domain.extension.model✕
- Connections
- 7 pairs of types, where a type in eu.kanade.tachiyomi.extension.model.Extension uses a type in mihon.domain.extension.model.
- The types involved
eu.kanade.tachiyomi.extension.model.Extension.Available→mihon.domain.extension.model.ContentWarningeu.kanade.tachiyomi.extension.model.Extension.Available→mihon.domain.extension.model.ExtensionStoreeu.kanade.tachiyomi.extension.model.Extension.Installed→mihon.domain.extension.model.ExtensionStoreeu.kanade.tachiyomi.extension.model.Extension.Loaded→mihon.domain.extension.model.ContentWarningeu.kanade.tachiyomi.extension.model.Extension.Loaded→mihon.domain.extension.model.ExtensionStoreeu.kanade.tachiyomi.extension.model.Extension.NotLoaded→mihon.domain.extension.model.ContentWarningeu.kanade.tachiyomi.extension.model.Extension.NotLoaded→mihon.domain.extension.model.ExtensionStore
- Direction
- eu.kanade.tachiyomi.extension.model.Extension uses mihon.domain.extension.model, so a change to mihon.domain.extension.model can break eu.kanade.tachiyomi.extension.model.Extension, while a change to eu.kanade.tachiyomi.extension.model.Extension can't break mihon.domain.extension.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.extension.model.Extension uses a module listed above it, which is the healthy direction.
13→22 eu.kanade.tachiyomi.extension.model.Extension uses eu.kanade.tachiyomi.source part of a loop✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.extension.model.Extension uses a type in eu.kanade.tachiyomi.source.
- The types involved
eu.kanade.tachiyomi.extension.model.Extension.Loaded→eu.kanade.tachiyomi.source.Source
- Direction
- eu.kanade.tachiyomi.extension.model.Extension uses eu.kanade.tachiyomi.source, so a change to eu.kanade.tachiyomi.source can break eu.kanade.tachiyomi.extension.model.Extension, while a change to eu.kanade.tachiyomi.extension.model.Extension can't break eu.kanade.tachiyomi.source.
- 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→3 eu.kanade.tachiyomi.ui.reader.model uses eu.kanade.tachiyomi.source.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.reader.model uses a type in eu.kanade.tachiyomi.source.model.
- The types involved
eu.kanade.tachiyomi.ui.reader.model.ReaderPage→eu.kanade.tachiyomi.source.model.Page
- Direction
- eu.kanade.tachiyomi.ui.reader.model uses eu.kanade.tachiyomi.source.model, so a change to eu.kanade.tachiyomi.source.model can break eu.kanade.tachiyomi.ui.reader.model, while a change to eu.kanade.tachiyomi.ui.reader.model can't break eu.kanade.tachiyomi.source.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader.model uses a module listed above it, which is the healthy direction.
14→8 eu.kanade.tachiyomi.ui.reader.model uses tachiyomi.domain.chapter.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.reader.model uses a type in tachiyomi.domain.chapter.model.
- The types involved
eu.kanade.tachiyomi.ui.reader.model.ReaderChapter→tachiyomi.domain.chapter.model.Chapter
- Direction
- eu.kanade.tachiyomi.ui.reader.model uses tachiyomi.domain.chapter.model, so a change to tachiyomi.domain.chapter.model can break eu.kanade.tachiyomi.ui.reader.model, while a change to eu.kanade.tachiyomi.ui.reader.model can't break tachiyomi.domain.chapter.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader.model uses a module listed above it, which is the healthy direction.
15→3 tachiyomi.domain.manga.model uses eu.kanade.tachiyomi.source.model✕
- Connections
- 2 pairs of types, where a type in tachiyomi.domain.manga.model uses a type in eu.kanade.tachiyomi.source.model.
- The types involved
tachiyomi.domain.manga.model.Manga→eu.kanade.tachiyomi.source.model.UpdateStrategytachiyomi.domain.manga.model.MangaRemoteUpdate→eu.kanade.tachiyomi.source.model.UpdateStrategy
- Direction
- tachiyomi.domain.manga.model uses eu.kanade.tachiyomi.source.model, so a change to eu.kanade.tachiyomi.source.model can break tachiyomi.domain.manga.model, while a change to tachiyomi.domain.manga.model can't break eu.kanade.tachiyomi.source.model.
- Position
- Below the diagonal: tachiyomi.domain.manga.model uses a module listed above it, which is the healthy direction.
15→6 tachiyomi.domain.manga.model uses tachiyomi.core.common.preference✕
- Connections
- 2 pairs of types, where a type in tachiyomi.domain.manga.model uses a type in tachiyomi.core.common.preference.
- The types involved
tachiyomi.domain.manga.model.Manga→tachiyomi.core.common.preference.TriStatetachiyomi.domain.manga.model.TriStateKt→tachiyomi.core.common.preference.TriState
- Direction
- tachiyomi.domain.manga.model uses tachiyomi.core.common.preference, so a change to tachiyomi.core.common.preference can break tachiyomi.domain.manga.model, while a change to tachiyomi.domain.manga.model can't break tachiyomi.core.common.preference.
- Position
- Below the diagonal: tachiyomi.domain.manga.model uses a module listed above it, which is the healthy direction.
16→3 tachiyomi.domain.source.model uses eu.kanade.tachiyomi.source.model✕
- Connections
- 6 pairs of types, where a type in tachiyomi.domain.source.model uses a type in eu.kanade.tachiyomi.source.model.
- The types involved
tachiyomi.domain.source.model.StubSource→eu.kanade.tachiyomi.source.model.FilterListtachiyomi.domain.source.model.StubSource→eu.kanade.tachiyomi.source.model.MangasPagetachiyomi.domain.source.model.StubSource→eu.kanade.tachiyomi.source.model.Pagetachiyomi.domain.source.model.StubSource→eu.kanade.tachiyomi.source.model.SChaptertachiyomi.domain.source.model.StubSource→eu.kanade.tachiyomi.source.model.SMangatachiyomi.domain.source.model.StubSource→eu.kanade.tachiyomi.source.model.SMangaUpdate
- Direction
- tachiyomi.domain.source.model uses eu.kanade.tachiyomi.source.model, so a change to eu.kanade.tachiyomi.source.model can break tachiyomi.domain.source.model, while a change to tachiyomi.domain.source.model can't break eu.kanade.tachiyomi.source.model.
- Position
- Below the diagonal: tachiyomi.domain.source.model uses a module listed above it, which is the healthy direction.
16→22 tachiyomi.domain.source.model uses eu.kanade.tachiyomi.source part of a loop✕
- Connections
- 1 pair of types, where a type in tachiyomi.domain.source.model uses a type in eu.kanade.tachiyomi.source.
- The types involved
tachiyomi.domain.source.model.StubSource→eu.kanade.tachiyomi.source.Source
- Direction
- tachiyomi.domain.source.model uses eu.kanade.tachiyomi.source, so a change to eu.kanade.tachiyomi.source can break tachiyomi.domain.source.model, while a change to tachiyomi.domain.source.model can't break eu.kanade.tachiyomi.source.
- 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→5 eu.kanade.tachiyomi.extension uses mihon.domain.extension.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.extension uses a type in mihon.domain.extension.model.
- The types involved
eu.kanade.tachiyomi.extension.ExtensionManager→mihon.domain.extension.model.ExtensionStore
- Direction
- eu.kanade.tachiyomi.extension uses mihon.domain.extension.model, so a change to mihon.domain.extension.model can break eu.kanade.tachiyomi.extension, while a change to eu.kanade.tachiyomi.extension can't break mihon.domain.extension.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.extension uses a module listed above it, which is the healthy direction.
17→11 eu.kanade.tachiyomi.extension uses eu.kanade.domain.source.service✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.extension uses a type in eu.kanade.domain.source.service.
- The types involved
eu.kanade.tachiyomi.extension.ExtensionManager→eu.kanade.domain.source.service.SourcePreferences
- Direction
- eu.kanade.tachiyomi.extension uses eu.kanade.domain.source.service, so a change to eu.kanade.domain.source.service can break eu.kanade.tachiyomi.extension, while a change to eu.kanade.tachiyomi.extension can't break eu.kanade.domain.source.service.
- Position
- Below the diagonal: eu.kanade.tachiyomi.extension uses a module listed above it, which is the healthy direction.
17→13 eu.kanade.tachiyomi.extension uses eu.kanade.tachiyomi.extension.model.Extension✕
- Connections
- 4 pairs of types, where a type in eu.kanade.tachiyomi.extension uses a type in eu.kanade.tachiyomi.extension.model.Extension.
- The types involved
eu.kanade.tachiyomi.extension.ExtensionManager→eu.kanade.tachiyomi.extension.model.Extension.Availableeu.kanade.tachiyomi.extension.ExtensionManager→eu.kanade.tachiyomi.extension.model.Extension.Installedeu.kanade.tachiyomi.extension.ExtensionManager→eu.kanade.tachiyomi.extension.model.Extension.Loadedeu.kanade.tachiyomi.extension.ExtensionManager→eu.kanade.tachiyomi.extension.model.Extension.NotLoaded
- Direction
- eu.kanade.tachiyomi.extension uses eu.kanade.tachiyomi.extension.model.Extension, so a change to eu.kanade.tachiyomi.extension.model.Extension can break eu.kanade.tachiyomi.extension, while a change to eu.kanade.tachiyomi.extension can't break eu.kanade.tachiyomi.extension.model.Extension.
- Position
- Below the diagonal: eu.kanade.tachiyomi.extension uses a module listed above it, which is the healthy direction.
17→16 eu.kanade.tachiyomi.extension uses tachiyomi.domain.source.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.extension uses a type in tachiyomi.domain.source.model.
- The types involved
eu.kanade.tachiyomi.extension.ExtensionManager→tachiyomi.domain.source.model.StubSource
- Direction
- eu.kanade.tachiyomi.extension uses tachiyomi.domain.source.model, so a change to tachiyomi.domain.source.model can break eu.kanade.tachiyomi.extension, while a change to eu.kanade.tachiyomi.extension can't break tachiyomi.domain.source.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.extension uses a module listed above it, which is the healthy direction.
18→6 tachiyomi.domain.library.service uses tachiyomi.core.common.preference✕
- Connections
- 3 pairs of types, where a type in tachiyomi.domain.library.service uses a type in tachiyomi.core.common.preference.
- The types involved
tachiyomi.domain.library.service.LibraryPreferences→tachiyomi.core.common.preference.Preferencetachiyomi.domain.library.service.LibraryPreferences→tachiyomi.core.common.preference.PreferenceStoretachiyomi.domain.library.service.LibraryPreferences→tachiyomi.core.common.preference.TriState
- Direction
- tachiyomi.domain.library.service uses tachiyomi.core.common.preference, so a change to tachiyomi.core.common.preference can break tachiyomi.domain.library.service, while a change to tachiyomi.domain.library.service can't break tachiyomi.core.common.preference.
- Position
- Below the diagonal: tachiyomi.domain.library.service uses a module listed above it, which is the healthy direction.
18→15 tachiyomi.domain.library.service uses tachiyomi.domain.manga.model✕
- Connections
- 1 pair of types, where a type in tachiyomi.domain.library.service uses a type in tachiyomi.domain.manga.model.
- The types involved
tachiyomi.domain.library.service.LibraryPreferences→tachiyomi.domain.manga.model.Manga
- Direction
- tachiyomi.domain.library.service uses tachiyomi.domain.manga.model, so a change to tachiyomi.domain.manga.model can break tachiyomi.domain.library.service, while a change to tachiyomi.domain.library.service can't break tachiyomi.domain.manga.model.
- Position
- Below the diagonal: tachiyomi.domain.library.service uses a module listed above it, which is the healthy direction.
19→8 tachiyomi.domain.manga.interactor uses tachiyomi.domain.chapter.model✕
- Connections
- 1 pair of types, where a type in tachiyomi.domain.manga.interactor uses a type in tachiyomi.domain.chapter.model.
- The types involved
tachiyomi.domain.manga.interactor.GetMangaWithChapters→tachiyomi.domain.chapter.model.Chapter
- Direction
- tachiyomi.domain.manga.interactor uses tachiyomi.domain.chapter.model, so a change to tachiyomi.domain.chapter.model can break tachiyomi.domain.manga.interactor, while a change to tachiyomi.domain.manga.interactor can't break tachiyomi.domain.chapter.model.
- Position
- Below the diagonal: tachiyomi.domain.manga.interactor uses a module listed above it, which is the healthy direction.
19→15 tachiyomi.domain.manga.interactor uses tachiyomi.domain.manga.model✕
- Connections
- 10 pairs of types, where a type in tachiyomi.domain.manga.interactor uses a type in tachiyomi.domain.manga.model.
- The types involved
tachiyomi.domain.manga.interactor.FetchInterval→tachiyomi.domain.manga.model.Mangatachiyomi.domain.manga.interactor.FetchInterval→tachiyomi.domain.manga.model.MangaUpdatetachiyomi.domain.manga.interactor.GetDuplicateLibraryManga→tachiyomi.domain.manga.model.Mangatachiyomi.domain.manga.interactor.GetDuplicateLibraryManga→tachiyomi.domain.manga.model.MangaWithChapterCounttachiyomi.domain.manga.interactor.GetFavorites→tachiyomi.domain.manga.model.Mangatachiyomi.domain.manga.interactor.GetManga→tachiyomi.domain.manga.model.Mangatachiyomi.domain.manga.interactor.GetMangaByUrlAndSourceId→tachiyomi.domain.manga.model.Mangatachiyomi.domain.manga.interactor.GetMangaWithChapters→tachiyomi.domain.manga.model.Mangatachiyomi.domain.manga.interactor.NetworkToLocalManga→tachiyomi.domain.manga.model.Mangatachiyomi.domain.manga.interactor.SetMangaChapterFlags→tachiyomi.domain.manga.model.Manga
- Direction
- tachiyomi.domain.manga.interactor uses tachiyomi.domain.manga.model, so a change to tachiyomi.domain.manga.model can break tachiyomi.domain.manga.interactor, while a change to tachiyomi.domain.manga.interactor can't break tachiyomi.domain.manga.model.
- Position
- Below the diagonal: tachiyomi.domain.manga.interactor uses a module listed above it, which is the healthy direction.
19→24 tachiyomi.domain.manga.interactor uses tachiyomi.domain.chapter.interactor part of a loop✕
- Connections
- 1 pair of types, where a type in tachiyomi.domain.manga.interactor uses a type in tachiyomi.domain.chapter.interactor.
- The types involved
tachiyomi.domain.manga.interactor.FetchInterval→tachiyomi.domain.chapter.interactor.GetChaptersByMangaId
- Direction
- tachiyomi.domain.manga.interactor uses tachiyomi.domain.chapter.interactor, so a change to tachiyomi.domain.chapter.interactor can break tachiyomi.domain.manga.interactor, while a change to tachiyomi.domain.manga.interactor can't break tachiyomi.domain.chapter.interactor.
- 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→16 tachiyomi.domain.source.service uses tachiyomi.domain.source.model✕
- Connections
- 1 pair of types, where a type in tachiyomi.domain.source.service uses a type in tachiyomi.domain.source.model.
- The types involved
tachiyomi.domain.source.service.SourceManager→tachiyomi.domain.source.model.StubSource
- Direction
- tachiyomi.domain.source.service uses tachiyomi.domain.source.model, so a change to tachiyomi.domain.source.model can break tachiyomi.domain.source.service, while a change to tachiyomi.domain.source.service can't break tachiyomi.domain.source.model.
- Position
- Below the diagonal: tachiyomi.domain.source.service uses a module listed above it, which is the healthy direction.
20→22 tachiyomi.domain.source.service uses eu.kanade.tachiyomi.source part of a loop✕
- Connections
- 1 pair of types, where a type in tachiyomi.domain.source.service uses a type in eu.kanade.tachiyomi.source.
- The types involved
tachiyomi.domain.source.service.SourceManager→eu.kanade.tachiyomi.source.Source
- Direction
- tachiyomi.domain.source.service uses eu.kanade.tachiyomi.source, so a change to eu.kanade.tachiyomi.source can break tachiyomi.domain.source.service, while a change to tachiyomi.domain.source.service can't break eu.kanade.tachiyomi.source.
- 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.
21→15 eu.kanade.tachiyomi.data.backup.create uses tachiyomi.domain.manga.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.data.backup.create uses a type in tachiyomi.domain.manga.model.
- The types involved
eu.kanade.tachiyomi.data.backup.create.BackupCreator→tachiyomi.domain.manga.model.Manga
- Direction
- eu.kanade.tachiyomi.data.backup.create uses tachiyomi.domain.manga.model, so a change to tachiyomi.domain.manga.model can break eu.kanade.tachiyomi.data.backup.create, while a change to eu.kanade.tachiyomi.data.backup.create can't break tachiyomi.domain.manga.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.data.backup.create uses a module listed above it, which is the healthy direction.
21→19 eu.kanade.tachiyomi.data.backup.create uses tachiyomi.domain.manga.interactor✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.data.backup.create uses a type in tachiyomi.domain.manga.interactor.
- The types involved
eu.kanade.tachiyomi.data.backup.create.BackupCreator→tachiyomi.domain.manga.interactor.GetFavorites
- Direction
- eu.kanade.tachiyomi.data.backup.create uses tachiyomi.domain.manga.interactor, so a change to tachiyomi.domain.manga.interactor can break eu.kanade.tachiyomi.data.backup.create, while a change to eu.kanade.tachiyomi.data.backup.create can't break tachiyomi.domain.manga.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.data.backup.create uses a module listed above it, which is the healthy direction.
21→33 eu.kanade.tachiyomi.data.backup.create uses mihon.app.di part of a loop✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.data.backup.create uses a type in mihon.app.di.
- The types involved
eu.kanade.tachiyomi.data.backup.create.BackupCreateWorker→mihon.app.di.AppGraph
- Direction
- eu.kanade.tachiyomi.data.backup.create uses mihon.app.di, so a change to mihon.app.di can break eu.kanade.tachiyomi.data.backup.create, while a change to eu.kanade.tachiyomi.data.backup.create can't break mihon.app.di.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→3 eu.kanade.tachiyomi.source uses eu.kanade.tachiyomi.source.model✕
- Connections
- 12 pairs of types, where a type in eu.kanade.tachiyomi.source uses a type in eu.kanade.tachiyomi.source.model.
- The types involved
eu.kanade.tachiyomi.source.CatalogueSource→eu.kanade.tachiyomi.source.model.FilterListeu.kanade.tachiyomi.source.CatalogueSource→eu.kanade.tachiyomi.source.model.MangasPageeu.kanade.tachiyomi.source.CatalogueSource→eu.kanade.tachiyomi.source.model.Pageeu.kanade.tachiyomi.source.CatalogueSource→eu.kanade.tachiyomi.source.model.SChaptereu.kanade.tachiyomi.source.CatalogueSource→eu.kanade.tachiyomi.source.model.SMangaeu.kanade.tachiyomi.source.CatalogueSource→eu.kanade.tachiyomi.source.model.SMangaUpdateeu.kanade.tachiyomi.source.Source→eu.kanade.tachiyomi.source.model.FilterListeu.kanade.tachiyomi.source.Source→eu.kanade.tachiyomi.source.model.MangasPageeu.kanade.tachiyomi.source.Source→eu.kanade.tachiyomi.source.model.Pageeu.kanade.tachiyomi.source.Source→eu.kanade.tachiyomi.source.model.SChaptereu.kanade.tachiyomi.source.Source→eu.kanade.tachiyomi.source.model.SMangaeu.kanade.tachiyomi.source.Source→eu.kanade.tachiyomi.source.model.SMangaUpdate
- Direction
- eu.kanade.tachiyomi.source uses eu.kanade.tachiyomi.source.model, so a change to eu.kanade.tachiyomi.source.model can break eu.kanade.tachiyomi.source, while a change to eu.kanade.tachiyomi.source can't break eu.kanade.tachiyomi.source.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.source uses a module listed above it, which is the healthy direction.
22→11 eu.kanade.tachiyomi.source uses eu.kanade.domain.source.service✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.source uses a type in eu.kanade.domain.source.service.
- The types involved
eu.kanade.tachiyomi.source.SourceExtensionsKt→eu.kanade.domain.source.service.SourcePreferences
- Direction
- eu.kanade.tachiyomi.source uses eu.kanade.domain.source.service, so a change to eu.kanade.domain.source.service can break eu.kanade.tachiyomi.source, while a change to eu.kanade.tachiyomi.source can't break eu.kanade.domain.source.service.
- Position
- Below the diagonal: eu.kanade.tachiyomi.source uses a module listed above it, which is the healthy direction.
22→16 eu.kanade.tachiyomi.source uses tachiyomi.domain.source.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.source uses a type in tachiyomi.domain.source.model.
- The types involved
eu.kanade.tachiyomi.source.AndroidSourceManager→tachiyomi.domain.source.model.StubSource
- Direction
- eu.kanade.tachiyomi.source uses tachiyomi.domain.source.model, so a change to tachiyomi.domain.source.model can break eu.kanade.tachiyomi.source, while a change to eu.kanade.tachiyomi.source can't break tachiyomi.domain.source.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.source uses a module listed above it, which is the healthy direction.
22→17 eu.kanade.tachiyomi.source uses eu.kanade.tachiyomi.extension✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.source uses a type in eu.kanade.tachiyomi.extension.
- The types involved
eu.kanade.tachiyomi.source.AndroidSourceManager→eu.kanade.tachiyomi.extension.ExtensionManager
- Direction
- eu.kanade.tachiyomi.source uses eu.kanade.tachiyomi.extension, so a change to eu.kanade.tachiyomi.extension can break eu.kanade.tachiyomi.source, while a change to eu.kanade.tachiyomi.source can't break eu.kanade.tachiyomi.extension.
- Position
- Below the diagonal: eu.kanade.tachiyomi.source uses a module listed above it, which is the healthy direction.
22→20 eu.kanade.tachiyomi.source uses tachiyomi.domain.source.service✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.source uses a type in tachiyomi.domain.source.service.
- The types involved
eu.kanade.tachiyomi.source.AndroidSourceManager→tachiyomi.domain.source.service.SourceManager
- Direction
- eu.kanade.tachiyomi.source uses tachiyomi.domain.source.service, so a change to tachiyomi.domain.source.service can break eu.kanade.tachiyomi.source, while a change to eu.kanade.tachiyomi.source can't break tachiyomi.domain.source.service.
- Position
- Below the diagonal: eu.kanade.tachiyomi.source uses a module listed above it, which is the healthy direction.
22→34 eu.kanade.tachiyomi.source uses eu.kanade.tachiyomi.data.download part of a loop✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.source uses a type in eu.kanade.tachiyomi.data.download.
- The types involved
eu.kanade.tachiyomi.source.AndroidSourceManager→eu.kanade.tachiyomi.data.download.DownloadManager
- Direction
- eu.kanade.tachiyomi.source uses eu.kanade.tachiyomi.data.download, so a change to eu.kanade.tachiyomi.data.download can break eu.kanade.tachiyomi.source, while a change to eu.kanade.tachiyomi.source can't break eu.kanade.tachiyomi.data.download.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→7 tachiyomi.domain.category.interactor uses tachiyomi.domain.category.model✕
- Connections
- 4 pairs of types, where a type in tachiyomi.domain.category.interactor uses a type in tachiyomi.domain.category.model.
- The types involved
tachiyomi.domain.category.interactor.GetCategories→tachiyomi.domain.category.model.Categorytachiyomi.domain.category.interactor.RenameCategory→tachiyomi.domain.category.model.Categorytachiyomi.domain.category.interactor.ReorderCategory→tachiyomi.domain.category.model.Categorytachiyomi.domain.category.interactor.SetSortModeForCategory→tachiyomi.domain.category.model.Category
- Direction
- tachiyomi.domain.category.interactor uses tachiyomi.domain.category.model, so a change to tachiyomi.domain.category.model can break tachiyomi.domain.category.interactor, while a change to tachiyomi.domain.category.interactor can't break tachiyomi.domain.category.model.
- Position
- Below the diagonal: tachiyomi.domain.category.interactor uses a module listed above it, which is the healthy direction.
23→18 tachiyomi.domain.category.interactor uses tachiyomi.domain.library.service✕
- Connections
- 5 pairs of types, where a type in tachiyomi.domain.category.interactor uses a type in tachiyomi.domain.library.service.
- The types involved
tachiyomi.domain.category.interactor.CreateCategoryWithName→tachiyomi.domain.library.service.LibraryPreferencestachiyomi.domain.category.interactor.DeleteCategory→tachiyomi.domain.library.service.LibraryPreferencestachiyomi.domain.category.interactor.ResetCategoryFlags→tachiyomi.domain.library.service.LibraryPreferencestachiyomi.domain.category.interactor.SetDisplayMode→tachiyomi.domain.library.service.LibraryPreferencestachiyomi.domain.category.interactor.SetSortModeForCategory→tachiyomi.domain.library.service.LibraryPreferences
- Direction
- tachiyomi.domain.category.interactor uses tachiyomi.domain.library.service, so a change to tachiyomi.domain.library.service can break tachiyomi.domain.category.interactor, while a change to tachiyomi.domain.category.interactor can't break tachiyomi.domain.library.service.
- Position
- Below the diagonal: tachiyomi.domain.category.interactor uses a module listed above it, which is the healthy direction.
24→8 tachiyomi.domain.chapter.interactor uses tachiyomi.domain.chapter.model✕
- Connections
- 7 pairs of types, where a type in tachiyomi.domain.chapter.interactor uses a type in tachiyomi.domain.chapter.model.
- The types involved
tachiyomi.domain.chapter.interactor.GetBookmarkedChaptersByMangaId→tachiyomi.domain.chapter.model.Chaptertachiyomi.domain.chapter.interactor.GetChapter→tachiyomi.domain.chapter.model.Chaptertachiyomi.domain.chapter.interactor.GetChapterByUrlAndMangaId→tachiyomi.domain.chapter.model.Chaptertachiyomi.domain.chapter.interactor.GetChapterSummaryByMangaId→tachiyomi.domain.chapter.model.ChapterSummarytachiyomi.domain.chapter.interactor.GetChaptersByMangaId→tachiyomi.domain.chapter.model.Chaptertachiyomi.domain.chapter.interactor.ShouldUpdateDbChapter→tachiyomi.domain.chapter.model.Chaptertachiyomi.domain.chapter.interactor.UpdateChapter→tachiyomi.domain.chapter.model.ChapterUpdate
- Direction
- tachiyomi.domain.chapter.interactor uses tachiyomi.domain.chapter.model, so a change to tachiyomi.domain.chapter.model can break tachiyomi.domain.chapter.interactor, while a change to tachiyomi.domain.chapter.interactor can't break tachiyomi.domain.chapter.model.
- Position
- Below the diagonal: tachiyomi.domain.chapter.interactor uses a module listed above it, which is the healthy direction.
24→15 tachiyomi.domain.chapter.interactor uses tachiyomi.domain.manga.model✕
- Connections
- 1 pair of types, where a type in tachiyomi.domain.chapter.interactor uses a type in tachiyomi.domain.manga.model.
- The types involved
tachiyomi.domain.chapter.interactor.SetMangaDefaultChapterFlags→tachiyomi.domain.manga.model.Manga
- Direction
- tachiyomi.domain.chapter.interactor uses tachiyomi.domain.manga.model, so a change to tachiyomi.domain.manga.model can break tachiyomi.domain.chapter.interactor, while a change to tachiyomi.domain.chapter.interactor can't break tachiyomi.domain.manga.model.
- Position
- Below the diagonal: tachiyomi.domain.chapter.interactor uses a module listed above it, which is the healthy direction.
24→18 tachiyomi.domain.chapter.interactor uses tachiyomi.domain.library.service✕
- Connections
- 1 pair of types, where a type in tachiyomi.domain.chapter.interactor uses a type in tachiyomi.domain.library.service.
- The types involved
tachiyomi.domain.chapter.interactor.SetMangaDefaultChapterFlags→tachiyomi.domain.library.service.LibraryPreferences
- Direction
- tachiyomi.domain.chapter.interactor uses tachiyomi.domain.library.service, so a change to tachiyomi.domain.library.service can break tachiyomi.domain.chapter.interactor, while a change to tachiyomi.domain.chapter.interactor can't break tachiyomi.domain.library.service.
- Position
- Below the diagonal: tachiyomi.domain.chapter.interactor uses a module listed above it, which is the healthy direction.
24→19 tachiyomi.domain.chapter.interactor uses tachiyomi.domain.manga.interactor✕
- Connections
- 2 pairs of types, where a type in tachiyomi.domain.chapter.interactor uses a type in tachiyomi.domain.manga.interactor.
- The types involved
tachiyomi.domain.chapter.interactor.SetMangaDefaultChapterFlags→tachiyomi.domain.manga.interactor.GetFavoritestachiyomi.domain.chapter.interactor.SetMangaDefaultChapterFlags→tachiyomi.domain.manga.interactor.SetMangaChapterFlags
- Direction
- tachiyomi.domain.chapter.interactor uses tachiyomi.domain.manga.interactor, so a change to tachiyomi.domain.manga.interactor can break tachiyomi.domain.chapter.interactor, while a change to tachiyomi.domain.chapter.interactor can't break tachiyomi.domain.manga.interactor.
- Position
- Below the diagonal: tachiyomi.domain.chapter.interactor uses a module listed above it, which is the healthy direction.
25→5 eu.kanade.presentation.browse uses mihon.domain.extension.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.presentation.browse uses a type in mihon.domain.extension.model.
- The types involved
eu.kanade.presentation.browse.ExtensionsScreenKt→mihon.domain.extension.model.ExtensionStore
- Direction
- eu.kanade.presentation.browse uses mihon.domain.extension.model, so a change to mihon.domain.extension.model can break eu.kanade.presentation.browse, while a change to eu.kanade.presentation.browse can't break mihon.domain.extension.model.
- Position
- Below the diagonal: eu.kanade.presentation.browse uses a module listed above it, which is the healthy direction.
25→13 eu.kanade.presentation.browse uses eu.kanade.tachiyomi.extension.model.Extension✕
- Connections
- 6 pairs of types, where a type in eu.kanade.presentation.browse uses a type in eu.kanade.tachiyomi.extension.model.Extension.
- The types involved
eu.kanade.presentation.browse.ExtensionDetailsScreenKt→eu.kanade.tachiyomi.extension.model.Extension.Installedeu.kanade.presentation.browse.ExtensionDetailsScreenKt→eu.kanade.tachiyomi.extension.model.Extension.Loadedeu.kanade.presentation.browse.ExtensionsScreenKt→eu.kanade.tachiyomi.extension.model.Extension.Availableeu.kanade.presentation.browse.ExtensionsScreenKt→eu.kanade.tachiyomi.extension.model.Extension.Installedeu.kanade.presentation.browse.ExtensionsScreenKt→eu.kanade.tachiyomi.extension.model.Extension.Loadedeu.kanade.presentation.browse.ExtensionsScreenKt→eu.kanade.tachiyomi.extension.model.Extension.NotLoaded
- Direction
- eu.kanade.presentation.browse uses eu.kanade.tachiyomi.extension.model.Extension, so a change to eu.kanade.tachiyomi.extension.model.Extension can break eu.kanade.presentation.browse, while a change to eu.kanade.presentation.browse can't break eu.kanade.tachiyomi.extension.model.Extension.
- Position
- Below the diagonal: eu.kanade.presentation.browse uses a module listed above it, which is the healthy direction.
25→15 eu.kanade.presentation.browse uses tachiyomi.domain.manga.model✕
- Connections
- 3 pairs of types, where a type in eu.kanade.presentation.browse uses a type in tachiyomi.domain.manga.model.
- The types involved
eu.kanade.presentation.browse.BrowseSourceScreenKt→tachiyomi.domain.manga.model.Mangaeu.kanade.presentation.browse.GlobalSearchScreenKt→tachiyomi.domain.manga.model.Mangaeu.kanade.presentation.browse.MigrateSearchScreenKt→tachiyomi.domain.manga.model.Manga
- Direction
- eu.kanade.presentation.browse uses tachiyomi.domain.manga.model, so a change to tachiyomi.domain.manga.model can break eu.kanade.presentation.browse, while a change to eu.kanade.presentation.browse can't break tachiyomi.domain.manga.model.
- Position
- Below the diagonal: eu.kanade.presentation.browse uses a module listed above it, which is the healthy direction.
25→16 eu.kanade.presentation.browse uses tachiyomi.domain.source.model✕
- Connections
- 4 pairs of types, where a type in eu.kanade.presentation.browse uses a type in tachiyomi.domain.source.model.
- The types involved
eu.kanade.presentation.browse.BrowseSourceScreenKt→tachiyomi.domain.source.model.StubSourceeu.kanade.presentation.browse.MigrateSourceScreenKt→tachiyomi.domain.source.model.Sourceeu.kanade.presentation.browse.SourcesFilterScreenKt→tachiyomi.domain.source.model.Sourceeu.kanade.presentation.browse.SourcesScreenKt→tachiyomi.domain.source.model.Source
- Direction
- eu.kanade.presentation.browse uses tachiyomi.domain.source.model, so a change to tachiyomi.domain.source.model can break eu.kanade.presentation.browse, while a change to eu.kanade.presentation.browse can't break tachiyomi.domain.source.model.
- Position
- Below the diagonal: eu.kanade.presentation.browse uses a module listed above it, which is the healthy direction.
25→22 eu.kanade.presentation.browse uses eu.kanade.tachiyomi.source✕
- Connections
- 3 pairs of types, where a type in eu.kanade.presentation.browse uses a type in eu.kanade.tachiyomi.source.
- The types involved
eu.kanade.presentation.browse.BrowseSourceScreenKt→eu.kanade.tachiyomi.source.Sourceeu.kanade.presentation.browse.GlobalSearchScreenKt→eu.kanade.tachiyomi.source.Sourceeu.kanade.presentation.browse.MigrateSearchScreenKt→eu.kanade.tachiyomi.source.Source
- Direction
- eu.kanade.presentation.browse uses eu.kanade.tachiyomi.source, so a change to eu.kanade.tachiyomi.source can break eu.kanade.presentation.browse, while a change to eu.kanade.presentation.browse can't break eu.kanade.tachiyomi.source.
- Position
- Below the diagonal: eu.kanade.presentation.browse uses a module listed above it, which is the healthy direction.
26→2 eu.kanade.tachiyomi.data.track uses eu.kanade.tachiyomi.data.database.models✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.data.track uses a type in eu.kanade.tachiyomi.data.database.models.
- The types involved
eu.kanade.tachiyomi.data.track.BaseTracker→eu.kanade.tachiyomi.data.database.models.Trackeu.kanade.tachiyomi.data.track.Tracker→eu.kanade.tachiyomi.data.database.models.Track
- Direction
- eu.kanade.tachiyomi.data.track uses eu.kanade.tachiyomi.data.database.models, so a change to eu.kanade.tachiyomi.data.database.models can break eu.kanade.tachiyomi.data.track, while a change to eu.kanade.tachiyomi.data.track can't break eu.kanade.tachiyomi.data.database.models.
- Position
- Below the diagonal: eu.kanade.tachiyomi.data.track uses a module listed above it, which is the healthy direction.
26→9 eu.kanade.tachiyomi.data.track uses tachiyomi.domain.track.model✕
- Connections
- 4 pairs of types, where a type in eu.kanade.tachiyomi.data.track uses a type in tachiyomi.domain.track.model.
- The types involved
eu.kanade.tachiyomi.data.track.BaseTracker→tachiyomi.domain.track.model.Trackeu.kanade.tachiyomi.data.track.DeletableTracker→tachiyomi.domain.track.model.Trackeu.kanade.tachiyomi.data.track.EnhancedTracker→tachiyomi.domain.track.model.Trackeu.kanade.tachiyomi.data.track.Tracker→tachiyomi.domain.track.model.Track
- Direction
- eu.kanade.tachiyomi.data.track uses tachiyomi.domain.track.model, so a change to tachiyomi.domain.track.model can break eu.kanade.tachiyomi.data.track, while a change to eu.kanade.tachiyomi.data.track can't break tachiyomi.domain.track.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.data.track uses a module listed above it, which is the healthy direction.
26→12 eu.kanade.tachiyomi.data.track uses eu.kanade.tachiyomi.data.track.model✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.data.track uses a type in eu.kanade.tachiyomi.data.track.model.
- The types involved
eu.kanade.tachiyomi.data.track.EnhancedTracker→eu.kanade.tachiyomi.data.track.model.TrackSearcheu.kanade.tachiyomi.data.track.Tracker→eu.kanade.tachiyomi.data.track.model.TrackSearch
- Direction
- eu.kanade.tachiyomi.data.track uses eu.kanade.tachiyomi.data.track.model, so a change to eu.kanade.tachiyomi.data.track.model can break eu.kanade.tachiyomi.data.track, while a change to eu.kanade.tachiyomi.data.track can't break eu.kanade.tachiyomi.data.track.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.data.track uses a module listed above it, which is the healthy direction.
26→15 eu.kanade.tachiyomi.data.track uses tachiyomi.domain.manga.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.data.track uses a type in tachiyomi.domain.manga.model.
- The types involved
eu.kanade.tachiyomi.data.track.EnhancedTracker→tachiyomi.domain.manga.model.Manga
- Direction
- eu.kanade.tachiyomi.data.track uses tachiyomi.domain.manga.model, so a change to tachiyomi.domain.manga.model can break eu.kanade.tachiyomi.data.track, while a change to eu.kanade.tachiyomi.data.track can't break tachiyomi.domain.manga.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.data.track uses a module listed above it, which is the healthy direction.
26→22 eu.kanade.tachiyomi.data.track uses eu.kanade.tachiyomi.source✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.data.track uses a type in eu.kanade.tachiyomi.source.
- The types involved
eu.kanade.tachiyomi.data.track.EnhancedTracker→eu.kanade.tachiyomi.source.Source
- Direction
- eu.kanade.tachiyomi.data.track uses eu.kanade.tachiyomi.source, so a change to eu.kanade.tachiyomi.source can break eu.kanade.tachiyomi.data.track, while a change to eu.kanade.tachiyomi.data.track can't break eu.kanade.tachiyomi.source.
- Position
- Below the diagonal: eu.kanade.tachiyomi.data.track uses a module listed above it, which is the healthy direction.
26→28 eu.kanade.tachiyomi.data.track uses eu.kanade.domain.track.interactor part of a loop✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.data.track uses a type in eu.kanade.domain.track.interactor.
- The types involved
eu.kanade.tachiyomi.data.track.BaseTracker→eu.kanade.domain.track.interactor.AddTrackseu.kanade.tachiyomi.data.track.TrackerDependencies→eu.kanade.domain.track.interactor.AddTracks
- Direction
- eu.kanade.tachiyomi.data.track uses eu.kanade.domain.track.interactor, so a change to eu.kanade.domain.track.interactor can break eu.kanade.tachiyomi.data.track, while a change to eu.kanade.tachiyomi.data.track can't break eu.kanade.domain.track.interactor.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→4 eu.kanade.tachiyomi.ui.reader.viewer uses eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences✕
- Connections
- 3 pairs of types, where a type in eu.kanade.tachiyomi.ui.reader.viewer uses a type in eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences.
- The types involved
eu.kanade.tachiyomi.ui.reader.viewer.NavigationSettings→eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences.NavigationModeeu.kanade.tachiyomi.ui.reader.viewer.NavigationSettings→eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences.TappingInvertModeeu.kanade.tachiyomi.ui.reader.viewer.ViewerNavigation→eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences.TappingInvertMode
- Direction
- eu.kanade.tachiyomi.ui.reader.viewer uses eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences, so a change to eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences can break eu.kanade.tachiyomi.ui.reader.viewer, while a change to eu.kanade.tachiyomi.ui.reader.viewer can't break eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader.viewer uses a module listed above it, which is the healthy direction.
27→14 eu.kanade.tachiyomi.ui.reader.viewer uses eu.kanade.tachiyomi.ui.reader.model✕
- Connections
- 14 pairs of types, where a type in eu.kanade.tachiyomi.ui.reader.viewer uses a type in eu.kanade.tachiyomi.ui.reader.model.
- The types involved
eu.kanade.tachiyomi.ui.reader.viewer.MissingChaptersKt→eu.kanade.tachiyomi.ui.reader.model.ReaderChaptereu.kanade.tachiyomi.ui.reader.viewer.PageImageProcessingKt→eu.kanade.tachiyomi.ui.reader.model.InsertPageeu.kanade.tachiyomi.ui.reader.viewer.PageImageProcessingKt→eu.kanade.tachiyomi.ui.reader.model.ReaderPageeu.kanade.tachiyomi.ui.reader.viewer.ReaderPageErrorKt→eu.kanade.tachiyomi.ui.reader.model.ReaderPageeu.kanade.tachiyomi.ui.reader.viewer.ReaderPageErrorView→eu.kanade.tachiyomi.ui.reader.model.ReaderPageeu.kanade.tachiyomi.ui.reader.viewer.ReaderTransitionPageKt→eu.kanade.tachiyomi.ui.reader.model.ChapterTransitioneu.kanade.tachiyomi.ui.reader.viewer.ReaderTransitionPageKt→eu.kanade.tachiyomi.ui.reader.model.ReaderChaptereu.kanade.tachiyomi.ui.reader.viewer.ReaderTransitionView→eu.kanade.tachiyomi.ui.reader.model.ChapterTransitioneu.kanade.tachiyomi.ui.reader.viewer.ReaderTransitionView→eu.kanade.tachiyomi.ui.reader.model.ReaderChaptereu.kanade.tachiyomi.ui.reader.viewer.TransitionDownloadStateKt→eu.kanade.tachiyomi.ui.reader.model.ChapterTransitioneu.kanade.tachiyomi.ui.reader.viewer.Viewer→eu.kanade.tachiyomi.ui.reader.model.ReaderPageeu.kanade.tachiyomi.ui.reader.viewer.Viewer→eu.kanade.tachiyomi.ui.reader.model.ViewerChapterseu.kanade.tachiyomi.ui.reader.viewer.ViewerItemsKt→eu.kanade.tachiyomi.ui.reader.model.ReaderPageeu.kanade.tachiyomi.ui.reader.viewer.ViewerItemsKt→eu.kanade.tachiyomi.ui.reader.model.ViewerChapters
- Direction
- eu.kanade.tachiyomi.ui.reader.viewer uses eu.kanade.tachiyomi.ui.reader.model, so a change to eu.kanade.tachiyomi.ui.reader.model can break eu.kanade.tachiyomi.ui.reader.viewer, while a change to eu.kanade.tachiyomi.ui.reader.viewer can't break eu.kanade.tachiyomi.ui.reader.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader.viewer uses a module listed above it, which is the healthy direction.
27→15 eu.kanade.tachiyomi.ui.reader.viewer uses tachiyomi.domain.manga.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.reader.viewer uses a type in tachiyomi.domain.manga.model.
- The types involved
eu.kanade.tachiyomi.ui.reader.viewer.TransitionDownloadStateKt→tachiyomi.domain.manga.model.Manga
- Direction
- eu.kanade.tachiyomi.ui.reader.viewer uses tachiyomi.domain.manga.model, so a change to tachiyomi.domain.manga.model can break eu.kanade.tachiyomi.ui.reader.viewer, while a change to eu.kanade.tachiyomi.ui.reader.viewer can't break tachiyomi.domain.manga.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader.viewer uses a module listed above it, which is the healthy direction.
27→22 eu.kanade.tachiyomi.ui.reader.viewer uses eu.kanade.tachiyomi.source✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.reader.viewer uses a type in eu.kanade.tachiyomi.source.
- The types involved
eu.kanade.tachiyomi.ui.reader.viewer.TransitionDownloadStateKt→eu.kanade.tachiyomi.source.Source
- Direction
- eu.kanade.tachiyomi.ui.reader.viewer uses eu.kanade.tachiyomi.source, so a change to eu.kanade.tachiyomi.source can break eu.kanade.tachiyomi.ui.reader.viewer, while a change to eu.kanade.tachiyomi.ui.reader.viewer can't break eu.kanade.tachiyomi.source.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader.viewer uses a module listed above it, which is the healthy direction.
28→2 eu.kanade.domain.track.interactor uses eu.kanade.tachiyomi.data.database.models✕
- Connections
- 1 pair of types, where a type in eu.kanade.domain.track.interactor uses a type in eu.kanade.tachiyomi.data.database.models.
- The types involved
eu.kanade.domain.track.interactor.AddTracks→eu.kanade.tachiyomi.data.database.models.Track
- Direction
- eu.kanade.domain.track.interactor uses eu.kanade.tachiyomi.data.database.models, so a change to eu.kanade.tachiyomi.data.database.models can break eu.kanade.domain.track.interactor, while a change to eu.kanade.domain.track.interactor can't break eu.kanade.tachiyomi.data.database.models.
- Position
- Below the diagonal: eu.kanade.domain.track.interactor uses a module listed above it, which is the healthy direction.
28→9 eu.kanade.domain.track.interactor uses tachiyomi.domain.track.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.domain.track.interactor uses a type in tachiyomi.domain.track.model.
- The types involved
eu.kanade.domain.track.interactor.SyncChapterProgressWithTrack→tachiyomi.domain.track.model.Track
- Direction
- eu.kanade.domain.track.interactor uses tachiyomi.domain.track.model, so a change to tachiyomi.domain.track.model can break eu.kanade.domain.track.interactor, while a change to eu.kanade.domain.track.interactor can't break tachiyomi.domain.track.model.
- Position
- Below the diagonal: eu.kanade.domain.track.interactor uses a module listed above it, which is the healthy direction.
28→15 eu.kanade.domain.track.interactor uses tachiyomi.domain.manga.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.domain.track.interactor uses a type in tachiyomi.domain.manga.model.
- The types involved
eu.kanade.domain.track.interactor.AddTracks→tachiyomi.domain.manga.model.Manga
- Direction
- eu.kanade.domain.track.interactor uses tachiyomi.domain.manga.model, so a change to tachiyomi.domain.manga.model can break eu.kanade.domain.track.interactor, while a change to eu.kanade.domain.track.interactor can't break tachiyomi.domain.manga.model.
- Position
- Below the diagonal: eu.kanade.domain.track.interactor uses a module listed above it, which is the healthy direction.
28→22 eu.kanade.domain.track.interactor uses eu.kanade.tachiyomi.source✕
- Connections
- 1 pair of types, where a type in eu.kanade.domain.track.interactor uses a type in eu.kanade.tachiyomi.source.
- The types involved
eu.kanade.domain.track.interactor.AddTracks→eu.kanade.tachiyomi.source.Source
- Direction
- eu.kanade.domain.track.interactor uses eu.kanade.tachiyomi.source, so a change to eu.kanade.tachiyomi.source can break eu.kanade.domain.track.interactor, while a change to eu.kanade.domain.track.interactor can't break eu.kanade.tachiyomi.source.
- Position
- Below the diagonal: eu.kanade.domain.track.interactor uses a module listed above it, which is the healthy direction.
28→24 eu.kanade.domain.track.interactor uses tachiyomi.domain.chapter.interactor✕
- Connections
- 3 pairs of types, where a type in eu.kanade.domain.track.interactor uses a type in tachiyomi.domain.chapter.interactor.
- The types involved
eu.kanade.domain.track.interactor.AddTracks→tachiyomi.domain.chapter.interactor.GetChaptersByMangaIdeu.kanade.domain.track.interactor.SyncChapterProgressWithTrack→tachiyomi.domain.chapter.interactor.GetChaptersByMangaIdeu.kanade.domain.track.interactor.SyncChapterProgressWithTrack→tachiyomi.domain.chapter.interactor.UpdateChapter
- Direction
- eu.kanade.domain.track.interactor uses tachiyomi.domain.chapter.interactor, so a change to tachiyomi.domain.chapter.interactor can break eu.kanade.domain.track.interactor, while a change to eu.kanade.domain.track.interactor can't break tachiyomi.domain.chapter.interactor.
- Position
- Below the diagonal: eu.kanade.domain.track.interactor uses a module listed above it, which is the healthy direction.
28→26 eu.kanade.domain.track.interactor uses eu.kanade.tachiyomi.data.track✕
- Connections
- 6 pairs of types, where a type in eu.kanade.domain.track.interactor uses a type in eu.kanade.tachiyomi.data.track.
- The types involved
eu.kanade.domain.track.interactor.AddTracks→eu.kanade.tachiyomi.data.track.Trackereu.kanade.domain.track.interactor.AddTracks→eu.kanade.tachiyomi.data.track.TrackerManagereu.kanade.domain.track.interactor.RefreshTracks→eu.kanade.tachiyomi.data.track.Trackereu.kanade.domain.track.interactor.RefreshTracks→eu.kanade.tachiyomi.data.track.TrackerManagereu.kanade.domain.track.interactor.SyncChapterProgressWithTrack→eu.kanade.tachiyomi.data.track.Trackereu.kanade.domain.track.interactor.TrackChapter→eu.kanade.tachiyomi.data.track.TrackerManager
- Direction
- eu.kanade.domain.track.interactor uses eu.kanade.tachiyomi.data.track, so a change to eu.kanade.tachiyomi.data.track can break eu.kanade.domain.track.interactor, while a change to eu.kanade.domain.track.interactor can't break eu.kanade.tachiyomi.data.track.
- Position
- Below the diagonal: eu.kanade.domain.track.interactor uses a module listed above it, which is the healthy direction.
29→4 eu.kanade.tachiyomi.ui.reader.setting uses eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences✕
- Connections
- 7 pairs of types, where a type in eu.kanade.tachiyomi.ui.reader.setting uses a type in eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences.
- The types involved
eu.kanade.tachiyomi.ui.reader.setting.GeneralSettings→eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences.ReaderThemeeu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences→eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences.CutoutModeeu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences→eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences.DualPageVieweu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences→eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences.FlashColoreu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences→eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences.ReaderHideThresholdeu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences→eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences.TappingInvertModeeu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences→eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences.TransitionAnimation
- Direction
- eu.kanade.tachiyomi.ui.reader.setting uses eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences, so a change to eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences can break eu.kanade.tachiyomi.ui.reader.setting, while a change to eu.kanade.tachiyomi.ui.reader.setting can't break eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader.setting uses a module listed above it, which is the healthy direction.
29→6 eu.kanade.tachiyomi.ui.reader.setting uses tachiyomi.core.common.preference✕
- Connections
- 3 pairs of types, where a type in eu.kanade.tachiyomi.ui.reader.setting uses a type in tachiyomi.core.common.preference.
- The types involved
eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences→tachiyomi.core.common.preference.Preferenceeu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences→tachiyomi.core.common.preference.PreferenceStoreeu.kanade.tachiyomi.ui.reader.setting.ReaderSettingsViewModel→tachiyomi.core.common.preference.Preference
- Direction
- eu.kanade.tachiyomi.ui.reader.setting uses tachiyomi.core.common.preference, so a change to tachiyomi.core.common.preference can break eu.kanade.tachiyomi.ui.reader.setting, while a change to eu.kanade.tachiyomi.ui.reader.setting can't break tachiyomi.core.common.preference.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader.setting uses a module listed above it, which is the healthy direction.
29→10 eu.kanade.tachiyomi.ui.reader.setting uses eu.kanade.domain.base✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.reader.setting uses a type in eu.kanade.domain.base.
- The types involved
eu.kanade.tachiyomi.ui.reader.setting.ReaderSettingsViewModel→eu.kanade.domain.base.BasePreferences
- Direction
- eu.kanade.tachiyomi.ui.reader.setting uses eu.kanade.domain.base, so a change to eu.kanade.domain.base can break eu.kanade.tachiyomi.ui.reader.setting, while a change to eu.kanade.tachiyomi.ui.reader.setting can't break eu.kanade.domain.base.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader.setting uses a module listed above it, which is the healthy direction.
29→15 eu.kanade.tachiyomi.ui.reader.setting uses tachiyomi.domain.manga.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.reader.setting uses a type in tachiyomi.domain.manga.model.
- The types involved
eu.kanade.tachiyomi.ui.reader.setting.ReaderSettingsViewModel→tachiyomi.domain.manga.model.Manga
- Direction
- eu.kanade.tachiyomi.ui.reader.setting uses tachiyomi.domain.manga.model, so a change to tachiyomi.domain.manga.model can break eu.kanade.tachiyomi.ui.reader.setting, while a change to eu.kanade.tachiyomi.ui.reader.setting can't break tachiyomi.domain.manga.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader.setting uses a module listed above it, which is the healthy direction.
29→27 eu.kanade.tachiyomi.ui.reader.setting uses eu.kanade.tachiyomi.ui.reader.viewer✕
- Connections
- 3 pairs of types, where a type in eu.kanade.tachiyomi.ui.reader.setting uses a type in eu.kanade.tachiyomi.ui.reader.viewer.
- The types involved
eu.kanade.tachiyomi.ui.reader.setting.ReaderSettingsViewModel→eu.kanade.tachiyomi.ui.reader.viewer.LongStripSettingseu.kanade.tachiyomi.ui.reader.setting.ReaderSettingsViewModel→eu.kanade.tachiyomi.ui.reader.viewer.PagedSettingseu.kanade.tachiyomi.ui.reader.setting.ReaderSettingsViewModel→eu.kanade.tachiyomi.ui.reader.viewer.ViewerNavigation
- Direction
- eu.kanade.tachiyomi.ui.reader.setting uses eu.kanade.tachiyomi.ui.reader.viewer, so a change to eu.kanade.tachiyomi.ui.reader.viewer can break eu.kanade.tachiyomi.ui.reader.setting, while a change to eu.kanade.tachiyomi.ui.reader.setting can't break eu.kanade.tachiyomi.ui.reader.viewer.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader.setting uses a module listed above it, which is the healthy direction.
29→32 eu.kanade.tachiyomi.ui.reader.setting uses eu.kanade.tachiyomi.ui.reader part of a loop✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.reader.setting uses a type in eu.kanade.tachiyomi.ui.reader.
- The types involved
eu.kanade.tachiyomi.ui.reader.setting.ReaderSettingsViewModel→eu.kanade.tachiyomi.ui.reader.ReaderViewModel
- Direction
- eu.kanade.tachiyomi.ui.reader.setting uses eu.kanade.tachiyomi.ui.reader, so a change to eu.kanade.tachiyomi.ui.reader can break eu.kanade.tachiyomi.ui.reader.setting, while a change to eu.kanade.tachiyomi.ui.reader.setting can't break eu.kanade.tachiyomi.ui.reader.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→1 eu.kanade.presentation.more.settings.screen uses eu.kanade.presentation.util✕
- Connections
- 2 pairs of types, where a type in eu.kanade.presentation.more.settings.screen uses a type in eu.kanade.presentation.util.
- The types involved
eu.kanade.presentation.more.settings.screen.SettingsMainScreen→eu.kanade.presentation.util.Screeneu.kanade.presentation.more.settings.screen.SettingsSearchScreen→eu.kanade.presentation.util.Screen
- Direction
- eu.kanade.presentation.more.settings.screen uses eu.kanade.presentation.util, so a change to eu.kanade.presentation.util can break eu.kanade.presentation.more.settings.screen, while a change to eu.kanade.presentation.more.settings.screen can't break eu.kanade.presentation.util.
- Position
- Below the diagonal: eu.kanade.presentation.more.settings.screen uses a module listed above it, which is the healthy direction.
30→6 eu.kanade.presentation.more.settings.screen uses tachiyomi.core.common.preference✕
- Connections
- 1 pair of types, where a type in eu.kanade.presentation.more.settings.screen uses a type in tachiyomi.core.common.preference.
- The types involved
eu.kanade.presentation.more.settings.screen.SettingsDataScreen→tachiyomi.core.common.preference.Preference
- Direction
- eu.kanade.presentation.more.settings.screen uses tachiyomi.core.common.preference, so a change to tachiyomi.core.common.preference can break eu.kanade.presentation.more.settings.screen, while a change to eu.kanade.presentation.more.settings.screen can't break tachiyomi.core.common.preference.
- Position
- Below the diagonal: eu.kanade.presentation.more.settings.screen uses a module listed above it, which is the healthy direction.
30→7 eu.kanade.presentation.more.settings.screen uses tachiyomi.domain.category.model✕
- Connections
- 3 pairs of types, where a type in eu.kanade.presentation.more.settings.screen uses a type in tachiyomi.domain.category.model.
- The types involved
eu.kanade.presentation.more.settings.screen.CommonsKt→tachiyomi.domain.category.model.Categoryeu.kanade.presentation.more.settings.screen.SettingsDownloadScreen→tachiyomi.domain.category.model.Categoryeu.kanade.presentation.more.settings.screen.SettingsLibraryScreen→tachiyomi.domain.category.model.Category
- Direction
- eu.kanade.presentation.more.settings.screen uses tachiyomi.domain.category.model, so a change to tachiyomi.domain.category.model can break eu.kanade.presentation.more.settings.screen, while a change to eu.kanade.presentation.more.settings.screen can't break tachiyomi.domain.category.model.
- Position
- Below the diagonal: eu.kanade.presentation.more.settings.screen uses a module listed above it, which is the healthy direction.
30→10 eu.kanade.presentation.more.settings.screen uses eu.kanade.domain.base✕
- Connections
- 1 pair of types, where a type in eu.kanade.presentation.more.settings.screen uses a type in eu.kanade.domain.base.
- The types involved
eu.kanade.presentation.more.settings.screen.SettingsAdvancedScreen→eu.kanade.domain.base.BasePreferences
- Direction
- eu.kanade.presentation.more.settings.screen uses eu.kanade.domain.base, so a change to eu.kanade.domain.base can break eu.kanade.presentation.more.settings.screen, while a change to eu.kanade.presentation.more.settings.screen can't break eu.kanade.domain.base.
- Position
- Below the diagonal: eu.kanade.presentation.more.settings.screen uses a module listed above it, which is the healthy direction.
30→18 eu.kanade.presentation.more.settings.screen uses tachiyomi.domain.library.service✕
- Connections
- 2 pairs of types, where a type in eu.kanade.presentation.more.settings.screen uses a type in tachiyomi.domain.library.service.
- The types involved
eu.kanade.presentation.more.settings.screen.SettingsAdvancedScreen→tachiyomi.domain.library.service.LibraryPreferenceseu.kanade.presentation.more.settings.screen.SettingsLibraryScreen→tachiyomi.domain.library.service.LibraryPreferences
- Direction
- eu.kanade.presentation.more.settings.screen uses tachiyomi.domain.library.service, so a change to tachiyomi.domain.library.service can break eu.kanade.presentation.more.settings.screen, while a change to eu.kanade.presentation.more.settings.screen can't break tachiyomi.domain.library.service.
- Position
- Below the diagonal: eu.kanade.presentation.more.settings.screen uses a module listed above it, which is the healthy direction.
30→26 eu.kanade.presentation.more.settings.screen uses eu.kanade.tachiyomi.data.track✕
- Connections
- 3 pairs of types, where a type in eu.kanade.presentation.more.settings.screen uses a type in eu.kanade.tachiyomi.data.track.
- The types involved
eu.kanade.presentation.more.settings.screen.LoginDialog→eu.kanade.tachiyomi.data.track.Trackereu.kanade.presentation.more.settings.screen.LogoutDialog→eu.kanade.tachiyomi.data.track.Trackereu.kanade.presentation.more.settings.screen.SettingsTrackingScreen→eu.kanade.tachiyomi.data.track.Tracker
- Direction
- eu.kanade.presentation.more.settings.screen uses eu.kanade.tachiyomi.data.track, so a change to eu.kanade.tachiyomi.data.track can break eu.kanade.presentation.more.settings.screen, while a change to eu.kanade.presentation.more.settings.screen can't break eu.kanade.tachiyomi.data.track.
- Position
- Below the diagonal: eu.kanade.presentation.more.settings.screen uses a module listed above it, which is the healthy direction.
30→29 eu.kanade.presentation.more.settings.screen uses eu.kanade.tachiyomi.ui.reader.setting✕
- Connections
- 1 pair of types, where a type in eu.kanade.presentation.more.settings.screen uses a type in eu.kanade.tachiyomi.ui.reader.setting.
- The types involved
eu.kanade.presentation.more.settings.screen.SettingsReaderScreen→eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences
- Direction
- eu.kanade.presentation.more.settings.screen uses eu.kanade.tachiyomi.ui.reader.setting, so a change to eu.kanade.tachiyomi.ui.reader.setting can break eu.kanade.presentation.more.settings.screen, while a change to eu.kanade.presentation.more.settings.screen can't break eu.kanade.tachiyomi.ui.reader.setting.
- Position
- Below the diagonal: eu.kanade.presentation.more.settings.screen uses a module listed above it, which is the healthy direction.
31→1 eu.kanade.tachiyomi.ui.browse.source.browse uses eu.kanade.presentation.util✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.ui.browse.source.browse uses a type in eu.kanade.presentation.util.
- The types involved
eu.kanade.tachiyomi.ui.browse.source.browse.BrowseSourceScreen→eu.kanade.presentation.util.AssistContentScreeneu.kanade.tachiyomi.ui.browse.source.browse.BrowseSourceScreen→eu.kanade.presentation.util.Screen
- Direction
- eu.kanade.tachiyomi.ui.browse.source.browse uses eu.kanade.presentation.util, so a change to eu.kanade.presentation.util can break eu.kanade.tachiyomi.ui.browse.source.browse, while a change to eu.kanade.tachiyomi.ui.browse.source.browse can't break eu.kanade.presentation.util.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.browse.source.browse uses a module listed above it, which is the healthy direction.
31→3 eu.kanade.tachiyomi.ui.browse.source.browse uses eu.kanade.tachiyomi.source.model✕
- Connections
- 3 pairs of types, where a type in eu.kanade.tachiyomi.ui.browse.source.browse uses a type in eu.kanade.tachiyomi.source.model.
- The types involved
eu.kanade.tachiyomi.ui.browse.source.browse.BrowseSourceViewModel→eu.kanade.tachiyomi.source.model.FilterListeu.kanade.tachiyomi.ui.browse.source.browse.SourceFilterDialogKt→eu.kanade.tachiyomi.source.model.Filtereu.kanade.tachiyomi.ui.browse.source.browse.SourceFilterDialogKt→eu.kanade.tachiyomi.source.model.FilterList
- Direction
- eu.kanade.tachiyomi.ui.browse.source.browse uses eu.kanade.tachiyomi.source.model, so a change to eu.kanade.tachiyomi.source.model can break eu.kanade.tachiyomi.ui.browse.source.browse, while a change to eu.kanade.tachiyomi.ui.browse.source.browse can't break eu.kanade.tachiyomi.source.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.browse.source.browse uses a module listed above it, which is the healthy direction.
31→6 eu.kanade.tachiyomi.ui.browse.source.browse uses tachiyomi.core.common.preference✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.browse.source.browse uses a type in tachiyomi.core.common.preference.
- The types involved
eu.kanade.tachiyomi.ui.browse.source.browse.SourceFilterDialogKt→tachiyomi.core.common.preference.TriState
- Direction
- eu.kanade.tachiyomi.ui.browse.source.browse uses tachiyomi.core.common.preference, so a change to tachiyomi.core.common.preference can break eu.kanade.tachiyomi.ui.browse.source.browse, while a change to eu.kanade.tachiyomi.ui.browse.source.browse can't break tachiyomi.core.common.preference.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.browse.source.browse uses a module listed above it, which is the healthy direction.
31→7 eu.kanade.tachiyomi.ui.browse.source.browse uses tachiyomi.domain.category.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.browse.source.browse uses a type in tachiyomi.domain.category.model.
- The types involved
eu.kanade.tachiyomi.ui.browse.source.browse.BrowseSourceViewModel→tachiyomi.domain.category.model.Category
- Direction
- eu.kanade.tachiyomi.ui.browse.source.browse uses tachiyomi.domain.category.model, so a change to tachiyomi.domain.category.model can break eu.kanade.tachiyomi.ui.browse.source.browse, while a change to eu.kanade.tachiyomi.ui.browse.source.browse can't break tachiyomi.domain.category.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.browse.source.browse uses a module listed above it, which is the healthy direction.
31→11 eu.kanade.tachiyomi.ui.browse.source.browse uses eu.kanade.domain.source.service✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.browse.source.browse uses a type in eu.kanade.domain.source.service.
- The types involved
eu.kanade.tachiyomi.ui.browse.source.browse.BrowseSourceViewModel→eu.kanade.domain.source.service.SourcePreferences
- Direction
- eu.kanade.tachiyomi.ui.browse.source.browse uses eu.kanade.domain.source.service, so a change to eu.kanade.domain.source.service can break eu.kanade.tachiyomi.ui.browse.source.browse, while a change to eu.kanade.tachiyomi.ui.browse.source.browse can't break eu.kanade.domain.source.service.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.browse.source.browse uses a module listed above it, which is the healthy direction.
31→15 eu.kanade.tachiyomi.ui.browse.source.browse uses tachiyomi.domain.manga.model✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.ui.browse.source.browse uses a type in tachiyomi.domain.manga.model.
- The types involved
eu.kanade.tachiyomi.ui.browse.source.browse.BrowseSourceViewModel→tachiyomi.domain.manga.model.Mangaeu.kanade.tachiyomi.ui.browse.source.browse.BrowseSourceViewModel→tachiyomi.domain.manga.model.MangaWithChapterCount
- Direction
- eu.kanade.tachiyomi.ui.browse.source.browse uses tachiyomi.domain.manga.model, so a change to tachiyomi.domain.manga.model can break eu.kanade.tachiyomi.ui.browse.source.browse, while a change to eu.kanade.tachiyomi.ui.browse.source.browse can't break tachiyomi.domain.manga.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.browse.source.browse uses a module listed above it, which is the healthy direction.
31→18 eu.kanade.tachiyomi.ui.browse.source.browse uses tachiyomi.domain.library.service✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.browse.source.browse uses a type in tachiyomi.domain.library.service.
- The types involved
eu.kanade.tachiyomi.ui.browse.source.browse.BrowseSourceViewModel→tachiyomi.domain.library.service.LibraryPreferences
- Direction
- eu.kanade.tachiyomi.ui.browse.source.browse uses tachiyomi.domain.library.service, so a change to tachiyomi.domain.library.service can break eu.kanade.tachiyomi.ui.browse.source.browse, while a change to eu.kanade.tachiyomi.ui.browse.source.browse can't break tachiyomi.domain.library.service.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.browse.source.browse uses a module listed above it, which is the healthy direction.
31→19 eu.kanade.tachiyomi.ui.browse.source.browse uses tachiyomi.domain.manga.interactor✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.ui.browse.source.browse uses a type in tachiyomi.domain.manga.interactor.
- The types involved
eu.kanade.tachiyomi.ui.browse.source.browse.BrowseSourceViewModel→tachiyomi.domain.manga.interactor.GetDuplicateLibraryMangaeu.kanade.tachiyomi.ui.browse.source.browse.BrowseSourceViewModel→tachiyomi.domain.manga.interactor.GetManga
- Direction
- eu.kanade.tachiyomi.ui.browse.source.browse uses tachiyomi.domain.manga.interactor, so a change to tachiyomi.domain.manga.interactor can break eu.kanade.tachiyomi.ui.browse.source.browse, while a change to eu.kanade.tachiyomi.ui.browse.source.browse can't break tachiyomi.domain.manga.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.browse.source.browse uses a module listed above it, which is the healthy direction.
31→20 eu.kanade.tachiyomi.ui.browse.source.browse uses tachiyomi.domain.source.service✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.browse.source.browse uses a type in tachiyomi.domain.source.service.
- The types involved
eu.kanade.tachiyomi.ui.browse.source.browse.BrowseSourceViewModel→tachiyomi.domain.source.service.SourceManager
- Direction
- eu.kanade.tachiyomi.ui.browse.source.browse uses tachiyomi.domain.source.service, so a change to tachiyomi.domain.source.service can break eu.kanade.tachiyomi.ui.browse.source.browse, while a change to eu.kanade.tachiyomi.ui.browse.source.browse can't break tachiyomi.domain.source.service.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.browse.source.browse uses a module listed above it, which is the healthy direction.
31→22 eu.kanade.tachiyomi.ui.browse.source.browse uses eu.kanade.tachiyomi.source✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.browse.source.browse uses a type in eu.kanade.tachiyomi.source.
- The types involved
eu.kanade.tachiyomi.ui.browse.source.browse.BrowseSourceViewModel→eu.kanade.tachiyomi.source.Source
- Direction
- eu.kanade.tachiyomi.ui.browse.source.browse uses eu.kanade.tachiyomi.source, so a change to eu.kanade.tachiyomi.source can break eu.kanade.tachiyomi.ui.browse.source.browse, while a change to eu.kanade.tachiyomi.ui.browse.source.browse can't break eu.kanade.tachiyomi.source.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.browse.source.browse uses a module listed above it, which is the healthy direction.
31→23 eu.kanade.tachiyomi.ui.browse.source.browse uses tachiyomi.domain.category.interactor✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.ui.browse.source.browse uses a type in tachiyomi.domain.category.interactor.
- The types involved
eu.kanade.tachiyomi.ui.browse.source.browse.BrowseSourceViewModel→tachiyomi.domain.category.interactor.GetCategorieseu.kanade.tachiyomi.ui.browse.source.browse.BrowseSourceViewModel→tachiyomi.domain.category.interactor.SetMangaCategories
- Direction
- eu.kanade.tachiyomi.ui.browse.source.browse uses tachiyomi.domain.category.interactor, so a change to tachiyomi.domain.category.interactor can break eu.kanade.tachiyomi.ui.browse.source.browse, while a change to eu.kanade.tachiyomi.ui.browse.source.browse can't break tachiyomi.domain.category.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.browse.source.browse uses a module listed above it, which is the healthy direction.
31→24 eu.kanade.tachiyomi.ui.browse.source.browse uses tachiyomi.domain.chapter.interactor✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.browse.source.browse uses a type in tachiyomi.domain.chapter.interactor.
- The types involved
eu.kanade.tachiyomi.ui.browse.source.browse.BrowseSourceViewModel→tachiyomi.domain.chapter.interactor.SetMangaDefaultChapterFlags
- Direction
- eu.kanade.tachiyomi.ui.browse.source.browse uses tachiyomi.domain.chapter.interactor, so a change to tachiyomi.domain.chapter.interactor can break eu.kanade.tachiyomi.ui.browse.source.browse, while a change to eu.kanade.tachiyomi.ui.browse.source.browse can't break tachiyomi.domain.chapter.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.browse.source.browse uses a module listed above it, which is the healthy direction.
31→28 eu.kanade.tachiyomi.ui.browse.source.browse uses eu.kanade.domain.track.interactor✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.browse.source.browse uses a type in eu.kanade.domain.track.interactor.
- The types involved
eu.kanade.tachiyomi.ui.browse.source.browse.BrowseSourceViewModel→eu.kanade.domain.track.interactor.AddTracks
- Direction
- eu.kanade.tachiyomi.ui.browse.source.browse uses eu.kanade.domain.track.interactor, so a change to eu.kanade.domain.track.interactor can break eu.kanade.tachiyomi.ui.browse.source.browse, while a change to eu.kanade.tachiyomi.ui.browse.source.browse can't break eu.kanade.domain.track.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.browse.source.browse uses a module listed above it, which is the healthy direction.
32→3 eu.kanade.tachiyomi.ui.reader uses eu.kanade.tachiyomi.source.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.reader uses a type in eu.kanade.tachiyomi.source.model.
- The types involved
eu.kanade.tachiyomi.ui.reader.ReaderViewModel→eu.kanade.tachiyomi.source.model.Page
- Direction
- eu.kanade.tachiyomi.ui.reader uses eu.kanade.tachiyomi.source.model, so a change to eu.kanade.tachiyomi.source.model can break eu.kanade.tachiyomi.ui.reader, while a change to eu.kanade.tachiyomi.ui.reader can't break eu.kanade.tachiyomi.source.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader uses a module listed above it, which is the healthy direction.
32→8 eu.kanade.tachiyomi.ui.reader uses tachiyomi.domain.chapter.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.reader uses a type in tachiyomi.domain.chapter.model.
- The types involved
eu.kanade.tachiyomi.ui.reader.ReaderViewModel→tachiyomi.domain.chapter.model.Chapter
- Direction
- eu.kanade.tachiyomi.ui.reader uses tachiyomi.domain.chapter.model, so a change to tachiyomi.domain.chapter.model can break eu.kanade.tachiyomi.ui.reader, while a change to eu.kanade.tachiyomi.ui.reader can't break tachiyomi.domain.chapter.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader uses a module listed above it, which is the healthy direction.
32→10 eu.kanade.tachiyomi.ui.reader uses eu.kanade.domain.base✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.ui.reader uses a type in eu.kanade.domain.base.
- The types involved
eu.kanade.tachiyomi.ui.reader.ReaderActivity→eu.kanade.domain.base.BasePreferenceseu.kanade.tachiyomi.ui.reader.ReaderViewModel→eu.kanade.domain.base.BasePreferences
- Direction
- eu.kanade.tachiyomi.ui.reader uses eu.kanade.domain.base, so a change to eu.kanade.domain.base can break eu.kanade.tachiyomi.ui.reader, while a change to eu.kanade.tachiyomi.ui.reader can't break eu.kanade.domain.base.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader uses a module listed above it, which is the healthy direction.
32→14 eu.kanade.tachiyomi.ui.reader uses eu.kanade.tachiyomi.ui.reader.model✕
- Connections
- 6 pairs of types, where a type in eu.kanade.tachiyomi.ui.reader uses a type in eu.kanade.tachiyomi.ui.reader.model.
- The types involved
eu.kanade.tachiyomi.ui.reader.ReaderActivity→eu.kanade.tachiyomi.ui.reader.model.ReaderChaptereu.kanade.tachiyomi.ui.reader.ReaderActivity→eu.kanade.tachiyomi.ui.reader.model.ReaderPageeu.kanade.tachiyomi.ui.reader.ReaderActivity→eu.kanade.tachiyomi.ui.reader.model.ViewerChapterseu.kanade.tachiyomi.ui.reader.ReaderViewModel→eu.kanade.tachiyomi.ui.reader.model.ReaderChaptereu.kanade.tachiyomi.ui.reader.ReaderViewModel→eu.kanade.tachiyomi.ui.reader.model.ReaderPageeu.kanade.tachiyomi.ui.reader.ReaderViewModel→eu.kanade.tachiyomi.ui.reader.model.ViewerChapters
- Direction
- eu.kanade.tachiyomi.ui.reader uses eu.kanade.tachiyomi.ui.reader.model, so a change to eu.kanade.tachiyomi.ui.reader.model can break eu.kanade.tachiyomi.ui.reader, while a change to eu.kanade.tachiyomi.ui.reader can't break eu.kanade.tachiyomi.ui.reader.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader uses a module listed above it, which is the healthy direction.
32→15 eu.kanade.tachiyomi.ui.reader uses tachiyomi.domain.manga.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.reader uses a type in tachiyomi.domain.manga.model.
- The types involved
eu.kanade.tachiyomi.ui.reader.ReaderViewModel→tachiyomi.domain.manga.model.Manga
- Direction
- eu.kanade.tachiyomi.ui.reader uses tachiyomi.domain.manga.model, so a change to tachiyomi.domain.manga.model can break eu.kanade.tachiyomi.ui.reader, while a change to eu.kanade.tachiyomi.ui.reader can't break tachiyomi.domain.manga.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader uses a module listed above it, which is the healthy direction.
32→18 eu.kanade.tachiyomi.ui.reader uses tachiyomi.domain.library.service✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.reader uses a type in tachiyomi.domain.library.service.
- The types involved
eu.kanade.tachiyomi.ui.reader.ReaderViewModel→tachiyomi.domain.library.service.LibraryPreferences
- Direction
- eu.kanade.tachiyomi.ui.reader uses tachiyomi.domain.library.service, so a change to tachiyomi.domain.library.service can break eu.kanade.tachiyomi.ui.reader, while a change to eu.kanade.tachiyomi.ui.reader can't break tachiyomi.domain.library.service.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader uses a module listed above it, which is the healthy direction.
32→19 eu.kanade.tachiyomi.ui.reader uses tachiyomi.domain.manga.interactor✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.reader uses a type in tachiyomi.domain.manga.interactor.
- The types involved
eu.kanade.tachiyomi.ui.reader.ReaderViewModel→tachiyomi.domain.manga.interactor.GetManga
- Direction
- eu.kanade.tachiyomi.ui.reader uses tachiyomi.domain.manga.interactor, so a change to tachiyomi.domain.manga.interactor can break eu.kanade.tachiyomi.ui.reader, while a change to eu.kanade.tachiyomi.ui.reader can't break tachiyomi.domain.manga.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader uses a module listed above it, which is the healthy direction.
32→20 eu.kanade.tachiyomi.ui.reader uses tachiyomi.domain.source.service✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.reader uses a type in tachiyomi.domain.source.service.
- The types involved
eu.kanade.tachiyomi.ui.reader.ReaderViewModel→tachiyomi.domain.source.service.SourceManager
- Direction
- eu.kanade.tachiyomi.ui.reader uses tachiyomi.domain.source.service, so a change to tachiyomi.domain.source.service can break eu.kanade.tachiyomi.ui.reader, while a change to eu.kanade.tachiyomi.ui.reader can't break tachiyomi.domain.source.service.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader uses a module listed above it, which is the healthy direction.
32→22 eu.kanade.tachiyomi.ui.reader uses eu.kanade.tachiyomi.source✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.reader uses a type in eu.kanade.tachiyomi.source.
- The types involved
eu.kanade.tachiyomi.ui.reader.ReaderViewModel→eu.kanade.tachiyomi.source.Source
- Direction
- eu.kanade.tachiyomi.ui.reader uses eu.kanade.tachiyomi.source, so a change to eu.kanade.tachiyomi.source can break eu.kanade.tachiyomi.ui.reader, while a change to eu.kanade.tachiyomi.ui.reader can't break eu.kanade.tachiyomi.source.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader uses a module listed above it, which is the healthy direction.
32→24 eu.kanade.tachiyomi.ui.reader uses tachiyomi.domain.chapter.interactor✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.ui.reader uses a type in tachiyomi.domain.chapter.interactor.
- The types involved
eu.kanade.tachiyomi.ui.reader.ReaderViewModel→tachiyomi.domain.chapter.interactor.GetChaptersByMangaIdeu.kanade.tachiyomi.ui.reader.ReaderViewModel→tachiyomi.domain.chapter.interactor.UpdateChapter
- Direction
- eu.kanade.tachiyomi.ui.reader uses tachiyomi.domain.chapter.interactor, so a change to tachiyomi.domain.chapter.interactor can break eu.kanade.tachiyomi.ui.reader, while a change to eu.kanade.tachiyomi.ui.reader can't break tachiyomi.domain.chapter.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader uses a module listed above it, which is the healthy direction.
32→27 eu.kanade.tachiyomi.ui.reader uses eu.kanade.tachiyomi.ui.reader.viewer✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.reader uses a type in eu.kanade.tachiyomi.ui.reader.viewer.
- The types involved
eu.kanade.tachiyomi.ui.reader.ReaderActivity→eu.kanade.tachiyomi.ui.reader.viewer.Viewer
- Direction
- eu.kanade.tachiyomi.ui.reader uses eu.kanade.tachiyomi.ui.reader.viewer, so a change to eu.kanade.tachiyomi.ui.reader.viewer can break eu.kanade.tachiyomi.ui.reader, while a change to eu.kanade.tachiyomi.ui.reader can't break eu.kanade.tachiyomi.ui.reader.viewer.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader uses a module listed above it, which is the healthy direction.
32→28 eu.kanade.tachiyomi.ui.reader uses eu.kanade.domain.track.interactor✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.reader uses a type in eu.kanade.domain.track.interactor.
- The types involved
eu.kanade.tachiyomi.ui.reader.ReaderViewModel→eu.kanade.domain.track.interactor.TrackChapter
- Direction
- eu.kanade.tachiyomi.ui.reader uses eu.kanade.domain.track.interactor, so a change to eu.kanade.domain.track.interactor can break eu.kanade.tachiyomi.ui.reader, while a change to eu.kanade.tachiyomi.ui.reader can't break eu.kanade.domain.track.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader uses a module listed above it, which is the healthy direction.
32→29 eu.kanade.tachiyomi.ui.reader uses eu.kanade.tachiyomi.ui.reader.setting✕
- Connections
- 4 pairs of types, where a type in eu.kanade.tachiyomi.ui.reader uses a type in eu.kanade.tachiyomi.ui.reader.setting.
- The types involved
eu.kanade.tachiyomi.ui.reader.ReaderActivity→eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferenceseu.kanade.tachiyomi.ui.reader.ReaderViewModel→eu.kanade.tachiyomi.ui.reader.setting.ReaderOrientationeu.kanade.tachiyomi.ui.reader.ReaderViewModel→eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferenceseu.kanade.tachiyomi.ui.reader.ReaderViewModel→eu.kanade.tachiyomi.ui.reader.setting.ReadingMode
- Direction
- eu.kanade.tachiyomi.ui.reader uses eu.kanade.tachiyomi.ui.reader.setting, so a change to eu.kanade.tachiyomi.ui.reader.setting can break eu.kanade.tachiyomi.ui.reader, while a change to eu.kanade.tachiyomi.ui.reader can't break eu.kanade.tachiyomi.ui.reader.setting.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.reader uses a module listed above it, which is the healthy direction.
32→33 eu.kanade.tachiyomi.ui.reader uses mihon.app.di part of a loop✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.reader uses a type in mihon.app.di.
- The types involved
eu.kanade.tachiyomi.ui.reader.ReaderActivity→mihon.app.di.AppGraph
- Direction
- eu.kanade.tachiyomi.ui.reader uses mihon.app.di, so a change to mihon.app.di can break eu.kanade.tachiyomi.ui.reader, while a change to eu.kanade.tachiyomi.ui.reader can't break mihon.app.di.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→34 eu.kanade.tachiyomi.ui.reader uses eu.kanade.tachiyomi.data.download part of a loop✕
- Connections
- 3 pairs of types, where a type in eu.kanade.tachiyomi.ui.reader uses a type in eu.kanade.tachiyomi.data.download.
- The types involved
eu.kanade.tachiyomi.ui.reader.ReaderViewModel→eu.kanade.tachiyomi.data.download.DownloadCacheeu.kanade.tachiyomi.ui.reader.ReaderViewModel→eu.kanade.tachiyomi.data.download.DownloadManagereu.kanade.tachiyomi.ui.reader.ReaderViewModel→eu.kanade.tachiyomi.data.download.DownloadProvider
- Direction
- eu.kanade.tachiyomi.ui.reader uses eu.kanade.tachiyomi.data.download, so a change to eu.kanade.tachiyomi.data.download can break eu.kanade.tachiyomi.ui.reader, while a change to eu.kanade.tachiyomi.ui.reader can't break eu.kanade.tachiyomi.data.download.
- 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.
33→10 mihon.app.di uses eu.kanade.domain.base✕
- Connections
- 1 pair of types, where a type in mihon.app.di uses a type in eu.kanade.domain.base.
- The types involved
mihon.app.di.AppGraph→eu.kanade.domain.base.BasePreferences
- Direction
- mihon.app.di uses eu.kanade.domain.base, so a change to eu.kanade.domain.base can break mihon.app.di, while a change to mihon.app.di can't break eu.kanade.domain.base.
- Position
- Below the diagonal: mihon.app.di uses a module listed above it, which is the healthy direction.
33→11 mihon.app.di uses eu.kanade.domain.source.service✕
- Connections
- 1 pair of types, where a type in mihon.app.di uses a type in eu.kanade.domain.source.service.
- The types involved
mihon.app.di.AppGraph→eu.kanade.domain.source.service.SourcePreferences
- Direction
- mihon.app.di uses eu.kanade.domain.source.service, so a change to eu.kanade.domain.source.service can break mihon.app.di, while a change to mihon.app.di can't break eu.kanade.domain.source.service.
- Position
- Below the diagonal: mihon.app.di uses a module listed above it, which is the healthy direction.
33→17 mihon.app.di uses eu.kanade.tachiyomi.extension✕
- Connections
- 1 pair of types, where a type in mihon.app.di uses a type in eu.kanade.tachiyomi.extension.
- The types involved
mihon.app.di.AppGraph→eu.kanade.tachiyomi.extension.ExtensionManager
- Direction
- mihon.app.di uses eu.kanade.tachiyomi.extension, so a change to eu.kanade.tachiyomi.extension can break mihon.app.di, while a change to mihon.app.di can't break eu.kanade.tachiyomi.extension.
- Position
- Below the diagonal: mihon.app.di uses a module listed above it, which is the healthy direction.
33→18 mihon.app.di uses tachiyomi.domain.library.service✕
- Connections
- 1 pair of types, where a type in mihon.app.di uses a type in tachiyomi.domain.library.service.
- The types involved
mihon.app.di.AppGraph→tachiyomi.domain.library.service.LibraryPreferences
- Direction
- mihon.app.di uses tachiyomi.domain.library.service, so a change to tachiyomi.domain.library.service can break mihon.app.di, while a change to mihon.app.di can't break tachiyomi.domain.library.service.
- Position
- Below the diagonal: mihon.app.di uses a module listed above it, which is the healthy direction.
33→19 mihon.app.di uses tachiyomi.domain.manga.interactor✕
- Connections
- 2 pairs of types, where a type in mihon.app.di uses a type in tachiyomi.domain.manga.interactor.
- The types involved
mihon.app.di.AppGraph→tachiyomi.domain.manga.interactor.GetFavoritesmihon.app.di.AppGraph→tachiyomi.domain.manga.interactor.ResetViewerFlags
- Direction
- mihon.app.di uses tachiyomi.domain.manga.interactor, so a change to tachiyomi.domain.manga.interactor can break mihon.app.di, while a change to mihon.app.di can't break tachiyomi.domain.manga.interactor.
- Position
- Below the diagonal: mihon.app.di uses a module listed above it, which is the healthy direction.
33→20 mihon.app.di uses tachiyomi.domain.source.service✕
- Connections
- 1 pair of types, where a type in mihon.app.di uses a type in tachiyomi.domain.source.service.
- The types involved
mihon.app.di.AppGraph→tachiyomi.domain.source.service.SourceManager
- Direction
- mihon.app.di uses tachiyomi.domain.source.service, so a change to tachiyomi.domain.source.service can break mihon.app.di, while a change to mihon.app.di can't break tachiyomi.domain.source.service.
- Position
- Below the diagonal: mihon.app.di uses a module listed above it, which is the healthy direction.
33→21 mihon.app.di uses eu.kanade.tachiyomi.data.backup.create✕
- Connections
- 1 pair of types, where a type in mihon.app.di uses a type in eu.kanade.tachiyomi.data.backup.create.
- The types involved
mihon.app.di.AppGraph→eu.kanade.tachiyomi.data.backup.create.BackupCreateWorker
- Direction
- mihon.app.di uses eu.kanade.tachiyomi.data.backup.create, so a change to eu.kanade.tachiyomi.data.backup.create can break mihon.app.di, while a change to mihon.app.di can't break eu.kanade.tachiyomi.data.backup.create.
- Position
- Below the diagonal: mihon.app.di uses a module listed above it, which is the healthy direction.
33→23 mihon.app.di uses tachiyomi.domain.category.interactor✕
- Connections
- 2 pairs of types, where a type in mihon.app.di uses a type in tachiyomi.domain.category.interactor.
- The types involved
mihon.app.di.AppGraph→tachiyomi.domain.category.interactor.GetCategoriesmihon.app.di.AppGraph→tachiyomi.domain.category.interactor.ResetCategoryFlags
- Direction
- mihon.app.di uses tachiyomi.domain.category.interactor, so a change to tachiyomi.domain.category.interactor can break mihon.app.di, while a change to mihon.app.di can't break tachiyomi.domain.category.interactor.
- Position
- Below the diagonal: mihon.app.di uses a module listed above it, which is the healthy direction.
33→26 mihon.app.di uses eu.kanade.tachiyomi.data.track✕
- Connections
- 1 pair of types, where a type in mihon.app.di uses a type in eu.kanade.tachiyomi.data.track.
- The types involved
mihon.app.di.AppGraph→eu.kanade.tachiyomi.data.track.TrackerManager
- Direction
- mihon.app.di uses eu.kanade.tachiyomi.data.track, so a change to eu.kanade.tachiyomi.data.track can break mihon.app.di, while a change to mihon.app.di can't break eu.kanade.tachiyomi.data.track.
- Position
- Below the diagonal: mihon.app.di uses a module listed above it, which is the healthy direction.
33→28 mihon.app.di uses eu.kanade.domain.track.interactor✕
- Connections
- 1 pair of types, where a type in mihon.app.di uses a type in eu.kanade.domain.track.interactor.
- The types involved
mihon.app.di.AppGraph→eu.kanade.domain.track.interactor.AddTracks
- Direction
- mihon.app.di uses eu.kanade.domain.track.interactor, so a change to eu.kanade.domain.track.interactor can break mihon.app.di, while a change to mihon.app.di can't break eu.kanade.domain.track.interactor.
- Position
- Below the diagonal: mihon.app.di uses a module listed above it, which is the healthy direction.
33→29 mihon.app.di uses eu.kanade.tachiyomi.ui.reader.setting✕
- Connections
- 1 pair of types, where a type in mihon.app.di uses a type in eu.kanade.tachiyomi.ui.reader.setting.
- The types involved
mihon.app.di.AppGraph→eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences
- Direction
- mihon.app.di uses eu.kanade.tachiyomi.ui.reader.setting, so a change to eu.kanade.tachiyomi.ui.reader.setting can break mihon.app.di, while a change to mihon.app.di can't break eu.kanade.tachiyomi.ui.reader.setting.
- Position
- Below the diagonal: mihon.app.di uses a module listed above it, which is the healthy direction.
33→32 mihon.app.di uses eu.kanade.tachiyomi.ui.reader✕
- Connections
- 1 pair of types, where a type in mihon.app.di uses a type in eu.kanade.tachiyomi.ui.reader.
- The types involved
mihon.app.di.AppGraph→eu.kanade.tachiyomi.ui.reader.ReaderActivity
- Direction
- mihon.app.di uses eu.kanade.tachiyomi.ui.reader, so a change to eu.kanade.tachiyomi.ui.reader can break mihon.app.di, while a change to mihon.app.di can't break eu.kanade.tachiyomi.ui.reader.
- Position
- Below the diagonal: mihon.app.di uses a module listed above it, which is the healthy direction.
33→34 mihon.app.di uses eu.kanade.tachiyomi.data.download part of a loop✕
- Connections
- 3 pairs of types, where a type in mihon.app.di uses a type in eu.kanade.tachiyomi.data.download.
- The types involved
mihon.app.di.AppGraph→eu.kanade.tachiyomi.data.download.DownloadCachemihon.app.di.AppGraph→eu.kanade.tachiyomi.data.download.DownloadManagermihon.app.di.AppGraph→eu.kanade.tachiyomi.data.download.DownloadWorker
- Direction
- mihon.app.di uses eu.kanade.tachiyomi.data.download, so a change to eu.kanade.tachiyomi.data.download can break mihon.app.di, while a change to mihon.app.di can't break eu.kanade.tachiyomi.data.download.
- 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.
34→3 eu.kanade.tachiyomi.data.download uses eu.kanade.tachiyomi.source.model✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.data.download uses a type in eu.kanade.tachiyomi.source.model.
- The types involved
eu.kanade.tachiyomi.data.download.DownloadManager→eu.kanade.tachiyomi.source.model.Pageeu.kanade.tachiyomi.data.download.Downloader→eu.kanade.tachiyomi.source.model.Page
- Direction
- eu.kanade.tachiyomi.data.download uses eu.kanade.tachiyomi.source.model, so a change to eu.kanade.tachiyomi.source.model can break eu.kanade.tachiyomi.data.download, while a change to eu.kanade.tachiyomi.data.download can't break eu.kanade.tachiyomi.source.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.data.download uses a module listed above it, which is the healthy direction.
34→8 eu.kanade.tachiyomi.data.download uses tachiyomi.domain.chapter.model✕
- Connections
- 5 pairs of types, where a type in eu.kanade.tachiyomi.data.download uses a type in tachiyomi.domain.chapter.model.
- The types involved
eu.kanade.tachiyomi.data.download.DownloadCache→tachiyomi.domain.chapter.model.Chaptereu.kanade.tachiyomi.data.download.DownloadManager→tachiyomi.domain.chapter.model.Chaptereu.kanade.tachiyomi.data.download.DownloadPendingDeleter→tachiyomi.domain.chapter.model.Chaptereu.kanade.tachiyomi.data.download.DownloadProvider→tachiyomi.domain.chapter.model.Chaptereu.kanade.tachiyomi.data.download.Downloader→tachiyomi.domain.chapter.model.Chapter
- Direction
- eu.kanade.tachiyomi.data.download uses tachiyomi.domain.chapter.model, so a change to tachiyomi.domain.chapter.model can break eu.kanade.tachiyomi.data.download, while a change to eu.kanade.tachiyomi.data.download can't break tachiyomi.domain.chapter.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.data.download uses a module listed above it, which is the healthy direction.
34→15 eu.kanade.tachiyomi.data.download uses tachiyomi.domain.manga.model✕
- Connections
- 5 pairs of types, where a type in eu.kanade.tachiyomi.data.download uses a type in tachiyomi.domain.manga.model.
- The types involved
eu.kanade.tachiyomi.data.download.DownloadCache→tachiyomi.domain.manga.model.Mangaeu.kanade.tachiyomi.data.download.DownloadManager→tachiyomi.domain.manga.model.Mangaeu.kanade.tachiyomi.data.download.DownloadPendingDeleter→tachiyomi.domain.manga.model.Mangaeu.kanade.tachiyomi.data.download.DownloadProvider→tachiyomi.domain.manga.model.Mangaeu.kanade.tachiyomi.data.download.Downloader→tachiyomi.domain.manga.model.Manga
- Direction
- eu.kanade.tachiyomi.data.download uses tachiyomi.domain.manga.model, so a change to tachiyomi.domain.manga.model can break eu.kanade.tachiyomi.data.download, while a change to eu.kanade.tachiyomi.data.download can't break tachiyomi.domain.manga.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.data.download uses a module listed above it, which is the healthy direction.
34→18 eu.kanade.tachiyomi.data.download uses tachiyomi.domain.library.service✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.data.download uses a type in tachiyomi.domain.library.service.
- The types involved
eu.kanade.tachiyomi.data.download.DownloadProvider→tachiyomi.domain.library.service.LibraryPreferences
- Direction
- eu.kanade.tachiyomi.data.download uses tachiyomi.domain.library.service, so a change to tachiyomi.domain.library.service can break eu.kanade.tachiyomi.data.download, while a change to eu.kanade.tachiyomi.data.download can't break tachiyomi.domain.library.service.
- Position
- Below the diagonal: eu.kanade.tachiyomi.data.download uses a module listed above it, which is the healthy direction.
34→19 eu.kanade.tachiyomi.data.download uses tachiyomi.domain.manga.interactor✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.data.download uses a type in tachiyomi.domain.manga.interactor.
- The types involved
eu.kanade.tachiyomi.data.download.DownloadManager→tachiyomi.domain.manga.interactor.GetMangaeu.kanade.tachiyomi.data.download.DownloadStore→tachiyomi.domain.manga.interactor.GetManga
- Direction
- eu.kanade.tachiyomi.data.download uses tachiyomi.domain.manga.interactor, so a change to tachiyomi.domain.manga.interactor can break eu.kanade.tachiyomi.data.download, while a change to eu.kanade.tachiyomi.data.download can't break tachiyomi.domain.manga.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.data.download uses a module listed above it, which is the healthy direction.
34→20 eu.kanade.tachiyomi.data.download uses tachiyomi.domain.source.service✕
- Connections
- 4 pairs of types, where a type in eu.kanade.tachiyomi.data.download uses a type in tachiyomi.domain.source.service.
- The types involved
eu.kanade.tachiyomi.data.download.DownloadCache→tachiyomi.domain.source.service.SourceManagereu.kanade.tachiyomi.data.download.DownloadManager→tachiyomi.domain.source.service.SourceManagereu.kanade.tachiyomi.data.download.DownloadStore→tachiyomi.domain.source.service.SourceManagereu.kanade.tachiyomi.data.download.Downloader→tachiyomi.domain.source.service.SourceManager
- Direction
- eu.kanade.tachiyomi.data.download uses tachiyomi.domain.source.service, so a change to tachiyomi.domain.source.service can break eu.kanade.tachiyomi.data.download, while a change to eu.kanade.tachiyomi.data.download can't break tachiyomi.domain.source.service.
- Position
- Below the diagonal: eu.kanade.tachiyomi.data.download uses a module listed above it, which is the healthy direction.
34→22 eu.kanade.tachiyomi.data.download uses eu.kanade.tachiyomi.source✕
- Connections
- 3 pairs of types, where a type in eu.kanade.tachiyomi.data.download uses a type in eu.kanade.tachiyomi.source.
- The types involved
eu.kanade.tachiyomi.data.download.DownloadCache→eu.kanade.tachiyomi.source.Sourceeu.kanade.tachiyomi.data.download.DownloadManager→eu.kanade.tachiyomi.source.Sourceeu.kanade.tachiyomi.data.download.DownloadProvider→eu.kanade.tachiyomi.source.Source
- Direction
- eu.kanade.tachiyomi.data.download uses eu.kanade.tachiyomi.source, so a change to eu.kanade.tachiyomi.source can break eu.kanade.tachiyomi.data.download, while a change to eu.kanade.tachiyomi.data.download can't break eu.kanade.tachiyomi.source.
- Position
- Below the diagonal: eu.kanade.tachiyomi.data.download uses a module listed above it, which is the healthy direction.
34→23 eu.kanade.tachiyomi.data.download uses tachiyomi.domain.category.interactor✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.data.download uses a type in tachiyomi.domain.category.interactor.
- The types involved
eu.kanade.tachiyomi.data.download.DownloadManager→tachiyomi.domain.category.interactor.GetCategorieseu.kanade.tachiyomi.data.download.Downloader→tachiyomi.domain.category.interactor.GetCategories
- Direction
- eu.kanade.tachiyomi.data.download uses tachiyomi.domain.category.interactor, so a change to tachiyomi.domain.category.interactor can break eu.kanade.tachiyomi.data.download, while a change to eu.kanade.tachiyomi.data.download can't break tachiyomi.domain.category.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.data.download uses a module listed above it, which is the healthy direction.
34→24 eu.kanade.tachiyomi.data.download uses tachiyomi.domain.chapter.interactor✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.data.download uses a type in tachiyomi.domain.chapter.interactor.
- The types involved
eu.kanade.tachiyomi.data.download.DownloadManager→tachiyomi.domain.chapter.interactor.GetChaptereu.kanade.tachiyomi.data.download.DownloadStore→tachiyomi.domain.chapter.interactor.GetChapter
- Direction
- eu.kanade.tachiyomi.data.download uses tachiyomi.domain.chapter.interactor, so a change to tachiyomi.domain.chapter.interactor can break eu.kanade.tachiyomi.data.download, while a change to eu.kanade.tachiyomi.data.download can't break tachiyomi.domain.chapter.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.data.download uses a module listed above it, which is the healthy direction.
34→33 eu.kanade.tachiyomi.data.download uses mihon.app.di✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.data.download uses a type in mihon.app.di.
- The types involved
eu.kanade.tachiyomi.data.download.DownloadWorker→mihon.app.di.AppGraph
- Direction
- eu.kanade.tachiyomi.data.download uses mihon.app.di, so a change to mihon.app.di can break eu.kanade.tachiyomi.data.download, while a change to eu.kanade.tachiyomi.data.download can't break mihon.app.di.
- Position
- Below the diagonal: eu.kanade.tachiyomi.data.download uses a module listed above it, which is the healthy direction.
35→3 eu.kanade.domain.chapter.interactor uses eu.kanade.tachiyomi.source.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.domain.chapter.interactor uses a type in eu.kanade.tachiyomi.source.model.
- The types involved
eu.kanade.domain.chapter.interactor.SyncChaptersWithSource→eu.kanade.tachiyomi.source.model.SChapter
- Direction
- eu.kanade.domain.chapter.interactor uses eu.kanade.tachiyomi.source.model, so a change to eu.kanade.tachiyomi.source.model can break eu.kanade.domain.chapter.interactor, while a change to eu.kanade.domain.chapter.interactor can't break eu.kanade.tachiyomi.source.model.
- Position
- Below the diagonal: eu.kanade.domain.chapter.interactor uses a module listed above it, which is the healthy direction.
35→8 eu.kanade.domain.chapter.interactor uses tachiyomi.domain.chapter.model✕
- Connections
- 3 pairs of types, where a type in eu.kanade.domain.chapter.interactor uses a type in tachiyomi.domain.chapter.model.
- The types involved
eu.kanade.domain.chapter.interactor.SetReadStatus→tachiyomi.domain.chapter.model.Chaptereu.kanade.domain.chapter.interactor.SetReadStatus→tachiyomi.domain.chapter.model.ChapterUpdateeu.kanade.domain.chapter.interactor.SyncChaptersWithSource→tachiyomi.domain.chapter.model.Chapter
- Direction
- eu.kanade.domain.chapter.interactor uses tachiyomi.domain.chapter.model, so a change to tachiyomi.domain.chapter.model can break eu.kanade.domain.chapter.interactor, while a change to eu.kanade.domain.chapter.interactor can't break tachiyomi.domain.chapter.model.
- Position
- Below the diagonal: eu.kanade.domain.chapter.interactor uses a module listed above it, which is the healthy direction.
35→15 eu.kanade.domain.chapter.interactor uses tachiyomi.domain.manga.model✕
- Connections
- 2 pairs of types, where a type in eu.kanade.domain.chapter.interactor uses a type in tachiyomi.domain.manga.model.
- The types involved
eu.kanade.domain.chapter.interactor.SetReadStatus→tachiyomi.domain.manga.model.Mangaeu.kanade.domain.chapter.interactor.SyncChaptersWithSource→tachiyomi.domain.manga.model.Manga
- Direction
- eu.kanade.domain.chapter.interactor uses tachiyomi.domain.manga.model, so a change to tachiyomi.domain.manga.model can break eu.kanade.domain.chapter.interactor, while a change to eu.kanade.domain.chapter.interactor can't break tachiyomi.domain.manga.model.
- Position
- Below the diagonal: eu.kanade.domain.chapter.interactor uses a module listed above it, which is the healthy direction.
35→18 eu.kanade.domain.chapter.interactor uses tachiyomi.domain.library.service✕
- Connections
- 1 pair of types, where a type in eu.kanade.domain.chapter.interactor uses a type in tachiyomi.domain.library.service.
- The types involved
eu.kanade.domain.chapter.interactor.SyncChaptersWithSource→tachiyomi.domain.library.service.LibraryPreferences
- Direction
- eu.kanade.domain.chapter.interactor uses tachiyomi.domain.library.service, so a change to tachiyomi.domain.library.service can break eu.kanade.domain.chapter.interactor, while a change to eu.kanade.domain.chapter.interactor can't break tachiyomi.domain.library.service.
- Position
- Below the diagonal: eu.kanade.domain.chapter.interactor uses a module listed above it, which is the healthy direction.
35→22 eu.kanade.domain.chapter.interactor uses eu.kanade.tachiyomi.source✕
- Connections
- 1 pair of types, where a type in eu.kanade.domain.chapter.interactor uses a type in eu.kanade.tachiyomi.source.
- The types involved
eu.kanade.domain.chapter.interactor.SyncChaptersWithSource→eu.kanade.tachiyomi.source.Source
- Direction
- eu.kanade.domain.chapter.interactor uses eu.kanade.tachiyomi.source, so a change to eu.kanade.tachiyomi.source can break eu.kanade.domain.chapter.interactor, while a change to eu.kanade.domain.chapter.interactor can't break eu.kanade.tachiyomi.source.
- Position
- Below the diagonal: eu.kanade.domain.chapter.interactor uses a module listed above it, which is the healthy direction.
35→24 eu.kanade.domain.chapter.interactor uses tachiyomi.domain.chapter.interactor✕
- Connections
- 1 pair of types, where a type in eu.kanade.domain.chapter.interactor uses a type in tachiyomi.domain.chapter.interactor.
- The types involved
eu.kanade.domain.chapter.interactor.SyncChaptersWithSource→tachiyomi.domain.chapter.interactor.ShouldUpdateDbChapter
- Direction
- eu.kanade.domain.chapter.interactor uses tachiyomi.domain.chapter.interactor, so a change to tachiyomi.domain.chapter.interactor can break eu.kanade.domain.chapter.interactor, while a change to eu.kanade.domain.chapter.interactor can't break tachiyomi.domain.chapter.interactor.
- Position
- Below the diagonal: eu.kanade.domain.chapter.interactor uses a module listed above it, which is the healthy direction.
35→34 eu.kanade.domain.chapter.interactor uses eu.kanade.tachiyomi.data.download✕
- Connections
- 2 pairs of types, where a type in eu.kanade.domain.chapter.interactor uses a type in eu.kanade.tachiyomi.data.download.
- The types involved
eu.kanade.domain.chapter.interactor.SyncChaptersWithSource→eu.kanade.tachiyomi.data.download.DownloadManagereu.kanade.domain.chapter.interactor.SyncChaptersWithSource→eu.kanade.tachiyomi.data.download.DownloadProvider
- Direction
- eu.kanade.domain.chapter.interactor uses eu.kanade.tachiyomi.data.download, so a change to eu.kanade.tachiyomi.data.download can break eu.kanade.domain.chapter.interactor, while a change to eu.kanade.domain.chapter.interactor can't break eu.kanade.tachiyomi.data.download.
- Position
- Below the diagonal: eu.kanade.domain.chapter.interactor uses a module listed above it, which is the healthy direction.
36→1 eu.kanade.tachiyomi.ui.updates uses eu.kanade.presentation.util✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.updates uses a type in eu.kanade.presentation.util.
- The types involved
eu.kanade.tachiyomi.ui.updates.UpdatesTab→eu.kanade.presentation.util.Tab
- Direction
- eu.kanade.tachiyomi.ui.updates uses eu.kanade.presentation.util, so a change to eu.kanade.presentation.util can break eu.kanade.tachiyomi.ui.updates, while a change to eu.kanade.tachiyomi.ui.updates can't break eu.kanade.presentation.util.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.updates uses a module listed above it, which is the healthy direction.
36→6 eu.kanade.tachiyomi.ui.updates uses tachiyomi.core.common.preference✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.ui.updates uses a type in tachiyomi.core.common.preference.
- The types involved
eu.kanade.tachiyomi.ui.updates.UpdatesSettingsViewModel→tachiyomi.core.common.preference.Preferenceeu.kanade.tachiyomi.ui.updates.UpdatesSettingsViewModel→tachiyomi.core.common.preference.TriState
- Direction
- eu.kanade.tachiyomi.ui.updates uses tachiyomi.core.common.preference, so a change to tachiyomi.core.common.preference can break eu.kanade.tachiyomi.ui.updates, while a change to eu.kanade.tachiyomi.ui.updates can't break tachiyomi.core.common.preference.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.updates uses a module listed above it, which is the healthy direction.
36→7 eu.kanade.tachiyomi.ui.updates uses tachiyomi.domain.category.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.updates uses a type in tachiyomi.domain.category.model.
- The types involved
eu.kanade.tachiyomi.ui.updates.UpdatesSettingsViewModel→tachiyomi.domain.category.model.Category
- Direction
- eu.kanade.tachiyomi.ui.updates uses tachiyomi.domain.category.model, so a change to tachiyomi.domain.category.model can break eu.kanade.tachiyomi.ui.updates, while a change to eu.kanade.tachiyomi.ui.updates can't break tachiyomi.domain.category.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.updates uses a module listed above it, which is the healthy direction.
36→18 eu.kanade.tachiyomi.ui.updates uses tachiyomi.domain.library.service✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.updates uses a type in tachiyomi.domain.library.service.
- The types involved
eu.kanade.tachiyomi.ui.updates.UpdatesViewModel→tachiyomi.domain.library.service.LibraryPreferences
- Direction
- eu.kanade.tachiyomi.ui.updates uses tachiyomi.domain.library.service, so a change to tachiyomi.domain.library.service can break eu.kanade.tachiyomi.ui.updates, while a change to eu.kanade.tachiyomi.ui.updates can't break tachiyomi.domain.library.service.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.updates uses a module listed above it, which is the healthy direction.
36→19 eu.kanade.tachiyomi.ui.updates uses tachiyomi.domain.manga.interactor✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.updates uses a type in tachiyomi.domain.manga.interactor.
- The types involved
eu.kanade.tachiyomi.ui.updates.UpdatesViewModel→tachiyomi.domain.manga.interactor.GetManga
- Direction
- eu.kanade.tachiyomi.ui.updates uses tachiyomi.domain.manga.interactor, so a change to tachiyomi.domain.manga.interactor can break eu.kanade.tachiyomi.ui.updates, while a change to eu.kanade.tachiyomi.ui.updates can't break tachiyomi.domain.manga.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.updates uses a module listed above it, which is the healthy direction.
36→20 eu.kanade.tachiyomi.ui.updates uses tachiyomi.domain.source.service✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.updates uses a type in tachiyomi.domain.source.service.
- The types involved
eu.kanade.tachiyomi.ui.updates.UpdatesViewModel→tachiyomi.domain.source.service.SourceManager
- Direction
- eu.kanade.tachiyomi.ui.updates uses tachiyomi.domain.source.service, so a change to tachiyomi.domain.source.service can break eu.kanade.tachiyomi.ui.updates, while a change to eu.kanade.tachiyomi.ui.updates can't break tachiyomi.domain.source.service.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.updates uses a module listed above it, which is the healthy direction.
36→23 eu.kanade.tachiyomi.ui.updates uses tachiyomi.domain.category.interactor✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.updates uses a type in tachiyomi.domain.category.interactor.
- The types involved
eu.kanade.tachiyomi.ui.updates.UpdatesSettingsViewModel→tachiyomi.domain.category.interactor.GetCategories
- Direction
- eu.kanade.tachiyomi.ui.updates uses tachiyomi.domain.category.interactor, so a change to tachiyomi.domain.category.interactor can break eu.kanade.tachiyomi.ui.updates, while a change to eu.kanade.tachiyomi.ui.updates can't break tachiyomi.domain.category.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.updates uses a module listed above it, which is the healthy direction.
36→24 eu.kanade.tachiyomi.ui.updates uses tachiyomi.domain.chapter.interactor✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.ui.updates uses a type in tachiyomi.domain.chapter.interactor.
- The types involved
eu.kanade.tachiyomi.ui.updates.UpdatesViewModel→tachiyomi.domain.chapter.interactor.GetChaptereu.kanade.tachiyomi.ui.updates.UpdatesViewModel→tachiyomi.domain.chapter.interactor.UpdateChapter
- Direction
- eu.kanade.tachiyomi.ui.updates uses tachiyomi.domain.chapter.interactor, so a change to tachiyomi.domain.chapter.interactor can break eu.kanade.tachiyomi.ui.updates, while a change to eu.kanade.tachiyomi.ui.updates can't break tachiyomi.domain.chapter.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.updates uses a module listed above it, which is the healthy direction.
36→34 eu.kanade.tachiyomi.ui.updates uses eu.kanade.tachiyomi.data.download✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.ui.updates uses a type in eu.kanade.tachiyomi.data.download.
- The types involved
eu.kanade.tachiyomi.ui.updates.UpdatesViewModel→eu.kanade.tachiyomi.data.download.DownloadCacheeu.kanade.tachiyomi.ui.updates.UpdatesViewModel→eu.kanade.tachiyomi.data.download.DownloadManager
- Direction
- eu.kanade.tachiyomi.ui.updates uses eu.kanade.tachiyomi.data.download, so a change to eu.kanade.tachiyomi.data.download can break eu.kanade.tachiyomi.ui.updates, while a change to eu.kanade.tachiyomi.ui.updates can't break eu.kanade.tachiyomi.data.download.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.updates uses a module listed above it, which is the healthy direction.
36→35 eu.kanade.tachiyomi.ui.updates uses eu.kanade.domain.chapter.interactor✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.updates uses a type in eu.kanade.domain.chapter.interactor.
- The types involved
eu.kanade.tachiyomi.ui.updates.UpdatesViewModel→eu.kanade.domain.chapter.interactor.SetReadStatus
- Direction
- eu.kanade.tachiyomi.ui.updates uses eu.kanade.domain.chapter.interactor, so a change to eu.kanade.domain.chapter.interactor can break eu.kanade.tachiyomi.ui.updates, while a change to eu.kanade.tachiyomi.ui.updates can't break eu.kanade.domain.chapter.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.updates uses a module listed above it, which is the healthy direction.
37→3 mihon.domain.source.interactor uses eu.kanade.tachiyomi.source.model✕
- Connections
- 1 pair of types, where a type in mihon.domain.source.interactor uses a type in eu.kanade.tachiyomi.source.model.
- The types involved
mihon.domain.source.interactor.UpdateMangaFromRemote→eu.kanade.tachiyomi.source.model.SManga
- Direction
- mihon.domain.source.interactor uses eu.kanade.tachiyomi.source.model, so a change to eu.kanade.tachiyomi.source.model can break mihon.domain.source.interactor, while a change to mihon.domain.source.interactor can't break eu.kanade.tachiyomi.source.model.
- Position
- Below the diagonal: mihon.domain.source.interactor uses a module listed above it, which is the healthy direction.
37→15 mihon.domain.source.interactor uses tachiyomi.domain.manga.model✕
- Connections
- 1 pair of types, where a type in mihon.domain.source.interactor uses a type in tachiyomi.domain.manga.model.
- The types involved
mihon.domain.source.interactor.UpdateMangaFromRemote→tachiyomi.domain.manga.model.Manga
- Direction
- mihon.domain.source.interactor uses tachiyomi.domain.manga.model, so a change to tachiyomi.domain.manga.model can break mihon.domain.source.interactor, while a change to mihon.domain.source.interactor can't break tachiyomi.domain.manga.model.
- Position
- Below the diagonal: mihon.domain.source.interactor uses a module listed above it, which is the healthy direction.
37→18 mihon.domain.source.interactor uses tachiyomi.domain.library.service✕
- Connections
- 1 pair of types, where a type in mihon.domain.source.interactor uses a type in tachiyomi.domain.library.service.
- The types involved
mihon.domain.source.interactor.UpdateMangaFromRemote→tachiyomi.domain.library.service.LibraryPreferences
- Direction
- mihon.domain.source.interactor uses tachiyomi.domain.library.service, so a change to tachiyomi.domain.library.service can break mihon.domain.source.interactor, while a change to mihon.domain.source.interactor can't break tachiyomi.domain.library.service.
- Position
- Below the diagonal: mihon.domain.source.interactor uses a module listed above it, which is the healthy direction.
37→20 mihon.domain.source.interactor uses tachiyomi.domain.source.service✕
- Connections
- 1 pair of types, where a type in mihon.domain.source.interactor uses a type in tachiyomi.domain.source.service.
- The types involved
mihon.domain.source.interactor.UpdateMangaFromRemote→tachiyomi.domain.source.service.SourceManager
- Direction
- mihon.domain.source.interactor uses tachiyomi.domain.source.service, so a change to tachiyomi.domain.source.service can break mihon.domain.source.interactor, while a change to mihon.domain.source.interactor can't break tachiyomi.domain.source.service.
- Position
- Below the diagonal: mihon.domain.source.interactor uses a module listed above it, which is the healthy direction.
37→22 mihon.domain.source.interactor uses eu.kanade.tachiyomi.source✕
- Connections
- 1 pair of types, where a type in mihon.domain.source.interactor uses a type in eu.kanade.tachiyomi.source.
- The types involved
mihon.domain.source.interactor.UpdateMangaFromRemote→eu.kanade.tachiyomi.source.Source
- Direction
- mihon.domain.source.interactor uses eu.kanade.tachiyomi.source, so a change to eu.kanade.tachiyomi.source can break mihon.domain.source.interactor, while a change to mihon.domain.source.interactor can't break eu.kanade.tachiyomi.source.
- Position
- Below the diagonal: mihon.domain.source.interactor uses a module listed above it, which is the healthy direction.
37→34 mihon.domain.source.interactor uses eu.kanade.tachiyomi.data.download✕
- Connections
- 1 pair of types, where a type in mihon.domain.source.interactor uses a type in eu.kanade.tachiyomi.data.download.
- The types involved
mihon.domain.source.interactor.UpdateMangaFromRemote→eu.kanade.tachiyomi.data.download.DownloadManager
- Direction
- mihon.domain.source.interactor uses eu.kanade.tachiyomi.data.download, so a change to eu.kanade.tachiyomi.data.download can break mihon.domain.source.interactor, while a change to mihon.domain.source.interactor can't break eu.kanade.tachiyomi.data.download.
- Position
- Below the diagonal: mihon.domain.source.interactor uses a module listed above it, which is the healthy direction.
37→35 mihon.domain.source.interactor uses eu.kanade.domain.chapter.interactor✕
- Connections
- 1 pair of types, where a type in mihon.domain.source.interactor uses a type in eu.kanade.domain.chapter.interactor.
- The types involved
mihon.domain.source.interactor.UpdateMangaFromRemote→eu.kanade.domain.chapter.interactor.SyncChaptersWithSource
- Direction
- mihon.domain.source.interactor uses eu.kanade.domain.chapter.interactor, so a change to eu.kanade.domain.chapter.interactor can break mihon.domain.source.interactor, while a change to mihon.domain.source.interactor can't break eu.kanade.domain.chapter.interactor.
- Position
- Below the diagonal: mihon.domain.source.interactor uses a module listed above it, which is the healthy direction.
38→1 eu.kanade.tachiyomi.ui.manga uses eu.kanade.presentation.util✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.ui.manga uses a type in eu.kanade.presentation.util.
- The types involved
eu.kanade.tachiyomi.ui.manga.MangaScreen→eu.kanade.presentation.util.AssistContentScreeneu.kanade.tachiyomi.ui.manga.MangaScreen→eu.kanade.presentation.util.Screen
- Direction
- eu.kanade.tachiyomi.ui.manga uses eu.kanade.presentation.util, so a change to eu.kanade.presentation.util can break eu.kanade.tachiyomi.ui.manga, while a change to eu.kanade.tachiyomi.ui.manga can't break eu.kanade.presentation.util.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.manga uses a module listed above it, which is the healthy direction.
38→6 eu.kanade.tachiyomi.ui.manga uses tachiyomi.core.common.preference✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.manga uses a type in tachiyomi.core.common.preference.
- The types involved
eu.kanade.tachiyomi.ui.manga.MangaViewModel→tachiyomi.core.common.preference.TriState
- Direction
- eu.kanade.tachiyomi.ui.manga uses tachiyomi.core.common.preference, so a change to tachiyomi.core.common.preference can break eu.kanade.tachiyomi.ui.manga, while a change to eu.kanade.tachiyomi.ui.manga can't break tachiyomi.core.common.preference.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.manga uses a module listed above it, which is the healthy direction.
38→7 eu.kanade.tachiyomi.ui.manga uses tachiyomi.domain.category.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.manga uses a type in tachiyomi.domain.category.model.
- The types involved
eu.kanade.tachiyomi.ui.manga.MangaViewModel→tachiyomi.domain.category.model.Category
- Direction
- eu.kanade.tachiyomi.ui.manga uses tachiyomi.domain.category.model, so a change to tachiyomi.domain.category.model can break eu.kanade.tachiyomi.ui.manga, while a change to eu.kanade.tachiyomi.ui.manga can't break tachiyomi.domain.category.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.manga uses a module listed above it, which is the healthy direction.
38→8 eu.kanade.tachiyomi.ui.manga uses tachiyomi.domain.chapter.model✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.ui.manga uses a type in tachiyomi.domain.chapter.model.
- The types involved
eu.kanade.tachiyomi.ui.manga.MangaScreen→tachiyomi.domain.chapter.model.Chaptereu.kanade.tachiyomi.ui.manga.MangaViewModel→tachiyomi.domain.chapter.model.Chapter
- Direction
- eu.kanade.tachiyomi.ui.manga uses tachiyomi.domain.chapter.model, so a change to tachiyomi.domain.chapter.model can break eu.kanade.tachiyomi.ui.manga, while a change to eu.kanade.tachiyomi.ui.manga can't break tachiyomi.domain.chapter.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.manga uses a module listed above it, which is the healthy direction.
38→10 eu.kanade.tachiyomi.ui.manga uses eu.kanade.domain.base✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.manga uses a type in eu.kanade.domain.base.
- The types involved
eu.kanade.tachiyomi.ui.manga.MangaViewModel→eu.kanade.domain.base.BasePreferences
- Direction
- eu.kanade.tachiyomi.ui.manga uses eu.kanade.domain.base, so a change to eu.kanade.domain.base can break eu.kanade.tachiyomi.ui.manga, while a change to eu.kanade.tachiyomi.ui.manga can't break eu.kanade.domain.base.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.manga uses a module listed above it, which is the healthy direction.
38→11 eu.kanade.tachiyomi.ui.manga uses eu.kanade.domain.source.service✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.manga uses a type in eu.kanade.domain.source.service.
- The types involved
eu.kanade.tachiyomi.ui.manga.MangaViewModel→eu.kanade.domain.source.service.SourcePreferences
- Direction
- eu.kanade.tachiyomi.ui.manga uses eu.kanade.domain.source.service, so a change to eu.kanade.domain.source.service can break eu.kanade.tachiyomi.ui.manga, while a change to eu.kanade.tachiyomi.ui.manga can't break eu.kanade.domain.source.service.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.manga uses a module listed above it, which is the healthy direction.
38→15 eu.kanade.tachiyomi.ui.manga uses tachiyomi.domain.manga.model✕
- Connections
- 3 pairs of types, where a type in eu.kanade.tachiyomi.ui.manga uses a type in tachiyomi.domain.manga.model.
- The types involved
eu.kanade.tachiyomi.ui.manga.MangaCoverViewModel→tachiyomi.domain.manga.model.Mangaeu.kanade.tachiyomi.ui.manga.MangaScreen→tachiyomi.domain.manga.model.Mangaeu.kanade.tachiyomi.ui.manga.MangaViewModel→tachiyomi.domain.manga.model.Manga
- Direction
- eu.kanade.tachiyomi.ui.manga uses tachiyomi.domain.manga.model, so a change to tachiyomi.domain.manga.model can break eu.kanade.tachiyomi.ui.manga, while a change to eu.kanade.tachiyomi.ui.manga can't break tachiyomi.domain.manga.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.manga uses a module listed above it, which is the healthy direction.
38→18 eu.kanade.tachiyomi.ui.manga uses tachiyomi.domain.library.service✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.manga uses a type in tachiyomi.domain.library.service.
- The types involved
eu.kanade.tachiyomi.ui.manga.MangaViewModel→tachiyomi.domain.library.service.LibraryPreferences
- Direction
- eu.kanade.tachiyomi.ui.manga uses tachiyomi.domain.library.service, so a change to tachiyomi.domain.library.service can break eu.kanade.tachiyomi.ui.manga, while a change to eu.kanade.tachiyomi.ui.manga can't break tachiyomi.domain.library.service.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.manga uses a module listed above it, which is the healthy direction.
38→19 eu.kanade.tachiyomi.ui.manga uses tachiyomi.domain.manga.interactor✕
- Connections
- 4 pairs of types, where a type in eu.kanade.tachiyomi.ui.manga uses a type in tachiyomi.domain.manga.interactor.
- The types involved
eu.kanade.tachiyomi.ui.manga.MangaCoverViewModel→tachiyomi.domain.manga.interactor.GetMangaeu.kanade.tachiyomi.ui.manga.MangaViewModel→tachiyomi.domain.manga.interactor.GetDuplicateLibraryMangaeu.kanade.tachiyomi.ui.manga.MangaViewModel→tachiyomi.domain.manga.interactor.GetMangaWithChapterseu.kanade.tachiyomi.ui.manga.MangaViewModel→tachiyomi.domain.manga.interactor.SetMangaChapterFlags
- Direction
- eu.kanade.tachiyomi.ui.manga uses tachiyomi.domain.manga.interactor, so a change to tachiyomi.domain.manga.interactor can break eu.kanade.tachiyomi.ui.manga, while a change to eu.kanade.tachiyomi.ui.manga can't break tachiyomi.domain.manga.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.manga uses a module listed above it, which is the healthy direction.
38→20 eu.kanade.tachiyomi.ui.manga uses tachiyomi.domain.source.service✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.manga uses a type in tachiyomi.domain.source.service.
- The types involved
eu.kanade.tachiyomi.ui.manga.MangaViewModel→tachiyomi.domain.source.service.SourceManager
- Direction
- eu.kanade.tachiyomi.ui.manga uses tachiyomi.domain.source.service, so a change to tachiyomi.domain.source.service can break eu.kanade.tachiyomi.ui.manga, while a change to eu.kanade.tachiyomi.ui.manga can't break tachiyomi.domain.source.service.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.manga uses a module listed above it, which is the healthy direction.
38→22 eu.kanade.tachiyomi.ui.manga uses eu.kanade.tachiyomi.source✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.ui.manga uses a type in eu.kanade.tachiyomi.source.
- The types involved
eu.kanade.tachiyomi.ui.manga.MangaScreen→eu.kanade.tachiyomi.source.Sourceeu.kanade.tachiyomi.ui.manga.MangaViewModel→eu.kanade.tachiyomi.source.Source
- Direction
- eu.kanade.tachiyomi.ui.manga uses eu.kanade.tachiyomi.source, so a change to eu.kanade.tachiyomi.source can break eu.kanade.tachiyomi.ui.manga, while a change to eu.kanade.tachiyomi.ui.manga can't break eu.kanade.tachiyomi.source.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.manga uses a module listed above it, which is the healthy direction.
38→23 eu.kanade.tachiyomi.ui.manga uses tachiyomi.domain.category.interactor✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.ui.manga uses a type in tachiyomi.domain.category.interactor.
- The types involved
eu.kanade.tachiyomi.ui.manga.MangaViewModel→tachiyomi.domain.category.interactor.GetCategorieseu.kanade.tachiyomi.ui.manga.MangaViewModel→tachiyomi.domain.category.interactor.SetMangaCategories
- Direction
- eu.kanade.tachiyomi.ui.manga uses tachiyomi.domain.category.interactor, so a change to tachiyomi.domain.category.interactor can break eu.kanade.tachiyomi.ui.manga, while a change to eu.kanade.tachiyomi.ui.manga can't break tachiyomi.domain.category.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.manga uses a module listed above it, which is the healthy direction.
38→24 eu.kanade.tachiyomi.ui.manga uses tachiyomi.domain.chapter.interactor✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.ui.manga uses a type in tachiyomi.domain.chapter.interactor.
- The types involved
eu.kanade.tachiyomi.ui.manga.MangaViewModel→tachiyomi.domain.chapter.interactor.SetMangaDefaultChapterFlagseu.kanade.tachiyomi.ui.manga.MangaViewModel→tachiyomi.domain.chapter.interactor.UpdateChapter
- Direction
- eu.kanade.tachiyomi.ui.manga uses tachiyomi.domain.chapter.interactor, so a change to tachiyomi.domain.chapter.interactor can break eu.kanade.tachiyomi.ui.manga, while a change to eu.kanade.tachiyomi.ui.manga can't break tachiyomi.domain.chapter.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.manga uses a module listed above it, which is the healthy direction.
38→26 eu.kanade.tachiyomi.ui.manga uses eu.kanade.tachiyomi.data.track✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.manga uses a type in eu.kanade.tachiyomi.data.track.
- The types involved
eu.kanade.tachiyomi.ui.manga.MangaViewModel→eu.kanade.tachiyomi.data.track.TrackerManager
- Direction
- eu.kanade.tachiyomi.ui.manga uses eu.kanade.tachiyomi.data.track, so a change to eu.kanade.tachiyomi.data.track can break eu.kanade.tachiyomi.ui.manga, while a change to eu.kanade.tachiyomi.ui.manga can't break eu.kanade.tachiyomi.data.track.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.manga uses a module listed above it, which is the healthy direction.
38→28 eu.kanade.tachiyomi.ui.manga uses eu.kanade.domain.track.interactor✕
- Connections
- 3 pairs of types, where a type in eu.kanade.tachiyomi.ui.manga uses a type in eu.kanade.domain.track.interactor.
- The types involved
eu.kanade.tachiyomi.ui.manga.MangaViewModel→eu.kanade.domain.track.interactor.AddTrackseu.kanade.tachiyomi.ui.manga.MangaViewModel→eu.kanade.domain.track.interactor.RefreshTrackseu.kanade.tachiyomi.ui.manga.MangaViewModel→eu.kanade.domain.track.interactor.TrackChapter
- Direction
- eu.kanade.tachiyomi.ui.manga uses eu.kanade.domain.track.interactor, so a change to eu.kanade.domain.track.interactor can break eu.kanade.tachiyomi.ui.manga, while a change to eu.kanade.tachiyomi.ui.manga can't break eu.kanade.domain.track.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.manga uses a module listed above it, which is the healthy direction.
38→29 eu.kanade.tachiyomi.ui.manga uses eu.kanade.tachiyomi.ui.reader.setting✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.manga uses a type in eu.kanade.tachiyomi.ui.reader.setting.
- The types involved
eu.kanade.tachiyomi.ui.manga.MangaViewModel→eu.kanade.tachiyomi.ui.reader.setting.ReaderPreferences
- Direction
- eu.kanade.tachiyomi.ui.manga uses eu.kanade.tachiyomi.ui.reader.setting, so a change to eu.kanade.tachiyomi.ui.reader.setting can break eu.kanade.tachiyomi.ui.manga, while a change to eu.kanade.tachiyomi.ui.manga can't break eu.kanade.tachiyomi.ui.reader.setting.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.manga uses a module listed above it, which is the healthy direction.
38→34 eu.kanade.tachiyomi.ui.manga uses eu.kanade.tachiyomi.data.download✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.ui.manga uses a type in eu.kanade.tachiyomi.data.download.
- The types involved
eu.kanade.tachiyomi.ui.manga.MangaViewModel→eu.kanade.tachiyomi.data.download.DownloadCacheeu.kanade.tachiyomi.ui.manga.MangaViewModel→eu.kanade.tachiyomi.data.download.DownloadManager
- Direction
- eu.kanade.tachiyomi.ui.manga uses eu.kanade.tachiyomi.data.download, so a change to eu.kanade.tachiyomi.data.download can break eu.kanade.tachiyomi.ui.manga, while a change to eu.kanade.tachiyomi.ui.manga can't break eu.kanade.tachiyomi.data.download.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.manga uses a module listed above it, which is the healthy direction.
38→35 eu.kanade.tachiyomi.ui.manga uses eu.kanade.domain.chapter.interactor✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.ui.manga uses a type in eu.kanade.domain.chapter.interactor.
- The types involved
eu.kanade.tachiyomi.ui.manga.MangaViewModel→eu.kanade.domain.chapter.interactor.GetAvailableScanlatorseu.kanade.tachiyomi.ui.manga.MangaViewModel→eu.kanade.domain.chapter.interactor.SetReadStatus
- Direction
- eu.kanade.tachiyomi.ui.manga uses eu.kanade.domain.chapter.interactor, so a change to eu.kanade.domain.chapter.interactor can break eu.kanade.tachiyomi.ui.manga, while a change to eu.kanade.tachiyomi.ui.manga can't break eu.kanade.domain.chapter.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.manga uses a module listed above it, which is the healthy direction.
38→37 eu.kanade.tachiyomi.ui.manga uses mihon.domain.source.interactor✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.manga uses a type in mihon.domain.source.interactor.
- The types involved
eu.kanade.tachiyomi.ui.manga.MangaViewModel→mihon.domain.source.interactor.UpdateMangaFromRemote
- Direction
- eu.kanade.tachiyomi.ui.manga uses mihon.domain.source.interactor, so a change to mihon.domain.source.interactor can break eu.kanade.tachiyomi.ui.manga, while a change to eu.kanade.tachiyomi.ui.manga can't break mihon.domain.source.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.manga uses a module listed above it, which is the healthy direction.
38→39 eu.kanade.tachiyomi.ui.manga uses eu.kanade.presentation.manga part of a loop✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.manga uses a type in eu.kanade.presentation.manga.
- The types involved
eu.kanade.tachiyomi.ui.manga.MangaViewModel→eu.kanade.presentation.manga.DownloadAction
- Direction
- eu.kanade.tachiyomi.ui.manga uses eu.kanade.presentation.manga, so a change to eu.kanade.presentation.manga can break eu.kanade.tachiyomi.ui.manga, while a change to eu.kanade.tachiyomi.ui.manga can't break eu.kanade.presentation.manga.
- 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.
39→6 eu.kanade.presentation.manga uses tachiyomi.core.common.preference✕
- Connections
- 1 pair of types, where a type in eu.kanade.presentation.manga uses a type in tachiyomi.core.common.preference.
- The types involved
eu.kanade.presentation.manga.ChapterSettingsDialogKt→tachiyomi.core.common.preference.TriState
- Direction
- eu.kanade.presentation.manga uses tachiyomi.core.common.preference, so a change to tachiyomi.core.common.preference can break eu.kanade.presentation.manga, while a change to eu.kanade.presentation.manga can't break tachiyomi.core.common.preference.
- Position
- Below the diagonal: eu.kanade.presentation.manga uses a module listed above it, which is the healthy direction.
39→8 eu.kanade.presentation.manga uses tachiyomi.domain.chapter.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.presentation.manga uses a type in tachiyomi.domain.chapter.model.
- The types involved
eu.kanade.presentation.manga.MangaScreenKt→tachiyomi.domain.chapter.model.Chapter
- Direction
- eu.kanade.presentation.manga uses tachiyomi.domain.chapter.model, so a change to tachiyomi.domain.chapter.model can break eu.kanade.presentation.manga, while a change to eu.kanade.presentation.manga can't break tachiyomi.domain.chapter.model.
- Position
- Below the diagonal: eu.kanade.presentation.manga uses a module listed above it, which is the healthy direction.
39→15 eu.kanade.presentation.manga uses tachiyomi.domain.manga.model✕
- Connections
- 4 pairs of types, where a type in eu.kanade.presentation.manga uses a type in tachiyomi.domain.manga.model.
- The types involved
eu.kanade.presentation.manga.ChapterSettingsDialogKt→tachiyomi.domain.manga.model.Mangaeu.kanade.presentation.manga.DuplicateMangaDialogKt→tachiyomi.domain.manga.model.Mangaeu.kanade.presentation.manga.DuplicateMangaDialogKt→tachiyomi.domain.manga.model.MangaWithChapterCounteu.kanade.presentation.manga.MangaScreenKt→tachiyomi.domain.manga.model.Manga
- Direction
- eu.kanade.presentation.manga uses tachiyomi.domain.manga.model, so a change to tachiyomi.domain.manga.model can break eu.kanade.presentation.manga, while a change to eu.kanade.presentation.manga can't break tachiyomi.domain.manga.model.
- Position
- Below the diagonal: eu.kanade.presentation.manga uses a module listed above it, which is the healthy direction.
39→22 eu.kanade.presentation.manga uses eu.kanade.tachiyomi.source✕
- Connections
- 1 pair of types, where a type in eu.kanade.presentation.manga uses a type in eu.kanade.tachiyomi.source.
- The types involved
eu.kanade.presentation.manga.DuplicateMangaDialogKt→eu.kanade.tachiyomi.source.Source
- Direction
- eu.kanade.presentation.manga uses eu.kanade.tachiyomi.source, so a change to eu.kanade.tachiyomi.source can break eu.kanade.presentation.manga, while a change to eu.kanade.presentation.manga can't break eu.kanade.tachiyomi.source.
- Position
- Below the diagonal: eu.kanade.presentation.manga uses a module listed above it, which is the healthy direction.
39→38 eu.kanade.presentation.manga uses eu.kanade.tachiyomi.ui.manga✕
- Connections
- 1 pair of types, where a type in eu.kanade.presentation.manga uses a type in eu.kanade.tachiyomi.ui.manga.
- The types involved
eu.kanade.presentation.manga.MangaScreenKt→eu.kanade.tachiyomi.ui.manga.ChapterList
- Direction
- eu.kanade.presentation.manga uses eu.kanade.tachiyomi.ui.manga, so a change to eu.kanade.tachiyomi.ui.manga can break eu.kanade.presentation.manga, while a change to eu.kanade.presentation.manga can't break eu.kanade.tachiyomi.ui.manga.
- Position
- Below the diagonal: eu.kanade.presentation.manga uses a module listed above it, which is the healthy direction.
40→1 eu.kanade.tachiyomi.ui.library uses eu.kanade.presentation.util✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.library uses a type in eu.kanade.presentation.util.
- The types involved
eu.kanade.tachiyomi.ui.library.LibraryTab→eu.kanade.presentation.util.Tab
- Direction
- eu.kanade.tachiyomi.ui.library uses eu.kanade.presentation.util, so a change to eu.kanade.presentation.util can break eu.kanade.tachiyomi.ui.library, while a change to eu.kanade.tachiyomi.ui.library can't break eu.kanade.presentation.util.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.library uses a module listed above it, which is the healthy direction.
40→6 eu.kanade.tachiyomi.ui.library uses tachiyomi.core.common.preference✕
- Connections
- 3 pairs of types, where a type in eu.kanade.tachiyomi.ui.library uses a type in tachiyomi.core.common.preference.
- The types involved
eu.kanade.tachiyomi.ui.library.LibrarySettingsViewModel→tachiyomi.core.common.preference.Preferenceeu.kanade.tachiyomi.ui.library.LibrarySettingsViewModel→tachiyomi.core.common.preference.TriStateeu.kanade.tachiyomi.ui.library.LibraryViewModel→tachiyomi.core.common.preference.TriState
- Direction
- eu.kanade.tachiyomi.ui.library uses tachiyomi.core.common.preference, so a change to tachiyomi.core.common.preference can break eu.kanade.tachiyomi.ui.library, while a change to eu.kanade.tachiyomi.ui.library can't break tachiyomi.core.common.preference.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.library uses a module listed above it, which is the healthy direction.
40→7 eu.kanade.tachiyomi.ui.library uses tachiyomi.domain.category.model✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.ui.library uses a type in tachiyomi.domain.category.model.
- The types involved
eu.kanade.tachiyomi.ui.library.LibrarySettingsViewModel→tachiyomi.domain.category.model.Categoryeu.kanade.tachiyomi.ui.library.LibraryViewModel→tachiyomi.domain.category.model.Category
- Direction
- eu.kanade.tachiyomi.ui.library uses tachiyomi.domain.category.model, so a change to tachiyomi.domain.category.model can break eu.kanade.tachiyomi.ui.library, while a change to eu.kanade.tachiyomi.ui.library can't break tachiyomi.domain.category.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.library uses a module listed above it, which is the healthy direction.
40→8 eu.kanade.tachiyomi.ui.library uses tachiyomi.domain.chapter.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.library uses a type in tachiyomi.domain.chapter.model.
- The types involved
eu.kanade.tachiyomi.ui.library.LibraryViewModel→tachiyomi.domain.chapter.model.Chapter
- Direction
- eu.kanade.tachiyomi.ui.library uses tachiyomi.domain.chapter.model, so a change to tachiyomi.domain.chapter.model can break eu.kanade.tachiyomi.ui.library, while a change to eu.kanade.tachiyomi.ui.library can't break tachiyomi.domain.chapter.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.library uses a module listed above it, which is the healthy direction.
40→9 eu.kanade.tachiyomi.ui.library uses tachiyomi.domain.track.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.library uses a type in tachiyomi.domain.track.model.
- The types involved
eu.kanade.tachiyomi.ui.library.LibraryViewModel→tachiyomi.domain.track.model.Track
- Direction
- eu.kanade.tachiyomi.ui.library uses tachiyomi.domain.track.model, so a change to tachiyomi.domain.track.model can break eu.kanade.tachiyomi.ui.library, while a change to eu.kanade.tachiyomi.ui.library can't break tachiyomi.domain.track.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.library uses a module listed above it, which is the healthy direction.
40→10 eu.kanade.tachiyomi.ui.library uses eu.kanade.domain.base✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.ui.library uses a type in eu.kanade.domain.base.
- The types involved
eu.kanade.tachiyomi.ui.library.LibrarySettingsViewModel→eu.kanade.domain.base.BasePreferenceseu.kanade.tachiyomi.ui.library.LibraryViewModel→eu.kanade.domain.base.BasePreferences
- Direction
- eu.kanade.tachiyomi.ui.library uses eu.kanade.domain.base, so a change to eu.kanade.domain.base can break eu.kanade.tachiyomi.ui.library, while a change to eu.kanade.tachiyomi.ui.library can't break eu.kanade.domain.base.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.library uses a module listed above it, which is the healthy direction.
40→15 eu.kanade.tachiyomi.ui.library uses tachiyomi.domain.manga.model✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.library uses a type in tachiyomi.domain.manga.model.
- The types involved
eu.kanade.tachiyomi.ui.library.LibraryViewModel→tachiyomi.domain.manga.model.Manga
- Direction
- eu.kanade.tachiyomi.ui.library uses tachiyomi.domain.manga.model, so a change to tachiyomi.domain.manga.model can break eu.kanade.tachiyomi.ui.library, while a change to eu.kanade.tachiyomi.ui.library can't break tachiyomi.domain.manga.model.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.library uses a module listed above it, which is the healthy direction.
40→18 eu.kanade.tachiyomi.ui.library uses tachiyomi.domain.library.service✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.ui.library uses a type in tachiyomi.domain.library.service.
- The types involved
eu.kanade.tachiyomi.ui.library.LibrarySettingsViewModel→tachiyomi.domain.library.service.LibraryPreferenceseu.kanade.tachiyomi.ui.library.LibraryViewModel→tachiyomi.domain.library.service.LibraryPreferences
- Direction
- eu.kanade.tachiyomi.ui.library uses tachiyomi.domain.library.service, so a change to tachiyomi.domain.library.service can break eu.kanade.tachiyomi.ui.library, while a change to eu.kanade.tachiyomi.ui.library can't break tachiyomi.domain.library.service.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.library uses a module listed above it, which is the healthy direction.
40→19 eu.kanade.tachiyomi.ui.library uses tachiyomi.domain.manga.interactor✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.library uses a type in tachiyomi.domain.manga.interactor.
- The types involved
eu.kanade.tachiyomi.ui.library.LibraryViewModel→tachiyomi.domain.manga.interactor.GetLibraryManga
- Direction
- eu.kanade.tachiyomi.ui.library uses tachiyomi.domain.manga.interactor, so a change to tachiyomi.domain.manga.interactor can break eu.kanade.tachiyomi.ui.library, while a change to eu.kanade.tachiyomi.ui.library can't break tachiyomi.domain.manga.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.library uses a module listed above it, which is the healthy direction.
40→20 eu.kanade.tachiyomi.ui.library uses tachiyomi.domain.source.service✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.library uses a type in tachiyomi.domain.source.service.
- The types involved
eu.kanade.tachiyomi.ui.library.LibraryViewModel→tachiyomi.domain.source.service.SourceManager
- Direction
- eu.kanade.tachiyomi.ui.library uses tachiyomi.domain.source.service, so a change to tachiyomi.domain.source.service can break eu.kanade.tachiyomi.ui.library, while a change to eu.kanade.tachiyomi.ui.library can't break tachiyomi.domain.source.service.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.library uses a module listed above it, which is the healthy direction.
40→23 eu.kanade.tachiyomi.ui.library uses tachiyomi.domain.category.interactor✕
- Connections
- 4 pairs of types, where a type in eu.kanade.tachiyomi.ui.library uses a type in tachiyomi.domain.category.interactor.
- The types involved
eu.kanade.tachiyomi.ui.library.LibrarySettingsViewModel→tachiyomi.domain.category.interactor.SetDisplayModeeu.kanade.tachiyomi.ui.library.LibrarySettingsViewModel→tachiyomi.domain.category.interactor.SetSortModeForCategoryeu.kanade.tachiyomi.ui.library.LibraryViewModel→tachiyomi.domain.category.interactor.GetCategorieseu.kanade.tachiyomi.ui.library.LibraryViewModel→tachiyomi.domain.category.interactor.SetMangaCategories
- Direction
- eu.kanade.tachiyomi.ui.library uses tachiyomi.domain.category.interactor, so a change to tachiyomi.domain.category.interactor can break eu.kanade.tachiyomi.ui.library, while a change to eu.kanade.tachiyomi.ui.library can't break tachiyomi.domain.category.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.library uses a module listed above it, which is the healthy direction.
40→24 eu.kanade.tachiyomi.ui.library uses tachiyomi.domain.chapter.interactor✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.ui.library uses a type in tachiyomi.domain.chapter.interactor.
- The types involved
eu.kanade.tachiyomi.ui.library.LibraryViewModel→tachiyomi.domain.chapter.interactor.GetBookmarkedChaptersByMangaIdeu.kanade.tachiyomi.ui.library.LibraryViewModel→tachiyomi.domain.chapter.interactor.GetChaptersByMangaId
- Direction
- eu.kanade.tachiyomi.ui.library uses tachiyomi.domain.chapter.interactor, so a change to tachiyomi.domain.chapter.interactor can break eu.kanade.tachiyomi.ui.library, while a change to eu.kanade.tachiyomi.ui.library can't break tachiyomi.domain.chapter.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.library uses a module listed above it, which is the healthy direction.
40→26 eu.kanade.tachiyomi.ui.library uses eu.kanade.tachiyomi.data.track✕
- Connections
- 3 pairs of types, where a type in eu.kanade.tachiyomi.ui.library uses a type in eu.kanade.tachiyomi.data.track.
- The types involved
eu.kanade.tachiyomi.ui.library.LibrarySettingsViewModel→eu.kanade.tachiyomi.data.track.BaseTrackereu.kanade.tachiyomi.ui.library.LibrarySettingsViewModel→eu.kanade.tachiyomi.data.track.TrackerManagereu.kanade.tachiyomi.ui.library.LibraryViewModel→eu.kanade.tachiyomi.data.track.TrackerManager
- Direction
- eu.kanade.tachiyomi.ui.library uses eu.kanade.tachiyomi.data.track, so a change to eu.kanade.tachiyomi.data.track can break eu.kanade.tachiyomi.ui.library, while a change to eu.kanade.tachiyomi.ui.library can't break eu.kanade.tachiyomi.data.track.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.library uses a module listed above it, which is the healthy direction.
40→34 eu.kanade.tachiyomi.ui.library uses eu.kanade.tachiyomi.data.download✕
- Connections
- 2 pairs of types, where a type in eu.kanade.tachiyomi.ui.library uses a type in eu.kanade.tachiyomi.data.download.
- The types involved
eu.kanade.tachiyomi.ui.library.LibraryViewModel→eu.kanade.tachiyomi.data.download.DownloadCacheeu.kanade.tachiyomi.ui.library.LibraryViewModel→eu.kanade.tachiyomi.data.download.DownloadManager
- Direction
- eu.kanade.tachiyomi.ui.library uses eu.kanade.tachiyomi.data.download, so a change to eu.kanade.tachiyomi.data.download can break eu.kanade.tachiyomi.ui.library, while a change to eu.kanade.tachiyomi.ui.library can't break eu.kanade.tachiyomi.data.download.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.library uses a module listed above it, which is the healthy direction.
40→35 eu.kanade.tachiyomi.ui.library uses eu.kanade.domain.chapter.interactor✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.library uses a type in eu.kanade.domain.chapter.interactor.
- The types involved
eu.kanade.tachiyomi.ui.library.LibraryViewModel→eu.kanade.domain.chapter.interactor.SetReadStatus
- Direction
- eu.kanade.tachiyomi.ui.library uses eu.kanade.domain.chapter.interactor, so a change to eu.kanade.domain.chapter.interactor can break eu.kanade.tachiyomi.ui.library, while a change to eu.kanade.tachiyomi.ui.library can't break eu.kanade.domain.chapter.interactor.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.library uses a module listed above it, which is the healthy direction.
40→39 eu.kanade.tachiyomi.ui.library uses eu.kanade.presentation.manga✕
- Connections
- 1 pair of types, where a type in eu.kanade.tachiyomi.ui.library uses a type in eu.kanade.presentation.manga.
- The types involved
eu.kanade.tachiyomi.ui.library.LibraryViewModel→eu.kanade.presentation.manga.DownloadAction
- Direction
- eu.kanade.tachiyomi.ui.library uses eu.kanade.presentation.manga, so a change to eu.kanade.presentation.manga can break eu.kanade.tachiyomi.ui.library, while a change to eu.kanade.tachiyomi.ui.library can't break eu.kanade.presentation.manga.
- Position
- Below the diagonal: eu.kanade.tachiyomi.ui.library 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 — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A07:2025 — Authentication Failures | 17 | High / Critical |
| A05:2025 — Injection | 6 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
Roadmap
Top priorities: Resolve the 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED (2); Resolve the 1 No ADRs found finding(s) in ADR Quality; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED (2). | +5.5 pts | Low | REDACTED Scanning |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +4.7 pts | Low | ADR Quality |
| Resolve the 8 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2), REDACTED. | +2.5 pts | Low | Secrets (history) |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +4.1 pts | Medium | Architecture documentation |
| 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. | +2.8 pts | Medium | Security & performance tooling |
| Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery). | +2.4 pts | Medium | DR & Backup |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +1.1 pts | Low | Bus Factor |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.1 pts | Low | Bus Factor |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.1 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 3.0 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 3.0 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 3.0 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| app/src/main/java/eu/kanade/tachiyomi/ui/library/LibraryViewModel.kt | 5.6 | Mixed | Cyclomatic Complexity: LibraryViewModel.applySort (cyclomatic 19) |
| app/src/main/java/eu/kanade/presentation/manga/components/MangaInfoHeader.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| app/src/main/java/eu/kanade/tachiyomi/data/library/LibraryUpdateWorker.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt | 7.0 | Near-clean | Cyclomatic Complexity: WebGpuViewer.decodeInto (cyclomatic 56) |
| app/src/main/java/eu/kanade/tachiyomi/ui/updates/UpdatesViewModel.kt | 7.0 | Near-clean | Cognitive Complexity: UpdatesViewModel.toggleSelection (cognitive 24) |
| app/src/main/java/eu/kanade/tachiyomi/ui/history/HistoryViewModel.kt | 7.0 | Near-clean | Code Duplication: Duplicated block (8–9 lines × 2) |
| app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderActivity.kt | 7.0 | Near-clean | Cyclomatic Complexity: ReaderActivity.onCreate (cyclomatic 26) |
| app/src/main/java/eu/kanade/tachiyomi/ui/manga/MangaViewModel.kt | 7.0 | Near-clean | Cognitive Complexity: MangaViewModel.toggleSelection (cognitive 24) |
| app/src/main/java/eu/kanade/tachiyomi/data/track/anilist/Anilist.kt | 7.0 | Near-clean | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderViewModel.kt | 7.1 | Near-clean | Cyclomatic Complexity: ReaderViewModel.loadChapterList (cyclomatic 17) |
| app/src/main/java/eu/kanade/tachiyomi/ui/main/MainActivity.kt | 7.2 | Near-clean | Cyclomatic Complexity: MainActivity.onCreate (cyclomatic 26) |
| app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewerSettings.kt | 7.2 | Near-clean | Cyclomatic Complexity: WebGpuViewerSettingsKt.WebGpuViewerSettings (cyclomatic 17) |
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 50 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 — 50 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, 393 of 407 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. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 21 Maven/Gradle manifest(s) were read, stating a version for 105 dependency(ies) and leaving 14 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (telemetry/build.gradle.kts), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `app/src/main/java/eu/kanade/presentation/browse/components/GlobalSearchToolbar.kt`, `app/src/main/java/eu/kanade/presentation/more/settings/screen/advanced/ClearDatabaseScreen.kt`, `app/src/main/java/eu/kanade/presentation/more/settings/screen/appearance/AppLanguageScreen.kt`, `app/src/main/java/eu/kanade/presentation/more/settings/screen/data/CreateBackupScreen.kt`, `app/src/main/java/eu/kanade/presentation/more/settings/screen/data/RestoreBackupScreen.kt`, … (+47 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Metro, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- AXR1 Runtime accessibility — 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. Boot via AndroidApp (app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: p.HttpURLConnection.connect(HttpURLConnection.java:1075) at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:181) at java.base/…; runtime evidence skipped (launch chosen because app/build.gradle.kts applies the Android application plugin and gradlew builds it).
- 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.
- DM8 Value-object opportunities — 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 finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
- 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 no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — 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 no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- 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.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- 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
30 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ImageUtil.chooseBackground at 70. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being DuplicateMangaDialogKt.DuplicateMangaListItem at 17 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: app/src/main/java/eu/kanade/presentation/manga/DuplicateMangaDialog.kt (DuplicateMangaDialogKt.DuplicateMangaListItem at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with ImageUtil.chooseBackground (cyclomatic 70), WebGpuViewer.decodeInto (cyclomatic 56). — 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 6.4 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
36 method(s) exceeded the cognitive complexity threshold of 15; the worst was ImageUtil.chooseBackground at 107.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with ImageUtil.chooseBackground (cognitive 107), WebGpuViewer.decodeInto (cognitive 82). — 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 5.9 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
D3 · God Classes
40 god class(es) detected.
What to do
- Resolve the 20 MethodTooLong finding(s) in God Classes — start with WebGpuViewer.kt, MangaScreen.kt, BrowseSourceScreen.kt. — One of this dimension's main actionable groups (20 warning-level).
- Resolve the 8 FileTooLong finding(s) in God Classes — start with WebGpuViewer.kt, MangaViewModel.kt, ReaderViewModel.kt. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 6 ClassTooLong finding(s) in God Classes — start with WebGpuViewer.kt, MangaViewModel.kt, ReaderViewModel.kt. — One of this dimension's main actionable groups (6 warning-level).
D4 · Code Duplication
56 duplicated block group(s) detected. A further 3 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 5 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with SettingsLibraryScreen.kt, SettingsReaderScreen.kt, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 5 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with MangaBottomActionMenu.kt, AnilistUtils.kt, ReaderViewModel.kt. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with MangaBaka.kt (2), MangaCoverDialog.kt, LibraryUpdateWorker.kt. — One of this dimension's main actionable groups (4 warning-level).
D5 · Coupling
17 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 2 module(s) off the main sequence, with abstractness counted on 13 of the 17 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
6 of 210 classes have LCOM4 above 3.
What to do
- Resolve the 6 Low cohesion finding(s) in Cohesion (LCOM4) — start with UpcomingViewModel.kt, StatsViewModel.kt, UpdatesViewModel.kt. — One of this dimension's main actionable groups (6 warning-level).
D13 · REDACTED Scanning
8 secret(s) detected.
What to do
- Resolve the 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (8 issue-level).
D14 · License Compliance
0 of 66 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 21 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. 14 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 39 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
Top hotspots: app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt (24×56=1344); app/src/main/java/eu/kanade/tachiyomi/ui/main/MainActivity.kt (15×26=390); app/src/main/java/eu/kanade/tachiyomi/extension/util/ExtensionLoader.kt (15×25=375) Repeated repair below the complexity floor: core/common/src/main/kotlin/eu/kanade/tachiyomi/network/interceptor/WebViewInterceptor.kt (3 of 4 changes were fixes)
What to do
- Resolve the 20 Hotspot finding(s) in Churn × Complexity Hotspots — start with WebGpuViewer.kt, MainActivity.kt, ExtensionLoader.kt. — One of this dimension's main actionable groups (20 warning-level).
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with WebViewInterceptor.kt. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
107 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is app/src/main/java/eu/kanade/tachiyomi/ui/main/MainActivity.kt. Counted over 412 of the 944 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
22 deducted task-comment markers across 87407 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 20 TodoComment finding(s) in Explicit Debt — start with Tracker.kt (2), AddTracks.kt (2), LocalSource.kt. — One of this dimension's main actionable groups (20 warning-level).
- Resolve the 2 HackComment finding(s) in Explicit Debt — start with GlanceUtils.kt, SearchableSettings.kt. — One of this dimension's main actionable groups (2 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 3 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 14 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)
8 finding(s): 0 critical, 8 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 8 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
6 finding(s): 0 critical, 1 high, 5 medium, 0 low. semgrep hit a parse error in 1 file(s) — `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 2 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 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-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).
D34 · Knowledge Freshness
90 of 412 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is presentation-core/src/main/java/tachiyomi/presentation/core/components/material/Button.kt. Counted over 412 of the 944 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 90 Orphaned file finding(s) in Knowledge Freshness — start with Button.kt, WheelPicker.kt, MangaChapterListItem.kt. — One of this dimension's main actionable groups (90 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: ReaderAppBars.kt↔ReaderActivity.kt 86%; MangaBackupCreator.kt↔MangaRestorer.kt 75%; SourcePreferences.kt↔SettingsBrowseScreen.kt 70%
What to do
- Resolve the 9 Change coupling finding(s) in Change Coupling — start with ReaderAppBars.kt, MangaBackupCreator.kt, SourcePreferences.kt. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with MangaRepositoryImpl.kt. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 105 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
- `:domain` is a Domain project but references `:source-api`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
What to do
- Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion).
AX8 · Test isolation
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM12 · Ambient inputs in the domain
DM6 · Domain ↔ infrastructure boundary
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Describe the projects a newcomer cannot place from the root README: 17 of 18 have no README of their own, in their folder or in their family's project (`app`, `baseline-profile`, `core-metadata`, `data`, `domain` and 12 more).
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
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 3 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. — .github/workflows/build.yml:3
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.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
P6 · Release Hygiene
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X16 · Unfloored truncation loop
X2 · Cancellation propagation
X21 · Side-effecting pattern guard
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `catch (e: 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. (×10) — domain/src/main/java/tachiyomi/domain/library/model/LibrarySortMode.kt:114, domain/src/main/java/tachiyomi/domain/chapter/interactor/GetChapterByUrlAndMangaId.kt:15, core/common/src/main/kotlin/tachiyomi/core/common/preference/AndroidPreference.kt:185, …
- `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. (×22) — data/src/main/java/mihon/data/extension/service/ExtensionStoreService.kt:124, core/common/src/main/kotlin/tachiyomi/core/common/preference/AndroidPreference.kt:227, core/common/src/main/kotlin/eu/kanade/tachiyomi/util/storage/DiskUtil.kt:58, …
- 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) — core/common/src/main/kotlin/eu/kanade/tachiyomi/network/OkHttpExtensions.kt:82, app/src/main/java/mihon/feature/migration/list/MigrationListViewModel.kt:170, app/src/main/java/eu/kanade/tachiyomi/App.kt:281, …
What to do
- Swallowed exception (caught, then discarded)
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 80% | Strong | Solid. |
| Architecture | 79% | Strong | Solid. |
| Maturity | 54% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 53% | Adequate — gated by D13, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 59% | Adequate — gated by D28 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Performance | 94% | Exemplary | Solid. |
Unscored — 3 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X9 Subsumed condition operand — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 77 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the Android app did not build — `./gradlew :app:assembleDebug` exited 1: p.HttpURLConnection.connect(HttpURLConnection.java:1075) at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:181) at java.base/…; runtime evidence skipped (launch chosen because app/build.gradle.kts applies the Android application plugin and gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
- 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 — ~1675 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 — the .kt suite was found but not re-run
- D12 Dependency Hygiene — Not scored — 21 Maven/Gradle manifest(s) were read, stating a version for 105 dependency(ies) and leaving 14 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Kotlin not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 52 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- D9 Test Distribution — Test source is present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 JVM source (14 module(s), 924 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 source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- 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.
- 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.
- 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
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 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
- 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
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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.
Appendix A — Findings (grouped)
Critical — 18 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Dependency-rule violation: :domain (Domain) → :source-api (Web)
- REDACTED
Serious — 271 finding(s)
- Swallowed exception (caught, then discarded) domain/src/main/java/tachiyomi/domain/library/model/LibrarySortMode.kt:114
- Swallowed exception (caught, then discarded) domain/src/main/java/tachiyomi/domain/chapter/interactor/GetChapterByUrlAndMangaId.kt:15
- Swallowed exception (caught, then discarded) data/src/main/java/mihon/data/extension/service/ExtensionStoreService.kt:124
- Swallowed exception (caught, then discarded) core/common/src/main/kotlin/tachiyomi/core/common/preference/AndroidPreference.kt:185
- Swallowed exception (caught, then discarded) core/common/src/main/kotlin/tachiyomi/core/common/preference/AndroidPreference.kt:206
- Swallowed exception (caught, then discarded) core/common/src/main/kotlin/tachiyomi/core/common/preference/AndroidPreference.kt:227
- Swallowed exception (caught, then discarded) core/common/src/main/kotlin/eu/kanade/tachiyomi/util/system/DeviceUtil.kt:42
- Swallowed exception (caught, then discarded) core/common/src/main/kotlin/eu/kanade/tachiyomi/util/system/DeviceUtil.kt:60
- Swallowed exception (caught, then discarded) core/common/src/main/kotlin/eu/kanade/tachiyomi/util/storage/DiskUtil.kt:58
- Swallowed exception (caught, then discarded) core/common/src/main/kotlin/eu/kanade/tachiyomi/util/storage/DiskUtil.kt:70
- Swallowed exception (caught, then discarded) core/common/src/main/kotlin/eu/kanade/tachiyomi/util/storage/DiskUtil.kt:82
- Swallowed exception (caught, then discarded) app/src/main/java/mihon/feature/migration/list/MigrationListViewModel.kt:213
- Swallowed exception (caught, then discarded) app/src/main/java/mihon/feature/migration/list/MigrationListViewModel.kt:242
- Swallowed exception (caught, then discarded) app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderViewModel.kt:1032
- Swallowed exception (caught, then discarded) app/src/main/java/eu/kanade/tachiyomi/ui/manga/MangaScreen.kt:316
- Swallowed exception (caught, then discarded) app/src/main/java/eu/kanade/tachiyomi/data/track/suwayomi/Suwayomi.kt:101
- Swallowed exception (caught, then discarded) app/src/main/java/eu/kanade/tachiyomi/data/track/shikimori/Shikimori.kt:158
- Swallowed exception (caught, then discarded) app/src/main/java/eu/kanade/tachiyomi/data/track/myanimelist/MyAnimeList.kt:180
- Swallowed exception (caught, then discarded) app/src/main/java/eu/kanade/tachiyomi/data/track/myanimelist/MyAnimeListApi.kt:263
- Swallowed exception (caught, then discarded) app/src/main/java/eu/kanade/tachiyomi/data/track/mangaupdates/MangaUpdatesApi.kt:130
- Swallowed exception (caught, then discarded) app/src/main/java/eu/kanade/tachiyomi/data/track/mangabaka/MangaBaka.kt:174
- Swallowed exception (caught, then discarded) app/src/main/java/eu/kanade/tachiyomi/data/track/komga/Komga.kt:108
- Swallowed exception (caught, then discarded) app/src/main/java/eu/kanade/tachiyomi/data/track/kitsu/Kitsu.kt:231
- Swallowed exception (caught, then discarded) REDACTED:108
- Swallowed exception (caught, then discarded) app/src/main/java/eu/kanade/tachiyomi/data/track/hikka/Hikka.kt:190
- Hotspot: app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt:1334
- Hotspot: app/src/main/java/eu/kanade/tachiyomi/ui/main/MainActivity.kt app/src/main/java/eu/kanade/tachiyomi/ui/main/MainActivity.kt:168
- Hotspot: app/src/main/java/eu/kanade/tachiyomi/extension/util/ExtensionLoader.kt app/src/main/java/eu/kanade/tachiyomi/extension/util/ExtensionLoader.kt:295
- Hotspot: app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderActivity.kt app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderActivity.kt:169
- Hotspot: app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderViewModel.kt app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderViewModel.kt:220
- Hotspot: app/src/main/java/eu/kanade/domain/chapter/interactor/SyncChaptersWithSource.kt app/src/main/java/eu/kanade/domain/chapter/interactor/SyncChaptersWithSource.kt:52
- Hotspot: app/src/main/java/eu/kanade/tachiyomi/ui/library/LibraryViewModel.kt app/src/main/java/eu/kanade/tachiyomi/ui/library/LibraryViewModel.kt:304
- Hotspot: app/src/main/java/eu/kanade/tachiyomi/ui/manga/MangaScreen.kt app/src/main/java/eu/kanade/tachiyomi/ui/manga/MangaScreen.kt:75
- Hotspot: app/src/main/java/eu/kanade/presentation/browse/ExtensionsScreen.kt app/src/main/java/eu/kanade/presentation/browse/ExtensionsScreen.kt:140
- Hotspot: app/src/main/java/eu/kanade/tachiyomi/ui/library/LibraryTab.kt app/src/main/java/eu/kanade/tachiyomi/ui/library/LibraryTab.kt:84
- Hotspot: core/common/src/main/kotlin/eu/kanade/tachiyomi/network/interceptor/CloudflareInterceptor.kt core/common/src/main/kotlin/eu/kanade/tachiyomi/network/interceptor/CloudflareInterceptor.kt:119
- Hotspot: app/src/main/java/mihon/domain/migration/usecases/MigrateMangaUseCase.kt app/src/main/java/mihon/domain/migration/usecases/MigrateMangaUseCase.kt:48
- Hotspot: app/src/main/java/eu/kanade/presentation/manga/components/MangaInfoHeader.kt app/src/main/java/eu/kanade/presentation/manga/components/MangaInfoHeader.kt:433
- Hotspot: app/src/main/java/eu/kanade/tachiyomi/data/notification/NotificationReceiver.kt app/src/main/java/eu/kanade/tachiyomi/data/notification/NotificationReceiver.kt:57
- Hotspot: app/src/main/java/eu/kanade/presentation/webview/WebViewScreenContent.kt app/src/main/java/eu/kanade/presentation/webview/WebViewScreenContent.kt:76
- Hotspot: app/src/main/java/eu/kanade/tachiyomi/ui/browse/source/browse/BrowseSourceScreen.kt app/src/main/java/eu/kanade/tachiyomi/ui/browse/source/browse/BrowseSourceScreen.kt:78
- Hotspot: app/src/main/java/eu/kanade/presentation/manga/DuplicateMangaDialog.kt app/src/main/java/eu/kanade/presentation/manga/DuplicateMangaDialog.kt:173
- Hotspot: core/common/src/main/kotlin/eu/kanade/tachiyomi/network/NetworkHelper.kt core/common/src/main/kotlin/eu/kanade/tachiyomi/network/NetworkHelper.kt:29
- Hotspot: app/src/main/java/eu/kanade/presentation/more/settings/PreferenceItem.kt app/src/main/java/eu/kanade/presentation/more/settings/PreferenceItem.kt:64
- Hotspot: app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewerSettings.kt app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewerSettings.kt:77
- TodoComment source-local/src/main/kotlin/tachiyomi/source/local/LocalSource.kt:189
- TodoComment source-api/src/main/kotlin/eu/kanade/tachiyomi/source/ConfigurableSource.kt:24
- TodoComment core/common/src/main/kotlin/tachiyomi/core/common/i18n/Localize.kt:28
- TodoComment baseline-profile/src/main/kotlin/mihon/baselineprofile/StartupBenchmarks.kt:87
- TodoComment app/src/main/java/eu/kanade/tachiyomi/util/system/DisplayExtensions.kt:23
- TodoComment app/src/main/java/eu/kanade/tachiyomi/ui/manga/MangaCoverViewModel.kt:119
- TodoComment app/src/main/java/eu/kanade/tachiyomi/data/track/BaseTracker.kt:47
- TodoComment app/src/main/java/eu/kanade/tachiyomi/data/track/Tracker.kt:42
- TodoComment app/src/main/java/eu/kanade/tachiyomi/data/track/Tracker.kt:82
- TodoComment app/src/main/java/eu/kanade/tachiyomi/data/track/myanimelist/MyAnimeListInterceptor.kt:35
- TodoComment app/src/main/java/eu/kanade/tachiyomi/data/library/LibraryUpdateWorker.kt:233
- TodoComment app/src/main/java/eu/kanade/tachiyomi/data/backup/restore/BackupRestorer.kt:150
- TodoComment app/src/main/java/eu/kanade/presentation/track/TrackInfoDialogHome.kt:119
- TodoComment app/src/main/java/eu/kanade/presentation/more/settings/screen/SettingsAdvancedScreen.kt:396
- TodoComment app/src/main/java/eu/kanade/presentation/manga/components/MangaInfoHeader.kt:193
- TodoComment app/src/main/java/eu/kanade/presentation/library/LibrarySettingsDialog.kt:118
- TodoComment app/src/main/java/eu/kanade/presentation/browse/components/GlobalSearchToolbar.kt:78
- TodoComment app/src/main/java/eu/kanade/domain/track/interactor/AddTracks.kt:30
- TodoComment app/src/main/java/eu/kanade/domain/track/interactor/AddTracks.kt:40
- TodoComment app/src/main/java/eu/kanade/domain/manga/model/Manga.kt:16
- MethodTooLong: WebGpuViewer.decodeInto app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt:1334
- MethodTooLong: MangaScreen.Content app/src/main/java/eu/kanade/tachiyomi/ui/manga/MangaScreen.kt:75
- MethodTooLong: BrowseSourceScreen.Content app/src/main/java/eu/kanade/tachiyomi/ui/browse/source/browse/BrowseSourceScreen.kt:78
- MethodTooLong: ReaderActivity.onCreate app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderActivity.kt:169
- MethodTooLong: ImageUtil.chooseBackground core/common/src/main/kotlin/tachiyomi/core/common/util/system/ImageUtil.kt:215
- MethodTooLong: WebGpuViewerSettingsKt.WebGpuViewerSettings app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewerSettings.kt:77
- MethodTooLong: LibraryTab.Content app/src/main/java/eu/kanade/tachiyomi/ui/library/LibraryTab.kt:84
- MethodTooLong: MangaCoverDialogKt.MangaCoverDialog app/src/main/java/eu/kanade/presentation/manga/components/MangaCoverDialog.kt:73
- MethodTooLong: DownloadQueueScreen.Content app/src/main/java/eu/kanade/tachiyomi/ui/download/DownloadQueueScreen.kt:54
- MethodTooLong: SyncChaptersWithSource.await app/src/main/java/eu/kanade/domain/chapter/interactor/SyncChaptersWithSource.kt:52
- MethodTooLong: ExtensionDetailsScreenKt.DetailsHeader app/src/main/java/eu/kanade/presentation/browse/ExtensionDetailsScreen.kt:194
- MethodTooLong: ExtensionLoader.loadExtension app/src/main/java/eu/kanade/tachiyomi/extension/util/ExtensionLoader.kt:295
- MethodTooLong: AdaptiveSheetKt.AdaptiveSheet presentation-core/src/main/java/tachiyomi/presentation/core/components/AdaptiveSheet.kt:53
- MethodTooLong: PreferenceItemKt.PreferenceItem app/src/main/java/eu/kanade/presentation/more/settings/PreferenceItem.kt:64
- MethodTooLong: MangaInfoHeaderKt.MangaContentInfo app/src/main/java/eu/kanade/presentation/manga/components/MangaInfoHeader.kt:433
- MethodTooLong: MangaChapterListItemKt.MangaChapterListItem app/src/main/java/eu/kanade/presentation/manga/components/MangaChapterListItem.kt:49
- MethodTooLong: TrackerSearchKt.TrackerSearch app/src/main/java/eu/kanade/presentation/track/TrackerSearch.kt:91
- MethodTooLong: MainActivity.onCreate app/src/main/java/eu/kanade/tachiyomi/ui/main/MainActivity.kt:168
- MethodTooLong: ExtensionsScreenKt.ExtensionContent app/src/main/java/eu/kanade/presentation/browse/ExtensionsScreen.kt:140
- MethodTooLong: MigrationConfigScreen.<init> app/src/main/java/mihon/feature/migration/config/MigrationConfigScreen.kt:80
- Change coupling: ReaderAppBars.kt ↔ ReaderActivity.kt app/src/main/java/eu/kanade/presentation/reader/appbars/ReaderAppBars.kt:1
- Change coupling: MangaBackupCreator.kt ↔ MangaRestorer.kt app/src/main/java/eu/kanade/tachiyomi/data/backup/create/creators/MangaBackupCreator.kt:1
- Change coupling: SourcePreferences.kt ↔ SettingsBrowseScreen.kt app/src/main/java/eu/kanade/domain/source/service/SourcePreferences.kt:1
- Change coupling: UpdatesScreen.kt ↔ UpdatesTab.kt app/src/main/java/eu/kanade/presentation/updates/UpdatesScreen.kt:1
- Change coupling: HistoryScreen.kt ↔ HistoryItem.kt app/src/main/java/eu/kanade/presentation/history/HistoryScreen.kt:1
- Change coupling: MigrateSearchScreen.kt ↔ MigrateSearchViewModel.kt app/src/main/java/eu/kanade/presentation/browse/MigrateSearchScreen.kt:1
- Change coupling: HomeScreen.kt ↔ SettingsScreen.kt app/src/main/java/eu/kanade/tachiyomi/ui/home/HomeScreen.kt:1
- Change coupling: TabbedScreen.kt ↔ LibraryTabs.kt app/src/main/java/eu/kanade/presentation/components/TabbedScreen.kt:1
- Change coupling: GlobalSearchScreen.kt ↔ MigrateSearchViewModel.kt app/src/main/java/eu/kanade/presentation/browse/GlobalSearchScreen.kt:1
- FileTooLong: webgpu/WebGpuViewer.kt app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt
- FileTooLong: manga/MangaViewModel.kt app/src/main/java/eu/kanade/tachiyomi/ui/manga/MangaViewModel.kt
- FileTooLong: reader/ReaderViewModel.kt app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderViewModel.kt
- FileTooLong: track/TrackInfoDialog.kt app/src/main/java/eu/kanade/tachiyomi/ui/manga/track/TrackInfoDialog.kt
- FileTooLong: manga/MangaScreen.kt app/src/main/java/eu/kanade/presentation/manga/MangaScreen.kt
- FileTooLong: library/LibraryViewModel.kt app/src/main/java/eu/kanade/tachiyomi/ui/library/LibraryViewModel.kt
- FileTooLong: components/MangaInfoHeader.kt app/src/main/java/eu/kanade/presentation/manga/components/MangaInfoHeader.kt
- FileTooLong: reader/ReaderActivity.kt app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderActivity.kt
- ClassTooLong: WebGpuViewer app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt:86
- ClassTooLong: MangaViewModel app/src/main/java/eu/kanade/tachiyomi/ui/manga/MangaViewModel.kt:114
- ClassTooLong: ReaderViewModel app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderViewModel.kt:104
- ClassTooLong: LibraryViewModel app/src/main/java/eu/kanade/tachiyomi/ui/library/LibraryViewModel.kt:83
- ClassTooLong: ReaderActivity app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderActivity.kt:124
- ClassTooLong: Downloader app/src/main/java/eu/kanade/tachiyomi/data/download/Downloader.kt:78
- TooManyMethods: MangaViewModel app/src/main/java/eu/kanade/tachiyomi/ui/manga/MangaViewModel.kt:114
- TooManyMethods: WebGpuViewer app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt:86
- TooManyMethods: ReaderViewModel app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderViewModel.kt:104
- TooManyMethods: ReaderActivity app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderActivity.kt:124
- TooManyMethods: Downloader app/src/main/java/eu/kanade/tachiyomi/data/download/Downloader.kt:78
- TooManyMethods: HttpSource REDACTED:28
- Low cohesion: UpcomingViewModel (LCOM4 7) app/src/main/java/mihon/feature/upcoming/UpcomingViewModel.kt:45
- Low cohesion: StatsViewModel (LCOM4 5) app/src/main/java/eu/kanade/tachiyomi/ui/stats/StatsViewModel.kt:37
- Low cohesion: UpdatesViewModel (LCOM4 5) app/src/main/java/eu/kanade/tachiyomi/ui/updates/UpdatesViewModel.kt:71
- Low cohesion: ExtensionsViewModel (LCOM4 4) app/src/main/java/eu/kanade/tachiyomi/ui/browse/extension/ExtensionsViewModel.kt:46
- Low cohesion: HistoryViewModel (LCOM4 4) app/src/main/java/eu/kanade/tachiyomi/ui/history/HistoryViewModel.kt:60
- Low cohesion: LibraryViewModel (LCOM4 4) app/src/main/java/eu/kanade/tachiyomi/ui/library/LibraryViewModel.kt:83
- Swallowed exception (empty catch) core/common/src/main/kotlin/eu/kanade/tachiyomi/network/OkHttpExtensions.kt:82
- Swallowed exception (empty catch) app/src/main/java/mihon/feature/migration/list/MigrationListViewModel.kt:170
- Swallowed exception (empty catch) app/src/main/java/eu/kanade/tachiyomi/App.kt:281
- Swallowed exception (empty catch) app/src/main/java/eu/kanade/tachiyomi/data/library/LibraryUpdateWorker.kt:421
- Swallowed exception (empty catch) app/src/main/java/eu/kanade/tachiyomi/data/coil/MangaCoverFetcher.kt:270
- Swallowed exception (empty catch) app/src/main/java/eu/kanade/tachiyomi/data/backup/restore/BackupRestorer.kt:292
- Duplicated block (10 lines × 2) app/src/main/java/eu/kanade/presentation/more/settings/screen/SettingsLibraryScreen.kt:221
- Duplicated block (10 lines × 2) app/src/main/java/eu/kanade/presentation/more/settings/screen/SettingsReaderScreen.kt:212
- Duplicated block (10 lines × 2) REDACTED:42
- Duplicated block (10 lines × 2) REDACTED:67
- Duplicated block (10 lines × 2) app/src/main/java/eu/kanade/tachiyomi/ui/updates/UpdatesSettingsViewModel.kt:27
- Duplicated block (8 lines × 2) app/src/main/java/eu/kanade/presentation/manga/components/MangaBottomActionMenu.kt:85
- Duplicated block (8 lines × 2) app/src/main/java/eu/kanade/tachiyomi/data/track/anilist/AnilistUtils.kt:49
- Duplicated block (8 lines × 2) app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderViewModel.kt:837
- Duplicated block (8 lines × 2) app/src/main/java/eu/kanade/tachiyomi/data/track/bangumi/Bangumi.kt:97
- Duplicated block (8 lines × 2) app/src/main/java/eu/kanade/presentation/manga/DuplicateMangaDialog.kt:248
- Duplicated block (11 lines × 2) app/src/main/java/eu/kanade/presentation/manga/components/MangaCoverDialog.kt:196
- Duplicated block (11 lines × 2) app/src/main/java/eu/kanade/tachiyomi/data/track/mangabaka/MangaBaka.kt:95
- Duplicated block (11 lines × 2) app/src/main/java/eu/kanade/tachiyomi/data/track/mangabaka/MangaBaka.kt:136
- Duplicated block (11 lines × 2) app/src/main/java/eu/kanade/tachiyomi/data/library/LibraryUpdateWorker.kt:151
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (12 lines × 2) app/src/main/java/eu/kanade/presentation/components/TabbedDialog.kt:88
- Duplicated block (12 lines × 2) app/src/main/java/eu/kanade/tachiyomi/data/notification/NotificationReceiver.kt:406
- Duplicated block (12 lines × 2) app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderActivity.kt:442
- Duplicated block (9 lines × 2) app/src/main/java/eu/kanade/presentation/manga/components/MangaBottomActionMenu.kt:95
- Duplicated block (9 lines × 2) app/src/main/java/eu/kanade/presentation/more/settings/screen/SettingsReaderScreen.kt:202
- Duplicated block (9 lines × 2) app/src/main/java/eu/kanade/tachiyomi/data/track/comick/ComickApi.kt:307
- HackComment presentation-widget/src/main/java/tachiyomi/presentation/widget/util/GlanceUtils.kt:34
- HackComment app/src/main/java/eu/kanade/presentation/more/settings/screen/SearchableSettings.kt:37
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) app/src/main/java/eu/kanade/tachiyomi/data/track/anilist/Anilist.kt:187
- Members sharing a duplicated core (4 members, 50+ identical tokens) app/src/main/java/eu/kanade/tachiyomi/data/track/anilist/Anilist.kt:207
- Duplicated block (17 lines × 2) app/src/main/java/eu/kanade/tachiyomi/ui/manga/MangaViewModel.kt:822
- Duplicated block (17 lines × 2) app/src/main/java/eu/kanade/tachiyomi/ui/manga/MangaViewModel.kt:1004
- Duplicated block (16 lines × 2) app/src/main/java/eu/kanade/presentation/browse/components/BrowseSourceComfortableGrid.kt:65
- Duplicated block (16 lines × 2) app/src/main/java/eu/kanade/tachiyomi/ui/manga/MangaViewModel.kt:575
- Duplicated block (15 lines × 2) app/src/main/java/eu/kanade/presentation/history/components/HistoryDialogs.kt:75
- Duplicated block (15 lines × 2) app/src/main/java/eu/kanade/presentation/reader/settings/ReadingModePage.kt:86
- Duplicated block (14 lines × 2) app/src/main/java/eu/kanade/presentation/browse/components/BrowseSourceComfortableGrid.kt:29
- Duplicated block (14 lines × 2) app/src/main/java/eu/kanade/presentation/browse/components/BrowseSourceDialogs.kt:17
- Duplicated block (13 lines × 3) app/src/main/java/eu/kanade/presentation/category/components/CategoryDialogs.kt:166
- Duplicated block (13 lines × 3) app/src/main/java/eu/kanade/tachiyomi/data/track/anilist/Anilist.kt:161
- Duplicated block (13 lines × 2) app/src/main/java/eu/kanade/presentation/browse/components/BrowseSourceComfortableGrid.kt:44
- Duplicated block (13 lines × 2) app/src/main/java/eu/kanade/presentation/more/settings/screen/SettingsReaderScreen.kt:260
- Duplicated block (7 lines × 2) app/src/main/java/eu/kanade/tachiyomi/data/notification/NotificationReceiver.kt:87
- Duplicated block (7 lines × 2) app/src/main/java/eu/kanade/tachiyomi/data/track/comick/Comick.kt:127
- ImageUtil.chooseBackground (cyclomatic 70) core/common/src/main/kotlin/tachiyomi/core/common/util/system/ImageUtil.kt:215
- WebGpuViewer.decodeInto (cyclomatic 56) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt:1334
- SyncChaptersWithSource.await (cyclomatic 28) app/src/main/java/eu/kanade/domain/chapter/interactor/SyncChaptersWithSource.kt:52
- MainActivity.onCreate (cyclomatic 26) app/src/main/java/eu/kanade/tachiyomi/ui/main/MainActivity.kt:168
- ReaderActivity.onCreate (cyclomatic 26) app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderActivity.kt:169
- WebGpuViewer.startPageLoad (cyclomatic 26) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt:1096
- ExtensionLoader.loadExtension (cyclomatic 25) app/src/main/java/eu/kanade/tachiyomi/extension/util/ExtensionLoader.kt:295
- MangaScreen.Content (cyclomatic 23) app/src/main/java/eu/kanade/tachiyomi/ui/manga/MangaScreen.kt:75
- ReaderActivity.onKeyEvent (cyclomatic 23) app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderActivity.kt:483
- WebGpuViewer.evictFarthestPage (cyclomatic 23) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt:378
- WebGpuViewer.onPageSettingsChanged (cyclomatic 23) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt:877
- ExtensionsScreenKt.ExtensionContent (cyclomatic 21) app/src/main/java/eu/kanade/presentation/browse/ExtensionsScreen.kt:140
- WebViewScreenContentKt.WebViewScreenContent (cyclomatic 21) app/src/main/java/eu/kanade/presentation/webview/WebViewScreenContent.kt:76
- Detector.onTouchEvent (cyclomatic 21) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webtoon/WebtoonRecyclerView.kt:292
- MangaInfoHeaderKt.MangaContentInfo (cyclomatic 20) app/src/main/java/eu/kanade/presentation/manga/components/MangaInfoHeader.kt:433
- MainActivity.handleIntentAction (cyclomatic 20) app/src/main/java/eu/kanade/tachiyomi/ui/main/MainActivity.kt:589
- WebGpuViewer.startStreamDecode (cyclomatic 20) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt:1239
- PreferenceItemKt.PreferenceItem (cyclomatic 19) app/src/main/java/eu/kanade/presentation/more/settings/PreferenceItem.kt:64
- LibraryViewModel.applySort (cyclomatic 19) app/src/main/java/eu/kanade/tachiyomi/ui/library/LibraryViewModel.kt:304
- MigrationListViewModel.runMigrations (cyclomatic 19) app/src/main/java/mihon/feature/migration/list/MigrationListViewModel.kt:124
- CloudflareInterceptor.resolveWithWebView (cyclomatic 19) core/common/src/main/kotlin/eu/kanade/tachiyomi/network/interceptor/CloudflareInterceptor.kt:119
- TriStateListDialogKt.TriStateListDialog (cyclomatic 18) app/src/main/java/eu/kanade/presentation/more/settings/widget/TriStateListDialog.kt:41
- PreferenceRestorer.restorePreferences (cyclomatic 17) app/src/main/java/eu/kanade/tachiyomi/data/backup/restore/restorers/PreferenceRestorer.kt:53
- LibraryTab.Content (cyclomatic 17) app/src/main/java/eu/kanade/tachiyomi/ui/library/LibraryTab.kt:84
- ReaderViewModel.loadChapterList (cyclomatic 17) app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderViewModel.kt:220
- WebGpuViewerSettingsKt.WebGpuViewerSettings (cyclomatic 17) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewerSettings.kt:77
- LibraryUpdateWorker.addMangaToQueue (cyclomatic 16) app/src/main/java/eu/kanade/tachiyomi/data/library/LibraryUpdateWorker.kt:168
- BrowseSourceScreen.Content (cyclomatic 16) app/src/main/java/eu/kanade/tachiyomi/ui/browse/source/browse/BrowseSourceScreen.kt:78
- ChapterRecognition.fillChapterNumbers (cyclomatic 16) domain/src/main/java/tachiyomi/domain/chapter/service/ChapterRecognition.kt:196
- ButtonElevation.animateElevation (cyclomatic 16) presentation-core/src/main/java/tachiyomi/presentation/core/components/material/Button.kt:236
- Repeated repair: core/common/src/main/kotlin/eu/kanade/tachiyomi/network/interceptor/WebViewInterceptor.kt core/common/src/main/kotlin/eu/kanade/tachiyomi/network/interceptor/WebViewInterceptor.kt:53
- ImageUtil.chooseBackground (cognitive 107) core/common/src/main/kotlin/tachiyomi/core/common/util/system/ImageUtil.kt:215
- WebGpuViewer.decodeInto (cognitive 82) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt:1334
- SyncChaptersWithSource.await (cognitive 40) app/src/main/java/eu/kanade/domain/chapter/interactor/SyncChaptersWithSource.kt:52
- Detector.onTouchEvent (cognitive 37) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webtoon/WebtoonRecyclerView.kt:292
- MigrationListViewModel.runMigrations (cognitive 36) app/src/main/java/mihon/feature/migration/list/MigrationListViewModel.kt:124
- MainActivity.onCreate (cognitive 30) app/src/main/java/eu/kanade/tachiyomi/ui/main/MainActivity.kt:168
- WebGpuViewer.evictFarthestPage (cognitive 26) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt:378
- CloudflareInterceptor.resolveWithWebView (cognitive 26) core/common/src/main/kotlin/eu/kanade/tachiyomi/network/interceptor/CloudflareInterceptor.kt:119
- ExtensionLoader.loadExtension (cognitive 25) app/src/main/java/eu/kanade/tachiyomi/extension/util/ExtensionLoader.kt:295
- WebGpuViewer.startPageLoad (cognitive 25) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt:1096
- MangaViewModel.toggleSelection (cognitive 24) app/src/main/java/eu/kanade/tachiyomi/ui/manga/MangaViewModel.kt:988
- UpdatesViewModel.toggleSelection (cognitive 24) app/src/main/java/eu/kanade/tachiyomi/ui/updates/UpdatesViewModel.kt:375
- WebViewScreenContentKt.WebViewScreenContent (cognitive 23) app/src/main/java/eu/kanade/presentation/webview/WebViewScreenContent.kt:76
- PreferenceRestorer.restorePreferences (cognitive 23) app/src/main/java/eu/kanade/tachiyomi/data/backup/restore/restorers/PreferenceRestorer.kt:53
- BrowseSourceViewModel.searchGenre (cognitive 23) app/src/main/java/eu/kanade/tachiyomi/ui/browse/source/browse/BrowseSourceViewModel.kt:191
- ReaderViewModel.loadChapterList (cognitive 23) app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderViewModel.kt:220
- BaseSmartSearchEngine.removeTextInBrackets (cognitive 22) app/src/main/java/mihon/feature/migration/list/search/BaseSmartSearchEngine.kt:97
- MangaScreen.Content (cognitive 21) app/src/main/java/eu/kanade/tachiyomi/ui/manga/MangaScreen.kt:75
- ReaderActivity.onKeyEvent (cognitive 21) app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderActivity.kt:483
- WebGpuViewer.startStreamDecode (cognitive 20) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt:1239
- WebGpuViewerSettingsKt.ShaderParams (cognitive 20) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewerSettings.kt:480
- MangaInfoHeaderKt.MangaActionRow (cognitive 19) app/src/main/java/eu/kanade/presentation/manga/components/MangaInfoHeader.kt:178
- MangaViewModel.toggleFavorite (cognitive 19) app/src/main/java/eu/kanade/tachiyomi/ui/manga/MangaViewModel.kt:415
- RateLimitInterceptor.intercept (cognitive 19) core/common/src/main/kotlin/eu/kanade/tachiyomi/network/interceptor/RateLimitInterceptor.kt:68
- ExtensionsScreenKt.ExtensionContent (cognitive 18) app/src/main/java/eu/kanade/presentation/browse/ExtensionsScreen.kt:140
- ReaderActivity.onCreate (cognitive 18) app/src/main/java/eu/kanade/tachiyomi/ui/reader/ReaderActivity.kt:169
- WebGpuViewer.moveToPage (cognitive 18) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt:1879
- MigrateMangaUseCase.invoke (cognitive 18) app/src/main/java/mihon/domain/migration/usecases/MigrateMangaUseCase.kt:48
- MigrationConfigScreen.Content (cognitive 18) app/src/main/java/mihon/feature/migration/config/MigrationConfigScreen.kt:83
- ChapterRecognition.fillChapterNumbers (cognitive 18) domain/src/main/java/tachiyomi/domain/chapter/service/ChapterRecognition.kt:196
- LibraryViewModel.applySort (cognitive 17) app/src/main/java/eu/kanade/tachiyomi/ui/library/LibraryViewModel.kt:304
- PreferenceItemKt.PreferenceItem (cognitive 16) app/src/main/java/eu/kanade/presentation/more/settings/PreferenceItem.kt:64
- AppLanguageScreen.getLangs (cognitive 16) app/src/main/java/eu/kanade/presentation/more/settings/screen/appearance/AppLanguageScreen.kt:95
- ChapterNavigatorKt.HorizontalChapterNavigator (cognitive 16) app/src/main/java/eu/kanade/presentation/reader/components/ChapterNavigator.kt:156
- LibraryViewModel.applyFilters (cognitive 16) app/src/main/java/eu/kanade/tachiyomi/ui/library/LibraryViewModel.kt:220
- WebGpuViewerSettingsKt.WebGpuViewerSettings (cognitive 16) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewerSettings.kt:77
- Change-coupling hub: MangaRepositoryImpl.kt → MangaBackupCreator.kt, CategoryRepositoryImpl.kt, MangaMapper.kt data/src/main/java/tachiyomi/data/manga/MangaRepositoryImpl.kt
- REDACTED
- Near-duplicate member pair (32 shared lines) app/src/main/java/eu/kanade/presentation/more/settings/screen/SettingsReaderScreen.kt:189
- Duplicated block (27–28 lines × 2) app/src/main/java/mihon/feature/upcoming/UpcomingScreenContent.kt:178
- Duplicated block (24 lines × 2) app/src/main/java/eu/kanade/presentation/updates/UpdatesFilterDialog.kt:151
- Duplicated block (23 lines × 2) data/src/main/java/tachiyomi/data/manga/MangaMapper.kt:87
- Duplicated block (22 lines × 2) app/src/main/java/eu/kanade/presentation/manga/MangaScreen.kt:322
- Duplicated block (19–20 lines × 2) app/src/main/java/eu/kanade/presentation/manga/MangaScreen.kt:155
- Duplicated block (19 lines × 2) app/src/main/java/eu/kanade/presentation/library/components/LibraryComfortableGrid.kt:39
- Duplicated block (17–18 lines × 2) app/src/main/java/eu/kanade/presentation/more/settings/screen/browse/components/ExtensionStoresDialogs.kt:75
- Duplicated block (16–17 lines × 2) app/src/main/java/eu/kanade/presentation/updates/UpdatesFilterDialog.kt:130
- Duplicated block (16 lines × 3) app/src/main/java/eu/kanade/presentation/library/components/LibraryComfortableGrid.kt:51
- Duplicated block (14–15 lines × 2) app/src/main/java/eu/kanade/tachiyomi/ui/browse/migration/search/MigrateSourceSearchScreen.kt:126
- Duplicated block (13–14 lines × 2) data/src/main/java/tachiyomi/data/backup/RestoreRepositoryImpl.kt:183
- Duplicated block (12–13 lines × 2) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/pager/PagerPageHolder.kt:87
- Duplicated block (12 lines × 3) app/src/main/java/eu/kanade/tachiyomi/data/track/anilist/Anilist.kt:194
- Duplicated block (10 lines × 4) app/src/main/java/eu/kanade/tachiyomi/data/track/anilist/Anilist.kt:193
- Duplicated block (9 lines × 3) REDACTED:66
- Duplicated block (8–9 lines × 2) app/src/main/java/eu/kanade/tachiyomi/ui/history/HistoryViewModel.kt:215
- Duplicated block (8 lines × 4) app/src/main/java/eu/kanade/tachiyomi/data/track/anilist/Anilist.kt:208
- Duplicated block (7–8 lines × 2) app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/webgpu/WebGpuViewer.kt:1946
- Duplicated block (5 lines × 2) app/src/main/java/eu/kanade/presentation/manga/DuplicateMangaDialog.kt:260
- Duplicated block (9 lines × 4) app/src/main/java/eu/kanade/tachiyomi/data/track/anilist/Anilist.kt:70
- Duplicated block (6 lines × 3) REDACTED:48
- Duplicated block (6 lines × 2) data/src/main/java/tachiyomi/data/QueryPagingSource.kt:62
- Off the main sequence: :core:archive
Minor — 117 finding(s)
- Orphaned file presentation-core/src/main/java/tachiyomi/presentation/core/components/material/Button.kt:1
- Orphaned file presentation-core/src/main/java/tachiyomi/presentation/core/components/WheelPicker.kt:1
- Orphaned file app/src/main/java/eu/kanade/presentation/manga/components/MangaChapterListItem.kt:1
- Orphaned file app/src/main/java/eu/kanade/presentation/more/settings/screen/SettingsMainScreen.kt:1
- Orphaned file app/src/main/java/eu/kanade/presentation/track/TrackInfoDialogSelector.kt:1
- Orphaned file source-api/src/main/kotlin/eu/kanade/tachiyomi/source/online/ParsedHttpSource.kt:1
- Orphaned file app/src/main/java/eu/kanade/presentation/browse/SourcesScreen.kt:1
- Orphaned file core/common/src/main/kotlin/eu/kanade/tachiyomi/util/storage/DiskUtil.kt:1
- Orphaned file app/src/main/java/eu/kanade/tachiyomi/data/saver/ImageSaver.kt:1
- Orphaned file app/src/main/java/eu/kanade/presentation/components/Banners.kt:1
- Orphaned file app/src/main/java/eu/kanade/presentation/browse/BrowseSourceScreen.kt:1
- Orphaned file app/src/main/java/eu/kanade/presentation/manga/components/MangaToolbar.kt:1
- Orphaned file app/src/main/java/eu/kanade/tachiyomi/data/backup/BackupNotifier.kt:1
- Orphaned file app/src/main/java/eu/kanade/presentation/more/settings/widget/TriStateListDialog.kt:1
- Orphaned file core/common/src/main/kotlin/eu/kanade/tachiyomi/network/DohProviders.kt:1
- Orphaned file app/src/main/java/eu/kanade/presentation/library/components/LibraryToolbar.kt:1
- Orphaned file app/src/main/java/eu/kanade/presentation/manga/components/MangaDialogs.kt:1
- Orphaned file app/src/main/java/eu/kanade/tachiyomi/data/download/DownloadPendingDeleter.kt:1
- Orphaned file app/src/main/java/mihon/feature/migration/list/search/BaseSmartSearchEngine.kt:1
- Orphaned file app/src/main/java/eu/kanade/presentation/browse/components/BrowseSourceToolbar.kt:1
- Orphaned file presentation-core/src/main/java/tachiyomi/presentation/core/components/material/AlertDialog.kt:1
- Orphaned file presentation-core/src/main/java/tachiyomi/presentation/core/util/Elevation.kt:1
- Orphaned file app/src/main/java/eu/kanade/tachiyomi/util/system/AuthenticatorUtil.kt:1
- Orphaned file core/common/src/main/kotlin/tachiyomi/core/common/preference/InMemoryPreferenceStore.kt:1
- Orphaned file domain/src/main/java/tachiyomi/domain/library/model/LibrarySortMode.kt:1
- Duplicated predicate app/src/main/java/eu/kanade/presentation/more/settings/screen/SettingsDataScreen.kt:237
- Duplicated predicate app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/pager/PagerViewer.kt:130
- Duplicated predicate app/src/main/java/eu/kanade/tachiyomi/ui/history/HistoryViewModel.kt:114
- Duplicated predicate app/src/main/java/eu/kanade/tachiyomi/ui/history/HistoryViewModel.kt:228
- Duplicated predicate app/src/main/java/eu/kanade/tachiyomi/ui/manga/MangaViewModel.kt:579
- Duplicated predicate app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/pager/PagerPageTracker.kt:130
- Duplicated predicate app/src/main/java/eu/kanade/tachiyomi/data/library/LibraryUpdateWorker.kt:178
- Duplicated predicate app/src/main/java/eu/kanade/tachiyomi/data/backup/create/BackupOptions.kt:32
- Duplicated predicate app/src/main/java/eu/kanade/presentation/browse/components/BrowseSourceComfortableGrid.kt:50
- Duplicated predicate app/src/main/java/eu/kanade/presentation/library/components/LibraryComfortableGrid.kt:58
- Duplicated predicate app/src/main/java/eu/kanade/tachiyomi/data/track/anilist/Anilist.kt:163
- Silent fallback default in catch core/common/src/main/kotlin/eu/kanade/tachiyomi/util/storage/DiskUtil.kt:58
- Silent fallback default in catch core/common/src/main/kotlin/eu/kanade/tachiyomi/util/storage/DiskUtil.kt:70
- Silent fallback default in catch core/common/src/main/kotlin/eu/kanade/tachiyomi/util/storage/DiskUtil.kt:82
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST .github/workflows/build.yml:3
- Silent fallback default on parse failure app/src/main/java/eu/kanade/tachiyomi/data/track/mangaupdates/MangaUpdates.kt:109
- Subsumed condition operand app/src/main/java/eu/kanade/presentation/webview/WebViewScreenContent.kt:157
Minor — 1 finding(s)
- Off the main sequence: :core:common
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-1c08afd38a6a404d8a49e1e05b563d25/history.json --exit-code 0 --source . | 14 | 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-1c08afd38a6a404d8a49e1e05b563d25/tree.json --exit-code 0 --source . | 4 | 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 . | 6 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 52 file(s) — `app/src/main/java/eu/kanade/presentation/browse/components/GlobalSearchToolbar.kt`, `app/src/main/java/eu/kanade/presentation/more/settings/screen/advanced/ClearDatabaseScreen.kt`, `app/src/main/java/eu/kanade/presentation/more/settings/screen/appearance/AppLanguageScreen.kt`, `app/src/main/java/eu/kanade/presentation/more/settings/screen/data/CreateBackupScreen.kt`, `app/src/main/java/eu/kanade/presentation/more/settings/screen/data/RestoreBackupScreen.kt`, … (+47 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet). | 0 | — |