Executive summary
ykrank/S1-Next falls short of our standard for production because 204 files are no longer known to anyone active in the project and the project keeps no record of its design decisions. It scores 50.8 out of 100 and is rated Adequate, and its one critical finding is a leaked password or key.
Maturity, at 36.5, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 12.6 points. Having someone learn and document the 204 files no active contributor knows comes next, also worth about 12.6. Raising Maturity to 70 would lift the score to about 61.7.
One password or key is open to anyone who can read the repository. Replacing the exposed password or key would close this risk.
The product code is 40,017 lines, about €46,000 to rebuild.
If Maturity rose from 36.5 to 70, the lowest score rated Strong, the score would rise from 50.8 to about 61.7.
Rebuild cost: about €46,000 · Estimate
| Cost to rebuild | €15,000 to €76,000, for 252 to 799 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 51. 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: 40,017 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 com.github.ykrank.androidtools.data | 2 com.github.ykrank.androidtools.ui.adapter | 3 com.github.ykrank.androidtools.ui.internal | 4 com.github.ykrank.androidtools.widget | 5 me.ykrank.s1next.data.api.model.link | 6 me.ykrank.s1next.data.cache.biz | 7 me.ykrank.s1next.data.db.dbmodel | 8 com.github.ykrank.androidtools.widget.track | 9 com.github.ykrank.androidtools.widget.uploadimg | 10 me.ykrank.s1next.data.api.app.model | 11 me.ykrank.s1next.data.api.model | 12 me.ykrank.s1next.data.db.biz | 13 me.ykrank.s1next.data.pref | 14 com.github.ykrank.androidtools.ui | 15 me.ykrank.s1next.data | 16 me.ykrank.s1next.data.db | 17 me.ykrank.s1next.widget.span | 18 com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment | 19 me.ykrank.s1next.data.api.app | 20 me.ykrank.s1next.data.api.model.wrapper | 21 me.ykrank.s1next.viewmodel | 22 me.ykrank.s1next.data.api | 23 me.ykrank.s1next.view.adapter.delegate | 24 me.ykrank.s1next.view.internal | 25 me.ykrank.s1next.data.cache.api | 26 me.ykrank.s1next.view.adapter | 27 me.ykrank.s1next.view.dialog | 28 me.ykrank.s1next.view.page.post.postedit | 29 me.ykrank.s1next.widget.hostcheck | 30 me.ykrank.s1next.view.dialog.requestdialog | 31 me.ykrank.s1next.view.fragment | 32 me.ykrank.s1next.view.page.post.adapter | 33 me.ykrank.s1next.view.page.setting.fragment | 34 me.ykrank.s1next.view.activity | 35 me.ykrank.s1next.view.page.login | 36 me.ykrank.s1next.view.page.post.postedit.toolstab | 37 me.ykrank.s1next.view.page.setting.blacklist | 38 me.ykrank.s1next.view.page.app | 39 me.ykrank.s1next.view.page.post.postlist | 40 me.ykrank.s1next |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 com.github.ykrank.androidtools.data | ||||||||||||||||||||||||||||||||||||||||
| 2 com.github.ykrank.androidtools.ui.adapter | ||||||||||||||||||||||||||||||||||||||||
| 3 com.github.ykrank.androidtools.ui.internal | ||||||||||||||||||||||||||||||||||||||||
| 4 com.github.ykrank.androidtools.widget | ||||||||||||||||||||||||||||||||||||||||
| 5 me.ykrank.s1next.data.api.model.link | ||||||||||||||||||||||||||||||||||||||||
| 6 me.ykrank.s1next.data.cache.biz | ||||||||||||||||||||||||||||||||||||||||
| 7 me.ykrank.s1next.data.db.dbmodel | ||||||||||||||||||||||||||||||||||||||||
| 8 com.github.ykrank.androidtools.widget.track | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 com.github.ykrank.androidtools.widget.uploadimg | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 me.ykrank.s1next.data.api.app.model | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 me.ykrank.s1next.data.api.model | 11 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 me.ykrank.s1next.data.db.biz | 6 | 12 | ||||||||||||||||||||||||||||||||||||||
| 13 me.ykrank.s1next.data.pref | 6 | 3 | ||||||||||||||||||||||||||||||||||||||
| 14 com.github.ykrank.androidtools.ui | 1 | 1 | 6 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 15 me.ykrank.s1next.data | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 me.ykrank.s1next.data.db | 2 | 6 | ||||||||||||||||||||||||||||||||||||||
| 17 me.ykrank.s1next.widget.span | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 me.ykrank.s1next.data.api.app | 1 | 6 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 me.ykrank.s1next.data.api.model.wrapper | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 me.ykrank.s1next.viewmodel | 4 | 3 | 1 | 9 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 22 me.ykrank.s1next.data.api | 2 | 2 | 3 | 2 | 5 | |||||||||||||||||||||||||||||||||||
| 23 me.ykrank.s1next.view.adapter.delegate | 3 | 2 | 11 | 2 | 4 | 1 | ||||||||||||||||||||||||||||||||||
| 24 me.ykrank.s1next.view.internal | 5 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 25 me.ykrank.s1next.data.cache.api | 5 | 1 | 3 | 1 | 1 | 2 | 2 | 1 | 2 | |||||||||||||||||||||||||||||||
| 26 me.ykrank.s1next.view.adapter | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 27 me.ykrank.s1next.view.dialog | 3 | 2 | 1 | 1 | 1 | 3 | 1 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||
| 28 me.ykrank.s1next.view.page.post.postedit | 2 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 29 me.ykrank.s1next.widget.hostcheck | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 me.ykrank.s1next.view.dialog.requestdialog | 1 | 2 | 3 | 2 | ||||||||||||||||||||||||||||||||||||
| 31 me.ykrank.s1next.view.fragment | 3 | 3 | 5 | 2 | 2 | 8 | 1 | 4 | 4 | 6 | 2 | 5 | 12 | 1 | 10 | 1 | 1 | |||||||||||||||||||||||
| 32 me.ykrank.s1next.view.page.post.adapter | 2 | 8 | 2 | 1 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 33 me.ykrank.s1next.view.page.setting.fragment | 2 | 1 | 1 | 4 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 34 me.ykrank.s1next.view.activity | 2 | 1 | 2 | 2 | 4 | 1 | 1 | 4 | 3 | 1 | 3 | 6 | ||||||||||||||||||||||||||||
| 35 me.ykrank.s1next.view.page.login | 1 | 2 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 36 me.ykrank.s1next.view.page.post.postedit.toolstab | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 me.ykrank.s1next.view.page.setting.blacklist | 1 | 4 | 1 | 1 | 3 | 2 | ||||||||||||||||||||||||||||||||||
| 38 me.ykrank.s1next.view.page.app | 1 | 1 | 4 | 1 | 3 | 1 | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||
| 39 me.ykrank.s1next.view.page.post.postlist | 1 | 1 | 1 | 2 | 2 | 1 | 5 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||
| 40 me.ykrank.s1next | 5 | 3 | 3 | 7 | 10 | 2 | 1 | 2 | 2 | 6 | 7 | 1 | 1 | 4 | 3 | 4 | 17 | 2 | 5 | 6 | 2 | 1 | 1 | 2 | 4 |
8→1 com.github.ykrank.androidtools.widget.track uses com.github.ykrank.androidtools.data✕
- Connections
- 2 pairs of types, where a type in com.github.ykrank.androidtools.widget.track uses a type in com.github.ykrank.androidtools.data.
- The types involved
com.github.ykrank.androidtools.widget.track.DataTrackAgent→com.github.ykrank.androidtools.data.TrackUsercom.github.ykrank.androidtools.widget.track.TrackAgent→com.github.ykrank.androidtools.data.TrackUser
- Direction
- com.github.ykrank.androidtools.widget.track uses com.github.ykrank.androidtools.data, so a change to com.github.ykrank.androidtools.data can break com.github.ykrank.androidtools.widget.track, while a change to com.github.ykrank.androidtools.widget.track can't break com.github.ykrank.androidtools.data.
- Position
- Below the diagonal: com.github.ykrank.androidtools.widget.track uses a module listed above it, which is the healthy direction.
9→2 com.github.ykrank.androidtools.widget.uploadimg uses com.github.ykrank.androidtools.ui.adapter✕
- Connections
- 3 pairs of types, where a type in com.github.ykrank.androidtools.widget.uploadimg uses a type in com.github.ykrank.androidtools.ui.adapter.
- The types involved
com.github.ykrank.androidtools.widget.uploadimg.ImageUploadAdapter→com.github.ykrank.androidtools.ui.adapter.LibBaseRecyclerViewAdaptercom.github.ykrank.androidtools.widget.uploadimg.ModelImageUpload→com.github.ykrank.androidtools.ui.adapter.StableIdModelcom.github.ykrank.androidtools.widget.uploadimg.ModelImageUploadAdd→com.github.ykrank.androidtools.ui.adapter.StableIdModel
- Direction
- com.github.ykrank.androidtools.widget.uploadimg uses com.github.ykrank.androidtools.ui.adapter, so a change to com.github.ykrank.androidtools.ui.adapter can break com.github.ykrank.androidtools.widget.uploadimg, while a change to com.github.ykrank.androidtools.widget.uploadimg can't break com.github.ykrank.androidtools.ui.adapter.
- Position
- Below the diagonal: com.github.ykrank.androidtools.widget.uploadimg uses a module listed above it, which is the healthy direction.
9→4 com.github.ykrank.androidtools.widget.uploadimg uses com.github.ykrank.androidtools.widget✕
- Connections
- 1 pair of types, where a type in com.github.ykrank.androidtools.widget.uploadimg uses a type in com.github.ykrank.androidtools.widget.
- The types involved
com.github.ykrank.androidtools.widget.uploadimg.ImageUploadError→com.github.ykrank.androidtools.widget.AppException
- Direction
- com.github.ykrank.androidtools.widget.uploadimg uses com.github.ykrank.androidtools.widget, so a change to com.github.ykrank.androidtools.widget can break com.github.ykrank.androidtools.widget.uploadimg, while a change to com.github.ykrank.androidtools.widget.uploadimg can't break com.github.ykrank.androidtools.widget.
- Position
- Below the diagonal: com.github.ykrank.androidtools.widget.uploadimg uses a module listed above it, which is the healthy direction.
10→2 me.ykrank.s1next.data.api.app.model uses com.github.ykrank.androidtools.ui.adapter✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.data.api.app.model uses a type in com.github.ykrank.androidtools.ui.adapter.
- The types involved
me.ykrank.s1next.data.api.app.model.AppPost→com.github.ykrank.androidtools.ui.adapter.StableIdModel
- Direction
- me.ykrank.s1next.data.api.app.model uses com.github.ykrank.androidtools.ui.adapter, so a change to com.github.ykrank.androidtools.ui.adapter can break me.ykrank.s1next.data.api.app.model, while a change to me.ykrank.s1next.data.api.app.model can't break com.github.ykrank.androidtools.ui.adapter.
- Position
- Below the diagonal: me.ykrank.s1next.data.api.app.model uses a module listed above it, which is the healthy direction.
11→2 me.ykrank.s1next.data.api.model uses com.github.ykrank.androidtools.ui.adapter✕
- Connections
- 11 pairs of types, where a type in me.ykrank.s1next.data.api.model uses a type in com.github.ykrank.androidtools.ui.adapter.
- The types involved
me.ykrank.s1next.data.api.model.Favourite→com.github.ykrank.androidtools.ui.adapter.StableIdModelme.ykrank.s1next.data.api.model.Forum→com.github.ykrank.androidtools.ui.adapter.StableIdModelme.ykrank.s1next.data.api.model.Friend→com.github.ykrank.androidtools.ui.adapter.StableIdModelme.ykrank.s1next.data.api.model.HomeReply→com.github.ykrank.androidtools.ui.adapter.StableIdModelme.ykrank.s1next.data.api.model.HomeThread→com.github.ykrank.androidtools.ui.adapter.StableIdModelme.ykrank.s1next.data.api.model.Note→com.github.ykrank.androidtools.ui.adapter.StableIdModelme.ykrank.s1next.data.api.model.Pm→com.github.ykrank.androidtools.ui.adapter.StableIdModelme.ykrank.s1next.data.api.model.PmGroup→com.github.ykrank.androidtools.ui.adapter.StableIdModelme.ykrank.s1next.data.api.model.Post→com.github.ykrank.androidtools.ui.adapter.StableIdModelme.ykrank.s1next.data.api.model.Rate→com.github.ykrank.androidtools.ui.adapter.StableIdModelme.ykrank.s1next.data.api.model.Thread→com.github.ykrank.androidtools.ui.adapter.StableIdModel
- Direction
- me.ykrank.s1next.data.api.model uses com.github.ykrank.androidtools.ui.adapter, so a change to com.github.ykrank.androidtools.ui.adapter can break me.ykrank.s1next.data.api.model, while a change to me.ykrank.s1next.data.api.model can't break com.github.ykrank.androidtools.ui.adapter.
- Position
- Below the diagonal: me.ykrank.s1next.data.api.model uses a module listed above it, which is the healthy direction.
11→7 me.ykrank.s1next.data.api.model uses me.ykrank.s1next.data.db.dbmodel✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.data.api.model uses a type in me.ykrank.s1next.data.db.dbmodel.
- The types involved
me.ykrank.s1next.data.api.model.Thread→me.ykrank.s1next.data.db.dbmodel.History
- Direction
- me.ykrank.s1next.data.api.model uses me.ykrank.s1next.data.db.dbmodel, so a change to me.ykrank.s1next.data.db.dbmodel can break me.ykrank.s1next.data.api.model, while a change to me.ykrank.s1next.data.api.model can't break me.ykrank.s1next.data.db.dbmodel.
- Position
- Below the diagonal: me.ykrank.s1next.data.api.model uses a module listed above it, which is the healthy direction.
12→7 me.ykrank.s1next.data.db.biz uses me.ykrank.s1next.data.db.dbmodel✕
- Connections
- 6 pairs of types, where a type in me.ykrank.s1next.data.db.biz uses a type in me.ykrank.s1next.data.db.dbmodel.
- The types involved
me.ykrank.s1next.data.db.biz.BlackListBiz→me.ykrank.s1next.data.db.dbmodel.BlackListme.ykrank.s1next.data.db.biz.BlackWordBiz→me.ykrank.s1next.data.db.dbmodel.BlackWordme.ykrank.s1next.data.db.biz.HistoryBiz→me.ykrank.s1next.data.db.dbmodel.Historyme.ykrank.s1next.data.db.biz.LoginUserBiz→me.ykrank.s1next.data.db.dbmodel.LoginUserme.ykrank.s1next.data.db.biz.ReadProgressBiz→me.ykrank.s1next.data.db.dbmodel.ReadProgressme.ykrank.s1next.data.db.biz.ThreadBiz→me.ykrank.s1next.data.db.dbmodel.DbThread
- Direction
- me.ykrank.s1next.data.db.biz uses me.ykrank.s1next.data.db.dbmodel, so a change to me.ykrank.s1next.data.db.dbmodel can break me.ykrank.s1next.data.db.biz, while a change to me.ykrank.s1next.data.db.biz can't break me.ykrank.s1next.data.db.dbmodel.
- Position
- Below the diagonal: me.ykrank.s1next.data.db.biz uses a module listed above it, which is the healthy direction.
12→16 me.ykrank.s1next.data.db.biz uses me.ykrank.s1next.data.db part of a loop✕
- Connections
- 12 pairs of types, where a type in me.ykrank.s1next.data.db.biz uses a type in me.ykrank.s1next.data.db.
- The types involved
me.ykrank.s1next.data.db.biz.BlackListBiz→me.ykrank.s1next.data.db.AppDatabaseme.ykrank.s1next.data.db.biz.BlackListBiz→me.ykrank.s1next.data.db.AppDatabaseManagerme.ykrank.s1next.data.db.biz.BlackWordBiz→me.ykrank.s1next.data.db.AppDatabaseme.ykrank.s1next.data.db.biz.BlackWordBiz→me.ykrank.s1next.data.db.AppDatabaseManagerme.ykrank.s1next.data.db.biz.HistoryBiz→me.ykrank.s1next.data.db.AppDatabaseme.ykrank.s1next.data.db.biz.HistoryBiz→me.ykrank.s1next.data.db.AppDatabaseManagerme.ykrank.s1next.data.db.biz.LoginUserBiz→me.ykrank.s1next.data.db.AppDatabaseme.ykrank.s1next.data.db.biz.LoginUserBiz→me.ykrank.s1next.data.db.AppDatabaseManagerme.ykrank.s1next.data.db.biz.ReadProgressBiz→me.ykrank.s1next.data.db.AppDatabaseme.ykrank.s1next.data.db.biz.ReadProgressBiz→me.ykrank.s1next.data.db.AppDatabaseManagerme.ykrank.s1next.data.db.biz.ThreadBiz→me.ykrank.s1next.data.db.AppDatabaseme.ykrank.s1next.data.db.biz.ThreadBiz→me.ykrank.s1next.data.db.AppDatabaseManager
- Direction
- me.ykrank.s1next.data.db.biz uses me.ykrank.s1next.data.db, so a change to me.ykrank.s1next.data.db can break me.ykrank.s1next.data.db.biz, while a change to me.ykrank.s1next.data.db.biz can't break me.ykrank.s1next.data.db.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→1 me.ykrank.s1next.data.pref uses com.github.ykrank.androidtools.data✕
- Connections
- 6 pairs of types, where a type in me.ykrank.s1next.data.pref uses a type in com.github.ykrank.androidtools.data.
- The types involved
me.ykrank.s1next.data.pref.AppDataPreferencesImpl→com.github.ykrank.androidtools.data.BasePreferencesme.ykrank.s1next.data.pref.DataPreferencesImpl→com.github.ykrank.androidtools.data.BasePreferencesme.ykrank.s1next.data.pref.DownloadPreferencesImpl→com.github.ykrank.androidtools.data.BasePreferencesme.ykrank.s1next.data.pref.GeneralPreferencesImpl→com.github.ykrank.androidtools.data.BasePreferencesme.ykrank.s1next.data.pref.NetworkPreferencesImpl→com.github.ykrank.androidtools.data.BasePreferencesme.ykrank.s1next.data.pref.ReadPreferencesImpl→com.github.ykrank.androidtools.data.BasePreferences
- Direction
- me.ykrank.s1next.data.pref uses com.github.ykrank.androidtools.data, so a change to com.github.ykrank.androidtools.data can break me.ykrank.s1next.data.pref, while a change to me.ykrank.s1next.data.pref can't break com.github.ykrank.androidtools.data.
- Position
- Below the diagonal: me.ykrank.s1next.data.pref uses a module listed above it, which is the healthy direction.
13→7 me.ykrank.s1next.data.pref uses me.ykrank.s1next.data.db.dbmodel✕
- Connections
- 3 pairs of types, where a type in me.ykrank.s1next.data.pref uses a type in me.ykrank.s1next.data.db.dbmodel.
- The types involved
me.ykrank.s1next.data.pref.ReadPreferences→me.ykrank.s1next.data.db.dbmodel.ReadProgressme.ykrank.s1next.data.pref.ReadPreferencesImpl→me.ykrank.s1next.data.db.dbmodel.ReadProgressme.ykrank.s1next.data.pref.ReadPreferencesManager→me.ykrank.s1next.data.db.dbmodel.ReadProgress
- Direction
- me.ykrank.s1next.data.pref uses me.ykrank.s1next.data.db.dbmodel, so a change to me.ykrank.s1next.data.db.dbmodel can break me.ykrank.s1next.data.pref, while a change to me.ykrank.s1next.data.pref can't break me.ykrank.s1next.data.db.dbmodel.
- Position
- Below the diagonal: me.ykrank.s1next.data.pref uses a module listed above it, which is the healthy direction.
14→1 com.github.ykrank.androidtools.ui uses com.github.ykrank.androidtools.data✕
- Connections
- 1 pair of types, where a type in com.github.ykrank.androidtools.ui uses a type in com.github.ykrank.androidtools.data.
- The types involved
com.github.ykrank.androidtools.ui.LibBaseRecyclerViewFragment→com.github.ykrank.androidtools.data.Resource
- Direction
- com.github.ykrank.androidtools.ui uses com.github.ykrank.androidtools.data, so a change to com.github.ykrank.androidtools.data can break com.github.ykrank.androidtools.ui, while a change to com.github.ykrank.androidtools.ui can't break com.github.ykrank.androidtools.data.
- Position
- Below the diagonal: com.github.ykrank.androidtools.ui uses a module listed above it, which is the healthy direction.
14→2 com.github.ykrank.androidtools.ui uses com.github.ykrank.androidtools.ui.adapter✕
- Connections
- 1 pair of types, where a type in com.github.ykrank.androidtools.ui uses a type in com.github.ykrank.androidtools.ui.adapter.
- The types involved
com.github.ykrank.androidtools.ui.LibBaseLoadMoreRecycleViewFragment→com.github.ykrank.androidtools.ui.adapter.LibBaseRecyclerViewAdapter
- Direction
- com.github.ykrank.androidtools.ui uses com.github.ykrank.androidtools.ui.adapter, so a change to com.github.ykrank.androidtools.ui.adapter can break com.github.ykrank.androidtools.ui, while a change to com.github.ykrank.androidtools.ui can't break com.github.ykrank.androidtools.ui.adapter.
- Position
- Below the diagonal: com.github.ykrank.androidtools.ui uses a module listed above it, which is the healthy direction.
14→3 com.github.ykrank.androidtools.ui uses com.github.ykrank.androidtools.ui.internal✕
- Connections
- 6 pairs of types, where a type in com.github.ykrank.androidtools.ui uses a type in com.github.ykrank.androidtools.ui.internal.
- The types involved
com.github.ykrank.androidtools.ui.LibBaseActivity→com.github.ykrank.androidtools.ui.internal.CoordinatorLayoutAnchorDelegatecom.github.ykrank.androidtools.ui.LibBaseActivity→com.github.ykrank.androidtools.ui.internal.DrawerLayoutDelegatecom.github.ykrank.androidtools.ui.LibBaseActivity→com.github.ykrank.androidtools.ui.internal.DrawerLayoutOpcom.github.ykrank.androidtools.ui.LibBaseFragment→com.github.ykrank.androidtools.ui.internal.CoordinatorLayoutAnchorDelegatecom.github.ykrank.androidtools.ui.LibBaseRecyclerViewFragment→com.github.ykrank.androidtools.ui.internal.LoadingViewModelBindingDelegatecom.github.ykrank.androidtools.ui.LibBaseViewPagerFragment→com.github.ykrank.androidtools.ui.internal.PagerCallback
- Direction
- com.github.ykrank.androidtools.ui uses com.github.ykrank.androidtools.ui.internal, so a change to com.github.ykrank.androidtools.ui.internal can break com.github.ykrank.androidtools.ui, while a change to com.github.ykrank.androidtools.ui can't break com.github.ykrank.androidtools.ui.internal.
- Position
- Below the diagonal: com.github.ykrank.androidtools.ui uses a module listed above it, which is the healthy direction.
14→4 com.github.ykrank.androidtools.ui uses com.github.ykrank.androidtools.widget✕
- Connections
- 1 pair of types, where a type in com.github.ykrank.androidtools.ui uses a type in com.github.ykrank.androidtools.widget.
- The types involved
com.github.ykrank.androidtools.ui.LibBaseFragmentStatePagerAdapter→com.github.ykrank.androidtools.widget.TagFragmentStatePagerAdapter
- Direction
- com.github.ykrank.androidtools.ui uses com.github.ykrank.androidtools.widget, so a change to com.github.ykrank.androidtools.widget can break com.github.ykrank.androidtools.ui, while a change to com.github.ykrank.androidtools.ui can't break com.github.ykrank.androidtools.widget.
- Position
- Below the diagonal: com.github.ykrank.androidtools.ui uses a module listed above it, which is the healthy direction.
14→8 com.github.ykrank.androidtools.ui uses com.github.ykrank.androidtools.widget.track✕
- Connections
- 1 pair of types, where a type in com.github.ykrank.androidtools.ui uses a type in com.github.ykrank.androidtools.widget.track.
- The types involved
com.github.ykrank.androidtools.ui.UiDataProvider→com.github.ykrank.androidtools.widget.track.DataTrackAgent
- Direction
- com.github.ykrank.androidtools.ui uses com.github.ykrank.androidtools.widget.track, so a change to com.github.ykrank.androidtools.widget.track can break com.github.ykrank.androidtools.ui, while a change to com.github.ykrank.androidtools.ui can't break com.github.ykrank.androidtools.widget.track.
- Position
- Below the diagonal: com.github.ykrank.androidtools.ui uses a module listed above it, which is the healthy direction.
15→1 me.ykrank.s1next.data uses com.github.ykrank.androidtools.data✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.data uses a type in com.github.ykrank.androidtools.data.
- The types involved
me.ykrank.s1next.data.User→com.github.ykrank.androidtools.data.TrackUser
- Direction
- me.ykrank.s1next.data uses com.github.ykrank.androidtools.data, so a change to com.github.ykrank.androidtools.data can break me.ykrank.s1next.data, while a change to me.ykrank.s1next.data can't break com.github.ykrank.androidtools.data.
- Position
- Below the diagonal: me.ykrank.s1next.data uses a module listed above it, which is the healthy direction.
15→13 me.ykrank.s1next.data uses me.ykrank.s1next.data.pref✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.data uses a type in me.ykrank.s1next.data.pref.
- The types involved
me.ykrank.s1next.data.User→me.ykrank.s1next.data.pref.AppDataPreferencesManager
- Direction
- me.ykrank.s1next.data uses me.ykrank.s1next.data.pref, so a change to me.ykrank.s1next.data.pref can break me.ykrank.s1next.data, while a change to me.ykrank.s1next.data can't break me.ykrank.s1next.data.pref.
- Position
- Below the diagonal: me.ykrank.s1next.data uses a module listed above it, which is the healthy direction.
16→6 me.ykrank.s1next.data.db uses me.ykrank.s1next.data.cache.biz✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.data.db uses a type in me.ykrank.s1next.data.cache.biz.
- The types involved
me.ykrank.s1next.data.db.DbModule→me.ykrank.s1next.data.cache.biz.CacheBizme.ykrank.s1next.data.db.DbModule→me.ykrank.s1next.data.cache.biz.CacheGroupBiz
- Direction
- me.ykrank.s1next.data.db uses me.ykrank.s1next.data.cache.biz, so a change to me.ykrank.s1next.data.cache.biz can break me.ykrank.s1next.data.db, while a change to me.ykrank.s1next.data.db can't break me.ykrank.s1next.data.cache.biz.
- Position
- Below the diagonal: me.ykrank.s1next.data.db uses a module listed above it, which is the healthy direction.
16→12 me.ykrank.s1next.data.db uses me.ykrank.s1next.data.db.biz✕
- Connections
- 6 pairs of types, where a type in me.ykrank.s1next.data.db uses a type in me.ykrank.s1next.data.db.biz.
- The types involved
me.ykrank.s1next.data.db.DbModule→me.ykrank.s1next.data.db.biz.BlackListBizme.ykrank.s1next.data.db.DbModule→me.ykrank.s1next.data.db.biz.BlackWordBizme.ykrank.s1next.data.db.DbModule→me.ykrank.s1next.data.db.biz.HistoryBizme.ykrank.s1next.data.db.DbModule→me.ykrank.s1next.data.db.biz.LoginUserBizme.ykrank.s1next.data.db.DbModule→me.ykrank.s1next.data.db.biz.ReadProgressBizme.ykrank.s1next.data.db.DbModule→me.ykrank.s1next.data.db.biz.ThreadBiz
- Direction
- me.ykrank.s1next.data.db uses me.ykrank.s1next.data.db.biz, so a change to me.ykrank.s1next.data.db.biz can break me.ykrank.s1next.data.db, while a change to me.ykrank.s1next.data.db can't break me.ykrank.s1next.data.db.biz.
- Position
- Below the diagonal: me.ykrank.s1next.data.db uses a module listed above it, which is the healthy direction.
17→5 me.ykrank.s1next.widget.span uses me.ykrank.s1next.data.api.model.link✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.widget.span uses a type in me.ykrank.s1next.data.api.model.link.
- The types involved
me.ykrank.s1next.widget.span.SarabaInsideThreadSpan→me.ykrank.s1next.data.api.model.link.ThreadLinkme.ykrank.s1next.widget.span.SarabaInsideThreadSpan→me.ykrank.s1next.data.api.model.link.UserLink
- Direction
- me.ykrank.s1next.widget.span uses me.ykrank.s1next.data.api.model.link, so a change to me.ykrank.s1next.data.api.model.link can break me.ykrank.s1next.widget.span, while a change to me.ykrank.s1next.widget.span can't break me.ykrank.s1next.data.api.model.link.
- Position
- Below the diagonal: me.ykrank.s1next.widget.span uses a module listed above it, which is the healthy direction.
17→8 me.ykrank.s1next.widget.span uses com.github.ykrank.androidtools.widget.track✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.widget.span uses a type in com.github.ykrank.androidtools.widget.track.
- The types involved
me.ykrank.s1next.widget.span.GlideImageGetter→com.github.ykrank.androidtools.widget.track.DataTrackAgent
- Direction
- me.ykrank.s1next.widget.span uses com.github.ykrank.androidtools.widget.track, so a change to com.github.ykrank.androidtools.widget.track can break me.ykrank.s1next.widget.span, while a change to me.ykrank.s1next.widget.span can't break com.github.ykrank.androidtools.widget.track.
- Position
- Below the diagonal: me.ykrank.s1next.widget.span uses a module listed above it, which is the healthy direction.
17→13 me.ykrank.s1next.widget.span uses me.ykrank.s1next.data.pref✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.widget.span uses a type in me.ykrank.s1next.data.pref.
- The types involved
me.ykrank.s1next.widget.span.ImageGetterViewTarget→me.ykrank.s1next.data.pref.DownloadPreferencesManager
- Direction
- me.ykrank.s1next.widget.span uses me.ykrank.s1next.data.pref, so a change to me.ykrank.s1next.data.pref can break me.ykrank.s1next.widget.span, while a change to me.ykrank.s1next.widget.span can't break me.ykrank.s1next.data.pref.
- Position
- Below the diagonal: me.ykrank.s1next.widget.span uses a module listed above it, which is the healthy direction.
18→14 com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment uses com.github.ykrank.androidtools.ui✕
- Connections
- 1 pair of types, where a type in com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment uses a type in com.github.ykrank.androidtools.ui.
- The types involved
com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment.FragmentStatePagerAdapter→com.github.ykrank.androidtools.ui.LibBaseFragmentStatePagerAdapter
- Direction
- com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment uses com.github.ykrank.androidtools.ui, so a change to com.github.ykrank.androidtools.ui can break com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment, while a change to com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment can't break com.github.ykrank.androidtools.ui.
- Position
- Below the diagonal: com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment uses a module listed above it, which is the healthy direction.
19→4 me.ykrank.s1next.data.api.app uses com.github.ykrank.androidtools.widget✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.data.api.app uses a type in com.github.ykrank.androidtools.widget.
- The types involved
me.ykrank.s1next.data.api.app.AppApiUtil→com.github.ykrank.androidtools.widget.EventBus
- Direction
- me.ykrank.s1next.data.api.app uses com.github.ykrank.androidtools.widget, so a change to com.github.ykrank.androidtools.widget can break me.ykrank.s1next.data.api.app, while a change to me.ykrank.s1next.data.api.app can't break com.github.ykrank.androidtools.widget.
- Position
- Below the diagonal: me.ykrank.s1next.data.api.app uses a module listed above it, which is the healthy direction.
19→10 me.ykrank.s1next.data.api.app uses me.ykrank.s1next.data.api.app.model✕
- Connections
- 6 pairs of types, where a type in me.ykrank.s1next.data.api.app uses a type in me.ykrank.s1next.data.api.app.model.
- The types involved
me.ykrank.s1next.data.api.app.AppService→me.ykrank.s1next.data.api.app.model.AppDataWrapperme.ykrank.s1next.data.api.app.AppService→me.ykrank.s1next.data.api.app.model.AppLoginResultme.ykrank.s1next.data.api.app.AppService→me.ykrank.s1next.data.api.app.model.AppResultme.ykrank.s1next.data.api.app.AppService→me.ykrank.s1next.data.api.app.model.AppThreadme.ykrank.s1next.data.api.app.AppService→me.ykrank.s1next.data.api.app.model.AppUserInfome.ykrank.s1next.data.api.app.AppService→me.ykrank.s1next.data.api.app.model.AppVote
- Direction
- me.ykrank.s1next.data.api.app uses me.ykrank.s1next.data.api.app.model, so a change to me.ykrank.s1next.data.api.app.model can break me.ykrank.s1next.data.api.app, while a change to me.ykrank.s1next.data.api.app can't break me.ykrank.s1next.data.api.app.model.
- Position
- Below the diagonal: me.ykrank.s1next.data.api.app uses a module listed above it, which is the healthy direction.
19→15 me.ykrank.s1next.data.api.app uses me.ykrank.s1next.data✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.data.api.app uses a type in me.ykrank.s1next.data.
- The types involved
me.ykrank.s1next.data.api.app.AppTokenInterceptor→me.ykrank.s1next.data.User
- Direction
- me.ykrank.s1next.data.api.app uses me.ykrank.s1next.data, so a change to me.ykrank.s1next.data can break me.ykrank.s1next.data.api.app, while a change to me.ykrank.s1next.data.api.app can't break me.ykrank.s1next.data.
- Position
- Below the diagonal: me.ykrank.s1next.data.api.app uses a module listed above it, which is the healthy direction.
20→11 me.ykrank.s1next.data.api.model.wrapper uses me.ykrank.s1next.data.api.model✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.data.api.model.wrapper uses a type in me.ykrank.s1next.data.api.model.
- The types involved
me.ykrank.s1next.data.api.model.wrapper.BaseResultWrapper→me.ykrank.s1next.data.api.model.Resultme.ykrank.s1next.data.api.model.wrapper.HomeThreadWebWrapper→me.ykrank.s1next.data.api.model.HomeThread
- Direction
- me.ykrank.s1next.data.api.model.wrapper uses me.ykrank.s1next.data.api.model, so a change to me.ykrank.s1next.data.api.model can break me.ykrank.s1next.data.api.model.wrapper, while a change to me.ykrank.s1next.data.api.model.wrapper can't break me.ykrank.s1next.data.api.model.
- Position
- Below the diagonal: me.ykrank.s1next.data.api.model.wrapper uses a module listed above it, which is the healthy direction.
20→15 me.ykrank.s1next.data.api.model.wrapper uses me.ykrank.s1next.data✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.data.api.model.wrapper uses a type in me.ykrank.s1next.data.
- The types involved
me.ykrank.s1next.data.api.model.wrapper.PmsWrapper→me.ykrank.s1next.data.User
- Direction
- me.ykrank.s1next.data.api.model.wrapper uses me.ykrank.s1next.data, so a change to me.ykrank.s1next.data can break me.ykrank.s1next.data.api.model.wrapper, while a change to me.ykrank.s1next.data.api.model.wrapper can't break me.ykrank.s1next.data.
- Position
- Below the diagonal: me.ykrank.s1next.data.api.model.wrapper uses a module listed above it, which is the healthy direction.
21→4 me.ykrank.s1next.viewmodel uses com.github.ykrank.androidtools.widget✕
- Connections
- 4 pairs of types, where a type in me.ykrank.s1next.viewmodel uses a type in com.github.ykrank.androidtools.widget.
- The types involved
me.ykrank.s1next.viewmodel.AppPostViewModel→com.github.ykrank.androidtools.widget.EventBusme.ykrank.s1next.viewmodel.EmoticonViewModel→com.github.ykrank.androidtools.widget.EventBusme.ykrank.s1next.viewmodel.FavouriteViewModel→com.github.ykrank.androidtools.widget.EventBusme.ykrank.s1next.viewmodel.PmGroupViewModel→com.github.ykrank.androidtools.widget.EventBus
- Direction
- me.ykrank.s1next.viewmodel uses com.github.ykrank.androidtools.widget, so a change to com.github.ykrank.androidtools.widget can break me.ykrank.s1next.viewmodel, while a change to me.ykrank.s1next.viewmodel can't break com.github.ykrank.androidtools.widget.
- Position
- Below the diagonal: me.ykrank.s1next.viewmodel uses a module listed above it, which is the healthy direction.
21→7 me.ykrank.s1next.viewmodel uses me.ykrank.s1next.data.db.dbmodel✕
- Connections
- 3 pairs of types, where a type in me.ykrank.s1next.viewmodel uses a type in me.ykrank.s1next.data.db.dbmodel.
- The types involved
me.ykrank.s1next.viewmodel.BlackDialogViewModel→me.ykrank.s1next.data.db.dbmodel.BlackListme.ykrank.s1next.viewmodel.BlackListViewModel→me.ykrank.s1next.data.db.dbmodel.BlackListme.ykrank.s1next.viewmodel.BlackWordViewModel→me.ykrank.s1next.data.db.dbmodel.BlackWord
- Direction
- me.ykrank.s1next.viewmodel uses me.ykrank.s1next.data.db.dbmodel, so a change to me.ykrank.s1next.data.db.dbmodel can break me.ykrank.s1next.viewmodel, while a change to me.ykrank.s1next.viewmodel can't break me.ykrank.s1next.data.db.dbmodel.
- Position
- Below the diagonal: me.ykrank.s1next.viewmodel uses a module listed above it, which is the healthy direction.
21→10 me.ykrank.s1next.viewmodel uses me.ykrank.s1next.data.api.app.model✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.viewmodel uses a type in me.ykrank.s1next.data.api.app.model.
- The types involved
me.ykrank.s1next.viewmodel.VoteViewModel→me.ykrank.s1next.data.api.app.model.AppVote
- Direction
- me.ykrank.s1next.viewmodel uses me.ykrank.s1next.data.api.app.model, so a change to me.ykrank.s1next.data.api.app.model can break me.ykrank.s1next.viewmodel, while a change to me.ykrank.s1next.viewmodel can't break me.ykrank.s1next.data.api.app.model.
- Position
- Below the diagonal: me.ykrank.s1next.viewmodel uses a module listed above it, which is the healthy direction.
21→11 me.ykrank.s1next.viewmodel uses me.ykrank.s1next.data.api.model✕
- Connections
- 9 pairs of types, where a type in me.ykrank.s1next.viewmodel uses a type in me.ykrank.s1next.data.api.model.
- The types involved
me.ykrank.s1next.viewmodel.ForumViewModel→me.ykrank.s1next.data.api.model.Forumme.ykrank.s1next.viewmodel.FriendViewModel→me.ykrank.s1next.data.api.model.Friendme.ykrank.s1next.viewmodel.HomeReplyItemViewModel→me.ykrank.s1next.data.api.model.HomeReplyme.ykrank.s1next.viewmodel.HomeReplyTitleViewModel→me.ykrank.s1next.data.api.model.HomeThreadme.ykrank.s1next.viewmodel.HomeThreadViewModel→me.ykrank.s1next.data.api.model.HomeThreadme.ykrank.s1next.viewmodel.NewRateViewModel→me.ykrank.s1next.data.api.model.RatePreInfome.ykrank.s1next.viewmodel.NoteViewModel→me.ykrank.s1next.data.api.model.Noteme.ykrank.s1next.viewmodel.PmGroupViewModel→me.ykrank.s1next.data.api.model.PmGroupme.ykrank.s1next.viewmodel.VoteViewModel→me.ykrank.s1next.data.api.model.Vote
- Direction
- me.ykrank.s1next.viewmodel uses me.ykrank.s1next.data.api.model, so a change to me.ykrank.s1next.data.api.model can break me.ykrank.s1next.viewmodel, while a change to me.ykrank.s1next.viewmodel can't break me.ykrank.s1next.data.api.model.
- Position
- Below the diagonal: me.ykrank.s1next.viewmodel uses a module listed above it, which is the healthy direction.
21→13 me.ykrank.s1next.viewmodel uses me.ykrank.s1next.data.pref✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.viewmodel uses a type in me.ykrank.s1next.data.pref.
- The types involved
me.ykrank.s1next.viewmodel.UserViewModel→me.ykrank.s1next.data.pref.AppDataPreferencesManager
- Direction
- me.ykrank.s1next.viewmodel uses me.ykrank.s1next.data.pref, so a change to me.ykrank.s1next.data.pref can break me.ykrank.s1next.viewmodel, while a change to me.ykrank.s1next.viewmodel can't break me.ykrank.s1next.data.pref.
- Position
- Below the diagonal: me.ykrank.s1next.viewmodel uses a module listed above it, which is the healthy direction.
21→15 me.ykrank.s1next.viewmodel uses me.ykrank.s1next.data✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.viewmodel uses a type in me.ykrank.s1next.data.
- The types involved
me.ykrank.s1next.viewmodel.AppPostViewModel→me.ykrank.s1next.data.Userme.ykrank.s1next.viewmodel.UserViewModel→me.ykrank.s1next.data.User
- Direction
- me.ykrank.s1next.viewmodel uses me.ykrank.s1next.data, so a change to me.ykrank.s1next.data can break me.ykrank.s1next.viewmodel, while a change to me.ykrank.s1next.viewmodel can't break me.ykrank.s1next.data.
- Position
- Below the diagonal: me.ykrank.s1next.viewmodel uses a module listed above it, which is the healthy direction.
22→1 me.ykrank.s1next.data.api uses com.github.ykrank.androidtools.data✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.data.api uses a type in com.github.ykrank.androidtools.data.
- The types involved
me.ykrank.s1next.data.api.ApiCacheProvider→com.github.ykrank.androidtools.data.CacheParamme.ykrank.s1next.data.api.ApiCacheProvider→com.github.ykrank.androidtools.data.Resource
- Direction
- me.ykrank.s1next.data.api uses com.github.ykrank.androidtools.data, so a change to com.github.ykrank.androidtools.data can break me.ykrank.s1next.data.api, while a change to me.ykrank.s1next.data.api can't break com.github.ykrank.androidtools.data.
- Position
- Below the diagonal: me.ykrank.s1next.data.api uses a module listed above it, which is the healthy direction.
22→10 me.ykrank.s1next.data.api uses me.ykrank.s1next.data.api.app.model✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.data.api uses a type in me.ykrank.s1next.data.api.app.model.
- The types involved
me.ykrank.s1next.data.api.UserValidator→me.ykrank.s1next.data.api.app.model.AppLoginResultme.ykrank.s1next.data.api.UserValidator→me.ykrank.s1next.data.api.app.model.AppUserInfo
- Direction
- me.ykrank.s1next.data.api uses me.ykrank.s1next.data.api.app.model, so a change to me.ykrank.s1next.data.api.app.model can break me.ykrank.s1next.data.api, while a change to me.ykrank.s1next.data.api can't break me.ykrank.s1next.data.api.app.model.
- Position
- Below the diagonal: me.ykrank.s1next.data.api uses a module listed above it, which is the healthy direction.
22→11 me.ykrank.s1next.data.api uses me.ykrank.s1next.data.api.model✕
- Connections
- 3 pairs of types, where a type in me.ykrank.s1next.data.api uses a type in me.ykrank.s1next.data.api.model.
- The types involved
me.ykrank.s1next.data.api.ApiCacheProvider→me.ykrank.s1next.data.api.model.Rateme.ykrank.s1next.data.api.S1Service→me.ykrank.s1next.data.api.model.Profileme.ykrank.s1next.data.api.UserValidator→me.ykrank.s1next.data.api.model.Account
- Direction
- me.ykrank.s1next.data.api uses me.ykrank.s1next.data.api.model, so a change to me.ykrank.s1next.data.api.model can break me.ykrank.s1next.data.api, while a change to me.ykrank.s1next.data.api can't break me.ykrank.s1next.data.api.model.
- Position
- Below the diagonal: me.ykrank.s1next.data.api uses a module listed above it, which is the healthy direction.
22→15 me.ykrank.s1next.data.api uses me.ykrank.s1next.data✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.data.api uses a type in me.ykrank.s1next.data.
- The types involved
me.ykrank.s1next.data.api.ApiFlatTransformer→me.ykrank.s1next.data.Userme.ykrank.s1next.data.api.UserValidator→me.ykrank.s1next.data.User
- Direction
- me.ykrank.s1next.data.api uses me.ykrank.s1next.data, so a change to me.ykrank.s1next.data can break me.ykrank.s1next.data.api, while a change to me.ykrank.s1next.data.api can't break me.ykrank.s1next.data.
- Position
- Below the diagonal: me.ykrank.s1next.data.api uses a module listed above it, which is the healthy direction.
22→20 me.ykrank.s1next.data.api uses me.ykrank.s1next.data.api.model.wrapper✕
- Connections
- 5 pairs of types, where a type in me.ykrank.s1next.data.api uses a type in me.ykrank.s1next.data.api.model.wrapper.
- The types involved
me.ykrank.s1next.data.api.ApiCacheProvider→me.ykrank.s1next.data.api.model.wrapper.ForumGroupsWrapperme.ykrank.s1next.data.api.ApiFlatTransformer→me.ykrank.s1next.data.api.model.wrapper.AccountResultWrapperme.ykrank.s1next.data.api.S1Service→me.ykrank.s1next.data.api.model.wrapper.AccountResultWrapperme.ykrank.s1next.data.api.S1Service→me.ykrank.s1next.data.api.model.wrapper.BaseDataWrapperme.ykrank.s1next.data.api.S1Service→me.ykrank.s1next.data.api.model.wrapper.BaseResultWrapper
- Direction
- me.ykrank.s1next.data.api uses me.ykrank.s1next.data.api.model.wrapper, so a change to me.ykrank.s1next.data.api.model.wrapper can break me.ykrank.s1next.data.api, while a change to me.ykrank.s1next.data.api can't break me.ykrank.s1next.data.api.model.wrapper.
- Position
- Below the diagonal: me.ykrank.s1next.data.api uses a module listed above it, which is the healthy direction.
23→4 me.ykrank.s1next.view.adapter.delegate uses com.github.ykrank.androidtools.widget✕
- Connections
- 3 pairs of types, where a type in me.ykrank.s1next.view.adapter.delegate uses a type in com.github.ykrank.androidtools.widget.
- The types involved
me.ykrank.s1next.view.adapter.delegate.AppPostAdapterDelegate→com.github.ykrank.androidtools.widget.EventBusme.ykrank.s1next.view.adapter.delegate.FavouriteAdapterDelegate→com.github.ykrank.androidtools.widget.EventBusme.ykrank.s1next.view.adapter.delegate.PmGroupsAdapterDelegate→com.github.ykrank.androidtools.widget.EventBus
- Direction
- me.ykrank.s1next.view.adapter.delegate uses com.github.ykrank.androidtools.widget, so a change to com.github.ykrank.androidtools.widget can break me.ykrank.s1next.view.adapter.delegate, while a change to me.ykrank.s1next.view.adapter.delegate can't break com.github.ykrank.androidtools.widget.
- Position
- Below the diagonal: me.ykrank.s1next.view.adapter.delegate uses a module listed above it, which is the healthy direction.
23→10 me.ykrank.s1next.view.adapter.delegate uses me.ykrank.s1next.data.api.app.model✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.adapter.delegate uses a type in me.ykrank.s1next.data.api.app.model.
- The types involved
me.ykrank.s1next.view.adapter.delegate.AppPostAdapterDelegate→me.ykrank.s1next.data.api.app.model.AppPostme.ykrank.s1next.view.adapter.delegate.AppPostAdapterDelegate→me.ykrank.s1next.data.api.app.model.AppThread
- Direction
- me.ykrank.s1next.view.adapter.delegate uses me.ykrank.s1next.data.api.app.model, so a change to me.ykrank.s1next.data.api.app.model can break me.ykrank.s1next.view.adapter.delegate, while a change to me.ykrank.s1next.view.adapter.delegate can't break me.ykrank.s1next.data.api.app.model.
- Position
- Below the diagonal: me.ykrank.s1next.view.adapter.delegate uses a module listed above it, which is the healthy direction.
23→11 me.ykrank.s1next.view.adapter.delegate uses me.ykrank.s1next.data.api.model✕
- Connections
- 11 pairs of types, where a type in me.ykrank.s1next.view.adapter.delegate uses a type in me.ykrank.s1next.data.api.model.
- The types involved
me.ykrank.s1next.view.adapter.delegate.FavouriteAdapterDelegate→me.ykrank.s1next.data.api.model.Favouriteme.ykrank.s1next.view.adapter.delegate.ForumAdapterDelegate→me.ykrank.s1next.data.api.model.Forumme.ykrank.s1next.view.adapter.delegate.FriendAdapterDelegate→me.ykrank.s1next.data.api.model.Friendme.ykrank.s1next.view.adapter.delegate.HomeReplyItemAdapterDelegate→me.ykrank.s1next.data.api.model.HomeReplyme.ykrank.s1next.view.adapter.delegate.HomeReplyTitleAdapterDelegate→me.ykrank.s1next.data.api.model.HomeThreadme.ykrank.s1next.view.adapter.delegate.HomeThreadAdapterDelegate→me.ykrank.s1next.data.api.model.HomeThreadme.ykrank.s1next.view.adapter.delegate.NoteAdapterDelegate→me.ykrank.s1next.data.api.model.Noteme.ykrank.s1next.view.adapter.delegate.PmGroupsAdapterDelegate→me.ykrank.s1next.data.api.model.PmGroupme.ykrank.s1next.view.adapter.delegate.PmLeftAdapterDelegate→me.ykrank.s1next.data.api.model.Pmme.ykrank.s1next.view.adapter.delegate.PmRightAdapterDelegate→me.ykrank.s1next.data.api.model.Pmme.ykrank.s1next.view.adapter.delegate.ThreadAdapterDelegate→me.ykrank.s1next.data.api.model.Thread
- Direction
- me.ykrank.s1next.view.adapter.delegate uses me.ykrank.s1next.data.api.model, so a change to me.ykrank.s1next.data.api.model can break me.ykrank.s1next.view.adapter.delegate, while a change to me.ykrank.s1next.view.adapter.delegate can't break me.ykrank.s1next.data.api.model.
- Position
- Below the diagonal: me.ykrank.s1next.view.adapter.delegate uses a module listed above it, which is the healthy direction.
23→13 me.ykrank.s1next.view.adapter.delegate uses me.ykrank.s1next.data.pref✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.adapter.delegate uses a type in me.ykrank.s1next.data.pref.
- The types involved
me.ykrank.s1next.view.adapter.delegate.AppPostAdapterDelegate→me.ykrank.s1next.data.pref.GeneralPreferencesManagerme.ykrank.s1next.view.adapter.delegate.ThreadAdapterDelegate→me.ykrank.s1next.data.pref.ReadPreferencesManager
- Direction
- me.ykrank.s1next.view.adapter.delegate uses me.ykrank.s1next.data.pref, so a change to me.ykrank.s1next.data.pref can break me.ykrank.s1next.view.adapter.delegate, while a change to me.ykrank.s1next.view.adapter.delegate can't break me.ykrank.s1next.data.pref.
- Position
- Below the diagonal: me.ykrank.s1next.view.adapter.delegate uses a module listed above it, which is the healthy direction.
23→15 me.ykrank.s1next.view.adapter.delegate uses me.ykrank.s1next.data✕
- Connections
- 4 pairs of types, where a type in me.ykrank.s1next.view.adapter.delegate uses a type in me.ykrank.s1next.data.
- The types involved
me.ykrank.s1next.view.adapter.delegate.AppPostAdapterDelegate→me.ykrank.s1next.data.Userme.ykrank.s1next.view.adapter.delegate.PmGroupsAdapterDelegate→me.ykrank.s1next.data.Userme.ykrank.s1next.view.adapter.delegate.PmLeftAdapterDelegate→me.ykrank.s1next.data.Userme.ykrank.s1next.view.adapter.delegate.PmRightAdapterDelegate→me.ykrank.s1next.data.User
- Direction
- me.ykrank.s1next.view.adapter.delegate uses me.ykrank.s1next.data, so a change to me.ykrank.s1next.data can break me.ykrank.s1next.view.adapter.delegate, while a change to me.ykrank.s1next.view.adapter.delegate can't break me.ykrank.s1next.data.
- Position
- Below the diagonal: me.ykrank.s1next.view.adapter.delegate uses a module listed above it, which is the healthy direction.
23→21 me.ykrank.s1next.view.adapter.delegate uses me.ykrank.s1next.viewmodel✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.adapter.delegate uses a type in me.ykrank.s1next.viewmodel.
- The types involved
me.ykrank.s1next.view.adapter.delegate.ThreadAdapterDelegate→me.ykrank.s1next.viewmodel.UserViewModel
- Direction
- me.ykrank.s1next.view.adapter.delegate uses me.ykrank.s1next.viewmodel, so a change to me.ykrank.s1next.viewmodel can break me.ykrank.s1next.view.adapter.delegate, while a change to me.ykrank.s1next.view.adapter.delegate can't break me.ykrank.s1next.viewmodel.
- Position
- Below the diagonal: me.ykrank.s1next.view.adapter.delegate uses a module listed above it, which is the healthy direction.
24→3 me.ykrank.s1next.view.internal uses com.github.ykrank.androidtools.ui.internal✕
- Connections
- 5 pairs of types, where a type in me.ykrank.s1next.view.internal uses a type in com.github.ykrank.androidtools.ui.internal.
- The types involved
me.ykrank.s1next.view.internal.CoordinatorLayoutAnchorDelegateImpl→com.github.ykrank.androidtools.ui.internal.CoordinatorLayoutAnchorDelegateBaseImplme.ykrank.s1next.view.internal.DrawerLayoutDelegateConcrete→com.github.ykrank.androidtools.ui.internal.DrawerLayoutDelegateme.ykrank.s1next.view.internal.LoadingViewModelBindingDelegateBaseCardViewContainerImpl→com.github.ykrank.androidtools.ui.internal.LoadingViewModelBindingDelegateme.ykrank.s1next.view.internal.LoadingViewModelBindingDelegateBaseImpl→com.github.ykrank.androidtools.ui.internal.LoadingViewModelBindingDelegateme.ykrank.s1next.view.internal.LoadingViewModelBindingDelegateQuickSidebarImpl→com.github.ykrank.androidtools.ui.internal.LoadingViewModelBindingDelegate
- Direction
- me.ykrank.s1next.view.internal uses com.github.ykrank.androidtools.ui.internal, so a change to com.github.ykrank.androidtools.ui.internal can break me.ykrank.s1next.view.internal, while a change to me.ykrank.s1next.view.internal can't break com.github.ykrank.androidtools.ui.internal.
- Position
- Below the diagonal: me.ykrank.s1next.view.internal uses a module listed above it, which is the healthy direction.
24→4 me.ykrank.s1next.view.internal uses com.github.ykrank.androidtools.widget✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.internal uses a type in com.github.ykrank.androidtools.widget.
- The types involved
me.ykrank.s1next.view.internal.BlacklistMenuAction→com.github.ykrank.androidtools.widget.EventBus
- Direction
- me.ykrank.s1next.view.internal uses com.github.ykrank.androidtools.widget, so a change to com.github.ykrank.androidtools.widget can break me.ykrank.s1next.view.internal, while a change to me.ykrank.s1next.view.internal can't break com.github.ykrank.androidtools.widget.
- Position
- Below the diagonal: me.ykrank.s1next.view.internal uses a module listed above it, which is the healthy direction.
24→8 me.ykrank.s1next.view.internal uses com.github.ykrank.androidtools.widget.track✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.internal uses a type in com.github.ykrank.androidtools.widget.track.
- The types involved
me.ykrank.s1next.view.internal.DrawerLayoutDelegateConcrete→com.github.ykrank.androidtools.widget.track.DataTrackAgent
- Direction
- me.ykrank.s1next.view.internal uses com.github.ykrank.androidtools.widget.track, so a change to com.github.ykrank.androidtools.widget.track can break me.ykrank.s1next.view.internal, while a change to me.ykrank.s1next.view.internal can't break com.github.ykrank.androidtools.widget.track.
- Position
- Below the diagonal: me.ykrank.s1next.view.internal uses a module listed above it, which is the healthy direction.
24→13 me.ykrank.s1next.view.internal uses me.ykrank.s1next.data.pref✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.internal uses a type in me.ykrank.s1next.data.pref.
- The types involved
me.ykrank.s1next.view.internal.DrawerLayoutDelegateConcrete→me.ykrank.s1next.data.pref.DataPreferencesManager
- Direction
- me.ykrank.s1next.view.internal uses me.ykrank.s1next.data.pref, so a change to me.ykrank.s1next.data.pref can break me.ykrank.s1next.view.internal, while a change to me.ykrank.s1next.view.internal can't break me.ykrank.s1next.data.pref.
- Position
- Below the diagonal: me.ykrank.s1next.view.internal uses a module listed above it, which is the healthy direction.
24→15 me.ykrank.s1next.view.internal uses me.ykrank.s1next.data✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.internal uses a type in me.ykrank.s1next.data.
- The types involved
me.ykrank.s1next.view.internal.DrawerLayoutDelegateConcrete→me.ykrank.s1next.data.User
- Direction
- me.ykrank.s1next.view.internal uses me.ykrank.s1next.data, so a change to me.ykrank.s1next.data can break me.ykrank.s1next.view.internal, while a change to me.ykrank.s1next.view.internal can't break me.ykrank.s1next.data.
- Position
- Below the diagonal: me.ykrank.s1next.view.internal uses a module listed above it, which is the healthy direction.
24→21 me.ykrank.s1next.view.internal uses me.ykrank.s1next.viewmodel✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.internal uses a type in me.ykrank.s1next.viewmodel.
- The types involved
me.ykrank.s1next.view.internal.DrawerLayoutDelegateConcrete→me.ykrank.s1next.viewmodel.UserViewModel
- Direction
- me.ykrank.s1next.view.internal uses me.ykrank.s1next.viewmodel, so a change to me.ykrank.s1next.viewmodel can break me.ykrank.s1next.view.internal, while a change to me.ykrank.s1next.view.internal can't break me.ykrank.s1next.viewmodel.
- Position
- Below the diagonal: me.ykrank.s1next.view.internal uses a module listed above it, which is the healthy direction.
25→1 me.ykrank.s1next.data.cache.api uses com.github.ykrank.androidtools.data✕
- Connections
- 5 pairs of types, where a type in me.ykrank.s1next.data.cache.api uses a type in com.github.ykrank.androidtools.data.
- The types involved
me.ykrank.s1next.data.cache.api.ApiCacheFlow→com.github.ykrank.androidtools.data.CacheParamme.ykrank.s1next.data.cache.api.ApiCacheFlow→com.github.ykrank.androidtools.data.CacheStrategyme.ykrank.s1next.data.cache.api.ApiCacheFlow→com.github.ykrank.androidtools.data.Resourceme.ykrank.s1next.data.cache.api.S1ApiCacheProvider→com.github.ykrank.androidtools.data.CacheParamme.ykrank.s1next.data.cache.api.S1ApiCacheProvider→com.github.ykrank.androidtools.data.Resource
- Direction
- me.ykrank.s1next.data.cache.api uses com.github.ykrank.androidtools.data, so a change to com.github.ykrank.androidtools.data can break me.ykrank.s1next.data.cache.api, while a change to me.ykrank.s1next.data.cache.api can't break com.github.ykrank.androidtools.data.
- Position
- Below the diagonal: me.ykrank.s1next.data.cache.api uses a module listed above it, which is the healthy direction.
25→4 me.ykrank.s1next.data.cache.api uses com.github.ykrank.androidtools.widget✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.data.cache.api uses a type in com.github.ykrank.androidtools.widget.
- The types involved
me.ykrank.s1next.data.cache.api.ApiCacheFlow→com.github.ykrank.androidtools.widget.LoadTime
- Direction
- me.ykrank.s1next.data.cache.api uses com.github.ykrank.androidtools.widget, so a change to com.github.ykrank.androidtools.widget can break me.ykrank.s1next.data.cache.api, while a change to me.ykrank.s1next.data.cache.api can't break com.github.ykrank.androidtools.widget.
- Position
- Below the diagonal: me.ykrank.s1next.data.cache.api uses a module listed above it, which is the healthy direction.
25→6 me.ykrank.s1next.data.cache.api uses me.ykrank.s1next.data.cache.biz✕
- Connections
- 3 pairs of types, where a type in me.ykrank.s1next.data.cache.api uses a type in me.ykrank.s1next.data.cache.biz.
- The types involved
me.ykrank.s1next.data.cache.api.ApiCacheFlow→me.ykrank.s1next.data.cache.biz.CacheBizme.ykrank.s1next.data.cache.api.S1ApiCacheProvider→me.ykrank.s1next.data.cache.biz.CacheBizme.ykrank.s1next.data.cache.api.S1ApiCacheProvider→me.ykrank.s1next.data.cache.biz.CacheGroupBiz
- Direction
- me.ykrank.s1next.data.cache.api uses me.ykrank.s1next.data.cache.biz, so a change to me.ykrank.s1next.data.cache.biz can break me.ykrank.s1next.data.cache.api, while a change to me.ykrank.s1next.data.cache.api can't break me.ykrank.s1next.data.cache.biz.
- Position
- Below the diagonal: me.ykrank.s1next.data.cache.api uses a module listed above it, which is the healthy direction.
25→11 me.ykrank.s1next.data.cache.api uses me.ykrank.s1next.data.api.model✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.data.cache.api uses a type in me.ykrank.s1next.data.api.model.
- The types involved
me.ykrank.s1next.data.cache.api.S1ApiCacheProvider→me.ykrank.s1next.data.api.model.Rate
- Direction
- me.ykrank.s1next.data.cache.api uses me.ykrank.s1next.data.api.model, so a change to me.ykrank.s1next.data.api.model can break me.ykrank.s1next.data.cache.api, while a change to me.ykrank.s1next.data.cache.api can't break me.ykrank.s1next.data.api.model.
- Position
- Below the diagonal: me.ykrank.s1next.data.cache.api uses a module listed above it, which is the healthy direction.
25→12 me.ykrank.s1next.data.cache.api uses me.ykrank.s1next.data.db.biz✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.data.cache.api uses a type in me.ykrank.s1next.data.db.biz.
- The types involved
me.ykrank.s1next.data.cache.api.S1ApiCacheProvider→me.ykrank.s1next.data.db.biz.BlackListBiz
- Direction
- me.ykrank.s1next.data.cache.api uses me.ykrank.s1next.data.db.biz, so a change to me.ykrank.s1next.data.db.biz can break me.ykrank.s1next.data.cache.api, while a change to me.ykrank.s1next.data.cache.api can't break me.ykrank.s1next.data.db.biz.
- Position
- Below the diagonal: me.ykrank.s1next.data.cache.api uses a module listed above it, which is the healthy direction.
25→13 me.ykrank.s1next.data.cache.api uses me.ykrank.s1next.data.pref✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.data.cache.api uses a type in me.ykrank.s1next.data.pref.
- The types involved
me.ykrank.s1next.data.cache.api.ApiCacheFlow→me.ykrank.s1next.data.pref.DownloadPreferencesManagerme.ykrank.s1next.data.cache.api.S1ApiCacheProvider→me.ykrank.s1next.data.pref.DownloadPreferencesManager
- Direction
- me.ykrank.s1next.data.cache.api uses me.ykrank.s1next.data.pref, so a change to me.ykrank.s1next.data.pref can break me.ykrank.s1next.data.cache.api, while a change to me.ykrank.s1next.data.cache.api can't break me.ykrank.s1next.data.pref.
- Position
- Below the diagonal: me.ykrank.s1next.data.cache.api uses a module listed above it, which is the healthy direction.
25→15 me.ykrank.s1next.data.cache.api uses me.ykrank.s1next.data✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.data.cache.api uses a type in me.ykrank.s1next.data.
- The types involved
me.ykrank.s1next.data.cache.api.ApiCacheFlow→me.ykrank.s1next.data.Userme.ykrank.s1next.data.cache.api.S1ApiCacheProvider→me.ykrank.s1next.data.User
- Direction
- me.ykrank.s1next.data.cache.api uses me.ykrank.s1next.data, so a change to me.ykrank.s1next.data can break me.ykrank.s1next.data.cache.api, while a change to me.ykrank.s1next.data.cache.api can't break me.ykrank.s1next.data.
- Position
- Below the diagonal: me.ykrank.s1next.data.cache.api uses a module listed above it, which is the healthy direction.
25→20 me.ykrank.s1next.data.cache.api uses me.ykrank.s1next.data.api.model.wrapper✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.data.cache.api uses a type in me.ykrank.s1next.data.api.model.wrapper.
- The types involved
me.ykrank.s1next.data.cache.api.S1ApiCacheProvider→me.ykrank.s1next.data.api.model.wrapper.ForumGroupsWrapper
- Direction
- me.ykrank.s1next.data.cache.api uses me.ykrank.s1next.data.api.model.wrapper, so a change to me.ykrank.s1next.data.api.model.wrapper can break me.ykrank.s1next.data.cache.api, while a change to me.ykrank.s1next.data.cache.api can't break me.ykrank.s1next.data.api.model.wrapper.
- Position
- Below the diagonal: me.ykrank.s1next.data.cache.api uses a module listed above it, which is the healthy direction.
25→22 me.ykrank.s1next.data.cache.api uses me.ykrank.s1next.data.api✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.data.cache.api uses a type in me.ykrank.s1next.data.api.
- The types involved
me.ykrank.s1next.data.cache.api.S1ApiCacheProvider→me.ykrank.s1next.data.api.ApiCacheProviderme.ykrank.s1next.data.cache.api.S1ApiCacheProvider→me.ykrank.s1next.data.api.S1Service
- Direction
- me.ykrank.s1next.data.cache.api uses me.ykrank.s1next.data.api, so a change to me.ykrank.s1next.data.api can break me.ykrank.s1next.data.cache.api, while a change to me.ykrank.s1next.data.cache.api can't break me.ykrank.s1next.data.api.
- Position
- Below the diagonal: me.ykrank.s1next.data.cache.api uses a module listed above it, which is the healthy direction.
26→2 me.ykrank.s1next.view.adapter uses com.github.ykrank.androidtools.ui.adapter✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.adapter uses a type in com.github.ykrank.androidtools.ui.adapter.
- The types involved
me.ykrank.s1next.view.adapter.BaseRecyclerViewAdapter→com.github.ykrank.androidtools.ui.adapter.LibBaseRecyclerViewAdapter
- Direction
- me.ykrank.s1next.view.adapter uses com.github.ykrank.androidtools.ui.adapter, so a change to com.github.ykrank.androidtools.ui.adapter can break me.ykrank.s1next.view.adapter, while a change to me.ykrank.s1next.view.adapter can't break com.github.ykrank.androidtools.ui.adapter.
- Position
- Below the diagonal: me.ykrank.s1next.view.adapter uses a module listed above it, which is the healthy direction.
26→7 me.ykrank.s1next.view.adapter uses me.ykrank.s1next.data.db.dbmodel✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.adapter uses a type in me.ykrank.s1next.data.db.dbmodel.
- The types involved
me.ykrank.s1next.view.adapter.BlackWordCursorListViewAdapter→me.ykrank.s1next.data.db.dbmodel.BlackWord
- Direction
- me.ykrank.s1next.view.adapter uses me.ykrank.s1next.data.db.dbmodel, so a change to me.ykrank.s1next.data.db.dbmodel can break me.ykrank.s1next.view.adapter, while a change to me.ykrank.s1next.view.adapter can't break me.ykrank.s1next.data.db.dbmodel.
- Position
- Below the diagonal: me.ykrank.s1next.view.adapter uses a module listed above it, which is the healthy direction.
26→10 me.ykrank.s1next.view.adapter uses me.ykrank.s1next.data.api.app.model✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.adapter uses a type in me.ykrank.s1next.data.api.app.model.
- The types involved
me.ykrank.s1next.view.adapter.AppPostListRecyclerViewAdapter→me.ykrank.s1next.data.api.app.model.AppThread
- Direction
- me.ykrank.s1next.view.adapter uses me.ykrank.s1next.data.api.app.model, so a change to me.ykrank.s1next.data.api.app.model can break me.ykrank.s1next.view.adapter, while a change to me.ykrank.s1next.view.adapter can't break me.ykrank.s1next.data.api.app.model.
- Position
- Below the diagonal: me.ykrank.s1next.view.adapter uses a module listed above it, which is the healthy direction.
26→11 me.ykrank.s1next.view.adapter uses me.ykrank.s1next.data.api.model✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.adapter uses a type in me.ykrank.s1next.data.api.model.
- The types involved
me.ykrank.s1next.view.adapter.SubForumArrayAdapter→me.ykrank.s1next.data.api.model.Forum
- Direction
- me.ykrank.s1next.view.adapter uses me.ykrank.s1next.data.api.model, so a change to me.ykrank.s1next.data.api.model can break me.ykrank.s1next.view.adapter, while a change to me.ykrank.s1next.view.adapter can't break me.ykrank.s1next.data.api.model.
- Position
- Below the diagonal: me.ykrank.s1next.view.adapter uses a module listed above it, which is the healthy direction.
26→23 me.ykrank.s1next.view.adapter uses me.ykrank.s1next.view.adapter.delegate✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.adapter uses a type in me.ykrank.s1next.view.adapter.delegate.
- The types involved
me.ykrank.s1next.view.adapter.AppPostListRecyclerViewAdapter→me.ykrank.s1next.view.adapter.delegate.AppPostAdapterDelegate
- Direction
- me.ykrank.s1next.view.adapter uses me.ykrank.s1next.view.adapter.delegate, so a change to me.ykrank.s1next.view.adapter.delegate can break me.ykrank.s1next.view.adapter, while a change to me.ykrank.s1next.view.adapter can't break me.ykrank.s1next.view.adapter.delegate.
- Position
- Below the diagonal: me.ykrank.s1next.view.adapter uses a module listed above it, which is the healthy direction.
27→4 me.ykrank.s1next.view.dialog uses com.github.ykrank.androidtools.widget✕
- Connections
- 3 pairs of types, where a type in me.ykrank.s1next.view.dialog uses a type in com.github.ykrank.androidtools.widget.
- The types involved
me.ykrank.s1next.view.dialog.DiscardEditPromptDialogFragment→com.github.ykrank.androidtools.widget.EditorDiskCacheme.ykrank.s1next.view.dialog.LogoutDialogFragment→com.github.ykrank.androidtools.widget.EventBusme.ykrank.s1next.view.dialog.ThemeChangeDialogFragment→com.github.ykrank.androidtools.widget.EventBus
- Direction
- me.ykrank.s1next.view.dialog uses com.github.ykrank.androidtools.widget, so a change to com.github.ykrank.androidtools.widget can break me.ykrank.s1next.view.dialog, while a change to me.ykrank.s1next.view.dialog can't break com.github.ykrank.androidtools.widget.
- Position
- Below the diagonal: me.ykrank.s1next.view.dialog uses a module listed above it, which is the healthy direction.
27→5 me.ykrank.s1next.view.dialog uses me.ykrank.s1next.data.api.model.link✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.dialog uses a type in me.ykrank.s1next.data.api.model.link.
- The types involved
me.ykrank.s1next.view.dialog.QuotePostPageParserDialogFragment→me.ykrank.s1next.data.api.model.link.ThreadLinkme.ykrank.s1next.view.dialog.ThreadGoDialogFragment→me.ykrank.s1next.data.api.model.link.ThreadLink
- Direction
- me.ykrank.s1next.view.dialog uses me.ykrank.s1next.data.api.model.link, so a change to me.ykrank.s1next.data.api.model.link can break me.ykrank.s1next.view.dialog, while a change to me.ykrank.s1next.view.dialog can't break me.ykrank.s1next.data.api.model.link.
- Position
- Below the diagonal: me.ykrank.s1next.view.dialog uses a module listed above it, which is the healthy direction.
27→11 me.ykrank.s1next.view.dialog uses me.ykrank.s1next.data.api.model✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.dialog uses a type in me.ykrank.s1next.data.api.model.
- The types involved
me.ykrank.s1next.view.dialog.VoteDialogFragment→me.ykrank.s1next.data.api.model.Vote
- Direction
- me.ykrank.s1next.view.dialog uses me.ykrank.s1next.data.api.model, so a change to me.ykrank.s1next.data.api.model can break me.ykrank.s1next.view.dialog, while a change to me.ykrank.s1next.view.dialog can't break me.ykrank.s1next.data.api.model.
- Position
- Below the diagonal: me.ykrank.s1next.view.dialog uses a module listed above it, which is the healthy direction.
27→12 me.ykrank.s1next.view.dialog uses me.ykrank.s1next.data.db.biz✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.dialog uses a type in me.ykrank.s1next.data.db.biz.
- The types involved
me.ykrank.s1next.view.dialog.LoadBlackListFromWebDialogFragment→me.ykrank.s1next.data.db.biz.BlackListBiz
- Direction
- me.ykrank.s1next.view.dialog uses me.ykrank.s1next.data.db.biz, so a change to me.ykrank.s1next.data.db.biz can break me.ykrank.s1next.view.dialog, while a change to me.ykrank.s1next.view.dialog can't break me.ykrank.s1next.data.db.biz.
- Position
- Below the diagonal: me.ykrank.s1next.view.dialog uses a module listed above it, which is the healthy direction.
27→13 me.ykrank.s1next.view.dialog uses me.ykrank.s1next.data.pref✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.dialog uses a type in me.ykrank.s1next.data.pref.
- The types involved
me.ykrank.s1next.view.dialog.ThemeChangeDialogFragment→me.ykrank.s1next.data.pref.ThemeManager
- Direction
- me.ykrank.s1next.view.dialog uses me.ykrank.s1next.data.pref, so a change to me.ykrank.s1next.data.pref can break me.ykrank.s1next.view.dialog, while a change to me.ykrank.s1next.view.dialog can't break me.ykrank.s1next.data.pref.
- Position
- Below the diagonal: me.ykrank.s1next.view.dialog uses a module listed above it, which is the healthy direction.
27→15 me.ykrank.s1next.view.dialog uses me.ykrank.s1next.data✕
- Connections
- 3 pairs of types, where a type in me.ykrank.s1next.view.dialog uses a type in me.ykrank.s1next.data.
- The types involved
me.ykrank.s1next.view.dialog.LoadBlackListFromWebDialogFragment→me.ykrank.s1next.data.Userme.ykrank.s1next.view.dialog.ProgressDialogFragment→me.ykrank.s1next.data.Userme.ykrank.s1next.view.dialog.VoteDialogFragment→me.ykrank.s1next.data.User
- Direction
- me.ykrank.s1next.view.dialog uses me.ykrank.s1next.data, so a change to me.ykrank.s1next.data can break me.ykrank.s1next.view.dialog, while a change to me.ykrank.s1next.view.dialog can't break me.ykrank.s1next.data.
- Position
- Below the diagonal: me.ykrank.s1next.view.dialog uses a module listed above it, which is the healthy direction.
27→19 me.ykrank.s1next.view.dialog uses me.ykrank.s1next.data.api.app✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.dialog uses a type in me.ykrank.s1next.data.api.app.
- The types involved
me.ykrank.s1next.view.dialog.VoteDialogFragment→me.ykrank.s1next.data.api.app.AppService
- Direction
- me.ykrank.s1next.view.dialog uses me.ykrank.s1next.data.api.app, so a change to me.ykrank.s1next.data.api.app can break me.ykrank.s1next.view.dialog, while a change to me.ykrank.s1next.view.dialog can't break me.ykrank.s1next.data.api.app.
- Position
- Below the diagonal: me.ykrank.s1next.view.dialog uses a module listed above it, which is the healthy direction.
27→20 me.ykrank.s1next.view.dialog uses me.ykrank.s1next.data.api.model.wrapper✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.dialog uses a type in me.ykrank.s1next.data.api.model.wrapper.
- The types involved
me.ykrank.s1next.view.dialog.ThreadFavouritesAddRequestDialogFragment→me.ykrank.s1next.data.api.model.wrapper.AccountResultWrapper
- Direction
- me.ykrank.s1next.view.dialog uses me.ykrank.s1next.data.api.model.wrapper, so a change to me.ykrank.s1next.data.api.model.wrapper can break me.ykrank.s1next.view.dialog, while a change to me.ykrank.s1next.view.dialog can't break me.ykrank.s1next.data.api.model.wrapper.
- Position
- Below the diagonal: me.ykrank.s1next.view.dialog uses a module listed above it, which is the healthy direction.
27→21 me.ykrank.s1next.view.dialog uses me.ykrank.s1next.viewmodel✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.dialog uses a type in me.ykrank.s1next.viewmodel.
- The types involved
me.ykrank.s1next.view.dialog.LogoutDialogFragment→me.ykrank.s1next.viewmodel.UserViewModel
- Direction
- me.ykrank.s1next.view.dialog uses me.ykrank.s1next.viewmodel, so a change to me.ykrank.s1next.viewmodel can break me.ykrank.s1next.view.dialog, while a change to me.ykrank.s1next.view.dialog can't break me.ykrank.s1next.viewmodel.
- Position
- Below the diagonal: me.ykrank.s1next.view.dialog uses a module listed above it, which is the healthy direction.
27→22 me.ykrank.s1next.view.dialog uses me.ykrank.s1next.data.api✕
- Connections
- 4 pairs of types, where a type in me.ykrank.s1next.view.dialog uses a type in me.ykrank.s1next.data.api.
- The types involved
me.ykrank.s1next.view.dialog.LoadBlackListFromWebDialogFragment→me.ykrank.s1next.data.api.S1Serviceme.ykrank.s1next.view.dialog.ProgressDialogFragment→me.ykrank.s1next.data.api.S1Serviceme.ykrank.s1next.view.dialog.ProgressDialogFragment→me.ykrank.s1next.data.api.UserValidatorme.ykrank.s1next.view.dialog.VoteDialogFragment→me.ykrank.s1next.data.api.S1Service
- Direction
- me.ykrank.s1next.view.dialog uses me.ykrank.s1next.data.api, so a change to me.ykrank.s1next.data.api can break me.ykrank.s1next.view.dialog, while a change to me.ykrank.s1next.view.dialog can't break me.ykrank.s1next.data.api.
- Position
- Below the diagonal: me.ykrank.s1next.view.dialog uses a module listed above it, which is the healthy direction.
28→4 me.ykrank.s1next.view.page.post.postedit uses com.github.ykrank.androidtools.widget✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.page.post.postedit uses a type in com.github.ykrank.androidtools.widget.
- The types involved
me.ykrank.s1next.view.page.post.postedit.BasePostEditFragment→com.github.ykrank.androidtools.widget.EditorDiskCacheme.ykrank.s1next.view.page.post.postedit.BasePostEditFragment→com.github.ykrank.androidtools.widget.EventBus
- Direction
- me.ykrank.s1next.view.page.post.postedit uses com.github.ykrank.androidtools.widget, so a change to com.github.ykrank.androidtools.widget can break me.ykrank.s1next.view.page.post.postedit, while a change to me.ykrank.s1next.view.page.post.postedit can't break com.github.ykrank.androidtools.widget.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.postedit uses a module listed above it, which is the healthy direction.
28→9 me.ykrank.s1next.view.page.post.postedit uses com.github.ykrank.androidtools.widget.uploadimg✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.post.postedit uses a type in com.github.ykrank.androidtools.widget.uploadimg.
- The types involved
me.ykrank.s1next.view.page.post.postedit.BasePostEditFragment→com.github.ykrank.androidtools.widget.uploadimg.ModelImageUpload
- Direction
- me.ykrank.s1next.view.page.post.postedit uses com.github.ykrank.androidtools.widget.uploadimg, so a change to com.github.ykrank.androidtools.widget.uploadimg can break me.ykrank.s1next.view.page.post.postedit, while a change to me.ykrank.s1next.view.page.post.postedit can't break com.github.ykrank.androidtools.widget.uploadimg.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.postedit uses a module listed above it, which is the healthy direction.
28→11 me.ykrank.s1next.view.page.post.postedit uses me.ykrank.s1next.data.api.model✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.post.postedit uses a type in me.ykrank.s1next.data.api.model.
- The types involved
me.ykrank.s1next.view.page.post.postedit.NewThreadFragment→me.ykrank.s1next.data.api.model.ThreadType
- Direction
- me.ykrank.s1next.view.page.post.postedit uses me.ykrank.s1next.data.api.model, so a change to me.ykrank.s1next.data.api.model can break me.ykrank.s1next.view.page.post.postedit, while a change to me.ykrank.s1next.view.page.post.postedit can't break me.ykrank.s1next.data.api.model.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.postedit uses a module listed above it, which is the healthy direction.
28→13 me.ykrank.s1next.view.page.post.postedit uses me.ykrank.s1next.data.pref✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.post.postedit uses a type in me.ykrank.s1next.data.pref.
- The types involved
me.ykrank.s1next.view.page.post.postedit.BasePostEditFragment→me.ykrank.s1next.data.pref.GeneralPreferencesManager
- Direction
- me.ykrank.s1next.view.page.post.postedit uses me.ykrank.s1next.data.pref, so a change to me.ykrank.s1next.data.pref can break me.ykrank.s1next.view.page.post.postedit, while a change to me.ykrank.s1next.view.page.post.postedit can't break me.ykrank.s1next.data.pref.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.postedit uses a module listed above it, which is the healthy direction.
28→22 me.ykrank.s1next.view.page.post.postedit uses me.ykrank.s1next.data.api✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.post.postedit uses a type in me.ykrank.s1next.data.api.
- The types involved
me.ykrank.s1next.view.page.post.postedit.NewThreadFragment→me.ykrank.s1next.data.api.S1Service
- Direction
- me.ykrank.s1next.view.page.post.postedit uses me.ykrank.s1next.data.api, so a change to me.ykrank.s1next.data.api can break me.ykrank.s1next.view.page.post.postedit, while a change to me.ykrank.s1next.view.page.post.postedit can't break me.ykrank.s1next.data.api.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.postedit uses a module listed above it, which is the healthy direction.
28→31 me.ykrank.s1next.view.page.post.postedit uses me.ykrank.s1next.view.fragment part of a loop✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.post.postedit uses a type in me.ykrank.s1next.view.fragment.
- The types involved
me.ykrank.s1next.view.page.post.postedit.BasePostEditFragment→me.ykrank.s1next.view.fragment.BaseFragment
- Direction
- me.ykrank.s1next.view.page.post.postedit uses me.ykrank.s1next.view.fragment, so a change to me.ykrank.s1next.view.fragment can break me.ykrank.s1next.view.page.post.postedit, while a change to me.ykrank.s1next.view.page.post.postedit can't break me.ykrank.s1next.view.fragment.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→4 me.ykrank.s1next.widget.hostcheck uses com.github.ykrank.androidtools.widget✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.widget.hostcheck uses a type in com.github.ykrank.androidtools.widget.
- The types involved
me.ykrank.s1next.widget.hostcheck.NoticeCheckTask→com.github.ykrank.androidtools.widget.EventBus
- Direction
- me.ykrank.s1next.widget.hostcheck uses com.github.ykrank.androidtools.widget, so a change to com.github.ykrank.androidtools.widget can break me.ykrank.s1next.widget.hostcheck, while a change to me.ykrank.s1next.widget.hostcheck can't break com.github.ykrank.androidtools.widget.
- Position
- Below the diagonal: me.ykrank.s1next.widget.hostcheck uses a module listed above it, which is the healthy direction.
29→13 me.ykrank.s1next.widget.hostcheck uses me.ykrank.s1next.data.pref✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.widget.hostcheck uses a type in me.ykrank.s1next.data.pref.
- The types involved
me.ykrank.s1next.widget.hostcheck.AppHostUrl→me.ykrank.s1next.data.pref.NetworkPreferencesManager
- Direction
- me.ykrank.s1next.widget.hostcheck uses me.ykrank.s1next.data.pref, so a change to me.ykrank.s1next.data.pref can break me.ykrank.s1next.widget.hostcheck, while a change to me.ykrank.s1next.widget.hostcheck can't break me.ykrank.s1next.data.pref.
- Position
- Below the diagonal: me.ykrank.s1next.widget.hostcheck uses a module listed above it, which is the healthy direction.
29→15 me.ykrank.s1next.widget.hostcheck uses me.ykrank.s1next.data✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.widget.hostcheck uses a type in me.ykrank.s1next.data.
- The types involved
me.ykrank.s1next.widget.hostcheck.NoticeCheckTask→me.ykrank.s1next.data.User
- Direction
- me.ykrank.s1next.widget.hostcheck uses me.ykrank.s1next.data, so a change to me.ykrank.s1next.data can break me.ykrank.s1next.widget.hostcheck, while a change to me.ykrank.s1next.widget.hostcheck can't break me.ykrank.s1next.data.
- Position
- Below the diagonal: me.ykrank.s1next.widget.hostcheck uses a module listed above it, which is the healthy direction.
29→22 me.ykrank.s1next.widget.hostcheck uses me.ykrank.s1next.data.api✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.widget.hostcheck uses a type in me.ykrank.s1next.data.api.
- The types involved
me.ykrank.s1next.widget.hostcheck.NoticeCheckTask→me.ykrank.s1next.data.api.S1Service
- Direction
- me.ykrank.s1next.widget.hostcheck uses me.ykrank.s1next.data.api, so a change to me.ykrank.s1next.data.api can break me.ykrank.s1next.widget.hostcheck, while a change to me.ykrank.s1next.widget.hostcheck can't break me.ykrank.s1next.data.api.
- Position
- Below the diagonal: me.ykrank.s1next.widget.hostcheck uses a module listed above it, which is the healthy direction.
30→4 me.ykrank.s1next.view.dialog.requestdialog uses com.github.ykrank.androidtools.widget✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.dialog.requestdialog uses a type in com.github.ykrank.androidtools.widget.
- The types involved
me.ykrank.s1next.view.dialog.requestdialog.BaseRequestDialogFragment→com.github.ykrank.androidtools.widget.EventBus
- Direction
- me.ykrank.s1next.view.dialog.requestdialog uses com.github.ykrank.androidtools.widget, so a change to com.github.ykrank.androidtools.widget can break me.ykrank.s1next.view.dialog.requestdialog, while a change to me.ykrank.s1next.view.dialog.requestdialog can't break com.github.ykrank.androidtools.widget.
- Position
- Below the diagonal: me.ykrank.s1next.view.dialog.requestdialog uses a module listed above it, which is the healthy direction.
30→11 me.ykrank.s1next.view.dialog.requestdialog uses me.ykrank.s1next.data.api.model✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.dialog.requestdialog uses a type in me.ykrank.s1next.data.api.model.
- The types involved
me.ykrank.s1next.view.dialog.requestdialog.EditPostRequestDialogFragment→me.ykrank.s1next.data.api.model.AjaxResultme.ykrank.s1next.view.dialog.requestdialog.RateRequestDialogFragment→me.ykrank.s1next.data.api.model.AjaxResult
- Direction
- me.ykrank.s1next.view.dialog.requestdialog uses me.ykrank.s1next.data.api.model, so a change to me.ykrank.s1next.data.api.model can break me.ykrank.s1next.view.dialog.requestdialog, while a change to me.ykrank.s1next.view.dialog.requestdialog can't break me.ykrank.s1next.data.api.model.
- Position
- Below the diagonal: me.ykrank.s1next.view.dialog.requestdialog uses a module listed above it, which is the healthy direction.
30→20 me.ykrank.s1next.view.dialog.requestdialog uses me.ykrank.s1next.data.api.model.wrapper✕
- Connections
- 3 pairs of types, where a type in me.ykrank.s1next.view.dialog.requestdialog uses a type in me.ykrank.s1next.data.api.model.wrapper.
- The types involved
me.ykrank.s1next.view.dialog.requestdialog.NewThreadRequestDialogFragment→me.ykrank.s1next.data.api.model.wrapper.AccountResultWrapperme.ykrank.s1next.view.dialog.requestdialog.PmRequestDialogFragment→me.ykrank.s1next.data.api.model.wrapper.AccountResultWrapperme.ykrank.s1next.view.dialog.requestdialog.ReplyRequestDialogFragment→me.ykrank.s1next.data.api.model.wrapper.AccountResultWrapper
- Direction
- me.ykrank.s1next.view.dialog.requestdialog uses me.ykrank.s1next.data.api.model.wrapper, so a change to me.ykrank.s1next.data.api.model.wrapper can break me.ykrank.s1next.view.dialog.requestdialog, while a change to me.ykrank.s1next.view.dialog.requestdialog can't break me.ykrank.s1next.data.api.model.wrapper.
- Position
- Below the diagonal: me.ykrank.s1next.view.dialog.requestdialog uses a module listed above it, which is the healthy direction.
30→27 me.ykrank.s1next.view.dialog.requestdialog uses me.ykrank.s1next.view.dialog✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.dialog.requestdialog uses a type in me.ykrank.s1next.view.dialog.
- The types involved
me.ykrank.s1next.view.dialog.requestdialog.BaseRequestDialogFragment→me.ykrank.s1next.view.dialog.ProgressDialogFragmentme.ykrank.s1next.view.dialog.requestdialog.RateRequestDialogFragment→me.ykrank.s1next.view.dialog.ProgressDialogFragment
- Direction
- me.ykrank.s1next.view.dialog.requestdialog uses me.ykrank.s1next.view.dialog, so a change to me.ykrank.s1next.view.dialog can break me.ykrank.s1next.view.dialog.requestdialog, while a change to me.ykrank.s1next.view.dialog.requestdialog can't break me.ykrank.s1next.view.dialog.
- Position
- Below the diagonal: me.ykrank.s1next.view.dialog.requestdialog uses a module listed above it, which is the healthy direction.
31→1 me.ykrank.s1next.view.fragment uses com.github.ykrank.androidtools.data✕
- Connections
- 3 pairs of types, where a type in me.ykrank.s1next.view.fragment uses a type in com.github.ykrank.androidtools.data.
- The types involved
me.ykrank.s1next.view.fragment.BaseRecyclerViewFragment→com.github.ykrank.androidtools.data.Resourceme.ykrank.s1next.view.fragment.ForumFragment→com.github.ykrank.androidtools.data.Resourceme.ykrank.s1next.view.fragment.ThreadListPagerFragment→com.github.ykrank.androidtools.data.Resource
- Direction
- me.ykrank.s1next.view.fragment uses com.github.ykrank.androidtools.data, so a change to com.github.ykrank.androidtools.data can break me.ykrank.s1next.view.fragment, while a change to me.ykrank.s1next.view.fragment can't break com.github.ykrank.androidtools.data.
- Position
- Below the diagonal: me.ykrank.s1next.view.fragment uses a module listed above it, which is the healthy direction.
31→3 me.ykrank.s1next.view.fragment uses com.github.ykrank.androidtools.ui.internal✕
- Connections
- 3 pairs of types, where a type in me.ykrank.s1next.view.fragment uses a type in com.github.ykrank.androidtools.ui.internal.
- The types involved
me.ykrank.s1next.view.fragment.BaseLoadMoreRecycleViewFragment→com.github.ykrank.androidtools.ui.internal.LoadingViewModelBindingDelegateme.ykrank.s1next.view.fragment.BaseRecyclerViewFragment→com.github.ykrank.androidtools.ui.internal.LoadingViewModelBindingDelegateme.ykrank.s1next.view.fragment.LoadingViewModelBindingDelegateNoteImpl→com.github.ykrank.androidtools.ui.internal.LoadingViewModelBindingDelegate
- Direction
- me.ykrank.s1next.view.fragment uses com.github.ykrank.androidtools.ui.internal, so a change to com.github.ykrank.androidtools.ui.internal can break me.ykrank.s1next.view.fragment, while a change to me.ykrank.s1next.view.fragment can't break com.github.ykrank.androidtools.ui.internal.
- Position
- Below the diagonal: me.ykrank.s1next.view.fragment uses a module listed above it, which is the healthy direction.
31→4 me.ykrank.s1next.view.fragment uses com.github.ykrank.androidtools.widget✕
- Connections
- 5 pairs of types, where a type in me.ykrank.s1next.view.fragment uses a type in com.github.ykrank.androidtools.widget.
- The types involved
me.ykrank.s1next.view.fragment.BaseRecyclerViewFragment→com.github.ykrank.androidtools.widget.EventBusme.ykrank.s1next.view.fragment.FavouriteListFragment→com.github.ykrank.androidtools.widget.EventBusme.ykrank.s1next.view.fragment.NoteFragment→com.github.ykrank.androidtools.widget.EventBusme.ykrank.s1next.view.fragment.PmGroupsFragment→com.github.ykrank.androidtools.widget.EventBusme.ykrank.s1next.view.fragment.ThreadListFragment→com.github.ykrank.androidtools.widget.EventBus
- Direction
- me.ykrank.s1next.view.fragment uses com.github.ykrank.androidtools.widget, so a change to com.github.ykrank.androidtools.widget can break me.ykrank.s1next.view.fragment, while a change to me.ykrank.s1next.view.fragment can't break com.github.ykrank.androidtools.widget.
- Position
- Below the diagonal: me.ykrank.s1next.view.fragment uses a module listed above it, which is the healthy direction.
31→8 me.ykrank.s1next.view.fragment uses com.github.ykrank.androidtools.widget.track✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.fragment uses a type in com.github.ykrank.androidtools.widget.track.
- The types involved
me.ykrank.s1next.view.fragment.BaseViewPagerFragment→com.github.ykrank.androidtools.widget.track.DataTrackAgentme.ykrank.s1next.view.fragment.GalleryFragment→com.github.ykrank.androidtools.widget.track.DataTrackAgent
- Direction
- me.ykrank.s1next.view.fragment uses com.github.ykrank.androidtools.widget.track, so a change to com.github.ykrank.androidtools.widget.track can break me.ykrank.s1next.view.fragment, while a change to me.ykrank.s1next.view.fragment can't break com.github.ykrank.androidtools.widget.track.
- Position
- Below the diagonal: me.ykrank.s1next.view.fragment uses a module listed above it, which is the healthy direction.
31→10 me.ykrank.s1next.view.fragment uses me.ykrank.s1next.data.api.app.model✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.fragment uses a type in me.ykrank.s1next.data.api.app.model.
- The types involved
me.ykrank.s1next.view.fragment.BaseLoadMoreRecycleViewFragment→me.ykrank.s1next.data.api.app.model.AppResultme.ykrank.s1next.view.fragment.BaseRecyclerViewFragment→me.ykrank.s1next.data.api.app.model.AppResult
- Direction
- me.ykrank.s1next.view.fragment uses me.ykrank.s1next.data.api.app.model, so a change to me.ykrank.s1next.data.api.app.model can break me.ykrank.s1next.view.fragment, while a change to me.ykrank.s1next.view.fragment can't break me.ykrank.s1next.data.api.app.model.
- Position
- Below the diagonal: me.ykrank.s1next.view.fragment uses a module listed above it, which is the healthy direction.
31→11 me.ykrank.s1next.view.fragment uses me.ykrank.s1next.data.api.model✕
- Connections
- 8 pairs of types, where a type in me.ykrank.s1next.view.fragment uses a type in me.ykrank.s1next.data.api.model.
- The types involved
me.ykrank.s1next.view.fragment.BaseLoadMoreRecycleViewFragment→me.ykrank.s1next.data.api.model.Resultme.ykrank.s1next.view.fragment.BaseRecyclerViewFragment→me.ykrank.s1next.data.api.model.Resultme.ykrank.s1next.view.fragment.EditPostFragment→me.ykrank.s1next.data.api.model.Postme.ykrank.s1next.view.fragment.EditPostFragment→me.ykrank.s1next.data.api.model.Threadme.ykrank.s1next.view.fragment.EditPostFragment→me.ykrank.s1next.data.api.model.ThreadTypeme.ykrank.s1next.view.fragment.NewRateFragment→me.ykrank.s1next.data.api.model.RatePreInfome.ykrank.s1next.view.fragment.NewReportFragment→me.ykrank.s1next.data.api.model.ReportPreInfome.ykrank.s1next.view.fragment.RateDetailsListFragment→me.ykrank.s1next.data.api.model.Rate
- Direction
- me.ykrank.s1next.view.fragment uses me.ykrank.s1next.data.api.model, so a change to me.ykrank.s1next.data.api.model can break me.ykrank.s1next.view.fragment, while a change to me.ykrank.s1next.view.fragment can't break me.ykrank.s1next.data.api.model.
- Position
- Below the diagonal: me.ykrank.s1next.view.fragment uses a module listed above it, which is the healthy direction.
31→12 me.ykrank.s1next.view.fragment uses me.ykrank.s1next.data.db.biz✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.fragment uses a type in me.ykrank.s1next.data.db.biz.
- The types involved
me.ykrank.s1next.view.fragment.HistoryListFragment→me.ykrank.s1next.data.db.biz.HistoryBiz
- Direction
- me.ykrank.s1next.view.fragment uses me.ykrank.s1next.data.db.biz, so a change to me.ykrank.s1next.data.db.biz can break me.ykrank.s1next.view.fragment, while a change to me.ykrank.s1next.view.fragment can't break me.ykrank.s1next.data.db.biz.
- Position
- Below the diagonal: me.ykrank.s1next.view.fragment uses a module listed above it, which is the healthy direction.
31→13 me.ykrank.s1next.view.fragment uses me.ykrank.s1next.data.pref✕
- Connections
- 4 pairs of types, where a type in me.ykrank.s1next.view.fragment uses a type in me.ykrank.s1next.data.pref.
- The types involved
me.ykrank.s1next.view.fragment.BaseLoadMoreRecycleViewFragment→me.ykrank.s1next.data.pref.DownloadPreferencesManagerme.ykrank.s1next.view.fragment.GalleryFragment→me.ykrank.s1next.data.pref.DownloadPreferencesManagerme.ykrank.s1next.view.fragment.ThreadListFragment→me.ykrank.s1next.data.pref.GeneralPreferencesManagerme.ykrank.s1next.view.fragment.ThreadListPagerFragment→me.ykrank.s1next.data.pref.GeneralPreferencesManager
- Direction
- me.ykrank.s1next.view.fragment uses me.ykrank.s1next.data.pref, so a change to me.ykrank.s1next.data.pref can break me.ykrank.s1next.view.fragment, while a change to me.ykrank.s1next.view.fragment can't break me.ykrank.s1next.data.pref.
- Position
- Below the diagonal: me.ykrank.s1next.view.fragment uses a module listed above it, which is the healthy direction.
31→14 me.ykrank.s1next.view.fragment uses com.github.ykrank.androidtools.ui✕
- Connections
- 4 pairs of types, where a type in me.ykrank.s1next.view.fragment uses a type in com.github.ykrank.androidtools.ui.
- The types involved
me.ykrank.s1next.view.fragment.BaseFragment→com.github.ykrank.androidtools.ui.LibBaseFragmentme.ykrank.s1next.view.fragment.BaseLoadMoreRecycleViewFragment→com.github.ykrank.androidtools.ui.LibBaseLoadMoreRecycleViewFragmentme.ykrank.s1next.view.fragment.BaseRecyclerViewFragment→com.github.ykrank.androidtools.ui.LibBaseRecyclerViewFragmentme.ykrank.s1next.view.fragment.BaseViewPagerFragment→com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment
- Direction
- me.ykrank.s1next.view.fragment uses com.github.ykrank.androidtools.ui, so a change to com.github.ykrank.androidtools.ui can break me.ykrank.s1next.view.fragment, while a change to me.ykrank.s1next.view.fragment can't break com.github.ykrank.androidtools.ui.
- Position
- Below the diagonal: me.ykrank.s1next.view.fragment uses a module listed above it, which is the healthy direction.
31→15 me.ykrank.s1next.view.fragment uses me.ykrank.s1next.data✕
- Connections
- 6 pairs of types, where a type in me.ykrank.s1next.view.fragment uses a type in me.ykrank.s1next.data.
- The types involved
me.ykrank.s1next.view.fragment.BaseFragment→me.ykrank.s1next.data.Userme.ykrank.s1next.view.fragment.BaseLoadMoreRecycleViewFragment→me.ykrank.s1next.data.Userme.ykrank.s1next.view.fragment.BaseRecyclerViewFragment→me.ykrank.s1next.data.Userme.ykrank.s1next.view.fragment.BaseViewPagerFragment→me.ykrank.s1next.data.Userme.ykrank.s1next.view.fragment.DarkRoomFragment→me.ykrank.s1next.data.Userme.ykrank.s1next.view.fragment.PmFragment→me.ykrank.s1next.data.User
- Direction
- me.ykrank.s1next.view.fragment uses me.ykrank.s1next.data, so a change to me.ykrank.s1next.data can break me.ykrank.s1next.view.fragment, while a change to me.ykrank.s1next.view.fragment can't break me.ykrank.s1next.data.
- Position
- Below the diagonal: me.ykrank.s1next.view.fragment uses a module listed above it, which is the healthy direction.
31→18 me.ykrank.s1next.view.fragment uses com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.fragment uses a type in com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment.
- The types involved
me.ykrank.s1next.view.fragment.FavouriteListFragment→com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment.FragmentStatePagerAdapterme.ykrank.s1next.view.fragment.ThreadListFragment→com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment.FragmentStatePagerAdapter
- Direction
- me.ykrank.s1next.view.fragment uses com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment, so a change to com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment can break me.ykrank.s1next.view.fragment, while a change to me.ykrank.s1next.view.fragment can't break com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment.
- Position
- Below the diagonal: me.ykrank.s1next.view.fragment uses a module listed above it, which is the healthy direction.
31→20 me.ykrank.s1next.view.fragment uses me.ykrank.s1next.data.api.model.wrapper✕
- Connections
- 5 pairs of types, where a type in me.ykrank.s1next.view.fragment uses a type in me.ykrank.s1next.data.api.model.wrapper.
- The types involved
me.ykrank.s1next.view.fragment.FavouriteListPagerFragment→me.ykrank.s1next.data.api.model.wrapper.BaseResultWrapperme.ykrank.s1next.view.fragment.ForumFragment→me.ykrank.s1next.data.api.model.wrapper.ForumGroupsWrapperme.ykrank.s1next.view.fragment.FriendListFragment→me.ykrank.s1next.data.api.model.wrapper.BaseDataWrapperme.ykrank.s1next.view.fragment.NoteFragment→me.ykrank.s1next.data.api.model.wrapper.BaseDataWrapperme.ykrank.s1next.view.fragment.PmGroupsFragment→me.ykrank.s1next.data.api.model.wrapper.BaseDataWrapper
- Direction
- me.ykrank.s1next.view.fragment uses me.ykrank.s1next.data.api.model.wrapper, so a change to me.ykrank.s1next.data.api.model.wrapper can break me.ykrank.s1next.view.fragment, while a change to me.ykrank.s1next.view.fragment can't break me.ykrank.s1next.data.api.model.wrapper.
- Position
- Below the diagonal: me.ykrank.s1next.view.fragment uses a module listed above it, which is the healthy direction.
31→22 me.ykrank.s1next.view.fragment uses me.ykrank.s1next.data.api✕
- Connections
- 12 pairs of types, where a type in me.ykrank.s1next.view.fragment uses a type in me.ykrank.s1next.data.api.
- The types involved
me.ykrank.s1next.view.fragment.BaseFragment→me.ykrank.s1next.data.api.UserValidatorme.ykrank.s1next.view.fragment.BaseLoadMoreRecycleViewFragment→me.ykrank.s1next.data.api.ApiCacheProviderme.ykrank.s1next.view.fragment.BaseLoadMoreRecycleViewFragment→me.ykrank.s1next.data.api.S1Serviceme.ykrank.s1next.view.fragment.BaseLoadMoreRecycleViewFragment→me.ykrank.s1next.data.api.UserValidatorme.ykrank.s1next.view.fragment.BaseRecyclerViewFragment→me.ykrank.s1next.data.api.ApiCacheProviderme.ykrank.s1next.view.fragment.BaseRecyclerViewFragment→me.ykrank.s1next.data.api.S1Serviceme.ykrank.s1next.view.fragment.BaseRecyclerViewFragment→me.ykrank.s1next.data.api.UserValidatorme.ykrank.s1next.view.fragment.BaseViewPagerFragment→me.ykrank.s1next.data.api.UserValidatorme.ykrank.s1next.view.fragment.EditPostFragment→me.ykrank.s1next.data.api.S1Serviceme.ykrank.s1next.view.fragment.FavouriteListFragment→me.ykrank.s1next.data.api.S1Serviceme.ykrank.s1next.view.fragment.NewRateFragment→me.ykrank.s1next.data.api.S1Serviceme.ykrank.s1next.view.fragment.NewReportFragment→me.ykrank.s1next.data.api.S1Service
- Direction
- me.ykrank.s1next.view.fragment uses me.ykrank.s1next.data.api, so a change to me.ykrank.s1next.data.api can break me.ykrank.s1next.view.fragment, while a change to me.ykrank.s1next.view.fragment can't break me.ykrank.s1next.data.api.
- Position
- Below the diagonal: me.ykrank.s1next.view.fragment uses a module listed above it, which is the healthy direction.
31→24 me.ykrank.s1next.view.fragment uses me.ykrank.s1next.view.internal✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.fragment uses a type in me.ykrank.s1next.view.internal.
- The types involved
me.ykrank.s1next.view.fragment.WebViewFragment→me.ykrank.s1next.view.internal.BackPressDelegate
- Direction
- me.ykrank.s1next.view.fragment uses me.ykrank.s1next.view.internal, so a change to me.ykrank.s1next.view.internal can break me.ykrank.s1next.view.fragment, while a change to me.ykrank.s1next.view.fragment can't break me.ykrank.s1next.view.internal.
- Position
- Below the diagonal: me.ykrank.s1next.view.fragment uses a module listed above it, which is the healthy direction.
31→26 me.ykrank.s1next.view.fragment uses me.ykrank.s1next.view.adapter✕
- Connections
- 10 pairs of types, where a type in me.ykrank.s1next.view.fragment uses a type in me.ykrank.s1next.view.adapter.
- The types involved
me.ykrank.s1next.view.fragment.DarkRoomFragment→me.ykrank.s1next.view.adapter.BaseRecyclerViewAdapterme.ykrank.s1next.view.fragment.FavouriteListPagerFragment→me.ykrank.s1next.view.adapter.FavouriteRecyclerViewAdapterme.ykrank.s1next.view.fragment.HistoryListFragment→me.ykrank.s1next.view.adapter.HistoryCursorRecyclerViewAdapterme.ykrank.s1next.view.fragment.NoteFragment→me.ykrank.s1next.view.adapter.BaseRecyclerViewAdapterme.ykrank.s1next.view.fragment.PmFragment→me.ykrank.s1next.view.adapter.BaseRecyclerViewAdapterme.ykrank.s1next.view.fragment.PmFragment→me.ykrank.s1next.view.adapter.PmRecyclerViewAdapterme.ykrank.s1next.view.fragment.PmGroupsFragment→me.ykrank.s1next.view.adapter.BaseRecyclerViewAdapterme.ykrank.s1next.view.fragment.ThreadListPagerFragment→me.ykrank.s1next.view.adapter.ThreadRecyclerViewAdapterme.ykrank.s1next.view.fragment.UserReplyFragment→me.ykrank.s1next.view.adapter.BaseRecyclerViewAdapterme.ykrank.s1next.view.fragment.UserThreadFragment→me.ykrank.s1next.view.adapter.BaseRecyclerViewAdapter
- Direction
- me.ykrank.s1next.view.fragment uses me.ykrank.s1next.view.adapter, so a change to me.ykrank.s1next.view.adapter can break me.ykrank.s1next.view.fragment, while a change to me.ykrank.s1next.view.fragment can't break me.ykrank.s1next.view.adapter.
- Position
- Below the diagonal: me.ykrank.s1next.view.fragment uses a module listed above it, which is the healthy direction.
31→28 me.ykrank.s1next.view.fragment uses me.ykrank.s1next.view.page.post.postedit✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.fragment uses a type in me.ykrank.s1next.view.page.post.postedit.
- The types involved
me.ykrank.s1next.view.fragment.EditPostFragment→me.ykrank.s1next.view.page.post.postedit.BasePostEditFragment
- Direction
- me.ykrank.s1next.view.fragment uses me.ykrank.s1next.view.page.post.postedit, so a change to me.ykrank.s1next.view.page.post.postedit can break me.ykrank.s1next.view.fragment, while a change to me.ykrank.s1next.view.fragment can't break me.ykrank.s1next.view.page.post.postedit.
- Position
- Below the diagonal: me.ykrank.s1next.view.fragment uses a module listed above it, which is the healthy direction.
31→29 me.ykrank.s1next.view.fragment uses me.ykrank.s1next.widget.hostcheck✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.fragment uses a type in me.ykrank.s1next.widget.hostcheck.
- The types involved
me.ykrank.s1next.view.fragment.WebLoginFragment→me.ykrank.s1next.widget.hostcheck.AppHostUrl
- Direction
- me.ykrank.s1next.view.fragment uses me.ykrank.s1next.widget.hostcheck, so a change to me.ykrank.s1next.widget.hostcheck can break me.ykrank.s1next.view.fragment, while a change to me.ykrank.s1next.view.fragment can't break me.ykrank.s1next.widget.hostcheck.
- Position
- Below the diagonal: me.ykrank.s1next.view.fragment uses a module listed above it, which is the healthy direction.
32→4 me.ykrank.s1next.view.page.post.adapter uses com.github.ykrank.androidtools.widget✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.page.post.adapter uses a type in com.github.ykrank.androidtools.widget.
- The types involved
me.ykrank.s1next.view.page.post.adapter.PostAdapterDelegate→com.github.ykrank.androidtools.widget.EventBusme.ykrank.s1next.view.page.post.adapter.PostBlackAdapterDelegate→com.github.ykrank.androidtools.widget.EventBus
- Direction
- me.ykrank.s1next.view.page.post.adapter uses com.github.ykrank.androidtools.widget, so a change to com.github.ykrank.androidtools.widget can break me.ykrank.s1next.view.page.post.adapter, while a change to me.ykrank.s1next.view.page.post.adapter can't break com.github.ykrank.androidtools.widget.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.adapter uses a module listed above it, which is the healthy direction.
32→11 me.ykrank.s1next.view.page.post.adapter uses me.ykrank.s1next.data.api.model✕
- Connections
- 8 pairs of types, where a type in me.ykrank.s1next.view.page.post.adapter uses a type in me.ykrank.s1next.data.api.model.
- The types involved
me.ykrank.s1next.view.page.post.adapter.PostAdapterDelegate→me.ykrank.s1next.data.api.model.Postme.ykrank.s1next.view.page.post.adapter.PostAdapterDelegate→me.ykrank.s1next.data.api.model.Threadme.ykrank.s1next.view.page.post.adapter.PostAdapterDelegate→me.ykrank.s1next.data.api.model.Voteme.ykrank.s1next.view.page.post.adapter.PostBlackAdapterDelegate→me.ykrank.s1next.data.api.model.Postme.ykrank.s1next.view.page.post.adapter.PostBlackAdapterDelegate→me.ykrank.s1next.data.api.model.Threadme.ykrank.s1next.view.page.post.adapter.PostBlackAdapterDelegate→me.ykrank.s1next.data.api.model.Voteme.ykrank.s1next.view.page.post.adapter.PostListRecyclerViewAdapter→me.ykrank.s1next.data.api.model.Threadme.ykrank.s1next.view.page.post.adapter.PostListRecyclerViewAdapter→me.ykrank.s1next.data.api.model.Vote
- Direction
- me.ykrank.s1next.view.page.post.adapter uses me.ykrank.s1next.data.api.model, so a change to me.ykrank.s1next.data.api.model can break me.ykrank.s1next.view.page.post.adapter, while a change to me.ykrank.s1next.view.page.post.adapter can't break me.ykrank.s1next.data.api.model.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.adapter uses a module listed above it, which is the healthy direction.
32→13 me.ykrank.s1next.view.page.post.adapter uses me.ykrank.s1next.data.pref✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.page.post.adapter uses a type in me.ykrank.s1next.data.pref.
- The types involved
me.ykrank.s1next.view.page.post.adapter.PostAdapterDelegate→me.ykrank.s1next.data.pref.GeneralPreferencesManagerme.ykrank.s1next.view.page.post.adapter.PostBlackAdapterDelegate→me.ykrank.s1next.data.pref.GeneralPreferencesManager
- Direction
- me.ykrank.s1next.view.page.post.adapter uses me.ykrank.s1next.data.pref, so a change to me.ykrank.s1next.data.pref can break me.ykrank.s1next.view.page.post.adapter, while a change to me.ykrank.s1next.view.page.post.adapter can't break me.ykrank.s1next.data.pref.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.adapter uses a module listed above it, which is the healthy direction.
32→15 me.ykrank.s1next.view.page.post.adapter uses me.ykrank.s1next.data✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.post.adapter uses a type in me.ykrank.s1next.data.
- The types involved
me.ykrank.s1next.view.page.post.adapter.PostAdapterDelegate→me.ykrank.s1next.data.User
- Direction
- me.ykrank.s1next.view.page.post.adapter uses me.ykrank.s1next.data, so a change to me.ykrank.s1next.data can break me.ykrank.s1next.view.page.post.adapter, while a change to me.ykrank.s1next.view.page.post.adapter can't break me.ykrank.s1next.data.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.adapter uses a module listed above it, which is the healthy direction.
32→22 me.ykrank.s1next.view.page.post.adapter uses me.ykrank.s1next.data.api✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.page.post.adapter uses a type in me.ykrank.s1next.data.api.
- The types involved
me.ykrank.s1next.view.page.post.adapter.PostAdapterDelegate→me.ykrank.s1next.data.api.ApiCacheProviderme.ykrank.s1next.view.page.post.adapter.PostBlackAdapterDelegate→me.ykrank.s1next.data.api.S1Service
- Direction
- me.ykrank.s1next.view.page.post.adapter uses me.ykrank.s1next.data.api, so a change to me.ykrank.s1next.data.api can break me.ykrank.s1next.view.page.post.adapter, while a change to me.ykrank.s1next.view.page.post.adapter can't break me.ykrank.s1next.data.api.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.adapter uses a module listed above it, which is the healthy direction.
32→23 me.ykrank.s1next.view.page.post.adapter uses me.ykrank.s1next.view.adapter.delegate✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.page.post.adapter uses a type in me.ykrank.s1next.view.adapter.delegate.
- The types involved
me.ykrank.s1next.view.page.post.adapter.PostAdapterDelegate→me.ykrank.s1next.view.adapter.delegate.BaseAdapterDelegateme.ykrank.s1next.view.page.post.adapter.PostBlackAdapterDelegate→me.ykrank.s1next.view.adapter.delegate.BaseAdapterDelegate
- Direction
- me.ykrank.s1next.view.page.post.adapter uses me.ykrank.s1next.view.adapter.delegate, so a change to me.ykrank.s1next.view.adapter.delegate can break me.ykrank.s1next.view.page.post.adapter, while a change to me.ykrank.s1next.view.page.post.adapter can't break me.ykrank.s1next.view.adapter.delegate.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.adapter uses a module listed above it, which is the healthy direction.
32→26 me.ykrank.s1next.view.page.post.adapter uses me.ykrank.s1next.view.adapter✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.post.adapter uses a type in me.ykrank.s1next.view.adapter.
- The types involved
me.ykrank.s1next.view.page.post.adapter.PostListRecyclerViewAdapter→me.ykrank.s1next.view.adapter.BaseRecyclerViewAdapter
- Direction
- me.ykrank.s1next.view.page.post.adapter uses me.ykrank.s1next.view.adapter, so a change to me.ykrank.s1next.view.adapter can break me.ykrank.s1next.view.page.post.adapter, while a change to me.ykrank.s1next.view.page.post.adapter can't break me.ykrank.s1next.view.adapter.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.adapter uses a module listed above it, which is the healthy direction.
33→4 me.ykrank.s1next.view.page.setting.fragment uses com.github.ykrank.androidtools.widget✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.page.setting.fragment uses a type in com.github.ykrank.androidtools.widget.
- The types involved
me.ykrank.s1next.view.page.setting.fragment.BackupPreferenceFragment→com.github.ykrank.androidtools.widget.BackupDelegateme.ykrank.s1next.view.page.setting.fragment.GeneralPreferenceFragment→com.github.ykrank.androidtools.widget.EventBus
- Direction
- me.ykrank.s1next.view.page.setting.fragment uses com.github.ykrank.androidtools.widget, so a change to com.github.ykrank.androidtools.widget can break me.ykrank.s1next.view.page.setting.fragment, while a change to me.ykrank.s1next.view.page.setting.fragment can't break com.github.ykrank.androidtools.widget.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.setting.fragment uses a module listed above it, which is the healthy direction.
33→6 me.ykrank.s1next.view.page.setting.fragment uses me.ykrank.s1next.data.cache.biz✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.setting.fragment uses a type in me.ykrank.s1next.data.cache.biz.
- The types involved
me.ykrank.s1next.view.page.setting.fragment.DownloadPreferenceFragment→me.ykrank.s1next.data.cache.biz.CacheBiz
- Direction
- me.ykrank.s1next.view.page.setting.fragment uses me.ykrank.s1next.data.cache.biz, so a change to me.ykrank.s1next.data.cache.biz can break me.ykrank.s1next.view.page.setting.fragment, while a change to me.ykrank.s1next.view.page.setting.fragment can't break me.ykrank.s1next.data.cache.biz.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.setting.fragment uses a module listed above it, which is the healthy direction.
33→8 me.ykrank.s1next.view.page.setting.fragment uses com.github.ykrank.androidtools.widget.track✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.setting.fragment uses a type in com.github.ykrank.androidtools.widget.track.
- The types involved
me.ykrank.s1next.view.page.setting.fragment.GeneralPreferenceFragment→com.github.ykrank.androidtools.widget.track.DataTrackAgent
- Direction
- me.ykrank.s1next.view.page.setting.fragment uses com.github.ykrank.androidtools.widget.track, so a change to com.github.ykrank.androidtools.widget.track can break me.ykrank.s1next.view.page.setting.fragment, while a change to me.ykrank.s1next.view.page.setting.fragment can't break com.github.ykrank.androidtools.widget.track.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.setting.fragment uses a module listed above it, which is the healthy direction.
33→13 me.ykrank.s1next.view.page.setting.fragment uses me.ykrank.s1next.data.pref✕
- Connections
- 4 pairs of types, where a type in me.ykrank.s1next.view.page.setting.fragment uses a type in me.ykrank.s1next.data.pref.
- The types involved
me.ykrank.s1next.view.page.setting.fragment.DownloadPreferenceFragment→me.ykrank.s1next.data.pref.DownloadPreferencesManagerme.ykrank.s1next.view.page.setting.fragment.GeneralPreferenceFragment→me.ykrank.s1next.data.pref.GeneralPreferencesManagerme.ykrank.s1next.view.page.setting.fragment.NetworkPreferenceFragment→me.ykrank.s1next.data.pref.NetworkPreferencesManagerme.ykrank.s1next.view.page.setting.fragment.ReadPreferenceFragment→me.ykrank.s1next.data.pref.ReadPreferencesManager
- Direction
- me.ykrank.s1next.view.page.setting.fragment uses me.ykrank.s1next.data.pref, so a change to me.ykrank.s1next.data.pref can break me.ykrank.s1next.view.page.setting.fragment, while a change to me.ykrank.s1next.view.page.setting.fragment can't break me.ykrank.s1next.data.pref.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.setting.fragment uses a module listed above it, which is the healthy direction.
33→14 me.ykrank.s1next.view.page.setting.fragment uses com.github.ykrank.androidtools.ui✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.setting.fragment uses a type in com.github.ykrank.androidtools.ui.
- The types involved
me.ykrank.s1next.view.page.setting.fragment.BasePreferenceFragment→com.github.ykrank.androidtools.ui.LibBasePreferenceFragment
- Direction
- me.ykrank.s1next.view.page.setting.fragment uses com.github.ykrank.androidtools.ui, so a change to com.github.ykrank.androidtools.ui can break me.ykrank.s1next.view.page.setting.fragment, while a change to me.ykrank.s1next.view.page.setting.fragment can't break com.github.ykrank.androidtools.ui.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.setting.fragment uses a module listed above it, which is the healthy direction.
33→15 me.ykrank.s1next.view.page.setting.fragment uses me.ykrank.s1next.data✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.setting.fragment uses a type in me.ykrank.s1next.data.
- The types involved
me.ykrank.s1next.view.page.setting.fragment.DownloadPreferenceFragment→me.ykrank.s1next.data.User
- Direction
- me.ykrank.s1next.view.page.setting.fragment uses me.ykrank.s1next.data, so a change to me.ykrank.s1next.data can break me.ykrank.s1next.view.page.setting.fragment, while a change to me.ykrank.s1next.view.page.setting.fragment can't break me.ykrank.s1next.data.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.setting.fragment uses a module listed above it, which is the healthy direction.
33→16 me.ykrank.s1next.view.page.setting.fragment uses me.ykrank.s1next.data.db✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.setting.fragment uses a type in me.ykrank.s1next.data.db.
- The types involved
me.ykrank.s1next.view.page.setting.fragment.BackupPreferenceFragment→me.ykrank.s1next.data.db.AppDatabaseManager
- Direction
- me.ykrank.s1next.view.page.setting.fragment uses me.ykrank.s1next.data.db, so a change to me.ykrank.s1next.data.db can break me.ykrank.s1next.view.page.setting.fragment, while a change to me.ykrank.s1next.view.page.setting.fragment can't break me.ykrank.s1next.data.db.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.setting.fragment uses a module listed above it, which is the healthy direction.
33→29 me.ykrank.s1next.view.page.setting.fragment uses me.ykrank.s1next.widget.hostcheck✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.setting.fragment uses a type in me.ykrank.s1next.widget.hostcheck.
- The types involved
me.ykrank.s1next.view.page.setting.fragment.NetworkPreferenceFragment→me.ykrank.s1next.widget.hostcheck.AppHostUrl
- Direction
- me.ykrank.s1next.view.page.setting.fragment uses me.ykrank.s1next.widget.hostcheck, so a change to me.ykrank.s1next.widget.hostcheck can break me.ykrank.s1next.view.page.setting.fragment, while a change to me.ykrank.s1next.view.page.setting.fragment can't break me.ykrank.s1next.widget.hostcheck.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.setting.fragment uses a module listed above it, which is the healthy direction.
34→3 me.ykrank.s1next.view.activity uses com.github.ykrank.androidtools.ui.internal✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.activity uses a type in com.github.ykrank.androidtools.ui.internal.
- The types involved
me.ykrank.s1next.view.activity.BaseActivity→com.github.ykrank.androidtools.ui.internal.CoordinatorLayoutAnchorDelegateme.ykrank.s1next.view.activity.BaseActivity→com.github.ykrank.androidtools.ui.internal.DrawerLayoutDelegate
- Direction
- me.ykrank.s1next.view.activity uses com.github.ykrank.androidtools.ui.internal, so a change to com.github.ykrank.androidtools.ui.internal can break me.ykrank.s1next.view.activity, while a change to me.ykrank.s1next.view.activity can't break com.github.ykrank.androidtools.ui.internal.
- Position
- Below the diagonal: me.ykrank.s1next.view.activity uses a module listed above it, which is the healthy direction.
34→4 me.ykrank.s1next.view.activity uses com.github.ykrank.androidtools.widget✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.activity uses a type in com.github.ykrank.androidtools.widget.
- The types involved
me.ykrank.s1next.view.activity.BaseActivity→com.github.ykrank.androidtools.widget.EventBus
- Direction
- me.ykrank.s1next.view.activity uses com.github.ykrank.androidtools.widget, so a change to com.github.ykrank.androidtools.widget can break me.ykrank.s1next.view.activity, while a change to me.ykrank.s1next.view.activity can't break com.github.ykrank.androidtools.widget.
- Position
- Below the diagonal: me.ykrank.s1next.view.activity uses a module listed above it, which is the healthy direction.
34→8 me.ykrank.s1next.view.activity uses com.github.ykrank.androidtools.widget.track✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.activity uses a type in com.github.ykrank.androidtools.widget.track.
- The types involved
me.ykrank.s1next.view.activity.BaseActivity→com.github.ykrank.androidtools.widget.track.DataTrackAgentme.ykrank.s1next.view.activity.GalleryActivity→com.github.ykrank.androidtools.widget.track.DataTrackAgent
- Direction
- me.ykrank.s1next.view.activity uses com.github.ykrank.androidtools.widget.track, so a change to com.github.ykrank.androidtools.widget.track can break me.ykrank.s1next.view.activity, while a change to me.ykrank.s1next.view.activity can't break com.github.ykrank.androidtools.widget.track.
- Position
- Below the diagonal: me.ykrank.s1next.view.activity uses a module listed above it, which is the healthy direction.
34→11 me.ykrank.s1next.view.activity uses me.ykrank.s1next.data.api.model✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.activity uses a type in me.ykrank.s1next.data.api.model.
- The types involved
me.ykrank.s1next.view.activity.ThreadListActivity→me.ykrank.s1next.data.api.model.Forumme.ykrank.s1next.view.activity.ThreadListActivity→me.ykrank.s1next.data.api.model.ThreadType
- Direction
- me.ykrank.s1next.view.activity uses me.ykrank.s1next.data.api.model, so a change to me.ykrank.s1next.data.api.model can break me.ykrank.s1next.view.activity, while a change to me.ykrank.s1next.view.activity can't break me.ykrank.s1next.data.api.model.
- Position
- Below the diagonal: me.ykrank.s1next.view.activity uses a module listed above it, which is the healthy direction.
34→13 me.ykrank.s1next.view.activity uses me.ykrank.s1next.data.pref✕
- Connections
- 4 pairs of types, where a type in me.ykrank.s1next.view.activity uses a type in me.ykrank.s1next.data.pref.
- The types involved
me.ykrank.s1next.view.activity.BaseActivity→me.ykrank.s1next.data.pref.DataPreferencesManagerme.ykrank.s1next.view.activity.BaseActivity→me.ykrank.s1next.data.pref.DownloadPreferencesManagerme.ykrank.s1next.view.activity.BaseActivity→me.ykrank.s1next.data.pref.GeneralPreferencesManagerme.ykrank.s1next.view.activity.ForumActivity→me.ykrank.s1next.data.pref.ReadPreferencesManager
- Direction
- me.ykrank.s1next.view.activity uses me.ykrank.s1next.data.pref, so a change to me.ykrank.s1next.data.pref can break me.ykrank.s1next.view.activity, while a change to me.ykrank.s1next.view.activity can't break me.ykrank.s1next.data.pref.
- Position
- Below the diagonal: me.ykrank.s1next.view.activity uses a module listed above it, which is the healthy direction.
34→14 me.ykrank.s1next.view.activity uses com.github.ykrank.androidtools.ui✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.activity uses a type in com.github.ykrank.androidtools.ui.
- The types involved
me.ykrank.s1next.view.activity.BaseActivity→com.github.ykrank.androidtools.ui.LibBaseActivity
- Direction
- me.ykrank.s1next.view.activity uses com.github.ykrank.androidtools.ui, so a change to com.github.ykrank.androidtools.ui can break me.ykrank.s1next.view.activity, while a change to me.ykrank.s1next.view.activity can't break com.github.ykrank.androidtools.ui.
- Position
- Below the diagonal: me.ykrank.s1next.view.activity uses a module listed above it, which is the healthy direction.
34→15 me.ykrank.s1next.view.activity uses me.ykrank.s1next.data✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.activity uses a type in me.ykrank.s1next.data.
- The types involved
me.ykrank.s1next.view.activity.BaseActivity→me.ykrank.s1next.data.User
- Direction
- me.ykrank.s1next.view.activity uses me.ykrank.s1next.data, so a change to me.ykrank.s1next.data can break me.ykrank.s1next.view.activity, while a change to me.ykrank.s1next.view.activity can't break me.ykrank.s1next.data.
- Position
- Below the diagonal: me.ykrank.s1next.view.activity uses a module listed above it, which is the healthy direction.
34→22 me.ykrank.s1next.view.activity uses me.ykrank.s1next.data.api✕
- Connections
- 4 pairs of types, where a type in me.ykrank.s1next.view.activity uses a type in me.ykrank.s1next.data.api.
- The types involved
me.ykrank.s1next.view.activity.SearchActivity→me.ykrank.s1next.data.api.S1Serviceme.ykrank.s1next.view.activity.SearchActivity→me.ykrank.s1next.data.api.UserValidatorme.ykrank.s1next.view.activity.ThreadListActivity→me.ykrank.s1next.data.api.S1Serviceme.ykrank.s1next.view.activity.UserHomeActivity→me.ykrank.s1next.data.api.S1Service
- Direction
- me.ykrank.s1next.view.activity uses me.ykrank.s1next.data.api, so a change to me.ykrank.s1next.data.api can break me.ykrank.s1next.view.activity, while a change to me.ykrank.s1next.view.activity can't break me.ykrank.s1next.data.api.
- Position
- Below the diagonal: me.ykrank.s1next.view.activity uses a module listed above it, which is the healthy direction.
34→24 me.ykrank.s1next.view.activity uses me.ykrank.s1next.view.internal✕
- Connections
- 3 pairs of types, where a type in me.ykrank.s1next.view.activity uses a type in me.ykrank.s1next.view.internal.
- The types involved
me.ykrank.s1next.view.activity.BaseActivity→me.ykrank.s1next.view.internal.DrawerLayoutDelegateConcreteme.ykrank.s1next.view.activity.BaseActivity→me.ykrank.s1next.view.internal.ToolbarDelegateme.ykrank.s1next.view.activity.HelpActivity→me.ykrank.s1next.view.internal.ToolbarDelegate
- Direction
- me.ykrank.s1next.view.activity uses me.ykrank.s1next.view.internal, so a change to me.ykrank.s1next.view.internal can break me.ykrank.s1next.view.activity, while a change to me.ykrank.s1next.view.activity can't break me.ykrank.s1next.view.internal.
- Position
- Below the diagonal: me.ykrank.s1next.view.activity uses a module listed above it, which is the healthy direction.
34→26 me.ykrank.s1next.view.activity uses me.ykrank.s1next.view.adapter✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.activity uses a type in me.ykrank.s1next.view.adapter.
- The types involved
me.ykrank.s1next.view.activity.ThreadListActivity→me.ykrank.s1next.view.adapter.SubForumArrayAdapter
- Direction
- me.ykrank.s1next.view.activity uses me.ykrank.s1next.view.adapter, so a change to me.ykrank.s1next.view.adapter can break me.ykrank.s1next.view.activity, while a change to me.ykrank.s1next.view.activity can't break me.ykrank.s1next.view.adapter.
- Position
- Below the diagonal: me.ykrank.s1next.view.activity uses a module listed above it, which is the healthy direction.
34→28 me.ykrank.s1next.view.activity uses me.ykrank.s1next.view.page.post.postedit✕
- Connections
- 3 pairs of types, where a type in me.ykrank.s1next.view.activity uses a type in me.ykrank.s1next.view.page.post.postedit.
- The types involved
me.ykrank.s1next.view.activity.NewPmActivity→me.ykrank.s1next.view.page.post.postedit.NewPmFragmentme.ykrank.s1next.view.activity.NewThreadActivity→me.ykrank.s1next.view.page.post.postedit.NewThreadFragmentme.ykrank.s1next.view.activity.ReplyActivity→me.ykrank.s1next.view.page.post.postedit.ReplyFragment
- Direction
- me.ykrank.s1next.view.activity uses me.ykrank.s1next.view.page.post.postedit, so a change to me.ykrank.s1next.view.page.post.postedit can break me.ykrank.s1next.view.activity, while a change to me.ykrank.s1next.view.activity can't break me.ykrank.s1next.view.page.post.postedit.
- Position
- Below the diagonal: me.ykrank.s1next.view.activity uses a module listed above it, which is the healthy direction.
34→31 me.ykrank.s1next.view.activity uses me.ykrank.s1next.view.fragment✕
- Connections
- 6 pairs of types, where a type in me.ykrank.s1next.view.activity uses a type in me.ykrank.s1next.view.fragment.
- The types involved
me.ykrank.s1next.view.activity.DarkRoomActivity→me.ykrank.s1next.view.fragment.DarkRoomFragmentme.ykrank.s1next.view.activity.ForumActivity→me.ykrank.s1next.view.fragment.ForumFragmentme.ykrank.s1next.view.activity.HelpActivity→me.ykrank.s1next.view.fragment.HelpFragmentme.ykrank.s1next.view.activity.NewRateActivity→me.ykrank.s1next.view.fragment.NewRateFragmentme.ykrank.s1next.view.activity.NewReportActivity→me.ykrank.s1next.view.fragment.NewReportFragmentme.ykrank.s1next.view.activity.ThreadListActivity→me.ykrank.s1next.view.fragment.ThreadListFragment
- Direction
- me.ykrank.s1next.view.activity uses me.ykrank.s1next.view.fragment, so a change to me.ykrank.s1next.view.fragment can break me.ykrank.s1next.view.activity, while a change to me.ykrank.s1next.view.activity can't break me.ykrank.s1next.view.fragment.
- Position
- Below the diagonal: me.ykrank.s1next.view.activity uses a module listed above it, which is the healthy direction.
35→4 me.ykrank.s1next.view.page.login uses com.github.ykrank.androidtools.widget✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.login uses a type in com.github.ykrank.androidtools.widget.
- The types involved
me.ykrank.s1next.view.page.login.BaseLoginDialogFragment→com.github.ykrank.androidtools.widget.EventBus
- Direction
- me.ykrank.s1next.view.page.login uses com.github.ykrank.androidtools.widget, so a change to com.github.ykrank.androidtools.widget can break me.ykrank.s1next.view.page.login, while a change to me.ykrank.s1next.view.page.login can't break com.github.ykrank.androidtools.widget.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.login uses a module listed above it, which is the healthy direction.
35→10 me.ykrank.s1next.view.page.login uses me.ykrank.s1next.data.api.app.model✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.page.login uses a type in me.ykrank.s1next.data.api.app.model.
- The types involved
me.ykrank.s1next.view.page.login.AppLoginDialogFragment→me.ykrank.s1next.data.api.app.model.AppDataWrapperme.ykrank.s1next.view.page.login.AppLoginDialogFragment→me.ykrank.s1next.data.api.app.model.AppLoginResult
- Direction
- me.ykrank.s1next.view.page.login uses me.ykrank.s1next.data.api.app.model, so a change to me.ykrank.s1next.data.api.app.model can break me.ykrank.s1next.view.page.login, while a change to me.ykrank.s1next.view.page.login can't break me.ykrank.s1next.data.api.app.model.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.login uses a module listed above it, which is the healthy direction.
35→12 me.ykrank.s1next.view.page.login uses me.ykrank.s1next.data.db.biz✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.login uses a type in me.ykrank.s1next.data.db.biz.
- The types involved
me.ykrank.s1next.view.page.login.BaseLoginFragment→me.ykrank.s1next.data.db.biz.LoginUserBiz
- Direction
- me.ykrank.s1next.view.page.login uses me.ykrank.s1next.data.db.biz, so a change to me.ykrank.s1next.data.db.biz can break me.ykrank.s1next.view.page.login, while a change to me.ykrank.s1next.view.page.login can't break me.ykrank.s1next.data.db.biz.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.login uses a module listed above it, which is the healthy direction.
35→19 me.ykrank.s1next.view.page.login uses me.ykrank.s1next.data.api.app✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.login uses a type in me.ykrank.s1next.data.api.app.
- The types involved
me.ykrank.s1next.view.page.login.AppLoginDialogFragment→me.ykrank.s1next.data.api.app.AppService
- Direction
- me.ykrank.s1next.view.page.login uses me.ykrank.s1next.data.api.app, so a change to me.ykrank.s1next.data.api.app can break me.ykrank.s1next.view.page.login, while a change to me.ykrank.s1next.view.page.login can't break me.ykrank.s1next.data.api.app.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.login uses a module listed above it, which is the healthy direction.
35→20 me.ykrank.s1next.view.page.login uses me.ykrank.s1next.data.api.model.wrapper✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.login uses a type in me.ykrank.s1next.data.api.model.wrapper.
- The types involved
me.ykrank.s1next.view.page.login.LoginDialogFragment→me.ykrank.s1next.data.api.model.wrapper.AccountResultWrapper
- Direction
- me.ykrank.s1next.view.page.login uses me.ykrank.s1next.data.api.model.wrapper, so a change to me.ykrank.s1next.data.api.model.wrapper can break me.ykrank.s1next.view.page.login, while a change to me.ykrank.s1next.view.page.login can't break me.ykrank.s1next.data.api.model.wrapper.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.login uses a module listed above it, which is the healthy direction.
35→27 me.ykrank.s1next.view.page.login uses me.ykrank.s1next.view.dialog✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.login uses a type in me.ykrank.s1next.view.dialog.
- The types involved
me.ykrank.s1next.view.page.login.BaseLoginDialogFragment→me.ykrank.s1next.view.dialog.ProgressDialogFragment
- Direction
- me.ykrank.s1next.view.page.login uses me.ykrank.s1next.view.dialog, so a change to me.ykrank.s1next.view.dialog can break me.ykrank.s1next.view.page.login, while a change to me.ykrank.s1next.view.page.login can't break me.ykrank.s1next.view.dialog.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.login uses a module listed above it, which is the healthy direction.
35→31 me.ykrank.s1next.view.page.login uses me.ykrank.s1next.view.fragment✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.login uses a type in me.ykrank.s1next.view.fragment.
- The types involved
me.ykrank.s1next.view.page.login.BaseLoginFragment→me.ykrank.s1next.view.fragment.BaseFragment
- Direction
- me.ykrank.s1next.view.page.login uses me.ykrank.s1next.view.fragment, so a change to me.ykrank.s1next.view.fragment can break me.ykrank.s1next.view.page.login, while a change to me.ykrank.s1next.view.page.login can't break me.ykrank.s1next.view.fragment.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.login uses a module listed above it, which is the healthy direction.
36→4 me.ykrank.s1next.view.page.post.postedit.toolstab uses com.github.ykrank.androidtools.widget✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.post.postedit.toolstab uses a type in com.github.ykrank.androidtools.widget.
- The types involved
me.ykrank.s1next.view.page.post.postedit.toolstab.ImageUploadFragment→com.github.ykrank.androidtools.widget.EventBus
- Direction
- me.ykrank.s1next.view.page.post.postedit.toolstab uses com.github.ykrank.androidtools.widget, so a change to com.github.ykrank.androidtools.widget can break me.ykrank.s1next.view.page.post.postedit.toolstab, while a change to me.ykrank.s1next.view.page.post.postedit.toolstab can't break com.github.ykrank.androidtools.widget.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.postedit.toolstab uses a module listed above it, which is the healthy direction.
36→9 me.ykrank.s1next.view.page.post.postedit.toolstab uses com.github.ykrank.androidtools.widget.uploadimg✕
- Connections
- 3 pairs of types, where a type in me.ykrank.s1next.view.page.post.postedit.toolstab uses a type in com.github.ykrank.androidtools.widget.uploadimg.
- The types involved
me.ykrank.s1next.view.page.post.postedit.toolstab.ImageUploadFragment→com.github.ykrank.androidtools.widget.uploadimg.ImageUploadManagerme.ykrank.s1next.view.page.post.postedit.toolstab.ImageUploadFragment→com.github.ykrank.androidtools.widget.uploadimg.LibImageUploadFragmentme.ykrank.s1next.view.page.post.postedit.toolstab.ImageUploadFragment→com.github.ykrank.androidtools.widget.uploadimg.ModelImageUpload
- Direction
- me.ykrank.s1next.view.page.post.postedit.toolstab uses com.github.ykrank.androidtools.widget.uploadimg, so a change to com.github.ykrank.androidtools.widget.uploadimg can break me.ykrank.s1next.view.page.post.postedit.toolstab, while a change to me.ykrank.s1next.view.page.post.postedit.toolstab can't break com.github.ykrank.androidtools.widget.uploadimg.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.postedit.toolstab uses a module listed above it, which is the healthy direction.
36→31 me.ykrank.s1next.view.page.post.postedit.toolstab uses me.ykrank.s1next.view.fragment✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.post.postedit.toolstab uses a type in me.ykrank.s1next.view.fragment.
- The types involved
me.ykrank.s1next.view.page.post.postedit.toolstab.PostToolsExtrasFragment→me.ykrank.s1next.view.fragment.BaseFragment
- Direction
- me.ykrank.s1next.view.page.post.postedit.toolstab uses me.ykrank.s1next.view.fragment, so a change to me.ykrank.s1next.view.fragment can break me.ykrank.s1next.view.page.post.postedit.toolstab, while a change to me.ykrank.s1next.view.page.post.postedit.toolstab can't break me.ykrank.s1next.view.fragment.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.postedit.toolstab uses a module listed above it, which is the healthy direction.
37→4 me.ykrank.s1next.view.page.setting.blacklist uses com.github.ykrank.androidtools.widget✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.setting.blacklist uses a type in com.github.ykrank.androidtools.widget.
- The types involved
me.ykrank.s1next.view.page.setting.blacklist.BlackListRemarkDialogFragment→com.github.ykrank.androidtools.widget.EventBus
- Direction
- me.ykrank.s1next.view.page.setting.blacklist uses com.github.ykrank.androidtools.widget, so a change to com.github.ykrank.androidtools.widget can break me.ykrank.s1next.view.page.setting.blacklist, while a change to me.ykrank.s1next.view.page.setting.blacklist can't break com.github.ykrank.androidtools.widget.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.setting.blacklist uses a module listed above it, which is the healthy direction.
37→7 me.ykrank.s1next.view.page.setting.blacklist uses me.ykrank.s1next.data.db.dbmodel✕
- Connections
- 4 pairs of types, where a type in me.ykrank.s1next.view.page.setting.blacklist uses a type in me.ykrank.s1next.data.db.dbmodel.
- The types involved
me.ykrank.s1next.view.page.setting.blacklist.BlackListCursorListViewAdapter→me.ykrank.s1next.data.db.dbmodel.BlackListme.ykrank.s1next.view.page.setting.blacklist.BlackListSettingFragment→me.ykrank.s1next.data.db.dbmodel.BlackListme.ykrank.s1next.view.page.setting.blacklist.BlackWordSettingFragment→me.ykrank.s1next.data.db.dbmodel.BlackWordme.ykrank.s1next.view.page.setting.blacklist.BlacklistDialogFragment→me.ykrank.s1next.data.db.dbmodel.BlackList
- Direction
- me.ykrank.s1next.view.page.setting.blacklist uses me.ykrank.s1next.data.db.dbmodel, so a change to me.ykrank.s1next.data.db.dbmodel can break me.ykrank.s1next.view.page.setting.blacklist, while a change to me.ykrank.s1next.view.page.setting.blacklist can't break me.ykrank.s1next.data.db.dbmodel.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.setting.blacklist uses a module listed above it, which is the healthy direction.
37→12 me.ykrank.s1next.view.page.setting.blacklist uses me.ykrank.s1next.data.db.biz✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.setting.blacklist uses a type in me.ykrank.s1next.data.db.biz.
- The types involved
me.ykrank.s1next.view.page.setting.blacklist.BlackListRemarkDialogFragment→me.ykrank.s1next.data.db.biz.BlackListBiz
- Direction
- me.ykrank.s1next.view.page.setting.blacklist uses me.ykrank.s1next.data.db.biz, so a change to me.ykrank.s1next.data.db.biz can break me.ykrank.s1next.view.page.setting.blacklist, while a change to me.ykrank.s1next.view.page.setting.blacklist can't break me.ykrank.s1next.data.db.biz.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.setting.blacklist uses a module listed above it, which is the healthy direction.
37→26 me.ykrank.s1next.view.page.setting.blacklist uses me.ykrank.s1next.view.adapter✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.setting.blacklist uses a type in me.ykrank.s1next.view.adapter.
- The types involved
me.ykrank.s1next.view.page.setting.blacklist.BlackWordSettingFragment→me.ykrank.s1next.view.adapter.BlackWordCursorListViewAdapter
- Direction
- me.ykrank.s1next.view.page.setting.blacklist uses me.ykrank.s1next.view.adapter, so a change to me.ykrank.s1next.view.adapter can break me.ykrank.s1next.view.page.setting.blacklist, while a change to me.ykrank.s1next.view.page.setting.blacklist can't break me.ykrank.s1next.view.adapter.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.setting.blacklist uses a module listed above it, which is the healthy direction.
37→27 me.ykrank.s1next.view.page.setting.blacklist uses me.ykrank.s1next.view.dialog✕
- Connections
- 3 pairs of types, where a type in me.ykrank.s1next.view.page.setting.blacklist uses a type in me.ykrank.s1next.view.dialog.
- The types involved
me.ykrank.s1next.view.page.setting.blacklist.BlackListRemarkDialogFragment→me.ykrank.s1next.view.dialog.BaseDialogFragmentme.ykrank.s1next.view.page.setting.blacklist.BlackWordDialogFragment→me.ykrank.s1next.view.dialog.BaseDialogFragmentme.ykrank.s1next.view.page.setting.blacklist.BlacklistDialogFragment→me.ykrank.s1next.view.dialog.BaseDialogFragment
- Direction
- me.ykrank.s1next.view.page.setting.blacklist uses me.ykrank.s1next.view.dialog, so a change to me.ykrank.s1next.view.dialog can break me.ykrank.s1next.view.page.setting.blacklist, while a change to me.ykrank.s1next.view.page.setting.blacklist can't break me.ykrank.s1next.view.dialog.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.setting.blacklist uses a module listed above it, which is the healthy direction.
37→31 me.ykrank.s1next.view.page.setting.blacklist uses me.ykrank.s1next.view.fragment✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.page.setting.blacklist uses a type in me.ykrank.s1next.view.fragment.
- The types involved
me.ykrank.s1next.view.page.setting.blacklist.BlackListSettingFragment→me.ykrank.s1next.view.fragment.BaseFragmentme.ykrank.s1next.view.page.setting.blacklist.BlackWordSettingFragment→me.ykrank.s1next.view.fragment.BaseFragment
- Direction
- me.ykrank.s1next.view.page.setting.blacklist uses me.ykrank.s1next.view.fragment, so a change to me.ykrank.s1next.view.fragment can break me.ykrank.s1next.view.page.setting.blacklist, while a change to me.ykrank.s1next.view.page.setting.blacklist can't break me.ykrank.s1next.view.fragment.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.setting.blacklist uses a module listed above it, which is the healthy direction.
38→3 me.ykrank.s1next.view.page.app uses com.github.ykrank.androidtools.ui.internal✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.app uses a type in com.github.ykrank.androidtools.ui.internal.
- The types involved
me.ykrank.s1next.view.page.app.AppPostListPagerFragment→com.github.ykrank.androidtools.ui.internal.LoadingViewModelBindingDelegate
- Direction
- me.ykrank.s1next.view.page.app uses com.github.ykrank.androidtools.ui.internal, so a change to com.github.ykrank.androidtools.ui.internal can break me.ykrank.s1next.view.page.app, while a change to me.ykrank.s1next.view.page.app can't break com.github.ykrank.androidtools.ui.internal.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.app uses a module listed above it, which is the healthy direction.
38→4 me.ykrank.s1next.view.page.app uses com.github.ykrank.androidtools.widget✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.app uses a type in com.github.ykrank.androidtools.widget.
- The types involved
me.ykrank.s1next.view.page.app.AppPostListFragment→com.github.ykrank.androidtools.widget.EventBus
- Direction
- me.ykrank.s1next.view.page.app uses com.github.ykrank.androidtools.widget, so a change to com.github.ykrank.androidtools.widget can break me.ykrank.s1next.view.page.app, while a change to me.ykrank.s1next.view.page.app can't break com.github.ykrank.androidtools.widget.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.app uses a module listed above it, which is the healthy direction.
38→10 me.ykrank.s1next.view.page.app uses me.ykrank.s1next.data.api.app.model✕
- Connections
- 4 pairs of types, where a type in me.ykrank.s1next.view.page.app uses a type in me.ykrank.s1next.data.api.app.model.
- The types involved
me.ykrank.s1next.view.page.app.AppPostListActivity→me.ykrank.s1next.data.api.app.model.AppThreadme.ykrank.s1next.view.page.app.AppPostListFragment→me.ykrank.s1next.data.api.app.model.AppThreadme.ykrank.s1next.view.page.app.AppPostListPagerFragment→me.ykrank.s1next.data.api.app.model.AppPostme.ykrank.s1next.view.page.app.AppPostListPagerFragment→me.ykrank.s1next.data.api.app.model.AppPostsWrapper
- Direction
- me.ykrank.s1next.view.page.app uses me.ykrank.s1next.data.api.app.model, so a change to me.ykrank.s1next.data.api.app.model can break me.ykrank.s1next.view.page.app, while a change to me.ykrank.s1next.view.page.app can't break me.ykrank.s1next.data.api.app.model.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.app uses a module listed above it, which is the healthy direction.
38→12 me.ykrank.s1next.view.page.app uses me.ykrank.s1next.data.db.biz✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.app uses a type in me.ykrank.s1next.data.db.biz.
- The types involved
me.ykrank.s1next.view.page.app.AppPostListPagerFragment→me.ykrank.s1next.data.db.biz.LoginUserBiz
- Direction
- me.ykrank.s1next.view.page.app uses me.ykrank.s1next.data.db.biz, so a change to me.ykrank.s1next.data.db.biz can break me.ykrank.s1next.view.page.app, while a change to me.ykrank.s1next.view.page.app can't break me.ykrank.s1next.data.db.biz.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.app uses a module listed above it, which is the healthy direction.
38→13 me.ykrank.s1next.view.page.app uses me.ykrank.s1next.data.pref✕
- Connections
- 3 pairs of types, where a type in me.ykrank.s1next.view.page.app uses a type in me.ykrank.s1next.data.pref.
- The types involved
me.ykrank.s1next.view.page.app.AppPostListFragment→me.ykrank.s1next.data.pref.DownloadPreferencesManagerme.ykrank.s1next.view.page.app.AppPostListFragment→me.ykrank.s1next.data.pref.GeneralPreferencesManagerme.ykrank.s1next.view.page.app.AppPostListPagerFragment→me.ykrank.s1next.data.pref.GeneralPreferencesManager
- Direction
- me.ykrank.s1next.view.page.app uses me.ykrank.s1next.data.pref, so a change to me.ykrank.s1next.data.pref can break me.ykrank.s1next.view.page.app, while a change to me.ykrank.s1next.view.page.app can't break me.ykrank.s1next.data.pref.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.app uses a module listed above it, which is the healthy direction.
38→18 me.ykrank.s1next.view.page.app uses com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.app uses a type in com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment.
- The types involved
me.ykrank.s1next.view.page.app.AppPostListFragment→com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment.FragmentStatePagerAdapter
- Direction
- me.ykrank.s1next.view.page.app uses com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment, so a change to com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment can break me.ykrank.s1next.view.page.app, while a change to me.ykrank.s1next.view.page.app can't break com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.app uses a module listed above it, which is the healthy direction.
38→19 me.ykrank.s1next.view.page.app uses me.ykrank.s1next.data.api.app✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.app uses a type in me.ykrank.s1next.data.api.app.
- The types involved
me.ykrank.s1next.view.page.app.AppPostListPagerFragment→me.ykrank.s1next.data.api.app.AppService
- Direction
- me.ykrank.s1next.view.page.app uses me.ykrank.s1next.data.api.app, so a change to me.ykrank.s1next.data.api.app can break me.ykrank.s1next.view.page.app, while a change to me.ykrank.s1next.view.page.app can't break me.ykrank.s1next.data.api.app.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.app uses a module listed above it, which is the healthy direction.
38→26 me.ykrank.s1next.view.page.app uses me.ykrank.s1next.view.adapter✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.app uses a type in me.ykrank.s1next.view.adapter.
- The types involved
me.ykrank.s1next.view.page.app.AppPostListPagerFragment→me.ykrank.s1next.view.adapter.AppPostListRecyclerViewAdapter
- Direction
- me.ykrank.s1next.view.page.app uses me.ykrank.s1next.view.adapter, so a change to me.ykrank.s1next.view.adapter can break me.ykrank.s1next.view.page.app, while a change to me.ykrank.s1next.view.page.app can't break me.ykrank.s1next.view.adapter.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.app uses a module listed above it, which is the healthy direction.
38→31 me.ykrank.s1next.view.page.app uses me.ykrank.s1next.view.fragment✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.page.app uses a type in me.ykrank.s1next.view.fragment.
- The types involved
me.ykrank.s1next.view.page.app.AppPostListFragment→me.ykrank.s1next.view.fragment.BaseViewPagerFragmentme.ykrank.s1next.view.page.app.AppPostListPagerFragment→me.ykrank.s1next.view.fragment.BaseRecyclerViewFragment
- Direction
- me.ykrank.s1next.view.page.app uses me.ykrank.s1next.view.fragment, so a change to me.ykrank.s1next.view.fragment can break me.ykrank.s1next.view.page.app, while a change to me.ykrank.s1next.view.page.app can't break me.ykrank.s1next.view.fragment.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.app uses a module listed above it, which is the healthy direction.
38→34 me.ykrank.s1next.view.page.app uses me.ykrank.s1next.view.activity✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.page.app uses a type in me.ykrank.s1next.view.activity.
- The types involved
me.ykrank.s1next.view.page.app.AppLoginActivity→me.ykrank.s1next.view.activity.BaseActivityme.ykrank.s1next.view.page.app.AppPostListActivity→me.ykrank.s1next.view.activity.BaseActivity
- Direction
- me.ykrank.s1next.view.page.app uses me.ykrank.s1next.view.activity, so a change to me.ykrank.s1next.view.activity can break me.ykrank.s1next.view.page.app, while a change to me.ykrank.s1next.view.page.app can't break me.ykrank.s1next.view.activity.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.app uses a module listed above it, which is the healthy direction.
39→1 me.ykrank.s1next.view.page.post.postlist uses com.github.ykrank.androidtools.data✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.post.postlist uses a type in com.github.ykrank.androidtools.data.
- The types involved
me.ykrank.s1next.view.page.post.postlist.PostListPagerFragment→com.github.ykrank.androidtools.data.Resource
- Direction
- me.ykrank.s1next.view.page.post.postlist uses com.github.ykrank.androidtools.data, so a change to com.github.ykrank.androidtools.data can break me.ykrank.s1next.view.page.post.postlist, while a change to me.ykrank.s1next.view.page.post.postlist can't break com.github.ykrank.androidtools.data.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.postlist uses a module listed above it, which is the healthy direction.
39→3 me.ykrank.s1next.view.page.post.postlist uses com.github.ykrank.androidtools.ui.internal✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.post.postlist uses a type in com.github.ykrank.androidtools.ui.internal.
- The types involved
me.ykrank.s1next.view.page.post.postlist.PostListPagerFragment→com.github.ykrank.androidtools.ui.internal.LoadingViewModelBindingDelegate
- Direction
- me.ykrank.s1next.view.page.post.postlist uses com.github.ykrank.androidtools.ui.internal, so a change to com.github.ykrank.androidtools.ui.internal can break me.ykrank.s1next.view.page.post.postlist, while a change to me.ykrank.s1next.view.page.post.postlist can't break com.github.ykrank.androidtools.ui.internal.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.postlist uses a module listed above it, which is the healthy direction.
39→4 me.ykrank.s1next.view.page.post.postlist uses com.github.ykrank.androidtools.widget✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.post.postlist uses a type in com.github.ykrank.androidtools.widget.
- The types involved
me.ykrank.s1next.view.page.post.postlist.PostListFragment→com.github.ykrank.androidtools.widget.EventBus
- Direction
- me.ykrank.s1next.view.page.post.postlist uses com.github.ykrank.androidtools.widget, so a change to com.github.ykrank.androidtools.widget can break me.ykrank.s1next.view.page.post.postlist, while a change to me.ykrank.s1next.view.page.post.postlist can't break com.github.ykrank.androidtools.widget.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.postlist uses a module listed above it, which is the healthy direction.
39→7 me.ykrank.s1next.view.page.post.postlist uses me.ykrank.s1next.data.db.dbmodel✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.page.post.postlist uses a type in me.ykrank.s1next.data.db.dbmodel.
- The types involved
me.ykrank.s1next.view.page.post.postlist.PostListFragment→me.ykrank.s1next.data.db.dbmodel.ReadProgressme.ykrank.s1next.view.page.post.postlist.PostListPagerFragment→me.ykrank.s1next.data.db.dbmodel.ReadProgress
- Direction
- me.ykrank.s1next.view.page.post.postlist uses me.ykrank.s1next.data.db.dbmodel, so a change to me.ykrank.s1next.data.db.dbmodel can break me.ykrank.s1next.view.page.post.postlist, while a change to me.ykrank.s1next.view.page.post.postlist can't break me.ykrank.s1next.data.db.dbmodel.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.postlist uses a module listed above it, which is the healthy direction.
39→11 me.ykrank.s1next.view.page.post.postlist uses me.ykrank.s1next.data.api.model✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.page.post.postlist uses a type in me.ykrank.s1next.data.api.model.
- The types involved
me.ykrank.s1next.view.page.post.postlist.PostListFragment→me.ykrank.s1next.data.api.model.Threadme.ykrank.s1next.view.page.post.postlist.PostListPagerFragment→me.ykrank.s1next.data.api.model.Post
- Direction
- me.ykrank.s1next.view.page.post.postlist uses me.ykrank.s1next.data.api.model, so a change to me.ykrank.s1next.data.api.model can break me.ykrank.s1next.view.page.post.postlist, while a change to me.ykrank.s1next.view.page.post.postlist can't break me.ykrank.s1next.data.api.model.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.postlist uses a module listed above it, which is the healthy direction.
39→12 me.ykrank.s1next.view.page.post.postlist uses me.ykrank.s1next.data.db.biz✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.post.postlist uses a type in me.ykrank.s1next.data.db.biz.
- The types involved
me.ykrank.s1next.view.page.post.postlist.PostListFragment→me.ykrank.s1next.data.db.biz.HistoryBiz
- Direction
- me.ykrank.s1next.view.page.post.postlist uses me.ykrank.s1next.data.db.biz, so a change to me.ykrank.s1next.data.db.biz can break me.ykrank.s1next.view.page.post.postlist, while a change to me.ykrank.s1next.view.page.post.postlist can't break me.ykrank.s1next.data.db.biz.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.postlist uses a module listed above it, which is the healthy direction.
39→13 me.ykrank.s1next.view.page.post.postlist uses me.ykrank.s1next.data.pref✕
- Connections
- 5 pairs of types, where a type in me.ykrank.s1next.view.page.post.postlist uses a type in me.ykrank.s1next.data.pref.
- The types involved
me.ykrank.s1next.view.page.post.postlist.PostListActivity→me.ykrank.s1next.data.pref.ReadPreferencesManagerme.ykrank.s1next.view.page.post.postlist.PostListFragment→me.ykrank.s1next.data.pref.DownloadPreferencesManagerme.ykrank.s1next.view.page.post.postlist.PostListFragment→me.ykrank.s1next.data.pref.GeneralPreferencesManagerme.ykrank.s1next.view.page.post.postlist.PostListFragment→me.ykrank.s1next.data.pref.ReadPreferencesManagerme.ykrank.s1next.view.page.post.postlist.PostListPagerFragment→me.ykrank.s1next.data.pref.GeneralPreferencesManager
- Direction
- me.ykrank.s1next.view.page.post.postlist uses me.ykrank.s1next.data.pref, so a change to me.ykrank.s1next.data.pref can break me.ykrank.s1next.view.page.post.postlist, while a change to me.ykrank.s1next.view.page.post.postlist can't break me.ykrank.s1next.data.pref.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.postlist uses a module listed above it, which is the healthy direction.
39→18 me.ykrank.s1next.view.page.post.postlist uses com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.post.postlist uses a type in com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment.
- The types involved
me.ykrank.s1next.view.page.post.postlist.PostListFragment→com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment.FragmentStatePagerAdapter
- Direction
- me.ykrank.s1next.view.page.post.postlist uses com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment, so a change to com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment can break me.ykrank.s1next.view.page.post.postlist, while a change to me.ykrank.s1next.view.page.post.postlist can't break com.github.ykrank.androidtools.ui.LibBaseViewPagerFragment.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.postlist uses a module listed above it, which is the healthy direction.
39→31 me.ykrank.s1next.view.page.post.postlist uses me.ykrank.s1next.view.fragment✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next.view.page.post.postlist uses a type in me.ykrank.s1next.view.fragment.
- The types involved
me.ykrank.s1next.view.page.post.postlist.PostListFragment→me.ykrank.s1next.view.fragment.BaseViewPagerFragmentme.ykrank.s1next.view.page.post.postlist.PostListPagerFragment→me.ykrank.s1next.view.fragment.BaseRecyclerViewFragment
- Direction
- me.ykrank.s1next.view.page.post.postlist uses me.ykrank.s1next.view.fragment, so a change to me.ykrank.s1next.view.fragment can break me.ykrank.s1next.view.page.post.postlist, while a change to me.ykrank.s1next.view.page.post.postlist can't break me.ykrank.s1next.view.fragment.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.postlist uses a module listed above it, which is the healthy direction.
39→32 me.ykrank.s1next.view.page.post.postlist uses me.ykrank.s1next.view.page.post.adapter✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.post.postlist uses a type in me.ykrank.s1next.view.page.post.adapter.
- The types involved
me.ykrank.s1next.view.page.post.postlist.PostListPagerFragment→me.ykrank.s1next.view.page.post.adapter.PostListRecyclerViewAdapter
- Direction
- me.ykrank.s1next.view.page.post.postlist uses me.ykrank.s1next.view.page.post.adapter, so a change to me.ykrank.s1next.view.page.post.adapter can break me.ykrank.s1next.view.page.post.postlist, while a change to me.ykrank.s1next.view.page.post.postlist can't break me.ykrank.s1next.view.page.post.adapter.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.postlist uses a module listed above it, which is the healthy direction.
39→34 me.ykrank.s1next.view.page.post.postlist uses me.ykrank.s1next.view.activity✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next.view.page.post.postlist uses a type in me.ykrank.s1next.view.activity.
- The types involved
me.ykrank.s1next.view.page.post.postlist.PostListActivity→me.ykrank.s1next.view.activity.BaseActivity
- Direction
- me.ykrank.s1next.view.page.post.postlist uses me.ykrank.s1next.view.activity, so a change to me.ykrank.s1next.view.activity can break me.ykrank.s1next.view.page.post.postlist, while a change to me.ykrank.s1next.view.page.post.postlist can't break me.ykrank.s1next.view.activity.
- Position
- Below the diagonal: me.ykrank.s1next.view.page.post.postlist uses a module listed above it, which is the healthy direction.
40→4 me.ykrank.s1next uses com.github.ykrank.androidtools.widget✕
- Connections
- 5 pairs of types, where a type in me.ykrank.s1next uses a type in com.github.ykrank.androidtools.widget.
- The types involved
me.ykrank.s1next.AppComponent→com.github.ykrank.androidtools.widget.EditorDiskCacheme.ykrank.s1next.AppModule→com.github.ykrank.androidtools.widget.EditorDiskCacheme.ykrank.s1next.AppModule→com.github.ykrank.androidtools.widget.EventBusme.ykrank.s1next.PreAppComponent→com.github.ykrank.androidtools.widget.EventBusme.ykrank.s1next.PreAppModule→com.github.ykrank.androidtools.widget.EventBus
- Direction
- me.ykrank.s1next uses com.github.ykrank.androidtools.widget, so a change to com.github.ykrank.androidtools.widget can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break com.github.ykrank.androidtools.widget.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→6 me.ykrank.s1next uses me.ykrank.s1next.data.cache.biz✕
- Connections
- 3 pairs of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.data.cache.biz.
- The types involved
me.ykrank.s1next.AppComponent→me.ykrank.s1next.data.cache.biz.CacheBizme.ykrank.s1next.AppModule→me.ykrank.s1next.data.cache.biz.CacheBizme.ykrank.s1next.AppModule→me.ykrank.s1next.data.cache.biz.CacheGroupBiz
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.data.cache.biz, so a change to me.ykrank.s1next.data.cache.biz can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.data.cache.biz.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→8 me.ykrank.s1next uses com.github.ykrank.androidtools.widget.track✕
- Connections
- 3 pairs of types, where a type in me.ykrank.s1next uses a type in com.github.ykrank.androidtools.widget.track.
- The types involved
me.ykrank.s1next.App→com.github.ykrank.androidtools.widget.track.DataTrackAgentme.ykrank.s1next.PreAppComponent→com.github.ykrank.androidtools.widget.track.DataTrackAgentme.ykrank.s1next.PreAppModule→com.github.ykrank.androidtools.widget.track.DataTrackAgent
- Direction
- me.ykrank.s1next uses com.github.ykrank.androidtools.widget.track, so a change to com.github.ykrank.androidtools.widget.track can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break com.github.ykrank.androidtools.widget.track.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→12 me.ykrank.s1next uses me.ykrank.s1next.data.db.biz✕
- Connections
- 7 pairs of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.data.db.biz.
- The types involved
me.ykrank.s1next.AppComponent→me.ykrank.s1next.data.db.biz.BlackListBizme.ykrank.s1next.AppComponent→me.ykrank.s1next.data.db.biz.BlackWordBizme.ykrank.s1next.AppComponent→me.ykrank.s1next.data.db.biz.HistoryBizme.ykrank.s1next.AppComponent→me.ykrank.s1next.data.db.biz.LoginUserBizme.ykrank.s1next.AppComponent→me.ykrank.s1next.data.db.biz.ReadProgressBizme.ykrank.s1next.AppComponent→me.ykrank.s1next.data.db.biz.ThreadBizme.ykrank.s1next.AppModule→me.ykrank.s1next.data.db.biz.BlackListBiz
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.data.db.biz, so a change to me.ykrank.s1next.data.db.biz can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.data.db.biz.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→13 me.ykrank.s1next uses me.ykrank.s1next.data.pref✕
- Connections
- 10 pairs of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.data.pref.
- The types involved
me.ykrank.s1next.App→me.ykrank.s1next.data.pref.GeneralPreferencesManagerme.ykrank.s1next.AppModule→me.ykrank.s1next.data.pref.AppDataPreferencesManagerme.ykrank.s1next.AppModule→me.ykrank.s1next.data.pref.DownloadPreferencesManagerme.ykrank.s1next.AppModule→me.ykrank.s1next.data.pref.NetworkPreferencesManagerme.ykrank.s1next.PreAppComponent→me.ykrank.s1next.data.pref.AppDataPreferencesManagerme.ykrank.s1next.PreAppComponent→me.ykrank.s1next.data.pref.DataPreferencesManagerme.ykrank.s1next.PreAppComponent→me.ykrank.s1next.data.pref.DownloadPreferencesManagerme.ykrank.s1next.PreAppComponent→me.ykrank.s1next.data.pref.GeneralPreferencesManagerme.ykrank.s1next.PreAppComponent→me.ykrank.s1next.data.pref.NetworkPreferencesManagerme.ykrank.s1next.PreAppComponent→me.ykrank.s1next.data.pref.ReadPreferencesManager
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.data.pref, so a change to me.ykrank.s1next.data.pref can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.data.pref.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→15 me.ykrank.s1next uses me.ykrank.s1next.data✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.data.
- The types involved
me.ykrank.s1next.AppComponent→me.ykrank.s1next.data.Userme.ykrank.s1next.AppModule→me.ykrank.s1next.data.User
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.data, so a change to me.ykrank.s1next.data can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.data.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→16 me.ykrank.s1next uses me.ykrank.s1next.data.db✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.data.db.
- The types involved
me.ykrank.s1next.AppComponent→me.ykrank.s1next.data.db.AppDatabaseManager
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.data.db, so a change to me.ykrank.s1next.data.db can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.data.db.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→19 me.ykrank.s1next uses me.ykrank.s1next.data.api.app✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.data.api.app.
- The types involved
me.ykrank.s1next.AppComponent→me.ykrank.s1next.data.api.app.AppServiceme.ykrank.s1next.AppModule→me.ykrank.s1next.data.api.app.AppService
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.data.api.app, so a change to me.ykrank.s1next.data.api.app can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.data.api.app.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→21 me.ykrank.s1next uses me.ykrank.s1next.viewmodel✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.viewmodel.
- The types involved
me.ykrank.s1next.AppComponent→me.ykrank.s1next.viewmodel.UserViewModelme.ykrank.s1next.AppModule→me.ykrank.s1next.viewmodel.UserViewModel
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.viewmodel, so a change to me.ykrank.s1next.viewmodel can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.viewmodel.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→22 me.ykrank.s1next uses me.ykrank.s1next.data.api✕
- Connections
- 6 pairs of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.data.api.
- The types involved
me.ykrank.s1next.AppComponent→me.ykrank.s1next.data.api.ApiCacheProviderme.ykrank.s1next.AppComponent→me.ykrank.s1next.data.api.S1Serviceme.ykrank.s1next.AppComponent→me.ykrank.s1next.data.api.UserValidatorme.ykrank.s1next.AppModule→me.ykrank.s1next.data.api.ApiCacheProviderme.ykrank.s1next.AppModule→me.ykrank.s1next.data.api.S1Serviceme.ykrank.s1next.AppModule→me.ykrank.s1next.data.api.UserValidator
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.data.api, so a change to me.ykrank.s1next.data.api can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.data.api.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→23 me.ykrank.s1next uses me.ykrank.s1next.view.adapter.delegate✕
- Connections
- 7 pairs of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.view.adapter.delegate.
- The types involved
me.ykrank.s1next.AppComponent→me.ykrank.s1next.view.adapter.delegate.AppPostAdapterDelegateme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.adapter.delegate.FavouriteAdapterDelegateme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.adapter.delegate.ForumAdapterDelegateme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.adapter.delegate.PmGroupsAdapterDelegateme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.adapter.delegate.PmLeftAdapterDelegateme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.adapter.delegate.PmRightAdapterDelegateme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.adapter.delegate.ThreadAdapterDelegate
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.view.adapter.delegate, so a change to me.ykrank.s1next.view.adapter.delegate can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.view.adapter.delegate.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→24 me.ykrank.s1next uses me.ykrank.s1next.view.internal✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.view.internal.
- The types involved
me.ykrank.s1next.AppComponent→me.ykrank.s1next.view.internal.DrawerLayoutDelegateConcrete
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.view.internal, so a change to me.ykrank.s1next.view.internal can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.view.internal.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→26 me.ykrank.s1next uses me.ykrank.s1next.view.adapter✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.view.adapter.
- The types involved
me.ykrank.s1next.AppComponent→me.ykrank.s1next.view.adapter.SubForumArrayAdapter
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.view.adapter, so a change to me.ykrank.s1next.view.adapter can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.view.adapter.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→27 me.ykrank.s1next uses me.ykrank.s1next.view.dialog✕
- Connections
- 4 pairs of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.view.dialog.
- The types involved
me.ykrank.s1next.AppComponent→me.ykrank.s1next.view.dialog.LoadBlackListFromWebDialogFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.dialog.LoginPromptDialogFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.dialog.LogoutDialogFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.dialog.VoteDialogFragment
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.view.dialog, so a change to me.ykrank.s1next.view.dialog can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.view.dialog.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→28 me.ykrank.s1next uses me.ykrank.s1next.view.page.post.postedit✕
- Connections
- 3 pairs of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.view.page.post.postedit.
- The types involved
me.ykrank.s1next.AppComponent→me.ykrank.s1next.view.page.post.postedit.BasePostEditFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.page.post.postedit.NewThreadFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.page.post.postedit.ReplyFragment
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.view.page.post.postedit, so a change to me.ykrank.s1next.view.page.post.postedit can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.view.page.post.postedit.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→29 me.ykrank.s1next uses me.ykrank.s1next.widget.hostcheck✕
- Connections
- 4 pairs of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.widget.hostcheck.
- The types involved
me.ykrank.s1next.AppComponent→me.ykrank.s1next.widget.hostcheck.AppHostUrlme.ykrank.s1next.AppComponent→me.ykrank.s1next.widget.hostcheck.NoticeCheckTaskme.ykrank.s1next.AppModule→me.ykrank.s1next.widget.hostcheck.AppHostUrlme.ykrank.s1next.AppModule→me.ykrank.s1next.widget.hostcheck.NoticeCheckTask
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.widget.hostcheck, so a change to me.ykrank.s1next.widget.hostcheck can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.widget.hostcheck.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→31 me.ykrank.s1next uses me.ykrank.s1next.view.fragment✕
- Connections
- 17 pairs of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.view.fragment.
- The types involved
me.ykrank.s1next.AppComponent→me.ykrank.s1next.view.fragment.BaseFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.fragment.BaseViewPagerFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.fragment.DarkRoomFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.fragment.EditPostFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.fragment.FavouriteListFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.fragment.ForumFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.fragment.GalleryFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.fragment.HistoryListFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.fragment.NewRateFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.fragment.NewReportFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.fragment.NoteFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.fragment.PmFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.fragment.PmGroupsFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.fragment.ThreadListFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.fragment.ThreadListPagerFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.fragment.WebLoginFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.fragment.WebViewFragment
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.view.fragment, so a change to me.ykrank.s1next.view.fragment can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.view.fragment.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→32 me.ykrank.s1next uses me.ykrank.s1next.view.page.post.adapter✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.view.page.post.adapter.
- The types involved
me.ykrank.s1next.AppComponent→me.ykrank.s1next.view.page.post.adapter.PostAdapterDelegateme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.page.post.adapter.PostBlackAdapterDelegate
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.view.page.post.adapter, so a change to me.ykrank.s1next.view.page.post.adapter can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.view.page.post.adapter.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→33 me.ykrank.s1next uses me.ykrank.s1next.view.page.setting.fragment✕
- Connections
- 5 pairs of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.view.page.setting.fragment.
- The types involved
me.ykrank.s1next.AppComponent→me.ykrank.s1next.view.page.setting.fragment.BackupPreferenceFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.page.setting.fragment.DownloadPreferenceFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.page.setting.fragment.GeneralPreferenceFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.page.setting.fragment.NetworkPreferenceFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.page.setting.fragment.ReadPreferenceFragment
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.view.page.setting.fragment, so a change to me.ykrank.s1next.view.page.setting.fragment can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.view.page.setting.fragment.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→34 me.ykrank.s1next uses me.ykrank.s1next.view.activity✕
- Connections
- 6 pairs of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.view.activity.
- The types involved
me.ykrank.s1next.AppComponent→me.ykrank.s1next.view.activity.BaseActivityme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.activity.ForumActivityme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.activity.GalleryActivityme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.activity.SearchActivityme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.activity.ThreadListActivityme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.activity.UserHomeActivity
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.view.activity, so a change to me.ykrank.s1next.view.activity can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.view.activity.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→35 me.ykrank.s1next uses me.ykrank.s1next.view.page.login✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.view.page.login.
- The types involved
me.ykrank.s1next.AppComponent→me.ykrank.s1next.view.page.login.AppLoginDialogFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.page.login.BaseLoginFragment
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.view.page.login, so a change to me.ykrank.s1next.view.page.login can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.view.page.login.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→36 me.ykrank.s1next uses me.ykrank.s1next.view.page.post.postedit.toolstab✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.view.page.post.postedit.toolstab.
- The types involved
me.ykrank.s1next.AppComponent→me.ykrank.s1next.view.page.post.postedit.toolstab.ImageUploadFragment
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.view.page.post.postedit.toolstab, so a change to me.ykrank.s1next.view.page.post.postedit.toolstab can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.view.page.post.postedit.toolstab.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→37 me.ykrank.s1next uses me.ykrank.s1next.view.page.setting.blacklist✕
- Connections
- 1 pair of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.view.page.setting.blacklist.
- The types involved
me.ykrank.s1next.AppComponent→me.ykrank.s1next.view.page.setting.blacklist.BlackListRemarkDialogFragment
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.view.page.setting.blacklist, so a change to me.ykrank.s1next.view.page.setting.blacklist can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.view.page.setting.blacklist.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→38 me.ykrank.s1next uses me.ykrank.s1next.view.page.app✕
- Connections
- 2 pairs of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.view.page.app.
- The types involved
me.ykrank.s1next.AppComponent→me.ykrank.s1next.view.page.app.AppPostListFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.page.app.AppPostListPagerFragment
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.view.page.app, so a change to me.ykrank.s1next.view.page.app can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.view.page.app.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
40→39 me.ykrank.s1next uses me.ykrank.s1next.view.page.post.postlist✕
- Connections
- 4 pairs of types, where a type in me.ykrank.s1next uses a type in me.ykrank.s1next.view.page.post.postlist.
- The types involved
me.ykrank.s1next.AppComponent→me.ykrank.s1next.view.page.post.postlist.PostListActivityme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.page.post.postlist.PostListFragmentme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.page.post.postlist.PostListGatewayActivityme.ykrank.s1next.AppComponent→me.ykrank.s1next.view.page.post.postlist.PostListPagerFragment
- Direction
- me.ykrank.s1next uses me.ykrank.s1next.view.page.post.postlist, so a change to me.ykrank.s1next.view.page.post.postlist can break me.ykrank.s1next, while a change to me.ykrank.s1next can't break me.ykrank.s1next.view.page.post.postlist.
- Position
- Below the diagonal: me.ykrank.s1next uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 4 | Medium |
| A03:2025 — Software Supply Chain Failures | 3 | Medium |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts; Resolve the 204 Orphaned file finding(s) in Knowledge Freshness — start with ViewUtil.java (2), PostListPagerFragment.kt, KeyboardUtil.java; 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 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. | +12.6 pts | Low | ADR Quality |
| Resolve the 204 Orphaned file finding(s) in Knowledge Freshness — start with ViewUtil.java (2), PostListPagerFragment.kt, KeyboardUtil.java. | +12.6 pts | High | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +10.0 pts | Medium | Architecture documentation |
| Expand the README with getting-started, architecture overview and a project map. | +6.0 pts | Medium | Documentation (README) |
| Resolve the 2 `postID` spells `ID` where 221 names in the project spell it `Id` finding(s) in Naming Consistency — start with NewRateFragment.kt, NewReportFragment.kt. | +2.1 pts | Low | Naming Consistency |
| 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. | +3.3 pts | Medium | Security & performance tooling |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.4 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.4 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| app/src/main/java/me/ykrank/s1next/data/api/app/model/AppPostsWrapper.kt | 5.6 | Mixed | Cyclomatic Complexity: AppPost.equals (cyclomatic 21) |
| app/src/main/java/me/ykrank/s1next/widget/span/AcfunSpan.kt | 6.0 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| app/src/main/java/me/ykrank/s1next/view/page/setting/fragment/DownloadPreferenceFragment.kt | 7.0 | Mixed | Code Duplication: Edited copy of a member (17 corresponding lines) |
| library/src/main/java/com/github/ykrank/androidtools/ui/LibBaseActivity.kt | 7.0 | Mixed | Code Duplication: Duplicated block (9 lines × 2) |
| app/src/main/java/me/ykrank/s1next/view/page/app/AppPostListFragment.kt | 7.0 | Mixed | Code Duplication: Edited copy of a member (63 corresponding lines) |
| app/src/main/java/me/ykrank/s1next/view/page/app/AppPostListPagerFragment.kt | 7.1 | Mixed | Cognitive Complexity: AppPostListPagerFragment.onNext (cognitive 26) |
| app/src/main/java/me/ykrank/s1next/view/page/post/viewmodel/PostViewModel.kt | 7.1 | Mixed | Cognitive Complexity: PostViewModel.onAvatarLongClick (cognitive 19) |
| app/src/main/java/me/ykrank/s1next/data/api/model/collection/Posts.kt | 7.2 | Mixed | Cyclomatic Complexity: Posts.filterPost (cyclomatic 18) |
| app/src/main/java/me/ykrank/s1next/view/page/post/adapter/PostAdapterDelegate.kt | 7.2 | Mixed | Cognitive Complexity: PostAdapterDelegate.onBindViewHolderData (cognitive 27) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| app/src/main/java/me/ykrank/s1next/view/fragment/NewReportFragment.kt | 7.3 | Mixed | Code Duplication: Edited copy of a member (12 corresponding lines) |
| app/src/main/java/me/ykrank/s1next/data/cache/api/S1ApiCacheProvider.kt | 7.4 | Mixed | Cyclomatic Complexity: S1ApiCacheProvider.getPostsWrapper (cyclomatic 28) |
| app/src/main/java/me/ykrank/s1next/view/page/post/viewmodel/PostBlackViewModel.kt | 7.4 | Mixed | Cognitive Complexity: PostBlackViewModel.showBlackListMenu (cognitive 19) |
| library/src/main/java/com/github/ykrank/androidtools/util/ColorDrawableUtils.java | 7.4 | Mixed | Code Duplication: Edited copy of a member (9 corresponding lines) |
| library/src/main/java/com/github/ykrank/androidtools/widget/BackupDelegate.kt | 7.4 | Mixed | Code Duplication: Edited copy of a member (24 corresponding lines) |
| app/src/main/java/me/ykrank/s1next/view/fragment/BaseLoadMoreRecycleViewFragment.kt | 7.4 | Mixed | Code Duplication: Duplicated block (10 lines × 2) |
| app/src/main/java/me/ykrank/s1next/data/api/model/Post.kt | 7.8 | Mixed | Cyclomatic Complexity: Post.equals (cyclomatic 20) |
| app/src/main/java/me/ykrank/s1next/data/api/app/model/AppThread.kt | 7.8 | Mixed | Cyclomatic Complexity: AppThread.equals (cyclomatic 19) |
| app/src/main/java/me/ykrank/s1next/view/page/post/postlist/PostListPagerFragment.kt | 7.8 | Mixed | Cyclomatic Complexity: PostListPagerFragment.onNextSuccess (cyclomatic 16) |
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 45 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 — 45 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, 391 of 402 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: the test suite could not be built/run in-image (commonly external-service dependencies — a database, a broker — we won't provision). To have it measured, make the suite runnable without them. For context only, test code is ≈ 0% of production LoC (122 test / 40,017 production) — a rough proxy, NOT a coverage measurement, so it is excluded from the score. You can widen what we reach: optional: make the suite runnable without a database, broker or other service we do not provision, and real coverage is measured on the next scan.
- 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 — a Gradle build resolved 261 artifact(s) across its subprojects (102 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 206 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 172 of the 640 production source files in this repository: 434 are under the ~2,400-byte size floor this dimension measures over, and the remaining 34 have no attributable history left to measure.
- D19 Documentation Quality — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each 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 — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — 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. Tracing effort is measured over resolved call sites, and all 214 sampled here came from .kt files. This repository's .java source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
- 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/me/ykrank/s1next/data/api/model/collection/Threads.kt`, `app/src/main/java/me/ykrank/s1next/data/cache/CacheDatabase.kt`, `app/src/main/java/me/ykrank/s1next/data/cache/dbmodel/Cache.kt`, `app/src/main/java/me/ykrank/s1next/data/cache/dbmodel/CacheGroup.kt`, `app/src/main/java/me/ykrank/s1next/data/db/dbmodel/BlackWord.kt`, … (+3 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.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (library/src/main/AndroidManifest.xml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C1 Data Protection — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- 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.
- ED5 Idempotency — 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 decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X12 Unreachable branch — 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. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X2 Cancellation propagation — 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, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
- 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.
- 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.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- 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.
- 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
6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was S1ApiCacheProvider.getPostsWrapper at 28.
What to do
- Bring the 6 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with S1ApiCacheProvider.getPostsWrapper (cyclomatic 28), AppPost.equals (cyclomatic 21), Post.equals (cyclomatic 20). — 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 6 together lifts Cyclomatic Complexity from 8.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
20 method(s) exceeded the cognitive complexity threshold of 15; the worst was S1ApiCacheProvider.getPostsWrapper at 44.
What to do
- Bring the 20 bodies over 15 down to 15 or less in Cognitive Complexity — start with S1ApiCacheProvider.getPostsWrapper (cognitive 44), PostListPagerFragment.onNextSuccess (cognitive 37), Posts.filterPost (cognitive 33). — 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 20 together lifts Cognitive Complexity from 7.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
1 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with S1ApiCacheProvider.kt. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
56 duplicated block group(s) detected. 7.1 % of the production lines (2,858 of 40,017) are in a reported copy. A further 56 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 8 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with AjaxResult.kt, BackupPreferenceFragment.kt, BaseLoadMoreRecycleViewFragment.kt. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 8 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with AppPostListFragment.kt (2), PostViewModel.kt, ReadProgressBiz.kt. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 7 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with BackupPreferenceFragment.kt, OpenSourceLicensesFragment.java, NoteFragment.kt. — One of this dimension's main actionable groups (7 warning-level).
D5 · Coupling
4 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 3 of the 4 (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 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
D6 · Cohesion (LCOM4)
3 of 146 classes have LCOM4 above 3.
What to do
- Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with DownloadPreferenceFragment.kt, LibBaseActivity.kt, LibBaseRecyclerViewAdapter.kt. — One of this dimension's main actionable groups (3 warning-level).
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 37 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 5 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. A further 24 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/me/ykrank/s1next/data/cache/api/S1ApiCacheProvider.kt (6×28=168)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with S1ApiCacheProvider.kt. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
4 deducted task-comment markers across 40017 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 4 TodoComment finding(s) in Explicit Debt — start with AcfunSpan.kt, DrawerLayoutDelegateConcrete.kt, ThreadListActivity.kt. — One of this dimension's main actionable groups (4 warning-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
D21 · Naming Consistency
2 naming inconsistencies among 225 declarations measured against a convention their peers follow.
D26 · Project Cohesion
2 of 3 build units (Gradle) flagged as possibly oversized/incoherent.
What to do
- Resolve the 2 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle.kts (2). — One of this dimension's main actionable groups (2 recommendation-level).
D27 · Navigability
65 % of calls cross a namespace and 6 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated. Measured over the .kt source only — this repository's .java was not sampled for call sites, so this score covers part of the tree, not all of it.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 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 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 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)
4 finding(s): 0 critical, 0 high, 2 medium, 2 low. semgrep hit a parse error in 2 file(s) — `app/src/main/java/me/ykrank/s1next/data/api/model/collection/Threads.kt` (line 103), `gradlew` (lines 140–141, line 142, line 143, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 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 recommendation-level).
D34 · Knowledge Freshness
206 of 206 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is app/src/main/java/me/ykrank/s1next/view/page/post/postlist/PostListFragment.kt. Counted over 206 of the 640 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 204 Orphaned file finding(s) in Knowledge Freshness — start with ViewUtil.java (2), PostListPagerFragment.kt, KeyboardUtil.java. — One of this dimension's main actionable groups (204 recommendation-level).
- Resolve the 2 Most significant orphaned file finding(s) in Knowledge Freshness — start with PostListFragment.kt, CustomViewTarget.java. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: AppComponent.kt↔AppDatabase.kt 80%; AppDatabase.kt↔DbModule.kt 70%; BuildTypeModule.kt↔AppModule.kt 69%
What to do
- Resolve the 5 Change coupling finding(s) in Change Coupling — start with AppComponent.kt, AppDatabase.kt, BuildTypeModule.kt. — One of this dimension's main actionable groups (5 warning-level).
D36 · Supply-chain Provenance & Signing
1/3 supply-chain integrity signals present (provenance, signing, SBOM).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-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 3 platform declaration(s) and 61 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
- `S1Service` declares 40 abstract methods: `getForumGroupsWrapper`, `getFavouritesWrapper`, `getThreadsWrapper`, `getPostsWrapper`, `getPostsWrapperNew`, `getTradePostInfo`, `getQuotePostResponseBody`, `login`, `refreshAuthenticityToken`, `refreshAuthenticityTokenRx`, `addThreadFavorite`, `removeThreadFavorite`, `reply`, `getQuoteInfo`, `replyQuote`, `getPmGroups`, `getPmList`, `postPm`, `getNewThreadInfo`, `newThread`, `getEditPostInfo`, `editPost`, `searchForum`, `searchUser`, `getMyNotes`, `getMyNotesSystem`, `getProfile`, `getProfileWeb`, `getFriends`, `getHomeThreads`, `getHomeReplies`, `getRatePreInfo`, `rate`, `getReportPreInfo`, `report`, `autoSign`, `vote`, `getRates`, `getDarkRoom`, `getWebBlackList`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — app/src/main/java/me/ykrank/s1next/data/api/S1Service.kt:23
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / REDACTED Manager, Azure Key Vault, HashiCorp Vault — not a key compiled into the app) and encrypt the store that holds the personal data (SQLCipher, a Realm encryptionKey, field-level AEAD) — partial coverage still leaves gaps.
- Enforce HTTPS on the server that receives this data: terminate TLS in it (Ktor's sslConnector, Spring's server.ssl and requiresSecure, Netty's SslContextBuilder.forServer) and send Strict-Transport-Security (Ktor's HttpsRedirect), or run it behind a TLS-terminating proxy, so data in transit is always encrypted.
M1 · Documentation (README)
- The root README is 53 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- 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.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
- A CI pipeline exists but no test-runner invocation (your stack's test command, or a test job) was found — changes may merge without the suite running.
What to do
- Run the test suite in CI via an explicit runner step (`./gradlew test` for the toolchain this pipeline already uses) and gate merges on it.
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `app/build.gradle.kts` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — app/build.gradle.kts:132
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
- `AppDatabaseManagerImpl` declares `close` — it has told its callers it holds something worth ending — and it creates `executors` itself (line 23, `Executors.newSingleThreadExecutor(…)`), which makes that instance its own. Nothing in the file releases it — no `executors.shutdown()`, on any path — and it is private and never handed on as a value (passed, returned, stored, or read through another instance), so no other owner can be releasing it. On what was read, `close` ends the object and leaves what `Executors.newSingleThreadExecutor(…)` holds — a file descriptor, a socket, a pool's live threads — open until the collector happens to reach it, one per instance. Release it in `close` (`executors.shutdown()`), or, if it truly does not need releasing, drop the `close` so the claim and the behaviour agree. — app/src/main/java/me/ykrank/s1next/data/db/AppDatabaseManager.kt:23
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X20 · Mistyped argument guard
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. (×6) — library/src/main/java/com/github/ykrank/androidtools/widget/AlipayDonate.kt:130, library/src/main/java/com/github/ykrank/androidtools/widget/AlipayDonate.kt:151, library/src/main/java/com/github/ykrank/androidtools/widget/AlipayDonate.kt:172, …
- 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. — app/src/main/java/me/ykrank/s1next/widget/hostcheck/NoticeCheckTask.kt:44
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 82.3 | Strong | Solid. |
| Architecture | 79.8 | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 36.5 | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 59.8 | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 53.3 | Adequate — gated by D36, C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X6 Hand-rolled structured-format parsing — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model — an Exposed table, a data class, a Room entity or a SQL migration's table named for it — Hibernate Envers' @Audited, a JPA entity listener, Hibernate event listener or jOOQ RecordListener that records each change) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 64 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Dagger rejects, at compile time, a component that holds a binding with a narrower scope than its own.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean.
- AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- D10 Test Quality — ~122 lines of test code exist on disk but weren't loaded from the analyzed solution (excluded from the .sln, or co-located/using a test attribute not loaded here), so test quality couldn't be assessed. Include the tests in the analyzed solution to enable this check.
- D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
- D12 Dependency Hygiene — Not scored — a Gradle build resolved 261 artifact(s) across its subprojects (102 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- 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.
- D19 Documentation Quality — D19 reads .NET projects and npm packages as units; 4 folder(s) declared by build.gradle.kts were not judged for an overview, an example or the map.
- D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Java surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .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
- 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) — 8 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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 measured
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (27 value object(s))
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (11 CQRS handler(s))
- ED5 Idempotency — Not assessed, and this one is on us: 11 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JVM source (3 module(s), 645 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 — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not 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.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — 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
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — 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.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 1 finding(s)
- REDACTED
Serious — 164 finding(s)
- Duplicated block (10 lines × 2) app/src/main/java/me/ykrank/s1next/data/api/model/AjaxResult.kt:20
- Duplicated block (10 lines × 2) app/src/main/java/me/ykrank/s1next/view/page/setting/fragment/BackupPreferenceFragment.kt:92
- Duplicated block (10 lines × 2) app/src/main/java/me/ykrank/s1next/view/fragment/BaseLoadMoreRecycleViewFragment.kt:65
- Duplicated block (10 lines × 2) app/src/main/java/me/ykrank/s1next/view/page/app/AppPostListFragment.kt:242
- Duplicated block (10 lines × 2) app/src/main/java/me/ykrank/s1next/view/page/post/viewmodel/PostBlackViewModel.kt:43
- Duplicated block (10 lines × 2) app/src/main/java/me/ykrank/s1next/view/page/post/adapter/PostAdapterDelegate.kt:184
- Duplicated block (10 lines × 2) app/src/main/java/me/ykrank/s1next/view/page/setting/blacklist/BlackListSettingFragment.kt:133
- Duplicated block (10 lines × 2) library/src/main/java/com/github/ykrank/androidtools/widget/BackupDelegate.kt:111
- Duplicated block (9 lines × 2) app/src/main/java/me/ykrank/s1next/view/page/post/viewmodel/PostViewModel.kt:125
- Duplicated block (9 lines × 2) app/src/main/java/me/ykrank/s1next/view/page/app/AppPostListFragment.kt:253
- Duplicated block (9 lines × 2) app/src/main/java/me/ykrank/s1next/view/page/app/AppPostListFragment.kt:263
- Duplicated block (9 lines × 2) app/src/main/java/me/ykrank/s1next/data/db/biz/ReadProgressBiz.kt:24
- Duplicated block (9 lines × 2) app/src/main/java/me/ykrank/s1next/view/fragment/NewReportFragment.kt:156
- Duplicated block (9 lines × 2) library/src/main/java/com/github/ykrank/androidtools/ui/LibBaseActivity.kt:150
- Duplicated block (9 lines × 2) app/src/main/java/me/ykrank/s1next/binding/RecyclerViewBindingAdapter.java:14
- Duplicated block (9 lines × 2) app/src/main/java/me/ykrank/s1next/view/activity/LoginActivity.java:21
- Edited copy of a member (14 corresponding lines) app/src/main/java/me/ykrank/s1next/view/page/setting/fragment/BackupPreferenceFragment.kt:88
- Edited copy of a member (14 corresponding lines) app/src/main/java/me/ykrank/s1next/view/fragment/OpenSourceLicensesFragment.java:42
- Edited copy of a member (14 corresponding lines) app/src/main/java/me/ykrank/s1next/view/fragment/NoteFragment.kt:83
- Edited copy of a member (14 corresponding lines) app/src/main/java/me/ykrank/s1next/data/api/model/collection/Posts.kt:64
- Edited copy of a member (14 corresponding lines) app/src/main/java/me/ykrank/s1next/data/db/dbmodel/BlackList.kt:166
- Edited copy of a member (14 corresponding lines) app/src/main/java/me/ykrank/s1next/view/fragment/UserReplyFragment.kt:41
- Edited copy of a member (14 corresponding lines) app/src/normal/java/me/ykrank/s1next/util/BuglyUtils.kt:22
- Swallowed exception (caught, then discarded) library/src/main/java/com/github/ykrank/androidtools/widget/AlipayDonate.kt:130
- Swallowed exception (caught, then discarded) library/src/main/java/com/github/ykrank/androidtools/widget/AlipayDonate.kt:151
- Swallowed exception (caught, then discarded) library/src/main/java/com/github/ykrank/androidtools/widget/AlipayDonate.kt:172
- Swallowed exception (caught, then discarded) library/src/main/java/com/github/ykrank/androidtools/widget/AlipayDonate.kt:187
- Swallowed exception (caught, then discarded) app/src/main/java/me/ykrank/s1next/data/db/biz/LoginUserBiz.kt:63
- Swallowed exception (caught, then discarded) app/src/main/java/me/ykrank/s1next/data/db/biz/LoginUserBiz.kt:74
- Change coupling: AppComponent.kt ↔ AppDatabase.kt app/src/main/java/me/ykrank/s1next/AppComponent.kt:1
- Change coupling: AppDatabase.kt ↔ DbModule.kt app/src/main/java/me/ykrank/s1next/data/db/AppDatabase.kt:1
- Change coupling: BuildTypeModule.kt ↔ AppModule.kt app/src/debug/java/me/ykrank/s1next/BuildTypeModule.kt:1
- Change coupling: ApiCacheProvider.kt ↔ PostListPagerFragment.kt app/src/main/java/me/ykrank/s1next/data/api/ApiCacheProvider.kt:1
- Change coupling: AppPostsWrapper.kt ↔ Post.kt app/src/main/java/me/ykrank/s1next/data/api/app/model/AppPostsWrapper.kt:1
- Edited copy of a member (9 corresponding lines) library/src/main/java/com/github/ykrank/androidtools/util/ColorDrawableUtils.java:68
- Edited copy of a member (9 corresponding lines) library/src/main/java/com/github/ykrank/androidtools/util/ContextUtils.kt:63
- Edited copy of a member (9 corresponding lines) app/src/main/java/me/ykrank/s1next/view/activity/NoteActivity.java:24
- Edited copy of a member (9 corresponding lines) app/src/main/java/me/ykrank/s1next/widget/span/AcfunSpan.kt:68
- Edited copy of a member (9 corresponding lines) app/src/main/java/me/ykrank/s1next/view/fragment/UserReplyFragment.kt:61
- Edited copy of a member (11 corresponding lines) app/src/main/java/me/ykrank/s1next/data/api/model/Note.kt:95
- Edited copy of a member (11 corresponding lines) library/src/main/java/com/github/ykrank/androidtools/widget/BackupDelegate.kt:167
- Edited copy of a member (11 corresponding lines) app/src/main/java/me/ykrank/s1next/data/api/app/model/AppPostsWrapper.kt:126
- Edited copy of a member (11 corresponding lines) app/src/main/java/me/ykrank/s1next/view/dialog/requestdialog/EditPostRequestDialogFragment.kt:69
- Edited copy of a member (11 corresponding lines) library/src/main/java/com/github/ykrank/androidtools/ui/LibBaseRecyclerViewFragment.kt:317
- Duplicated block (6 lines × 2) app/src/main/java/me/ykrank/s1next/view/activity/BaseActivity.kt:245
- Duplicated block (6 lines × 2) app/src/main/java/me/ykrank/s1next/view/adapter/BlackWordCursorListViewAdapter.kt:21
- Duplicated block (6 lines × 2) app/src/main/java/me/ykrank/s1next/view/adapter/delegate/DarkRoomAdapterDelegate.kt:15
- Duplicated block (6 lines × 2) app/src/main/java/me/ykrank/s1next/view/adapter/delegate/PmLeftAdapterDelegate.kt:33
- Duplicated block (6 lines × 2) app/src/main/java/me/ykrank/s1next/view/adapter/delegate/PmLeftAdapterDelegate.kt:50
- TodoComment app/src/main/java/me/ykrank/s1next/widget/span/AcfunSpan.kt:67
- TodoComment app/src/main/java/me/ykrank/s1next/view/internal/DrawerLayoutDelegateConcrete.kt:206
- TodoComment app/src/main/java/me/ykrank/s1next/view/activity/ThreadListActivity.kt:97
- TodoComment app/src/main/java/me/ykrank/s1next/data/db/AppDatabaseManager.kt:34
- Edited copy of a member (15 corresponding lines) app/src/main/java/me/ykrank/s1next/data/api/model/Pm.kt:71
- Edited copy of a member (15 corresponding lines) app/src/main/java/me/ykrank/s1next/widget/glide/AvatarFailUrlsCache.kt:111
- Edited copy of a member (15 corresponding lines) app/src/main/java/me/ykrank/s1next/view/fragment/FavouriteListFragment.kt:72
- Edited copy of a member (15 corresponding lines) app/src/main/java/me/ykrank/s1next/view/page/post/adapter/PostAdapterDelegate.kt:69
- Edited copy of a member (12 corresponding lines) library/src/main/java/com/github/ykrank/androidtools/widget/glide/transformations/FitOutWidthBitmapTransformation.java:18
- Edited copy of a member (12 corresponding lines) app/src/main/java/me/ykrank/s1next/data/cache/api/ApiCacheFlow.kt:126
- Edited copy of a member (12 corresponding lines) app/src/main/java/me/ykrank/s1next/data/api/model/collection/Posts.kt:169
- Edited copy of a member (12 corresponding lines) app/src/main/java/me/ykrank/s1next/view/fragment/NewReportFragment.kt:55
- Edited copy of a member (7 corresponding lines) app/src/main/java/me/ykrank/s1next/viewmodel/DarkRoomViewModel.kt:15
- Edited copy of a member (7 corresponding lines) app/src/main/java/me/ykrank/s1next/view/activity/NewRateActivity.kt:41
- Edited copy of a member (7 corresponding lines) app/src/main/java/me/ykrank/s1next/view/page/app/AppPostListPagerFragment.kt:342
- Duplicated block (12 lines × 2) app/src/main/java/me/ykrank/s1next/viewmodel/BlackDialogViewModel.kt:46
- Duplicated block (12 lines × 2) app/src/main/java/me/ykrank/s1next/view/fragment/BaseLoadMoreRecycleViewFragment.kt:122
- Duplicated block (12 lines × 2) app/src/main/java/me/ykrank/s1next/view/fragment/BaseLoadMoreRecycleViewFragment.kt:135
- Duplicated block (7 lines × 2) app/src/main/java/me/ykrank/s1next/view/page/app/AppPostListFragment.kt:130
- Duplicated block (7 lines × 2) app/src/main/java/me/ykrank/s1next/view/fragment/DarkRoomFragment.kt:33
- Duplicated block (7 lines × 2) app/src/main/java/me/ykrank/s1next/view/page/post/viewmodel/PostViewModel.kt:161
- Duplicated block (8 lines × 2) app/src/main/java/me/ykrank/s1next/view/page/login/AppLoginDialogFragment.kt:57
- Duplicated block (8 lines × 2) app/src/main/java/me/ykrank/s1next/view/page/setting/blacklist/BlackListSettingFragment.kt:124
- Duplicated block (8 lines × 2) library/src/main/java/com/github/ykrank/androidtools/util/ColorDrawableUtils.java:151
- Low cohesion: DownloadPreferenceFragment (LCOM4 5) app/src/main/java/me/ykrank/s1next/view/page/setting/fragment/DownloadPreferenceFragment.kt:36
- Low cohesion: LibBaseActivity (LCOM4 4) library/src/main/java/com/github/ykrank/androidtools/ui/LibBaseActivity.kt:24
- Low cohesion: LibBaseRecyclerViewAdapter (LCOM4 4) library/src/main/java/com/github/ykrank/androidtools/ui/adapter/LibBaseRecyclerViewAdapter.kt:20
- REDACTED
- REDACTED
- Edited copy of a member (20 corresponding lines) app/src/main/java/me/ykrank/s1next/data/api/app/model/AppPostsWrapper.kt:170
- Edited copy of a member (20 corresponding lines) app/src/main/java/me/ykrank/s1next/view/activity/NewThreadActivity.kt:16
- Edited copy of a member (28 corresponding lines) app/src/main/java/me/ykrank/s1next/view/fragment/EditPostFragment.kt:67
- Edited copy of a member (28 corresponding lines) app/src/main/java/me/ykrank/s1next/view/page/post/viewmodel/PostViewModel.kt:107
- Edited copies of one member (3 members, 15+ corresponding lines) app/src/main/java/me/ykrank/s1next/view/activity/FriendListActivity.java:31
- Edited copies of one member (3 members, 15+ corresponding lines) app/src/main/java/me/ykrank/s1next/widget/span/AcfunSpan.kt:50
- Edited copy of a member (17 corresponding lines) app/src/main/java/me/ykrank/s1next/view/page/app/AppPostListPagerFragment.kt:322
- Edited copy of a member (17 corresponding lines) app/src/main/java/me/ykrank/s1next/view/page/setting/fragment/DownloadPreferenceFragment.kt:130
- Edited copies of one member (3 members, 10+ corresponding lines) app/src/main/java/me/ykrank/s1next/AppModule.kt:73
- Edited copies of one member (3 members, 10+ corresponding lines) app/src/main/java/me/ykrank/s1next/data/api/model/Friend.kt:21
- Edited copy of a member (10 corresponding lines) library/src/main/java/com/github/ykrank/androidtools/util/TransitionUtils.java:93
- Edited copy of a member (10 corresponding lines) app/src/main/java/me/ykrank/s1next/view/page/app/AppPostListPagerFragment.kt:154
- Edited copy of a member (8 corresponding lines) app/src/main/java/me/ykrank/s1next/widget/glide/AvatarFailUrlsCache.kt:97
- Edited copy of a member (8 corresponding lines) app/src/main/java/me/ykrank/s1next/widget/uploadimg/model/RIPImageUpload.kt:32
- Edited copy of a member (4 corresponding lines) library/src/main/java/com/github/ykrank/androidtools/widget/track/trackhandler/page/FragmentEndTrackHandler.java:21
- Edited copy of a member (4 corresponding lines) library/src/main/java/com/github/ykrank/androidtools/widget/track/trackhandler/page/LocalFragmentEndTrackHandler.java:21
- Duplicated block (20 lines × 2) app/src/main/java/me/ykrank/s1next/view/page/post/adapter/PostAdapterDelegate.kt:91
- Duplicated block (20 lines × 2) app/src/main/java/me/ykrank/s1next/viewmodel/HomeReplyTitleViewModel.java:1
- Duplicated block (5 lines × 3) app/src/main/java/me/ykrank/s1next/view/dialog/ThreadGoDialogFragment.kt:60
- Duplicated block (5 lines × 3) app/src/main/java/me/ykrank/s1next/view/activity/RateDetailsListActivity.kt:31
- Duplicated block (5 lines × 2) app/src/main/java/me/ykrank/s1next/data/api/model/wrapper/HomeReplyWebWrapper.java:31
- Duplicated block (5 lines × 2) library/src/main/java/com/github/ykrank/androidtools/util/ColorDrawableUtils.java:87
- Off the main sequence: :JKeyboardPanelSwitch
- Off the main sequence: :library
- S1ApiCacheProvider.getPostsWrapper (cyclomatic 28) app/src/main/java/me/ykrank/s1next/data/cache/api/S1ApiCacheProvider.kt:116
- AppPost.equals (cyclomatic 21) app/src/main/java/me/ykrank/s1next/data/api/app/model/AppPostsWrapper.kt:142
- Post.equals (cyclomatic 20) app/src/main/java/me/ykrank/s1next/data/api/model/Post.kt:175
- AppThread.equals (cyclomatic 19) app/src/main/java/me/ykrank/s1next/data/api/app/model/AppThread.kt:124
- Posts.filterPost (cyclomatic 18) app/src/main/java/me/ykrank/s1next/data/api/model/collection/Posts.kt:193
- PostListPagerFragment.onNextSuccess (cyclomatic 16) app/src/main/java/me/ykrank/s1next/view/page/post/postlist/PostListPagerFragment.kt:296
- Hotspot: app/src/main/java/me/ykrank/s1next/data/cache/api/S1ApiCacheProvider.kt app/src/main/java/me/ykrank/s1next/data/cache/api/S1ApiCacheProvider.kt:116
- S1ApiCacheProvider.getPostsWrapper (cognitive 44) app/src/main/java/me/ykrank/s1next/data/cache/api/S1ApiCacheProvider.kt:116
- PostListPagerFragment.onNextSuccess (cognitive 37) app/src/main/java/me/ykrank/s1next/view/page/post/postlist/PostListPagerFragment.kt:296
- Posts.filterPost (cognitive 33) app/src/main/java/me/ykrank/s1next/data/api/model/collection/Posts.kt:193
- PostMovementMethod.onTouchEvent (cognitive 32) app/src/main/java/me/ykrank/s1next/widget/span/PostMovementMethod.kt:33
- UrlDrawable.setBounds (cognitive 29) app/src/main/java/me/ykrank/s1next/widget/span/UrlDrawable.java:140
- PostAdapterDelegate.onBindViewHolderData (cognitive 27) app/src/main/java/me/ykrank/s1next/view/page/post/adapter/PostAdapterDelegate.kt:85
- AppPostListPagerFragment.onNext (cognitive 26) app/src/main/java/me/ykrank/s1next/view/page/app/AppPostListPagerFragment.kt:210
- StringUtils.uniDecode (cognitive 24) library/src/main/java/com/github/ykrank/androidtools/util/StringUtils.kt:61
- LibViewBindingAdapter.setBackgroundTint (cognitive 24) library/src/main/java/com/github/ykrank/androidtools/binding/LibViewBindingAdapter.java:82
- TagFragmentStatePagerAdapter.restoreState (cognitive 21) library/src/main/java/com/github/ykrank/androidtools/widget/TagFragmentStatePagerAdapter.java:196
- AppPost.equals (cognitive 20) app/src/main/java/me/ykrank/s1next/data/api/app/model/AppPostsWrapper.kt:142
- ErrorUtil.parseNetError (cognitive 20) app/src/main/java/me/ykrank/s1next/util/ErrorUtil.kt:49
- Post.equals (cognitive 19) app/src/main/java/me/ykrank/s1next/data/api/model/Post.kt:175
- PostBlackViewModel.showBlackListMenu (cognitive 19) app/src/main/java/me/ykrank/s1next/view/page/post/viewmodel/PostBlackViewModel.kt:67
- PostViewModel.onAvatarLongClick (cognitive 19) app/src/main/java/me/ykrank/s1next/view/page/post/viewmodel/PostViewModel.kt:68
- AppThread.equals (cognitive 18) app/src/main/java/me/ykrank/s1next/data/api/app/model/AppThread.kt:124
- Threads.getFilterThread (cognitive 18) app/src/main/java/me/ykrank/s1next/data/api/model/collection/Threads.kt:85
- BlackList.equals (cognitive 18) app/src/main/java/me/ykrank/s1next/data/db/dbmodel/BlackList.kt:196
- NetworkUtil.isWifiConnected (cognitive 17) library/src/main/java/com/github/ykrank/androidtools/util/NetworkUtil.java:20
- KeyboardStatusListener.calculateKeyboardShowing (cognitive 16) JKeyboardPanelSwitch/src/main/java/cn/dreamtobe/kpswitch/util/KeyboardUtil.java:360
- MethodTooLong: S1ApiCacheProvider.getPostsWrapper app/src/main/java/me/ykrank/s1next/data/cache/api/S1ApiCacheProvider.kt:116
- Members sharing a duplicated core (4 members, 50+ identical tokens) library/src/main/java/com/github/ykrank/androidtools/widget/AlipayDonate.kt:120
- Edited copy of a member (63 corresponding lines) app/src/main/java/me/ykrank/s1next/view/page/app/AppPostListFragment.kt:138
- Edited copy of a member (26 corresponding lines) app/src/main/java/me/ykrank/s1next/data/api/app/model/AppPostsWrapper.kt:142
- Edited copy of a member (36 corresponding lines) app/src/main/java/me/ykrank/s1next/data/db/biz/BlackListBiz.kt:89
- Edited copy of a member (25 corresponding lines) app/src/main/java/me/ykrank/s1next/view/activity/NewPmActivity.kt:17
- Edited copy of a member (19 corresponding lines) app/src/main/java/me/ykrank/s1next/view/activity/NewRateActivity.kt:16
- Edited copy of a member (24 corresponding lines) library/src/main/java/com/github/ykrank/androidtools/widget/BackupDelegate.kt:101
- Edited copy of a member (16 corresponding lines) app/src/main/java/me/ykrank/s1next/view/page/app/AppPostListPagerFragment.kt:268
- Edited copy of a member (13 corresponding lines) library/src/main/java/com/github/ykrank/androidtools/util/TransitionUtils.java:50
- Edited copies of one member (3 members, 8+ corresponding lines) app/src/main/java/me/ykrank/s1next/view/dialog/ThreadFavouritesAddDialogFragment.kt:55
- Edited copy of a member (6 corresponding lines) app/src/main/java/me/ykrank/s1next/view/page/app/AppPostListFragment.kt:224
- Edited copy of a member (5 corresponding lines) app/src/main/java/me/ykrank/s1next/data/api/model/Friend.kt:44
- Duplicated block (40–56 lines × 2) app/src/main/java/me/ykrank/s1next/view/page/app/AppPostListFragment.kt:140
- Duplicated block (35–40 lines × 2) app/src/main/java/me/ykrank/s1next/view/page/post/viewmodel/PostBlackViewModel.kt:69
- Duplicated block (23 lines × 2) library/src/main/java/com/github/ykrank/androidtools/util/FileUtil.kt:39
- Duplicated block (20–22 lines × 2) app/src/main/java/me/ykrank/s1next/view/page/app/AppPostListFragment.kt:178
- Duplicated block (21 lines × 2) app/src/main/java/me/ykrank/s1next/widget/span/BilibiliSpan.kt:32
- Duplicated block (17 lines × 2) app/src/main/java/me/ykrank/s1next/view/fragment/RateDetailsListFragment.kt:49
- Duplicated block (15–17 lines × 2) app/src/main/java/me/ykrank/s1next/view/page/post/viewmodel/PostViewModel.kt:108
- Duplicated block (13 lines × 3) app/src/main/java/me/ykrank/s1next/view/fragment/NoteFragment.kt:65
- Duplicated block (11 lines × 4) library/src/main/java/com/github/ykrank/androidtools/widget/AlipayDonate.kt:123
- Duplicated block (10–11 lines × 2) library/src/main/java/com/github/ykrank/androidtools/binding/LibImageViewBindingAdapter.kt:72
- Duplicated block (15 lines × 2) app/src/main/java/me/ykrank/s1next/view/dialog/ProgressDialogFragment.kt:72
- Duplicated block (8 lines × 3) app/src/main/java/me/ykrank/s1next/view/dialog/requestdialog/NewThreadRequestDialogFragment.kt:39
- Duplicated block (5 lines × 4) app/src/main/java/me/ykrank/s1next/view/adapter/delegate/HomeReplyItemAdapterDelegate.kt:23
- Duplicated block (16 lines × 2) JKeyboardPanelSwitch/src/main/java/cn/dreamtobe/kpswitch/util/KPSwitchConflictUtil.java:90
- Duplicated block (41 lines × 2) JKeyboardPanelSwitch/src/main/java/cn/dreamtobe/kpswitch/widget/KPSwitchFSPanelLinearLayout.java:49
- Duplicated block (76 lines × 2) JKeyboardPanelSwitch/src/main/java/cn/dreamtobe/kpswitch/widget/KPSwitchPanelFrameLayout.java:46
- Duplicated block (72 lines × 3) JKeyboardPanelSwitch/src/main/java/cn/dreamtobe/kpswitch/widget/KPSwitchPanelFrameLayout.java:46
- Duplicated block (32 lines × 3) JKeyboardPanelSwitch/src/main/java/cn/dreamtobe/kpswitch/widget/KPSwitchRootFrameLayout.java:44
- Duplicated block (25 lines × 4) JKeyboardPanelSwitch/src/main/java/cn/dreamtobe/kpswitch/widget/KPSwitchRootFrameLayout.java:44
- Duplicated block (6 lines × 3) app/src/main/java/me/ykrank/s1next/view/activity/FriendListActivity.java:23
- Owned disposable field is never released app/src/main/java/me/ykrank/s1next/data/db/AppDatabaseManager.kt:23
- Swallowed exception (empty catch) app/src/main/java/me/ykrank/s1next/widget/hostcheck/NoticeCheckTask.kt:44
Minor — 237 finding(s)
- Orphaned file app/src/main/java/me/ykrank/s1next/view/page/post/postlist/PostListPagerFragment.kt:1
- Orphaned file JKeyboardPanelSwitch/src/main/java/cn/dreamtobe/kpswitch/util/KeyboardUtil.java:1
- Orphaned file app/src/main/java/me/ykrank/s1next/data/cache/api/S1ApiCacheProvider.kt:1
- Orphaned file JKeyboardPanelSwitch/src/main/java/cn/dreamtobe/kpswitch/util/KPSwitchConflictUtil.java:1
- Orphaned file app/src/main/java/me/ykrank/s1next/view/page/app/AppPostListPagerFragment.kt:1
- Orphaned file app/src/main/java/me/ykrank/s1next/widget/span/GlideImageGetter.kt:1
- Orphaned file app/src/main/java/me/ykrank/s1next/view/activity/SearchActivity.kt:1
- Orphaned file app/src/main/java/me/ykrank/s1next/binding/TextViewBindingAdapter.kt:1
- Orphaned file app/src/main/java/me/ykrank/s1next/view/page/post/postedit/BasePostEditFragment.kt:1
- Orphaned file app/src/main/java/me/ykrank/s1next/view/page/app/AppPostListFragment.kt:1
- Orphaned file app/src/main/java/me/ykrank/s1next/view/activity/UserHomeActivity.kt:1
- Orphaned file app/src/main/java/me/ykrank/s1next/view/internal/DrawerLayoutDelegateConcrete.kt:1
- Orphaned file library/src/main/java/com/github/ykrank/androidtools/ui/LibBaseRecyclerViewFragment.kt:1
- Orphaned file app/src/main/java/me/ykrank/s1next/view/activity/BaseActivity.kt:1
- Orphaned file app/src/main/java/me/ykrank/s1next/binding/ImageViewBindingAdapter.kt:1
- Orphaned file app/src/main/java/me/ykrank/s1next/data/api/model/Post.kt:1
- Orphaned file app/src/main/java/me/ykrank/s1next/view/activity/ThreadListActivity.kt:1
- Orphaned file app/src/main/java/me/ykrank/s1next/view/fragment/GalleryFragment.kt:1
- Orphaned file app/src/main/java/me/ykrank/s1next/AppComponent.kt:1
- Orphaned file app/src/main/java/me/ykrank/s1next/data/cache/api/ApiCacheFlow.kt:1
- Orphaned file app/src/main/java/me/ykrank/s1next/data/api/S1Service.kt:1
- Orphaned file library/src/main/java/com/github/ykrank/androidtools/binding/LibViewBindingAdapter.java:1
- Orphaned file app/src/main/java/me/ykrank/s1next/data/db/biz/BlackListBiz.kt:1
- Orphaned file app/src/main/java/me/ykrank/s1next/data/api/business/PostFilter.kt:1
- Orphaned file app/src/main/java/me/ykrank/s1next/data/api/model/collection/Posts.kt:1
- Duplicated predicate app/src/main/java/me/ykrank/s1next/view/fragment/EditPostFragment.kt:89
- Duplicated predicate app/src/main/java/me/ykrank/s1next/view/page/app/AppPostListFragment.kt:225
- Duplicated predicate app/src/main/java/me/ykrank/s1next/widget/span/BilibiliSpan.kt:32
- Duplicated predicate app/src/main/java/me/ykrank/s1next/widget/span/BilibiliSpan.kt:44
- Duplicated predicate app/src/main/java/me/ykrank/s1next/data/api/app/model/AppPostsWrapper.kt:49
- Duplicated predicate app/src/main/java/me/ykrank/s1next/data/db/dbmodel/BlackList.kt:198
- Duplicated predicate library/src/main/java/com/github/ykrank/androidtools/ui/LibBaseActivity.kt:153
- Duplicated predicate app/src/main/java/me/ykrank/s1next/view/activity/NewPmActivity.kt:60
- Hand-rolled JSON/XML parsing via regex app/src/main/java/me/ykrank/s1next/data/api/model/Note.kt:42
- Hand-rolled JSON/XML parsing via regex app/src/main/java/me/ykrank/s1next/data/api/model/Note.kt:47
- Hand-rolled JSON/XML parsing via regex app/src/main/java/me/ykrank/s1next/data/api/business/PostFilter.kt:116
- Hand-rolled JSON/XML parsing via regex app/src/main/java/me/ykrank/s1next/data/api/business/PostFilter.kt:123
- `postID` spells `ID` where 221 names in the project spell it `Id` app/src/main/java/me/ykrank/s1next/view/fragment/NewRateFragment.kt:38
- `postID` spells `ID` where 221 names in the project spell it `Id` app/src/main/java/me/ykrank/s1next/view/fragment/NewReportFragment.kt:39
- Projects may be oversized for their cohesion app/build.gradle.kts:1
- Projects may be oversized for their cohesion library/build.gradle.kts:1
- REDACTED
- REDACTED
- Most significant orphaned file app/src/main/java/me/ykrank/s1next/view/page/post/postlist/PostListFragment.kt:1
- Most significant orphaned file library/src/main/java/com/github/ykrank/androidtools/widget/glide/viewtarget/CustomViewTarget.java:1
- Fat interface: S1Service (40 abstract methods) app/src/main/java/me/ykrank/s1next/data/api/S1Service.kt:23
- No ADRs found app/build.gradle.kts:4
- REDACTED
- Dormant codebase
- REDACTED
- REDACTED
- REDACTED
- Thin README README.md:1
- No ADRs
- No architecture diagram/doc
- CI test execution not evidenced
- No SAST
- No dependency-update automation app/build.gradle.kts:132
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-49b06eea402e4e19ac768667001e05d2/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-49b06eea402e4e19ac768667001e05d2/history-1.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=973" --report-format json --report-path /tmp/watchdog-gitleaks-49b06eea402e4e19ac768667001e05d2/history-2.json --exit-code 0 --source . | 4 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-49b06eea402e4e19ac768667001e05d2/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 4 | 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 8 file(s) — `app/src/main/java/me/ykrank/s1next/data/api/model/collection/Threads.kt`, `app/src/main/java/me/ykrank/s1next/data/cache/CacheDatabase.kt`, `app/src/main/java/me/ykrank/s1next/data/cache/dbmodel/Cache.kt`, `app/src/main/java/me/ykrank/s1next/data/cache/dbmodel/CacheGroup.kt`, `app/src/main/java/me/ykrank/s1next/data/db/dbmodel/BlackWord.kt`, … (+3 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 | — |