Executive summary
Uwi0/Oakane falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no logging, tracing or health checks in the code. It scores 48 out of 100 and is rated Weak, and none of its 11 critical findings concern security.
Production Readiness, at 21, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 11 points. Having someone learn and document the 150 files no active contributor knows comes next, also worth about 11. Raising Production Readiness to 70 would lift the score to about 65.
Eleven sets of files in separate parts keep changing together, which points to hidden dependencies. Making the hidden dependencies explicit would close this risk.
The product code is 28,120 lines, about €30,000 to rebuild.
If Production Readiness rose from 21 to 70, the lowest score rated Strong, the score would rise from 48 to about 65.
Rebuild cost: about €30,000 · Estimate
| Cost to rebuild | €9,800 to €49,000, for 164 to 521 hours of work, about 0.2 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 | Medium: 28,120 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 app.buildlogic | 2 database.model | 3 model.reminder | 4 model.system | 5 oakane.presentation.model | 6 model.category | 7 oakane | 8 model.transaction | 9 model.goal | 10 model | 11 model.monthlyBudget | 12 model.report | 13 model.wallet | 14 data.model | 15 model.wallet.WalletLogItem | 16 data.repository.base | 17 domain.usecase.base | 18 data.repository.impl | 19 domain.usecase.impl | 20 oakane.presentation.viewModel.addGoal | 21 oakane.presentation.viewModel.addTransaction | 22 oakane.presentation.viewModel.categories | 23 oakane.presentation.viewModel.createWallet | 24 oakane.presentation.viewModel.goal | 25 oakane.presentation.viewModel.goals | 26 oakane.presentation.viewModel.home | 27 oakane.presentation.viewModel.main | 28 oakane.presentation.viewModel.monthlyBudget | 29 oakane.presentation.viewModel.onboarding | 30 oakane.presentation.viewModel.reminder | 31 oakane.presentation.viewModel.reports | 32 oakane.presentation.viewModel.settings | 33 oakane.presentation.viewModel.termAndService | 34 oakane.presentation.viewModel.transaction | 35 oakane.presentation.viewModel.transactions | 36 oakane.presentation.viewModel.wallet | 37 oakane.presentation.viewModel.wallets | 38 oakane.presentation.feature.goal.component | 39 oakane.presentation.feature.home.component | 40 oakane.presentation.feature.reports.component |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 app.buildlogic | ||||||||||||||||||||||||||||||||||||||||
| 2 database.model | ||||||||||||||||||||||||||||||||||||||||
| 3 model.reminder | ||||||||||||||||||||||||||||||||||||||||
| 4 model.system | ||||||||||||||||||||||||||||||||||||||||
| 5 oakane.presentation.model | ||||||||||||||||||||||||||||||||||||||||
| 6 model.category | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 7 oakane | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 model.transaction | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 model.goal | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 10 model | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 model.monthlyBudget | 2 | |||||||||||||||||||||||||||||||||||||||
| 12 model.report | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 model.wallet | 2 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 14 data.model | 8 | 1 | 3 | 1 | 2 | 7 | 1 | 2 | 3 | |||||||||||||||||||||||||||||||
| 15 model.wallet.WalletLogItem | 4 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 16 data.repository.base | 1 | 1 | 2 | 1 | 2 | 1 | 1 | 2 | 3 | 5 | ||||||||||||||||||||||||||||||
| 17 domain.usecase.base | 2 | 1 | 1 | 1 | 5 | |||||||||||||||||||||||||||||||||||
| 18 data.repository.impl | 1 | 1 | 2 | 1 | 2 | 1 | 1 | 2 | 3 | 5 | 13 | |||||||||||||||||||||||||||||
| 19 domain.usecase.impl | 2 | 2 | 1 | 1 | 1 | 6 | 3 | 30 | 11 | |||||||||||||||||||||||||||||||
| 20 oakane.presentation.viewModel.addGoal | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 21 oakane.presentation.viewModel.addTransaction | 1 | 1 | 4 | 1 | 2 | 2 | 4 | 2 | ||||||||||||||||||||||||||||||||
| 22 oakane.presentation.viewModel.categories | 1 | 1 | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 23 oakane.presentation.viewModel.createWallet | 1 | 1 | 3 | 2 | ||||||||||||||||||||||||||||||||||||
| 24 oakane.presentation.viewModel.goal | 1 | 2 | 1 | 1 | 1 | 4 | 1 | |||||||||||||||||||||||||||||||||
| 25 oakane.presentation.viewModel.goals | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 26 oakane.presentation.viewModel.home | 1 | 1 | 1 | 1 | 1 | 5 | 1 | |||||||||||||||||||||||||||||||||
| 27 oakane.presentation.viewModel.main | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 oakane.presentation.viewModel.monthlyBudget | 1 | 2 | 1 | 1 | 2 | 4 | 2 | |||||||||||||||||||||||||||||||||
| 29 oakane.presentation.viewModel.onboarding | 1 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 30 oakane.presentation.viewModel.reminder | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 oakane.presentation.viewModel.reports | 1 | 1 | 1 | 1 | 2 | 4 | 1 | |||||||||||||||||||||||||||||||||
| 32 oakane.presentation.viewModel.settings | 1 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 33 oakane.presentation.viewModel.termAndService | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 oakane.presentation.viewModel.transaction | 1 | 1 | 1 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||
| 35 oakane.presentation.viewModel.transactions | 1 | 2 | 4 | 2 | ||||||||||||||||||||||||||||||||||||
| 36 oakane.presentation.viewModel.wallet | 1 | 6 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 37 oakane.presentation.viewModel.wallets | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 38 oakane.presentation.feature.goal.component | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 39 oakane.presentation.feature.home.component | 1 | 1 | 2 | 1 | 4 | |||||||||||||||||||||||||||||||||||
| 40 oakane.presentation.feature.reports.component | 2 | 1 | 1 | 1 | 3 |
6→8 model.category uses model.transaction part of a loop✕
- Connections
- 1 pair of types, where a type in model.category uses a type in model.transaction.
- The types involved
com.kakapo.model.category.CategoryModel→com.kakapo.model.transaction.TransactionType
- Direction
- model.category uses model.transaction, so a change to model.transaction can break model.category, while a change to model.category can't break model.transaction.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→10 model.category uses model part of a loop✕
- Connections
- 1 pair of types, where a type in model.category uses a type in model.
- The types involved
com.kakapo.model.category.CategoryLimitModel→com.kakapo.model.Currency
- Direction
- model.category uses model, so a change to model can break model.category, while a change to model.category can't break model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→4 oakane uses model.system✕
- Connections
- 1 pair of types, where a type in oakane uses a type in model.system.
- The types involved
com.kakapo.oakane.MainActivityKt→com.kakapo.model.system.Theme
- Direction
- oakane uses model.system, so a change to model.system can break oakane, while a change to oakane can't break model.system.
- Position
- Below the diagonal: oakane uses a module listed above it, which is the healthy direction.
8→6 model.transaction uses model.category✕
- Connections
- 1 pair of types, where a type in model.transaction uses a type in model.category.
- The types involved
com.kakapo.model.transaction.TransactionModel→com.kakapo.model.category.CategoryModel
- Direction
- model.transaction uses model.category, so a change to model.category can break model.transaction, while a change to model.transaction can't break model.category.
- Position
- Below the diagonal: model.transaction uses a module listed above it, which is the healthy direction.
8→10 model.transaction uses model part of a loop✕
- Connections
- 1 pair of types, where a type in model.transaction uses a type in model.
- The types involved
com.kakapo.model.transaction.TransactionModel→com.kakapo.model.Currency
- Direction
- model.transaction uses model, so a change to model can break model.transaction, while a change to model.transaction can't break model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→8 model.goal uses model.transaction✕
- Connections
- 1 pair of types, where a type in model.goal uses a type in model.transaction.
- The types involved
com.kakapo.model.goal.GoalSavingModel→com.kakapo.model.transaction.TransactionType
- Direction
- model.goal uses model.transaction, so a change to model.transaction can break model.goal, while a change to model.goal can't break model.transaction.
- Position
- Below the diagonal: model.goal uses a module listed above it, which is the healthy direction.
9→10 model.goal uses model part of a loop✕
- Connections
- 1 pair of types, where a type in model.goal uses a type in model.
- The types involved
com.kakapo.model.goal.GoalModel→com.kakapo.model.Currency
- Direction
- model.goal uses model, so a change to model can break model.goal, while a change to model.goal can't break model.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→8 model uses model.transaction✕
- Connections
- 1 pair of types, where a type in model uses a type in model.transaction.
- The types involved
com.kakapo.model.TransactionModelKt→com.kakapo.model.transaction.TransactionModel
- Direction
- model uses model.transaction, so a change to model.transaction can break model, while a change to model can't break model.transaction.
- Position
- Below the diagonal: model uses a module listed above it, which is the healthy direction.
10→9 model uses model.goal✕
- Connections
- 1 pair of types, where a type in model uses a type in model.goal.
- The types involved
com.kakapo.model.GoalModelKt→com.kakapo.model.goal.GoalModel
- Direction
- model uses model.goal, so a change to model.goal can break model, while a change to model can't break model.goal.
- Position
- Below the diagonal: model uses a module listed above it, which is the healthy direction.
11→10 model.monthlyBudget uses model✕
- Connections
- 2 pairs of types, where a type in model.monthlyBudget uses a type in model.
- The types involved
com.kakapo.model.monthlyBudget.MonthlyBudgetModel→com.kakapo.model.Currencycom.kakapo.model.monthlyBudget.MonthlyBudgetOverView→com.kakapo.model.Currency
- Direction
- model.monthlyBudget uses model, so a change to model can break model.monthlyBudget, while a change to model.monthlyBudget can't break model.
- Position
- Below the diagonal: model.monthlyBudget uses a module listed above it, which is the healthy direction.
12→6 model.report uses model.category✕
- Connections
- 1 pair of types, where a type in model.report uses a type in model.category.
- The types involved
com.kakapo.model.report.ReportModel→com.kakapo.model.category.CategoryIconName
- Direction
- model.report uses model.category, so a change to model.category can break model.report, while a change to model.report can't break model.category.
- Position
- Below the diagonal: model.report uses a module listed above it, which is the healthy direction.
12→10 model.report uses model✕
- Connections
- 1 pair of types, where a type in model.report uses a type in model.
- The types involved
com.kakapo.model.report.ReportModel→com.kakapo.model.Currency
- Direction
- model.report uses model, so a change to model can break model.report, while a change to model.report can't break model.
- Position
- Below the diagonal: model.report uses a module listed above it, which is the healthy direction.
13→6 model.wallet uses model.category✕
- Connections
- 2 pairs of types, where a type in model.wallet uses a type in model.category.
- The types involved
com.kakapo.model.wallet.WalletItemModel→com.kakapo.model.category.CategoryIconNamecom.kakapo.model.wallet.WalletModel→com.kakapo.model.category.CategoryIconName
- Direction
- model.wallet uses model.category, so a change to model.category can break model.wallet, while a change to model.wallet can't break model.category.
- Position
- Below the diagonal: model.wallet uses a module listed above it, which is the healthy direction.
13→8 model.wallet uses model.transaction✕
- Connections
- 2 pairs of types, where a type in model.wallet uses a type in model.transaction.
- The types involved
com.kakapo.model.wallet.WalletLogItem→com.kakapo.model.transaction.TransactionTypecom.kakapo.model.wallet.WalletTransferModel→com.kakapo.model.transaction.TransactionType
- Direction
- model.wallet uses model.transaction, so a change to model.transaction can break model.wallet, while a change to model.wallet can't break model.transaction.
- Position
- Below the diagonal: model.wallet uses a module listed above it, which is the healthy direction.
13→10 model.wallet uses model✕
- Connections
- 3 pairs of types, where a type in model.wallet uses a type in model.
- The types involved
com.kakapo.model.wallet.WalletItemModel→com.kakapo.model.Currencycom.kakapo.model.wallet.WalletModel→com.kakapo.model.Currencycom.kakapo.model.wallet.WalletTransferModel→com.kakapo.model.Currency
- Direction
- model.wallet uses model, so a change to model can break model.wallet, while a change to model.wallet can't break model.
- Position
- Below the diagonal: model.wallet uses a module listed above it, which is the healthy direction.
14→2 data.model uses database.model✕
- Connections
- 8 pairs of types, where a type in data.model uses a type in database.model.
- The types involved
com.kakapo.data.model.CategoryLimitParam→com.kakapo.database.model.CategoryLimitEntitycom.kakapo.data.model.CategoryMapperKt→com.kakapo.database.model.CategoryEntitycom.kakapo.data.model.GoalMapperKt→com.kakapo.database.model.GoalEntitycom.kakapo.data.model.GoalSavingParam→com.kakapo.database.model.GoalSavingsEntitycom.kakapo.data.model.MonthlyBudgetParam→com.kakapo.database.model.MonthlyBudgetEntitycom.kakapo.data.model.TransactionParam→com.kakapo.database.model.TransactionEntitycom.kakapo.data.model.WalletMapperKt→com.kakapo.database.model.WalletEntitycom.kakapo.data.model.WalletTransferParam→com.kakapo.database.model.WalletTransferEntity
- Direction
- data.model uses database.model, so a change to database.model can break data.model, while a change to data.model can't break database.model.
- Position
- Below the diagonal: data.model uses a module listed above it, which is the healthy direction.
14→3 data.model uses model.reminder✕
- Connections
- 1 pair of types, where a type in data.model uses a type in model.reminder.
- The types involved
com.kakapo.data.model.ReminderMapperKt→com.kakapo.model.reminder.Reminder
- Direction
- data.model uses model.reminder, so a change to model.reminder can break data.model, while a change to data.model can't break model.reminder.
- Position
- Below the diagonal: data.model uses a module listed above it, which is the healthy direction.
14→6 data.model uses model.category✕
- Connections
- 3 pairs of types, where a type in data.model uses a type in model.category.
- The types involved
com.kakapo.data.model.CategoryLimitMapperKt→com.kakapo.model.category.CategoryLimitModelcom.kakapo.data.model.CategoryMapperKt→com.kakapo.model.category.CategoryModelcom.kakapo.data.model.TransactionParam→com.kakapo.model.category.CategoryModel
- Direction
- data.model uses model.category, so a change to model.category can break data.model, while a change to data.model can't break model.category.
- Position
- Below the diagonal: data.model uses a module listed above it, which is the healthy direction.
14→8 data.model uses model.transaction✕
- Connections
- 1 pair of types, where a type in data.model uses a type in model.transaction.
- The types involved
com.kakapo.data.model.TransactionMapperKt→com.kakapo.model.transaction.TransactionModel
- Direction
- data.model uses model.transaction, so a change to model.transaction can break data.model, while a change to data.model can't break model.transaction.
- Position
- Below the diagonal: data.model uses a module listed above it, which is the healthy direction.
14→9 data.model uses model.goal✕
- Connections
- 2 pairs of types, where a type in data.model uses a type in model.goal.
- The types involved
com.kakapo.data.model.GoalMapperKt→com.kakapo.model.goal.GoalModelcom.kakapo.data.model.GoalSavingMapperKt→com.kakapo.model.goal.GoalSavingModel
- Direction
- data.model uses model.goal, so a change to model.goal can break data.model, while a change to data.model can't break model.goal.
- Position
- Below the diagonal: data.model uses a module listed above it, which is the healthy direction.
14→10 data.model uses model✕
- Connections
- 7 pairs of types, where a type in data.model uses a type in model.
- The types involved
com.kakapo.data.model.CategoryLimitMapperKt→com.kakapo.model.Currencycom.kakapo.data.model.GoalMapperKt→com.kakapo.model.Currencycom.kakapo.data.model.MonthlyBudgetMapperKt→com.kakapo.model.Currencycom.kakapo.data.model.ReportMapperKt→com.kakapo.model.Currencycom.kakapo.data.model.TransactionMapperKt→com.kakapo.model.Currencycom.kakapo.data.model.WalletMapperKt→com.kakapo.model.Currencycom.kakapo.data.model.WalletTransferMapperKt→com.kakapo.model.Currency
- Direction
- data.model uses model, so a change to model can break data.model, while a change to data.model can't break model.
- Position
- Below the diagonal: data.model uses a module listed above it, which is the healthy direction.
14→11 data.model uses model.monthlyBudget✕
- Connections
- 1 pair of types, where a type in data.model uses a type in model.monthlyBudget.
- The types involved
com.kakapo.data.model.MonthlyBudgetMapperKt→com.kakapo.model.monthlyBudget.MonthlyBudgetModel
- Direction
- data.model uses model.monthlyBudget, so a change to model.monthlyBudget can break data.model, while a change to data.model can't break model.monthlyBudget.
- Position
- Below the diagonal: data.model uses a module listed above it, which is the healthy direction.
14→12 data.model uses model.report✕
- Connections
- 2 pairs of types, where a type in data.model uses a type in model.report.
- The types involved
com.kakapo.data.model.ReportMapperKt→com.kakapo.model.report.ReportCsvModelcom.kakapo.data.model.TransactionMapperKt→com.kakapo.model.report.ReportModel
- Direction
- data.model uses model.report, so a change to model.report can break data.model, while a change to data.model can't break model.report.
- Position
- Below the diagonal: data.model uses a module listed above it, which is the healthy direction.
14→13 data.model uses model.wallet✕
- Connections
- 3 pairs of types, where a type in data.model uses a type in model.wallet.
- The types involved
com.kakapo.data.model.WalletMapperKt→com.kakapo.model.wallet.WalletItemModelcom.kakapo.data.model.WalletMapperKt→com.kakapo.model.wallet.WalletModelcom.kakapo.data.model.WalletTransferMapperKt→com.kakapo.model.wallet.WalletTransferModel
- Direction
- data.model uses model.wallet, so a change to model.wallet can break data.model, while a change to data.model can't break model.wallet.
- Position
- Below the diagonal: data.model uses a module listed above it, which is the healthy direction.
15→8 model.wallet.WalletLogItem uses model.transaction✕
- Connections
- 4 pairs of types, where a type in model.wallet.WalletLogItem uses a type in model.transaction.
- The types involved
com.kakapo.model.wallet.WalletLogItem.GoalSavingLogItem→com.kakapo.model.transaction.TransactionTypecom.kakapo.model.wallet.WalletLogItem.TransactionLogItem→com.kakapo.model.transaction.TransactionModelcom.kakapo.model.wallet.WalletLogItem.TransactionLogItem→com.kakapo.model.transaction.TransactionTypecom.kakapo.model.wallet.WalletLogItem.WalletTransferLogItem→com.kakapo.model.transaction.TransactionType
- Direction
- model.wallet.WalletLogItem uses model.transaction, so a change to model.transaction can break model.wallet.WalletLogItem, while a change to model.wallet.WalletLogItem can't break model.transaction.
- Position
- Below the diagonal: model.wallet.WalletLogItem uses a module listed above it, which is the healthy direction.
15→9 model.wallet.WalletLogItem uses model.goal✕
- Connections
- 1 pair of types, where a type in model.wallet.WalletLogItem uses a type in model.goal.
- The types involved
com.kakapo.model.wallet.WalletLogItem.GoalSavingLogItem→com.kakapo.model.goal.GoalSavingModel
- Direction
- model.wallet.WalletLogItem uses model.goal, so a change to model.goal can break model.wallet.WalletLogItem, while a change to model.wallet.WalletLogItem can't break model.goal.
- Position
- Below the diagonal: model.wallet.WalletLogItem uses a module listed above it, which is the healthy direction.
15→13 model.wallet.WalletLogItem uses model.wallet✕
- Connections
- 4 pairs of types, where a type in model.wallet.WalletLogItem uses a type in model.wallet.
- The types involved
com.kakapo.model.wallet.WalletLogItem.GoalSavingLogItem→com.kakapo.model.wallet.WalletLogItemcom.kakapo.model.wallet.WalletLogItem.TransactionLogItem→com.kakapo.model.wallet.WalletLogItemcom.kakapo.model.wallet.WalletLogItem.WalletTransferLogItem→com.kakapo.model.wallet.WalletLogItemcom.kakapo.model.wallet.WalletLogItem.WalletTransferLogItem→com.kakapo.model.wallet.WalletTransferModel
- Direction
- model.wallet.WalletLogItem uses model.wallet, so a change to model.wallet can break model.wallet.WalletLogItem, while a change to model.wallet.WalletLogItem can't break model.wallet.
- Position
- Below the diagonal: model.wallet.WalletLogItem uses a module listed above it, which is the healthy direction.
16→3 data.repository.base uses model.reminder✕
- Connections
- 1 pair of types, where a type in data.repository.base uses a type in model.reminder.
- The types involved
com.kakapo.data.repository.base.SettingsRepository→com.kakapo.model.reminder.Reminder
- Direction
- data.repository.base uses model.reminder, so a change to model.reminder can break data.repository.base, while a change to data.repository.base can't break model.reminder.
- Position
- Below the diagonal: data.repository.base uses a module listed above it, which is the healthy direction.
16→4 data.repository.base uses model.system✕
- Connections
- 1 pair of types, where a type in data.repository.base uses a type in model.system.
- The types involved
com.kakapo.data.repository.base.SystemRepository→com.kakapo.model.system.Theme
- Direction
- data.repository.base uses model.system, so a change to model.system can break data.repository.base, while a change to data.repository.base can't break model.system.
- Position
- Below the diagonal: data.repository.base uses a module listed above it, which is the healthy direction.
16→6 data.repository.base uses model.category✕
- Connections
- 2 pairs of types, where a type in data.repository.base uses a type in model.category.
- The types involved
com.kakapo.data.repository.base.CategoryLimitRepository→com.kakapo.model.category.CategoryLimitModelcom.kakapo.data.repository.base.CategoryRepository→com.kakapo.model.category.CategoryModel
- Direction
- data.repository.base uses model.category, so a change to model.category can break data.repository.base, while a change to data.repository.base can't break model.category.
- Position
- Below the diagonal: data.repository.base uses a module listed above it, which is the healthy direction.
16→8 data.repository.base uses model.transaction✕
- Connections
- 1 pair of types, where a type in data.repository.base uses a type in model.transaction.
- The types involved
com.kakapo.data.repository.base.TransactionRepository→com.kakapo.model.transaction.TransactionModel
- Direction
- data.repository.base uses model.transaction, so a change to model.transaction can break data.repository.base, while a change to data.repository.base can't break model.transaction.
- Position
- Below the diagonal: data.repository.base uses a module listed above it, which is the healthy direction.
16→9 data.repository.base uses model.goal✕
- Connections
- 2 pairs of types, where a type in data.repository.base uses a type in model.goal.
- The types involved
com.kakapo.data.repository.base.GoalRepository→com.kakapo.model.goal.GoalModelcom.kakapo.data.repository.base.GoalSavingsRepository→com.kakapo.model.goal.GoalSavingModel
- Direction
- data.repository.base uses model.goal, so a change to model.goal can break data.repository.base, while a change to data.repository.base can't break model.goal.
- Position
- Below the diagonal: data.repository.base uses a module listed above it, which is the healthy direction.
16→10 data.repository.base uses model✕
- Connections
- 1 pair of types, where a type in data.repository.base uses a type in model.
- The types involved
com.kakapo.data.repository.base.SystemRepository→com.kakapo.model.Currency
- Direction
- data.repository.base uses model, so a change to model can break data.repository.base, while a change to data.repository.base can't break model.
- Position
- Below the diagonal: data.repository.base uses a module listed above it, which is the healthy direction.
16→11 data.repository.base uses model.monthlyBudget✕
- Connections
- 1 pair of types, where a type in data.repository.base uses a type in model.monthlyBudget.
- The types involved
com.kakapo.data.repository.base.MonthlyBudgetRepository→com.kakapo.model.monthlyBudget.MonthlyBudgetModel
- Direction
- data.repository.base uses model.monthlyBudget, so a change to model.monthlyBudget can break data.repository.base, while a change to data.repository.base can't break model.monthlyBudget.
- Position
- Below the diagonal: data.repository.base uses a module listed above it, which is the healthy direction.
16→12 data.repository.base uses model.report✕
- Connections
- 2 pairs of types, where a type in data.repository.base uses a type in model.report.
- The types involved
com.kakapo.data.repository.base.ReportRepository→com.kakapo.model.report.ReportCsvModelcom.kakapo.data.repository.base.TransactionRepository→com.kakapo.model.report.ReportModel
- Direction
- data.repository.base uses model.report, so a change to model.report can break data.repository.base, while a change to data.repository.base can't break model.report.
- Position
- Below the diagonal: data.repository.base uses a module listed above it, which is the healthy direction.
16→13 data.repository.base uses model.wallet✕
- Connections
- 3 pairs of types, where a type in data.repository.base uses a type in model.wallet.
- The types involved
com.kakapo.data.repository.base.WalletRepository→com.kakapo.model.wallet.WalletItemModelcom.kakapo.data.repository.base.WalletRepository→com.kakapo.model.wallet.WalletModelcom.kakapo.data.repository.base.WalletTransferRepository→com.kakapo.model.wallet.WalletTransferModel
- Direction
- data.repository.base uses model.wallet, so a change to model.wallet can break data.repository.base, while a change to data.repository.base can't break model.wallet.
- Position
- Below the diagonal: data.repository.base uses a module listed above it, which is the healthy direction.
16→14 data.repository.base uses data.model✕
- Connections
- 5 pairs of types, where a type in data.repository.base uses a type in data.model.
- The types involved
com.kakapo.data.repository.base.CategoryLimitRepository→com.kakapo.data.model.CategoryLimitParamcom.kakapo.data.repository.base.GoalSavingsRepository→com.kakapo.data.model.GoalSavingParamcom.kakapo.data.repository.base.MonthlyBudgetRepository→com.kakapo.data.model.MonthlyBudgetParamcom.kakapo.data.repository.base.TransactionRepository→com.kakapo.data.model.TransactionParamcom.kakapo.data.repository.base.WalletTransferRepository→com.kakapo.data.model.WalletTransferParam
- Direction
- data.repository.base uses data.model, so a change to data.model can break data.repository.base, while a change to data.repository.base can't break data.model.
- Position
- Below the diagonal: data.repository.base uses a module listed above it, which is the healthy direction.
17→8 domain.usecase.base uses model.transaction✕
- Connections
- 2 pairs of types, where a type in domain.usecase.base uses a type in model.transaction.
- The types involved
com.kakapo.domain.usecase.base.DeleteTransactionUseCase→com.kakapo.model.transaction.TransactionModelcom.kakapo.domain.usecase.base.UpdateTransactionUseCase→com.kakapo.model.transaction.TransactionModel
- Direction
- domain.usecase.base uses model.transaction, so a change to model.transaction can break domain.usecase.base, while a change to domain.usecase.base can't break model.transaction.
- Position
- Below the diagonal: domain.usecase.base uses a module listed above it, which is the healthy direction.
17→9 domain.usecase.base uses model.goal✕
- Connections
- 1 pair of types, where a type in domain.usecase.base uses a type in model.goal.
- The types involved
com.kakapo.domain.usecase.base.SaveGoalUseCase→com.kakapo.model.goal.GoalModel
- Direction
- domain.usecase.base uses model.goal, so a change to model.goal can break domain.usecase.base, while a change to domain.usecase.base can't break model.goal.
- Position
- Below the diagonal: domain.usecase.base uses a module listed above it, which is the healthy direction.
17→11 domain.usecase.base uses model.monthlyBudget✕
- Connections
- 1 pair of types, where a type in domain.usecase.base uses a type in model.monthlyBudget.
- The types involved
com.kakapo.domain.usecase.base.GetMonthlyBudgetOverviewUseCase→com.kakapo.model.monthlyBudget.MonthlyBudgetOverView
- Direction
- domain.usecase.base uses model.monthlyBudget, so a change to model.monthlyBudget can break domain.usecase.base, while a change to domain.usecase.base can't break model.monthlyBudget.
- Position
- Below the diagonal: domain.usecase.base uses a module listed above it, which is the healthy direction.
17→13 domain.usecase.base uses model.wallet✕
- Connections
- 1 pair of types, where a type in domain.usecase.base uses a type in model.wallet.
- The types involved
com.kakapo.domain.usecase.base.WalletLogItemsUseCase→com.kakapo.model.wallet.WalletLogItem
- Direction
- domain.usecase.base uses model.wallet, so a change to model.wallet can break domain.usecase.base, while a change to domain.usecase.base can't break model.wallet.
- Position
- Below the diagonal: domain.usecase.base uses a module listed above it, which is the healthy direction.
17→14 domain.usecase.base uses data.model✕
- Connections
- 5 pairs of types, where a type in domain.usecase.base uses a type in data.model.
- The types involved
com.kakapo.domain.usecase.base.AddGoalSavingUseCase→com.kakapo.data.model.GoalSavingParamcom.kakapo.domain.usecase.base.MoveWalletBalanceUseCase→com.kakapo.data.model.WalletTransferParamcom.kakapo.domain.usecase.base.SaveTransactionUseCase→com.kakapo.data.model.TransactionParamcom.kakapo.domain.usecase.base.UpdateTransactionUseCase→com.kakapo.data.model.TransactionParamcom.kakapo.domain.usecase.base.ValidateCategoryLimitUseCase→com.kakapo.data.model.CategoryLimitParam
- Direction
- domain.usecase.base uses data.model, so a change to data.model can break domain.usecase.base, while a change to domain.usecase.base can't break data.model.
- Position
- Below the diagonal: domain.usecase.base uses a module listed above it, which is the healthy direction.
18→3 data.repository.impl uses model.reminder✕
- Connections
- 1 pair of types, where a type in data.repository.impl uses a type in model.reminder.
- The types involved
com.kakapo.data.repository.impl.SettingsRepositoryImpl→com.kakapo.model.reminder.Reminder
- Direction
- data.repository.impl uses model.reminder, so a change to model.reminder can break data.repository.impl, while a change to data.repository.impl can't break model.reminder.
- Position
- Below the diagonal: data.repository.impl uses a module listed above it, which is the healthy direction.
18→4 data.repository.impl uses model.system✕
- Connections
- 1 pair of types, where a type in data.repository.impl uses a type in model.system.
- The types involved
com.kakapo.data.repository.impl.SystemRepositoryImpl→com.kakapo.model.system.Theme
- Direction
- data.repository.impl uses model.system, so a change to model.system can break data.repository.impl, while a change to data.repository.impl can't break model.system.
- Position
- Below the diagonal: data.repository.impl uses a module listed above it, which is the healthy direction.
18→6 data.repository.impl uses model.category✕
- Connections
- 2 pairs of types, where a type in data.repository.impl uses a type in model.category.
- The types involved
com.kakapo.data.repository.impl.CategoryLimitRepositoryImpl→com.kakapo.model.category.CategoryLimitModelcom.kakapo.data.repository.impl.CategoryRepositoryImpl→com.kakapo.model.category.CategoryModel
- Direction
- data.repository.impl uses model.category, so a change to model.category can break data.repository.impl, while a change to data.repository.impl can't break model.category.
- Position
- Below the diagonal: data.repository.impl uses a module listed above it, which is the healthy direction.
18→8 data.repository.impl uses model.transaction✕
- Connections
- 1 pair of types, where a type in data.repository.impl uses a type in model.transaction.
- The types involved
com.kakapo.data.repository.impl.TransactionRepositoryImpl→com.kakapo.model.transaction.TransactionModel
- Direction
- data.repository.impl uses model.transaction, so a change to model.transaction can break data.repository.impl, while a change to data.repository.impl can't break model.transaction.
- Position
- Below the diagonal: data.repository.impl uses a module listed above it, which is the healthy direction.
18→9 data.repository.impl uses model.goal✕
- Connections
- 2 pairs of types, where a type in data.repository.impl uses a type in model.goal.
- The types involved
com.kakapo.data.repository.impl.GoalRepositoryImpl→com.kakapo.model.goal.GoalModelcom.kakapo.data.repository.impl.GoalSavingsRepositoryImpl→com.kakapo.model.goal.GoalSavingModel
- Direction
- data.repository.impl uses model.goal, so a change to model.goal can break data.repository.impl, while a change to data.repository.impl can't break model.goal.
- Position
- Below the diagonal: data.repository.impl uses a module listed above it, which is the healthy direction.
18→10 data.repository.impl uses model✕
- Connections
- 1 pair of types, where a type in data.repository.impl uses a type in model.
- The types involved
com.kakapo.data.repository.impl.SystemRepositoryImpl→com.kakapo.model.Currency
- Direction
- data.repository.impl uses model, so a change to model can break data.repository.impl, while a change to data.repository.impl can't break model.
- Position
- Below the diagonal: data.repository.impl uses a module listed above it, which is the healthy direction.
18→11 data.repository.impl uses model.monthlyBudget✕
- Connections
- 1 pair of types, where a type in data.repository.impl uses a type in model.monthlyBudget.
- The types involved
com.kakapo.data.repository.impl.MonthlyBudgetRepositoryImpl→com.kakapo.model.monthlyBudget.MonthlyBudgetModel
- Direction
- data.repository.impl uses model.monthlyBudget, so a change to model.monthlyBudget can break data.repository.impl, while a change to data.repository.impl can't break model.monthlyBudget.
- Position
- Below the diagonal: data.repository.impl uses a module listed above it, which is the healthy direction.
18→12 data.repository.impl uses model.report✕
- Connections
- 2 pairs of types, where a type in data.repository.impl uses a type in model.report.
- The types involved
com.kakapo.data.repository.impl.ReportRepositoryImpl→com.kakapo.model.report.ReportCsvModelcom.kakapo.data.repository.impl.TransactionRepositoryImpl→com.kakapo.model.report.ReportModel
- Direction
- data.repository.impl uses model.report, so a change to model.report can break data.repository.impl, while a change to data.repository.impl can't break model.report.
- Position
- Below the diagonal: data.repository.impl uses a module listed above it, which is the healthy direction.
18→13 data.repository.impl uses model.wallet✕
- Connections
- 3 pairs of types, where a type in data.repository.impl uses a type in model.wallet.
- The types involved
com.kakapo.data.repository.impl.WalletRepositoryImpl→com.kakapo.model.wallet.WalletItemModelcom.kakapo.data.repository.impl.WalletRepositoryImpl→com.kakapo.model.wallet.WalletModelcom.kakapo.data.repository.impl.WalletTransferRepositoryImpl→com.kakapo.model.wallet.WalletTransferModel
- Direction
- data.repository.impl uses model.wallet, so a change to model.wallet can break data.repository.impl, while a change to data.repository.impl can't break model.wallet.
- Position
- Below the diagonal: data.repository.impl uses a module listed above it, which is the healthy direction.
18→14 data.repository.impl uses data.model✕
- Connections
- 5 pairs of types, where a type in data.repository.impl uses a type in data.model.
- The types involved
com.kakapo.data.repository.impl.CategoryLimitRepositoryImpl→com.kakapo.data.model.CategoryLimitParamcom.kakapo.data.repository.impl.GoalSavingsRepositoryImpl→com.kakapo.data.model.GoalSavingParamcom.kakapo.data.repository.impl.MonthlyBudgetRepositoryImpl→com.kakapo.data.model.MonthlyBudgetParamcom.kakapo.data.repository.impl.TransactionRepositoryImpl→com.kakapo.data.model.TransactionParamcom.kakapo.data.repository.impl.WalletTransferRepositoryImpl→com.kakapo.data.model.WalletTransferParam
- Direction
- data.repository.impl uses data.model, so a change to data.model can break data.repository.impl, while a change to data.repository.impl can't break data.model.
- Position
- Below the diagonal: data.repository.impl uses a module listed above it, which is the healthy direction.
18→16 data.repository.impl uses data.repository.base✕
- Connections
- 13 pairs of types, where a type in data.repository.impl uses a type in data.repository.base.
- The types involved
com.kakapo.data.repository.impl.BackupRepositoryImpl→com.kakapo.data.repository.base.BackupRepositorycom.kakapo.data.repository.impl.BudgetRepositoryImpl→com.kakapo.data.repository.base.BudgetRepositorycom.kakapo.data.repository.impl.CategoryLimitRepositoryImpl→com.kakapo.data.repository.base.CategoryLimitRepositorycom.kakapo.data.repository.impl.CategoryRepositoryImpl→com.kakapo.data.repository.base.CategoryRepositorycom.kakapo.data.repository.impl.GoalRepositoryImpl→com.kakapo.data.repository.base.GoalRepositorycom.kakapo.data.repository.impl.GoalSavingsRepositoryImpl→com.kakapo.data.repository.base.GoalSavingsRepositorycom.kakapo.data.repository.impl.MonthlyBudgetRepositoryImpl→com.kakapo.data.repository.base.MonthlyBudgetRepositorycom.kakapo.data.repository.impl.ReportRepositoryImpl→com.kakapo.data.repository.base.ReportRepositorycom.kakapo.data.repository.impl.SettingsRepositoryImpl→com.kakapo.data.repository.base.SettingsRepositorycom.kakapo.data.repository.impl.SystemRepositoryImpl→com.kakapo.data.repository.base.SystemRepositorycom.kakapo.data.repository.impl.TransactionRepositoryImpl→com.kakapo.data.repository.base.TransactionRepositorycom.kakapo.data.repository.impl.WalletRepositoryImpl→com.kakapo.data.repository.base.WalletRepositorycom.kakapo.data.repository.impl.WalletTransferRepositoryImpl→com.kakapo.data.repository.base.WalletTransferRepository
- Direction
- data.repository.impl uses data.repository.base, so a change to data.repository.base can break data.repository.impl, while a change to data.repository.impl can't break data.repository.base.
- Position
- Below the diagonal: data.repository.impl uses a module listed above it, which is the healthy direction.
19→6 domain.usecase.impl uses model.category✕
- Connections
- 2 pairs of types, where a type in domain.usecase.impl uses a type in model.category.
- The types involved
com.kakapo.domain.usecase.impl.DeleteTransactionUseCaseImpl→com.kakapo.model.category.CategoryLimitModelcom.kakapo.domain.usecase.impl.UpdateTransactionUseCaseImpl→com.kakapo.model.category.CategoryLimitModel
- Direction
- domain.usecase.impl uses model.category, so a change to model.category can break domain.usecase.impl, while a change to domain.usecase.impl can't break model.category.
- Position
- Below the diagonal: domain.usecase.impl uses a module listed above it, which is the healthy direction.
19→8 domain.usecase.impl uses model.transaction✕
- Connections
- 2 pairs of types, where a type in domain.usecase.impl uses a type in model.transaction.
- The types involved
com.kakapo.domain.usecase.impl.DeleteTransactionUseCaseImpl→com.kakapo.model.transaction.TransactionModelcom.kakapo.domain.usecase.impl.UpdateTransactionUseCaseImpl→com.kakapo.model.transaction.TransactionModel
- Direction
- domain.usecase.impl uses model.transaction, so a change to model.transaction can break domain.usecase.impl, while a change to domain.usecase.impl can't break model.transaction.
- Position
- Below the diagonal: domain.usecase.impl uses a module listed above it, which is the healthy direction.
19→9 domain.usecase.impl uses model.goal✕
- Connections
- 1 pair of types, where a type in domain.usecase.impl uses a type in model.goal.
- The types involved
com.kakapo.domain.usecase.impl.SaveGoalUseCaseImpl→com.kakapo.model.goal.GoalModel
- Direction
- domain.usecase.impl uses model.goal, so a change to model.goal can break domain.usecase.impl, while a change to domain.usecase.impl can't break model.goal.
- Position
- Below the diagonal: domain.usecase.impl uses a module listed above it, which is the healthy direction.
19→11 domain.usecase.impl uses model.monthlyBudget✕
- Connections
- 1 pair of types, where a type in domain.usecase.impl uses a type in model.monthlyBudget.
- The types involved
com.kakapo.domain.usecase.impl.GetMonthlyBudgetOverviewUseCaseImpl→com.kakapo.model.monthlyBudget.MonthlyBudgetOverView
- Direction
- domain.usecase.impl uses model.monthlyBudget, so a change to model.monthlyBudget can break domain.usecase.impl, while a change to domain.usecase.impl can't break model.monthlyBudget.
- Position
- Below the diagonal: domain.usecase.impl uses a module listed above it, which is the healthy direction.
19→13 domain.usecase.impl uses model.wallet✕
- Connections
- 1 pair of types, where a type in domain.usecase.impl uses a type in model.wallet.
- The types involved
com.kakapo.domain.usecase.impl.WalletLogItemsUseCaseImpl→com.kakapo.model.wallet.WalletLogItem
- Direction
- domain.usecase.impl uses model.wallet, so a change to model.wallet can break domain.usecase.impl, while a change to domain.usecase.impl can't break model.wallet.
- Position
- Below the diagonal: domain.usecase.impl uses a module listed above it, which is the healthy direction.
19→14 domain.usecase.impl uses data.model✕
- Connections
- 6 pairs of types, where a type in domain.usecase.impl uses a type in data.model.
- The types involved
com.kakapo.domain.usecase.impl.AddGoalSavingUseCaseImpl→com.kakapo.data.model.GoalSavingParamcom.kakapo.domain.usecase.impl.ImportRecurringBudgetUseCaseImpl→com.kakapo.data.model.MonthlyBudgetParamcom.kakapo.domain.usecase.impl.MoveWalletBalanceUseCaseImpl→com.kakapo.data.model.WalletTransferParamcom.kakapo.domain.usecase.impl.SaveTransactionUseCaseImpl→com.kakapo.data.model.TransactionParamcom.kakapo.domain.usecase.impl.UpdateTransactionUseCaseImpl→com.kakapo.data.model.TransactionParamcom.kakapo.domain.usecase.impl.ValidateCategoryLimitUseCaseImpl→com.kakapo.data.model.CategoryLimitParam
- Direction
- domain.usecase.impl uses data.model, so a change to data.model can break domain.usecase.impl, while a change to domain.usecase.impl can't break data.model.
- Position
- Below the diagonal: domain.usecase.impl uses a module listed above it, which is the healthy direction.
19→15 domain.usecase.impl uses model.wallet.WalletLogItem✕
- Connections
- 3 pairs of types, where a type in domain.usecase.impl uses a type in model.wallet.WalletLogItem.
- The types involved
com.kakapo.domain.usecase.impl.WalletLogItemsUseCaseImpl→com.kakapo.model.wallet.WalletLogItem.GoalSavingLogItemcom.kakapo.domain.usecase.impl.WalletLogItemsUseCaseImpl→com.kakapo.model.wallet.WalletLogItem.TransactionLogItemcom.kakapo.domain.usecase.impl.WalletLogItemsUseCaseImpl→com.kakapo.model.wallet.WalletLogItem.WalletTransferLogItem
- Direction
- domain.usecase.impl uses model.wallet.WalletLogItem, so a change to model.wallet.WalletLogItem can break domain.usecase.impl, while a change to domain.usecase.impl can't break model.wallet.WalletLogItem.
- Position
- Below the diagonal: domain.usecase.impl uses a module listed above it, which is the healthy direction.
19→16 domain.usecase.impl uses data.repository.base✕
- Connections
- 30 pairs of types, where a type in domain.usecase.impl uses a type in data.repository.base. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.kakapo.domain.usecase.impl.AddGoalSavingUseCaseImpl→com.kakapo.data.repository.base.GoalRepositorycom.kakapo.domain.usecase.impl.AddGoalSavingUseCaseImpl→com.kakapo.data.repository.base.GoalSavingsRepositorycom.kakapo.domain.usecase.impl.AddGoalSavingUseCaseImpl→com.kakapo.data.repository.base.WalletRepositorycom.kakapo.domain.usecase.impl.DeleteTransactionUseCaseImpl→com.kakapo.data.repository.base.CategoryLimitRepositorycom.kakapo.domain.usecase.impl.DeleteTransactionUseCaseImpl→com.kakapo.data.repository.base.MonthlyBudgetRepositorycom.kakapo.domain.usecase.impl.DeleteTransactionUseCaseImpl→com.kakapo.data.repository.base.TransactionRepositorycom.kakapo.domain.usecase.impl.DeleteTransactionUseCaseImpl→com.kakapo.data.repository.base.WalletRepositorycom.kakapo.domain.usecase.impl.GetMonthlyBudgetOverviewUseCaseImpl→com.kakapo.data.repository.base.MonthlyBudgetRepositorycom.kakapo.domain.usecase.impl.GetMonthlyBudgetOverviewUseCaseImpl→com.kakapo.data.repository.base.SystemRepositorycom.kakapo.domain.usecase.impl.GetMonthlyBudgetOverviewUseCaseImpl→com.kakapo.data.repository.base.TransactionRepositorycom.kakapo.domain.usecase.impl.ImportRecurringBudgetUseCaseImpl→com.kakapo.data.repository.base.BudgetRepositorycom.kakapo.domain.usecase.impl.ImportRecurringBudgetUseCaseImpl→com.kakapo.data.repository.base.CategoryLimitRepositorycom.kakapo.domain.usecase.impl.ImportRecurringBudgetUseCaseImpl→com.kakapo.data.repository.base.MonthlyBudgetRepositorycom.kakapo.domain.usecase.impl.MoveWalletBalanceUseCaseImpl→com.kakapo.data.repository.base.WalletRepositorycom.kakapo.domain.usecase.impl.MoveWalletBalanceUseCaseImpl→com.kakapo.data.repository.base.WalletTransferRepositorycom.kakapo.domain.usecase.impl.SaveGoalUseCaseImpl→com.kakapo.data.repository.base.GoalRepositorycom.kakapo.domain.usecase.impl.SaveTransactionUseCaseImpl→com.kakapo.data.repository.base.CategoryLimitRepositorycom.kakapo.domain.usecase.impl.SaveTransactionUseCaseImpl→com.kakapo.data.repository.base.MonthlyBudgetRepositorycom.kakapo.domain.usecase.impl.SaveTransactionUseCaseImpl→com.kakapo.data.repository.base.TransactionRepositorycom.kakapo.domain.usecase.impl.SaveTransactionUseCaseImpl→com.kakapo.data.repository.base.WalletRepositorycom.kakapo.domain.usecase.impl.SetRecurringBudgetUseCaseImpl→com.kakapo.data.repository.base.BudgetRepositorycom.kakapo.domain.usecase.impl.UpdateTransactionUseCaseImpl→com.kakapo.data.repository.base.CategoryLimitRepositorycom.kakapo.domain.usecase.impl.UpdateTransactionUseCaseImpl→com.kakapo.data.repository.base.MonthlyBudgetRepositorycom.kakapo.domain.usecase.impl.UpdateTransactionUseCaseImpl→com.kakapo.data.repository.base.TransactionRepositorycom.kakapo.domain.usecase.impl.UpdateTransactionUseCaseImpl→com.kakapo.data.repository.base.WalletRepository
- Direction
- domain.usecase.impl uses data.repository.base, so a change to data.repository.base can break domain.usecase.impl, while a change to domain.usecase.impl can't break data.repository.base.
- Position
- Below the diagonal: domain.usecase.impl uses a module listed above it, which is the healthy direction.
19→17 domain.usecase.impl uses domain.usecase.base✕
- Connections
- 11 pairs of types, where a type in domain.usecase.impl uses a type in domain.usecase.base.
- The types involved
com.kakapo.domain.usecase.impl.AddGoalSavingUseCaseImpl→com.kakapo.domain.usecase.base.AddGoalSavingUseCasecom.kakapo.domain.usecase.impl.DeleteTransactionUseCaseImpl→com.kakapo.domain.usecase.base.DeleteTransactionUseCasecom.kakapo.domain.usecase.impl.GetMonthlyBudgetOverviewUseCaseImpl→com.kakapo.domain.usecase.base.GetMonthlyBudgetOverviewUseCasecom.kakapo.domain.usecase.impl.ImportRecurringBudgetUseCaseImpl→com.kakapo.domain.usecase.base.ImportRecurringBudgetUseCasecom.kakapo.domain.usecase.impl.MoveWalletBalanceUseCaseImpl→com.kakapo.domain.usecase.base.MoveWalletBalanceUseCasecom.kakapo.domain.usecase.impl.SaveGoalUseCaseImpl→com.kakapo.domain.usecase.base.SaveGoalUseCasecom.kakapo.domain.usecase.impl.SaveTransactionUseCaseImpl→com.kakapo.domain.usecase.base.SaveTransactionUseCasecom.kakapo.domain.usecase.impl.SetRecurringBudgetUseCaseImpl→com.kakapo.domain.usecase.base.SetRecurringBudgetUseCasecom.kakapo.domain.usecase.impl.UpdateTransactionUseCaseImpl→com.kakapo.domain.usecase.base.UpdateTransactionUseCasecom.kakapo.domain.usecase.impl.ValidateCategoryLimitUseCaseImpl→com.kakapo.domain.usecase.base.ValidateCategoryLimitUseCasecom.kakapo.domain.usecase.impl.WalletLogItemsUseCaseImpl→com.kakapo.domain.usecase.base.WalletLogItemsUseCase
- Direction
- domain.usecase.impl uses domain.usecase.base, so a change to domain.usecase.base can break domain.usecase.impl, while a change to domain.usecase.impl can't break domain.usecase.base.
- Position
- Below the diagonal: domain.usecase.impl uses a module listed above it, which is the healthy direction.
20→9 oakane.presentation.viewModel.addGoal uses model.goal✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.addGoal uses a type in model.goal.
- The types involved
com.kakapo.oakane.presentation.viewModel.addGoal.AddGoalState→com.kakapo.model.goal.GoalModel
- Direction
- oakane.presentation.viewModel.addGoal uses model.goal, so a change to model.goal can break oakane.presentation.viewModel.addGoal, while a change to oakane.presentation.viewModel.addGoal can't break model.goal.
- Position
- Below the diagonal: oakane.presentation.viewModel.addGoal uses a module listed above it, which is the healthy direction.
20→10 oakane.presentation.viewModel.addGoal uses model✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.addGoal uses a type in model.
- The types involved
com.kakapo.oakane.presentation.viewModel.addGoal.AddGoalState→com.kakapo.model.Currency
- Direction
- oakane.presentation.viewModel.addGoal uses model, so a change to model can break oakane.presentation.viewModel.addGoal, while a change to oakane.presentation.viewModel.addGoal can't break model.
- Position
- Below the diagonal: oakane.presentation.viewModel.addGoal uses a module listed above it, which is the healthy direction.
20→16 oakane.presentation.viewModel.addGoal uses data.repository.base✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.viewModel.addGoal uses a type in data.repository.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.addGoal.AddGoalViewModel→com.kakapo.data.repository.base.GoalRepositorycom.kakapo.oakane.presentation.viewModel.addGoal.AddGoalViewModel→com.kakapo.data.repository.base.SystemRepository
- Direction
- oakane.presentation.viewModel.addGoal uses data.repository.base, so a change to data.repository.base can break oakane.presentation.viewModel.addGoal, while a change to oakane.presentation.viewModel.addGoal can't break data.repository.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.addGoal uses a module listed above it, which is the healthy direction.
20→17 oakane.presentation.viewModel.addGoal uses domain.usecase.base✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.addGoal uses a type in domain.usecase.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.addGoal.AddGoalViewModel→com.kakapo.domain.usecase.base.SaveGoalUseCase
- Direction
- oakane.presentation.viewModel.addGoal uses domain.usecase.base, so a change to domain.usecase.base can break oakane.presentation.viewModel.addGoal, while a change to oakane.presentation.viewModel.addGoal can't break domain.usecase.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.addGoal uses a module listed above it, which is the healthy direction.
21→4 oakane.presentation.viewModel.addTransaction uses model.system✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.addTransaction uses a type in model.system.
- The types involved
com.kakapo.oakane.presentation.viewModel.addTransaction.AddTransactionState→com.kakapo.model.system.Theme
- Direction
- oakane.presentation.viewModel.addTransaction uses model.system, so a change to model.system can break oakane.presentation.viewModel.addTransaction, while a change to oakane.presentation.viewModel.addTransaction can't break model.system.
- Position
- Below the diagonal: oakane.presentation.viewModel.addTransaction uses a module listed above it, which is the healthy direction.
21→6 oakane.presentation.viewModel.addTransaction uses model.category✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.addTransaction uses a type in model.category.
- The types involved
com.kakapo.oakane.presentation.viewModel.addTransaction.AddTransactionState→com.kakapo.model.category.CategoryModel
- Direction
- oakane.presentation.viewModel.addTransaction uses model.category, so a change to model.category can break oakane.presentation.viewModel.addTransaction, while a change to oakane.presentation.viewModel.addTransaction can't break model.category.
- Position
- Below the diagonal: oakane.presentation.viewModel.addTransaction uses a module listed above it, which is the healthy direction.
21→8 oakane.presentation.viewModel.addTransaction uses model.transaction✕
- Connections
- 4 pairs of types, where a type in oakane.presentation.viewModel.addTransaction uses a type in model.transaction.
- The types involved
com.kakapo.oakane.presentation.viewModel.addTransaction.AddTransactionState→com.kakapo.model.transaction.TransactionModelcom.kakapo.oakane.presentation.viewModel.addTransaction.AddTransactionState→com.kakapo.model.transaction.TransactionTypecom.kakapo.oakane.presentation.viewModel.addTransaction.AddTransactionViewModel→com.kakapo.model.transaction.TransactionModelcom.kakapo.oakane.presentation.viewModel.addTransaction.AddTransactionViewModel→com.kakapo.model.transaction.TransactionType
- Direction
- oakane.presentation.viewModel.addTransaction uses model.transaction, so a change to model.transaction can break oakane.presentation.viewModel.addTransaction, while a change to oakane.presentation.viewModel.addTransaction can't break model.transaction.
- Position
- Below the diagonal: oakane.presentation.viewModel.addTransaction uses a module listed above it, which is the healthy direction.
21→10 oakane.presentation.viewModel.addTransaction uses model✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.addTransaction uses a type in model.
- The types involved
com.kakapo.oakane.presentation.viewModel.addTransaction.AddTransactionState→com.kakapo.model.Currency
- Direction
- oakane.presentation.viewModel.addTransaction uses model, so a change to model can break oakane.presentation.viewModel.addTransaction, while a change to oakane.presentation.viewModel.addTransaction can't break model.
- Position
- Below the diagonal: oakane.presentation.viewModel.addTransaction uses a module listed above it, which is the healthy direction.
21→13 oakane.presentation.viewModel.addTransaction uses model.wallet✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.viewModel.addTransaction uses a type in model.wallet.
- The types involved
com.kakapo.oakane.presentation.viewModel.addTransaction.AddTransactionState→com.kakapo.model.wallet.WalletModelcom.kakapo.oakane.presentation.viewModel.addTransaction.AddTransactionViewModel→com.kakapo.model.wallet.WalletModel
- Direction
- oakane.presentation.viewModel.addTransaction uses model.wallet, so a change to model.wallet can break oakane.presentation.viewModel.addTransaction, while a change to oakane.presentation.viewModel.addTransaction can't break model.wallet.
- Position
- Below the diagonal: oakane.presentation.viewModel.addTransaction uses a module listed above it, which is the healthy direction.
21→14 oakane.presentation.viewModel.addTransaction uses data.model✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.viewModel.addTransaction uses a type in data.model.
- The types involved
com.kakapo.oakane.presentation.viewModel.addTransaction.AddTransactionState→com.kakapo.data.model.TransactionParamcom.kakapo.oakane.presentation.viewModel.addTransaction.AddTransactionViewModel→com.kakapo.data.model.TransactionParam
- Direction
- oakane.presentation.viewModel.addTransaction uses data.model, so a change to data.model can break oakane.presentation.viewModel.addTransaction, while a change to oakane.presentation.viewModel.addTransaction can't break data.model.
- Position
- Below the diagonal: oakane.presentation.viewModel.addTransaction uses a module listed above it, which is the healthy direction.
21→16 oakane.presentation.viewModel.addTransaction uses data.repository.base✕
- Connections
- 4 pairs of types, where a type in oakane.presentation.viewModel.addTransaction uses a type in data.repository.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.addTransaction.AddTransactionViewModel→com.kakapo.data.repository.base.CategoryRepositorycom.kakapo.oakane.presentation.viewModel.addTransaction.AddTransactionViewModel→com.kakapo.data.repository.base.SystemRepositorycom.kakapo.oakane.presentation.viewModel.addTransaction.AddTransactionViewModel→com.kakapo.data.repository.base.TransactionRepositorycom.kakapo.oakane.presentation.viewModel.addTransaction.AddTransactionViewModel→com.kakapo.data.repository.base.WalletRepository
- Direction
- oakane.presentation.viewModel.addTransaction uses data.repository.base, so a change to data.repository.base can break oakane.presentation.viewModel.addTransaction, while a change to oakane.presentation.viewModel.addTransaction can't break data.repository.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.addTransaction uses a module listed above it, which is the healthy direction.
21→17 oakane.presentation.viewModel.addTransaction uses domain.usecase.base✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.viewModel.addTransaction uses a type in domain.usecase.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.addTransaction.AddTransactionViewModel→com.kakapo.domain.usecase.base.SaveTransactionUseCasecom.kakapo.oakane.presentation.viewModel.addTransaction.AddTransactionViewModel→com.kakapo.domain.usecase.base.UpdateTransactionUseCase
- Direction
- oakane.presentation.viewModel.addTransaction uses domain.usecase.base, so a change to domain.usecase.base can break oakane.presentation.viewModel.addTransaction, while a change to oakane.presentation.viewModel.addTransaction can't break domain.usecase.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.addTransaction uses a module listed above it, which is the healthy direction.
22→4 oakane.presentation.viewModel.categories uses model.system✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.categories uses a type in model.system.
- The types involved
com.kakapo.oakane.presentation.viewModel.categories.CategoriesState→com.kakapo.model.system.Theme
- Direction
- oakane.presentation.viewModel.categories uses model.system, so a change to model.system can break oakane.presentation.viewModel.categories, while a change to oakane.presentation.viewModel.categories can't break model.system.
- Position
- Below the diagonal: oakane.presentation.viewModel.categories uses a module listed above it, which is the healthy direction.
22→5 oakane.presentation.viewModel.categories uses oakane.presentation.model✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.categories uses a type in oakane.presentation.model.
- The types involved
com.kakapo.oakane.presentation.viewModel.categories.CategoriesState→com.kakapo.oakane.presentation.model.CategoriesSheetContent
- Direction
- oakane.presentation.viewModel.categories uses oakane.presentation.model, so a change to oakane.presentation.model can break oakane.presentation.viewModel.categories, while a change to oakane.presentation.viewModel.categories can't break oakane.presentation.model.
- Position
- Below the diagonal: oakane.presentation.viewModel.categories uses a module listed above it, which is the healthy direction.
22→6 oakane.presentation.viewModel.categories uses model.category✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.viewModel.categories uses a type in model.category.
- The types involved
com.kakapo.oakane.presentation.viewModel.categories.CategoriesState→com.kakapo.model.category.CategoryIconNamecom.kakapo.oakane.presentation.viewModel.categories.CategoriesState→com.kakapo.model.category.CategoryModel
- Direction
- oakane.presentation.viewModel.categories uses model.category, so a change to model.category can break oakane.presentation.viewModel.categories, while a change to oakane.presentation.viewModel.categories can't break model.category.
- Position
- Below the diagonal: oakane.presentation.viewModel.categories uses a module listed above it, which is the healthy direction.
22→8 oakane.presentation.viewModel.categories uses model.transaction✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.categories uses a type in model.transaction.
- The types involved
com.kakapo.oakane.presentation.viewModel.categories.CategoriesState→com.kakapo.model.transaction.TransactionType
- Direction
- oakane.presentation.viewModel.categories uses model.transaction, so a change to model.transaction can break oakane.presentation.viewModel.categories, while a change to oakane.presentation.viewModel.categories can't break model.transaction.
- Position
- Below the diagonal: oakane.presentation.viewModel.categories uses a module listed above it, which is the healthy direction.
22→16 oakane.presentation.viewModel.categories uses data.repository.base✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.viewModel.categories uses a type in data.repository.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.categories.CategoriesViewModel→com.kakapo.data.repository.base.CategoryRepositorycom.kakapo.oakane.presentation.viewModel.categories.CategoriesViewModel→com.kakapo.data.repository.base.SystemRepository
- Direction
- oakane.presentation.viewModel.categories uses data.repository.base, so a change to data.repository.base can break oakane.presentation.viewModel.categories, while a change to oakane.presentation.viewModel.categories can't break data.repository.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.categories uses a module listed above it, which is the healthy direction.
23→6 oakane.presentation.viewModel.createWallet uses model.category✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.createWallet uses a type in model.category.
- The types involved
com.kakapo.oakane.presentation.viewModel.createWallet.CreateWalletState→com.kakapo.model.category.CategoryIconName
- Direction
- oakane.presentation.viewModel.createWallet uses model.category, so a change to model.category can break oakane.presentation.viewModel.createWallet, while a change to oakane.presentation.viewModel.createWallet can't break model.category.
- Position
- Below the diagonal: oakane.presentation.viewModel.createWallet uses a module listed above it, which is the healthy direction.
23→10 oakane.presentation.viewModel.createWallet uses model✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.createWallet uses a type in model.
- The types involved
com.kakapo.oakane.presentation.viewModel.createWallet.CreateWalletState→com.kakapo.model.Currency
- Direction
- oakane.presentation.viewModel.createWallet uses model, so a change to model can break oakane.presentation.viewModel.createWallet, while a change to oakane.presentation.viewModel.createWallet can't break model.
- Position
- Below the diagonal: oakane.presentation.viewModel.createWallet uses a module listed above it, which is the healthy direction.
23→13 oakane.presentation.viewModel.createWallet uses model.wallet✕
- Connections
- 3 pairs of types, where a type in oakane.presentation.viewModel.createWallet uses a type in model.wallet.
- The types involved
com.kakapo.oakane.presentation.viewModel.createWallet.CreateWalletState→com.kakapo.model.wallet.WalletItemModelcom.kakapo.oakane.presentation.viewModel.createWallet.CreateWalletState→com.kakapo.model.wallet.WalletModelcom.kakapo.oakane.presentation.viewModel.createWallet.CreateWalletViewModel→com.kakapo.model.wallet.WalletModel
- Direction
- oakane.presentation.viewModel.createWallet uses model.wallet, so a change to model.wallet can break oakane.presentation.viewModel.createWallet, while a change to oakane.presentation.viewModel.createWallet can't break model.wallet.
- Position
- Below the diagonal: oakane.presentation.viewModel.createWallet uses a module listed above it, which is the healthy direction.
23→16 oakane.presentation.viewModel.createWallet uses data.repository.base✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.viewModel.createWallet uses a type in data.repository.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.createWallet.CreateWalletViewModel→com.kakapo.data.repository.base.SystemRepositorycom.kakapo.oakane.presentation.viewModel.createWallet.CreateWalletViewModel→com.kakapo.data.repository.base.WalletRepository
- Direction
- oakane.presentation.viewModel.createWallet uses data.repository.base, so a change to data.repository.base can break oakane.presentation.viewModel.createWallet, while a change to oakane.presentation.viewModel.createWallet can't break data.repository.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.createWallet uses a module listed above it, which is the healthy direction.
24→4 oakane.presentation.viewModel.goal uses model.system✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.goal uses a type in model.system.
- The types involved
com.kakapo.oakane.presentation.viewModel.goal.GoalState→com.kakapo.model.system.Theme
- Direction
- oakane.presentation.viewModel.goal uses model.system, so a change to model.system can break oakane.presentation.viewModel.goal, while a change to oakane.presentation.viewModel.goal can't break model.system.
- Position
- Below the diagonal: oakane.presentation.viewModel.goal uses a module listed above it, which is the healthy direction.
24→9 oakane.presentation.viewModel.goal uses model.goal✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.viewModel.goal uses a type in model.goal.
- The types involved
com.kakapo.oakane.presentation.viewModel.goal.GoalState→com.kakapo.model.goal.GoalModelcom.kakapo.oakane.presentation.viewModel.goal.GoalState→com.kakapo.model.goal.GoalSavingModel
- Direction
- oakane.presentation.viewModel.goal uses model.goal, so a change to model.goal can break oakane.presentation.viewModel.goal, while a change to oakane.presentation.viewModel.goal can't break model.goal.
- Position
- Below the diagonal: oakane.presentation.viewModel.goal uses a module listed above it, which is the healthy direction.
24→10 oakane.presentation.viewModel.goal uses model✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.goal uses a type in model.
- The types involved
com.kakapo.oakane.presentation.viewModel.goal.GoalState→com.kakapo.model.Currency
- Direction
- oakane.presentation.viewModel.goal uses model, so a change to model can break oakane.presentation.viewModel.goal, while a change to oakane.presentation.viewModel.goal can't break model.
- Position
- Below the diagonal: oakane.presentation.viewModel.goal uses a module listed above it, which is the healthy direction.
24→13 oakane.presentation.viewModel.goal uses model.wallet✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.goal uses a type in model.wallet.
- The types involved
com.kakapo.oakane.presentation.viewModel.goal.GoalState→com.kakapo.model.wallet.WalletModel
- Direction
- oakane.presentation.viewModel.goal uses model.wallet, so a change to model.wallet can break oakane.presentation.viewModel.goal, while a change to oakane.presentation.viewModel.goal can't break model.wallet.
- Position
- Below the diagonal: oakane.presentation.viewModel.goal uses a module listed above it, which is the healthy direction.
24→14 oakane.presentation.viewModel.goal uses data.model✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.goal uses a type in data.model.
- The types involved
com.kakapo.oakane.presentation.viewModel.goal.GoalState→com.kakapo.data.model.GoalSavingParam
- Direction
- oakane.presentation.viewModel.goal uses data.model, so a change to data.model can break oakane.presentation.viewModel.goal, while a change to oakane.presentation.viewModel.goal can't break data.model.
- Position
- Below the diagonal: oakane.presentation.viewModel.goal uses a module listed above it, which is the healthy direction.
24→16 oakane.presentation.viewModel.goal uses data.repository.base✕
- Connections
- 4 pairs of types, where a type in oakane.presentation.viewModel.goal uses a type in data.repository.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.goal.GoalViewModel→com.kakapo.data.repository.base.GoalRepositorycom.kakapo.oakane.presentation.viewModel.goal.GoalViewModel→com.kakapo.data.repository.base.GoalSavingsRepositorycom.kakapo.oakane.presentation.viewModel.goal.GoalViewModel→com.kakapo.data.repository.base.SystemRepositorycom.kakapo.oakane.presentation.viewModel.goal.GoalViewModel→com.kakapo.data.repository.base.WalletRepository
- Direction
- oakane.presentation.viewModel.goal uses data.repository.base, so a change to data.repository.base can break oakane.presentation.viewModel.goal, while a change to oakane.presentation.viewModel.goal can't break data.repository.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.goal uses a module listed above it, which is the healthy direction.
24→17 oakane.presentation.viewModel.goal uses domain.usecase.base✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.goal uses a type in domain.usecase.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.goal.GoalViewModel→com.kakapo.domain.usecase.base.AddGoalSavingUseCase
- Direction
- oakane.presentation.viewModel.goal uses domain.usecase.base, so a change to domain.usecase.base can break oakane.presentation.viewModel.goal, while a change to oakane.presentation.viewModel.goal can't break domain.usecase.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.goal uses a module listed above it, which is the healthy direction.
25→4 oakane.presentation.viewModel.goals uses model.system✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.goals uses a type in model.system.
- The types involved
com.kakapo.oakane.presentation.viewModel.goals.GoalsState→com.kakapo.model.system.Theme
- Direction
- oakane.presentation.viewModel.goals uses model.system, so a change to model.system can break oakane.presentation.viewModel.goals, while a change to oakane.presentation.viewModel.goals can't break model.system.
- Position
- Below the diagonal: oakane.presentation.viewModel.goals uses a module listed above it, which is the healthy direction.
25→9 oakane.presentation.viewModel.goals uses model.goal✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.goals uses a type in model.goal.
- The types involved
com.kakapo.oakane.presentation.viewModel.goals.GoalsState→com.kakapo.model.goal.GoalModel
- Direction
- oakane.presentation.viewModel.goals uses model.goal, so a change to model.goal can break oakane.presentation.viewModel.goals, while a change to oakane.presentation.viewModel.goals can't break model.goal.
- Position
- Below the diagonal: oakane.presentation.viewModel.goals uses a module listed above it, which is the healthy direction.
25→16 oakane.presentation.viewModel.goals uses data.repository.base✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.viewModel.goals uses a type in data.repository.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.goals.GoalsViewModel→com.kakapo.data.repository.base.GoalRepositorycom.kakapo.oakane.presentation.viewModel.goals.GoalsViewModel→com.kakapo.data.repository.base.SystemRepository
- Direction
- oakane.presentation.viewModel.goals uses data.repository.base, so a change to data.repository.base can break oakane.presentation.viewModel.goals, while a change to oakane.presentation.viewModel.goals can't break data.repository.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.goals uses a module listed above it, which is the healthy direction.
26→4 oakane.presentation.viewModel.home uses model.system✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.home uses a type in model.system.
- The types involved
com.kakapo.oakane.presentation.viewModel.home.HomeState→com.kakapo.model.system.Theme
- Direction
- oakane.presentation.viewModel.home uses model.system, so a change to model.system can break oakane.presentation.viewModel.home, while a change to oakane.presentation.viewModel.home can't break model.system.
- Position
- Below the diagonal: oakane.presentation.viewModel.home uses a module listed above it, which is the healthy direction.
26→8 oakane.presentation.viewModel.home uses model.transaction✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.home uses a type in model.transaction.
- The types involved
com.kakapo.oakane.presentation.viewModel.home.HomeState→com.kakapo.model.transaction.TransactionModel
- Direction
- oakane.presentation.viewModel.home uses model.transaction, so a change to model.transaction can break oakane.presentation.viewModel.home, while a change to oakane.presentation.viewModel.home can't break model.transaction.
- Position
- Below the diagonal: oakane.presentation.viewModel.home uses a module listed above it, which is the healthy direction.
26→9 oakane.presentation.viewModel.home uses model.goal✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.home uses a type in model.goal.
- The types involved
com.kakapo.oakane.presentation.viewModel.home.HomeState→com.kakapo.model.goal.GoalModel
- Direction
- oakane.presentation.viewModel.home uses model.goal, so a change to model.goal can break oakane.presentation.viewModel.home, while a change to oakane.presentation.viewModel.home can't break model.goal.
- Position
- Below the diagonal: oakane.presentation.viewModel.home uses a module listed above it, which is the healthy direction.
26→11 oakane.presentation.viewModel.home uses model.monthlyBudget✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.home uses a type in model.monthlyBudget.
- The types involved
com.kakapo.oakane.presentation.viewModel.home.HomeState→com.kakapo.model.monthlyBudget.MonthlyBudgetOverView
- Direction
- oakane.presentation.viewModel.home uses model.monthlyBudget, so a change to model.monthlyBudget can break oakane.presentation.viewModel.home, while a change to oakane.presentation.viewModel.home can't break model.monthlyBudget.
- Position
- Below the diagonal: oakane.presentation.viewModel.home uses a module listed above it, which is the healthy direction.
26→13 oakane.presentation.viewModel.home uses model.wallet✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.home uses a type in model.wallet.
- The types involved
com.kakapo.oakane.presentation.viewModel.home.HomeState→com.kakapo.model.wallet.WalletModel
- Direction
- oakane.presentation.viewModel.home uses model.wallet, so a change to model.wallet can break oakane.presentation.viewModel.home, while a change to oakane.presentation.viewModel.home can't break model.wallet.
- Position
- Below the diagonal: oakane.presentation.viewModel.home uses a module listed above it, which is the healthy direction.
26→16 oakane.presentation.viewModel.home uses data.repository.base✕
- Connections
- 5 pairs of types, where a type in oakane.presentation.viewModel.home uses a type in data.repository.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.home.HomeViewModel→com.kakapo.data.repository.base.GoalRepositorycom.kakapo.oakane.presentation.viewModel.home.HomeViewModel→com.kakapo.data.repository.base.SettingsRepositorycom.kakapo.oakane.presentation.viewModel.home.HomeViewModel→com.kakapo.data.repository.base.SystemRepositorycom.kakapo.oakane.presentation.viewModel.home.HomeViewModel→com.kakapo.data.repository.base.TransactionRepositorycom.kakapo.oakane.presentation.viewModel.home.HomeViewModel→com.kakapo.data.repository.base.WalletRepository
- Direction
- oakane.presentation.viewModel.home uses data.repository.base, so a change to data.repository.base can break oakane.presentation.viewModel.home, while a change to oakane.presentation.viewModel.home can't break data.repository.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.home uses a module listed above it, which is the healthy direction.
26→17 oakane.presentation.viewModel.home uses domain.usecase.base✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.home uses a type in domain.usecase.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.home.HomeViewModel→com.kakapo.domain.usecase.base.GetMonthlyBudgetOverviewUseCase
- Direction
- oakane.presentation.viewModel.home uses domain.usecase.base, so a change to domain.usecase.base can break oakane.presentation.viewModel.home, while a change to oakane.presentation.viewModel.home can't break domain.usecase.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.home uses a module listed above it, which is the healthy direction.
27→4 oakane.presentation.viewModel.main uses model.system✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.main uses a type in model.system.
- The types involved
com.kakapo.oakane.presentation.viewModel.main.MainState→com.kakapo.model.system.Theme
- Direction
- oakane.presentation.viewModel.main uses model.system, so a change to model.system can break oakane.presentation.viewModel.main, while a change to oakane.presentation.viewModel.main can't break model.system.
- Position
- Below the diagonal: oakane.presentation.viewModel.main uses a module listed above it, which is the healthy direction.
27→16 oakane.presentation.viewModel.main uses data.repository.base✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.main uses a type in data.repository.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.main.MainViewModel→com.kakapo.data.repository.base.SystemRepository
- Direction
- oakane.presentation.viewModel.main uses data.repository.base, so a change to data.repository.base can break oakane.presentation.viewModel.main, while a change to oakane.presentation.viewModel.main can't break data.repository.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.main uses a module listed above it, which is the healthy direction.
27→17 oakane.presentation.viewModel.main uses domain.usecase.base✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.main uses a type in domain.usecase.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.main.MainViewModel→com.kakapo.domain.usecase.base.ImportRecurringBudgetUseCase
- Direction
- oakane.presentation.viewModel.main uses domain.usecase.base, so a change to domain.usecase.base can break oakane.presentation.viewModel.main, while a change to oakane.presentation.viewModel.main can't break domain.usecase.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.main uses a module listed above it, which is the healthy direction.
28→4 oakane.presentation.viewModel.monthlyBudget uses model.system✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.monthlyBudget uses a type in model.system.
- The types involved
com.kakapo.oakane.presentation.viewModel.monthlyBudget.MonthlyBudgetState→com.kakapo.model.system.Theme
- Direction
- oakane.presentation.viewModel.monthlyBudget uses model.system, so a change to model.system can break oakane.presentation.viewModel.monthlyBudget, while a change to oakane.presentation.viewModel.monthlyBudget can't break model.system.
- Position
- Below the diagonal: oakane.presentation.viewModel.monthlyBudget uses a module listed above it, which is the healthy direction.
28→6 oakane.presentation.viewModel.monthlyBudget uses model.category✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.viewModel.monthlyBudget uses a type in model.category.
- The types involved
com.kakapo.oakane.presentation.viewModel.monthlyBudget.MonthlyBudgetState→com.kakapo.model.category.CategoryLimitModelcom.kakapo.oakane.presentation.viewModel.monthlyBudget.MonthlyBudgetState→com.kakapo.model.category.CategoryModel
- Direction
- oakane.presentation.viewModel.monthlyBudget uses model.category, so a change to model.category can break oakane.presentation.viewModel.monthlyBudget, while a change to oakane.presentation.viewModel.monthlyBudget can't break model.category.
- Position
- Below the diagonal: oakane.presentation.viewModel.monthlyBudget uses a module listed above it, which is the healthy direction.
28→10 oakane.presentation.viewModel.monthlyBudget uses model✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.monthlyBudget uses a type in model.
- The types involved
com.kakapo.oakane.presentation.viewModel.monthlyBudget.MonthlyBudgetState→com.kakapo.model.Currency
- Direction
- oakane.presentation.viewModel.monthlyBudget uses model, so a change to model can break oakane.presentation.viewModel.monthlyBudget, while a change to oakane.presentation.viewModel.monthlyBudget can't break model.
- Position
- Below the diagonal: oakane.presentation.viewModel.monthlyBudget uses a module listed above it, which is the healthy direction.
28→11 oakane.presentation.viewModel.monthlyBudget uses model.monthlyBudget✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.monthlyBudget uses a type in model.monthlyBudget.
- The types involved
com.kakapo.oakane.presentation.viewModel.monthlyBudget.MonthlyBudgetState→com.kakapo.model.monthlyBudget.MonthlyBudgetModel
- Direction
- oakane.presentation.viewModel.monthlyBudget uses model.monthlyBudget, so a change to model.monthlyBudget can break oakane.presentation.viewModel.monthlyBudget, while a change to oakane.presentation.viewModel.monthlyBudget can't break model.monthlyBudget.
- Position
- Below the diagonal: oakane.presentation.viewModel.monthlyBudget uses a module listed above it, which is the healthy direction.
28→14 oakane.presentation.viewModel.monthlyBudget uses data.model✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.viewModel.monthlyBudget uses a type in data.model.
- The types involved
com.kakapo.oakane.presentation.viewModel.monthlyBudget.MonthlyBudgetState→com.kakapo.data.model.MonthlyBudgetParamcom.kakapo.oakane.presentation.viewModel.monthlyBudget.MonthlyBudgetViewModel→com.kakapo.data.model.MonthlyBudgetParam
- Direction
- oakane.presentation.viewModel.monthlyBudget uses data.model, so a change to data.model can break oakane.presentation.viewModel.monthlyBudget, while a change to oakane.presentation.viewModel.monthlyBudget can't break data.model.
- Position
- Below the diagonal: oakane.presentation.viewModel.monthlyBudget uses a module listed above it, which is the healthy direction.
28→16 oakane.presentation.viewModel.monthlyBudget uses data.repository.base✕
- Connections
- 4 pairs of types, where a type in oakane.presentation.viewModel.monthlyBudget uses a type in data.repository.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.monthlyBudget.MonthlyBudgetViewModel→com.kakapo.data.repository.base.CategoryLimitRepositorycom.kakapo.oakane.presentation.viewModel.monthlyBudget.MonthlyBudgetViewModel→com.kakapo.data.repository.base.CategoryRepositorycom.kakapo.oakane.presentation.viewModel.monthlyBudget.MonthlyBudgetViewModel→com.kakapo.data.repository.base.MonthlyBudgetRepositorycom.kakapo.oakane.presentation.viewModel.monthlyBudget.MonthlyBudgetViewModel→com.kakapo.data.repository.base.SystemRepository
- Direction
- oakane.presentation.viewModel.monthlyBudget uses data.repository.base, so a change to data.repository.base can break oakane.presentation.viewModel.monthlyBudget, while a change to oakane.presentation.viewModel.monthlyBudget can't break data.repository.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.monthlyBudget uses a module listed above it, which is the healthy direction.
28→17 oakane.presentation.viewModel.monthlyBudget uses domain.usecase.base✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.viewModel.monthlyBudget uses a type in domain.usecase.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.monthlyBudget.MonthlyBudgetViewModel→com.kakapo.domain.usecase.base.SetRecurringBudgetUseCasecom.kakapo.oakane.presentation.viewModel.monthlyBudget.MonthlyBudgetViewModel→com.kakapo.domain.usecase.base.ValidateCategoryLimitUseCase
- Direction
- oakane.presentation.viewModel.monthlyBudget uses domain.usecase.base, so a change to domain.usecase.base can break oakane.presentation.viewModel.monthlyBudget, while a change to oakane.presentation.viewModel.monthlyBudget can't break domain.usecase.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.monthlyBudget uses a module listed above it, which is the healthy direction.
29→5 oakane.presentation.viewModel.onboarding uses oakane.presentation.model✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.onboarding uses a type in oakane.presentation.model.
- The types involved
com.kakapo.oakane.presentation.viewModel.onboarding.OnBoardingState→com.kakapo.oakane.presentation.model.OnBoardingContent
- Direction
- oakane.presentation.viewModel.onboarding uses oakane.presentation.model, so a change to oakane.presentation.model can break oakane.presentation.viewModel.onboarding, while a change to oakane.presentation.viewModel.onboarding can't break oakane.presentation.model.
- Position
- Below the diagonal: oakane.presentation.viewModel.onboarding uses a module listed above it, which is the healthy direction.
29→10 oakane.presentation.viewModel.onboarding uses model✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.viewModel.onboarding uses a type in model.
- The types involved
com.kakapo.oakane.presentation.viewModel.onboarding.OnBoardingState→com.kakapo.model.Currencycom.kakapo.oakane.presentation.viewModel.onboarding.OnBoardingViewModel→com.kakapo.model.Currency
- Direction
- oakane.presentation.viewModel.onboarding uses model, so a change to model can break oakane.presentation.viewModel.onboarding, while a change to oakane.presentation.viewModel.onboarding can't break model.
- Position
- Below the diagonal: oakane.presentation.viewModel.onboarding uses a module listed above it, which is the healthy direction.
29→16 oakane.presentation.viewModel.onboarding uses data.repository.base✕
- Connections
- 4 pairs of types, where a type in oakane.presentation.viewModel.onboarding uses a type in data.repository.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.onboarding.OnBoardingViewModel→com.kakapo.data.repository.base.BackupRepositorycom.kakapo.oakane.presentation.viewModel.onboarding.OnBoardingViewModel→com.kakapo.data.repository.base.SettingsRepositorycom.kakapo.oakane.presentation.viewModel.onboarding.OnBoardingViewModel→com.kakapo.data.repository.base.SystemRepositorycom.kakapo.oakane.presentation.viewModel.onboarding.OnBoardingViewModel→com.kakapo.data.repository.base.WalletRepository
- Direction
- oakane.presentation.viewModel.onboarding uses data.repository.base, so a change to data.repository.base can break oakane.presentation.viewModel.onboarding, while a change to oakane.presentation.viewModel.onboarding can't break data.repository.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.onboarding uses a module listed above it, which is the healthy direction.
30→3 oakane.presentation.viewModel.reminder uses model.reminder✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.viewModel.reminder uses a type in model.reminder.
- The types involved
com.kakapo.oakane.presentation.viewModel.reminder.ReminderState→com.kakapo.model.reminder.Remindercom.kakapo.oakane.presentation.viewModel.reminder.ReminderState→com.kakapo.model.reminder.ReminderDay
- Direction
- oakane.presentation.viewModel.reminder uses model.reminder, so a change to model.reminder can break oakane.presentation.viewModel.reminder, while a change to oakane.presentation.viewModel.reminder can't break model.reminder.
- Position
- Below the diagonal: oakane.presentation.viewModel.reminder uses a module listed above it, which is the healthy direction.
30→16 oakane.presentation.viewModel.reminder uses data.repository.base✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.reminder uses a type in data.repository.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.reminder.ReminderViewModel→com.kakapo.data.repository.base.SettingsRepository
- Direction
- oakane.presentation.viewModel.reminder uses data.repository.base, so a change to data.repository.base can break oakane.presentation.viewModel.reminder, while a change to oakane.presentation.viewModel.reminder can't break data.repository.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.reminder uses a module listed above it, which is the healthy direction.
31→4 oakane.presentation.viewModel.reports uses model.system✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.reports uses a type in model.system.
- The types involved
com.kakapo.oakane.presentation.viewModel.reports.ReportsState→com.kakapo.model.system.Theme
- Direction
- oakane.presentation.viewModel.reports uses model.system, so a change to model.system can break oakane.presentation.viewModel.reports, while a change to oakane.presentation.viewModel.reports can't break model.system.
- Position
- Below the diagonal: oakane.presentation.viewModel.reports uses a module listed above it, which is the healthy direction.
31→10 oakane.presentation.viewModel.reports uses model✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.reports uses a type in model.
- The types involved
com.kakapo.oakane.presentation.viewModel.reports.ReportsState→com.kakapo.model.Currency
- Direction
- oakane.presentation.viewModel.reports uses model, so a change to model can break oakane.presentation.viewModel.reports, while a change to oakane.presentation.viewModel.reports can't break model.
- Position
- Below the diagonal: oakane.presentation.viewModel.reports uses a module listed above it, which is the healthy direction.
31→11 oakane.presentation.viewModel.reports uses model.monthlyBudget✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.reports uses a type in model.monthlyBudget.
- The types involved
com.kakapo.oakane.presentation.viewModel.reports.ReportsState→com.kakapo.model.monthlyBudget.MonthlyBudgetOverView
- Direction
- oakane.presentation.viewModel.reports uses model.monthlyBudget, so a change to model.monthlyBudget can break oakane.presentation.viewModel.reports, while a change to oakane.presentation.viewModel.reports can't break model.monthlyBudget.
- Position
- Below the diagonal: oakane.presentation.viewModel.reports uses a module listed above it, which is the healthy direction.
31→12 oakane.presentation.viewModel.reports uses model.report✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.reports uses a type in model.report.
- The types involved
com.kakapo.oakane.presentation.viewModel.reports.ReportsState→com.kakapo.model.report.ReportModel
- Direction
- oakane.presentation.viewModel.reports uses model.report, so a change to model.report can break oakane.presentation.viewModel.reports, while a change to oakane.presentation.viewModel.reports can't break model.report.
- Position
- Below the diagonal: oakane.presentation.viewModel.reports uses a module listed above it, which is the healthy direction.
31→13 oakane.presentation.viewModel.reports uses model.wallet✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.viewModel.reports uses a type in model.wallet.
- The types involved
com.kakapo.oakane.presentation.viewModel.reports.ReportsState→com.kakapo.model.wallet.WalletItemModelcom.kakapo.oakane.presentation.viewModel.reports.ReportsViewModel→com.kakapo.model.wallet.WalletItemModel
- Direction
- oakane.presentation.viewModel.reports uses model.wallet, so a change to model.wallet can break oakane.presentation.viewModel.reports, while a change to oakane.presentation.viewModel.reports can't break model.wallet.
- Position
- Below the diagonal: oakane.presentation.viewModel.reports uses a module listed above it, which is the healthy direction.
31→16 oakane.presentation.viewModel.reports uses data.repository.base✕
- Connections
- 4 pairs of types, where a type in oakane.presentation.viewModel.reports uses a type in data.repository.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.reports.ReportsViewModel→com.kakapo.data.repository.base.ReportRepositorycom.kakapo.oakane.presentation.viewModel.reports.ReportsViewModel→com.kakapo.data.repository.base.SystemRepositorycom.kakapo.oakane.presentation.viewModel.reports.ReportsViewModel→com.kakapo.data.repository.base.TransactionRepositorycom.kakapo.oakane.presentation.viewModel.reports.ReportsViewModel→com.kakapo.data.repository.base.WalletRepository
- Direction
- oakane.presentation.viewModel.reports uses data.repository.base, so a change to data.repository.base can break oakane.presentation.viewModel.reports, while a change to oakane.presentation.viewModel.reports can't break data.repository.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.reports uses a module listed above it, which is the healthy direction.
31→17 oakane.presentation.viewModel.reports uses domain.usecase.base✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.reports uses a type in domain.usecase.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.reports.ReportsViewModel→com.kakapo.domain.usecase.base.GetMonthlyBudgetOverviewUseCase
- Direction
- oakane.presentation.viewModel.reports uses domain.usecase.base, so a change to domain.usecase.base can break oakane.presentation.viewModel.reports, while a change to oakane.presentation.viewModel.reports can't break domain.usecase.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.reports uses a module listed above it, which is the healthy direction.
32→4 oakane.presentation.viewModel.settings uses model.system✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.settings uses a type in model.system.
- The types involved
com.kakapo.oakane.presentation.viewModel.settings.SettingsState→com.kakapo.model.system.Theme
- Direction
- oakane.presentation.viewModel.settings uses model.system, so a change to model.system can break oakane.presentation.viewModel.settings, while a change to oakane.presentation.viewModel.settings can't break model.system.
- Position
- Below the diagonal: oakane.presentation.viewModel.settings uses a module listed above it, which is the healthy direction.
32→10 oakane.presentation.viewModel.settings uses model✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.viewModel.settings uses a type in model.
- The types involved
com.kakapo.oakane.presentation.viewModel.settings.SettingsState→com.kakapo.model.Currencycom.kakapo.oakane.presentation.viewModel.settings.SettingsViewModel→com.kakapo.model.Currency
- Direction
- oakane.presentation.viewModel.settings uses model, so a change to model can break oakane.presentation.viewModel.settings, while a change to oakane.presentation.viewModel.settings can't break model.
- Position
- Below the diagonal: oakane.presentation.viewModel.settings uses a module listed above it, which is the healthy direction.
32→16 oakane.presentation.viewModel.settings uses data.repository.base✕
- Connections
- 4 pairs of types, where a type in oakane.presentation.viewModel.settings uses a type in data.repository.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.settings.SettingsViewModel→com.kakapo.data.repository.base.BackupRepositorycom.kakapo.oakane.presentation.viewModel.settings.SettingsViewModel→com.kakapo.data.repository.base.BudgetRepositorycom.kakapo.oakane.presentation.viewModel.settings.SettingsViewModel→com.kakapo.data.repository.base.SettingsRepositorycom.kakapo.oakane.presentation.viewModel.settings.SettingsViewModel→com.kakapo.data.repository.base.SystemRepository
- Direction
- oakane.presentation.viewModel.settings uses data.repository.base, so a change to data.repository.base can break oakane.presentation.viewModel.settings, while a change to oakane.presentation.viewModel.settings can't break data.repository.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.settings uses a module listed above it, which is the healthy direction.
33→4 oakane.presentation.viewModel.termAndService uses model.system✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.termAndService uses a type in model.system.
- The types involved
com.kakapo.oakane.presentation.viewModel.termAndService.TermAndServiceState→com.kakapo.model.system.Theme
- Direction
- oakane.presentation.viewModel.termAndService uses model.system, so a change to model.system can break oakane.presentation.viewModel.termAndService, while a change to oakane.presentation.viewModel.termAndService can't break model.system.
- Position
- Below the diagonal: oakane.presentation.viewModel.termAndService uses a module listed above it, which is the healthy direction.
33→16 oakane.presentation.viewModel.termAndService uses data.repository.base✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.termAndService uses a type in data.repository.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.termAndService.TermAndServiceViewModel→com.kakapo.data.repository.base.SettingsRepository
- Direction
- oakane.presentation.viewModel.termAndService uses data.repository.base, so a change to data.repository.base can break oakane.presentation.viewModel.termAndService, while a change to oakane.presentation.viewModel.termAndService can't break data.repository.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.termAndService uses a module listed above it, which is the healthy direction.
34→4 oakane.presentation.viewModel.transaction uses model.system✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.transaction uses a type in model.system.
- The types involved
com.kakapo.oakane.presentation.viewModel.transaction.TransactionState→com.kakapo.model.system.Theme
- Direction
- oakane.presentation.viewModel.transaction uses model.system, so a change to model.system can break oakane.presentation.viewModel.transaction, while a change to oakane.presentation.viewModel.transaction can't break model.system.
- Position
- Below the diagonal: oakane.presentation.viewModel.transaction uses a module listed above it, which is the healthy direction.
34→8 oakane.presentation.viewModel.transaction uses model.transaction✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.transaction uses a type in model.transaction.
- The types involved
com.kakapo.oakane.presentation.viewModel.transaction.TransactionState→com.kakapo.model.transaction.TransactionModel
- Direction
- oakane.presentation.viewModel.transaction uses model.transaction, so a change to model.transaction can break oakane.presentation.viewModel.transaction, while a change to oakane.presentation.viewModel.transaction can't break model.transaction.
- Position
- Below the diagonal: oakane.presentation.viewModel.transaction uses a module listed above it, which is the healthy direction.
34→10 oakane.presentation.viewModel.transaction uses model✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.transaction uses a type in model.
- The types involved
com.kakapo.oakane.presentation.viewModel.transaction.TransactionState→com.kakapo.model.Currency
- Direction
- oakane.presentation.viewModel.transaction uses model, so a change to model can break oakane.presentation.viewModel.transaction, while a change to oakane.presentation.viewModel.transaction can't break model.
- Position
- Below the diagonal: oakane.presentation.viewModel.transaction uses a module listed above it, which is the healthy direction.
34→13 oakane.presentation.viewModel.transaction uses model.wallet✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.transaction uses a type in model.wallet.
- The types involved
com.kakapo.oakane.presentation.viewModel.transaction.TransactionState→com.kakapo.model.wallet.WalletModel
- Direction
- oakane.presentation.viewModel.transaction uses model.wallet, so a change to model.wallet can break oakane.presentation.viewModel.transaction, while a change to oakane.presentation.viewModel.transaction can't break model.wallet.
- Position
- Below the diagonal: oakane.presentation.viewModel.transaction uses a module listed above it, which is the healthy direction.
34→16 oakane.presentation.viewModel.transaction uses data.repository.base✕
- Connections
- 3 pairs of types, where a type in oakane.presentation.viewModel.transaction uses a type in data.repository.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.transaction.TransactionViewModel→com.kakapo.data.repository.base.SystemRepositorycom.kakapo.oakane.presentation.viewModel.transaction.TransactionViewModel→com.kakapo.data.repository.base.TransactionRepositorycom.kakapo.oakane.presentation.viewModel.transaction.TransactionViewModel→com.kakapo.data.repository.base.WalletRepository
- Direction
- oakane.presentation.viewModel.transaction uses data.repository.base, so a change to data.repository.base can break oakane.presentation.viewModel.transaction, while a change to oakane.presentation.viewModel.transaction can't break data.repository.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.transaction uses a module listed above it, which is the healthy direction.
34→17 oakane.presentation.viewModel.transaction uses domain.usecase.base✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.transaction uses a type in domain.usecase.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.transaction.TransactionViewModel→com.kakapo.domain.usecase.base.DeleteTransactionUseCase
- Direction
- oakane.presentation.viewModel.transaction uses domain.usecase.base, so a change to domain.usecase.base can break oakane.presentation.viewModel.transaction, while a change to oakane.presentation.viewModel.transaction can't break domain.usecase.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.transaction uses a module listed above it, which is the healthy direction.
35→4 oakane.presentation.viewModel.transactions uses model.system✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.transactions uses a type in model.system.
- The types involved
com.kakapo.oakane.presentation.viewModel.transactions.TransactionsState→com.kakapo.model.system.Theme
- Direction
- oakane.presentation.viewModel.transactions uses model.system, so a change to model.system can break oakane.presentation.viewModel.transactions, while a change to oakane.presentation.viewModel.transactions can't break model.system.
- Position
- Below the diagonal: oakane.presentation.viewModel.transactions uses a module listed above it, which is the healthy direction.
35→6 oakane.presentation.viewModel.transactions uses model.category✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.viewModel.transactions uses a type in model.category.
- The types involved
com.kakapo.oakane.presentation.viewModel.transactions.TransactionsState→com.kakapo.model.category.CategoryModelcom.kakapo.oakane.presentation.viewModel.transactions.TransactionsViewModel→com.kakapo.model.category.CategoryModel
- Direction
- oakane.presentation.viewModel.transactions uses model.category, so a change to model.category can break oakane.presentation.viewModel.transactions, while a change to oakane.presentation.viewModel.transactions can't break model.category.
- Position
- Below the diagonal: oakane.presentation.viewModel.transactions uses a module listed above it, which is the healthy direction.
35→8 oakane.presentation.viewModel.transactions uses model.transaction✕
- Connections
- 4 pairs of types, where a type in oakane.presentation.viewModel.transactions uses a type in model.transaction.
- The types involved
com.kakapo.oakane.presentation.viewModel.transactions.TransactionsState→com.kakapo.model.transaction.TransactionModelcom.kakapo.oakane.presentation.viewModel.transactions.TransactionsState→com.kakapo.model.transaction.TransactionTypecom.kakapo.oakane.presentation.viewModel.transactions.TransactionsViewModel→com.kakapo.model.transaction.TransactionModelcom.kakapo.oakane.presentation.viewModel.transactions.TransactionsViewModel→com.kakapo.model.transaction.TransactionType
- Direction
- oakane.presentation.viewModel.transactions uses model.transaction, so a change to model.transaction can break oakane.presentation.viewModel.transactions, while a change to oakane.presentation.viewModel.transactions can't break model.transaction.
- Position
- Below the diagonal: oakane.presentation.viewModel.transactions uses a module listed above it, which is the healthy direction.
35→16 oakane.presentation.viewModel.transactions uses data.repository.base✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.viewModel.transactions uses a type in data.repository.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.transactions.TransactionsViewModel→com.kakapo.data.repository.base.SystemRepositorycom.kakapo.oakane.presentation.viewModel.transactions.TransactionsViewModel→com.kakapo.data.repository.base.TransactionRepository
- Direction
- oakane.presentation.viewModel.transactions uses data.repository.base, so a change to data.repository.base can break oakane.presentation.viewModel.transactions, while a change to oakane.presentation.viewModel.transactions can't break data.repository.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.transactions uses a module listed above it, which is the healthy direction.
36→4 oakane.presentation.viewModel.wallet uses model.system✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.wallet uses a type in model.system.
- The types involved
com.kakapo.oakane.presentation.viewModel.wallet.WalletState→com.kakapo.model.system.Theme
- Direction
- oakane.presentation.viewModel.wallet uses model.system, so a change to model.system can break oakane.presentation.viewModel.wallet, while a change to oakane.presentation.viewModel.wallet can't break model.system.
- Position
- Below the diagonal: oakane.presentation.viewModel.wallet uses a module listed above it, which is the healthy direction.
36→13 oakane.presentation.viewModel.wallet uses model.wallet✕
- Connections
- 6 pairs of types, where a type in oakane.presentation.viewModel.wallet uses a type in model.wallet.
- The types involved
com.kakapo.oakane.presentation.viewModel.wallet.WalletState→com.kakapo.model.wallet.FilterWalletLogByCategorycom.kakapo.oakane.presentation.viewModel.wallet.WalletState→com.kakapo.model.wallet.FilterWalletLogByDateModelcom.kakapo.oakane.presentation.viewModel.wallet.WalletState→com.kakapo.model.wallet.WalletItemModelcom.kakapo.oakane.presentation.viewModel.wallet.WalletState→com.kakapo.model.wallet.WalletLogItemcom.kakapo.oakane.presentation.viewModel.wallet.WalletState→com.kakapo.model.wallet.WalletModelcom.kakapo.oakane.presentation.viewModel.wallet.WalletViewModel→com.kakapo.model.wallet.WalletLogItem
- Direction
- oakane.presentation.viewModel.wallet uses model.wallet, so a change to model.wallet can break oakane.presentation.viewModel.wallet, while a change to oakane.presentation.viewModel.wallet can't break model.wallet.
- Position
- Below the diagonal: oakane.presentation.viewModel.wallet uses a module listed above it, which is the healthy direction.
36→14 oakane.presentation.viewModel.wallet uses data.model✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.wallet uses a type in data.model.
- The types involved
com.kakapo.oakane.presentation.viewModel.wallet.WalletState→com.kakapo.data.model.WalletTransferParam
- Direction
- oakane.presentation.viewModel.wallet uses data.model, so a change to data.model can break oakane.presentation.viewModel.wallet, while a change to oakane.presentation.viewModel.wallet can't break data.model.
- Position
- Below the diagonal: oakane.presentation.viewModel.wallet uses a module listed above it, which is the healthy direction.
36→16 oakane.presentation.viewModel.wallet uses data.repository.base✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.viewModel.wallet uses a type in data.repository.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.wallet.WalletViewModel→com.kakapo.data.repository.base.SystemRepositorycom.kakapo.oakane.presentation.viewModel.wallet.WalletViewModel→com.kakapo.data.repository.base.WalletRepository
- Direction
- oakane.presentation.viewModel.wallet uses data.repository.base, so a change to data.repository.base can break oakane.presentation.viewModel.wallet, while a change to oakane.presentation.viewModel.wallet can't break data.repository.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.wallet uses a module listed above it, which is the healthy direction.
36→17 oakane.presentation.viewModel.wallet uses domain.usecase.base✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.viewModel.wallet uses a type in domain.usecase.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.wallet.WalletViewModel→com.kakapo.domain.usecase.base.MoveWalletBalanceUseCasecom.kakapo.oakane.presentation.viewModel.wallet.WalletViewModel→com.kakapo.domain.usecase.base.WalletLogItemsUseCase
- Direction
- oakane.presentation.viewModel.wallet uses domain.usecase.base, so a change to domain.usecase.base can break oakane.presentation.viewModel.wallet, while a change to oakane.presentation.viewModel.wallet can't break domain.usecase.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.wallet uses a module listed above it, which is the healthy direction.
37→4 oakane.presentation.viewModel.wallets uses model.system✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.wallets uses a type in model.system.
- The types involved
com.kakapo.oakane.presentation.viewModel.wallets.WalletsState→com.kakapo.model.system.Theme
- Direction
- oakane.presentation.viewModel.wallets uses model.system, so a change to model.system can break oakane.presentation.viewModel.wallets, while a change to oakane.presentation.viewModel.wallets can't break model.system.
- Position
- Below the diagonal: oakane.presentation.viewModel.wallets uses a module listed above it, which is the healthy direction.
37→10 oakane.presentation.viewModel.wallets uses model✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.wallets uses a type in model.
- The types involved
com.kakapo.oakane.presentation.viewModel.wallets.WalletsState→com.kakapo.model.Currency
- Direction
- oakane.presentation.viewModel.wallets uses model, so a change to model can break oakane.presentation.viewModel.wallets, while a change to oakane.presentation.viewModel.wallets can't break model.
- Position
- Below the diagonal: oakane.presentation.viewModel.wallets uses a module listed above it, which is the healthy direction.
37→13 oakane.presentation.viewModel.wallets uses model.wallet✕
- Connections
- 1 pair of types, where a type in oakane.presentation.viewModel.wallets uses a type in model.wallet.
- The types involved
com.kakapo.oakane.presentation.viewModel.wallets.WalletsState→com.kakapo.model.wallet.WalletItemModel
- Direction
- oakane.presentation.viewModel.wallets uses model.wallet, so a change to model.wallet can break oakane.presentation.viewModel.wallets, while a change to oakane.presentation.viewModel.wallets can't break model.wallet.
- Position
- Below the diagonal: oakane.presentation.viewModel.wallets uses a module listed above it, which is the healthy direction.
37→16 oakane.presentation.viewModel.wallets uses data.repository.base✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.viewModel.wallets uses a type in data.repository.base.
- The types involved
com.kakapo.oakane.presentation.viewModel.wallets.WalletsViewModel→com.kakapo.data.repository.base.SystemRepositorycom.kakapo.oakane.presentation.viewModel.wallets.WalletsViewModel→com.kakapo.data.repository.base.WalletRepository
- Direction
- oakane.presentation.viewModel.wallets uses data.repository.base, so a change to data.repository.base can break oakane.presentation.viewModel.wallets, while a change to oakane.presentation.viewModel.wallets can't break data.repository.base.
- Position
- Below the diagonal: oakane.presentation.viewModel.wallets uses a module listed above it, which is the healthy direction.
38→4 oakane.presentation.feature.goal.component uses model.system✕
- Connections
- 1 pair of types, where a type in oakane.presentation.feature.goal.component uses a type in model.system.
- The types involved
com.kakapo.oakane.presentation.feature.goal.component.GoalSavingItemViewKt→com.kakapo.model.system.Theme
- Direction
- oakane.presentation.feature.goal.component uses model.system, so a change to model.system can break oakane.presentation.feature.goal.component, while a change to oakane.presentation.feature.goal.component can't break model.system.
- Position
- Below the diagonal: oakane.presentation.feature.goal.component uses a module listed above it, which is the healthy direction.
38→9 oakane.presentation.feature.goal.component uses model.goal✕
- Connections
- 1 pair of types, where a type in oakane.presentation.feature.goal.component uses a type in model.goal.
- The types involved
com.kakapo.oakane.presentation.feature.goal.component.GoalSavingItemViewKt→com.kakapo.model.goal.GoalSavingModel
- Direction
- oakane.presentation.feature.goal.component uses model.goal, so a change to model.goal can break oakane.presentation.feature.goal.component, while a change to oakane.presentation.feature.goal.component can't break model.goal.
- Position
- Below the diagonal: oakane.presentation.feature.goal.component uses a module listed above it, which is the healthy direction.
38→10 oakane.presentation.feature.goal.component uses model✕
- Connections
- 1 pair of types, where a type in oakane.presentation.feature.goal.component uses a type in model.
- The types involved
com.kakapo.oakane.presentation.feature.goal.component.GoalSavingItemViewKt→com.kakapo.model.Currency
- Direction
- oakane.presentation.feature.goal.component uses model, so a change to model can break oakane.presentation.feature.goal.component, while a change to oakane.presentation.feature.goal.component can't break model.
- Position
- Below the diagonal: oakane.presentation.feature.goal.component uses a module listed above it, which is the healthy direction.
38→24 oakane.presentation.feature.goal.component uses oakane.presentation.viewModel.goal✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.feature.goal.component uses a type in oakane.presentation.viewModel.goal.
- The types involved
com.kakapo.oakane.presentation.feature.goal.component.DialogGoalViewKt→com.kakapo.oakane.presentation.viewModel.goal.GoalEventcom.kakapo.oakane.presentation.feature.goal.component.DialogGoalViewKt→com.kakapo.oakane.presentation.viewModel.goal.GoalState
- Direction
- oakane.presentation.feature.goal.component uses oakane.presentation.viewModel.goal, so a change to oakane.presentation.viewModel.goal can break oakane.presentation.feature.goal.component, while a change to oakane.presentation.feature.goal.component can't break oakane.presentation.viewModel.goal.
- Position
- Below the diagonal: oakane.presentation.feature.goal.component uses a module listed above it, which is the healthy direction.
39→4 oakane.presentation.feature.home.component uses model.system✕
- Connections
- 1 pair of types, where a type in oakane.presentation.feature.home.component uses a type in model.system.
- The types involved
com.kakapo.oakane.presentation.feature.home.component.GoalHeaderViewKt→com.kakapo.model.system.Theme
- Direction
- oakane.presentation.feature.home.component uses model.system, so a change to model.system can break oakane.presentation.feature.home.component, while a change to oakane.presentation.feature.home.component can't break model.system.
- Position
- Below the diagonal: oakane.presentation.feature.home.component uses a module listed above it, which is the healthy direction.
39→8 oakane.presentation.feature.home.component uses model.transaction✕
- Connections
- 1 pair of types, where a type in oakane.presentation.feature.home.component uses a type in model.transaction.
- The types involved
com.kakapo.oakane.presentation.feature.home.component.BalanceItemViewKt→com.kakapo.model.transaction.TransactionType
- Direction
- oakane.presentation.feature.home.component uses model.transaction, so a change to model.transaction can break oakane.presentation.feature.home.component, while a change to oakane.presentation.feature.home.component can't break model.transaction.
- Position
- Below the diagonal: oakane.presentation.feature.home.component uses a module listed above it, which is the healthy direction.
39→10 oakane.presentation.feature.home.component uses model✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.feature.home.component uses a type in model.
- The types involved
com.kakapo.oakane.presentation.feature.home.component.BalanceItemViewKt→com.kakapo.model.Currencycom.kakapo.oakane.presentation.feature.home.component.MonthlyBudgetViewKt→com.kakapo.model.Currency
- Direction
- oakane.presentation.feature.home.component uses model, so a change to model can break oakane.presentation.feature.home.component, while a change to oakane.presentation.feature.home.component can't break model.
- Position
- Below the diagonal: oakane.presentation.feature.home.component uses a module listed above it, which is the healthy direction.
39→11 oakane.presentation.feature.home.component uses model.monthlyBudget✕
- Connections
- 1 pair of types, where a type in oakane.presentation.feature.home.component uses a type in model.monthlyBudget.
- The types involved
com.kakapo.oakane.presentation.feature.home.component.MonthlyBudgetViewKt→com.kakapo.model.monthlyBudget.MonthlyBudgetOverView
- Direction
- oakane.presentation.feature.home.component uses model.monthlyBudget, so a change to model.monthlyBudget can break oakane.presentation.feature.home.component, while a change to oakane.presentation.feature.home.component can't break model.monthlyBudget.
- Position
- Below the diagonal: oakane.presentation.feature.home.component uses a module listed above it, which is the healthy direction.
39→26 oakane.presentation.feature.home.component uses oakane.presentation.viewModel.home✕
- Connections
- 4 pairs of types, where a type in oakane.presentation.feature.home.component uses a type in oakane.presentation.viewModel.home.
- The types involved
com.kakapo.oakane.presentation.feature.home.component.MonthlyBudgetViewKt→com.kakapo.oakane.presentation.viewModel.home.HomeEventcom.kakapo.oakane.presentation.feature.home.component.MonthlyBudgetViewKt→com.kakapo.oakane.presentation.viewModel.home.HomeStatecom.kakapo.oakane.presentation.feature.home.component.PrimaryWalletViewKt→com.kakapo.oakane.presentation.viewModel.home.HomeEventcom.kakapo.oakane.presentation.feature.home.component.PrimaryWalletViewKt→com.kakapo.oakane.presentation.viewModel.home.HomeState
- Direction
- oakane.presentation.feature.home.component uses oakane.presentation.viewModel.home, so a change to oakane.presentation.viewModel.home can break oakane.presentation.feature.home.component, while a change to oakane.presentation.feature.home.component can't break oakane.presentation.viewModel.home.
- Position
- Below the diagonal: oakane.presentation.feature.home.component uses a module listed above it, which is the healthy direction.
40→4 oakane.presentation.feature.reports.component uses model.system✕
- Connections
- 2 pairs of types, where a type in oakane.presentation.feature.reports.component uses a type in model.system.
- The types involved
com.kakapo.oakane.presentation.feature.reports.component.DonutChartComponentViewKt→com.kakapo.model.system.Themecom.kakapo.oakane.presentation.feature.reports.component.ReportsItemViewKt→com.kakapo.model.system.Theme
- Direction
- oakane.presentation.feature.reports.component uses model.system, so a change to model.system can break oakane.presentation.feature.reports.component, while a change to oakane.presentation.feature.reports.component can't break model.system.
- Position
- Below the diagonal: oakane.presentation.feature.reports.component uses a module listed above it, which is the healthy direction.
40→10 oakane.presentation.feature.reports.component uses model✕
- Connections
- 1 pair of types, where a type in oakane.presentation.feature.reports.component uses a type in model.
- The types involved
com.kakapo.oakane.presentation.feature.reports.component.DonutChartComponentViewKt→com.kakapo.model.Currency
- Direction
- oakane.presentation.feature.reports.component uses model, so a change to model can break oakane.presentation.feature.reports.component, while a change to oakane.presentation.feature.reports.component can't break model.
- Position
- Below the diagonal: oakane.presentation.feature.reports.component uses a module listed above it, which is the healthy direction.
40→11 oakane.presentation.feature.reports.component uses model.monthlyBudget✕
- Connections
- 1 pair of types, where a type in oakane.presentation.feature.reports.component uses a type in model.monthlyBudget.
- The types involved
com.kakapo.oakane.presentation.feature.reports.component.BudgetContentViewKt→com.kakapo.model.monthlyBudget.MonthlyBudgetOverView
- Direction
- oakane.presentation.feature.reports.component uses model.monthlyBudget, so a change to model.monthlyBudget can break oakane.presentation.feature.reports.component, while a change to oakane.presentation.feature.reports.component can't break model.monthlyBudget.
- Position
- Below the diagonal: oakane.presentation.feature.reports.component uses a module listed above it, which is the healthy direction.
40→12 oakane.presentation.feature.reports.component uses model.report✕
- Connections
- 1 pair of types, where a type in oakane.presentation.feature.reports.component uses a type in model.report.
- The types involved
com.kakapo.oakane.presentation.feature.reports.component.ReportsItemViewKt→com.kakapo.model.report.ReportModel
- Direction
- oakane.presentation.feature.reports.component uses model.report, so a change to model.report can break oakane.presentation.feature.reports.component, while a change to oakane.presentation.feature.reports.component can't break model.report.
- Position
- Below the diagonal: oakane.presentation.feature.reports.component uses a module listed above it, which is the healthy direction.
40→31 oakane.presentation.feature.reports.component uses oakane.presentation.viewModel.reports✕
- Connections
- 3 pairs of types, where a type in oakane.presentation.feature.reports.component uses a type in oakane.presentation.viewModel.reports.
- The types involved
com.kakapo.oakane.presentation.feature.reports.component.BudgetContentViewKt→com.kakapo.oakane.presentation.viewModel.reports.ReportsStatecom.kakapo.oakane.presentation.feature.reports.component.ButtonFilterViewKt→com.kakapo.oakane.presentation.viewModel.reports.ReportsEventcom.kakapo.oakane.presentation.feature.reports.component.ButtonFilterViewKt→com.kakapo.oakane.presentation.viewModel.reports.ReportsState
- Direction
- oakane.presentation.feature.reports.component uses oakane.presentation.viewModel.reports, so a change to oakane.presentation.viewModel.reports can break oakane.presentation.feature.reports.component, while a change to oakane.presentation.feature.reports.component can't break oakane.presentation.viewModel.reports.
- Position
- Below the diagonal: oakane.presentation.feature.reports.component 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
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality; Resolve the 150 Orphaned file finding(s) in Knowledge Freshness — start with AddTransactionScreen.kt, SettingsScreen.kt, Theme.kt; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +11.3 pts | Low | ADR Quality |
| Resolve the 150 Orphaned file finding(s) in Knowledge Freshness — start with AddTransactionScreen.kt, SettingsScreen.kt, Theme.kt. | +11.2 pts | High | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +7.7 pts | Medium | Architecture documentation |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +5.6 pts | Medium | CI/CD gates |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +5.6 pts | Medium | Observability |
| Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery). | +2.6 pts | Medium | DR & Backup |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.1 pts | Medium | Release Hygiene |
| Swallowed exception (caught, then discarded) | +1.2 pts | Medium | Exception handling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/navigation/HomeNavigation.kt | 5.5 | Mixed | Change Coupling: Boundary-crossing change coupling: HomeNavigation.kt ↔ HomeViewContract.kt |
| composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/GoalItemView.kt | 6.2 | Mixed | Change Coupling: Boundary-crossing change coupling: GoalItemView.kt ↔ CommonModule.kt |
| composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/onboarding/content/createWallet/CreateWalletView.kt | 6.2 | Mixed | Change Coupling: Boundary-crossing change coupling: CreateWalletView.kt ↔ OnBoardingViewModel.kt |
| composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/onboarding/OnBoardingScreen.kt | 7.0 | Mixed | Code Duplication: Duplicated block (10 lines × 2) |
| composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/category/CategoryItemView.kt | 7.0 | Mixed | Change Coupling: Boundary-crossing change coupling: CategoryItemView.kt ↔ CategoriesViewModel.kt |
| core/common/src/androidMain/kotlin/com/kakapo/common/FileUtils.kt | 7.8 | Mixed | Cognitive Complexity: FileUtilsKt.getImageUriFromFileName (cognitive 16) |
| iosApp/iosApp/screen/addGoal/AddGoalViewModel.swift | 7.8 | Mixed | Code Duplication: Duplicated block (8 lines × 2) |
| iosApp/iosApp/screen/goal/GoalViewModel.swift | 7.8 | Mixed | Code Duplication: Duplicated block (8 lines × 4) |
| core/data/src/commonMain/kotlin/com/kakapo/data/repository/base/TransactionRepository.kt | 7.8 | Mixed | Change Coupling: Change coupling: TransactionRepository.kt ↔ TransactionLocalDatasource.kt |
| composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/transactions/component/TransactionsTopAppBarView.kt | 8.0 | Near-clean | Change Coupling: Boundary-crossing change coupling: TransactionsTopAppBarView.kt ↔ TransactionsViewModel.kt |
| composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/component/PrimaryWalletView.kt | 8.0 | Near-clean | Change Coupling: Boundary-crossing change coupling: PrimaryWalletView.kt ↔ HomeViewModel.kt |
| composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/sheet/SelectIconVIew.kt | 8.0 | Near-clean | Change Coupling: Boundary-crossing change coupling: SelectIconVIew.kt ↔ CategoriesViewContract.kt |
| composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/component/MonthlyBudgetView.kt | 8.0 | Near-clean | Change Coupling: Boundary-crossing change coupling: MonthlyBudgetView.kt ↔ HomeViewModel.kt |
| composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/CategoriesSheetView.kt | 8.0 | Near-clean | Change Coupling: Boundary-crossing change coupling: CategoriesSheetView.kt ↔ CategoriesViewModel.kt |
| composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/wallet/PrimaryWalletIcon.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/addGoal/component/ImageGoalPicker.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
| core/database/src/commonMain/kotlin/com/kakapo/database/model/TransactionEntity.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (16–17 lines × 2) |
| composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/addTransaction/component/SelectCategorySheet.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (11 lines × 2) |
| composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/reports/component/ButtonFilterView.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (11 lines × 2) |
| core/data/src/commonMain/kotlin/com/kakapo/data/model/MonthlyBudgetMapper.kt | 8.5 | Near-clean | Code Duplication: Duplicated block (9 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 59 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 59 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, 208 of 222 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.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — a Gradle build resolved 634 artifact(s) across its subprojects (314 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 639 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.
- 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- 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.
- D27 Navigability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Tracing effort is measured over resolved call sites, and all 605 sampled here came from .kt files. This repository's .swift source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `iosApp/iosApp/designSystem/component/button/FabButtonView.swift`, `iosApp/iosApp/designSystem/component/button/FilledButtonView.swift`, `iosApp/iosApp/designSystem/component/button/FilledContentButtonView.swift`, `iosApp/iosApp/designSystem/component/button/IconButtonView.swift`, `iosApp/iosApp/designSystem/component/button/InputChipView.swift`, … (+84 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.
- AX1 Captive dependencies — 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 Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Koin, whose lifetimes are not modelled 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.
- 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 (iosApp/oakane.xcodeproj/project.pbxproj). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C1 Data Protection — 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 personal data 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 personal data controls.
- 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.
- C3 Audit Trail — 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 audit 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 audit controls.
- C4 Data Retention — 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 retention 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 retention controls.
- C5 Data-Subject Rights — 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 data-subject rights 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 data-subject rights 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, Swift 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, Swift 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.
- 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.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- 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.
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15. A further 5 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being CategoryIconMapperKt.asIcon at 49 — they are counted neither in the figure above nor in this dimension's score. 5 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/model/CategoryIconMapper.kt (CategoryIconMapperKt.asIcon at 49), iosApp/iosApp/designSystem/model/CategoryIconMapper.swift (CategoryIconName.asIconCategory at 49), iosApp/iosApp/main/ContentView.swift (ContentView.ScreenContent at 18), shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt (AddTransactionViewModel.handleEvent at 18), shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt (CategoriesViewModel.handleEvent at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was FileUtilsKt.getImageUriFromFileName at 16.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with FileUtilsKt.getImageUriFromFileName (cognitive 16). — Refactoring it lifts Cognitive Complexity from 9.9 to about 10.0/10.
- Stand up a CI pipeline, then gate Cognitive Complexity 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.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
20 duplicated block group(s) detected.
What to do
- Resolve the 4 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with MonthlyBudgetMapper.kt, AddTransactionViewModel.kt, GoalViewModel.kt. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with AddGoalViewModel.swift (2), HomeScreen.swift, TransactionViewModel.swift. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with SelectCategorySheet.kt, ButtonFilterView.kt. — One of this dimension's main actionable groups (2 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
10 production modules (Gradle), 0 dependency cycle(s), 1 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; 4 module(s) off the main sequence.
What to do
- Resolve the 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Unstable project Oakane finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Stand up a CI pipeline, then gate Coupling 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.
D6 · Cohesion (LCOM4)
0 of 53 classes have LCOM4 above 3.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Java/Kotlin (repository root, Gradle): measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 25 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 11 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 9 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 26 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
Top hotspots: iosApp/iosApp/main/ContentView.swift (16×18=288); shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt (14×18=252)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with ContentView.swift, AddTransactionViewModel.kt. — One of this dimension's main actionable groups (2 warning-level).
D17 · Explicit Debt
4 deducted task-comment markers across 28120 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 4 TodoComment finding(s) in Explicit Debt — start with PrimaryWalletIcon.kt, GoalItemView.kt, CreateWalletView.kt. — One of this dimension's main actionable groups (4 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. 1 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
2 of 10 build units (Gradle, Xcode) 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).
D27 · Navigability
27 % of calls cross a namespace and 26 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated. Measured over the .kt source only — this repository's .swift was not sampled for call sites, so this score covers part of the tree, not all of it.
What to do
- Improve Navigability — currently 8.7/10. — 27 % of calls cross a namespace and 26 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated. Measured over the .kt source only — this repository's .swift was not sampled for call sites, so this score covers part of the tree, not all of it.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues. semgrep hit a parse error in 1 file(s) — `gradlew` (line 72, line 178) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
150 of 150 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/addTransaction/AddTransactionScreen.kt. Counted over 150 of the 516 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 150 Orphaned file finding(s) in Knowledge Freshness — start with AddTransactionScreen.kt, SettingsScreen.kt, Theme.kt. — One of this dimension's main actionable groups (150 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: HomeScreen.kt↔HomeNavigation.kt 92%; WalletRepositoryImpl.kt↔WalletLocalDatasourceImpl.kt 90%; HomeNavigation.kt↔OakaneNavigation.kt 83%
What to do
- Resolve the 11 Boundary-crossing change coupling finding(s) in Change Coupling — start with HomeNavigation.kt (2), CategoryItemView.kt (2), TransactionsTopAppBarView.kt. — One of this dimension's main actionable groups (11 issue-level).
- Resolve the 15 Change coupling finding(s) in Change Coupling — start with TransactionRepository.kt (2), HomeScreen.kt, WalletRepositoryImpl.kt. — One of this dimension's main actionable groups (15 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 3 platform declaration(s) and 51 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
DM10 · One transaction, one aggregate
- `MoveWalletBalanceUseCaseImpl.execute` saves `WalletTransferParam`, `Double` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — core/domain/src/commonMain/kotlin/com/kakapo/domain/usecase/impl/MoveWalletBalanceUseCaseImpl.kt:18
- `SaveTransactionUseCaseImpl.execute` saves `Double`, `TransactionParam` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — core/domain/src/commonMain/kotlin/com/kakapo/domain/usecase/impl/SaveTransactionUseCaseImpl.kt:17
- `UpdateTransactionUseCaseImpl.executed` saves `TransactionParam`, `Double` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — core/domain/src/commonMain/kotlin/com/kakapo/domain/usecase/impl/UpdateTransactionUseCaseImpl.kt:20
What to do
- Mutate one aggregate per operation and let the others follow from a domain event — the second aggregate reaching consistency a moment later is the design, not a compromise.
DM12 · Ambient inputs in the domain
DM6 · Domain ↔ infrastructure boundary
M1 · Documentation (README)
What to do
- Add a README to the 9 of 9 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
- 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.
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
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.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
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
- `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — core/common/src/commonMain/kotlin/com/kakapo/common/StringExt.kt:36
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 86% | Strong | Solid. |
| Architecture | 92% | Exemplary | Solid. |
| Maturity | 46% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 21% | Critical — gated by P1, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 100% | Checked 3 of 9 | Strongest area. |
| Domain Modelling | 95% | Exemplary | Solid. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit 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 audit 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.
- C4 Data Retention — Not assessed: these retention 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 retention 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.
- C5 Data-Subject Rights — Not assessed: these data-subject rights 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 data-subject rights 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.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
Not included — 66 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 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
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: these personal data 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 personal data 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.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~193 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.
- D12 Dependency Hygiene — Not scored — a Gradle build resolved 634 artifact(s) across its subprojects (314 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — 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.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Kotlin, Swift 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, .swift, 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
- 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) — 89 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.
- 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
- DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
- 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
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — no CI workflow found
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, Swift 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 — 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
- 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.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 11 finding(s)
- Boundary-crossing change coupling: HomeNavigation.kt ↔ HomeViewContract.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/navigation/HomeNavigation.kt:1
- Boundary-crossing change coupling: HomeNavigation.kt ↔ HomeViewModel.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/navigation/HomeNavigation.kt:1
- Boundary-crossing change coupling: CategoryItemView.kt ↔ CategoriesViewModel.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/category/CategoryItemView.kt:1
- Boundary-crossing change coupling: TransactionsTopAppBarView.kt ↔ TransactionsViewModel.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/transactions/component/TransactionsTopAppBarView.kt:1
- Boundary-crossing change coupling: PrimaryWalletView.kt ↔ HomeViewModel.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/component/PrimaryWalletView.kt:1
- Boundary-crossing change coupling: CreateWalletView.kt ↔ OnBoardingViewModel.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/onboarding/content/createWallet/CreateWalletView.kt:1
- Boundary-crossing change coupling: GoalItemView.kt ↔ CommonModule.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/GoalItemView.kt:1
- Boundary-crossing change coupling: CategoryItemView.kt ↔ CategoriesViewContract.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/category/CategoryItemView.kt:1
- Boundary-crossing change coupling: SelectIconVIew.kt ↔ CategoriesViewContract.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/sheet/SelectIconVIew.kt:1
- Boundary-crossing change coupling: MonthlyBudgetView.kt ↔ HomeViewModel.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/component/MonthlyBudgetView.kt:1
- Boundary-crossing change coupling: CategoriesSheetView.kt ↔ CategoriesViewModel.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/CategoriesSheetView.kt:1
Serious — 52 finding(s)
- Change coupling: HomeScreen.kt ↔ HomeNavigation.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/HomeScreen.kt:1
- Change coupling: WalletRepositoryImpl.kt ↔ WalletLocalDatasourceImpl.kt core/data/src/commonMain/kotlin/com/kakapo/data/repository/impl/WalletRepositoryImpl.kt:1
- Change coupling: HomeNavigation.kt ↔ OakaneNavigation.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/navigation/HomeNavigation.kt:1
- Change coupling: WalletRepository.kt ↔ WalletLocalDatasourceImpl.kt core/data/src/commonMain/kotlin/com/kakapo/data/repository/base/WalletRepository.kt:1
- Change coupling: TransactionRepository.kt ↔ TransactionLocalDatasource.kt core/data/src/commonMain/kotlin/com/kakapo/data/repository/base/TransactionRepository.kt:1
- Change coupling: MonthlyBudgetRepositoryImpl.kt ↔ MonthlyBudgetViewModel.kt core/data/src/commonMain/kotlin/com/kakapo/data/repository/impl/MonthlyBudgetRepositoryImpl.kt:1
- Change coupling: CreateWalletSheetView.swift ↔ WalletsScreen.swift iosApp/iosApp/designSystem/ui/sheet/CreateWalletSheetView.swift:1
- Change coupling: TransactionRepository.kt ↔ TransactionLocalDatasourceImpl.kt core/data/src/commonMain/kotlin/com/kakapo/data/repository/base/TransactionRepository.kt:1
- Change coupling: TransactionRepositoryImpl.kt ↔ TransactionLocalDatasourceImpl.kt core/data/src/commonMain/kotlin/com/kakapo/data/repository/impl/TransactionRepositoryImpl.kt:1
- Change coupling: OnBoardingScreen.kt ↔ CreateWalletView.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/onboarding/OnBoardingScreen.kt:1
- Change coupling: MainActivity.kt ↔ OakaneNavigation.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/MainActivity.kt:1
- Change coupling: CreateCategoryContentView.kt ↔ SelectIconVIew.kt composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/sheet/CreateCategoryContentView.kt:1
- Change coupling: WalletMapper.kt ↔ WalletRepositoryImpl.kt core/data/src/commonMain/kotlin/com/kakapo/data/model/WalletMapper.kt:1
- Change coupling: MySqlDriverFactory.kt ↔ CommonModule.kt core/database/src/androidMain/kotlin/com/kakapo/database/MySqlDriverFactory.kt:1
- Change coupling: CategoryLocalDatasourceImpl.kt ↔ CategoriesViewModel.kt core/database/src/commonMain/kotlin/com/kakapo/database/datasource/impl/CategoryLocalDatasourceImpl.kt:1
- TodoComment composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/wallet/PrimaryWalletIcon.kt:34
- TodoComment composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/GoalItemView.kt:46
- TodoComment composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/onboarding/content/createWallet/CreateWalletView.kt:52
- TodoComment composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/addGoal/component/ImageGoalPicker.kt:49
- Duplicated block (9 lines × 2) core/data/src/commonMain/kotlin/com/kakapo/data/model/MonthlyBudgetMapper.kt:19
- Duplicated block (9 lines × 2) shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt:148
- Duplicated block (9 lines × 2) shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/goal/GoalViewModel.kt:87
- Duplicated block (9 lines × 2) iosApp/iosApp/screen/addTransaction/component/CategoriesSheetView.swift:14
- Duplicated block (8 lines × 2) iosApp/iosApp/screen/home/HomeScreen.swift:22
- Duplicated block (8 lines × 2) iosApp/iosApp/screen/addGoal/AddGoalViewModel.swift:25
- Duplicated block (8 lines × 2) iosApp/iosApp/screen/addGoal/AddGoalViewModel.swift:40
- Duplicated block (8 lines × 2) iosApp/iosApp/screen/transaction/TransactionViewModel.swift:28
- Off the main sequence: Oakane:core:preference
- Off the main sequence: Oakane:core:database
- Off the main sequence: Oakane:core:model
- One operation mutates 2 aggregates: MoveWalletBalanceUseCaseImpl.execute core/domain/src/commonMain/kotlin/com/kakapo/domain/usecase/impl/MoveWalletBalanceUseCaseImpl.kt:18
- One operation mutates 2 aggregates: SaveTransactionUseCaseImpl.execute core/domain/src/commonMain/kotlin/com/kakapo/domain/usecase/impl/SaveTransactionUseCaseImpl.kt:17
- One operation mutates 2 aggregates: UpdateTransactionUseCaseImpl.executed core/domain/src/commonMain/kotlin/com/kakapo/domain/usecase/impl/UpdateTransactionUseCaseImpl.kt:20
- Hotspot: iosApp/iosApp/main/ContentView.swift iosApp/iosApp/main/ContentView.swift:21
- Hotspot: shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt:55
- Duplicated block (11 lines × 2) composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/addTransaction/component/SelectCategorySheet.kt:110
- Duplicated block (11 lines × 2) composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/reports/component/ButtonFilterView.kt:70
- Duplicated block (8 lines × 4) iosApp/iosApp/screen/goal/GoalViewModel.swift:28
- Duplicated block (8 lines × 4) iosApp/iosApp/screen/home/HomeViewModel.swift:43
- FileUtilsKt.getImageUriFromFileName (cognitive 16) core/common/src/androidMain/kotlin/com/kakapo/common/FileUtils.kt:50
- Duplicated block (16–17 lines × 2) core/database/src/commonMain/kotlin/com/kakapo/database/model/TransactionEntity.kt:52
- Duplicated block (12 lines × 2) core/common/src/androidMain/kotlin/com/kakapo/common/FileUtils.kt:58
- Duplicated block (10 lines × 2) composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/onboarding/OnBoardingScreen.kt:62
- Duplicated block (9 lines × 6) shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addGoal/AddGoalViewModel.kt:66
- Duplicated block (9 lines × 11) shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt:87
- Duplicated block (8 lines × 5) iosApp/iosApp/screen/addTransaction/AddTransactionViewModel.swift:22
- Duplicated block (7 lines × 5) iosApp/iosApp/screen/categories/CategoriesScreen.swift:131
- Duplicated block (8 lines × 3) iosApp/iosApp/screen/goal/GoalViewModel.swift:43
- Unstable project Oakane:shared
- No CI pipeline
- No structured logging
- Swallowed exception (caught, then discarded) core/common/src/commonMain/kotlin/com/kakapo/common/StringExt.kt:36
Minor — 158 finding(s)
- Orphaned file composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/addTransaction/AddTransactionScreen.kt:1
- Orphaned file composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/settings/SettingsScreen.kt:1
- Orphaned file composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/designSystem/theme/Theme.kt:1
- Orphaned file shared/src/commonMain/kotlin/com/kakapo/oakane/di/CommonModule.kt:1
- Orphaned file composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/designSystem/theme/Color.kt:1
- Orphaned file composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/transaction/TransactionScreen.kt:1
- Orphaned file composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/createwallet/CreateWalletScreen.kt:1
- Orphaned file composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/wallet/WalletScreen.kt:1
- Orphaned file shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt:1
- Orphaned file composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/reminder/ReminderScreen.kt:1
- Orphaned file composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/wallet/component/sheet/FilterLogSheetView.kt:1
- Orphaned file core/model/src/commonMain/kotlin/com/kakapo/model/Currency.kt:1
- Orphaned file composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/sheet/SelectIconVIew.kt:1
- Orphaned file shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/monthlyBudget/MonthlyBudgetViewModel.kt:1
- Orphaned file composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/addGoal/AddGoalScreen.kt:1
- Orphaned file composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/termAndService/TermAndServiceScreen.kt:1
- Orphaned file iosApp/iosApp/screen/addTransaction/AddTransactionScreen.swift:1
- Orphaned file shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/reports/ReportsViewModel.kt:1
- Orphaned file composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/CategoriesScreen.kt:1
- Orphaned file shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/settings/SettingsViewModel.kt:1
- Orphaned file composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/navigation/OakaneNavigation.kt:1
- Orphaned file composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/HomeScreen.kt:1
- Orphaned file iosApp/iosApp/designSystem/theme/IconConstant.swift:1
- Orphaned file shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/transactions/TransactionsViewModel.kt:1
- Orphaned file shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/goal/GoalViewModel.kt:1
- No ADRs found
- Projects may be oversized for their cohesion
- Dormant codebase
- No ADRs
- No architecture diagram/doc
- No SAST
- No changelog
- Silent fallback default in catch core/common/src/commonMain/kotlin/com/kakapo/common/StringExt.kt:36
Minor — 1 finding(s)
- Off the main sequence: Oakane:core:common
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-5a0dd291df1a4acba3753b5309a713af/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-5a0dd291df1a4acba3753b5309a713af/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 . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |
| 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 89 file(s) — `iosApp/iosApp/designSystem/component/button/FabButtonView.swift`, `iosApp/iosApp/designSystem/component/button/FilledButtonView.swift`, `iosApp/iosApp/designSystem/component/button/FilledContentButtonView.swift`, `iosApp/iosApp/designSystem/component/button/IconButtonView.swift`, `iosApp/iosApp/designSystem/component/button/InputChipView.swift`, … (+84 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |