Executive summary
algolia/instantsearch-android falls short of our standard for production because we found no recorded design decisions and no architecture document or diagram, and 29 files are no longer known to anyone active in the project. It scores 65.2 out of 100 and is rated Adequate, and all 11 of its critical findings are security problems in the build pipeline.
Maturity, at 58.9, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 5.4 points. Having someone learn and document the 29 files no active contributor knows comes next, worth about 4.2 points. Raising Maturity to 70 would lift the score to about 68.7.
Eleven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk.
The product code is 25,239 lines, about €39,000 to rebuild.
If Maturity rose from 58.9 to 70, the lowest score rated Strong, the score would rise from 65.2 to about 68.7.
Rebuild cost: about €39,000 · Estimate
| Cost to rebuild | €13,000 to €65,000, for 217 to 689 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 65. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 25,239 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 agent.model | 2 core.connection | 3 core.subscription | 4 filter | 5 searcher.multi.internal.types | 6 core.hits | 7 core.loading | 8 core.number.range | 9 core.searchbox | 10 core.searcher | 11 core.selectable | 12 core.selectable.list | 13 core.selectable.map | 14 core.tree | 15 filter.Filter | 16 insights.internal.data.local.model.InsightsEventDO | 17 compose.selectable.list | 18 core.number | 19 core.relevantsort | 20 hierarchical | 21 insights.internal.data.local.model | 22 searchbox | 23 stats | 24 filter.state | 25 insights.internal | 26 filter.clear | 27 filter.current | 28 filter.list | 29 relateditems.internal | 30 searcher | 31 android.paging3 | 32 filter.current.internal | 33 filter.facet | 34 filter.facet.dynamic | 35 filter.list.FilterListConnector | 36 searcher.internal | 37 filter.facet.internal | 38 searcher.multi.internal | 39 searcher.composition.internal | 40 searcher.hits.internal |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 agent.model | ||||||||||||||||||||||||||||||||||||||||
| 2 core.connection | ||||||||||||||||||||||||||||||||||||||||
| 3 core.subscription | ||||||||||||||||||||||||||||||||||||||||
| 4 filter | ||||||||||||||||||||||||||||||||||||||||
| 5 searcher.multi.internal.types | ||||||||||||||||||||||||||||||||||||||||
| 6 core.hits | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 core.loading | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 8 core.number.range | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 9 core.searchbox | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 10 core.searcher | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 core.selectable | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 12 core.selectable.list | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 13 core.selectable.map | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 14 core.tree | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 filter.Filter | 4 | |||||||||||||||||||||||||||||||||||||||
| 16 insights.internal.data.local.model.InsightsEventDO | 3 | |||||||||||||||||||||||||||||||||||||||
| 17 compose.selectable.list | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 core.number | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 core.relevantsort | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 hierarchical | 3 | 2 | 5 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||
| 21 insights.internal.data.local.model | 2 | |||||||||||||||||||||||||||||||||||||||
| 22 searchbox | 3 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 23 stats | 3 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 24 filter.state | 1 | 8 | 5 | 2 | ||||||||||||||||||||||||||||||||||||
| 25 insights.internal | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 26 filter.clear | 3 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 27 filter.current | 3 | 5 | 7 | |||||||||||||||||||||||||||||||||||||
| 28 filter.list | 3 | 3 | 5 | |||||||||||||||||||||||||||||||||||||
| 29 relateditems.internal | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 searcher | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 android.paging3 | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 filter.current.internal | 2 | 3 | 5 | 2 | ||||||||||||||||||||||||||||||||||||
| 33 filter.facet | 3 | 1 | 4 | 5 | 4 | |||||||||||||||||||||||||||||||||||
| 34 filter.facet.dynamic | 3 | 2 | 3 | 4 | 2 | |||||||||||||||||||||||||||||||||||
| 35 filter.list.FilterListConnector | 4 | 1 | 4 | 3 | 8 | 4 | ||||||||||||||||||||||||||||||||||
| 36 searcher.internal | 2 | 3 | 3 | 4 | 1 | |||||||||||||||||||||||||||||||||||
| 37 filter.facet.internal | 4 | 1 | 1 | 3 | 2 | 4 | ||||||||||||||||||||||||||||||||||
| 38 searcher.multi.internal | 1 | 5 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 searcher.composition.internal | 2 | 3 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 40 searcher.hits.internal | 1 | 4 | 3 | 1 | 3 | 3 |
6→2 core.hits uses core.connection✕
- Connections
- 1 pair of types, where a type in core.hits uses a type in core.connection.
- The types involved
com.algolia.instantsearch.core.hits.HitsConnectionKt→com.algolia.instantsearch.core.connection.Connection
- Direction
- core.hits uses core.connection, so a change to core.connection can break core.hits, while a change to core.hits can't break core.connection.
- Position
- Below the diagonal: core.hits uses a module listed above it, which is the healthy direction.
7→2 core.loading uses core.connection✕
- Connections
- 1 pair of types, where a type in core.loading uses a type in core.connection.
- The types involved
com.algolia.instantsearch.core.loading.LoadingConnectionKt→com.algolia.instantsearch.core.connection.Connection
- Direction
- core.loading uses core.connection, so a change to core.connection can break core.loading, while a change to core.loading can't break core.connection.
- Position
- Below the diagonal: core.loading uses a module listed above it, which is the healthy direction.
7→3 core.loading uses core.subscription✕
- Connections
- 2 pairs of types, where a type in core.loading uses a type in core.subscription.
- The types involved
com.algolia.instantsearch.core.loading.LoadingViewModel→com.algolia.instantsearch.core.subscription.SubscriptionEventcom.algolia.instantsearch.core.loading.LoadingViewModel→com.algolia.instantsearch.core.subscription.SubscriptionValue
- Direction
- core.loading uses core.subscription, so a change to core.subscription can break core.loading, while a change to core.loading can't break core.subscription.
- Position
- Below the diagonal: core.loading uses a module listed above it, which is the healthy direction.
8→2 core.number.range uses core.connection✕
- Connections
- 1 pair of types, where a type in core.number.range uses a type in core.connection.
- The types involved
com.algolia.instantsearch.core.number.range.NumberRangeConnectionKt→com.algolia.instantsearch.core.connection.Connection
- Direction
- core.number.range uses core.connection, so a change to core.connection can break core.number.range, while a change to core.number.range can't break core.connection.
- Position
- Below the diagonal: core.number.range uses a module listed above it, which is the healthy direction.
8→3 core.number.range uses core.subscription✕
- Connections
- 2 pairs of types, where a type in core.number.range uses a type in core.subscription.
- The types involved
com.algolia.instantsearch.core.number.range.NumberRangeViewModel→com.algolia.instantsearch.core.subscription.SubscriptionEventcom.algolia.instantsearch.core.number.range.NumberRangeViewModel→com.algolia.instantsearch.core.subscription.SubscriptionValue
- Direction
- core.number.range uses core.subscription, so a change to core.subscription can break core.number.range, while a change to core.number.range can't break core.subscription.
- Position
- Below the diagonal: core.number.range uses a module listed above it, which is the healthy direction.
9→2 core.searchbox uses core.connection✕
- Connections
- 1 pair of types, where a type in core.searchbox uses a type in core.connection.
- The types involved
com.algolia.instantsearch.core.searchbox.SearchBoxConnectionKt→com.algolia.instantsearch.core.connection.Connection
- Direction
- core.searchbox uses core.connection, so a change to core.connection can break core.searchbox, while a change to core.searchbox can't break core.connection.
- Position
- Below the diagonal: core.searchbox uses a module listed above it, which is the healthy direction.
9→3 core.searchbox uses core.subscription✕
- Connections
- 2 pairs of types, where a type in core.searchbox uses a type in core.subscription.
- The types involved
com.algolia.instantsearch.core.searchbox.SearchBoxViewModel→com.algolia.instantsearch.core.subscription.SubscriptionEventcom.algolia.instantsearch.core.searchbox.SearchBoxViewModel→com.algolia.instantsearch.core.subscription.SubscriptionValue
- Direction
- core.searchbox uses core.subscription, so a change to core.subscription can break core.searchbox, while a change to core.searchbox can't break core.subscription.
- Position
- Below the diagonal: core.searchbox uses a module listed above it, which is the healthy direction.
10→2 core.searcher uses core.connection✕
- Connections
- 1 pair of types, where a type in core.searcher uses a type in core.connection.
- The types involved
com.algolia.instantsearch.core.searcher.SearcherConnectionKt→com.algolia.instantsearch.core.connection.Connection
- Direction
- core.searcher uses core.connection, so a change to core.connection can break core.searcher, while a change to core.searcher can't break core.connection.
- Position
- Below the diagonal: core.searcher uses a module listed above it, which is the healthy direction.
10→3 core.searcher uses core.subscription✕
- Connections
- 1 pair of types, where a type in core.searcher uses a type in core.subscription.
- The types involved
com.algolia.instantsearch.core.searcher.Searcher→com.algolia.instantsearch.core.subscription.SubscriptionValue
- Direction
- core.searcher uses core.subscription, so a change to core.subscription can break core.searcher, while a change to core.searcher can't break core.subscription.
- Position
- Below the diagonal: core.searcher uses a module listed above it, which is the healthy direction.
11→2 core.selectable uses core.connection✕
- Connections
- 1 pair of types, where a type in core.selectable uses a type in core.connection.
- The types involved
com.algolia.instantsearch.core.selectable.SelectableItemConnectionKt→com.algolia.instantsearch.core.connection.Connection
- Direction
- core.selectable uses core.connection, so a change to core.connection can break core.selectable, while a change to core.selectable can't break core.connection.
- Position
- Below the diagonal: core.selectable uses a module listed above it, which is the healthy direction.
11→3 core.selectable uses core.subscription✕
- Connections
- 2 pairs of types, where a type in core.selectable uses a type in core.subscription.
- The types involved
com.algolia.instantsearch.core.selectable.SelectableItemViewModel→com.algolia.instantsearch.core.subscription.SubscriptionEventcom.algolia.instantsearch.core.selectable.SelectableItemViewModel→com.algolia.instantsearch.core.subscription.SubscriptionValue
- Direction
- core.selectable uses core.subscription, so a change to core.subscription can break core.selectable, while a change to core.selectable can't break core.subscription.
- Position
- Below the diagonal: core.selectable uses a module listed above it, which is the healthy direction.
12→2 core.selectable.list uses core.connection✕
- Connections
- 1 pair of types, where a type in core.selectable.list uses a type in core.connection.
- The types involved
com.algolia.instantsearch.core.selectable.list.SelectableListConnectionKt→com.algolia.instantsearch.core.connection.Connection
- Direction
- core.selectable.list uses core.connection, so a change to core.connection can break core.selectable.list, while a change to core.selectable.list can't break core.connection.
- Position
- Below the diagonal: core.selectable.list uses a module listed above it, which is the healthy direction.
12→3 core.selectable.list uses core.subscription✕
- Connections
- 2 pairs of types, where a type in core.selectable.list uses a type in core.subscription.
- The types involved
com.algolia.instantsearch.core.selectable.list.SelectableListViewModel→com.algolia.instantsearch.core.subscription.SubscriptionEventcom.algolia.instantsearch.core.selectable.list.SelectableListViewModel→com.algolia.instantsearch.core.subscription.SubscriptionValue
- Direction
- core.selectable.list uses core.subscription, so a change to core.subscription can break core.selectable.list, while a change to core.selectable.list can't break core.subscription.
- Position
- Below the diagonal: core.selectable.list uses a module listed above it, which is the healthy direction.
13→2 core.selectable.map uses core.connection✕
- Connections
- 1 pair of types, where a type in core.selectable.map uses a type in core.connection.
- The types involved
com.algolia.instantsearch.core.selectable.map.SelectableMapConnectionKt→com.algolia.instantsearch.core.connection.Connection
- Direction
- core.selectable.map uses core.connection, so a change to core.connection can break core.selectable.map, while a change to core.selectable.map can't break core.connection.
- Position
- Below the diagonal: core.selectable.map uses a module listed above it, which is the healthy direction.
13→3 core.selectable.map uses core.subscription✕
- Connections
- 2 pairs of types, where a type in core.selectable.map uses a type in core.subscription.
- The types involved
com.algolia.instantsearch.core.selectable.map.SelectableMapViewModel→com.algolia.instantsearch.core.subscription.SubscriptionEventcom.algolia.instantsearch.core.selectable.map.SelectableMapViewModel→com.algolia.instantsearch.core.subscription.SubscriptionValue
- Direction
- core.selectable.map uses core.subscription, so a change to core.subscription can break core.selectable.map, while a change to core.selectable.map can't break core.subscription.
- Position
- Below the diagonal: core.selectable.map uses a module listed above it, which is the healthy direction.
14→2 core.tree uses core.connection✕
- Connections
- 1 pair of types, where a type in core.tree uses a type in core.connection.
- The types involved
com.algolia.instantsearch.core.tree.TreeConnectionKt→com.algolia.instantsearch.core.connection.Connection
- Direction
- core.tree uses core.connection, so a change to core.connection can break core.tree, while a change to core.tree can't break core.connection.
- Position
- Below the diagonal: core.tree uses a module listed above it, which is the healthy direction.
14→3 core.tree uses core.subscription✕
- Connections
- 1 pair of types, where a type in core.tree uses a type in core.subscription.
- The types involved
com.algolia.instantsearch.core.tree.TreeViewModel→com.algolia.instantsearch.core.subscription.SubscriptionValue
- Direction
- core.tree uses core.subscription, so a change to core.subscription can break core.tree, while a change to core.tree can't break core.subscription.
- Position
- Below the diagonal: core.tree uses a module listed above it, which is the healthy direction.
15→4 filter.Filter uses filter✕
- Connections
- 4 pairs of types, where a type in filter.Filter uses a type in filter.
- The types involved
com.algolia.instantsearch.filter.Filter.Facet→com.algolia.instantsearch.filter.Filtercom.algolia.instantsearch.filter.Filter.Numeric→com.algolia.instantsearch.filter.Filtercom.algolia.instantsearch.filter.Filter.Numeric→com.algolia.instantsearch.filter.NumericOperatorcom.algolia.instantsearch.filter.Filter.Tag→com.algolia.instantsearch.filter.Filter
- Direction
- filter.Filter uses filter, so a change to filter can break filter.Filter, while a change to filter.Filter can't break filter.
- Position
- Below the diagonal: filter.Filter uses a module listed above it, which is the healthy direction.
16→21 insights.internal.data.local.model.InsightsEventDO uses insights.internal.data.local.model part of a loop✕
- Connections
- 3 pairs of types, where a type in insights.internal.data.local.model.InsightsEventDO uses a type in insights.internal.data.local.model.
- The types involved
com.algolia.instantsearch.insights.internal.data.local.model.InsightsEventDO.Builder→com.algolia.instantsearch.insights.internal.data.local.model.FilterFacetDOcom.algolia.instantsearch.insights.internal.data.local.model.InsightsEventDO.Builder→com.algolia.instantsearch.insights.internal.data.local.model.InsightsEventDOcom.algolia.instantsearch.insights.internal.data.local.model.InsightsEventDO.Builder→com.algolia.instantsearch.insights.internal.data.local.model.ObjectDataDO
- Direction
- insights.internal.data.local.model.InsightsEventDO uses insights.internal.data.local.model, so a change to insights.internal.data.local.model can break insights.internal.data.local.model.InsightsEventDO, while a change to insights.internal.data.local.model.InsightsEventDO can't break insights.internal.data.local.model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→12 compose.selectable.list uses core.selectable.list✕
- Connections
- 1 pair of types, where a type in compose.selectable.list uses a type in core.selectable.list.
- The types involved
com.algolia.instantsearch.compose.selectable.list.SelectableListState→com.algolia.instantsearch.core.selectable.list.SelectableListView
- Direction
- compose.selectable.list uses core.selectable.list, so a change to core.selectable.list can break compose.selectable.list, while a change to compose.selectable.list can't break core.selectable.list.
- Position
- Below the diagonal: compose.selectable.list uses a module listed above it, which is the healthy direction.
18→2 core.number uses core.connection✕
- Connections
- 1 pair of types, where a type in core.number uses a type in core.connection.
- The types involved
com.algolia.instantsearch.core.number.NumberConnectionKt→com.algolia.instantsearch.core.connection.Connection
- Direction
- core.number uses core.connection, so a change to core.connection can break core.number, while a change to core.number can't break core.connection.
- Position
- Below the diagonal: core.number uses a module listed above it, which is the healthy direction.
18→3 core.number uses core.subscription✕
- Connections
- 2 pairs of types, where a type in core.number uses a type in core.subscription.
- The types involved
com.algolia.instantsearch.core.number.NumberViewModel→com.algolia.instantsearch.core.subscription.SubscriptionEventcom.algolia.instantsearch.core.number.NumberViewModel→com.algolia.instantsearch.core.subscription.SubscriptionValue
- Direction
- core.number uses core.subscription, so a change to core.subscription can break core.number, while a change to core.number can't break core.subscription.
- Position
- Below the diagonal: core.number uses a module listed above it, which is the healthy direction.
18→8 core.number uses core.number.range✕
- Connections
- 1 pair of types, where a type in core.number uses a type in core.number.range.
- The types involved
com.algolia.instantsearch.core.number.NumberViewModel→com.algolia.instantsearch.core.number.range.Range
- Direction
- core.number uses core.number.range, so a change to core.number.range can break core.number, while a change to core.number can't break core.number.range.
- Position
- Below the diagonal: core.number uses a module listed above it, which is the healthy direction.
19→2 core.relevantsort uses core.connection✕
- Connections
- 2 pairs of types, where a type in core.relevantsort uses a type in core.connection.
- The types involved
com.algolia.instantsearch.core.relevantsort.RelevantSortConnectionKt→com.algolia.instantsearch.core.connection.Connectioncom.algolia.instantsearch.core.relevantsort.RelevantSortConnector→com.algolia.instantsearch.core.connection.Connection
- Direction
- core.relevantsort uses core.connection, so a change to core.connection can break core.relevantsort, while a change to core.relevantsort can't break core.connection.
- Position
- Below the diagonal: core.relevantsort uses a module listed above it, which is the healthy direction.
19→3 core.relevantsort uses core.subscription✕
- Connections
- 1 pair of types, where a type in core.relevantsort uses a type in core.subscription.
- The types involved
com.algolia.instantsearch.core.relevantsort.RelevantSortViewModel→com.algolia.instantsearch.core.subscription.SubscriptionValue
- Direction
- core.relevantsort uses core.subscription, so a change to core.subscription can break core.relevantsort, while a change to core.relevantsort can't break core.subscription.
- Position
- Below the diagonal: core.relevantsort uses a module listed above it, which is the healthy direction.
19→10 core.relevantsort uses core.searcher✕
- Connections
- 1 pair of types, where a type in core.relevantsort uses a type in core.searcher.
- The types involved
com.algolia.instantsearch.core.relevantsort.RelevantSortConnector→com.algolia.instantsearch.core.searcher.Searcher
- Direction
- core.relevantsort uses core.searcher, so a change to core.searcher can break core.relevantsort, while a change to core.relevantsort can't break core.searcher.
- Position
- Below the diagonal: core.relevantsort uses a module listed above it, which is the healthy direction.
20→2 hierarchical uses core.connection✕
- Connections
- 3 pairs of types, where a type in hierarchical uses a type in core.connection.
- The types involved
com.algolia.instantsearch.hierarchical.HierarchicalConnectionKt→com.algolia.instantsearch.core.connection.Connectioncom.algolia.instantsearch.hierarchical.HierarchicalConnector→com.algolia.instantsearch.core.connection.AbstractConnectioncom.algolia.instantsearch.hierarchical.HierarchicalConnector→com.algolia.instantsearch.core.connection.Connection
- Direction
- hierarchical uses core.connection, so a change to core.connection can break hierarchical, while a change to hierarchical can't break core.connection.
- Position
- Below the diagonal: hierarchical uses a module listed above it, which is the healthy direction.
20→3 hierarchical uses core.subscription✕
- Connections
- 2 pairs of types, where a type in hierarchical uses a type in core.subscription.
- The types involved
com.algolia.instantsearch.hierarchical.HierarchicalViewModel→com.algolia.instantsearch.core.subscription.SubscriptionEventcom.algolia.instantsearch.hierarchical.HierarchicalViewModel→com.algolia.instantsearch.core.subscription.SubscriptionValue
- Direction
- hierarchical uses core.subscription, so a change to core.subscription can break hierarchical, while a change to hierarchical can't break core.subscription.
- Position
- Below the diagonal: hierarchical uses a module listed above it, which is the healthy direction.
20→14 hierarchical uses core.tree✕
- Connections
- 5 pairs of types, where a type in hierarchical uses a type in core.tree.
- The types involved
com.algolia.instantsearch.hierarchical.DefaultHierarchicalPresenter→com.algolia.instantsearch.core.tree.Treecom.algolia.instantsearch.hierarchical.HierarchicalConnectionKt→com.algolia.instantsearch.core.tree.Treecom.algolia.instantsearch.hierarchical.HierarchicalConnectionKt→com.algolia.instantsearch.core.tree.TreeViewcom.algolia.instantsearch.hierarchical.HierarchicalViewModel→com.algolia.instantsearch.core.tree.Treecom.algolia.instantsearch.hierarchical.HierarchicalViewModel→com.algolia.instantsearch.core.tree.TreeViewModel
- Direction
- hierarchical uses core.tree, so a change to core.tree can break hierarchical, while a change to hierarchical can't break core.tree.
- Position
- Below the diagonal: hierarchical uses a module listed above it, which is the healthy direction.
20→15 hierarchical uses filter.Filter✕
- Connections
- 1 pair of types, where a type in hierarchical uses a type in filter.Filter.
- The types involved
com.algolia.instantsearch.hierarchical.HierarchicalFilter→com.algolia.instantsearch.filter.Filter.Facet
- Direction
- hierarchical uses filter.Filter, so a change to filter.Filter can break hierarchical, while a change to hierarchical can't break filter.Filter.
- Position
- Below the diagonal: hierarchical uses a module listed above it, which is the healthy direction.
20→24 hierarchical uses filter.state part of a loop✕
- Connections
- 2 pairs of types, where a type in hierarchical uses a type in filter.state.
- The types involved
com.algolia.instantsearch.hierarchical.HierarchicalConnectionKt→com.algolia.instantsearch.filter.state.FilterStatecom.algolia.instantsearch.hierarchical.HierarchicalConnector→com.algolia.instantsearch.filter.state.FilterState
- Direction
- hierarchical uses filter.state, so a change to filter.state can break hierarchical, while a change to hierarchical can't break filter.state.
- 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→30 hierarchical uses searcher part of a loop✕
- Connections
- 2 pairs of types, where a type in hierarchical uses a type in searcher.
- The types involved
com.algolia.instantsearch.hierarchical.HierarchicalConnectionKt→com.algolia.instantsearch.searcher.SearcherForHitscom.algolia.instantsearch.hierarchical.HierarchicalConnector→com.algolia.instantsearch.searcher.SearcherForHits
- Direction
- hierarchical uses searcher, so a change to searcher can break hierarchical, while a change to hierarchical can't break searcher.
- 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→16 insights.internal.data.local.model uses insights.internal.data.local.model.InsightsEventDO✕
- Connections
- 2 pairs of types, where a type in insights.internal.data.local.model uses a type in insights.internal.data.local.model.InsightsEventDO.
- The types involved
com.algolia.instantsearch.insights.internal.data.local.model.InsightsEventDO→com.algolia.instantsearch.insights.internal.data.local.model.InsightsEventDO.EventSubtypecom.algolia.instantsearch.insights.internal.data.local.model.InsightsEventDO→com.algolia.instantsearch.insights.internal.data.local.model.InsightsEventDO.EventType
- Direction
- insights.internal.data.local.model uses insights.internal.data.local.model.InsightsEventDO, so a change to insights.internal.data.local.model.InsightsEventDO can break insights.internal.data.local.model, while a change to insights.internal.data.local.model can't break insights.internal.data.local.model.InsightsEventDO.
- Position
- Below the diagonal: insights.internal.data.local.model uses a module listed above it, which is the healthy direction.
22→2 searchbox uses core.connection✕
- Connections
- 3 pairs of types, where a type in searchbox uses a type in core.connection.
- The types involved
com.algolia.instantsearch.searchbox.SearchBoxConnectionKt→com.algolia.instantsearch.core.connection.Connectioncom.algolia.instantsearch.searchbox.SearchBoxConnector→com.algolia.instantsearch.core.connection.AbstractConnectioncom.algolia.instantsearch.searchbox.SearchBoxConnector→com.algolia.instantsearch.core.connection.Connection
- Direction
- searchbox uses core.connection, so a change to core.connection can break searchbox, while a change to searchbox can't break core.connection.
- Position
- Below the diagonal: searchbox uses a module listed above it, which is the healthy direction.
22→9 searchbox uses core.searchbox✕
- Connections
- 2 pairs of types, where a type in searchbox uses a type in core.searchbox.
- The types involved
com.algolia.instantsearch.searchbox.SearchBoxConnectionKt→com.algolia.instantsearch.core.searchbox.SearchBoxViewcom.algolia.instantsearch.searchbox.SearchBoxConnector→com.algolia.instantsearch.core.searchbox.SearchBoxViewModel
- Direction
- searchbox uses core.searchbox, so a change to core.searchbox can break searchbox, while a change to searchbox can't break core.searchbox.
- Position
- Below the diagonal: searchbox uses a module listed above it, which is the healthy direction.
22→10 searchbox uses core.searcher✕
- Connections
- 4 pairs of types, where a type in searchbox uses a type in core.searcher.
- The types involved
com.algolia.instantsearch.searchbox.SearchBoxConnectionKt→com.algolia.instantsearch.core.searcher.Debouncercom.algolia.instantsearch.searchbox.SearchBoxConnectionKt→com.algolia.instantsearch.core.searcher.Searchercom.algolia.instantsearch.searchbox.SearchBoxConnector→com.algolia.instantsearch.core.searcher.Debouncercom.algolia.instantsearch.searchbox.SearchBoxConnector→com.algolia.instantsearch.core.searcher.Searcher
- Direction
- searchbox uses core.searcher, so a change to core.searcher can break searchbox, while a change to searchbox can't break core.searcher.
- Position
- Below the diagonal: searchbox uses a module listed above it, which is the healthy direction.
23→2 stats uses core.connection✕
- Connections
- 3 pairs of types, where a type in stats uses a type in core.connection.
- The types involved
com.algolia.instantsearch.stats.StatsConnectionKt→com.algolia.instantsearch.core.connection.Connectioncom.algolia.instantsearch.stats.StatsConnector→com.algolia.instantsearch.core.connection.AbstractConnectioncom.algolia.instantsearch.stats.StatsConnector→com.algolia.instantsearch.core.connection.Connection
- Direction
- stats uses core.connection, so a change to core.connection can break stats, while a change to stats can't break core.connection.
- Position
- Below the diagonal: stats uses a module listed above it, which is the healthy direction.
23→3 stats uses core.subscription✕
- Connections
- 1 pair of types, where a type in stats uses a type in core.subscription.
- The types involved
com.algolia.instantsearch.stats.StatsViewModel→com.algolia.instantsearch.core.subscription.SubscriptionValue
- Direction
- stats uses core.subscription, so a change to core.subscription can break stats, while a change to stats can't break core.subscription.
- Position
- Below the diagonal: stats uses a module listed above it, which is the healthy direction.
23→10 stats uses core.searcher✕
- Connections
- 2 pairs of types, where a type in stats uses a type in core.searcher.
- The types involved
com.algolia.instantsearch.stats.StatsConnectionKt→com.algolia.instantsearch.core.searcher.Searchercom.algolia.instantsearch.stats.StatsConnector→com.algolia.instantsearch.core.searcher.Searcher
- Direction
- stats uses core.searcher, so a change to core.searcher can break stats, while a change to stats can't break core.searcher.
- Position
- Below the diagonal: stats uses a module listed above it, which is the healthy direction.
24→3 filter.state uses core.subscription✕
- Connections
- 1 pair of types, where a type in filter.state uses a type in core.subscription.
- The types involved
com.algolia.instantsearch.filter.state.FilterState→com.algolia.instantsearch.core.subscription.SubscriptionValue
- Direction
- filter.state uses core.subscription, so a change to core.subscription can break filter.state, while a change to filter.state can't break core.subscription.
- Position
- Below the diagonal: filter.state uses a module listed above it, which is the healthy direction.
24→4 filter.state uses filter✕
- Connections
- 8 pairs of types, where a type in filter.state uses a type in filter.
- The types involved
com.algolia.instantsearch.filter.state.DSLGroupFilter→com.algolia.instantsearch.filter.Filtercom.algolia.instantsearch.filter.state.DSLGroupFilter→com.algolia.instantsearch.filter.NumericOperatorcom.algolia.instantsearch.filter.state.DSLKt→com.algolia.instantsearch.filter.Filtercom.algolia.instantsearch.filter.state.ExtensionKt→com.algolia.instantsearch.filter.FilterGroupcom.algolia.instantsearch.filter.state.FilterGroupsDSL→com.algolia.instantsearch.filter.Filtercom.algolia.instantsearch.filter.state.FilterState→com.algolia.instantsearch.filter.Filtercom.algolia.instantsearch.filter.state.Filters→com.algolia.instantsearch.filter.Filtercom.algolia.instantsearch.filter.state.MutableFilters→com.algolia.instantsearch.filter.Filter
- Direction
- filter.state uses filter, so a change to filter can break filter.state, while a change to filter.state can't break filter.
- Position
- Below the diagonal: filter.state uses a module listed above it, which is the healthy direction.
24→15 filter.state uses filter.Filter✕
- Connections
- 5 pairs of types, where a type in filter.state uses a type in filter.Filter.
- The types involved
com.algolia.instantsearch.filter.state.ExtensionKt→com.algolia.instantsearch.filter.Filter.Facetcom.algolia.instantsearch.filter.state.ExtensionKt→com.algolia.instantsearch.filter.Filter.Numericcom.algolia.instantsearch.filter.state.Filters→com.algolia.instantsearch.filter.Filter.Facetcom.algolia.instantsearch.filter.state.Filters→com.algolia.instantsearch.filter.Filter.Numericcom.algolia.instantsearch.filter.state.Filters→com.algolia.instantsearch.filter.Filter.Tag
- Direction
- filter.state uses filter.Filter, so a change to filter.Filter can break filter.state, while a change to filter.state can't break filter.Filter.
- Position
- Below the diagonal: filter.state uses a module listed above it, which is the healthy direction.
24→20 filter.state uses hierarchical✕
- Connections
- 2 pairs of types, where a type in filter.state uses a type in hierarchical.
- The types involved
com.algolia.instantsearch.filter.state.Filters→com.algolia.instantsearch.hierarchical.HierarchicalFiltercom.algolia.instantsearch.filter.state.MutableFilters→com.algolia.instantsearch.hierarchical.HierarchicalFilter
- Direction
- filter.state uses hierarchical, so a change to hierarchical can break filter.state, while a change to filter.state can't break hierarchical.
- Position
- Below the diagonal: filter.state uses a module listed above it, which is the healthy direction.
25→15 insights.internal uses filter.Filter✕
- Connections
- 1 pair of types, where a type in insights.internal uses a type in filter.Filter.
- The types involved
com.algolia.instantsearch.insights.internal.InsightsController→com.algolia.instantsearch.filter.Filter.Facet
- Direction
- insights.internal uses filter.Filter, so a change to filter.Filter can break insights.internal, while a change to insights.internal can't break filter.Filter.
- Position
- Below the diagonal: insights.internal uses a module listed above it, which is the healthy direction.
25→16 insights.internal uses insights.internal.data.local.model.InsightsEventDO✕
- Connections
- 2 pairs of types, where a type in insights.internal uses a type in insights.internal.data.local.model.InsightsEventDO.
- The types involved
com.algolia.instantsearch.insights.internal.InsightsController→com.algolia.instantsearch.insights.internal.data.local.model.InsightsEventDO.EventSubtypecom.algolia.instantsearch.insights.internal.InsightsController→com.algolia.instantsearch.insights.internal.data.local.model.InsightsEventDO.EventType
- Direction
- insights.internal uses insights.internal.data.local.model.InsightsEventDO, so a change to insights.internal.data.local.model.InsightsEventDO can break insights.internal, while a change to insights.internal can't break insights.internal.data.local.model.InsightsEventDO.
- Position
- Below the diagonal: insights.internal uses a module listed above it, which is the healthy direction.
25→21 insights.internal uses insights.internal.data.local.model✕
- Connections
- 2 pairs of types, where a type in insights.internal uses a type in insights.internal.data.local.model.
- The types involved
com.algolia.instantsearch.insights.internal.InsightsController→com.algolia.instantsearch.insights.internal.data.local.model.InsightsEventDOcom.algolia.instantsearch.insights.internal.InsightsController→com.algolia.instantsearch.insights.internal.data.local.model.ObjectDataDO
- Direction
- insights.internal uses insights.internal.data.local.model, so a change to insights.internal.data.local.model can break insights.internal, while a change to insights.internal can't break insights.internal.data.local.model.
- Position
- Below the diagonal: insights.internal uses a module listed above it, which is the healthy direction.
26→2 filter.clear uses core.connection✕
- Connections
- 3 pairs of types, where a type in filter.clear uses a type in core.connection.
- The types involved
com.algolia.instantsearch.filter.clear.FilterClearConnectionKt→com.algolia.instantsearch.core.connection.Connectioncom.algolia.instantsearch.filter.clear.FilterClearConnector→com.algolia.instantsearch.core.connection.AbstractConnectioncom.algolia.instantsearch.filter.clear.FilterClearConnector→com.algolia.instantsearch.core.connection.Connection
- Direction
- filter.clear uses core.connection, so a change to core.connection can break filter.clear, while a change to filter.clear can't break core.connection.
- Position
- Below the diagonal: filter.clear uses a module listed above it, which is the healthy direction.
26→3 filter.clear uses core.subscription✕
- Connections
- 1 pair of types, where a type in filter.clear uses a type in core.subscription.
- The types involved
com.algolia.instantsearch.filter.clear.FilterClearViewModel→com.algolia.instantsearch.core.subscription.SubscriptionEvent
- Direction
- filter.clear uses core.subscription, so a change to core.subscription can break filter.clear, while a change to filter.clear can't break core.subscription.
- Position
- Below the diagonal: filter.clear uses a module listed above it, which is the healthy direction.
26→24 filter.clear uses filter.state✕
- Connections
- 4 pairs of types, where a type in filter.clear uses a type in filter.state.
- The types involved
com.algolia.instantsearch.filter.clear.FilterClearConnectionKt→com.algolia.instantsearch.filter.state.FilterGroupIDcom.algolia.instantsearch.filter.clear.FilterClearConnectionKt→com.algolia.instantsearch.filter.state.FilterStatecom.algolia.instantsearch.filter.clear.FilterClearConnector→com.algolia.instantsearch.filter.state.FilterGroupIDcom.algolia.instantsearch.filter.clear.FilterClearConnector→com.algolia.instantsearch.filter.state.FilterState
- Direction
- filter.clear uses filter.state, so a change to filter.state can break filter.clear, while a change to filter.clear can't break filter.state.
- Position
- Below the diagonal: filter.clear uses a module listed above it, which is the healthy direction.
27→2 filter.current uses core.connection✕
- Connections
- 3 pairs of types, where a type in filter.current uses a type in core.connection.
- The types involved
com.algolia.instantsearch.filter.current.FilterCurrentConnectionKt→com.algolia.instantsearch.core.connection.Connectioncom.algolia.instantsearch.filter.current.FilterCurrentConnector→com.algolia.instantsearch.core.connection.AbstractConnectioncom.algolia.instantsearch.filter.current.FilterCurrentConnector→com.algolia.instantsearch.core.connection.Connection
- Direction
- filter.current uses core.connection, so a change to core.connection can break filter.current, while a change to filter.current can't break core.connection.
- Position
- Below the diagonal: filter.current uses a module listed above it, which is the healthy direction.
27→4 filter.current uses filter✕
- Connections
- 5 pairs of types, where a type in filter.current uses a type in filter.
- The types involved
com.algolia.instantsearch.filter.current.DefaultFilterCurrentPresenter→com.algolia.instantsearch.filter.Filtercom.algolia.instantsearch.filter.current.DefaultFilterCurrentPresenter→com.algolia.instantsearch.filter.FilterPresentercom.algolia.instantsearch.filter.current.FilterAndIDKt→com.algolia.instantsearch.filter.Filtercom.algolia.instantsearch.filter.current.FilterCurrentConnector→com.algolia.instantsearch.filter.Filtercom.algolia.instantsearch.filter.current.FilterCurrentView→com.algolia.instantsearch.filter.Filter
- Direction
- filter.current uses filter, so a change to filter can break filter.current, while a change to filter.current can't break filter.
- Position
- Below the diagonal: filter.current uses a module listed above it, which is the healthy direction.
27→24 filter.current uses filter.state✕
- Connections
- 7 pairs of types, where a type in filter.current uses a type in filter.state.
- The types involved
com.algolia.instantsearch.filter.current.DefaultFilterCurrentPresenter→com.algolia.instantsearch.filter.state.FilterGroupIDcom.algolia.instantsearch.filter.current.FilterAndIDKt→com.algolia.instantsearch.filter.state.FilterGroupIDcom.algolia.instantsearch.filter.current.FilterCurrentConnectionKt→com.algolia.instantsearch.filter.state.FilterGroupIDcom.algolia.instantsearch.filter.current.FilterCurrentConnectionKt→com.algolia.instantsearch.filter.state.FilterStatecom.algolia.instantsearch.filter.current.FilterCurrentConnector→com.algolia.instantsearch.filter.state.FilterGroupIDcom.algolia.instantsearch.filter.current.FilterCurrentConnector→com.algolia.instantsearch.filter.state.FilterStatecom.algolia.instantsearch.filter.current.FilterCurrentView→com.algolia.instantsearch.filter.state.FilterGroupID
- Direction
- filter.current uses filter.state, so a change to filter.state can break filter.current, while a change to filter.current can't break filter.state.
- Position
- Below the diagonal: filter.current uses a module listed above it, which is the healthy direction.
28→2 filter.list uses core.connection✕
- Connections
- 3 pairs of types, where a type in filter.list uses a type in core.connection.
- The types involved
com.algolia.instantsearch.filter.list.FilterListConnectionKt→com.algolia.instantsearch.core.connection.Connectioncom.algolia.instantsearch.filter.list.FilterListConnector→com.algolia.instantsearch.core.connection.AbstractConnectioncom.algolia.instantsearch.filter.list.FilterListConnector→com.algolia.instantsearch.core.connection.Connection
- Direction
- filter.list uses core.connection, so a change to core.connection can break filter.list, while a change to filter.list can't break core.connection.
- Position
- Below the diagonal: filter.list uses a module listed above it, which is the healthy direction.
28→12 filter.list uses core.selectable.list✕
- Connections
- 3 pairs of types, where a type in filter.list uses a type in core.selectable.list.
- The types involved
com.algolia.instantsearch.filter.list.FilterListView→com.algolia.instantsearch.core.selectable.list.SelectableListViewcom.algolia.instantsearch.filter.list.FilterListViewModel→com.algolia.instantsearch.core.selectable.list.SelectableListViewModelcom.algolia.instantsearch.filter.list.FilterListViewModel→com.algolia.instantsearch.core.selectable.list.SelectionMode
- Direction
- filter.list uses core.selectable.list, so a change to core.selectable.list can break filter.list, while a change to filter.list can't break core.selectable.list.
- Position
- Below the diagonal: filter.list uses a module listed above it, which is the healthy direction.
28→24 filter.list uses filter.state✕
- Connections
- 5 pairs of types, where a type in filter.list uses a type in filter.state.
- The types involved
com.algolia.instantsearch.filter.list.FilterListConnectionKt→com.algolia.instantsearch.filter.state.FilterGroupIDcom.algolia.instantsearch.filter.list.FilterListConnectionKt→com.algolia.instantsearch.filter.state.FilterStatecom.algolia.instantsearch.filter.list.FilterListConnectionKt→com.algolia.instantsearch.filter.state.Filterscom.algolia.instantsearch.filter.list.FilterListConnector→com.algolia.instantsearch.filter.state.FilterGroupIDcom.algolia.instantsearch.filter.list.FilterListConnector→com.algolia.instantsearch.filter.state.FilterState
- Direction
- filter.list uses filter.state, so a change to filter.state can break filter.list, while a change to filter.list can't break filter.state.
- Position
- Below the diagonal: filter.list uses a module listed above it, which is the healthy direction.
29→2 relateditems.internal uses core.connection✕
- Connections
- 1 pair of types, where a type in relateditems.internal uses a type in core.connection.
- The types involved
com.algolia.instantsearch.relateditems.internal.RelatedItemsConnectionView→com.algolia.instantsearch.core.connection.AbstractConnection
- Direction
- relateditems.internal uses core.connection, so a change to core.connection can break relateditems.internal, while a change to relateditems.internal can't break core.connection.
- Position
- Below the diagonal: relateditems.internal uses a module listed above it, which is the healthy direction.
29→6 relateditems.internal uses core.hits✕
- Connections
- 1 pair of types, where a type in relateditems.internal uses a type in core.hits.
- The types involved
com.algolia.instantsearch.relateditems.internal.RelatedItemsConnectionView→com.algolia.instantsearch.core.hits.HitsView
- Direction
- relateditems.internal uses core.hits, so a change to core.hits can break relateditems.internal, while a change to relateditems.internal can't break core.hits.
- Position
- Below the diagonal: relateditems.internal uses a module listed above it, which is the healthy direction.
29→15 relateditems.internal uses filter.Filter✕
- Connections
- 1 pair of types, where a type in relateditems.internal uses a type in filter.Filter.
- The types involved
com.algolia.instantsearch.relateditems.internal.FilterFacetAndID→com.algolia.instantsearch.filter.Filter.Facet
- Direction
- relateditems.internal uses filter.Filter, so a change to filter.Filter can break relateditems.internal, while a change to relateditems.internal can't break filter.Filter.
- Position
- Below the diagonal: relateditems.internal uses a module listed above it, which is the healthy direction.
29→24 relateditems.internal uses filter.state✕
- Connections
- 1 pair of types, where a type in relateditems.internal uses a type in filter.state.
- The types involved
com.algolia.instantsearch.relateditems.internal.FilterFacetAndID→com.algolia.instantsearch.filter.state.FilterGroupID
- Direction
- relateditems.internal uses filter.state, so a change to filter.state can break relateditems.internal, while a change to relateditems.internal can't break filter.state.
- Position
- Below the diagonal: relateditems.internal uses a module listed above it, which is the healthy direction.
30→2 searcher uses core.connection✕
- Connections
- 1 pair of types, where a type in searcher uses a type in core.connection.
- The types involved
com.algolia.instantsearch.searcher.SearcherConnectionKt→com.algolia.instantsearch.core.connection.Connection
- Direction
- searcher uses core.connection, so a change to core.connection can break searcher, while a change to searcher can't break core.connection.
- Position
- Below the diagonal: searcher uses a module listed above it, which is the healthy direction.
30→4 searcher uses filter✕
- Connections
- 1 pair of types, where a type in searcher uses a type in filter.
- The types involved
com.algolia.instantsearch.searcher.FilterGroupsHolder→com.algolia.instantsearch.filter.FilterGroup
- Direction
- searcher uses filter, so a change to filter can break searcher, while a change to searcher can't break filter.
- Position
- Below the diagonal: searcher uses a module listed above it, which is the healthy direction.
30→10 searcher uses core.searcher✕
- Connections
- 2 pairs of types, where a type in searcher uses a type in core.searcher.
- The types involved
com.algolia.instantsearch.searcher.SearcherConnectionKt→com.algolia.instantsearch.core.searcher.Debouncercom.algolia.instantsearch.searcher.SearcherQuery→com.algolia.instantsearch.core.searcher.Searcher
- Direction
- searcher uses core.searcher, so a change to core.searcher can break searcher, while a change to searcher can't break core.searcher.
- Position
- Below the diagonal: searcher uses a module listed above it, which is the healthy direction.
30→24 searcher uses filter.state✕
- Connections
- 1 pair of types, where a type in searcher uses a type in filter.state.
- The types involved
com.algolia.instantsearch.searcher.SearcherConnectionKt→com.algolia.instantsearch.filter.state.FilterState
- Direction
- searcher uses filter.state, so a change to filter.state can break searcher, while a change to searcher can't break filter.state.
- Position
- Below the diagonal: searcher uses a module listed above it, which is the healthy direction.
31→30 android.paging3 uses searcher✕
- Connections
- 1 pair of types, where a type in android.paging3 uses a type in searcher.
- The types involved
com.algolia.instantsearch.android.paging3.PaginatorKt→com.algolia.instantsearch.searcher.SearcherForHits
- Direction
- android.paging3 uses searcher, so a change to searcher can break android.paging3, while a change to android.paging3 can't break searcher.
- Position
- Below the diagonal: android.paging3 uses a module listed above it, which is the healthy direction.
32→2 filter.current.internal uses core.connection✕
- Connections
- 2 pairs of types, where a type in filter.current.internal uses a type in core.connection.
- The types involved
com.algolia.instantsearch.filter.current.internal.FilterCurrentConnectionFilterState→com.algolia.instantsearch.core.connection.AbstractConnectioncom.algolia.instantsearch.filter.current.internal.FilterCurrentConnectionView→com.algolia.instantsearch.core.connection.AbstractConnection
- Direction
- filter.current.internal uses core.connection, so a change to core.connection can break filter.current.internal, while a change to filter.current.internal can't break core.connection.
- Position
- Below the diagonal: filter.current.internal uses a module listed above it, which is the healthy direction.
32→4 filter.current.internal uses filter✕
- Connections
- 3 pairs of types, where a type in filter.current.internal uses a type in filter.
- The types involved
com.algolia.instantsearch.filter.current.internal.FilterAndIDKt→com.algolia.instantsearch.filter.Filtercom.algolia.instantsearch.filter.current.internal.FilterCurrentConnectionFilterState→com.algolia.instantsearch.filter.Filtercom.algolia.instantsearch.filter.current.internal.FilterCurrentConnectionView→com.algolia.instantsearch.filter.Filter
- Direction
- filter.current.internal uses filter, so a change to filter can break filter.current.internal, while a change to filter.current.internal can't break filter.
- Position
- Below the diagonal: filter.current.internal uses a module listed above it, which is the healthy direction.
32→24 filter.current.internal uses filter.state✕
- Connections
- 5 pairs of types, where a type in filter.current.internal uses a type in filter.state.
- The types involved
com.algolia.instantsearch.filter.current.internal.FilterAndIDKt→com.algolia.instantsearch.filter.state.FilterGroupIDcom.algolia.instantsearch.filter.current.internal.FilterCurrentConnectionFilterState→com.algolia.instantsearch.filter.state.FilterGroupIDcom.algolia.instantsearch.filter.current.internal.FilterCurrentConnectionFilterState→com.algolia.instantsearch.filter.state.FilterStatecom.algolia.instantsearch.filter.current.internal.FilterCurrentConnectionFilterState→com.algolia.instantsearch.filter.state.Filterscom.algolia.instantsearch.filter.current.internal.FilterCurrentConnectionView→com.algolia.instantsearch.filter.state.FilterGroupID
- Direction
- filter.current.internal uses filter.state, so a change to filter.state can break filter.current.internal, while a change to filter.current.internal can't break filter.state.
- Position
- Below the diagonal: filter.current.internal uses a module listed above it, which is the healthy direction.
32→27 filter.current.internal uses filter.current✕
- Connections
- 2 pairs of types, where a type in filter.current.internal uses a type in filter.current.
- The types involved
com.algolia.instantsearch.filter.current.internal.FilterCurrentConnectionView→com.algolia.instantsearch.filter.current.FilterCurrentPresentercom.algolia.instantsearch.filter.current.internal.FilterCurrentConnectionView→com.algolia.instantsearch.filter.current.FilterCurrentView
- Direction
- filter.current.internal uses filter.current, so a change to filter.current can break filter.current.internal, while a change to filter.current.internal can't break filter.current.
- Position
- Below the diagonal: filter.current.internal uses a module listed above it, which is the healthy direction.
33→2 filter.facet uses core.connection✕
- Connections
- 3 pairs of types, where a type in filter.facet uses a type in core.connection.
- The types involved
com.algolia.instantsearch.filter.facet.FacetListConnectionKt→com.algolia.instantsearch.core.connection.Connectioncom.algolia.instantsearch.filter.facet.FacetListConnector→com.algolia.instantsearch.core.connection.AbstractConnectioncom.algolia.instantsearch.filter.facet.FacetListConnector→com.algolia.instantsearch.core.connection.Connection
- Direction
- filter.facet uses core.connection, so a change to core.connection can break filter.facet, while a change to filter.facet can't break core.connection.
- Position
- Below the diagonal: filter.facet uses a module listed above it, which is the healthy direction.
33→3 filter.facet uses core.subscription✕
- Connections
- 1 pair of types, where a type in filter.facet uses a type in core.subscription.
- The types involved
com.algolia.instantsearch.filter.facet.FacetListViewModel→com.algolia.instantsearch.core.subscription.SubscriptionValue
- Direction
- filter.facet uses core.subscription, so a change to core.subscription can break filter.facet, while a change to filter.facet can't break core.subscription.
- Position
- Below the diagonal: filter.facet uses a module listed above it, which is the healthy direction.
33→12 filter.facet uses core.selectable.list✕
- Connections
- 4 pairs of types, where a type in filter.facet uses a type in core.selectable.list.
- The types involved
com.algolia.instantsearch.filter.facet.FacetListConnectionKt→com.algolia.instantsearch.core.selectable.list.SelectableListViewcom.algolia.instantsearch.filter.facet.FacetListConnector→com.algolia.instantsearch.core.selectable.list.SelectionModecom.algolia.instantsearch.filter.facet.FacetListViewModel→com.algolia.instantsearch.core.selectable.list.SelectableListViewModelcom.algolia.instantsearch.filter.facet.FacetListViewModel→com.algolia.instantsearch.core.selectable.list.SelectionMode
- Direction
- filter.facet uses core.selectable.list, so a change to core.selectable.list can break filter.facet, while a change to filter.facet can't break core.selectable.list.
- Position
- Below the diagonal: filter.facet uses a module listed above it, which is the healthy direction.
33→24 filter.facet uses filter.state✕
- Connections
- 5 pairs of types, where a type in filter.facet uses a type in filter.state.
- The types involved
com.algolia.instantsearch.filter.facet.FacetListConnectionKt→com.algolia.instantsearch.filter.state.FilterGroupIDcom.algolia.instantsearch.filter.facet.FacetListConnectionKt→com.algolia.instantsearch.filter.state.FilterOperatorcom.algolia.instantsearch.filter.facet.FacetListConnectionKt→com.algolia.instantsearch.filter.state.FilterStatecom.algolia.instantsearch.filter.facet.FacetListConnector→com.algolia.instantsearch.filter.state.FilterGroupIDcom.algolia.instantsearch.filter.facet.FacetListConnector→com.algolia.instantsearch.filter.state.FilterState
- Direction
- filter.facet uses filter.state, so a change to filter.state can break filter.facet, while a change to filter.facet can't break filter.state.
- Position
- Below the diagonal: filter.facet uses a module listed above it, which is the healthy direction.
33→30 filter.facet uses searcher✕
- Connections
- 4 pairs of types, where a type in filter.facet uses a type in searcher.
- The types involved
com.algolia.instantsearch.filter.facet.FacetListConnectionKt→com.algolia.instantsearch.searcher.SearcherForFacetscom.algolia.instantsearch.filter.facet.FacetListConnectionKt→com.algolia.instantsearch.searcher.SearcherForHitscom.algolia.instantsearch.filter.facet.FacetListConnector→com.algolia.instantsearch.searcher.SearcherForFacetscom.algolia.instantsearch.filter.facet.FacetListConnector→com.algolia.instantsearch.searcher.SearcherForHits
- Direction
- filter.facet uses searcher, so a change to searcher can break filter.facet, while a change to filter.facet can't break searcher.
- Position
- Below the diagonal: filter.facet uses a module listed above it, which is the healthy direction.
34→2 filter.facet.dynamic uses core.connection✕
- Connections
- 3 pairs of types, where a type in filter.facet.dynamic uses a type in core.connection.
- The types involved
com.algolia.instantsearch.filter.facet.dynamic.DynamicFacetConnectionKt→com.algolia.instantsearch.core.connection.Connectioncom.algolia.instantsearch.filter.facet.dynamic.DynamicFacetListConnector→com.algolia.instantsearch.core.connection.AbstractConnectioncom.algolia.instantsearch.filter.facet.dynamic.DynamicFacetListConnector→com.algolia.instantsearch.core.connection.Connection
- Direction
- filter.facet.dynamic uses core.connection, so a change to core.connection can break filter.facet.dynamic, while a change to filter.facet.dynamic can't break core.connection.
- Position
- Below the diagonal: filter.facet.dynamic uses a module listed above it, which is the healthy direction.
34→3 filter.facet.dynamic uses core.subscription✕
- Connections
- 2 pairs of types, where a type in filter.facet.dynamic uses a type in core.subscription.
- The types involved
com.algolia.instantsearch.filter.facet.dynamic.DynamicFacetListViewModel→com.algolia.instantsearch.core.subscription.SubscriptionEventcom.algolia.instantsearch.filter.facet.dynamic.DynamicFacetListViewModel→com.algolia.instantsearch.core.subscription.SubscriptionValue
- Direction
- filter.facet.dynamic uses core.subscription, so a change to core.subscription can break filter.facet.dynamic, while a change to filter.facet.dynamic can't break core.subscription.
- Position
- Below the diagonal: filter.facet.dynamic uses a module listed above it, which is the healthy direction.
34→12 filter.facet.dynamic uses core.selectable.list✕
- Connections
- 3 pairs of types, where a type in filter.facet.dynamic uses a type in core.selectable.list.
- The types involved
com.algolia.instantsearch.filter.facet.dynamic.DynamicFacetListConnector→com.algolia.instantsearch.core.selectable.list.SelectionModecom.algolia.instantsearch.filter.facet.dynamic.DynamicFacetListViewModel→com.algolia.instantsearch.core.selectable.list.SelectableListViewModelcom.algolia.instantsearch.filter.facet.dynamic.DynamicFacetListViewModel→com.algolia.instantsearch.core.selectable.list.SelectionMode
- Direction
- filter.facet.dynamic uses core.selectable.list, so a change to core.selectable.list can break filter.facet.dynamic, while a change to filter.facet.dynamic can't break core.selectable.list.
- Position
- Below the diagonal: filter.facet.dynamic uses a module listed above it, which is the healthy direction.
34→24 filter.facet.dynamic uses filter.state✕
- Connections
- 4 pairs of types, where a type in filter.facet.dynamic uses a type in filter.state.
- The types involved
com.algolia.instantsearch.filter.facet.dynamic.DynamicFacetConnectionKt→com.algolia.instantsearch.filter.state.FilterOperatorcom.algolia.instantsearch.filter.facet.dynamic.DynamicFacetConnectionKt→com.algolia.instantsearch.filter.state.FilterStatecom.algolia.instantsearch.filter.facet.dynamic.DynamicFacetListConnector→com.algolia.instantsearch.filter.state.FilterOperatorcom.algolia.instantsearch.filter.facet.dynamic.DynamicFacetListConnector→com.algolia.instantsearch.filter.state.FilterState
- Direction
- filter.facet.dynamic uses filter.state, so a change to filter.state can break filter.facet.dynamic, while a change to filter.facet.dynamic can't break filter.state.
- Position
- Below the diagonal: filter.facet.dynamic uses a module listed above it, which is the healthy direction.
34→30 filter.facet.dynamic uses searcher✕
- Connections
- 2 pairs of types, where a type in filter.facet.dynamic uses a type in searcher.
- The types involved
com.algolia.instantsearch.filter.facet.dynamic.DynamicFacetConnectionKt→com.algolia.instantsearch.searcher.SearcherForHitscom.algolia.instantsearch.filter.facet.dynamic.DynamicFacetListConnector→com.algolia.instantsearch.searcher.SearcherForHits
- Direction
- filter.facet.dynamic uses searcher, so a change to searcher can break filter.facet.dynamic, while a change to filter.facet.dynamic can't break searcher.
- Position
- Below the diagonal: filter.facet.dynamic uses a module listed above it, which is the healthy direction.
35→2 filter.list.FilterListConnector uses core.connection✕
- Connections
- 4 pairs of types, where a type in filter.list.FilterListConnector uses a type in core.connection.
- The types involved
com.algolia.instantsearch.filter.list.FilterListConnector.All→com.algolia.instantsearch.core.connection.Connectioncom.algolia.instantsearch.filter.list.FilterListConnector.Facet→com.algolia.instantsearch.core.connection.Connectioncom.algolia.instantsearch.filter.list.FilterListConnector.Numeric→com.algolia.instantsearch.core.connection.Connectioncom.algolia.instantsearch.filter.list.FilterListConnector.Tag→com.algolia.instantsearch.core.connection.Connection
- Direction
- filter.list.FilterListConnector uses core.connection, so a change to core.connection can break filter.list.FilterListConnector, while a change to filter.list.FilterListConnector can't break core.connection.
- Position
- Below the diagonal: filter.list.FilterListConnector uses a module listed above it, which is the healthy direction.
35→4 filter.list.FilterListConnector uses filter✕
- Connections
- 1 pair of types, where a type in filter.list.FilterListConnector uses a type in filter.
- The types involved
com.algolia.instantsearch.filter.list.FilterListConnector.All→com.algolia.instantsearch.filter.Filter
- Direction
- filter.list.FilterListConnector uses filter, so a change to filter can break filter.list.FilterListConnector, while a change to filter.list.FilterListConnector can't break filter.
- Position
- Below the diagonal: filter.list.FilterListConnector uses a module listed above it, which is the healthy direction.
35→12 filter.list.FilterListConnector uses core.selectable.list✕
- Connections
- 4 pairs of types, where a type in filter.list.FilterListConnector uses a type in core.selectable.list.
- The types involved
com.algolia.instantsearch.filter.list.FilterListConnector.All→com.algolia.instantsearch.core.selectable.list.SelectionModecom.algolia.instantsearch.filter.list.FilterListConnector.Facet→com.algolia.instantsearch.core.selectable.list.SelectionModecom.algolia.instantsearch.filter.list.FilterListConnector.Numeric→com.algolia.instantsearch.core.selectable.list.SelectionModecom.algolia.instantsearch.filter.list.FilterListConnector.Tag→com.algolia.instantsearch.core.selectable.list.SelectionMode
- Direction
- filter.list.FilterListConnector uses core.selectable.list, so a change to core.selectable.list can break filter.list.FilterListConnector, while a change to filter.list.FilterListConnector can't break core.selectable.list.
- Position
- Below the diagonal: filter.list.FilterListConnector uses a module listed above it, which is the healthy direction.
35→15 filter.list.FilterListConnector uses filter.Filter✕
- Connections
- 3 pairs of types, where a type in filter.list.FilterListConnector uses a type in filter.Filter.
- The types involved
com.algolia.instantsearch.filter.list.FilterListConnector.Facet→com.algolia.instantsearch.filter.Filter.Facetcom.algolia.instantsearch.filter.list.FilterListConnector.Numeric→com.algolia.instantsearch.filter.Filter.Numericcom.algolia.instantsearch.filter.list.FilterListConnector.Tag→com.algolia.instantsearch.filter.Filter.Tag
- Direction
- filter.list.FilterListConnector uses filter.Filter, so a change to filter.Filter can break filter.list.FilterListConnector, while a change to filter.list.FilterListConnector can't break filter.Filter.
- Position
- Below the diagonal: filter.list.FilterListConnector uses a module listed above it, which is the healthy direction.
35→24 filter.list.FilterListConnector uses filter.state✕
- Connections
- 8 pairs of types, where a type in filter.list.FilterListConnector uses a type in filter.state.
- The types involved
com.algolia.instantsearch.filter.list.FilterListConnector.All→com.algolia.instantsearch.filter.state.FilterGroupIDcom.algolia.instantsearch.filter.list.FilterListConnector.All→com.algolia.instantsearch.filter.state.FilterStatecom.algolia.instantsearch.filter.list.FilterListConnector.Facet→com.algolia.instantsearch.filter.state.FilterGroupIDcom.algolia.instantsearch.filter.list.FilterListConnector.Facet→com.algolia.instantsearch.filter.state.FilterStatecom.algolia.instantsearch.filter.list.FilterListConnector.Numeric→com.algolia.instantsearch.filter.state.FilterGroupIDcom.algolia.instantsearch.filter.list.FilterListConnector.Numeric→com.algolia.instantsearch.filter.state.FilterStatecom.algolia.instantsearch.filter.list.FilterListConnector.Tag→com.algolia.instantsearch.filter.state.FilterGroupIDcom.algolia.instantsearch.filter.list.FilterListConnector.Tag→com.algolia.instantsearch.filter.state.FilterState
- Direction
- filter.list.FilterListConnector uses filter.state, so a change to filter.state can break filter.list.FilterListConnector, while a change to filter.list.FilterListConnector can't break filter.state.
- Position
- Below the diagonal: filter.list.FilterListConnector uses a module listed above it, which is the healthy direction.
35→28 filter.list.FilterListConnector uses filter.list✕
- Connections
- 4 pairs of types, where a type in filter.list.FilterListConnector uses a type in filter.list.
- The types involved
com.algolia.instantsearch.filter.list.FilterListConnector.All→com.algolia.instantsearch.filter.list.FilterListConnectorcom.algolia.instantsearch.filter.list.FilterListConnector.Facet→com.algolia.instantsearch.filter.list.FilterListConnectorcom.algolia.instantsearch.filter.list.FilterListConnector.Numeric→com.algolia.instantsearch.filter.list.FilterListConnectorcom.algolia.instantsearch.filter.list.FilterListConnector.Tag→com.algolia.instantsearch.filter.list.FilterListConnector
- Direction
- filter.list.FilterListConnector uses filter.list, so a change to filter.list can break filter.list.FilterListConnector, while a change to filter.list.FilterListConnector can't break filter.list.
- Position
- Below the diagonal: filter.list.FilterListConnector uses a module listed above it, which is the healthy direction.
36→2 searcher.internal uses core.connection✕
- Connections
- 2 pairs of types, where a type in searcher.internal uses a type in core.connection.
- The types involved
com.algolia.instantsearch.searcher.internal.FacetsSearcherConnectionFilterState→com.algolia.instantsearch.core.connection.AbstractConnectioncom.algolia.instantsearch.searcher.internal.HitsSearcherConnectionFilterState→com.algolia.instantsearch.core.connection.AbstractConnection
- Direction
- searcher.internal uses core.connection, so a change to core.connection can break searcher.internal, while a change to searcher.internal can't break core.connection.
- Position
- Below the diagonal: searcher.internal uses a module listed above it, which is the healthy direction.
36→5 searcher.internal uses searcher.multi.internal.types✕
- Connections
- 3 pairs of types, where a type in searcher.internal uses a type in searcher.multi.internal.types.
- The types involved
com.algolia.instantsearch.searcher.internal.SearchClientExtensionsKt→com.algolia.instantsearch.searcher.multi.internal.types.IndexedQuerycom.algolia.instantsearch.searcher.internal.SearchClientExtensionsKt→com.algolia.instantsearch.searcher.multi.internal.types.MultipleQueriesStrategycom.algolia.instantsearch.searcher.internal.SearchClientExtensionsKt→com.algolia.instantsearch.searcher.multi.internal.types.ResponseMultiSearch
- Direction
- searcher.internal uses searcher.multi.internal.types, so a change to searcher.multi.internal.types can break searcher.internal, while a change to searcher.internal can't break searcher.multi.internal.types.
- Position
- Below the diagonal: searcher.internal uses a module listed above it, which is the healthy direction.
36→10 searcher.internal uses core.searcher✕
- Connections
- 3 pairs of types, where a type in searcher.internal uses a type in core.searcher.
- The types involved
com.algolia.instantsearch.searcher.internal.FacetsSearcherConnectionFilterState→com.algolia.instantsearch.core.searcher.Debouncercom.algolia.instantsearch.searcher.internal.HitsSearcherConnectionFilterState→com.algolia.instantsearch.core.searcher.Debouncercom.algolia.instantsearch.searcher.internal.SearcherExceptionHandler→com.algolia.instantsearch.core.searcher.Searcher
- Direction
- searcher.internal uses core.searcher, so a change to core.searcher can break searcher.internal, while a change to searcher.internal can't break core.searcher.
- Position
- Below the diagonal: searcher.internal uses a module listed above it, which is the healthy direction.
36→24 searcher.internal uses filter.state✕
- Connections
- 4 pairs of types, where a type in searcher.internal uses a type in filter.state.
- The types involved
com.algolia.instantsearch.searcher.internal.FacetsSearcherConnectionFilterState→com.algolia.instantsearch.filter.state.FilterStatecom.algolia.instantsearch.searcher.internal.FacetsSearcherConnectionFilterState→com.algolia.instantsearch.filter.state.Filterscom.algolia.instantsearch.searcher.internal.HitsSearcherConnectionFilterState→com.algolia.instantsearch.filter.state.FilterStatecom.algolia.instantsearch.searcher.internal.HitsSearcherConnectionFilterState→com.algolia.instantsearch.filter.state.Filters
- Direction
- searcher.internal uses filter.state, so a change to filter.state can break searcher.internal, while a change to searcher.internal can't break filter.state.
- Position
- Below the diagonal: searcher.internal uses a module listed above it, which is the healthy direction.
36→30 searcher.internal uses searcher✕
- Connections
- 1 pair of types, where a type in searcher.internal uses a type in searcher.
- The types involved
com.algolia.instantsearch.searcher.internal.FacetsSearcherConnectionFilterState→com.algolia.instantsearch.searcher.SearcherForFacets
- Direction
- searcher.internal uses searcher, so a change to searcher can break searcher.internal, while a change to searcher.internal can't break searcher.
- Position
- Below the diagonal: searcher.internal uses a module listed above it, which is the healthy direction.
37→2 filter.facet.internal uses core.connection✕
- Connections
- 4 pairs of types, where a type in filter.facet.internal uses a type in core.connection.
- The types involved
com.algolia.instantsearch.filter.facet.internal.FacetListConnectionFilterState→com.algolia.instantsearch.core.connection.AbstractConnectioncom.algolia.instantsearch.filter.facet.internal.FacetListConnectionSearcher→com.algolia.instantsearch.core.connection.AbstractConnectioncom.algolia.instantsearch.filter.facet.internal.FacetListConnectionSearcherForFacets→com.algolia.instantsearch.core.connection.AbstractConnectioncom.algolia.instantsearch.filter.facet.internal.FacetListConnectionView→com.algolia.instantsearch.core.connection.AbstractConnection
- Direction
- filter.facet.internal uses core.connection, so a change to core.connection can break filter.facet.internal, while a change to filter.facet.internal can't break core.connection.
- Position
- Below the diagonal: filter.facet.internal uses a module listed above it, which is the healthy direction.
37→12 filter.facet.internal uses core.selectable.list✕
- Connections
- 1 pair of types, where a type in filter.facet.internal uses a type in core.selectable.list.
- The types involved
com.algolia.instantsearch.filter.facet.internal.FacetListConnectionView→com.algolia.instantsearch.core.selectable.list.SelectableListView
- Direction
- filter.facet.internal uses core.selectable.list, so a change to core.selectable.list can break filter.facet.internal, while a change to filter.facet.internal can't break core.selectable.list.
- Position
- Below the diagonal: filter.facet.internal uses a module listed above it, which is the healthy direction.
37→15 filter.facet.internal uses filter.Filter✕
- Connections
- 1 pair of types, where a type in filter.facet.internal uses a type in filter.Filter.
- The types involved
com.algolia.instantsearch.filter.facet.internal.FacetListConnectionFilterState→com.algolia.instantsearch.filter.Filter.Facet
- Direction
- filter.facet.internal uses filter.Filter, so a change to filter.Filter can break filter.facet.internal, while a change to filter.facet.internal can't break filter.Filter.
- Position
- Below the diagonal: filter.facet.internal uses a module listed above it, which is the healthy direction.
37→24 filter.facet.internal uses filter.state✕
- Connections
- 3 pairs of types, where a type in filter.facet.internal uses a type in filter.state.
- The types involved
com.algolia.instantsearch.filter.facet.internal.FacetListConnectionFilterState→com.algolia.instantsearch.filter.state.FilterGroupIDcom.algolia.instantsearch.filter.facet.internal.FacetListConnectionFilterState→com.algolia.instantsearch.filter.state.FilterStatecom.algolia.instantsearch.filter.facet.internal.FacetListConnectionFilterState→com.algolia.instantsearch.filter.state.Filters
- Direction
- filter.facet.internal uses filter.state, so a change to filter.state can break filter.facet.internal, while a change to filter.facet.internal can't break filter.state.
- Position
- Below the diagonal: filter.facet.internal uses a module listed above it, which is the healthy direction.
37→30 filter.facet.internal uses searcher✕
- Connections
- 2 pairs of types, where a type in filter.facet.internal uses a type in searcher.
- The types involved
com.algolia.instantsearch.filter.facet.internal.FacetListConnectionSearcher→com.algolia.instantsearch.searcher.SearcherQuerycom.algolia.instantsearch.filter.facet.internal.FacetListConnectionSearcherForFacets→com.algolia.instantsearch.searcher.SearcherForFacets
- Direction
- filter.facet.internal uses searcher, so a change to searcher can break filter.facet.internal, while a change to filter.facet.internal can't break searcher.
- Position
- Below the diagonal: filter.facet.internal uses a module listed above it, which is the healthy direction.
37→33 filter.facet.internal uses filter.facet✕
- Connections
- 4 pairs of types, where a type in filter.facet.internal uses a type in filter.facet.
- The types involved
com.algolia.instantsearch.filter.facet.internal.FacetListConnectionFilterState→com.algolia.instantsearch.filter.facet.FacetListViewModelcom.algolia.instantsearch.filter.facet.internal.FacetListConnectionSearcher→com.algolia.instantsearch.filter.facet.FacetListViewModelcom.algolia.instantsearch.filter.facet.internal.FacetListConnectionSearcherForFacets→com.algolia.instantsearch.filter.facet.FacetListViewModelcom.algolia.instantsearch.filter.facet.internal.FacetListConnectionView→com.algolia.instantsearch.filter.facet.FacetListViewModel
- Direction
- filter.facet.internal uses filter.facet, so a change to filter.facet can break filter.facet.internal, while a change to filter.facet.internal can't break filter.facet.
- Position
- Below the diagonal: filter.facet.internal uses a module listed above it, which is the healthy direction.
38→3 searcher.multi.internal uses core.subscription✕
- Connections
- 1 pair of types, where a type in searcher.multi.internal uses a type in core.subscription.
- The types involved
com.algolia.instantsearch.searcher.multi.internal.DefaultMultiSearcher→com.algolia.instantsearch.core.subscription.SubscriptionValue
- Direction
- searcher.multi.internal uses core.subscription, so a change to core.subscription can break searcher.multi.internal, while a change to searcher.multi.internal can't break core.subscription.
- Position
- Below the diagonal: searcher.multi.internal uses a module listed above it, which is the healthy direction.
38→5 searcher.multi.internal uses searcher.multi.internal.types✕
- Connections
- 5 pairs of types, where a type in searcher.multi.internal uses a type in searcher.multi.internal.types.
- The types involved
com.algolia.instantsearch.searcher.multi.internal.DefaultMultiSearchService→com.algolia.instantsearch.searcher.multi.internal.types.ResponseMultiSearchcom.algolia.instantsearch.searcher.multi.internal.DefaultMultiSearcher→com.algolia.instantsearch.searcher.multi.internal.types.IndexedQuerycom.algolia.instantsearch.searcher.multi.internal.DefaultMultiSearcher→com.algolia.instantsearch.searcher.multi.internal.types.MultipleQueriesStrategycom.algolia.instantsearch.searcher.multi.internal.DefaultMultiSearcher→com.algolia.instantsearch.searcher.multi.internal.types.ResponseMultiSearchcom.algolia.instantsearch.searcher.multi.internal.MultiSearchComponentKt→com.algolia.instantsearch.searcher.multi.internal.types.IndexedQuery
- Direction
- searcher.multi.internal uses searcher.multi.internal.types, so a change to searcher.multi.internal.types can break searcher.multi.internal, while a change to searcher.multi.internal can't break searcher.multi.internal.types.
- Position
- Below the diagonal: searcher.multi.internal uses a module listed above it, which is the healthy direction.
38→10 searcher.multi.internal uses core.searcher✕
- Connections
- 2 pairs of types, where a type in searcher.multi.internal uses a type in core.searcher.
- The types involved
com.algolia.instantsearch.searcher.multi.internal.DefaultMultiSearcher→com.algolia.instantsearch.core.searcher.Sequencercom.algolia.instantsearch.searcher.multi.internal.MultiSearchComponent→com.algolia.instantsearch.core.searcher.Searcher
- Direction
- searcher.multi.internal uses core.searcher, so a change to core.searcher can break searcher.multi.internal, while a change to searcher.multi.internal can't break core.searcher.
- Position
- Below the diagonal: searcher.multi.internal uses a module listed above it, which is the healthy direction.
38→36 searcher.multi.internal uses searcher.internal✕
- Connections
- 1 pair of types, where a type in searcher.multi.internal uses a type in searcher.internal.
- The types involved
com.algolia.instantsearch.searcher.multi.internal.DefaultMultiSearcher→com.algolia.instantsearch.searcher.internal.SearcherExceptionHandler
- Direction
- searcher.multi.internal uses searcher.internal, so a change to searcher.internal can break searcher.multi.internal, while a change to searcher.multi.internal can't break searcher.internal.
- Position
- Below the diagonal: searcher.multi.internal uses a module listed above it, which is the healthy direction.
39→3 searcher.composition.internal uses core.subscription✕
- Connections
- 2 pairs of types, where a type in searcher.composition.internal uses a type in core.subscription.
- The types involved
com.algolia.instantsearch.searcher.composition.internal.DefaultCompositionFacetsSearcher→com.algolia.instantsearch.core.subscription.SubscriptionValuecom.algolia.instantsearch.searcher.composition.internal.DefaultCompositionSearcher→com.algolia.instantsearch.core.subscription.SubscriptionValue
- Direction
- searcher.composition.internal uses core.subscription, so a change to core.subscription can break searcher.composition.internal, while a change to searcher.composition.internal can't break core.subscription.
- Position
- Below the diagonal: searcher.composition.internal uses a module listed above it, which is the healthy direction.
39→4 searcher.composition.internal uses filter✕
- Connections
- 3 pairs of types, where a type in searcher.composition.internal uses a type in filter.
- The types involved
com.algolia.instantsearch.searcher.composition.internal.CompositionSearchService→com.algolia.instantsearch.filter.FilterGroupcom.algolia.instantsearch.searcher.composition.internal.DefaultCompositionSearchService→com.algolia.instantsearch.filter.FilterGroupcom.algolia.instantsearch.searcher.composition.internal.DefaultCompositionSearcher→com.algolia.instantsearch.filter.FilterGroup
- Direction
- searcher.composition.internal uses filter, so a change to filter can break searcher.composition.internal, while a change to searcher.composition.internal can't break filter.
- Position
- Below the diagonal: searcher.composition.internal uses a module listed above it, which is the healthy direction.
39→10 searcher.composition.internal uses core.searcher✕
- Connections
- 2 pairs of types, where a type in searcher.composition.internal uses a type in core.searcher.
- The types involved
com.algolia.instantsearch.searcher.composition.internal.DefaultCompositionFacetsSearcher→com.algolia.instantsearch.core.searcher.Sequencercom.algolia.instantsearch.searcher.composition.internal.DefaultCompositionSearcher→com.algolia.instantsearch.core.searcher.Sequencer
- Direction
- searcher.composition.internal uses core.searcher, so a change to core.searcher can break searcher.composition.internal, while a change to searcher.composition.internal can't break core.searcher.
- Position
- Below the diagonal: searcher.composition.internal uses a module listed above it, which is the healthy direction.
39→38 searcher.composition.internal uses searcher.multi.internal✕
- Connections
- 2 pairs of types, where a type in searcher.composition.internal uses a type in searcher.multi.internal.
- The types involved
com.algolia.instantsearch.searcher.composition.internal.CompositionFacetsSearchService→com.algolia.instantsearch.searcher.multi.internal.SearchServicecom.algolia.instantsearch.searcher.composition.internal.CompositionSearchService→com.algolia.instantsearch.searcher.multi.internal.SearchService
- Direction
- searcher.composition.internal uses searcher.multi.internal, so a change to searcher.multi.internal can break searcher.composition.internal, while a change to searcher.composition.internal can't break searcher.multi.internal.
- Position
- Below the diagonal: searcher.composition.internal uses a module listed above it, which is the healthy direction.
40→3 searcher.hits.internal uses core.subscription✕
- Connections
- 1 pair of types, where a type in searcher.hits.internal uses a type in core.subscription.
- The types involved
com.algolia.instantsearch.searcher.hits.internal.DefaultHitsSearcher→com.algolia.instantsearch.core.subscription.SubscriptionValue
- Direction
- searcher.hits.internal uses core.subscription, so a change to core.subscription can break searcher.hits.internal, while a change to searcher.hits.internal can't break core.subscription.
- Position
- Below the diagonal: searcher.hits.internal uses a module listed above it, which is the healthy direction.
40→4 searcher.hits.internal uses filter✕
- Connections
- 4 pairs of types, where a type in searcher.hits.internal uses a type in filter.
- The types involved
com.algolia.instantsearch.searcher.hits.internal.DefaultHitsSearchService→com.algolia.instantsearch.filter.Filtercom.algolia.instantsearch.searcher.hits.internal.DefaultHitsSearchService→com.algolia.instantsearch.filter.FilterGroupcom.algolia.instantsearch.searcher.hits.internal.DefaultHitsSearcher→com.algolia.instantsearch.filter.FilterGroupcom.algolia.instantsearch.searcher.hits.internal.HitsSearchService→com.algolia.instantsearch.filter.FilterGroup
- Direction
- searcher.hits.internal uses filter, so a change to filter can break searcher.hits.internal, while a change to searcher.hits.internal can't break filter.
- Position
- Below the diagonal: searcher.hits.internal uses a module listed above it, which is the healthy direction.
40→5 searcher.hits.internal uses searcher.multi.internal.types✕
- Connections
- 3 pairs of types, where a type in searcher.hits.internal uses a type in searcher.multi.internal.types.
- The types involved
com.algolia.instantsearch.searcher.hits.internal.DefaultHitsSearchService→com.algolia.instantsearch.searcher.multi.internal.types.IndexQuerycom.algolia.instantsearch.searcher.hits.internal.DefaultHitsSearcher→com.algolia.instantsearch.searcher.multi.internal.types.IndexQuerycom.algolia.instantsearch.searcher.hits.internal.HitsSearchService→com.algolia.instantsearch.searcher.multi.internal.types.IndexQuery
- Direction
- searcher.hits.internal uses searcher.multi.internal.types, so a change to searcher.multi.internal.types can break searcher.hits.internal, while a change to searcher.hits.internal can't break searcher.multi.internal.types.
- Position
- Below the diagonal: searcher.hits.internal uses a module listed above it, which is the healthy direction.
40→10 searcher.hits.internal uses core.searcher✕
- Connections
- 1 pair of types, where a type in searcher.hits.internal uses a type in core.searcher.
- The types involved
com.algolia.instantsearch.searcher.hits.internal.DefaultHitsSearcher→com.algolia.instantsearch.core.searcher.Sequencer
- Direction
- searcher.hits.internal uses core.searcher, so a change to core.searcher can break searcher.hits.internal, while a change to searcher.hits.internal can't break core.searcher.
- Position
- Below the diagonal: searcher.hits.internal uses a module listed above it, which is the healthy direction.
40→15 searcher.hits.internal uses filter.Filter✕
- Connections
- 3 pairs of types, where a type in searcher.hits.internal uses a type in filter.Filter.
- The types involved
com.algolia.instantsearch.searcher.hits.internal.DefaultHitsSearchService→com.algolia.instantsearch.filter.Filter.Facetcom.algolia.instantsearch.searcher.hits.internal.DefaultHitsSearchService→com.algolia.instantsearch.filter.Filter.Numericcom.algolia.instantsearch.searcher.hits.internal.DefaultHitsSearchService→com.algolia.instantsearch.filter.Filter.Tag
- Direction
- searcher.hits.internal uses filter.Filter, so a change to filter.Filter can break searcher.hits.internal, while a change to searcher.hits.internal can't break filter.Filter.
- Position
- Below the diagonal: searcher.hits.internal uses a module listed above it, which is the healthy direction.
40→38 searcher.hits.internal uses searcher.multi.internal✕
- Connections
- 3 pairs of types, where a type in searcher.hits.internal uses a type in searcher.multi.internal.
- The types involved
com.algolia.instantsearch.searcher.hits.internal.DefaultHitsSearcher→com.algolia.instantsearch.searcher.multi.internal.MultiSearchComponentcom.algolia.instantsearch.searcher.hits.internal.DefaultHitsSearcher→com.algolia.instantsearch.searcher.multi.internal.MultiSearchOperationcom.algolia.instantsearch.searcher.hits.internal.HitsSearchService→com.algolia.instantsearch.searcher.multi.internal.SearchService
- Direction
- searcher.hits.internal uses searcher.multi.internal, so a change to searcher.multi.internal can break searcher.hits.internal, while a change to searcher.hits.internal can't break searcher.multi.internal.
- Position
- Below the diagonal: searcher.hits.internal 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 | 15 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
Roadmap
Top priorities: 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; Resolve the 29 Orphaned file finding(s) in Knowledge Freshness — start with Telemetry.kt (2), build.gradle.kts (2), Insights.kt (2); Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| 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. | +5.4 pts | Medium | Architecture documentation |
| Resolve the 29 Orphaned file finding(s) in Knowledge Freshness — start with Telemetry.kt (2), build.gradle.kts (2), Insights.kt (2). | +4.2 pts | Medium | Knowledge Freshness |
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +2.4 pts | Medium | Security & performance tooling |
| Interpolated log message defeats structured logging | +1.8 pts | Medium | Structured logging |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +1.8 pts | Medium | Documentation (README) |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +0.7 pts | Low | Bus Factor |
| Swallowed exception (caught, then discarded) | +1.4 pts | Medium | Exception handling |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +0.6 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.8 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/codex/suggestions/categories/SearchScreen.kt | 7.1 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/codex/categorieshits/SearchScreen.kt | 7.1 | Mixed | Code Duplication: Edited copies of one member (3 members, 31+ corresponding lines) |
| instantsearch-agent/src/commonMain/kotlin/com/algolia/instantsearch/agent/chat/ChunkReducer.kt | 7.4 | Mixed | Cyclomatic Complexity: ChunkReducer.apply (cyclomatic 27) |
| examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/compose/ui/component/SearchBox.kt | 7.4 | Mixed | Code Duplication: Duplicated block (26 lines × 3) |
| examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/compose/ui/component/MoviesList.kt | 7.4 | Mixed | Code Duplication: Edited copy of a member (35 corresponding lines) |
| instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/extension/EventsItems.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (29 corresponding lines) |
| instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/composition/CompositionFacetsSearcher.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (12 corresponding lines) |
| extensions/android-paging3/src/main/kotlin/com/algolia/instantsearch/android/paging3/searchbox/internal/SearchBoxConnectionPaginator.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (7 corresponding lines) |
| instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/composition/internal/DefaultCompositionFacetsSearcher.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (6 corresponding lines) |
| examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/compose/search/SearchAsYouTypeShowcase.kt | 7.8 | Mixed | Code Duplication: Duplicated block (20 lines × 2) |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| instantsearch/src/commonMain/kotlin/com/algolia/search/helper/Deserialize.kt | 8.5 | Near-clean | Code Duplication: Edited copy of a member (11 corresponding lines) |
| instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/composition/internal/DefaultCompositionSearcher.kt | 8.5 | Near-clean | Code Duplication: Edited copy of a member (6 corresponding lines) |
| instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/current/FilterAndID.kt | 8.5 | Near-clean | Code Duplication: Edited copy of a member (3 corresponding lines) |
| instantsearch-core/src/commonMain/kotlin/com/algolia/instantsearch/core/number/NumberViewModel.kt | 8.5 | Near-clean | Code Duplication: Edited copy of a member (5 corresponding lines) |
| examples/androidtv/src/main/java/com/algolia/instantsearch/examples/androidtv/ui/SearchBox.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (13 lines × 2) |
| instantsearch/src/androidMain/kotlin/com/algolia/instantsearch/android/hits/internal/HitsArrayAdapterConnection.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (9 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
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 46 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 46 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, 143 of 360 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D12 Dependency Hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Gradle tree, and its score reflects currency alone.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `instantsearch-core/src/commonMain/kotlin/com/algolia/instantsearch/filter/FilterGroupsConverter.kt`, `instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/mapper/InsightsEventsMapper.kt`, `instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/state/FilterState.kt`, `instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/facets/SearchForFacetQuery.kt`, `instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/hits/SearchForQuery.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.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (instantsearch-insights/src/androidMain/AndroidManifest.xml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- 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
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ChunkReducer.apply at 27. 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 UIMessageChunk.decodeOrThrow at 22 — 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: instantsearch-agent/src/commonMain/kotlin/com/algolia/instantsearch/agent/model/UIMessageChunk.kt (UIMessageChunk.decodeOrThrow at 22). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with ChunkReducer.apply (cyclomatic 27). — Refactoring it lifts Cyclomatic Complexity from 9.3 to about 10.0/10.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
28 duplicated block group(s) detected. 7.0 % of the production lines (1,756 of 25,239) are in a reported copy. A further 31 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 39 of the 59 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 4 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with HitsArrayAdapterConnection.kt, FacetListConnectionSearcher.kt, SearchScreen.kt. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with DefaultCompositionFacetsSearcher.kt, FilterListFacetShowcase.kt, SearchAsYouTypeShowcase.kt. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Edited copy of a member (6 corresponding lines) finding(s) in Code Duplication — start with ChunkReducer.kt, DefaultCompositionSearcher.kt, DefaultCompositionFacetsSearcher.kt. — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
10 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; 1 module(s) off the main sequence, with abstractness counted on 9 of the 10 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 121 classes have LCOM4 above 3.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Java/Kotlin (repository root, Gradle): measured (0 flaky).
D12 · Dependency Hygiene
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 472 artifact(s) resolved, 276 of them gradable against Maven Central, and 208 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 20 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 14 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 5 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 23 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.
D16 · Bus Factor
3 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/mapper/InsightsEventsMapper.kt. Counted over 58 of the 444 production source files in this repository: 385 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
D17 · Explicit Debt
0 deducted task-comment markers across 25239 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 5 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 9 build units (Gradle) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
62 % of calls cross a namespace and 9 % 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)
15 finding(s): 0 critical, 11 high, 4 medium, 0 low. 11 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 177) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 11 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 (11 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
29 of 59 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/extension/Telemetry.kt. Counted over 59 of the 444 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 29 Orphaned file finding(s) in Knowledge Freshness — start with Telemetry.kt (2), build.gradle.kts (2), Insights.kt (2). — One of this dimension's main actionable groups (29 recommendation-level).
- Resolve the 1 Concentrated knowledge decay 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 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 12 platform declaration(s) and 47 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
- 1 public type in `com.algolia.instantsearch.compose.internal` is marked as implementation by its own namespace, folder or name: `TelemetryKt` (instantsearch-compose/src/main/java/com/algolia/instantsearch/compose/internal/Telemetry.kt:1, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — instantsearch-compose/src/main/java/com/algolia/instantsearch/compose/internal/Telemetry.kt:1
- 1 public type in `com.algolia.instantsearch.compose.searchbox.internal` is marked as implementation by its own namespace, folder or name: `SearchBoxComponentsKt` (instantsearch-compose/src/main/java/com/algolia/instantsearch/compose/searchbox/internal/SearchBoxComponents.kt:1, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — instantsearch-compose/src/main/java/com/algolia/instantsearch/compose/searchbox/internal/SearchBoxComponents.kt:1
- 3 public types in `com.algolia.instantsearch.core.internal` are marked as implementation by their own namespace, folder or name: `CollectionsKt` (instantsearch-core/src/commonMain/kotlin/com/algolia/instantsearch/core/internal/Collections.kt:1, `internal`), `ExceptionKt` (instantsearch-core/src/commonMain/kotlin/com/algolia/instantsearch/core/internal/Exception.kt:1, `internal`), `TelemetryKt` (instantsearch-core/src/commonMain/kotlin/com/algolia/instantsearch/core/internal/Telemetry.kt:1, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — instantsearch-core/src/commonMain/kotlin/com/algolia/instantsearch/core/internal/Collections.kt:1
- 1 public type in `com.algolia.instantsearch.core.number.range.internal` is marked as implementation by its own namespace, folder or name: `ExtensionsKt` (instantsearch-core/src/commonMain/kotlin/com/algolia/instantsearch/core/number/range/internal/Extensions.kt:1, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — instantsearch-core/src/commonMain/kotlin/com/algolia/instantsearch/core/number/range/internal/Extensions.kt:1
- 1 public type in `com.algolia.instantsearch.insights.internal` is marked as implementation by its own namespace, folder or name: `InsightsControllerKt` (instantsearch-insights/src/androidMain/kotlin/com/algolia/instantsearch/insights/internal/InsightsController.kt:1, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — instantsearch-insights/src/androidMain/kotlin/com/algolia/instantsearch/insights/internal/InsightsController.kt:1
- 7 public types in `com.algolia.instantsearch.insights.internal.extension` are marked as implementation by their own namespace, folder or name: `PlatformKt` (instantsearch-insights/src/androidMain/kotlin/com/algolia/instantsearch/insights/internal/extension/Platform.kt:1, `internal`), `TimeKt` (instantsearch-insights/src/androidMain/kotlin/com/algolia/instantsearch/insights/internal/extension/Time.kt:1, `internal`), `UUIDKt` (instantsearch-insights/src/androidMain/kotlin/com/algolia/instantsearch/insights/internal/extension/UUID.kt:1, `internal`), `EventsItemsKt` (instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/extension/EventsItems.kt:1, `internal`), `InsightsKt` (instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/extension/Insights.kt:1, `internal`), `JsonKt` (instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/extension/Json.kt:1, `internal`), `MapKt` (instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/extension/Map.kt:1, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — instantsearch-insights/src/androidMain/kotlin/com/algolia/instantsearch/insights/internal/extension/Platform.kt:1
- 3 public types in `com.algolia.instantsearch.insights.internal.extension.SharedPreferencesDelegate` are marked as implementation by their own namespace, folder or name: `Int` (instantsearch-insights/src/androidMain/kotlin/com/algolia/instantsearch/insights/internal/extension/SharedPreferencesDelegate.kt:12, `internal`), `String` (instantsearch-insights/src/androidMain/kotlin/com/algolia/instantsearch/insights/internal/extension/SharedPreferencesDelegate.kt:23, `internal`), `StringSet` (instantsearch-insights/src/androidMain/kotlin/com/algolia/instantsearch/insights/internal/extension/SharedPreferencesDelegate.kt:35, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — instantsearch-insights/src/androidMain/kotlin/com/algolia/instantsearch/insights/internal/extension/SharedPreferencesDelegate.kt:12
- 1 public type in `com.algolia.instantsearch.insights.internal.worker.InsightsWorkManager` is marked as implementation by its own namespace, folder or name: `Companion` (instantsearch-insights/src/androidMain/kotlin/com/algolia/instantsearch/insights/internal/worker/InsightsWorkManager.kt:51, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — instantsearch-insights/src/androidMain/kotlin/com/algolia/instantsearch/insights/internal/worker/InsightsWorkManager.kt:51
- 1 public type in `com.algolia.instantsearch.insights.internal.data.local.mapper` is marked as implementation by its own namespace, folder or name: `InsightsEventsMapperKt` (instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/mapper/InsightsEventsMapper.kt:1, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/mapper/InsightsEventsMapper.kt:1
- 3 public types in `com.algolia.instantsearch.insights.internal.data.local.model.FilterFacetDO.ValueType` are marked as implementation by their own namespace, folder or name: `String` (instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/model/FilterFacetDO.kt:19, `internal`), `Boolean` (instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/model/FilterFacetDO.kt:22, `internal`), `Number` (instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/model/FilterFacetDO.kt:25, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/model/FilterFacetDO.kt:19
- 3 public types in `com.algolia.instantsearch.insights.internal.data.local.model.InsightsEventDO.EventType` are marked as implementation by their own namespace, folder or name: `Click` (instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/model/InsightsEventDO.kt:26, `internal`), `View` (instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/model/InsightsEventDO.kt:29, `internal`), `Conversion` (instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/model/InsightsEventDO.kt:32, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/model/InsightsEventDO.kt:26
- 2 public types in `com.algolia.instantsearch.insights.internal.data.local.model.InsightsEventDO.EventSubtype` are marked as implementation by their own namespace, folder or name: `Purchase` (instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/model/InsightsEventDO.kt:38, `internal`), `AddToCart` (instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/model/InsightsEventDO.kt:41, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/model/InsightsEventDO.kt:38
- 1 public type in `com.algolia.instantsearch.insights.internal.data.local.model.InsightsEventDO` is marked as implementation by its own namespace, folder or name: `Builder` (instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/model/InsightsEventDO.kt:44, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/model/InsightsEventDO.kt:44
- 1 public type in `com.algolia.instantsearch.insights.internal.event.EventResponse` is marked as implementation by its own namespace, folder or name: `Companion` (instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/event/EventResponse.kt:11, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/event/EventResponse.kt:11
- 1 public type in `com.algolia.instantsearch.insights.internal.uploader.InsightsEventUploader` is marked as implementation by its own namespace, folder or name: `Companion` (instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/uploader/InsightsEventUploader.kt:47, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/uploader/InsightsEventUploader.kt:47
- 1 public type in `com.algolia.instantsearch.android.internal` is marked as implementation by its own namespace, folder or name: `TelemetryKt` (instantsearch/src/androidMain/kotlin/com/algolia/instantsearch/android/internal/Telemetry.kt:1, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — instantsearch/src/androidMain/kotlin/com/algolia/instantsearch/android/internal/Telemetry.kt:1
- 5 public types in `com.algolia.instantsearch.searcher.internal` are marked as implementation by their own namespace, folder or name: `ActualKt` (instantsearch/src/androidMain/kotlin/com/algolia/instantsearch/searcher/internal/Actual.kt:1, `internal`), `ExpectedKt` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/internal/Expected.kt:1, `internal`), `LoadingKt` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/internal/Loading.kt:1, `internal`), `SearchClientExtensionsKt` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/internal/SearchClientExtensions.kt:1, `internal`), `WithUserAgentKt` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/internal/withUserAgent.kt:1, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — instantsearch/src/androidMain/kotlin/com/algolia/instantsearch/searcher/internal/Actual.kt:1
- 1 public type in `com.algolia.instantsearch.filter.current.internal` is marked as implementation by its own namespace, folder or name: `FilterAndIDKt` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/current/internal/FilterAndID.kt:1, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/current/internal/FilterAndID.kt:1
- 1 public type in `com.algolia.instantsearch.filter.facet.dynamic.internal` is marked as implementation by its own namespace, folder or name: `FacetsOrderKt` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/facet/dynamic/internal/FacetsOrder.kt:1, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/facet/dynamic/internal/FacetsOrder.kt:1
- 1 public type in `com.algolia.instantsearch.filter.list.internal` is marked as implementation by its own namespace, folder or name: `ExtensionsKt` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/list/internal/Extensions.kt:1, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/list/internal/Extensions.kt:1
- 1 public type in `com.algolia.instantsearch.filter.range.internal` is marked as implementation by its own namespace, folder or name: `MapperKt` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/range/internal/Mapper.kt:1, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/range/internal/Mapper.kt:1
- 1 public type in `com.algolia.instantsearch.hierarchical.internal` is marked as implementation by its own namespace, folder or name: `ExtensionsKt` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/hierarchical/internal/Extensions.kt:1, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/hierarchical/internal/Extensions.kt:1
- 4 public types in `com.algolia.instantsearch.relateditems.internal.extensions` are marked as implementation by their own namespace, folder or name: `FilterStateKt` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/relateditems/internal/extensions/FilterState.kt:1, `internal`), `IndexableKt` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/relateditems/internal/extensions/Indexable.kt:1, `internal`), `MatchingPatternKt` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/relateditems/internal/extensions/MatchingPattern.kt:1, `internal`), `UnquoteKt` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/relateditems/internal/extensions/Unquote.kt:1, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/relateditems/internal/extensions/FilterState.kt:1
- 1 public type in `com.algolia.instantsearch.searcher.composition.internal` is marked as implementation by its own namespace, folder or name: `CompositionExtensionsKt` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/composition/internal/CompositionExtensions.kt:1, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/composition/internal/CompositionExtensions.kt:1
- 1 public type in `com.algolia.instantsearch.searcher.composition.internal.CompositionFacetsSearchService` is marked as implementation by its own namespace, folder or name: `Request` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/composition/internal/CompositionFacetsSearchService.kt:25, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/composition/internal/CompositionFacetsSearchService.kt:25
- 1 public type in `com.algolia.instantsearch.searcher.composition.internal.CompositionSearchService` is marked as implementation by its own namespace, folder or name: `Request` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/composition/internal/CompositionSearchService.kt:29, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/composition/internal/CompositionSearchService.kt:29
- 2 public types in `com.algolia.instantsearch.searcher.hits.internal.HitsSearchService` are marked as implementation by their own namespace, folder or name: `Request` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/hits/internal/DefaultHitsSearchService.kt:46, `internal`), `AdvancedQuery` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/hits/internal/DefaultHitsSearchService.kt:55, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/hits/internal/DefaultHitsSearchService.kt:46
- 1 public type in `com.algolia.instantsearch.searcher.hits.internal.DefaultHitsSearcher` is marked as implementation by its own namespace, folder or name: `Companion` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/hits/internal/DefaultHitsSearcher.kt:139, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/hits/internal/DefaultHitsSearcher.kt:139
- 1 public type in `com.algolia.instantsearch.searcher.multi.internal` is marked as implementation by its own namespace, folder or name: `MultiSearchComponentKt` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/MultiSearchComponent.kt:1, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/MultiSearchComponent.kt:1
- 1 public type in `com.algolia.instantsearch.searcher.multi.internal.MultiSearchService` is marked as implementation by its own namespace, folder or name: `Request` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/MultiSearchService.kt:24, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/MultiSearchService.kt:24
- 1 public type in `com.algolia.instantsearch.searcher.multi.internal.extension` is marked as implementation by its own namespace, folder or name: `ResponseMultiSearchKt` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/extension/ResponseMultiSearch.kt:1, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/extension/ResponseMultiSearch.kt:1
- 7 public types in `com.algolia.instantsearch.searcher.multi.internal.types` are marked as implementation by their own namespace, folder or name: `IndexedQuery` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/types/IndexedQuery.kt:7, `internal`), `IndexQuery` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/types/IndexedQuery.kt:17, `internal`), `FacetIndexQuery` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/types/IndexedQuery.kt:25, `internal`), `MultipleQueriesStrategy` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/types/MultipleQueriesStrategy.kt:12, `internal`), `ResponseMultiSearchKt` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/types/ResponseMultiSearch.kt:1, `internal`), `ResponseMultiSearch` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/types/ResponseMultiSearch.kt:23, `internal`), `ResultMultiSearch` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/types/ResponseMultiSearch.kt:34, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/types/IndexedQuery.kt:7
- 4 public types in `com.algolia.instantsearch.searcher.multi.internal.types.MultipleQueriesStrategy` are marked as implementation by their own namespace, folder or name: `None` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/types/MultipleQueriesStrategy.kt:18, `internal`), `StopIfEnoughMatches` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/types/MultipleQueriesStrategy.kt:25, `internal`), `Other` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/types/MultipleQueriesStrategy.kt:27, `internal`), `Companion` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/types/MultipleQueriesStrategy.kt:33, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/types/MultipleQueriesStrategy.kt:18
- 2 public types in `com.algolia.instantsearch.searcher.multi.internal.types.ResultMultiSearch` are marked as implementation by their own namespace, folder or name: `Hits` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/types/ResponseMultiSearch.kt:40, `internal`), `Facets` (instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/types/ResponseMultiSearch.kt:43, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/types/ResponseMultiSearch.kt:40
What to do
- Hide `com.algolia.instantsearch.compose.internal` (`TelemetryKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.compose.searchbox.internal` (`SearchBoxComponentsKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.core.internal` (`CollectionsKt`, `ExceptionKt`, `TelemetryKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.core.number.range.internal` (`ExtensionsKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.insights.internal` (`InsightsControllerKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.insights.internal.extension` (`PlatformKt`, `TimeKt`, `UUIDKt`, `EventsItemsKt`, `InsightsKt`, `JsonKt`, `MapKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.insights.internal.extension.SharedPreferencesDelegate` (`Int`, `String`, `StringSet`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.insights.internal.worker.InsightsWorkManager` (`Companion`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.insights.internal.data.local.mapper` (`InsightsEventsMapperKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.insights.internal.data.local.model.FilterFacetDO.ValueType` (`String`, `Boolean`, `Number`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.insights.internal.data.local.model.InsightsEventDO.EventType` (`Click`, `View`, `Conversion`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.insights.internal.data.local.model.InsightsEventDO.EventSubtype` (`Purchase`, `AddToCart`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.insights.internal.data.local.model.InsightsEventDO` (`Builder`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.insights.internal.event.EventResponse` (`Companion`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.insights.internal.uploader.InsightsEventUploader` (`Companion`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.android.internal` (`TelemetryKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.searcher.internal` (`ActualKt`, `ExpectedKt`, `LoadingKt`, `SearchClientExtensionsKt`, `WithUserAgentKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.filter.current.internal` (`FilterAndIDKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.filter.facet.dynamic.internal` (`FacetsOrderKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.filter.list.internal` (`ExtensionsKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.filter.range.internal` (`MapperKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.hierarchical.internal` (`ExtensionsKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.relateditems.internal.extensions` (`FilterStateKt`, `IndexableKt`, `MatchingPatternKt`, `UnquoteKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.searcher.composition.internal` (`CompositionExtensionsKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.searcher.composition.internal.CompositionFacetsSearchService` (`Request`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.searcher.composition.internal.CompositionSearchService` (`Request`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.searcher.hits.internal.HitsSearchService` (`Request`, `AdvancedQuery`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.searcher.hits.internal.DefaultHitsSearcher` (`Companion`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.searcher.multi.internal` (`MultiSearchComponentKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.searcher.multi.internal.MultiSearchService` (`Request`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.searcher.multi.internal.extension` (`ResponseMultiSearchKt`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.searcher.multi.internal.types` (`IndexedQuery`, `IndexQuery`, `FacetIndexQuery`, `MultipleQueriesStrategy`, `ResponseMultiSearchKt`, `ResponseMultiSearch`, `ResultMultiSearch`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.searcher.multi.internal.types.MultipleQueriesStrategy` (`None`, `StopIfEnoughMatches`, `Other`, `Companion`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `com.algolia.instantsearch.searcher.multi.internal.types.ResultMultiSearch` (`Hits`, `Facets`) (Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X3 · Exception handling
- `catch (e: Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/extension/Utils.kt:6
What to do
- Swallowed exception (caught, then discarded)
X4 · Structured logging
- `debug` at line 13 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — instantsearch-insights/src/jvmMain/kotlin/com/algolia/instantsearch/insights/internal/logging/InsightsLogger.kt:13
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 67.7 | Adequate — gated by X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 96.9 | Exemplary | Solid. |
| Maturity | 58.9 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 63.5 | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 76.6 | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
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 — 70 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's 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 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
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~7988 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (6022 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Kotlin surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 5 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 130 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 (9 module(s), 433 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Kotlin was 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 Kotlin request outside a suspend function has no caller's cancellation to honour
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 — 11 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 69 finding(s)
- Duplicated block (9 lines × 2) instantsearch/src/androidMain/kotlin/com/algolia/instantsearch/android/hits/internal/HitsArrayAdapterConnection.kt:36
- Duplicated block (9 lines × 2) instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/facet/internal/FacetListConnectionSearcher.kt:36
- Duplicated block (9 lines × 2) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/codex/categorieshits/SearchScreen.kt:128
- Duplicated block (9 lines × 2) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/androidview/filter/facet/FacetListShowcase.kt:108
- Duplicated block (14 lines × 2) instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/composition/internal/DefaultCompositionFacetsSearcher.kt:50
- Duplicated block (14 lines × 2) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/compose/filter/list/FilterListFacetShowcase.kt:58
- Duplicated block (14 lines × 2) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/compose/search/SearchAsYouTypeShowcase.kt:43
- Duplicated block (14 lines × 2) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/codex/categorieshits/SearchScreen.kt:42
- Edited copy of a member (6 corresponding lines) instantsearch-agent/src/commonMain/kotlin/com/algolia/instantsearch/agent/chat/ChunkReducer.kt:137
- Edited copy of a member (6 corresponding lines) instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/composition/internal/DefaultCompositionSearcher.kt:62
- Edited copy of a member (6 corresponding lines) instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/composition/internal/DefaultCompositionFacetsSearcher.kt:65
- Duplicated block (11 lines × 2) instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/facet/FacetListConnector.kt:93
- Duplicated block (11 lines × 2) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/codex/suggestions/hits/SearchScreen.kt:36
- Duplicated block (11 lines × 2) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/androidview/list/movie/MovieAdapter.kt:11
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (11 corresponding lines) instantsearch/src/commonMain/kotlin/com/algolia/search/helper/Deserialize.kt:15
- Edited copy of a member (11 corresponding lines) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/compose/ui/component/ActorsList.kt:43
- Edited copy of a member (7 corresponding lines) extensions/android-paging3/src/main/kotlin/com/algolia/instantsearch/android/paging3/searchbox/internal/SearchBoxConnectionPaginator.kt:23
- Edited copy of a member (7 corresponding lines) extensions/android-paging3/src/main/kotlin/com/algolia/instantsearch/android/paging3/searchbox/internal/SearchBoxConnectionPaginator.kt:31
- Duplicated block (13 lines × 2) examples/androidtv/src/main/java/com/algolia/instantsearch/examples/androidtv/ui/SearchBox.kt:100
- Duplicated block (13 lines × 2) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/compose/ui/component/FacetList.kt:115
- Edited copy of a member (22 corresponding lines) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/codex/categorieshits/SearchScreen.kt:41
- Edited copy of a member (22 corresponding lines) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/compose/customdata/QueryRuleCustomDataShowcase.kt:108
- Edited copy of a member (9 corresponding lines) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/compose/ui/component/MoviesList.kt:135
- Edited copy of a member (9 corresponding lines) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/androidview/list/movie/MovieViewHolderNested.kt:10
- Duplicated block (7 lines × 2) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/codex/suggestions/categories/SearchScreen.kt:170
- Duplicated block (7 lines × 2) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/androidview/customdata/QueryRuleCustomDataShowcase.kt:102
- ChunkReducer.apply (cyclomatic 27) instantsearch-agent/src/commonMain/kotlin/com/algolia/instantsearch/agent/chat/ChunkReducer.kt:37
- REDACTED
- Edited copy of a member (29 corresponding lines) instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/extension/EventsItems.kt:91
- Edited copy of a member (31 corresponding lines) instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/extension/EventsItems.kt:189
- Edited copies of one member (3 members, 10+ corresponding lines) instantsearch-agent/src/commonMain/kotlin/com/algolia/instantsearch/agent/chat/ChunkReducer.kt:126
- Edited copy of a member (12 corresponding lines) instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/composition/CompositionFacetsSearcher.kt:103
- Edited copies of one member (3 members, 11+ corresponding lines) instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/composition/CompositionFacetsSearcher.kt:63
- Edited copy of a member (3 corresponding lines) instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/current/FilterAndID.kt:8
- Edited copy of a member (5 corresponding lines) instantsearch-core/src/commonMain/kotlin/com/algolia/instantsearch/core/number/NumberViewModel.kt:27
- Duplicated block (26 lines × 3) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/compose/ui/component/SearchBox.kt:47
- Duplicated block (11 lines × 3) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/compose/ui/component/SearchBox.kt:79
- Members sharing a duplicated core (4 members, 50+ identical tokens) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/codex/suggestions/categories/SearchScreen.kt:138
- Edited copy of a member (35 corresponding lines) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/compose/ui/component/MoviesList.kt:84
- Edited copies of one member (3 members, 31+ corresponding lines) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/codex/categorieshits/SearchScreen.kt:91
- Edited copy of a member (32 corresponding lines) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/compose/hierarchical/HierarchicalShowcase.kt:148
- Edited copy of a member (20 corresponding lines) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/androidview/list/paging/PagingSingleIndexShowcase.kt:32
- Edited copy of a member (21 corresponding lines) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/compose/ui/component/AutoCompleteTextField.kt:22
- Edited copy of a member (34 corresponding lines) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/compose/filter/facet/FacetListPersistentShowcase.kt:87
- Edited copies of one member (4 members, 19+ corresponding lines) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/androidview/filter/list/FilterListFacetShowcase.kt:40
- Edited copy of a member (30 corresponding lines) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/codex/suggestions/categories/SearchScreen.kt:39
- Edited copies of one member (4 members, 18+ corresponding lines) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/codex/categorieshits/SearchScreen.kt:67
- Edited copy of a member (16 corresponding lines) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/compose/filter/toggle/FilterToggleShowcase.kt:126
- Edited copy of a member (14 corresponding lines) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/compose/ui/component/SearchBox.kt:101
- Edited copy of a member (13 corresponding lines) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/codex/suggestions/categories/SearchScreen.kt:119
- Duplicated block (18–20 lines × 2) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/androidview/search/SearchAsYouTypeShowcase.kt:27
- Duplicated block (20 lines × 2) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/compose/search/SearchAsYouTypeShowcase.kt:63
- Duplicated block (18 lines × 4) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/codex/suggestions/categories/SearchScreen.kt:150
- Duplicated block (16 lines × 3) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/compose/filter/clear/FilterClearShowcase.kt:93
- Duplicated block (11–13 lines × 2) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/codex/suggestions/categories/SearchScreen.kt:45
- Duplicated block (12–13 lines × 2) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/guides/extension/SearchView.kt:33
- Duplicated block (12 lines × 3) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/codex/categorieshits/SearchScreen.kt:97
- Duplicated block (10–11 lines × 3) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/codex/multisearch/MainActivity.kt:78
- Duplicated block (8–10 lines × 2) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/compose/ui/component/MoviesList.kt:86
- Duplicated block (6 lines × 3) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/showcase/androidview/highlighting/HighlightingShowcase.kt:28
- Duplicated block (12 lines × 4) examples/android/src/main/kotlin/com/algolia/instantsearch/examples/android/codex/categorieshits/MainActivity.kt:14
- Off the main sequence: :instantsearch-utils
- Swallowed exception (caught, then discarded) instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/extension/Utils.kt:6
Minor — 72 finding(s)
- Implementation type on the public API instantsearch-compose/src/main/java/com/algolia/instantsearch/compose/internal/Telemetry.kt:1
- Implementation type on the public API instantsearch-compose/src/main/java/com/algolia/instantsearch/compose/searchbox/internal/SearchBoxComponents.kt:1
- Implementation type on the public API instantsearch-core/src/commonMain/kotlin/com/algolia/instantsearch/core/internal/Collections.kt:1
- Implementation type on the public API instantsearch-core/src/commonMain/kotlin/com/algolia/instantsearch/core/number/range/internal/Extensions.kt:1
- Implementation type on the public API instantsearch-insights/src/androidMain/kotlin/com/algolia/instantsearch/insights/internal/InsightsController.kt:1
- Implementation type on the public API instantsearch-insights/src/androidMain/kotlin/com/algolia/instantsearch/insights/internal/extension/Platform.kt:1
- Implementation type on the public API instantsearch-insights/src/androidMain/kotlin/com/algolia/instantsearch/insights/internal/extension/SharedPreferencesDelegate.kt:12
- Implementation type on the public API instantsearch-insights/src/androidMain/kotlin/com/algolia/instantsearch/insights/internal/worker/InsightsWorkManager.kt:51
- Implementation type on the public API instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/mapper/InsightsEventsMapper.kt:1
- Implementation type on the public API instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/model/FilterFacetDO.kt:19
- Implementation type on the public API instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/model/InsightsEventDO.kt:26
- Implementation type on the public API instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/model/InsightsEventDO.kt:38
- Implementation type on the public API instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/model/InsightsEventDO.kt:44
- Implementation type on the public API instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/event/EventResponse.kt:11
- Implementation type on the public API instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/uploader/InsightsEventUploader.kt:47
- Implementation type on the public API instantsearch/src/androidMain/kotlin/com/algolia/instantsearch/android/internal/Telemetry.kt:1
- Implementation type on the public API instantsearch/src/androidMain/kotlin/com/algolia/instantsearch/searcher/internal/Actual.kt:1
- Implementation type on the public API instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/current/internal/FilterAndID.kt:1
- Implementation type on the public API instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/facet/dynamic/internal/FacetsOrder.kt:1
- Implementation type on the public API instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/list/internal/Extensions.kt:1
- Implementation type on the public API instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/range/internal/Mapper.kt:1
- Implementation type on the public API instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/hierarchical/internal/Extensions.kt:1
- Implementation type on the public API instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/relateditems/internal/extensions/FilterState.kt:1
- Implementation type on the public API instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/composition/internal/CompositionExtensions.kt:1
- Implementation type on the public API instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/composition/internal/CompositionFacetsSearchService.kt:25
- Orphaned file instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/extension/Telemetry.kt:1
- Orphaned file instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/hits/internal/DefaultHitsSearchService.kt:1
- Orphaned file instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/list/FilterListConnector.kt:1
- Orphaned file instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/hits/HitsSearcher.kt:1
- Orphaned file instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/hits/internal/DefaultHitsSearcher.kt:1
- Orphaned file instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/internal/DefaultMultiSearcher.kt:1
- Orphaned file instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/facet/dynamic/DynamicFacetListViewModel.kt:1
- Orphaned file instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/facets/FacetsSearcher.kt:1
- Orphaned file instantsearch/src/androidMain/kotlin/com/algolia/instantsearch/android/filter/facet/dynamic/DynamicFacetListAdapter.kt:1
- Orphaned file instantsearch-compose/src/main/java/com/algolia/instantsearch/compose/searchbox/SearchBox.kt:1
- Orphaned file instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/state/internal/DefaultMutableFilters.kt:1
- Orphaned file instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/facet/dynamic/internal/DynamicFacetListConnectionFilterState.kt:1
- Orphaned file instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/customdata/QueryRuleCustomDataConnector.kt:1
- Orphaned file instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/facet/dynamic/DynamicFacetListConnector.kt:1
- Orphaned file instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/facets/internal/DefaultFacetsSearcher.kt:1
- Orphaned file instantsearch-compose/src/main/java/com/algolia/instantsearch/compose/internal/Telemetry.kt:1
- Orphaned file instantsearch-insights/build.gradle.kts:1
- Orphaned file instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/range/FilterRangeConnector.kt:1
- Orphaned file instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/multi/MultiSearcher.kt:1
- Orphaned file instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/tracker/FilterTracker.kt:1
- Orphaned file instantsearch-insights/src/androidMain/kotlin/com/algolia/instantsearch/insights/Insights.kt:1
- Orphaned file instantsearch/build.gradle.kts:1
- Orphaned file instantsearch-core/src/commonMain/kotlin/com/algolia/instantsearch/core/tree/Extensions.kt:1
- Orphaned file instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/hierarchical/internal/HierarchicalConnectionSearcher.kt:1
- Orphaned file instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/tracker/HitsTracker.kt:1
- Off-boarding risk: anonymized user #1
- Projects may be oversized for their cohesion instantsearch/build.gradle.kts:1
- Concentrated knowledge decay
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST
- Interpolated log message defeats structured logging instantsearch-insights/src/jvmMain/kotlin/com/algolia/instantsearch/insights/internal/logging/InsightsLogger.kt:13
Minor — 208 finding(s)
- Outdated (compile): com.google.guava:guava
- Outdated (compile): com.google.guava:failureaccess
- Outdated (compile): org.checkerframework:checker-qual
- Outdated (compile): com.google.errorprone:error_prone_annotations
- Outdated (compile): com.google.j2objc:j2objc-annotations
- Outdated (compile): net.java.dev.jna:jna-platform
- Outdated (compile): net.java.dev.jna:jna
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk8
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib
- Outdated (compile): org.jetbrains:annotations
- Outdated (compile): org.jetbrains.kotlin:kotlin-stdlib-jdk7
- Outdated (compile): com.google.protobuf:protobuf-java
- Outdated (compile): com.google.code.gson:gson
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-core
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm
- Outdated (compile): org.jetbrains.kotlinx:kotlinx-coroutines-bom
- Outdated (compile): com.google.jimfs:jimfs
- Outdated (compile): org.apache.commons:commons-compress
- Outdated (compile): commons-codec:commons-codec
- Outdated (compile): commons-io:commons-io
- Outdated (compile): org.apache.commons:commons-lang3
- Outdated (compile): org.glassfish.jaxb:jaxb-runtime
- Outdated (compile): jakarta.xml.bind:jakarta.xml.bind-api
- Outdated (compile): jakarta.activation:jakarta.activation-api
- Outdated (compile): org.glassfish.jaxb:txw2
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-f22c01ab44dd4d549b16564de24b2c65/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-f22c01ab44dd4d549b16564de24b2c65/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=1553" --report-format json --report-path /tmp/watchdog-gitleaks-f22c01ab44dd4d549b16564de24b2c65/history-2.json --exit-code 0 --source . | 27 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f22c01ab44dd4d549b16564de24b2c65/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 15 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 5 file(s) — `instantsearch-core/src/commonMain/kotlin/com/algolia/instantsearch/filter/FilterGroupsConverter.kt`, `instantsearch-insights/src/commonMain/kotlin/com/algolia/instantsearch/insights/internal/data/local/mapper/InsightsEventsMapper.kt`, `instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/filter/state/FilterState.kt`, `instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/facets/SearchForFacetQuery.kt`, `instantsearch/src/commonMain/kotlin/com/algolia/instantsearch/searcher/hits/SearchForQuery.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) and a Gradle version catalogue — not scanned yet). | 0 | — |