{"$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":"D8","name":"Code Coverage","shortDescription":{"text":"Code Coverage"},"helpUri":"https://codehealth.canine.dev/dimensions/D8"},{"id":"D9","name":"Test Distribution","shortDescription":{"text":"Test Distribution"},"helpUri":"https://codehealth.canine.dev/dimensions/D9"},{"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":"D16","name":"Bus Factor","shortDescription":{"text":"Bus Factor"},"helpUri":"https://codehealth.canine.dev/dimensions/D16"},{"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":"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":"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":"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":"D1","level":"warning","message":{"text":"HomeRouteKt.HomeScreen (cyclomatic 21): HomeRouteKt.HomeScreen has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/home/src/main/java/com/hankki/feature/home/HomeRoute.kt"},"region":{"startLine":260}}}],"partialFingerprints":{"codehealthFindingId/v1":"ddd223770baca78f2c3ae2c0fd94ab11a1452d2472aa2d4800b91e09ab5c72eb"}},{"ruleId":"D1","level":"warning","message":{"text":"MyJogboDetailRouteKt.MyJogboDetailScreen (cyclomatic 18): MyJogboDetailRouteKt.MyJogboDetailScreen has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/MyJogboDetailRoute.kt"},"region":{"startLine":126}}}],"partialFingerprints":{"codehealthFindingId/v1":"79e2d07cece9596dd5b079e551c46a8fe2809da0ef21ca3aa3ad94a5a6582740"}},{"ruleId":"D1","level":"warning","message":{"text":"HankkiCountTextFieldKt.HankkiCountTextField (cyclomatic 16): HankkiCountTextFieldKt.HankkiCountTextField has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"core/designsystem/src/main/java/com/hankki/core/designsystem/component/textfield/HankkiCountTextField.kt"},"region":{"startLine":46}}}],"partialFingerprints":{"codehealthFindingId/v1":"70a320f4ff95b01ecea5f7f1de6dbaa3daa659d7fc090445c5e72587e4c09f75"}},{"ruleId":"D2","level":"warning","message":{"text":"HankkiCountTextFieldKt.HankkiCountTextField (cognitive 27): HankkiCountTextFieldKt.HankkiCountTextField has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (25 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"core/designsystem/src/main/java/com/hankki/core/designsystem/component/textfield/HankkiCountTextField.kt"},"region":{"startLine":46}}}],"partialFingerprints":{"codehealthFindingId/v1":"b98e0d62ad5b522bd439acaf07fc87b33fa2fda5c09a20c8d234866baee0f993"}},{"ruleId":"D2","level":"warning","message":{"text":"HomeRouteKt.HomeScreen (cognitive 21): HomeRouteKt.HomeScreen has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 3, match/switch 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth \u2014 checks laid out side by side rather than stacked \u2014 so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/home/src/main/java/com/hankki/feature/home/HomeRoute.kt"},"region":{"startLine":260}}}],"partialFingerprints":{"codehealthFindingId/v1":"bd0b2794a84bb0721e6f72cfaa50fff0bc5ab386562f15b7cf0934ce1855beaa"}},{"ruleId":"D2","level":"warning","message":{"text":"ModRouteKt.ModifyMenuScreen (cognitive 19): ModRouteKt.ModifyMenuScreen has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/edit/mod/ModRoute.kt"},"region":{"startLine":155}}}],"partialFingerprints":{"codehealthFindingId/v1":"e7e3026182f88115a58db2b6a6356c248154cdaa512922b23c5953213bb3d4d6"}},{"ruleId":"D2","level":"warning","message":{"text":"MyJogboDetailRouteKt.MyJogboDetailScreen (cognitive 18): MyJogboDetailRouteKt.MyJogboDetailScreen has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4, match/switch 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/MyJogboDetailRoute.kt"},"region":{"startLine":126}}}],"partialFingerprints":{"codehealthFindingId/v1":"67ffd914fbba7a6d11a52d53d9be12092fe571f21a3cc802cfd5cbbc89f26a3e"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: MyJogboDetailRouteKt.MyJogboDetailScreen: MethodTooLong \u2014 MyJogboDetailScreen runs 179 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 79 over it, 1.79\u00D7 the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/MyJogboDetailRoute.kt"},"region":{"startLine":126}}}],"partialFingerprints":{"codehealthFindingId/v1":"95bc2bb978fcfca8050af1523761c239d06b29f8405912b25f246695e585d73a"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: StoreDetailRouteKt.StoreDetailScreen: MethodTooLong \u2014 StoreDetailScreen runs 170 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 70 over it, 1.70\u00D7 the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/storedetail/src/main/java/com/hankki/feature/storedetail/StoreDetailRoute.kt"},"region":{"startLine":223}}}],"partialFingerprints":{"codehealthFindingId/v1":"5906fea85c80d784702cebf12a5a9175827b3b44fc9ce9f5e77b2375f8c0149e"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: MainScreenKt.MainContent: MethodTooLong \u2014 MainContent runs 160 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 60 over it, 1.60\u00D7 the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/main/src/main/java/com/hankki/feature/main/MainScreen.kt"},"region":{"startLine":208}}}],"partialFingerprints":{"codehealthFindingId/v1":"38c9e4c4f6db3483ee916f358c091abead91ade14fd9bbb8ce5083e1e6bce210"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: TypeKt.hankkiTypography: MethodTooLong \u2014 hankkiTypography runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58\u00D7 the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"core/designsystem/src/main/java/com/hankki/core/designsystem/theme/Type.kt"},"region":{"startLine":242}}}],"partialFingerprints":{"codehealthFindingId/v1":"f3eef4f2915ffa21fabc6504a925ed5e766a373de1dc340f1e3572fba2d05a90"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: MyRouteKt.MyScreen: MethodTooLong \u2014 MyScreen runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40\u00D7 the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/my/src/main/java/com/hankki/feature/my/mypage/MyRoute.kt"},"region":{"startLine":127}}}],"partialFingerprints":{"codehealthFindingId/v1":"0fe1db54d1834375d526e1822928f77fe13ce8b25ccbe1981ba749b26afe5561"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: ModRouteKt.ModifyMenuScreen: MethodTooLong \u2014 ModifyMenuScreen runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33\u00D7 the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/edit/mod/ModRoute.kt"},"region":{"startLine":155}}}],"partialFingerprints":{"codehealthFindingId/v1":"d336d63ab2369f34595e31a5add661e1bc1356607ff823eda38087731021751d"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: HankkiModTextFieldKt.HankkiBaseField: MethodTooLong \u2014 HankkiBaseField runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17\u00D7 the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/storedetail/src/main/java/com/hankki/feature/storedetail/component/HankkiModTextField.kt"},"region":{"startLine":51}}}],"partialFingerprints":{"codehealthFindingId/v1":"8a625abab4fd1c27b8a4213b1f9f21a89264c3d48e67210128648938db1ddeb1"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: NewJogboRouteKt.NewJogboScreen: MethodTooLong \u2014 NewJogboScreen runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16\u00D7 the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/my/src/main/java/com/hankki/feature/my/newjogbo/NewJogboRoute.kt"},"region":{"startLine":103}}}],"partialFingerprints":{"codehealthFindingId/v1":"d4ded8d433e5df63e84b2a25bdd9c3966b645836404fae81361601a7fcc60ca8"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: StoreDetailRouteKt.StoreDetailRoute: MethodTooLong \u2014 StoreDetailRoute runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08\u00D7 the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/storedetail/src/main/java/com/hankki/feature/storedetail/StoreDetailRoute.kt"},"region":{"startLine":71}}}],"partialFingerprints":{"codehealthFindingId/v1":"08d029b3923e75afe5f8d5676eeb630660c02fffbec64702a7ddaf8822551315"}},{"ruleId":"D3","level":"warning","message":{"text":"MethodTooLong: AddMenuRouteKt.AddMenuScreen: MethodTooLong \u2014 AddMenuScreen runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04\u00D7 the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body \u2014 the runs of statements that work on the same values and would earn the same name \u2014 into its own named unit, and have this one call them in order."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/add/addmenu/AddMenuRoute.kt"},"region":{"startLine":85}}}],"partialFingerprints":{"codehealthFindingId/v1":"ed94d450eb000cbf4305072ff0685205ac09ca70d562da2e7239c5f6b177b0c1"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (31 lines \u00D7 2): feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/edit/delete/DeleteSuccessLastRoute.kt:62-92 | feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/edit/delete/DeleteSuccessRoute.kt:67-97 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at \u0060feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/edit/delete/DeleteSuccessLastRoute.kt:62\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":"feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/edit/delete/DeleteSuccessLastRoute.kt"},"region":{"startLine":62}}}],"partialFingerprints":{"codehealthFindingId/v1":"510e6d60a7da9f3520ab4e9a054ef8dddb3aa8d24bcd64e589de4d0056b05fe2"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (28 lines \u00D7 2): feature/login/src/main/java/com/hankki/feature/login/OnboardingRoute.kt:137-164 | feature/login/src/main/java/com/hankki/feature/login/OnboardingRoute.kt:203-230 \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 \u0060feature/login/src/main/java/com/hankki/feature/login/OnboardingRoute.kt:137\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":"feature/login/src/main/java/com/hankki/feature/login/OnboardingRoute.kt"},"region":{"startLine":137}}}],"partialFingerprints":{"codehealthFindingId/v1":"bb788d02a39abb2475fbe5c4713f66be43b4f1bf1141135f5d6586c02e1626dc"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (24\u201325 lines \u00D7 2): core/designsystem/src/main/java/com/hankki/core/designsystem/component/dialog/DoubleButtonDialog.kt:55-79 | core/designsystem/src/main/java/com/hankki/core/designsystem/component/dialog/SingleButtonDialog.kt:43-66 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at \u0060core/designsystem/src/main/java/com/hankki/core/designsystem/component/dialog/DoubleButtonDialog.kt:55\u0060 it begins part-way through the construct above it, 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":"core/designsystem/src/main/java/com/hankki/core/designsystem/component/dialog/DoubleButtonDialog.kt"},"region":{"startLine":55}}}],"partialFingerprints":{"codehealthFindingId/v1":"4baa34097b42bf923d05a20f2ab4f34022f97d6706ee0c13b71203d22371f7de"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (23 lines \u00D7 3): feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/add/addsuccess/AddMenuSuccessRoute.kt:94-116 | feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/edit/delete/DeleteSuccessRoute.kt:100-122 | feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/edit/mod/ModSuccessRoute.kt:93-115 \u2014 the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times. Read the line range as the matched WINDOW rather than a finished unit: at \u0060feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/add/addsuccess/AddMenuSuccessRoute.kt:94\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, 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":"feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/add/addsuccess/AddMenuSuccessRoute.kt"},"region":{"startLine":94}}}],"partialFingerprints":{"codehealthFindingId/v1":"32dd82b79a12aa44291bfa590a05f3cf692c1aa0cc1e75cfe9f00ef257943cab"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (19 lines \u00D7 2): core/designsystem/src/main/java/com/hankki/core/designsystem/component/dialog/DialogWithDescription.kt:34-52 | core/designsystem/src/main/java/com/hankki/core/designsystem/component/dialog/SingleButtonDialog.kt:34-52 \u2014 the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach \u2014 a file they already depend on, or a new one alongside them \u2014 and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at \u0060core/designsystem/src/main/java/com/hankki/core/designsystem/component/dialog/DialogWithDescription.kt:34\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":"core/designsystem/src/main/java/com/hankki/core/designsystem/component/dialog/DialogWithDescription.kt"},"region":{"startLine":34}}}],"partialFingerprints":{"codehealthFindingId/v1":"6bb469768a29cd7ad7cc47398cd72b01c6a190d15155834b52cfe972ed3aabfd"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (18 lines \u00D7 3): feature/login/src/main/java/com/hankki/feature/login/OnboardingRoute.kt:66-83 | feature/login/src/main/java/com/hankki/feature/login/OnboardingRoute.kt:133-150 | feature/login/src/main/java/com/hankki/feature/login/OnboardingRoute.kt:199-216 \u2014 all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites \u2014 resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060feature/login/src/main/java/com/hankki/feature/login/OnboardingRoute.kt:66\u0060 it begins part-way through the construct above it, 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":"feature/login/src/main/java/com/hankki/feature/login/OnboardingRoute.kt"},"region":{"startLine":66}}}],"partialFingerprints":{"codehealthFindingId/v1":"b17c206adc20b366c066909723988a60aeaf9a66b1e5bff7dc61555a9cbe3c9a"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (17 lines \u00D7 2): feature/my/src/main/java/com/hankki/feature/my/newjogbo/NewJogboRoute.kt:258-274 | feature/my/src/main/java/com/hankki/feature/my/newjogbo/NewJogboRoute.kt:284-300 \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 \u0060feature/my/src/main/java/com/hankki/feature/my/newjogbo/NewJogboRoute.kt:258\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":"feature/my/src/main/java/com/hankki/feature/my/newjogbo/NewJogboRoute.kt"},"region":{"startLine":258}}}],"partialFingerprints":{"codehealthFindingId/v1":"3762ee1c1027fbf22160e3101c08889ed2dd65ae3032f6a28e6fb5550900e5a0"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (16 lines \u00D7 3): feature/login/src/main/java/com/hankki/feature/login/OnboardingRoute.kt:85-100 | feature/login/src/main/java/com/hankki/feature/login/OnboardingRoute.kt:152-167 | feature/login/src/main/java/com/hankki/feature/login/OnboardingRoute.kt:218-233 \u2014 all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites \u2014 resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at \u0060feature/login/src/main/java/com/hankki/feature/login/OnboardingRoute.kt:85\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members\u0027 bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/login/src/main/java/com/hankki/feature/login/OnboardingRoute.kt"},"region":{"startLine":85}}}],"partialFingerprints":{"codehealthFindingId/v1":"d5feb0eae3a60d0ba2abaa75adfd569a8adb8de2fd52f900b5f75821d208bb05"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (16 lines \u00D7 2): feature/my/src/main/java/com/hankki/feature/my/newjogbo/NewJogboViewModel.kt:60-75 | feature/my/src/main/java/com/hankki/feature/my/newjogbo/NewJogboViewModel.kt:84-99 \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 \u0060feature/my/src/main/java/com/hankki/feature/my/newjogbo/NewJogboViewModel.kt:60\u0060 it runs out through the closing brace of the declaration holding it \u2014 the window is that declaration\u0027s tail, not a fragment that begins part-way through something, 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":"feature/my/src/main/java/com/hankki/feature/my/newjogbo/NewJogboViewModel.kt"},"region":{"startLine":60}}}],"partialFingerprints":{"codehealthFindingId/v1":"0b7d84a96472e6d499fb904f413b45278edc9962e45bb57be736a2bd373f1215"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (15 lines \u00D7 2): feature/home/src/main/java/com/hankki/feature/home/HomeViewModel.kt:197-211 | feature/report/src/main/java/com/hankki/feature/report/finish/ReportFinishViewModel.kt:66-80 \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 \u0060feature/home/src/main/java/com/hankki/feature/home/HomeViewModel.kt:197\u0060 it begins part-way through the construct above it, 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":"feature/home/src/main/java/com/hankki/feature/home/HomeViewModel.kt"},"region":{"startLine":197}}}],"partialFingerprints":{"codehealthFindingId/v1":"a4db7dd5f430c73626a7216b7cc9b4242592335ca33ac1d27ed64bfe204c9778"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (15 lines \u00D7 2): feature/report/src/main/java/com/hankki/feature/report/main/ReportRoute.kt:235-249 | feature/report/src/main/java/com/hankki/feature/report/searchstore/SearchStoreRoute.kt:174-188 \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 \u0060feature/report/src/main/java/com/hankki/feature/report/main/ReportRoute.kt:235\u0060 it begins part-way through the construct above it, 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. \u2605 These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, \u0060feature/report/src/main/java/com/hankki/feature/report/searchstore/SearchStoreRoute.kt:173\u0060 calls \u0060fillMaxSize\u0060 and \u0060feature/report/src/main/java/com/hankki/feature/report/main/ReportRoute.kt:234\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":"feature/report/src/main/java/com/hankki/feature/report/main/ReportRoute.kt"},"region":{"startLine":235}}}],"partialFingerprints":{"codehealthFindingId/v1":"b6374c9b8aae2f5357b19dde17a07f96bf69d83d62c46fd71b21efc3988bfbf5"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (14 lines \u00D7 2): feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/add/addsuccess/AddMenuSuccessRoute.kt:77-91 | feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/edit/mod/ModSuccessRoute.kt:75-88 \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 \u0060feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/add/addsuccess/AddMenuSuccessRoute.kt:77\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members\u0027 bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/add/addsuccess/AddMenuSuccessRoute.kt"},"region":{"startLine":77}}}],"partialFingerprints":{"codehealthFindingId/v1":"0436eea656e83a0211f7d443b116374c72d44d3eea9b4dfde9e02d52c94202b0"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 2): feature/home/src/main/java/com/hankki/feature/home/HomeViewModel.kt:163-173 | feature/home/src/main/java/com/hankki/feature/home/HomeViewModel.kt:216-226 \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":"feature/home/src/main/java/com/hankki/feature/home/HomeViewModel.kt"},"region":{"startLine":163}}}],"partialFingerprints":{"codehealthFindingId/v1":"8715c0ea0ac5b918159d99e3ffe5b4120e4a62e83c41121a2c319fbe76c8c566"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (9\u201310 lines \u00D7 2): feature/storedetail/src/main/java/com/hankki/feature/storedetail/navigation/navigateStoreDetail.kt:152-161 | feature/storedetail/src/main/java/com/hankki/feature/storedetail/navigation/navigateStoreDetail.kt:168-176 \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 \u0060feature/storedetail/src/main/java/com/hankki/feature/storedetail/navigation/navigateStoreDetail.kt:168\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":"feature/storedetail/src/main/java/com/hankki/feature/storedetail/navigation/navigateStoreDetail.kt"},"region":{"startLine":152}}}],"partialFingerprints":{"codehealthFindingId/v1":"4160a8f693cbf093285b65dd370c0f53b0903bac3fb793a5b53bf0a5054a96fb"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 2): feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/MyJogboDetailViewModel.kt:42-51 | feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/MyJogboDetailViewModel.kt:61-70 \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 \u0060feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/MyJogboDetailViewModel.kt:42\u0060 it begins part-way through the construct above it, 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":"feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/MyJogboDetailViewModel.kt"},"region":{"startLine":42}}}],"partialFingerprints":{"codehealthFindingId/v1":"99862396fbf58392f3f09cd20d10dbaa0112f31834ba13686cb89ccbb0a3fe21"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (6\u20137 lines \u00D7 2): feature/report/src/main/java/com/hankki/feature/report/main/ReportViewModel.kt:101-106 | feature/report/src/main/java/com/hankki/feature/report/main/ReportViewModel.kt:114-120 \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 \u0060feature/report/src/main/java/com/hankki/feature/report/main/ReportViewModel.kt:101\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. 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. 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":"feature/report/src/main/java/com/hankki/feature/report/main/ReportViewModel.kt"},"region":{"startLine":101}}}],"partialFingerprints":{"codehealthFindingId/v1":"fdccf7242710871008269bcb4b1601a6f52ef5d55bc719b8e86c06647bf558e6"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (10 lines \u00D7 3): data/home/src/main/java/com/hankki/data/home/dto/response/FavoritesResponseDto.kt:25-34 | data/report/src/main/java/com/hankki/data/report/dto/response/FavoritesResponseDto.kt:25-34 | data/storedetail/src/main/java/com/hankki/data/storedetail/response/FavoritesResponseDto.kt:25-34 \u2014 before extracting anything, compare \u0060data/home/src/main/java/com/hankki/data/home/dto/response/FavoritesResponseDto.kt\u0060 and \u0060data/report/src/main/java/com/hankki/data/report/dto/response/FavoritesResponseDto.kt\u0060 as WHOLE FILES: 92% of the shorter file\u0027s lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it \u2014 treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at \u0060data/home/src/main/java/com/hankki/data/home/dto/response/FavoritesResponseDto.kt:25\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members\u0027 bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it. Note first that the copies are not typed on the same thing: \u0060JogboResponseEntity\u0060 names \u0060com.hankki.domain.home.entity.response.JogboResponseEntity\u0060 in one and \u0060com.hankki.domain.report.entity.response.JogboResponseEntity\u0060 in another \u2014 different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"data/home/src/main/java/com/hankki/data/home/dto/response/FavoritesResponseDto.kt"},"region":{"startLine":25}}}],"partialFingerprints":{"codehealthFindingId/v1":"b206af934c710c61eaefa25349da0072c62688a286e79ebb04b8a64dd8e1b282"}},{"ruleId":"D4","level":"warning","message":{"text":"Duplicated block (11 lines \u00D7 2): feature/login/src/main/java/com/hankki/feature/login/OnboardingRoute.kt:169-179 | feature/login/src/main/java/com/hankki/feature/login/OnboardingRoute.kt:235-245 \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 \u0060feature/login/src/main/java/com/hankki/feature/login/OnboardingRoute.kt:169\u0060 it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows \u2014 the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members\u0027 bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run \u2014 a one-line delegation has no helper inside it to lift \u2014 so generate the run from the set it enumerates, or accept it and keep each member\u0027s own documentation with it."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/login/src/main/java/com/hankki/feature/login/OnboardingRoute.kt"},"region":{"startLine":169}}}],"partialFingerprints":{"codehealthFindingId/v1":"38cd40b5c9e377459d08fac75311f6affc538177b1a532aac18260fc91b2a7f7"}},{"ruleId":"D8","level":"error","message":{"text":"No automated tests: No automated tests \u2014 no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (JUnit (with Kotest or MockK on Kotlin)), and run it in CI so the gap cannot reopen."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"3132564c6310e5d01a231f252a02d5d2f5a542c0a8fa29a14c89693f1e3df871"}},{"ruleId":"D9","level":"note","message":{"text":"No tests found: No test suite could be collected \u2014 no discoverable tests to count. If this repository does test, wiring the suite to a framework a runner can collect (JUnit (with Kotest or MockK on Kotlin)) is what makes it countable here; a pipeline step that invokes a runner is not evidence on its own, because a runner over an empty suite passes. Tests written as plain executables or shell/PowerShell harnesses are not collectible this way and are not scored here."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"c9bf64cbb5a4ae13d6bcd01fa3bc8d2879d860c73bc67f176ee3c2cecb8adce3"}},{"ruleId":"D16","level":"note","message":{"text":"Off-boarding risk: anonymized user #1: If anonymized user #1 becomes unavailable, 16 significant file(s) lose their only recent owner: feature/storedetail/src/main/java/com/hankki/feature/storedetail/component/HankkiModTextField.kt, feature/storedetail/src/main/java/com/hankki/feature/storedetail/StoreDetailReportRoute.kt, feature/storedetail/src/main/java/com/hankki/feature/storedetail/component/StoreDetailMapBox.kt, feature/storedetail/src/main/java/com/hankki/feature/storedetail/StoreDetailViewModel.kt, feature/login/src/main/java/com/hankki/feature/login/LoginRoute.kt, feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/edit/mod/ModViewModel.kt, feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/EditMenuBottomSheet.kt, feature/storedetail/src/main/java/com/hankki/feature/storedetail/component/StoreDetailButton.kt (\u002B8 more). Pair on, review, or document these before any departure."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"efa83c6daca341f91c7dc635c3ff374cab1d463ade6f4ddc0dd7ea8ae783aa87"}},{"ruleId":"D16","level":"note","message":{"text":"Off-boarding risk: anonymized user #2: If anonymized user #2 becomes unavailable, 11 significant file(s) lose their only recent owner: feature/home/src/main/java/com/hankki/feature/home/HomeRoute.kt, feature/home/src/main/java/com/hankki/feature/home/HomeViewModel.kt, feature/report/src/main/java/com/hankki/feature/report/finish/ReportFinishRoute.kt, core/designsystem/src/main/java/com/hankki/core/designsystem/component/textfield/HankkiTitleTextField.kt, feature/report/src/main/java/com/hankki/feature/report/searchstore/SearchStoreViewModel.kt, core/common/src/main/java/com/hankki/core/common/extension/Modifier.kt, core/designsystem/src/main/java/com/hankki/core/designsystem/component/textfield/HankkiTextField.kt, feature/home/src/main/java/com/hankki/feature/home/component/HankkiStateChip.kt (\u002B3 more). Pair on, review, or document these before any departure."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"2bdc752bb6a9b8106b99638e0dedd468e70cab5d1ee2a2d13ebe80b667c5c7a4"}},{"ruleId":"D16","level":"note","message":{"text":"Off-boarding risk: anonymized user #3: If anonymized user #3 becomes unavailable, 10 significant file(s) lose their only recent owner: feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/MyJogboDetailRoute.kt, feature/my/src/main/java/com/hankki/feature/my/newjogbo/NewJogboRoute.kt, feature/my/src/main/java/com/hankki/feature/my/myjogbo/MyJogboRoute.kt, core/designsystem/src/main/java/com/hankki/core/designsystem/component/textfield/HankkiCountTextField.kt, feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/MyJogboDetailViewModel.kt, feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/component/JogboFolder.kt, feature/my/src/main/java/com/hankki/feature/my/myjogbo/MyJogboViewModel.kt, feature/my/src/main/java/com/hankki/feature/my/myjogbo/component/JogboItem.kt (\u002B2 more). Pair on, review, or document these before any departure."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"38b5babca4099aedc352bae9057985d9f2a60ee4edf9be6feebb197a58a472c2"}},{"ruleId":"D17","level":"warning","message":{"text":"TodoComment: // TODO Add interactions to wait for when your app is fully drawn. \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":"baselineprofile/src/main/java/com/hankki/baselineprofile/StartupBenchmarks.kt"},"region":{"startLine":65}}}],"partialFingerprints":{"codehealthFindingId/v1":"39f2591dbf41711d00dbad5b7e068cd0da821a0c4f4d6b80e0357ac5f3ccaae0"}},{"ruleId":"D17","level":"warning","message":{"text":"TodoComment: // TODO Write more interactions to optimize advanced journeys of your app. \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":"baselineprofile/src/main/java/com/hankki/baselineprofile/BaselineProfileGenerator.kt"},"region":{"startLine":58}}}],"partialFingerprints":{"codehealthFindingId/v1":"99424121decc0dd3028697e61ef3ee0582dda8d2122a9c117674c4c60cb5fc1d"}},{"ruleId":"D19","level":"note","message":{"text":"Documentation: no installation or build instructions: No build/run instructions for an Android app. Add setup steps: install Gradle, clone the repo, sync project, and open Android Studio to run the app."},"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 use the app\u0027s features (e.g. add a restaurant, view the map). Add an inline code snippet or a short demo of one feature, such as opening the map and adding a restaurant."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"README.md"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"1355eb4e127a4bc9236772ce1c46f09510aa9286e7a06d1e47f308229df19049"}},{"ruleId":"D19","level":"note","message":{"text":"Documentation: no licence statement: No licence statement in the README. Insert a line stating the project\u0027s license (e.g. MIT) so it is visible from the top of the page."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"README.md"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"bc71d4465cafafc3df7a1b646a8cd5f9a306761b307dc199a6de8c1c35d8b21d"}},{"ruleId":"D29","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"3b0367e7ea9bdd389991714fe83002077989c3eac9db9d8bdc3becd4dd073aee"},"taxa":[{"id":"CWE-926","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}}]},{"ruleId":"D34","level":"note","message":{"text":"Orphaned files with no living knowledge: 24 of 97 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; 97 of the 371 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: feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/add/addmenu/AddMenuViewModel.kt, core/network/src/main/java/com/hankki/core/network/ContentUriRequestBody.kt, gradle/projectDependencyGraph.gradle, feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/edit/delete/DeleteSuccessRoute.kt, feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/edit/mod/ModSuccessRoute.kt, feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/add/addsuccess/AddMenuSuccessRoute.kt, feature/storedetail/src/main/java/com/hankki/feature/storedetail/editbottomsheet/edit/editmenu/EditMenuViewModel.kt, feature/report/src/main/java/com/hankki/feature/report/finish/ReportFinishViewModel.kt (and 16 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":"warning","message":{"text":"Change-coupling hub: MainScreen.kt \u2192 HomeNavigation.kt, MainActivity.kt, MainTab.kt, MyNavigation.kt, ReportNavigation.kt: \u0060feature/main/src/main/java/com/hankki/feature/main/MainScreen.kt\u0060 changes together with 5 other files \u2014 \u0060feature/home/src/main/java/com/hankki/feature/home/navigation/HomeNavigation.kt\u0060, \u0060feature/main/src/main/java/com/hankki/feature/main/MainActivity.kt\u0060, \u0060feature/main/src/main/java/com/hankki/feature/main/MainTab.kt\u0060, \u0060feature/my/src/main/java/com/hankki/feature/my/navigation/MyNavigation.kt\u0060, \u0060feature/report/src/main/java/com/hankki/feature/report/navigation/ReportNavigation.kt\u0060 \u2014 none of which declares a dependency on it: one file is the hub of 5 separate couplings, not 5 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 5."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/main/src/main/java/com/hankki/feature/main/MainScreen.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"694a3ef3004902de26ae1c5646f4d8a6407e3f59d49240d4467c4f9866778849"}},{"ruleId":"D35","level":"warning","message":{"text":"Change-coupling hub: ReportService.kt \u2192 ReportDataSource.kt, ReportRepositoryImpl.kt, ReportRepository.kt: \u0060data/report/src/main/java/com/hankki/data/report/service/ReportService.kt\u0060 changes together with 3 other files \u2014 \u0060data/report/src/main/java/com/hankki/data/report/datasource/ReportDataSource.kt\u0060, \u0060data/report/src/main/java/com/hankki/data/report/repositoryimpl/ReportRepositoryImpl.kt\u0060, \u0060domain/report/src/main/java/com/hankki/domain/report/repository/ReportRepository.kt\u0060 \u2014 none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"data/report/src/main/java/com/hankki/data/report/service/ReportService.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"1bd12b79cfdf41cf245cdd622cbf86b2d0e3ae75dfb18f352a531515aff92925"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: ReportDataSourceImpl.kt \u2194 ReportRepositoryImpl.kt: \u0060data/report/src/main/java/com/hankki/data/report/datasourceimpl/ReportDataSourceImpl.kt\u0060 and \u0060data/report/src/main/java/com/hankki/data/report/repositoryimpl/ReportRepositoryImpl.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 \u006007209f94\u0060 Feature #188: feat apis; \u00605b9eadea\u0060 Feature #128: connect jogbo apis; \u006066bc0bda\u0060 Feature #128: connect userName api \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"data/report/src/main/java/com/hankki/data/report/datasourceimpl/ReportDataSourceImpl.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"2f3157befe2e6e9be6b784409bd0071ccefea8b3f3cdd7ba8f6dc86daed1ec16"}},{"ruleId":"D35","level":"warning","message":{"text":"Change-coupling hub: HomeRoute.kt \u2192 HankkiTopBar.kt, HomeState.kt, HankkiFilterChip.kt, HomeNavigation.kt: \u0060feature/home/src/main/java/com/hankki/feature/home/HomeRoute.kt\u0060 changes together with 4 other files \u2014 \u0060core/designsystem/src/main/java/com/hankki/core/designsystem/component/topappbar/HankkiTopBar.kt\u0060, \u0060feature/home/src/main/java/com/hankki/feature/home/HomeState.kt\u0060, \u0060feature/home/src/main/java/com/hankki/feature/home/component/HankkiFilterChip.kt\u0060, \u0060feature/home/src/main/java/com/hankki/feature/home/navigation/HomeNavigation.kt\u0060 \u2014 none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/home/src/main/java/com/hankki/feature/home/HomeRoute.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"60b5022731748b8e0a1edd8cf3af1ca29790cd5b7701517b9b45acaeb1caa562"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: ReportDataSource.kt \u2194 ReportRepository.kt: \u0060data/report/src/main/java/com/hankki/data/report/datasource/ReportDataSource.kt\u0060 and \u0060domain/report/src/main/java/com/hankki/domain/report/repository/ReportRepository.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 \u006007209f94\u0060 Feature #188: feat apis; \u00605b9eadea\u0060 Feature #128: connect jogbo apis; \u006066bc0bda\u0060 Feature #128: connect userName api \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"data/report/src/main/java/com/hankki/data/report/datasource/ReportDataSource.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"6281f661327708e9917d7d2bc87c3867f217007cab86e598b43daa99ad6adc29"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: ReportDataSourceImpl.kt \u2194 ReportRepository.kt: \u0060data/report/src/main/java/com/hankki/data/report/datasourceimpl/ReportDataSourceImpl.kt\u0060 and \u0060domain/report/src/main/java/com/hankki/domain/report/repository/ReportRepository.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 \u006007209f94\u0060 Feature #188: feat apis; \u00605b9eadea\u0060 Feature #128: connect jogbo apis; \u006066bc0bda\u0060 Feature #128: connect userName api \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"data/report/src/main/java/com/hankki/data/report/datasourceimpl/ReportDataSourceImpl.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"b495a92a7d588ca59372b9ab6bb28c3160283caf0eb6133a5e1ab5887fa774ac"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: JogboFolder.kt \u2194 JogboShareButton.kt: \u0060feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/component/JogboFolder.kt\u0060 and \u0060feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/component/JogboShareButton.kt\u0060 change together 76% of the time (13 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package \u2014 so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are \u00607b0f4fca\u0060 Chore #286 : add modifier and change visibility; \u0060bbe020f7\u0060 Chore #245 : change painter to imagevector; \u0060b4c1af4a\u0060 Add #243 : add type Body2,Body7 \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/component/JogboFolder.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"ccd41811844f0be8203145a4b2cac3628d3fba7b6d8e3a8865526b6748eb3626"}},{"ruleId":"D35","level":"warning","message":{"text":"Change-coupling hub: MyJogboDetailRoute.kt \u2192 BaseEmptyView.kt, MyJogboDetailState.kt, MyStoreRoute.kt: \u0060feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/MyJogboDetailRoute.kt\u0060 changes together with 3 other files \u2014 \u0060core/designsystem/src/main/java/com/hankki/core/designsystem/component/layout/BaseEmptyView.kt\u0060, \u0060feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/MyJogboDetailState.kt\u0060, \u0060feature/my/src/main/java/com/hankki/feature/my/mystore/MyStoreRoute.kt\u0060 \u2014 none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/MyJogboDetailRoute.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"3a3040021f5671b1b50df4e71bf9cb7906fc2fa9ebe123c8207224ee15b9eaa1"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: MyJogboRoute.kt \u2194 MyJogboState.kt: \u0060feature/my/src/main/java/com/hankki/feature/my/myjogbo/MyJogboRoute.kt\u0060 and \u0060feature/my/src/main/java/com/hankki/feature/my/myjogbo/MyJogboState.kt\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 the same directory, and in this ecosystem sibling files there normally share one namespace/package \u2014 so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; 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 \u0060f19f4527\u0060 Chore #278 : show dialog when deleted jogbo; \u0060d448b093\u0060 Mod #223 : block double click; \u0060d2780340\u0060 Mod #213 : rename MyJogbo parameter and function \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/my/src/main/java/com/hankki/feature/my/myjogbo/MyJogboRoute.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"e17af187da2b2216f4d5db7768224f6114919d2dde7287fa1e69d7326f1dd47e"}},{"ruleId":"D35","level":"warning","message":{"text":"Change-coupling hub: MyRoute.kt \u2192 DoubleButtonDialog.kt, JogboShareButton.kt, MoveToHomeButton.kt, ArrowIconButton.kt: \u0060feature/my/src/main/java/com/hankki/feature/my/mypage/MyRoute.kt\u0060 changes together with 4 other files \u2014 \u0060core/designsystem/src/main/java/com/hankki/core/designsystem/component/dialog/DoubleButtonDialog.kt\u0060, \u0060feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/component/JogboShareButton.kt\u0060, \u0060feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/component/MoveToHomeButton.kt\u0060, \u0060feature/my/src/main/java/com/hankki/feature/my/mypage/component/ArrowIconButton.kt\u0060 \u2014 none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/my/src/main/java/com/hankki/feature/my/mypage/MyRoute.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"247b094043df7889f43dbc948cb213402db0c7e93ad3adcf04f6033974c1e105"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: JogboFolder.kt \u2194 MoveToHomeButton.kt: \u0060feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/component/JogboFolder.kt\u0060 and \u0060feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/component/MoveToHomeButton.kt\u0060 change together 59% of the time (10 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package \u2014 so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; 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 \u0060bbe020f7\u0060 Chore #245 : change painter to imagevector; \u0060b4c1af4a\u0060 Add #243 : add type Body2,Body7; \u006056403012\u0060 Chore #245 : change painter to imagevector \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/component/JogboFolder.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"5e90833795bf64a17c3a3f39e04e284bb6612f841d22fa254c6516300fc299b2"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: AddPhotoButton.kt \u2194 StoreNameSearchButton.kt: \u0060core/designsystem/src/main/java/com/hankki/core/designsystem/component/button/AddPhotoButton.kt\u0060 and \u0060core/designsystem/src/main/java/com/hankki/core/designsystem/component/button/StoreNameSearchButton.kt\u0060 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package \u2014 so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; 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 \u0060b4c1af4a\u0060 Add #243 : add type Body2,Body7; \u00608f0193ea\u0060 Add #243 : add type Body2,Body7; \u0060a5c8858d\u0060 Add #243 : add type Body2,Body7 \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"core/designsystem/src/main/java/com/hankki/core/designsystem/component/button/AddPhotoButton.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"a4360d13872c3671ff75c2190a7aa7e9949240d1a6a897b962623a2aa62ce65e"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: HankkiFilterChip.kt \u2194 HankkiStateChip.kt: \u0060feature/home/src/main/java/com/hankki/feature/home/component/HankkiFilterChip.kt\u0060 and \u0060feature/home/src/main/java/com/hankki/feature/home/component/HankkiStateChip.kt\u0060 change together 53% of the time (8 of the 15 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 the same directory, and in this ecosystem sibling files there normally share one namespace/package \u2014 so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; 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 \u0060a357e11d\u0060 Feature #248: change chip design; \u0060b07851fa\u0060 Feature #248: change chip design; \u0060ed07f6a4\u0060 Feature #248: change chip design \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/home/src/main/java/com/hankki/feature/home/component/HankkiFilterChip.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"d5807affdd9b0c8d71deb5491aca2069407da6ca4a9b137b3e55858e97d3bb73"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: JogboShareButton.kt \u2194 MoveToHomeButton.kt: \u0060feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/component/JogboShareButton.kt\u0060 and \u0060feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/component/MoveToHomeButton.kt\u0060 change together 53% of the time (9 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package \u2014 so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; 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 \u0060bbe020f7\u0060 Chore #245 : change painter to imagevector; \u0060b4c1af4a\u0060 Add #243 : add type Body2,Body7; \u006056403012\u0060 Chore #245 : change painter to imagevector \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/my/src/main/java/com/hankki/feature/my/myjogbodetail/component/JogboShareButton.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"889ccef245db694be7b21d0f583ad7c90238a377f846743b721e3c1c560e3944"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: ReportRoute.kt \u2194 ReportState.kt: \u0060feature/report/src/main/java/com/hankki/feature/report/main/ReportRoute.kt\u0060 and \u0060feature/report/src/main/java/com/hankki/feature/report/main/ReportState.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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package \u2014 so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; 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 \u0060b92c5f7e\u0060 Fix #226: add image error dialog; \u00600f4d5285\u0060 Fix #169: check university before report; \u0060bf779353\u0060 Feature #83: feat Image picker \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/report/src/main/java/com/hankki/feature/report/main/ReportRoute.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"82b5f98e0d7b09ed9b88d8e78e654c0463a30c50f95a5813c416d7849169a2d0"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: ReportFinishCard.kt \u2194 ReportRoute.kt: \u0060feature/report/src/main/java/com/hankki/feature/report/finish/component/ReportFinishCard.kt\u0060 and \u0060feature/report/src/main/java/com/hankki/feature/report/main/ReportRoute.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 \u0060b4c1af4a\u0060 Add #243 : add type Body2,Body7; \u00608f0193ea\u0060 Add #243 : add type Body2,Body7; \u0060a5c8858d\u0060 Add #243 : add type Body2,Body7 \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"feature/report/src/main/java/com/hankki/feature/report/finish/component/ReportFinishCard.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"33a26ca500f7809ff88c761f3abc1f34c17d48e254bbf95c0bcab6e943252d49"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: ImageDoubleButtonDialog.kt \u2194 StoreDetailRoute.kt: \u0060core/designsystem/src/main/java/com/hankki/core/designsystem/component/dialog/ImageDoubleButtonDialog.kt\u0060 and \u0060feature/storedetail/src/main/java/com/hankki/feature/storedetail/StoreDetailRoute.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 \u0060b4c1af4a\u0060 Add #243 : add type Body2,Body7; \u00608f0193ea\u0060 Add #243 : add type Body2,Body7; \u0060a5c8858d\u0060 Add #243 : add type Body2,Body7 \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"core/designsystem/src/main/java/com/hankki/core/designsystem/component/dialog/ImageDoubleButtonDialog.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"f4392466d332962131354cfa174aaf5f9e35ece6e071c8fb2c6136669c900a20"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: DoubleButtonDialog.kt \u2194 ImageDoubleButtonDialog.kt: \u0060core/designsystem/src/main/java/com/hankki/core/designsystem/component/dialog/DoubleButtonDialog.kt\u0060 and \u0060core/designsystem/src/main/java/com/hankki/core/designsystem/component/dialog/ImageDoubleButtonDialog.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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package \u2014 so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; 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 \u0060b4c1af4a\u0060 Add #243 : add type Body2,Body7; \u00608f0193ea\u0060 Add #243 : add type Body2,Body7; \u0060a5c8858d\u0060 Add #243 : add type Body2,Body7 \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"core/designsystem/src/main/java/com/hankki/core/designsystem/component/dialog/DoubleButtonDialog.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"1212ea3f7b0bf50ebacac3d755c7e6569941d4a62713441a6aee5d9788552c8e"}},{"ruleId":"D35","level":"warning","message":{"text":"Change coupling: HomeRepository.kt \u2194 HomeState.kt: \u0060domain/home/src/main/java/com/hankki/domain/home/repository/HomeRepository.kt\u0060 and \u0060feature/home/src/main/java/com/hankki/feature/home/HomeState.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 \u0060220385f1\u0060 Feature #90: feat jogboList api; \u0060a9931c9a\u0060 Feature #83: feat get storeListPins; \u006038bea6e7\u0060 Feature #83: feat get storeList \u2014 run \u0060git show\u0060 on any of them."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"domain/home/src/main/java/com/hankki/domain/home/repository/HomeRepository.kt"},"region":{"startLine":1}}}],"partialFingerprints":{"codehealthFindingId/v1":"e649b935f1f0981fc774227176e93a123705984b1026249d96b680a93d8ddb03"}},{"ruleId":"DM8","level":"note","message":{"text":"Primitive data clump: [id, imagetype, isadded, title]: The parameters [id, imagetype, isadded, title] travel together across 3 signatures and were confirmed as a coherent concept by the model \u2014 that\u0027s a missing value object. Extracting them into one type (e.g. \u0060Address\u0060, \u0060Money\u0060, \u0060Coordinate\u0060) removes repetition, prevents argument-order mistakes, and gives the concept a home for its rules."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"domain/storedetail/src/main/java/com/hankki/domain/storedetail/entity/JogboResponseEntity.kt"},"region":{"startLine":3}}}],"partialFingerprints":{"codehealthFindingId/v1":"3fa16d482363dbf35a61711b75de68ef0529b844bc37739929dd602636c5bbea"}},{"ruleId":"DM8","level":"note","message":{"text":"Primitive data clump: [category, heartcount, id, imageurl, lowestprice, name]: The parameters [category, heartcount, id, imageurl, lowestprice, name] travel together across 3 signatures and were confirmed as a coherent concept by the model \u2014 that\u0027s a missing value object. Extracting them into one type (e.g. \u0060Address\u0060, \u0060Money\u0060, \u0060Coordinate\u0060) removes repetition, prevents argument-order mistakes, and gives the concept a home for its rules."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"domain/my/src/main/java/com/hankki/domain/my/entity/response/MyJogboDetailEntity.kt"},"region":{"startLine":10}}}],"partialFingerprints":{"codehealthFindingId/v1":"49975c87c27a7639a56854c70e61dbaf6fb2b4b34240299280136c4b050369ee"}},{"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":"M3","level":"note","message":{"text":"No tests/ separation: No test surface was found \u2014 this check walked the tree for authored source in the languages it models (\u0060.cs\u0060, \u0060.vb\u0060, \u0060.fs\u0060, \u0060.java\u0060, \u0060.kt\u0060, \u0060.scala\u0060, \u0060.py\u0060, \u0060.php\u0060, \u0060.rb\u0060, \u0060.ex\u0060, \u0060.exs\u0060, \u0060.go\u0060, \u0060.erl\u0060, \u0060.hrl\u0060, \u0060.swift\u0060, \u0060.dart\u0060, \u0060.rs\u0060, \u0060.ts\u0060, \u0060.tsx\u0060, \u0060.mts\u0060, \u0060.cts\u0060) and found none of it test-shaped. \u2605 \u0060.js\u0060, \u0060.jsx\u0060, \u0060.mjs\u0060 and \u0060.cjs\u0060 are NOT in that walk, so a Jest or Mocha suite written in plain JavaScript is invisible to it and this row is then wrong. If that is your case, say so rather than moving anything. Otherwise there are no tests here to separate from production code, so the folder question hasn\u0027t been reached yet."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"999e0c784909c76b6346a705ee63961fe363ed1cd6a94e3f80e2ebe7820ccd5d"}},{"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-926","guid":"0d9b5579-5549-555a-8a97-f9cc14f3ad4a","name":"CWE-926","shortDescription":{"text":"CWE-926"},"helpUri":"https://cwe.mitre.org/data/definitions/926.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":1,"secretScannerRunsExcluded":0}},"redactionTokens":["A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."]}]}