Executive summary
commons-app/apps-android-commons falls short of our standard for production, in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 56.9 out of 100 and is rated Adequate, and 22 of its 23 critical findings are security problems in the build pipeline.
Production Readiness, at 48.5, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 6.3 points. Adding automated security scanning would lift Production Readiness itself, also worth about 6.3. Raising Production Readiness to 70 would lift the score to about 63.0.
Nineteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three secrets can leak from the build pipeline, and one part of the code is no longer understood by anyone working on it. Pinning each tool to an exact version, limiting each secret to its own step and having someone learn the forgotten files would close these risks.
The product code is 71,250 lines, about €110,000 to rebuild.
If Production Readiness rose from 48.5 to 70, the lowest score rated Strong, the score would rise from 56.9 to about 63.0.
Rebuild cost: about €110,000 · Estimate
| Cost to rebuild | €37,000 to €180,000, for 612 to 1,943 hours of work, about 0.8 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 57. 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: 71,250 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: which parts of the code depend on which
| uses → | 1 customselector.model | 2 filepicker | 3 kvstore | 4 location | 5 explore.paging.PagingContract | 6 profile.leaderboard | 7 wikidata.model | 8 explore.paging | 9 wikidata.mwapi | 10 auth.csrf | 11 explore.media | 12 actions | 13 wikidata | 14 upload.structure.depictions | 15 repository | 16 upload.categories | 17 upload.mediaDetails | 18 notification | 19 upload.depicts | 20 upload | 21 utils | 22 theme | 23 description | 24 explore.depictions | 25 review | 26 mwapi | 27 nearby | 28 nearby.fragments | 29 bookmarks.locations | 30 explore.map | 31 explore | 32 contributions | 33 customselector.ui.selector | 34 media | 35 category | 36 bookmarks | 37 db | 38 di | 39 auth | 40 fr.free.nrw.commons |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 customselector.model | ||||||||||||||||||||||||||||||||||||||||
| 2 filepicker | ||||||||||||||||||||||||||||||||||||||||
| 3 kvstore | ||||||||||||||||||||||||||||||||||||||||
| 4 location | ||||||||||||||||||||||||||||||||||||||||
| 5 explore.paging.PagingContract | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 6 profile.leaderboard | 5 | 1 | 5 | |||||||||||||||||||||||||||||||||||||
| 7 wikidata.model | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 explore.paging | 5 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 wikidata.mwapi | 6 | |||||||||||||||||||||||||||||||||||||||
| 10 auth.csrf | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 explore.media | 1 | 1 | 5 | 1 | 2 | 1 | 6 | |||||||||||||||||||||||||||||||||
| 12 actions | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 13 wikidata | 1 | 4 | 3 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||
| 14 upload.structure.depictions | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 15 repository | 1 | 3 | 7 | 15 | 2 | 4 | 4 | |||||||||||||||||||||||||||||||||
| 16 upload.categories | 3 | 1 | 7 | 1 | 4 | |||||||||||||||||||||||||||||||||||
| 17 upload.mediaDetails | 2 | 6 | 4 | 3 | 19 | |||||||||||||||||||||||||||||||||||
| 18 notification | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 19 upload.depicts | 1 | 2 | 3 | 1 | 1 | 6 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||
| 20 upload | 5 | 8 | 10 | 2 | 1 | 2 | 2 | 2 | 1 | 3 | 2 | 2 | 3 | 17 | 2 | 1 | 3 | 4 | 2 | |||||||||||||||||||||
| 21 utils | 1 | 1 | 9 | 2 | 1 | 2 | 1 | 3 | ||||||||||||||||||||||||||||||||
| 22 theme | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 description | 1 | 1 | 3 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 24 explore.depictions | 1 | 1 | 6 | 1 | 1 | 1 | 2 | 1 | 3 | |||||||||||||||||||||||||||||||
| 25 review | 2 | 2 | 1 | 2 | 1 | 2 | 4 | |||||||||||||||||||||||||||||||||
| 26 mwapi | 1 | 2 | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 27 nearby | 1 | 5 | 1 | 1 | 1 | 2 | 1 | 2 | 2 | 2 | ||||||||||||||||||||||||||||||
| 28 nearby.fragments | 2 | 4 | 1 | 1 | 1 | 2 | 2 | 2 | 3 | 1 | 1 | |||||||||||||||||||||||||||||
| 29 bookmarks.locations | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 explore.map | 3 | 14 | 1 | 1 | 2 | 2 | 1 | 7 | ||||||||||||||||||||||||||||||||
| 31 explore | 1 | 2 | 1 | 1 | 4 | 2 | 2 | 6 | ||||||||||||||||||||||||||||||||
| 32 contributions | 2 | 5 | 7 | 3 | 1 | 1 | 2 | 3 | 1 | 1 | 4 | 1 | 1 | 8 | 1 | 2 | 5 | 8 | ||||||||||||||||||||||
| 33 customselector.ui.selector | 7 | 6 | 1 | 2 | 3 | 2 | ||||||||||||||||||||||||||||||||||
| 34 media | 2 | 2 | 1 | 4 | 10 | 2 | 1 | 3 | 1 | 2 | 1 | 1 | 3 | 2 | 2 | 4 | 2 | 4 | 13 | |||||||||||||||||||||
| 35 category | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 6 | ||||||||||||||||||||||||||||||
| 36 bookmarks | 1 | 1 | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 37 db | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||
| 38 di | 2 | 1 | 1 | 1 | 3 | 1 | 3 | 3 | 1 | 1 | 2 | 4 | 8 | 1 | 1 | 2 | 5 | 3 | 1 | 1 | 2 | 1 | 4 | 4 | 4 | 8 | 3 | 2 | 1 | 6 | 3 | |||||||||
| 39 auth | 3 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 fr.free.nrw.commons | 1 | 2 | 2 | 2 | 1 | 1 |
5→8 explore.paging.PagingContract uses explore.paging part of a loop✕
- Connections
- 1 pair of types, where a type in explore.paging.PagingContract uses a type in explore.paging.
- The types involved
fr.free.nrw.commons.explore.paging.PagingContract.Presenter→fr.free.nrw.commons.explore.paging.FooterItem
- Direction
- explore.paging.PagingContract uses explore.paging, so a change to explore.paging can break explore.paging.PagingContract, while a change to explore.paging.PagingContract can't break explore.paging.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→40 explore.paging.PagingContract uses fr.free.nrw.commons part of a loop✕
- Connections
- 1 pair of types, where a type in explore.paging.PagingContract uses a type in fr.free.nrw.commons.
- The types involved
fr.free.nrw.commons.explore.paging.PagingContract.Presenter→fr.free.nrw.commons.BasePresenter
- Direction
- explore.paging.PagingContract uses fr.free.nrw.commons, so a change to fr.free.nrw.commons can break explore.paging.PagingContract, while a change to explore.paging.PagingContract can't break fr.free.nrw.commons.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→26 profile.leaderboard uses mwapi part of a loop✕
- Connections
- 5 pairs of types, where a type in profile.leaderboard uses a type in mwapi.
- The types involved
fr.free.nrw.commons.profile.leaderboard.DataSourceClass→fr.free.nrw.commons.mwapi.OkHttpJsonApiClientfr.free.nrw.commons.profile.leaderboard.DataSourceFactory→fr.free.nrw.commons.mwapi.OkHttpJsonApiClientfr.free.nrw.commons.profile.leaderboard.LeaderboardFragment→fr.free.nrw.commons.mwapi.OkHttpJsonApiClientfr.free.nrw.commons.profile.leaderboard.LeaderboardListViewModel→fr.free.nrw.commons.mwapi.OkHttpJsonApiClientfr.free.nrw.commons.profile.leaderboard.ViewModelFactory→fr.free.nrw.commons.mwapi.OkHttpJsonApiClient
- Direction
- profile.leaderboard uses mwapi, so a change to mwapi can break profile.leaderboard, while a change to profile.leaderboard can't break mwapi.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→38 profile.leaderboard uses di part of a loop✕
- Connections
- 1 pair of types, where a type in profile.leaderboard uses a type in di.
- The types involved
fr.free.nrw.commons.profile.leaderboard.LeaderboardFragment→fr.free.nrw.commons.di.CommonsDaggerSupportFragment
- Direction
- profile.leaderboard uses di, so a change to di can break profile.leaderboard, while a change to profile.leaderboard can't break di.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→39 profile.leaderboard uses auth part of a loop✕
- Connections
- 5 pairs of types, where a type in profile.leaderboard uses a type in auth.
- The types involved
fr.free.nrw.commons.profile.leaderboard.DataSourceClass→fr.free.nrw.commons.auth.SessionManagerfr.free.nrw.commons.profile.leaderboard.DataSourceFactory→fr.free.nrw.commons.auth.SessionManagerfr.free.nrw.commons.profile.leaderboard.LeaderboardFragment→fr.free.nrw.commons.auth.SessionManagerfr.free.nrw.commons.profile.leaderboard.LeaderboardListViewModel→fr.free.nrw.commons.auth.SessionManagerfr.free.nrw.commons.profile.leaderboard.ViewModelFactory→fr.free.nrw.commons.auth.SessionManager
- Direction
- profile.leaderboard uses auth, so a change to auth can break profile.leaderboard, while a change to profile.leaderboard can't break auth.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→9 wikidata.model uses wikidata.mwapi part of a loop✕
- Connections
- 1 pair of types, where a type in wikidata.model uses a type in wikidata.mwapi.
- The types involved
fr.free.nrw.commons.wikidata.model.Entities→fr.free.nrw.commons.wikidata.mwapi.MwResponse
- Direction
- wikidata.model uses wikidata.mwapi, so a change to wikidata.mwapi can break wikidata.model, while a change to wikidata.model can't break wikidata.mwapi.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→5 explore.paging uses explore.paging.PagingContract✕
- Connections
- 5 pairs of types, where a type in explore.paging uses a type in explore.paging.PagingContract.
- The types involved
fr.free.nrw.commons.explore.paging.BasePagingFragment→fr.free.nrw.commons.explore.paging.PagingContract.Presenterfr.free.nrw.commons.explore.paging.BasePagingFragment→fr.free.nrw.commons.explore.paging.PagingContract.Viewfr.free.nrw.commons.explore.paging.BasePagingPresenter→fr.free.nrw.commons.explore.paging.PagingContract.Presenterfr.free.nrw.commons.explore.paging.BasePagingPresenter→fr.free.nrw.commons.explore.paging.PagingContract.Viewfr.free.nrw.commons.explore.paging.PagingView→fr.free.nrw.commons.explore.paging.PagingContract.View
- Direction
- explore.paging uses explore.paging.PagingContract, so a change to explore.paging.PagingContract can break explore.paging, while a change to explore.paging can't break explore.paging.PagingContract.
- Position
- Below the diagonal: explore.paging uses a module listed above it, which is the healthy direction.
8→38 explore.paging uses di part of a loop✕
- Connections
- 1 pair of types, where a type in explore.paging uses a type in di.
- The types involved
fr.free.nrw.commons.explore.paging.BasePagingFragment→fr.free.nrw.commons.di.CommonsDaggerSupportFragment
- Direction
- explore.paging uses di, so a change to di can break explore.paging, while a change to explore.paging can't break di.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→7 wikidata.mwapi uses wikidata.model✕
- Connections
- 6 pairs of types, where a type in wikidata.mwapi uses a type in wikidata.model.
- The types involved
fr.free.nrw.commons.wikidata.mwapi.MwErrorResponse→fr.free.nrw.commons.wikidata.model.BaseModelfr.free.nrw.commons.wikidata.mwapi.MwLegacyServiceError→fr.free.nrw.commons.wikidata.model.BaseModelfr.free.nrw.commons.wikidata.mwapi.MwQueryPage→fr.free.nrw.commons.wikidata.model.BaseModelfr.free.nrw.commons.wikidata.mwapi.MwQueryResult→fr.free.nrw.commons.wikidata.model.BaseModelfr.free.nrw.commons.wikidata.mwapi.MwResponse→fr.free.nrw.commons.wikidata.model.BaseModelfr.free.nrw.commons.wikidata.mwapi.MwServiceError→fr.free.nrw.commons.wikidata.model.BaseModel
- Direction
- wikidata.mwapi uses wikidata.model, so a change to wikidata.model can break wikidata.mwapi, while a change to wikidata.mwapi can't break wikidata.model.
- Position
- Below the diagonal: wikidata.mwapi uses a module listed above it, which is the healthy direction.
10→9 auth.csrf uses wikidata.mwapi✕
- Connections
- 2 pairs of types, where a type in auth.csrf uses a type in wikidata.mwapi.
- The types involved
fr.free.nrw.commons.auth.csrf.CsrfTokenClient→fr.free.nrw.commons.wikidata.mwapi.MwQueryResponsefr.free.nrw.commons.auth.csrf.CsrfTokenInterface→fr.free.nrw.commons.wikidata.mwapi.MwQueryResponse
- Direction
- auth.csrf uses wikidata.mwapi, so a change to wikidata.mwapi can break auth.csrf, while a change to auth.csrf can't break wikidata.mwapi.
- Position
- Below the diagonal: auth.csrf uses a module listed above it, which is the healthy direction.
10→39 auth.csrf uses auth part of a loop✕
- Connections
- 1 pair of types, where a type in auth.csrf uses a type in auth.
- The types involved
fr.free.nrw.commons.auth.csrf.CsrfTokenClient→fr.free.nrw.commons.auth.SessionManager
- Direction
- auth.csrf uses auth, so a change to auth can break auth.csrf, while a change to auth.csrf can't break auth.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→4 explore.media uses location✕
- Connections
- 1 pair of types, where a type in explore.media uses a type in location.
- The types involved
fr.free.nrw.commons.explore.media.MediaConverterKt→fr.free.nrw.commons.location.LatLng
- Direction
- explore.media uses location, so a change to location can break explore.media, while a change to explore.media can't break location.
- Position
- Below the diagonal: explore.media uses a module listed above it, which is the healthy direction.
11→5 explore.media uses explore.paging.PagingContract✕
- Connections
- 1 pair of types, where a type in explore.media uses a type in explore.paging.PagingContract.
- The types involved
fr.free.nrw.commons.explore.media.SearchMediaFragmentPresenter→fr.free.nrw.commons.explore.paging.PagingContract.Presenter
- Direction
- explore.media uses explore.paging.PagingContract, so a change to explore.paging.PagingContract can break explore.media, while a change to explore.media can't break explore.paging.PagingContract.
- Position
- Below the diagonal: explore.media uses a module listed above it, which is the healthy direction.
11→8 explore.media uses explore.paging✕
- Connections
- 5 pairs of types, where a type in explore.media uses a type in explore.paging.
- The types involved
fr.free.nrw.commons.explore.media.PageableMediaDataSource→fr.free.nrw.commons.explore.paging.LiveDataConverterfr.free.nrw.commons.explore.media.PageableMediaDataSource→fr.free.nrw.commons.explore.paging.PageableBaseDataSourcefr.free.nrw.commons.explore.media.PageableMediaFragment→fr.free.nrw.commons.explore.paging.BasePagingFragmentfr.free.nrw.commons.explore.media.SearchImagesViewHolder→fr.free.nrw.commons.explore.paging.BaseViewHolderfr.free.nrw.commons.explore.media.SearchMediaFragmentPresenterImpl→fr.free.nrw.commons.explore.paging.BasePagingPresenter
- Direction
- explore.media uses explore.paging, so a change to explore.paging can break explore.media, while a change to explore.media can't break explore.paging.
- Position
- Below the diagonal: explore.media uses a module listed above it, which is the healthy direction.
11→9 explore.media uses wikidata.mwapi✕
- Connections
- 1 pair of types, where a type in explore.media uses a type in wikidata.mwapi.
- The types involved
fr.free.nrw.commons.explore.media.MediaConverter→fr.free.nrw.commons.wikidata.mwapi.MwQueryPage
- Direction
- explore.media uses wikidata.mwapi, so a change to wikidata.mwapi can break explore.media, while a change to explore.media can't break wikidata.mwapi.
- Position
- Below the diagonal: explore.media uses a module listed above it, which is the healthy direction.
11→34 explore.media uses media part of a loop✕
- Connections
- 2 pairs of types, where a type in explore.media uses a type in media.
- The types involved
fr.free.nrw.commons.explore.media.PageableMediaDataSource→fr.free.nrw.commons.media.MediaCollectionClientfr.free.nrw.commons.explore.media.PageableMediaFragment→fr.free.nrw.commons.media.MediaDetailProvider
- Direction
- explore.media uses media, so a change to media can break explore.media, while a change to explore.media can't break media.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→35 explore.media uses category part of a loop✕
- Connections
- 1 pair of types, where a type in explore.media uses a type in category.
- The types involved
fr.free.nrw.commons.explore.media.PageableMediaFragment→fr.free.nrw.commons.category.CategoryImagesCallback
- Direction
- explore.media uses category, so a change to category can break explore.media, while a change to explore.media can't break category.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→40 explore.media uses fr.free.nrw.commons part of a loop✕
- Connections
- 6 pairs of types, where a type in explore.media uses a type in fr.free.nrw.commons.
- The types involved
fr.free.nrw.commons.explore.media.MediaConverter→fr.free.nrw.commons.Mediafr.free.nrw.commons.explore.media.PageableMediaDataSource→fr.free.nrw.commons.Mediafr.free.nrw.commons.explore.media.PageableMediaFragment→fr.free.nrw.commons.Mediafr.free.nrw.commons.explore.media.PageableMediaFragment→fr.free.nrw.commons.MediaDataExtractorfr.free.nrw.commons.explore.media.PagedMediaAdapter→fr.free.nrw.commons.MediaDataExtractorfr.free.nrw.commons.explore.media.SearchImagesViewHolder→fr.free.nrw.commons.Media
- Direction
- explore.media uses fr.free.nrw.commons, so a change to fr.free.nrw.commons can break explore.media, while a change to explore.media can't break fr.free.nrw.commons.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→7 actions uses wikidata.model✕
- Connections
- 1 pair of types, where a type in actions uses a type in wikidata.model.
- The types involved
fr.free.nrw.commons.actions.PageEditInterface→fr.free.nrw.commons.wikidata.model.Entities
- Direction
- actions uses wikidata.model, so a change to wikidata.model can break actions, while a change to actions can't break wikidata.model.
- Position
- Below the diagonal: actions uses a module listed above it, which is the healthy direction.
12→9 actions uses wikidata.mwapi✕
- Connections
- 2 pairs of types, where a type in actions uses a type in wikidata.mwapi.
- The types involved
fr.free.nrw.commons.actions.MwThankPostResponse→fr.free.nrw.commons.wikidata.mwapi.MwResponsefr.free.nrw.commons.actions.PageEditInterface→fr.free.nrw.commons.wikidata.mwapi.MwQueryResponse
- Direction
- actions uses wikidata.mwapi, so a change to wikidata.mwapi can break actions, while a change to actions can't break wikidata.mwapi.
- Position
- Below the diagonal: actions uses a module listed above it, which is the healthy direction.
12→10 actions uses auth.csrf✕
- Connections
- 2 pairs of types, where a type in actions uses a type in auth.csrf.
- The types involved
fr.free.nrw.commons.actions.PageEditClient→fr.free.nrw.commons.auth.csrf.CsrfTokenClientfr.free.nrw.commons.actions.ThanksClient→fr.free.nrw.commons.auth.csrf.CsrfTokenClient
- Direction
- actions uses auth.csrf, so a change to auth.csrf can break actions, while a change to actions can't break auth.csrf.
- Position
- Below the diagonal: actions uses a module listed above it, which is the healthy direction.
13→3 wikidata uses kvstore✕
- Connections
- 1 pair of types, where a type in wikidata uses a type in kvstore.
- The types involved
fr.free.nrw.commons.wikidata.WikidataEditService→fr.free.nrw.commons.kvstore.JsonKvStore
- Direction
- wikidata uses kvstore, so a change to kvstore can break wikidata, while a change to wikidata can't break kvstore.
- Position
- Below the diagonal: wikidata uses a module listed above it, which is the healthy direction.
13→7 wikidata uses wikidata.model✕
- Connections
- 4 pairs of types, where a type in wikidata uses a type in wikidata.model.
- The types involved
fr.free.nrw.commons.wikidata.WikiBaseClient→fr.free.nrw.commons.wikidata.model.StatementPartialfr.free.nrw.commons.wikidata.WikidataClient→fr.free.nrw.commons.wikidata.model.StatementPartialfr.free.nrw.commons.wikidata.WikidataInterface→fr.free.nrw.commons.wikidata.model.Entitiesfr.free.nrw.commons.wikidata.WikidataInterface→fr.free.nrw.commons.wikidata.model.WbCreateClaimResponse
- Direction
- wikidata uses wikidata.model, so a change to wikidata.model can break wikidata, while a change to wikidata can't break wikidata.model.
- Position
- Below the diagonal: wikidata uses a module listed above it, which is the healthy direction.
13→9 wikidata uses wikidata.mwapi✕
- Connections
- 3 pairs of types, where a type in wikidata uses a type in wikidata.mwapi.
- The types involved
fr.free.nrw.commons.wikidata.WikiBaseClient→fr.free.nrw.commons.wikidata.mwapi.MwPostResponsefr.free.nrw.commons.wikidata.WikidataEditService→fr.free.nrw.commons.wikidata.mwapi.MwPostResponsefr.free.nrw.commons.wikidata.WikidataInterface→fr.free.nrw.commons.wikidata.mwapi.MwQueryResponse
- Direction
- wikidata uses wikidata.mwapi, so a change to wikidata.mwapi can break wikidata, while a change to wikidata can't break wikidata.mwapi.
- Position
- Below the diagonal: wikidata uses a module listed above it, which is the healthy direction.
13→10 wikidata uses auth.csrf✕
- Connections
- 1 pair of types, where a type in wikidata uses a type in auth.csrf.
- The types involved
fr.free.nrw.commons.wikidata.WikiBaseClient→fr.free.nrw.commons.auth.csrf.CsrfTokenClient
- Direction
- wikidata uses auth.csrf, so a change to auth.csrf can break wikidata, while a change to wikidata can't break auth.csrf.
- Position
- Below the diagonal: wikidata uses a module listed above it, which is the healthy direction.
13→20 wikidata uses upload part of a loop✕
- Connections
- 3 pairs of types, where a type in wikidata uses a type in upload.
- The types involved
fr.free.nrw.commons.wikidata.WikiBaseClient→fr.free.nrw.commons.upload.WikiBaseInterfacefr.free.nrw.commons.wikidata.WikidataEditService→fr.free.nrw.commons.upload.WikidataItemfr.free.nrw.commons.wikidata.WikidataEditService→fr.free.nrw.commons.upload.WikidataPlace
- Direction
- wikidata uses upload, so a change to upload can break wikidata, while a change to wikidata can't break upload.
- 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→32 wikidata uses contributions part of a loop✕
- Connections
- 1 pair of types, where a type in wikidata uses a type in contributions.
- The types involved
fr.free.nrw.commons.wikidata.WikidataEditService→fr.free.nrw.commons.contributions.Contribution
- Direction
- wikidata uses contributions, so a change to contributions can break wikidata, while a change to wikidata can't break contributions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→7 upload.structure.depictions uses wikidata.model✕
- Connections
- 1 pair of types, where a type in upload.structure.depictions uses a type in wikidata.model.
- The types involved
fr.free.nrw.commons.upload.structure.depictions.DepictedItemKt→fr.free.nrw.commons.wikidata.model.StatementPartial
- Direction
- upload.structure.depictions uses wikidata.model, so a change to wikidata.model can break upload.structure.depictions, while a change to upload.structure.depictions can't break wikidata.model.
- Position
- Below the diagonal: upload.structure.depictions uses a module listed above it, which is the healthy direction.
14→13 upload.structure.depictions uses wikidata✕
- Connections
- 1 pair of types, where a type in upload.structure.depictions uses a type in wikidata.
- The types involved
fr.free.nrw.commons.upload.structure.depictions.DepictedItemKt→fr.free.nrw.commons.wikidata.WikidataProperties
- Direction
- upload.structure.depictions uses wikidata, so a change to wikidata can break upload.structure.depictions, while a change to upload.structure.depictions can't break wikidata.
- Position
- Below the diagonal: upload.structure.depictions uses a module listed above it, which is the healthy direction.
14→15 upload.structure.depictions uses repository part of a loop✕
- Connections
- 1 pair of types, where a type in upload.structure.depictions uses a type in repository.
- The types involved
fr.free.nrw.commons.upload.structure.depictions.DepictModel→fr.free.nrw.commons.repository.UploadRepository
- Direction
- upload.structure.depictions uses repository, so a change to repository can break upload.structure.depictions, while a change to upload.structure.depictions can't break repository.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→20 upload.structure.depictions uses upload part of a loop✕
- Connections
- 1 pair of types, where a type in upload.structure.depictions uses a type in upload.
- The types involved
fr.free.nrw.commons.upload.structure.depictions.DepictedItem→fr.free.nrw.commons.upload.WikidataItem
- Direction
- upload.structure.depictions uses upload, so a change to upload can break upload.structure.depictions, while a change to upload.structure.depictions can't break upload.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→24 upload.structure.depictions uses explore.depictions part of a loop✕
- Connections
- 1 pair of types, where a type in upload.structure.depictions uses a type in explore.depictions.
- The types involved
fr.free.nrw.commons.upload.structure.depictions.DepictModel→fr.free.nrw.commons.explore.depictions.DepictsClient
- Direction
- upload.structure.depictions uses explore.depictions, so a change to explore.depictions can break upload.structure.depictions, while a change to upload.structure.depictions can't break explore.depictions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→35 upload.structure.depictions uses category part of a loop✕
- Connections
- 1 pair of types, where a type in upload.structure.depictions uses a type in category.
- The types involved
fr.free.nrw.commons.upload.structure.depictions.DepictedItem→fr.free.nrw.commons.category.CategoryItem
- Direction
- upload.structure.depictions uses category, so a change to category can break upload.structure.depictions, while a change to upload.structure.depictions can't break category.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→2 repository uses filepicker✕
- Connections
- 1 pair of types, where a type in repository uses a type in filepicker.
- The types involved
fr.free.nrw.commons.repository.UploadRepository→fr.free.nrw.commons.filepicker.UploadableFile
- Direction
- repository uses filepicker, so a change to filepicker can break repository, while a change to repository can't break filepicker.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
15→4 repository uses location✕
- Connections
- 3 pairs of types, where a type in repository uses a type in location.
- The types involved
fr.free.nrw.commons.repository.DefaultUploadQualityOperations→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.repository.UploadQualityOperations→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.repository.UploadRepository→fr.free.nrw.commons.location.LatLng
- Direction
- repository uses location, so a change to location can break repository, while a change to repository can't break location.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
15→14 repository uses upload.structure.depictions✕
- Connections
- 7 pairs of types, where a type in repository uses a type in upload.structure.depictions.
- The types involved
fr.free.nrw.commons.repository.DefaultUploadCategoryOperations→fr.free.nrw.commons.upload.structure.depictions.DepictedItemfr.free.nrw.commons.repository.DefaultUploadDepictionOperations→fr.free.nrw.commons.upload.structure.depictions.DepictModelfr.free.nrw.commons.repository.DefaultUploadDepictionOperations→fr.free.nrw.commons.upload.structure.depictions.DepictedItemfr.free.nrw.commons.repository.UploadCategoryOperations→fr.free.nrw.commons.upload.structure.depictions.DepictedItemfr.free.nrw.commons.repository.UploadDepictionOperations→fr.free.nrw.commons.upload.structure.depictions.DepictedItemfr.free.nrw.commons.repository.UploadRepository→fr.free.nrw.commons.upload.structure.depictions.DepictModelfr.free.nrw.commons.repository.UploadRepository→fr.free.nrw.commons.upload.structure.depictions.DepictedItem
- Direction
- repository uses upload.structure.depictions, so a change to upload.structure.depictions can break repository, while a change to repository can't break upload.structure.depictions.
- Position
- Below the diagonal: repository uses a module listed above it, which is the healthy direction.
15→20 repository uses upload part of a loop✕
- Connections
- 15 pairs of types, where a type in repository uses a type in upload.
- The types involved
fr.free.nrw.commons.repository.DefaultUploadCategoryOperations→fr.free.nrw.commons.upload.UploadModelfr.free.nrw.commons.repository.DefaultUploadDepictionOperations→fr.free.nrw.commons.upload.UploadModelfr.free.nrw.commons.repository.DefaultUploadItemOperations→fr.free.nrw.commons.upload.UploadItemfr.free.nrw.commons.repository.DefaultUploadItemOperations→fr.free.nrw.commons.upload.UploadModelfr.free.nrw.commons.repository.DefaultUploadLicenseOperations→fr.free.nrw.commons.upload.UploadModelfr.free.nrw.commons.repository.DefaultUploadQualityOperations→fr.free.nrw.commons.upload.ImageCoordinatesfr.free.nrw.commons.repository.DefaultUploadQualityOperations→fr.free.nrw.commons.upload.UploadItemfr.free.nrw.commons.repository.DefaultUploadQualityOperations→fr.free.nrw.commons.upload.UploadModelfr.free.nrw.commons.repository.UploadItemOperations→fr.free.nrw.commons.upload.UploadItemfr.free.nrw.commons.repository.UploadQualityOperations→fr.free.nrw.commons.upload.ImageCoordinatesfr.free.nrw.commons.repository.UploadQualityOperations→fr.free.nrw.commons.upload.UploadItemfr.free.nrw.commons.repository.UploadRepository→fr.free.nrw.commons.upload.SimilarImageInterfacefr.free.nrw.commons.repository.UploadRepository→fr.free.nrw.commons.upload.UploadControllerfr.free.nrw.commons.repository.UploadRepository→fr.free.nrw.commons.upload.UploadItemfr.free.nrw.commons.repository.UploadRepository→fr.free.nrw.commons.upload.UploadModel
- Direction
- repository uses upload, so a change to upload can break repository, while a change to repository can't break upload.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→32 repository uses contributions part of a loop✕
- Connections
- 2 pairs of types, where a type in repository uses a type in contributions.
- The types involved
fr.free.nrw.commons.repository.UploadRepository→fr.free.nrw.commons.contributions.Contributionfr.free.nrw.commons.repository.UploadRepository→fr.free.nrw.commons.contributions.ContributionDao
- Direction
- repository uses contributions, so a change to contributions can break repository, while a change to repository can't break contributions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→35 repository uses category part of a loop✕
- Connections
- 4 pairs of types, where a type in repository uses a type in category.
- The types involved
fr.free.nrw.commons.repository.DefaultUploadCategoryOperations→fr.free.nrw.commons.category.CategoriesModelfr.free.nrw.commons.repository.DefaultUploadCategoryOperations→fr.free.nrw.commons.category.CategoryItemfr.free.nrw.commons.repository.UploadCategoryOperations→fr.free.nrw.commons.category.CategoryItemfr.free.nrw.commons.repository.UploadRepository→fr.free.nrw.commons.category.CategoriesModel
- Direction
- repository uses category, so a change to category can break repository, while a change to repository can't break category.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→40 repository uses fr.free.nrw.commons part of a loop✕
- Connections
- 4 pairs of types, where a type in repository uses a type in fr.free.nrw.commons.
- The types involved
fr.free.nrw.commons.repository.DefaultUploadCategoryOperations→fr.free.nrw.commons.Mediafr.free.nrw.commons.repository.DefaultUploadDepictionOperations→fr.free.nrw.commons.Mediafr.free.nrw.commons.repository.UploadCategoryOperations→fr.free.nrw.commons.Mediafr.free.nrw.commons.repository.UploadDepictionOperations→fr.free.nrw.commons.Media
- Direction
- repository uses fr.free.nrw.commons, so a change to fr.free.nrw.commons can break repository, while a change to repository can't break fr.free.nrw.commons.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→15 upload.categories uses repository✕
- Connections
- 3 pairs of types, where a type in upload.categories uses a type in repository.
- The types involved
fr.free.nrw.commons.upload.categories.CategoriesPresenter→fr.free.nrw.commons.repository.UploadRepositoryfr.free.nrw.commons.upload.categories.CategorySearchResults→fr.free.nrw.commons.repository.UploadRepositoryfr.free.nrw.commons.upload.categories.CategorySelection→fr.free.nrw.commons.repository.UploadRepository
- Direction
- upload.categories uses repository, so a change to repository can break upload.categories, while a change to upload.categories can't break repository.
- Position
- Below the diagonal: upload.categories uses a module listed above it, which is the healthy direction.
16→20 upload.categories uses upload part of a loop✕
- Connections
- 1 pair of types, where a type in upload.categories uses a type in upload.
- The types involved
fr.free.nrw.commons.upload.categories.UploadCategoriesFragment→fr.free.nrw.commons.upload.UploadBaseFragment
- Direction
- upload.categories uses upload, so a change to upload can break upload.categories, while a change to upload.categories can't break upload.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→35 upload.categories uses category part of a loop✕
- Connections
- 7 pairs of types, where a type in upload.categories uses a type in category.
- The types involved
fr.free.nrw.commons.upload.categories.CategoriesPresenter→fr.free.nrw.commons.category.CategoryEditHelperfr.free.nrw.commons.upload.categories.CategoriesPresenter→fr.free.nrw.commons.category.CategoryItemfr.free.nrw.commons.upload.categories.CategorySearchResults→fr.free.nrw.commons.category.CategoryItemfr.free.nrw.commons.upload.categories.CategorySearchView→fr.free.nrw.commons.category.CategoryItemfr.free.nrw.commons.upload.categories.CategorySelection→fr.free.nrw.commons.category.CategoryItemfr.free.nrw.commons.upload.categories.UploadCategoryAdapter→fr.free.nrw.commons.category.CategoryItemfr.free.nrw.commons.upload.categories.UploadCategoryAdapterDelegatesKt→fr.free.nrw.commons.category.CategoryItem
- Direction
- upload.categories uses category, so a change to category can break upload.categories, while a change to upload.categories can't break category.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→39 upload.categories uses auth part of a loop✕
- Connections
- 1 pair of types, where a type in upload.categories uses a type in auth.
- The types involved
fr.free.nrw.commons.upload.categories.UploadCategoriesFragment→fr.free.nrw.commons.auth.SessionManager
- Direction
- upload.categories uses auth, so a change to auth can break upload.categories, while a change to upload.categories can't break auth.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→40 upload.categories uses fr.free.nrw.commons part of a loop✕
- Connections
- 4 pairs of types, where a type in upload.categories uses a type in fr.free.nrw.commons.
- The types involved
fr.free.nrw.commons.upload.categories.CategoriesPresenter→fr.free.nrw.commons.Mediafr.free.nrw.commons.upload.categories.CategorySearchResults→fr.free.nrw.commons.Mediafr.free.nrw.commons.upload.categories.CategorySelection→fr.free.nrw.commons.Mediafr.free.nrw.commons.upload.categories.UploadCategoriesFragment→fr.free.nrw.commons.Media
- Direction
- upload.categories uses fr.free.nrw.commons, so a change to fr.free.nrw.commons can break upload.categories, while a change to upload.categories can't break fr.free.nrw.commons.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→2 upload.mediaDetails uses filepicker✕
- Connections
- 2 pairs of types, where a type in upload.mediaDetails uses a type in filepicker.
- The types involved
fr.free.nrw.commons.upload.mediaDetails.UploadMediaDetailFragment→fr.free.nrw.commons.filepicker.UploadableFilefr.free.nrw.commons.upload.mediaDetails.UploadMediaPresenter→fr.free.nrw.commons.filepicker.UploadableFile
- Direction
- upload.mediaDetails uses filepicker, so a change to filepicker can break upload.mediaDetails, while a change to upload.mediaDetails can't break filepicker.
- Position
- Below the diagonal: upload.mediaDetails uses a module listed above it, which is the healthy direction.
17→3 upload.mediaDetails uses kvstore✕
- Connections
- 6 pairs of types, where a type in upload.mediaDetails uses a type in kvstore.
- The types involved
fr.free.nrw.commons.upload.mediaDetails.BaseUploadMediaPresenter→fr.free.nrw.commons.kvstore.BasicKvStorefr.free.nrw.commons.upload.mediaDetails.UploadMediaDetailDialogs→fr.free.nrw.commons.kvstore.BasicKvStorefr.free.nrw.commons.upload.mediaDetails.UploadMediaDetailFragment→fr.free.nrw.commons.kvstore.BasicKvStorefr.free.nrw.commons.upload.mediaDetails.UploadMediaDetailFragment→fr.free.nrw.commons.kvstore.JsonKvStorefr.free.nrw.commons.upload.mediaDetails.UploadMediaDetailView→fr.free.nrw.commons.kvstore.BasicKvStorefr.free.nrw.commons.upload.mediaDetails.UploadMediaQualityHelper→fr.free.nrw.commons.kvstore.BasicKvStore
- Direction
- upload.mediaDetails uses kvstore, so a change to kvstore can break upload.mediaDetails, while a change to upload.mediaDetails can't break kvstore.
- Position
- Below the diagonal: upload.mediaDetails uses a module listed above it, which is the healthy direction.
17→4 upload.mediaDetails uses location✕
- Connections
- 4 pairs of types, where a type in upload.mediaDetails uses a type in location.
- The types involved
fr.free.nrw.commons.upload.mediaDetails.BaseUploadMediaPresenter→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.upload.mediaDetails.UploadMediaDetailFragment→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.upload.mediaDetails.UploadMediaPresenter→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.upload.mediaDetails.UploadMediaQualityHelper→fr.free.nrw.commons.location.LatLng
- Direction
- upload.mediaDetails uses location, so a change to location can break upload.mediaDetails, while a change to upload.mediaDetails can't break location.
- Position
- Below the diagonal: upload.mediaDetails uses a module listed above it, which is the healthy direction.
17→15 upload.mediaDetails uses repository✕
- Connections
- 3 pairs of types, where a type in upload.mediaDetails uses a type in repository.
- The types involved
fr.free.nrw.commons.upload.mediaDetails.BaseUploadMediaPresenter→fr.free.nrw.commons.repository.UploadRepositoryfr.free.nrw.commons.upload.mediaDetails.UploadMediaPresenter→fr.free.nrw.commons.repository.UploadRepositoryfr.free.nrw.commons.upload.mediaDetails.UploadMediaQualityHelper→fr.free.nrw.commons.repository.UploadRepository
- Direction
- upload.mediaDetails uses repository, so a change to repository can break upload.mediaDetails, while a change to upload.mediaDetails can't break repository.
- Position
- Below the diagonal: upload.mediaDetails uses a module listed above it, which is the healthy direction.
17→20 upload.mediaDetails uses upload part of a loop✕
- Connections
- 19 pairs of types, where a type in upload.mediaDetails uses a type in upload.
- The types involved
fr.free.nrw.commons.upload.mediaDetails.BaseUploadMediaPresenter→fr.free.nrw.commons.upload.ImageCoordinatesfr.free.nrw.commons.upload.mediaDetails.BaseUploadMediaPresenter→fr.free.nrw.commons.upload.SimilarImageInterfacefr.free.nrw.commons.upload.mediaDetails.BaseUploadMediaPresenter→fr.free.nrw.commons.upload.UploadItemfr.free.nrw.commons.upload.mediaDetails.UploadMediaDetailDialogs→fr.free.nrw.commons.upload.ImageCoordinatesfr.free.nrw.commons.upload.mediaDetails.UploadMediaDetailDialogs→fr.free.nrw.commons.upload.UploadItemfr.free.nrw.commons.upload.mediaDetails.UploadMediaDetailDialogs→fr.free.nrw.commons.upload.UploadMediaDetailAdapterfr.free.nrw.commons.upload.mediaDetails.UploadMediaDetailFragment→fr.free.nrw.commons.upload.UploadBaseFragmentfr.free.nrw.commons.upload.mediaDetails.UploadMediaDetailFragment→fr.free.nrw.commons.upload.UploadMediaDetailAdapterfr.free.nrw.commons.upload.mediaDetails.UploadMediaDetailView→fr.free.nrw.commons.upload.UploadItemfr.free.nrw.commons.upload.mediaDetails.UploadMediaDetailView→fr.free.nrw.commons.upload.UploadMediaDetailfr.free.nrw.commons.upload.mediaDetails.UploadMediaDetailView→fr.free.nrw.commons.upload.UploadMediaDetailAdapterfr.free.nrw.commons.upload.mediaDetails.UploadMediaLocationController→fr.free.nrw.commons.upload.UploadItemfr.free.nrw.commons.upload.mediaDetails.UploadMediaMetadataController→fr.free.nrw.commons.upload.UploadItemfr.free.nrw.commons.upload.mediaDetails.UploadMediaMetadataController→fr.free.nrw.commons.upload.UploadMediaDetailfr.free.nrw.commons.upload.mediaDetails.UploadMediaMetadataController→fr.free.nrw.commons.upload.UploadMediaDetailAdapterfr.free.nrw.commons.upload.mediaDetails.UploadMediaPresenter→fr.free.nrw.commons.upload.ImageCoordinatesfr.free.nrw.commons.upload.mediaDetails.UploadMediaPresenter→fr.free.nrw.commons.upload.UploadItemfr.free.nrw.commons.upload.mediaDetails.UploadMediaPresenter→fr.free.nrw.commons.upload.UploadMediaDetailfr.free.nrw.commons.upload.mediaDetails.UploadMediaQualityHelper→fr.free.nrw.commons.upload.UploadItem
- Direction
- upload.mediaDetails uses upload, so a change to upload can break upload.mediaDetails, while a change to upload.mediaDetails can't break upload.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→9 notification uses wikidata.mwapi✕
- Connections
- 1 pair of types, where a type in notification uses a type in wikidata.mwapi.
- The types involved
fr.free.nrw.commons.notification.NotificationInterface→fr.free.nrw.commons.wikidata.mwapi.MwQueryResponse
- Direction
- notification uses wikidata.mwapi, so a change to wikidata.mwapi can break notification, while a change to notification can't break wikidata.mwapi.
- Position
- Below the diagonal: notification uses a module listed above it, which is the healthy direction.
18→10 notification uses auth.csrf✕
- Connections
- 1 pair of types, where a type in notification uses a type in auth.csrf.
- The types involved
fr.free.nrw.commons.notification.NotificationClient→fr.free.nrw.commons.auth.csrf.CsrfTokenClient
- Direction
- notification uses auth.csrf, so a change to auth.csrf can break notification, while a change to notification can't break auth.csrf.
- Position
- Below the diagonal: notification uses a module listed above it, which is the healthy direction.
18→16 notification uses upload.categories✕
- Connections
- 1 pair of types, where a type in notification uses a type in upload.categories.
- The types involved
fr.free.nrw.commons.notification.NotificationAdapter→fr.free.nrw.commons.upload.categories.BaseDelegateAdapter
- Direction
- notification uses upload.categories, so a change to upload.categories can break notification, while a change to notification can't break upload.categories.
- Position
- Below the diagonal: notification uses a module listed above it, which is the healthy direction.
18→22 notification uses theme part of a loop✕
- Connections
- 1 pair of types, where a type in notification uses a type in theme.
- The types involved
fr.free.nrw.commons.notification.NotificationActivity→fr.free.nrw.commons.theme.BaseActivity
- Direction
- notification uses theme, so a change to theme can break notification, while a change to notification can't break theme.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→39 notification uses auth part of a loop✕
- Connections
- 1 pair of types, where a type in notification uses a type in auth.
- The types involved
fr.free.nrw.commons.notification.NotificationActivity→fr.free.nrw.commons.auth.SessionManager
- Direction
- notification uses auth, so a change to auth can break notification, while a change to notification can't break auth.
- 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.
19→3 upload.depicts uses kvstore✕
- Connections
- 1 pair of types, where a type in upload.depicts uses a type in kvstore.
- The types involved
fr.free.nrw.commons.upload.depicts.DepictsFragment→fr.free.nrw.commons.kvstore.JsonKvStore
- Direction
- upload.depicts uses kvstore, so a change to kvstore can break upload.depicts, while a change to upload.depicts can't break kvstore.
- Position
- Below the diagonal: upload.depicts uses a module listed above it, which is the healthy direction.
19→4 upload.depicts uses location✕
- Connections
- 2 pairs of types, where a type in upload.depicts uses a type in location.
- The types involved
fr.free.nrw.commons.upload.depicts.DepictsFragment→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.upload.depicts.DepictsFragment→fr.free.nrw.commons.location.LocationServiceManager
- Direction
- upload.depicts uses location, so a change to location can break upload.depicts, while a change to upload.depicts can't break location.
- Position
- Below the diagonal: upload.depicts uses a module listed above it, which is the healthy direction.
19→7 upload.depicts uses wikidata.model✕
- Connections
- 3 pairs of types, where a type in upload.depicts uses a type in wikidata.model.
- The types involved
fr.free.nrw.commons.upload.depicts.Claims→fr.free.nrw.commons.wikidata.model.StatementPartialfr.free.nrw.commons.upload.depicts.DepictsInterface→fr.free.nrw.commons.wikidata.model.DepictSearchResponsefr.free.nrw.commons.upload.depicts.DepictsInterface→fr.free.nrw.commons.wikidata.model.Entities
- Direction
- upload.depicts uses wikidata.model, so a change to wikidata.model can break upload.depicts, while a change to upload.depicts can't break wikidata.model.
- Position
- Below the diagonal: upload.depicts uses a module listed above it, which is the healthy direction.
19→9 upload.depicts uses wikidata.mwapi✕
- Connections
- 1 pair of types, where a type in upload.depicts uses a type in wikidata.mwapi.
- The types involved
fr.free.nrw.commons.upload.depicts.Claims→fr.free.nrw.commons.wikidata.mwapi.MwResponse
- Direction
- upload.depicts uses wikidata.mwapi, so a change to wikidata.mwapi can break upload.depicts, while a change to upload.depicts can't break wikidata.mwapi.
- Position
- Below the diagonal: upload.depicts uses a module listed above it, which is the healthy direction.
19→13 upload.depicts uses wikidata✕
- Connections
- 1 pair of types, where a type in upload.depicts uses a type in wikidata.
- The types involved
fr.free.nrw.commons.upload.depicts.DepictEditHelper→fr.free.nrw.commons.wikidata.WikidataEditService
- Direction
- upload.depicts uses wikidata, so a change to wikidata can break upload.depicts, while a change to upload.depicts can't break wikidata.
- Position
- Below the diagonal: upload.depicts uses a module listed above it, which is the healthy direction.
19→14 upload.depicts uses upload.structure.depictions✕
- Connections
- 6 pairs of types, where a type in upload.depicts uses a type in upload.structure.depictions.
- The types involved
fr.free.nrw.commons.upload.depicts.Depicts→fr.free.nrw.commons.upload.structure.depictions.DepictedItemfr.free.nrw.commons.upload.depicts.DepictsDao→fr.free.nrw.commons.upload.structure.depictions.DepictedItemfr.free.nrw.commons.upload.depicts.DepictsFragment→fr.free.nrw.commons.upload.structure.depictions.DepictedItemfr.free.nrw.commons.upload.depicts.DepictsPresenter→fr.free.nrw.commons.upload.structure.depictions.DepictedItemfr.free.nrw.commons.upload.depicts.UploadDepictsAdapter→fr.free.nrw.commons.upload.structure.depictions.DepictedItemfr.free.nrw.commons.upload.depicts.UploadDepictsAdapterDelegatesKt→fr.free.nrw.commons.upload.structure.depictions.DepictedItem
- Direction
- upload.depicts uses upload.structure.depictions, so a change to upload.structure.depictions can break upload.depicts, while a change to upload.depicts can't break upload.structure.depictions.
- Position
- Below the diagonal: upload.depicts uses a module listed above it, which is the healthy direction.
19→15 upload.depicts uses repository✕
- Connections
- 1 pair of types, where a type in upload.depicts uses a type in repository.
- The types involved
fr.free.nrw.commons.upload.depicts.DepictsPresenter→fr.free.nrw.commons.repository.UploadRepository
- Direction
- upload.depicts uses repository, so a change to repository can break upload.depicts, while a change to upload.depicts can't break repository.
- Position
- Below the diagonal: upload.depicts uses a module listed above it, which is the healthy direction.
19→16 upload.depicts uses upload.categories✕
- Connections
- 1 pair of types, where a type in upload.depicts uses a type in upload.categories.
- The types involved
fr.free.nrw.commons.upload.depicts.UploadDepictsAdapter→fr.free.nrw.commons.upload.categories.BaseDelegateAdapter
- Direction
- upload.depicts uses upload.categories, so a change to upload.categories can break upload.depicts, while a change to upload.depicts can't break upload.categories.
- Position
- Below the diagonal: upload.depicts uses a module listed above it, which is the healthy direction.
19→18 upload.depicts uses notification✕
- Connections
- 1 pair of types, where a type in upload.depicts uses a type in notification.
- The types involved
fr.free.nrw.commons.upload.depicts.DepictEditHelper→fr.free.nrw.commons.notification.NotificationHelper
- Direction
- upload.depicts uses notification, so a change to notification can break upload.depicts, while a change to upload.depicts can't break notification.
- Position
- Below the diagonal: upload.depicts uses a module listed above it, which is the healthy direction.
19→20 upload.depicts uses upload part of a loop✕
- Connections
- 2 pairs of types, where a type in upload.depicts uses a type in upload.
- The types involved
fr.free.nrw.commons.upload.depicts.DepictsFragment→fr.free.nrw.commons.upload.UploadBaseFragmentfr.free.nrw.commons.upload.depicts.DepictsPresenter→fr.free.nrw.commons.upload.UploadItem
- Direction
- upload.depicts uses upload, so a change to upload can break upload.depicts, while a change to upload.depicts can't break upload.
- 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.
19→21 upload.depicts uses utils part of a loop✕
- Connections
- 1 pair of types, where a type in upload.depicts uses a type in utils.
- The types involved
fr.free.nrw.commons.upload.depicts.DepictEditHelper→fr.free.nrw.commons.utils.ViewUtilWrapper
- Direction
- upload.depicts uses utils, so a change to utils can break upload.depicts, while a change to upload.depicts can't break utils.
- 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.
19→22 upload.depicts uses theme part of a loop✕
- Connections
- 1 pair of types, where a type in upload.depicts uses a type in theme.
- The types involved
fr.free.nrw.commons.upload.depicts.DepictsPickerActivity→fr.free.nrw.commons.theme.BaseActivity
- Direction
- upload.depicts uses theme, so a change to theme can break upload.depicts, while a change to upload.depicts can't break theme.
- 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.
19→39 upload.depicts uses auth part of a loop✕
- Connections
- 1 pair of types, where a type in upload.depicts uses a type in auth.
- The types involved
fr.free.nrw.commons.upload.depicts.DepictsFragment→fr.free.nrw.commons.auth.SessionManager
- Direction
- upload.depicts uses auth, so a change to auth can break upload.depicts, while a change to upload.depicts can't break auth.
- 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.
19→40 upload.depicts uses fr.free.nrw.commons part of a loop✕
- Connections
- 3 pairs of types, where a type in upload.depicts uses a type in fr.free.nrw.commons.
- The types involved
fr.free.nrw.commons.upload.depicts.DepictEditHelper→fr.free.nrw.commons.Mediafr.free.nrw.commons.upload.depicts.DepictsFragment→fr.free.nrw.commons.Mediafr.free.nrw.commons.upload.depicts.DepictsPresenter→fr.free.nrw.commons.Media
- Direction
- upload.depicts uses fr.free.nrw.commons, so a change to fr.free.nrw.commons can break upload.depicts, while a change to upload.depicts can't break fr.free.nrw.commons.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→2 upload uses filepicker✕
- Connections
- 5 pairs of types, where a type in upload uses a type in filepicker.
- The types involved
fr.free.nrw.commons.upload.ThumbnailsAdapter→fr.free.nrw.commons.filepicker.UploadableFilefr.free.nrw.commons.upload.UploadActivityView→fr.free.nrw.commons.filepicker.UploadableFilefr.free.nrw.commons.upload.UploadInputController→fr.free.nrw.commons.filepicker.UploadableFilefr.free.nrw.commons.upload.UploadModel→fr.free.nrw.commons.filepicker.UploadableFilefr.free.nrw.commons.upload.UploadStepSetup→fr.free.nrw.commons.filepicker.UploadableFile
- Direction
- upload uses filepicker, so a change to filepicker can break upload, while a change to upload can't break filepicker.
- Position
- Below the diagonal: upload uses a module listed above it, which is the healthy direction.
20→3 upload uses kvstore✕
- Connections
- 8 pairs of types, where a type in upload uses a type in kvstore.
- The types involved
fr.free.nrw.commons.upload.FileProcessor→fr.free.nrw.commons.kvstore.JsonKvStorefr.free.nrw.commons.upload.UploadActivity→fr.free.nrw.commons.kvstore.BasicKvStorefr.free.nrw.commons.upload.UploadActivity→fr.free.nrw.commons.kvstore.JsonKvStorefr.free.nrw.commons.upload.UploadActivityView→fr.free.nrw.commons.kvstore.BasicKvStorefr.free.nrw.commons.upload.UploadController→fr.free.nrw.commons.kvstore.JsonKvStorefr.free.nrw.commons.upload.UploadModel→fr.free.nrw.commons.kvstore.JsonKvStorefr.free.nrw.commons.upload.UploadPresenter→fr.free.nrw.commons.kvstore.BasicKvStorefr.free.nrw.commons.upload.UploadPresenter→fr.free.nrw.commons.kvstore.JsonKvStore
- Direction
- upload uses kvstore, so a change to kvstore can break upload, while a change to upload can't break kvstore.
- Position
- Below the diagonal: upload uses a module listed above it, which is the healthy direction.
20→4 upload uses location✕
- Connections
- 10 pairs of types, where a type in upload uses a type in location.
- The types involved
fr.free.nrw.commons.upload.FileProcessor→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.upload.FileUtils→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.upload.FileUtilsWrapper→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.upload.ImageCoordinates→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.upload.ImageProcessingService→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.upload.UploadActivity→fr.free.nrw.commons.location.LocationServiceManagerfr.free.nrw.commons.upload.UploadActivityView→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.upload.UploadInputController→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.upload.UploadModel→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.upload.WikidataPlace→fr.free.nrw.commons.location.LatLng
- Direction
- upload uses location, so a change to location can break upload, while a change to upload can't break location.
- Position
- Below the diagonal: upload uses a module listed above it, which is the healthy direction.
20→9 upload uses wikidata.mwapi✕
- Connections
- 2 pairs of types, where a type in upload uses a type in wikidata.mwapi.
- The types involved
fr.free.nrw.commons.upload.WikiBaseInterface→fr.free.nrw.commons.wikidata.mwapi.MwPostResponsefr.free.nrw.commons.upload.WikiBaseInterface→fr.free.nrw.commons.wikidata.mwapi.MwQueryResponse
- Direction
- upload uses wikidata.mwapi, so a change to wikidata.mwapi can break upload, while a change to upload can't break wikidata.mwapi.
- Position
- Below the diagonal: upload uses a module listed above it, which is the healthy direction.
20→10 upload uses auth.csrf✕
- Connections
- 1 pair of types, where a type in upload uses a type in auth.csrf.
- The types involved
fr.free.nrw.commons.upload.UploadClient→fr.free.nrw.commons.auth.csrf.CsrfTokenClient
- Direction
- upload uses auth.csrf, so a change to auth.csrf can break upload, while a change to upload can't break auth.csrf.
- Position
- Below the diagonal: upload uses a module listed above it, which is the healthy direction.
20→14 upload uses upload.structure.depictions✕
- Connections
- 2 pairs of types, where a type in upload uses a type in upload.structure.depictions.
- The types involved
fr.free.nrw.commons.upload.FileProcessorDependencies→fr.free.nrw.commons.upload.structure.depictions.DepictModelfr.free.nrw.commons.upload.UploadModel→fr.free.nrw.commons.upload.structure.depictions.DepictedItem
- Direction
- upload uses upload.structure.depictions, so a change to upload.structure.depictions can break upload, while a change to upload can't break upload.structure.depictions.
- Position
- Below the diagonal: upload uses a module listed above it, which is the healthy direction.
20→15 upload uses repository✕
- Connections
- 2 pairs of types, where a type in upload uses a type in repository.
- The types involved
fr.free.nrw.commons.upload.PendingUploadsPresenter→fr.free.nrw.commons.repository.UploadRepositoryfr.free.nrw.commons.upload.UploadPresenter→fr.free.nrw.commons.repository.UploadRepository
- Direction
- upload uses repository, so a change to repository can break upload, while a change to upload can't break repository.
- Position
- Below the diagonal: upload uses a module listed above it, which is the healthy direction.
20→16 upload uses upload.categories✕
- Connections
- 2 pairs of types, where a type in upload uses a type in upload.categories.
- The types involved
fr.free.nrw.commons.upload.UploadActivityView→fr.free.nrw.commons.upload.categories.UploadCategoriesFragmentfr.free.nrw.commons.upload.UploadModule→fr.free.nrw.commons.upload.categories.CategoriesPresenter
- Direction
- upload uses upload.categories, so a change to upload.categories can break upload, while a change to upload can't break upload.categories.
- Position
- Below the diagonal: upload uses a module listed above it, which is the healthy direction.
20→17 upload uses upload.mediaDetails✕
- Connections
- 1 pair of types, where a type in upload uses a type in upload.mediaDetails.
- The types involved
fr.free.nrw.commons.upload.UploadModule→fr.free.nrw.commons.upload.mediaDetails.UploadMediaPresenter
- Direction
- upload uses upload.mediaDetails, so a change to upload.mediaDetails can break upload, while a change to upload can't break upload.mediaDetails.
- Position
- Below the diagonal: upload uses a module listed above it, which is the healthy direction.
20→19 upload uses upload.depicts✕
- Connections
- 3 pairs of types, where a type in upload uses a type in upload.depicts.
- The types involved
fr.free.nrw.commons.upload.UploadActivityView→fr.free.nrw.commons.upload.depicts.DepictsFragmentfr.free.nrw.commons.upload.UploadModule→fr.free.nrw.commons.upload.depicts.DepictsPresenterfr.free.nrw.commons.upload.WikiBaseInterface→fr.free.nrw.commons.upload.depicts.Claims
- Direction
- upload uses upload.depicts, so a change to upload.depicts can break upload, while a change to upload can't break upload.depicts.
- Position
- Below the diagonal: upload uses a module listed above it, which is the healthy direction.
20→21 upload uses utils part of a loop✕
- Connections
- 2 pairs of types, where a type in upload uses a type in utils.
- The types involved
fr.free.nrw.commons.upload.ImageProcessingService→fr.free.nrw.commons.utils.ImageUtilsWrapperfr.free.nrw.commons.upload.UploadClient→fr.free.nrw.commons.utils.TimeProvider
- Direction
- upload uses utils, so a change to utils can break upload, while a change to upload can't break utils.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→22 upload uses theme part of a loop✕
- Connections
- 2 pairs of types, where a type in upload uses a type in theme.
- The types involved
fr.free.nrw.commons.upload.UploadActivity→fr.free.nrw.commons.theme.BaseActivityfr.free.nrw.commons.upload.UploadProgressActivity→fr.free.nrw.commons.theme.BaseActivity
- Direction
- upload uses theme, so a change to theme can break upload, while a change to upload can't break theme.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→26 upload uses mwapi part of a loop✕
- Connections
- 3 pairs of types, where a type in upload uses a type in mwapi.
- The types involved
fr.free.nrw.commons.upload.FileProcessorDependencies→fr.free.nrw.commons.mwapi.CategoryApifr.free.nrw.commons.upload.FileProcessorDependencies→fr.free.nrw.commons.mwapi.OkHttpJsonApiClientfr.free.nrw.commons.upload.UploadActivity→fr.free.nrw.commons.mwapi.UserClient
- Direction
- upload uses mwapi, so a change to mwapi can break upload, while a change to upload can't break mwapi.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→32 upload uses contributions part of a loop✕
- Connections
- 17 pairs of types, where a type in upload uses a type in contributions.
- The types involved
fr.free.nrw.commons.upload.FailedUploadsFragment→fr.free.nrw.commons.contributions.Contributionfr.free.nrw.commons.upload.PageContentsCreator→fr.free.nrw.commons.contributions.Contributionfr.free.nrw.commons.upload.PendingUploadsFragment→fr.free.nrw.commons.contributions.Contributionfr.free.nrw.commons.upload.PendingUploadsPresenter→fr.free.nrw.commons.contributions.Contributionfr.free.nrw.commons.upload.PendingUploadsPresenter→fr.free.nrw.commons.contributions.ContributionBoundaryCallbackfr.free.nrw.commons.upload.PendingUploadsPresenter→fr.free.nrw.commons.contributions.ContributionsRemoteDataSourcefr.free.nrw.commons.upload.PendingUploadsPresenter→fr.free.nrw.commons.contributions.ContributionsRepositoryfr.free.nrw.commons.upload.UploadActivity→fr.free.nrw.commons.contributions.ContributionControllerfr.free.nrw.commons.upload.UploadClient→fr.free.nrw.commons.contributions.ChunkInfofr.free.nrw.commons.upload.UploadClient→fr.free.nrw.commons.contributions.Contributionfr.free.nrw.commons.upload.UploadClient→fr.free.nrw.commons.contributions.ContributionDaofr.free.nrw.commons.upload.UploadClientKt→fr.free.nrw.commons.contributions.ChunkInfofr.free.nrw.commons.upload.UploadClientKt→fr.free.nrw.commons.contributions.Contributionfr.free.nrw.commons.upload.UploadClientKt→fr.free.nrw.commons.contributions.ContributionDaofr.free.nrw.commons.upload.UploadController→fr.free.nrw.commons.contributions.Contributionfr.free.nrw.commons.upload.UploadModel→fr.free.nrw.commons.contributions.Contributionfr.free.nrw.commons.upload.UploadProgressActivity→fr.free.nrw.commons.contributions.ContributionDao
- Direction
- upload uses contributions, so a change to contributions can break upload, while a change to upload can't break contributions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→34 upload uses media part of a loop✕
- Connections
- 2 pairs of types, where a type in upload uses a type in media.
- The types involved
fr.free.nrw.commons.upload.FailedUploadsFragment→fr.free.nrw.commons.media.MediaClientfr.free.nrw.commons.upload.ImageProcessingService→fr.free.nrw.commons.media.MediaClient
- Direction
- upload uses media, so a change to media can break upload, while a change to upload can't break media.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→35 upload uses category part of a loop✕
- Connections
- 1 pair of types, where a type in upload uses a type in category.
- The types involved
fr.free.nrw.commons.upload.GpsCategoryModel→fr.free.nrw.commons.category.CategoryItem
- Direction
- upload uses category, so a change to category can break upload, while a change to upload can't break category.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→38 upload uses di part of a loop✕
- Connections
- 3 pairs of types, where a type in upload uses a type in di.
- The types involved
fr.free.nrw.commons.upload.FailedUploadsFragment→fr.free.nrw.commons.di.CommonsDaggerSupportFragmentfr.free.nrw.commons.upload.PendingUploadsFragment→fr.free.nrw.commons.di.CommonsDaggerSupportFragmentfr.free.nrw.commons.upload.UploadBaseFragment→fr.free.nrw.commons.di.CommonsDaggerSupportFragment
- Direction
- upload uses di, so a change to di can break upload, while a change to upload can't break di.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→39 upload uses auth part of a loop✕
- Connections
- 4 pairs of types, where a type in upload uses a type in auth.
- The types involved
fr.free.nrw.commons.upload.FailedUploadsFragment→fr.free.nrw.commons.auth.SessionManagerfr.free.nrw.commons.upload.UploadActivity→fr.free.nrw.commons.auth.SessionManagerfr.free.nrw.commons.upload.UploadController→fr.free.nrw.commons.auth.SessionManagerfr.free.nrw.commons.upload.UploadModel→fr.free.nrw.commons.auth.SessionManager
- Direction
- upload uses auth, so a change to auth can break upload, while a change to upload can't break auth.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→40 upload uses fr.free.nrw.commons part of a loop✕
- Connections
- 2 pairs of types, where a type in upload uses a type in fr.free.nrw.commons.
- The types involved
fr.free.nrw.commons.upload.UploadModel→fr.free.nrw.commons.Mediafr.free.nrw.commons.upload.UploadProgressActivity→fr.free.nrw.commons.ViewPagerAdapter
- Direction
- upload uses fr.free.nrw.commons, so a change to fr.free.nrw.commons can break upload, while a change to upload can't break fr.free.nrw.commons.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→1 utils uses customselector.model✕
- Connections
- 1 pair of types, where a type in utils uses a type in customselector.model.
- The types involved
fr.free.nrw.commons.utils.CustomSelectorUtils→fr.free.nrw.commons.customselector.model.Image
- Direction
- utils uses customselector.model, so a change to customselector.model can break utils, while a change to utils can't break customselector.model.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
21→3 utils uses kvstore✕
- Connections
- 1 pair of types, where a type in utils uses a type in kvstore.
- The types involved
fr.free.nrw.commons.utils.SystemThemeUtils→fr.free.nrw.commons.kvstore.JsonKvStore
- Direction
- utils uses kvstore, so a change to kvstore can break utils, while a change to utils can't break kvstore.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
21→4 utils uses location✕
- Connections
- 9 pairs of types, where a type in utils uses a type in location.
- The types involved
fr.free.nrw.commons.utils.GeoCoordinatesKt→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.utils.ImageUtils→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.utils.ImageUtilsWrapper→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.utils.LengthUtils→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.utils.LocationUtils→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.utils.MapUtils→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.utils.MapUtils→fr.free.nrw.commons.location.LocationServiceManagerfr.free.nrw.commons.utils.MapUtils→fr.free.nrw.commons.location.LocationUpdateListenerfr.free.nrw.commons.utils.PlaceUtils→fr.free.nrw.commons.location.LatLng
- Direction
- utils uses location, so a change to location can break utils, while a change to utils can't break location.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
21→20 utils uses upload✕
- Connections
- 2 pairs of types, where a type in utils uses a type in upload.
- The types involved
fr.free.nrw.commons.utils.CustomSelectorUtils→fr.free.nrw.commons.upload.FileProcessorfr.free.nrw.commons.utils.CustomSelectorUtils→fr.free.nrw.commons.upload.FileUtilsWrapper
- Direction
- utils uses upload, so a change to upload can break utils, while a change to utils can't break upload.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
21→26 utils uses mwapi part of a loop✕
- Connections
- 1 pair of types, where a type in utils uses a type in mwapi.
- The types involved
fr.free.nrw.commons.utils.ImageUtils→fr.free.nrw.commons.mwapi.OkHttpJsonApiClient
- Direction
- utils uses mwapi, so a change to mwapi can break utils, while a change to utils can't break mwapi.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→34 utils uses media part of a loop✕
- Connections
- 2 pairs of types, where a type in utils uses a type in media.
- The types involved
fr.free.nrw.commons.utils.CustomSelectorUtils→fr.free.nrw.commons.media.MediaClientfr.free.nrw.commons.utils.MediaAttributionUtil→fr.free.nrw.commons.media.IdAndLabels
- Direction
- utils uses media, so a change to media can break utils, while a change to utils can't break media.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→35 utils uses category part of a loop✕
- Connections
- 1 pair of types, where a type in utils uses a type in category.
- The types involved
fr.free.nrw.commons.utils.StringSortingUtils→fr.free.nrw.commons.category.CategoryItem
- Direction
- utils uses category, so a change to category can break utils, while a change to utils can't break category.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→40 utils uses fr.free.nrw.commons part of a loop✕
- Connections
- 3 pairs of types, where a type in utils uses a type in fr.free.nrw.commons.
- The types involved
fr.free.nrw.commons.utils.DownloadUtils→fr.free.nrw.commons.Mediafr.free.nrw.commons.utils.MediaAttributionUtil→fr.free.nrw.commons.Mediafr.free.nrw.commons.utils.PlaceUtils→fr.free.nrw.commons.Media
- Direction
- utils uses fr.free.nrw.commons, so a change to fr.free.nrw.commons can break utils, while a change to utils can't break fr.free.nrw.commons.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→3 theme uses kvstore✕
- Connections
- 1 pair of types, where a type in theme uses a type in kvstore.
- The types involved
fr.free.nrw.commons.theme.BaseActivity→fr.free.nrw.commons.kvstore.JsonKvStore
- Direction
- theme uses kvstore, so a change to kvstore can break theme, while a change to theme can't break kvstore.
- Position
- Below the diagonal: theme uses a module listed above it, which is the healthy direction.
22→21 theme uses utils✕
- Connections
- 1 pair of types, where a type in theme uses a type in utils.
- The types involved
fr.free.nrw.commons.theme.BaseActivity→fr.free.nrw.commons.utils.SystemThemeUtils
- Direction
- theme uses utils, so a change to utils can break theme, while a change to theme can't break utils.
- Position
- Below the diagonal: theme uses a module listed above it, which is the healthy direction.
22→38 theme uses di part of a loop✕
- Connections
- 1 pair of types, where a type in theme uses a type in di.
- The types involved
fr.free.nrw.commons.theme.BaseActivity→fr.free.nrw.commons.di.CommonsDaggerAppCompatActivity
- Direction
- theme uses di, so a change to di can break theme, while a change to theme can't break di.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→12 description uses actions✕
- Connections
- 1 pair of types, where a type in description uses a type in actions.
- The types involved
fr.free.nrw.commons.description.DescriptionEditHelper→fr.free.nrw.commons.actions.PageEditClient
- Direction
- description uses actions, so a change to actions can break description, while a change to description can't break actions.
- Position
- Below the diagonal: description uses a module listed above it, which is the healthy direction.
23→18 description uses notification✕
- Connections
- 1 pair of types, where a type in description uses a type in notification.
- The types involved
fr.free.nrw.commons.description.DescriptionEditHelper→fr.free.nrw.commons.notification.NotificationHelper
- Direction
- description uses notification, so a change to notification can break description, while a change to description can't break notification.
- Position
- Below the diagonal: description uses a module listed above it, which is the healthy direction.
23→20 description uses upload✕
- Connections
- 3 pairs of types, where a type in description uses a type in upload.
- The types involved
fr.free.nrw.commons.description.DescriptionEditActivity→fr.free.nrw.commons.upload.UploadMediaDetailfr.free.nrw.commons.description.DescriptionEditActivity→fr.free.nrw.commons.upload.UploadMediaDetailAdapterfr.free.nrw.commons.description.DescriptionWikiTextKt→fr.free.nrw.commons.upload.UploadMediaDetail
- Direction
- description uses upload, so a change to upload can break description, while a change to description can't break upload.
- Position
- Below the diagonal: description uses a module listed above it, which is the healthy direction.
23→22 description uses theme✕
- Connections
- 1 pair of types, where a type in description uses a type in theme.
- The types involved
fr.free.nrw.commons.description.DescriptionEditActivity→fr.free.nrw.commons.theme.BaseActivity
- Direction
- description uses theme, so a change to theme can break description, while a change to description can't break theme.
- Position
- Below the diagonal: description uses a module listed above it, which is the healthy direction.
23→39 description uses auth part of a loop✕
- Connections
- 1 pair of types, where a type in description uses a type in auth.
- The types involved
fr.free.nrw.commons.description.DescriptionEditActivity→fr.free.nrw.commons.auth.SessionManager
- Direction
- description uses auth, so a change to auth can break description, while a change to description can't break auth.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→40 description uses fr.free.nrw.commons part of a loop✕
- Connections
- 2 pairs of types, where a type in description uses a type in fr.free.nrw.commons.
- The types involved
fr.free.nrw.commons.description.DescriptionEditActivity→fr.free.nrw.commons.Mediafr.free.nrw.commons.description.DescriptionEditHelper→fr.free.nrw.commons.Media
- Direction
- description uses fr.free.nrw.commons, so a change to fr.free.nrw.commons can break description, while a change to description can't break fr.free.nrw.commons.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→7 explore.depictions uses wikidata.model✕
- Connections
- 1 pair of types, where a type in explore.depictions uses a type in wikidata.model.
- The types involved
fr.free.nrw.commons.explore.depictions.DepictsClient→fr.free.nrw.commons.wikidata.model.Entities
- Direction
- explore.depictions uses wikidata.model, so a change to wikidata.model can break explore.depictions, while a change to explore.depictions can't break wikidata.model.
- Position
- Below the diagonal: explore.depictions uses a module listed above it, which is the healthy direction.
24→8 explore.depictions uses explore.paging✕
- Connections
- 1 pair of types, where a type in explore.depictions uses a type in explore.paging.
- The types involved
fr.free.nrw.commons.explore.depictions.PageableDepictionsFragment→fr.free.nrw.commons.explore.paging.BasePagingFragment
- Direction
- explore.depictions uses explore.paging, so a change to explore.paging can break explore.depictions, while a change to explore.depictions can't break explore.paging.
- Position
- Below the diagonal: explore.depictions uses a module listed above it, which is the healthy direction.
24→14 explore.depictions uses upload.structure.depictions✕
- Connections
- 6 pairs of types, where a type in explore.depictions uses a type in upload.structure.depictions.
- The types involved
fr.free.nrw.commons.explore.depictions.DepictedItemViewHolder→fr.free.nrw.commons.upload.structure.depictions.DepictedItemfr.free.nrw.commons.explore.depictions.DepictionAdapter→fr.free.nrw.commons.upload.structure.depictions.DepictedItemfr.free.nrw.commons.explore.depictions.DepictionDiffUtilCallback→fr.free.nrw.commons.upload.structure.depictions.DepictedItemfr.free.nrw.commons.explore.depictions.DepictsClient→fr.free.nrw.commons.upload.structure.depictions.DepictedItemfr.free.nrw.commons.explore.depictions.WikidataItemDetailsActivity→fr.free.nrw.commons.upload.structure.depictions.DepictModelfr.free.nrw.commons.explore.depictions.WikidataItemDetailsActivity→fr.free.nrw.commons.upload.structure.depictions.DepictedItem
- Direction
- explore.depictions uses upload.structure.depictions, so a change to upload.structure.depictions can break explore.depictions, while a change to explore.depictions can't break upload.structure.depictions.
- Position
- Below the diagonal: explore.depictions uses a module listed above it, which is the healthy direction.
24→19 explore.depictions uses upload.depicts✕
- Connections
- 1 pair of types, where a type in explore.depictions uses a type in upload.depicts.
- The types involved
fr.free.nrw.commons.explore.depictions.DepictsClient→fr.free.nrw.commons.upload.depicts.DepictsInterface
- Direction
- explore.depictions uses upload.depicts, so a change to upload.depicts can break explore.depictions, while a change to explore.depictions can't break upload.depicts.
- Position
- Below the diagonal: explore.depictions uses a module listed above it, which is the healthy direction.
24→22 explore.depictions uses theme✕
- Connections
- 1 pair of types, where a type in explore.depictions uses a type in theme.
- The types involved
fr.free.nrw.commons.explore.depictions.WikidataItemDetailsActivity→fr.free.nrw.commons.theme.BaseActivity
- Direction
- explore.depictions uses theme, so a change to theme can break explore.depictions, while a change to explore.depictions can't break theme.
- Position
- Below the diagonal: explore.depictions uses a module listed above it, which is the healthy direction.
24→26 explore.depictions uses mwapi part of a loop✕
- Connections
- 1 pair of types, where a type in explore.depictions uses a type in mwapi.
- The types involved
fr.free.nrw.commons.explore.depictions.DepictsClient→fr.free.nrw.commons.mwapi.SparqlResponse
- Direction
- explore.depictions uses mwapi, so a change to mwapi can break explore.depictions, while a change to explore.depictions can't break mwapi.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→34 explore.depictions uses media part of a loop✕
- Connections
- 2 pairs of types, where a type in explore.depictions uses a type in media.
- The types involved
fr.free.nrw.commons.explore.depictions.WikidataItemDetailsActivity→fr.free.nrw.commons.media.MediaDetailPagerFragmentfr.free.nrw.commons.explore.depictions.WikidataItemDetailsActivity→fr.free.nrw.commons.media.MediaDetailProvider
- Direction
- explore.depictions uses media, so a change to media can break explore.depictions, while a change to explore.depictions can't break media.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→35 explore.depictions uses category part of a loop✕
- Connections
- 1 pair of types, where a type in explore.depictions uses a type in category.
- The types involved
fr.free.nrw.commons.explore.depictions.WikidataItemDetailsActivity→fr.free.nrw.commons.category.CategoryImagesCallback
- Direction
- explore.depictions uses category, so a change to category can break explore.depictions, while a change to explore.depictions can't break category.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→40 explore.depictions uses fr.free.nrw.commons part of a loop✕
- Connections
- 3 pairs of types, where a type in explore.depictions uses a type in fr.free.nrw.commons.
- The types involved
fr.free.nrw.commons.explore.depictions.WikidataItemDetailsActivity→fr.free.nrw.commons.Mediafr.free.nrw.commons.explore.depictions.WikidataItemDetailsActivity→fr.free.nrw.commons.ViewPagerAdapterfr.free.nrw.commons.explore.depictions.WikidataItemDetailsTabs→fr.free.nrw.commons.ViewPagerAdapter
- Direction
- explore.depictions uses fr.free.nrw.commons, so a change to fr.free.nrw.commons can break explore.depictions, while a change to explore.depictions can't break fr.free.nrw.commons.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→9 review uses wikidata.mwapi✕
- Connections
- 2 pairs of types, where a type in review uses a type in wikidata.mwapi.
- The types involved
fr.free.nrw.commons.review.ReviewHelper→fr.free.nrw.commons.wikidata.mwapi.MwQueryPagefr.free.nrw.commons.review.ReviewInterface→fr.free.nrw.commons.wikidata.mwapi.MwQueryResponse
- Direction
- review uses wikidata.mwapi, so a change to wikidata.mwapi can break review, while a change to review can't break wikidata.mwapi.
- Position
- Below the diagonal: review uses a module listed above it, which is the healthy direction.
25→12 review uses actions✕
- Connections
- 2 pairs of types, where a type in review uses a type in actions.
- The types involved
fr.free.nrw.commons.review.ReviewController→fr.free.nrw.commons.actions.PageEditClientfr.free.nrw.commons.review.ReviewController→fr.free.nrw.commons.actions.ThanksClient
- Direction
- review uses actions, so a change to actions can break review, while a change to review can't break actions.
- Position
- Below the diagonal: review uses a module listed above it, which is the healthy direction.
25→22 review uses theme✕
- Connections
- 1 pair of types, where a type in review uses a type in theme.
- The types involved
fr.free.nrw.commons.review.ReviewActivity→fr.free.nrw.commons.theme.BaseActivity
- Direction
- review uses theme, so a change to theme can break review, while a change to review can't break theme.
- Position
- Below the diagonal: review uses a module listed above it, which is the healthy direction.
25→34 review uses media part of a loop✕
- Connections
- 2 pairs of types, where a type in review uses a type in media.
- The types involved
fr.free.nrw.commons.review.ReviewHelper→fr.free.nrw.commons.media.MediaClientfr.free.nrw.commons.review.ReviewScreenUi→fr.free.nrw.commons.media.MediaDetailFragment
- Direction
- review uses media, so a change to media can break review, while a change to review can't break media.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→38 review uses di part of a loop✕
- Connections
- 1 pair of types, where a type in review uses a type in di.
- The types involved
fr.free.nrw.commons.review.ReviewImageFragment→fr.free.nrw.commons.di.CommonsDaggerSupportFragment
- Direction
- review uses di, so a change to di can break review, while a change to review can't break di.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→39 review uses auth part of a loop✕
- Connections
- 2 pairs of types, where a type in review uses a type in auth.
- The types involved
fr.free.nrw.commons.review.ReviewController→fr.free.nrw.commons.auth.SessionManagerfr.free.nrw.commons.review.ReviewImageFragment→fr.free.nrw.commons.auth.SessionManager
- Direction
- review uses auth, so a change to auth can break review, while a change to review can't break auth.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→40 review uses fr.free.nrw.commons part of a loop✕
- Connections
- 4 pairs of types, where a type in review uses a type in fr.free.nrw.commons.
- The types involved
fr.free.nrw.commons.review.ReviewActivity→fr.free.nrw.commons.Mediafr.free.nrw.commons.review.ReviewController→fr.free.nrw.commons.Mediafr.free.nrw.commons.review.ReviewHelper→fr.free.nrw.commons.Mediafr.free.nrw.commons.review.ReviewScreenUi→fr.free.nrw.commons.Media
- Direction
- review uses fr.free.nrw.commons, so a change to fr.free.nrw.commons can break review, while a change to review can't break fr.free.nrw.commons.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→4 mwapi uses location✕
- Connections
- 1 pair of types, where a type in mwapi uses a type in location.
- The types involved
fr.free.nrw.commons.mwapi.OkHttpJsonApiClient→fr.free.nrw.commons.location.LatLng
- Direction
- mwapi uses location, so a change to location can break mwapi, while a change to mwapi can't break location.
- Position
- Below the diagonal: mwapi uses a module listed above it, which is the healthy direction.
26→6 mwapi uses profile.leaderboard✕
- Connections
- 2 pairs of types, where a type in mwapi uses a type in profile.leaderboard.
- The types involved
fr.free.nrw.commons.mwapi.OkHttpJsonApiClient→fr.free.nrw.commons.profile.leaderboard.LeaderboardResponsefr.free.nrw.commons.mwapi.OkHttpJsonApiClient→fr.free.nrw.commons.profile.leaderboard.UpdateAvatarResponse
- Direction
- mwapi uses profile.leaderboard, so a change to profile.leaderboard can break mwapi, while a change to mwapi can't break profile.leaderboard.
- Position
- Below the diagonal: mwapi uses a module listed above it, which is the healthy direction.
26→9 mwapi uses wikidata.mwapi✕
- Connections
- 2 pairs of types, where a type in mwapi uses a type in wikidata.mwapi.
- The types involved
fr.free.nrw.commons.mwapi.UserClient→fr.free.nrw.commons.wikidata.mwapi.MwQueryResponsefr.free.nrw.commons.mwapi.UserInterface→fr.free.nrw.commons.wikidata.mwapi.MwQueryResponse
- Direction
- mwapi uses wikidata.mwapi, so a change to wikidata.mwapi can break mwapi, while a change to mwapi can't break wikidata.mwapi.
- Position
- Below the diagonal: mwapi uses a module listed above it, which is the healthy direction.
26→14 mwapi uses upload.structure.depictions✕
- Connections
- 1 pair of types, where a type in mwapi uses a type in upload.structure.depictions.
- The types involved
fr.free.nrw.commons.mwapi.WikidataQueryClient→fr.free.nrw.commons.upload.structure.depictions.DepictedItem
- Direction
- mwapi uses upload.structure.depictions, so a change to upload.structure.depictions can break mwapi, while a change to mwapi can't break upload.structure.depictions.
- Position
- Below the diagonal: mwapi uses a module listed above it, which is the healthy direction.
26→24 mwapi uses explore.depictions✕
- Connections
- 1 pair of types, where a type in mwapi uses a type in explore.depictions.
- The types involved
fr.free.nrw.commons.mwapi.WikidataQueryClient→fr.free.nrw.commons.explore.depictions.DepictsClient
- Direction
- mwapi uses explore.depictions, so a change to explore.depictions can break mwapi, while a change to mwapi can't break explore.depictions.
- Position
- Below the diagonal: mwapi uses a module listed above it, which is the healthy direction.
26→35 mwapi uses category part of a loop✕
- Connections
- 1 pair of types, where a type in mwapi uses a type in category.
- The types involved
fr.free.nrw.commons.mwapi.CategoryApi→fr.free.nrw.commons.category.CategoryItem
- Direction
- mwapi uses category, so a change to category can break mwapi, while a change to mwapi can't break category.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→3 nearby uses kvstore✕
- Connections
- 1 pair of types, where a type in nearby uses a type in kvstore.
- The types involved
fr.free.nrw.commons.nearby.PlaceTypeLabelsClient→fr.free.nrw.commons.kvstore.JsonKvStore
- Direction
- nearby uses kvstore, so a change to kvstore can break nearby, while a change to nearby can't break kvstore.
- Position
- Below the diagonal: nearby uses a module listed above it, which is the healthy direction.
27→4 nearby uses location✕
- Connections
- 5 pairs of types, where a type in nearby uses a type in location.
- The types involved
fr.free.nrw.commons.nearby.NearbyController→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.nearby.NearbyPlaces→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.nearby.Place→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.nearby.PlacesLocalDataSource→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.nearby.PlacesRepository→fr.free.nrw.commons.location.LatLng
- Direction
- nearby uses location, so a change to location can break nearby, while a change to nearby can't break location.
- Position
- Below the diagonal: nearby uses a module listed above it, which is the healthy direction.
27→12 nearby uses actions✕
- Connections
- 1 pair of types, where a type in nearby uses a type in actions.
- The types involved
fr.free.nrw.commons.nearby.PageEditHelper→fr.free.nrw.commons.actions.PageEditClient
- Direction
- nearby uses actions, so a change to actions can break nearby, while a change to nearby can't break actions.
- Position
- Below the diagonal: nearby uses a module listed above it, which is the healthy direction.
27→18 nearby uses notification✕
- Connections
- 1 pair of types, where a type in nearby uses a type in notification.
- The types involved
fr.free.nrw.commons.nearby.PageEditHelper→fr.free.nrw.commons.notification.NotificationHelper
- Direction
- nearby uses notification, so a change to notification can break nearby, while a change to nearby can't break notification.
- Position
- Below the diagonal: nearby uses a module listed above it, which is the healthy direction.
27→19 nearby uses upload.depicts✕
- Connections
- 1 pair of types, where a type in nearby uses a type in upload.depicts.
- The types involved
fr.free.nrw.commons.nearby.PlaceTypeLabelsClient→fr.free.nrw.commons.upload.depicts.DepictsInterface
- Direction
- nearby uses upload.depicts, so a change to upload.depicts can break nearby, while a change to nearby can't break upload.depicts.
- Position
- Below the diagonal: nearby uses a module listed above it, which is the healthy direction.
27→21 nearby uses utils✕
- Connections
- 2 pairs of types, where a type in nearby uses a type in utils.
- The types involved
fr.free.nrw.commons.nearby.NearbyNotificationCardView→fr.free.nrw.commons.utils.SwipableCardViewfr.free.nrw.commons.nearby.PageEditHelper→fr.free.nrw.commons.utils.ViewUtilWrapper
- Direction
- nearby uses utils, so a change to utils can break nearby, while a change to nearby can't break utils.
- Position
- Below the diagonal: nearby uses a module listed above it, which is the healthy direction.
27→22 nearby uses theme✕
- Connections
- 1 pair of types, where a type in nearby uses a type in theme.
- The types involved
fr.free.nrw.commons.nearby.WikidataFeedback→fr.free.nrw.commons.theme.BaseActivity
- Direction
- nearby uses theme, so a change to theme can break nearby, while a change to nearby can't break theme.
- Position
- Below the diagonal: nearby uses a module listed above it, which is the healthy direction.
27→26 nearby uses mwapi✕
- Connections
- 2 pairs of types, where a type in nearby uses a type in mwapi.
- The types involved
fr.free.nrw.commons.nearby.NearbyPlaces→fr.free.nrw.commons.mwapi.OkHttpJsonApiClientfr.free.nrw.commons.nearby.NearbyPlaces→fr.free.nrw.commons.mwapi.WikidataQueryClient
- Direction
- nearby uses mwapi, so a change to mwapi can break nearby, while a change to nearby can't break mwapi.
- Position
- Below the diagonal: nearby uses a module listed above it, which is the healthy direction.
27→29 nearby uses bookmarks.locations part of a loop✕
- Connections
- 2 pairs of types, where a type in nearby uses a type in bookmarks.locations.
- The types involved
fr.free.nrw.commons.nearby.NearbyUtil→fr.free.nrw.commons.bookmarks.locations.BookmarkLocationsDaofr.free.nrw.commons.nearby.PlaceAdapterDelegateKt→fr.free.nrw.commons.bookmarks.locations.BookmarkLocationsDao
- Direction
- nearby uses bookmarks.locations, so a change to bookmarks.locations can break nearby, while a change to nearby can't break bookmarks.locations.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→40 nearby uses fr.free.nrw.commons part of a loop✕
- Connections
- 2 pairs of types, where a type in nearby uses a type in fr.free.nrw.commons.
- The types involved
fr.free.nrw.commons.nearby.NearbyController→fr.free.nrw.commons.BaseMarkerfr.free.nrw.commons.nearby.NearbyController→fr.free.nrw.commons.MapController
- Direction
- nearby uses fr.free.nrw.commons, so a change to fr.free.nrw.commons can break nearby, while a change to nearby can't break fr.free.nrw.commons.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→3 nearby.fragments uses kvstore✕
- Connections
- 2 pairs of types, where a type in nearby.fragments uses a type in kvstore.
- The types involved
fr.free.nrw.commons.nearby.fragments.CommonPlaceClickActions→fr.free.nrw.commons.kvstore.JsonKvStorefr.free.nrw.commons.nearby.fragments.NearbyParentFragment→fr.free.nrw.commons.kvstore.JsonKvStore
- Direction
- nearby.fragments uses kvstore, so a change to kvstore can break nearby.fragments, while a change to nearby.fragments can't break kvstore.
- Position
- Below the diagonal: nearby.fragments uses a module listed above it, which is the healthy direction.
28→4 nearby.fragments uses location✕
- Connections
- 4 pairs of types, where a type in nearby.fragments uses a type in location.
- The types involved
fr.free.nrw.commons.nearby.fragments.NearbyParentFragment→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.nearby.fragments.NearbyParentFragment→fr.free.nrw.commons.location.LocationPermissionsHelperfr.free.nrw.commons.nearby.fragments.NearbyParentFragment→fr.free.nrw.commons.location.LocationServiceManagerfr.free.nrw.commons.nearby.fragments.NearbyParentFragment→fr.free.nrw.commons.location.LocationUpdateListener
- Direction
- nearby.fragments uses location, so a change to location can break nearby.fragments, while a change to nearby.fragments can't break location.
- Position
- Below the diagonal: nearby.fragments uses a module listed above it, which is the healthy direction.
28→13 nearby.fragments uses wikidata✕
- Connections
- 1 pair of types, where a type in nearby.fragments uses a type in wikidata.
- The types involved
fr.free.nrw.commons.nearby.fragments.NearbyParentFragment→fr.free.nrw.commons.wikidata.WikidataEditListener
- Direction
- nearby.fragments uses wikidata, so a change to wikidata can break nearby.fragments, while a change to nearby.fragments can't break wikidata.
- Position
- Below the diagonal: nearby.fragments uses a module listed above it, which is the healthy direction.
28→16 nearby.fragments uses upload.categories✕
- Connections
- 1 pair of types, where a type in nearby.fragments uses a type in upload.categories.
- The types involved
fr.free.nrw.commons.nearby.fragments.PlaceAdapter→fr.free.nrw.commons.upload.categories.BaseDelegateAdapter
- Direction
- nearby.fragments uses upload.categories, so a change to upload.categories can break nearby.fragments, while a change to nearby.fragments can't break upload.categories.
- Position
- Below the diagonal: nearby.fragments uses a module listed above it, which is the healthy direction.
28→21 nearby.fragments uses utils✕
- Connections
- 1 pair of types, where a type in nearby.fragments uses a type in utils.
- The types involved
fr.free.nrw.commons.nearby.fragments.NearbyParentFragment→fr.free.nrw.commons.utils.SystemThemeUtils
- Direction
- nearby.fragments uses utils, so a change to utils can break nearby.fragments, while a change to nearby.fragments can't break utils.
- Position
- Below the diagonal: nearby.fragments uses a module listed above it, which is the healthy direction.
28→27 nearby.fragments uses nearby✕
- Connections
- 2 pairs of types, where a type in nearby.fragments uses a type in nearby.
- The types involved
fr.free.nrw.commons.nearby.fragments.NearbyParentFragment→fr.free.nrw.commons.nearby.BottomSheetAdapterfr.free.nrw.commons.nearby.fragments.NearbyParentFragment→fr.free.nrw.commons.nearby.PlaceTypeLabelsClient
- Direction
- nearby.fragments uses nearby, so a change to nearby can break nearby.fragments, while a change to nearby.fragments can't break nearby.
- Position
- Below the diagonal: nearby.fragments uses a module listed above it, which is the healthy direction.
28→29 nearby.fragments uses bookmarks.locations part of a loop✕
- Connections
- 2 pairs of types, where a type in nearby.fragments uses a type in bookmarks.locations.
- The types involved
fr.free.nrw.commons.nearby.fragments.NearbyParentFragment→fr.free.nrw.commons.bookmarks.locations.BookmarkLocationsDaofr.free.nrw.commons.nearby.fragments.PlaceAdapter→fr.free.nrw.commons.bookmarks.locations.BookmarkLocationsDao
- Direction
- nearby.fragments uses bookmarks.locations, so a change to bookmarks.locations can break nearby.fragments, while a change to nearby.fragments can't break bookmarks.locations.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→32 nearby.fragments uses contributions part of a loop✕
- Connections
- 2 pairs of types, where a type in nearby.fragments uses a type in contributions.
- The types involved
fr.free.nrw.commons.nearby.fragments.CommonPlaceClickActions→fr.free.nrw.commons.contributions.ContributionControllerfr.free.nrw.commons.nearby.fragments.NearbyParentFragment→fr.free.nrw.commons.contributions.ContributionController
- Direction
- nearby.fragments uses contributions, so a change to contributions can break nearby.fragments, while a change to nearby.fragments can't break contributions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→34 nearby.fragments uses media part of a loop✕
- Connections
- 3 pairs of types, where a type in nearby.fragments uses a type in media.
- The types involved
fr.free.nrw.commons.nearby.fragments.NearbyParentFragment→fr.free.nrw.commons.media.MediaClientfr.free.nrw.commons.nearby.fragments.NearbyParentFragment→fr.free.nrw.commons.media.MediaDetailPagerFragmentfr.free.nrw.commons.nearby.fragments.NearbyParentFragment→fr.free.nrw.commons.media.MediaDetailProvider
- Direction
- nearby.fragments uses media, so a change to media can break nearby.fragments, while a change to nearby.fragments can't break media.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→38 nearby.fragments uses di part of a loop✕
- Connections
- 1 pair of types, where a type in nearby.fragments uses a type in di.
- The types involved
fr.free.nrw.commons.nearby.fragments.NearbyParentFragment→fr.free.nrw.commons.di.CommonsDaggerSupportFragment
- Direction
- nearby.fragments uses di, so a change to di can break nearby.fragments, while a change to nearby.fragments can't break di.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→40 nearby.fragments uses fr.free.nrw.commons part of a loop✕
- Connections
- 1 pair of types, where a type in nearby.fragments uses a type in fr.free.nrw.commons.
- The types involved
fr.free.nrw.commons.nearby.fragments.NearbyParentFragment→fr.free.nrw.commons.Media
- Direction
- nearby.fragments uses fr.free.nrw.commons, so a change to fr.free.nrw.commons can break nearby.fragments, while a change to nearby.fragments can't break fr.free.nrw.commons.
- 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→28 bookmarks.locations uses nearby.fragments✕
- Connections
- 2 pairs of types, where a type in bookmarks.locations uses a type in nearby.fragments.
- The types involved
fr.free.nrw.commons.bookmarks.locations.BookmarkLocationsFragment→fr.free.nrw.commons.nearby.fragments.CommonPlaceClickActionsfr.free.nrw.commons.bookmarks.locations.BookmarkLocationsFragment→fr.free.nrw.commons.nearby.fragments.PlaceAdapter
- Direction
- bookmarks.locations uses nearby.fragments, so a change to nearby.fragments can break bookmarks.locations, while a change to bookmarks.locations can't break nearby.fragments.
- Position
- Below the diagonal: bookmarks.locations uses a module listed above it, which is the healthy direction.
29→32 bookmarks.locations uses contributions part of a loop✕
- Connections
- 1 pair of types, where a type in bookmarks.locations uses a type in contributions.
- The types involved
fr.free.nrw.commons.bookmarks.locations.BookmarkLocationsFragment→fr.free.nrw.commons.contributions.ContributionController
- Direction
- bookmarks.locations uses contributions, so a change to contributions can break bookmarks.locations, while a change to bookmarks.locations can't break contributions.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→3 explore.map uses kvstore✕
- Connections
- 3 pairs of types, where a type in explore.map uses a type in kvstore.
- The types involved
fr.free.nrw.commons.explore.map.ExploreMapFragment→fr.free.nrw.commons.kvstore.JsonKvStorefr.free.nrw.commons.explore.map.ExploreMapPresenter→fr.free.nrw.commons.kvstore.JsonKvStorefr.free.nrw.commons.explore.map.ExploreMapViewportHelper→fr.free.nrw.commons.kvstore.JsonKvStore
- Direction
- explore.map uses kvstore, so a change to kvstore can break explore.map, while a change to explore.map can't break kvstore.
- Position
- Below the diagonal: explore.map uses a module listed above it, which is the healthy direction.
30→4 explore.map uses location✕
- Connections
- 14 pairs of types, where a type in explore.map uses a type in location.
- The types involved
fr.free.nrw.commons.explore.map.ExploreMapCalls→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.explore.map.ExploreMapController→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.explore.map.ExploreMapFragment→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.explore.map.ExploreMapFragment→fr.free.nrw.commons.location.LocationPermissionsHelperfr.free.nrw.commons.explore.map.ExploreMapFragment→fr.free.nrw.commons.location.LocationServiceManagerfr.free.nrw.commons.explore.map.ExploreMapFragment→fr.free.nrw.commons.location.LocationUpdateListenerfr.free.nrw.commons.explore.map.ExploreMapLocationHelper→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.explore.map.ExploreMapLocationHelper→fr.free.nrw.commons.location.LocationPermissionsHelperfr.free.nrw.commons.explore.map.ExploreMapLocationHelper→fr.free.nrw.commons.location.LocationServiceManagerfr.free.nrw.commons.explore.map.ExploreMapLocationHelper→fr.free.nrw.commons.location.LocationUpdateListenerfr.free.nrw.commons.explore.map.ExploreMapMarkerOverlayHelper→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.explore.map.ExploreMapPresenter→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.explore.map.ExploreMapViewportHelper→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.explore.map.ExploreMapViewportHelper→fr.free.nrw.commons.location.LocationPermissionsHelper
- Direction
- explore.map uses location, so a change to location can break explore.map, while a change to explore.map can't break location.
- Position
- Below the diagonal: explore.map uses a module listed above it, which is the healthy direction.
30→8 explore.map uses explore.paging✕
- Connections
- 1 pair of types, where a type in explore.map uses a type in explore.paging.
- The types involved
fr.free.nrw.commons.explore.map.ExploreMapFragment→fr.free.nrw.commons.explore.paging.LiveDataConverter
- Direction
- explore.map uses explore.paging, so a change to explore.paging can break explore.map, while a change to explore.map can't break explore.paging.
- Position
- Below the diagonal: explore.map uses a module listed above it, which is the healthy direction.
30→21 explore.map uses utils✕
- Connections
- 1 pair of types, where a type in explore.map uses a type in utils.
- The types involved
fr.free.nrw.commons.explore.map.ExploreMapFragment→fr.free.nrw.commons.utils.SystemThemeUtils
- Direction
- explore.map uses utils, so a change to utils can break explore.map, while a change to explore.map can't break utils.
- Position
- Below the diagonal: explore.map uses a module listed above it, which is the healthy direction.
30→29 explore.map uses bookmarks.locations✕
- Connections
- 2 pairs of types, where a type in explore.map uses a type in bookmarks.locations.
- The types involved
fr.free.nrw.commons.explore.map.ExploreMapFragment→fr.free.nrw.commons.bookmarks.locations.BookmarkLocationsDaofr.free.nrw.commons.explore.map.ExploreMapPresenter→fr.free.nrw.commons.bookmarks.locations.BookmarkLocationsDao
- Direction
- explore.map uses bookmarks.locations, so a change to bookmarks.locations can break explore.map, while a change to explore.map can't break bookmarks.locations.
- Position
- Below the diagonal: explore.map uses a module listed above it, which is the healthy direction.
30→34 explore.map uses media part of a loop✕
- Connections
- 2 pairs of types, where a type in explore.map uses a type in media.
- The types involved
fr.free.nrw.commons.explore.map.ExploreMapCalls→fr.free.nrw.commons.media.MediaCollectionClientfr.free.nrw.commons.explore.map.ExploreMapFragment→fr.free.nrw.commons.media.MediaClient
- Direction
- explore.map uses media, so a change to media can break explore.map, while a change to explore.map can't break media.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→38 explore.map uses di part of a loop✕
- Connections
- 1 pair of types, where a type in explore.map uses a type in di.
- The types involved
fr.free.nrw.commons.explore.map.ExploreMapFragment→fr.free.nrw.commons.di.CommonsDaggerSupportFragment
- Direction
- explore.map uses di, so a change to di can break explore.map, while a change to explore.map can't break di.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→40 explore.map uses fr.free.nrw.commons part of a loop✕
- Connections
- 7 pairs of types, where a type in explore.map uses a type in fr.free.nrw.commons.
- The types involved
fr.free.nrw.commons.explore.map.ExploreMapCalls→fr.free.nrw.commons.Mediafr.free.nrw.commons.explore.map.ExploreMapController→fr.free.nrw.commons.MapControllerfr.free.nrw.commons.explore.map.ExploreMapDetailsSheetHelper→fr.free.nrw.commons.Mediafr.free.nrw.commons.explore.map.ExploreMapFragment→fr.free.nrw.commons.Mediafr.free.nrw.commons.explore.map.ExploreMapMarkerHandler→fr.free.nrw.commons.BaseMarkerfr.free.nrw.commons.explore.map.ExploreMapMarkerOverlayHelper→fr.free.nrw.commons.BaseMarkerfr.free.nrw.commons.explore.map.ExploreMapMarkerOverlayHelper→fr.free.nrw.commons.Media
- Direction
- explore.map uses fr.free.nrw.commons, so a change to fr.free.nrw.commons can break explore.map, while a change to explore.map can't break fr.free.nrw.commons.
- 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.
31→3 explore uses kvstore✕
- Connections
- 1 pair of types, where a type in explore uses a type in kvstore.
- The types involved
fr.free.nrw.commons.explore.ExploreFragment→fr.free.nrw.commons.kvstore.JsonKvStore
- Direction
- explore uses kvstore, so a change to kvstore can break explore, while a change to explore can't break kvstore.
- Position
- Below the diagonal: explore uses a module listed above it, which is the healthy direction.
31→11 explore uses explore.media✕
- Connections
- 2 pairs of types, where a type in explore uses a type in explore.media.
- The types involved
fr.free.nrw.commons.explore.SearchModule→fr.free.nrw.commons.explore.media.SearchMediaFragmentPresenterfr.free.nrw.commons.explore.SearchQueryController→fr.free.nrw.commons.explore.media.SearchMediaFragment
- Direction
- explore uses explore.media, so a change to explore.media can break explore, while a change to explore can't break explore.media.
- Position
- Below the diagonal: explore uses a module listed above it, which is the healthy direction.
31→22 explore uses theme✕
- Connections
- 1 pair of types, where a type in explore uses a type in theme.
- The types involved
fr.free.nrw.commons.explore.SearchActivity→fr.free.nrw.commons.theme.BaseActivity
- Direction
- explore uses theme, so a change to theme can break explore, while a change to explore can't break theme.
- Position
- Below the diagonal: explore uses a module listed above it, which is the healthy direction.
31→30 explore uses explore.map✕
- Connections
- 1 pair of types, where a type in explore uses a type in explore.map.
- The types involved
fr.free.nrw.commons.explore.ExploreMapRootFragment→fr.free.nrw.commons.explore.map.ExploreMapFragment
- Direction
- explore uses explore.map, so a change to explore.map can break explore, while a change to explore can't break explore.map.
- Position
- Below the diagonal: explore uses a module listed above it, which is the healthy direction.
31→34 explore uses media part of a loop✕
- Connections
- 4 pairs of types, where a type in explore uses a type in media.
- The types involved
fr.free.nrw.commons.explore.ExploreMediaRootFragment→fr.free.nrw.commons.media.MediaDetailPagerFragmentfr.free.nrw.commons.explore.ExploreMediaRootFragment→fr.free.nrw.commons.media.MediaDetailProviderfr.free.nrw.commons.explore.SearchActivity→fr.free.nrw.commons.media.MediaDetailPagerFragmentfr.free.nrw.commons.explore.SearchActivity→fr.free.nrw.commons.media.MediaDetailProvider
- Direction
- explore uses media, so a change to media can break explore, while a change to explore can't break media.
- 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.
31→35 explore uses category part of a loop✕
- Connections
- 2 pairs of types, where a type in explore uses a type in category.
- The types involved
fr.free.nrw.commons.explore.ExploreMediaRootFragment→fr.free.nrw.commons.category.CategoryImagesCallbackfr.free.nrw.commons.explore.SearchActivity→fr.free.nrw.commons.category.CategoryImagesCallback
- Direction
- explore uses category, so a change to category can break explore, while a change to explore can't break category.
- 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.
31→38 explore uses di part of a loop✕
- Connections
- 2 pairs of types, where a type in explore uses a type in di.
- The types involved
fr.free.nrw.commons.explore.ExploreFragment→fr.free.nrw.commons.di.CommonsDaggerSupportFragmentfr.free.nrw.commons.explore.ExploreMediaRootFragment→fr.free.nrw.commons.di.CommonsDaggerSupportFragment
- Direction
- explore uses di, so a change to di can break explore, while a change to explore can't break di.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→40 explore uses fr.free.nrw.commons part of a loop✕
- Connections
- 6 pairs of types, where a type in explore uses a type in fr.free.nrw.commons.
- The types involved
fr.free.nrw.commons.explore.ExploreFragment→fr.free.nrw.commons.ViewPagerAdapterfr.free.nrw.commons.explore.ExploreListRootFragment→fr.free.nrw.commons.Mediafr.free.nrw.commons.explore.ExploreMapRootFragment→fr.free.nrw.commons.Mediafr.free.nrw.commons.explore.SearchActivity→fr.free.nrw.commons.Mediafr.free.nrw.commons.explore.SearchActivity→fr.free.nrw.commons.ViewPagerAdapterfr.free.nrw.commons.explore.SearchQueryController→fr.free.nrw.commons.ViewPagerAdapter
- Direction
- explore uses fr.free.nrw.commons, so a change to fr.free.nrw.commons can break explore, while a change to explore can't break fr.free.nrw.commons.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→2 contributions uses filepicker✕
- Connections
- 2 pairs of types, where a type in contributions uses a type in filepicker.
- The types involved
fr.free.nrw.commons.contributions.ContributionController→fr.free.nrw.commons.filepicker.ExternalImagesResultfr.free.nrw.commons.contributions.ContributionController→fr.free.nrw.commons.filepicker.UploadableFile
- Direction
- contributions uses filepicker, so a change to filepicker can break contributions, while a change to contributions can't break filepicker.
- Position
- Below the diagonal: contributions uses a module listed above it, which is the healthy direction.
32→3 contributions uses kvstore✕
- Connections
- 5 pairs of types, where a type in contributions uses a type in kvstore.
- The types involved
fr.free.nrw.commons.contributions.ContributionController→fr.free.nrw.commons.kvstore.JsonKvStorefr.free.nrw.commons.contributions.ContributionsFragment→fr.free.nrw.commons.kvstore.JsonKvStorefr.free.nrw.commons.contributions.ContributionsLocalDataSource→fr.free.nrw.commons.kvstore.JsonKvStorefr.free.nrw.commons.contributions.ContributionsProvidesModule→fr.free.nrw.commons.kvstore.JsonKvStorefr.free.nrw.commons.contributions.MainActivity→fr.free.nrw.commons.kvstore.JsonKvStore
- Direction
- contributions uses kvstore, so a change to kvstore can break contributions, while a change to contributions can't break kvstore.
- Position
- Below the diagonal: contributions uses a module listed above it, which is the healthy direction.
32→4 contributions uses location✕
- Connections
- 7 pairs of types, where a type in contributions uses a type in location.
- The types involved
fr.free.nrw.commons.contributions.ContributionController→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.contributions.ContributionController→fr.free.nrw.commons.location.LocationPermissionsHelperfr.free.nrw.commons.contributions.ContributionController→fr.free.nrw.commons.location.LocationServiceManagerfr.free.nrw.commons.contributions.ContributionsFragment→fr.free.nrw.commons.location.LocationServiceManagerfr.free.nrw.commons.contributions.ContributionsNearbyController→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.contributions.ContributionsNearbyController→fr.free.nrw.commons.location.LocationUpdateListenerfr.free.nrw.commons.contributions.MainActivity→fr.free.nrw.commons.location.LocationServiceManager
- Direction
- contributions uses location, so a change to location can break contributions, while a change to contributions can't break location.
- Position
- Below the diagonal: contributions uses a module listed above it, which is the healthy direction.
32→7 contributions uses wikidata.model✕
- Connections
- 3 pairs of types, where a type in contributions uses a type in wikidata.model.
- The types involved
fr.free.nrw.commons.contributions.ContributionsListFragment→fr.free.nrw.commons.wikidata.model.WikiSitefr.free.nrw.commons.contributions.ContributionsListWikipediaHelper→fr.free.nrw.commons.wikidata.model.WikiSitefr.free.nrw.commons.contributions.ContributionsProvidesModule→fr.free.nrw.commons.wikidata.model.WikiSite
- Direction
- contributions uses wikidata.model, so a change to wikidata.model can break contributions, while a change to contributions can't break wikidata.model.
- Position
- Below the diagonal: contributions uses a module listed above it, which is the healthy direction.
32→14 contributions uses upload.structure.depictions✕
- Connections
- 1 pair of types, where a type in contributions uses a type in upload.structure.depictions.
- The types involved
fr.free.nrw.commons.contributions.Contribution→fr.free.nrw.commons.upload.structure.depictions.DepictedItem
- Direction
- contributions uses upload.structure.depictions, so a change to upload.structure.depictions can break contributions, while a change to contributions can't break upload.structure.depictions.
- Position
- Below the diagonal: contributions uses a module listed above it, which is the healthy direction.
32→15 contributions uses repository✕
- Connections
- 1 pair of types, where a type in contributions uses a type in repository.
- The types involved
fr.free.nrw.commons.contributions.ContributionsPresenter→fr.free.nrw.commons.repository.UploadRepository
- Direction
- contributions uses repository, so a change to repository can break contributions, while a change to contributions can't break repository.
- Position
- Below the diagonal: contributions uses a module listed above it, which is the healthy direction.
32→18 contributions uses notification✕
- Connections
- 2 pairs of types, where a type in contributions uses a type in notification.
- The types involved
fr.free.nrw.commons.contributions.ContributionsFragment→fr.free.nrw.commons.notification.NotificationControllerfr.free.nrw.commons.contributions.MainActivity→fr.free.nrw.commons.notification.NotificationController
- Direction
- contributions uses notification, so a change to notification can break contributions, while a change to contributions can't break notification.
- Position
- Below the diagonal: contributions uses a module listed above it, which is the healthy direction.
32→20 contributions uses upload✕
- Connections
- 3 pairs of types, where a type in contributions uses a type in upload.
- The types involved
fr.free.nrw.commons.contributions.ChunkInfo→fr.free.nrw.commons.upload.UploadResultfr.free.nrw.commons.contributions.Contribution→fr.free.nrw.commons.upload.UploadItemfr.free.nrw.commons.contributions.Contribution→fr.free.nrw.commons.upload.WikidataPlace
- Direction
- contributions uses upload, so a change to upload can break contributions, while a change to contributions can't break upload.
- Position
- Below the diagonal: contributions uses a module listed above it, which is the healthy direction.
32→21 contributions uses utils✕
- Connections
- 1 pair of types, where a type in contributions uses a type in utils.
- The types involved
fr.free.nrw.commons.contributions.MainActivity→fr.free.nrw.commons.utils.ViewUtilWrapper
- Direction
- contributions uses utils, so a change to utils can break contributions, while a change to contributions can't break utils.
- Position
- Below the diagonal: contributions uses a module listed above it, which is the healthy direction.
32→22 contributions uses theme✕
- Connections
- 1 pair of types, where a type in contributions uses a type in theme.
- The types involved
fr.free.nrw.commons.contributions.MainActivity→fr.free.nrw.commons.theme.BaseActivity
- Direction
- contributions uses theme, so a change to theme can break contributions, while a change to contributions can't break theme.
- Position
- Below the diagonal: contributions uses a module listed above it, which is the healthy direction.
32→26 contributions uses mwapi✕
- Connections
- 4 pairs of types, where a type in contributions uses a type in mwapi.
- The types involved
fr.free.nrw.commons.contributions.ContributionsFragment→fr.free.nrw.commons.mwapi.UserStatsClientfr.free.nrw.commons.contributions.ContributionsMenuController→fr.free.nrw.commons.mwapi.UploadCountfr.free.nrw.commons.contributions.MainActivityKt→fr.free.nrw.commons.mwapi.UploadCountfr.free.nrw.commons.contributions.MainTabHandler→fr.free.nrw.commons.mwapi.UploadCount
- Direction
- contributions uses mwapi, so a change to mwapi can break contributions, while a change to contributions can't break mwapi.
- Position
- Below the diagonal: contributions uses a module listed above it, which is the healthy direction.
32→28 contributions uses nearby.fragments✕
- Connections
- 1 pair of types, where a type in contributions uses a type in nearby.fragments.
- The types involved
fr.free.nrw.commons.contributions.MainNavigationHelper→fr.free.nrw.commons.nearby.fragments.NearbyParentFragment
- Direction
- contributions uses nearby.fragments, so a change to nearby.fragments can break contributions, while a change to contributions can't break nearby.fragments.
- Position
- Below the diagonal: contributions uses a module listed above it, which is the healthy direction.
32→31 contributions uses explore✕
- Connections
- 1 pair of types, where a type in contributions uses a type in explore.
- The types involved
fr.free.nrw.commons.contributions.MainNavigationHelper→fr.free.nrw.commons.explore.ExploreFragment
- Direction
- contributions uses explore, so a change to explore can break contributions, while a change to contributions can't break explore.
- Position
- Below the diagonal: contributions uses a module listed above it, which is the healthy direction.
32→34 contributions uses media part of a loop✕
- Connections
- 8 pairs of types, where a type in contributions uses a type in media.
- The types involved
fr.free.nrw.commons.contributions.ContributionBoundaryCallback→fr.free.nrw.commons.media.MediaCollectionClientfr.free.nrw.commons.contributions.ContributionViewHolder→fr.free.nrw.commons.media.MediaClientfr.free.nrw.commons.contributions.ContributionsFragment→fr.free.nrw.commons.media.MediaDetailPagerFragmentfr.free.nrw.commons.contributions.ContributionsFragment→fr.free.nrw.commons.media.MediaDetailProviderfr.free.nrw.commons.contributions.ContributionsListAdapter→fr.free.nrw.commons.media.MediaClientfr.free.nrw.commons.contributions.ContributionsListFragment→fr.free.nrw.commons.media.MediaClientfr.free.nrw.commons.contributions.ContributionsNavigator→fr.free.nrw.commons.media.MediaDetailProviderfr.free.nrw.commons.contributions.ContributionsRemoteDataSource→fr.free.nrw.commons.media.MediaCollectionClient
- Direction
- contributions uses media, so a change to media can break contributions, while a change to contributions can't break media.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→36 contributions uses bookmarks part of a loop✕
- Connections
- 1 pair of types, where a type in contributions uses a type in bookmarks.
- The types involved
fr.free.nrw.commons.contributions.MainNavigationHelper→fr.free.nrw.commons.bookmarks.BookmarkFragment
- Direction
- contributions uses bookmarks, so a change to bookmarks can break contributions, while a change to contributions can't break bookmarks.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→38 contributions uses di part of a loop✕
- Connections
- 2 pairs of types, where a type in contributions uses a type in di.
- The types involved
fr.free.nrw.commons.contributions.BaseContributionsListFragment→fr.free.nrw.commons.di.CommonsDaggerSupportFragmentfr.free.nrw.commons.contributions.ContributionsFragment→fr.free.nrw.commons.di.CommonsDaggerSupportFragment
- Direction
- contributions uses di, so a change to di can break contributions, while a change to contributions can't break di.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→39 contributions uses auth part of a loop✕
- Connections
- 5 pairs of types, where a type in contributions uses a type in auth.
- The types involved
fr.free.nrw.commons.contributions.Contribution→fr.free.nrw.commons.auth.SessionManagerfr.free.nrw.commons.contributions.ContributionBoundaryCallback→fr.free.nrw.commons.auth.SessionManagerfr.free.nrw.commons.contributions.ContributionsFragment→fr.free.nrw.commons.auth.SessionManagerfr.free.nrw.commons.contributions.ContributionsListFragment→fr.free.nrw.commons.auth.SessionManagerfr.free.nrw.commons.contributions.MainActivity→fr.free.nrw.commons.auth.SessionManager
- Direction
- contributions uses auth, so a change to auth can break contributions, while a change to contributions can't break auth.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→40 contributions uses fr.free.nrw.commons part of a loop✕
- Connections
- 8 pairs of types, where a type in contributions uses a type in fr.free.nrw.commons.
- The types involved
fr.free.nrw.commons.contributions.BaseContributionsListFragment→fr.free.nrw.commons.Mediafr.free.nrw.commons.contributions.Contribution→fr.free.nrw.commons.Mediafr.free.nrw.commons.contributions.ContributionViewHolder→fr.free.nrw.commons.Mediafr.free.nrw.commons.contributions.ContributionViewHolder→fr.free.nrw.commons.MediaDataExtractorfr.free.nrw.commons.contributions.ContributionsListAdapter→fr.free.nrw.commons.MediaDataExtractorfr.free.nrw.commons.contributions.ContributionsListFragment→fr.free.nrw.commons.MediaDataExtractorfr.free.nrw.commons.contributions.ContributionsNavigator→fr.free.nrw.commons.Mediafr.free.nrw.commons.contributions.ContributionsPresenter→fr.free.nrw.commons.MediaDataExtractor
- Direction
- contributions uses fr.free.nrw.commons, so a change to fr.free.nrw.commons can break contributions, while a change to contributions can't break fr.free.nrw.commons.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→1 customselector.ui.selector uses customselector.model✕
- Connections
- 7 pairs of types, where a type in customselector.ui.selector uses a type in customselector.model.
- The types involved
fr.free.nrw.commons.customselector.ui.selector.CustomSelectorActivity→fr.free.nrw.commons.customselector.model.Imagefr.free.nrw.commons.customselector.ui.selector.CustomSelectorViewModel→fr.free.nrw.commons.customselector.model.Imagefr.free.nrw.commons.customselector.ui.selector.FolderFragment→fr.free.nrw.commons.customselector.model.Folderfr.free.nrw.commons.customselector.ui.selector.FolderFragment→fr.free.nrw.commons.customselector.model.Resultfr.free.nrw.commons.customselector.ui.selector.ImageFileLoader→fr.free.nrw.commons.customselector.model.Imagefr.free.nrw.commons.customselector.ui.selector.ImageFragment→fr.free.nrw.commons.customselector.model.Imagefr.free.nrw.commons.customselector.ui.selector.ImageLoader→fr.free.nrw.commons.customselector.model.Image
- Direction
- customselector.ui.selector uses customselector.model, so a change to customselector.model can break customselector.ui.selector, while a change to customselector.ui.selector can't break customselector.model.
- Position
- Below the diagonal: customselector.ui.selector uses a module listed above it, which is the healthy direction.
33→20 customselector.ui.selector uses upload✕
- Connections
- 6 pairs of types, where a type in customselector.ui.selector uses a type in upload.
- The types involved
fr.free.nrw.commons.customselector.ui.selector.CustomSelectorActivity→fr.free.nrw.commons.upload.FileUtilsWrapperfr.free.nrw.commons.customselector.ui.selector.FolderFragment→fr.free.nrw.commons.upload.FileProcessorfr.free.nrw.commons.customselector.ui.selector.ImageFragment→fr.free.nrw.commons.upload.FileProcessorfr.free.nrw.commons.customselector.ui.selector.ImageFragment→fr.free.nrw.commons.upload.FileUtilsWrapperfr.free.nrw.commons.customselector.ui.selector.ImageLoader→fr.free.nrw.commons.upload.FileProcessorfr.free.nrw.commons.customselector.ui.selector.ImageLoader→fr.free.nrw.commons.upload.FileUtilsWrapper
- Direction
- customselector.ui.selector uses upload, so a change to upload can break customselector.ui.selector, while a change to customselector.ui.selector can't break upload.
- Position
- Below the diagonal: customselector.ui.selector uses a module listed above it, which is the healthy direction.
33→22 customselector.ui.selector uses theme✕
- Connections
- 1 pair of types, where a type in customselector.ui.selector uses a type in theme.
- The types involved
fr.free.nrw.commons.customselector.ui.selector.CustomSelectorActivity→fr.free.nrw.commons.theme.BaseActivity
- Direction
- customselector.ui.selector uses theme, so a change to theme can break customselector.ui.selector, while a change to customselector.ui.selector can't break theme.
- Position
- Below the diagonal: customselector.ui.selector uses a module listed above it, which is the healthy direction.
33→32 customselector.ui.selector uses contributions✕
- Connections
- 2 pairs of types, where a type in customselector.ui.selector uses a type in contributions.
- The types involved
fr.free.nrw.commons.customselector.ui.selector.ImageFragment→fr.free.nrw.commons.contributions.ContributionDaofr.free.nrw.commons.customselector.ui.selector.ImageLoader→fr.free.nrw.commons.contributions.Contribution
- Direction
- customselector.ui.selector uses contributions, so a change to contributions can break customselector.ui.selector, while a change to customselector.ui.selector can't break contributions.
- Position
- Below the diagonal: customselector.ui.selector uses a module listed above it, which is the healthy direction.
33→34 customselector.ui.selector uses media part of a loop✕
- Connections
- 3 pairs of types, where a type in customselector.ui.selector uses a type in media.
- The types involved
fr.free.nrw.commons.customselector.ui.selector.FolderFragment→fr.free.nrw.commons.media.MediaClientfr.free.nrw.commons.customselector.ui.selector.ImageFragment→fr.free.nrw.commons.media.MediaClientfr.free.nrw.commons.customselector.ui.selector.ImageLoader→fr.free.nrw.commons.media.MediaClient
- Direction
- customselector.ui.selector uses media, so a change to media can break customselector.ui.selector, while a change to customselector.ui.selector can't break media.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→38 customselector.ui.selector uses di part of a loop✕
- Connections
- 2 pairs of types, where a type in customselector.ui.selector uses a type in di.
- The types involved
fr.free.nrw.commons.customselector.ui.selector.FolderFragment→fr.free.nrw.commons.di.CommonsDaggerSupportFragmentfr.free.nrw.commons.customselector.ui.selector.ImageFragment→fr.free.nrw.commons.di.CommonsDaggerSupportFragment
- Direction
- customselector.ui.selector uses di, so a change to di can break customselector.ui.selector, while a change to customselector.ui.selector can't break di.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→1 media uses customselector.model✕
- Connections
- 2 pairs of types, where a type in media uses a type in customselector.model.
- The types involved
fr.free.nrw.commons.media.ZoomableActivity→fr.free.nrw.commons.customselector.model.Imagefr.free.nrw.commons.media.ZoomableActivity→fr.free.nrw.commons.customselector.model.Result
- Direction
- media uses customselector.model, so a change to customselector.model can break media, while a change to media can't break customselector.model.
- Position
- Below the diagonal: media uses a module listed above it, which is the healthy direction.
34→3 media uses kvstore✕
- Connections
- 2 pairs of types, where a type in media uses a type in kvstore.
- The types involved
fr.free.nrw.commons.media.CustomOkHttpNetworkFetcher→fr.free.nrw.commons.kvstore.JsonKvStorefr.free.nrw.commons.media.MediaDetailFragment→fr.free.nrw.commons.kvstore.JsonKvStore
- Direction
- media uses kvstore, so a change to kvstore can break media, while a change to media can't break kvstore.
- Position
- Below the diagonal: media uses a module listed above it, which is the healthy direction.
34→4 media uses location✕
- Connections
- 1 pair of types, where a type in media uses a type in location.
- The types involved
fr.free.nrw.commons.media.MediaDetailFragment→fr.free.nrw.commons.location.LocationServiceManager
- Direction
- media uses location, so a change to location can break media, while a change to media can't break location.
- Position
- Below the diagonal: media uses a module listed above it, which is the healthy direction.
34→7 media uses wikidata.model✕
- Connections
- 4 pairs of types, where a type in media uses a type in wikidata.model.
- The types involved
fr.free.nrw.commons.media.MediaClient→fr.free.nrw.commons.wikidata.model.Entitiesfr.free.nrw.commons.media.MediaDetailInterface→fr.free.nrw.commons.wikidata.model.Entitiesfr.free.nrw.commons.media.MediaResponseMapper→fr.free.nrw.commons.wikidata.model.Entitiesfr.free.nrw.commons.media.WikidataMediaClient→fr.free.nrw.commons.wikidata.model.Entities
- Direction
- media uses wikidata.model, so a change to wikidata.model can break media, while a change to media can't break wikidata.model.
- Position
- Below the diagonal: media uses a module listed above it, which is the healthy direction.
34→9 media uses wikidata.mwapi✕
- Connections
- 10 pairs of types, where a type in media uses a type in wikidata.mwapi.
- The types involved
fr.free.nrw.commons.media.FileDeletedOnCommonsExceptionKt→fr.free.nrw.commons.wikidata.mwapi.MwQueryPagefr.free.nrw.commons.media.MediaCollectionClient→fr.free.nrw.commons.wikidata.mwapi.MwQueryResponsefr.free.nrw.commons.media.MediaDetailInterface→fr.free.nrw.commons.wikidata.mwapi.MwQueryResponsefr.free.nrw.commons.media.MediaInterface→fr.free.nrw.commons.wikidata.mwapi.MwQueryResponsefr.free.nrw.commons.media.MediaResponseMapper→fr.free.nrw.commons.wikidata.mwapi.MwQueryPagefr.free.nrw.commons.media.MediaResponseMapper→fr.free.nrw.commons.wikidata.mwapi.MwQueryResponsefr.free.nrw.commons.media.MwParseResponse→fr.free.nrw.commons.wikidata.mwapi.MwResponsefr.free.nrw.commons.media.WikidataMediaClient→fr.free.nrw.commons.wikidata.mwapi.MwQueryPagefr.free.nrw.commons.media.WikidataMediaClient→fr.free.nrw.commons.wikidata.mwapi.MwQueryResponsefr.free.nrw.commons.media.WikidataMediaInterface→fr.free.nrw.commons.wikidata.mwapi.MwQueryResponse
- Direction
- media uses wikidata.mwapi, so a change to wikidata.mwapi can break media, while a change to media can't break wikidata.mwapi.
- Position
- Below the diagonal: media uses a module listed above it, which is the healthy direction.
34→11 media uses explore.media✕
- Connections
- 2 pairs of types, where a type in media uses a type in explore.media.
- The types involved
fr.free.nrw.commons.media.MediaResponseMapper→fr.free.nrw.commons.explore.media.MediaConverterfr.free.nrw.commons.media.WikidataMediaClient→fr.free.nrw.commons.explore.media.MediaConverter
- Direction
- media uses explore.media, so a change to explore.media can break media, while a change to media can't break explore.media.
- Position
- Below the diagonal: media uses a module listed above it, which is the healthy direction.
34→12 media uses actions✕
- Connections
- 1 pair of types, where a type in media uses a type in actions.
- The types involved
fr.free.nrw.commons.media.MediaDetailFragment→fr.free.nrw.commons.actions.ThanksClient
- Direction
- media uses actions, so a change to actions can break media, while a change to media can't break actions.
- Position
- Below the diagonal: media uses a module listed above it, which is the healthy direction.
34→20 media uses upload✕
- Connections
- 3 pairs of types, where a type in media uses a type in upload.
- The types involved
fr.free.nrw.commons.media.MediaDetailCaptionEditorKt→fr.free.nrw.commons.upload.UploadMediaDetailfr.free.nrw.commons.media.ZoomableActivity→fr.free.nrw.commons.upload.FileProcessorfr.free.nrw.commons.media.ZoomableActivity→fr.free.nrw.commons.upload.FileUtilsWrapper
- Direction
- media uses upload, so a change to upload can break media, while a change to media can't break upload.
- Position
- Below the diagonal: media uses a module listed above it, which is the healthy direction.
34→21 media uses utils✕
- Connections
- 1 pair of types, where a type in media uses a type in utils.
- The types involved
fr.free.nrw.commons.media.MediaDetailFragment→fr.free.nrw.commons.utils.ViewUtilWrapper
- Direction
- media uses utils, so a change to utils can break media, while a change to media can't break utils.
- Position
- Below the diagonal: media uses a module listed above it, which is the healthy direction.
34→22 media uses theme✕
- Connections
- 2 pairs of types, where a type in media uses a type in theme.
- The types involved
fr.free.nrw.commons.media.DeletedFileActivity→fr.free.nrw.commons.theme.BaseActivityfr.free.nrw.commons.media.ZoomableActivity→fr.free.nrw.commons.theme.BaseActivity
- Direction
- media uses theme, so a change to theme can break media, while a change to media can't break theme.
- Position
- Below the diagonal: media uses a module listed above it, which is the healthy direction.
34→23 media uses description✕
- Connections
- 1 pair of types, where a type in media uses a type in description.
- The types involved
fr.free.nrw.commons.media.MediaDetailFragment→fr.free.nrw.commons.description.DescriptionEditHelper
- Direction
- media uses description, so a change to description can break media, while a change to media can't break description.
- Position
- Below the diagonal: media uses a module listed above it, which is the healthy direction.
34→25 media uses review✕
- Connections
- 1 pair of types, where a type in media uses a type in review.
- The types involved
fr.free.nrw.commons.media.MediaDetailFragment→fr.free.nrw.commons.review.ReviewHelper
- Direction
- media uses review, so a change to review can break media, while a change to media can't break review.
- Position
- Below the diagonal: media uses a module listed above it, which is the healthy direction.
34→26 media uses mwapi✕
- Connections
- 3 pairs of types, where a type in media uses a type in mwapi.
- The types involved
fr.free.nrw.commons.media.MediaDetailMenuHandler→fr.free.nrw.commons.mwapi.OkHttpJsonApiClientfr.free.nrw.commons.media.MediaDetailPagerFragment→fr.free.nrw.commons.mwapi.OkHttpJsonApiClientfr.free.nrw.commons.media.MediaDetailViewModel→fr.free.nrw.commons.mwapi.OkHttpJsonApiClient
- Direction
- media uses mwapi, so a change to mwapi can break media, while a change to media can't break mwapi.
- Position
- Below the diagonal: media uses a module listed above it, which is the healthy direction.
34→32 media uses contributions✕
- Connections
- 2 pairs of types, where a type in media uses a type in contributions.
- The types involved
fr.free.nrw.commons.media.MediaDetailFragment→fr.free.nrw.commons.contributions.ContributionsRepositoryfr.free.nrw.commons.media.MediaDetailLoadingKt→fr.free.nrw.commons.contributions.ContributionsFragment
- Direction
- media uses contributions, so a change to contributions can break media, while a change to media can't break contributions.
- Position
- Below the diagonal: media uses a module listed above it, which is the healthy direction.
34→33 media uses customselector.ui.selector✕
- Connections
- 2 pairs of types, where a type in media uses a type in customselector.ui.selector.
- The types involved
fr.free.nrw.commons.media.ZoomableActivity→fr.free.nrw.commons.customselector.ui.selector.CustomSelectorViewModelfr.free.nrw.commons.media.ZoomableActivity→fr.free.nrw.commons.customselector.ui.selector.CustomSelectorViewModelFactory
- Direction
- media uses customselector.ui.selector, so a change to customselector.ui.selector can break media, while a change to media can't break customselector.ui.selector.
- Position
- Below the diagonal: media uses a module listed above it, which is the healthy direction.
34→35 media uses category part of a loop✕
- Connections
- 4 pairs of types, where a type in media uses a type in category.
- The types involved
fr.free.nrw.commons.media.MediaCollectionClient→fr.free.nrw.commons.category.ContinuationClientfr.free.nrw.commons.media.MediaDetailFragment→fr.free.nrw.commons.category.CategoryClientfr.free.nrw.commons.media.MediaDetailFragment→fr.free.nrw.commons.category.CategoryEditHelperfr.free.nrw.commons.media.WikidataMediaClient→fr.free.nrw.commons.category.ContinuationClient
- Direction
- media uses category, so a change to category can break media, while a change to media can't break category.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→38 media uses di part of a loop✕
- Connections
- 2 pairs of types, where a type in media uses a type in di.
- The types involved
fr.free.nrw.commons.media.MediaDetailFragment→fr.free.nrw.commons.di.CommonsDaggerSupportFragmentfr.free.nrw.commons.media.MediaDetailPagerFragment→fr.free.nrw.commons.di.CommonsDaggerSupportFragment
- Direction
- media uses di, so a change to di can break media, while a change to media can't break di.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→39 media uses auth part of a loop✕
- Connections
- 4 pairs of types, where a type in media uses a type in auth.
- The types involved
fr.free.nrw.commons.media.MediaDetailFragment→fr.free.nrw.commons.auth.SessionManagerfr.free.nrw.commons.media.MediaDetailMenuHandler→fr.free.nrw.commons.auth.SessionManagerfr.free.nrw.commons.media.MediaDetailPagerFragment→fr.free.nrw.commons.auth.SessionManagerfr.free.nrw.commons.media.MediaReportHelper→fr.free.nrw.commons.auth.SessionManager
- Direction
- media uses auth, so a change to auth can break media, while a change to media can't break auth.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→40 media uses fr.free.nrw.commons part of a loop✕
- Connections
- 13 pairs of types, where a type in media uses a type in fr.free.nrw.commons.
- The types involved
fr.free.nrw.commons.media.MediaClient→fr.free.nrw.commons.Mediafr.free.nrw.commons.media.MediaCollectionClient→fr.free.nrw.commons.Mediafr.free.nrw.commons.media.MediaDetailFragment→fr.free.nrw.commons.Mediafr.free.nrw.commons.media.MediaDetailFragment→fr.free.nrw.commons.MediaDataExtractorfr.free.nrw.commons.media.MediaDetailImageKt→fr.free.nrw.commons.Mediafr.free.nrw.commons.media.MediaDetailLoadingKt→fr.free.nrw.commons.Mediafr.free.nrw.commons.media.MediaDetailMenuHandler→fr.free.nrw.commons.Mediafr.free.nrw.commons.media.MediaDetailMetadataKt→fr.free.nrw.commons.Mediafr.free.nrw.commons.media.MediaDetailPlaybackKt→fr.free.nrw.commons.MediaTypefr.free.nrw.commons.media.MediaDetailProvider→fr.free.nrw.commons.Mediafr.free.nrw.commons.media.MediaReportHelper→fr.free.nrw.commons.Mediafr.free.nrw.commons.media.MediaResponseMapper→fr.free.nrw.commons.Mediafr.free.nrw.commons.media.WikidataMediaClient→fr.free.nrw.commons.Media
- Direction
- media uses fr.free.nrw.commons, so a change to fr.free.nrw.commons can break media, while a change to media can't break fr.free.nrw.commons.
- 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.
35→9 category uses wikidata.mwapi✕
- Connections
- 2 pairs of types, where a type in category uses a type in wikidata.mwapi.
- The types involved
fr.free.nrw.commons.category.CategoryClient→fr.free.nrw.commons.wikidata.mwapi.MwQueryResponsefr.free.nrw.commons.category.CategoryInterface→fr.free.nrw.commons.wikidata.mwapi.MwQueryResponse
- Direction
- category uses wikidata.mwapi, so a change to wikidata.mwapi can break category, while a change to category can't break wikidata.mwapi.
- Position
- Below the diagonal: category uses a module listed above it, which is the healthy direction.
35→12 category uses actions✕
- Connections
- 1 pair of types, where a type in category uses a type in actions.
- The types involved
fr.free.nrw.commons.category.CategoryEditHelper→fr.free.nrw.commons.actions.PageEditClient
- Direction
- category uses actions, so a change to actions can break category, while a change to category can't break actions.
- Position
- Below the diagonal: category uses a module listed above it, which is the healthy direction.
35→14 category uses upload.structure.depictions✕
- Connections
- 1 pair of types, where a type in category uses a type in upload.structure.depictions.
- The types involved
fr.free.nrw.commons.category.CategoriesModel→fr.free.nrw.commons.upload.structure.depictions.DepictedItem
- Direction
- category uses upload.structure.depictions, so a change to upload.structure.depictions can break category, while a change to category can't break upload.structure.depictions.
- Position
- Below the diagonal: category uses a module listed above it, which is the healthy direction.
35→18 category uses notification✕
- Connections
- 1 pair of types, where a type in category uses a type in notification.
- The types involved
fr.free.nrw.commons.category.CategoryEditHelper→fr.free.nrw.commons.notification.NotificationHelper
- Direction
- category uses notification, so a change to notification can break category, while a change to category can't break notification.
- Position
- Below the diagonal: category uses a module listed above it, which is the healthy direction.
35→20 category uses upload✕
- Connections
- 1 pair of types, where a type in category uses a type in upload.
- The types involved
fr.free.nrw.commons.category.CategoriesModel→fr.free.nrw.commons.upload.GpsCategoryModel
- Direction
- category uses upload, so a change to upload can break category, while a change to category can't break upload.
- Position
- Below the diagonal: category uses a module listed above it, which is the healthy direction.
35→21 category uses utils✕
- Connections
- 1 pair of types, where a type in category uses a type in utils.
- The types involved
fr.free.nrw.commons.category.CategoryEditHelper→fr.free.nrw.commons.utils.ViewUtilWrapper
- Direction
- category uses utils, so a change to utils can break category, while a change to category can't break utils.
- Position
- Below the diagonal: category uses a module listed above it, which is the healthy direction.
35→22 category uses theme✕
- Connections
- 1 pair of types, where a type in category uses a type in theme.
- The types involved
fr.free.nrw.commons.category.CategoryDetailsActivity→fr.free.nrw.commons.theme.BaseActivity
- Direction
- category uses theme, so a change to theme can break category, while a change to category can't break theme.
- Position
- Below the diagonal: category uses a module listed above it, which is the healthy direction.
35→34 category uses media✕
- Connections
- 2 pairs of types, where a type in category uses a type in media.
- The types involved
fr.free.nrw.commons.category.CategoryDetailsActivity→fr.free.nrw.commons.media.MediaDetailPagerFragmentfr.free.nrw.commons.category.CategoryDetailsActivity→fr.free.nrw.commons.media.MediaDetailProvider
- Direction
- category uses media, so a change to media can break category, while a change to category can't break media.
- Position
- Below the diagonal: category uses a module listed above it, which is the healthy direction.
35→38 category uses di part of a loop✕
- Connections
- 1 pair of types, where a type in category uses a type in di.
- The types involved
fr.free.nrw.commons.category.CategoryContentProvider→fr.free.nrw.commons.di.CommonsDaggerContentProvider
- Direction
- category uses di, so a change to di can break category, while a change to category can't break di.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
35→40 category uses fr.free.nrw.commons part of a loop✕
- Connections
- 6 pairs of types, where a type in category uses a type in fr.free.nrw.commons.
- The types involved
fr.free.nrw.commons.category.CategoriesModel→fr.free.nrw.commons.Mediafr.free.nrw.commons.category.CategoryDetailsActivity→fr.free.nrw.commons.Mediafr.free.nrw.commons.category.CategoryDetailsActivity→fr.free.nrw.commons.ViewPagerAdapterfr.free.nrw.commons.category.CategoryDetailsTabs→fr.free.nrw.commons.ViewPagerAdapterfr.free.nrw.commons.category.CategoryEditHelper→fr.free.nrw.commons.Mediafr.free.nrw.commons.category.GridViewAdapter→fr.free.nrw.commons.Media
- Direction
- category uses fr.free.nrw.commons, so a change to fr.free.nrw.commons can break category, while a change to category can't break fr.free.nrw.commons.
- 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.
36→3 bookmarks uses kvstore✕
- Connections
- 1 pair of types, where a type in bookmarks uses a type in kvstore.
- The types involved
fr.free.nrw.commons.bookmarks.BookmarkFragment→fr.free.nrw.commons.kvstore.JsonKvStore
- Direction
- bookmarks uses kvstore, so a change to kvstore can break bookmarks, while a change to bookmarks can't break kvstore.
- Position
- Below the diagonal: bookmarks uses a module listed above it, which is the healthy direction.
36→32 bookmarks uses contributions✕
- Connections
- 1 pair of types, where a type in bookmarks uses a type in contributions.
- The types involved
fr.free.nrw.commons.bookmarks.BookmarkFragment→fr.free.nrw.commons.contributions.ContributionController
- Direction
- bookmarks uses contributions, so a change to contributions can break bookmarks, while a change to bookmarks can't break contributions.
- Position
- Below the diagonal: bookmarks uses a module listed above it, which is the healthy direction.
36→34 bookmarks uses media✕
- Connections
- 2 pairs of types, where a type in bookmarks uses a type in media.
- The types involved
fr.free.nrw.commons.bookmarks.BookmarkListRootFragment→fr.free.nrw.commons.media.MediaDetailPagerFragmentfr.free.nrw.commons.bookmarks.BookmarkListRootFragment→fr.free.nrw.commons.media.MediaDetailProvider
- Direction
- bookmarks uses media, so a change to media can break bookmarks, while a change to bookmarks can't break media.
- Position
- Below the diagonal: bookmarks uses a module listed above it, which is the healthy direction.
36→35 bookmarks uses category✕
- Connections
- 1 pair of types, where a type in bookmarks uses a type in category.
- The types involved
fr.free.nrw.commons.bookmarks.BookmarkListRootFragment→fr.free.nrw.commons.category.CategoryImagesCallback
- Direction
- bookmarks uses category, so a change to category can break bookmarks, while a change to bookmarks can't break category.
- Position
- Below the diagonal: bookmarks uses a module listed above it, which is the healthy direction.
36→38 bookmarks uses di part of a loop✕
- Connections
- 2 pairs of types, where a type in bookmarks uses a type in di.
- The types involved
fr.free.nrw.commons.bookmarks.BookmarkFragment→fr.free.nrw.commons.di.CommonsDaggerSupportFragmentfr.free.nrw.commons.bookmarks.BookmarkListRootFragment→fr.free.nrw.commons.di.CommonsDaggerSupportFragment
- Direction
- bookmarks uses di, so a change to di can break bookmarks, while a change to bookmarks can't break di.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
36→40 bookmarks uses fr.free.nrw.commons part of a loop✕
- Connections
- 1 pair of types, where a type in bookmarks uses a type in fr.free.nrw.commons.
- The types involved
fr.free.nrw.commons.bookmarks.BookmarkListRootFragment→fr.free.nrw.commons.Media
- Direction
- bookmarks uses fr.free.nrw.commons, so a change to fr.free.nrw.commons can break bookmarks, while a change to bookmarks can't break fr.free.nrw.commons.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
37→4 db uses location✕
- Connections
- 1 pair of types, where a type in db uses a type in location.
- The types involved
fr.free.nrw.commons.db.Converters→fr.free.nrw.commons.location.LatLng
- Direction
- db uses location, so a change to location can break db, while a change to db can't break location.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
37→14 db uses upload.structure.depictions✕
- Connections
- 1 pair of types, where a type in db uses a type in upload.structure.depictions.
- The types involved
fr.free.nrw.commons.db.Converters→fr.free.nrw.commons.upload.structure.depictions.DepictedItem
- Direction
- db uses upload.structure.depictions, so a change to upload.structure.depictions can break db, while a change to db can't break upload.structure.depictions.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
37→19 db uses upload.depicts✕
- Connections
- 1 pair of types, where a type in db uses a type in upload.depicts.
- The types involved
fr.free.nrw.commons.db.AppDatabase→fr.free.nrw.commons.upload.depicts.DepictsDao
- Direction
- db uses upload.depicts, so a change to upload.depicts can break db, while a change to db can't break upload.depicts.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
37→20 db uses upload✕
- Connections
- 1 pair of types, where a type in db uses a type in upload.
- The types involved
fr.free.nrw.commons.db.Converters→fr.free.nrw.commons.upload.WikidataPlace
- Direction
- db uses upload, so a change to upload can break db, while a change to db can't break upload.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
37→25 db uses review✕
- Connections
- 1 pair of types, where a type in db uses a type in review.
- The types involved
fr.free.nrw.commons.db.AppDatabase→fr.free.nrw.commons.review.ReviewDao
- Direction
- db uses review, so a change to review can break db, while a change to db can't break review.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
37→29 db uses bookmarks.locations✕
- Connections
- 1 pair of types, where a type in db uses a type in bookmarks.locations.
- The types involved
fr.free.nrw.commons.db.AppDatabase→fr.free.nrw.commons.bookmarks.locations.BookmarkLocationsDao
- Direction
- db uses bookmarks.locations, so a change to bookmarks.locations can break db, while a change to db can't break bookmarks.locations.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
37→32 db uses contributions✕
- Connections
- 2 pairs of types, where a type in db uses a type in contributions.
- The types involved
fr.free.nrw.commons.db.AppDatabase→fr.free.nrw.commons.contributions.ContributionDaofr.free.nrw.commons.db.Converters→fr.free.nrw.commons.contributions.ChunkInfo
- Direction
- db uses contributions, so a change to contributions can break db, while a change to db can't break contributions.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
37→35 db uses category✕
- Connections
- 1 pair of types, where a type in db uses a type in category.
- The types involved
fr.free.nrw.commons.db.AppDatabase→fr.free.nrw.commons.category.CategoryRoomDao
- Direction
- db uses category, so a change to category can break db, while a change to db can't break category.
- Position
- Below the diagonal: db uses a module listed above it, which is the healthy direction.
37→40 db uses fr.free.nrw.commons part of a loop✕
- Connections
- 1 pair of types, where a type in db uses a type in fr.free.nrw.commons.
- The types involved
fr.free.nrw.commons.db.Converters→fr.free.nrw.commons.MediaType
- Direction
- db uses fr.free.nrw.commons, so a change to fr.free.nrw.commons can break db, while a change to db can't break fr.free.nrw.commons.
- 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.
38→3 di uses kvstore✕
- Connections
- 2 pairs of types, where a type in di uses a type in kvstore.
- The types involved
fr.free.nrw.commons.di.CommonsApplicationModule→fr.free.nrw.commons.kvstore.JsonKvStorefr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.kvstore.JsonKvStore
- Direction
- di uses kvstore, so a change to kvstore can break di, while a change to di can't break kvstore.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→4 di uses location✕
- Connections
- 1 pair of types, where a type in di uses a type in location.
- The types involved
fr.free.nrw.commons.di.CommonsApplicationModule→fr.free.nrw.commons.location.LocationServiceManager
- Direction
- di uses location, so a change to location can break di, while a change to di can't break location.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→6 di uses profile.leaderboard✕
- Connections
- 1 pair of types, where a type in di uses a type in profile.leaderboard.
- The types involved
fr.free.nrw.commons.di.FragmentBuilderModule→fr.free.nrw.commons.profile.leaderboard.LeaderboardFragment
- Direction
- di uses profile.leaderboard, so a change to profile.leaderboard can break di, while a change to di can't break profile.leaderboard.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→7 di uses wikidata.model✕
- Connections
- 1 pair of types, where a type in di uses a type in wikidata.model.
- The types involved
fr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.wikidata.model.WikiSite
- Direction
- di uses wikidata.model, so a change to wikidata.model can break di, while a change to di can't break wikidata.model.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→10 di uses auth.csrf✕
- Connections
- 3 pairs of types, where a type in di uses a type in auth.csrf.
- The types involved
fr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.auth.csrf.CsrfTokenClientfr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.auth.csrf.CsrfTokenInterfacefr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.auth.csrf.LogoutClient
- Direction
- di uses auth.csrf, so a change to auth.csrf can break di, while a change to di can't break auth.csrf.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→11 di uses explore.media✕
- Connections
- 1 pair of types, where a type in di uses a type in explore.media.
- The types involved
fr.free.nrw.commons.di.FragmentBuilderModule→fr.free.nrw.commons.explore.media.SearchMediaFragment
- Direction
- di uses explore.media, so a change to explore.media can break di, while a change to di can't break explore.media.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→12 di uses actions✕
- Connections
- 3 pairs of types, where a type in di uses a type in actions.
- The types involved
fr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.actions.PageEditClientfr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.actions.PageEditInterfacefr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.actions.ThanksInterface
- Direction
- di uses actions, so a change to actions can break di, while a change to di can't break actions.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→13 di uses wikidata✕
- Connections
- 3 pairs of types, where a type in di uses a type in wikidata.
- The types involved
fr.free.nrw.commons.di.CommonsApplicationModule→fr.free.nrw.commons.wikidata.WikidataEditListenerfr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.wikidata.CommonsServiceFactoryfr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.wikidata.WikidataInterface
- Direction
- di uses wikidata, so a change to wikidata can break di, while a change to di can't break wikidata.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→16 di uses upload.categories✕
- Connections
- 1 pair of types, where a type in di uses a type in upload.categories.
- The types involved
fr.free.nrw.commons.di.FragmentBuilderModule→fr.free.nrw.commons.upload.categories.UploadCategoriesFragment
- Direction
- di uses upload.categories, so a change to upload.categories can break di, while a change to di can't break upload.categories.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→17 di uses upload.mediaDetails✕
- Connections
- 1 pair of types, where a type in di uses a type in upload.mediaDetails.
- The types involved
fr.free.nrw.commons.di.FragmentBuilderModule→fr.free.nrw.commons.upload.mediaDetails.UploadMediaDetailFragment
- Direction
- di uses upload.mediaDetails, so a change to upload.mediaDetails can break di, while a change to di can't break upload.mediaDetails.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→18 di uses notification✕
- Connections
- 2 pairs of types, where a type in di uses a type in notification.
- The types involved
fr.free.nrw.commons.di.ActivityBuilderModule→fr.free.nrw.commons.notification.NotificationActivityfr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.notification.NotificationInterface
- Direction
- di uses notification, so a change to notification can break di, while a change to di can't break notification.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→19 di uses upload.depicts✕
- Connections
- 4 pairs of types, where a type in di uses a type in upload.depicts.
- The types involved
fr.free.nrw.commons.di.ActivityBuilderModule→fr.free.nrw.commons.upload.depicts.DepictsPickerActivityfr.free.nrw.commons.di.CommonsApplicationModule→fr.free.nrw.commons.upload.depicts.DepictsDaofr.free.nrw.commons.di.FragmentBuilderModule→fr.free.nrw.commons.upload.depicts.DepictsFragmentfr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.upload.depicts.DepictsInterface
- Direction
- di uses upload.depicts, so a change to upload.depicts can break di, while a change to di can't break upload.depicts.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→20 di uses upload✕
- Connections
- 8 pairs of types, where a type in di uses a type in upload.
- The types involved
fr.free.nrw.commons.di.ActivityBuilderModule→fr.free.nrw.commons.upload.UploadActivityfr.free.nrw.commons.di.ActivityBuilderModule→fr.free.nrw.commons.upload.UploadProgressActivityfr.free.nrw.commons.di.CommonsApplicationComponent→fr.free.nrw.commons.upload.FileProcessorfr.free.nrw.commons.di.CommonsApplicationModule→fr.free.nrw.commons.upload.UploadControllerfr.free.nrw.commons.di.FragmentBuilderModule→fr.free.nrw.commons.upload.FailedUploadsFragmentfr.free.nrw.commons.di.FragmentBuilderModule→fr.free.nrw.commons.upload.PendingUploadsFragmentfr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.upload.UploadInterfacefr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.upload.WikiBaseInterface
- Direction
- di uses upload, so a change to upload can break di, while a change to di can't break upload.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→21 di uses utils✕
- Connections
- 1 pair of types, where a type in di uses a type in utils.
- The types involved
fr.free.nrw.commons.di.CommonsApplicationModule→fr.free.nrw.commons.utils.TimeProvider
- Direction
- di uses utils, so a change to utils can break di, while a change to di can't break utils.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→23 di uses description✕
- Connections
- 1 pair of types, where a type in di uses a type in description.
- The types involved
fr.free.nrw.commons.di.ActivityBuilderModule→fr.free.nrw.commons.description.DescriptionEditActivity
- Direction
- di uses description, so a change to description can break di, while a change to di can't break description.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→24 di uses explore.depictions✕
- Connections
- 2 pairs of types, where a type in di uses a type in explore.depictions.
- The types involved
fr.free.nrw.commons.di.ActivityBuilderModule→fr.free.nrw.commons.explore.depictions.WikidataItemDetailsActivityfr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.explore.depictions.DepictsClient
- Direction
- di uses explore.depictions, so a change to explore.depictions can break di, while a change to di can't break explore.depictions.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→25 di uses review✕
- Connections
- 5 pairs of types, where a type in di uses a type in review.
- The types involved
fr.free.nrw.commons.di.ActivityBuilderModule→fr.free.nrw.commons.review.ReviewActivityfr.free.nrw.commons.di.CommonsApplicationComponent→fr.free.nrw.commons.review.ReviewControllerfr.free.nrw.commons.di.CommonsApplicationModule→fr.free.nrw.commons.review.ReviewDaofr.free.nrw.commons.di.FragmentBuilderModule→fr.free.nrw.commons.review.ReviewImageFragmentfr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.review.ReviewInterface
- Direction
- di uses review, so a change to review can break di, while a change to di can't break review.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→26 di uses mwapi✕
- Connections
- 3 pairs of types, where a type in di uses a type in mwapi.
- The types involved
fr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.mwapi.OkHttpJsonApiClientfr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.mwapi.UserInterfacefr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.mwapi.WikidataQueryClient
- Direction
- di uses mwapi, so a change to mwapi can break di, while a change to di can't break mwapi.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→27 di uses nearby✕
- Connections
- 1 pair of types, where a type in di uses a type in nearby.
- The types involved
fr.free.nrw.commons.di.ActivityBuilderModule→fr.free.nrw.commons.nearby.WikidataFeedback
- Direction
- di uses nearby, so a change to nearby can break di, while a change to di can't break nearby.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→28 di uses nearby.fragments✕
- Connections
- 1 pair of types, where a type in di uses a type in nearby.fragments.
- The types involved
fr.free.nrw.commons.di.FragmentBuilderModule→fr.free.nrw.commons.nearby.fragments.NearbyParentFragment
- Direction
- di uses nearby.fragments, so a change to nearby.fragments can break di, while a change to di can't break nearby.fragments.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→29 di uses bookmarks.locations✕
- Connections
- 2 pairs of types, where a type in di uses a type in bookmarks.locations.
- The types involved
fr.free.nrw.commons.di.CommonsApplicationModule→fr.free.nrw.commons.bookmarks.locations.BookmarkLocationsDaofr.free.nrw.commons.di.FragmentBuilderModule→fr.free.nrw.commons.bookmarks.locations.BookmarkLocationsFragment
- Direction
- di uses bookmarks.locations, so a change to bookmarks.locations can break di, while a change to di can't break bookmarks.locations.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→30 di uses explore.map✕
- Connections
- 1 pair of types, where a type in di uses a type in explore.map.
- The types involved
fr.free.nrw.commons.di.FragmentBuilderModule→fr.free.nrw.commons.explore.map.ExploreMapFragment
- Direction
- di uses explore.map, so a change to explore.map can break di, while a change to di can't break explore.map.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→31 di uses explore✕
- Connections
- 4 pairs of types, where a type in di uses a type in explore.
- The types involved
fr.free.nrw.commons.di.ActivityBuilderModule→fr.free.nrw.commons.explore.SearchActivityfr.free.nrw.commons.di.FragmentBuilderModule→fr.free.nrw.commons.explore.ExploreFragmentfr.free.nrw.commons.di.FragmentBuilderModule→fr.free.nrw.commons.explore.ExploreListRootFragmentfr.free.nrw.commons.di.FragmentBuilderModule→fr.free.nrw.commons.explore.ExploreMapRootFragment
- Direction
- di uses explore, so a change to explore can break di, while a change to di can't break explore.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→32 di uses contributions✕
- Connections
- 4 pairs of types, where a type in di uses a type in contributions.
- The types involved
fr.free.nrw.commons.di.ActivityBuilderModule→fr.free.nrw.commons.contributions.MainActivityfr.free.nrw.commons.di.CommonsApplicationModule→fr.free.nrw.commons.contributions.ContributionDaofr.free.nrw.commons.di.FragmentBuilderModule→fr.free.nrw.commons.contributions.ContributionsFragmentfr.free.nrw.commons.di.FragmentBuilderModule→fr.free.nrw.commons.contributions.ContributionsListFragment
- Direction
- di uses contributions, so a change to contributions can break di, while a change to di can't break contributions.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→33 di uses customselector.ui.selector✕
- Connections
- 4 pairs of types, where a type in di uses a type in customselector.ui.selector.
- The types involved
fr.free.nrw.commons.di.ActivityBuilderModule→fr.free.nrw.commons.customselector.ui.selector.CustomSelectorActivityfr.free.nrw.commons.di.CommonsApplicationModule→fr.free.nrw.commons.customselector.ui.selector.ImageFileLoaderfr.free.nrw.commons.di.FragmentBuilderModule→fr.free.nrw.commons.customselector.ui.selector.FolderFragmentfr.free.nrw.commons.di.FragmentBuilderModule→fr.free.nrw.commons.customselector.ui.selector.ImageFragment
- Direction
- di uses customselector.ui.selector, so a change to customselector.ui.selector can break di, while a change to di can't break customselector.ui.selector.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→34 di uses media✕
- Connections
- 8 pairs of types, where a type in di uses a type in media.
- The types involved
fr.free.nrw.commons.di.ActivityBuilderModule→fr.free.nrw.commons.media.DeletedFileActivityfr.free.nrw.commons.di.ActivityBuilderModule→fr.free.nrw.commons.media.ZoomableActivityfr.free.nrw.commons.di.FragmentBuilderModule→fr.free.nrw.commons.media.MediaDetailFragmentfr.free.nrw.commons.di.FragmentBuilderModule→fr.free.nrw.commons.media.MediaDetailPagerFragmentfr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.media.MediaDetailInterfacefr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.media.MediaInterfacefr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.media.PageMediaInterfacefr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.media.WikidataMediaInterface
- Direction
- di uses media, so a change to media can break di, while a change to di can't break media.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→35 di uses category✕
- Connections
- 3 pairs of types, where a type in di uses a type in category.
- The types involved
fr.free.nrw.commons.di.ActivityBuilderModule→fr.free.nrw.commons.category.CategoryDetailsActivityfr.free.nrw.commons.di.ContentProviderBuilderModule→fr.free.nrw.commons.category.CategoryContentProviderfr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.category.CategoryInterface
- Direction
- di uses category, so a change to category can break di, while a change to di can't break category.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→36 di uses bookmarks✕
- Connections
- 2 pairs of types, where a type in di uses a type in bookmarks.
- The types involved
fr.free.nrw.commons.di.FragmentBuilderModule→fr.free.nrw.commons.bookmarks.BookmarkFragmentfr.free.nrw.commons.di.FragmentBuilderModule→fr.free.nrw.commons.bookmarks.BookmarkListRootFragment
- Direction
- di uses bookmarks, so a change to bookmarks can break di, while a change to di can't break bookmarks.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→37 di uses db✕
- Connections
- 1 pair of types, where a type in di uses a type in db.
- The types involved
fr.free.nrw.commons.di.CommonsApplicationModule→fr.free.nrw.commons.db.AppDatabase
- Direction
- di uses db, so a change to db can break di, while a change to di can't break db.
- Position
- Below the diagonal: di uses a module listed above it, which is the healthy direction.
38→39 di uses auth part of a loop✕
- Connections
- 6 pairs of types, where a type in di uses a type in auth.
- The types involved
fr.free.nrw.commons.di.ActivityBuilderModule→fr.free.nrw.commons.auth.LoginActivityfr.free.nrw.commons.di.ActivityBuilderModule→fr.free.nrw.commons.auth.SignupActivityfr.free.nrw.commons.di.CommonsApplicationComponent→fr.free.nrw.commons.auth.LoginActivityfr.free.nrw.commons.di.CommonsApplicationModule→fr.free.nrw.commons.auth.SessionManagerfr.free.nrw.commons.di.NetworkingModule→fr.free.nrw.commons.auth.SessionManagerfr.free.nrw.commons.di.ServiceBuilderModule→fr.free.nrw.commons.auth.WikiAccountAuthenticatorService
- Direction
- di uses auth, so a change to auth can break di, while a change to di can't break auth.
- 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.
38→40 di uses fr.free.nrw.commons part of a loop✕
- Connections
- 3 pairs of types, where a type in di uses a type in fr.free.nrw.commons.
- The types involved
fr.free.nrw.commons.di.ActivityBuilderModule→fr.free.nrw.commons.AboutActivityfr.free.nrw.commons.di.ActivityBuilderModule→fr.free.nrw.commons.WelcomeActivityfr.free.nrw.commons.di.CommonsApplicationComponent→fr.free.nrw.commons.CommonsApplication
- Direction
- di uses fr.free.nrw.commons, so a change to fr.free.nrw.commons can break di, while a change to di can't break fr.free.nrw.commons.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
39→3 auth uses kvstore✕
- Connections
- 3 pairs of types, where a type in auth uses a type in kvstore.
- The types involved
fr.free.nrw.commons.auth.LoginActivity→fr.free.nrw.commons.kvstore.JsonKvStorefr.free.nrw.commons.auth.LoginViewModel→fr.free.nrw.commons.kvstore.JsonKvStorefr.free.nrw.commons.auth.SessionManager→fr.free.nrw.commons.kvstore.JsonKvStore
- Direction
- auth uses kvstore, so a change to kvstore can break auth, while a change to auth can't break kvstore.
- Position
- Below the diagonal: auth uses a module listed above it, which is the healthy direction.
39→21 auth uses utils✕
- Connections
- 1 pair of types, where a type in auth uses a type in utils.
- The types involved
fr.free.nrw.commons.auth.LoginActivity→fr.free.nrw.commons.utils.AbstractTextWatcher
- Direction
- auth uses utils, so a change to utils can break auth, while a change to auth can't break utils.
- Position
- Below the diagonal: auth uses a module listed above it, which is the healthy direction.
39→22 auth uses theme✕
- Connections
- 2 pairs of types, where a type in auth uses a type in theme.
- The types involved
fr.free.nrw.commons.auth.LoginActivity→fr.free.nrw.commons.theme.BaseActivityfr.free.nrw.commons.auth.SignupActivity→fr.free.nrw.commons.theme.BaseActivity
- Direction
- auth uses theme, so a change to theme can break auth, while a change to auth can't break theme.
- Position
- Below the diagonal: auth uses a module listed above it, which is the healthy direction.
39→38 auth uses di✕
- Connections
- 1 pair of types, where a type in auth uses a type in di.
- The types involved
fr.free.nrw.commons.auth.WikiAccountAuthenticatorService→fr.free.nrw.commons.di.CommonsDaggerService
- Direction
- auth uses di, so a change to di can break auth, while a change to auth can't break di.
- Position
- Below the diagonal: auth uses a module listed above it, which is the healthy direction.
40→3 fr.free.nrw.commons uses kvstore✕
- Connections
- 1 pair of types, where a type in fr.free.nrw.commons uses a type in kvstore.
- The types involved
fr.free.nrw.commons.CommonsApplication→fr.free.nrw.commons.kvstore.JsonKvStore
- Direction
- fr.free.nrw.commons uses kvstore, so a change to kvstore can break fr.free.nrw.commons, while a change to fr.free.nrw.commons can't break kvstore.
- Position
- Below the diagonal: fr.free.nrw.commons uses a module listed above it, which is the healthy direction.
40→4 fr.free.nrw.commons uses location✕
- Connections
- 2 pairs of types, where a type in fr.free.nrw.commons uses a type in location.
- The types involved
fr.free.nrw.commons.BaseMarker→fr.free.nrw.commons.location.LatLngfr.free.nrw.commons.Media→fr.free.nrw.commons.location.LatLng
- Direction
- fr.free.nrw.commons uses location, so a change to location can break fr.free.nrw.commons, while a change to fr.free.nrw.commons can't break location.
- Position
- Below the diagonal: fr.free.nrw.commons uses a module listed above it, which is the healthy direction.
40→22 fr.free.nrw.commons uses theme✕
- Connections
- 2 pairs of types, where a type in fr.free.nrw.commons uses a type in theme.
- The types involved
fr.free.nrw.commons.AboutActivity→fr.free.nrw.commons.theme.BaseActivityfr.free.nrw.commons.WelcomeActivity→fr.free.nrw.commons.theme.BaseActivity
- Direction
- fr.free.nrw.commons uses theme, so a change to theme can break fr.free.nrw.commons, while a change to fr.free.nrw.commons can't break theme.
- Position
- Below the diagonal: fr.free.nrw.commons uses a module listed above it, which is the healthy direction.
40→34 fr.free.nrw.commons uses media✕
- Connections
- 2 pairs of types, where a type in fr.free.nrw.commons uses a type in media.
- The types involved
fr.free.nrw.commons.CommonsApplication→fr.free.nrw.commons.media.CustomOkHttpNetworkFetcherfr.free.nrw.commons.MediaDataExtractor→fr.free.nrw.commons.media.MediaClient
- Direction
- fr.free.nrw.commons uses media, so a change to media can break fr.free.nrw.commons, while a change to fr.free.nrw.commons can't break media.
- Position
- Below the diagonal: fr.free.nrw.commons uses a module listed above it, which is the healthy direction.
40→37 fr.free.nrw.commons uses db✕
- Connections
- 1 pair of types, where a type in fr.free.nrw.commons uses a type in db.
- The types involved
fr.free.nrw.commons.CommonsApplication→fr.free.nrw.commons.db.AppDatabase
- Direction
- fr.free.nrw.commons uses db, so a change to db can break fr.free.nrw.commons, while a change to fr.free.nrw.commons can't break db.
- Position
- Below the diagonal: fr.free.nrw.commons uses a module listed above it, which is the healthy direction.
40→39 fr.free.nrw.commons uses auth✕
- Connections
- 1 pair of types, where a type in fr.free.nrw.commons uses a type in auth.
- The types involved
fr.free.nrw.commons.CommonsApplication→fr.free.nrw.commons.auth.SessionManager
- Direction
- fr.free.nrw.commons uses auth, so a change to auth can break fr.free.nrw.commons, while a change to fr.free.nrw.commons can't break auth.
- Position
- Below the diagonal: fr.free.nrw.commons 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 | 24 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
Roadmap
Top priorities: 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; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts; 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. | +6.3 pts | Low | ADR Quality |
| 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. | +6.3 pts | Medium | Security & performance tooling |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +6.2 pts | Medium | Architecture documentation |
| Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry). | +4.2 pts | Medium | Outbound HTTP resilience |
| Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with SettingsFragment.kt. | +1.7 pts | Low | Knowledge Freshness |
| Resolve the 2 `defaultKVStore` spells `KV` where 48 names in the project spell it `Kv` finding(s) in Naming Consistency — start with ContributionsLocalDataSource.kt, MediaLicensePresenter.kt. | +1.4 pts | Low | Naming Consistency |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +2.7 pts | Medium | Documentation (README) |
| Resolve the 1 `getAPILevel` spells `API` where 19 names in the project spell it `Api` finding(s) in Naming Consistency — start with DeviceInfoUtil.kt. | +0.7 pts | Low | Naming Consistency |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| app/src/main/java/fr/free/nrw/commons/upload/UploadMediaDetailAdapter.kt | 5.6 | Mixed | Cognitive Complexity: UploadMediaDetailAdapter.updateAddButtonVisibility (cognitive 30) |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| app/src/main/java/fr/free/nrw/commons/wikidata/model/page/PageTitle.kt | 6.4 | Mixed | Explicit Debt: TodoComment |
| app/src/main/java/fr/free/nrw/commons/auth/login/LoginClient.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| app/src/main/java/fr/free/nrw/commons/wikidata/mwapi/MwQueryResult.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| app/src/main/java/fr/free/nrw/commons/profile/achievements/AchievementsFragment.kt | 6.7 | Mixed | Explicit Debt: TodoComment |
| app/src/main/java/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt | 7.0 | Mixed | Cyclomatic Complexity: NearbyParentFragment.filterMarkersByLabels (cyclomatic 21) |
| app/src/main/java/fr/free/nrw/commons/mwapi/OkHttpJsonApiClient.kt | 7.0 | Mixed | Cognitive Complexity: OkHttpJsonApiClient.getNearbyPlaces (cognitive 23) |
| app/src/main/java/fr/free/nrw/commons/customselector/ui/selector/ImageLoader.kt | 7.1 | Mixed | Cyclomatic Complexity: ImageLoader.queryAndSetView (cyclomatic 31) |
| app/src/main/java/fr/free/nrw/commons/edit/BlurOverlayView.kt | 7.1 | Mixed | Cyclomatic Complexity: BlurOverlayView.onTouchEvent (cyclomatic 26) |
| app/src/main/java/fr/free/nrw/commons/media/MediaDetailFragment.kt | 7.1 | Mixed | Cognitive Complexity: MediaDetailFragmentKt.FileUsagesContainer (cognitive 18) |
| app/src/main/java/fr/free/nrw/commons/media/ZoomableActivity.kt | 7.1 | Mixed | God Classes: ClassTooLong: ZoomableActivity |
| app/src/main/java/fr/free/nrw/commons/bookmarks/items/BookmarkItemsContentProvider.kt | 7.1 | Mixed | Code Duplication: Edited copy of a member (18 corresponding lines) |
| app/src/main/java/fr/free/nrw/commons/media/MediaDetailPagerFragment.kt | 7.2 | Mixed | Cyclomatic Complexity: MediaDetailPagerFragment.onOptionsItemSelected (cyclomatic 17) |
| app/src/main/java/fr/free/nrw/commons/nearby/NearbyController.java | 7.2 | Mixed | Cognitive Complexity: NearbyController.loadAttractionsFromLocation (cognitive 29) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 52 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 52 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 340 of 352 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 3 Maven/Gradle manifest(s) were read, stating a version for 96 dependency(ies) and leaving 11 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- 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.
- 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 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — 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.
- D26 Project Cohesion — 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` (71250 LoC, 1368 module-visible types across 100 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- 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/fr/free/nrw/commons/auth/LoginViewModel.kt`, `app/src/main/java/fr/free/nrw/commons/category/CategoryDetailsViewModel.kt`, `app/src/main/java/fr/free/nrw/commons/contributions/WikipediaInstructionsDialogFragment.kt`, `app/src/main/java/fr/free/nrw/commons/filepicker/FilePicker.kt`, `app/src/main/java/fr/free/nrw/commons/kvstore/BasicKvStore.kt`, … (+12 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.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Boot via AndroidApp (app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: FAILURE: Build failed with an exception. * Where: Build file 'app/build.gradle.kts' line: 551 * What went wrong: /tmp/codehealth-iso-44e865ad41f1…; runtime evidence skipped (launch chosen because app/build.gradle.kts applies the Android application plugin and gradlew builds it).
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- 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.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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.
- 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 ImageLoader.queryAndSetView at 31.
What to do
- Bring the 6 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ImageLoader.queryAndSetView (cyclomatic 31), BlurOverlayView.onTouchEvent (cyclomatic 26), NearbyParentFragment.filterMarkersByLabels (cyclomatic 21). — 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.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
29 method(s) exceeded the cognitive complexity threshold of 15; the worst was ImageLoader.queryAndSetView at 46.
What to do
- Bring the 29 bodies over 15 down to 15 or less in Cognitive Complexity — start with ImageLoader.queryAndSetView (cognitive 46), BlurOverlayView.onTouchEvent (cognitive 44), UploadProgressActivity.updateMenuItems (cognitive 38). — 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 29 together lifts Cognitive Complexity from 6.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
23 god class(es) detected.
What to do
- Resolve the 10 MethodTooLong finding(s) in God Classes — start with NearbyParentFragment.kt (2), MediaDetailFragment.kt (2), BlurOverlayView.kt. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 8 TooManyMethods finding(s) in God Classes — start with NearbyParentFragment.kt, DefaultZoomableController.kt, FragmentBuilderModule.kt. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 3 ClassTooLong finding(s) in God Classes — start with NearbyParentFragment.kt, ZoomableActivity.kt, UploadMediaDetailAdapter.kt. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
48 duplicated block group(s) detected. 5.3 % of the production lines (3,744 of 71,250) are in a reported copy. A further 66 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 5 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with RandomAccessFileExifWriter.kt, MediaResponseMapper.kt, MwQueryResult.kt. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 5 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with DepictsClient.kt, MediaResponseMapper.kt, FailedUploadsAdapter.kt. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with GestureTransform.kt, MediaDetailImage.kt, Place.java. — One of this dimension's main actionable groups (4 warning-level).
D5 · Coupling
2 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; 0 module(s) off the main sequence, with abstractness counted on 1 of the 2 (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).
D6 · Cohesion (LCOM4)
2 of 238 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with MediaDetailMenuHandler.kt, UploadMediaDetailAdapter.kt. — One of this dimension's main actionable groups (2 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 56 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 3 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. 11 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 40 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/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt (22×17=374); app/src/main/java/fr/free/nrw/commons/media/MediaDetailPagerFragment.kt (7×17=119); app/src/main/java/fr/free/nrw/commons/edit/BlurOverlayView.kt (3×26=78) Repeated repair below the complexity floor: app/src/main/java/fr/free/nrw/commons/media/MediaDetailFragment.kt (10 of 17 changes were fixes); app/src/main/java/fr/free/nrw/commons/auth/LoginActivity.kt (7 of 9 changes were fixes); app/src/main/java/fr/free/nrw/commons/filepicker/FilePicker.kt (6 of 8 changes were fixes)
What to do
- Resolve the 17 Repeated repair finding(s) in Churn × Complexity Hotspots — start with MediaDetailFragment.kt, LoginActivity.kt, FilePicker.kt. — One of this dimension's main actionable groups (17 warning-level).
- Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with NearbyParentFragment.kt, MediaDetailPagerFragment.kt, BlurOverlayView.kt. — One of this dimension's main actionable groups (3 warning-level).
D16 · Bus Factor
10 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is app/src/main/java/fr/free/nrw/commons/repository/UploadRepository.kt. Counted over 339 of the 691 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
23 deducted task-comment markers across 71250 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 20 TodoComment finding(s) in Explicit Debt — start with PageTitle.kt (3), CommonsApplication.kt (2), ContributionsFragment.kt (2). — One of this dimension's main actionable groups (20 warning-level).
- Resolve the 3 FixmeComment finding(s) in Explicit Debt — start with SearchActivity.kt (2), RecentSearchesDao.kt. — One of this dimension's main actionable groups (3 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
D21 · Naming Consistency
5 naming inconsistencies among 119 declarations measured against a convention their peers follow.
What to do
- Resolve the 2 `defaultKVStore` spells `KV` where 48 names in the project spell it `Kv` finding(s) in Naming Consistency — start with ContributionsLocalDataSource.kt, MediaLicensePresenter.kt. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 `getMediaFromImageURL` spells `URL` where 54 names in the project spell… finding(s) in Naming Consistency — start with ExploreMapMarkerOverlayHelper.kt. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 `getAPILevel` spells `API` where 19 names in the project spell it `Api` finding(s) in Naming Consistency — start with DeviceInfoUtil.kt. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
24 finding(s): 0 critical, 22 high, 2 medium, 0 low. 19 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `gradlew` (lines 144–145, line 146, line 147, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 19 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (19 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
56 of 339 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/fr/free/nrw/commons/settings/SettingsFragment.kt. Counted over 339 of the 691 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with SettingsFragment.kt. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 55 Orphaned file finding(s) in Knowledge Freshness — start with ImageLoader.kt, NearbyController.java, DepictsPresenter.kt. — One of this dimension's main actionable groups (55 recommendation-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 96 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
AX2 · Stateful singletons
- `SessionManager` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (password, _currentAccount; e.g. `password` in `updateAccount` at line 52). — app/src/main/java/fr/free/nrw/commons/auth/SessionManager.kt:21
- `BookmarkPicturesController` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (currentBookmarks; e.g. `currentBookmarks` in `loadBookmarkedPictures` at line 24). — app/src/main/java/fr/free/nrw/commons/bookmarks/pictures/BookmarkPicturesController.kt:12
- `CampaignsPresenter` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (view, disposable, campaign; e.g. `view` in `onAttachView` at line 36). — app/src/main/java/fr/free/nrw/commons/campaigns/CampaignsPresenter.kt:25
- `ContributionController` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (locationPermissionCallback, locationPermissionsHelper, locationBeforeImageCapture, isInAppCameraUpload, isInternalUploadInProgress; e.g. `locationPermissionCallback` in `createDialogsAndHandleLocationPermissions` at line 120). — app/src/main/java/fr/free/nrw/commons/contributions/ContributionController.kt:44
- `DeleteHelper` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (d; e.g. `d` in `askReasonAndExecute` at line 213). — app/src/main/java/fr/free/nrw/commons/delete/DeleteHelper.kt:41
- `QuizChecker` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (totalUploadCount, isUploadCountFetched, revertCount, isRevertCountFetched; e.g. `totalUploadCount` in `setTotalUploadCount` at line 80). — app/src/main/java/fr/free/nrw/commons/quiz/QuizChecker.kt:27
- `ReviewController` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (media; e.g. `media` in `onImageRefreshed` at line 64). — app/src/main/java/fr/free/nrw/commons/review/ReviewController.kt:29
- `UploadModel` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (items, selectedCategories, selectedDepictions, selectedExistingDepictions; e.g. `items` in `cleanUp` at line 65). — app/src/main/java/fr/free/nrw/commons/upload/UploadModel.kt:24
- `UploadPresenter` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (basicKvStoreFactory, view; e.g. `basicKvStoreFactory` in `setupBasicKvStoreFactory` at line 149). — app/src/main/java/fr/free/nrw/commons/upload/UploadPresenter.kt:26
- `CategoriesPresenter` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (view, media; e.g. `view` in `onAttachView` at line 58). — app/src/main/java/fr/free/nrw/commons/upload/categories/CategoriesPresenter.kt:29
- `DepictsPresenter` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (view, media; e.g. `view` in `onAttachView` at line 62). — app/src/main/java/fr/free/nrw/commons/upload/depicts/DepictsPresenter.kt:33
- `NearbyPlaces` is a singleton (@Singleton: the container shares one instance across every request thread) but mutates instance state outside any lock (radius; e.g. `radius` in `radiusExpander` at line 59). — app/src/main/java/fr/free/nrw/commons/nearby/NearbyPlaces.java:26
What to do
- Java/Kotlin: keep container singletons stateless — move per-request data into locals or a request-scoped bean — or back the state with java.util.concurrent types (ConcurrentHashMap, AtomicInteger/AtomicReference), guard it with synchronized / a Lock (Kotlin: withLock), or mark a flag that is only ever overwritten volatile (@Volatile).
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `View` declares 45 abstract methods: `addCurrentLocationMarker`, `animateFABs`, `askForLocationPermission`, `centerMapToPlace`, `clearAllMarkers`, `disableFABRecenter`, `displayLoginSkippedWarning`, `enableFABRecenter`, `filterMarkersByLabels`, `filterOutAllMarkers`, `getCameraTarget`, `getContext`, `getLastLocation`, `getLastMapFocus`, `getMapCenter`, `getMapFocus`, `getScreenBottomLeft`, `getScreenTopRight`, `hideBottomDetailsSheet`, `hideBottomSheet`, `hideNearbyFilterList`, `isAdvancedQueryFragmentVisible`, `isDetailsBottomSheetVisible`, `isListBottomSheetExpanded`, `isNearbyFilterListVisible`, `isNetworkConnectionEstablished`, `listOptionMenuItemClicked`, `openLocationSettings`, `populatePlaces`, `populatePlaces`, `recenterMap`, `replaceMarkerOverlays`, `setBottomSheetDetailsSmaller`, `setCheckBoxAction`, `setCheckBoxState`, `setFABPlusAction`, `setFABRecenterAction`, `setFilterState`, `setProgressBarVisibility`, `setRecyclerViewAdapterAllSelected`, and 5 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 45 declarations carry 44 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 44 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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/fr/free/nrw/commons/nearby/contract/NearbyParentFragmentContract.java:17
- `ActivityBuilderModule` declares 22 abstract methods: `bindLoginActivity`, `bindWelcomeActivity`, `bindContributionsActivity`, `bindCustomSelectorActivity`, `bindSettingsActivity`, `bindAboutActivity`, `bindLocationPickerActivity`, `bindSignupActivity`, `bindNotificationActivity`, `bindUploadActivity`, `bindDepictsPickerActivity`, `bindSearchActivity`, `bindCategoryDetailsActivity`, `bindDepictionDetailsActivity`, `bindAchievementsActivity`, `bindReviewActivity`, `bindDescriptionEditActivity`, `bindZoomableActivity`, `bindUploadProgressActivity`, `bindWikiFeedback`, `bindEditActivity`, `bindDeletedFileActivity`. 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/fr/free/nrw/commons/di/ActivityBuilderModule.kt:37
- `FragmentBuilderModule` declares 39 abstract methods: `bindContributionsListFragment`, `bindMediaDetailFragment`, `bindFolderFragment`, `bindImageFragment`, `bindMediaDetailPagerFragment`, `bindSettingsFragment`, `bindDepictedImagesFragment`, `bindBrowseImagesListFragment`, `bindSearchCategoryListFragment`, `bindSearchDepictionListFragment`, `bindRecentSearchesFragment`, `bindContributionsFragment`, `bindNearbyParentFragment`, `bindBookmarkPictureListFragment`, `bindBookmarkLocationListFragment`, `bindBookmarkItemListFragment`, `bindBookmarkCategoriesListFragment`, `bindReviewOutOfContextFragment`, `bindUploadMediaDetailFragment`, `bindUploadCategoriesFragment`, `bindDepictsFragment`, `bindMediaLicenseFragment`, `bindParentDepictionsFragment`, `bindChildDepictionsFragment`, `bindCategoriesMediaFragment`, `bindSubCategoriesFragment`, `bindParentCategoriesFragment`, `bindExploreFragmentFragment`, `bindExploreFeaturedRootFragment`, `bindExploreNearbyUploadsFragment`, `bindExploreNearbyUploadsRootFragment`, `bindBookmarkListRootFragment`, `bindBookmarkFragmentFragment`, `bindMoreBottomSheetFragment`, `bindMoreBottomSheetLoggedOutFragment`, `bindAchievementsFragment`, `bindLeaderboardFragment`, `bindPendingUploadsFragment`, `bindFailedUploadsFragment`. 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/fr/free/nrw/commons/di/FragmentBuilderModule.kt:54
- `ZoomableController` declares 16 abstract methods: `setEnabled`, `isEnabled`, `setListener`, `getScaleFactor`, `isIdentity`, `wasTransformCorrected`, `computeHorizontalScrollRange`, `computeHorizontalScrollOffset`, `computeHorizontalScrollExtent`, `computeVerticalScrollRange`, `computeVerticalScrollOffset`, `computeVerticalScrollExtent`, `getTransform`, `setImageBounds`, `setViewBounds`, `onTouchEvent`. 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/fr/free/nrw/commons/media/zoomControllers/zoomable/ZoomableController.kt:11
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P2 · Observability
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 9 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:3
- `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:359
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
P7 · Outbound HTTP resilience
- `.openConnection(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — app/src/main/java/fr/free/nrw/commons/media/MediaDetailPagerFragment.kt:373
What to do
- Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 0/2 suspend functions that make a cancellable request (Ktor, OkHttp newCall, URL streams) accept the coroutine's cancellation or pass one on, so a request keeps running after whatever wanted it has given up — a screen navigated away from, a disposed widget, a superseded search. In a suspend function, make the request with a call that suspends — Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` that cancels the `Call` — not a blocking `execute()`: `withContext(Dispatchers.IO)` moves the call off the caller's thread but does not make it cancellable; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `getFileUsagesOnCommons` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. — app/src/main/java/fr/free/nrw/commons/mwapi/OkHttpJsonApiClient.kt:87
- `getGlobalFileUsages` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. — app/src/main/java/fr/free/nrw/commons/mwapi/OkHttpJsonApiClient.kt:123
What to do
- Thread the coroutine's cancellation through suspend functions that make requests, so the work stops when its caller gives up.
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `catch (ignored: 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. — app/src/main/java/fr/free/nrw/commons/customselector/ui/selector/ImageFileLoader.kt:167
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
X5 · Nullable reference types
- ~18.5 `!!` not-null assertions per 1k Kotlin product lines — 1435 across the 77547 line(s) of the 672 Kotlin file(s) read (generated, test and sample code not counted). Densest: app/src/main/java/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt (298), app/src/main/java/fr/free/nrw/commons/contributions/ContributionsListFragment.kt (45), app/src/main/java/fr/free/nrw/commons/explore/SearchActivity.kt (43). Each one tells the compiler to trust the author about null and becomes a `NullPointerException` the first time the author is wrong. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- Replace `!!` rather than adding to it: each is a run-time null check the compiler could not prove. Narrow the value with a null check, an early return or `?: return`, use `?.` / `?:` where absence is legitimate, `requireNotNull(x) { "why" }` / `checkNotNull` where a missing value is a contract breach worth a message, make the property non-nullable and set it in the constructor (or `by lazy`) instead of `lateinit` plus `!!`, or change the API so the null cannot arrive.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 70.4 | Strong | Solid. |
| Architecture | 82.3 | Strong | Solid. |
| Maturity | 51.1 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 48.5 | Weak — gated by P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 75.7 | Adequate — gated by D36 | 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
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 13 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 60 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.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the Android app did not build — `./gradlew :app:assembleDebug` exited 1: FAILURE: Build failed with an exception. * Where: Build file 'app/build.gradle.kts' line: 551 * What went wrong: /tmp/codehealth-iso-44e865ad41f1…; runtime evidence skipped (launch chosen because app/build.gradle.kts applies the Android application plugin and gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~36561 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
- D12 Dependency Hygiene — Not scored — 3 Maven/Gradle manifest(s) were read, stating a version for 96 dependency(ies) and leaving 11 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .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
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 17 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 96 value object(s); 3 repository port(s) loading or saving an aggregate/entity
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks. 5 claim(s) of kinds M4 does not check were not checked (path 3, environment variable 2); M4 checks only links and versions and artefact counts.
- 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
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — X24 reached only 3% of this repository's production lines — kotlin (69,034 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 23 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge app/src/main/java/fr/free/nrw/commons/settings/SettingsFragment.kt:1
Serious — 239 finding(s)
- TodoComment app/src/main/java/fr/free/nrw/commons/CommonsApplication.kt:137
- TodoComment app/src/main/java/fr/free/nrw/commons/CommonsApplication.kt:257
- TodoComment app/src/main/java/fr/free/nrw/commons/Media.kt:216
- TodoComment app/src/main/java/fr/free/nrw/commons/wikidata/mwapi/MwQueryPage.kt:54
- TodoComment app/src/main/java/fr/free/nrw/commons/wikidata/mwapi/MwQueryResult.kt:66
- TodoComment app/src/main/java/fr/free/nrw/commons/wikidata/model/WikiSite.kt:51
- TodoComment app/src/main/java/fr/free/nrw/commons/wikidata/model/page/PageTitle.kt:59
- TodoComment app/src/main/java/fr/free/nrw/commons/wikidata/model/page/PageTitle.kt:194
- TodoComment app/src/main/java/fr/free/nrw/commons/wikidata/model/page/PageTitle.kt:304
- TodoComment app/src/main/java/fr/free/nrw/commons/utils/ConfigUtils.kt:8
- TodoComment app/src/main/java/fr/free/nrw/commons/utils/NetworkUtils.kt:50
- TodoComment app/src/main/java/fr/free/nrw/commons/review/ReviewController.kt:51
- TodoComment app/src/main/java/fr/free/nrw/commons/profile/achievements/AchievementsFragment.kt:135
- TodoComment app/src/main/java/fr/free/nrw/commons/profile/achievements/AchievementsStatsBinder.kt:137
- TodoComment app/src/main/java/fr/free/nrw/commons/feedback/FeedbackDialog.kt:46
- TodoComment app/src/main/java/fr/free/nrw/commons/customselector/ui/selector/FolderFragment.kt:76
- TodoComment app/src/main/java/fr/free/nrw/commons/customselector/ui/selector/ImageFragment.kt:160
- TodoComment app/src/main/java/fr/free/nrw/commons/contributions/ContributionsFragment.kt:293
- TodoComment app/src/main/java/fr/free/nrw/commons/contributions/ContributionsFragment.kt:306
- TodoComment app/src/main/java/fr/free/nrw/commons/auth/login/LoginClient.kt:322
- Repeated repair: app/src/main/java/fr/free/nrw/commons/media/MediaDetailFragment.kt app/src/main/java/fr/free/nrw/commons/media/MediaDetailFragment.kt:595
- Repeated repair: app/src/main/java/fr/free/nrw/commons/auth/LoginActivity.kt app/src/main/java/fr/free/nrw/commons/auth/LoginActivity.kt:119
- Repeated repair: app/src/main/java/fr/free/nrw/commons/filepicker/FilePicker.kt app/src/main/java/fr/free/nrw/commons/filepicker/FilePicker.kt:69
- Repeated repair: app/src/main/java/fr/free/nrw/commons/description/DescriptionEditActivity.kt app/src/main/java/fr/free/nrw/commons/description/DescriptionEditActivity.kt:188
- Repeated repair: app/src/main/java/fr/free/nrw/commons/customselector/ui/selector/ImageFragment.kt app/src/main/java/fr/free/nrw/commons/customselector/ui/selector/ImageFragment.kt:259
- Repeated repair: app/src/main/java/fr/free/nrw/commons/upload/PendingUploadsPresenter.kt app/src/main/java/fr/free/nrw/commons/upload/PendingUploadsPresenter.kt:174
- Repeated repair: app/src/main/java/fr/free/nrw/commons/delete/DeleteHelper.kt app/src/main/java/fr/free/nrw/commons/delete/DeleteHelper.kt:213
- Repeated repair: app/src/main/java/fr/free/nrw/commons/utils/CustomSelectorUtils.kt app/src/main/java/fr/free/nrw/commons/utils/CustomSelectorUtils.kt:81
- Repeated repair: app/src/main/java/fr/free/nrw/commons/media/zoomControllers/zoomable/ZoomableDraweeView.kt app/src/main/java/fr/free/nrw/commons/media/zoomControllers/zoomable/ZoomableDraweeView.kt:231
- Repeated repair: app/src/main/java/fr/free/nrw/commons/navtab/MoreBottomSheetFragment.kt app/src/main/java/fr/free/nrw/commons/navtab/MoreBottomSheetFragment.kt:50
- Repeated repair: app/src/main/java/fr/free/nrw/commons/contributions/ContributionsLocalDataSource.kt app/src/main/java/fr/free/nrw/commons/contributions/ContributionsLocalDataSource.kt:92
- Repeated repair: app/src/main/java/fr/free/nrw/commons/contributions/ContributionsRepository.kt app/src/main/java/fr/free/nrw/commons/contributions/ContributionsRepository.kt:22
- Repeated repair: app/src/main/java/fr/free/nrw/commons/contributions/ContributionsListPresenter.kt app/src/main/java/fr/free/nrw/commons/contributions/ContributionsListPresenter.kt:37
- Repeated repair: app/src/main/java/fr/free/nrw/commons/utils/DownloadReceiver.kt app/src/main/java/fr/free/nrw/commons/utils/DownloadReceiver.kt:31
- Repeated repair: app/src/main/java/fr/free/nrw/commons/notification/NotificationClient.kt app/src/main/java/fr/free/nrw/commons/notification/NotificationClient.kt:52
- Repeated repair: app/src/main/java/fr/free/nrw/commons/utils/RandomAccessFileExifWriter.kt app/src/main/java/fr/free/nrw/commons/utils/RandomAccessFileExifWriter.kt:241
- Repeated repair: app/src/main/java/fr/free/nrw/commons/navtab/MoreBottomSheetLoggedOutFragment.kt app/src/main/java/fr/free/nrw/commons/navtab/MoreBottomSheetLoggedOutFragment.kt:106
- Stateful singleton: SessionManager app/src/main/java/fr/free/nrw/commons/auth/SessionManager.kt:21
- Stateful singleton: BookmarkPicturesController app/src/main/java/fr/free/nrw/commons/bookmarks/pictures/BookmarkPicturesController.kt:12
- Stateful singleton: CampaignsPresenter app/src/main/java/fr/free/nrw/commons/campaigns/CampaignsPresenter.kt:25
- Stateful singleton: ContributionController app/src/main/java/fr/free/nrw/commons/contributions/ContributionController.kt:44
- Stateful singleton: DeleteHelper app/src/main/java/fr/free/nrw/commons/delete/DeleteHelper.kt:41
- Stateful singleton: QuizChecker app/src/main/java/fr/free/nrw/commons/quiz/QuizChecker.kt:27
- Stateful singleton: ReviewController app/src/main/java/fr/free/nrw/commons/review/ReviewController.kt:29
- Stateful singleton: UploadModel app/src/main/java/fr/free/nrw/commons/upload/UploadModel.kt:24
- Stateful singleton: UploadPresenter app/src/main/java/fr/free/nrw/commons/upload/UploadPresenter.kt:26
- Stateful singleton: CategoriesPresenter app/src/main/java/fr/free/nrw/commons/upload/categories/CategoriesPresenter.kt:29
- Stateful singleton: DepictsPresenter app/src/main/java/fr/free/nrw/commons/upload/depicts/DepictsPresenter.kt:33
- Stateful singleton: NearbyPlaces app/src/main/java/fr/free/nrw/commons/nearby/NearbyPlaces.java:26
- MethodTooLong: NearbyParentFragment.onViewCreated app/src/main/java/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt:462
- MethodTooLong: NearbyParentFragment.passInfoToSheet app/src/main/java/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt:2716
- MethodTooLong: BlurOverlayView.onTouchEvent app/src/main/java/fr/free/nrw/commons/edit/BlurOverlayView.kt:311
- MethodTooLong: MediaDetailFragment.onCreateView app/src/main/java/fr/free/nrw/commons/media/MediaDetailFragment.kt:231
- MethodTooLong: ViewHolder.initLanguage app/src/main/java/fr/free/nrw/commons/upload/UploadMediaDetailAdapter.kt:315
- MethodTooLong: UploadWorker.uploadContribution app/src/main/java/fr/free/nrw/commons/upload/worker/UploadWorker.kt:263
- MethodTooLong: MediaDetailFragmentKt.FileUsagesContainer app/src/main/java/fr/free/nrw/commons/media/MediaDetailFragment.kt:595
- MethodTooLong: MediaDetailPagerFragment.onCreateOptionsMenu app/src/main/java/fr/free/nrw/commons/media/MediaDetailPagerFragment.kt:327
- MethodTooLong: SettingsFragment.onCreatePreferences app/src/main/java/fr/free/nrw/commons/settings/SettingsFragment.kt:110
- MethodTooLong: ImageLoader.queryAndSetView app/src/main/java/fr/free/nrw/commons/customselector/ui/selector/ImageLoader.kt:73
- TooManyMethods: NearbyParentFragment app/src/main/java/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt:155
- TooManyMethods: DefaultZoomableController app/src/main/java/fr/free/nrw/commons/media/zoomControllers/zoomable/DefaultZoomableController.kt:12
- TooManyMethods: FragmentBuilderModule app/src/main/java/fr/free/nrw/commons/di/FragmentBuilderModule.kt:54
- TooManyMethods: ZoomableDraweeView app/src/main/java/fr/free/nrw/commons/media/zoomControllers/zoomable/ZoomableDraweeView.kt:36
- TooManyMethods: NetworkingModule app/src/main/java/fr/free/nrw/commons/di/NetworkingModule.kt:57
- TooManyMethods: LoginActivity app/src/main/java/fr/free/nrw/commons/auth/LoginActivity.kt:57
- TooManyMethods: CommonsApplicationModule app/src/main/java/fr/free/nrw/commons/di/CommonsApplicationModule.kt:56
- TooManyMethods: DepictsFragment app/src/main/java/fr/free/nrw/commons/upload/depicts/DepictsFragment.kt:50
- Edited copy of a member (14 corresponding lines) app/src/main/java/fr/free/nrw/commons/utils/RandomAccessFileExifWriter.kt:122
- Edited copy of a member (14 corresponding lines) app/src/main/java/fr/free/nrw/commons/media/MediaResponseMapper.kt:30
- Edited copy of a member (14 corresponding lines) app/src/main/java/fr/free/nrw/commons/wikidata/mwapi/MwQueryResult.kt:59
- Edited copy of a member (14 corresponding lines) app/src/main/java/fr/free/nrw/commons/upload/worker/UploadNotificationHelper.kt:253
- Edited copy of a member (14 corresponding lines) app/src/main/java/fr/free/nrw/commons/upload/categories/CategoryEditView.kt:72
- Duplicated block (5 lines × 2) app/src/main/java/fr/free/nrw/commons/explore/depictions/DepictsClient.kt:115
- Duplicated block (5 lines × 2) app/src/main/java/fr/free/nrw/commons/media/MediaResponseMapper.kt:23
- Duplicated block (5 lines × 2) app/src/main/java/fr/free/nrw/commons/upload/FailedUploadsAdapter.kt:44
- Duplicated block (5 lines × 2) app/src/main/java/fr/free/nrw/commons/mwapi/UserStatsClient.kt:123
- Duplicated block (5 lines × 2) app/src/main/java/fr/free/nrw/commons/upload/FailedUploadsFragment.kt:152
- Edited copy of a member (11 corresponding lines) app/src/main/java/fr/free/nrw/commons/media/zoomControllers/gestures/GestureTransform.kt:32
- Edited copy of a member (11 corresponding lines) app/src/main/java/fr/free/nrw/commons/media/MediaDetailImage.kt:149
- Edited copy of a member (11 corresponding lines) app/src/main/java/fr/free/nrw/commons/nearby/Place.java:62
- Edited copy of a member (11 corresponding lines) app/src/main/java/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt:1480
- Edited copy of a member (22 corresponding lines) app/src/main/java/fr/free/nrw/commons/settings/SettingsFragment.kt:438
- Edited copy of a member (22 corresponding lines) app/src/main/java/fr/free/nrw/commons/upload/depicts/DepictsPresenter.kt:62
- Edited copy of a member (22 corresponding lines) app/src/main/java/fr/free/nrw/commons/upload/categories/UploadCategoriesFragment.kt:157
- Edited copy of a member (22 corresponding lines) app/src/main/java/fr/free/nrw/commons/media/MediaReportHelper.kt:70
- Hotspot: app/src/main/java/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt app/src/main/java/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt:462
- Hotspot: app/src/main/java/fr/free/nrw/commons/media/MediaDetailPagerFragment.kt app/src/main/java/fr/free/nrw/commons/media/MediaDetailPagerFragment.kt:180
- Hotspot: app/src/main/java/fr/free/nrw/commons/edit/BlurOverlayView.kt app/src/main/java/fr/free/nrw/commons/edit/BlurOverlayView.kt:311
- FixmeComment app/src/main/java/fr/free/nrw/commons/explore/SearchActivity.kt:153
- FixmeComment app/src/main/java/fr/free/nrw/commons/explore/SearchActivity.kt:155
- FixmeComment app/src/main/java/fr/free/nrw/commons/explore/recentsearches/RecentSearchesDao.kt:159
- ClassTooLong: NearbyParentFragment app/src/main/java/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt:155
- ClassTooLong: ZoomableActivity app/src/main/java/fr/free/nrw/commons/media/ZoomableActivity.kt:61
- ClassTooLong: UploadMediaDetailAdapter app/src/main/java/fr/free/nrw/commons/upload/UploadMediaDetailAdapter.kt:41
- Edited copy of a member (18 corresponding lines) app/src/main/java/fr/free/nrw/commons/media/MediaDetailCategories.kt:133
- Edited copy of a member (18 corresponding lines) app/src/main/java/fr/free/nrw/commons/location/LocationPermissionsHelper.kt:106
- Edited copy of a member (18 corresponding lines) app/src/main/java/fr/free/nrw/commons/bookmarks/items/BookmarkItemsContentProvider.kt:59
- Edited copy of a member (12 corresponding lines) app/src/main/java/fr/free/nrw/commons/language/AppLanguageLookUpTable.kt:59
- Edited copy of a member (12 corresponding lines) app/src/main/java/fr/free/nrw/commons/media/MediaDetailCategories.kt:88
- Edited copy of a member (12 corresponding lines) app/src/main/java/fr/free/nrw/commons/quiz/QuizChecker.kt:63
- Edited copy of a member (7 corresponding lines) app/src/main/java/fr/free/nrw/commons/navtab/MoreBottomSheetLoggedOutFragment.kt:129
- Edited copy of a member (7 corresponding lines) app/src/main/java/fr/free/nrw/commons/navtab/MoreBottomSheetLoggedOutFragment.kt:137
- Edited copy of a member (7 corresponding lines) app/src/main/java/fr/free/nrw/commons/media/MediaCollectionClient.kt:84
- Duplicated block (14 lines × 2) app/src/main/java/fr/free/nrw/commons/category/CategoryDao.kt:65
- Duplicated block (14 lines × 2) app/src/main/java/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt:1713
- Duplicated block (14 lines × 2) app/src/main/java/fr/free/nrw/commons/di/CommonsDaggerIntentService.kt:9
- Duplicated block (13 lines × 2) app/src/main/java/fr/free/nrw/commons/bookmarks/pictures/BookmarkPicturesDao.kt:94
- Duplicated block (13 lines × 2) app/src/main/java/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt:1686
- Duplicated block (13 lines × 2) app/src/main/java/fr/free/nrw/commons/bookmarks/items/BookmarkItemsContentProvider.kt:64
- Duplicated block (12 lines × 2) app/src/main/java/fr/free/nrw/commons/upload/PendingUploadsPresenter.kt:184
- Duplicated block (12 lines × 2) app/src/main/java/fr/free/nrw/commons/upload/UploadProgressActivity.kt:126
- Duplicated block (12 lines × 2) app/src/main/java/fr/free/nrw/commons/bookmarks/items/BookmarkItemsContentProvider.kt:34
- Duplicated block (11 lines × 2) app/src/main/java/fr/free/nrw/commons/edit/CropOverlayView.kt:314
- Duplicated block (11 lines × 2) app/src/main/java/fr/free/nrw/commons/mwapi/OkHttpJsonApiClient.kt:243
- Duplicated block (11 lines × 2) app/src/main/java/fr/free/nrw/commons/recentlanguages/RecentLanguagesAdapter.kt:39
- Duplicated block (9 lines × 2) app/src/main/java/fr/free/nrw/commons/upload/UploadMediaDetailAdapter.kt:570
- Duplicated block (9 lines × 2) app/src/main/java/fr/free/nrw/commons/upload/UploadMediaDetailAdapter.kt:582
- Duplicated block (9 lines × 2) app/src/main/java/fr/free/nrw/commons/nearby/Place.java:63
- Duplicated block (6 lines × 2) app/src/main/java/fr/free/nrw/commons/MediaDataExtractor.kt:29
- Duplicated block (6 lines × 2) app/src/main/java/fr/free/nrw/commons/profile/leaderboard/DataSourceClass.kt:40
- Duplicated block (6 lines × 2) app/src/main/java/fr/free/nrw/commons/bookmarks/items/BookmarkItemsContentProvider.kt:84
- NearbyController.loadAttractionsFromLocation (cognitive 29) app/src/main/java/fr/free/nrw/commons/nearby/NearbyController.java:50
- NearbyController.loadAttractionsFromLocation (cognitive 29) app/src/main/java/fr/free/nrw/commons/nearby/NearbyController.java:186
- FileTooLong: fragments/NearbyParentFragment.kt app/src/main/java/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt
- FileTooLong: media/MediaDetailFragment.kt app/src/main/java/fr/free/nrw/commons/media/MediaDetailFragment.kt
- Edited copy of a member (49 corresponding lines) app/src/main/java/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt:1925
- Edited copy of a member (49 corresponding lines) app/src/main/java/fr/free/nrw/commons/mwapi/OkHttpJsonApiClient.kt:327
- Edited copy of a member (33 corresponding lines) app/src/main/java/fr/free/nrw/commons/bookmarks/BookmarkListNavigator.kt:29
- Edited copy of a member (33 corresponding lines) app/src/main/java/fr/free/nrw/commons/media/ZoomableActivity.kt:455
- Edited copy of a member (21 corresponding lines) app/src/main/java/fr/free/nrw/commons/upload/FailedUploadsFragment.kt:142
- Edited copy of a member (21 corresponding lines) app/src/main/java/fr/free/nrw/commons/contributions/ContributionViewHolder.kt:113
- Edited copy of a member (28 corresponding lines) app/src/main/java/fr/free/nrw/commons/recentlanguages/RecentLanguagesAdapter.kt:38
- Edited copy of a member (28 corresponding lines) app/src/main/java/fr/free/nrw/commons/mwapi/UserStatsClient.kt:33
- Edited copy of a member (19 corresponding lines) app/src/main/java/fr/free/nrw/commons/upload/PendingUploadsFragment.kt:119
- Edited copy of a member (19 corresponding lines) app/src/main/java/fr/free/nrw/commons/nearby/presenter/NearbyPlaceDetailsLoader.kt:316
- Edited copy of a member (24 corresponding lines) app/src/main/java/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt:930
- Edited copy of a member (24 corresponding lines) app/src/main/java/fr/free/nrw/commons/media/MediaDetailDeletion.kt:162
- Edited copy of a member (15 corresponding lines) app/src/main/java/fr/free/nrw/commons/upload/categories/CategorySearchView.kt:28
- Edited copy of a member (15 corresponding lines) app/src/main/java/fr/free/nrw/commons/category/CategoryDao.kt:26
- Edited copy of a member (16 corresponding lines) app/src/main/java/fr/free/nrw/commons/category/CategoryContentProvider.kt:98
- Edited copy of a member (16 corresponding lines) app/src/main/java/fr/free/nrw/commons/profile/achievements/AchievementsFragment.kt:255
- Edited copy of a member (8 corresponding lines) app/src/main/java/fr/free/nrw/commons/MediaDataExtractor.kt:27
- Edited copy of a member (8 corresponding lines) app/src/main/java/fr/free/nrw/commons/description/DescriptionEditActivity.kt:143
- Edited copy of a member (13 corresponding lines) app/src/main/java/fr/free/nrw/commons/AboutLinkHandler.kt:20
- Edited copy of a member (13 corresponding lines) app/src/main/java/fr/free/nrw/commons/contributions/SetWallpaperWorker.kt:86
- Edited copy of a member (10 corresponding lines) app/src/main/java/fr/free/nrw/commons/upload/license/LicenseAdapter.kt:84
- Edited copy of a member (10 corresponding lines) app/src/main/java/fr/free/nrw/commons/bookmarks/items/BookmarkItemsDao.kt:101
- Duplicated block (10 lines × 2) app/src/main/java/fr/free/nrw/commons/settings/SettingsFragment.kt:405
- Duplicated block (10 lines × 2) app/src/main/java/fr/free/nrw/commons/bookmarks/items/BookmarkItemsDao.kt:86
- Low cohesion: MediaDetailMenuHandler (LCOM4 4) app/src/main/java/fr/free/nrw/commons/media/MediaDetailMenuHandler.kt:29
- Low cohesion: UploadMediaDetailAdapter (LCOM4 4) app/src/main/java/fr/free/nrw/commons/upload/UploadMediaDetailAdapter.kt:41
- Suspend function with a blocking request: getFileUsagesOnCommons app/src/main/java/fr/free/nrw/commons/mwapi/OkHttpJsonApiClient.kt:87
- Suspend function with a blocking request: getGlobalFileUsages app/src/main/java/fr/free/nrw/commons/mwapi/OkHttpJsonApiClient.kt:123
- ImageLoader.queryAndSetView (cyclomatic 31) app/src/main/java/fr/free/nrw/commons/customselector/ui/selector/ImageLoader.kt:73
- BlurOverlayView.onTouchEvent (cyclomatic 26) app/src/main/java/fr/free/nrw/commons/edit/BlurOverlayView.kt:311
- NearbyParentFragment.filterMarkersByLabels (cyclomatic 21) app/src/main/java/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt:2353
- MediaDetailPagerFragment.onOptionsItemSelected (cyclomatic 17) app/src/main/java/fr/free/nrw/commons/media/MediaDetailPagerFragment.kt:180
- NearbyParentFragment.onViewCreated (cyclomatic 17) app/src/main/java/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt:462
- BlurOverlayView.onDraw (cyclomatic 16) app/src/main/java/fr/free/nrw/commons/edit/BlurOverlayView.kt:191
- ImageLoader.queryAndSetView (cognitive 46) app/src/main/java/fr/free/nrw/commons/customselector/ui/selector/ImageLoader.kt:73
- BlurOverlayView.onTouchEvent (cognitive 44) app/src/main/java/fr/free/nrw/commons/edit/BlurOverlayView.kt:311
- UploadProgressActivity.updateMenuItems (cognitive 38) app/src/main/java/fr/free/nrw/commons/upload/UploadProgressActivity.kt:109
- MediaDetailPagerFragment.onCreateOptionsMenu (cognitive 37) app/src/main/java/fr/free/nrw/commons/media/MediaDetailPagerFragment.kt:327
- NearbyParentFragment.filterMarkersByLabels (cognitive 31) app/src/main/java/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt:2353
- UploadMediaDetailAdapter.updateAddButtonVisibility (cognitive 30) app/src/main/java/fr/free/nrw/commons/upload/UploadMediaDetailAdapter.kt:566
- NearbyParentFragment.onViewCreated (cognitive 24) app/src/main/java/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt:462
- NearbyPlaces.getFromWikidataQuery (cognitive 24) app/src/main/java/fr/free/nrw/commons/nearby/NearbyPlaces.java:127
- OkHttpJsonApiClient.getNearbyPlaces (cognitive 23) app/src/main/java/fr/free/nrw/commons/mwapi/OkHttpJsonApiClient.kt:233
- UploadWorker.uploadContribution (cognitive 23) app/src/main/java/fr/free/nrw/commons/upload/worker/UploadWorker.kt:263
- RandomAccessFileExifWriter.scanAndUpdateIfd (cognitive 21) app/src/main/java/fr/free/nrw/commons/utils/RandomAccessFileExifWriter.kt:241
- ViewHolder.initLanguage (cognitive 20) app/src/main/java/fr/free/nrw/commons/upload/UploadMediaDetailAdapter.kt:315
- UploadModel.onDepictItemClicked (cognitive 20) app/src/main/java/fr/free/nrw/commons/upload/UploadModel.kt:195
- UploadActivity.onRequestPermissionsResult (cognitive 19) app/src/main/java/fr/free/nrw/commons/upload/UploadActivity.kt:249
- ImageLoader.nextActionableImage (cognitive 18) app/src/main/java/fr/free/nrw/commons/customselector/ui/selector/ImageLoader.kt:243
- MediaDetailFragmentKt.FileUsagesContainer (cognitive 18) app/src/main/java/fr/free/nrw/commons/media/MediaDetailFragment.kt:595
- LoginClient.login (cognitive 17) app/src/main/java/fr/free/nrw/commons/auth/login/LoginClient.kt:85
- GestureListener.onFling (cognitive 17) app/src/main/java/fr/free/nrw/commons/customselector/helper/OnSwipeTouchListener.kt:55
- ImageAdapter.onBindViewHolder (cognitive 17) app/src/main/java/fr/free/nrw/commons/customselector/ui/adapter/ImageAdapter.kt:141
- BlurOverlayView.onDraw (cognitive 17) app/src/main/java/fr/free/nrw/commons/edit/BlurOverlayView.kt:191
- NearbyParentFragment.getIconFor (cognitive 17) app/src/main/java/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt:2442
- RandomAccessFileExifWriter.writeTagsInternal (cognitive 17) app/src/main/java/fr/free/nrw/commons/utils/RandomAccessFileExifWriter.kt:192
- ExploreMapViewportHelper.recenterMap (cognitive 16) app/src/main/java/fr/free/nrw/commons/explore/map/ExploreMapViewportHelper.kt:149
- NearbyPlaceDetailsLoader.fetchPlacesThreadMethod (cognitive 16) app/src/main/java/fr/free/nrw/commons/nearby/presenter/NearbyPlaceDetailsLoader.kt:191
- DownloadReceiver.getFailedDownload (cognitive 16) app/src/main/java/fr/free/nrw/commons/utils/DownloadReceiver.kt:31
- ImageUtils.checkIfImageIsDark (cognitive 16) app/src/main/java/fr/free/nrw/commons/utils/ImageUtils.kt:185
- ImageUtils.getErrorMessageForResult (cognitive 16) app/src/main/java/fr/free/nrw/commons/utils/ImageUtils.kt:377
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (5 members, 50+ identical tokens) app/src/main/java/fr/free/nrw/commons/mwapi/OkHttpJsonApiClient.kt:192
- Edited copy of a member (68 corresponding lines) app/src/main/java/fr/free/nrw/commons/nearby/NearbyController.java:53
- Edited copy of a member (53 corresponding lines) app/src/main/java/fr/free/nrw/commons/utils/EdgeToEdgeUtils.kt:29
- Edited copy of a member (66 corresponding lines) app/src/main/java/fr/free/nrw/commons/media/ZoomableActivity.kt:312
- Edited copy of a member (47 corresponding lines) app/src/main/java/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt:1680
- Edited copy of a member (35 corresponding lines) app/src/main/java/fr/free/nrw/commons/category/CategoryEditHelper.kt:100
- Edited copy of a member (34 corresponding lines) app/src/main/java/fr/free/nrw/commons/media/MediaDetailCaptionEditor.kt:93
- Edited copies of one member (3 members, 28+ corresponding lines) app/src/main/java/fr/free/nrw/commons/mwapi/OkHttpJsonApiClient.kt:90
- Edited copy of a member (23 corresponding lines) app/src/main/java/fr/free/nrw/commons/profile/leaderboard/DataSourceClass.kt:31
- Edited copy of a member (36 corresponding lines) app/src/main/java/fr/free/nrw/commons/media/MediaDetailActions.kt:102
- Edited copy of a member (30 corresponding lines) app/src/main/java/fr/free/nrw/commons/media/MediaDetailViewModel.kt:33
- Edited copy of a member (27 corresponding lines) app/src/main/java/fr/free/nrw/commons/category/CategoryContentProvider.kt:122
- Edited copies of one member (3 members, 13+ corresponding lines) app/src/main/java/fr/free/nrw/commons/filepicker/FilePicker.kt:73
- Edited copies of one member (3 members, 25+ corresponding lines) app/src/main/java/fr/free/nrw/commons/delete/DeleteHelper.kt:177
- Edited copy of a member (17 corresponding lines) app/src/main/java/fr/free/nrw/commons/upload/mediaDetails/UploadMediaMetadataController.kt:53
- Edited copies of one member (5 members, 22+ corresponding lines) app/src/main/java/fr/free/nrw/commons/bookmarks/pictures/BookmarkPicturesDao.kt:31
- Edited copies of one member (3 members, 18+ corresponding lines) app/src/main/java/fr/free/nrw/commons/upload/worker/UploadNotificationHelper.kt:138
- Edited copies of one member (4 members, 21+ corresponding lines) app/src/main/java/fr/free/nrw/commons/bookmarks/items/BookmarkItemsDao.kt:117
- Edited copies of one member (5 members, 10+ corresponding lines) app/src/main/java/fr/free/nrw/commons/actions/PageEditClient.kt:32
- Edited copy of a member (9 corresponding lines) app/src/main/java/fr/free/nrw/commons/actions/PageEditClient.kt:199
- Edited copies of one member (3 members, 10+ corresponding lines) app/src/main/java/fr/free/nrw/commons/bookmarks/items/BookmarkItemsContentProvider.kt:98
- Edited copy of a member (1 corresponding lines) app/src/main/java/fr/free/nrw/commons/explore/depictions/DepictsClient.kt:107
- Duplicated block (69 lines × 2) app/src/main/java/fr/free/nrw/commons/media/MediaDetailFragment.kt:613
- Duplicated block (39 lines × 2) app/src/main/java/fr/free/nrw/commons/media/ZoomableActivity.kt:535
- Duplicated block (31 lines × 2) app/src/main/java/fr/free/nrw/commons/customselector/ui/selector/ImageLoader.kt:132
- Duplicated block (29–31 lines × 2) app/src/main/java/fr/free/nrw/commons/media/ZoomableActivity.kt:326
- Duplicated block (24–26 lines × 2) app/src/main/java/fr/free/nrw/commons/mwapi/OkHttpJsonApiClient.kt:332
- Duplicated block (26 lines × 2) app/src/main/java/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt:1926
- Duplicated block (25 lines × 2) app/src/main/java/fr/free/nrw/commons/media/MediaDetailPagerFragment.kt:398
- Duplicated block (19–22 lines × 2) app/src/main/java/fr/free/nrw/commons/bookmarks/pictures/BookmarksTable.kt:38
- Duplicated block (20 lines × 2) app/src/main/java/fr/free/nrw/commons/upload/depicts/DepictsPresenter.kt:64
- Duplicated block (17 lines × 2) app/src/main/java/fr/free/nrw/commons/bookmarks/category/BookmarkCategoriesFragment.kt:55
- Duplicated block (9–15 lines × 4) app/src/main/java/fr/free/nrw/commons/mwapi/OkHttpJsonApiClient.kt:207
- Duplicated block (14–15 lines × 2) app/src/main/java/fr/free/nrw/commons/nearby/fragments/NearbyParentFragment.kt:931
- Duplicated block (15 lines × 2) app/src/main/java/fr/free/nrw/commons/upload/SimilarImageDialogFragment.kt:43
- Duplicated block (11–12 lines × 2) app/src/main/java/fr/free/nrw/commons/contributions/ContributionViewHolder.kt:116
- Duplicated block (10–11 lines × 2) app/src/main/java/fr/free/nrw/commons/mwapi/OkHttpJsonApiClient.kt:204
- Duplicated block (7–8 lines × 3) app/src/main/java/fr/free/nrw/commons/mwapi/OkHttpJsonApiClient.kt:100
- Duplicated block (6 lines × 3) app/src/main/java/fr/free/nrw/commons/mwapi/OkHttpJsonApiClient.kt:218
- Duplicated block (7 lines × 2) app/src/main/java/fr/free/nrw/commons/media/zoomControllers/gestures/GestureTransform.kt:32
- Duplicated block (40 lines × 2) app/src/main/java/fr/free/nrw/commons/bookmarks/items/BookmarkItemsTable.kt:55
- Duplicated block (16 lines × 2) app/src/main/java/fr/free/nrw/commons/mwapi/UserStatsClient.kt:37
- Duplicated block (7 lines × 3) app/src/main/java/fr/free/nrw/commons/actions/PageEditClient.kt:35
- Duplicated block (8 lines × 2) app/src/main/java/fr/free/nrw/commons/upload/UploadClient.kt:250
- Duplicated block (57–58 lines × 2) app/src/main/java/fr/free/nrw/commons/nearby/NearbyController.java:63
- Coverage collected but not gated
- Outbound HTTP without resilience app/src/main/java/fr/free/nrw/commons/media/MediaDetailPagerFragment.kt:373
- Swallowed exception (caught, then discarded) app/src/main/java/fr/free/nrw/commons/customselector/ui/selector/ImageFileLoader.kt:167
Minor — 90 finding(s)
- Orphaned file app/src/main/java/fr/free/nrw/commons/customselector/ui/selector/ImageLoader.kt:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/nearby/NearbyController.java:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/upload/depicts/DepictsPresenter.kt:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/upload/PendingUploadsAdapter.kt:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/utils/PermissionUtils.kt:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/nearby/NearbyPlaces.java:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/activity/SingleWebViewActivity.kt:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/nearby/NearbyNotificationCardView.java:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/di/FragmentBuilderModule.kt:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/auth/csrf/CsrfTokenClient.kt:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/upload/LanguagesAdapter.kt:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/nearby/PageEditHelper.java:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/widget/PicOfDayAppWidget.kt:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/upload/PendingUploadsFragment.kt:1
- Orphaned file jacoco.gradle:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/nearby/PlaceAdapterDelegate.kt:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/category/CategoryClient.kt:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/nearby/fragments/CommonPlaceClickActions.kt:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/explore/recentsearches/RecentSearchesFragment.kt:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/wikidata/model/page/PageProperties.kt:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/bookmarks/locations/BookmarkLocationsFragment.kt:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/review/ReviewHelper.kt:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/description/DescriptionEditHelper.kt:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/explore/media/MediaConverter.kt:1
- Orphaned file app/src/main/java/fr/free/nrw/commons/contributions/ContributionBoundaryCallback.kt:1
- Duplicated predicate app/src/main/java/fr/free/nrw/commons/contributions/ContributionsFragmentRenderer.kt:79
- Duplicated predicate app/src/main/java/fr/free/nrw/commons/profile/achievements/AchievementsFragment.kt:258
- Duplicated predicate app/src/main/java/fr/free/nrw/commons/auth/LoginActivity.kt:371
- Duplicated predicate app/src/main/java/fr/free/nrw/commons/category/CategoryDao.kt:98
- Duplicated predicate app/src/main/java/fr/free/nrw/commons/contributions/ContributionsFragmentRenderer.kt:68
- Duplicated predicate app/src/main/java/fr/free/nrw/commons/contributions/ContributionsFragmentRenderer.kt:74
- Duplicated predicate app/src/main/java/fr/free/nrw/commons/contributions/ContributionsNavigator.kt:133
- Duplicated predicate app/src/main/java/fr/free/nrw/commons/recentlanguages/RecentLanguagesAdapter.kt:29
- Duplicated predicate app/src/main/java/fr/free/nrw/commons/explore/map/ExploreMapFragment.kt:128
- Duplicated predicate app/src/main/java/fr/free/nrw/commons/explore/ExploreListRootFragment.kt:83
- Duplicated predicate app/src/main/java/fr/free/nrw/commons/explore/map/ExploreMapViewportHelper.kt:81
- Duplicated predicate app/src/main/java/fr/free/nrw/commons/profile/leaderboard/DataSourceClass.kt:44
- Duplicated predicate app/src/main/java/fr/free/nrw/commons/mwapi/OkHttpJsonApiClient.kt:67
- Fat interface: View (45 abstract methods) app/src/main/java/fr/free/nrw/commons/nearby/contract/NearbyParentFragmentContract.java:17
- Fat interface: ActivityBuilderModule (22 abstract methods) app/src/main/java/fr/free/nrw/commons/di/ActivityBuilderModule.kt:37
- Fat interface: FragmentBuilderModule (39 abstract methods) app/src/main/java/fr/free/nrw/commons/di/FragmentBuilderModule.kt:54
- Fat interface: ZoomableController (16 abstract methods) app/src/main/java/fr/free/nrw/commons/media/zoomControllers/zoomable/ZoomableController.kt:11
- `defaultKVStore` spells `KV` where 48 names in the project spell it `Kv` app/src/main/java/fr/free/nrw/commons/contributions/ContributionsLocalDataSource.kt:16
- `defaultKVStore` spells `KV` where 48 names in the project spell it `Kv` app/src/main/java/fr/free/nrw/commons/upload/license/MediaLicensePresenter.kt:18
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found app/build.gradle.kts:5
- `getMediaFromImageURL` spells `URL` where 54 names in the project spell it `Url` app/src/main/java/fr/free/nrw/commons/explore/map/ExploreMapMarkerOverlayHelper.kt:321
- `getAPILevel` spells `API` where 19 names in the project spell it `Api` app/src/main/java/fr/free/nrw/commons/utils/DeviceInfoUtil.kt:62
- `decodeURL` spells `URL` where 54 names in the project spell it `Url` app/src/main/java/fr/free/nrw/commons/wikidata/model/page/PageTitle.kt:138
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:3
- No dependency-update automation app/build.gradle.kts:359
- Not all suspend functions that make a request accept the coroutine's cancellation
- Not-null assertions (`!!`) override null safety
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-ad0ca7c9056748a38a9bca4daf561172/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-ad0ca7c9056748a38a9bca4daf561172/history-1.json --exit-code 0 --source . | 0 | 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=3200" --report-format json --report-path /tmp/watchdog-gitleaks-ad0ca7c9056748a38a9bca4daf561172/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=4200 --max-count=3023" --report-format json --report-path /tmp/watchdog-gitleaks-ad0ca7c9056748a38a9bca4daf561172/history-3.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-3.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-ad0ca7c9056748a38a9bca4daf561172/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 . | 24 | 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 17 file(s) — `app/src/main/java/fr/free/nrw/commons/auth/LoginViewModel.kt`, `app/src/main/java/fr/free/nrw/commons/category/CategoryDetailsViewModel.kt`, `app/src/main/java/fr/free/nrw/commons/contributions/WikipediaInstructionsDialogFragment.kt`, `app/src/main/java/fr/free/nrw/commons/filepicker/FilePicker.kt`, `app/src/main/java/fr/free/nrw/commons/kvstore/BasicKvStore.kt`, … (+12 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | 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 | — |