Executive summary
mikepenz/FastAdapter falls short of our standard for production because 79 files are no longer known to anyone active in the project and the project keeps no record of its design decisions. It scores 57 out of 100 and is rated Adequate, and all 21 of its critical findings are security problems in the build pipeline.
Maturity, at 44, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 12 points. Having someone learn and document the 79 files no active contributor knows comes next, also worth about 12. Raising Maturity to 70 would lift the score to about 68.
Eighteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three secrets can leak from the build pipeline. Pinning each tool to an exact version and limiting each secret to its own step would close both risks.
The product code is 14,040 lines, about €15,000 to rebuild.
If Maturity rose from 44 to 70, the lowest score rated Strong, the score would rise from 57 to about 68.
New since the last survey: 1 finding
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 1 finding
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €15,000 · Estimate
| Cost to rebuild | €5,100 to €25,000, for 84 to 268 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 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 | Small: 14,040 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 app.items.expandable.SimpleSubExpandableItem | 2 drag | 3 swipe.SimpleSwipeCallback | 4 swipe.SimpleSwipeDrawerCallback | 5 ui.utils | 6 extensions | 7 listeners | 8 swipe | 9 expandable | 10 select | 11 swipe_drag | 12 utils | 13 FastAdapter | 14 com.mikepenz.fastadapter | 15 app.items.SimpleItem | 16 helpers.UndoHelper | 17 IAdapterNotifier | 18 adapters | 19 app.items.CheckBoxSampleItem | 20 app.items.ImageItem | 21 app.items.RadioButtonSampleItem | 22 diff | 23 items | 24 paged | 25 app.adapters | 26 app.model | 27 binding | 28 dsl | 29 expandable.items | 30 helpers | 31 scroll.EndlessScrollHelper | 32 ui.dialog | 33 ui.items | 34 app.binding | 35 app.items.SwipeableDrawerItem | 36 app.items.SwipeableItem | 37 app.items.expandable | 38 scroll | 39 app.items | 40 app |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 app.items.expandable.SimpleSubExpandableItem | ||||||||||||||||||||||||||||||||||||||||
| 2 drag | ||||||||||||||||||||||||||||||||||||||||
| 3 swipe.SimpleSwipeCallback | ||||||||||||||||||||||||||||||||||||||||
| 4 swipe.SimpleSwipeDrawerCallback | ||||||||||||||||||||||||||||||||||||||||
| 5 ui.utils | ||||||||||||||||||||||||||||||||||||||||
| 6 extensions | 5 | |||||||||||||||||||||||||||||||||||||||
| 7 listeners | 11 | |||||||||||||||||||||||||||||||||||||||
| 8 swipe | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 expandable | 1 | 8 | ||||||||||||||||||||||||||||||||||||||
| 10 select | 1 | 6 | ||||||||||||||||||||||||||||||||||||||
| 11 swipe_drag | 4 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 12 utils | 1 | 1 | 1 | 11 | ||||||||||||||||||||||||||||||||||||
| 13 FastAdapter | 2 | 5 | ||||||||||||||||||||||||||||||||||||||
| 14 com.mikepenz.fastadapter | 7 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 15 app.items.SimpleItem | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 helpers.UndoHelper | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 IAdapterNotifier | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 adapters | 1 | 2 | 9 | |||||||||||||||||||||||||||||||||||||
| 19 app.items.CheckBoxSampleItem | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 app.items.ImageItem | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 21 app.items.RadioButtonSampleItem | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 diff | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 items | 7 | |||||||||||||||||||||||||||||||||||||||
| 24 paged | 1 | 7 | ||||||||||||||||||||||||||||||||||||||
| 25 app.adapters | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 app.model | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 binding | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 dsl | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 29 expandable.items | 9 | 2 | ||||||||||||||||||||||||||||||||||||||
| 30 helpers | 1 | 1 | 3 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 31 scroll.EndlessScrollHelper | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 ui.dialog | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 33 ui.items | 6 | 4 | ||||||||||||||||||||||||||||||||||||||
| 34 app.binding | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 app.items.SwipeableDrawerItem | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 app.items.SwipeableItem | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 app.items.expandable | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 38 scroll | 2 | 3 | 3 | |||||||||||||||||||||||||||||||||||||
| 39 app.items | 1 | 4 | 5 | 1 | 2 | 8 | 1 | 1 | 1 | 1 | 13 | 1 | 1 | 1 | ||||||||||||||||||||||||||
| 40 app | 10 | 1 | 1 | 2 | 1 | 6 | 1 | 17 | 17 | 1 | 1 | 5 | 1 | 14 |
6→14 extensions uses com.mikepenz.fastadapter part of a loop✕
- Connections
- 5 pairs of types, where a type in extensions uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.extensions.ExtensionFactory→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.extensions.ExtensionFactory→com.mikepenz.fastadapter.IItemcom.mikepenz.fastadapter.extensions.ExtensionsFactories→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.extensions.ExtensionsFactories→com.mikepenz.fastadapter.IAdapterExtensioncom.mikepenz.fastadapter.extensions.ExtensionsFactories→com.mikepenz.fastadapter.IItem
- Direction
- extensions uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break extensions, while a change to extensions can't break com.mikepenz.fastadapter.
- 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→14 listeners uses com.mikepenz.fastadapter part of a loop✕
- Connections
- 11 pairs of types, where a type in listeners uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.listeners.ClickEventHook→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.listeners.ClickEventHookKt→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.listeners.CustomEventHook→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.listeners.LongClickEventHook→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.listeners.LongClickEventHookKt→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.listeners.OnCreateViewHolderListener→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.listeners.OnCreateViewHolderListener→com.mikepenz.fastadapter.IItemVHFactorycom.mikepenz.fastadapter.listeners.OnCreateViewHolderListenerImpl→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.listeners.OnCreateViewHolderListenerImpl→com.mikepenz.fastadapter.IItemVHFactorycom.mikepenz.fastadapter.listeners.TouchEventHook→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.listeners.TouchEventHookKt→com.mikepenz.fastadapter.FastAdapter
- Direction
- listeners uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break listeners, while a change to listeners can't break com.mikepenz.fastadapter.
- 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→3 swipe uses swipe.SimpleSwipeCallback✕
- Connections
- 1 pair of types, where a type in swipe uses a type in swipe.SimpleSwipeCallback.
- The types involved
com.mikepenz.fastadapter.swipe.SimpleSwipeCallback→com.mikepenz.fastadapter.swipe.SimpleSwipeCallback.ItemSwipeCallback
- Direction
- swipe uses swipe.SimpleSwipeCallback, so a change to swipe.SimpleSwipeCallback can break swipe, while a change to swipe can't break swipe.SimpleSwipeCallback.
- Position
- Below the diagonal: swipe uses a module listed above it, which is the healthy direction.
8→4 swipe uses swipe.SimpleSwipeDrawerCallback✕
- Connections
- 1 pair of types, where a type in swipe uses a type in swipe.SimpleSwipeDrawerCallback.
- The types involved
com.mikepenz.fastadapter.swipe.SimpleSwipeDrawerCallback→com.mikepenz.fastadapter.swipe.SimpleSwipeDrawerCallback.ItemSwipeCallback
- Direction
- swipe uses swipe.SimpleSwipeDrawerCallback, so a change to swipe.SimpleSwipeDrawerCallback can break swipe, while a change to swipe can't break swipe.SimpleSwipeDrawerCallback.
- Position
- Below the diagonal: swipe uses a module listed above it, which is the healthy direction.
9→6 expandable uses extensions✕
- Connections
- 1 pair of types, where a type in expandable uses a type in extensions.
- The types involved
com.mikepenz.fastadapter.expandable.ExpandableExtensionFactory→com.mikepenz.fastadapter.extensions.ExtensionFactory
- Direction
- expandable uses extensions, so a change to extensions can break expandable, while a change to expandable can't break extensions.
- Position
- Below the diagonal: expandable uses a module listed above it, which is the healthy direction.
9→14 expandable uses com.mikepenz.fastadapter part of a loop✕
- Connections
- 8 pairs of types, where a type in expandable uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.expandable.ExpandableExtension→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.expandable.ExpandableExtension→com.mikepenz.fastadapter.IAdapterExtensioncom.mikepenz.fastadapter.expandable.ExpandableExtension→com.mikepenz.fastadapter.IExpandablecom.mikepenz.fastadapter.expandable.ExpandableExtensionFactory→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.expandable.ExpandableExtensionFactory→com.mikepenz.fastadapter.IItemcom.mikepenz.fastadapter.expandable.ExpandableExtensionKt→com.mikepenz.fastadapter.IExpandablecom.mikepenz.fastadapter.expandable.ExpandableExtensionKt→com.mikepenz.fastadapter.IParentItemcom.mikepenz.fastadapter.expandable.ExpandableExtensionKt→com.mikepenz.fastadapter.ISubItem
- Direction
- expandable uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break expandable, while a change to expandable can't break com.mikepenz.fastadapter.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→6 select uses extensions✕
- Connections
- 1 pair of types, where a type in select uses a type in extensions.
- The types involved
com.mikepenz.fastadapter.select.SelectExtensionFactory→com.mikepenz.fastadapter.extensions.ExtensionFactory
- Direction
- select uses extensions, so a change to extensions can break select, while a change to select can't break extensions.
- Position
- Below the diagonal: select uses a module listed above it, which is the healthy direction.
10→14 select uses com.mikepenz.fastadapter part of a loop✕
- Connections
- 6 pairs of types, where a type in select uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.select.SelectExtension→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.select.SelectExtension→com.mikepenz.fastadapter.IAdaptercom.mikepenz.fastadapter.select.SelectExtension→com.mikepenz.fastadapter.IAdapterExtensioncom.mikepenz.fastadapter.select.SelectExtension→com.mikepenz.fastadapter.ISelectionListenercom.mikepenz.fastadapter.select.SelectExtensionFactory→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.select.SelectExtensionFactory→com.mikepenz.fastadapter.IItem
- Direction
- select uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break select, while a change to select can't break com.mikepenz.fastadapter.
- 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→2 swipe_drag uses drag✕
- Connections
- 4 pairs of types, where a type in swipe_drag uses a type in drag.
- The types involved
com.mikepenz.fastadapter.swipe_drag.SimpleSwipeDragCallback→com.mikepenz.fastadapter.drag.ItemTouchCallbackcom.mikepenz.fastadapter.swipe_drag.SimpleSwipeDragCallback→com.mikepenz.fastadapter.drag.SimpleDragCallbackcom.mikepenz.fastadapter.swipe_drag.SimpleSwipeDrawerDragCallback→com.mikepenz.fastadapter.drag.ItemTouchCallbackcom.mikepenz.fastadapter.swipe_drag.SimpleSwipeDrawerDragCallback→com.mikepenz.fastadapter.drag.SimpleDragCallback
- Direction
- swipe_drag uses drag, so a change to drag can break swipe_drag, while a change to swipe_drag can't break drag.
- Position
- Below the diagonal: swipe_drag uses a module listed above it, which is the healthy direction.
11→3 swipe_drag uses swipe.SimpleSwipeCallback✕
- Connections
- 1 pair of types, where a type in swipe_drag uses a type in swipe.SimpleSwipeCallback.
- The types involved
com.mikepenz.fastadapter.swipe_drag.SimpleSwipeDragCallback→com.mikepenz.fastadapter.swipe.SimpleSwipeCallback.ItemSwipeCallback
- Direction
- swipe_drag uses swipe.SimpleSwipeCallback, so a change to swipe.SimpleSwipeCallback can break swipe_drag, while a change to swipe_drag can't break swipe.SimpleSwipeCallback.
- Position
- Below the diagonal: swipe_drag uses a module listed above it, which is the healthy direction.
11→4 swipe_drag uses swipe.SimpleSwipeDrawerCallback✕
- Connections
- 1 pair of types, where a type in swipe_drag uses a type in swipe.SimpleSwipeDrawerCallback.
- The types involved
com.mikepenz.fastadapter.swipe_drag.SimpleSwipeDrawerDragCallback→com.mikepenz.fastadapter.swipe.SimpleSwipeDrawerCallback.ItemSwipeCallback
- Direction
- swipe_drag uses swipe.SimpleSwipeDrawerCallback, so a change to swipe.SimpleSwipeDrawerCallback can break swipe_drag, while a change to swipe_drag can't break swipe.SimpleSwipeDrawerCallback.
- Position
- Below the diagonal: swipe_drag uses a module listed above it, which is the healthy direction.
11→8 swipe_drag uses swipe✕
- Connections
- 2 pairs of types, where a type in swipe_drag uses a type in swipe.
- The types involved
com.mikepenz.fastadapter.swipe_drag.SimpleSwipeDragCallback→com.mikepenz.fastadapter.swipe.SimpleSwipeCallbackcom.mikepenz.fastadapter.swipe_drag.SimpleSwipeDrawerDragCallback→com.mikepenz.fastadapter.swipe.SimpleSwipeDrawerCallback
- Direction
- swipe_drag uses swipe, so a change to swipe can break swipe_drag, while a change to swipe_drag can't break swipe.
- Position
- Below the diagonal: swipe_drag uses a module listed above it, which is the healthy direction.
12→2 utils uses drag✕
- Connections
- 1 pair of types, where a type in utils uses a type in drag.
- The types involved
com.mikepenz.fastadapter.utils.DragDropUtil→com.mikepenz.fastadapter.drag.IExtendedDraggable
- Direction
- utils uses drag, so a change to drag can break utils, while a change to utils can't break drag.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
12→9 utils uses expandable✕
- Connections
- 1 pair of types, where a type in utils uses a type in expandable.
- The types involved
com.mikepenz.fastadapter.utils.SubItemUtil→com.mikepenz.fastadapter.expandable.ExpandableExtension
- Direction
- utils uses expandable, so a change to expandable can break utils, while a change to utils can't break expandable.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
12→10 utils uses select✕
- Connections
- 1 pair of types, where a type in utils uses a type in select.
- The types involved
com.mikepenz.fastadapter.utils.SubItemUtil→com.mikepenz.fastadapter.select.SelectExtension
- Direction
- utils uses select, so a change to select can break utils, while a change to utils can't break select.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
12→14 utils uses com.mikepenz.fastadapter part of a loop✕
- Connections
- 11 pairs of types, where a type in utils uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.utils.AdapterPredicate→com.mikepenz.fastadapter.IAdaptercom.mikepenz.fastadapter.utils.AdapterUtil→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.utils.DefaultIdDistributor→com.mikepenz.fastadapter.IIdDistributorcom.mikepenz.fastadapter.utils.DefaultItemList→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.utils.DefaultItemList→com.mikepenz.fastadapter.IItemListcom.mikepenz.fastadapter.utils.DefaultItemListImpl→com.mikepenz.fastadapter.IAdapterNotifiercom.mikepenz.fastadapter.utils.DefaultItemVHFactoryCache→com.mikepenz.fastadapter.IItemVHFactoryCachecom.mikepenz.fastadapter.utils.DragDropUtil→com.mikepenz.fastadapter.IItemAdaptercom.mikepenz.fastadapter.utils.SubItemUtil→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.utils.SubItemUtil→com.mikepenz.fastadapter.IItemcom.mikepenz.fastadapter.utils.SubItemUtil→com.mikepenz.fastadapter.IItemAdapter
- Direction
- utils uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break utils, while a change to utils can't break com.mikepenz.fastadapter.
- 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→12 FastAdapter uses utils✕
- Connections
- 2 pairs of types, where a type in FastAdapter uses a type in utils.
- The types involved
com.mikepenz.fastadapter.FastAdapter.Companion→com.mikepenz.fastadapter.utils.AdapterPredicatecom.mikepenz.fastadapter.FastAdapter.Companion→com.mikepenz.fastadapter.utils.Triple
- Direction
- FastAdapter uses utils, so a change to utils can break FastAdapter, while a change to FastAdapter can't break utils.
- Position
- Below the diagonal: FastAdapter uses a module listed above it, which is the healthy direction.
13→14 FastAdapter uses com.mikepenz.fastadapter part of a loop✕
- Connections
- 5 pairs of types, where a type in FastAdapter uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.FastAdapter.Companion→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.FastAdapter.Companion→com.mikepenz.fastadapter.IAdaptercom.mikepenz.fastadapter.FastAdapter.Companion→com.mikepenz.fastadapter.IAdapterExtensioncom.mikepenz.fastadapter.FastAdapter.Companion→com.mikepenz.fastadapter.IExpandablecom.mikepenz.fastadapter.FastAdapter.RelativeInfo→com.mikepenz.fastadapter.IAdapter
- Direction
- FastAdapter uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break FastAdapter, while a change to FastAdapter can't break com.mikepenz.fastadapter.
- 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 com.mikepenz.fastadapter uses listeners✕
- Connections
- 7 pairs of types, where a type in com.mikepenz.fastadapter uses a type in listeners.
- The types involved
com.mikepenz.fastadapter.FastAdapter→com.mikepenz.fastadapter.listeners.ClickEventHookcom.mikepenz.fastadapter.FastAdapter→com.mikepenz.fastadapter.listeners.EventHookcom.mikepenz.fastadapter.FastAdapter→com.mikepenz.fastadapter.listeners.LongClickEventHookcom.mikepenz.fastadapter.FastAdapter→com.mikepenz.fastadapter.listeners.OnBindViewHolderListenercom.mikepenz.fastadapter.FastAdapter→com.mikepenz.fastadapter.listeners.OnCreateViewHolderListenercom.mikepenz.fastadapter.FastAdapter→com.mikepenz.fastadapter.listeners.TouchEventHookcom.mikepenz.fastadapter.IHookable→com.mikepenz.fastadapter.listeners.EventHook
- Direction
- com.mikepenz.fastadapter uses listeners, so a change to listeners can break com.mikepenz.fastadapter, while a change to com.mikepenz.fastadapter can't break listeners.
- Position
- Below the diagonal: com.mikepenz.fastadapter uses a module listed above it, which is the healthy direction.
14→12 com.mikepenz.fastadapter uses utils✕
- Connections
- 2 pairs of types, where a type in com.mikepenz.fastadapter uses a type in utils.
- The types involved
com.mikepenz.fastadapter.FastAdapter→com.mikepenz.fastadapter.utils.AdapterPredicatecom.mikepenz.fastadapter.FastAdapter→com.mikepenz.fastadapter.utils.Triple
- Direction
- com.mikepenz.fastadapter uses utils, so a change to utils can break com.mikepenz.fastadapter, while a change to com.mikepenz.fastadapter can't break utils.
- Position
- Below the diagonal: com.mikepenz.fastadapter uses a module listed above it, which is the healthy direction.
14→13 com.mikepenz.fastadapter uses FastAdapter✕
- Connections
- 1 pair of types, where a type in com.mikepenz.fastadapter uses a type in FastAdapter.
- The types involved
com.mikepenz.fastadapter.FastAdapter→com.mikepenz.fastadapter.FastAdapter.RelativeInfo
- Direction
- com.mikepenz.fastadapter uses FastAdapter, so a change to FastAdapter can break com.mikepenz.fastadapter, while a change to com.mikepenz.fastadapter can't break FastAdapter.
- Position
- Below the diagonal: com.mikepenz.fastadapter uses a module listed above it, which is the healthy direction.
15→13 app.items.SimpleItem uses FastAdapter✕
- Connections
- 1 pair of types, where a type in app.items.SimpleItem uses a type in FastAdapter.
- The types involved
com.mikepenz.fastadapter.app.items.SimpleItem.ViewHolder→com.mikepenz.fastadapter.FastAdapter.ViewHolder
- Direction
- app.items.SimpleItem uses FastAdapter, so a change to FastAdapter can break app.items.SimpleItem, while a change to app.items.SimpleItem can't break FastAdapter.
- Position
- Below the diagonal: app.items.SimpleItem uses a module listed above it, which is the healthy direction.
15→39 app.items.SimpleItem uses app.items part of a loop✕
- Connections
- 1 pair of types, where a type in app.items.SimpleItem uses a type in app.items.
- The types involved
com.mikepenz.fastadapter.app.items.SimpleItem.ViewHolder→com.mikepenz.fastadapter.app.items.SimpleItem
- Direction
- app.items.SimpleItem uses app.items, so a change to app.items can break app.items.SimpleItem, while a change to app.items.SimpleItem can't break app.items.
- 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→13 helpers.UndoHelper uses FastAdapter✕
- Connections
- 2 pairs of types, where a type in helpers.UndoHelper uses a type in FastAdapter.
- The types involved
com.mikepenz.fastadapter.helpers.UndoHelper.History→com.mikepenz.fastadapter.FastAdapter.RelativeInfocom.mikepenz.fastadapter.helpers.UndoHelper.UndoListener→com.mikepenz.fastadapter.FastAdapter.RelativeInfo
- Direction
- helpers.UndoHelper uses FastAdapter, so a change to FastAdapter can break helpers.UndoHelper, while a change to helpers.UndoHelper can't break FastAdapter.
- Position
- Below the diagonal: helpers.UndoHelper uses a module listed above it, which is the healthy direction.
17→14 IAdapterNotifier uses com.mikepenz.fastadapter✕
- Connections
- 1 pair of types, where a type in IAdapterNotifier uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.IAdapterNotifier.Companion→com.mikepenz.fastadapter.IAdapterNotifier
- Direction
- IAdapterNotifier uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break IAdapterNotifier, while a change to IAdapterNotifier can't break com.mikepenz.fastadapter.
- Position
- Below the diagonal: IAdapterNotifier uses a module listed above it, which is the healthy direction.
18→7 adapters uses listeners✕
- Connections
- 1 pair of types, where a type in adapters uses a type in listeners.
- The types involved
com.mikepenz.fastadapter.adapters.ItemFilter→com.mikepenz.fastadapter.listeners.ItemFilterListener
- Direction
- adapters uses listeners, so a change to listeners can break adapters, while a change to adapters can't break listeners.
- Position
- Below the diagonal: adapters uses a module listed above it, which is the healthy direction.
18→12 adapters uses utils✕
- Connections
- 2 pairs of types, where a type in adapters uses a type in utils.
- The types involved
com.mikepenz.fastadapter.adapters.ModelAdapter→com.mikepenz.fastadapter.utils.AdapterPredicatecom.mikepenz.fastadapter.adapters.ModelAdapter→com.mikepenz.fastadapter.utils.Triple
- Direction
- adapters uses utils, so a change to utils can break adapters, while a change to adapters can't break utils.
- Position
- Below the diagonal: adapters uses a module listed above it, which is the healthy direction.
18→14 adapters uses com.mikepenz.fastadapter✕
- Connections
- 9 pairs of types, where a type in adapters uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.adapters.FastItemAdapter→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.adapters.FastItemAdapter→com.mikepenz.fastadapter.IItemAdaptercom.mikepenz.fastadapter.adapters.ItemAdapter→com.mikepenz.fastadapter.IItemListcom.mikepenz.fastadapter.adapters.ModelAdapter→com.mikepenz.fastadapter.AbstractAdaptercom.mikepenz.fastadapter.adapters.ModelAdapter→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.adapters.ModelAdapter→com.mikepenz.fastadapter.IAdapterNotifiercom.mikepenz.fastadapter.adapters.ModelAdapter→com.mikepenz.fastadapter.IIdDistributorcom.mikepenz.fastadapter.adapters.ModelAdapter→com.mikepenz.fastadapter.IItemAdaptercom.mikepenz.fastadapter.adapters.ModelAdapter→com.mikepenz.fastadapter.IItemList
- Direction
- adapters uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break adapters, while a change to adapters can't break com.mikepenz.fastadapter.
- Position
- Below the diagonal: adapters uses a module listed above it, which is the healthy direction.
19→7 app.items.CheckBoxSampleItem uses listeners✕
- Connections
- 1 pair of types, where a type in app.items.CheckBoxSampleItem uses a type in listeners.
- The types involved
com.mikepenz.fastadapter.app.items.CheckBoxSampleItem.CheckBoxClickEvent→com.mikepenz.fastadapter.listeners.ClickEventHook
- Direction
- app.items.CheckBoxSampleItem uses listeners, so a change to listeners can break app.items.CheckBoxSampleItem, while a change to app.items.CheckBoxSampleItem can't break listeners.
- Position
- Below the diagonal: app.items.CheckBoxSampleItem uses a module listed above it, which is the healthy direction.
19→14 app.items.CheckBoxSampleItem uses com.mikepenz.fastadapter✕
- Connections
- 1 pair of types, where a type in app.items.CheckBoxSampleItem uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.app.items.CheckBoxSampleItem.CheckBoxClickEvent→com.mikepenz.fastadapter.FastAdapter
- Direction
- app.items.CheckBoxSampleItem uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break app.items.CheckBoxSampleItem, while a change to app.items.CheckBoxSampleItem can't break com.mikepenz.fastadapter.
- Position
- Below the diagonal: app.items.CheckBoxSampleItem uses a module listed above it, which is the healthy direction.
19→39 app.items.CheckBoxSampleItem uses app.items part of a loop✕
- Connections
- 1 pair of types, where a type in app.items.CheckBoxSampleItem uses a type in app.items.
- The types involved
com.mikepenz.fastadapter.app.items.CheckBoxSampleItem.CheckBoxClickEvent→com.mikepenz.fastadapter.app.items.CheckBoxSampleItem
- Direction
- app.items.CheckBoxSampleItem uses app.items, so a change to app.items can break app.items.CheckBoxSampleItem, while a change to app.items.CheckBoxSampleItem can't break app.items.
- 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→7 app.items.ImageItem uses listeners✕
- Connections
- 1 pair of types, where a type in app.items.ImageItem uses a type in listeners.
- The types involved
com.mikepenz.fastadapter.app.items.ImageItem.ImageItemHeartClickEvent→com.mikepenz.fastadapter.listeners.ClickEventHook
- Direction
- app.items.ImageItem uses listeners, so a change to listeners can break app.items.ImageItem, while a change to app.items.ImageItem can't break listeners.
- Position
- Below the diagonal: app.items.ImageItem uses a module listed above it, which is the healthy direction.
20→14 app.items.ImageItem uses com.mikepenz.fastadapter✕
- Connections
- 1 pair of types, where a type in app.items.ImageItem uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.app.items.ImageItem.ImageItemHeartClickEvent→com.mikepenz.fastadapter.FastAdapter
- Direction
- app.items.ImageItem uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break app.items.ImageItem, while a change to app.items.ImageItem can't break com.mikepenz.fastadapter.
- Position
- Below the diagonal: app.items.ImageItem uses a module listed above it, which is the healthy direction.
20→39 app.items.ImageItem uses app.items part of a loop✕
- Connections
- 1 pair of types, where a type in app.items.ImageItem uses a type in app.items.
- The types involved
com.mikepenz.fastadapter.app.items.ImageItem.ImageItemHeartClickEvent→com.mikepenz.fastadapter.app.items.ImageItem
- Direction
- app.items.ImageItem uses app.items, so a change to app.items can break app.items.ImageItem, while a change to app.items.ImageItem can't break app.items.
- 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→7 app.items.RadioButtonSampleItem uses listeners✕
- Connections
- 1 pair of types, where a type in app.items.RadioButtonSampleItem uses a type in listeners.
- The types involved
com.mikepenz.fastadapter.app.items.RadioButtonSampleItem.RadioButtonClickEvent→com.mikepenz.fastadapter.listeners.ClickEventHook
- Direction
- app.items.RadioButtonSampleItem uses listeners, so a change to listeners can break app.items.RadioButtonSampleItem, while a change to app.items.RadioButtonSampleItem can't break listeners.
- Position
- Below the diagonal: app.items.RadioButtonSampleItem uses a module listed above it, which is the healthy direction.
21→14 app.items.RadioButtonSampleItem uses com.mikepenz.fastadapter✕
- Connections
- 1 pair of types, where a type in app.items.RadioButtonSampleItem uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.app.items.RadioButtonSampleItem.RadioButtonClickEvent→com.mikepenz.fastadapter.FastAdapter
- Direction
- app.items.RadioButtonSampleItem uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break app.items.RadioButtonSampleItem, while a change to app.items.RadioButtonSampleItem can't break com.mikepenz.fastadapter.
- Position
- Below the diagonal: app.items.RadioButtonSampleItem uses a module listed above it, which is the healthy direction.
21→39 app.items.RadioButtonSampleItem uses app.items part of a loop✕
- Connections
- 1 pair of types, where a type in app.items.RadioButtonSampleItem uses a type in app.items.
- The types involved
com.mikepenz.fastadapter.app.items.RadioButtonSampleItem.RadioButtonClickEvent→com.mikepenz.fastadapter.app.items.RadioButtonSampleItem
- Direction
- app.items.RadioButtonSampleItem uses app.items, so a change to app.items can break app.items.RadioButtonSampleItem, while a change to app.items.RadioButtonSampleItem can't break app.items.
- 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→14 diff uses com.mikepenz.fastadapter✕
- Connections
- 1 pair of types, where a type in diff uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.diff.FastAdapterDiffUtil→com.mikepenz.fastadapter.FastAdapter
- Direction
- diff uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break diff, while a change to diff can't break com.mikepenz.fastadapter.
- Position
- Below the diagonal: diff uses a module listed above it, which is the healthy direction.
23→14 items uses com.mikepenz.fastadapter✕
- Connections
- 7 pairs of types, where a type in items uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.items.AbstractItem→com.mikepenz.fastadapter.IItemVHFactorycom.mikepenz.fastadapter.items.AbstractItem→com.mikepenz.fastadapter.IItemViewGeneratorcom.mikepenz.fastadapter.items.BaseItem→com.mikepenz.fastadapter.IItemcom.mikepenz.fastadapter.items.BaseItem→com.mikepenz.fastadapter.IItemVHFactorycom.mikepenz.fastadapter.items.BaseItemFactory→com.mikepenz.fastadapter.IItemVHFactorycom.mikepenz.fastadapter.items.ModelAbstractItem→com.mikepenz.fastadapter.IModelItemcom.mikepenz.fastadapter.items.ModelBaseItem→com.mikepenz.fastadapter.IModelItem
- Direction
- items uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break items, while a change to items can't break com.mikepenz.fastadapter.
- Position
- Below the diagonal: items uses a module listed above it, which is the healthy direction.
24→12 paged uses utils✕
- Connections
- 1 pair of types, where a type in paged uses a type in utils.
- The types involved
com.mikepenz.fastadapter.paged.PagedItemListImpl→com.mikepenz.fastadapter.utils.DefaultItemList
- Direction
- paged uses utils, so a change to utils can break paged, while a change to paged can't break utils.
- Position
- Below the diagonal: paged uses a module listed above it, which is the healthy direction.
24→14 paged uses com.mikepenz.fastadapter✕
- Connections
- 7 pairs of types, where a type in paged uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.paged.PagedItemListImpl→com.mikepenz.fastadapter.IAdapterNotifiercom.mikepenz.fastadapter.paged.PagedItemListImpl→com.mikepenz.fastadapter.IIdDistributorcom.mikepenz.fastadapter.paged.PagedModelAdapter→com.mikepenz.fastadapter.AbstractAdaptercom.mikepenz.fastadapter.paged.PagedModelAdapter→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.paged.PagedModelAdapter→com.mikepenz.fastadapter.IAdapterNotifiercom.mikepenz.fastadapter.paged.PagedModelAdapter→com.mikepenz.fastadapter.IIdDistributorcom.mikepenz.fastadapter.paged.PagedModelAdapter→com.mikepenz.fastadapter.IItemAdapter
- Direction
- paged uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break paged, while a change to paged can't break com.mikepenz.fastadapter.
- Position
- Below the diagonal: paged uses a module listed above it, which is the healthy direction.
25→14 app.adapters uses com.mikepenz.fastadapter✕
- Connections
- 2 pairs of types, where a type in app.adapters uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.app.adapters.FastScrollIndicatorAdapter→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.app.adapters.StickyHeaderAdapter→com.mikepenz.fastadapter.FastAdapter
- Direction
- app.adapters uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break app.adapters, while a change to app.adapters can't break com.mikepenz.fastadapter.
- Position
- Below the diagonal: app.adapters uses a module listed above it, which is the healthy direction.
25→18 app.adapters uses adapters✕
- Connections
- 1 pair of types, where a type in app.adapters uses a type in adapters.
- The types involved
com.mikepenz.fastadapter.app.adapters.SampleWrapAdapter→com.mikepenz.fastadapter.adapters.AbstractWrapAdapter
- Direction
- app.adapters uses adapters, so a change to adapters can break app.adapters, while a change to app.adapters can't break adapters.
- Position
- Below the diagonal: app.adapters uses a module listed above it, which is the healthy direction.
26→23 app.model uses items✕
- Connections
- 1 pair of types, where a type in app.model uses a type in items.
- The types involved
com.mikepenz.fastadapter.app.model.ModelIconItem→com.mikepenz.fastadapter.items.ModelAbstractItem
- Direction
- app.model uses items, so a change to items can break app.model, while a change to app.model can't break items.
- Position
- Below the diagonal: app.model uses a module listed above it, which is the healthy direction.
27→14 binding uses com.mikepenz.fastadapter✕
- Connections
- 3 pairs of types, where a type in binding uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.binding.AbstractBindingItem→com.mikepenz.fastadapter.IItemVHFactorycom.mikepenz.fastadapter.binding.BaseBindingItemVHFactory→com.mikepenz.fastadapter.IItemVHFactorycom.mikepenz.fastadapter.binding.ModelAbstractBindingItem→com.mikepenz.fastadapter.IModelItem
- Direction
- binding uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break binding, while a change to binding can't break com.mikepenz.fastadapter.
- Position
- Below the diagonal: binding uses a module listed above it, which is the healthy direction.
27→23 binding uses items✕
- Connections
- 1 pair of types, where a type in binding uses a type in items.
- The types involved
com.mikepenz.fastadapter.binding.AbstractBindingItem→com.mikepenz.fastadapter.items.BaseItem
- Direction
- binding uses items, so a change to items can break binding, while a change to binding can't break items.
- Position
- Below the diagonal: binding uses a module listed above it, which is the healthy direction.
28→14 dsl uses com.mikepenz.fastadapter✕
- Connections
- 3 pairs of types, where a type in dsl uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.dsl.FastAdapterDslKt→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.dsl.FastAdapterDslKt→com.mikepenz.fastadapter.IItemcom.mikepenz.fastadapter.dsl.FastAdapterDslKt→com.mikepenz.fastadapter.IItemList
- Direction
- dsl uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break dsl, while a change to dsl can't break com.mikepenz.fastadapter.
- Position
- Below the diagonal: dsl uses a module listed above it, which is the healthy direction.
28→18 dsl uses adapters✕
- Connections
- 2 pairs of types, where a type in dsl uses a type in adapters.
- The types involved
com.mikepenz.fastadapter.dsl.FastAdapterDslKt→com.mikepenz.fastadapter.adapters.ItemAdaptercom.mikepenz.fastadapter.dsl.FastAdapterDslKt→com.mikepenz.fastadapter.adapters.ModelAdapter
- Direction
- dsl uses adapters, so a change to adapters can break dsl, while a change to dsl can't break adapters.
- Position
- Below the diagonal: dsl uses a module listed above it, which is the healthy direction.
29→14 expandable.items uses com.mikepenz.fastadapter✕
- Connections
- 9 pairs of types, where a type in expandable.items uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.expandable.items.AbstractExpandableItem→com.mikepenz.fastadapter.IExpandablecom.mikepenz.fastadapter.expandable.items.AbstractExpandableItem→com.mikepenz.fastadapter.IItemcom.mikepenz.fastadapter.expandable.items.AbstractExpandableItem→com.mikepenz.fastadapter.IParentItemcom.mikepenz.fastadapter.expandable.items.AbstractExpandableItem→com.mikepenz.fastadapter.ISubItemcom.mikepenz.fastadapter.expandable.items.AbstractExpandableItem→com.mikepenz.fastadapter.MutableSubItemListcom.mikepenz.fastadapter.expandable.items.ModelAbstractExpandableItem→com.mikepenz.fastadapter.IExpandablecom.mikepenz.fastadapter.expandable.items.ModelAbstractExpandableItem→com.mikepenz.fastadapter.IParentItemcom.mikepenz.fastadapter.expandable.items.ModelAbstractExpandableItem→com.mikepenz.fastadapter.ISubItemcom.mikepenz.fastadapter.expandable.items.ModelAbstractExpandableItem→com.mikepenz.fastadapter.MutableSubItemList
- Direction
- expandable.items uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break expandable.items, while a change to expandable.items can't break com.mikepenz.fastadapter.
- Position
- Below the diagonal: expandable.items uses a module listed above it, which is the healthy direction.
29→23 expandable.items uses items✕
- Connections
- 2 pairs of types, where a type in expandable.items uses a type in items.
- The types involved
com.mikepenz.fastadapter.expandable.items.AbstractExpandableItem→com.mikepenz.fastadapter.items.AbstractItemcom.mikepenz.fastadapter.expandable.items.ModelAbstractExpandableItem→com.mikepenz.fastadapter.items.ModelAbstractItem
- Direction
- expandable.items uses items, so a change to items can break expandable.items, while a change to expandable.items can't break items.
- Position
- Below the diagonal: expandable.items uses a module listed above it, which is the healthy direction.
30→9 helpers uses expandable✕
- Connections
- 1 pair of types, where a type in helpers uses a type in expandable.
- The types involved
com.mikepenz.fastadapter.helpers.ActionModeHelper→com.mikepenz.fastadapter.expandable.ExpandableExtension
- Direction
- helpers uses expandable, so a change to expandable can break helpers, while a change to helpers can't break expandable.
- Position
- Below the diagonal: helpers uses a module listed above it, which is the healthy direction.
30→10 helpers uses select✕
- Connections
- 1 pair of types, where a type in helpers uses a type in select.
- The types involved
com.mikepenz.fastadapter.helpers.ActionModeHelper→com.mikepenz.fastadapter.select.SelectExtension
- Direction
- helpers uses select, so a change to select can break helpers, while a change to helpers can't break select.
- Position
- Below the diagonal: helpers uses a module listed above it, which is the healthy direction.
30→14 helpers uses com.mikepenz.fastadapter✕
- Connections
- 3 pairs of types, where a type in helpers uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.helpers.ActionModeHelper→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.helpers.ActionModeHelper→com.mikepenz.fastadapter.IItemcom.mikepenz.fastadapter.helpers.UndoHelper→com.mikepenz.fastadapter.FastAdapter
- Direction
- helpers uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break helpers, while a change to helpers can't break com.mikepenz.fastadapter.
- Position
- Below the diagonal: helpers uses a module listed above it, which is the healthy direction.
30→16 helpers uses helpers.UndoHelper✕
- Connections
- 2 pairs of types, where a type in helpers uses a type in helpers.UndoHelper.
- The types involved
com.mikepenz.fastadapter.helpers.UndoHelper→com.mikepenz.fastadapter.helpers.UndoHelper.Historycom.mikepenz.fastadapter.helpers.UndoHelper→com.mikepenz.fastadapter.helpers.UndoHelper.UndoListener
- Direction
- helpers uses helpers.UndoHelper, so a change to helpers.UndoHelper can break helpers, while a change to helpers can't break helpers.UndoHelper.
- Position
- Below the diagonal: helpers uses a module listed above it, which is the healthy direction.
30→18 helpers uses adapters✕
- Connections
- 2 pairs of types, where a type in helpers uses a type in adapters.
- The types involved
com.mikepenz.fastadapter.helpers.HeaderHelper→com.mikepenz.fastadapter.adapters.ModelAdaptercom.mikepenz.fastadapter.helpers.RangeSelectorHelper→com.mikepenz.fastadapter.adapters.FastItemAdapter
- Direction
- helpers uses adapters, so a change to adapters can break helpers, while a change to helpers can't break adapters.
- Position
- Below the diagonal: helpers uses a module listed above it, which is the healthy direction.
31→14 scroll.EndlessScrollHelper uses com.mikepenz.fastadapter✕
- Connections
- 2 pairs of types, where a type in scroll.EndlessScrollHelper uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.scroll.EndlessScrollHelper.DeliverToIItemAdapter→com.mikepenz.fastadapter.IItemAdaptercom.mikepenz.fastadapter.scroll.EndlessScrollHelper.DeliverToIItemAdapter2→com.mikepenz.fastadapter.IItemAdapter
- Direction
- scroll.EndlessScrollHelper uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break scroll.EndlessScrollHelper, while a change to scroll.EndlessScrollHelper can't break com.mikepenz.fastadapter.
- Position
- Below the diagonal: scroll.EndlessScrollHelper uses a module listed above it, which is the healthy direction.
31→18 scroll.EndlessScrollHelper uses adapters✕
- Connections
- 2 pairs of types, where a type in scroll.EndlessScrollHelper uses a type in adapters.
- The types involved
com.mikepenz.fastadapter.scroll.EndlessScrollHelper.DeliverToModelAdapter→com.mikepenz.fastadapter.adapters.ModelAdaptercom.mikepenz.fastadapter.scroll.EndlessScrollHelper.DeliverToModelAdapter2→com.mikepenz.fastadapter.adapters.ModelAdapter
- Direction
- scroll.EndlessScrollHelper uses adapters, so a change to adapters can break scroll.EndlessScrollHelper, while a change to scroll.EndlessScrollHelper can't break adapters.
- Position
- Below the diagonal: scroll.EndlessScrollHelper uses a module listed above it, which is the healthy direction.
31→38 scroll.EndlessScrollHelper uses scroll part of a loop✕
- Connections
- 1 pair of types, where a type in scroll.EndlessScrollHelper uses a type in scroll.
- The types involved
com.mikepenz.fastadapter.scroll.EndlessScrollHelper.ResultReceiverImpl→com.mikepenz.fastadapter.scroll.EndlessScrollHelper
- Direction
- scroll.EndlessScrollHelper uses scroll, so a change to scroll can break scroll.EndlessScrollHelper, while a change to scroll.EndlessScrollHelper can't break scroll.
- 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→14 ui.dialog uses com.mikepenz.fastadapter✕
- Connections
- 2 pairs of types, where a type in ui.dialog uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.ui.dialog.FastAdapterBottomSheetDialog→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.ui.dialog.FastAdapterDialog→com.mikepenz.fastadapter.FastAdapter
- Direction
- ui.dialog uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break ui.dialog, while a change to ui.dialog can't break com.mikepenz.fastadapter.
- Position
- Below the diagonal: ui.dialog uses a module listed above it, which is the healthy direction.
32→18 ui.dialog uses adapters✕
- Connections
- 2 pairs of types, where a type in ui.dialog uses a type in adapters.
- The types involved
com.mikepenz.fastadapter.ui.dialog.FastAdapterBottomSheetDialog→com.mikepenz.fastadapter.adapters.ItemAdaptercom.mikepenz.fastadapter.ui.dialog.FastAdapterDialog→com.mikepenz.fastadapter.adapters.ItemAdapter
- Direction
- ui.dialog uses adapters, so a change to adapters can break ui.dialog, while a change to ui.dialog can't break adapters.
- Position
- Below the diagonal: ui.dialog uses a module listed above it, which is the healthy direction.
33→5 ui.items uses ui.utils✕
- Connections
- 6 pairs of types, where a type in ui.items uses a type in ui.utils.
- The types involved
com.mikepenz.fastadapter.ui.items.SingleLineItem→com.mikepenz.fastadapter.ui.utils.ImageHoldercom.mikepenz.fastadapter.ui.items.SingleLineItem→com.mikepenz.fastadapter.ui.utils.StringHoldercom.mikepenz.fastadapter.ui.items.ThreeLineItem→com.mikepenz.fastadapter.ui.utils.ImageHoldercom.mikepenz.fastadapter.ui.items.ThreeLineItem→com.mikepenz.fastadapter.ui.utils.StringHoldercom.mikepenz.fastadapter.ui.items.TwoLineItem→com.mikepenz.fastadapter.ui.utils.ImageHoldercom.mikepenz.fastadapter.ui.items.TwoLineItem→com.mikepenz.fastadapter.ui.utils.StringHolder
- Direction
- ui.items uses ui.utils, so a change to ui.utils can break ui.items, while a change to ui.items can't break ui.utils.
- Position
- Below the diagonal: ui.items uses a module listed above it, which is the healthy direction.
33→23 ui.items uses items✕
- Connections
- 4 pairs of types, where a type in ui.items uses a type in items.
- The types involved
com.mikepenz.fastadapter.ui.items.ProgressItem→com.mikepenz.fastadapter.items.AbstractItemcom.mikepenz.fastadapter.ui.items.SingleLineItem→com.mikepenz.fastadapter.items.AbstractItemcom.mikepenz.fastadapter.ui.items.ThreeLineItem→com.mikepenz.fastadapter.items.AbstractItemcom.mikepenz.fastadapter.ui.items.TwoLineItem→com.mikepenz.fastadapter.items.AbstractItem
- Direction
- ui.items uses items, so a change to items can break ui.items, while a change to ui.items can't break items.
- Position
- Below the diagonal: ui.items uses a module listed above it, which is the healthy direction.
34→14 app.binding uses com.mikepenz.fastadapter✕
- Connections
- 3 pairs of types, where a type in app.binding uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.app.binding.BindingIconItem→com.mikepenz.fastadapter.IExpandablecom.mikepenz.fastadapter.app.binding.BindingIconItem→com.mikepenz.fastadapter.IParentItemcom.mikepenz.fastadapter.app.binding.BindingIconItem→com.mikepenz.fastadapter.ISubItem
- Direction
- app.binding uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break app.binding, while a change to app.binding can't break com.mikepenz.fastadapter.
- Position
- Below the diagonal: app.binding uses a module listed above it, which is the healthy direction.
34→27 app.binding uses binding✕
- Connections
- 1 pair of types, where a type in app.binding uses a type in binding.
- The types involved
com.mikepenz.fastadapter.app.binding.BindingIconItem→com.mikepenz.fastadapter.binding.AbstractBindingItem
- Direction
- app.binding uses binding, so a change to binding can break app.binding, while a change to app.binding can't break binding.
- Position
- Below the diagonal: app.binding uses a module listed above it, which is the healthy direction.
35→8 app.items.SwipeableDrawerItem uses swipe✕
- Connections
- 1 pair of types, where a type in app.items.SwipeableDrawerItem uses a type in swipe.
- The types involved
com.mikepenz.fastadapter.app.items.SwipeableDrawerItem.ViewHolder→com.mikepenz.fastadapter.swipe.IDrawerSwipeableViewHolder
- Direction
- app.items.SwipeableDrawerItem uses swipe, so a change to swipe can break app.items.SwipeableDrawerItem, while a change to app.items.SwipeableDrawerItem can't break swipe.
- Position
- Below the diagonal: app.items.SwipeableDrawerItem uses a module listed above it, which is the healthy direction.
35→25 app.items.SwipeableDrawerItem uses app.adapters✕
- Connections
- 1 pair of types, where a type in app.items.SwipeableDrawerItem uses a type in app.adapters.
- The types involved
com.mikepenz.fastadapter.app.items.SwipeableDrawerItem.ViewHolder→com.mikepenz.fastadapter.app.adapters.IDraggableViewHolder
- Direction
- app.items.SwipeableDrawerItem uses app.adapters, so a change to app.adapters can break app.items.SwipeableDrawerItem, while a change to app.items.SwipeableDrawerItem can't break app.adapters.
- Position
- Below the diagonal: app.items.SwipeableDrawerItem uses a module listed above it, which is the healthy direction.
36→25 app.items.SwipeableItem uses app.adapters✕
- Connections
- 1 pair of types, where a type in app.items.SwipeableItem uses a type in app.adapters.
- The types involved
com.mikepenz.fastadapter.app.items.SwipeableItem.ViewHolder→com.mikepenz.fastadapter.app.adapters.IDraggableViewHolder
- Direction
- app.items.SwipeableItem uses app.adapters, so a change to app.adapters can break app.items.SwipeableItem, while a change to app.items.SwipeableItem can't break app.adapters.
- Position
- Below the diagonal: app.items.SwipeableItem uses a module listed above it, which is the healthy direction.
37→1 app.items.expandable uses app.items.expandable.SimpleSubExpandableItem✕
- Connections
- 1 pair of types, where a type in app.items.expandable uses a type in app.items.expandable.SimpleSubExpandableItem.
- The types involved
com.mikepenz.fastadapter.app.items.expandable.SimpleSubExpandableItem→com.mikepenz.fastadapter.app.items.expandable.SimpleSubExpandableItem.ViewHolder
- Direction
- app.items.expandable uses app.items.expandable.SimpleSubExpandableItem, so a change to app.items.expandable.SimpleSubExpandableItem can break app.items.expandable, while a change to app.items.expandable can't break app.items.expandable.SimpleSubExpandableItem.
- Position
- Below the diagonal: app.items.expandable uses a module listed above it, which is the healthy direction.
37→2 app.items.expandable uses drag✕
- Connections
- 1 pair of types, where a type in app.items.expandable uses a type in drag.
- The types involved
com.mikepenz.fastadapter.app.items.expandable.SimpleSubItem→com.mikepenz.fastadapter.drag.IDraggable
- Direction
- app.items.expandable uses drag, so a change to drag can break app.items.expandable, while a change to app.items.expandable can't break drag.
- Position
- Below the diagonal: app.items.expandable uses a module listed above it, which is the healthy direction.
37→14 app.items.expandable uses com.mikepenz.fastadapter✕
- Connections
- 2 pairs of types, where a type in app.items.expandable uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.app.items.expandable.SimpleSubExpandableItem→com.mikepenz.fastadapter.ISubItemcom.mikepenz.fastadapter.app.items.expandable.SimpleSubItem→com.mikepenz.fastadapter.IExpandable
- Direction
- app.items.expandable uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break app.items.expandable, while a change to app.items.expandable can't break com.mikepenz.fastadapter.
- Position
- Below the diagonal: app.items.expandable uses a module listed above it, which is the healthy direction.
37→29 app.items.expandable uses expandable.items✕
- Connections
- 2 pairs of types, where a type in app.items.expandable uses a type in expandable.items.
- The types involved
com.mikepenz.fastadapter.app.items.expandable.SimpleSubExpandableItem→com.mikepenz.fastadapter.expandable.items.AbstractExpandableItemcom.mikepenz.fastadapter.app.items.expandable.SimpleSubItem→com.mikepenz.fastadapter.expandable.items.AbstractExpandableItem
- Direction
- app.items.expandable uses expandable.items, so a change to expandable.items can break app.items.expandable, while a change to app.items.expandable can't break expandable.items.
- Position
- Below the diagonal: app.items.expandable uses a module listed above it, which is the healthy direction.
38→14 scroll uses com.mikepenz.fastadapter✕
- Connections
- 2 pairs of types, where a type in scroll uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.scroll.EndlessRecyclerOnTopScrollListener→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.scroll.EndlessScrollHelper→com.mikepenz.fastadapter.IItemAdapter
- Direction
- scroll uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break scroll, while a change to scroll can't break com.mikepenz.fastadapter.
- Position
- Below the diagonal: scroll uses a module listed above it, which is the healthy direction.
38→18 scroll uses adapters✕
- Connections
- 3 pairs of types, where a type in scroll uses a type in adapters.
- The types involved
com.mikepenz.fastadapter.scroll.EndlessRecyclerOnScrollListener→com.mikepenz.fastadapter.adapters.ItemAdaptercom.mikepenz.fastadapter.scroll.EndlessScrollHelper→com.mikepenz.fastadapter.adapters.ItemAdaptercom.mikepenz.fastadapter.scroll.EndlessScrollHelper→com.mikepenz.fastadapter.adapters.ModelAdapter
- Direction
- scroll uses adapters, so a change to adapters can break scroll, while a change to scroll can't break adapters.
- Position
- Below the diagonal: scroll uses a module listed above it, which is the healthy direction.
38→31 scroll uses scroll.EndlessScrollHelper✕
- Connections
- 3 pairs of types, where a type in scroll uses a type in scroll.EndlessScrollHelper.
- The types involved
com.mikepenz.fastadapter.scroll.EndlessScrollHelper→com.mikepenz.fastadapter.scroll.EndlessScrollHelper.OnLoadMoreHandlercom.mikepenz.fastadapter.scroll.EndlessScrollHelper→com.mikepenz.fastadapter.scroll.EndlessScrollHelper.OnNewItemsListenercom.mikepenz.fastadapter.scroll.EndlessScrollHelper→com.mikepenz.fastadapter.scroll.EndlessScrollHelper.ResultReceiver
- Direction
- scroll uses scroll.EndlessScrollHelper, so a change to scroll.EndlessScrollHelper can break scroll, while a change to scroll can't break scroll.EndlessScrollHelper.
- Position
- Below the diagonal: scroll uses a module listed above it, which is the healthy direction.
39→1 app.items uses app.items.expandable.SimpleSubExpandableItem✕
- Connections
- 1 pair of types, where a type in app.items uses a type in app.items.expandable.SimpleSubExpandableItem.
- The types involved
com.mikepenz.fastadapter.app.items.HeaderSelectionItem→com.mikepenz.fastadapter.app.items.expandable.SimpleSubExpandableItem.ViewHolder
- Direction
- app.items uses app.items.expandable.SimpleSubExpandableItem, so a change to app.items.expandable.SimpleSubExpandableItem can break app.items, while a change to app.items can't break app.items.expandable.SimpleSubExpandableItem.
- Position
- Below the diagonal: app.items uses a module listed above it, which is the healthy direction.
39→2 app.items uses drag✕
- Connections
- 4 pairs of types, where a type in app.items uses a type in drag.
- The types involved
com.mikepenz.fastadapter.app.items.DraggableSingleLineItem→com.mikepenz.fastadapter.drag.IDraggablecom.mikepenz.fastadapter.app.items.SimpleItem→com.mikepenz.fastadapter.drag.IDraggablecom.mikepenz.fastadapter.app.items.SwipeableDrawerItem→com.mikepenz.fastadapter.drag.IDraggablecom.mikepenz.fastadapter.app.items.SwipeableItem→com.mikepenz.fastadapter.drag.IDraggable
- Direction
- app.items uses drag, so a change to drag can break app.items, while a change to app.items can't break drag.
- Position
- Below the diagonal: app.items uses a module listed above it, which is the healthy direction.
39→5 app.items uses ui.utils✕
- Connections
- 5 pairs of types, where a type in app.items uses a type in ui.utils.
- The types involved
com.mikepenz.fastadapter.app.items.DraggableSingleLineItem→com.mikepenz.fastadapter.ui.utils.ImageHoldercom.mikepenz.fastadapter.app.items.DraggableSingleLineItem→com.mikepenz.fastadapter.ui.utils.StringHoldercom.mikepenz.fastadapter.app.items.SectionHeaderItem→com.mikepenz.fastadapter.ui.utils.StringHoldercom.mikepenz.fastadapter.app.items.SmallIconSingleLineItem→com.mikepenz.fastadapter.ui.utils.ImageHoldercom.mikepenz.fastadapter.app.items.SmallIconSingleLineItem→com.mikepenz.fastadapter.ui.utils.StringHolder
- Direction
- app.items uses ui.utils, so a change to ui.utils can break app.items, while a change to app.items can't break ui.utils.
- Position
- Below the diagonal: app.items uses a module listed above it, which is the healthy direction.
39→7 app.items uses listeners✕
- Connections
- 1 pair of types, where a type in app.items uses a type in listeners.
- The types involved
com.mikepenz.fastadapter.app.items.DragHandleTouchEvent→com.mikepenz.fastadapter.listeners.TouchEventHook
- Direction
- app.items uses listeners, so a change to listeners can break app.items, while a change to app.items can't break listeners.
- Position
- Below the diagonal: app.items uses a module listed above it, which is the healthy direction.
39→8 app.items uses swipe✕
- Connections
- 2 pairs of types, where a type in app.items uses a type in swipe.
- The types involved
com.mikepenz.fastadapter.app.items.SwipeableDrawerItem→com.mikepenz.fastadapter.swipe.ISwipeablecom.mikepenz.fastadapter.app.items.SwipeableItem→com.mikepenz.fastadapter.swipe.ISwipeable
- Direction
- app.items uses swipe, so a change to swipe can break app.items, while a change to app.items can't break swipe.
- Position
- Below the diagonal: app.items uses a module listed above it, which is the healthy direction.
39→14 app.items uses com.mikepenz.fastadapter✕
- Connections
- 8 pairs of types, where a type in app.items uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.app.items.DragHandleTouchEvent→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.app.items.IconItem→com.mikepenz.fastadapter.IExpandablecom.mikepenz.fastadapter.app.items.IconItem→com.mikepenz.fastadapter.IParentItemcom.mikepenz.fastadapter.app.items.IconItem→com.mikepenz.fastadapter.ISubItemcom.mikepenz.fastadapter.app.items.RealmSampleUserItem→com.mikepenz.fastadapter.IItemcom.mikepenz.fastadapter.app.items.RealmSampleUserItem→com.mikepenz.fastadapter.IItemVHFactorycom.mikepenz.fastadapter.app.items.RealmSampleUserItem→com.mikepenz.fastadapter.IItemViewGeneratorcom.mikepenz.fastadapter.app.items.SimpleImageItem→com.mikepenz.fastadapter.IItemVHFactory
- Direction
- app.items uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break app.items, while a change to app.items can't break com.mikepenz.fastadapter.
- Position
- Below the diagonal: app.items uses a module listed above it, which is the healthy direction.
39→15 app.items uses app.items.SimpleItem✕
- Connections
- 1 pair of types, where a type in app.items uses a type in app.items.SimpleItem.
- The types involved
com.mikepenz.fastadapter.app.items.SimpleItem→com.mikepenz.fastadapter.app.items.SimpleItem.ViewHolder
- Direction
- app.items uses app.items.SimpleItem, so a change to app.items.SimpleItem can break app.items, while a change to app.items can't break app.items.SimpleItem.
- Position
- Below the diagonal: app.items uses a module listed above it, which is the healthy direction.
39→19 app.items uses app.items.CheckBoxSampleItem✕
- Connections
- 1 pair of types, where a type in app.items uses a type in app.items.CheckBoxSampleItem.
- The types involved
com.mikepenz.fastadapter.app.items.CheckBoxSampleItem→com.mikepenz.fastadapter.app.items.CheckBoxSampleItem.ViewHolder
- Direction
- app.items uses app.items.CheckBoxSampleItem, so a change to app.items.CheckBoxSampleItem can break app.items, while a change to app.items can't break app.items.CheckBoxSampleItem.
- Position
- Below the diagonal: app.items uses a module listed above it, which is the healthy direction.
39→20 app.items uses app.items.ImageItem✕
- Connections
- 1 pair of types, where a type in app.items uses a type in app.items.ImageItem.
- The types involved
com.mikepenz.fastadapter.app.items.ImageItem→com.mikepenz.fastadapter.app.items.ImageItem.ViewHolder
- Direction
- app.items uses app.items.ImageItem, so a change to app.items.ImageItem can break app.items, while a change to app.items can't break app.items.ImageItem.
- Position
- Below the diagonal: app.items uses a module listed above it, which is the healthy direction.
39→21 app.items uses app.items.RadioButtonSampleItem✕
- Connections
- 1 pair of types, where a type in app.items uses a type in app.items.RadioButtonSampleItem.
- The types involved
com.mikepenz.fastadapter.app.items.RadioButtonSampleItem→com.mikepenz.fastadapter.app.items.RadioButtonSampleItem.ViewHolder
- Direction
- app.items uses app.items.RadioButtonSampleItem, so a change to app.items.RadioButtonSampleItem can break app.items, while a change to app.items can't break app.items.RadioButtonSampleItem.
- Position
- Below the diagonal: app.items uses a module listed above it, which is the healthy direction.
39→23 app.items uses items✕
- Connections
- 13 pairs of types, where a type in app.items uses a type in items.
- The types involved
com.mikepenz.fastadapter.app.items.CheckBoxSampleItem→com.mikepenz.fastadapter.items.AbstractItemcom.mikepenz.fastadapter.app.items.DraggableSingleLineItem→com.mikepenz.fastadapter.items.AbstractItemcom.mikepenz.fastadapter.app.items.IconItem→com.mikepenz.fastadapter.items.AbstractItemcom.mikepenz.fastadapter.app.items.ImageItem→com.mikepenz.fastadapter.items.AbstractItemcom.mikepenz.fastadapter.app.items.LetterItem→com.mikepenz.fastadapter.items.AbstractItemcom.mikepenz.fastadapter.app.items.RadioButtonSampleItem→com.mikepenz.fastadapter.items.AbstractItemcom.mikepenz.fastadapter.app.items.SectionHeaderItem→com.mikepenz.fastadapter.items.AbstractItemcom.mikepenz.fastadapter.app.items.SimpleImageItem→com.mikepenz.fastadapter.items.BaseItemcom.mikepenz.fastadapter.app.items.SimpleImageItemFactory→com.mikepenz.fastadapter.items.BaseItemFactorycom.mikepenz.fastadapter.app.items.SimpleItem→com.mikepenz.fastadapter.items.AbstractItemcom.mikepenz.fastadapter.app.items.SmallIconSingleLineItem→com.mikepenz.fastadapter.items.AbstractItemcom.mikepenz.fastadapter.app.items.SwipeableDrawerItem→com.mikepenz.fastadapter.items.AbstractItemcom.mikepenz.fastadapter.app.items.SwipeableItem→com.mikepenz.fastadapter.items.AbstractItem
- Direction
- app.items uses items, so a change to items can break app.items, while a change to app.items can't break items.
- Position
- Below the diagonal: app.items uses a module listed above it, which is the healthy direction.
39→35 app.items uses app.items.SwipeableDrawerItem✕
- Connections
- 1 pair of types, where a type in app.items uses a type in app.items.SwipeableDrawerItem.
- The types involved
com.mikepenz.fastadapter.app.items.SwipeableDrawerItem→com.mikepenz.fastadapter.app.items.SwipeableDrawerItem.ViewHolder
- Direction
- app.items uses app.items.SwipeableDrawerItem, so a change to app.items.SwipeableDrawerItem can break app.items, while a change to app.items can't break app.items.SwipeableDrawerItem.
- Position
- Below the diagonal: app.items uses a module listed above it, which is the healthy direction.
39→36 app.items uses app.items.SwipeableItem✕
- Connections
- 1 pair of types, where a type in app.items uses a type in app.items.SwipeableItem.
- The types involved
com.mikepenz.fastadapter.app.items.SwipeableItem→com.mikepenz.fastadapter.app.items.SwipeableItem.ViewHolder
- Direction
- app.items uses app.items.SwipeableItem, so a change to app.items.SwipeableItem can break app.items, while a change to app.items can't break app.items.SwipeableItem.
- Position
- Below the diagonal: app.items uses a module listed above it, which is the healthy direction.
39→37 app.items uses app.items.expandable✕
- Connections
- 1 pair of types, where a type in app.items uses a type in app.items.expandable.
- The types involved
com.mikepenz.fastadapter.app.items.HeaderSelectionItem→com.mikepenz.fastadapter.app.items.expandable.SimpleSubExpandableItem
- Direction
- app.items uses app.items.expandable, so a change to app.items.expandable can break app.items, while a change to app.items can't break app.items.expandable.
- Position
- Below the diagonal: app.items uses a module listed above it, which is the healthy direction.
40→2 app uses drag✕
- Connections
- 10 pairs of types, where a type in app uses a type in drag.
- The types involved
com.mikepenz.fastadapter.app.DragAndDropActivity→com.mikepenz.fastadapter.drag.ItemTouchCallbackcom.mikepenz.fastadapter.app.DragAndDropActivity→com.mikepenz.fastadapter.drag.SimpleDragCallbackcom.mikepenz.fastadapter.app.EndlessScrollListActivity→com.mikepenz.fastadapter.drag.ItemTouchCallbackcom.mikepenz.fastadapter.app.EndlessScrollListActivity→com.mikepenz.fastadapter.drag.SimpleDragCallbackcom.mikepenz.fastadapter.app.SimpleItemListActivity→com.mikepenz.fastadapter.drag.ItemTouchCallbackcom.mikepenz.fastadapter.app.SimpleItemListActivity→com.mikepenz.fastadapter.drag.SimpleDragCallbackcom.mikepenz.fastadapter.app.SwipeDrawerListActivity→com.mikepenz.fastadapter.drag.ItemTouchCallbackcom.mikepenz.fastadapter.app.SwipeDrawerListActivity→com.mikepenz.fastadapter.drag.SimpleDragCallbackcom.mikepenz.fastadapter.app.SwipeListActivity→com.mikepenz.fastadapter.drag.ItemTouchCallbackcom.mikepenz.fastadapter.app.SwipeListActivity→com.mikepenz.fastadapter.drag.SimpleDragCallback
- Direction
- app uses drag, so a change to drag can break app, while a change to app can't break drag.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
40→3 app uses swipe.SimpleSwipeCallback✕
- Connections
- 1 pair of types, where a type in app uses a type in swipe.SimpleSwipeCallback.
- The types involved
com.mikepenz.fastadapter.app.SwipeListActivity→com.mikepenz.fastadapter.swipe.SimpleSwipeCallback.ItemSwipeCallback
- Direction
- app uses swipe.SimpleSwipeCallback, so a change to swipe.SimpleSwipeCallback can break app, while a change to app can't break swipe.SimpleSwipeCallback.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
40→4 app uses swipe.SimpleSwipeDrawerCallback✕
- Connections
- 1 pair of types, where a type in app uses a type in swipe.SimpleSwipeDrawerCallback.
- The types involved
com.mikepenz.fastadapter.app.SwipeDrawerListActivity→com.mikepenz.fastadapter.swipe.SimpleSwipeDrawerCallback.ItemSwipeCallback
- Direction
- app uses swipe.SimpleSwipeDrawerCallback, so a change to swipe.SimpleSwipeDrawerCallback can break app, while a change to app can't break swipe.SimpleSwipeDrawerCallback.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
40→7 app uses listeners✕
- Connections
- 2 pairs of types, where a type in app uses a type in listeners.
- The types involved
com.mikepenz.fastadapter.app.EndlessScrollListActivity→com.mikepenz.fastadapter.listeners.ItemFilterListenercom.mikepenz.fastadapter.app.SimpleItemListActivity→com.mikepenz.fastadapter.listeners.ItemFilterListener
- Direction
- app uses listeners, so a change to listeners can break app, while a change to app can't break listeners.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
40→9 app uses expandable✕
- Connections
- 1 pair of types, where a type in app uses a type in expandable.
- The types involved
com.mikepenz.fastadapter.app.ExpandableMultiselectDeleteSampleActivity→com.mikepenz.fastadapter.expandable.ExpandableExtension
- Direction
- app uses expandable, so a change to expandable can break app, while a change to app can't break expandable.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
40→10 app uses select✕
- Connections
- 6 pairs of types, where a type in app uses a type in select.
- The types involved
com.mikepenz.fastadapter.app.CheckBoxSampleActivity→com.mikepenz.fastadapter.select.SelectExtensioncom.mikepenz.fastadapter.app.ExpandableMultiselectDeleteSampleActivity→com.mikepenz.fastadapter.select.SelectExtensioncom.mikepenz.fastadapter.app.MultiselectSampleActivity→com.mikepenz.fastadapter.select.SelectExtensioncom.mikepenz.fastadapter.app.RadioButtonSampleActivity→com.mikepenz.fastadapter.select.SelectExtensioncom.mikepenz.fastadapter.app.SampleActivity→com.mikepenz.fastadapter.select.SelectExtensioncom.mikepenz.fastadapter.app.SortActivity→com.mikepenz.fastadapter.select.SelectExtension
- Direction
- app uses select, so a change to select can break app, while a change to app can't break select.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
40→12 app uses utils✕
- Connections
- 1 pair of types, where a type in app uses a type in utils.
- The types involved
com.mikepenz.fastadapter.app.SortActivity→com.mikepenz.fastadapter.utils.ComparableItemListImpl
- Direction
- app uses utils, so a change to utils can break app, while a change to app can't break utils.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
40→14 app uses com.mikepenz.fastadapter✕
- Connections
- 17 pairs of types, where a type in app uses a type in com.mikepenz.fastadapter.
- The types involved
com.mikepenz.fastadapter.app.AdvancedSampleActivity→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.app.AdvancedSampleActivity→com.mikepenz.fastadapter.IItemcom.mikepenz.fastadapter.app.DragAndDropActivity→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.app.DragAndDropActivity→com.mikepenz.fastadapter.IItemcom.mikepenz.fastadapter.app.EndlessScrollListActivity→com.mikepenz.fastadapter.IItemcom.mikepenz.fastadapter.app.ExpandableMultiselectDeleteSampleActivity→com.mikepenz.fastadapter.IItemcom.mikepenz.fastadapter.app.ExpandableSampleActivity→com.mikepenz.fastadapter.IItemcom.mikepenz.fastadapter.app.IconGridActivity→com.mikepenz.fastadapter.IItemcom.mikepenz.fastadapter.app.ModelItemActivity→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.app.MultiTypeModelItemActivity→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.app.MultiTypeModelItemActivity→com.mikepenz.fastadapter.IItemcom.mikepenz.fastadapter.app.MultiselectSampleActivity→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.app.PagedActivity→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.app.SampleActivity→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.app.SimpleItemListActivity→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.app.SortActivity→com.mikepenz.fastadapter.FastAdaptercom.mikepenz.fastadapter.app.StickyHeaderSampleActivity→com.mikepenz.fastadapter.FastAdapter
- Direction
- app uses com.mikepenz.fastadapter, so a change to com.mikepenz.fastadapter can break app, while a change to app can't break com.mikepenz.fastadapter.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
40→18 app uses adapters✕
- Connections
- 17 pairs of types, where a type in app uses a type in adapters.
- The types involved
com.mikepenz.fastadapter.app.AdvancedSampleActivity→com.mikepenz.fastadapter.adapters.ItemAdaptercom.mikepenz.fastadapter.app.CheckBoxSampleActivity→com.mikepenz.fastadapter.adapters.FastItemAdaptercom.mikepenz.fastadapter.app.DiffUtilActivity→com.mikepenz.fastadapter.adapters.FastItemAdaptercom.mikepenz.fastadapter.app.DragAndDropActivity→com.mikepenz.fastadapter.adapters.ItemAdaptercom.mikepenz.fastadapter.app.EndlessScrollListActivity→com.mikepenz.fastadapter.adapters.FastItemAdaptercom.mikepenz.fastadapter.app.EndlessScrollListActivity→com.mikepenz.fastadapter.adapters.ItemAdaptercom.mikepenz.fastadapter.app.ExpandableMultiselectDeleteSampleActivity→com.mikepenz.fastadapter.adapters.FastItemAdaptercom.mikepenz.fastadapter.app.ExpandableSampleActivity→com.mikepenz.fastadapter.adapters.FastItemAdaptercom.mikepenz.fastadapter.app.IconGridActivity→com.mikepenz.fastadapter.adapters.FastItemAdaptercom.mikepenz.fastadapter.app.ImageListActivity→com.mikepenz.fastadapter.adapters.FastItemAdaptercom.mikepenz.fastadapter.app.RadioButtonSampleActivity→com.mikepenz.fastadapter.adapters.FastItemAdaptercom.mikepenz.fastadapter.app.RealmActivity→com.mikepenz.fastadapter.adapters.FastItemAdaptercom.mikepenz.fastadapter.app.SampleActivity→com.mikepenz.fastadapter.adapters.ItemAdaptercom.mikepenz.fastadapter.app.SimpleItemListActivity→com.mikepenz.fastadapter.adapters.ItemAdaptercom.mikepenz.fastadapter.app.SortActivity→com.mikepenz.fastadapter.adapters.ItemAdaptercom.mikepenz.fastadapter.app.SwipeDrawerListActivity→com.mikepenz.fastadapter.adapters.FastItemAdaptercom.mikepenz.fastadapter.app.SwipeListActivity→com.mikepenz.fastadapter.adapters.FastItemAdapter
- Direction
- app uses adapters, so a change to adapters can break app, while a change to app can't break adapters.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
40→24 app uses paged✕
- Connections
- 1 pair of types, where a type in app uses a type in paged.
- The types involved
com.mikepenz.fastadapter.app.PagedActivity→com.mikepenz.fastadapter.paged.PagedModelAdapter
- Direction
- app uses paged, so a change to paged can break app, while a change to app can't break paged.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
40→26 app uses app.model✕
- Connections
- 1 pair of types, where a type in app uses a type in app.model.
- The types involved
com.mikepenz.fastadapter.app.ModelItemActivity→com.mikepenz.fastadapter.app.model.ModelIconItem
- Direction
- app uses app.model, so a change to app.model can break app, while a change to app can't break app.model.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
40→30 app uses helpers✕
- Connections
- 5 pairs of types, where a type in app uses a type in helpers.
- The types involved
com.mikepenz.fastadapter.app.AdvancedSampleActivity→com.mikepenz.fastadapter.helpers.ActionModeHelpercom.mikepenz.fastadapter.app.ExpandableMultiselectDeleteSampleActivity→com.mikepenz.fastadapter.helpers.ActionModeHelpercom.mikepenz.fastadapter.app.ExpandableMultiselectDeleteSampleActivity→com.mikepenz.fastadapter.helpers.RangeSelectorHelpercom.mikepenz.fastadapter.app.MultiselectSampleActivity→com.mikepenz.fastadapter.helpers.ActionModeHelpercom.mikepenz.fastadapter.app.MultiselectSampleActivity→com.mikepenz.fastadapter.helpers.UndoHelper
- Direction
- app uses helpers, so a change to helpers can break app, while a change to app can't break helpers.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
40→38 app uses scroll✕
- Connections
- 1 pair of types, where a type in app uses a type in scroll.
- The types involved
com.mikepenz.fastadapter.app.EndlessScrollListActivity→com.mikepenz.fastadapter.scroll.EndlessRecyclerOnScrollListener
- Direction
- app uses scroll, so a change to scroll can break app, while a change to app can't break scroll.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
40→39 app uses app.items✕
- Connections
- 14 pairs of types, where a type in app uses a type in app.items.
- The types involved
com.mikepenz.fastadapter.app.AdvancedSampleActivity→com.mikepenz.fastadapter.app.items.SimpleItemcom.mikepenz.fastadapter.app.CheckBoxSampleActivity→com.mikepenz.fastadapter.app.items.CheckBoxSampleItemcom.mikepenz.fastadapter.app.DiffUtilActivity→com.mikepenz.fastadapter.app.items.SimpleItemcom.mikepenz.fastadapter.app.ImageListActivity→com.mikepenz.fastadapter.app.items.ImageItemcom.mikepenz.fastadapter.app.MultiselectSampleActivity→com.mikepenz.fastadapter.app.items.SimpleItemcom.mikepenz.fastadapter.app.PagedActivity→com.mikepenz.fastadapter.app.items.SimpleImageItemcom.mikepenz.fastadapter.app.RadioButtonSampleActivity→com.mikepenz.fastadapter.app.items.RadioButtonSampleItemcom.mikepenz.fastadapter.app.RealmActivity→com.mikepenz.fastadapter.app.items.RealmSampleUserItemcom.mikepenz.fastadapter.app.SampleActivity→com.mikepenz.fastadapter.app.items.SimpleImageItemcom.mikepenz.fastadapter.app.SimpleItemListActivity→com.mikepenz.fastadapter.app.items.SimpleItemcom.mikepenz.fastadapter.app.SortActivity→com.mikepenz.fastadapter.app.items.SimpleItemcom.mikepenz.fastadapter.app.StickyHeaderSampleActivity→com.mikepenz.fastadapter.app.items.SimpleItemcom.mikepenz.fastadapter.app.SwipeDrawerListActivity→com.mikepenz.fastadapter.app.items.SwipeableDrawerItemcom.mikepenz.fastadapter.app.SwipeListActivity→com.mikepenz.fastadapter.app.items.SwipeableItem
- Direction
- app uses app.items, so a change to app.items can break app, while a change to app can't break app.items.
- Position
- Below the diagonal: app 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 | 21 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | Medium |
Roadmap
First, resolve the missing Architectural Decision Records by documenting significant design choices in a dedicated folder. Next, address the 79 orphaned files in the Knowledge Freshness dimension, prioritizing build.gradle and key extension files. Then, update the root README to include a high-level 'Architecture' or 'How it works' section. Finally, improve allocation hygiene on hot paths by increasing the use of allocation-aware idioms to enhance performance.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +12.0 pts | Low | ADR Quality |
| Resolve the 79 Orphaned file finding(s) in Knowledge Freshness — start with build.gradle (4), SelectExtension.kt, ExpandableExtension.kt. | +11.9 pts | Medium | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +10.9 pts | Medium | Architecture documentation |
| Add an 'Architecture' / 'How it works' section to the root README — the high-level shape. | +2.6 pts | Medium | Documentation (README) |
| Raise allocation-aware density on the hot paths — currently 29 use(s) across 16,322 production line(s) (~1.8/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10. | +1.8 pts | Medium | Allocation hygiene |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +1.7 pts | Medium | Deployment & Rollback |
| Keep implementation types off the public surface (Kotlin: `internal`) so internals can change without breaking consumers. | +1.4 pts | Medium | Library API & versioning |
| Resolve the 2 Most significant orphaned file finding(s) in Knowledge Freshness — start with FastAdapter.kt, SubItemUtil.kt. | +0.6 pts | Low | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| fastadapter-extensions-expandable/src/main/java/com/mikepenz/fastadapter/utils/SubItemUtil.kt | 7.1 | Mixed | Cognitive Complexity: SubItemUtil.selectAllSubItems (cognitive 41) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| app/src/main/java/com/mikepenz/fastadapter/app/EndlessScrollListActivity.kt | 7.4 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| fastadapter-extensions-swipe/src/main/java/com/mikepenz/fastadapter/swipe/SimpleSwipeCallback.kt | 7.8 | Mixed | Cognitive Complexity: SimpleSwipeCallback.onChildDraw (cognitive 29) |
| fastadapter-extensions-scroll/src/main/java/com/mikepenz/fastadapter/scroll/EndlessRecyclerOnScrollListener.kt | 7.8 | Mixed | Cognitive Complexity: EndlessRecyclerOnScrollListener.findOneVisibleChild (cognitive 27) |
| app/src/main/java/com/mikepenz/fastadapter/app/CheckBoxSampleActivity.kt | 7.8 | Mixed | Code Duplication: Duplicated block (12 lines × 2) |
| fastadapter-extensions-ui/src/main/java/com/mikepenz/fastadapter/ui/items/ThreeLineItem.kt | 7.8 | Mixed | Code Duplication: Duplicated block (9 lines × 2) |
| fastadapter-extensions-utils/src/main/java/com/mikepenz/fastadapter/adapters/AbstractWrapAdapter.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| fastadapter-extensions-drag/src/main/java/com/mikepenz/fastadapter/drag/SimpleDragCallback.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| app/src/main/java/com/mikepenz/fastadapter/app/SwipeListActivity.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| fastadapter-extensions-scroll/src/main/java/com/mikepenz/fastadapter/scroll/EndlessRecyclerOnTopScrollListener.kt | 8.5 | Near-clean | Cognitive Complexity: EndlessRecyclerOnTopScrollListener.findOneVisibleChild (cognitive 27) |
| app/src/main/java/com/mikepenz/fastadapter/app/ExpandableSampleActivity.kt | 8.5 | Near-clean | Cognitive Complexity: ExpandableSampleActivity.onCreate (cognitive 20) |
| fastadapter-extensions-utils/src/main/java/com/mikepenz/fastadapter/helpers/RangeSelectorHelper.kt | 8.5 | Near-clean | Cognitive Complexity: RangeSelectorHelper.selectRange (cognitive 19) |
| app/src/main/java/com/mikepenz/fastadapter/app/ExpandableMultiselectDeleteSampleActivity.kt | 8.5 | Near-clean | Cognitive Complexity: ExpandableMultiselectDeleteSampleActivity.onCreate (cognitive 17) |
| fastadapter/src/main/java/com/mikepenz/fastadapter/utils/EventHookUtil.kt | 8.5 | Near-clean | Cognitive Complexity: EventHookUtilKt.attachToView (cognitive 16) |
| fastadapter/src/main/java/com/mikepenz/fastadapter/FastAdapter.kt | 8.5 | Near-clean | God Classes: TooManyMethods: FastAdapter |
| fastadapter-extensions-paged/src/main/java/com/mikepenz/fastadapter/paged/PagedModelAdapter.kt | 8.5 | Near-clean | God Classes: TooManyMethods: PagedModelAdapter |
| app/src/main/java/com/mikepenz/fastadapter/app/SampleActivity.kt | 8.5 | Near-clean | God Classes: MethodTooLong: SampleActivity.onCreate |
| fastadapter/src/main/java/com/mikepenz/fastadapter/listeners/LongClickEventHook.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (7 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 56 of 56 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 56 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, 142 of 154 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.java) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.java) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: the analyzer environment could not run it. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — a Gradle build resolved 245 artifact(s) across its subprojects (123 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 81 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 33 of the 176 production source files in this repository: 95 are under the ~2,400-byte size floor this dimension measures over, and the remaining 48 have no attributable history left to measure.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `fastadapter/src/main/java/com/mikepenz/fastadapter/dsl/FastAdapterDsl.kt` 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Boot via AndroidApp (app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: . > Run with --info or --debug option to get more log output. > Run with --scan to get full insights. ============================================================================== 2: Task failed wit…; runtime evidence skipped (launch chosen because app/build.gradle applies the Android application plugin and gradlew builds it).
- C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Java, Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and 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.
- P1 CI/CD gates — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being SampleActivity.onCreate at 23 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: app/src/main/java/com/mikepenz/fastadapter/app/SampleActivity.kt (SampleActivity.onCreate at 23). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
D2 · Cognitive Complexity
11 method(s) exceeded the cognitive complexity threshold of 15; the worst was SubItemUtil.selectAllSubItems at 41.
What to do
- Bring the 11 bodies over 15 down to 15 or less in Cognitive Complexity — start with SubItemUtil.selectAllSubItems (cognitive 41), SubItemUtil.getAllItems (cognitive 36), SimpleSwipeCallback.onChildDraw (cognitive 29). — 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 11 together lifts Cognitive Complexity from 8.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
3 god class(es) detected.
What to do
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with FastAdapter.kt, PagedModelAdapter.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 MethodTooLong finding(s) in God Classes — start with SampleActivity.kt. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
14 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 2 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with CheckBoxSampleActivity.kt, DraggableSingleLineItem.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with SimpleSwipeCallback.kt, CheckBoxSampleActivity.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with LongClickEventHook.kt, SwipeDrawerListActivity.kt. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
12 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 11 of the 12 (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)
4 of 37 classes have LCOM4 above 3.
What to do
- Resolve the 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with SimpleItem.kt, SwipeableDrawerItem.kt, SwipeableItem.kt. — One of this dimension's main actionable groups (4 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
25 test methods: 25 unit, 0 integration, 0 BDD, 0 e2e.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 8 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 12 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. 19 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 15 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
3 deducted task-comment markers across 14040 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 3 TodoComment finding(s) in Explicit Debt — start with AbstractWrapAdapter.kt, SimpleDragCallback.kt, SwipeListActivity.kt. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 11 build units (Gradle) flagged as possibly oversized/incoherent.
D27 · Navigability
53 % of calls cross a namespace and 18 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
21 finding(s): 0 critical, 21 high, 0 medium, 0 low. 18 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `gradlew` (line 72, line 173) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — 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 18 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 (18 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
81 of 81 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is fastadapter/src/main/java/com/mikepenz/fastadapter/FastAdapter.kt. Counted over 81 of the 176 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 79 Orphaned file finding(s) in Knowledge Freshness — start with build.gradle (4), SelectExtension.kt, ExpandableExtension.kt. — One of this dimension's main actionable groups (79 recommendation-level).
- Resolve the 2 Most significant orphaned file finding(s) in Knowledge Freshness — start with FastAdapter.kt, SubItemUtil.kt. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
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. — One of this dimension's main actionable groups (1 warning-level).
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 35 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 11 of 11 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`./gradlew test` for the toolchain this pipeline already uses) and gate merges on it.
P10 · Library API & versioning
- 145/156 types (93%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Kotlin: `internal`) so internals can change without breaking consumers.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF2 · Allocation hygiene
What to do
- Raise allocation-aware density on the hot paths — currently 29 use(s) across 16,322 production line(s) (~1.8/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
- Java: on hot paths, work through buffer views (ByteBuffer/LongBuffer slices, MemorySegment) instead of copies, avoid boxing with primitive collections (fastutil, Eclipse Collections, HPPC, Trove), presize collections and StringBuilders, and pool expensive buffers (Netty's pooled allocator, commons-pool).
- Kotlin: on hot paths, use primitive arrays (IntArray, LongArray …) and @JvmInline value classes instead of boxed values, primitive collections (androidx.collection, fastutil) instead of boxed ones, and presize collections and StringBuilders.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — fastadapter-extensions-diff/src/main/java/com/mikepenz/fastadapter/diff/FastAdapterDiffUtil.kt:117
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 82% | Strong | Solid. |
| Architecture | 95% | Exemplary | Strongest area. |
| Maturity | 44% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 64% | Adequate | Acceptable, with room to improve. |
| Security | 71% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 69% | Adequate | Acceptable, with room to improve. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 62 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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: . > Run with --info or --debug option to get more log output. > Run with --scan to get full insights. ============================================================================== 2: Task failed wit…; runtime evidence skipped (launch chosen because app/build.gradle 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 — ~721 lines of test source are present (.java) 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 .java suite was found but not re-run
- D12 Dependency Hygiene — Not scored — a Gradle build resolved 245 artifact(s) across its subprojects (123 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Java, Kotlin not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Kotlin surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .java, .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — 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) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — 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 — not scored — this repository shows only 1 of the 3 signals this lens looks for (2 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JVM source (11 module(s), 160 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- 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.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X2 Cancellation propagation — no C# was loaded; this repository's Java and Kotlin were read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Kotlin request outside a suspend function has no caller's cancellation to honour
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 21 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 41 finding(s)
- Low cohesion: SimpleItem (LCOM4 5) app/src/main/java/com/mikepenz/fastadapter/app/items/SimpleItem.kt:17
- Low cohesion: SwipeableDrawerItem (LCOM4 4) app/src/main/java/com/mikepenz/fastadapter/app/items/SwipeableDrawerItem.kt:20
- Low cohesion: SwipeableItem (LCOM4 4) app/src/main/java/com/mikepenz/fastadapter/app/items/SwipeableItem.kt:19
- Low cohesion: SimpleSubItem (LCOM4 4) app/src/main/java/com/mikepenz/fastadapter/app/items/expandable/SimpleSubItem.kt:16
- TodoComment fastadapter-extensions-utils/src/main/java/com/mikepenz/fastadapter/adapters/AbstractWrapAdapter.kt:87
- TodoComment fastadapter-extensions-drag/src/main/java/com/mikepenz/fastadapter/drag/SimpleDragCallback.kt:62
- TodoComment app/src/main/java/com/mikepenz/fastadapter/app/SwipeListActivity.kt:224
- TooManyMethods: FastAdapter fastadapter/src/main/java/com/mikepenz/fastadapter/FastAdapter.kt:41
- TooManyMethods: PagedModelAdapter fastadapter-extensions-paged/src/main/java/com/mikepenz/fastadapter/paged/PagedModelAdapter.kt:27
- Duplicated block (12 lines × 2) app/src/main/java/com/mikepenz/fastadapter/app/CheckBoxSampleActivity.kt:26
- Duplicated block (12 lines × 2) app/src/main/java/com/mikepenz/fastadapter/app/items/DraggableSingleLineItem.kt:29
- Duplicated block (11 lines × 2) fastadapter-extensions-swipe/src/main/java/com/mikepenz/fastadapter/swipe/SimpleSwipeCallback.kt:95
- Duplicated block (11 lines × 2) app/src/main/java/com/mikepenz/fastadapter/app/CheckBoxSampleActivity.kt:84
- Duplicated block (7 lines × 2) fastadapter/src/main/java/com/mikepenz/fastadapter/listeners/LongClickEventHook.kt:25
- Duplicated block (7 lines × 2) app/src/main/java/com/mikepenz/fastadapter/app/SwipeDrawerListActivity.kt:207
- SubItemUtil.selectAllSubItems (cognitive 41) fastadapter-extensions-expandable/src/main/java/com/mikepenz/fastadapter/utils/SubItemUtil.kt:187
- SubItemUtil.getAllItems (cognitive 36) fastadapter-extensions-expandable/src/main/java/com/mikepenz/fastadapter/utils/SubItemUtil.kt:92
- SimpleSwipeCallback.onChildDraw (cognitive 29) fastadapter-extensions-swipe/src/main/java/com/mikepenz/fastadapter/swipe/SimpleSwipeCallback.kt:130
- SubItemUtil.delete (cognitive 29) fastadapter-extensions-expandable/src/main/java/com/mikepenz/fastadapter/utils/SubItemUtil.kt:305
- EndlessRecyclerOnScrollListener.findOneVisibleChild (cognitive 27) fastadapter-extensions-scroll/src/main/java/com/mikepenz/fastadapter/scroll/EndlessRecyclerOnScrollListener.kt:75
- EndlessRecyclerOnTopScrollListener.findOneVisibleChild (cognitive 27) fastadapter-extensions-scroll/src/main/java/com/mikepenz/fastadapter/scroll/EndlessRecyclerOnTopScrollListener.kt:111
- SubItemUtil.deleteSelected (cognitive 23) fastadapter-extensions-expandable/src/main/java/com/mikepenz/fastadapter/utils/SubItemUtil.kt:237
- ExpandableSampleActivity.onCreate (cognitive 20) app/src/main/java/com/mikepenz/fastadapter/app/ExpandableSampleActivity.kt:25
- RangeSelectorHelper.selectRange (cognitive 19) fastadapter-extensions-utils/src/main/java/com/mikepenz/fastadapter/helpers/RangeSelectorHelper.kt:111
- ExpandableMultiselectDeleteSampleActivity.onCreate (cognitive 17) app/src/main/java/com/mikepenz/fastadapter/app/ExpandableMultiselectDeleteSampleActivity.kt:41
- EventHookUtilKt.attachToView (cognitive 16) fastadapter/src/main/java/com/mikepenz/fastadapter/utils/EventHookUtil.kt:36
- MethodTooLong: SampleActivity.onCreate app/src/main/java/com/mikepenz/fastadapter/app/SampleActivity.kt:53
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) app/src/main/java/com/mikepenz/fastadapter/app/EndlessScrollListActivity.kt:150
- Duplicated block (19 lines × 2) fastadapter-extensions-scroll/src/main/java/com/mikepenz/fastadapter/scroll/EndlessRecyclerOnScrollListener.kt:94
- Duplicated block (17 lines × 2) fastadapter-extensions-expandable/src/main/java/com/mikepenz/fastadapter/utils/SubItemUtil.kt:263
- Duplicated block (4–15 lines × 3) app/src/main/java/com/mikepenz/fastadapter/app/EndlessScrollListActivity.kt:158
- Duplicated block (9 lines × 2) fastadapter-extensions-ui/src/main/java/com/mikepenz/fastadapter/ui/items/ThreeLineItem.kt:96
- Duplicated block (5 lines × 4) app/src/main/java/com/mikepenz/fastadapter/app/EndlessScrollListActivity.kt:152
- Duplicated block (9 lines × 14) app/src/main/java/com/mikepenz/fastadapter/app/AdvancedSampleActivity.kt:182
- Duplicated block (8 lines × 2) fastadapter-extensions-ui/src/main/java/com/mikepenz/fastadapter/ui/items/ThreeLineItem.kt:106
- Duplicated block (7 lines × 3) fastadapter-extensions-binding/src/main/java/com/mikepenz/fastadapter/binding/listeners/BindingEventHookExtensions.kt:26
- Swallowed exception (empty catch) fastadapter-extensions-diff/src/main/java/com/mikepenz/fastadapter/diff/FastAdapterDiffUtil.kt:117
Minor — 92 finding(s)
- Orphaned file fastadapter/src/main/java/com/mikepenz/fastadapter/select/SelectExtension.kt:1
- Orphaned file fastadapter-extensions-expandable/src/main/java/com/mikepenz/fastadapter/expandable/ExpandableExtension.kt:1
- Orphaned file fastadapter/src/main/java/com/mikepenz/fastadapter/adapters/ModelAdapter.kt:1
- Orphaned file app/src/main/java/com/mikepenz/fastadapter/app/dummy/ImageDummyData.kt:1
- Orphaned file app/src/main/java/com/mikepenz/fastadapter/app/SampleActivity.kt:1
- Orphaned file fastadapter-extensions-paged/src/main/java/com/mikepenz/fastadapter/paged/PagedModelAdapter.kt:1
- Orphaned file fastadapter-extensions-scroll/src/main/java/com/mikepenz/fastadapter/scroll/EndlessScrollHelper.kt:1
- Orphaned file fastadapter-extensions-diff/src/main/java/com/mikepenz/fastadapter/diff/FastAdapterDiffUtil.kt:1
- Orphaned file fastadapter/src/main/java/com/mikepenz/fastadapter/adapters/ItemFilter.kt:1
- Orphaned file app/src/main/java/com/mikepenz/fastadapter/app/ExpandableMultiselectDeleteSampleActivity.kt:1
- Orphaned file fastadapter-extensions-ui/src/main/java/com/mikepenz/fastadapter/ui/dialog/FastAdapterDialog.kt:1
- Orphaned file app/src/main/java/com/mikepenz/fastadapter/app/SwipeDrawerListActivity.kt:1
- Orphaned file fastadapter-extensions-swipe/src/main/java/com/mikepenz/fastadapter/swipe/SimpleSwipeDrawerCallback.kt:1
- Orphaned file app/src/main/java/com/mikepenz/fastadapter/app/SwipeListActivity.kt:1
- Orphaned file fastadapter-extensions-utils/src/main/java/com/mikepenz/fastadapter/helpers/ActionModeHelper.kt:1
- Orphaned file app/src/main/java/com/mikepenz/fastadapter/app/AdvancedSampleActivity.kt:1
- Orphaned file app/src/main/java/com/mikepenz/fastadapter/app/SortActivity.kt:1
- Orphaned file app/src/main/java/com/mikepenz/fastadapter/app/DragAndDropActivity.kt:1
- Orphaned file fastadapter-extensions-paged/src/main/java/com/mikepenz/fastadapter/paged/PagedItemListImpl.kt:1
- Orphaned file app/src/main/java/com/mikepenz/fastadapter/app/adapters/StickyHeaderAdapter.kt:1
- Orphaned file app/src/main/java/com/mikepenz/fastadapter/app/EndlessScrollListActivity.kt:1
- Orphaned file app/src/main/java/com/mikepenz/fastadapter/app/MultiselectSampleActivity.kt:1
- Orphaned file fastadapter-extensions-utils/src/main/java/com/mikepenz/fastadapter/helpers/UndoHelper.kt:1
- Orphaned file fastadapter-extensions-utils/src/main/java/com/mikepenz/fastadapter/helpers/RangeSelectorHelper.kt:1
- Orphaned file app/src/main/java/com/mikepenz/fastadapter/app/SimpleItemListActivity.kt:1
- Most significant orphaned file fastadapter/src/main/java/com/mikepenz/fastadapter/FastAdapter.kt:1
- Most significant orphaned file fastadapter-extensions-expandable/src/main/java/com/mikepenz/fastadapter/utils/SubItemUtil.kt:1
- Duplicated predicate fastadapter-extensions-scroll/src/main/java/com/mikepenz/fastadapter/scroll/EndlessRecyclerOnScrollListener.kt:101
- Duplicated predicate app/src/main/java/com/mikepenz/fastadapter/app/items/RealmSampleUserItem.kt:178
- No ADRs found
- Dormant codebase
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Large public API surface
- No release approval gate
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f0d091ceac0147d291685bef90d75db4/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f0d091ceac0147d291685bef90d75db4/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 21 | 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) — 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 1 file(s) — `fastadapter/src/main/java/com/mikepenz/fastadapter/dsl/FastAdapterDsl.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |