{"$schema":"https://json.schemastore.org/sarif-2.1.0.json","version":"2.1.0","runs":[{"tool":{"driver":{"name":"codehealth","informationUri":"https://codehealth.canine.dev","rules":[{"id":"D1","name":"Cyclomatic Complexity","shortDescription":{"text":"Cyclomatic Complexity"},"helpUri":"https://codehealth.canine.dev/dimensions/D1"},{"id":"D2","name":"Cognitive Complexity","shortDescription":{"text":"Cognitive Complexity"},"helpUri":"https://codehealth.canine.dev/dimensions/D2"},{"id":"D3","name":"God Classes","shortDescription":{"text":"God Classes"},"helpUri":"https://codehealth.canine.dev/dimensions/D3"},{"id":"D4","name":"Code Duplication","shortDescription":{"text":"Code Duplication"},"helpUri":"https://codehealth.canine.dev/dimensions/D4"},{"id":"D13","name":"Secret Scanning","shortDescription":{"text":"Secret Scanning"},"helpUri":"https://codehealth.canine.dev/dimensions/D13","relationships":[{"target":{"id":"CWE-798","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-259","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-798","CWE-259"]}},{"id":"D15","name":"Churn \u00D7 Complexity Hotspots","shortDescription":{"text":"Churn \u00D7 Complexity Hotspots"},"helpUri":"https://codehealth.canine.dev/dimensions/D15"},{"id":"D17","name":"Explicit Debt","shortDescription":{"text":"Explicit Debt"},"helpUri":"https://codehealth.canine.dev/dimensions/D17"},{"id":"D19","name":"Documentation Quality","shortDescription":{"text":"Documentation Quality"},"helpUri":"https://codehealth.canine.dev/dimensions/D19"},{"id":"D20","name":"ADR Quality","shortDescription":{"text":"ADR Quality"},"helpUri":"https://codehealth.canine.dev/dimensions/D20"},{"id":"D21","name":"Naming Consistency","shortDescription":{"text":"Naming Consistency"},"helpUri":"https://codehealth.canine.dev/dimensions/D21"},{"id":"D28","name":"Secrets (history)","shortDescription":{"text":"Secrets (history)"},"helpUri":"https://codehealth.canine.dev/dimensions/D28","relationships":[{"target":{"id":"CWE-798","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-259","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-798","CWE-259"]}},{"id":"D29","name":"Static Analysis (SAST)","shortDescription":{"text":"Static Analysis (SAST)"},"helpUri":"https://codehealth.canine.dev/dimensions/D29","relationships":[{"target":{"id":"CWE-79","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-89","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-78","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-94","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-77","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-79","CWE-89","CWE-78","CWE-94","CWE-77"]}},{"id":"D34","name":"Knowledge Freshness","shortDescription":{"text":"Knowledge Freshness"},"helpUri":"https://codehealth.canine.dev/dimensions/D34"},{"id":"D35","name":"Change Coupling","shortDescription":{"text":"Change Coupling"},"helpUri":"https://codehealth.canine.dev/dimensions/D35"},{"id":"AX10","name":"Code composition","shortDescription":{"text":"Code composition"},"helpUri":"https://codehealth.canine.dev/dimensions/AX10"},{"id":"AX9","name":"CQS / query purity","shortDescription":{"text":"CQS / query purity"},"helpUri":"https://codehealth.canine.dev/dimensions/AX9"},{"id":"DM12","name":"Ambient inputs in the domain","shortDescription":{"text":"Ambient inputs in the domain"},"helpUri":"https://codehealth.canine.dev/dimensions/DM12"},{"id":"DM6","name":"Domain \u2194 infrastructure boundary","shortDescription":{"text":"Domain \u2194 infrastructure boundary"},"helpUri":"https://codehealth.canine.dev/dimensions/DM6"},{"id":"DM8","name":"Value-object opportunities","shortDescription":{"text":"Value-object opportunities"},"helpUri":"https://codehealth.canine.dev/dimensions/DM8"},{"id":"M1","name":"Documentation (README)","shortDescription":{"text":"Documentation (README)"},"helpUri":"https://codehealth.canine.dev/dimensions/M1"},{"id":"M2","name":"Architecture documentation","shortDescription":{"text":"Architecture documentation"},"helpUri":"https://codehealth.canine.dev/dimensions/M2"},{"id":"M3","name":"Folder \u0026 project structure","shortDescription":{"text":"Folder \u0026 project structure"},"helpUri":"https://codehealth.canine.dev/dimensions/M3"},{"id":"M4","name":"Documentation accuracy","shortDescription":{"text":"Documentation accuracy"},"helpUri":"https://codehealth.canine.dev/dimensions/M4"},{"id":"P1","name":"CI/CD gates","shortDescription":{"text":"CI/CD gates"},"helpUri":"https://codehealth.canine.dev/dimensions/P1"},{"id":"P3","name":"Security \u0026 performance tooling","shortDescription":{"text":"Security \u0026 performance tooling"},"helpUri":"https://codehealth.canine.dev/dimensions/P3"},{"id":"P5","name":"DR \u0026 Backup","shortDescription":{"text":"DR \u0026 Backup"},"helpUri":"https://codehealth.canine.dev/dimensions/P5"},{"id":"P6","name":"Release Hygiene","shortDescription":{"text":"Release Hygiene"},"helpUri":"https://codehealth.canine.dev/dimensions/P6"},{"id":"X9","name":"Subsumed condition operand","shortDescription":{"text":"Subsumed condition operand"},"helpUri":"https://codehealth.canine.dev/dimensions/X9"}]}},"results":[{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (16\u201317 lines \u00D7 2): core/database/src/commonMain/kotlin/com/kakapo/database/model/TransactionEntity.kt:52-67 | core/database/src/commonMain/kotlin/com/kakapo/database/model/TransactionEntity.kt:75-91 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060core/database/src/commonMain/kotlin/com/kakapo/database/model/TransactionEntity.kt:52\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names \u2014 the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"core/database/src/commonMain/kotlin/com/kakapo/database/model/TransactionEntity.kt"},"region":{"startLine":52}}}],"partialFingerprints":{"codehealthFindingId/v1":"dc0dc2ff02769291730cd4e6ddd93e37b7f32e23e487f9bd5864afcc332b3700"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (12 lines \u00D7 2): core/common/src/androidMain/kotlin/com/kakapo/common/FileUtils.kt:58-69 | core/common/src/androidMain/kotlin/com/kakapo/common/FileUtils.kt:92-103 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"core/common/src/androidMain/kotlin/com/kakapo/common/FileUtils.kt"},"region":{"startLine":58}}}],"partialFingerprints":{"codehealthFindingId/v1":"58efb763a5b75236f752a728dd195a62b4bbc6c62186685f1a115c00dd1e9b7c"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 2): composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/addTransaction/component/SelectCategorySheet.kt:110-120 | composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/CategoriesScreen.kt:142-152 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/addTransaction/component/SelectCategorySheet.kt:110\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/addTransaction/component/SelectCategorySheet.kt"},"region":{"startLine":110}}}],"partialFingerprints":{"codehealthFindingId/v1":"62499231fc40cf269ed5943b43d7651ce596027d44df95a2a114c9d19e4d34d0"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 2): composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/reports/component/ButtonFilterView.kt:70-80 | composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/reports/component/ButtonFilterView.kt:126-136 \u2014 both copies are in the same file, so extract the block into one function there and call it from each site \u2014 the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/reports/component/ButtonFilterView.kt:70\u0060 it does not close everything it opens, so those exact lines cannot be lifted as they stand \u2014 widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind \u0060modifier\u0060 to \u0060Modifier\u0060 in one and \u0060Modifier = Modifier\u0060 in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH \u2014 their common supertype where they have one, or a new abstraction over them where they do not \u2014 and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/reports/component/ButtonFilterView.kt:81\u0060 calls \u0060Icon\u0060 and \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/reports/component/ButtonFilterView.kt:137\u0060 does not \u2014 after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/reports/component/ButtonFilterView.kt"},"region":{"startLine":70}}}],"partialFingerprints":{"codehealthFindingId/v1":"7f5950a487b489a28a81ff3498aacaa92a012c4f1e9963cce34094d0723094fc"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 6): shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addGoal/AddGoalViewModel.kt:66-75 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/goal/GoalViewModel.kt:77-85 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/monthlyBudget/MonthlyBudgetViewModel.kt:103-111 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/reports/ReportsViewModel.kt:139-147 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/transaction/TransactionViewModel.kt:81-89 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/wallets/WalletsViewModel.kt:66-74 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made 6 times."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addGoal/AddGoalViewModel.kt"},"region":{"startLine":66}}}],"partialFingerprints":{"codehealthFindingId/v1":"cd12184583326e4db8d85ee426ccf49ebb51ad9b96e6afa51008cb6133e6479e"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt:148-156 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/goal/GoalViewModel.kt:97-105 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt"},"region":{"startLine":148}}}],"partialFingerprints":{"codehealthFindingId/v1":"012f84979fe5d9866453d124cf52079650a751bc492792615ecbcf4f23dbf536"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 11): shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt:87-95 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/goal/GoalViewModel.kt:152-160 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/goals/GoalsViewModel.kt:62-70 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/home/HomeViewModel.kt:131-139 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/main/MainViewModel.kt:43-51 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/monthlyBudget/MonthlyBudgetViewModel.kt:113-121 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/reports/ReportsViewModel.kt:149-157 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/transaction/TransactionViewModel.kt:101-109 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/transactions/TransactionsViewModel.kt:129-137 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/wallet/WalletViewModel.kt:97-105 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/wallets/WalletsViewModel.kt:76-84 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 11 call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made 11 times. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/transaction/TransactionViewModel.kt:113\u0060 calls \u0060e\u0060 and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/goal/GoalViewModel.kt:164\u0060 does not \u2014 after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt"},"region":{"startLine":87}}}],"partialFingerprints":{"codehealthFindingId/v1":"9a7fbab470b0e73038429a9e522c0aadb2211b8d7b84e5fb9cacb55d954cebc6"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/goal/GoalViewModel.kt:87-95 | shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/wallet/WalletViewModel.kt:65-73 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/goal/GoalViewModel.kt"},"region":{"startLine":87}}}],"partialFingerprints":{"codehealthFindingId/v1":"ef2593b72ab929b439970487a9994c76017b06ee3fb06ff39953e7e617721008"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9 lines \u00D7 2): core/data/src/commonMain/kotlin/com/kakapo/data/model/MonthlyBudgetMapper.kt:19-27 | core/database/src/commonMain/kotlin/com/kakapo/database/model/MonthlyBudgetEntity.kt:17-25 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"core/data/src/commonMain/kotlin/com/kakapo/data/model/MonthlyBudgetMapper.kt"},"region":{"startLine":19}}}],"partialFingerprints":{"codehealthFindingId/v1":"65ef93ae7f27d9251d139e0e797891c10579ae21a14c25794ac77db0f43a3047"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 2): composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/onboarding/OnBoardingScreen.kt:62-71 | composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/settings/SettingsScreen.kt:176-185 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach \u2014 a location they all depend on today, or a new shared one if there is none \u2014 and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/onboarding/OnBoardingScreen.kt"},"region":{"startLine":62}}}],"partialFingerprints":{"codehealthFindingId/v1":"5758bdf2d9acc6fdad6b7389b96431b055e893c61ebf6c9c98f6697011a5deff"}},{"ruleId":"D15","level":"warning","message":{"text":"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 changed 14 times in last 90 days, max cyclomatic complexity 18 in AddTransactionViewModel.handleEvent at line 55. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-01-09..2025-04-09, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-01-09 05:45:01 \u002B07:00\u0027 --until=\u00272025-04-09 05:45:01 \u002B07:00\u0027 --full-history --no-merges -- shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/addTransaction/AddTransactionViewModel.kt"},"region":{"startLine":55}}}],"partialFingerprints":{"codehealthFindingId/v1":"7b17551449bf25e674650c1a926638844080865e12699ba77cd66f15b8b7a548"}},{"ruleId":"D15","level":"warning","message":{"text":"Hotspot: shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt: shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt changed 2 times in last 90 days, max cyclomatic complexity 16 in CategoriesViewModel.handleEvent at line 41. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-01-09..2025-04-09, the 90 days ending at the analysed commit. Reproduce with \u0060git log --since=\u00272025-01-09 05:45:01 \u002B07:00\u0027 --until=\u00272025-04-09 05:45:01 \u002B07:00\u0027 --full-history --no-merges -- shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt\u0060: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each \u2014 a difference of several commits on a file whose history was re-landed or reverted inside the window."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt"},"region":{"startLine":41}}}],"partialFingerprints":{"codehealthFindingId/v1":"327efc79dc6f716edd2cffa60adc1a9aecdef889f7d97bf1951a19b7d76caa3e"}},{"ruleId":"D17","level":"warning","message":{"text":"TodoComment: //TODO change with new i con soon \u2014 source code is not a task system: move the work to your tracker and leave a reference instead (e.g. \u0060// REF: #123\u0060), so the task is planned where tasks live and the ticket links back to the code."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/addGoal/component/ImageGoalPicker.kt"},"region":{"startLine":49}}}],"partialFingerprints":{"codehealthFindingId/v1":"d62b8e6530633704bdc43ae0befa33bdc6ea57bbca607564b60fad0d7ca9f50a"}},{"ruleId":"D17","level":"warning","message":{"text":"TodoComment: //Todo change with new i con soon \u2014 source code is not a task system: move the work to your tracker and leave a reference instead (e.g. \u0060// REF: #123\u0060), so the task is planned where tasks live and the ticket links back to the code."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/onboarding/content/createWallet/CreateWalletView.kt"},"region":{"startLine":52}}}],"partialFingerprints":{"codehealthFindingId/v1":"c63eae6a7e8890d18b527879883b977cad1f6eded02bc0dc48fea55dd6c350e0"}},{"ruleId":"D17","level":"warning","message":{"text":"TodoComment: // TODO change with new icon soon \u2014 source code is not a task system: move the work to your tracker and leave a reference instead (e.g. \u0060// REF: #123\u0060), so the task is planned where tasks live and the ticket links back to the code."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/GoalItemView.kt"},"region":{"startLine":46}}}],"partialFingerprints":{"codehealthFindingId/v1":"206574eb295f9291bc0dbc551f96963f94b25b63bf54a6647cf5aaa68f09e218"}},{"ruleId":"D17","level":"warning","message":{"text":"TodoComment: //TODO change with new icon soon \u2014 source code is not a task system: move the work to your tracker and leave a reference instead (e.g. \u0060// REF: #123\u0060), so the task is planned where tasks live and the ticket links back to the code."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/wallet/PrimaryWalletIcon.kt"},"region":{"startLine":34}}}],"partialFingerprints":{"codehealthFindingId/v1":"7251b5d895ae13bfb919801ac86360a04fc2f2b84fac36d4326b74c60b87ee80"}},{"ruleId":"D19","level":"note","message":{"text":"Documentation: no installation or build instructions: No build or setup instructions for a KMP multiplatform project with Android/iOS support. Add a \u0027How to Run\u0027 section covering the full build, plugin configuration (google-services.json), and running both platforms."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"README.md"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"1fa6bfcd5c6ae231d1b8ee99bced50b832d1f61cde9da6cbb533467b879a57db"}},{"ruleId":"D19","level":"note","message":{"text":"Documentation: no usage examples: No runnable example showing how to create an expense or add a recurring budget. Add a short usage snippet demonstrating the core flow (expense logging, recurring setup) so readers can run it without code."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"README.md"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"1355eb4e127a4bc9236772ce1c46f09510aa9286e7a06d1e47f308229df19049"}},{"ruleId":"D20","level":"note","message":{"text":"No ADRs found: No ADRs found. No recognised ADR directory (\u0060docs/adr/\u0060, \u0060docs/decisions/\u0060, \u0060adr/\u0060, \u0060docs/rfcs/\u0060, an \u0060ADR0001/\u0060 folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (\u0060docs/adr/use-postgres.md\u0060, \u0060docs/adr/2024/0001-x.md\u0060); or a file anywhere whose name is ADR-shaped (\u00600001-use-postgres.md\u0060, \u0060adr-012-caching.md\u0060); or, when neither turned anything up, a document carrying the decision-record signature (an \u0022Architecture Decision Record\u0022 heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these \u2014 unnumbered files outside any recognised directory, without those headings \u2014 is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in \u0060docs/adr/\u0060."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"d2bea044ff79d7d275f5a91a6e2f548586178eaf480274c33960ad020c854631"}},{"ruleId":"D34","level":"note","message":{"text":"Orphaned files with no living knowledge: 59 of 150 analysed file(s) have no living knowledge left \u2014 their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 150 of the 516 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each \u2014 most significant first: composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/designSystem/theme/Theme.kt, composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/designSystem/theme/Color.kt, composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/wallet/component/sheet/FilterLogSheetView.kt, composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/termAndService/TermAndServiceScreen.kt, iosApp/iosApp/designSystem/theme/IconConstant.swift, core/model/src/commonMain/kotlin/com/kakapo/model/category/CategoryIconName.kt, core/domain/src/commonMain/kotlin/com/kakapo/domain/usecase/impl/ImportRecurringBudgetUseCaseImpl.kt, composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/designSystem/component/textField/currency/CurrencyTextFieldState.kt (and 51 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"ce861fd78f6935114d3a342cb90ad25870f984e1042954fcbbe27c0e23be3658"}},{"ruleId":"D35","level":"error","message":{"text":"Boundary-crossing change coupling: HomeNavigation.kt \u2194 HomeViewContract.kt: \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/navigation/HomeNavigation.kt\u0060 (context composeApp) and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/home/HomeViewContract.kt\u0060 (context shared) sit in DIFFERENT parts of the tree yet change together 67% of the time (8 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) \u2014 the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can\u0027t see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are \u0060efd42ae3\u0060 create basic screen for wallet and add navigation to wallets; \u006062b91df4\u0060 add navigation from home to transaction; \u0060585cc116\u0060 creating general structure for add budget screen and create navigatio\u2026 \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/navigation/HomeNavigation.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"40fc4d04bcf9a748249b0ce45484925a4bd04c3998b379906c6a238d4e2428da"}},{"ruleId":"D35","level":"error","message":{"text":"Boundary-crossing change coupling: HomeNavigation.kt \u2194 HomeViewModel.kt: \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/navigation/HomeNavigation.kt\u0060 (context composeApp) and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/home/HomeViewModel.kt\u0060 (context shared) sit in DIFFERENT parts of the tree yet change together 67% of the time (8 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) \u2014 the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can\u0027t see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are \u0060efd42ae3\u0060 create basic screen for wallet and add navigation to wallets; \u006062b91df4\u0060 add navigation from home to transaction; \u0060585cc116\u0060 creating general structure for add budget screen and create navigatio\u2026 \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/navigation/HomeNavigation.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"333d3861d9a6e15db53a0b2ae7d0289ff724a2d71a1ea3158dbe694d9663455d"}},{"ruleId":"D35","level":"error","message":{"text":"Boundary-crossing change coupling: CategoryItemView.kt \u2194 CategoriesViewModel.kt: \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/category/CategoryItemView.kt\u0060 (context composeApp) and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt\u0060 (context shared) sit in DIFFERENT parts of the tree yet change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) \u2014 the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can\u0027t see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are \u0060e5cb308b\u0060 load category when tapped and create some function to load data categ\u2026 (at that commit the file was still \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/CategoryItemView.kt\u0060); \u00608dfb3a2e\u0060 saving image from gallery in android side (at that commit the file was still \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/CategoryItemView.kt\u0060); \u0060cddc5aee\u0060 finishing view for creating category view (at that commit the file was still \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/CategoryItemView.kt\u0060) \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/category/CategoryItemView.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"67c6ada1ea74196ab48a78b3113b8db848e8413b6efb174d7f45f6e1daa5994f"}},{"ruleId":"D35","level":"error","message":{"text":"Boundary-crossing change coupling: TransactionsTopAppBarView.kt \u2194 TransactionsViewModel.kt: \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/transactions/component/TransactionsTopAppBarView.kt\u0060 (context composeApp) and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/transactions/TransactionsViewModel.kt\u0060 (context shared) sit in DIFFERENT parts of the tree yet change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) \u2014 the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can\u0027t see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are \u0060586bcbd3\u0060 feat: refactor transactions screen state and filtering; \u006044d84eb6\u0060 feat: enhance theme handling and UI components; \u00603cd62eec\u0060 implement filter transactions by date \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/transactions/component/TransactionsTopAppBarView.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"bb76cd2f953212e93b2033bb6c25df116686e790f19714b6857152490cd891b6"}},{"ruleId":"D35","level":"error","message":{"text":"Boundary-crossing change coupling: PrimaryWalletView.kt \u2194 HomeViewModel.kt: \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/component/PrimaryWalletView.kt\u0060 (context composeApp) and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/home/HomeViewModel.kt\u0060 (context shared) sit in DIFFERENT parts of the tree yet change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) \u2014 the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can\u0027t see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are \u006044d84eb6\u0060 feat: enhance theme handling and UI components; \u00605311c51d\u0060 feat: add balance visibility toggle (at that commit the file was still \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/component/WalletBalanceView.kt\u0060); \u0060ca676a99\u0060 finishing addjustment for home screen ios (at that commit the file was still \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/component/WalletBalanceView.kt\u0060) \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/component/PrimaryWalletView.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"b64f5d1b16636ac4c93dd0191bf7aff9f377e7140978ebdad6a85245d452c394"}},{"ruleId":"D35","level":"error","message":{"text":"Boundary-crossing change coupling: GoalItemView.kt \u2194 CommonModule.kt: \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/GoalItemView.kt\u0060 (context composeApp) and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/di/CommonModule.kt\u0060 (context shared) sit in DIFFERENT parts of the tree yet change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) \u2014 the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can\u0027t see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are \u0060327461b0\u0060 feat: refactor goal management and add goal validation; \u0060110b28e9\u0060 feat: enhance image handling and file management; \u006046943368\u0060 feat: implement add goal saving feature \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/GoalItemView.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"bd342f4b9c440377a96386dbc6114289c01c1b9f5af3f909f8c4fc2fafa662fd"}},{"ruleId":"D35","level":"error","message":{"text":"Boundary-crossing change coupling: CategoryItemView.kt \u2194 CategoriesViewContract.kt: \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/category/CategoryItemView.kt\u0060 (context composeApp) and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewContract.kt\u0060 (context shared) sit in DIFFERENT parts of the tree yet change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) \u2014 the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can\u0027t see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are \u0060e5cb308b\u0060 load category when tapped and create some function to load data categ\u2026 (at that commit the file was still \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/CategoryItemView.kt\u0060); \u00608dfb3a2e\u0060 saving image from gallery in android side (at that commit the file was still \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/CategoryItemView.kt\u0060); \u0060cddc5aee\u0060 finishing view for creating category view (at that commit the file was still \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/CategoryItemView.kt\u0060) \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/item/category/CategoryItemView.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"d64dd76b57184ac0a037d369f5fc09d29964d4931ead7c3ed3ee94736b3eeab4"}},{"ruleId":"D35","level":"error","message":{"text":"Boundary-crossing change coupling: SelectIconVIew.kt \u2194 CategoriesViewContract.kt: \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/sheet/SelectIconVIew.kt\u0060 (context composeApp) and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewContract.kt\u0060 (context shared) sit in DIFFERENT parts of the tree yet change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) \u2014 the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can\u0027t see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are \u006084cd6a15\u0060 finishing create wallet view and add currency symbols in currency enu\u2026; \u0060f356f8f6\u0060 add conditional check before parsing string color into Long color in \u2026; \u0060a182bac5\u0060 add adjustment in some swift component, and make some change in ui an\u2026 (at that commit the file was still \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/sheet/SelectCategoryIconVIew.kt\u0060) \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/sheet/SelectIconVIew.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"6eb9d6ca82dbf4ce8a5776abe6f5994a0e4c733e1455a5ef855514a519ecec52"}},{"ruleId":"D35","level":"error","message":{"text":"Boundary-crossing change coupling: MonthlyBudgetView.kt \u2194 HomeViewModel.kt: \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/component/MonthlyBudgetView.kt\u0060 (context composeApp) and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/home/HomeViewModel.kt\u0060 (context shared) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) \u2014 the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can\u0027t see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are \u006044d84eb6\u0060 feat: enhance theme handling and UI components; \u00600e43c6f9\u0060 feat: implement recurring monthly budget setting and update UI; \u00601d6528b2\u0060 get total transaction income and expense, creating use case to genera\u2026 \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/component/MonthlyBudgetView.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"f2409fdafeeb009a9088e19df4282562a31eed1f50e70d86377a0c422741fbb1"}},{"ruleId":"D35","level":"error","message":{"text":"Boundary-crossing change coupling: CategoriesSheetView.kt \u2194 CategoriesViewModel.kt: \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/CategoriesSheetView.kt\u0060 (context composeApp) and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt\u0060 (context shared) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) \u2014 the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can\u0027t see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are \u00609f3838bf\u0060 implementing icon color selection in select icon view both in ios and\u2026; \u006079491883\u0060 implement select icon from selection icon view; \u0060a2d53c4b\u0060 add color picker when creating custom category \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/CategoriesSheetView.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"2b9af20eaa4ad0a8c9f88c2ed7fb231f3ec4d42ec9b07664cc7bbc93eb299bd5"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: HomeScreen.kt \u2194 HomeNavigation.kt: \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/HomeScreen.kt\u0060 and \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/navigation/HomeNavigation.kt\u0060 change together 92% of the time (11 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency \u2014 the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE \u2014 the registration is the link, and it is meant not to be an import \u2014 and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are \u0060efd42ae3\u0060 create basic screen for wallet and add navigation to wallets; \u006062b91df4\u0060 add navigation from home to transaction; \u0060585cc116\u0060 creating general structure for add budget screen and create navigatio\u2026 \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/HomeScreen.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"789b36efc8e4097629dbf14a530987843223e680a695e8df37be8c6c3b9623b4"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: WalletRepositoryImpl.kt \u2194 WalletLocalDatasourceImpl.kt: \u0060core/data/src/commonMain/kotlin/com/kakapo/data/repository/impl/WalletRepositoryImpl.kt\u0060 and \u0060core/database/src/commonMain/kotlin/com/kakapo/database/datasource/impl/WalletLocalDatasourceImpl.kt\u0060 change together 90% of the time (9 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency \u2014 the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE \u2014 the registration is the link, and it is meant not to be an import \u2014 and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are \u0060036da0ec\u0060 feat: implement move balance between wallets; \u0060970fb425\u0060 change flow how to create default wallet with make user decide if it \u2026; \u00603ccb1fd7\u0060 implement get total balance in all wallet in reports screen (at that commit the files were still \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/impl/WalletRepositoryImpl.kt\u0060 and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/impl/WalletLocalDatasourceImpl.kt\u0060) \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"core/data/src/commonMain/kotlin/com/kakapo/data/repository/impl/WalletRepositoryImpl.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"7e81b63f5566dd7056f43d53503946deeb7b8b4cd904c8d79615a548400bfcac"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: HomeNavigation.kt \u2194 OakaneNavigation.kt: \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/navigation/HomeNavigation.kt\u0060 and \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/navigation/OakaneNavigation.kt\u0060 change together 83% of the time (10 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency \u2014 the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE \u2014 the registration is the link, and it is meant not to be an import \u2014 and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are \u0060efd42ae3\u0060 create basic screen for wallet and add navigation to wallets; \u006062b91df4\u0060 add navigation from home to transaction; \u0060585cc116\u0060 creating general structure for add budget screen and create navigatio\u2026 \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/home/navigation/HomeNavigation.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"7764987f45a70a96b49036adac0886d43adbc9279b6f465c3f5b8358a5466b0d"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: WalletRepository.kt \u2194 WalletLocalDatasourceImpl.kt: \u0060core/data/src/commonMain/kotlin/com/kakapo/data/repository/base/WalletRepository.kt\u0060 and \u0060core/database/src/commonMain/kotlin/com/kakapo/database/datasource/impl/WalletLocalDatasourceImpl.kt\u0060 change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency \u2014 the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE \u2014 the registration is the link, and it is meant not to be an import \u2014 and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are \u0060970fb425\u0060 change flow how to create default wallet with make user decide if it \u2026; \u00603ccb1fd7\u0060 implement get total balance in all wallet in reports screen (at that commit the files were still \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/base/WalletRepository.kt\u0060 and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/impl/WalletLocalDatasourceImpl.kt\u0060); \u00604cc9fa34\u0060 add functionality update wallet in wallet screen (at that commit the files were still \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/base/WalletRepository.kt\u0060 and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/impl/WalletLocalDatasourceImpl.kt\u0060) \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"core/data/src/commonMain/kotlin/com/kakapo/data/repository/base/WalletRepository.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"eb78bffb81bcf6159e6fb7645991040bcdcb4403d575114b7204ed9684854783"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: TransactionRepository.kt \u2194 TransactionLocalDatasource.kt: \u0060core/data/src/commonMain/kotlin/com/kakapo/data/repository/base/TransactionRepository.kt\u0060 and \u0060core/database/src/commonMain/kotlin/com/kakapo/database/datasource/base/TransactionLocalDatasource.kt\u0060 change together 77% of the time (10 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency \u2014 the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE \u2014 the registration is the link, and it is meant not to be an import \u2014 and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are \u0060c3c8a19d\u0060 feat: add wallet transfer logging and transaction retrieval by wallet\u2026; \u0060fd85ba53\u0060 fixing bug load all transaction without date, and load all transaction (at that commit the files were still \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/base/TransactionRepository.kt\u0060 and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/base/TransactionLocalDatasource.kt\u0060); \u006086917fdd\u0060 implement filter transaction by month (at that commit the files were still \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/base/TransactionRepository.kt\u0060 and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/base/TransactionLocalDatasource.kt\u0060) \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"core/data/src/commonMain/kotlin/com/kakapo/data/repository/base/TransactionRepository.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"6efb01028c4904a67dbb423fe5ae32491efd6147ef5140e22715d14e776800eb"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: MonthlyBudgetRepositoryImpl.kt \u2194 MonthlyBudgetViewModel.kt: \u0060core/data/src/commonMain/kotlin/com/kakapo/data/repository/impl/MonthlyBudgetRepositoryImpl.kt\u0060 and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/monthlyBudget/MonthlyBudgetViewModel.kt\u0060 change together 73% of the time (8 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency \u2014 the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE \u2014 the registration is the link, and it is meant not to be an import \u2014 and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are \u0060d501b7e9\u0060 feat: refactor budget input and add currency support; \u00605b0d4f7f\u0060 fixing load budget not change when filter month is changed (at that commit the file was still \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/impl/MonthlyBudgetRepositoryImpl.kt\u0060); \u00601d6528b2\u0060 get total transaction income and expense, creating use case to genera\u2026 (at that commit the file was still \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/impl/MonthlyBudgetRepositoryImpl.kt\u0060) \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"core/data/src/commonMain/kotlin/com/kakapo/data/repository/impl/MonthlyBudgetRepositoryImpl.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"7d5846719006265e9fee247906b4884de7bc8354dfba2f03f72de32f845cee33"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: CreateWalletSheetView.swift \u2194 WalletsScreen.swift: \u0060iosApp/iosApp/designSystem/ui/sheet/CreateWalletSheetView.swift\u0060 and \u0060iosApp/iosApp/screen/wallets/WalletsScreen.swift\u0060 change together 69% of the time (9 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder \u2014 so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are \u0060b11189a9\u0060 feat: implement saving new wallets and update WalletsScreen UI; \u006017e97bca\u0060 feat: refactor sheet presentation and implement dynamic height; \u0060f903f5cb\u0060 fixing bug wallet not changed color in wallets screen \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"iosApp/iosApp/designSystem/ui/sheet/CreateWalletSheetView.swift"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"f11825a6ad81f1c9235440768a1ee3058d99af47b742bb394230a395d0de5b5d"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: TransactionRepository.kt \u2194 TransactionLocalDatasourceImpl.kt: \u0060core/data/src/commonMain/kotlin/com/kakapo/data/repository/base/TransactionRepository.kt\u0060 and \u0060core/database/src/commonMain/kotlin/com/kakapo/database/datasource/impl/TransactionLocalDatasourceImpl.kt\u0060 change together 65% of the time (11 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency \u2014 the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE \u2014 the registration is the link, and it is meant not to be an import \u2014 and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are \u0060c3c8a19d\u0060 feat: add wallet transfer logging and transaction retrieval by wallet\u2026; \u0060fd85ba53\u0060 fixing bug load all transaction without date, and load all transaction (at that commit the files were still \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/base/TransactionRepository.kt\u0060 and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/impl/TransactionLocalDatasourceImpl.kt\u0060); \u006086917fdd\u0060 implement filter transaction by month (at that commit the files were still \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/base/TransactionRepository.kt\u0060 and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/impl/TransactionLocalDatasourceImpl.kt\u0060) \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"core/data/src/commonMain/kotlin/com/kakapo/data/repository/base/TransactionRepository.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"ed0c300b6ebe64cfa88dd9c6e700cfc483c713699430619d0d98bea7ff48cc98"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: TransactionRepositoryImpl.kt \u2194 TransactionLocalDatasourceImpl.kt: \u0060core/data/src/commonMain/kotlin/com/kakapo/data/repository/impl/TransactionRepositoryImpl.kt\u0060 and \u0060core/database/src/commonMain/kotlin/com/kakapo/database/datasource/impl/TransactionLocalDatasourceImpl.kt\u0060 change together 57% of the time (12 of the 21 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency \u2014 the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE \u2014 the registration is the link, and it is meant not to be an import \u2014 and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are \u0060c3c8a19d\u0060 feat: add wallet transfer logging and transaction retrieval by wallet\u2026; \u0060fd85ba53\u0060 fixing bug load all transaction without date, and load all transaction (at that commit the files were still \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/impl/TransactionRepositoryImpl.kt\u0060 and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/impl/TransactionLocalDatasourceImpl.kt\u0060); \u006086917fdd\u0060 implement filter transaction by month (at that commit the files were still \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/impl/TransactionRepositoryImpl.kt\u0060 and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/impl/TransactionLocalDatasourceImpl.kt\u0060) \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"core/data/src/commonMain/kotlin/com/kakapo/data/repository/impl/TransactionRepositoryImpl.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"1b381a11dd81fbc3cfcd04be91282ff022caaf5e14f9ea933536f4dee3458d86"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: MainActivity.kt \u2194 OakaneNavigation.kt: \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/MainActivity.kt\u0060 and \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/navigation/OakaneNavigation.kt\u0060 change together 56% of the time (10 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency \u2014 the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE \u2014 the registration is the link, and it is meant not to be an import \u2014 and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are \u0060020e0b8c\u0060 feat: update dependencies and integrate WorkManager for background tasks; \u00606ec2eadd\u0060 feat: enhance navigation transitions and improve UI components; \u00600c78b7f3\u0060 feat: enhance drawer and navigation behavior \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"composeApp/src/androidMain/kotlin/com/kakapo/oakane/MainActivity.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"08f09f173177bf087144863f0597e236f95e7e028ef72e69867784d015720f4b"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: OnBoardingScreen.kt \u2194 CreateWalletView.kt: \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/onboarding/OnBoardingScreen.kt\u0060 and \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/onboarding/content/createWallet/CreateWalletView.kt\u0060 change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency \u2014 the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE \u2014 the registration is the link, and it is meant not to be an import \u2014 and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are \u006064039058\u0060 feat: refactor on-boarding and wallet creation flow; \u00603ab219db\u0060 integrate selected currency to create wallet bottom sheet; \u0060970fb425\u0060 change flow how to create default wallet with make user decide if it \u2026 \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/onboarding/OnBoardingScreen.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"7a8dc61ce77d20b1fa7b9cf693ef0bcbf6369d9f3875f7727fb5643f46f26d86"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: CreateCategoryContentView.kt \u2194 SelectIconVIew.kt: \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/sheet/CreateCategoryContentView.kt\u0060 and \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/ui/component/sheet/SelectIconVIew.kt\u0060 change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency \u2014 the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE \u2014 the registration is the link, and it is meant not to be an import \u2014 and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are \u006058959d47\u0060 refactoring property name for SelectedIconModel; \u006083a9aeee\u0060 move some file and finishing CategoryLimitDropdownMenuView (at that commit the file was still \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/sheet/SelectCategoryIconVIew.kt\u0060); \u0060a182bac5\u0060 add adjustment in some swift component, and make some change in ui an\u2026 (at that commit the file was still \u0060composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/sheet/SelectCategoryIconVIew.kt\u0060) \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"composeApp/src/androidMain/kotlin/com/kakapo/oakane/presentation/feature/categories/component/sheet/CreateCategoryContentView.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"411a854bcfa9aa4f789aac87afdd5c5cd4b6ffd5666480a62d0094f5eea6bbca"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: WalletMapper.kt \u2194 WalletRepositoryImpl.kt: \u0060core/data/src/commonMain/kotlin/com/kakapo/data/model/WalletMapper.kt\u0060 and \u0060core/data/src/commonMain/kotlin/com/kakapo/data/repository/impl/WalletRepositoryImpl.kt\u0060 change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency \u2014 the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE \u2014 the registration is the link, and it is meant not to be an import \u2014 and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are \u006071801041\u0060 Improved currency symbol display in Android by refactoring to use Tex\u2026; \u00609a45b195\u0060 implement load wallets in wallets screen android side (at that commit the files were still \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/model/WalletMapper.kt\u0060 and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/impl/WalletRepositoryImpl.kt\u0060); \u006051bc5b05\u0060 implement save wallet into database (at that commit the files were still \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/model/WalletMapper.kt\u0060 and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/repository/impl/WalletRepositoryImpl.kt\u0060) \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"core/data/src/commonMain/kotlin/com/kakapo/data/model/WalletMapper.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"927b7dc0cfef0a294633febf91e6f59f395566dfad77d7c09761f8f03c08ac78"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: MySqlDriverFactory.kt \u2194 CommonModule.kt: \u0060core/database/src/androidMain/kotlin/com/kakapo/database/MySqlDriverFactory.kt\u0060 and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/di/CommonModule.kt\u0060 change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency \u2014 the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE \u2014 the registration is the link, and it is meant not to be an import \u2014 and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are \u0060df29cef7\u0060 feat: refactor recurring budget and add reminder functionality; \u0060bbb32845\u0060 feat: add WalletTransferEntity and implement database migration; \u0060800a0af8\u0060 refactor: move wallet dropdown component to ui module \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"core/database/src/androidMain/kotlin/com/kakapo/database/MySqlDriverFactory.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"90df5fcefd1dfda35189d65cd9ef7821d8ccd92ef6f61727d50048c0c37b32ef"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: CategoryLocalDatasourceImpl.kt \u2194 CategoriesViewModel.kt: \u0060core/database/src/commonMain/kotlin/com/kakapo/database/datasource/impl/CategoryLocalDatasourceImpl.kt\u0060 and \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/presentation/viewModel/categories/CategoriesViewModel.kt\u0060 change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well \u2014 a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency \u2014 the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE \u2014 the registration is the link, and it is meant not to be an import \u2014 and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are \u0060201da456\u0060 implement swipe to delete for category in android side (at that commit the file was still \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/impl/CategoryLocalDatasourceImpl.kt\u0060); \u00600835a21f\u0060 implement update category (at that commit the file was still \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/impl/CategoryLocalDatasourceImpl.kt\u0060); \u0060e5cb308b\u0060 load category when tapped and create some function to load data categ\u2026 (at that commit the file was still \u0060shared/src/commonMain/kotlin/com/kakapo/oakane/data/database/datasource/impl/CategoryLocalDatasourceImpl.kt\u0060) \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"core/database/src/commonMain/kotlin/com/kakapo/database/datasource/impl/CategoryLocalDatasourceImpl.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"3b27b777da6546fb83f4ebe53cf7818c258879519641fb15dfa8b237cc8a9e8f"}},{"ruleId":"M2","level":"note","message":{"text":"No ADRs: No Architecture Decision Records found \u2014 no conventional ADR directory, no numbered \u0060NNNN-title\u0060 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."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"670b3d6e36a756d63097d0dfbf90afd5fc761308800b9354894a07c3f4e4aa14"}},{"ruleId":"M2","level":"note","message":{"text":"No architecture diagram/doc: No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named \u0060architecture\u0060 or \u0060design\u0060 in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape \u2014 no \u0060## Architecture\u0060 heading, no \u0022architecture overview\u0022/\u0022high-level design\u0022 phrasing, no \u0022the architecture is \u2026\u0022 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 \u2014 not evidence that nobody wrote the shape down."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"0c190e7c159d1850ee706c3ac4486e151e8a4fe169de4bf61436b9f399654f06"}},{"ruleId":"P1","level":"warning","message":{"text":"No CI pipeline: No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, \u2026) \u2014 changes aren\u0027t gated by an automated build/test."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"44f01af96e50474fba2df84d95ddf4f7e1d34c29c307830b9efc9057daa6b670"}},{"ruleId":"P3","level":"note","message":{"text":"No SAST: No static application security testing detected. For this repository\u0027s stack, add spotbugs with find-sec-bugs (or \u0060semgrep --config=auto\u0060, which runs on any language) \u2014 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\u0027s web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen \u2014 if that is your case the row is wrong, and saying so is more useful than adding a second scanner."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"6e54424179c892f03ef2fd003130ac4bd43f39bbf3b1ca0a0143e25acb80ec87"}},{"ruleId":"P6","level":"note","message":{"text":"No changelog: No CHANGELOG/HISTORY/RELEASES file \u2014 what shipped when isn\u0027t easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)"},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"dda5aa5aed8cbb292c3ef2b733bc138f614293ae6426c85e98bf31ef330d9415"}}],"taxonomies":[{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d","organization":"MITRE","informationUri":"https://cwe.mitre.org/","isComprehensive":false,"shortDescription":{"text":"The MITRE Common Weakness Enumeration (CWE)."},"taxa":[{"id":"CWE-259","guid":"ae9ad959-fbb6-9d5e-892d-3dca66da0b69","name":"Use of Hard-coded Password","shortDescription":{"text":"Use of Hard-coded Password"},"helpUri":"https://cwe.mitre.org/data/definitions/259.html"},{"id":"CWE-77","guid":"332c8ade-6612-9f56-a06b-d8d90b1a8750","name":"Command Injection","shortDescription":{"text":"Command Injection"},"helpUri":"https://cwe.mitre.org/data/definitions/77.html"},{"id":"CWE-78","guid":"2e31ceaf-c7ae-2e5e-9661-cfb1362789cf","name":"OS Command Injection","shortDescription":{"text":"OS Command Injection"},"helpUri":"https://cwe.mitre.org/data/definitions/78.html"},{"id":"CWE-79","guid":"fd45580b-e8c4-fc5e-8c2f-aa8fab0b4dbf","name":"Cross-site Scripting (XSS)","shortDescription":{"text":"Cross-site Scripting (XSS)"},"helpUri":"https://cwe.mitre.org/data/definitions/79.html"},{"id":"CWE-798","guid":"5e8f057d-fee3-995a-a0cb-9fc5b0d174d1","name":"Use of Hard-coded Credentials","shortDescription":{"text":"Use of Hard-coded Credentials"},"helpUri":"https://cwe.mitre.org/data/definitions/798.html"},{"id":"CWE-89","guid":"6d08fdad-37eb-c150-bbf0-d7d946863407","name":"SQL Injection","shortDescription":{"text":"SQL Injection"},"helpUri":"https://cwe.mitre.org/data/definitions/89.html"},{"id":"CWE-94","guid":"75e7f50c-6c2f-dd52-bf40-bf6c52b861fd","name":"Code Injection","shortDescription":{"text":"Code Injection"},"helpUri":"https://cwe.mitre.org/data/definitions/94.html"}]}],"properties":{"codehealthPublication":{"public":true,"notice":"This is the PUBLIC form of this artifact. Findings are listed in full, but the details of SECURITY findings \u2014 which rule fired, in which file, on which line, and how to fix it \u2014 are deliberately withheld, and any secret-scanner results are excluded entirely. Where detail is absent here it was REMOVED FOR PUBLICATION; it is not missing from the analysis. The complete artifact is available from the repository owner.","securityFindingsRedacted":0,"secretScannerRunsExcluded":0}}}]}