Executive summary
jxareas/Xpensor falls short of our standard for a preview release because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 48 out of 100 and is rated Adequate, and it has no critical findings.
Production Readiness, at 26, is the weakest lens and counts most in the score. The best first steps are adding an automated build and test pipeline and adding automated security scanning, each worth about 11 points. Raising Production Readiness to 62 would lift the score to about 64.
The 23 serious findings are spread across the lenses, with the most in Architecture.
The product code is 5,151 lines, about €6,800 to rebuild.
If Production Readiness rose from 26 to 62, the lowest score rated Strong, the score would rise from 48 to about 64.
Rebuild cost: about €6,800 · Estimate
| Cost to rebuild | €2,300 to €11,000, for 38 to 119 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 48. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 5,151 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 common.utils | 2 core.data.local.dao | 3 core.data.local.preferences | 4 features.accounts.data.local.entity | 5 features.accounts.domain.model | 6 features.accounts.presentation.model | 7 features.converter.data.remote.api | 8 features.converter.domain.model | 9 features.transactions.data.local.entity | 10 features.transactions.presentation.model | 11 core.data.local.source | 12 features.accounts.data.local.dao | 13 features.accounts.domain.repository | 14 features.accounts.presentation.ui.adapter | 15 features.converter.data.remote.source.impl | 16 features.converter.domain.repository | 17 features.transactions.data.local.views | 18 features.transactions.domain.model | 19 features.transactions.presentation.ui.actions.category.adapter | 20 features.accounts.data.local.source | 21 features.accounts.domain.usecase | 22 features.converter.data.repository | 23 features.transactions.data.local.dao | 24 features.transactions.data.local.source | 25 features.transactions.domain.repository | 26 core.data.local.database | 27 core.presentation | 28 features.accounts.data.local.source.impl | 29 features.accounts.data.repository | 30 features.accounts.presentation.ui | 31 features.transactions.data.local.source.impl | 32 features.transactions.data.repository | 33 features.transactions.domain.usecase | 34 di.modules | 35 features.accounts.presentation.ui.actions | 36 features.accounts.presentation.ui.actions.filter | 37 features.chart.presentation.ui | 38 features.transactions.presentation.ui | 39 features.transactions.presentation.ui.actions.add | 40 features.transactions.presentation.ui.actions.category |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 common.utils | ||||||||||||||||||||||||||||||||||||||||
| 2 core.data.local.dao | ||||||||||||||||||||||||||||||||||||||||
| 3 core.data.local.preferences | ||||||||||||||||||||||||||||||||||||||||
| 4 features.accounts.data.local.entity | ||||||||||||||||||||||||||||||||||||||||
| 5 features.accounts.domain.model | ||||||||||||||||||||||||||||||||||||||||
| 6 features.accounts.presentation.model | ||||||||||||||||||||||||||||||||||||||||
| 7 features.converter.data.remote.api | ||||||||||||||||||||||||||||||||||||||||
| 8 features.converter.domain.model | ||||||||||||||||||||||||||||||||||||||||
| 9 features.transactions.data.local.entity | ||||||||||||||||||||||||||||||||||||||||
| 10 features.transactions.presentation.model | ||||||||||||||||||||||||||||||||||||||||
| 11 core.data.local.source | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 features.accounts.data.local.dao | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 features.accounts.domain.repository | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 features.accounts.presentation.ui.adapter | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 15 features.converter.data.remote.source.impl | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 features.converter.domain.repository | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 17 features.transactions.data.local.views | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 18 features.transactions.domain.model | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 features.transactions.presentation.ui.actions.category.adapter | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 20 features.accounts.data.local.source | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 features.accounts.domain.usecase | 4 | 5 | ||||||||||||||||||||||||||||||||||||||
| 22 features.converter.data.repository | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 23 features.transactions.data.local.dao | 2 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 24 features.transactions.data.local.source | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 25 features.transactions.domain.repository | 4 | |||||||||||||||||||||||||||||||||||||||
| 26 core.data.local.database | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 27 core.presentation | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 features.accounts.data.local.source.impl | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 29 features.accounts.data.repository | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 features.accounts.presentation.ui | 1 | 3 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 31 features.transactions.data.local.source.impl | 2 | 3 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 32 features.transactions.data.repository | 4 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 33 features.transactions.domain.usecase | 3 | 3 | 7 | 5 | ||||||||||||||||||||||||||||||||||||
| 34 di.modules | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 1 | 1 | 2 | 2 | ||||||||||||||||||||||||||||
| 35 features.accounts.presentation.ui.actions | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 features.accounts.presentation.ui.actions.filter | 1 | 3 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 37 features.chart.presentation.ui | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 features.transactions.presentation.ui | 2 | 2 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 39 features.transactions.presentation.ui.actions.add | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 40 features.transactions.presentation.ui.actions.category | 1 | 1 | 1 | 1 | 1 |
11→2 core.data.local.source uses core.data.local.dao✕
- Connections
- 1 pair of types, where a type in core.data.local.source uses a type in core.data.local.dao.
- The types involved
com.jxareas.xpensor.core.data.local.source.RoomLocalDataSource→com.jxareas.xpensor.core.data.local.dao.RoomDao
- Direction
- core.data.local.source uses core.data.local.dao, so a change to core.data.local.dao can break core.data.local.source, while a change to core.data.local.source can't break core.data.local.dao.
- Position
- Below the diagonal: core.data.local.source uses a module listed above it, which is the healthy direction.
12→2 features.accounts.data.local.dao uses core.data.local.dao✕
- Connections
- 1 pair of types, where a type in features.accounts.data.local.dao uses a type in core.data.local.dao.
- The types involved
com.jxareas.xpensor.features.accounts.data.local.dao.AccountDao→com.jxareas.xpensor.core.data.local.dao.RoomDao
- Direction
- features.accounts.data.local.dao uses core.data.local.dao, so a change to core.data.local.dao can break features.accounts.data.local.dao, while a change to features.accounts.data.local.dao can't break core.data.local.dao.
- Position
- Below the diagonal: features.accounts.data.local.dao uses a module listed above it, which is the healthy direction.
12→4 features.accounts.data.local.dao uses features.accounts.data.local.entity✕
- Connections
- 1 pair of types, where a type in features.accounts.data.local.dao uses a type in features.accounts.data.local.entity.
- The types involved
com.jxareas.xpensor.features.accounts.data.local.dao.AccountDao→com.jxareas.xpensor.features.accounts.data.local.entity.AccountEntity
- Direction
- features.accounts.data.local.dao uses features.accounts.data.local.entity, so a change to features.accounts.data.local.entity can break features.accounts.data.local.dao, while a change to features.accounts.data.local.dao can't break features.accounts.data.local.entity.
- Position
- Below the diagonal: features.accounts.data.local.dao uses a module listed above it, which is the healthy direction.
13→5 features.accounts.domain.repository uses features.accounts.domain.model✕
- Connections
- 1 pair of types, where a type in features.accounts.domain.repository uses a type in features.accounts.domain.model.
- The types involved
com.jxareas.xpensor.features.accounts.domain.repository.AccountRepository→com.jxareas.xpensor.features.accounts.domain.model.Account
- Direction
- features.accounts.domain.repository uses features.accounts.domain.model, so a change to features.accounts.domain.model can break features.accounts.domain.repository, while a change to features.accounts.domain.repository can't break features.accounts.domain.model.
- Position
- Below the diagonal: features.accounts.domain.repository uses a module listed above it, which is the healthy direction.
14→1 features.accounts.presentation.ui.adapter uses common.utils✕
- Connections
- 1 pair of types, where a type in features.accounts.presentation.ui.adapter uses a type in common.utils.
- The types involved
com.jxareas.xpensor.features.accounts.presentation.ui.adapter.AccountsViewHolder→com.jxareas.xpensor.common.utils.OnBindViewHolder
- Direction
- features.accounts.presentation.ui.adapter uses common.utils, so a change to common.utils can break features.accounts.presentation.ui.adapter, while a change to features.accounts.presentation.ui.adapter can't break common.utils.
- Position
- Below the diagonal: features.accounts.presentation.ui.adapter uses a module listed above it, which is the healthy direction.
14→3 features.accounts.presentation.ui.adapter uses core.data.local.preferences✕
- Connections
- 2 pairs of types, where a type in features.accounts.presentation.ui.adapter uses a type in core.data.local.preferences.
- The types involved
com.jxareas.xpensor.features.accounts.presentation.ui.adapter.AccountsListAdapter→com.jxareas.xpensor.core.data.local.preferences.UserPreferencescom.jxareas.xpensor.features.accounts.presentation.ui.adapter.AccountsViewHolder→com.jxareas.xpensor.core.data.local.preferences.UserPreferences
- Direction
- features.accounts.presentation.ui.adapter uses core.data.local.preferences, so a change to core.data.local.preferences can break features.accounts.presentation.ui.adapter, while a change to features.accounts.presentation.ui.adapter can't break core.data.local.preferences.
- Position
- Below the diagonal: features.accounts.presentation.ui.adapter uses a module listed above it, which is the healthy direction.
14→6 features.accounts.presentation.ui.adapter uses features.accounts.presentation.model✕
- Connections
- 2 pairs of types, where a type in features.accounts.presentation.ui.adapter uses a type in features.accounts.presentation.model.
- The types involved
com.jxareas.xpensor.features.accounts.presentation.ui.adapter.AccountDiffCallback→com.jxareas.xpensor.features.accounts.presentation.model.AccountUicom.jxareas.xpensor.features.accounts.presentation.ui.adapter.AccountsViewHolder→com.jxareas.xpensor.features.accounts.presentation.model.AccountUi
- Direction
- features.accounts.presentation.ui.adapter uses features.accounts.presentation.model, so a change to features.accounts.presentation.model can break features.accounts.presentation.ui.adapter, while a change to features.accounts.presentation.ui.adapter can't break features.accounts.presentation.model.
- Position
- Below the diagonal: features.accounts.presentation.ui.adapter uses a module listed above it, which is the healthy direction.
15→7 features.converter.data.remote.source.impl uses features.converter.data.remote.api✕
- Connections
- 1 pair of types, where a type in features.converter.data.remote.source.impl uses a type in features.converter.data.remote.api.
- The types involved
com.jxareas.xpensor.features.converter.data.remote.source.impl.FreeCurrencyApiRemoteDataSource→com.jxareas.xpensor.features.converter.data.remote.api.FreeCurrencyApi
- Direction
- features.converter.data.remote.source.impl uses features.converter.data.remote.api, so a change to features.converter.data.remote.api can break features.converter.data.remote.source.impl, while a change to features.converter.data.remote.source.impl can't break features.converter.data.remote.api.
- Position
- Below the diagonal: features.converter.data.remote.source.impl uses a module listed above it, which is the healthy direction.
16→1 features.converter.domain.repository uses common.utils✕
- Connections
- 1 pair of types, where a type in features.converter.domain.repository uses a type in common.utils.
- The types involved
com.jxareas.xpensor.features.converter.domain.repository.CurrencyRepository→com.jxareas.xpensor.common.utils.Resource
- Direction
- features.converter.domain.repository uses common.utils, so a change to common.utils can break features.converter.domain.repository, while a change to features.converter.domain.repository can't break common.utils.
- Position
- Below the diagonal: features.converter.domain.repository uses a module listed above it, which is the healthy direction.
16→8 features.converter.domain.repository uses features.converter.domain.model✕
- Connections
- 2 pairs of types, where a type in features.converter.domain.repository uses a type in features.converter.domain.model.
- The types involved
com.jxareas.xpensor.features.converter.domain.repository.CurrencyRepository→com.jxareas.xpensor.features.converter.domain.model.BaseCurrencycom.jxareas.xpensor.features.converter.domain.repository.CurrencyRepository→com.jxareas.xpensor.features.converter.domain.model.CurrencyComparison
- Direction
- features.converter.domain.repository uses features.converter.domain.model, so a change to features.converter.domain.model can break features.converter.domain.repository, while a change to features.converter.domain.repository can't break features.converter.domain.model.
- Position
- Below the diagonal: features.converter.domain.repository uses a module listed above it, which is the healthy direction.
17→4 features.transactions.data.local.views uses features.accounts.data.local.entity✕
- Connections
- 1 pair of types, where a type in features.transactions.data.local.views uses a type in features.accounts.data.local.entity.
- The types involved
com.jxareas.xpensor.features.transactions.data.local.views.TransactionWithCategoryAndAccount→com.jxareas.xpensor.features.accounts.data.local.entity.AccountEntity
- Direction
- features.transactions.data.local.views uses features.accounts.data.local.entity, so a change to features.accounts.data.local.entity can break features.transactions.data.local.views, while a change to features.transactions.data.local.views can't break features.accounts.data.local.entity.
- Position
- Below the diagonal: features.transactions.data.local.views uses a module listed above it, which is the healthy direction.
17→9 features.transactions.data.local.views uses features.transactions.data.local.entity✕
- Connections
- 3 pairs of types, where a type in features.transactions.data.local.views uses a type in features.transactions.data.local.entity.
- The types involved
com.jxareas.xpensor.features.transactions.data.local.views.TransactionAmountByCategory→com.jxareas.xpensor.features.transactions.data.local.entity.CategoryEntitycom.jxareas.xpensor.features.transactions.data.local.views.TransactionWithCategoryAndAccount→com.jxareas.xpensor.features.transactions.data.local.entity.CategoryEntitycom.jxareas.xpensor.features.transactions.data.local.views.TransactionWithCategoryAndAccount→com.jxareas.xpensor.features.transactions.data.local.entity.TransactionEntity
- Direction
- features.transactions.data.local.views uses features.transactions.data.local.entity, so a change to features.transactions.data.local.entity can break features.transactions.data.local.views, while a change to features.transactions.data.local.views can't break features.transactions.data.local.entity.
- Position
- Below the diagonal: features.transactions.data.local.views uses a module listed above it, which is the healthy direction.
18→5 features.transactions.domain.model uses features.accounts.domain.model✕
- Connections
- 1 pair of types, where a type in features.transactions.domain.model uses a type in features.accounts.domain.model.
- The types involved
com.jxareas.xpensor.features.transactions.domain.model.TransactionDetails→com.jxareas.xpensor.features.accounts.domain.model.Account
- Direction
- features.transactions.domain.model uses features.accounts.domain.model, so a change to features.accounts.domain.model can break features.transactions.domain.model, while a change to features.transactions.domain.model can't break features.accounts.domain.model.
- Position
- Below the diagonal: features.transactions.domain.model uses a module listed above it, which is the healthy direction.
19→1 features.transactions.presentation.ui.actions.category.adapter uses common.utils✕
- Connections
- 1 pair of types, where a type in features.transactions.presentation.ui.actions.category.adapter uses a type in common.utils.
- The types involved
com.jxareas.xpensor.features.transactions.presentation.ui.actions.category.adapter.CategoryViewHolder→com.jxareas.xpensor.common.utils.OnBindViewHolder
- Direction
- features.transactions.presentation.ui.actions.category.adapter uses common.utils, so a change to common.utils can break features.transactions.presentation.ui.actions.category.adapter, while a change to features.transactions.presentation.ui.actions.category.adapter can't break common.utils.
- Position
- Below the diagonal: features.transactions.presentation.ui.actions.category.adapter uses a module listed above it, which is the healthy direction.
19→3 features.transactions.presentation.ui.actions.category.adapter uses core.data.local.preferences✕
- Connections
- 2 pairs of types, where a type in features.transactions.presentation.ui.actions.category.adapter uses a type in core.data.local.preferences.
- The types involved
com.jxareas.xpensor.features.transactions.presentation.ui.actions.category.adapter.CategoryAdapter→com.jxareas.xpensor.core.data.local.preferences.UserPreferencescom.jxareas.xpensor.features.transactions.presentation.ui.actions.category.adapter.CategoryViewHolder→com.jxareas.xpensor.core.data.local.preferences.UserPreferences
- Direction
- features.transactions.presentation.ui.actions.category.adapter uses core.data.local.preferences, so a change to core.data.local.preferences can break features.transactions.presentation.ui.actions.category.adapter, while a change to features.transactions.presentation.ui.actions.category.adapter can't break core.data.local.preferences.
- Position
- Below the diagonal: features.transactions.presentation.ui.actions.category.adapter uses a module listed above it, which is the healthy direction.
19→10 features.transactions.presentation.ui.actions.category.adapter uses features.transactions.presentation.model✕
- Connections
- 2 pairs of types, where a type in features.transactions.presentation.ui.actions.category.adapter uses a type in features.transactions.presentation.model.
- The types involved
com.jxareas.xpensor.features.transactions.presentation.ui.actions.category.adapter.CategoryDiffCallback→com.jxareas.xpensor.features.transactions.presentation.model.CategoryWithAmountUicom.jxareas.xpensor.features.transactions.presentation.ui.actions.category.adapter.CategoryViewHolder→com.jxareas.xpensor.features.transactions.presentation.model.CategoryWithAmountUi
- Direction
- features.transactions.presentation.ui.actions.category.adapter uses features.transactions.presentation.model, so a change to features.transactions.presentation.model can break features.transactions.presentation.ui.actions.category.adapter, while a change to features.transactions.presentation.ui.actions.category.adapter can't break features.transactions.presentation.model.
- Position
- Below the diagonal: features.transactions.presentation.ui.actions.category.adapter uses a module listed above it, which is the healthy direction.
20→4 features.accounts.data.local.source uses features.accounts.data.local.entity✕
- Connections
- 1 pair of types, where a type in features.accounts.data.local.source uses a type in features.accounts.data.local.entity.
- The types involved
com.jxareas.xpensor.features.accounts.data.local.source.AccountLocalDataSource→com.jxareas.xpensor.features.accounts.data.local.entity.AccountEntity
- Direction
- features.accounts.data.local.source uses features.accounts.data.local.entity, so a change to features.accounts.data.local.entity can break features.accounts.data.local.source, while a change to features.accounts.data.local.source can't break features.accounts.data.local.entity.
- Position
- Below the diagonal: features.accounts.data.local.source uses a module listed above it, which is the healthy direction.
20→11 features.accounts.data.local.source uses core.data.local.source✕
- Connections
- 1 pair of types, where a type in features.accounts.data.local.source uses a type in core.data.local.source.
- The types involved
com.jxareas.xpensor.features.accounts.data.local.source.AccountLocalDataSource→com.jxareas.xpensor.core.data.local.source.LocalDataSource
- Direction
- features.accounts.data.local.source uses core.data.local.source, so a change to core.data.local.source can break features.accounts.data.local.source, while a change to features.accounts.data.local.source can't break core.data.local.source.
- Position
- Below the diagonal: features.accounts.data.local.source uses a module listed above it, which is the healthy direction.
21→5 features.accounts.domain.usecase uses features.accounts.domain.model✕
- Connections
- 4 pairs of types, where a type in features.accounts.domain.usecase uses a type in features.accounts.domain.model.
- The types involved
com.jxareas.xpensor.features.accounts.domain.usecase.AddAccountUseCase→com.jxareas.xpensor.features.accounts.domain.model.Accountcom.jxareas.xpensor.features.accounts.domain.usecase.DeleteAccountUseCase→com.jxareas.xpensor.features.accounts.domain.model.Accountcom.jxareas.xpensor.features.accounts.domain.usecase.GetAccountsUseCase→com.jxareas.xpensor.features.accounts.domain.model.Accountcom.jxareas.xpensor.features.accounts.domain.usecase.UpdateAccountUseCase→com.jxareas.xpensor.features.accounts.domain.model.Account
- Direction
- features.accounts.domain.usecase uses features.accounts.domain.model, so a change to features.accounts.domain.model can break features.accounts.domain.usecase, while a change to features.accounts.domain.usecase can't break features.accounts.domain.model.
- Position
- Below the diagonal: features.accounts.domain.usecase uses a module listed above it, which is the healthy direction.
21→13 features.accounts.domain.usecase uses features.accounts.domain.repository✕
- Connections
- 5 pairs of types, where a type in features.accounts.domain.usecase uses a type in features.accounts.domain.repository.
- The types involved
com.jxareas.xpensor.features.accounts.domain.usecase.AddAccountUseCase→com.jxareas.xpensor.features.accounts.domain.repository.AccountRepositorycom.jxareas.xpensor.features.accounts.domain.usecase.DeleteAccountUseCase→com.jxareas.xpensor.features.accounts.domain.repository.AccountRepositorycom.jxareas.xpensor.features.accounts.domain.usecase.GetAccountsUseCase→com.jxareas.xpensor.features.accounts.domain.repository.AccountRepositorycom.jxareas.xpensor.features.accounts.domain.usecase.GetTotalAccountsAmountUseCase→com.jxareas.xpensor.features.accounts.domain.repository.AccountRepositorycom.jxareas.xpensor.features.accounts.domain.usecase.UpdateAccountUseCase→com.jxareas.xpensor.features.accounts.domain.repository.AccountRepository
- Direction
- features.accounts.domain.usecase uses features.accounts.domain.repository, so a change to features.accounts.domain.repository can break features.accounts.domain.usecase, while a change to features.accounts.domain.usecase can't break features.accounts.domain.repository.
- Position
- Below the diagonal: features.accounts.domain.usecase uses a module listed above it, which is the healthy direction.
22→1 features.converter.data.repository uses common.utils✕
- Connections
- 1 pair of types, where a type in features.converter.data.repository uses a type in common.utils.
- The types involved
com.jxareas.xpensor.features.converter.data.repository.DefaultCurrencyRepository→com.jxareas.xpensor.common.utils.Resource
- Direction
- features.converter.data.repository uses common.utils, so a change to common.utils can break features.converter.data.repository, while a change to features.converter.data.repository can't break common.utils.
- Position
- Below the diagonal: features.converter.data.repository uses a module listed above it, which is the healthy direction.
22→7 features.converter.data.repository uses features.converter.data.remote.api✕
- Connections
- 1 pair of types, where a type in features.converter.data.repository uses a type in features.converter.data.remote.api.
- The types involved
com.jxareas.xpensor.features.converter.data.repository.DefaultCurrencyRepository→com.jxareas.xpensor.features.converter.data.remote.api.FreeCurrencyApi
- Direction
- features.converter.data.repository uses features.converter.data.remote.api, so a change to features.converter.data.remote.api can break features.converter.data.repository, while a change to features.converter.data.repository can't break features.converter.data.remote.api.
- Position
- Below the diagonal: features.converter.data.repository uses a module listed above it, which is the healthy direction.
22→8 features.converter.data.repository uses features.converter.domain.model✕
- Connections
- 2 pairs of types, where a type in features.converter.data.repository uses a type in features.converter.domain.model.
- The types involved
com.jxareas.xpensor.features.converter.data.repository.DefaultCurrencyRepository→com.jxareas.xpensor.features.converter.domain.model.BaseCurrencycom.jxareas.xpensor.features.converter.data.repository.DefaultCurrencyRepository→com.jxareas.xpensor.features.converter.domain.model.CurrencyComparison
- Direction
- features.converter.data.repository uses features.converter.domain.model, so a change to features.converter.domain.model can break features.converter.data.repository, while a change to features.converter.data.repository can't break features.converter.domain.model.
- Position
- Below the diagonal: features.converter.data.repository uses a module listed above it, which is the healthy direction.
22→16 features.converter.data.repository uses features.converter.domain.repository✕
- Connections
- 1 pair of types, where a type in features.converter.data.repository uses a type in features.converter.domain.repository.
- The types involved
com.jxareas.xpensor.features.converter.data.repository.DefaultCurrencyRepository→com.jxareas.xpensor.features.converter.domain.repository.CurrencyRepository
- Direction
- features.converter.data.repository uses features.converter.domain.repository, so a change to features.converter.domain.repository can break features.converter.data.repository, while a change to features.converter.data.repository can't break features.converter.domain.repository.
- Position
- Below the diagonal: features.converter.data.repository uses a module listed above it, which is the healthy direction.
23→2 features.transactions.data.local.dao uses core.data.local.dao✕
- Connections
- 2 pairs of types, where a type in features.transactions.data.local.dao uses a type in core.data.local.dao.
- The types involved
com.jxareas.xpensor.features.transactions.data.local.dao.CategoryDao→com.jxareas.xpensor.core.data.local.dao.RoomDaocom.jxareas.xpensor.features.transactions.data.local.dao.TransactionDao→com.jxareas.xpensor.core.data.local.dao.RoomDao
- Direction
- features.transactions.data.local.dao uses core.data.local.dao, so a change to core.data.local.dao can break features.transactions.data.local.dao, while a change to features.transactions.data.local.dao can't break core.data.local.dao.
- Position
- Below the diagonal: features.transactions.data.local.dao uses a module listed above it, which is the healthy direction.
23→9 features.transactions.data.local.dao uses features.transactions.data.local.entity✕
- Connections
- 2 pairs of types, where a type in features.transactions.data.local.dao uses a type in features.transactions.data.local.entity.
- The types involved
com.jxareas.xpensor.features.transactions.data.local.dao.CategoryDao→com.jxareas.xpensor.features.transactions.data.local.entity.CategoryEntitycom.jxareas.xpensor.features.transactions.data.local.dao.TransactionDao→com.jxareas.xpensor.features.transactions.data.local.entity.TransactionEntity
- Direction
- features.transactions.data.local.dao uses features.transactions.data.local.entity, so a change to features.transactions.data.local.entity can break features.transactions.data.local.dao, while a change to features.transactions.data.local.dao can't break features.transactions.data.local.entity.
- Position
- Below the diagonal: features.transactions.data.local.dao uses a module listed above it, which is the healthy direction.
23→17 features.transactions.data.local.dao uses features.transactions.data.local.views✕
- Connections
- 3 pairs of types, where a type in features.transactions.data.local.dao uses a type in features.transactions.data.local.views.
- The types involved
com.jxareas.xpensor.features.transactions.data.local.dao.CategoryDao→com.jxareas.xpensor.features.transactions.data.local.views.CategoryViewcom.jxareas.xpensor.features.transactions.data.local.dao.TransactionDao→com.jxareas.xpensor.features.transactions.data.local.views.TransactionViewcom.jxareas.xpensor.features.transactions.data.local.dao.TransactionDao→com.jxareas.xpensor.features.transactions.data.local.views.TransactionsByDayView
- Direction
- features.transactions.data.local.dao uses features.transactions.data.local.views, so a change to features.transactions.data.local.views can break features.transactions.data.local.dao, while a change to features.transactions.data.local.dao can't break features.transactions.data.local.views.
- Position
- Below the diagonal: features.transactions.data.local.dao uses a module listed above it, which is the healthy direction.
24→11 features.transactions.data.local.source uses core.data.local.source✕
- Connections
- 2 pairs of types, where a type in features.transactions.data.local.source uses a type in core.data.local.source.
- The types involved
com.jxareas.xpensor.features.transactions.data.local.source.CategoryLocalDataSource→com.jxareas.xpensor.core.data.local.source.LocalDataSourcecom.jxareas.xpensor.features.transactions.data.local.source.TransactionLocalDataSource→com.jxareas.xpensor.core.data.local.source.LocalDataSource
- Direction
- features.transactions.data.local.source uses core.data.local.source, so a change to core.data.local.source can break features.transactions.data.local.source, while a change to features.transactions.data.local.source can't break core.data.local.source.
- Position
- Below the diagonal: features.transactions.data.local.source uses a module listed above it, which is the healthy direction.
24→17 features.transactions.data.local.source uses features.transactions.data.local.views✕
- Connections
- 3 pairs of types, where a type in features.transactions.data.local.source uses a type in features.transactions.data.local.views.
- The types involved
com.jxareas.xpensor.features.transactions.data.local.source.CategoryLocalDataSource→com.jxareas.xpensor.features.transactions.data.local.views.TransactionAmountByCategorycom.jxareas.xpensor.features.transactions.data.local.source.TransactionLocalDataSource→com.jxareas.xpensor.features.transactions.data.local.views.TransactionWithCategoryAndAccountcom.jxareas.xpensor.features.transactions.data.local.source.TransactionLocalDataSource→com.jxareas.xpensor.features.transactions.data.local.views.TransactionsByDayView
- Direction
- features.transactions.data.local.source uses features.transactions.data.local.views, so a change to features.transactions.data.local.views can break features.transactions.data.local.source, while a change to features.transactions.data.local.source can't break features.transactions.data.local.views.
- Position
- Below the diagonal: features.transactions.data.local.source uses a module listed above it, which is the healthy direction.
25→18 features.transactions.domain.repository uses features.transactions.domain.model✕
- Connections
- 4 pairs of types, where a type in features.transactions.domain.repository uses a type in features.transactions.domain.model.
- The types involved
com.jxareas.xpensor.features.transactions.domain.repository.CategoryRepository→com.jxareas.xpensor.features.transactions.domain.model.CategoryWithDetailscom.jxareas.xpensor.features.transactions.domain.repository.TransactionRepository→com.jxareas.xpensor.features.transactions.domain.model.Transactioncom.jxareas.xpensor.features.transactions.domain.repository.TransactionRepository→com.jxareas.xpensor.features.transactions.domain.model.TransactionByDaycom.jxareas.xpensor.features.transactions.domain.repository.TransactionRepository→com.jxareas.xpensor.features.transactions.domain.model.TransactionDetails
- Direction
- features.transactions.domain.repository uses features.transactions.domain.model, so a change to features.transactions.domain.model can break features.transactions.domain.repository, while a change to features.transactions.domain.repository can't break features.transactions.domain.model.
- Position
- Below the diagonal: features.transactions.domain.repository uses a module listed above it, which is the healthy direction.
26→12 core.data.local.database uses features.accounts.data.local.dao✕
- Connections
- 1 pair of types, where a type in core.data.local.database uses a type in features.accounts.data.local.dao.
- The types involved
com.jxareas.xpensor.core.data.local.database.XpensorDatabase→com.jxareas.xpensor.features.accounts.data.local.dao.AccountDao
- Direction
- core.data.local.database uses features.accounts.data.local.dao, so a change to features.accounts.data.local.dao can break core.data.local.database, while a change to core.data.local.database can't break features.accounts.data.local.dao.
- Position
- Below the diagonal: core.data.local.database uses a module listed above it, which is the healthy direction.
26→23 core.data.local.database uses features.transactions.data.local.dao✕
- Connections
- 2 pairs of types, where a type in core.data.local.database uses a type in features.transactions.data.local.dao.
- The types involved
com.jxareas.xpensor.core.data.local.database.XpensorDatabase→com.jxareas.xpensor.features.transactions.data.local.dao.CategoryDaocom.jxareas.xpensor.core.data.local.database.XpensorDatabase→com.jxareas.xpensor.features.transactions.data.local.dao.TransactionDao
- Direction
- core.data.local.database uses features.transactions.data.local.dao, so a change to features.transactions.data.local.dao can break core.data.local.database, while a change to core.data.local.database can't break features.transactions.data.local.dao.
- Position
- Below the diagonal: core.data.local.database uses a module listed above it, which is the healthy direction.
27→3 core.presentation uses core.data.local.preferences✕
- Connections
- 1 pair of types, where a type in core.presentation uses a type in core.data.local.preferences.
- The types involved
com.jxareas.xpensor.core.presentation.MainViewModel→com.jxareas.xpensor.core.data.local.preferences.UserPreferences
- Direction
- core.presentation uses core.data.local.preferences, so a change to core.data.local.preferences can break core.presentation, while a change to core.presentation can't break core.data.local.preferences.
- Position
- Below the diagonal: core.presentation uses a module listed above it, which is the healthy direction.
27→6 core.presentation uses features.accounts.presentation.model✕
- Connections
- 1 pair of types, where a type in core.presentation uses a type in features.accounts.presentation.model.
- The types involved
com.jxareas.xpensor.core.presentation.MainViewModel→com.jxareas.xpensor.features.accounts.presentation.model.AccountUi
- Direction
- core.presentation uses features.accounts.presentation.model, so a change to features.accounts.presentation.model can break core.presentation, while a change to core.presentation can't break features.accounts.presentation.model.
- Position
- Below the diagonal: core.presentation uses a module listed above it, which is the healthy direction.
27→21 core.presentation uses features.accounts.domain.usecase✕
- Connections
- 1 pair of types, where a type in core.presentation uses a type in features.accounts.domain.usecase.
- The types involved
com.jxareas.xpensor.core.presentation.MainViewModel→com.jxareas.xpensor.features.accounts.domain.usecase.GetAccountsUseCase
- Direction
- core.presentation uses features.accounts.domain.usecase, so a change to features.accounts.domain.usecase can break core.presentation, while a change to core.presentation can't break features.accounts.domain.usecase.
- Position
- Below the diagonal: core.presentation uses a module listed above it, which is the healthy direction.
28→4 features.accounts.data.local.source.impl uses features.accounts.data.local.entity✕
- Connections
- 1 pair of types, where a type in features.accounts.data.local.source.impl uses a type in features.accounts.data.local.entity.
- The types involved
com.jxareas.xpensor.features.accounts.data.local.source.impl.AccountRoomLocalDataSource→com.jxareas.xpensor.features.accounts.data.local.entity.AccountEntity
- Direction
- features.accounts.data.local.source.impl uses features.accounts.data.local.entity, so a change to features.accounts.data.local.entity can break features.accounts.data.local.source.impl, while a change to features.accounts.data.local.source.impl can't break features.accounts.data.local.entity.
- Position
- Below the diagonal: features.accounts.data.local.source.impl uses a module listed above it, which is the healthy direction.
28→11 features.accounts.data.local.source.impl uses core.data.local.source✕
- Connections
- 1 pair of types, where a type in features.accounts.data.local.source.impl uses a type in core.data.local.source.
- The types involved
com.jxareas.xpensor.features.accounts.data.local.source.impl.AccountRoomLocalDataSource→com.jxareas.xpensor.core.data.local.source.RoomLocalDataSource
- Direction
- features.accounts.data.local.source.impl uses core.data.local.source, so a change to core.data.local.source can break features.accounts.data.local.source.impl, while a change to features.accounts.data.local.source.impl can't break core.data.local.source.
- Position
- Below the diagonal: features.accounts.data.local.source.impl uses a module listed above it, which is the healthy direction.
28→12 features.accounts.data.local.source.impl uses features.accounts.data.local.dao✕
- Connections
- 1 pair of types, where a type in features.accounts.data.local.source.impl uses a type in features.accounts.data.local.dao.
- The types involved
com.jxareas.xpensor.features.accounts.data.local.source.impl.AccountRoomLocalDataSource→com.jxareas.xpensor.features.accounts.data.local.dao.AccountDao
- Direction
- features.accounts.data.local.source.impl uses features.accounts.data.local.dao, so a change to features.accounts.data.local.dao can break features.accounts.data.local.source.impl, while a change to features.accounts.data.local.source.impl can't break features.accounts.data.local.dao.
- Position
- Below the diagonal: features.accounts.data.local.source.impl uses a module listed above it, which is the healthy direction.
28→20 features.accounts.data.local.source.impl uses features.accounts.data.local.source✕
- Connections
- 1 pair of types, where a type in features.accounts.data.local.source.impl uses a type in features.accounts.data.local.source.
- The types involved
com.jxareas.xpensor.features.accounts.data.local.source.impl.AccountRoomLocalDataSource→com.jxareas.xpensor.features.accounts.data.local.source.AccountLocalDataSource
- Direction
- features.accounts.data.local.source.impl uses features.accounts.data.local.source, so a change to features.accounts.data.local.source can break features.accounts.data.local.source.impl, while a change to features.accounts.data.local.source.impl can't break features.accounts.data.local.source.
- Position
- Below the diagonal: features.accounts.data.local.source.impl uses a module listed above it, which is the healthy direction.
29→5 features.accounts.data.repository uses features.accounts.domain.model✕
- Connections
- 1 pair of types, where a type in features.accounts.data.repository uses a type in features.accounts.domain.model.
- The types involved
com.jxareas.xpensor.features.accounts.data.repository.DefaultAccountRepository→com.jxareas.xpensor.features.accounts.domain.model.Account
- Direction
- features.accounts.data.repository uses features.accounts.domain.model, so a change to features.accounts.domain.model can break features.accounts.data.repository, while a change to features.accounts.data.repository can't break features.accounts.domain.model.
- Position
- Below the diagonal: features.accounts.data.repository uses a module listed above it, which is the healthy direction.
29→13 features.accounts.data.repository uses features.accounts.domain.repository✕
- Connections
- 1 pair of types, where a type in features.accounts.data.repository uses a type in features.accounts.domain.repository.
- The types involved
com.jxareas.xpensor.features.accounts.data.repository.DefaultAccountRepository→com.jxareas.xpensor.features.accounts.domain.repository.AccountRepository
- Direction
- features.accounts.data.repository uses features.accounts.domain.repository, so a change to features.accounts.domain.repository can break features.accounts.data.repository, while a change to features.accounts.data.repository can't break features.accounts.domain.repository.
- Position
- Below the diagonal: features.accounts.data.repository uses a module listed above it, which is the healthy direction.
29→20 features.accounts.data.repository uses features.accounts.data.local.source✕
- Connections
- 1 pair of types, where a type in features.accounts.data.repository uses a type in features.accounts.data.local.source.
- The types involved
com.jxareas.xpensor.features.accounts.data.repository.DefaultAccountRepository→com.jxareas.xpensor.features.accounts.data.local.source.AccountLocalDataSource
- Direction
- features.accounts.data.repository uses features.accounts.data.local.source, so a change to features.accounts.data.local.source can break features.accounts.data.repository, while a change to features.accounts.data.repository can't break features.accounts.data.local.source.
- Position
- Below the diagonal: features.accounts.data.repository uses a module listed above it, which is the healthy direction.
30→3 features.accounts.presentation.ui uses core.data.local.preferences✕
- Connections
- 1 pair of types, where a type in features.accounts.presentation.ui uses a type in core.data.local.preferences.
- The types involved
com.jxareas.xpensor.features.accounts.presentation.ui.AccountsViewModel→com.jxareas.xpensor.core.data.local.preferences.UserPreferences
- Direction
- features.accounts.presentation.ui uses core.data.local.preferences, so a change to core.data.local.preferences can break features.accounts.presentation.ui, while a change to features.accounts.presentation.ui can't break core.data.local.preferences.
- Position
- Below the diagonal: features.accounts.presentation.ui uses a module listed above it, which is the healthy direction.
30→6 features.accounts.presentation.ui uses features.accounts.presentation.model✕
- Connections
- 3 pairs of types, where a type in features.accounts.presentation.ui uses a type in features.accounts.presentation.model.
- The types involved
com.jxareas.xpensor.features.accounts.presentation.ui.AccountsFragment→com.jxareas.xpensor.features.accounts.presentation.model.TotalAccountsAmountUicom.jxareas.xpensor.features.accounts.presentation.ui.AccountsViewModel→com.jxareas.xpensor.features.accounts.presentation.model.AccountUicom.jxareas.xpensor.features.accounts.presentation.ui.AccountsViewModel→com.jxareas.xpensor.features.accounts.presentation.model.TotalAccountsAmountUi
- Direction
- features.accounts.presentation.ui uses features.accounts.presentation.model, so a change to features.accounts.presentation.model can break features.accounts.presentation.ui, while a change to features.accounts.presentation.ui can't break features.accounts.presentation.model.
- Position
- Below the diagonal: features.accounts.presentation.ui uses a module listed above it, which is the healthy direction.
30→14 features.accounts.presentation.ui uses features.accounts.presentation.ui.adapter✕
- Connections
- 1 pair of types, where a type in features.accounts.presentation.ui uses a type in features.accounts.presentation.ui.adapter.
- The types involved
com.jxareas.xpensor.features.accounts.presentation.ui.AccountsFragment→com.jxareas.xpensor.features.accounts.presentation.ui.adapter.AccountsListAdapter
- Direction
- features.accounts.presentation.ui uses features.accounts.presentation.ui.adapter, so a change to features.accounts.presentation.ui.adapter can break features.accounts.presentation.ui, while a change to features.accounts.presentation.ui can't break features.accounts.presentation.ui.adapter.
- Position
- Below the diagonal: features.accounts.presentation.ui uses a module listed above it, which is the healthy direction.
30→21 features.accounts.presentation.ui uses features.accounts.domain.usecase✕
- Connections
- 2 pairs of types, where a type in features.accounts.presentation.ui uses a type in features.accounts.domain.usecase.
- The types involved
com.jxareas.xpensor.features.accounts.presentation.ui.AccountsViewModel→com.jxareas.xpensor.features.accounts.domain.usecase.GetAccountsUseCasecom.jxareas.xpensor.features.accounts.presentation.ui.AccountsViewModel→com.jxareas.xpensor.features.accounts.domain.usecase.GetTotalAccountsAmountUseCase
- Direction
- features.accounts.presentation.ui uses features.accounts.domain.usecase, so a change to features.accounts.domain.usecase can break features.accounts.presentation.ui, while a change to features.accounts.presentation.ui can't break features.accounts.domain.usecase.
- Position
- Below the diagonal: features.accounts.presentation.ui uses a module listed above it, which is the healthy direction.
31→11 features.transactions.data.local.source.impl uses core.data.local.source✕
- Connections
- 2 pairs of types, where a type in features.transactions.data.local.source.impl uses a type in core.data.local.source.
- The types involved
com.jxareas.xpensor.features.transactions.data.local.source.impl.CategoryRoomLocalDataSource→com.jxareas.xpensor.core.data.local.source.RoomLocalDataSourcecom.jxareas.xpensor.features.transactions.data.local.source.impl.TransactionRoomLocalDataSource→com.jxareas.xpensor.core.data.local.source.RoomLocalDataSource
- Direction
- features.transactions.data.local.source.impl uses core.data.local.source, so a change to core.data.local.source can break features.transactions.data.local.source.impl, while a change to features.transactions.data.local.source.impl can't break core.data.local.source.
- Position
- Below the diagonal: features.transactions.data.local.source.impl uses a module listed above it, which is the healthy direction.
31→17 features.transactions.data.local.source.impl uses features.transactions.data.local.views✕
- Connections
- 3 pairs of types, where a type in features.transactions.data.local.source.impl uses a type in features.transactions.data.local.views.
- The types involved
com.jxareas.xpensor.features.transactions.data.local.source.impl.CategoryRoomLocalDataSource→com.jxareas.xpensor.features.transactions.data.local.views.TransactionAmountByCategorycom.jxareas.xpensor.features.transactions.data.local.source.impl.TransactionRoomLocalDataSource→com.jxareas.xpensor.features.transactions.data.local.views.TransactionWithCategoryAndAccountcom.jxareas.xpensor.features.transactions.data.local.source.impl.TransactionRoomLocalDataSource→com.jxareas.xpensor.features.transactions.data.local.views.TransactionsByDayView
- Direction
- features.transactions.data.local.source.impl uses features.transactions.data.local.views, so a change to features.transactions.data.local.views can break features.transactions.data.local.source.impl, while a change to features.transactions.data.local.source.impl can't break features.transactions.data.local.views.
- Position
- Below the diagonal: features.transactions.data.local.source.impl uses a module listed above it, which is the healthy direction.
31→23 features.transactions.data.local.source.impl uses features.transactions.data.local.dao✕
- Connections
- 2 pairs of types, where a type in features.transactions.data.local.source.impl uses a type in features.transactions.data.local.dao.
- The types involved
com.jxareas.xpensor.features.transactions.data.local.source.impl.CategoryRoomLocalDataSource→com.jxareas.xpensor.features.transactions.data.local.dao.CategoryDaocom.jxareas.xpensor.features.transactions.data.local.source.impl.TransactionRoomLocalDataSource→com.jxareas.xpensor.features.transactions.data.local.dao.TransactionDao
- Direction
- features.transactions.data.local.source.impl uses features.transactions.data.local.dao, so a change to features.transactions.data.local.dao can break features.transactions.data.local.source.impl, while a change to features.transactions.data.local.source.impl can't break features.transactions.data.local.dao.
- Position
- Below the diagonal: features.transactions.data.local.source.impl uses a module listed above it, which is the healthy direction.
31→24 features.transactions.data.local.source.impl uses features.transactions.data.local.source✕
- Connections
- 2 pairs of types, where a type in features.transactions.data.local.source.impl uses a type in features.transactions.data.local.source.
- The types involved
com.jxareas.xpensor.features.transactions.data.local.source.impl.CategoryRoomLocalDataSource→com.jxareas.xpensor.features.transactions.data.local.source.CategoryLocalDataSourcecom.jxareas.xpensor.features.transactions.data.local.source.impl.TransactionRoomLocalDataSource→com.jxareas.xpensor.features.transactions.data.local.source.TransactionLocalDataSource
- Direction
- features.transactions.data.local.source.impl uses features.transactions.data.local.source, so a change to features.transactions.data.local.source can break features.transactions.data.local.source.impl, while a change to features.transactions.data.local.source.impl can't break features.transactions.data.local.source.
- Position
- Below the diagonal: features.transactions.data.local.source.impl uses a module listed above it, which is the healthy direction.
32→18 features.transactions.data.repository uses features.transactions.domain.model✕
- Connections
- 4 pairs of types, where a type in features.transactions.data.repository uses a type in features.transactions.domain.model.
- The types involved
com.jxareas.xpensor.features.transactions.data.repository.DefaultCategoryRepository→com.jxareas.xpensor.features.transactions.domain.model.CategoryWithDetailscom.jxareas.xpensor.features.transactions.data.repository.DefaultTransactionRepository→com.jxareas.xpensor.features.transactions.domain.model.Transactioncom.jxareas.xpensor.features.transactions.data.repository.DefaultTransactionRepository→com.jxareas.xpensor.features.transactions.domain.model.TransactionByDaycom.jxareas.xpensor.features.transactions.data.repository.DefaultTransactionRepository→com.jxareas.xpensor.features.transactions.domain.model.TransactionDetails
- Direction
- features.transactions.data.repository uses features.transactions.domain.model, so a change to features.transactions.domain.model can break features.transactions.data.repository, while a change to features.transactions.data.repository can't break features.transactions.domain.model.
- Position
- Below the diagonal: features.transactions.data.repository uses a module listed above it, which is the healthy direction.
32→24 features.transactions.data.repository uses features.transactions.data.local.source✕
- Connections
- 2 pairs of types, where a type in features.transactions.data.repository uses a type in features.transactions.data.local.source.
- The types involved
com.jxareas.xpensor.features.transactions.data.repository.DefaultCategoryRepository→com.jxareas.xpensor.features.transactions.data.local.source.CategoryLocalDataSourcecom.jxareas.xpensor.features.transactions.data.repository.DefaultTransactionRepository→com.jxareas.xpensor.features.transactions.data.local.source.TransactionLocalDataSource
- Direction
- features.transactions.data.repository uses features.transactions.data.local.source, so a change to features.transactions.data.local.source can break features.transactions.data.repository, while a change to features.transactions.data.repository can't break features.transactions.data.local.source.
- Position
- Below the diagonal: features.transactions.data.repository uses a module listed above it, which is the healthy direction.
32→25 features.transactions.data.repository uses features.transactions.domain.repository✕
- Connections
- 2 pairs of types, where a type in features.transactions.data.repository uses a type in features.transactions.domain.repository.
- The types involved
com.jxareas.xpensor.features.transactions.data.repository.DefaultCategoryRepository→com.jxareas.xpensor.features.transactions.domain.repository.CategoryRepositorycom.jxareas.xpensor.features.transactions.data.repository.DefaultTransactionRepository→com.jxareas.xpensor.features.transactions.domain.repository.TransactionRepository
- Direction
- features.transactions.data.repository uses features.transactions.domain.repository, so a change to features.transactions.domain.repository can break features.transactions.data.repository, while a change to features.transactions.data.repository can't break features.transactions.domain.repository.
- Position
- Below the diagonal: features.transactions.data.repository uses a module listed above it, which is the healthy direction.
33→5 features.transactions.domain.usecase uses features.accounts.domain.model✕
- Connections
- 3 pairs of types, where a type in features.transactions.domain.usecase uses a type in features.accounts.domain.model.
- The types involved
com.jxareas.xpensor.features.transactions.domain.usecase.GetCategoriesUseCase→com.jxareas.xpensor.features.accounts.domain.model.Accountcom.jxareas.xpensor.features.transactions.domain.usecase.GetTransactionsUseCase→com.jxareas.xpensor.features.accounts.domain.model.Accountcom.jxareas.xpensor.features.transactions.domain.usecase.GetTransactionsWithDayUseCase→com.jxareas.xpensor.features.accounts.domain.model.Account
- Direction
- features.transactions.domain.usecase uses features.accounts.domain.model, so a change to features.accounts.domain.model can break features.transactions.domain.usecase, while a change to features.transactions.domain.usecase can't break features.accounts.domain.model.
- Position
- Below the diagonal: features.transactions.domain.usecase uses a module listed above it, which is the healthy direction.
33→13 features.transactions.domain.usecase uses features.accounts.domain.repository✕
- Connections
- 3 pairs of types, where a type in features.transactions.domain.usecase uses a type in features.accounts.domain.repository.
- The types involved
com.jxareas.xpensor.features.transactions.domain.usecase.AddTransactionUseCase→com.jxareas.xpensor.features.accounts.domain.repository.AccountRepositorycom.jxareas.xpensor.features.transactions.domain.usecase.DeleteTransactionUseCase→com.jxareas.xpensor.features.accounts.domain.repository.AccountRepositorycom.jxareas.xpensor.features.transactions.domain.usecase.ValidateTransactionUseCase→com.jxareas.xpensor.features.accounts.domain.repository.AccountRepository
- Direction
- features.transactions.domain.usecase uses features.accounts.domain.repository, so a change to features.accounts.domain.repository can break features.transactions.domain.usecase, while a change to features.transactions.domain.usecase can't break features.accounts.domain.repository.
- Position
- Below the diagonal: features.transactions.domain.usecase uses a module listed above it, which is the healthy direction.
33→18 features.transactions.domain.usecase uses features.transactions.domain.model✕
- Connections
- 7 pairs of types, where a type in features.transactions.domain.usecase uses a type in features.transactions.domain.model.
- The types involved
com.jxareas.xpensor.features.transactions.domain.usecase.AddTransactionUseCase→com.jxareas.xpensor.features.transactions.domain.model.Transactioncom.jxareas.xpensor.features.transactions.domain.usecase.AddTransactionUseCase→com.jxareas.xpensor.features.transactions.domain.model.TransactionDetailscom.jxareas.xpensor.features.transactions.domain.usecase.DeleteTransactionUseCase→com.jxareas.xpensor.features.transactions.domain.model.TransactionDetailscom.jxareas.xpensor.features.transactions.domain.usecase.GetCategoriesUseCase→com.jxareas.xpensor.features.transactions.domain.model.CategoryWithDetailscom.jxareas.xpensor.features.transactions.domain.usecase.GetTransactionsUseCase→com.jxareas.xpensor.features.transactions.domain.model.TransactionDetailscom.jxareas.xpensor.features.transactions.domain.usecase.GetTransactionsWithDayUseCase→com.jxareas.xpensor.features.transactions.domain.model.TransactionDetailscom.jxareas.xpensor.features.transactions.domain.usecase.ValidateTransactionUseCase→com.jxareas.xpensor.features.transactions.domain.model.Transaction
- Direction
- features.transactions.domain.usecase uses features.transactions.domain.model, so a change to features.transactions.domain.model can break features.transactions.domain.usecase, while a change to features.transactions.domain.usecase can't break features.transactions.domain.model.
- Position
- Below the diagonal: features.transactions.domain.usecase uses a module listed above it, which is the healthy direction.
33→25 features.transactions.domain.usecase uses features.transactions.domain.repository✕
- Connections
- 5 pairs of types, where a type in features.transactions.domain.usecase uses a type in features.transactions.domain.repository.
- The types involved
com.jxareas.xpensor.features.transactions.domain.usecase.AddTransactionUseCase→com.jxareas.xpensor.features.transactions.domain.repository.TransactionRepositorycom.jxareas.xpensor.features.transactions.domain.usecase.DeleteTransactionUseCase→com.jxareas.xpensor.features.transactions.domain.repository.TransactionRepositorycom.jxareas.xpensor.features.transactions.domain.usecase.GetCategoriesUseCase→com.jxareas.xpensor.features.transactions.domain.repository.CategoryRepositorycom.jxareas.xpensor.features.transactions.domain.usecase.GetTransactionsUseCase→com.jxareas.xpensor.features.transactions.domain.repository.TransactionRepositorycom.jxareas.xpensor.features.transactions.domain.usecase.GetTransactionsWithDayUseCase→com.jxareas.xpensor.features.transactions.domain.repository.TransactionRepository
- Direction
- features.transactions.domain.usecase uses features.transactions.domain.repository, so a change to features.transactions.domain.repository can break features.transactions.domain.usecase, while a change to features.transactions.domain.usecase can't break features.transactions.domain.repository.
- Position
- Below the diagonal: features.transactions.domain.usecase uses a module listed above it, which is the healthy direction.
34→3 di.modules uses core.data.local.preferences✕
- Connections
- 1 pair of types, where a type in di.modules uses a type in core.data.local.preferences.
- The types involved
com.jxareas.xpensor.di.modules.PreferencesModule→com.jxareas.xpensor.core.data.local.preferences.UserPreferences
- Direction
- di.modules uses core.data.local.preferences, so a change to core.data.local.preferences can break di.modules, while a change to di.modules can't break core.data.local.preferences.
- Position
- Below the diagonal: di.modules uses a module listed above it, which is the healthy direction.
34→13 di.modules uses features.accounts.domain.repository✕
- Connections
- 1 pair of types, where a type in di.modules uses a type in features.accounts.domain.repository.
- The types involved
com.jxareas.xpensor.di.modules.AccountModule→com.jxareas.xpensor.features.accounts.domain.repository.AccountRepository
- Direction
- di.modules uses features.accounts.domain.repository, so a change to features.accounts.domain.repository can break di.modules, while a change to di.modules can't break features.accounts.domain.repository.
- Position
- Below the diagonal: di.modules uses a module listed above it, which is the healthy direction.
34→15 di.modules uses features.converter.data.remote.source.impl✕
- Connections
- 1 pair of types, where a type in di.modules uses a type in features.converter.data.remote.source.impl.
- The types involved
com.jxareas.xpensor.di.modules.CurrencyConverterModule→com.jxareas.xpensor.features.converter.data.remote.source.impl.FreeCurrencyApiRemoteDataSource
- Direction
- di.modules uses features.converter.data.remote.source.impl, so a change to features.converter.data.remote.source.impl can break di.modules, while a change to di.modules can't break features.converter.data.remote.source.impl.
- Position
- Below the diagonal: di.modules uses a module listed above it, which is the healthy direction.
34→16 di.modules uses features.converter.domain.repository✕
- Connections
- 1 pair of types, where a type in di.modules uses a type in features.converter.domain.repository.
- The types involved
com.jxareas.xpensor.di.modules.CurrencyConverterModule→com.jxareas.xpensor.features.converter.domain.repository.CurrencyRepository
- Direction
- di.modules uses features.converter.domain.repository, so a change to features.converter.domain.repository can break di.modules, while a change to di.modules can't break features.converter.domain.repository.
- Position
- Below the diagonal: di.modules uses a module listed above it, which is the healthy direction.
34→20 di.modules uses features.accounts.data.local.source✕
- Connections
- 1 pair of types, where a type in di.modules uses a type in features.accounts.data.local.source.
- The types involved
com.jxareas.xpensor.di.modules.AccountModule→com.jxareas.xpensor.features.accounts.data.local.source.AccountLocalDataSource
- Direction
- di.modules uses features.accounts.data.local.source, so a change to features.accounts.data.local.source can break di.modules, while a change to di.modules can't break features.accounts.data.local.source.
- Position
- Below the diagonal: di.modules uses a module listed above it, which is the healthy direction.
34→22 di.modules uses features.converter.data.repository✕
- Connections
- 1 pair of types, where a type in di.modules uses a type in features.converter.data.repository.
- The types involved
com.jxareas.xpensor.di.modules.CurrencyConverterModule→com.jxareas.xpensor.features.converter.data.repository.DefaultCurrencyRepository
- Direction
- di.modules uses features.converter.data.repository, so a change to features.converter.data.repository can break di.modules, while a change to di.modules can't break features.converter.data.repository.
- Position
- Below the diagonal: di.modules uses a module listed above it, which is the healthy direction.
34→24 di.modules uses features.transactions.data.local.source✕
- Connections
- 2 pairs of types, where a type in di.modules uses a type in features.transactions.data.local.source.
- The types involved
com.jxareas.xpensor.di.modules.CategoryModule→com.jxareas.xpensor.features.transactions.data.local.source.CategoryLocalDataSourcecom.jxareas.xpensor.di.modules.TransactionModule→com.jxareas.xpensor.features.transactions.data.local.source.TransactionLocalDataSource
- Direction
- di.modules uses features.transactions.data.local.source, so a change to features.transactions.data.local.source can break di.modules, while a change to di.modules can't break features.transactions.data.local.source.
- Position
- Below the diagonal: di.modules uses a module listed above it, which is the healthy direction.
34→25 di.modules uses features.transactions.domain.repository✕
- Connections
- 2 pairs of types, where a type in di.modules uses a type in features.transactions.domain.repository.
- The types involved
com.jxareas.xpensor.di.modules.CategoryModule→com.jxareas.xpensor.features.transactions.domain.repository.CategoryRepositorycom.jxareas.xpensor.di.modules.TransactionModule→com.jxareas.xpensor.features.transactions.domain.repository.TransactionRepository
- Direction
- di.modules uses features.transactions.domain.repository, so a change to features.transactions.domain.repository can break di.modules, while a change to di.modules can't break features.transactions.domain.repository.
- Position
- Below the diagonal: di.modules uses a module listed above it, which is the healthy direction.
34→28 di.modules uses features.accounts.data.local.source.impl✕
- Connections
- 1 pair of types, where a type in di.modules uses a type in features.accounts.data.local.source.impl.
- The types involved
com.jxareas.xpensor.di.modules.AccountModule→com.jxareas.xpensor.features.accounts.data.local.source.impl.AccountRoomLocalDataSource
- Direction
- di.modules uses features.accounts.data.local.source.impl, so a change to features.accounts.data.local.source.impl can break di.modules, while a change to di.modules can't break features.accounts.data.local.source.impl.
- Position
- Below the diagonal: di.modules uses a module listed above it, which is the healthy direction.
34→29 di.modules uses features.accounts.data.repository✕
- Connections
- 1 pair of types, where a type in di.modules uses a type in features.accounts.data.repository.
- The types involved
com.jxareas.xpensor.di.modules.AccountModule→com.jxareas.xpensor.features.accounts.data.repository.DefaultAccountRepository
- Direction
- di.modules uses features.accounts.data.repository, so a change to features.accounts.data.repository can break di.modules, while a change to di.modules can't break features.accounts.data.repository.
- Position
- Below the diagonal: di.modules uses a module listed above it, which is the healthy direction.
34→31 di.modules uses features.transactions.data.local.source.impl✕
- Connections
- 2 pairs of types, where a type in di.modules uses a type in features.transactions.data.local.source.impl.
- The types involved
com.jxareas.xpensor.di.modules.CategoryModule→com.jxareas.xpensor.features.transactions.data.local.source.impl.CategoryRoomLocalDataSourcecom.jxareas.xpensor.di.modules.TransactionModule→com.jxareas.xpensor.features.transactions.data.local.source.impl.TransactionRoomLocalDataSource
- Direction
- di.modules uses features.transactions.data.local.source.impl, so a change to features.transactions.data.local.source.impl can break di.modules, while a change to di.modules can't break features.transactions.data.local.source.impl.
- Position
- Below the diagonal: di.modules uses a module listed above it, which is the healthy direction.
34→32 di.modules uses features.transactions.data.repository✕
- Connections
- 2 pairs of types, where a type in di.modules uses a type in features.transactions.data.repository.
- The types involved
com.jxareas.xpensor.di.modules.CategoryModule→com.jxareas.xpensor.features.transactions.data.repository.DefaultCategoryRepositorycom.jxareas.xpensor.di.modules.TransactionModule→com.jxareas.xpensor.features.transactions.data.repository.DefaultTransactionRepository
- Direction
- di.modules uses features.transactions.data.repository, so a change to features.transactions.data.repository can break di.modules, while a change to di.modules can't break features.transactions.data.repository.
- Position
- Below the diagonal: di.modules uses a module listed above it, which is the healthy direction.
35→6 features.accounts.presentation.ui.actions uses features.accounts.presentation.model✕
- Connections
- 1 pair of types, where a type in features.accounts.presentation.ui.actions uses a type in features.accounts.presentation.model.
- The types involved
com.jxareas.xpensor.features.accounts.presentation.ui.actions.AccountActionsViewModel→com.jxareas.xpensor.features.accounts.presentation.model.AccountUi
- Direction
- features.accounts.presentation.ui.actions uses features.accounts.presentation.model, so a change to features.accounts.presentation.model can break features.accounts.presentation.ui.actions, while a change to features.accounts.presentation.ui.actions can't break features.accounts.presentation.model.
- Position
- Below the diagonal: features.accounts.presentation.ui.actions uses a module listed above it, which is the healthy direction.
35→21 features.accounts.presentation.ui.actions uses features.accounts.domain.usecase✕
- Connections
- 1 pair of types, where a type in features.accounts.presentation.ui.actions uses a type in features.accounts.domain.usecase.
- The types involved
com.jxareas.xpensor.features.accounts.presentation.ui.actions.AccountActionsViewModel→com.jxareas.xpensor.features.accounts.domain.usecase.DeleteAccountUseCase
- Direction
- features.accounts.presentation.ui.actions uses features.accounts.domain.usecase, so a change to features.accounts.domain.usecase can break features.accounts.presentation.ui.actions, while a change to features.accounts.presentation.ui.actions can't break features.accounts.domain.usecase.
- Position
- Below the diagonal: features.accounts.presentation.ui.actions uses a module listed above it, which is the healthy direction.
35→27 features.accounts.presentation.ui.actions uses core.presentation✕
- Connections
- 1 pair of types, where a type in features.accounts.presentation.ui.actions uses a type in core.presentation.
- The types involved
com.jxareas.xpensor.features.accounts.presentation.ui.actions.AccountActionsBottomSheet→com.jxareas.xpensor.core.presentation.MainViewModel
- Direction
- features.accounts.presentation.ui.actions uses core.presentation, so a change to core.presentation can break features.accounts.presentation.ui.actions, while a change to features.accounts.presentation.ui.actions can't break core.presentation.
- Position
- Below the diagonal: features.accounts.presentation.ui.actions uses a module listed above it, which is the healthy direction.
36→3 features.accounts.presentation.ui.actions.filter uses core.data.local.preferences✕
- Connections
- 1 pair of types, where a type in features.accounts.presentation.ui.actions.filter uses a type in core.data.local.preferences.
- The types involved
com.jxareas.xpensor.features.accounts.presentation.ui.actions.filter.AccountFilterViewModel→com.jxareas.xpensor.core.data.local.preferences.UserPreferences
- Direction
- features.accounts.presentation.ui.actions.filter uses core.data.local.preferences, so a change to core.data.local.preferences can break features.accounts.presentation.ui.actions.filter, while a change to features.accounts.presentation.ui.actions.filter can't break core.data.local.preferences.
- Position
- Below the diagonal: features.accounts.presentation.ui.actions.filter uses a module listed above it, which is the healthy direction.
36→6 features.accounts.presentation.ui.actions.filter uses features.accounts.presentation.model✕
- Connections
- 3 pairs of types, where a type in features.accounts.presentation.ui.actions.filter uses a type in features.accounts.presentation.model.
- The types involved
com.jxareas.xpensor.features.accounts.presentation.ui.actions.filter.AccountFilterDialogFragment→com.jxareas.xpensor.features.accounts.presentation.model.TotalAccountsAmountUicom.jxareas.xpensor.features.accounts.presentation.ui.actions.filter.AccountFilterViewModel→com.jxareas.xpensor.features.accounts.presentation.model.AccountUicom.jxareas.xpensor.features.accounts.presentation.ui.actions.filter.AccountFilterViewModel→com.jxareas.xpensor.features.accounts.presentation.model.TotalAccountsAmountUi
- Direction
- features.accounts.presentation.ui.actions.filter uses features.accounts.presentation.model, so a change to features.accounts.presentation.model can break features.accounts.presentation.ui.actions.filter, while a change to features.accounts.presentation.ui.actions.filter can't break features.accounts.presentation.model.
- Position
- Below the diagonal: features.accounts.presentation.ui.actions.filter uses a module listed above it, which is the healthy direction.
36→14 features.accounts.presentation.ui.actions.filter uses features.accounts.presentation.ui.adapter✕
- Connections
- 1 pair of types, where a type in features.accounts.presentation.ui.actions.filter uses a type in features.accounts.presentation.ui.adapter.
- The types involved
com.jxareas.xpensor.features.accounts.presentation.ui.actions.filter.AccountFilterDialogFragment→com.jxareas.xpensor.features.accounts.presentation.ui.adapter.AccountsListAdapter
- Direction
- features.accounts.presentation.ui.actions.filter uses features.accounts.presentation.ui.adapter, so a change to features.accounts.presentation.ui.adapter can break features.accounts.presentation.ui.actions.filter, while a change to features.accounts.presentation.ui.actions.filter can't break features.accounts.presentation.ui.adapter.
- Position
- Below the diagonal: features.accounts.presentation.ui.actions.filter uses a module listed above it, which is the healthy direction.
36→21 features.accounts.presentation.ui.actions.filter uses features.accounts.domain.usecase✕
- Connections
- 2 pairs of types, where a type in features.accounts.presentation.ui.actions.filter uses a type in features.accounts.domain.usecase.
- The types involved
com.jxareas.xpensor.features.accounts.presentation.ui.actions.filter.AccountFilterViewModel→com.jxareas.xpensor.features.accounts.domain.usecase.GetAccountsUseCasecom.jxareas.xpensor.features.accounts.presentation.ui.actions.filter.AccountFilterViewModel→com.jxareas.xpensor.features.accounts.domain.usecase.GetTotalAccountsAmountUseCase
- Direction
- features.accounts.presentation.ui.actions.filter uses features.accounts.domain.usecase, so a change to features.accounts.domain.usecase can break features.accounts.presentation.ui.actions.filter, while a change to features.accounts.presentation.ui.actions.filter can't break features.accounts.domain.usecase.
- Position
- Below the diagonal: features.accounts.presentation.ui.actions.filter uses a module listed above it, which is the healthy direction.
36→27 features.accounts.presentation.ui.actions.filter uses core.presentation✕
- Connections
- 1 pair of types, where a type in features.accounts.presentation.ui.actions.filter uses a type in core.presentation.
- The types involved
com.jxareas.xpensor.features.accounts.presentation.ui.actions.filter.AccountFilterDialogFragment→com.jxareas.xpensor.core.presentation.MainViewModel
- Direction
- features.accounts.presentation.ui.actions.filter uses core.presentation, so a change to core.presentation can break features.accounts.presentation.ui.actions.filter, while a change to features.accounts.presentation.ui.actions.filter can't break core.presentation.
- Position
- Below the diagonal: features.accounts.presentation.ui.actions.filter uses a module listed above it, which is the healthy direction.
37→6 features.chart.presentation.ui uses features.accounts.presentation.model✕
- Connections
- 1 pair of types, where a type in features.chart.presentation.ui uses a type in features.accounts.presentation.model.
- The types involved
com.jxareas.xpensor.features.chart.presentation.ui.ChartViewModel→com.jxareas.xpensor.features.accounts.presentation.model.AccountUi
- Direction
- features.chart.presentation.ui uses features.accounts.presentation.model, so a change to features.accounts.presentation.model can break features.chart.presentation.ui, while a change to features.chart.presentation.ui can't break features.accounts.presentation.model.
- Position
- Below the diagonal: features.chart.presentation.ui uses a module listed above it, which is the healthy direction.
37→10 features.chart.presentation.ui uses features.transactions.presentation.model✕
- Connections
- 2 pairs of types, where a type in features.chart.presentation.ui uses a type in features.transactions.presentation.model.
- The types involved
com.jxareas.xpensor.features.chart.presentation.ui.ChartFragment→com.jxareas.xpensor.features.transactions.presentation.model.CategoryWithAmountUicom.jxareas.xpensor.features.chart.presentation.ui.ChartViewModel→com.jxareas.xpensor.features.transactions.presentation.model.CategoryWithAmountUi
- Direction
- features.chart.presentation.ui uses features.transactions.presentation.model, so a change to features.transactions.presentation.model can break features.chart.presentation.ui, while a change to features.chart.presentation.ui can't break features.transactions.presentation.model.
- Position
- Below the diagonal: features.chart.presentation.ui uses a module listed above it, which is the healthy direction.
37→27 features.chart.presentation.ui uses core.presentation✕
- Connections
- 1 pair of types, where a type in features.chart.presentation.ui uses a type in core.presentation.
- The types involved
com.jxareas.xpensor.features.chart.presentation.ui.ChartFragment→com.jxareas.xpensor.core.presentation.MainViewModel
- Direction
- features.chart.presentation.ui uses core.presentation, so a change to core.presentation can break features.chart.presentation.ui, while a change to features.chart.presentation.ui can't break core.presentation.
- Position
- Below the diagonal: features.chart.presentation.ui uses a module listed above it, which is the healthy direction.
37→33 features.chart.presentation.ui uses features.transactions.domain.usecase✕
- Connections
- 1 pair of types, where a type in features.chart.presentation.ui uses a type in features.transactions.domain.usecase.
- The types involved
com.jxareas.xpensor.features.chart.presentation.ui.ChartViewModel→com.jxareas.xpensor.features.transactions.domain.usecase.GetCategoriesUseCase
- Direction
- features.chart.presentation.ui uses features.transactions.domain.usecase, so a change to features.transactions.domain.usecase can break features.chart.presentation.ui, while a change to features.chart.presentation.ui can't break features.transactions.domain.usecase.
- Position
- Below the diagonal: features.chart.presentation.ui uses a module listed above it, which is the healthy direction.
38→6 features.transactions.presentation.ui uses features.accounts.presentation.model✕
- Connections
- 2 pairs of types, where a type in features.transactions.presentation.ui uses a type in features.accounts.presentation.model.
- The types involved
com.jxareas.xpensor.features.transactions.presentation.ui.TransactionsFragment→com.jxareas.xpensor.features.accounts.presentation.model.AccountUicom.jxareas.xpensor.features.transactions.presentation.ui.TransactionsViewModel→com.jxareas.xpensor.features.accounts.presentation.model.AccountUi
- Direction
- features.transactions.presentation.ui uses features.accounts.presentation.model, so a change to features.accounts.presentation.model can break features.transactions.presentation.ui, while a change to features.transactions.presentation.ui can't break features.accounts.presentation.model.
- Position
- Below the diagonal: features.transactions.presentation.ui uses a module listed above it, which is the healthy direction.
38→18 features.transactions.presentation.ui uses features.transactions.domain.model✕
- Connections
- 2 pairs of types, where a type in features.transactions.presentation.ui uses a type in features.transactions.domain.model.
- The types involved
com.jxareas.xpensor.features.transactions.presentation.ui.TransactionsFragment→com.jxareas.xpensor.features.transactions.domain.model.TransactionDetailscom.jxareas.xpensor.features.transactions.presentation.ui.TransactionsViewModel→com.jxareas.xpensor.features.transactions.domain.model.TransactionDetails
- Direction
- features.transactions.presentation.ui uses features.transactions.domain.model, so a change to features.transactions.domain.model can break features.transactions.presentation.ui, while a change to features.transactions.presentation.ui can't break features.transactions.domain.model.
- Position
- Below the diagonal: features.transactions.presentation.ui uses a module listed above it, which is the healthy direction.
38→27 features.transactions.presentation.ui uses core.presentation✕
- Connections
- 1 pair of types, where a type in features.transactions.presentation.ui uses a type in core.presentation.
- The types involved
com.jxareas.xpensor.features.transactions.presentation.ui.TransactionsFragment→com.jxareas.xpensor.core.presentation.MainViewModel
- Direction
- features.transactions.presentation.ui uses core.presentation, so a change to core.presentation can break features.transactions.presentation.ui, while a change to features.transactions.presentation.ui can't break core.presentation.
- Position
- Below the diagonal: features.transactions.presentation.ui uses a module listed above it, which is the healthy direction.
38→33 features.transactions.presentation.ui uses features.transactions.domain.usecase✕
- Connections
- 3 pairs of types, where a type in features.transactions.presentation.ui uses a type in features.transactions.domain.usecase.
- The types involved
com.jxareas.xpensor.features.transactions.presentation.ui.TransactionsViewModel→com.jxareas.xpensor.features.transactions.domain.usecase.DeleteTransactionUseCasecom.jxareas.xpensor.features.transactions.presentation.ui.TransactionsViewModel→com.jxareas.xpensor.features.transactions.domain.usecase.GetTransactionsUseCasecom.jxareas.xpensor.features.transactions.presentation.ui.TransactionsViewModel→com.jxareas.xpensor.features.transactions.domain.usecase.GetTransactionsWithDayUseCase
- Direction
- features.transactions.presentation.ui uses features.transactions.domain.usecase, so a change to features.transactions.domain.usecase can break features.transactions.presentation.ui, while a change to features.transactions.presentation.ui can't break features.transactions.domain.usecase.
- Position
- Below the diagonal: features.transactions.presentation.ui uses a module listed above it, which is the healthy direction.
39→18 features.transactions.presentation.ui.actions.add uses features.transactions.domain.model✕
- Connections
- 1 pair of types, where a type in features.transactions.presentation.ui.actions.add uses a type in features.transactions.domain.model.
- The types involved
com.jxareas.xpensor.features.transactions.presentation.ui.actions.add.AddTransactionViewModel→com.jxareas.xpensor.features.transactions.domain.model.Transaction
- Direction
- features.transactions.presentation.ui.actions.add uses features.transactions.domain.model, so a change to features.transactions.domain.model can break features.transactions.presentation.ui.actions.add, while a change to features.transactions.presentation.ui.actions.add can't break features.transactions.domain.model.
- Position
- Below the diagonal: features.transactions.presentation.ui.actions.add uses a module listed above it, which is the healthy direction.
39→33 features.transactions.presentation.ui.actions.add uses features.transactions.domain.usecase✕
- Connections
- 2 pairs of types, where a type in features.transactions.presentation.ui.actions.add uses a type in features.transactions.domain.usecase.
- The types involved
com.jxareas.xpensor.features.transactions.presentation.ui.actions.add.AddTransactionViewModel→com.jxareas.xpensor.features.transactions.domain.usecase.AddTransactionUseCasecom.jxareas.xpensor.features.transactions.presentation.ui.actions.add.AddTransactionViewModel→com.jxareas.xpensor.features.transactions.domain.usecase.ValidateTransactionUseCase
- Direction
- features.transactions.presentation.ui.actions.add uses features.transactions.domain.usecase, so a change to features.transactions.domain.usecase can break features.transactions.presentation.ui.actions.add, while a change to features.transactions.presentation.ui.actions.add can't break features.transactions.domain.usecase.
- Position
- Below the diagonal: features.transactions.presentation.ui.actions.add uses a module listed above it, which is the healthy direction.
40→6 features.transactions.presentation.ui.actions.category uses features.accounts.presentation.model✕
- Connections
- 1 pair of types, where a type in features.transactions.presentation.ui.actions.category uses a type in features.accounts.presentation.model.
- The types involved
com.jxareas.xpensor.features.transactions.presentation.ui.actions.category.SelectCategoryViewModel→com.jxareas.xpensor.features.accounts.presentation.model.AccountUi
- Direction
- features.transactions.presentation.ui.actions.category uses features.accounts.presentation.model, so a change to features.accounts.presentation.model can break features.transactions.presentation.ui.actions.category, while a change to features.transactions.presentation.ui.actions.category can't break features.accounts.presentation.model.
- Position
- Below the diagonal: features.transactions.presentation.ui.actions.category uses a module listed above it, which is the healthy direction.
40→10 features.transactions.presentation.ui.actions.category uses features.transactions.presentation.model✕
- Connections
- 1 pair of types, where a type in features.transactions.presentation.ui.actions.category uses a type in features.transactions.presentation.model.
- The types involved
com.jxareas.xpensor.features.transactions.presentation.ui.actions.category.SelectCategoryViewModel→com.jxareas.xpensor.features.transactions.presentation.model.CategoryWithAmountUi
- Direction
- features.transactions.presentation.ui.actions.category uses features.transactions.presentation.model, so a change to features.transactions.presentation.model can break features.transactions.presentation.ui.actions.category, while a change to features.transactions.presentation.ui.actions.category can't break features.transactions.presentation.model.
- Position
- Below the diagonal: features.transactions.presentation.ui.actions.category uses a module listed above it, which is the healthy direction.
40→19 features.transactions.presentation.ui.actions.category uses features.transactions.presentation.ui.actions.category.adapter✕
- Connections
- 1 pair of types, where a type in features.transactions.presentation.ui.actions.category uses a type in features.transactions.presentation.ui.actions.category.adapter.
- The types involved
com.jxareas.xpensor.features.transactions.presentation.ui.actions.category.SelectCategoryBottomSheet→com.jxareas.xpensor.features.transactions.presentation.ui.actions.category.adapter.CategoryAdapter
- Direction
- features.transactions.presentation.ui.actions.category uses features.transactions.presentation.ui.actions.category.adapter, so a change to features.transactions.presentation.ui.actions.category.adapter can break features.transactions.presentation.ui.actions.category, while a change to features.transactions.presentation.ui.actions.category can't break features.transactions.presentation.ui.actions.category.adapter.
- Position
- Below the diagonal: features.transactions.presentation.ui.actions.category uses a module listed above it, which is the healthy direction.
40→27 features.transactions.presentation.ui.actions.category uses core.presentation✕
- Connections
- 1 pair of types, where a type in features.transactions.presentation.ui.actions.category uses a type in core.presentation.
- The types involved
com.jxareas.xpensor.features.transactions.presentation.ui.actions.category.SelectCategoryBottomSheet→com.jxareas.xpensor.core.presentation.MainViewModel
- Direction
- features.transactions.presentation.ui.actions.category uses core.presentation, so a change to core.presentation can break features.transactions.presentation.ui.actions.category, while a change to features.transactions.presentation.ui.actions.category can't break core.presentation.
- Position
- Below the diagonal: features.transactions.presentation.ui.actions.category uses a module listed above it, which is the healthy direction.
40→33 features.transactions.presentation.ui.actions.category uses features.transactions.domain.usecase✕
- Connections
- 1 pair of types, where a type in features.transactions.presentation.ui.actions.category uses a type in features.transactions.domain.usecase.
- The types involved
com.jxareas.xpensor.features.transactions.presentation.ui.actions.category.SelectCategoryViewModel→com.jxareas.xpensor.features.transactions.domain.usecase.GetCategoriesUseCase
- Direction
- features.transactions.presentation.ui.actions.category uses features.transactions.domain.usecase, so a change to features.transactions.domain.usecase can break features.transactions.presentation.ui.actions.category, while a change to features.transactions.presentation.ui.actions.category can't break features.transactions.domain.usecase.
- Position
- Below the diagonal: features.transactions.presentation.ui.actions.category uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 1 | Medium |
Roadmap
Top priorities: Add a CI workflow that builds and runs the test suite on every push/PR; Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing; Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a CI workflow that builds and runs the test suite on every push/PR. | +11.0 pts | Medium | CI/CD gates |
| Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing. | +11.0 pts | Medium | Security & performance tooling |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +2.7 pts | Low | Project Cohesion |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +4.7 pts | Medium | Release Hygiene |
| Resolve the 27 Orphaned file finding(s) in Knowledge Freshness — start with TransactionsFragment.kt, AuthenticationActivity.kt, ChartFragment.kt. | +3.4 pts | Medium | Knowledge Freshness |
| Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices. | +2.8 pts | Medium | Slice cohesion |
| Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure. | +2.2 pts | Medium | Constructible invalid state |
| 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. | +1.4 pts | Medium | Architecture documentation |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| app/src/main/java/com/jxareas/xpensor/features/accounts/presentation/ui/actions/add/AddAccountFragment.kt | 7.4 | Near-clean | Code Duplication: Duplicated block (6 lines × 2) |
| app/src/main/java/com/jxareas/xpensor/features/accounts/presentation/ui/AccountsFragment.kt | 7.8 | Near-clean | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| app/src/main/java/com/jxareas/xpensor/features/accounts/presentation/ui/AccountsViewModel.kt | 7.8 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
| REDACTED | 7.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| app/src/main/java/com/jxareas/xpensor/features/converter/presentation/ui/ConverterFragment.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 52 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
What we checked — 52 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 49 of 55 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 4 Maven/Gradle manifest(s) were read, stating a version for 0 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository's 4 Maven/Gradle manifest(s) were read and none of the dependency coordinates they declare carries a version resolvable from the manifest itself: every one is inherited from a parent POM, a <dependencyManagement> block, an imported BOM or a Gradle version reference the catalogue does not define. Licences are resolved from the POMs Maven Central publishes, which requires a version to ask about, and grading whichever release happens to be newest today would be a verdict about a dependency graph this repository has not pinned. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 156 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- 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.
- D20 ADR Quality — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The ADR expectation is gated on whether a repository ships a deployable product. Our repo-kind classifier reads .NET project files and the host and package markers of the other ecosystems it knows (a Go `package main`, a Cargo binary, a package.json `bin`, `start` script or application dev server such as Vite or Next, Python console scripts or a Django/WSGI entry point, a Spring Boot / WAR / Gradle application build, a Rack or Rails app, a Composer project, an OTP release or escript, a Dockerfile, a Procfile, a Platform.sh `.platform/routes.yaml`, and the corresponding published-package manifests, including an OTP `*.app.src`, a Drupal module's `*.info` and a Claude Code `.claude-plugin/plugin.json`), and found none here, so we could not tell what kind of repository this is and did not assess its ADR log. This is a gap in our analyzer, not a finding about this repository.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `app/src/main/java/com/jxareas/xpensor/common/utils/OnBindViewHolder.kt`, `app/src/main/java/com/jxareas/xpensor/common/utils/OnToolbarMenuItemClick.kt`, `app/src/main/java/com/jxareas/xpensor/core/data/local/database/XpensorDatabase.kt`, `app/src/main/java/com/jxareas/xpensor/features/authentication/domain/model/PinCode.kt`, `app/src/main/java/com/jxareas/xpensor/features/converter/domain/model/BaseCurrency.kt`, … (+1 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 (shared-test/src/main/AndroidManifest.xml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Kotlin is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- 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").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
6 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 2 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with AddAccountFragment.kt (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with AccountsFragment.kt. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (11 lines × 4) finding(s) in Code Duplication — start with AccountsFragment.kt. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
3 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence, with abstractness counted on 2 of the 3 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 24 classes have LCOM4 above 3.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
1 deducted task-comment markers across 5151 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with ConverterFragment.kt. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 4 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 2 build units (Gradle) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
27 of 27 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is app/src/main/java/com/jxareas/xpensor/features/transactions/presentation/ui/TransactionsFragment.kt. Counted over 27 of the 177 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 27 Orphaned file finding(s) in Knowledge Freshness — start with TransactionsFragment.kt, AuthenticationActivity.kt, ChartFragment.kt. — One of this dimension's main actionable groups (27 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX7 · Slice cohesion
- `ChartViewModel` (slice 'chart') depends on `GetCategoriesUseCase` from slice 'transactions'. — app/src/main/java/com/jxareas/xpensor/features/chart/presentation/ui/ChartViewModel.kt:27
- `OpenTheAddTransactionSheet` (slice 'converter') depends on `Account` from slice 'accounts'. — app/src/main/java/com/jxareas/xpensor/features/converter/presentation/ui/ConvertCurrencyUiEvent.kt:8
- `TransactionWithCategoryAndAccount` (slice 'transactions') depends on `AccountEntity` from slice 'accounts'. — app/src/main/java/com/jxareas/xpensor/features/transactions/data/local/views/TransactionWithCategoryAndAccount.kt:10
- `TransactionDetails` (slice 'transactions') depends on `Account` from slice 'accounts'. — app/src/main/java/com/jxareas/xpensor/features/transactions/domain/model/TransactionDetails.kt:8
- `AddTransactionUseCase` (slice 'transactions') depends on `AccountRepository` from slice 'accounts'. — app/src/main/java/com/jxareas/xpensor/features/transactions/domain/usecase/AddTransactionUseCase.kt:12
- `DeleteTransactionUseCase` (slice 'transactions') depends on `AccountRepository` from slice 'accounts'. — app/src/main/java/com/jxareas/xpensor/features/transactions/domain/usecase/DeleteTransactionUseCase.kt:12
- `ValidateTransactionUseCase` (slice 'transactions') depends on `AccountRepository` from slice 'accounts'. — app/src/main/java/com/jxareas/xpensor/features/transactions/domain/usecase/ValidateTransactionUseCase.kt:10
- `OpenTheAddTransactionSheet` (slice 'transactions') depends on `AccountUi` from slice 'accounts'. — app/src/main/java/com/jxareas/xpensor/features/transactions/presentation/ui/TransactionUiEvent.kt:8
- `TransactionsViewModel` (slice 'transactions') depends on `AccountUi` from slice 'accounts'. — app/src/main/java/com/jxareas/xpensor/features/transactions/presentation/ui/TransactionsViewModel.kt:38
- `SelectCategory` (slice 'transactions') depends on `AccountUi` from slice 'accounts'. — app/src/main/java/com/jxareas/xpensor/features/transactions/presentation/ui/actions/category/CategorySelectionUiEvent.kt:7
What to do
- Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
DM11 · Constructible invalid state
- `AccountEntity`'s public constructor takes `name`, `amount`, `color` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `AccountEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/com/jxareas/xpensor/features/accounts/data/local/entity/AccountEntity.kt:8
- `CategoryEntity`'s public constructor takes `name`, `iconColor` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `CategoryEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/com/jxareas/xpensor/features/transactions/data/local/entity/CategoryEntity.kt:8
- `TransactionEntity`'s public constructor takes `note`, `amount` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule`, `Requires.` or an `…Exception.ThrowIf…(` helper, and so was any method of this type it calls — a guard reached further than that is not seen. A static factory beside it was NOT counted: while this constructor is public a caller can skip the factory. If the constructor validates in a way this search misses, this row is wrong. If it does not, a caller can build a `TransactionEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — app/src/main/java/com/jxareas/xpensor/features/transactions/data/local/entity/TransactionEntity.kt:38
What to do
- Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain
DM6 · Domain ↔ infrastructure boundary
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add a README to the 3 of 3 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
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.
M3 · Folder & project structure
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
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) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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
- Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 99% | Exemplary | Solid. |
| Architecture | 60% | Adequate — gated by D26, AX7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 61% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 26% | Weak — gated by P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 98% | Exemplary | Solid. |
| Domain Modelling | 70% | Adequate — gated by DM11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 75 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Dagger rejects, at compile time, a component that holds a binding with a narrower scope than its own.
- AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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.
- 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 — ~772 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
- D12 Dependency Hygiene — Not scored — 4 Maven/Gradle manifest(s) were read, stating a version for 0 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — JVM licences not graded — no declared coordinate carries a version the manifest itself resolves
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- 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 — Repository kind not determined
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Kotlin not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .kt, .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — 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) — 6 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- D9 Test Distribution — Test source is present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 4 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — no CI workflow found
- P2 Observability — This repository's JVM source (3 module(s), 168 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- 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.
- 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
- 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
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Serious — 23 finding(s)
- Cross-slice coupling: chart → transactions app/src/main/java/com/jxareas/xpensor/features/chart/presentation/ui/ChartViewModel.kt:27
- Cross-slice coupling: converter → accounts app/src/main/java/com/jxareas/xpensor/features/converter/presentation/ui/ConvertCurrencyUiEvent.kt:8
- Cross-slice coupling: transactions → accounts app/src/main/java/com/jxareas/xpensor/features/transactions/data/local/views/TransactionWithCategoryAndAccount.kt:10
- Cross-slice coupling: transactions → accounts app/src/main/java/com/jxareas/xpensor/features/transactions/domain/model/TransactionDetails.kt:8
- Cross-slice coupling: transactions → accounts app/src/main/java/com/jxareas/xpensor/features/transactions/domain/usecase/AddTransactionUseCase.kt:12
- Cross-slice coupling: transactions → accounts app/src/main/java/com/jxareas/xpensor/features/transactions/domain/usecase/DeleteTransactionUseCase.kt:12
- Cross-slice coupling: transactions → accounts app/src/main/java/com/jxareas/xpensor/features/transactions/domain/usecase/ValidateTransactionUseCase.kt:10
- Cross-slice coupling: transactions → accounts app/src/main/java/com/jxareas/xpensor/features/transactions/presentation/ui/TransactionUiEvent.kt:8
- Cross-slice coupling: transactions → accounts app/src/main/java/com/jxareas/xpensor/features/transactions/presentation/ui/TransactionsViewModel.kt:38
- Cross-slice coupling: transactions → accounts app/src/main/java/com/jxareas/xpensor/features/transactions/presentation/ui/actions/category/CategorySelectionUiEvent.kt:7
- Constructible in an invalid state: AccountEntity app/src/main/java/com/jxareas/xpensor/features/accounts/data/local/entity/AccountEntity.kt:8
- Constructible in an invalid state: CategoryEntity app/src/main/java/com/jxareas/xpensor/features/transactions/data/local/entity/CategoryEntity.kt:8
- Constructible in an invalid state: TransactionEntity app/src/main/java/com/jxareas/xpensor/features/transactions/data/local/entity/TransactionEntity.kt:38
- Duplicated block (5 lines × 2) app/src/main/java/com/jxareas/xpensor/features/accounts/presentation/ui/actions/add/AddAccountFragment.kt:97
- Duplicated block (5 lines × 2) app/src/main/java/com/jxareas/xpensor/features/accounts/presentation/ui/actions/add/AddAccountFragment.kt:110
- TodoComment app/src/main/java/com/jxareas/xpensor/features/converter/presentation/ui/ConverterFragment.kt:114
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) app/src/main/java/com/jxareas/xpensor/features/accounts/presentation/ui/AccountsFragment.kt:44
- Duplicated block (11 lines × 4) app/src/main/java/com/jxareas/xpensor/features/accounts/presentation/ui/AccountsFragment.kt:45
- Duplicated block (6 lines × 2) app/src/main/java/com/jxareas/xpensor/features/accounts/presentation/ui/actions/add/AddAccountFragment.kt:70
- Duplicated block (10 lines × 2) app/src/main/java/com/jxareas/xpensor/features/accounts/presentation/ui/AccountsViewModel.kt:56
- Duplicated block (7 lines × 2) app/src/main/java/com/jxareas/xpensor/features/accounts/presentation/ui/AccountsViewModel.kt:67
- No CI pipeline
Minor — 32 finding(s)
- Orphaned file app/src/main/java/com/jxareas/xpensor/features/transactions/presentation/ui/TransactionsFragment.kt:1
- Orphaned file app/src/main/java/com/jxareas/xpensor/features/authentication/presentation/ui/AuthenticationActivity.kt:1
- Orphaned file app/src/main/java/com/jxareas/xpensor/features/chart/presentation/ui/ChartFragment.kt:1
- Orphaned file app/src/main/java/com/jxareas/xpensor/features/accounts/presentation/ui/actions/edit/EditAccountFragment.kt:1
- Orphaned file app/src/main/java/com/jxareas/xpensor/features/accounts/presentation/ui/AccountsFragment.kt:1
- Orphaned file app/src/main/java/com/jxareas/xpensor/core/presentation/MainActivity.kt:1
- Orphaned file app/src/main/java/com/jxareas/xpensor/features/accounts/presentation/ui/actions/add/AddAccountFragment.kt:1
- Orphaned file app/build.gradle.kts:1
- Orphaned file buildSrc/src/main/java/Dependencies.kt:1
- Orphaned file app/src/main/java/com/jxareas/xpensor/features/converter/presentation/ui/ConverterFragment.kt:1
- Orphaned file app/src/main/java/com/jxareas/xpensor/features/transactions/presentation/ui/actions/add/AddTransactionBottomSheet.kt:1
- Orphaned file app/src/main/java/com/jxareas/xpensor/features/date/presentation/ui/DateSelectorDialogFragment.kt:1
- Orphaned file app/src/main/java/com/jxareas/xpensor/features/transactions/presentation/ui/actions/category/SelectCategoryBottomSheet.kt:1
- Orphaned file app/src/main/java/com/jxareas/xpensor/features/accounts/presentation/ui/actions/filter/AccountFilterDialogFragment.kt:1
- Orphaned file app/src/main/java/com/jxareas/xpensor/features/accounts/presentation/ui/actions/AccountActionsBottomSheet.kt:1
- Orphaned file app/src/main/java/com/jxareas/xpensor/features/transactions/presentation/ui/TransactionsViewModel.kt:1
- Orphaned file app/src/main/java/com/jxareas/xpensor/features/authentication/presentation/ui/AuthenticationViewModel.kt:1
- Orphaned file app/src/main/java/com/jxareas/xpensor/features/transactions/data/mapper/TransactionDataMapper.kt:1
- Orphaned file app/src/main/java/com/jxareas/xpensor/core/presentation/MainViewModel.kt:1
- Orphaned file app/src/main/java/com/jxareas/xpensor/features/transactions/presentation/ui/actions/category/SelectCategoryViewModel.kt:1
- Orphaned file app/src/main/java/com/jxareas/xpensor/features/accounts/presentation/ui/AccountsViewModel.kt:1
- Orphaned file app/src/main/java/com/jxareas/xpensor/features/transactions/data/repository/DefaultTransactionRepository.kt:1
- Orphaned file app/src/main/java/com/jxareas/xpensor/common/extensions/FragmentExt.kt:1
- Orphaned file app/src/main/java/com/jxareas/xpensor/features/accounts/presentation/ui/actions/filter/AccountFilterViewModel.kt:1
- Orphaned file app/src/main/java/com/jxareas/xpensor/features/chart/presentation/ui/ChartViewModel.kt:1
- Projects may be oversized for their cohesion
- Dormant codebase
- No ADRs
- No SAST
- No changelog
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d872808697c6460ea3e649c61437a7ec/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d872808697c6460ea3e649c61437a7ec/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 . | 1 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 6 file(s) — `app/src/main/java/com/jxareas/xpensor/common/utils/OnBindViewHolder.kt`, `app/src/main/java/com/jxareas/xpensor/common/utils/OnToolbarMenuItemClick.kt`, `app/src/main/java/com/jxareas/xpensor/core/data/local/database/XpensorDatabase.kt`, `app/src/main/java/com/jxareas/xpensor/features/authentication/domain/model/PinCode.kt`, `app/src/main/java/com/jxareas/xpensor/features/converter/domain/model/BaseCurrency.kt`, … (+1 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |