Public report of mishka-group/mishka_chelekom, published 15 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 15 November 2026, 12:12 UTC · Survey ID cd_9451373cd42945e0b432dd7749805c7c

mishka-group/mishka_chelekom

Measured 15 November 2026, 12:10 UTC, at code version 6354c18

CAI score 38out of 100 Weak
CriticalWeakAdequateStrongExemplary
Up 2 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A large codebase: 202,342 lines of product code in 8 projects, tests not counted · Estimated rebuild effort: about 1.5 person-years · Weakest lens: Security and Compliance, 30

Findings by how serious they are

136 critical 658 serious 66 minor

24 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
15 November 2026, 12:10 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

60of 60 dimensions measured by tools.
834of 860 findings point to an exact file and line, so you can open each one in the code. The other 26 concern the repository as a whole, such as missing documentation.
60dimensions across 7 lenses, read from 202,342 lines of product code in 8 projects.
Chapters

Executive summary

mishka-group/mishka_chelekom falls short of our standard for a preview release because we found no encryption of stored data, no key vault and no enforced HTTPS and no access checks on the code's endpoints or handlers. It scores 38 out of 100 and is rated Weak, and 14 of its 136 critical findings are security problems in the build pipeline and in its automatic dependency updates.

Security and Compliance, at 30, is the weakest lens and counts most in the score. The best first steps are encrypting the sensitive stored data and keeping its keys in a vault and adding access checks, each worth about 5 points. Raising Security and Compliance to 68 would lift the score to about 44.

Eleven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two secrets can leak from the build pipeline, and twenty-seven form fields can't be read by a screen reader. Pinning each tool to an exact version, limiting each secret to its own step and labelling the form fields would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once. The 16 uses of packages that aren't listed need adding to the project's list of dependencies.

The product code is 202,342 lines, about €210,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Security and Compliance 30 · counts for 46%Code Health 38 · counts for 25%Production Readiness 38 · counts for 14%Accessibility 43 · counts for 8%Maturity 66 · counts for 4%Architecture 76 · counts for 2%Performance 100 · counts for 1%

If Security and Compliance rose from 30 to 68, the lowest score rated Strong, the score would rise from 38 to about 44.

Code composition: what the lines of code are
Product code 81%Tests 19%
New since the last survey: 316 findings

These 316 critical or serious findings weren't in the previous survey, on 31 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

  • Cyclomatic Complexity · MishkaCalendar.row_node (cyclomatic 20) development/mob/lib/mishka_mob/components/mishka_calendar.ex
  • Cyclomatic Complexity · MishkaCalendar.lane_node (cyclomatic 18) development/mob/lib/mishka_mob/components/mishka_calendar.ex
  • Cyclomatic Complexity · MishkaCalendar.week_block (cyclomatic 18) development/mob/lib/mishka_mob/components/mishka_calendar.ex
  • Cognitive Complexity · MishkaCalendar.row_node (cognitive 19) development/mob/lib/mishka_mob/components/mishka_calendar.ex
  • Cognitive Complexity · MishkaCalendar.lane_node (cognitive 18) development/mob/lib/mishka_mob/components/mishka_calendar.ex
  • Cognitive Complexity · MishkaCalendar.week_block (cognitive 17) development/mob/lib/mishka_mob/components/mishka_calendar.ex
  • God Classes · FileTooLong: showcase/preview.ex development/web/lib/development_web/live/showcase/preview.ex
  • God Classes · FileTooLong: components/mishka_calendar.ex development/mob/lib/mishka_mob/components/mishka_calendar.ex
  • God Classes · FileTooLong: components/calendar.ex development/mob/lib/mishka_mob/showcase/components/calendar.ex
  • Code Duplication · Near-duplicate member pair (129 shared lines) development/mob/lib/mishka_mob/showcase/components/nav_link.ex
  • Code Duplication · Edited copy of a member (110 corresponding lines) development/mob/lib/mishka_mob/showcase/components/menu.ex
  • Code Duplication · Members sharing a duplicated core (66 members, 50+ identical tokens) development/mob/lib/mishka_mob/showcase/components/accordion.ex
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) development/web/lib/development_web/live/showcase/headless_baseui_examples.ex
  • Code Duplication · Edited copy of a member (36 corresponding lines) lib/mix/tasks/mishka.ui.gen.components.ex
  • Code Duplication · Edited copy of a member (202 corresponding lines) development/mob/lib/mishka_mob/showcase/components/action_icon.ex
  • Code Duplication · Edited copies of one member (3 members, 152+ corresponding lines) development/mob/lib/mishka_mob/showcase/components/dialog.ex
  • Code Duplication · Edited copies of one member (3 members, 22+ corresponding lines) lib/mix/tasks/mishka.ui.gen.component.ex
  • Code Duplication · Edited copy of a member (27 corresponding lines) lib/mishka_chelekom/generators/npm.ex
  • Code Duplication · Edited copy of a member (23 corresponding lines) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt
  • Code Duplication · Edited copy of a member (14 corresponding lines) development/mob/lib/mishka_mob/components/mishka_highlight.ex
  • Code Duplication · Edited copy of a member (119 corresponding lines) development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex
  • Code Duplication · Edited copy of a member (21 corresponding lines) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt
  • Code Duplication · Edited copy of a member (10 corresponding lines) development/web/lib/development_web/components/combobox.ex
  • Code Duplication · Edited copy of a member (13 corresponding lines) development/mob/lib/mishka_mob/components/mishka_accordion.ex
  • Code Duplication · Edited copy of a member (8 corresponding lines) development/web/lib/development_web/components/combobox.ex
  • Code Duplication · Edited copy of a member (18 corresponding lines) lib/mix/tasks/mishka.assets.deps.ex
  • Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) development/web/lib/development_web/components/file_field.ex
  • Code Duplication · Edited copy of a member (10 corresponding lines) development/web/lib/development_web/components/checkbox_card.ex
  • Code Duplication · Edited copy of a member (11 corresponding lines) development/web/lib/development_web/live/showcase/example_source.ex
  • Code Duplication · Edited copy of a member (11 corresponding lines) development/mob/lib/mishka_mob/components/mishka_pills_input.ex
  • Code Duplication · Edited copy of a member (18 corresponding lines) development/mob/lib/mishka_mob/showcase/components/preview_card.ex
  • Code Duplication · Edited copy of a member (17 corresponding lines) development/mob/lib/mishka_mob/components/mishka_alpha_slider.ex
  • Code Duplication · Edited copy of a member (13 corresponding lines) lib/mishka_chelekom/generators/assets.ex
  • Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) development/mob/lib/mishka_mob/components/mishka_burger.ex
  • Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) lib/mix/tasks/mishka.ui.gen.component.ex
  • Code Duplication · Edited copy of a member (23 corresponding lines) lib/mix/tasks/mishka.ui.gen.components.ex
  • Code Duplication · Edited copy of a member (22 corresponding lines) lib/mishka_chelekom/mcp/resources/list_sizes.ex
  • Code Duplication · Edited copy of a member (12 corresponding lines) development/mob/lib/mishka_mob/components/mishka_popover.ex
  • Code Duplication · Edited copy of a member (9 corresponding lines) development/web/lib/development_web/components/headless/autocomplete.ex
  • Code Duplication · Edited copy of a member (13 corresponding lines) lib/mishka_chelekom/cms_bundle_exporter.ex
  • Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) development/web/lib/development_web/components/headless/file_input.ex
  • Code Duplication · Edited copy of a member (7 corresponding lines) lib/mix/tasks/mishka.ui.add.ex
  • Code Duplication · Edited copy of a member (18 corresponding lines) development/mob/lib/mishka_mob/components/mishka_color_input.ex
  • Code Duplication · Edited copy of a member (19 corresponding lines) development/mob/lib/mishka_mob/components/mishka_combobox.ex
  • Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) development/mob/lib/mishka_mob/dice_screen.ex
  • Code Duplication · Edited copy of a member (10 corresponding lines) development/web/lib/development_web/components/drawer.ex
  • Code Duplication · Edited copy of a member (7 corresponding lines) development/web/lib/development_web/live/showcase/headless_baseui_examples.ex
  • Code Duplication · Edited copy of a member (13 corresponding lines) development/web/lib/development_web/live/showcase/headless_form_demos.ex
  • Code Duplication · Edited copy of a member (7 corresponding lines) development/mob/lib/mishka_mob/components/mishka_fieldset.ex
  • Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) development/web/lib/development_web/live/showcase/catalog.ex
  • Code Duplication · Edited copy of a member (22 corresponding lines) development/mob/lib/mishka_mob/showcase/components/tooltip.ex
  • Code Duplication · Edited copies of one member (4 members, 6+ corresponding lines) development/mob/lib/mishka_mob/components/mishka_alpha_slider.ex
  • Code Duplication · Edited copy of a member (15 corresponding lines) lib/mishka_chelekom/generators/import_macro.ex
  • Code Duplication · Edited copy of a member (12 corresponding lines) development/mob/lib/mishka_mob/components/mishka_alpha_slider.ex
  • Code Duplication · Edited copy of a member (4 corresponding lines) development/web/lib/development_web/live/showcase/pills_input_form_demo.ex
  • Code Duplication · Edited copy of a member (10 corresponding lines) development/web/lib/development_web/live/showcase/catalog.ex
  • Code Duplication · Edited copy of a member (22 corresponding lines) development/mob/lib/mishka_mob/components/mishka_floating_indicator.ex
  • Code Duplication · Edited copy of a member (12 corresponding lines) development/mob/lib/mishka_mob/components/mishka_toolbar.ex
  • Code Duplication · Edited copy of a member (25 corresponding lines) development/mob/lib/mishka_mob/showcase/components/theme_icon.ex
  • Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) development/mob/lib/mishka_mob/components/mishka_calendar.ex
  • Code Duplication · Edited copy of a member (14 corresponding lines) development/web/lib/development_web/live/showcase/catalog.ex
  • Code Duplication · Edited copy of a member (15 corresponding lines) lib/mix/tasks/mishka.ui.gen.headless.ex
  • Code Duplication · Edited copy of a member (19 corresponding lines) development/mob/lib/mishka_mob/components/mishka_collapsible.ex
  • Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) development/mob/lib/mishka_mob/components/mishka_menu.ex
  • Code Duplication · Edited copy of a member (7 corresponding lines) development/web/lib/development_web/components/sidebar.ex
  • Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) development/web/lib/development_web/live/showcase/headless_form_demos.ex
  • Code Duplication · Edited copy of a member (13 corresponding lines) lib/mix/tasks/mishka.ui.gen.headless.ex
  • Code Duplication · Edited copy of a member (16 corresponding lines) development/mob/lib/mishka_mob/components/mishka_combobox.ex
  • Code Duplication · Edited copy of a member (12 corresponding lines) development/mob/lib/mishka_mob/components/mishka_spoiler.ex
  • Code Duplication · Edited copy of a member (9 corresponding lines) development/mob/lib/mishka_mob/home_screen.ex
  • Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) development/mob/lib/mishka_mob/storage_screen.ex
  • Code Duplication · Edited copies of one member (6 members, 3+ corresponding lines) development/mob/lib/mishka_mob/showcase/components/checkbox.ex
  • Code Duplication · Edited copy of a member (5 corresponding lines) development/web/lib/development_web/live/showcase/pills_input_form_demo.ex
  • Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) development/web/lib/development_web/components/badge.ex
  • Code Duplication · Edited copy of a member (7 corresponding lines) lib/mishka_chelekom/cms_bundle/attr_values.ex
  • Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) development/web/lib/development_web/live/showcase/examples/pagination.ex
  • Code Duplication · Edited copy of a member (10 corresponding lines) development/mob/lib/mishka_mob/components/mishka_select.ex
  • Code Duplication · Edited copy of a member (4 corresponding lines) development/mob/lib/mishka_mob/components/mishka_dialog.ex
  • Code Duplication · Edited copy of a member (3 corresponding lines) development/web/lib/development_web/components/headless/select.ex
  • Code Duplication · Edited copy of a member (14 corresponding lines) lib/mishka_chelekom/mcp/tools/get_js_hook_info.ex
  • Code Duplication · Edited copy of a member (5 corresponding lines) development/mob/lib/mishka_mob/components/mishka_progress.ex
  • Code Duplication · Edited copy of a member (4 corresponding lines) development/web/lib/development_web/components/headless/fab.ex
  • Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) development/mob/lib/mishka_mob/components/mishka_card.ex
  • Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) development/mob/lib/mishka_mob/showcase/components/autocomplete.ex
  • Code Duplication · Edited copy of a member (4 corresponding lines) development/mob/lib/mishka_mob/components/mishka_toolbar.ex
  • Code Duplication · Edited copy of a member (2 corresponding lines) lib/mishka_chelekom/cms_bundle/sanitize.ex
  • Code Duplication · Edited copy of a member (2 corresponding lines) lib/mix/tasks/mishka.ui.gen.component.ex
  • Code Duplication · Edited copy of a member (6 corresponding lines) development/web/lib/development_web/components/headless/tree.ex
  • Code Duplication · Edited copy of a member (2 corresponding lines) development/mob/lib/mishka_mob/components/mishka_alert_dialog.ex
  • Code Duplication · Edited copy of a member (2 corresponding lines) development/mob/lib/mishka_mob/components/mishka_dialog.ex
  • Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) development/mob/lib/mishka_mob/components/mishka_menu.ex
  • Code Duplication · Edited copy of a member (2 corresponding lines) development/mob/lib/mishka_mob/showcase/components/color_picker.ex
  • Code Duplication · Edited copy of a member (2 corresponding lines) lib/mishka_chelekom/generators/core.ex
  • Code Duplication · Edited copy of a member (2 corresponding lines) development/mob/lib/mishka_mob/components/mishka_dialog.ex
  • Code Duplication · Edited copies of one member (3 members, 1+ corresponding lines) development/web/lib/development_web/live/showcase/field_form_demo.ex
  • Code Duplication · Edited copy of a member (2 corresponding lines) development/mob/lib/mishka_mob/components/mishka_dialog.ex
  • Code Duplication · Edited copy of a member (2 corresponding lines) development/mob/lib/mishka_mob/components/mishka_select.ex
  • Code Duplication · Edited copies of one member (7 members, 1+ corresponding lines) development/mob/lib/mishka_mob/showcase/components/collapsible.ex
  • Code Duplication · Edited copy of a member (3 corresponding lines) development/mob/lib/mishka_mob/showcase/components/color_input.ex
  • Code Duplication · Edited copies of one member (4 members, 2+ corresponding lines) lib/mix/tasks/mishka.ui.gen.component.ex

We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 327 findings

These 327 critical or serious findings were in the previous survey, on 31 October 2026, and are gone from this one. The first 100 are listed here.

  • Code Duplication · Near-duplicate member family (4 members, 49 shared lines) development/web/lib/development_web/live/showcase/headless_baseui_examples.ex
  • Code Duplication · Near-duplicate member pair (129 shared lines) development/mob/lib/mishka_mob/showcase/components/nav_link.ex
  • Code Duplication · Edited copy of a member (43 corresponding lines) development/web/lib/development_web/live/showcase/headless_baseui_examples.ex
  • Code Duplication · Edited copy of a member (137 corresponding lines) development/mob/lib/mishka_mob/showcase/components/overflow_list.ex
  • Code Duplication · Members sharing a duplicated core (60 members, 50+ identical tokens) development/mob/lib/mishka_mob/showcase/components/accordion.ex
  • Code Duplication · Duplicated block (62–98 lines × 2) development/mob/lib/mishka_mob/showcase/components/highlight.ex
  • Code Duplication · Duplicated block (62–90 lines × 2) development/mob/lib/mishka_mob/showcase/components/nav_link.ex
  • Code Duplication · Duplicated block (25–85 lines × 5) development/mob/lib/mishka_mob/showcase/components/popover.ex
  • Code Duplication · Duplicated block (10–79 lines × 16) development/mob/lib/mishka_mob/showcase/components/accordion.ex
  • Code Duplication · Duplicated block (11–79 lines × 13) development/mob/lib/mishka_mob/showcase/components/action_icon.ex
  • Code Duplication · Duplicated block (48–77 lines × 3) development/mob/lib/mishka_mob/showcase/components/highlight.ex
  • Code Duplication · Duplicated block (10–72 lines × 8) development/mob/lib/mishka_mob/showcase/components/accordion.ex
  • Code Duplication · Duplicated block (48–70 lines × 2) development/mob/lib/mishka_mob/showcase/components/toast.ex
  • Code Duplication · Duplicated block (23–69 lines × 9) development/mob/lib/mishka_mob/showcase/components/action_icon.ex
  • Code Duplication · Duplicated block (11–67 lines × 19) development/mob/lib/mishka_mob/showcase/components/action_icon.ex
  • Code Duplication · Duplicated block (17–67 lines × 12) development/mob/lib/mishka_mob/showcase/components/action_icon.ex
  • Code Duplication · Duplicated block (37–67 lines × 4) development/mob/lib/mishka_mob/showcase/components/highlight.ex
  • Code Duplication · Duplicated block (33–58 lines × 5) development/mob/lib/mishka_mob/showcase/components/highlight.ex
  • Code Duplication · Duplicated block (47–57 lines × 3) development/mob/lib/mishka_mob/showcase/components/empty_state.ex
  • Code Duplication · Duplicated block (50–55 lines × 2) development/mob/lib/mishka_mob/showcase/components/highlight.ex
  • Code Duplication · Duplicated block (37–54 lines × 6) development/mob/lib/mishka_mob/showcase/components/chip.ex
  • Code Duplication · Duplicated block (9–53 lines × 3) development/mob/lib/mishka_mob/showcase/components/nav_link.ex
  • Code Duplication · Duplicated block (53 lines × 3) development/mob/lib/mishka_mob/showcase/components/toast.ex
  • Code Duplication · Duplicated block (33–51 lines × 5) development/mob/lib/mishka_mob/showcase/components/empty_state.ex
  • Code Duplication · Duplicated block (28–48 lines × 4) development/mob/lib/mishka_mob/showcase/components/highlight.ex
  • Code Duplication · Duplicated block (19–48 lines × 2) development/mob/lib/mishka_mob/showcase/components/empty_state.ex
  • Code Duplication · Duplicated block (37 lines × 7) development/mob/lib/mishka_mob/showcase/components/chip.ex
  • Code Duplication · Duplicated block (37 lines × 2) development/mob/lib/mishka_mob/showcase/components/nav_link.ex
  • Code Duplication · Duplicated block (28 lines × 6) development/mob/lib/mishka_mob/showcase/components/highlight.ex
  • Code Duplication · Duplicated block (14–25 lines × 10) development/mob/lib/mishka_mob/showcase/components/action_icon.ex
  • Code Duplication · Duplicated block (19–25 lines × 7) development/mob/lib/mishka_mob/showcase/components/action_icon.ex
  • Code Duplication · Duplicated block (25 lines × 2) development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex
  • Code Duplication · Duplicated block (24 lines × 4) development/mob/lib/mishka_mob/showcase/components/popover.ex
  • Code Duplication · Duplicated block (22 lines × 4) development/web/lib/development_web/live/showcase/headless_baseui_examples.ex
  • Code Duplication · Duplicated block (21–22 lines × 3) development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex
  • Code Duplication · Duplicated block (8–21 lines × 56) development/mob/lib/mishka_mob/showcase/components/accordion.ex
  • Code Duplication · Duplicated block (14–21 lines × 11) development/mob/lib/mishka_mob/showcase/components/action_icon.ex
  • Code Duplication · Duplicated block (19–21 lines × 8) development/mob/lib/mishka_mob/showcase/components/action_icon.ex
  • Code Duplication · Duplicated block (20 lines × 6) development/mob/lib/mishka_mob/showcase/components/action_icon.ex
  • Code Duplication · Duplicated block (20 lines × 5) development/mob/lib/mishka_mob/showcase/components/popover.ex
  • Code Duplication · Duplicated block (20 lines × 2) development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex
  • Code Duplication · Duplicated block (9–18 lines × 3) development/mob/lib/mishka_mob/showcase/components/nav_link.ex
  • Code Duplication · Duplicated block (16 lines × 3) development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex
  • Code Duplication · Duplicated block (14 lines × 52) development/mob/lib/mishka_mob/showcase/components/accordion.ex
  • Code Duplication · Duplicated block (14 lines × 2) development/web/lib/development_web/live/showcase/headless_baseui_examples.ex
  • Code Duplication · Duplicated block (10 lines × 16) development/mob/lib/mishka_mob/showcase/components/action_icon.ex
  • Code Duplication · Duplicated block (9 lines × 3) development/mob/lib/mishka_mob/showcase/components/nav_link.ex
  • Code Duplication · Duplicated block (5 lines × 3) development/web/lib/development_web/components/file_field.ex
  • Code Duplication · Duplicated block (6 lines × 2) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt
  • Secret Scanning · Leaked secret: high-entropy-secret development/web/config/dev.exs
  • Secret Scanning · Leaked secret: signing-key development/web/config/dev.exs
  • Secret Scanning · Leaked secret: high-entropy-secret development/web/config/test.exs
  • Secret Scanning · Leaked secret: signing-key development/web/config/test.exs
  • Churn × Complexity Hotspots · Hotspot: development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt
  • Churn × Complexity Hotspots · Repeated repair: development/mob/lib/mishka_mob/showcase/components/overflow_list.ex development/mob/lib/mishka_mob/showcase/components/overflow_list.ex
  • Churn × Complexity Hotspots · Repeated repair: development/mob/lib/mishka_mob/components/mishka_splitter.ex development/mob/lib/mishka_mob/components/mishka_splitter.ex
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: watchdog-mutable-job-container-image REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: watchdog-unpinned-package-install-in-run REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
Rebuild cost: about €210,000 · Estimate
Cost to rebuild€71,000 to €360,000, for 1,182 to 3,750 hours of work, about 1.5 person-years for 1 to 3 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 38. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeLarge: 202,342 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Encrypt sensitive data at rest (Cloak.Ecto — a Cloak.Ecto.Binary-backed field type for the column — or ash_cloak for Ash) and manage keys in a vault (AWS KMS / Secrets Manager through ex_aws_kms, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault).
Skip if delegated to infra (Postgres TDE, KMS, etc.).
Raises the score by about 5 points · Medium effort · Data Protection
2
Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
Raises the score by about 5 points · Medium effort · Access Controls
3
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED.
Raises the score by about 2 points · Low effort · Static Analysis (SAST)

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €210,000 to build again, about 1.5 person-years of work. Its weakest lens is Security and Compliance, at 30 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Encrypt sensitive data at rest (Cloak.Ecto — a Cloak.Ecto.Binary-backed field type for the column — or ash_cloak for Ash) and manage keys in a vault (AWS KMS / Secrets Manager through ex_aws_kms, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault). Of all the actions in this report, it raises the score most for the work it takes: about 5 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.1 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 85,052 lines over the last 90 days, which is about 344,933 lines a year. At that pace, the extra work comes to an estimated 20 to 120.2 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

At a glance — Code Health · 38% · Weak · gated by R1, R10 ·

At a glance — Architecture · 76% · Adequate · gated by D26 ·

At a glance — Maturity · 66% · Adequate · gated by D16, M2 ·

At a glance — Readiness · 38% · Weak · gated by R4, R8, P7 ·

At a glance — Security · 30% · Weak · gated by D36, C1, C2 ·

At a glance — Accessibility · 43% · Weak · gated by AC4 ·

At a glance — Performance · 100% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A05:2025 — Injection14High / Critical
A03:2025 — Software Supply Chain Failures3Medium

Roadmap

Top priorities: Encrypt sensitive data at rest (Cloak.Ecto — a Cloak.Ecto.Binary-backed field type for the column — or ash_cloak for Ash) and manage keys in a vault (AWS KMS / Secrets Manager through ex_aws_kms, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.); Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do; Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Encrypt sensitive data at rest (Cloak.Ecto — a Cloak.Ecto.Binary-backed field type for the column — or ash_cloak for Ash) and manage keys in a vault (AWS KMS / Secrets Manager through ex_aws_kms, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.).+5.2 ptsMediumData Protection
Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.+5.2 ptsMediumAccess Controls
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED.+1.6 ptsLowStatic Analysis (SAST)
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.+1.6 ptsLowSupply-chain Provenance & Signing
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.+1.6 ptsLowSupply-chain Provenance & Signing
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.+1.6 ptsLowSupply-chain Provenance & Signing
Resolve the 1 Banned license finding(s) in License Compliance.+1.1 ptsLowLicense Compliance
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with mix.exs.+1.0 ptsLowADR Quality

File quality

Per-file score 0–10 — a quality signature. Of 171 files carrying findings, judged against the Preview bar: 0% slop · 3% mixed · 97% near-clean.

FileScoreBandWorst signal
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt7.0Near-cleanCyclomatic Complexity: MobAnchoredPositionProvider.calculatePosition (cyclomatic 35)
development/web/lib/development_web/live/showcase/headless_baseui_examples.ex7.0Near-cleanGod Classes: FileTooLong: showcase/headless_baseui_examples.ex
development/mob/lib/mishka_mob/showcase/components/accordion.ex7.0Near-cleanCode Duplication: Near-duplicate member family (6 members, 33 shared lines)
development/mob/lib/mishka_mob/showcase/components/action_icon.ex7.0Near-cleanCode Duplication: Edited copy of a member (202 corresponding lines)
development/mob/lib/mishka_mob/components/mishka_calendar.ex7.0Near-cleanCyclomatic Complexity: MishkaCalendar.row_node (cyclomatic 20)
development/web/lib/development_web/live/showcase/headless_form_demos.ex7.0Near-cleanGod Classes: FileTooLong: showcase/headless_form_demos.ex
development/mob/lib/mishka_mob/components/mishka_dialog.ex7.0Near-cleanGod Classes: TooManyFunctions: MishkaDialog
development/mob/lib/mishka_mob/components/mishka_alpha_slider.ex7.0Near-cleanCode Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)
development/mob/lib/mishka_mob/showcase/components/nav_link.ex7.0Near-cleanCode Duplication: Near-duplicate member pair (129 shared lines)
priv/assets/js/menu.js7.1Near-cleanCyclomatic Complexity: handleKeydown (cyclomatic 28)
priv/assets/js/drawer.js7.1Near-cleanCyclomatic Complexity: bindSwipeArea (cyclomatic 25)
development/web/lib/development_web/components/checkbox_card.ex7.1Near-cleanGod Classes: FileTooLong: components/checkbox_card.ex
development/mob/lib/mishka_mob/showcase/components/calendar.ex7.1Near-cleanGod Classes: FileTooLong: components/calendar.ex
lib/mix/tasks/mishka.ui.gen.component.ex7.1Near-cleanCode Duplication: Edited copies of one member (3 members, 22+ corresponding lines)
development/web/lib/development_web/live/showcase/catalog.ex7.1Near-cleanCode Duplication: Edited copies of one member (3 members, 10+ corresponding lines)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 136

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 658

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 66

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 24

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 60 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 60 dimensions across the health lenses
D1D2D3D4D5D10D12D13D14D15D16D17D19D20D24D26D27D28D29D30D34D35D36D37D43D44AC1AC2AC3AC4AC5AC6AX10AX3AX4C1C2M1M2M3M4P1P10P2P3P6P7PF3R1R10R2R3R4R6R7R8R9S1X28X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 834 of 860 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1df1d-bab2-7b65-9fcb-d513f7004a9d.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .ex, and our analyzer cannot run the .ex test suite(s) — so no coverage was collected for the repository as a whole. The JavaScript/TypeScript half did build and run, and its own line coverage came back at 64.3% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
  • D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 75 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 301 test source file(s) (.exs, .ex) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT SCORED: this repository's production source includes .ex, and the built-in reliability runner cannot re-run the .ex test suite(s) — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (node:test via `npm install --ignore-scripts` (no lockfile) in development/web/script/claude-video/ (9 tests); node:test via `npm install --ignore-scripts` (no lockfile) in priv/assets/js/ (44 tests)): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (mix.exs), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
  • D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • AC1 Text alternatives — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository renders user interface from a TEMPLATE LANGUAGE — 78 Phoenix (EEx) template file(s) carrying 914 markup element(s) (e.g. priv/mob/accordion.eex, priv/mob/action_icon.eex, priv/mob/alert_dialog.eex) — and the accessibility cards on this run were measured over the 384 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
  • AC2 Forms & labels — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository renders user interface from a TEMPLATE LANGUAGE — 78 Phoenix (EEx) template file(s) carrying 914 markup element(s) (e.g. priv/mob/accordion.eex, priv/mob/action_icon.eex, priv/mob/alert_dialog.eex) — and the accessibility cards on this run were measured over the 384 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
  • AC2 Forms & labels — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 45 further occurrence(s) are not listed individually; the score already reflects all 85.
  • AC3 Page structure — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository renders user interface from a TEMPLATE LANGUAGE — 78 Phoenix (EEx) template file(s) carrying 914 markup element(s) (e.g. priv/mob/accordion.eex, priv/mob/action_icon.eex, priv/mob/alert_dialog.eex) — and the accessibility cards on this run were measured over the 384 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
  • AC4 Keyboard semantics — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository renders user interface from a TEMPLATE LANGUAGE — 78 Phoenix (EEx) template file(s) carrying 914 markup element(s) (e.g. priv/mob/accordion.eex, priv/mob/action_icon.eex, priv/mob/alert_dialog.eex) — and the accessibility cards on this run were measured over the 384 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
  • AC5 ARIA correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository renders user interface from a TEMPLATE LANGUAGE — 78 Phoenix (EEx) template file(s) carrying 914 markup element(s) (e.g. priv/mob/accordion.eex, priv/mob/action_icon.eex, priv/mob/alert_dialog.eex) — and the accessibility cards on this run were measured over the 384 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
  • AC5 ARIA correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 73 further occurrence(s) are not listed individually; the score already reflects all 113.
  • AC6 Visual & motion safety — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository renders user interface from a TEMPLATE LANGUAGE — 78 Phoenix (EEx) template file(s) carrying 914 markup element(s) (e.g. priv/mob/accordion.eex, priv/mob/action_icon.eex, priv/mob/alert_dialog.eex) — and the accessibility cards on this run were measured over the 384 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
  • AC6 Visual & motion safety — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 22 further occurrence(s) are not listed individually; the score already reflects all 62.
  • AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Boot via AndroidApp (development/mob/android/app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: ternal.ExecException: Process 'command '/opt/android-sdk/cmake/3.22.1/bin/cmake'' finished with non-zero exit value 1 at org.gradle.process.internal.DefaultExecHandle$ExecResultImpl.assertNormalExi…; runtime evidence skipped (launch chosen because development/mob/android/app/build.gradle applies the Android application plugin and development/mob/android/gradlew builds it).
  • GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Elixir, Erlang, Kotlin, c, objectivec, zig is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Elixir, Erlang, Kotlin, c, objectivec, zig is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 38 further occurrence(s) are not listed individually; the score already reflects all 78.
  • R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 11 further occurrence(s) are not listed individually; the score already reflects all 51.
  • R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 18 further occurrence(s) are not listed individually; the score already reflects all 58.
  • X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X10 Duplicated predicate — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 27 further occurrence(s) are not listed individually; the score already reflects all 67.
  • X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 11 further occurrence(s) are not listed individually; the score already reflects all 51.
  • X7 Silent fallback defaults — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. X7 measured the part of this repository it reads (C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart), and its Elixir, Erlang source is outside the check's reach, so the card covers only part of the product. That is a gap in this analyzer's language reach — not a finding that the unread source is free of silent defaults.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity6.9 / 10Adequate✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented → Verified → Prevented · effective 6.9 / 10 · rule-coverage 100% · ceiling Prevented

38 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was updatePosition at 41. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being MobBridgeKt.materialIconFor at 30 — they are counted neither in the figure above nor in this dimension's score.

positionPopup (cyclomatic 27) · ×2priv/assets/js/popover.js:195
mounted (cyclomatic 21) · ×2priv/assets/js/editor_tiptap.js:106
mounted (cyclomatic 20) · ×2priv/assets/js/drawer.js:115
mounted (cyclomatic 17) · ×2priv/assets/js/otp.js:24
mounted (cyclomatic 16) · ×2priv/assets/js/floating_window.js:17

+ 26 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 36 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with updatePosition (cyclomatic 41), MobAnchoredPositionProvider.calculatePosition (cyclomatic 35), MobBridgeKt.RenderNodeInner (cyclomatic 35). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 36 together lifts Cyclomatic Complexity from 6.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity6.6 / 10Adequate✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented → Verified → Prevented · effective 6.6 / 10 · rule-coverage 100% · ceiling Prevented

53 method(s) exceeded the cognitive complexity threshold of 15; the worst was MobAnchoredPositionProvider.calculatePosition at 57.

mounted (cognitive 16) · ×3priv/assets/js/floating_window.js:17
positionPopup (cognitive 33) · ×2priv/assets/js/popover.js:195
mounted (cognitive 22) · ×2priv/assets/js/drawer.js:115
mounted (cognitive 20) · ×2priv/assets/js/editor_tiptap.js:106
MobAnchoredPositionProvider.calculatePosition (cognitive 57)development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:3347

+ 40 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 50 bodies over 15 down to 15 or less in Cognitive Complexity — start with MobAnchoredPositionProvider.calculatePosition (cognitive 57), updatePosition (cognitive 45), activate (cognitive 43). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 50 together lifts Cognitive Complexity from 6.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes8.8 / 10Strong✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.8 / 10 · rule-coverage 100% · ceiling Prevented

52 god class(es) detected.

FileTooLong: showcase/headless_daisyui_examples.ex · ×39development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex
TooManyFunctions: MishkaDrawer · ×8development/mob/lib/mishka_mob/components/mishka_drawer.ex:1
MethodTooLong: MobBridgeKt.MobTextField · ×2development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:3562
TooManyMethods: MobBridgedevelopment/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:284
ClassTooLong: RootStatedevelopment/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:264

+ 1 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 39 FileTooLong finding(s) in God Classes — start with headless_daisyui_examples.ex, headless_baseui_examples.ex, headless_preview.ex. — One of this dimension's main actionable groups (39 warning-level).
  2. Resolve the 8 TooManyFunctions finding(s) in God Classes — start with mishka_drawer.ex, mishka_popover.ex, mishka_tree.ex. — One of this dimension's main actionable groups (8 warning-level).
  3. Resolve the 2 MethodTooLong finding(s) in God Classes — start with MobBridge.kt (2). — One of this dimension's main actionable groups (2 warning-level).

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication7.7 / 10Strong✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

Maturity: Documented → Verified → Prevented · effective 7.7 / 10 · rule-coverage 100% · ceiling Verified

147 duplicated block group(s) detected. 5.8 % of the production lines (11,777 of 202,342) are in a reported copy. A further 110 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 5 of the 257 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Duplicated block (6 lines × 2) · ×12development/web/lib/development_web/components/checkbox_field.ex:93
Edited copy of a member (2 corresponding lines) · ×11lib/mishka_chelekom/cms_bundle/sanitize.ex:80
Duplicated block (5 lines × 2) · ×8development/web/lib/development_web/live/showcase/example_source.ex:42
Duplicated block (7 lines × 2) · ×6development/mob/lib/mishka_mob/components/mishka_pills_input.ex:177
Edited copy of a member (10 corresponding lines) · ×5development/web/lib/development_web/components/combobox.ex:167

+ 166 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 12 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with headless_baseui_examples.ex (3), mishka_alpha_slider.ex (2), checkbox_field.ex. — One of this dimension's main actionable groups (12 warning-level).
  2. Resolve the 11 Edited copy of a member (2 corresponding lines) finding(s) in Code Duplication — start with mishka_dialog.ex (4), sanitize.ex, mishka.ui.gen.component.ex. — One of this dimension's main actionable groups (11 warning-level).
  3. Resolve the 8 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with headless_baseui_examples.ex (2), example_source.ex, mishka_checkbox_group.ex. — One of this dimension's main actionable groups (8 warning-level).

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

8 production modules (Gradle+npm+OTP+CMake), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence, with abstractness counted on 4 of the 8 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

11 skipped (11 with a documented reason), 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 75 tests. Measured on the JavaScript/TypeScript suite only — at least 301 test source file(s) (.exs, .ex) went unread, so its test quality is unmeasured and is not in these counts.

Skipped (documented): (unnamed test) · ×11priv/assets/js/overflow_list.test.mjs:24

✓ On the Gold path — maintain.

Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.

D12 · Dependency Hygiene9.9 / 10Exemplary✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Verified

2 outdated, 0 retired direct Hex dependencies, 0 pinning defect(s). Whether any of these packages is UNMAINTAINED is not graded — hex.pm publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: a Hex app name does not determine the modules it provides (`ecto_sql` provides Ecto.Adapters.SQL), and a large idiomatic class of BEAM dependencies — runtime adapters, codec plugins, protocol implementations and OTP applications the release starts — is correctly declared and never referenced in source, so absence of a reference is not evidence of an unused dependency. Known CVEs in this dependency graph are D30's question, read from mix.lock there.

Outdated: dialyxir · ×2

✓ On the Gold path — maintain.

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets. 4 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance8.0 / 10Adequategated by 1 critical finding✓ Tool-verified

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

Maturity: Documented → Verified → Prevented · effective 8.0 / 10 · rule-coverage 100% · ceiling Verified

1 of 60 shipped Hex package(s) use a banned license. Licences were resolved from hex.pm over the packages a consumer installs — this repository's mix.lock closed over the declarations its mix.exs files do not gate behind `only:`. Packages it asks for ONLY under `only: [:dev, :test]` (or any other non-prod environment, such as `:docs`) are excluded: they are not installed by anything that depends on this repository. Each licence is the one hex.pm publishes for the package's current release. A further 1 package(s) the closure reaches resolve from git, a path or a local override and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.

Banned license: anubis_mcp

What to do

  1. Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.

D15 · Churn × Complexity Hotspots10.0 / 10Stronggated by 47 serious findings✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: priv/assets/js/floating.js (4×41=164) Repeated repair below the complexity floor: lib/mishka_chelekom/cms_bundle_exporter.ex (11 of 13 changes were fixes); lib/mishka_chelekom/generators/assets.ex (7 of 11 changes were fixes); development/web/lib/development_web/components/file_field.ex (6 of 9 changes were fixes)

Repeated repair: lib/mishka_chelekom/cms_bundle_exporter.ex · ×46lib/mishka_chelekom/cms_bundle_exporter.ex:126
Hotspot: priv/assets/js/floating.jspriv/assets/js/floating.js:450

What to do

  1. Resolve the 46 Repeated repair finding(s) in Churn × Complexity Hotspots — start with cms_bundle_exporter.ex, assets.ex, file_field.ex. — One of this dimension's main actionable groups (46 warning-level).
  2. Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with floating.js. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

D16 · Bus Factor3.3 / 10Weak✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

Maturity: Documented → Verified → Prevented · effective 3.3 / 10 · rule-coverage 100% · ceiling Documented

351 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex. Counted over 514 of the 838 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1

What to do

  1. Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.

D17 · Explicit Debt10.0 / 10Exemplary○ Nothing flagged

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 deducted task-comment markers across 202342 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.md.

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

2 of 2 documentation facets pass in full. 14 document(s) read across 4 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs founddevelopment/web/mix.exs:13

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with mix.exs. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

D24 · Comment Value9.7 9.7 / 10Exemplary✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 99% · ceiling Documented

1 of 377 judged comments only repeat the code they sit on (0.3 %). 3 comment(s) in another language or script were not judged.

redundant commentpriv/assets/js/clipboard.js:338
doc comments repeat the namespriv/assets/js/clipboard.js:116

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.

D26 · Project Cohesion1.4 / 10Critical✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 1.4 / 10 · rule-coverage 100% · ceiling Documented

3 of 7 build units (Gradle, Mix, npm) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

D27 · Navigability10.0 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)5.0 / 10Adequate✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 5.0 / 10 · rule-coverage 100% · ceiling Documented

14 finding(s): 0 critical, 14 high, 0 medium, 0 low. 10 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `.github/scripts/android_e2e.sh` (line 6), `development/mob/android/app/src/main/jni/beam_jni.c` (line 13, line 21, line 26, …), `development/mob/android/gradlew` (line 72, line 177) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
  2. No action in Static Analysis (SAST) — all 7 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (7 issue-level, 0 of them charged here).
  3. No action in Static Analysis (SAST) — all 3 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (3 issue-level, 0 of them charged here).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No known-vulnerable dependencies in any ecosystem this repository declares.

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 514 of the 838 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

Maturity: Documented → Verified → Prevented · effective 2.5 / 10 · rule-coverage 100% · ceiling Documented

1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 10 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AC1 · Text alternatives5.1 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×9) — development/web/lib/development_web/components/layouts.ex:41, development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:5950, priv/components/avatar.eex:100, …
  • Video with no captions <track> offers no captions. Add a <track kind="captions"> pointing at a WebVTT file for this video (or confirm captions are provided another way). — priv/components/video.eex:114

What to do

  • Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels5.6 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×23) — development/web/lib/development_web/components/headless/autocomplete.ex:110, development/web/lib/development_web/components/headless/combobox.ex:128, development/web/lib/development_web/components/headless/pills_input.ex:42, …
  • This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×4) — development/web/lib/development_web/live/showcase/field_form_demo.ex:183, development/web/lib/development_web/live/showcase/field_form_demo.ex:223, development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:3490, …
  • This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×13) — development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:1665, development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:1692, development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:1722, …

What to do

  • Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure5.7 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×5) — development/web/lib/development_web/components/layouts/root.html.heex:2, development/web/script/claude-video/shared/templates/intro.html:1, development/web/script/claude-video/shared/templates/outro.html:1, …
  • A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). — development/web/lib/development_web/live/showcase/headless_preview.ex:1722
  • Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×2) — development/web/lib/development_web/live/showcase/kit_demo.ex:580, development/web/lib/development_web/live/showcase/preview.ex:505
  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×4) — development/web/script/claude-video/shared/templates/intro.html:1, development/web/script/claude-video/shared/templates/outro.html:1, development/web/script/claude-video/shared/templates/segment.html:1, …
  • A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — priv/headless/chart.eex:1

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics2.6 / 10Weak✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×11) — development/web/lib/development_web/components/core_components.ex:378, development/web/lib/development_web/components/headless/table.ex:168, development/web/lib/development_web/components/mega_menu.ex:202, …
  • This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. (×2) — development/web/lib/development_web/components/drawer.ex:102, priv/components/drawer.eex:102
  • This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. (×10) — development/web/lib/development_web/components/headless/color_input.ex:85, development/web/lib/development_web/components/headless/floating_window.ex:36, development/web/lib/development_web/components/headless/preview_card.ex:84, …
  • This <span role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. (×2) — development/web/lib/development_web/components/popover.ex:155, priv/components/popover.eex:152
  • An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×2) — priv/headless/anchor.eex:5, priv/headless/card.eex:16

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness5.4 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • A plain <span> has the implicit role "generic", which supports no ARIA states, so this aria-expanded is dropped and assistive tech is never told the state at all. Put aria-expanded on the element that owns the behaviour (the button or control the user operates), or give this <span> a role that supports aria-expanded. — development/web/lib/development_web/components/headless/preview_card.ex:75
  • aria-hidden="true" here hides the subtree from assistive tech, but a focusable descendant stays in the tab order — a keyboard user can land on a control screen readers can't see. Add inert, take the descendants out of the tab order (tabindex="-1"), or drop aria-hidden. (×2) — development/web/lib/development_web/components/modal.ex:132, priv/components/modal.eex:152
  • "{" is not a valid value for aria-hidden — allowed: true, false, undefined. (×2) — priv/components/carousel.eex:186, priv/headless/carousel.eex:101
  • "{" is not a valid value for aria-checked — allowed: true, false, mixed, undefined. (×5) — priv/components/checkbox_card.eex:123, priv/components/radio_card.eex:146, priv/components/rating.eex:203, …
  • "{" is not a valid value for aria-current — allowed: true, false, page, step, location, date, time. (×8) — priv/components/dock.eex:228, priv/components/pagination.eex:249, priv/components/stepper.eex:208, …
  • "{" is not a valid value for aria-disabled — allowed: true, false. (×8) — priv/components/pagination.eex:249, priv/components/pagination.eex:277, priv/components/rating.eex:111, …
  • "{" is not a valid value for aria-selected — allowed: true, false, undefined. (×7) — priv/components/tabs.eex:174, priv/components/tabs.eex:228, priv/components/tabs.eex:334, …
  • "{" is not a valid value for aria-expanded — allowed: true, false, undefined. (×3) — priv/headless/accordion.eex:109, priv/headless/autocomplete.eex:110, priv/headless/burger.eex:38
  • "{" is not a valid value for aria-live — allowed: off, polite, assertive. (×2) — priv/headless/alert.eex:61, priv/headless/carousel.eex:95
  • "{" is not a valid value for aria-busy — allowed: true, false. (×2) — priv/headless/button.eex:96, priv/headless/button.eex:112

What to do

  • Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
AC6 · Visual & motion safety4.5 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • <span> moves — its `animate-bounce` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. (×6) — development/web/lib/development_web/components/spinner.ex:168, development/web/lib/development_web/components/spinner.ex:169, development/web/lib/development_web/components/spinner.ex:170, …
  • <svg> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. (×2) — development/web/lib/development_web/components/stepper.ex:0, development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:0
  • <span> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. (×3) — development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:2747, development/web/lib/development_web/live/showcase/headless_preview.ex:903, development/web/lib/development_web/live/showcase/loading_overlay_demo.ex:31
  • <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×12) — development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:5191, development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:5198, development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:5205, …
  • This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade. — development/web/lib/development_web/live/showcase/headless_kit_demo.ex:122
  • <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×4) — development/web/lib/development_web/live/showcase/headless_preview.ex:1619, development/web/lib/development_web/live/showcase/headless_preview.ex:3584, development/web/lib/development_web/live/showcase/headless_preview.ex:3602, …
  • `.hf-slot` moves (`animation: slotIn 0.34s cubic-bezier(0.2, 0.8, 0.3, 1) forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — development/web/script/claude-video/shared/templates/intro.html:94
  • `.hf-slot[data-last="true"]` moves (`animation: slotIn 0.34s cubic-bezier(0.2, 0.8, 0.3, 1) forwards, slotAccept 0.5s ease-out forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — development/web/script/claude-video/shared/templates/intro.html:105
  • `.hf-slots[data-resolving="true"] .hf-slot` moves (`animation: slotOut 0.42s cubic-bezier(0.6, 0, 0.8, 0.2) forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — development/web/script/claude-video/shared/templates/intro.html:110
  • `.hf-title` moves (`animation: titleIn 0.5s cubic-bezier(0.2, 0.8, 0.3, 1) forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — development/web/script/claude-video/shared/templates/intro.html:158
  • `.hf-meta` moves (`animation: titleIn 0.5s ease-out forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — development/web/script/claude-video/shared/templates/intro.html:183
  • `.hf-tagline` moves (`animation: titleIn 0.5s ease-out forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — development/web/script/claude-video/shared/templates/intro.html:198
  • `.hf-lockup` moves (`animation: rise 0.5s ease-out forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — development/web/script/claude-video/shared/templates/intro.html:231
  • `.hf-eyebrow` moves (`animation: rise 0.45s ease-out 0.15s forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — development/web/script/claude-video/shared/templates/outro.html:60
  • `.hf-url` moves (`animation: rise 0.5s cubic-bezier(0.2, 0.8, 0.3, 1) 0.32s forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — development/web/script/claude-video/shared/templates/outro.html:71
  • `.hf-url::after` moves (`animation: draw 0.85s cubic-bezier(0.3, 0.7, 0.2, 1) 0.75s forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — development/web/script/claude-video/shared/templates/outro.html:83
  • `.hf-note` moves (`animation: rise 0.45s ease-out 1.35s forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — development/web/script/claude-video/shared/templates/outro.html:90
  • `.seg-index` moves (`animation: rise 0.4s ease-out 0.1s forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — development/web/script/claude-video/shared/templates/segment.html:67

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition5.0 / 10Adequate✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

C1 · Data Protection0.0 / 10Critical✓ Tool-verified

Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.

Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.

  • No encryption usage (Cloak.Ecto encrypted field types, a Cloak vault, Plug.Crypto's message encryptor, :crypto ciphers that encrypt, libsodium boxes) was found, and this repository persists personal data in the model cited here — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore. — development/web/lib/development_web/live/showcase/field_form_demo.ex:16

What to do

  • Encrypt sensitive data at rest (Cloak.Ecto — a Cloak.Ecto.Binary-backed field type for the column — or ash_cloak for Ash) and manage keys in a vault (AWS KMS / Secrets Manager through ex_aws_kms, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.).
  • Enforce HTTPS (force_ssl: [hsts: true] on the Phoenix endpoint, or plug Plug.SSL, or an https: listener) so data in transit is always encrypted.
C2 · Access Controls0.0 / 10Critical✓ Tool-verified

Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.

Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.

  • This repository serves requests — a server ({Bandit,) (lib/mishka_chelekom/mcp/supervisor.ex:58) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — lib/mishka_chelekom/mcp/supervisor.ex:58

What to do

  • Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
M1 · Documentation (README)8.8 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

M2 · Architecture documentation2.0 / 10Weak✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates8.5 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P2 · Observability7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `development/web`.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • `REDACTED` schedules updates, but no `package-ecosystem` entry covers `bun`, `gradle`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:8

What to do

  • Dependabot is configured but does not watch `bun`, `gradle` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

  • `:httpc.request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — development/web/check_http.exs:31
  • `Req.new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — lib/mix/tasks/mishka.ui.add.ex:210
  • `Req.get!(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — lib/mix/tasks/mishka.ui.add.ex:215

What to do

  • Set an explicit timeout on every client — `recv_timeout:` for HTTPoison, `receive_timeout:` for Req and Finch, `Tesla.Middleware.Timeout` (or the adapter's `recv_timeout`) for Tesla, `timeout:` for `:httpc` — and add retries with back-off (`Tesla.Middleware.Retry`, Req's `retry:`) and a breaker (`:fuse`, `ExternalService`) around dependencies that fail.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

R1 · Type Safety0.0 / 10Critical✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

  • 0 typed · 77 plain JS — the untyped files are development/web/assets/js/app.js, development/web/script/claude-video/gladia/sync-captions.mjs, development/web/script/claude-video/shared/assemble.mjs, development/web/script/claude-video/shared/assemble.test.mjs, development/web/script/claude-video/shared/assets/logo.mjs, development/web/script/claude-video/shared/capture.mjs (+71 more).

What to do

  • Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication0.7 / 10Critical✓ Tool-verified

React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.

  • priv/assets/js/preview_card.js:11 · priv/assets/js/tooltip.js:44 — the two spans are one implementation copied and then locally edited — 1734 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — priv/assets/js/preview_card.js:11
  • priv/assets/js/chart_chartjs.js:20 · priv/assets/js/chart_echarts.js:36 — the two spans are one implementation copied and then locally edited — 1118 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — priv/assets/js/chart_chartjs.js:20
  • priv/assets/js/drawer.js:126 · priv/assets/js/focus_trap.js:89 — the two spans are one implementation copied and then locally edited — 825 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — priv/assets/js/drawer.js:126
  • priv/assets/js/editor_lexical.js:23 · priv/assets/js/editor_milk_down.js:45 — the two spans are one implementation copied and then locally edited — 715 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — priv/assets/js/editor_lexical.js:23
  • priv/assets/js/popover.js:71 · priv/assets/js/tooltip.js:61 — the two spans are one implementation copied and then locally edited — 759 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — priv/assets/js/popover.js:71
  • priv/assets/js/menu.js:39 · priv/assets/js/popover.js:76 — the two spans are one implementation copied and then locally edited — 530 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — priv/assets/js/menu.js:39
  • priv/assets/js/editor_code_mirror.js:100 · priv/assets/js/editor_lexical.js:88 — the two spans are one implementation copied and then locally edited — 439 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — priv/assets/js/editor_code_mirror.js:100
  • priv/assets/js/popover.js:102 · priv/assets/js/preview_card.js:44 — the two spans are one implementation copied and then locally edited — 393 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — priv/assets/js/popover.js:102
  • priv/assets/js/context_menu.js:318 · priv/assets/js/menu.js:319 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — priv/assets/js/context_menu.js:318
  • priv/assets/js/chart_billboard.js:152 · priv/assets/js/chart_chartjs.js:55 · priv/assets/js/chart_echarts.js:71 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — priv/assets/js/chart_billboard.js:152
  • priv/assets/js/popover.js:212 · priv/assets/js/preview_card.js:164 · priv/assets/js/tooltip.js:217 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — priv/assets/js/popover.js:212
  • priv/assets/js/context_menu.js:205 · priv/assets/js/menu.js:221 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — priv/assets/js/context_menu.js:205
  • priv/assets/js/focus_trap.js:54 · priv/assets/js/popover.js:24 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — priv/assets/js/focus_trap.js:54
  • priv/assets/js/context_menu.js:151 · priv/assets/js/menu.js:128 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — priv/assets/js/context_menu.js:151
  • priv/assets/js/focus_trap.js:257 · priv/assets/js/popover.js:294 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — priv/assets/js/focus_trap.js:257
  • priv/assets/js/context_menu.js:248 · priv/assets/js/menu.js:259 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — priv/assets/js/context_menu.js:248
  • priv/assets/js/drawer.js:75 · priv/assets/js/popover.js:15 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — priv/assets/js/drawer.js:75
  • priv/assets/js/radio_group.js:59 · priv/assets/js/toggle_group.js:124 — the two spans are one implementation copied and then locally edited — 143 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — priv/assets/js/radio_group.js:59
  • priv/assets/js/collapsible.js:78 · priv/assets/js/floating.js:237 — the two spans are one implementation copied and then locally edited — 157 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — priv/assets/js/collapsible.js:78
  • priv/assets/js/context_menu.js:401 · priv/assets/js/menu.js:422 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — priv/assets/js/context_menu.js:401
  • priv/assets/js/scrollArea.js:135 · priv/assets/js/scrollArea.js:164 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — priv/assets/js/scrollArea.js:135
  • priv/assets/js/popup.js:64 · priv/assets/js/select.js:105 — the two spans are one implementation copied and then locally edited — 187 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — priv/assets/js/popup.js:64
  • priv/assets/js/floating.js:346 · priv/assets/js/floating.js:367 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — priv/assets/js/floating.js:346
  • priv/assets/js/focus_trap.js:232 · priv/assets/js/popover.js:276 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — priv/assets/js/focus_trap.js:232
  • priv/assets/js/editor_code_mirror.js:38 · priv/assets/js/editor_tiptap.js:97 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — priv/assets/js/editor_code_mirror.js:38
  • priv/assets/js/menubar.js:167 · priv/assets/js/menubar.js:216 — the two spans are one implementation copied and then locally edited — 123 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — priv/assets/js/menubar.js:167
  • priv/assets/js/roving_tabindex.js:53 · priv/assets/js/tabs.js:153 — the two spans are one implementation copied and then locally edited — 132 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — priv/assets/js/roving_tabindex.js:53
  • priv/assets/js/select.js:187 · priv/assets/js/toggle_group.js:129 — the two spans are one implementation copied and then locally edited — 121 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — priv/assets/js/select.js:187
  • priv/assets/js/chart_billboard.js:298 · priv/assets/js/chart_chartjs.js:192 · priv/assets/js/chart_echarts.js:240 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — priv/assets/js/chart_billboard.js:298
  • priv/assets/js/chart_billboard.js:323 · priv/assets/js/chart_echarts.js:268 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — priv/assets/js/chart_billboard.js:323
  • priv/assets/js/clipboard.js:354 · priv/assets/js/clipboard.js:438 — the two spans are one implementation copied and then locally edited — 88 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — priv/assets/js/clipboard.js:354
  • priv/assets/js/context_menu.js:283 · priv/assets/js/menu.js:302 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — priv/assets/js/context_menu.js:283
  • priv/assets/js/menubar.js:163 · priv/assets/js/toggle_group.js:132 — the two spans are one implementation copied and then locally edited — 94 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — priv/assets/js/menubar.js:163
  • priv/assets/js/angle_slider.js:25 · priv/assets/js/floating_window.js:23 — the two spans are one implementation copied and then locally edited — 79 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — priv/assets/js/angle_slider.js:25
  • priv/assets/js/calendar.js:13 · priv/assets/js/roving_tabindex.js:11 — the two spans are one implementation copied and then locally edited — 59 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — priv/assets/js/calendar.js:13
  • priv/assets/js/combobox.js:420 · priv/assets/js/combobox.js:653 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — priv/assets/js/combobox.js:420
  • priv/assets/js/combobox.js:123 · priv/assets/js/combobox.js:302 — the two spans are one implementation copied and then locally edited — 122 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — priv/assets/js/combobox.js:123
  • priv/assets/js/disclosure.js:98 · priv/assets/js/roving_tabindex.js:60 — the two spans are one implementation copied and then locally edited — 65 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — priv/assets/js/disclosure.js:98
  • priv/assets/js/select.js:61 · priv/assets/js/toggle_group.js:44 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — priv/assets/js/select.js:61
  • priv/assets/js/tabs.js:154 · priv/assets/js/toggle_group.js:132 — the two spans are one implementation copied and then locally edited — 94 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — priv/assets/js/tabs.js:154

What to do

  • Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity5.8 / 10Adequate✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

  • updatePosition has cyclomatic complexity 41 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/floating.js:450
  • positionPopup has cyclomatic complexity 33 and cognitive complexity 41; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/tooltip.js:187
  • handleKeyDown has cyclomatic complexity 31 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/tree.js:413
  • handleKeyDown has cyclomatic complexity 27 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/combobox.js:564
  • positionPopup has cyclomatic complexity 27 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — priv/assets/js/popover.js:195, priv/assets/js/preview_card.js:147
  • handleKeydown has cyclomatic complexity 26 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/menu.js:387
  • handleKeydown has cyclomatic complexity 26 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/context_menu.js:369
  • activate has cyclomatic complexity 24 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/navigation_menu.js:102
  • onKeyDown has cyclomatic complexity 24 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/otp.js:203
  • parse has cyclomatic complexity 23 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/number_field.js:119
  • positionPopup has cyclomatic complexity 21 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/menu.js:166
  • onKey has cyclomatic complexity 20 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/toolbar.js:70
  • mounted has cyclomatic complexity 19 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/number_field.js:35
  • mounted has cyclomatic complexity 17 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/drawer.js:115
  • main has cyclomatic complexity 16 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — development/web/script/claude-video/shared/assemble.mjs:161
  • moveSwipe has cyclomatic complexity 16 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/drawer.js:407
  • mounted has cyclomatic complexity 16 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/popover.js:52
  • runBeat has cyclomatic complexity 16 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — development/web/script/claude-video/shared/capture.mjs:89
  • handleClick has cyclomatic complexity 15 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/tree.js:362
  • select has cyclomatic complexity 14 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/tabs.js:78
  • set has cyclomatic complexity 14 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/slider.js:198
  • onKey has cyclomatic complexity 14 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/toggle_group.js:127
  • handleKeydown has cyclomatic complexity 14 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/disclosure.js:86
  • onKeyDown has cyclomatic complexity 14 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/number_field.js:307
  • onPopupKey has cyclomatic complexity 14 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/select.js:177
  • mounted has cyclomatic complexity 14 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/tooltip.js:45
  • destroyed has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/combobox.js:930
  • mounted has cyclomatic complexity 13 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/menu.js:19
  • onKey has cyclomatic complexity 13 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/radio_group.js:62
  • handleKeydown has cyclomatic complexity 13 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/roving_tabindex.js:53
  • applyTheme has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/chart_chartjs.js:138
  • handleKeydown has cyclomatic complexity 13 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/floating.js:398
  • updateAxis has cyclomatic complexity 12 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/scrollArea.js:67
  • groupWords has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — development/web/script/claude-video/shared/assemble.mjs:109
  • dropPosition has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/tree.js:615
  • scrubMove has cyclomatic complexity 12 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/number_field.js:427
  • mounted has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/scrollArea.js:22
  • onKey has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/tabs.js:153
  • (anonymous) has cyclomatic complexity 12 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — priv/assets/js/drawer.js:567
R3 · Large Files4.9 / 10Adequate✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

  • priv/assets/js/combobox.js has 854 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — priv/assets/js/combobox.js:1
  • priv/assets/js/floating.js has 603 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — priv/assets/js/floating.js:1
  • priv/assets/js/tree.js has 569 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — priv/assets/js/tree.js:1
  • priv/assets/js/drawer.js has 566 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — priv/assets/js/drawer.js:1
  • priv/assets/js/carousel.js has 513 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — priv/assets/js/carousel.js:1
  • priv/assets/js/number_field.js has 435 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — priv/assets/js/number_field.js:1
  • priv/assets/js/menu.js has 423 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — priv/assets/js/menu.js:1
  • priv/assets/js/context_menu.js has 408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — priv/assets/js/context_menu.js:1
  • priv/assets/js/clipboard.js has 402 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — priv/assets/js/clipboard.js:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage1.3 / 10Critical✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — priv/assets/js/combobox.js:1, priv/assets/js/tree.js:1, priv/assets/js/carousel.js:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling6.7 / 10Strong✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

  • test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.

What to do

  • Add type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
R7 · Dead Code9.9 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

  • This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×2) — priv/assets/js/drawer.js:22, priv/assets/js/drawer.js:112

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene0.0 / 10Critical✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

  • Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×16) — development/web/assets/js/app.js:23, priv/assets/js/editor_code_mirror.js:26, priv/assets/js/editor_code_mirror.js:35, …
  • Declared in development/web/assets/package.json but never imported anywhere in that package or its workspace members — while priv/assets/js/editor_code_mirror.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it. (×5)
  • Declared in development/web/assets/package.json but never imported anywhere in that package or its workspace members — while priv/assets/js/editor_lexical.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it. (×4)
  • Declared in development/web/assets/package.json but never imported anywhere in that package or its workspace members — while priv/assets/js/editor_tiptap.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it. (×2)
  • Declared in development/web/assets/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
  • Declared in development/web/assets/package.json but never imported anywhere in that package or its workspace members — while priv/assets/js/chart_echarts.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

S1 · Web-Security Posture9.5 / 10Exemplary✓ Tool-verified

Other · Security — Read from this repository's Elixir source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository serves HTTP itself (development/web/lib/development_web/endpoint.ex:2 — `Phoenix.Endpoint`), so its Elixir source was also read for the server controls: TLS served or HSTS set, security response headers, cookie flags and inbound validation — each credited where its Elixir spelling appears in production source, not proven on every route. A router that plugs Phoenix's `put_secure_browser_headers` is credited the headers Phoenix sends by default (`content-security-policy` from Phoenix 1.8, `x-frame-options` before it, as the `mix.lock` pins), and a cookie Plug sets the HttpOnly flag it sets by default.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

  • Set: Content-Security-Policy, Referrer-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Permitted-Cross-Domain-Policies. Missing: X-Frame-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each.(−0.5 on this card.) The server: development/web/lib/development_web/endpoint.ex:2 — `Phoenix.Endpoint`.

What to do

  • Add X-Frame-Options beside the headers the Elixir server already sets.
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X5 · Nullable reference types9.9 / 10Exemplary✓ Tool-verified

Other · Code Health — Whether Kotlin's null safety is not undermined by not-null assertions — `String` cannot hold null and `String?` must be checked before use in every Kotlin module, and each `!!` is a run-time `NullPointerException` the author has told the compiler cannot happen.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

WCAG coverage — what static analysis assessed

Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only

Not statically assessed — these 40 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health38%Weak — gated by R1, R10Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture76%Adequate — gated by D26Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity66%Adequate — gated by D16, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness38%Weak — gated by R4, R8, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security30%Weak — gated by D36, C1, C2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility43%Weak — gated by AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored — 2 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or schema — a module, Ecto schema or migration table named for it — ExAudit, PaperTrail, AshPaperTrail or Carbonite recording each change, or a Commanded / EventStore event-sourced store beside one) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
  • C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
  • C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 63 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AX1 Captive dependencies — Not applicable: the BEAM has no dependency-injection container — state lives in processes, and no process is handed an instance whose lifetime another one scopes; this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. Elixir processes share no mutable memory — state lives in a process's own mailbox — so there is no shared object to race on. Erlang processes share no mutable memory — state lives in a process's own mailbox — so there is no shared object to race on. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the Android app did not build — `./gradlew :app:assembleDebug` exited 1: ternal.ExecException: Process 'command '/opt/android-sdk/cmake/3.22.1/bin/cmake'' finished with non-zero exit value 1 at org.gradle.process.internal.DefaultExecHandle$ExecResultImpl.assertNormalExi…; runtime evidence skipped (launch chosen because development/mob/android/app/build.gradle applies the Android application plugin and development/mob/android/gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
  • D11 Test Reliability — Test reliability not scored — polyglot repository, one half has no runner
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D21 Naming Consistency — Naming consistency does not read html yet; not measured.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D25 ADR Conformance — no ADRs to check
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D6 Cohesion (LCOM4) — Cohesion (LCOM4) was not measured: of the 558 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (90 with fewer than two methods, 468 stateless), so LCOM4 is undefined for every type in this repository. Not scored — the metric does not apply here, and this is not a finding about this repository.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — polyglot repository, one half has no runner
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (9 value object(s))
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage data present for 15 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for Benchee jobs (the entries of a `Benchee.run` job map) or Benchfella `bench "…"` blocks under `use Benchfella` in any `.ex`/`.exs` file, or benchee or benchfella in a mix.exs, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
  • R5 Dependency Freshness — uses a bun lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • X1 Async correctness — X1 reached only 9% of this repository's production lines — elixir (196,928 lines), zig (1,443 lines), c (271 lines), objectivec (76 lines), erlang (25 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X12 Unreachable branch — X12 reached only 9% of this repository's production lines — elixir (196,928 lines), zig (1,443 lines), c (271 lines), objectivec (76 lines), erlang (25 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X16 Unfloored truncation loop — X16 reached only 9% of this repository's production lines — elixir (196,928 lines), zig (1,443 lines), c (271 lines), objectivec (76 lines), erlang (25 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — X18 reached only 9% of this repository's production lines — elixir (196,928 lines), zig (1,443 lines), c (271 lines), objectivec (76 lines), erlang (25 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — X2 reached only 9% of this repository's production lines — elixir (196,928 lines), zig (1,443 lines), c (271 lines), objectivec (76 lines), erlang (25 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X21 Side-effecting pattern guard — X21 reached only 9% of this repository's production lines — elixir (196,928 lines), zig (1,443 lines), c (271 lines), objectivec (76 lines), erlang (25 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — X24 reached only 6% of this repository's production lines — elixir (196,928 lines), kotlin (5,389 lines), zig (1,443 lines), c (271 lines), objectivec (76 lines), erlang (25 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — X26 reached only 2% of this repository's production lines — elixir (196,928 lines), javascript (14,018 lines), zig (1,443 lines), c (271 lines), objectivec (76 lines), erlang (25 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X27 Collection changed while being enumerated — X27 reached only 2% of this repository's production lines — elixir (196,928 lines), javascript (14,018 lines), zig (1,443 lines), c (271 lines), objectivec (76 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X29 Per-element action decided by a fixed element — X29 reached only 9% of this repository's production lines — elixir (196,928 lines), zig (1,443 lines), c (271 lines), objectivec (76 lines), erlang (25 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X3 Exception handling — X3 reached only 9% of this repository's production lines — elixir (196,928 lines), zig (1,443 lines), c (271 lines), objectivec (76 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X31 Test-only surface in a production module — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 136 finding(s)
AC2 · Forms & labels · <input> without a programmatic label · ×25
  • <input> without a programmatic label development/web/lib/development_web/components/headless/autocomplete.ex:110 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label development/web/lib/development_web/components/headless/combobox.ex:128 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label development/web/lib/development_web/components/headless/pills_input.ex:42 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label development/web/lib/development_web/components/headless/tags_input.ex:81 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label development/web/lib/development_web/live/showcase/field_form_demo.ex:114 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label development/web/lib/development_web/live/showcase/field_form_demo.ex:136 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label development/web/lib/development_web/live/showcase/field_form_demo.ex:158 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label development/web/lib/development_web/live/showcase/field_form_demo.ex:223 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:4644 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:4676 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:4692 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:2649 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:2667 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:2686 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:2692 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:2698 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:2716 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:2732 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:2738 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:2757 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:3371 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:3466 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:3490 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:3514 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:3538 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
AC2 · Forms & labels · <label> that labels no control · ×13
  • <label> that labels no control development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:1665 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:1692 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:1722 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:1750 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:1773 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:1805 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:1833 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:1932 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:2685 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:2691 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:2697 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:2731 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:2737 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC1 · Text alternatives · <img> without a text alternative · ×9
  • <img> without a text alternative development/web/lib/development_web/components/layouts.ex:41 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:5950 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative priv/components/avatar.eex:100 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative priv/components/avatar.eex:144 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative priv/components/shape.eex:16 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative priv/components/shape.eex:58 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative priv/headless/avatar.eex:11 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative priv/headless/avatar.eex:28 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative priv/headless/avatar.eex:29 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC5 · ARIA correctness · Invalid value "{" for aria-current · ×8
  • Invalid value "{" for aria-current priv/components/dock.eex:228 — "{" is not a valid value for aria-current — allowed: true, false, page, step, location, date, time.
  • Invalid value "{" for aria-current priv/components/pagination.eex:249 — "{" is not a valid value for aria-current — allowed: true, false, page, step, location, date, time.
  • Invalid value "{" for aria-current priv/components/stepper.eex:208 — "{" is not a valid value for aria-current — allowed: true, false, page, step, location, date, time.
  • Invalid value "{" for aria-current priv/components/stepper.eex:283 — "{" is not a valid value for aria-current — allowed: true, false, page, step, location, date, time.
  • Invalid value "{" for aria-current priv/components/table_content.eex:275 — "{" is not a valid value for aria-current — allowed: true, false, page, step, location, date, time.
  • Invalid value "{" for aria-current priv/headless/breadcrumb.eex:143 — "{" is not a valid value for aria-current — allowed: true, false, page, step, location, date, time.
  • Invalid value "{" for aria-current priv/headless/calendar.eex:177 — "{" is not a valid value for aria-current — allowed: true, false, page, step, location, date, time.
  • Invalid value "{" for aria-current priv/headless/carousel.eex:138 — "{" is not a valid value for aria-current — allowed: true, false, page, step, location, date, time.
AC5 · ARIA correctness · Invalid value "{" for aria-disabled · ×8
  • Invalid value "{" for aria-disabled priv/components/pagination.eex:249 — "{" is not a valid value for aria-disabled — allowed: true, false.
  • Invalid value "{" for aria-disabled priv/components/pagination.eex:277 — "{" is not a valid value for aria-disabled — allowed: true, false.
  • Invalid value "{" for aria-disabled priv/components/rating.eex:111 — "{" is not a valid value for aria-disabled — allowed: true, false.
  • Invalid value "{" for aria-disabled priv/components/stepper.eex:208 — "{" is not a valid value for aria-disabled — allowed: true, false.
  • Invalid value "{" for aria-disabled priv/components/stepper.eex:283 — "{" is not a valid value for aria-disabled — allowed: true, false.
  • Invalid value "{" for aria-disabled priv/headless/accordion.eex:109 — "{" is not a valid value for aria-disabled — allowed: true, false.
  • Invalid value "{" for aria-disabled priv/headless/button.eex:96 — "{" is not a valid value for aria-disabled — allowed: true, false.
  • Invalid value "{" for aria-disabled priv/headless/calendar.eex:177 — "{" is not a valid value for aria-disabled — allowed: true, false.
AC5 · ARIA correctness · Invalid value "{" for aria-selected · ×7
  • Invalid value "{" for aria-selected priv/components/tabs.eex:174 — "{" is not a valid value for aria-selected — allowed: true, false, undefined.
  • Invalid value "{" for aria-selected priv/components/tabs.eex:228 — "{" is not a valid value for aria-selected — allowed: true, false, undefined.
  • Invalid value "{" for aria-selected priv/components/tabs.eex:334 — "{" is not a valid value for aria-selected — allowed: true, false, undefined.
  • Invalid value "{" for aria-selected priv/components/tabs.eex:385 — "{" is not a valid value for aria-selected — allowed: true, false, undefined.
  • Invalid value "{" for aria-selected priv/headless/autocomplete.eex:168 — "{" is not a valid value for aria-selected — allowed: true, false, undefined.
  • Invalid value "{" for aria-selected priv/headless/autocomplete.eex:183 — "{" is not a valid value for aria-selected — allowed: true, false, undefined.
  • Invalid value "{" for aria-selected priv/headless/calendar.eex:177 — "{" is not a valid value for aria-selected — allowed: true, false, undefined.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC5 · ARIA correctness · Invalid value "{" for aria-checked · ×5
  • Invalid value "{" for aria-checked priv/components/checkbox_card.eex:123 — "{" is not a valid value for aria-checked — allowed: true, false, mixed, undefined.
  • Invalid value "{" for aria-checked priv/components/radio_card.eex:146 — "{" is not a valid value for aria-checked — allowed: true, false, mixed, undefined.
  • Invalid value "{" for aria-checked priv/components/rating.eex:203 — "{" is not a valid value for aria-checked — allowed: true, false, mixed, undefined.
  • Invalid value "{" for aria-checked priv/components/toggle_field.eex:111 — "{" is not a valid value for aria-checked — allowed: true, false, mixed, undefined.
  • Invalid value "{" for aria-checked priv/headless/checkbox.eex:45 — "{" is not a valid value for aria-checked — allowed: true, false, mixed, undefined.
AC3 · Page structure · <html> without a lang · ×4
  • <html> without a lang development/web/script/claude-video/shared/templates/intro.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang development/web/script/claude-video/shared/templates/outro.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang development/web/script/claude-video/shared/templates/segment.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang priv/headless/chart.eex:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×4
  • Click handler on a non-interactive <div> development/web/lib/development_web/components/mega_menu.ex:202 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> priv/components/mega_menu.eex:202 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> priv/headless/pills_input.eex:33 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> priv/headless/tags_input.eex:58 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC4 · Keyboard semantics · Click handler on a non-interactive <span> · ×4
  • Click handler on a non-interactive <span> development/web/lib/development_web/components/rating.ex:190 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <span> development/web/lib/development_web/components/rating.ex:196 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <span> priv/components/rating.eex:189 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <span> priv/components/rating.eex:195 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC5 · ARIA correctness · Invalid value "{" for aria-expanded · ×3
  • Invalid value "{" for aria-expanded priv/headless/accordion.eex:109 — "{" is not a valid value for aria-expanded — allowed: true, false, undefined.
  • Invalid value "{" for aria-expanded priv/headless/autocomplete.eex:110 — "{" is not a valid value for aria-expanded — allowed: true, false, undefined.
  • Invalid value "{" for aria-expanded priv/headless/burger.eex:38 — "{" is not a valid value for aria-expanded — allowed: true, false, undefined.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC4 · Keyboard semantics · Click handler on a non-interactive <tr> · ×2
  • Click handler on a non-interactive <tr> development/web/lib/development_web/components/headless/table.ex:168 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <tr> priv/headless/table.eex:151 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC5 · ARIA correctness · aria-hidden hides a focusable element · ×2
  • aria-hidden hides a focusable element development/web/lib/development_web/components/modal.ex:132 — aria-hidden="true" here hides the subtree from assistive tech, but a focusable descendant stays in the tab order — a keyboard user can land on a control screen readers can't see. Add inert, take the descendants out of the tab order (tabindex="-1"), or drop aria-hidden.
  • aria-hidden hides a focusable element priv/components/modal.eex:152 — aria-hidden="true" here hides the subtree from assistive tech, but a focusable descendant stays in the tab order — a keyboard user can land on a control screen readers can't see. Add inert, take the descendants out of the tab order (tabindex="-1"), or drop aria-hidden.
AC5 · ARIA correctness · Invalid value "{" for aria-hidden · ×2
  • Invalid value "{" for aria-hidden priv/components/carousel.eex:186 — "{" is not a valid value for aria-hidden — allowed: true, false, undefined.
  • Invalid value "{" for aria-hidden priv/headless/carousel.eex:101 — "{" is not a valid value for aria-hidden — allowed: true, false, undefined.
AC5 · ARIA correctness · Invalid value "{" for aria-live · ×2
  • Invalid value "{" for aria-live priv/headless/alert.eex:61 — "{" is not a valid value for aria-live — allowed: off, polite, assertive.
  • Invalid value "{" for aria-live priv/headless/carousel.eex:95 — "{" is not a valid value for aria-live — allowed: off, polite, assertive.
AC5 · ARIA correctness · Invalid value "{" for aria-busy · ×2
  • Invalid value "{" for aria-busy priv/headless/button.eex:96 — "{" is not a valid value for aria-busy — allowed: true, false.
  • Invalid value "{" for aria-busy priv/headless/button.eex:112 — "{" is not a valid value for aria-busy — allowed: true, false.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <select> without a programmatic label · ×1
  • <select> without a programmatic label development/web/lib/development_web/live/showcase/field_form_demo.ex:183 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels · <textarea> without a programmatic label · ×1
  • <textarea> without a programmatic label development/web/lib/development_web/live/showcase/field_form_demo.ex:210 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
AC3 · Page structure · Document without a <title> · ×1
  • Document without a <title> priv/headless/chart.eex:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
AC4 · Keyboard semantics · Click handler on a non-interactive <td> · ×1
  • Click handler on a non-interactive <td> development/web/lib/development_web/components/core_components.ex:378 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC5 · ARIA correctness · aria-expanded on a <span> with no role to carry it · ×1
  • aria-expanded on a <span> with no role to carry it development/web/lib/development_web/components/headless/preview_card.ex:75 — A plain <span> has the implicit role "generic", which supports no ARIA states, so this aria-expanded is dropped and assistive tech is never told the state at all. Put aria-expanded on the element that owns the behaviour (the button or control the user operates), or give this <span> a role that supports aria-expanded.
D14 · License Compliance · Banned license · ×1
  • Banned license: anubis_mcp — `anubis_mcp` 2.2.0 is published on hex.pm under `LGPL-3.0`, which this policy bans, and it is in the SHIPPED closure of this repository's mix.lock — so it is installed by everything that depends on this repository, not just by its test harness. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package, or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
R8 · Dependency Hygiene · Unlisted import 'phoenix-colocated' · ×1
  • Unlisted import 'phoenix-colocated' development/web/assets/js/app.js:23 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@codemirror/commands' · ×1
  • Unlisted import '@codemirror/commands' priv/assets/js/editor_code_mirror.js:26 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@codemirror/lang-javascript' · ×1
  • Unlisted import '@codemirror/lang-javascript' priv/assets/js/editor_code_mirror.js:35 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@codemirror/language' · ×1
  • Unlisted import '@codemirror/language' priv/assets/js/editor_code_mirror.js:27 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@codemirror/state' · ×1
  • Unlisted import '@codemirror/state' priv/assets/js/editor_code_mirror.js:13 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@codemirror/view' · ×1
  • Unlisted import '@codemirror/view' priv/assets/js/editor_code_mirror.js:14 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@lexical/history' · ×1
  • Unlisted import '@lexical/history' priv/assets/js/editor_lexical.js:19 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@lexical/rich-text' · ×1
  • Unlisted import '@lexical/rich-text' priv/assets/js/editor_lexical.js:18 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@lexical/utils' · ×1
  • Unlisted import '@lexical/utils' priv/assets/js/editor_lexical.js:20 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@milkdown/kit' · ×1
  • Unlisted import '@milkdown/kit' priv/assets/js/editor_milk_down.js:15 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@tiptap/core' · ×1
  • Unlisted import '@tiptap/core' priv/assets/js/editor_tiptap.js:37 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@tiptap/starter-kit' · ×1
  • Unlisted import '@tiptap/starter-kit' priv/assets/js/editor_tiptap.js:38 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'billboard.js' · ×1
  • Unlisted import 'billboard.js' priv/assets/js/chart_billboard.js:29 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'chart.js' · ×1
  • Unlisted import 'chart.js' priv/assets/js/chart_chartjs.js:13 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'echarts' · ×1
  • Unlisted import 'echarts' priv/assets/js/chart_echarts.js:28 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'lexical' · ×1
  • Unlisted import 'lexical' priv/assets/js/editor_lexical.js:17 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Serious — 658 finding(s)
D15 · Churn × Complexity Hotspots · Repeated repair · ×46
  • Repeated repair: lib/mishka_chelekom/cms_bundle_exporter.ex lib/mishka_chelekom/cms_bundle_exporter.ex:126 — lib/mishka_chelekom/cms_bundle_exporter.ex changed 13 times in last 90 days and 11 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is CmsBundleExporter.convert at line 126), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(catalog): every public helper a styled component defines is in its catalog's helpers”; “fix(sobelow): a targeted skip, with its reason, on each function that only reads the kit's own files”; “fix(credo): split the deeply nested and branchy functions in lib”; “fix(credo): readability and refactor findings in lib”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- lib/mishka_chelekom/cms_bundle_exporter.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: lib/mishka_chelekom/generators/assets.ex lib/mishka_chelekom/generators/assets.ex:231 — lib/mishka_chelekom/generators/assets.ex changed 11 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is Assets.register_hook at line 231), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(sobelow): a targeted skip, with its reason, on each function that only reads the kit's own files”; “fix(credo): split the deeply nested and branchy functions in lib”; “fix(credo): readability and refactor findings in lib”; “fix(dialyzer): match EEx.tokenize's error tuple, and complete two specs”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- lib/mishka_chelekom/generators/assets.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: development/web/lib/development_web/components/file_field.ex development/web/lib/development_web/components/file_field.ex:101 — development/web/lib/development_web/components/file_field.ex changed 9 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is FileField.file_field at line 101), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(components): tab badges, accordion and combobox triggers, and card, toggle and dropzone labels hold only phrasing content (#550)”; “fix(components): a guard clause with a keyword do is written with do ... end”; “fix(components): fields render without a value, positions name their edge, and extra_small is its own size again (#526)”; “fix(components): caller display classes win, avatars keep their size, breadcrumbs wrap, headless and kit-name fixes (#524)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- development/web/lib/development_web/components/file_field.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: lib/mix/tasks/mishka.ui.uninstall.ex lib/mix/tasks/mishka.ui.uninstall.ex:77 — lib/mix/tasks/mishka.ui.uninstall.ex changed 9 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is Uninstall.igniter at line 77), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(uninstall): a component that is not installed is reported, not removed”; “fix(credo): split the deeply nested and branchy functions in lib”; “fix(credo): readability and refactor findings in lib”; “fix(mob): tags declared in config :mob, :extra_tags, doc links in templates, version 0.0.10 (#533)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- lib/mix/tasks/mishka.ui.uninstall.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: lib/mishka_chelekom/config.ex lib/mishka_chelekom/config.ex:116 — lib/mishka_chelekom/config.ex changed 7 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is Config.read_custom_css at line 116), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(sobelow): a targeted skip, with its reason, on each function that only reads the kit's own files”; “fix(credo): readability and refactor findings in lib”; “fix(priv): classes Tailwind drew nothing for, and theme colours the theme never defined”; “fix(mcp): list_css_variables reads the variables and their defaults from the stylesheet”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- lib/mishka_chelekom/config.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: lib/mishka_chelekom/mcp/component_config.ex lib/mishka_chelekom/mcp/component_config.ex:54 — lib/mishka_chelekom/mcp/component_config.ex changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is ComponentConfig.component_names at line 54), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(sobelow): a targeted skip, with its reason, on each function that only reads the kit's own files”; “fix(credo): readability and refactor findings in lib”; “fix(mcp): link a component to the docs page its own config names”; “fix(mcp): accept a client's component or hook name only if the kit ships it”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- lib/mishka_chelekom/mcp/component_config.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: development/web/lib/development_web/components/accordion.ex development/web/lib/development_web/components/accordion.ex:164 — development/web/lib/development_web/components/accordion.ex changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is Accordion.format_initial_open at line 164), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(components): tab badges, accordion and combobox triggers, and card, toggle and dropzone labels hold only phrasing content (#550)”; “fix(components): a guard clause with a keyword do is written with do ... end”; “fix(components): fields render without a value, positions name their edge, and extra_small is its own size again (#526)”; “fix(a11y): images take alt text, icon-only controls get an accessible name (#523)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- development/web/lib/development_web/components/accordion.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: development/web/lib/development_web/components/dock.ex development/web/lib/development_web/components/dock.ex:294 — development/web/lib/development_web/components/dock.ex changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is Dock.dock_item_class at line 294), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(components): a fixed overlay resets its margin, so a parent's space-y does not push it into view”; “fix(components): a guard clause with a keyword do is written with do ... end”; “fix(components): fields render without a value, positions name their edge, and extra_small is its own size again (#526)”; “fix(a11y): images take alt text, icon-only controls get an accessible name (#523)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- development/web/lib/development_web/components/dock.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: development/web/lib/development_web/components/badge.ex development/web/lib/development_web/components/badge.ex:861 — development/web/lib/development_web/components/badge.ex changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is Badge.size_class at line 861), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(components): tab badges, accordion and combobox triggers, and card, toggle and dropzone labels hold only phrasing content (#550)”; “fix(components): a guard clause with a keyword do is written with do ... end”; “fix(components): fields render without a value, positions name their edge, and extra_small is its own size again (#526)”; “fix(components): caller display classes win, avatars keep their size, breadcrumbs wrap, headless and kit-name fixes (#524)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- development/web/lib/development_web/components/badge.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: development/web/lib/development_web/components/combobox.ex development/web/lib/development_web/components/combobox.ex:155 — development/web/lib/development_web/components/combobox.ex changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is Combobox.combobox at line 155), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(components): tab badges, accordion and combobox triggers, and card, toggle and dropzone labels hold only phrasing content (#550)”; “fix(components): fields render without a value, positions name their edge, and extra_small is its own size again (#526)”; “fix(components): caller display classes win, avatars keep their size, breadcrumbs wrap, headless and kit-name fixes (#524)”; “fix(combobox): one placed without options draws instead of raising”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- development/web/lib/development_web/components/combobox.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: development/web/lib/development_web/components/button.ex development/web/lib/development_web/components/button.ex:1766 — development/web/lib/development_web/components/button.ex changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is Button.color_variant at line 1766), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(components): a guard clause with a keyword do is written with do ... end”; “fix(components): fields render without a value, positions name their edge, and extra_small is its own size again (#526)”; “fix(components): caller display classes win, avatars keep their size, breadcrumbs wrap, headless and kit-name fixes (#524)”; “fix(priv): classes Tailwind drew nothing for, and theme colours the theme never defined”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- development/web/lib/development_web/components/button.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: development/web/lib/development_web/components/pagination.ex development/web/lib/development_web/components/pagination.ex:308 — development/web/lib/development_web/components/pagination.ex changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is Pagination.build_pagination at line 308), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(components): a guard clause with a keyword do is written with do ... end”; “fix(components): fields render without a value, positions name their edge, and extra_small is its own size again (#526)”; “fix(components): caller display classes win, avatars keep their size, breadcrumbs wrap, headless and kit-name fixes (#524)”; “fix(priv): classes Tailwind drew nothing for, and theme colours the theme never defined”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- development/web/lib/development_web/components/pagination.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: lib/mishka_chelekom/mcp/tools/get_component_info.ex lib/mishka_chelekom/mcp/tools/get_component_info.ex:130 — lib/mishka_chelekom/mcp/tools/get_component_info.ex changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is GetComponentInfo.format_config_section at line 130), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(sobelow): a targeted skip, with its reason, on each function that only reads the kit's own files”; “fix(credo): readability and refactor findings in lib”; “fix(mcp): link a component to the docs page its own config names”; “fix(mcp): accept a client's component or hook name only if the kit ships it”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- lib/mishka_chelekom/mcp/tools/get_component_info.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: development/web/lib/development_web/components/card.ex development/web/lib/development_web/components/card.ex:871 — development/web/lib/development_web/components/card.ex changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is Card.display_class at line 871), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(components): a guard clause with a keyword do is written with do ... end”; “fix(components): fields render without a value, positions name their edge, and extra_small is its own size again (#526)”; “fix(components): caller display classes win, avatars keep their size, breadcrumbs wrap, headless and kit-name fixes (#524)”; “fix(priv): classes Tailwind drew nothing for, and theme colours the theme never defined”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- development/web/lib/development_web/components/card.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: development/web/lib/development_web/components/table.ex development/web/lib/development_web/components/table.ex:135 — development/web/lib/development_web/components/table.ex changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is Table.table at line 135), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(components): a guard clause with a keyword do is written with do ... end”; “fix(components): fields render without a value, positions name their edge, and extra_small is its own size again (#526)”; “fix(components): caller display classes win, avatars keep their size, breadcrumbs wrap, headless and kit-name fixes (#524)”; “fix(priv): classes Tailwind drew nothing for, and theme colours the theme never defined”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- development/web/lib/development_web/components/table.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: lib/mishka_chelekom/mcp/resources/list_css_variables.ex lib/mishka_chelekom/mcp/resources/list_css_variables.ex:398 — lib/mishka_chelekom/mcp/resources/list_css_variables.ex changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is ListCssVariables.format_css_variables at line 398), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(sobelow): a targeted skip, with its reason, on each function that only reads the kit's own files”; “fix(credo): readability and refactor findings in lib”; “fix(priv): classes Tailwind drew nothing for, and theme colours the theme never defined”; “fix(mcp): list_css_variables reads the variables and their defaults from the stylesheet”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- lib/mishka_chelekom/mcp/resources/list_css_variables.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: lib/mishka_chelekom/mcp/tools/get_docs.ex lib/mishka_chelekom/mcp/tools/get_docs.ex:157 — lib/mishka_chelekom/mcp/tools/get_docs.ex changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is GetDocs.local_doc_pointer at line 157), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(sobelow): a targeted skip, with its reason, on each function that only reads the kit's own files”; “fix(credo): split the deeply nested and branchy functions in lib”; “fix(credo): readability and refactor findings in lib”; “fix(mcp): accept a client's component or hook name only if the kit ships it”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- lib/mishka_chelekom/mcp/tools/get_docs.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: lib/mishka_chelekom/mcp/tools/get_js_hook_info.ex lib/mishka_chelekom/mcp/tools/get_js_hook_info.ex:59 — lib/mishka_chelekom/mcp/tools/get_js_hook_info.ex changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is GetJsHookInfo.get_hook_info at line 59), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(sobelow): a targeted skip, with its reason, on each function that only reads the kit's own files”; “fix(credo): split the deeply nested and branchy functions in lib”; “fix(credo): readability and refactor findings in lib”; “fix(mcp): accept a client's component or hook name only if the kit ships it”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- lib/mishka_chelekom/mcp/tools/get_js_hook_info.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: lib/mishka_chelekom/generators/import_macro.ex lib/mishka_chelekom/generators/import_macro.ex:161 — lib/mishka_chelekom/generators/import_macro.ex changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is ImportMacro.use_import_module at line 161), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(sobelow): a targeted skip, with its reason, on each function that only reads the kit's own files”; “fix(credo): split the deeply nested and branchy functions in lib”; “fix(credo): readability and refactor findings in lib”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- lib/mishka_chelekom/generators/import_macro.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: development/web/lib/development_web/components/toggle_field.ex development/web/lib/development_web/components/toggle_field.ex:79 — development/web/lib/development_web/components/toggle_field.ex changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is ToggleField.toggle_field at line 79), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(components): tab badges, accordion and combobox triggers, and card, toggle and dropzone labels hold only phrasing content (#550)”; “fix(components): fields render without a value, positions name their edge, and extra_small is its own size again (#526)”; “fix(components): caller display classes win, avatars keep their size, breadcrumbs wrap, headless and kit-name fixes (#524)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- development/web/lib/development_web/components/toggle_field.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: development/web/lib/development_web/components/banner.ex development/web/lib/development_web/components/banner.ex:144 — development/web/lib/development_web/components/banner.ex changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is Banner.banner at line 144), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(components): a fixed overlay resets its margin, so a parent's space-y does not push it into view”; “fix(components): a guard clause with a keyword do is written with do ... end”; “fix(components): fields render without a value, positions name their edge, and extra_small is its own size again (#526)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- development/web/lib/development_web/components/banner.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: lib/mishka_chelekom/generators/core.ex lib/mishka_chelekom/generators/core.ex:489 — lib/mishka_chelekom/generators/core.ex changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is Core.resolve_components at line 489), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(sobelow): a targeted skip, with its reason, on each function that only reads the kit's own files”; “fix(credo): split the deeply nested and branchy functions in lib”; “fix(credo): readability and refactor findings in lib”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- lib/mishka_chelekom/generators/core.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: development/web/lib/development_web/components/password_field.ex development/web/lib/development_web/components/password_field.ex:125 — development/web/lib/development_web/components/password_field.ex changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is PasswordField.password_field at line 125), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(components): fields render without a value, positions name their edge, and extra_small is its own size again (#526)”; “fix(a11y): images take alt text, icon-only controls get an accessible name (#523)”; “fix(priv): classes Tailwind drew nothing for, and theme colours the theme never defined”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- development/web/lib/development_web/components/password_field.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: development/web/lib/development_web/components/search_field.ex development/web/lib/development_web/components/search_field.ex:124 — development/web/lib/development_web/components/search_field.ex changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is SearchField.search_field at line 124), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(components): fields render without a value, positions name their edge, and extra_small is its own size again (#526)”; “fix(a11y): images take alt text, icon-only controls get an accessible name (#523)”; “fix(priv): classes Tailwind drew nothing for, and theme colours the theme never defined”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- development/web/lib/development_web/components/search_field.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: development/web/lib/development_web/components/checkbox_card.ex development/web/lib/development_web/components/checkbox_card.ex:104 — development/web/lib/development_web/components/checkbox_card.ex changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is CheckboxCard.checkbox_card at line 104), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(components): tab badges, accordion and combobox triggers, and card, toggle and dropzone labels hold only phrasing content (#550)”; “fix(components): fields render without a value, positions name their edge, and extra_small is its own size again (#526)”; “fix(components): caller display classes win, avatars keep their size, breadcrumbs wrap, headless and kit-name fixes (#524)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- development/web/lib/development_web/components/checkbox_card.ex`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • + 21 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×40
  • No test reaches this file priv/assets/js/combobox.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file priv/assets/js/tree.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file priv/assets/js/carousel.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file priv/assets/js/number_field.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file priv/assets/js/clipboard.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file priv/assets/js/menu.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file priv/assets/js/context_menu.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file priv/assets/js/navigation_menu.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file priv/assets/js/collapsible.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file development/web/script/claude-video/shared/capture.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file priv/assets/js/headless_combobox.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file priv/assets/js/slider.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file priv/assets/js/chart_echarts.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file priv/assets/js/select.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file priv/assets/js/otp.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file priv/assets/js/chart_chartjs.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file priv/assets/js/editor_tiptap.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file priv/assets/js/tooltip.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file priv/assets/js/menubar.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file development/web/script/claude-video/gladia/sync-captions.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file priv/assets/js/editor_milk_down.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file priv/assets/js/disclosure.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file priv/assets/js/editor_lexical.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file priv/assets/js/scrollArea.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file priv/assets/js/editor_code_mirror.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • + 15 more in this group — see findings.md.
D3 · God Classes · FileTooLong · ×39
  • FileTooLong: showcase/headless_daisyui_examples.ex development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex — FileTooLong — 13137 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 12637 over it, 26.27× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: showcase/headless_baseui_examples.ex development/web/lib/development_web/live/showcase/headless_baseui_examples.ex — FileTooLong — 6861 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 6361 over it, 13.72× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: showcase/headless_preview.ex development/web/lib/development_web/live/showcase/headless_preview.ex — FileTooLong — 4220 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 70 functions. The bar is 500 significant lines; this is 3720 over it, 8.44× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: mishka_mob/MobBridge.kt development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt — FileTooLong — 3292 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2792 over it, 6.58× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/button.ex development/web/lib/development_web/components/button.ex — FileTooLong — 1568 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1068 over it, 3.14× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: showcase/preview.ex development/web/lib/development_web/live/showcase/preview.ex — FileTooLong — 1542 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1042 over it, 3.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: showcase/headless_form_demos.ex development/web/lib/development_web/live/showcase/headless_form_demos.ex — FileTooLong — 1340 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 840 over it, 2.68× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/pagination.ex development/web/lib/development_web/components/pagination.ex — FileTooLong — 1146 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 646 over it, 2.29× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/combobox.ex development/web/lib/development_web/components/combobox.ex — FileTooLong — 1014 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 514 over it, 2.03× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: mishka_chelekom/cms_bundle_exporter.ex lib/mishka_chelekom/cms_bundle_exporter.ex — FileTooLong — 951 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 83 functions. The bar is 500 significant lines; this is 451 over it, 1.90× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: tasks/mishka.ui.uninstall.ex lib/mix/tasks/mishka.ui.uninstall.ex — FileTooLong — 872 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 88 functions. The bar is 500 significant lines; this is 372 over it, 1.74× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: showcase/kit_demo.ex development/web/lib/development_web/live/showcase/kit_demo.ex — FileTooLong — 857 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 357 over it, 1.71× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/list.ex development/web/lib/development_web/components/list.ex — FileTooLong — 841 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 341 over it, 1.68× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/table.ex development/web/lib/development_web/components/table.ex — FileTooLong — 833 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 333 over it, 1.67× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/password_field.ex development/web/lib/development_web/components/password_field.ex — FileTooLong — 813 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 313 over it, 1.63× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/search_field.ex development/web/lib/development_web/components/search_field.ex — FileTooLong — 800 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 300 over it, 1.60× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/accordion.ex development/web/lib/development_web/components/accordion.ex — FileTooLong — 786 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 286 over it, 1.57× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/number_field.ex development/web/lib/development_web/components/number_field.ex — FileTooLong — 778 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 278 over it, 1.56× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/date_time_field.ex development/web/lib/development_web/components/date_time_field.ex — FileTooLong — 776 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 276 over it, 1.55× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/tel_field.ex development/web/lib/development_web/components/tel_field.ex — FileTooLong — 773 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 273 over it, 1.55× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/text_field.ex development/web/lib/development_web/components/text_field.ex — FileTooLong — 773 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 273 over it, 1.55× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/mishka_calendar.ex development/mob/lib/mishka_mob/components/mishka_calendar.ex — FileTooLong — 770 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 45 functions. The bar is 500 significant lines; this is 270 over it, 1.54× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/email_field.ex development/web/lib/development_web/components/email_field.ex — FileTooLong — 768 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 268 over it, 1.54× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/drawer.ex development/mob/lib/mishka_mob/showcase/components/drawer.ex — FileTooLong — 757 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 40 functions. The bar is 500 significant lines; this is 257 over it, 1.51× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/textarea_field.ex development/web/lib/development_web/components/textarea_field.ex — FileTooLong — 742 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 242 over it, 1.48× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • + 14 more in this group — see findings.md.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×23
  • Animation without a prefers-reduced-motion guard development/web/lib/development_web/components/spinner.ex:168 — <span> moves — its `animate-bounce` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard development/web/lib/development_web/components/spinner.ex:169 — <span> moves — its `animate-bounce` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard development/web/lib/development_web/components/spinner.ex:170 — <span> moves — its `animate-bounce` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard development/web/lib/development_web/components/spinner.ex:177 — <span> moves — its `animate-bounce` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard development/web/lib/development_web/components/spinner.ex:178 — <span> moves — its `animate-bounce` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard development/web/lib/development_web/components/spinner.ex:179 — <span> moves — its `animate-bounce` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard development/web/lib/development_web/components/stepper.ex — <svg> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard development/web/lib/development_web/live/showcase/headless_baseui_examples.ex — <svg> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:2747 — <span> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard development/web/lib/development_web/live/showcase/headless_preview.ex:903 — <span> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard development/web/lib/development_web/live/showcase/loading_overlay_demo.ex:31 — <span> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard development/web/script/claude-video/shared/templates/intro.html:94 — `.hf-slot` moves (`animation: slotIn 0.34s cubic-bezier(0.2, 0.8, 0.3, 1) forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard development/web/script/claude-video/shared/templates/intro.html:105 — `.hf-slot[data-last="true"]` moves (`animation: slotIn 0.34s cubic-bezier(0.2, 0.8, 0.3, 1) forwards, slotAccept 0.5s ease-out forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard development/web/script/claude-video/shared/templates/intro.html:110 — `.hf-slots[data-resolving="true"] .hf-slot` moves (`animation: slotOut 0.42s cubic-bezier(0.6, 0, 0.8, 0.2) forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard development/web/script/claude-video/shared/templates/intro.html:158 — `.hf-title` moves (`animation: titleIn 0.5s cubic-bezier(0.2, 0.8, 0.3, 1) forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard development/web/script/claude-video/shared/templates/intro.html:183 — `.hf-meta` moves (`animation: titleIn 0.5s ease-out forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard development/web/script/claude-video/shared/templates/intro.html:198 — `.hf-tagline` moves (`animation: titleIn 0.5s ease-out forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard development/web/script/claude-video/shared/templates/intro.html:231 — `.hf-lockup` moves (`animation: rise 0.5s ease-out forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard development/web/script/claude-video/shared/templates/outro.html:60 — `.hf-eyebrow` moves (`animation: rise 0.45s ease-out 0.15s forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard development/web/script/claude-video/shared/templates/outro.html:71 — `.hf-url` moves (`animation: rise 0.5s cubic-bezier(0.2, 0.8, 0.3, 1) 0.32s forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard development/web/script/claude-video/shared/templates/outro.html:83 — `.hf-url::after` moves (`animation: draw 0.85s cubic-bezier(0.3, 0.7, 0.2, 1) 0.75s forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard development/web/script/claude-video/shared/templates/outro.html:90 — `.hf-note` moves (`animation: rise 0.45s ease-out 1.35s forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard development/web/script/claude-video/shared/templates/segment.html:67 — `.seg-index` moves (`animation: rise 0.4s ease-out 0.1s forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
AC6 · Visual & motion safety · Focus outline removed inline · ×16
  • Focus outline removed inline development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:5191 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:5198 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:5205 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:5212 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:5228 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:5238 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:5245 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:5252 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:5262 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:5269 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:5276 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:5292 — <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline development/web/lib/development_web/live/showcase/headless_preview.ex:1619 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline development/web/lib/development_web/live/showcase/headless_preview.ex:3584 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline development/web/lib/development_web/live/showcase/headless_preview.ex:3602 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline development/web/lib/development_web/live/showcase/headless_preview.ex:3620 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
AC4 · Keyboard semantics · Modal dialog does not manage focus · ×14
  • Modal dialog does not manage focus development/web/lib/development_web/components/drawer.ex:102 — This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
  • Modal dialog does not manage focus development/web/lib/development_web/components/headless/color_input.ex:85 — This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
  • Modal dialog does not manage focus development/web/lib/development_web/components/headless/floating_window.ex:36 — This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
  • Modal dialog does not manage focus development/web/lib/development_web/components/headless/preview_card.ex:84 — This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
  • Modal dialog does not manage focus development/web/lib/development_web/components/modal.ex:137 — This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
  • Modal dialog does not manage focus development/web/lib/development_web/components/popover.ex:155 — This <span role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
  • Modal dialog does not manage focus development/web/lib/development_web/components/popover.ex:220 — This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
  • Modal dialog does not manage focus priv/components/drawer.eex:102 — This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
  • Modal dialog does not manage focus priv/components/modal.eex:157 — This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
  • Modal dialog does not manage focus priv/components/popover.eex:152 — This <span role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
  • Modal dialog does not manage focus priv/components/popover.eex:215 — This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
  • Modal dialog does not manage focus priv/headless/color_input.eex:85 — This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
  • Modal dialog does not manage focus priv/headless/floating_window.eex:36 — This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
  • Modal dialog does not manage focus priv/headless/preview_card.eex:84 — This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×12
  • Duplicated block (6 lines × 2) development/web/lib/development_web/components/checkbox_field.ex:93 — development/web/lib/development_web/components/checkbox_field.ex:93-98 | development/web/lib/development_web/components/input_field.ex:93-98 — 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 — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (6 lines × 2) development/mob/lib/mishka_mob/components/mishka_alpha_slider.ex:180 — development/mob/lib/mishka_mob/components/mishka_alpha_slider.ex:180-185 | development/mob/lib/mishka_mob/components/mishka_hue_slider.ex:175-180 — 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 — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (6 lines × 2) development/web/lib/development_web/components/combobox.ex:167 — development/web/lib/development_web/components/combobox.ex:167-172 | development/web/lib/development_web/components/combobox.ex:394-399 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) development/web/lib/development_web/components/checkbox_card.ex:210 — development/web/lib/development_web/components/checkbox_card.ex:210-215 | development/web/lib/development_web/components/checkbox_field.ex:267-272 — 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 — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (6 lines × 2) development/web/lib/development_web/components/core_components.ex:361 — development/web/lib/development_web/components/core_components.ex:361-366 | development/web/lib/development_web/components/table.ex:136-141 — 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 — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (6 lines × 2) development/web/lib/development_web/components/radio_card.ex:211 — development/web/lib/development_web/components/radio_card.ex:211-216 | development/web/lib/development_web/components/radio_field.ex:260-265 — 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 — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (6 lines × 2) development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:7331 — development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:7331-7336 | development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:14005-14010 — before extracting anything, compare `development/web/lib/development_web/live/showcase/headless_baseui_examples.ex` and `development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:7340 — development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:7340-7345 | development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:13969-13974 — before extracting anything, compare `development/web/lib/development_web/live/showcase/headless_baseui_examples.ex` and `development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:7357 — development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:7357-7362 | development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:13978-13983 — before extracting anything, compare `development/web/lib/development_web/live/showcase/headless_baseui_examples.ex` and `development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) development/web/lib/development_web/live/showcase/catalog.ex:37 — development/web/lib/development_web/live/showcase/catalog.ex:37-42 | development/web/lib/development_web/live/showcase/headless_catalog.ex:12-17 — 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 — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `development/web/lib/development_web/live/showcase/catalog.ex:46` calls `get`, `t`, `component` and `development/web/lib/development_web/live/showcase/headless_catalog.ex:20` does not — 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.
  • Duplicated block (6 lines × 2) development/mob/lib/mishka_mob/components/mishka_alpha_slider.ex:164 — development/mob/lib/mishka_mob/components/mishka_alpha_slider.ex:164-169 | development/mob/lib/mishka_mob/components/mishka_hue_slider.ex:166-171 — 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 — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `development/mob/lib/mishka_mob/components/mishka_hue_slider.ex:159` calls `normalize_hue`, `is_number`, `wrap_hue` and `development/mob/lib/mishka_mob/components/mishka_alpha_slider.ex:159` does not — 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.
  • Duplicated block (6 lines × 2) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:1621 — development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:1621-1626 | development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:1668-1673 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:1620` calls `elapsedRealtime` and `development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:1667` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Edited copy of a member (2 corresponding lines) · ×11
  • Edited copy of a member (2 corresponding lines) lib/mishka_chelekom/cms_bundle/sanitize.ex:80 — lib/mishka_chelekom/cms_bundle/sanitize.ex:80-81 | lib/mix/tasks/mishka.ui.export.ex:745-746 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) lib/mix/tasks/mishka.ui.gen.component.ex:461 — lib/mix/tasks/mishka.ui.gen.component.ex:461-462 | lib/mix/tasks/mishka.ui.gen.headless.ex:203-204 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) development/mob/lib/mishka_mob/components/mishka_alert_dialog.ex:139 — development/mob/lib/mishka_mob/components/mishka_alert_dialog.ex:139-140 | development/mob/lib/mishka_mob/components/mishka_dialog.ex:289-290 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) development/mob/lib/mishka_mob/components/mishka_dialog.ex:504 — development/mob/lib/mishka_mob/components/mishka_dialog.ex:504-505 | development/mob/lib/mishka_mob/components/mishka_popover.ex:264-265 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) development/mob/lib/mishka_mob/showcase/components/color_picker.ex:150 — development/mob/lib/mishka_mob/showcase/components/color_picker.ex:150-151 | development/mob/lib/mishka_mob/showcase/components/hue_slider.ex:110-111 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) lib/mishka_chelekom/generators/core.ex:221 — lib/mishka_chelekom/generators/core.ex:221-222 | lib/mix/tasks/mishka.ui.gen.mob.ex:232-233 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) development/mob/lib/mishka_mob/components/mishka_dialog.ex:510 — development/mob/lib/mishka_mob/components/mishka_dialog.ex:510-511 | development/mob/lib/mishka_mob/components/mishka_popover.ex:270-271 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) development/mob/lib/mishka_mob/components/mishka_dialog.ex:519 — development/mob/lib/mishka_mob/components/mishka_dialog.ex:519-520 | development/mob/lib/mishka_mob/components/mishka_popover.ex:456-457 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) development/mob/lib/mishka_mob/components/mishka_select.ex:159 — development/mob/lib/mishka_mob/components/mishka_select.ex:159-161 | development/mob/lib/mishka_mob/components/mishka_toggle_group.ex:122-123 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) development/mob/lib/mishka_mob/components/mishka_dialog.ex:507 — development/mob/lib/mishka_mob/components/mishka_dialog.ex:507-508 | development/mob/lib/mishka_mob/components/mishka_popover.ex:267-268 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (2 corresponding lines) development/web/lib/development_web/live/showcase/headless_form_demos.ex:1186 — development/web/lib/development_web/live/showcase/headless_form_demos.ex:1186-1187 | development/web/lib/development_web/live/showcase/tree_demos.ex:156-157 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D3 · God Classes · TooManyFunctions · ×8
  • TooManyFunctions: MishkaDrawer development/mob/lib/mishka_mob/components/mishka_drawer.ex:1 — TooManyFunctions — 57 functions. The bar is 30 functions; this is 27 over it, 1.90× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: MishkaPopover development/mob/lib/mishka_mob/components/mishka_popover.ex:1 — TooManyFunctions — 46 functions. The bar is 30 functions; this is 16 over it, 1.53× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: MishkaTree development/mob/lib/mishka_mob/components/mishka_tree.ex:1 — TooManyFunctions — 46 functions. The bar is 30 functions; this is 16 over it, 1.53× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: MishkaToolbar development/mob/lib/mishka_mob/components/mishka_toolbar.ex:1 — TooManyFunctions — 41 functions. The bar is 30 functions; this is 11 over it, 1.37× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: AttrValues lib/mishka_chelekom/cms_bundle/attr_values.ex:1 — TooManyFunctions — 41 functions. The bar is 30 functions; this is 11 over it, 1.37× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: MishkaDialog development/mob/lib/mishka_mob/components/mishka_dialog.ex:1 — TooManyFunctions — 33 functions. The bar is 30 functions; this is 3 over it, 1.10× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: Npm lib/mishka_chelekom/cms_bundle/npm.ex:1 — TooManyFunctions — 33 functions. The bar is 30 functions; this is 3 over it, 1.10× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
  • TooManyFunctions: Core lib/mishka_chelekom/generators/core.ex:1 — TooManyFunctions — 31 functions. The bar is 30 functions; this is 1 over it, 1.03× the bar. The counted members are a module's functions — a module holds no instance state, so there is no shared data to group them by and no type to move them onto. To reduce it, extract each cohesive family of functions into a new module of its own and have this one delegate to it, so no single module carries every responsibility.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×8
  • Duplicated block (5 lines × 2) development/web/lib/development_web/live/showcase/example_source.ex:42 — development/web/lib/development_web/live/showcase/example_source.ex:42-46 | development/web/lib/development_web/live/showcase/json_meta.ex:81-85 — 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 — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:7368 — development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:7368-7372 | development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:14016-14020 — before extracting anything, compare `development/web/lib/development_web/live/showcase/headless_baseui_examples.ex` and `development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:7368` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) development/mob/lib/mishka_mob/components/mishka_checkbox_group.ex:129 — development/mob/lib/mishka_mob/components/mishka_checkbox_group.ex:129-133 | development/mob/lib/mishka_mob/components/mishka_toggle_group.ex:96-100 — 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 — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) development/mob/lib/mishka_mob/components/mishka_radio_group.ex:99 — development/mob/lib/mishka_mob/components/mishka_radio_group.ex:99-103 | development/mob/lib/mishka_mob/components/mishka_segmented_control.ex:234-238 — 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 — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) development/mob/lib/mishka_mob/showcase/components/drawer.ex:980 — development/mob/lib/mishka_mob/showcase/components/drawer.ex:980-984 | development/mob/lib/mishka_mob/showcase/kit.ex:278-282 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (5 lines × 2) development/web/lib/development_web/live/showcase/color_input_form_demo.ex:14 — development/web/lib/development_web/live/showcase/color_input_form_demo.ex:14-18 | development/web/lib/development_web/live/showcase/color_picker_form_demo.ex:13-17 — 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 — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:7349 — development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:7349-7353 | development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:13987-13991 — before extracting anything, compare `development/web/lib/development_web/live/showcase/headless_baseui_examples.ex` and `development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) development/web/lib/development_web/components/combobox.ex:158 — development/web/lib/development_web/components/combobox.ex:158-162 | development/web/lib/development_web/components/core_components.ex:191-195 — 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 — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×6
  • Duplicated block (7 lines × 2) development/mob/lib/mishka_mob/components/mishka_pills_input.ex:177 — development/mob/lib/mishka_mob/components/mishka_pills_input.ex:177-183 | development/mob/lib/mishka_mob/components/mishka_tags_input.ex:162-168 — 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 — a file they already depend on, or a new one alongside them — 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 `development/mob/lib/mishka_mob/components/mishka_pills_input.ex:177` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) development/web/lib/development_web/components/headless/text_input.ex:77 — development/web/lib/development_web/components/headless/text_input.ex:77-84 | development/web/lib/development_web/components/headless/textarea.ex:63-69 — 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 — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) development/web/lib/development_web/live/showcase/headless_form_demos.ex:859 — development/web/lib/development_web/live/showcase/headless_form_demos.ex:859-865 | development/web/lib/development_web/live/showcase/headless_form_demos.ex:1177-1183 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) development/web/lib/development_web/components/checkbox_card.ex:105 — development/web/lib/development_web/components/checkbox_card.ex:105-111 | development/web/lib/development_web/components/checkbox_field.ex:210-216 — 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 — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) development/web/lib/development_web/live/showcase/catalog.ex:55 — development/web/lib/development_web/live/showcase/catalog.ex:55-61 | development/web/lib/development_web/live/showcase/headless_catalog.ex:24-30 — 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 — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:7317 — development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:7317-7323 | development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:13995-14001 — before extracting anything, compare `development/web/lib/development_web/live/showcase/headless_baseui_examples.ex` and `development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
AC3 · Page structure · Page without a main landmark · ×5
  • Page without a main landmark development/web/lib/development_web/components/layouts/root.html.heex:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark development/web/script/claude-video/shared/templates/intro.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark development/web/script/claude-video/shared/templates/outro.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark development/web/script/claude-video/shared/templates/segment.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark priv/headless/chart.eex:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×5
  • Edited copy of a member (10 corresponding lines) development/web/lib/development_web/components/combobox.ex:167 — development/web/lib/development_web/components/combobox.ex:167-176 | development/web/lib/development_web/components/combobox.ex:394-403 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) development/web/lib/development_web/components/checkbox_card.ex:105 — development/web/lib/development_web/components/checkbox_card.ex:105-114 | development/web/lib/development_web/components/checkbox_field.ex:210-219 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) development/web/lib/development_web/components/drawer.ex:693 — development/web/lib/development_web/components/drawer.ex:693-703 | development/web/lib/development_web/components/drawer.ex:729-738 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) development/web/lib/development_web/live/showcase/catalog.ex:237 — development/web/lib/development_web/live/showcase/catalog.ex:237-246 | development/web/lib/development_web/live/showcase/catalog.ex:523-538 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) development/mob/lib/mishka_mob/components/mishka_select.ex:109 — development/mob/lib/mishka_mob/components/mishka_select.ex:109-118 | development/mob/lib/mishka_mob/components/mishka_toolbar.ex:236-246 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×5
  • Edited copy of a member (13 corresponding lines) development/mob/lib/mishka_mob/components/mishka_accordion.ex:186 — development/mob/lib/mishka_mob/components/mishka_accordion.ex:186-198 | development/mob/lib/mishka_mob/components/mishka_tabs.ex:165-177 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) lib/mishka_chelekom/generators/assets.ex:232 — lib/mishka_chelekom/generators/assets.ex:232-251 | lib/mishka_chelekom/generators/assets.ex:328-340 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) lib/mishka_chelekom/cms_bundle_exporter.ex:1109 — lib/mishka_chelekom/cms_bundle_exporter.ex:1109-1128 | lib/mishka_chelekom/cms_bundle_exporter.ex:1145-1157 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) development/web/lib/development_web/live/showcase/headless_form_demos.ex:869 — development/web/lib/development_web/live/showcase/headless_form_demos.ex:869-882 | development/web/lib/development_web/live/showcase/headless_form_demos.ex:965-977 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) lib/mix/tasks/mishka.ui.gen.headless.ex:173 — lib/mix/tasks/mishka.ui.gen.headless.ex:173-186 | lib/mix/tasks/mishka.ui.gen.mob.ex:213-225 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 11+ corresponding lines) development/web/lib/development_web/components/file_field.ex:102 — development/web/lib/development_web/components/file_field.ex:102-112 | development/web/lib/development_web/components/input_field.ex:89-99 | development/web/lib/development_web/components/native_select.ex:117-127 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) development/web/lib/development_web/components/headless/file_input.ex:69 — development/web/lib/development_web/components/headless/file_input.ex:69-82 | development/web/lib/development_web/components/headless/text_input.ex:77-88 | development/web/lib/development_web/components/headless/textarea.ex:63-73 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) development/mob/lib/mishka_mob/components/mishka_calendar.ex:158 — development/mob/lib/mishka_mob/components/mishka_calendar.ex:158-168 | development/mob/lib/mishka_mob/components/mishka_calendar.ex:248-258 | development/mob/lib/mishka_mob/components/mishka_calendar.ex:552-571 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) development/mob/lib/mishka_mob/components/mishka_menu.ex:111 — development/mob/lib/mishka_mob/components/mishka_menu.ex:111-121 | development/mob/lib/mishka_mob/components/mishka_menu.ex:134-145 | development/mob/lib/mishka_mob/components/mishka_menu.ex:162-172 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) development/web/lib/development_web/live/showcase/examples/pagination.ex:164 — development/web/lib/development_web/live/showcase/examples/pagination.ex:164-175 | development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:5518-5528 | development/web/lib/development_web/live/showcase/preview.ex:1578-1588 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×5
  • Edited copy of a member (7 corresponding lines) lib/mix/tasks/mishka.ui.add.ex:319 — lib/mix/tasks/mishka.ui.add.ex:319-326 | lib/mix/tasks/mishka.ui.add.ex:330-336 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:7366 — development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:7366-7372 | development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:14014-14020 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) development/mob/lib/mishka_mob/components/mishka_fieldset.ex:69 — development/mob/lib/mishka_mob/components/mishka_fieldset.ex:69-75 | development/mob/lib/mishka_mob/components/mishka_scroll_area.ex:92-107 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) development/web/lib/development_web/components/sidebar.ex:214 — development/web/lib/development_web/components/sidebar.ex:214-228 | development/web/lib/development_web/components/tabs.ex:1006-1012 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) lib/mishka_chelekom/cms_bundle/attr_values.ex:277 — lib/mishka_chelekom/cms_bundle/attr_values.ex:277-283 | lib/mishka_chelekom/cms_bundle_exporter.ex:662-668 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×5
  • Edited copy of a member (4 corresponding lines) development/web/lib/development_web/live/showcase/pills_input_form_demo.ex:23 — development/web/lib/development_web/live/showcase/pills_input_form_demo.ex:23-26 | development/web/lib/development_web/live/showcase/tags_input_demo.ex:21-25 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) development/mob/lib/mishka_mob/components/mishka_dialog.ex:330 — development/mob/lib/mishka_mob/components/mishka_dialog.ex:330-333 | development/mob/lib/mishka_mob/components/mishka_drawer.ex:573-576 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) development/web/lib/development_web/components/headless/fab.ex:221 — development/web/lib/development_web/components/headless/fab.ex:221-224 | development/web/lib/development_web/components/tabs.ex:978-982 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) development/mob/lib/mishka_mob/components/mishka_toolbar.ex:805 — development/mob/lib/mishka_mob/components/mishka_toolbar.ex:805-808 | lib/mishka_chelekom/cms_bundle/name.ex:23-27 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) lib/mishka_chelekom/cms_bundle/docs_page.ex:174 — lib/mishka_chelekom/cms_bundle/docs_page.ex:174-177 | lib/mishka_chelekom/cms_bundle/examples.ex:205-208 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (1 corresponding lines) · ×5
  • Edited copy of a member (1 corresponding lines) development/web/lib/development_web/live/showcase/catalog.ex:47 — development/web/lib/development_web/live/showcase/catalog.ex:47-47 | development/web/lib/development_web/live/showcase/headless_catalog.ex:20-20 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) lib/mishka_chelekom/cms_bundle/examples.ex:201 — lib/mishka_chelekom/cms_bundle/examples.ex:201-201 | lib/mishka_chelekom/cms_bundle/showcase.ex:215-216 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) development/mob/lib/mishka_mob/components/mishka_combobox.ex:475 — development/mob/lib/mishka_mob/components/mishka_combobox.ex:475-475 | development/mob/lib/mishka_mob/components/mishka_select.ex:253-257 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) development/mob/lib/mishka_mob/components/mishka_dialog.ex:549 — development/mob/lib/mishka_mob/components/mishka_dialog.ex:549-550 | development/mob/lib/mishka_mob/showcase/components/accordion.ex:367-367 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) development/mob/lib/mishka_mob/showcase/component_screen.ex:95 — development/mob/lib/mishka_mob/showcase/component_screen.ex:95-95 | development/mob/lib/mishka_mob/showcase/gallery_screen.ex:48-48 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
R10 · Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) · ×5
  • Duplicated block with local edits (12 matched lines × 2 locations) priv/assets/js/angle_slider.js:25 — priv/assets/js/angle_slider.js:25 · priv/assets/js/floating_window.js:23 — the two spans are one implementation copied and then locally edited — 79 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (12 matched lines × 2 locations) priv/assets/js/calendar.js:13 — priv/assets/js/calendar.js:13 · priv/assets/js/roving_tabindex.js:11 — the two spans are one implementation copied and then locally edited — 59 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (12 matched lines × 2 locations) priv/assets/js/combobox.js:123 — priv/assets/js/combobox.js:123 · priv/assets/js/combobox.js:302 — the two spans are one implementation copied and then locally edited — 122 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (12 matched lines × 2 locations) priv/assets/js/disclosure.js:98 — priv/assets/js/disclosure.js:98 · priv/assets/js/roving_tabindex.js:60 — the two spans are one implementation copied and then locally edited — 65 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (12 matched lines × 2 locations) priv/assets/js/tabs.js:154 — priv/assets/js/tabs.js:154 · priv/assets/js/toggle_group.js:132 — the two spans are one implementation copied and then locally edited — 94 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×4
  • Edited copy of a member (12 corresponding lines) development/mob/lib/mishka_mob/components/mishka_popover.ex:591 — development/mob/lib/mishka_mob/components/mishka_popover.ex:591-609 | development/mob/lib/mishka_mob/components/mishka_preview_card.ex:336-347 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) development/mob/lib/mishka_mob/components/mishka_alpha_slider.ex:138 — development/mob/lib/mishka_mob/components/mishka_alpha_slider.ex:138-149 | development/mob/lib/mishka_mob/components/mishka_hue_slider.ex:130-142 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) development/mob/lib/mishka_mob/components/mishka_toolbar.ex:264 — development/mob/lib/mishka_mob/components/mishka_toolbar.ex:264-275 | development/mob/lib/mishka_mob/components/mishka_toolbar.ex:297-309 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) development/mob/lib/mishka_mob/components/mishka_spoiler.ex:55 — development/mob/lib/mishka_mob/components/mishka_spoiler.ex:55-66 | development/mob/lib/mishka_mob/components/mishka_tree_select.ex:93-104 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D2 · Cognitive Complexity · mounted (cognitive 16) · ×3
  • mounted (cognitive 16) priv/assets/js/floating_window.js:17 — mounted has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11, boolean chains 3, error handling 1, ternaries 1. Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 4 function items inside it that branch (_onKey, _onDown, _onUp, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
  • mounted (cognitive 16) priv/assets/js/otp.js:24 — mounted has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 10, if/else 5, other 1. Of this number, 8 points are the body's own statements and 8 belong to 9 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
  • mounted (cognitive 16) priv/assets/js/splitter.js:9 — mounted has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8, ternaries 4, boolean chains 3, error handling 1. Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 8 function items inside it that branch (_key, _down, setPos, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×3
  • Edited copy of a member (14 corresponding lines) development/mob/lib/mishka_mob/components/mishka_highlight.ex:164 — development/mob/lib/mishka_mob/components/mishka_highlight.ex:164-181 | development/web/lib/development_web/components/headless/highlight.ex:51-64 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) development/web/lib/development_web/live/showcase/catalog.ex:278 — development/web/lib/development_web/live/showcase/catalog.ex:278-291 | development/web/lib/development_web/live/showcase/catalog.ex:295-313 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) lib/mishka_chelekom/mcp/tools/get_js_hook_info.ex:41 — lib/mishka_chelekom/mcp/tools/get_js_hook_info.ex:41-54 | lib/mishka_chelekom/mcp/tools/get_mix_task_info.ex:42-55 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×3
  • Edited copy of a member (18 corresponding lines) lib/mix/tasks/mishka.assets.deps.ex:74 — lib/mix/tasks/mishka.assets.deps.ex:74-93 | lib/mix/tasks/mishka.ui.export.ex:236-253 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) development/mob/lib/mishka_mob/showcase/components/preview_card.ex:524 — development/mob/lib/mishka_mob/showcase/components/preview_card.ex:524-542 | development/mob/lib/mishka_mob/showcase/components/scroll_area.ex:149-166 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) development/mob/lib/mishka_mob/components/mishka_color_input.ex:76 — development/mob/lib/mishka_mob/components/mishka_color_input.ex:76-93 | development/mob/lib/mishka_mob/components/mishka_json_input.ex:68-91 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×3
  • Edited copy of a member (22 corresponding lines) lib/mishka_chelekom/mcp/resources/list_sizes.ex:45 — lib/mishka_chelekom/mcp/resources/list_sizes.ex:45-73 | lib/mishka_chelekom/mcp/resources/list_spaces.ex:37-58 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) development/mob/lib/mishka_mob/showcase/components/tooltip.ex:443 — development/mob/lib/mishka_mob/showcase/components/tooltip.ex:443-464 | development/mob/lib/mishka_mob/showcase/components/tooltip.ex:472-493 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) development/mob/lib/mishka_mob/components/mishka_floating_indicator.ex:59 — development/mob/lib/mishka_mob/components/mishka_floating_indicator.ex:59-80 | development/mob/lib/mishka_mob/components/mishka_navigation_menu.ex:63-85 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 1+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 1+ corresponding lines) development/web/lib/development_web/live/showcase/field_form_demo.ex:283 — development/web/lib/development_web/live/showcase/field_form_demo.ex:283-285 | development/web/lib/development_web/live/showcase/file_field_form_demo.ex:58-58 | development/web/lib/development_web/live/showcase/headless_form_demos.ex:8-8 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 1+ corresponding lines) development/mob/lib/mishka_mob/showcase.ex:291 — development/mob/lib/mishka_mob/showcase.ex:291-293 | development/web/lib/development_web/live/showcase/catalog.ex:67-69 | development/web/lib/development_web/live/showcase/headless_catalog.ex:34-34 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 1+ corresponding lines) development/mob/lib/mishka_mob/showcase/components/collapsible.ex:244 — development/mob/lib/mishka_mob/showcase/components/collapsible.ex:244-244 | development/mob/lib/mishka_mob/showcase/components/spoiler.ex:165-166 | development/mob/lib/mishka_mob/showcase/components/tabs.ex:298-298 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (8–10 lines × 2) · ×3
  • Duplicated block (8–10 lines × 2) development/mob/lib/mishka_mob/components/mishka_combobox.ex:436 — development/mob/lib/mishka_mob/components/mishka_combobox.ex:436-443 | development/mob/lib/mishka_mob/components/mishka_select.ex:286-295 — 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 — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (8–10 lines × 2) development/mob/lib/mishka_mob/list_screen.ex:225 — development/mob/lib/mishka_mob/list_screen.ex:225-232 | development/mob/lib/mishka_mob/list_screen.ex:243-252 — both copies are in the same file, so extract the block into one function there and call it from each site — 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 `development/mob/lib/mishka_mob/list_screen.ex:225` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8–10 lines × 2) lib/mix/tasks/mishka.ui.gen.headless.components.ex:60 — lib/mix/tasks/mishka.ui.gen.headless.components.ex:60-69 | lib/mix/tasks/mishka.ui.gen.mob.components.ex:66-73 — 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 — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×3
  • Duplicated block (8 lines × 2) development/web/lib/development_web/components/file_field.ex:104 — development/web/lib/development_web/components/file_field.ex:104-111 | development/web/lib/development_web/components/native_select.ex:119-126 — 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 — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (8 lines × 2) development/web/lib/development_web/live/showcase/headless_form_demos.ex:584 — development/web/lib/development_web/live/showcase/headless_form_demos.ex:584-591 | development/web/lib/development_web/live/showcase/headless_form_demos.ex:676-683 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) development/web/lib/development_web/live/showcase/headless_form_demos.ex:595 — development/web/lib/development_web/live/showcase/headless_form_demos.ex:595-602 | development/web/lib/development_web/live/showcase/headless_form_demos.ex:687-694 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×3
  • Outbound HTTP without resilience development/web/check_http.exs:31 — `:httpc.request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience lib/mix/tasks/mishka.ui.add.ex:210 — `Req.new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience lib/mix/tasks/mishka.ui.add.ex:215 — `Req.get!(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
AC3 · Page structure · Heading level jumps from h1 to h4 · ×2
  • Heading level jumps from h1 to h4 development/web/lib/development_web/live/showcase/kit_demo.ex:580 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h1 to h4 development/web/lib/development_web/live/showcase/preview.ex:505 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC4 · Keyboard semantics · Anchor without href · ×2
  • Anchor without href priv/headless/anchor.eex:5 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href priv/headless/card.eex:16 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
D1 · Cyclomatic Complexity · positionPopup (cyclomatic 27) · ×2
  • positionPopup (cyclomatic 27) priv/assets/js/popover.js:195 — positionPopup has cyclomatic complexity 27 (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.
  • positionPopup (cyclomatic 27) priv/assets/js/preview_card.js:147 — positionPopup has cyclomatic complexity 27 (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.
D1 · Cyclomatic Complexity · mounted (cyclomatic 21) · ×2
  • mounted (cyclomatic 21) priv/assets/js/editor_tiptap.js:106 — mounted has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to 8 function items inside it that branch (_onToolbar, a function literal at line 186, _onSurfaceDown, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
  • mounted (cyclomatic 21) priv/assets/js/number_field.js:35 — mounted has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to 7 function items inside it that branch. 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.
D1 · Cyclomatic Complexity · mounted (cyclomatic 20) · ×2
  • mounted (cyclomatic 20) priv/assets/js/drawer.js:115 — mounted has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to 5 function literals inside it that branch. 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.
  • mounted (cyclomatic 20) priv/assets/js/popover.js:52 — mounted has cyclomatic complexity 20 (threshold 15). Of this number, 16 points are the body's own statements and 4 belong to 11 function items inside it that branch. 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.
D1 · Cyclomatic Complexity · mounted (cyclomatic 17) · ×2
  • mounted (cyclomatic 17) priv/assets/js/otp.js:24 — mounted has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 belong to 9 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
  • mounted (cyclomatic 17) priv/assets/js/splitter.js:9 — mounted has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 8 function items inside it that branch (_key, _down, setPos, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · mounted (cyclomatic 16) · ×2
  • mounted (cyclomatic 16) priv/assets/js/floating_window.js:17 — mounted has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 4 function items inside it that branch (_onKey, _onDown, _onUp, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
  • mounted (cyclomatic 16) priv/assets/js/menu.js:19 — mounted has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to 11 function items inside it that branch. 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.
D2 · Cognitive Complexity · positionPopup (cognitive 33) · ×2
  • positionPopup (cognitive 33) priv/assets/js/popover.js:195 — positionPopup has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (15 pts), ternaries 6 (12 pts), boolean chains 6 (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.
  • positionPopup (cognitive 33) priv/assets/js/preview_card.js:147 — positionPopup has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (15 pts), ternaries 6 (12 pts), boolean chains 6 (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.
D2 · Cognitive Complexity · mounted (cognitive 22) · ×2
  • mounted (cognitive 22) priv/assets/js/drawer.js:115 — mounted has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 10 (nesting depth added 3). Of this number, 17 points are the body's own statements and 5 belong to 5 function literals inside it that branch. 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.
  • mounted (cognitive 22) priv/assets/js/popover.js:52 — mounted has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 10, if/else 8 (10 pts), ternaries 1 (2 pts) (nesting depth added 3). Of this number, 16 points are the body's own statements and 6 belong to 11 function items inside it that branch. 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.
D2 · Cognitive Complexity · mounted (cognitive 20) · ×2
  • mounted (cognitive 20) priv/assets/js/editor_tiptap.js:106 — mounted has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 11, if/else 6, other 2, ternaries 1. Most of this is not in the body itself: 9 of the 20 points are its own statements and the rest belongs to 8 function items inside it that branch (_onToolbar, a function literal at line 186, _onSurfaceDown, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
  • mounted (cognitive 20) priv/assets/js/number_field.js:35 — mounted has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 5, if/else 5, other 5, ternaries 4, error handling 1. Of this number, 18 points are the body's own statements and 2 belong to 7 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. 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.
D3 · God Classes · MethodTooLong · ×2
  • MethodTooLong: MobBridgeKt.MobTextField development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:3562 — MethodTooLong — MobTextField runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× 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 — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: MobBridgeKt.drawCanvasOp development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:4460 — MethodTooLong — drawCanvasOp runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× 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 — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (4 members, 50+ identical tokens) development/mob/lib/mishka_mob/components/mishka_alpha_slider.ex:180 — development/mob/lib/mishka_mob/components/mishka_alpha_slider.ex:180-188 | development/mob/lib/mishka_mob/components/mishka_hue_slider.ex:175-183 | development/mob/lib/mishka_mob/components/mishka_progress.ex:407-415 | development/mob/lib/mishka_mob/components/mishka_slider.ex:279-287 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:3225 — development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:3225-3315 | development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:3380-3470 | development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:8455-8545 | development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:8611-8701 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×2
  • Edited copy of a member (23 corresponding lines) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:1051 — development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:1051-1082 | development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:1087-1109 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) lib/mix/tasks/mishka.ui.gen.components.ex:38 — lib/mix/tasks/mishka.ui.gen.components.ex:38-71 | lib/mix/tasks/mishka.ui.uninstall.ex:52-74 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×2
  • Edited copy of a member (11 corresponding lines) development/web/lib/development_web/live/showcase/example_source.ex:42 — development/web/lib/development_web/live/showcase/example_source.ex:42-54 | development/web/lib/development_web/live/showcase/json_meta.ex:81-91 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) development/mob/lib/mishka_mob/components/mishka_pills_input.ex:173 — development/mob/lib/mishka_mob/components/mishka_pills_input.ex:173-183 | development/mob/lib/mishka_mob/components/mishka_tags_input.ex:158-168 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 17+ corresponding lines) development/mob/lib/mishka_mob/components/mishka_burger.ex:48 — development/mob/lib/mishka_mob/components/mishka_burger.ex:48-64 | development/mob/lib/mishka_mob/components/mishka_checkbox.ex:82-100 | development/mob/lib/mishka_mob/components/mishka_radio.ex:65-93 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 17+ corresponding lines) lib/mix/tasks/mishka.ui.gen.component.ex:133 — lib/mix/tasks/mishka.ui.gen.component.ex:133-151 | lib/mix/tasks/mishka.ui.gen.headless.ex:94-110 | lib/mix/tasks/mishka.ui.gen.mob.ex:158-174 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×2
  • Edited copy of a member (9 corresponding lines) development/web/lib/development_web/components/headless/autocomplete.ex:217 — development/web/lib/development_web/components/headless/autocomplete.ex:217-228 | development/web/lib/development_web/components/headless/combobox.ex:300-308 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) development/mob/lib/mishka_mob/home_screen.ex:133 — development/mob/lib/mishka_mob/home_screen.ex:133-145 | development/mob/lib/mishka_mob/showcase/components/popover.ex:542-550 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×2
  • Edited copy of a member (19 corresponding lines) development/mob/lib/mishka_mob/components/mishka_combobox.ex:342 — development/mob/lib/mishka_mob/components/mishka_combobox.ex:342-361 | development/mob/lib/mishka_mob/components/mishka_pills_input.ex:213-231 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) development/mob/lib/mishka_mob/components/mishka_collapsible.ex:72 — development/mob/lib/mishka_mob/components/mishka_collapsible.ex:72-90 | development/mob/lib/mishka_mob/components/mishka_toggle.ex:153-177 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×2
  • Edited copy of a member (15 corresponding lines) lib/mishka_chelekom/generators/import_macro.ex:137 — lib/mishka_chelekom/generators/import_macro.ex:137-151 | lib/mix/tasks/mishka.ui.uninstall.ex:1016-1030 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) lib/mix/tasks/mishka.ui.gen.headless.ex:43 — lib/mix/tasks/mishka.ui.gen.headless.ex:43-57 | lib/mix/tasks/mishka.ui.gen.mob.ex:88-115 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×2
  • Edited copy of a member (5 corresponding lines) development/web/lib/development_web/live/showcase/pills_input_form_demo.ex:14 — development/web/lib/development_web/live/showcase/pills_input_form_demo.ex:14-18 | development/web/lib/development_web/live/showcase/tags_input_demo.ex:12-16 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) development/mob/lib/mishka_mob/components/mishka_progress.ex:433 — development/mob/lib/mishka_mob/components/mishka_progress.ex:433-437 | development/mob/lib/mishka_mob/components/mishka_slider.ex:301-305 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×2
  • Edited copy of a member (3 corresponding lines) development/web/lib/development_web/components/headless/select.ex:290 — development/web/lib/development_web/components/headless/select.ex:290-292 | development/web/lib/development_web/components/headless/toolbar.ex:201-205 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) development/mob/lib/mishka_mob/showcase/components/color_input.ex:196 — development/mob/lib/mishka_mob/showcase/components/color_input.ex:196-198 | development/mob/lib/mishka_mob/showcase/components/color_picker.ex:145-147 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 3+ corresponding lines) development/mob/lib/mishka_mob/components/mishka_card.ex:130 — development/mob/lib/mishka_mob/components/mishka_card.ex:130-132 | development/mob/lib/mishka_mob/components/mishka_empty_state.ex:121-123 | development/mob/lib/mishka_mob/components/mishka_toast.ex:136-138 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 3+ corresponding lines) development/mob/lib/mishka_mob/showcase/components/autocomplete.ex:292 — development/mob/lib/mishka_mob/showcase/components/autocomplete.ex:292-297 | development/mob/lib/mishka_mob/showcase/components/checkbox.ex:183-185 | development/mob/lib/mishka_mob/showcase/components/chip.ex:174-176 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×2
  • Duplicated block (12 lines × 3) lib/mix/tasks/mishka.ui.gen.component.ex:103 — lib/mix/tasks/mishka.ui.gen.component.ex:103-114 | lib/mix/tasks/mishka.ui.gen.headless.ex:63-74 | lib/mix/tasks/mishka.ui.gen.mob.ex:124-135 — 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 — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `lib/mix/tasks/mishka.ui.gen.headless.ex:77` calls `validate_lib` and `lib/mix/tasks/mishka.ui.gen.component.ex:117` does not — 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.
  • Duplicated block (12 lines × 3) development/mob/lib/mishka_mob/dice_screen.ex:193 — development/mob/lib/mishka_mob/dice_screen.ex:193-204 | development/mob/lib/mishka_mob/showcase/kit.ex:110-121 | development/mob/lib/mishka_mob/text_screen.ex:127-138 — before extracting anything, compare `development/mob/lib/mishka_mob/dice_screen.ex` and `development/mob/lib/mishka_mob/text_screen.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×2
  • Duplicated block (9 lines × 2) development/mob/lib/mishka_mob/dice_screen.ex:98 — development/mob/lib/mishka_mob/dice_screen.ex:98-106 | development/mob/lib/mishka_mob/text_screen.ex:50-58 — before extracting anything, compare `development/mob/lib/mishka_mob/dice_screen.ex` and `development/mob/lib/mishka_mob/text_screen.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/dice_screen.ex:98` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) lib/mix/tasks/mishka.ui.gen.components.ex:94 — lib/mix/tasks/mishka.ui.gen.components.ex:94-102 | lib/mix/tasks/mishka.ui.gen.headless.components.ex:76-84 — 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 — a file they already depend on, or a new one alongside them — 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 `lib/mix/tasks/mishka.ui.gen.components.ex:94` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×2
  • Duplicated block (5 lines × 3) development/web/lib/development_web/components/file_field.ex:104 — development/web/lib/development_web/components/file_field.ex:104-108 | development/web/lib/development_web/components/input_field.ex:91-95 | development/web/lib/development_web/components/native_select.ex:119-123 — 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 — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `development/web/lib/development_web/components/file_field.ex:104` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 3) development/mob/lib/mishka_mob/components/mishka_card.ex:174 — development/mob/lib/mishka_mob/components/mishka_card.ex:174-178 | development/mob/lib/mishka_mob/components/mishka_dock.ex:80-84 | development/mob/lib/mishka_mob/components/mishka_list_item.ex:89-93 — 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 — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `development/mob/lib/mishka_mob/components/mishka_dock.ex:89` calls `bar_props` and `development/mob/lib/mishka_mob/components/mishka_card.ex:179` does not — 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.
D4 · Code Duplication · Duplicated block (6 lines × 47) · ×2
  • Duplicated block (6 lines × 47) development/web/lib/development_web/live/showcase/examples/accordion.ex:16 — development/web/lib/development_web/live/showcase/examples/accordion.ex:16-21 | development/web/lib/development_web/live/showcase/examples/alert.ex:16-21 | development/web/lib/development_web/live/showcase/examples/avatar.ex:16-21 | development/web/lib/development_web/live/showcase/examples/badge.ex:16-21 | development/web/lib/development_web/live/showcase/examples/banner.ex:20-25 | development/web/lib/development_web/live/showcase/examples/blockquote.ex:16-21 | development/web/lib/development_web/live/showcase/examples/breadcrumb.ex:16-21 | development/web/lib/development_web/live/showcase/examples/card.ex:16-21 | development/web/lib/development_web/live/showcase/examples/carousel.ex:19-24 | development/web/lib/development_web/live/showcase/examples/chat.ex:16-21 | development/web/lib/development_web/live/showcase/examples/checkbox_card.ex:16-21 | development/web/lib/development_web/live/showcase/examples/clipboard.ex:16-21 | development/web/lib/development_web/live/showcase/examples/combobox.ex:16-21 | development/web/lib/development_web/live/showcase/examples/device_mockup.ex:19-24 | development/web/lib/development_web/live/showcase/examples/divider.ex:16-21 | development/web/lib/development_web/live/showcase/examples/dock.ex:16-21 | development/web/lib/development_web/live/showcase/examples/drawer.ex:19-24 | development/web/lib/development_web/live/showcase/examples/dropdown.ex:16-21 | development/web/lib/development_web/live/showcase/examples/file_field.ex:22-27 | development/web/lib/development_web/live/showcase/examples/footer.ex:22-27 | development/web/lib/development_web/live/showcase/examples/gallery.ex:20-25 | development/web/lib/development_web/live/showcase/examples/jumbotron.ex:16-21 | development/web/lib/development_web/live/showcase/examples/keyboard.ex:16-21 | development/web/lib/development_web/live/showcase/examples/layout.ex:17-22 | development/web/lib/development_web/live/showcase/examples/list.ex:16-21 | development/web/lib/development_web/live/showcase/examples/mega_menu.ex:16-21 | development/web/lib/development_web/live/showcase/examples/modal.ex:21-26 | development/web/lib/development_web/live/showcase/examples/navbar.ex:16-21 | development/web/lib/development_web/live/showcase/examples/pagination.ex:20-25 | development/web/lib/development_web/live/showcase/examples/popover.ex:16-21 | development/web/lib/development_web/live/showcase/examples/progress.ex:16-21 | development/web/lib/development_web/live/showcase/examples/radio_card.ex:16-21 | development/web/lib/development_web/live/showcase/examples/rating.ex:16-21 | development/web/lib/development_web/live/showcase/examples/scroll_area.ex:16-21 | development/web/lib/development_web/live/showcase/examples/sidebar.ex:21-26 | development/web/lib/development_web/live/showcase/examples/skeleton.ex:16-21 | development/web/lib/development_web/live/showcase/examples/speed_dial.ex:19-24 | development/web/lib/development_web/live/showcase/examples/stat.ex:16-21 | development/web/lib/development_web/live/showcase/examples/stepper.ex:16-21 | development/web/lib/development_web/live/showcase/examples/table.ex:16-21 | development/web/lib/development_web/live/showcase/examples/table_content.ex:19-24 | development/web/lib/development_web/live/showcase/examples/tabs.ex:16-21 | development/web/lib/development_web/live/showcase/examples/text_field.ex:16-21 | development/web/lib/development_web/live/showcase/examples/timeline.ex:21-26 | development/web/lib/development_web/live/showcase/examples/toast.ex:21-26 | development/web/lib/development_web/live/showcase/examples/tooltip.ex:16-21 | development/web/lib/development_web/live/showcase/examples/video.ex:26-31 — 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 — a file they already depend on, or a new one alongside them — and call it from all 47 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `development/web/lib/development_web/live/showcase/examples/accordion.ex:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 47) development/web/lib/development_web/live/showcase/examples/accordion.ex:20 — development/web/lib/development_web/live/showcase/examples/accordion.ex:20-25 | development/web/lib/development_web/live/showcase/examples/alert.ex:20-25 | development/web/lib/development_web/live/showcase/examples/avatar.ex:21-26 | development/web/lib/development_web/live/showcase/examples/badge.ex:20-25 | development/web/lib/development_web/live/showcase/examples/banner.ex:23-28 | development/web/lib/development_web/live/showcase/examples/blockquote.ex:21-26 | development/web/lib/development_web/live/showcase/examples/breadcrumb.ex:19-24 | development/web/lib/development_web/live/showcase/examples/card.ex:20-25 | development/web/lib/development_web/live/showcase/examples/carousel.ex:22-27 | development/web/lib/development_web/live/showcase/examples/chat.ex:21-26 | development/web/lib/development_web/live/showcase/examples/checkbox_card.ex:19-24 | development/web/lib/development_web/live/showcase/examples/clipboard.ex:19-24 | development/web/lib/development_web/live/showcase/examples/combobox.ex:21-26 | development/web/lib/development_web/live/showcase/examples/device_mockup.ex:23-28 | development/web/lib/development_web/live/showcase/examples/divider.ex:20-25 | development/web/lib/development_web/live/showcase/examples/dock.ex:20-25 | development/web/lib/development_web/live/showcase/examples/drawer.ex:23-28 | development/web/lib/development_web/live/showcase/examples/dropdown.ex:20-25 | development/web/lib/development_web/live/showcase/examples/file_field.ex:25-30 | development/web/lib/development_web/live/showcase/examples/footer.ex:25-30 | development/web/lib/development_web/live/showcase/examples/gallery.ex:24-29 | development/web/lib/development_web/live/showcase/examples/jumbotron.ex:19-24 | development/web/lib/development_web/live/showcase/examples/keyboard.ex:22-27 | development/web/lib/development_web/live/showcase/examples/layout.ex:21-26 | development/web/lib/development_web/live/showcase/examples/list.ex:20-25 | development/web/lib/development_web/live/showcase/examples/mega_menu.ex:20-25 | development/web/lib/development_web/live/showcase/examples/modal.ex:23-28 | development/web/lib/development_web/live/showcase/examples/navbar.ex:19-24 | development/web/lib/development_web/live/showcase/examples/pagination.ex:36-41 | development/web/lib/development_web/live/showcase/examples/popover.ex:20-25 | development/web/lib/development_web/live/showcase/examples/progress.ex:19-24 | development/web/lib/development_web/live/showcase/examples/radio_card.ex:20-25 | development/web/lib/development_web/live/showcase/examples/rating.ex:18-23 | development/web/lib/development_web/live/showcase/examples/scroll_area.ex:19-24 | development/web/lib/development_web/live/showcase/examples/sidebar.ex:24-29 | development/web/lib/development_web/live/showcase/examples/skeleton.ex:19-24 | development/web/lib/development_web/live/showcase/examples/speed_dial.ex:21-26 | development/web/lib/development_web/live/showcase/examples/stat.ex:20-25 | development/web/lib/development_web/live/showcase/examples/stepper.ex:19-24 | development/web/lib/development_web/live/showcase/examples/table.ex:19-24 | development/web/lib/development_web/live/showcase/examples/table_content.ex:23-28 | development/web/lib/development_web/live/showcase/examples/tabs.ex:20-25 | development/web/lib/development_web/live/showcase/examples/text_field.ex:18-23 | development/web/lib/development_web/live/showcase/examples/timeline.ex:25-30 | development/web/lib/development_web/live/showcase/examples/toast.ex:24-29 | development/web/lib/development_web/live/showcase/examples/tooltip.ex:20-25 | development/web/lib/development_web/live/showcase/examples/video.ex:30-35 — 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 — a file they already depend on, or a new one alongside them — and call it from all 47 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `development/web/lib/development_web/live/showcase/examples/accordion.ex:20` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `development/web/lib/development_web/live/showcase/examples/video.ex:39` calls `assign` and `development/web/lib/development_web/live/showcase/examples/accordion.ex:29` does not — 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.
R10 · Code Duplication · Duplicated block (31 lines × 2 locations) · ×2
  • Duplicated block (31 lines × 2 locations) priv/assets/js/context_menu.js:205 — priv/assets/js/context_menu.js:205 · priv/assets/js/menu.js:221 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (31 lines × 2 locations) priv/assets/js/focus_trap.js:54 — priv/assets/js/focus_trap.js:54 · priv/assets/js/popover.js:24 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block (26 lines × 2 locations) · ×2
  • Duplicated block (26 lines × 2 locations) priv/assets/js/context_menu.js:248 — priv/assets/js/context_menu.js:248 · priv/assets/js/menu.js:259 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (26 lines × 2 locations) priv/assets/js/drawer.js:75 — priv/assets/js/drawer.js:75 · priv/assets/js/popover.js:15 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (24 lines × 2 locations) · ×2
  • Duplicated block (24 lines × 2 locations) priv/assets/js/context_menu.js:401 — priv/assets/js/context_menu.js:401 · priv/assets/js/menu.js:422 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (24 lines × 2 locations) priv/assets/js/scrollArea.js:135 — priv/assets/js/scrollArea.js:135 · priv/assets/js/scrollArea.js:164 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (20 lines × 2 locations) · ×2
  • Duplicated block (20 lines × 2 locations) priv/assets/js/floating.js:346 — priv/assets/js/floating.js:346 · priv/assets/js/floating.js:367 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (20 lines × 2 locations) priv/assets/js/focus_trap.js:232 — priv/assets/js/focus_trap.js:232 · priv/assets/js/popover.js:276 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (16 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (16 matched lines × 2 locations) priv/assets/js/roving_tabindex.js:53 — priv/assets/js/roving_tabindex.js:53 · priv/assets/js/tabs.js:153 — the two spans are one implementation copied and then locally edited — 132 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (16 matched lines × 2 locations) priv/assets/js/select.js:187 — priv/assets/js/select.js:187 · priv/assets/js/toggle_group.js:129 — the two spans are one implementation copied and then locally edited — 121 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×2
  • Duplicated block (14 lines × 2 locations) priv/assets/js/chart_billboard.js:323 — priv/assets/js/chart_billboard.js:323 · priv/assets/js/chart_echarts.js:268 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (14 lines × 2 locations) priv/assets/js/context_menu.js:283 — priv/assets/js/context_menu.js:283 · priv/assets/js/menu.js:302 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (14 matched lines × 2 locations) priv/assets/js/clipboard.js:354 — priv/assets/js/clipboard.js:354 · priv/assets/js/clipboard.js:438 — the two spans are one implementation copied and then locally edited — 88 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (14 matched lines × 2 locations) priv/assets/js/menubar.js:163 — priv/assets/js/menubar.js:163 · priv/assets/js/toggle_group.js:132 — the two spans are one implementation copied and then locally edited — 94 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (12 lines × 2 locations) · ×2
  • Duplicated block (12 lines × 2 locations) priv/assets/js/combobox.js:420 — priv/assets/js/combobox.js:420 · priv/assets/js/combobox.js:653 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (12 lines × 2 locations) priv/assets/js/select.js:61 — priv/assets/js/select.js:61 · priv/assets/js/toggle_group.js:44 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R2 · Cyclomatic Complexity · Complex function positionPopup (cyclomatic 27, cognitive 33) · ×2
  • Complex function positionPopup (cyclomatic 27, cognitive 33) priv/assets/js/popover.js:195 — positionPopup has cyclomatic complexity 27 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function positionPopup (cyclomatic 27, cognitive 33) priv/assets/js/preview_card.js:147 — positionPopup has cyclomatic complexity 27 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
AC1 · Text alternatives · <video> without a captions track · ×1
  • <video> without a captions track priv/components/video.eex:114 — Video with no captions <track> offers no captions. Add a <track kind="captions"> pointing at a WebVTT file for this video (or confirm captions are provided another way).
AC3 · Page structure · Data table has no header cells · ×1
  • Data table has no header cells development/web/lib/development_web/live/showcase/headless_preview.ex:1722 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (2.1 · ×1
  • Low contrast Tailwind colour pair (2.1:1) development/web/lib/development_web/live/showcase/headless_kit_demo.ex:122 — This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
C1 · Data Protection · No data-protection/encryption · ×1
  • No data-protection/encryption development/web/lib/development_web/live/showcase/field_form_demo.ex:16 — No encryption usage (Cloak.Ecto encrypted field types, a Cloak vault, Plug.Crypto's message encryptor, :crypto ciphers that encrypt, libsodium boxes) was found, and this repository persists personal data in the model cited here — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
C2 · Access Controls · No authorization · ×1
  • No authorization lib/mishka_chelekom/mcp/supervisor.ex:58 — This repository serves requests — a server ({Bandit,) (lib/mishka_chelekom/mcp/supervisor.ex:58) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected.
D1 · Cyclomatic Complexity · updatePosition (cyclomatic 41) · ×1
  • updatePosition (cyclomatic 41) priv/assets/js/floating.js:450 — updatePosition has cyclomatic complexity 41 (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.
D1 · Cyclomatic Complexity · MobAnchoredPositionProvider.calculatePosition (cyclomatic 35) · ×1
  • MobAnchoredPositionProvider.calculatePosition (cyclomatic 35) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:3347 — MobAnchoredPositionProvider.calculatePosition has cyclomatic complexity 35 (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.
D1 · Cyclomatic Complexity · MobBridgeKt.RenderNodeInner (cyclomatic 35) · ×1
  • MobBridgeKt.RenderNodeInner (cyclomatic 35) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:3038 — MobBridgeKt.RenderNodeInner has cyclomatic complexity 35 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · positionPopup (cyclomatic 33) · ×1
  • positionPopup (cyclomatic 33) priv/assets/js/tooltip.js:187 — positionPopup has cyclomatic complexity 33 (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.
D1 · Cyclomatic Complexity · MobBridgeKt.MobTextField (cyclomatic 31) · ×1
  • MobBridgeKt.MobTextField (cyclomatic 31) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:3562 — MobBridgeKt.MobTextField has cyclomatic complexity 31 (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.
D1 · Cyclomatic Complexity · handleKeyDown (cyclomatic 31) · ×1
  • handleKeyDown (cyclomatic 31) priv/assets/js/tree.js:413 — handleKeyDown has cyclomatic complexity 31 (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.
D1 · Cyclomatic Complexity · activate (cyclomatic 30) · ×1
  • activate (cyclomatic 30) priv/assets/js/navigation_menu.js:102 — activate has cyclomatic complexity 30 (threshold 15). Of this number, 24 points are the body's own statements and 6 belong to 6 function literals inside it that branch. 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.
D1 · Cyclomatic Complexity · handleKeydown (cyclomatic 28) · ×1
  • handleKeydown (cyclomatic 28) priv/assets/js/menu.js:387 — handleKeydown has cyclomatic complexity 28 (threshold 15). Of this number, 26 points are the body's own statements and 2 belong to 3 function items inside it that branch. 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.
D1 · Cyclomatic Complexity · handleKeyDown (cyclomatic 27) · ×1
  • handleKeyDown (cyclomatic 27) priv/assets/js/combobox.js:564 — handleKeyDown has cyclomatic complexity 27 (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.
D1 · Cyclomatic Complexity · handleKeydown (cyclomatic 26) · ×1
  • handleKeydown (cyclomatic 26) priv/assets/js/context_menu.js:369 — handleKeydown has cyclomatic complexity 26 (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.
D1 · Cyclomatic Complexity · bindSwipeArea (cyclomatic 25) · ×1
  • bindSwipeArea (cyclomatic 25) priv/assets/js/drawer.js:550 — bindSwipeArea has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 4 of the 25 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 567, release, a function literal at line 554, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · applyTheme (cyclomatic 24) · ×1
  • applyTheme (cyclomatic 24) priv/assets/js/chart_chartjs.js:138 — applyTheme has cyclomatic complexity 24 (threshold 15). Of this number, 13 points are the body's own statements and 11 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · onKeyDown (cyclomatic 24) · ×1
  • onKeyDown (cyclomatic 24) priv/assets/js/otp.js:203 — onKeyDown has cyclomatic complexity 24 (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.
D1 · Cyclomatic Complexity · parse (cyclomatic 23) · ×1
  • parse (cyclomatic 23) priv/assets/js/number_field.js:119 — parse has cyclomatic complexity 23 (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.
D1 · Cyclomatic Complexity · MobBridgeKt.drawCanvasOp (cyclomatic 21) · ×1
  • MobBridgeKt.drawCanvasOp (cyclomatic 21) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:4460 — MobBridgeKt.drawCanvasOp has cyclomatic complexity 21 (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. This is NOT this file's highest cyclomatic complexity: MobBridgeKt.materialIconFor (cyclomatic 30) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · positionPopup (cyclomatic 21) · ×1
  • positionPopup (cyclomatic 21) priv/assets/js/menu.js:166 — positionPopup 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.
D1 · Cyclomatic Complexity · MishkaCalendar.row_node (cyclomatic 20) · ×1
  • MishkaCalendar.row_node (cyclomatic 20) development/mob/lib/mishka_mob/components/mishka_calendar.ex:419 — MishkaCalendar.row_node has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · MobBridge.vendor_usb_open (cyclomatic 20) · ×1
  • MobBridge.vendor_usb_open (cyclomatic 20) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:2735 — MobBridge.vendor_usb_open has cyclomatic complexity 20 (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. This is NOT this file's highest cyclomatic complexity: MobBridgeKt.materialIconFor (cyclomatic 30) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · onKey (cyclomatic 20) · ×1
  • onKey (cyclomatic 20) priv/assets/js/toolbar.js:70 — onKey has cyclomatic complexity 20 (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.
D1 · Cyclomatic Complexity · MishkaCalendar.lane_node (cyclomatic 18) · ×1
  • MishkaCalendar.lane_node (cyclomatic 18) development/mob/lib/mishka_mob/components/mishka_calendar.ex:177 — MishkaCalendar.lane_node has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · MishkaCalendar.week_block (cyclomatic 18) · ×1
  • MishkaCalendar.week_block (cyclomatic 18) development/mob/lib/mishka_mob/components/mishka_calendar.ex:268 — MishkaCalendar.week_block has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · runBeat (cyclomatic 18) · ×1
  • runBeat (cyclomatic 18) development/web/script/claude-video/shared/capture.mjs:89 — runBeat has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to 4 function literals inside it that branch. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · select (cyclomatic 17) · ×1
  • select (cyclomatic 17) priv/assets/js/tabs.js:78 — select has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to 5 function literals inside it that branch. 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.
D1 · Cyclomatic Complexity · MobBridgeKt.packGpuUniforms (cyclomatic 16) · ×1
  • MobBridgeKt.packGpuUniforms (cyclomatic 16) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:4751 — MobBridgeKt.packGpuUniforms has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions. This is NOT this file's highest cyclomatic complexity: MobBridgeKt.materialIconFor (cyclomatic 30) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · assemble.main (cyclomatic 16) · ×1
  • assemble.main (cyclomatic 16) development/web/script/claude-video/shared/assemble.mjs:161 — assemble.main 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.
D1 · Cyclomatic Complexity · moveSwipe (cyclomatic 16) · ×1
  • moveSwipe (cyclomatic 16) priv/assets/js/drawer.js:407 — moveSwipe 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.
D15 · Churn × Complexity Hotspots · Hotspot · ×1
  • Hotspot: priv/assets/js/floating.js priv/assets/js/floating.js:450 — priv/assets/js/floating.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in updatePosition at line 450. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 08:31:12 +01:00' --until='2026-11-15 08:31:12 +01:00' --full-history --no-merges -- priv/assets/js/floating.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D2 · Cognitive Complexity · MobAnchoredPositionProvider.calculatePosition (cognitive 57) · ×1
  • MobAnchoredPositionProvider.calculatePosition (cognitive 57) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:3347 — MobAnchoredPositionProvider.calculatePosition has cognitive complexity 57 (threshold 15). Drivers by points: if/else 27 (37 pts), boolean chains 10, match/switch 5 (10 pts) (nesting depth added 15). 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. This file is where this pass's cognitive complexity CONCENTRATES: development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt holds 12 of the 50 methods over the threshold — including the worst — and 139 of the 505 points over it (28%), 4× the next-largest file (priv/assets/js/combobox.js at 35). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · updatePosition (cognitive 45) · ×1
  • updatePosition (cognitive 45) priv/assets/js/floating.js:450 — updatePosition has cognitive complexity 45 (threshold 15). Drivers by points: if/else 21 (28 pts), boolean chains 13, ternaries 2 (4 pts) (nesting depth added 9). 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.
D2 · Cognitive Complexity · activate (cognitive 43) · ×1
  • activate (cognitive 43) priv/assets/js/navigation_menu.js:102 — activate has cognitive complexity 43 (threshold 15). Drivers by points: if/else 16 (19 pts), ternaries 5 (13 pts), boolean chains 11 (nesting depth added 11). Of this number, 35 points are the body's own statements and 8 belong to 6 function literals inside it that branch. 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.
D2 · Cognitive Complexity · positionPopup (cognitive 41) · ×1
  • positionPopup (cognitive 41) priv/assets/js/tooltip.js:187 — positionPopup has cognitive complexity 41 (threshold 15). Drivers by points: if/else 16 (20 pts), ternaries 6 (12 pts), boolean chains 9 (nesting depth added 10). 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.
D2 · Cognitive Complexity · MobBridgeKt.MobTextField (cognitive 39) · ×1
  • MobBridgeKt.MobTextField (cognitive 39) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:3562 — MobBridgeKt.MobTextField has cognitive complexity 39 (threshold 15). Drivers by points: if/else 29 (33 pts), match/switch 3 (4 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — 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, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This file is where this pass's cognitive complexity CONCENTRATES: development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt holds 12 of the 50 methods over the threshold — including the worst — and 139 of the 505 points over it (28%), 4× the next-largest file (priv/assets/js/combobox.js at 35). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · handleKeyDown (cognitive 38) · ×1
  • handleKeyDown (cognitive 38) priv/assets/js/combobox.js:564 — handleKeyDown has cognitive complexity 38 (threshold 15). Drivers by points: if/else 17 (23 pts), ternaries 3 (8 pts), boolean chains 7 (nesting depth added 11). 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.
D2 · Cognitive Complexity · assemble.main (cognitive 35) · ×1
  • assemble.main (cognitive 35) development/web/script/claude-video/shared/assemble.mjs:161 — assemble.main has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (24 pts), ternaries 2 (6 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 18). 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.
D2 · Cognitive Complexity · select (cognitive 35) · ×1
  • select (cognitive 35) priv/assets/js/tabs.js:78 — select has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 5 (17 pts), if/else 11 (15 pts), boolean chains 3 (nesting depth added 16). Of this number, 31 points are the body's own statements and 4 belong to 5 function literals inside it that branch. 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.
D2 · Cognitive Complexity · handleKeyDown (cognitive 35) · ×1
  • handleKeyDown (cognitive 35) priv/assets/js/tree.js:413 — handleKeyDown has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (22 pts), boolean chains 10, ternaries 1 (2 pts), match/switch 1 (nesting depth added 11). 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.
D2 · Cognitive Complexity · MobBridgeKt.drawCanvasOp (cognitive 31) · ×1
  • MobBridgeKt.drawCanvasOp (cognitive 31) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:4460 — MobBridgeKt.drawCanvasOp has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (25 pts), match/switch 2 (3 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident. This file is where this pass's cognitive complexity CONCENTRATES: development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt holds 12 of the 50 methods over the threshold — including the worst — and 139 of the 505 points over it (28%), 4× the next-largest file (priv/assets/js/combobox.js at 35). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MobBridge.vendor_usb_open (cognitive 28) · ×1
  • MobBridge.vendor_usb_open (cognitive 28) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:2735 — MobBridge.vendor_usb_open has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 6, error handling 2, loops 1 (nesting depth added 6). 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. This file is where this pass's cognitive complexity CONCENTRATES: development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt holds 12 of the 50 methods over the threshold — including the worst — and 139 of the 505 points over it (28%), 4× the next-largest file (priv/assets/js/combobox.js at 35). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · applyTheme (cognitive 28) · ×1
  • applyTheme (cognitive 28) priv/assets/js/chart_chartjs.js:138 — applyTheme has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 13, if/else 8 (12 pts), other 3 (nesting depth added 4). Most of this is not in the body itself: 12 of the 28 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 141, 161). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · handleKeydown (cognitive 28) · ×1
  • handleKeydown (cognitive 28) priv/assets/js/menu.js:387 — handleKeydown has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (18 pts), ternaries 5 (7 pts), boolean chains 2, match/switch 1 (nesting depth added 11). Of this number, 26 points are the body's own statements and 2 belong to 3 function items inside it that branch. 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.
D2 · Cognitive Complexity · handleSearch (cognitive 27) · ×1
  • handleSearch (cognitive 27) priv/assets/js/combobox.js:337 — handleSearch has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 3, ternaries 2 (nesting depth added 11). Of this number, 23 points are the body's own statements and 4 belong to 4 function literals inside it that branch. 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.
D2 · Cognitive Complexity · MobBridgeKt.RenderNodeInner (cognitive 26) · ×1
  • MobBridgeKt.RenderNodeInner (cognitive 26) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:3038 — MobBridgeKt.RenderNodeInner has cognitive complexity 26 (threshold 15). Drivers by points: if/else 15 (21 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 7). 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. This file is where this pass's cognitive complexity CONCENTRATES: development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt holds 12 of the 50 methods over the threshold — including the worst — and 139 of the 505 points over it (28%), 4× the next-largest file (priv/assets/js/combobox.js at 35). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · onKeyDown (cognitive 26) · ×1
  • onKeyDown (cognitive 26) priv/assets/js/otp.js:203 — onKeyDown has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 8, ternaries 3 (6 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — 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.
D2 · Cognitive Complexity · MobBridge.motion_start (cognitive 25) · ×1
  • MobBridge.motion_start (cognitive 25) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:2254 — MobBridge.motion_start has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (23 pts), boolean chains 1, match/switch 1 (nesting depth added 10). 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. This file is where this pass's cognitive complexity CONCENTRATES: development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt holds 12 of the 50 methods over the threshold — including the worst — and 139 of the 505 points over it (28%), 4× the next-largest file (priv/assets/js/combobox.js at 35). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MobBridgeKt.packGpuUniforms (cognitive 25) · ×1
  • MobBridgeKt.packGpuUniforms (cognitive 25) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:4751 — MobBridgeKt.packGpuUniforms has cognitive complexity 25 (threshold 15). Drivers by points: loops 4 (13 pts), if/else 5 (9 pts), match/switch 2 (3 pts) (nesting depth added 14). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline. This file is where this pass's cognitive complexity CONCENTRATES: development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt holds 12 of the 50 methods over the threshold — including the worst — and 139 of the 505 points over it (28%), 4× the next-largest file (priv/assets/js/combobox.js at 35). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · bindSwipeArea (cognitive 25) · ×1
  • bindSwipeArea (cognitive 25) priv/assets/js/drawer.js:550 — bindSwipeArea has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 7, boolean chains 5, error handling 2 (nesting depth added 1). Most of this is not in the body itself: 3 of the 25 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 567, release, a function literal at line 554, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · parse (cognitive 25) · ×1
  • parse (cognitive 25) priv/assets/js/number_field.js:119 — parse has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 6, ternaries 3 (4 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — 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.
D2 · Cognitive Complexity · set (cognitive 25) · ×1
  • set (cognitive 25) priv/assets/js/slider.js:198 — set has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 5 (10 pts), loops 2 (4 pts) (nesting depth added 11). 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.
D2 · Cognitive Complexity · handleKeydown (cognitive 24) · ×1
  • handleKeydown (cognitive 24) priv/assets/js/context_menu.js:369 — handleKeydown has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 4, match/switch 1, ternaries 1 (nesting depth added 9). 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.
D2 · Cognitive Complexity · onKey (cognitive 24) · ×1
  • onKey (cognitive 24) priv/assets/js/toolbar.js:70 — onKey has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 6, ternaries 4 (6 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — 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, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · positionPopup (cognitive 23) · ×1
  • positionPopup (cognitive 23) priv/assets/js/menu.js:166 — positionPopup has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 5, ternaries 2 (4 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — 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, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · MobBridge.vendor_usb_list_devices (cognitive 21) · ×1
  • MobBridge.vendor_usb_list_devices (cognitive 21) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:2674 — MobBridge.vendor_usb_list_devices has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 4, error handling 2, loops 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. This file is where this pass's cognitive complexity CONCENTRATES: development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt holds 12 of the 50 methods over the threshold — including the worst — and 139 of the 505 points over it (28%), 4× the next-largest file (priv/assets/js/combobox.js at 35). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · moveSwipe (cognitive 21) · ×1
  • moveSwipe (cognitive 21) priv/assets/js/drawer.js:407 — moveSwipe has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 6 (11 pts), if/else 7, boolean chains 3 (nesting depth added 5). 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.
D2 · Cognitive Complexity · mask_input.applyMask (cognitive 20) · ×1
  • mask_input.applyMask (cognitive 20) priv/assets/js/mask_input.js:10 — mask_input.applyMask has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (7 pts), boolean chains 2, loops 2 (nesting depth added 9). Of this number, 17 points are the body's own statements and 3 belong to one function item inside it that branches. 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.
D2 · Cognitive Complexity · MishkaCalendar.row_node (cognitive 19) · ×1
  • MishkaCalendar.row_node (cognitive 19) development/mob/lib/mishka_mob/components/mishka_calendar.ex:419 — MishkaCalendar.row_node has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 18, if/else 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · MishkaCalendar.lane_node (cognitive 18) · ×1
  • MishkaCalendar.lane_node (cognitive 18) development/mob/lib/mishka_mob/components/mishka_calendar.ex:177 — MishkaCalendar.lane_node has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 15, if/else 3. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · mounted (cognitive 18) · ×1
  • mounted (cognitive 18) priv/assets/js/menu.js:19 — mounted has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, if/else 6 (8 pts), ternaries 1 (2 pts) (nesting depth added 3). Of this number, 13 points are the body's own statements and 5 belong to 11 function items inside it that branch. 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.
D2 · Cognitive Complexity · MishkaCalendar.week_block (cognitive 17) · ×1
  • MishkaCalendar.week_block (cognitive 17) development/mob/lib/mishka_mob/components/mishka_calendar.ex:268 — MishkaCalendar.week_block has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 17. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · MobBridge.decodeWavHeader (cognitive 17) · ×1
  • MobBridge.decodeWavHeader (cognitive 17) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:1837 — MobBridge.decodeWavHeader has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 6). 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. This file is where this pass's cognitive complexity CONCENTRATES: development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt holds 12 of the 50 methods over the threshold — including the worst — and 139 of the 505 points over it (28%), 4× the next-largest file (priv/assets/js/combobox.js at 35). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MobBridge.audioOutputStatus (cognitive 17) · ×1
  • MobBridge.audioOutputStatus (cognitive 17) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:2562 — MobBridge.audioOutputStatus has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (11 pts), match/switch 1 (3 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. 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. This file is where this pass's cognitive complexity CONCENTRATES: development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt holds 12 of the 50 methods over the threshold — including the worst — and 139 of the 505 points over it (28%), 4× the next-largest file (priv/assets/js/combobox.js at 35). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · MobBridgeKt.MobRangeSlider (cognitive 17) · ×1
  • MobBridgeKt.MobRangeSlider (cognitive 17) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:3932 — MobBridgeKt.MobRangeSlider has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — 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, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This file is where this pass's cognitive complexity CONCENTRATES: development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt holds 12 of the 50 methods over the threshold — including the worst — and 139 of the 505 points over it (28%), 4× the next-largest file (priv/assets/js/combobox.js at 35). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · mounted (cognitive 17) · ×1
  • mounted (cognitive 17) priv/assets/js/popup.js:12 — mounted has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 2 (6 pts), boolean chains 4 (nesting depth added 6). Of this number, 11 points are the body's own statements and 6 belong to 6 function literals inside it that branch. 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.
D2 · Cognitive Complexity · updateAxis (cognitive 17) · ×1
  • updateAxis (cognitive 17) priv/assets/js/scrollArea.js:67 — updateAxis has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 4 (5 pts), boolean chains 2 (nesting depth added 6). 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.
D2 · Cognitive Complexity · GenerateComponent.build_mix_command (cognitive 16) · ×1
  • GenerateComponent.build_mix_command (cognitive 16) lib/mishka_chelekom/mcp/tools/generate_component.ex:98 — GenerateComponent.build_mix_command has cognitive complexity 16 (threshold 15). Drivers by points: if/else 16. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. 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.
D2 · Cognitive Complexity · MobBridgeKt.nodeModifier (cognitive 16) · ×1
  • MobBridgeKt.nodeModifier (cognitive 16) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:5073 — MobBridgeKt.nodeModifier has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 2, match/switch 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. 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. This file is where this pass's cognitive complexity CONCENTRATES: development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt holds 12 of the 50 methods over the threshold — including the worst — and 139 of the 505 points over it (28%), 4× the next-largest file (priv/assets/js/combobox.js at 35). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · onKey (cognitive 16) · ×1
  • onKey (cognitive 16) priv/assets/js/toggle_group.js:127 — onKey has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, ternaries 4 (6 pts), boolean chains 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — 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, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · dropPosition (cognitive 16) · ×1
  • dropPosition (cognitive 16) priv/assets/js/tree.js:615 — dropPosition has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 5, boolean chains 3 (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.
D2 · Cognitive Complexity · groupWords (cognitive 16) · ×1
  • groupWords (cognitive 16) development/web/script/claude-video/shared/assemble.mjs:109 — groupWords has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 2 (4 pts), boolean chains 2, loops 1, other 1 (nesting depth added 5). 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.
D3 · God Classes · TooManyMethods · ×1
  • TooManyMethods: MobBridge development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:284 — TooManyMethods — 126 methods. The bar is 30 methods; this is 96 over it, 4.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D3 · God Classes · ClassTooLong · ×1
  • ClassTooLong: RootState development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:264 — ClassTooLong — 1656 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 1256 over it, 4.14× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D3 · God Classes · FunctionTooLong · ×1
  • FunctionTooLong: assemble.main development/web/script/claude-video/shared/assemble.mjs:161 — FunctionTooLong — main runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× 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 — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member family (6 members, 33 shared lines) · ×1
  • Near-duplicate member family (6 members, 33 shared lines) development/mob/lib/mishka_mob/showcase/components/accordion.ex:46 — development/mob/lib/mishka_mob/showcase/components/accordion.ex:46-205 | development/mob/lib/mishka_mob/showcase/components/combobox.ex:56-228 | development/mob/lib/mishka_mob/showcase/components/number_field.ex:34-172 | development/mob/lib/mishka_mob/showcase/components/radio_group.ex:33-185 | development/mob/lib/mishka_mob/showcase/components/segmented_control.ex:46-283 | development/mob/lib/mishka_mob/showcase/components/toggle_group.ex:53-334 — These 6 members are variants of one another: a block of 33 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Near-duplicate member family (3 members, 55 shared lines) · ×1
  • Near-duplicate member family (3 members, 55 shared lines) development/mob/lib/mishka_mob/showcase/components/collapsible.ex:37 — development/mob/lib/mishka_mob/showcase/components/collapsible.ex:37-155 | development/mob/lib/mishka_mob/showcase/components/meter.ex:31-171 | development/mob/lib/mishka_mob/showcase/components/progress.ex:31-153 — These 3 members are variants of one another: a block of 55 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
D4 · Code Duplication · Near-duplicate member pair (129 shared lines) · ×1
  • Near-duplicate member pair (129 shared lines) development/mob/lib/mishka_mob/showcase/components/nav_link.ex:61 — development/mob/lib/mishka_mob/showcase/components/nav_link.ex:61-316 | development/mob/lib/mishka_mob/showcase/components/tree.ex:116-458 — These two members are variants of one another: 129 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Edited copy of a member (179 corresponding lines) · ×1
  • Edited copy of a member (179 corresponding lines) development/mob/lib/mishka_mob/showcase/components/preview_card.ex:49 — development/mob/lib/mishka_mob/showcase/components/preview_card.ex:49-294 | development/mob/lib/mishka_mob/showcase/components/tree_select.ex:83-261 — These two members are one piece of code written twice and then edited apart: 179 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (110 corresponding lines) · ×1
  • Edited copy of a member (110 corresponding lines) development/mob/lib/mishka_mob/showcase/components/menu.ex:35 — development/mob/lib/mishka_mob/showcase/components/menu.ex:35-253 | development/mob/lib/mishka_mob/showcase/components/skeleton.ex:30-158 — These two members are one piece of code written twice and then edited apart: 110 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Members sharing a duplicated core (66 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (66 members, 50+ identical tokens) development/mob/lib/mishka_mob/showcase/components/accordion.ex:210 — development/mob/lib/mishka_mob/showcase/components/accordion.ex:210-301 | development/mob/lib/mishka_mob/showcase/components/action_icon.ex:234-308 | development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex:271-357 | development/mob/lib/mishka_mob/showcase/components/alpha_slider.ex:82-112 | development/mob/lib/mishka_mob/showcase/components/angle_slider.ex:85-118 | development/mob/lib/mishka_mob/showcase/components/autocomplete.ex:186-259 | development/mob/lib/mishka_mob/showcase/components/avatar.ex:113-146 | development/mob/lib/mishka_mob/showcase/components/calendar.ex:515-604 | development/mob/lib/mishka_mob/showcase/components/card.ex:306-409 | development/mob/lib/mishka_mob/showcase/components/checkbox.ex:129-169 | development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex:177-241 | development/mob/lib/mishka_mob/showcase/components/chip.ex:131-169 | development/mob/lib/mishka_mob/showcase/components/code.ex:106-139 | development/mob/lib/mishka_mob/showcase/components/collapsible.ex:160-216 | development/mob/lib/mishka_mob/showcase/components/color_input.ex:124-165 | development/mob/lib/mishka_mob/showcase/components/color_picker.ex:111-136 | development/mob/lib/mishka_mob/showcase/components/color_swatch.ex:142-176 | development/mob/lib/mishka_mob/showcase/components/combobox.ex:233-283 | development/mob/lib/mishka_mob/showcase/components/context_menu.ex:95-120 | development/mob/lib/mishka_mob/showcase/components/dialog.ex:239-337 | development/mob/lib/mishka_mob/showcase/components/dock.ex:110-161 | development/mob/lib/mishka_mob/showcase/components/drawer.ex:319-485 | development/mob/lib/mishka_mob/showcase/components/empty_state.ex:168-216 | development/mob/lib/mishka_mob/showcase/components/field.ex:253-310 | development/mob/lib/mishka_mob/showcase/components/floating_window.ex:465-547 | development/mob/lib/mishka_mob/showcase/components/highlight.ex:184-229 | development/mob/lib/mishka_mob/showcase/components/hue_slider.ex:68-103 | development/mob/lib/mishka_mob/showcase/components/json_input.ex:133-230 | development/mob/lib/mishka_mob/showcase/components/list_item.ex:156-193 | development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex:289-333 | development/mob/lib/mishka_mob/showcase/components/mark.ex:131-146 | development/mob/lib/mishka_mob/showcase/components/menu.ex:258-346 | development/mob/lib/mishka_mob/showcase/components/meter.ex:176-210 | development/mob/lib/mishka_mob/showcase/components/nav_link.ex:321-412 | development/mob/lib/mishka_mob/showcase/components/number_field.ex:177-265 | development/mob/lib/mishka_mob/showcase/components/otp_field.ex:208-296 | development/mob/lib/mishka_mob/showcase/components/overflow_list.ex:280-329 | development/mob/lib/mishka_mob/showcase/components/pill.ex:271-327 | development/mob/lib/mishka_mob/showcase/components/popover.ex:338-506 | development/mob/lib/mishka_mob/showcase/components/preview_card.ex:299-391 | development/mob/lib/mishka_mob/showcase/components/progress.ex:158-191 | development/mob/lib/mishka_mob/showcase/components/radio.ex:114-154 | development/mob/lib/mishka_mob/showcase/components/radio_group.ex:203-249 | development/mob/lib/mishka_mob/showcase/components/rating.ex:108-154 | development/mob/lib/mishka_mob/showcase/components/rolling_number.ex:159-185 | development/mob/lib/mishka_mob/showcase/components/scroll_area.ex:94-132 | development/mob/lib/mishka_mob/showcase/components/segmented_control.ex:288-393 | development/mob/lib/mishka_mob/showcase/components/select.ex:173-223 | development/mob/lib/mishka_mob/showcase/components/semi_circle_progress.ex:107-145 | development/mob/lib/mishka_mob/showcase/components/separator.ex:118-155 | development/mob/lib/mishka_mob/showcase/components/skeleton.ex:163-209 | development/mob/lib/mishka_mob/showcase/components/slider.ex:193-250 | development/mob/lib/mishka_mob/showcase/components/splitter.ex:160-210 | development/mob/lib/mishka_mob/showcase/components/spoiler.ex:110-155 | development/mob/lib/mishka_mob/showcase/components/switch.ex:156-199 | development/mob/lib/mishka_mob/showcase/components/tabs.ex:197-247 | development/mob/lib/mishka_mob/showcase/components/tags_input.ex:131-184 | development/mob/lib/mishka_mob/showcase/components/text_input.ex:148-211 | development/mob/lib/mishka_mob/showcase/components/theme_icon.ex:391-465 | development/mob/lib/mishka_mob/showcase/components/toast.ex:191-245 | development/mob/lib/mishka_mob/showcase/components/toggle.ex:217-292 | development/mob/lib/mishka_mob/showcase/components/toggle_group.ex:339-412 | development/mob/lib/mishka_mob/showcase/components/toolbar.ex:446-592 | development/mob/lib/mishka_mob/showcase/components/tooltip.ex:293-386 | development/mob/lib/mishka_mob/showcase/components/tree.ex:463-573 | development/mob/lib/mishka_mob/showcase/components/tree_select.ex:266-317 — These 66 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 66 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 66 times.
D4 · Code Duplication · Members sharing a duplicated core (13 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (13 members, 50+ identical tokens) development/web/lib/development_web/components/color_field.ex:98 — development/web/lib/development_web/components/color_field.ex:98-105 | development/web/lib/development_web/components/date_time_field.ex:152-159 | development/web/lib/development_web/components/email_field.ex:127-134 | development/web/lib/development_web/components/number_field.ex:118-125 | development/web/lib/development_web/components/radio_field.ex:96-103 | development/web/lib/development_web/components/radio_field.ex:206-213 | development/web/lib/development_web/components/range_field.ex:106-113 | development/web/lib/development_web/components/search_field.ex:125-132 | development/web/lib/development_web/components/tel_field.ex:127-134 | development/web/lib/development_web/components/text_field.ex:130-137 | development/web/lib/development_web/components/textarea_field.ex:128-135 | development/web/lib/development_web/components/toggle_field.ex:80-87 | development/web/lib/development_web/components/url_field.ex:114-121 — These 13 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 13 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 13 times.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (5 members, 50+ identical tokens) development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:251 — development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:251-271 | development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:320-336 | development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:346-364 | development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:366-384 | development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:479-501 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Edited copy of a member (36 corresponding lines) · ×1
  • Edited copy of a member (36 corresponding lines) lib/mix/tasks/mishka.ui.gen.components.ex:76 — lib/mix/tasks/mishka.ui.gen.components.ex:76-112 | lib/mix/tasks/mishka.ui.gen.headless.components.ex:60-95 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (202 corresponding lines) · ×1
  • Edited copy of a member (202 corresponding lines) development/mob/lib/mishka_mob/showcase/components/action_icon.ex:28 — development/mob/lib/mishka_mob/showcase/components/action_icon.ex:28-229 | development/mob/lib/mishka_mob/showcase/components/card.ex:34-298 — These two members are one piece of code written twice and then edited apart: 202 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 152+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 152+ corresponding lines) development/mob/lib/mishka_mob/showcase/components/dialog.ex:49 — development/mob/lib/mishka_mob/showcase/components/dialog.ex:49-234 | development/mob/lib/mishka_mob/showcase/components/floating_window.ex:71-222 | development/mob/lib/mishka_mob/showcase/components/tooltip.ex:53-288 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 152 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 22+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 22+ corresponding lines) lib/mix/tasks/mishka.ui.gen.component.ex:103 — lib/mix/tasks/mishka.ui.gen.component.ex:103-124 | lib/mix/tasks/mishka.ui.gen.headless.ex:63-85 | lib/mix/tasks/mishka.ui.gen.mob.ex:124-149 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×1
  • Edited copy of a member (27 corresponding lines) lib/mishka_chelekom/generators/npm.ex:101 — lib/mishka_chelekom/generators/npm.ex:101-128 | lib/mishka_chelekom/generators/npm.ex:173-199 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (119 corresponding lines) · ×1
  • Edited copy of a member (119 corresponding lines) development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex:37 — development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex:37-284 | development/mob/lib/mishka_mob/showcase/components/rolling_number.ex:36-154 — These two members are one piece of code written twice and then edited apart: 119 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×1
  • Edited copy of a member (21 corresponding lines) development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:1613 — development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:1613-1635 | development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt:1662-1682 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×1
  • Edited copy of a member (8 corresponding lines) development/web/lib/development_web/components/combobox.ex:156 — development/web/lib/development_web/components/combobox.ex:156-163 | development/web/lib/development_web/components/core_components.ex:189-196 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×1
  • Edited copy of a member (17 corresponding lines) development/mob/lib/mishka_mob/components/mishka_alpha_slider.ex:57 — development/mob/lib/mishka_mob/components/mishka_alpha_slider.ex:57-74 | development/mob/lib/mishka_mob/components/mishka_hue_slider.ex:61-77 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 13+ corresponding lines) development/mob/lib/mishka_mob/dice_screen.ex:160 — development/mob/lib/mishka_mob/dice_screen.ex:160-175 | development/mob/lib/mishka_mob/list_screen.ex:195-216 | development/mob/lib/mishka_mob/list_screen.ex:220-232 | development/mob/lib/mishka_mob/list_screen.ex:236-252 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 10+ corresponding lines) development/web/lib/development_web/live/showcase/catalog.ex:359 — development/web/lib/development_web/live/showcase/catalog.ex:359-379 | development/web/lib/development_web/live/showcase/catalog.ex:400-414 | development/web/lib/development_web/live/showcase/catalog.ex:488-497 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 6+ corresponding lines) development/mob/lib/mishka_mob/components/mishka_alpha_slider.ex:106 — development/mob/lib/mishka_mob/components/mishka_alpha_slider.ex:106-112 | development/mob/lib/mishka_mob/components/mishka_angle_slider.ex:169-175 | development/mob/lib/mishka_mob/components/mishka_color_picker.ex:186-191 | development/mob/lib/mishka_mob/components/mishka_hue_slider.ex:109-115 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×1
  • Edited copy of a member (25 corresponding lines) development/mob/lib/mishka_mob/showcase/components/theme_icon.ex:112 — development/mob/lib/mishka_mob/showcase/components/theme_icon.ex:112-136 | development/mob/lib/mishka_mob/showcase/components/theme_icon.ex:140-165 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 7+ corresponding lines) development/web/lib/development_web/live/showcase/headless_form_demos.ex:769 — development/web/lib/development_web/live/showcase/headless_form_demos.ex:769-776 | development/web/lib/development_web/live/showcase/headless_form_demos.ex:955-961 | development/web/lib/development_web/live/showcase/headless_form_demos.ex:1073-1081 | development/web/lib/development_web/live/showcase/headless_form_demos.ex:1268-1276 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×1
  • Edited copy of a member (16 corresponding lines) development/mob/lib/mishka_mob/components/mishka_combobox.ex:381 — development/mob/lib/mishka_mob/components/mishka_combobox.ex:381-396 | development/mob/lib/mishka_mob/components/mishka_number_field.ex:359-377 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 6+ corresponding lines) development/mob/lib/mishka_mob/storage_screen.ex:71 — development/mob/lib/mishka_mob/storage_screen.ex:71-76 | development/mob/lib/mishka_mob/storage_screen.ex:80-86 | development/mob/lib/mishka_mob/storage_screen.ex:90-95 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 3+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 3+ corresponding lines) development/mob/lib/mishka_mob/showcase/components/checkbox.ex:194 — development/mob/lib/mishka_mob/showcase/components/checkbox.ex:194-198 | development/mob/lib/mishka_mob/showcase/components/chip.ex:183-192 | development/mob/lib/mishka_mob/showcase/components/chip.ex:196-205 | development/mob/lib/mishka_mob/showcase/components/color_swatch.ex:188-197 | development/mob/lib/mishka_mob/showcase/components/context_menu.ex:138-140 | development/mob/lib/mishka_mob/showcase/components/radio.ex:162-166 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 5+ corresponding lines) development/web/lib/development_web/components/badge.ex:922 — development/web/lib/development_web/components/badge.ex:922-926 | development/web/lib/development_web/components/button.ex:2116-2120 | development/web/lib/development_web/components/indicator.ex:274-278 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×1
  • Edited copy of a member (6 corresponding lines) development/web/lib/development_web/components/headless/tree.ex:437 — development/web/lib/development_web/components/headless/tree.ex:437-442 | development/web/lib/development_web/live/showcase/tree_demos.ex:528-533 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 4+ corresponding lines) development/mob/lib/mishka_mob/components/mishka_menu.ex:501 — development/mob/lib/mishka_mob/components/mishka_menu.ex:501-504 | development/mob/lib/mishka_mob/components/mishka_tabs.ex:342-345 | development/mob/lib/mishka_mob/components/mishka_tags_input.ex:243-246 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 1+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 1+ corresponding lines) development/mob/lib/mishka_mob/showcase/components/collapsible.ex:225 — development/mob/lib/mishka_mob/showcase/components/collapsible.ex:225-226 | development/mob/lib/mishka_mob/showcase/components/combobox.ex:338-339 | development/mob/lib/mishka_mob/showcase/components/select.ex:257-257 | development/mob/lib/mishka_mob/showcase/components/spoiler.ex:163-163 | development/mob/lib/mishka_mob/showcase/components/toggle.ex:301-301 | development/mob/lib/mishka_mob/showcase/components/toolbar.ex:613-613 | development/mob/lib/mishka_mob/showcase/components/tree_select.ex:358-358 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 2+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 2+ corresponding lines) lib/mix/tasks/mishka.ui.gen.component.ex:128 — lib/mix/tasks/mishka.ui.gen.component.ex:128-129 | lib/mix/tasks/mishka.ui.gen.components.ex:116-117 | lib/mix/tasks/mishka.ui.gen.headless.ex:89-90 | lib/mix/tasks/mishka.ui.gen.mob.ex:153-154 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 2 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 1+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 1+ corresponding lines) development/mob/lib/mishka_mob/components/mishka_dialog.ex:610 — development/mob/lib/mishka_mob/components/mishka_dialog.ex:610-610 | development/mob/lib/mishka_mob/components/mishka_progress.ex:441-441 | development/mob/lib/mishka_mob/components/mishka_separator.ex:270-270 | development/mob/lib/mishka_mob/components/mishka_slider.ex:309-309 | development/mob/lib/mishka_mob/components/mishka_switch.ex:406-406 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 2+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 2+ corresponding lines) development/mob/lib/mishka_mob/components/mishka_radio.ex:129 — development/mob/lib/mishka_mob/components/mishka_radio.ex:129-130 | development/mob/lib/mishka_mob/components/mishka_segmented_control.ex:430-431 | development/mob/lib/mishka_mob/components/mishka_toggle.ex:190-191 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 2 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (62–98 lines × 2) · ×1
  • Duplicated block (62–98 lines × 2) development/mob/lib/mishka_mob/showcase/components/highlight.ex:47 — development/mob/lib/mishka_mob/showcase/components/highlight.ex:47-108 | development/mob/lib/mishka_mob/showcase/components/preview_card.ex:196-293 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/highlight.ex` and `development/mob/lib/mishka_mob/showcase/components/preview_card.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 245 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/highlight.ex:47` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (10–90 lines × 13) · ×1
  • Duplicated block (10–90 lines × 13) development/mob/lib/mishka_mob/showcase/components/accordion.ex:66 — development/mob/lib/mishka_mob/showcase/components/accordion.ex:66-133 | development/mob/lib/mishka_mob/showcase/components/autocomplete.ex:103-112 | development/mob/lib/mishka_mob/showcase/components/combobox.ex:114-165 | development/mob/lib/mishka_mob/showcase/components/json_input.ex:51-101 | development/mob/lib/mishka_mob/showcase/components/number_field.ex:46-102 | development/mob/lib/mishka_mob/showcase/components/radio_group.ex:53-139 | development/mob/lib/mishka_mob/showcase/components/segmented_control.ex:70-145 | development/mob/lib/mishka_mob/showcase/components/select.ex:57-146 | development/mob/lib/mishka_mob/showcase/components/slider.ex:50-101 | development/mob/lib/mishka_mob/showcase/components/splitter.ex:63-140 | development/mob/lib/mishka_mob/showcase/components/spoiler.ex:55-104 | development/mob/lib/mishka_mob/showcase/components/tabs.ex:99-155 | development/mob/lib/mishka_mob/showcase/components/toggle_group.ex:110-128 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/accordion.ex` and `development/mob/lib/mishka_mob/showcase/components/autocomplete.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 311 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/accordion.ex:66` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `development/mob/lib/mishka_mob/showcase/components/autocomplete.ex:100` calls `inspect` and `development/mob/lib/mishka_mob/showcase/components/combobox.ex:111` does not — 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.
D4 · Code Duplication · Duplicated block (66–90 lines × 2) · ×1
  • Duplicated block (66–90 lines × 2) development/mob/lib/mishka_mob/showcase/components/list_item.ex:28 — development/mob/lib/mishka_mob/showcase/components/list_item.ex:28-117 | development/mob/lib/mishka_mob/showcase/components/text_input.ex:63-128 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/list_item.ex` and `development/mob/lib/mishka_mob/showcase/components/text_input.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 281 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/list_item.ex:28` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (49–86 lines × 2) · ×1
  • Duplicated block (49–86 lines × 2) development/mob/lib/mishka_mob/showcase/components/otp_field.ex:67 — development/mob/lib/mishka_mob/showcase/components/otp_field.ex:67-115 | development/mob/lib/mishka_mob/showcase/components/otp_field.ex:117-202 — both copies are in the same file, so extract the block into one function there and call it from each site — 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 `development/mob/lib/mishka_mob/showcase/components/otp_field.ex:67` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (25–85 lines × 6) · ×1
  • Duplicated block (25–85 lines × 6) development/mob/lib/mishka_mob/showcase/components/card.ex:149 — development/mob/lib/mishka_mob/showcase/components/card.ex:149-207 | development/mob/lib/mishka_mob/showcase/components/popover.ex:195-267 | development/mob/lib/mishka_mob/showcase/components/preview_card.ex:174-258 | development/mob/lib/mishka_mob/showcase/components/skeleton.ex:74-98 | development/mob/lib/mishka_mob/showcase/components/tooltip.ex:202-271 | development/mob/lib/mishka_mob/showcase/components/tree_select.ex:144-206 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/card.ex` and `development/mob/lib/mishka_mob/showcase/components/popover.ex` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 363 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/card.ex:149` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (10–79 lines × 16) · ×1
  • Duplicated block (10–79 lines × 16) development/mob/lib/mishka_mob/showcase/components/accordion.ex:50 — development/mob/lib/mishka_mob/showcase/components/accordion.ex:50-116 | development/mob/lib/mishka_mob/showcase/components/autocomplete.ex:103-112 | development/mob/lib/mishka_mob/showcase/components/checkbox.ex:41-91 | development/mob/lib/mishka_mob/showcase/components/collapsible.ex:41-99 | development/mob/lib/mishka_mob/showcase/components/combobox.ex:114-163 | development/mob/lib/mishka_mob/showcase/components/json_input.ex:37-87 | development/mob/lib/mishka_mob/showcase/components/number_field.ex:38-100 | development/mob/lib/mishka_mob/showcase/components/radio_group.ex:37-112 | development/mob/lib/mishka_mob/showcase/components/segmented_control.ex:50-128 | development/mob/lib/mishka_mob/showcase/components/select.ex:48-125 | development/mob/lib/mishka_mob/showcase/components/slider.ex:42-86 | development/mob/lib/mishka_mob/showcase/components/splitter.ex:41-119 | development/mob/lib/mishka_mob/showcase/components/spoiler.ex:38-94 | development/mob/lib/mishka_mob/showcase/components/tabs.ex:84-138 | development/mob/lib/mishka_mob/showcase/components/tags_input.ex:38-79 | development/mob/lib/mishka_mob/showcase/components/toggle_group.ex:110-128 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/accordion.ex` and `development/mob/lib/mishka_mob/showcase/components/autocomplete.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 311 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/accordion.ex:50` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `development/mob/lib/mishka_mob/showcase/components/combobox.ex:166` calls `self` and `development/mob/lib/mishka_mob/showcase/components/accordion.ex:119` does not — 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.
D4 · Code Duplication · Duplicated block (11–79 lines × 12) · ×1
  • Duplicated block (11–79 lines × 12) development/mob/lib/mishka_mob/showcase/components/action_icon.ex:33 — development/mob/lib/mishka_mob/showcase/components/action_icon.ex:33-111 | development/mob/lib/mishka_mob/showcase/components/checkbox.ex:62-107 | development/mob/lib/mishka_mob/showcase/components/chip.ex:77-113 | development/mob/lib/mishka_mob/showcase/components/color_swatch.ex:44-102 | development/mob/lib/mishka_mob/showcase/components/combobox.ex:188-217 | development/mob/lib/mishka_mob/showcase/components/field.ex:201-227 | development/mob/lib/mishka_mob/showcase/components/menu.ex:116-151 | development/mob/lib/mishka_mob/showcase/components/meter.ex:66-103 | development/mob/lib/mishka_mob/showcase/components/overflow_list.ex:84-141 | development/mob/lib/mishka_mob/showcase/components/progress.ex:69-92 | development/mob/lib/mishka_mob/showcase/components/radio.ex:34-82 | development/mob/lib/mishka_mob/showcase/components/toggle.ex:86-96 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/action_icon.ex` and `development/mob/lib/mishka_mob/showcase/components/checkbox.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 190 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/action_icon.ex:33` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (10–77 lines × 17) · ×1
  • Duplicated block (10–77 lines × 17) development/mob/lib/mishka_mob/showcase/components/accordion.ex:47 — development/mob/lib/mishka_mob/showcase/components/accordion.ex:47-108 | development/mob/lib/mishka_mob/showcase/components/autocomplete.ex:103-112 | development/mob/lib/mishka_mob/showcase/components/checkbox.ex:38-87 | development/mob/lib/mishka_mob/showcase/components/collapsible.ex:38-95 | development/mob/lib/mishka_mob/showcase/components/combobox.ex:114-151 | development/mob/lib/mishka_mob/showcase/components/field.ex:43-82 | development/mob/lib/mishka_mob/showcase/components/json_input.ex:34-83 | development/mob/lib/mishka_mob/showcase/components/number_field.ex:35-95 | development/mob/lib/mishka_mob/showcase/components/radio_group.ex:34-101 | development/mob/lib/mishka_mob/showcase/components/segmented_control.ex:47-114 | development/mob/lib/mishka_mob/showcase/components/select.ex:45-113 | development/mob/lib/mishka_mob/showcase/components/slider.ex:39-82 | development/mob/lib/mishka_mob/showcase/components/splitter.ex:38-114 | development/mob/lib/mishka_mob/showcase/components/spoiler.ex:35-90 | development/mob/lib/mishka_mob/showcase/components/tabs.ex:108-158 | development/mob/lib/mishka_mob/showcase/components/tags_input.ex:35-79 | development/mob/lib/mishka_mob/showcase/components/toggle_group.ex:110-128 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/accordion.ex` and `development/mob/lib/mishka_mob/showcase/components/autocomplete.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 311 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/accordion.ex:47` it does not close everything it opens, so those exact lines cannot be lifted as they stand — 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `development/mob/lib/mishka_mob/showcase/components/autocomplete.ex:100` calls `inspect` and `development/mob/lib/mishka_mob/showcase/components/combobox.ex:111` does not — 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.
D4 · Code Duplication · Duplicated block (46–76 lines × 5) · ×1
  • Duplicated block (46–76 lines × 5) development/mob/lib/mishka_mob/showcase/components/collapsible.ex:79 — development/mob/lib/mishka_mob/showcase/components/collapsible.ex:79-154 | development/mob/lib/mishka_mob/showcase/components/empty_state.ex:39-107 | development/mob/lib/mishka_mob/showcase/components/meter.ex:81-134 | development/mob/lib/mishka_mob/showcase/components/progress.ex:78-123 | development/mob/lib/mishka_mob/showcase/components/switch.ex:87-150 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/collapsible.ex` and `development/mob/lib/mishka_mob/showcase/components/empty_state.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 141 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/collapsible.ex:79` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (18–75 lines × 2) · ×1
  • Duplicated block (18–75 lines × 2) development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex:72 — development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex:72-146 | development/mob/lib/mishka_mob/showcase/components/field.ex:69-86 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex` and `development/mob/lib/mishka_mob/showcase/components/field.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 206 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex:72` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (10–72 lines × 8) · ×1
  • Duplicated block (10–72 lines × 8) development/mob/lib/mishka_mob/showcase/components/accordion.ex:110 — development/mob/lib/mishka_mob/showcase/components/accordion.ex:110-162 | development/mob/lib/mishka_mob/showcase/components/field.ex:46-83 | development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex:100-109 | development/mob/lib/mishka_mob/showcase/components/nav_link.ex:238-282 | development/mob/lib/mishka_mob/showcase/components/radio_group.ex:103-164 | development/mob/lib/mishka_mob/showcase/components/select.ex:80-151 | development/mob/lib/mishka_mob/showcase/components/slider.ex:84-122 | development/mob/lib/mishka_mob/showcase/components/tree.ex:147-187 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/accordion.ex` and `development/mob/lib/mishka_mob/showcase/components/field.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 283 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/accordion.ex:110` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (10–72 lines × 2) · ×1
  • Duplicated block (10–72 lines × 2) development/mob/lib/mishka_mob/showcase/components/empty_state.ex:80 — development/mob/lib/mishka_mob/showcase/components/empty_state.ex:80-151 | development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex:191-200 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/empty_state.ex` and `development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 199 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/empty_state.ex:80` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (25–71 lines × 7) · ×1
  • Duplicated block (25–71 lines × 7) development/mob/lib/mishka_mob/showcase/components/action_icon.ex:30 — development/mob/lib/mishka_mob/showcase/components/action_icon.ex:30-100 | development/mob/lib/mishka_mob/showcase/components/chip.ex:74-109 | development/mob/lib/mishka_mob/showcase/components/color_swatch.ex:41-96 | development/mob/lib/mishka_mob/showcase/components/menu.ex:116-140 | development/mob/lib/mishka_mob/showcase/components/overflow_list.ex:84-130 | development/mob/lib/mishka_mob/showcase/components/pill.ex:115-172 | development/mob/lib/mishka_mob/showcase/components/switch.ex:73-118 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/action_icon.ex` and `development/mob/lib/mishka_mob/showcase/components/chip.ex` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 399 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/action_icon.ex:30` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (48–70 lines × 3) · ×1
  • Duplicated block (48–70 lines × 3) development/mob/lib/mishka_mob/showcase/components/nav_link.ex:183 — development/mob/lib/mishka_mob/showcase/components/nav_link.ex:183-238 | development/mob/lib/mishka_mob/showcase/components/popover.ex:231-300 | development/mob/lib/mishka_mob/showcase/components/tooltip.ex:126-173 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/nav_link.ex` and `development/mob/lib/mishka_mob/showcase/components/popover.ex` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 447 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/nav_link.ex:183` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (23–69 lines × 9) · ×1
  • Duplicated block (23–69 lines × 9) development/mob/lib/mishka_mob/showcase/components/action_icon.ex:32 — development/mob/lib/mishka_mob/showcase/components/action_icon.ex:32-100 | development/mob/lib/mishka_mob/showcase/components/chip.ex:76-109 | development/mob/lib/mishka_mob/showcase/components/color_swatch.ex:43-96 | development/mob/lib/mishka_mob/showcase/components/field.ex:201-223 | development/mob/lib/mishka_mob/showcase/components/menu.ex:116-140 | development/mob/lib/mishka_mob/showcase/components/overflow_list.ex:84-130 | development/mob/lib/mishka_mob/showcase/components/pill.ex:117-173 | development/mob/lib/mishka_mob/showcase/components/rolling_number.ex:88-115 | development/mob/lib/mishka_mob/showcase/components/switch.ex:75-119 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/action_icon.ex` and `development/mob/lib/mishka_mob/showcase/components/chip.ex` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 399 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/action_icon.ex:32` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (9–69 lines × 4) · ×1
  • Duplicated block (9–69 lines × 4) development/mob/lib/mishka_mob/showcase/components/accordion.ex:136 — development/mob/lib/mishka_mob/showcase/components/accordion.ex:136-204 | development/mob/lib/mishka_mob/showcase/components/field.ex:62-86 | development/mob/lib/mishka_mob/showcase/components/slider.ex:104-125 | development/mob/lib/mishka_mob/showcase/components/tree.ex:210-218 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/accordion.ex` and `development/mob/lib/mishka_mob/showcase/components/field.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 283 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/accordion.ex:136` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (49–69 lines × 2) · ×1
  • Duplicated block (49–69 lines × 2) development/mob/lib/mishka_mob/showcase/components/calendar.ex:256 — development/mob/lib/mishka_mob/showcase/components/calendar.ex:256-304 | development/mob/lib/mishka_mob/showcase/components/drawer.ex:242-310 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/calendar.ex` and `development/mob/lib/mishka_mob/showcase/components/drawer.ex` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 197 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/calendar.ex:256` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (21–68 lines × 5) · ×1
  • Duplicated block (21–68 lines × 5) development/mob/lib/mishka_mob/showcase/components/chip.ex:41 — development/mob/lib/mishka_mob/showcase/components/chip.ex:41-93 | development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex:135-155 | development/mob/lib/mishka_mob/showcase/components/nav_link.ex:262-296 | development/mob/lib/mishka_mob/showcase/components/switch.ex:70-102 | development/mob/lib/mishka_mob/showcase/components/tabs.ex:42-109 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/chip.ex` and `development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 266 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/chip.ex:41` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (46–68 lines × 4) · ×1
  • Duplicated block (46–68 lines × 4) development/mob/lib/mishka_mob/showcase/components/card.ex:235 — development/mob/lib/mishka_mob/showcase/components/card.ex:235-298 | development/mob/lib/mishka_mob/showcase/components/text_input.ex:98-143 | development/mob/lib/mishka_mob/showcase/components/toast.ex:119-186 | development/mob/lib/mishka_mob/showcase/components/tooltip.ex:243-288 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/card.ex` and `development/mob/lib/mishka_mob/showcase/components/text_input.ex` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 410 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/card.ex:235` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `development/mob/lib/mishka_mob/showcase/components/card.ex:301` calls `taps_label` and `development/mob/lib/mishka_mob/showcase/components/text_input.ex:146` does not — 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.
D4 · Code Duplication · Duplicated block (47–68 lines × 4) · ×1
  • Duplicated block (47–68 lines × 4) development/mob/lib/mishka_mob/showcase/components/empty_state.ex:54 — development/mob/lib/mishka_mob/showcase/components/empty_state.ex:54-112 | development/mob/lib/mishka_mob/showcase/components/nav_link.ex:184-237 | development/mob/lib/mishka_mob/showcase/components/popover.ex:232-299 | development/mob/lib/mishka_mob/showcase/components/tooltip.ex:127-173 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/empty_state.ex` and `development/mob/lib/mishka_mob/showcase/components/nav_link.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 133 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/empty_state.ex:54` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (11–67 lines × 19) · ×1
  • Duplicated block (11–67 lines × 19) development/mob/lib/mishka_mob/showcase/components/action_icon.ex:56 — development/mob/lib/mishka_mob/showcase/components/action_icon.ex:56-122 | development/mob/lib/mishka_mob/showcase/components/avatar.ex:32-80 | development/mob/lib/mishka_mob/showcase/components/checkbox.ex:69-123 | development/mob/lib/mishka_mob/showcase/components/chip.ex:85-125 | development/mob/lib/mishka_mob/showcase/components/code.ex:32-80 | development/mob/lib/mishka_mob/showcase/components/color_swatch.ex:60-117 | development/mob/lib/mishka_mob/showcase/components/combobox.ex:188-227 | development/mob/lib/mishka_mob/showcase/components/highlight.ex:136-178 | development/mob/lib/mishka_mob/showcase/components/mark.ex:84-125 | development/mob/lib/mishka_mob/showcase/components/menu.ex:116-169 | development/mob/lib/mishka_mob/showcase/components/meter.ex:66-116 | development/mob/lib/mishka_mob/showcase/components/overflow_list.ex:143-192 | development/mob/lib/mishka_mob/showcase/components/pill.ex:208-265 | development/mob/lib/mishka_mob/showcase/components/progress.ex:69-101 | development/mob/lib/mishka_mob/showcase/components/radio.ex:46-91 | development/mob/lib/mishka_mob/showcase/components/scroll_area.ex:32-88 | development/mob/lib/mishka_mob/showcase/components/separator.ex:40-83 | development/mob/lib/mishka_mob/showcase/components/toast.ex:59-117 | development/mob/lib/mishka_mob/showcase/components/toggle.ex:86-96 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/action_icon.ex` and `development/mob/lib/mishka_mob/showcase/components/avatar.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/action_icon.ex:56` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (17–67 lines × 12) · ×1
  • Duplicated block (17–67 lines × 12) development/mob/lib/mishka_mob/showcase/components/action_icon.ex:76 — development/mob/lib/mishka_mob/showcase/components/action_icon.ex:76-132 | development/mob/lib/mishka_mob/showcase/components/avatar.ex:28-69 | development/mob/lib/mishka_mob/showcase/components/code.ex:28-69 | development/mob/lib/mishka_mob/showcase/components/color_swatch.ex:80-124 | development/mob/lib/mishka_mob/showcase/components/highlight.ex:130-168 | development/mob/lib/mishka_mob/showcase/components/mark.ex:84-111 | development/mob/lib/mishka_mob/showcase/components/pill.ex:208-248 | development/mob/lib/mishka_mob/showcase/components/radio.ex:63-98 | development/mob/lib/mishka_mob/showcase/components/scroll_area.ex:28-72 | development/mob/lib/mishka_mob/showcase/components/separator.ex:32-72 | development/mob/lib/mishka_mob/showcase/components/toast.ex:42-108 | development/mob/lib/mishka_mob/showcase/components/toggle.ex:120-136 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/action_icon.ex` and `development/mob/lib/mishka_mob/showcase/components/avatar.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/action_icon.ex:76` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (8–67 lines × 12) · ×1
  • Duplicated block (8–67 lines × 12) development/mob/lib/mishka_mob/showcase/components/chip.ex:43 — development/mob/lib/mishka_mob/showcase/components/chip.ex:43-93 | development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex:135-155 | development/mob/lib/mishka_mob/showcase/components/nav_link.ex:206-263 | development/mob/lib/mishka_mob/showcase/components/nav_link.ex:264-297 | development/mob/lib/mishka_mob/showcase/components/pill.ex:112-150 | development/mob/lib/mishka_mob/showcase/components/popover.ex:45-108 | development/mob/lib/mishka_mob/showcase/components/preview_card.ex:117-124 | development/mob/lib/mishka_mob/showcase/components/switch.ex:70-102 | development/mob/lib/mishka_mob/showcase/components/tabs.ex:44-110 | development/mob/lib/mishka_mob/showcase/components/tooltip.ex:199-245 | development/mob/lib/mishka_mob/showcase/components/tree.ex:360-367 | development/mob/lib/mishka_mob/showcase/components/tree_select.ex:141-186 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/chip.ex` and `development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 266 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/chip.ex:43` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `development/mob/lib/mishka_mob/showcase/components/pill.ex:108` calls `self` and `development/mob/lib/mishka_mob/showcase/components/preview_card.ex:113` does not — 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.
D4 · Code Duplication · Duplicated block (37–67 lines × 7) · ×1
  • Duplicated block (37–67 lines × 7) development/mob/lib/mishka_mob/showcase/components/card.ex:35 — development/mob/lib/mishka_mob/showcase/components/card.ex:35-80 | development/mob/lib/mishka_mob/showcase/components/card.ex:235-297 | development/mob/lib/mishka_mob/showcase/components/highlight.ex:34-92 | development/mob/lib/mishka_mob/showcase/components/mark.ex:25-61 | development/mob/lib/mishka_mob/showcase/components/text_input.ex:98-142 | development/mob/lib/mishka_mob/showcase/components/toast.ex:119-185 | development/mob/lib/mishka_mob/showcase/components/tooltip.ex:243-287 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/card.ex` and `development/mob/lib/mishka_mob/showcase/components/highlight.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 190 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/card.ex:35` it does not close everything it opens, so those exact lines cannot be lifted as they stand — 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (9–66 lines × 5) · ×1
  • Duplicated block (9–66 lines × 5) development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex:72 — development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex:72-137 | development/mob/lib/mishka_mob/showcase/components/field.ex:64-86 | development/mob/lib/mishka_mob/showcase/components/nav_link.ex:115-123 | development/mob/lib/mishka_mob/showcase/components/slider.ex:106-125 | development/mob/lib/mishka_mob/showcase/components/tree.ex:210-218 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex` and `development/mob/lib/mishka_mob/showcase/components/field.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 206 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex:72` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (8–66 lines × 4) · ×1
  • Duplicated block (8–66 lines × 4) development/mob/lib/mishka_mob/showcase/components/nav_link.ex:203 — development/mob/lib/mishka_mob/showcase/components/nav_link.ex:203-259 | development/mob/lib/mishka_mob/showcase/components/popover.ex:267-332 | development/mob/lib/mishka_mob/showcase/components/tooltip.ex:199-241 | development/mob/lib/mishka_mob/showcase/components/tree.ex:360-367 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/nav_link.ex` and `development/mob/lib/mishka_mob/showcase/components/popover.ex` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 447 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/nav_link.ex:203` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (9–65 lines × 4) · ×1
  • Duplicated block (9–65 lines × 4) development/mob/lib/mishka_mob/showcase/components/nav_link.ex:191 — development/mob/lib/mishka_mob/showcase/components/nav_link.ex:191-243 | development/mob/lib/mishka_mob/showcase/components/popover.ex:246-310 | development/mob/lib/mishka_mob/showcase/components/tooltip.ex:141-173 | development/mob/lib/mishka_mob/showcase/components/tree.ex:284-292 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/nav_link.ex` and `development/mob/lib/mishka_mob/showcase/components/popover.ex` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 447 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/nav_link.ex:191` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (9–65 lines × 3) · ×1
  • Duplicated block (9–65 lines × 3) development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex:72 — development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex:72-136 | development/mob/lib/mishka_mob/showcase/components/nav_link.ex:115-123 | development/mob/lib/mishka_mob/showcase/components/tree.ex:284-292 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex` and `development/mob/lib/mishka_mob/showcase/components/nav_link.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex:72` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (17–63 lines × 13) · ×1
  • Duplicated block (17–63 lines × 13) development/mob/lib/mishka_mob/showcase/components/action_icon.ex:73 — development/mob/lib/mishka_mob/showcase/components/action_icon.ex:73-125 | development/mob/lib/mishka_mob/showcase/components/avatar.ex:25-64 | development/mob/lib/mishka_mob/showcase/components/code.ex:25-65 | development/mob/lib/mishka_mob/showcase/components/color_swatch.ex:77-120 | development/mob/lib/mishka_mob/showcase/components/empty_state.ex:28-78 | development/mob/lib/mishka_mob/showcase/components/menu.ex:118-173 | development/mob/lib/mishka_mob/showcase/components/meter.ex:68-120 | development/mob/lib/mishka_mob/showcase/components/progress.ex:71-105 | development/mob/lib/mishka_mob/showcase/components/radio.ex:60-94 | development/mob/lib/mishka_mob/showcase/components/scroll_area.ex:25-68 | development/mob/lib/mishka_mob/showcase/components/separator.ex:29-68 | development/mob/lib/mishka_mob/showcase/components/toast.ex:39-101 | development/mob/lib/mishka_mob/showcase/components/toggle.ex:120-136 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/action_icon.ex` and `development/mob/lib/mishka_mob/showcase/components/avatar.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/action_icon.ex:73` it does not close everything it opens, so those exact lines cannot be lifted as they stand — 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (43–62 lines × 5) · ×1
  • Duplicated block (43–62 lines × 5) development/mob/lib/mishka_mob/showcase/components/floating_window.ex:178 — development/mob/lib/mishka_mob/showcase/components/floating_window.ex:178-220 | development/mob/lib/mishka_mob/showcase/components/nav_link.ex:232-277 | development/mob/lib/mishka_mob/showcase/components/tabs.ex:78-131 | development/mob/lib/mishka_mob/showcase/components/tree.ex:395-456 | development/mob/lib/mishka_mob/showcase/components/tree_select.ex:202-259 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/floating_window.ex` and `development/mob/lib/mishka_mob/showcase/components/nav_link.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 190 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/floating_window.ex:178` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (54–62 lines × 2) · ×1
  • Duplicated block (54–62 lines × 2) development/mob/lib/mishka_mob/showcase/components/empty_state.ex:102 — development/mob/lib/mishka_mob/showcase/components/empty_state.ex:102-163 | development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex:231-284 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/empty_state.ex` and `development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 199 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/empty_state.ex:102` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (39–61 lines × 3) · ×1
  • Duplicated block (39–61 lines × 3) development/mob/lib/mishka_mob/showcase/components/action_icon.ex:111 — development/mob/lib/mishka_mob/showcase/components/action_icon.ex:111-155 | development/mob/lib/mishka_mob/showcase/components/rating.ex:54-92 | development/mob/lib/mishka_mob/showcase/components/toast.ex:81-141 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/action_icon.ex` and `development/mob/lib/mishka_mob/showcase/components/rating.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 217 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/action_icon.ex:111` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (23–60 lines × 7) · ×1
  • Duplicated block (23–60 lines × 7) development/mob/lib/mishka_mob/showcase/components/action_icon.ex:141 — development/mob/lib/mishka_mob/showcase/components/action_icon.ex:141-182 | development/mob/lib/mishka_mob/showcase/components/card.ex:58-80 | development/mob/lib/mishka_mob/showcase/components/card.ex:233-279 | development/mob/lib/mishka_mob/showcase/components/list_item.ex:79-118 | development/mob/lib/mishka_mob/showcase/components/text_input.ex:96-129 | development/mob/lib/mishka_mob/showcase/components/toast.ex:117-176 | development/mob/lib/mishka_mob/showcase/components/tooltip.ex:241-277 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/action_icon.ex` and `development/mob/lib/mishka_mob/showcase/components/card.ex` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 312 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/action_icon.ex:141` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (33–58 lines × 10) · ×1
  • Duplicated block (33–58 lines × 10) development/mob/lib/mishka_mob/showcase/components/action_icon.ex:127 — development/mob/lib/mishka_mob/showcase/components/action_icon.ex:127-168 | development/mob/lib/mishka_mob/showcase/components/card.ex:39-80 | development/mob/lib/mishka_mob/showcase/components/card.ex:211-265 | development/mob/lib/mishka_mob/showcase/components/highlight.ex:38-95 | development/mob/lib/mishka_mob/showcase/components/highlight.ex:113-148 | development/mob/lib/mishka_mob/showcase/components/mark.ex:29-61 | development/mob/lib/mishka_mob/showcase/components/pill.ex:152-186 | development/mob/lib/mishka_mob/showcase/components/rating.ex:28-68 | development/mob/lib/mishka_mob/showcase/components/rolling_number.ex:93-139 | development/mob/lib/mishka_mob/showcase/components/toast.ex:103-160 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/action_icon.ex` and `development/mob/lib/mishka_mob/showcase/components/card.ex` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 312 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/action_icon.ex:127` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (29–57 lines × 5) · ×1
  • Duplicated block (29–57 lines × 5) development/mob/lib/mishka_mob/showcase/components/collapsible.ex:70 — development/mob/lib/mishka_mob/showcase/components/collapsible.ex:70-117 | development/mob/lib/mishka_mob/showcase/components/highlight.ex:97-129 | development/mob/lib/mishka_mob/showcase/components/pill.ex:118-174 | development/mob/lib/mishka_mob/showcase/components/rolling_number.ex:88-116 | development/mob/lib/mishka_mob/showcase/components/switch.ex:76-120 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/collapsible.ex` and `development/mob/lib/mishka_mob/showcase/components/highlight.ex` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 269 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/collapsible.ex:70` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (9–56 lines × 4) · ×1
  • Duplicated block (9–56 lines × 4) development/mob/lib/mishka_mob/showcase/components/calendar.ex:162 — development/mob/lib/mishka_mob/showcase/components/calendar.ex:162-217 | development/mob/lib/mishka_mob/showcase/components/nav_link.ex:115-123 | development/mob/lib/mishka_mob/showcase/components/slider.ex:146-163 | development/mob/lib/mishka_mob/showcase/components/tree.ex:210-218 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/calendar.ex` and `development/mob/lib/mishka_mob/showcase/components/nav_link.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 202 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/calendar.ex:162` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (41–56 lines × 3) · ×1
  • Duplicated block (41–56 lines × 3) development/mob/lib/mishka_mob/showcase/components/calendar.ex:180 — development/mob/lib/mishka_mob/showcase/components/calendar.ex:180-222 | development/mob/lib/mishka_mob/showcase/components/nav_link.ex:177-217 | development/mob/lib/mishka_mob/showcase/components/tooltip.ex:84-139 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/calendar.ex` and `development/mob/lib/mishka_mob/showcase/components/nav_link.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 202 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/calendar.ex:180` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (50–55 lines × 2) · ×1
  • Duplicated block (50–55 lines × 2) development/mob/lib/mishka_mob/showcase/components/highlight.ex:61 — development/mob/lib/mishka_mob/showcase/components/highlight.ex:61-115 | development/mob/lib/mishka_mob/showcase/components/overflow_list.ex:110-159 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/highlight.ex` and `development/mob/lib/mishka_mob/showcase/components/overflow_list.ex` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 392 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/highlight.ex:61` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (53–55 lines × 2) · ×1
  • Duplicated block (53–55 lines × 2) development/mob/lib/mishka_mob/showcase/components/menu.ex:126 — development/mob/lib/mishka_mob/showcase/components/menu.ex:126-178 | development/mob/lib/mishka_mob/showcase/components/skeleton.ex:84-138 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/menu.ex` and `development/mob/lib/mishka_mob/showcase/components/skeleton.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 153 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/menu.ex:126` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (33–54 lines × 8) · ×1
  • Duplicated block (33–54 lines × 8) development/mob/lib/mishka_mob/showcase/components/action_icon.ex:102 — development/mob/lib/mishka_mob/showcase/components/action_icon.ex:102-146 | development/mob/lib/mishka_mob/showcase/components/empty_state.ex:31-79 | development/mob/lib/mishka_mob/showcase/components/menu.ex:121-174 | development/mob/lib/mishka_mob/showcase/components/meter.ex:71-121 | development/mob/lib/mishka_mob/showcase/components/progress.ex:74-106 | development/mob/lib/mishka_mob/showcase/components/rating.ex:49-87 | development/mob/lib/mishka_mob/showcase/components/skeleton.ex:80-130 | development/mob/lib/mishka_mob/showcase/components/toast.ex:79-122 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/action_icon.ex` and `development/mob/lib/mishka_mob/showcase/components/empty_state.ex` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 245 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/action_icon.ex:102` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (37–54 lines × 6) · ×1
  • Duplicated block (37–54 lines × 6) development/mob/lib/mishka_mob/showcase/components/chip.ex:55 — development/mob/lib/mishka_mob/showcase/components/chip.ex:55-97 | development/mob/lib/mishka_mob/showcase/components/nav_link.ex:217-270 | development/mob/lib/mishka_mob/showcase/components/pill.ex:112-158 | development/mob/lib/mishka_mob/showcase/components/switch.ex:70-106 | development/mob/lib/mishka_mob/showcase/components/tabs.ex:61-114 | development/mob/lib/mishka_mob/showcase/components/tree.ex:395-434 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/chip.ex` and `development/mob/lib/mishka_mob/showcase/components/nav_link.ex` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 372 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/chip.ex:55` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (41–54 lines × 3) · ×1
  • Duplicated block (41–54 lines × 3) development/mob/lib/mishka_mob/showcase/components/nav_link.ex:235 — development/mob/lib/mishka_mob/showcase/components/nav_link.ex:235-280 | development/mob/lib/mishka_mob/showcase/components/tabs.ex:81-134 | development/mob/lib/mishka_mob/showcase/components/tree.ex:147-187 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/nav_link.ex` and `development/mob/lib/mishka_mob/showcase/components/tabs.ex` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 603 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/nav_link.ex:235` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (24–53 lines × 5) · ×1
  • Duplicated block (24–53 lines × 5) development/mob/lib/mishka_mob/showcase/components/highlight.ex:127 — development/mob/lib/mishka_mob/showcase/components/highlight.ex:127-164 | development/mob/lib/mishka_mob/showcase/components/mark.ex:84-107 | development/mob/lib/mishka_mob/showcase/components/pill.ex:208-236 | development/mob/lib/mishka_mob/showcase/components/rating.ex:46-86 | development/mob/lib/mishka_mob/showcase/components/skeleton.ex:77-129 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/highlight.ex` and `development/mob/lib/mishka_mob/showcase/components/mark.ex` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/highlight.ex:127` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (40–53 lines × 2) · ×1
  • Duplicated block (40–53 lines × 2) development/mob/lib/mishka_mob/showcase/components/calendar.ex:256 — development/mob/lib/mishka_mob/showcase/components/calendar.ex:256-295 | development/mob/lib/mishka_mob/showcase/components/tooltip.ex:99-151 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/calendar.ex` and `development/mob/lib/mishka_mob/showcase/components/tooltip.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 153 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/calendar.ex:256` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (24–53 lines × 2) · ×1
  • Duplicated block (24–53 lines × 2) development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex:96 — development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex:96-148 | development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex:38-61 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex` and `development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex:96` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10–52 lines × 4) · ×1
  • Duplicated block (10–52 lines × 4) development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex:100 — development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex:100-109 | development/mob/lib/mishka_mob/showcase/components/nav_link.ex:237-281 | development/mob/lib/mishka_mob/showcase/components/tabs.ex:83-134 | development/mob/lib/mishka_mob/showcase/components/tree.ex:147-187 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex` and `development/mob/lib/mishka_mob/showcase/components/nav_link.ex` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 434 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex:100` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (11–50 lines × 9) · ×1
  • Duplicated block (11–50 lines × 9) development/mob/lib/mishka_mob/showcase/components/checkbox.ex:59 — development/mob/lib/mishka_mob/showcase/components/checkbox.ex:59-103 | development/mob/lib/mishka_mob/showcase/components/collapsible.ex:67-116 | development/mob/lib/mishka_mob/showcase/components/combobox.ex:188-210 | development/mob/lib/mishka_mob/showcase/components/highlight.ex:94-128 | development/mob/lib/mishka_mob/showcase/components/meter.ex:66-98 | development/mob/lib/mishka_mob/showcase/components/overflow_list.ex:129-175 | development/mob/lib/mishka_mob/showcase/components/progress.ex:69-88 | development/mob/lib/mishka_mob/showcase/components/radio.ex:31-78 | development/mob/lib/mishka_mob/showcase/components/toggle.ex:86-96 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/checkbox.ex` and `development/mob/lib/mishka_mob/showcase/components/collapsible.ex` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 368 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/checkbox.ex:59` it does not close everything it opens, so those exact lines cannot be lifted as they stand — 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (21–50 lines × 6) · ×1
  • Duplicated block (21–50 lines × 6) development/mob/lib/mishka_mob/showcase/components/highlight.ex:126 — development/mob/lib/mishka_mob/showcase/components/highlight.ex:126-161 | development/mob/lib/mishka_mob/showcase/components/mark.ex:84-104 | development/mob/lib/mishka_mob/showcase/components/pill.ex:208-233 | development/mob/lib/mishka_mob/showcase/components/rating.ex:45-82 | development/mob/lib/mishka_mob/showcase/components/rolling_number.ex:113-153 | development/mob/lib/mishka_mob/showcase/components/skeleton.ex:76-125 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/highlight.ex` and `development/mob/lib/mishka_mob/showcase/components/mark.ex` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/highlight.ex:126` it does not close everything it opens, so those exact lines cannot be lifted as they stand — 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (25–50 lines × 2) · ×1
  • Duplicated block (25–50 lines × 2) development/mob/lib/mishka_mob/showcase/components/popover.ex:77 — development/mob/lib/mishka_mob/showcase/components/popover.ex:77-126 | development/mob/lib/mishka_mob/showcase/components/preview_card.ex:171-195 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/popover.ex` and `development/mob/lib/mishka_mob/showcase/components/preview_card.ex` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 480 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/popover.ex:77` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (25–49 lines × 8) · ×1
  • Duplicated block (25–49 lines × 8) development/mob/lib/mishka_mob/showcase/components/checkbox.ex:45 — development/mob/lib/mishka_mob/showcase/components/checkbox.ex:45-93 | development/mob/lib/mishka_mob/showcase/components/collapsible.ex:53-101 | development/mob/lib/mishka_mob/showcase/components/combobox.ex:127-165 | development/mob/lib/mishka_mob/showcase/components/highlight.ex:72-117 | development/mob/lib/mishka_mob/showcase/components/json_input.ex:75-111 | development/mob/lib/mishka_mob/showcase/components/number_field.ex:131-163 | development/mob/lib/mishka_mob/showcase/components/overflow_list.ex:120-161 | development/mob/lib/mishka_mob/showcase/components/tags_input.ex:55-79 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/checkbox.ex` and `development/mob/lib/mishka_mob/showcase/components/collapsible.ex` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 368 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/checkbox.ex:45` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (20–48 lines × 8) · ×1
  • Duplicated block (20–48 lines × 8) development/mob/lib/mishka_mob/showcase/components/checkbox.ex:57 — development/mob/lib/mishka_mob/showcase/components/checkbox.ex:57-100 | development/mob/lib/mishka_mob/showcase/components/collapsible.ex:65-112 | development/mob/lib/mishka_mob/showcase/components/combobox.ex:188-207 | development/mob/lib/mishka_mob/showcase/components/highlight.ex:92-124 | development/mob/lib/mishka_mob/showcase/components/json_input.ex:80-127 | development/mob/lib/mishka_mob/showcase/components/number_field.ex:131-171 | development/mob/lib/mishka_mob/showcase/components/overflow_list.ex:127-172 | development/mob/lib/mishka_mob/showcase/components/tags_input.ex:102-125 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/checkbox.ex` and `development/mob/lib/mishka_mob/showcase/components/collapsible.ex` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 368 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/checkbox.ex:57` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (27–48 lines × 6) · ×1
  • Duplicated block (27–48 lines × 6) development/mob/lib/mishka_mob/showcase/components/highlight.ex:117 — development/mob/lib/mishka_mob/showcase/components/highlight.ex:117-154 | development/mob/lib/mishka_mob/showcase/components/mark.ex:34-61 | development/mob/lib/mishka_mob/showcase/components/pill.ex:160-186 | development/mob/lib/mishka_mob/showcase/components/rating.ex:34-75 | development/mob/lib/mishka_mob/showcase/components/rolling_number.ex:98-145 | development/mob/lib/mishka_mob/showcase/components/skeleton.ex:74-106 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/highlight.ex` and `development/mob/lib/mishka_mob/showcase/components/mark.ex` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/highlight.ex:117` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (24–45 lines × 2) · ×1
  • Duplicated block (24–45 lines × 2) development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex:72 — development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex:72-116 | development/mob/lib/mishka_mob/showcase/components/nav_link.ex:61-84 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex` and `development/mob/lib/mishka_mob/showcase/components/nav_link.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex:72` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (21–44 lines × 3) · ×1
  • Duplicated block (21–44 lines × 3) development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex:135 — development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex:135-155 | development/mob/lib/mishka_mob/showcase/components/nav_link.ex:260-293 | development/mob/lib/mishka_mob/showcase/components/radio_group.ex:140-183 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex` and `development/mob/lib/mishka_mob/showcase/components/nav_link.ex` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 434 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex:135` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (9–42 lines × 2) · ×1
  • Duplicated block (9–42 lines × 2) development/mob/lib/mishka_mob/showcase/components/slider.ex:146 — development/mob/lib/mishka_mob/showcase/components/slider.ex:146-187 | development/mob/lib/mishka_mob/showcase/components/tree.ex:284-292 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/slider.ex` and `development/mob/lib/mishka_mob/showcase/components/tree.ex` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 416 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/slider.ex:146` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (39 lines × 5) · ×1
  • Duplicated block (39 lines × 5) development/mob/lib/mishka_mob/showcase/components/angle_slider.ex:32 — development/mob/lib/mishka_mob/showcase/components/angle_slider.ex:32-80 | development/mob/lib/mishka_mob/showcase/components/color_picker.ex:68-106 | development/mob/lib/mishka_mob/showcase/components/floating_window.ex:180-222 | development/mob/lib/mishka_mob/showcase/components/tree.ex:395-458 | development/mob/lib/mishka_mob/showcase/components/tree_select.ex:205-261 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/angle_slider.ex` and `development/mob/lib/mishka_mob/showcase/components/color_picker.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 169 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/angle_slider.ex:32` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (38 lines × 8) · ×1
  • Duplicated block (38 lines × 8) development/mob/lib/mishka_mob/showcase/components/angle_slider.ex:31 — development/mob/lib/mishka_mob/showcase/components/angle_slider.ex:31-79 | development/mob/lib/mishka_mob/showcase/components/color_picker.ex:68-105 | development/mob/lib/mishka_mob/showcase/components/floating_window.ex:179-221 | development/mob/lib/mishka_mob/showcase/components/nav_link.ex:234-277 | development/mob/lib/mishka_mob/showcase/components/tabs.ex:80-131 | development/mob/lib/mishka_mob/showcase/components/tree.ex:147-187 | development/mob/lib/mishka_mob/showcase/components/tree.ex:395-457 | development/mob/lib/mishka_mob/showcase/components/tree_select.ex:204-260 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/angle_slider.ex` and `development/mob/lib/mishka_mob/showcase/components/color_picker.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 169 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/color_picker.ex:68` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (26–38 lines × 3) · ×1
  • Duplicated block (26–38 lines × 3) development/mob/lib/mishka_mob/showcase/components/nav_link.ex:279 — development/mob/lib/mishka_mob/showcase/components/nav_link.ex:279-304 | development/mob/lib/mishka_mob/showcase/components/text_input.ex:34-71 | development/mob/lib/mishka_mob/showcase/components/tooltip.ex:84-114 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/nav_link.ex` and `development/mob/lib/mishka_mob/showcase/components/text_input.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/nav_link.ex:279` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (37 lines × 7) · ×1
  • Duplicated block (37 lines × 7) development/mob/lib/mishka_mob/showcase/components/chip.ex:57 — development/mob/lib/mishka_mob/showcase/components/chip.ex:57-97 | development/mob/lib/mishka_mob/showcase/components/nav_link.ex:219-270 | development/mob/lib/mishka_mob/showcase/components/pill.ex:112-158 | development/mob/lib/mishka_mob/showcase/components/switch.ex:70-106 | development/mob/lib/mishka_mob/showcase/components/tabs.ex:63-114 | development/mob/lib/mishka_mob/showcase/components/tree.ex:395-434 | development/mob/lib/mishka_mob/showcase/components/tree_select.ex:195-244 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/chip.ex` and `development/mob/lib/mishka_mob/showcase/components/nav_link.ex` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 372 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/chip.ex:57` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (34 lines × 8) · ×1
  • Duplicated block (34 lines × 8) development/mob/lib/mishka_mob/showcase/components/action_icon.ex:134 — development/mob/lib/mishka_mob/showcase/components/action_icon.ex:134-181 | development/mob/lib/mishka_mob/showcase/components/card.ex:47-80 | development/mob/lib/mishka_mob/showcase/components/card.ex:220-278 | development/mob/lib/mishka_mob/showcase/components/list_item.ex:59-117 | development/mob/lib/mishka_mob/showcase/components/text_input.ex:86-128 | development/mob/lib/mishka_mob/showcase/components/toast.ex:110-175 | development/mob/lib/mishka_mob/showcase/components/tooltip.ex:224-276 | development/mob/lib/mishka_mob/showcase/components/tree_select.ex:169-221 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/action_icon.ex` and `development/mob/lib/mishka_mob/showcase/components/card.ex` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 312 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/action_icon.ex:134` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (27 lines × 8) · ×1
  • Duplicated block (27 lines × 8) development/mob/lib/mishka_mob/showcase/components/highlight.ex:47 — development/mob/lib/mishka_mob/showcase/components/highlight.ex:47-99 | development/mob/lib/mishka_mob/showcase/components/highlight.ex:117-152 | development/mob/lib/mishka_mob/showcase/components/mark.ex:34-61 | development/mob/lib/mishka_mob/showcase/components/pill.ex:160-186 | development/mob/lib/mishka_mob/showcase/components/preview_card.ex:196-277 | development/mob/lib/mishka_mob/showcase/components/rating.ex:34-73 | development/mob/lib/mishka_mob/showcase/components/rolling_number.ex:98-143 | development/mob/lib/mishka_mob/showcase/components/skeleton.ex:74-104 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/highlight.ex` and `development/mob/lib/mishka_mob/showcase/components/mark.ex` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 592 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/highlight.ex:47` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (91 lines × 4) · ×1
  • Duplicated block (91 lines × 4) development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:3225 — development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:3225-3315 | development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:3380-3470 | development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:8455-8545 | development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:8611-8701 — before extracting anything, compare `development/web/lib/development_web/live/showcase/headless_baseui_examples.ex` and `development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (21–25 lines × 3) · ×1
  • Duplicated block (21–25 lines × 3) development/mob/lib/mishka_mob/showcase/components/action_icon.ex:242 — development/mob/lib/mishka_mob/showcase/components/action_icon.ex:242-262 | development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex:283-307 | development/mob/lib/mishka_mob/showcase/components/drawer.ex:459-483 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/action_icon.ex` and `development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 199 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/action_icon.ex:242` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (24 lines × 5) · ×1
  • Duplicated block (24 lines × 5) development/mob/lib/mishka_mob/showcase/components/card.ex:129 — development/mob/lib/mishka_mob/showcase/components/card.ex:129-191 | development/mob/lib/mishka_mob/showcase/components/popover.ex:65-125 | development/mob/lib/mishka_mob/showcase/components/preview_card.ex:171-194 | development/mob/lib/mishka_mob/showcase/components/tooltip.ex:199-260 | development/mob/lib/mishka_mob/showcase/components/tree_select.ex:141-193 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/card.ex` and `development/mob/lib/mishka_mob/showcase/components/popover.ex` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 363 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/card.ex:129` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×1
  • Duplicated block (24 lines × 2) development/mob/lib/mishka_mob/showcase/components/action_icon.ex:244 — development/mob/lib/mishka_mob/showcase/components/action_icon.ex:244-267 | development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex:313-336 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/action_icon.ex` and `development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 199 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/action_icon.ex:244` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (8–23 lines × 65) · ×1
  • Duplicated block (8–23 lines × 65) development/mob/lib/mishka_mob/showcase/components/accordion.ex:216 — development/mob/lib/mishka_mob/showcase/components/accordion.ex:216-235 | development/mob/lib/mishka_mob/showcase/components/action_icon.ex:256-276 | development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex:325-345 | development/mob/lib/mishka_mob/showcase/components/alpha_slider.ex:84-96 | development/mob/lib/mishka_mob/showcase/components/angle_slider.ex:87-94 | development/mob/lib/mishka_mob/showcase/components/autocomplete.ex:192-211 | development/mob/lib/mishka_mob/showcase/components/avatar.ex:119-133 | development/mob/lib/mishka_mob/showcase/components/calendar.ex:534-556 | development/mob/lib/mishka_mob/showcase/components/card.ex:312-331 | development/mob/lib/mishka_mob/showcase/components/card.ex:369-384 | development/mob/lib/mishka_mob/showcase/components/checkbox.ex:131-148 | development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex:179-192 | development/mob/lib/mishka_mob/showcase/components/chip.ex:133-151 | development/mob/lib/mishka_mob/showcase/components/code.ex:108-125 | development/mob/lib/mishka_mob/showcase/components/collapsible.ex:162-180 | development/mob/lib/mishka_mob/showcase/components/color_input.ex:130-143 | development/mob/lib/mishka_mob/showcase/components/color_swatch.ex:144-156 | development/mob/lib/mishka_mob/showcase/components/combobox.ex:239-253 | development/mob/lib/mishka_mob/showcase/components/dialog.ex:245-259 | development/mob/lib/mishka_mob/showcase/components/dock.ex:116-135 | development/mob/lib/mishka_mob/showcase/components/drawer.ex:333-353 | development/mob/lib/mishka_mob/showcase/components/empty_state.ex:170-184 | development/mob/lib/mishka_mob/showcase/components/field.ex:255-273 | development/mob/lib/mishka_mob/showcase/components/floating_window.ex:471-486 | development/mob/lib/mishka_mob/showcase/components/highlight.ex:186-204 | development/mob/lib/mishka_mob/showcase/components/hue_slider.ex:74-83 | development/mob/lib/mishka_mob/showcase/components/json_input.ex:139-158 | development/mob/lib/mishka_mob/showcase/components/list_item.ex:162-181 | development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex:295-314 | development/mob/lib/mishka_mob/showcase/components/menu.ex:264-278 | development/mob/lib/mishka_mob/showcase/components/nav_link.ex:327-346 | development/mob/lib/mishka_mob/showcase/components/number_field.ex:179-197 | development/mob/lib/mishka_mob/showcase/components/otp_field.ex:210-224 | development/mob/lib/mishka_mob/showcase/components/overflow_list.ex:286-305 | development/mob/lib/mishka_mob/showcase/components/pill.ex:277-296 | development/mob/lib/mishka_mob/showcase/components/popover.ex:344-364 | development/mob/lib/mishka_mob/showcase/components/popover.ex:455-475 | development/mob/lib/mishka_mob/showcase/components/preview_card.ex:327-347 | development/mob/lib/mishka_mob/showcase/components/progress.ex:164-173 | development/mob/lib/mishka_mob/showcase/components/radio.ex:116-129 | development/mob/lib/mishka_mob/showcase/components/radio_group.ex:205-218 | development/mob/lib/mishka_mob/showcase/components/rating.ex:114-123 | development/mob/lib/mishka_mob/showcase/components/rolling_number.ex:161-179 | development/mob/lib/mishka_mob/showcase/components/scroll_area.ex:100-120 | development/mob/lib/mishka_mob/showcase/components/segmented_control.ex:294-308 | development/mob/lib/mishka_mob/showcase/components/select.ex:179-197 | development/mob/lib/mishka_mob/showcase/components/semi_circle_progress.ex:113-127 | development/mob/lib/mishka_mob/showcase/components/separator.ex:124-143 | development/mob/lib/mishka_mob/showcase/components/skeleton.ex:169-182 | development/mob/lib/mishka_mob/showcase/components/slider.ex:199-213 | development/mob/lib/mishka_mob/showcase/components/splitter.ex:162-180 | development/mob/lib/mishka_mob/showcase/components/spoiler.ex:116-134 | development/mob/lib/mishka_mob/showcase/components/switch.ex:162-181 | development/mob/lib/mishka_mob/showcase/components/tabs.ex:203-222 | development/mob/lib/mishka_mob/showcase/components/tags_input.ex:133-146 | development/mob/lib/mishka_mob/showcase/components/text_input.ex:154-173 | development/mob/lib/mishka_mob/showcase/components/text_input.ex:179-199 | development/mob/lib/mishka_mob/showcase/components/theme_icon.ex:397-417 | development/mob/lib/mishka_mob/showcase/components/toast.ex:198-217 | development/mob/lib/mishka_mob/showcase/components/toggle.ex:223-237 | development/mob/lib/mishka_mob/showcase/components/toggle_group.ex:345-364 | development/mob/lib/mishka_mob/showcase/components/toolbar.ex:452-471 | development/mob/lib/mishka_mob/showcase/components/tooltip.ex:295-313 | development/mob/lib/mishka_mob/showcase/components/tree.ex:469-489 | development/mob/lib/mishka_mob/showcase/components/tree_select.ex:272-291 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/accordion.ex` and `development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/accordion.ex:216` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (23 lines × 3) · ×1
  • Duplicated block (23 lines × 3) development/mob/lib/mishka_mob/showcase/components/color_input.ex:83 — development/mob/lib/mishka_mob/showcase/components/color_input.ex:83-119 | development/mob/lib/mishka_mob/showcase/components/context_menu.ex:37-90 | development/mob/lib/mishka_mob/showcase/components/semi_circle_progress.ex:80-102 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/color_input.ex` and `development/mob/lib/mishka_mob/showcase/components/context_menu.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 214 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/color_input.ex:83` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (22 lines × 10) · ×1
  • Duplicated block (22 lines × 10) development/mob/lib/mishka_mob/showcase/components/action_icon.ex:29 — development/mob/lib/mishka_mob/showcase/components/action_icon.ex:29-97 | development/mob/lib/mishka_mob/showcase/components/chip.ex:73-106 | development/mob/lib/mishka_mob/showcase/components/color_input.ex:83-118 | development/mob/lib/mishka_mob/showcase/components/color_swatch.ex:40-93 | development/mob/lib/mishka_mob/showcase/components/context_menu.ex:36-89 | development/mob/lib/mishka_mob/showcase/components/menu.ex:116-137 | development/mob/lib/mishka_mob/showcase/components/overflow_list.ex:84-127 | development/mob/lib/mishka_mob/showcase/components/pill.ex:114-169 | development/mob/lib/mishka_mob/showcase/components/semi_circle_progress.ex:80-101 | development/mob/lib/mishka_mob/showcase/components/switch.ex:72-115 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/action_icon.ex` and `development/mob/lib/mishka_mob/showcase/components/chip.ex` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 399 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/action_icon.ex:29` it does not close everything it opens, so those exact lines cannot be lifted as they stand — 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (22 lines × 7) · ×1
  • Duplicated block (22 lines × 7) development/mob/lib/mishka_mob/showcase/components/action_icon.ex:28 — development/mob/lib/mishka_mob/showcase/components/action_icon.ex:28-97 | development/mob/lib/mishka_mob/showcase/components/color_input.ex:83-117 | development/mob/lib/mishka_mob/showcase/components/color_swatch.ex:39-93 | development/mob/lib/mishka_mob/showcase/components/context_menu.ex:35-88 | development/mob/lib/mishka_mob/showcase/components/menu.ex:116-137 | development/mob/lib/mishka_mob/showcase/components/overflow_list.ex:84-127 | development/mob/lib/mishka_mob/showcase/components/semi_circle_progress.ex:32-53 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/action_icon.ex` and `development/mob/lib/mishka_mob/showcase/components/color_input.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/action_icon.ex:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (16–22 lines × 4) · ×1
  • Duplicated block (16–22 lines × 4) development/mob/lib/mishka_mob/showcase/components/action_icon.ex:241 — development/mob/lib/mishka_mob/showcase/components/action_icon.ex:241-256 | development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex:281-301 | development/mob/lib/mishka_mob/showcase/components/angle_slider.ex:96-117 | development/mob/lib/mishka_mob/showcase/components/drawer.ex:457-477 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/action_icon.ex` and `development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 199 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/action_icon.ex:241` it does not close everything it opens, so those exact lines cannot be lifted as they stand — 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (18–22 lines × 4) · ×1
  • Duplicated block (18–22 lines × 4) development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:252 — development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:252-271 | development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:347-364 | development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:367-384 | development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:480-501 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:248` calls `sections` and `development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:344` does not — 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.
D4 · Code Duplication · Duplicated block (14–21 lines × 21) · ×1
  • Duplicated block (14–21 lines × 21) development/mob/lib/mishka_mob/showcase/components/action_icon.ex:240 — development/mob/lib/mishka_mob/showcase/components/action_icon.ex:240-254 | development/mob/lib/mishka_mob/showcase/components/action_icon.ex:281-300 | development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex:279-299 | development/mob/lib/mishka_mob/showcase/components/alpha_slider.ex:96-110 | development/mob/lib/mishka_mob/showcase/components/angle_slider.ex:96-114 | development/mob/lib/mishka_mob/showcase/components/calendar.ex:521-541 | development/mob/lib/mishka_mob/showcase/components/calendar.ex:548-568 | development/mob/lib/mishka_mob/showcase/components/calendar.ex:569-588 | development/mob/lib/mishka_mob/showcase/components/card.ex:336-355 | development/mob/lib/mishka_mob/showcase/components/card.ex:356-375 | development/mob/lib/mishka_mob/showcase/components/color_input.ex:145-163 | development/mob/lib/mishka_mob/showcase/components/color_picker.ex:115-128 | development/mob/lib/mishka_mob/showcase/components/dock.ex:140-159 | development/mob/lib/mishka_mob/showcase/components/drawer.ex:456-475 | development/mob/lib/mishka_mob/showcase/components/empty_state.ex:182-202 | development/mob/lib/mishka_mob/showcase/components/hue_slider.ex:77-95 | development/mob/lib/mishka_mob/showcase/components/popover.ex:442-461 | development/mob/lib/mishka_mob/showcase/components/preview_card.ex:313-333 | development/mob/lib/mishka_mob/showcase/components/text_input.ex:166-185 | development/mob/lib/mishka_mob/showcase/components/toast.ex:219-237 | development/mob/lib/mishka_mob/showcase/components/tree_select.ex:290-309 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/action_icon.ex` and `development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 199 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/action_icon.ex:240` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20–21 lines × 17) · ×1
  • Duplicated block (20–21 lines × 17) development/mob/lib/mishka_mob/showcase/components/action_icon.ex:248 — development/mob/lib/mishka_mob/showcase/components/action_icon.ex:248-268 | development/mob/lib/mishka_mob/showcase/components/action_icon.ex:287-307 | development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex:317-337 | development/mob/lib/mishka_mob/showcase/components/calendar.ex:527-547 | development/mob/lib/mishka_mob/showcase/components/calendar.ex:554-574 | development/mob/lib/mishka_mob/showcase/components/calendar.ex:575-594 | development/mob/lib/mishka_mob/showcase/components/card.ex:342-361 | development/mob/lib/mishka_mob/showcase/components/card.ex:362-381 | development/mob/lib/mishka_mob/showcase/components/color_picker.ex:116-135 | development/mob/lib/mishka_mob/showcase/components/drawer.ex:325-345 | development/mob/lib/mishka_mob/showcase/components/empty_state.ex:189-208 | development/mob/lib/mishka_mob/showcase/components/hue_slider.ex:82-102 | development/mob/lib/mishka_mob/showcase/components/popover.ex:448-467 | development/mob/lib/mishka_mob/showcase/components/preview_card.ex:319-339 | development/mob/lib/mishka_mob/showcase/components/text_input.ex:172-191 | development/mob/lib/mishka_mob/showcase/components/toast.ex:224-244 | development/mob/lib/mishka_mob/showcase/components/tree_select.ex:296-316 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/action_icon.ex` and `development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 199 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/action_icon.ex:248` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (21 lines × 6) · ×1
  • Duplicated block (21 lines × 6) development/mob/lib/mishka_mob/showcase/components/chip.ex:40 — development/mob/lib/mishka_mob/showcase/components/chip.ex:40-90 | development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex:135-155 | development/mob/lib/mishka_mob/showcase/components/nav_link.ex:261-293 | development/mob/lib/mishka_mob/showcase/components/radio_group.ex:141-184 | development/mob/lib/mishka_mob/showcase/components/switch.ex:70-99 | development/mob/lib/mishka_mob/showcase/components/tabs.ex:41-106 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/chip.ex` and `development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 266 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/chip.ex:40` it does not close everything it opens, so those exact lines cannot be lifted as they stand — 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (20 lines × 14) · ×1
  • Duplicated block (20 lines × 14) development/mob/lib/mishka_mob/showcase/components/action_icon.ex:250 — development/mob/lib/mishka_mob/showcase/components/action_icon.ex:250-269 | development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex:319-338 | development/mob/lib/mishka_mob/showcase/components/calendar.ex:528-548 | development/mob/lib/mishka_mob/showcase/components/calendar.ex:556-575 | development/mob/lib/mishka_mob/showcase/components/calendar.ex:576-595 | development/mob/lib/mishka_mob/showcase/components/card.ex:343-362 | development/mob/lib/mishka_mob/showcase/components/card.ex:363-382 | development/mob/lib/mishka_mob/showcase/components/drawer.ex:327-346 | development/mob/lib/mishka_mob/showcase/components/empty_state.ex:190-209 | development/mob/lib/mishka_mob/showcase/components/popover.ex:449-468 | development/mob/lib/mishka_mob/showcase/components/preview_card.ex:300-320 | development/mob/lib/mishka_mob/showcase/components/preview_card.ex:321-340 | development/mob/lib/mishka_mob/showcase/components/text_input.ex:173-192 | development/mob/lib/mishka_mob/showcase/components/toast.ex:192-211 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/action_icon.ex` and `development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 199 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (20 lines × 6) · ×1
  • Duplicated block (20 lines × 6) development/mob/lib/mishka_mob/showcase/components/card.ex:148 — development/mob/lib/mishka_mob/showcase/components/card.ex:148-192 | development/mob/lib/mishka_mob/showcase/components/popover.ex:194-245 | development/mob/lib/mishka_mob/showcase/components/preview_card.ex:173-238 | development/mob/lib/mishka_mob/showcase/components/skeleton.ex:31-50 | development/mob/lib/mishka_mob/showcase/components/tooltip.ex:201-261 | development/mob/lib/mishka_mob/showcase/components/tree_select.ex:143-194 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/card.ex` and `development/mob/lib/mishka_mob/showcase/components/popover.ex` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 363 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/card.ex:148` it does not close everything it opens, so those exact lines cannot be lifted as they stand — 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (20 lines × 3) · ×1
  • Duplicated block (20 lines × 3) development/mob/lib/mishka_mob/showcase/components/action_icon.ex:243 — development/mob/lib/mishka_mob/showcase/components/action_icon.ex:243-262 | development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex:312-331 | development/mob/lib/mishka_mob/showcase/components/drawer.ex:464-484 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/action_icon.ex` and `development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 199 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/action_icon.ex:243` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (18 lines × 6) · ×1
  • Duplicated block (18 lines × 6) development/mob/lib/mishka_mob/showcase/components/autocomplete.ex:133 — development/mob/lib/mishka_mob/showcase/components/autocomplete.ex:133-157 | development/mob/lib/mishka_mob/showcase/components/segmented_control.ex:241-258 | development/mob/lib/mishka_mob/showcase/components/splitter.ex:73-141 | development/mob/lib/mishka_mob/showcase/components/spoiler.ex:63-105 | development/mob/lib/mishka_mob/showcase/components/tabs.ex:132-169 | development/mob/lib/mishka_mob/showcase/components/toggle_group.ex:256-273 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/autocomplete.ex` and `development/mob/lib/mishka_mob/showcase/components/segmented_control.ex` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 380 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/autocomplete.ex:133` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (16–17 lines × 2) · ×1
  • Duplicated block (16–17 lines × 2) development/mob/lib/mishka_mob/dice_screen.ex:34 — development/mob/lib/mishka_mob/dice_screen.ex:34-50 | development/mob/lib/mishka_mob/text_screen.ex:55-70 — before extracting anything, compare `development/mob/lib/mishka_mob/dice_screen.ex` and `development/mob/lib/mishka_mob/text_screen.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/dice_screen.ex:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (15–16 lines × 5) · ×1
  • Duplicated block (15–16 lines × 5) development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:251 — development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:251-265 | development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:320-335 | development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:346-360 | development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:366-380 | development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:479-493 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — 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 `development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:251` it does not close everything it opens, so those exact lines cannot be lifted as they stand — 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:248` calls `sections` and `development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:318` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) lib/mishka_chelekom/cms_bundle/heex.ex:177 — lib/mishka_chelekom/cms_bundle/heex.ex:177-191 | lib/mishka_chelekom/cms_bundle/heex.ex:215-229 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (14 lines × 54) · ×1
  • Duplicated block (14 lines × 54) development/mob/lib/mishka_mob/showcase/components/accordion.ex:282 — development/mob/lib/mishka_mob/showcase/components/accordion.ex:282-301 | development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex:338-357 | development/mob/lib/mishka_mob/showcase/components/autocomplete.ex:240-259 | development/mob/lib/mishka_mob/showcase/components/avatar.ex:132-146 | development/mob/lib/mishka_mob/showcase/components/card.ex:395-409 | development/mob/lib/mishka_mob/showcase/components/checkbox.ex:155-169 | development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex:222-241 | development/mob/lib/mishka_mob/showcase/components/chip.ex:150-169 | development/mob/lib/mishka_mob/showcase/components/code.ex:125-139 | development/mob/lib/mishka_mob/showcase/components/collapsible.ex:197-216 | development/mob/lib/mishka_mob/showcase/components/color_swatch.ex:158-176 | development/mob/lib/mishka_mob/showcase/components/combobox.ex:264-283 | development/mob/lib/mishka_mob/showcase/components/context_menu.ex:101-120 | development/mob/lib/mishka_mob/showcase/components/dialog.ex:318-337 | development/mob/lib/mishka_mob/showcase/components/empty_state.ex:196-216 | development/mob/lib/mishka_mob/showcase/components/field.ex:291-310 | development/mob/lib/mishka_mob/showcase/components/floating_window.ex:528-547 | development/mob/lib/mishka_mob/showcase/components/highlight.ex:215-229 | development/mob/lib/mishka_mob/showcase/components/json_input.ex:211-230 | development/mob/lib/mishka_mob/showcase/components/list_item.ex:174-193 | development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex:313-333 | development/mob/lib/mishka_mob/showcase/components/mark.ex:133-146 | development/mob/lib/mishka_mob/showcase/components/meter.ex:191-210 | development/mob/lib/mishka_mob/showcase/components/nav_link.ex:393-412 | development/mob/lib/mishka_mob/showcase/components/number_field.ex:246-265 | development/mob/lib/mishka_mob/showcase/components/otp_field.ex:277-296 | development/mob/lib/mishka_mob/showcase/components/overflow_list.ex:310-329 | development/mob/lib/mishka_mob/showcase/components/pill.ex:307-327 | development/mob/lib/mishka_mob/showcase/components/popover.ex:486-506 | development/mob/lib/mishka_mob/showcase/components/preview_card.ex:373-391 | development/mob/lib/mishka_mob/showcase/components/progress.ex:172-191 | development/mob/lib/mishka_mob/showcase/components/radio.ex:140-154 | development/mob/lib/mishka_mob/showcase/components/radio_group.ex:231-249 | development/mob/lib/mishka_mob/showcase/components/rating.ex:140-154 | development/mob/lib/mishka_mob/showcase/components/rolling_number.ex:166-185 | development/mob/lib/mishka_mob/showcase/components/scroll_area.ex:112-132 | development/mob/lib/mishka_mob/showcase/components/segmented_control.ex:374-393 | development/mob/lib/mishka_mob/showcase/components/select.ex:204-223 | development/mob/lib/mishka_mob/showcase/components/semi_circle_progress.ex:126-145 | development/mob/lib/mishka_mob/showcase/components/separator.ex:136-155 | development/mob/lib/mishka_mob/showcase/components/skeleton.ex:191-209 | development/mob/lib/mishka_mob/showcase/components/slider.ex:231-250 | development/mob/lib/mishka_mob/showcase/components/splitter.ex:191-210 | development/mob/lib/mishka_mob/showcase/components/spoiler.ex:136-155 | development/mob/lib/mishka_mob/showcase/components/switch.ex:180-199 | development/mob/lib/mishka_mob/showcase/components/tabs.ex:229-247 | development/mob/lib/mishka_mob/showcase/components/tags_input.ex:165-184 | development/mob/lib/mishka_mob/showcase/components/text_input.ex:192-211 | development/mob/lib/mishka_mob/showcase/components/theme_icon.ex:446-465 | development/mob/lib/mishka_mob/showcase/components/toggle.ex:278-292 | development/mob/lib/mishka_mob/showcase/components/toggle_group.ex:393-412 | development/mob/lib/mishka_mob/showcase/components/toolbar.ex:573-592 | development/mob/lib/mishka_mob/showcase/components/tooltip.ex:368-386 | development/mob/lib/mishka_mob/showcase/components/tree.ex:554-573 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/accordion.ex` and `development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/accordion.ex:282` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `development/mob/lib/mishka_mob/showcase/components/nav_link.ex:418` calls `handle`, `assign` and `development/mob/lib/mishka_mob/showcase/components/checkbox.ex:173` does not — 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.
D4 · Code Duplication · Duplicated block (14 lines × 10) · ×1
  • Duplicated block (14 lines × 10) development/mob/lib/mishka_mob/showcase/components/accordion.ex:80 — development/mob/lib/mishka_mob/showcase/components/accordion.ex:80-134 | development/mob/lib/mishka_mob/showcase/components/combobox.ex:115-165 | development/mob/lib/mishka_mob/showcase/components/json_input.ex:64-102 | development/mob/lib/mishka_mob/showcase/components/number_field.ex:65-102 | development/mob/lib/mishka_mob/showcase/components/radio_group.ex:70-140 | development/mob/lib/mishka_mob/showcase/components/segmented_control.ex:89-146 | development/mob/lib/mishka_mob/showcase/components/select.ex:76-147 | development/mob/lib/mishka_mob/showcase/components/slider.ex:56-102 | development/mob/lib/mishka_mob/showcase/components/tabs.ex:107-156 | development/mob/lib/mishka_mob/showcase/components/toggle_group.ex:161-174 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/accordion.ex` and `development/mob/lib/mishka_mob/showcase/components/combobox.ex` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 383 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/accordion.ex:80` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (43 lines × 2) · ×1
  • Duplicated block (43 lines × 2) development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:3061 — development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:3061-3103 | development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:10921-10963 — before extracting anything, compare `development/web/lib/development_web/live/showcase/headless_baseui_examples.ex` and `development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (11–12 lines × 4) · ×1
  • Duplicated block (11–12 lines × 4) development/web/lib/development_web/live/showcase/headless_preview.ex:2427 — development/web/lib/development_web/live/showcase/headless_preview.ex:2427-2438 | development/web/lib/development_web/live/showcase/headless_preview.ex:2467-2478 | development/web/lib/development_web/live/showcase/headless_preview.ex:2482-2492 | development/web/lib/development_web/live/showcase/headless_preview.ex:2523-2534 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — 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 `development/web/lib/development_web/live/showcase/headless_preview.ex:2427` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10 lines × 14) · ×1
  • Duplicated block (10 lines × 14) development/mob/lib/mishka_mob/showcase/components/avatar.ex:62 — development/mob/lib/mishka_mob/showcase/components/avatar.ex:62-108 | development/mob/lib/mishka_mob/showcase/components/checkbox.ex:85-124 | development/mob/lib/mishka_mob/showcase/components/chip.ex:91-126 | development/mob/lib/mishka_mob/showcase/components/code.ex:63-101 | development/mob/lib/mishka_mob/showcase/components/color_swatch.ex:94-137 | development/mob/lib/mishka_mob/showcase/components/combobox.ex:189-228 | development/mob/lib/mishka_mob/showcase/components/highlight.ex:146-179 | development/mob/lib/mishka_mob/showcase/components/mark.ex:85-126 | development/mob/lib/mishka_mob/showcase/components/overflow_list.ex:153-193 | development/mob/lib/mishka_mob/showcase/components/pill.ex:209-266 | development/mob/lib/mishka_mob/showcase/components/radio.ex:76-109 | development/mob/lib/mishka_mob/showcase/components/scroll_area.ex:45-89 | development/mob/lib/mishka_mob/showcase/components/separator.ex:66-113 | development/mob/lib/mishka_mob/showcase/components/toggle.ex:172-181 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/avatar.ex` and `development/mob/lib/mishka_mob/showcase/components/checkbox.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 190 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/avatar.ex:62` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (9 lines × 20) · ×1
  • Duplicated block (9 lines × 20) development/mob/lib/mishka_mob/showcase/components/action_icon.ex:275 — development/mob/lib/mishka_mob/showcase/components/action_icon.ex:275-294 | development/mob/lib/mishka_mob/showcase/components/alpha_slider.ex:91-104 | development/mob/lib/mishka_mob/showcase/components/angle_slider.ex:95-108 | development/mob/lib/mishka_mob/showcase/components/calendar.ex:542-562 | development/mob/lib/mishka_mob/showcase/components/calendar.ex:563-582 | development/mob/lib/mishka_mob/showcase/components/calendar.ex:583-602 | development/mob/lib/mishka_mob/showcase/components/card.ex:330-349 | development/mob/lib/mishka_mob/showcase/components/card.ex:350-369 | development/mob/lib/mishka_mob/showcase/components/color_input.ex:143-157 | development/mob/lib/mishka_mob/showcase/components/color_picker.ex:114-122 | development/mob/lib/mishka_mob/showcase/components/dock.ex:134-153 | development/mob/lib/mishka_mob/showcase/components/drawer.ex:450-469 | development/mob/lib/mishka_mob/showcase/components/empty_state.ex:177-196 | development/mob/lib/mishka_mob/showcase/components/hue_slider.ex:76-89 | development/mob/lib/mishka_mob/showcase/components/menu.ex:307-326 | development/mob/lib/mishka_mob/showcase/components/popover.ex:436-455 | development/mob/lib/mishka_mob/showcase/components/preview_card.ex:307-327 | development/mob/lib/mishka_mob/showcase/components/text_input.ex:160-179 | development/mob/lib/mishka_mob/showcase/components/toast.ex:217-231 | development/mob/lib/mishka_mob/showcase/components/tree_select.ex:284-303 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/action_icon.ex` and `development/mob/lib/mishka_mob/showcase/components/alpha_slider.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/action_icon.ex:275` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×1
  • Duplicated block (9 lines × 4) development/mob/lib/mishka_mob/showcase/components/calendar.ex:175 — development/mob/lib/mishka_mob/showcase/components/calendar.ex:175-220 | development/mob/lib/mishka_mob/showcase/components/nav_link.ex:177-189 | development/mob/lib/mishka_mob/showcase/components/slider.ex:146-170 | development/mob/lib/mishka_mob/showcase/components/tree.ex:284-292 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/calendar.ex` and `development/mob/lib/mishka_mob/showcase/components/nav_link.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 202 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/calendar.ex:175` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×1
  • Duplicated block (9 lines × 3) development/web/lib/development_web/live/showcase/headless_form_demos.ex:207 — development/web/lib/development_web/live/showcase/headless_form_demos.ex:207-215 | development/web/lib/development_web/live/showcase/headless_form_demos.ex:1085-1093 | development/web/lib/development_web/live/showcase/headless_form_demos.ex:1191-1199 — 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 — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (8–9 lines × 3) · ×1
  • Duplicated block (8–9 lines × 3) lib/mix/tasks/mishka.ui.gen.component.ex:134 — lib/mix/tasks/mishka.ui.gen.component.ex:134-141 | lib/mix/tasks/mishka.ui.gen.headless.ex:95-103 | lib/mix/tasks/mishka.ui.gen.mob.ex:159-167 — 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 — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/mix/tasks/mishka.ui.gen.component.ex:134` it does not close everything it opens, so those exact lines cannot be lifted as they stand — 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `lib/mix/tasks/mishka.ui.gen.mob.ex:169` calls `join`, `all_component_names` and `lib/mix/tasks/mishka.ui.gen.headless.ex:106` does not — after which the two agree again for 3 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.
D4 · Code Duplication · Duplicated block (8 lines × 68) · ×1
  • Duplicated block (8 lines × 68) development/mob/lib/mishka_mob/showcase/components/accordion.ex:211 — development/mob/lib/mishka_mob/showcase/components/accordion.ex:211-229 | development/mob/lib/mishka_mob/showcase/components/action_icon.ex:258-276 | development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex:327-345 | development/mob/lib/mishka_mob/showcase/components/alpha_slider.ex:83-91 | development/mob/lib/mishka_mob/showcase/components/angle_slider.ex:86-93 | development/mob/lib/mishka_mob/showcase/components/autocomplete.ex:187-205 | development/mob/lib/mishka_mob/showcase/components/avatar.ex:114-127 | development/mob/lib/mishka_mob/showcase/components/calendar.ex:536-556 | development/mob/lib/mishka_mob/showcase/components/card.ex:307-325 | development/mob/lib/mishka_mob/showcase/components/card.ex:371-384 | development/mob/lib/mishka_mob/showcase/components/checkbox.ex:130-143 | development/mob/lib/mishka_mob/showcase/components/checkbox_group.ex:178-186 | development/mob/lib/mishka_mob/showcase/components/chip.ex:132-145 | development/mob/lib/mishka_mob/showcase/components/code.ex:107-120 | development/mob/lib/mishka_mob/showcase/components/collapsible.ex:161-174 | development/mob/lib/mishka_mob/showcase/components/color_input.ex:125-138 | development/mob/lib/mishka_mob/showcase/components/color_swatch.ex:143-151 | development/mob/lib/mishka_mob/showcase/components/combobox.ex:234-247 | development/mob/lib/mishka_mob/showcase/components/context_menu.ex:96-114 | development/mob/lib/mishka_mob/showcase/components/dialog.ex:240-257 | development/mob/lib/mishka_mob/showcase/components/dock.ex:111-129 | development/mob/lib/mishka_mob/showcase/components/drawer.ex:335-353 | development/mob/lib/mishka_mob/showcase/components/empty_state.ex:169-177 | development/mob/lib/mishka_mob/showcase/components/field.ex:254-267 | development/mob/lib/mishka_mob/showcase/components/floating_window.ex:466-484 | development/mob/lib/mishka_mob/showcase/components/highlight.ex:185-198 | development/mob/lib/mishka_mob/showcase/components/hue_slider.ex:69-77 | development/mob/lib/mishka_mob/showcase/components/json_input.ex:134-152 | development/mob/lib/mishka_mob/showcase/components/list_item.ex:157-175 | development/mob/lib/mishka_mob/showcase/components/loading_overlay.ex:290-308 | development/mob/lib/mishka_mob/showcase/components/mark.ex:132-144 | development/mob/lib/mishka_mob/showcase/components/menu.ex:259-272 | development/mob/lib/mishka_mob/showcase/components/meter.ex:177-184 | development/mob/lib/mishka_mob/showcase/components/nav_link.ex:322-340 | development/mob/lib/mishka_mob/showcase/components/number_field.ex:178-191 | development/mob/lib/mishka_mob/showcase/components/otp_field.ex:209-218 | development/mob/lib/mishka_mob/showcase/components/overflow_list.ex:281-299 | development/mob/lib/mishka_mob/showcase/components/pill.ex:272-290 | development/mob/lib/mishka_mob/showcase/components/popover.ex:339-358 | development/mob/lib/mishka_mob/showcase/components/popover.ex:457-475 | development/mob/lib/mishka_mob/showcase/components/preview_card.ex:329-347 | development/mob/lib/mishka_mob/showcase/components/progress.ex:159-167 | development/mob/lib/mishka_mob/showcase/components/radio.ex:115-127 | development/mob/lib/mishka_mob/showcase/components/radio_group.ex:204-212 | development/mob/lib/mishka_mob/showcase/components/rating.ex:109-121 | development/mob/lib/mishka_mob/showcase/components/rolling_number.ex:160-173 | development/mob/lib/mishka_mob/showcase/components/scroll_area.ex:95-114 | development/mob/lib/mishka_mob/showcase/components/segmented_control.ex:289-302 | development/mob/lib/mishka_mob/showcase/components/select.ex:174-192 | development/mob/lib/mishka_mob/showcase/components/semi_circle_progress.ex:108-121 | development/mob/lib/mishka_mob/showcase/components/separator.ex:119-137 | development/mob/lib/mishka_mob/showcase/components/skeleton.ex:164-181 | development/mob/lib/mishka_mob/showcase/components/slider.ex:194-207 | development/mob/lib/mishka_mob/showcase/components/splitter.ex:161-174 | development/mob/lib/mishka_mob/showcase/components/spoiler.ex:111-129 | development/mob/lib/mishka_mob/showcase/components/switch.ex:157-175 | development/mob/lib/mishka_mob/showcase/components/tabs.ex:198-216 | development/mob/lib/mishka_mob/showcase/components/tags_input.ex:132-140 | development/mob/lib/mishka_mob/showcase/components/text_input.ex:149-167 | development/mob/lib/mishka_mob/showcase/components/text_input.ex:181-199 | development/mob/lib/mishka_mob/showcase/components/theme_icon.ex:392-411 | development/mob/lib/mishka_mob/showcase/components/toast.ex:200-217 | development/mob/lib/mishka_mob/showcase/components/toggle.ex:218-235 | development/mob/lib/mishka_mob/showcase/components/toggle_group.ex:340-358 | development/mob/lib/mishka_mob/showcase/components/toolbar.ex:447-465 | development/mob/lib/mishka_mob/showcase/components/tooltip.ex:294-307 | development/mob/lib/mishka_mob/showcase/components/tree.ex:464-483 | development/mob/lib/mishka_mob/showcase/components/tree_select.ex:267-285 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/accordion.ex` and `development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/accordion.ex:211` it does not close everything it opens, so those exact lines cannot be lifted as they stand — 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×1
  • Duplicated block (8 lines × 4) development/mob/lib/mishka_mob/showcase/components/nav_link.ex:202 — development/mob/lib/mishka_mob/showcase/components/nav_link.ex:202-244 | development/mob/lib/mishka_mob/showcase/components/popover.ex:266-311 | development/mob/lib/mishka_mob/showcase/components/tooltip.ex:149-173 | development/mob/lib/mishka_mob/showcase/components/tree.ex:360-367 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/nav_link.ex` and `development/mob/lib/mishka_mob/showcase/components/popover.ex` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 447 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `development/mob/lib/mishka_mob/showcase/components/nav_link.ex:202` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — 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' 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 — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×1
  • Duplicated block (7 lines × 3) development/web/lib/development_web/live/showcase/headless_preview.ex:2414 — development/web/lib/development_web/live/showcase/headless_preview.ex:2414-2420 | development/web/lib/development_web/live/showcase/headless_preview.ex:2432-2438 | development/web/lib/development_web/live/showcase/headless_preview.ex:2486-2492 — 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 — 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 `development/web/lib/development_web/live/showcase/headless_preview.ex:2414` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×1
  • Duplicated block (6 lines × 3) development/mob/lib/mishka_mob/components/mishka_alpha_slider.ex:107 — development/mob/lib/mishka_mob/components/mishka_alpha_slider.ex:107-112 | development/mob/lib/mishka_mob/components/mishka_angle_slider.ex:170-175 | development/mob/lib/mishka_mob/components/mishka_hue_slider.ex:110-115 — 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 — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (4–6 lines × 4) · ×1
  • Duplicated block (4–6 lines × 4) development/mob/lib/mishka_mob/components/mishka_alpha_slider.ex:185 — development/mob/lib/mishka_mob/components/mishka_alpha_slider.ex:185-188 | development/mob/lib/mishka_mob/components/mishka_hue_slider.ex:180-183 | development/mob/lib/mishka_mob/components/mishka_progress.ex:407-412 | development/mob/lib/mishka_mob/components/mishka_slider.ex:279-284 — 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 — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. 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 — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `development/mob/lib/mishka_mob/components/mishka_progress.ex:412` calls `is_binary`, `MOB` and `development/mob/lib/mishka_mob/components/mishka_alpha_slider.ex:188` does not — 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.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1
  • Duplicated block (11 lines × 2) development/mob/lib/mishka_mob/dice_screen.ex:179 — development/mob/lib/mishka_mob/dice_screen.ex:179-189 | development/mob/lib/mishka_mob/text_screen.ex:113-123 — before extracting anything, compare `development/mob/lib/mishka_mob/dice_screen.ex` and `development/mob/lib/mishka_mob/text_screen.ex` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (33 lines × 6) · ×1
  • Duplicated block (33 lines × 6) development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex:62 — development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex:62-109 | development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex:156-201 | development/mob/lib/mishka_mob/showcase/components/theme_icon.ex:248-296 | development/mob/lib/mishka_mob/showcase/components/toolbar.ex:163-197 | development/mob/lib/mishka_mob/showcase/components/toolbar.ex:201-233 | development/mob/lib/mishka_mob/showcase/components/toolbar.ex:237-282 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex` and `development/mob/lib/mishka_mob/showcase/components/theme_icon.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 160 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (28 lines × 6) · ×1
  • Duplicated block (28 lines × 6) development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex:113 — development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex:113-152 | development/mob/lib/mishka_mob/showcase/components/theme_icon.ex:56-83 | development/mob/lib/mishka_mob/showcase/components/theme_icon.ex:327-361 | development/mob/lib/mishka_mob/showcase/components/toolbar.ex:80-110 | development/mob/lib/mishka_mob/showcase/components/toolbar.ex:114-159 | development/mob/lib/mishka_mob/showcase/components/toolbar.ex:317-361 — before extracting anything, compare `development/mob/lib/mishka_mob/showcase/components/alert_dialog.ex` and `development/mob/lib/mishka_mob/showcase/components/theme_icon.ex` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 160 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (5 lines × 26) · ×1
  • Duplicated block (5 lines × 26) development/web/lib/development_web/components/avatar.ex:587 — development/web/lib/development_web/components/avatar.ex:587-591 | development/web/lib/development_web/components/badge.ex:1010-1014 | development/web/lib/development_web/components/button.ex:2130-2134 | development/web/lib/development_web/components/card.ex:872-876 | development/web/lib/development_web/components/chat.ex:785-789 | development/web/lib/development_web/components/checkbox_card.ex:903-907 | development/web/lib/development_web/components/checkbox_field.ex:535-539 | development/web/lib/development_web/components/combobox.ex:1359-1363 | development/web/lib/development_web/components/file_field.ex:975-979 | development/web/lib/development_web/components/gallery.ex:370-374 | development/web/lib/development_web/components/indicator.ex:284-288 | development/web/lib/development_web/components/layout.ex:389-393 | development/web/lib/development_web/components/navbar.ex:676-680 | development/web/lib/development_web/components/pagination.ex:1559-1563 | development/web/lib/development_web/components/progress.ex:847-851 | development/web/lib/development_web/components/radio_field.ex:505-509 | development/web/lib/development_web/components/range_field.ex:453-457 | development/web/lib/development_web/components/rating.ex:548-552 | development/web/lib/development_web/components/shape.ex:158-162 | development/web/lib/development_web/components/spinner.ex:359-363 | development/web/lib/development_web/components/stat.ex:552-556 | development/web/lib/development_web/components/stepper.ex:1022-1026 | development/web/lib/development_web/components/table.ex:1288-1292 | development/web/lib/development_web/components/tabs.ex:1018-1022 | development/web/lib/development_web/components/timeline.ex:583-587 | development/web/lib/development_web/components/toggle_field.ex:333-337 — 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 — a file they already depend on, or a new one alongside them — and call it from all 26 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (5 lines × 5) · ×1
  • Duplicated block (5 lines × 5) development/web/lib/development_web/components/checkbox_card.ex:219 — development/web/lib/development_web/components/checkbox_card.ex:219-223 | development/web/lib/development_web/components/checkbox_field.ex:276-280 | development/web/lib/development_web/components/radio_card.ex:220-224 | development/web/lib/development_web/components/radio_field.ex:269-273 | development/web/lib/development_web/components/toggle_field.ex:144-148 — 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 — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (5 lines × 22) · ×1
  • Duplicated block (5 lines × 22) development/web/lib/development_web/components/checkbox_card.ex:893 — development/web/lib/development_web/components/checkbox_card.ex:893-897 | development/web/lib/development_web/components/checkbox_field.ex:525-529 | development/web/lib/development_web/components/color_field.ex:342-346 | development/web/lib/development_web/components/combobox.ex:1349-1353 | development/web/lib/development_web/components/core_components.ex:489-493 | development/web/lib/development_web/components/date_time_field.ex:1099-1103 | development/web/lib/development_web/components/email_field.ex:1058-1062 | development/web/lib/development_web/components/file_field.ex:965-969 | development/web/lib/development_web/components/input_field.ex:246-250 | development/web/lib/development_web/components/native_select.ex:711-715 | development/web/lib/development_web/components/number_field.ex:1058-1062 | development/web/lib/development_web/components/password_field.ex:1099-1103 | development/web/lib/development_web/components/radio_card.ex:890-894 | development/web/lib/development_web/components/radio_field.ex:495-499 | development/web/lib/development_web/components/range_field.ex:443-447 | development/web/lib/development_web/components/rating.ex:538-542 | development/web/lib/development_web/components/search_field.ex:1085-1089 | development/web/lib/development_web/components/tel_field.ex:1063-1067 | development/web/lib/development_web/components/text_field.ex:1066-1070 | development/web/lib/development_web/components/textarea_field.ex:1025-1029 | development/web/lib/development_web/components/toggle_field.ex:323-327 | development/web/lib/development_web/components/url_field.ex:1050-1054 — 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 — a file they already depend on, or a new one alongside them — and call it from all 22 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:2907 — development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:2907-2922 | development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:10842-10857 — before extracting anything, compare `development/web/lib/development_web/live/showcase/headless_baseui_examples.ex` and `development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:2986 — development/web/lib/development_web/live/showcase/headless_baseui_examples.ex:2986-3003 | development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex:11005-11022 — before extracting anything, compare `development/web/lib/development_web/live/showcase/headless_baseui_examples.ex` and `development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×1
  • Duplicated block (10 lines × 2) lib/mishka_chelekom/mcp/tools/generate_components.ex:56 — lib/mishka_chelekom/mcp/tools/generate_components.ex:56-65 | lib/mishka_chelekom/mcp/tools/uninstall_component.ex:48-57 — 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 — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (5 lines × 13) · ×1
  • Duplicated block (5 lines × 13) development/web/lib/development_web/components/color_field.ex:100 — development/web/lib/development_web/components/color_field.ex:100-104 | development/web/lib/development_web/components/date_time_field.ex:154-158 | development/web/lib/development_web/components/email_field.ex:129-133 | development/web/lib/development_web/components/number_field.ex:120-124 | development/web/lib/development_web/components/radio_field.ex:98-102 | development/web/lib/development_web/components/radio_field.ex:208-212 | development/web/lib/development_web/components/range_field.ex:108-112 | development/web/lib/development_web/components/search_field.ex:127-131 | development/web/lib/development_web/components/tel_field.ex:129-133 | development/web/lib/development_web/components/text_field.ex:132-136 | development/web/lib/development_web/components/textarea_field.ex:130-134 | development/web/lib/development_web/components/toggle_field.ex:82-86 | development/web/lib/development_web/components/url_field.ex:116-120 — there are 13 copies across 12 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 13 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Members sharing a duplicated core (47 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (47 members, 50+ identical tokens) development/web/lib/development_web/live/showcase/examples/accordion.ex:16 — development/web/lib/development_web/live/showcase/examples/accordion.ex:16-25 | development/web/lib/development_web/live/showcase/examples/alert.ex:16-25 | development/web/lib/development_web/live/showcase/examples/avatar.ex:16-26 | development/web/lib/development_web/live/showcase/examples/badge.ex:16-25 | development/web/lib/development_web/live/showcase/examples/banner.ex:20-28 | development/web/lib/development_web/live/showcase/examples/blockquote.ex:16-26 | development/web/lib/development_web/live/showcase/examples/breadcrumb.ex:16-24 | development/web/lib/development_web/live/showcase/examples/card.ex:16-25 | development/web/lib/development_web/live/showcase/examples/carousel.ex:19-27 | development/web/lib/development_web/live/showcase/examples/chat.ex:16-26 | development/web/lib/development_web/live/showcase/examples/checkbox_card.ex:16-24 | development/web/lib/development_web/live/showcase/examples/clipboard.ex:16-24 | development/web/lib/development_web/live/showcase/examples/combobox.ex:16-26 | development/web/lib/development_web/live/showcase/examples/device_mockup.ex:19-28 | development/web/lib/development_web/live/showcase/examples/divider.ex:16-25 | development/web/lib/development_web/live/showcase/examples/dock.ex:16-25 | development/web/lib/development_web/live/showcase/examples/drawer.ex:19-28 | development/web/lib/development_web/live/showcase/examples/dropdown.ex:16-25 | development/web/lib/development_web/live/showcase/examples/file_field.ex:22-30 | development/web/lib/development_web/live/showcase/examples/footer.ex:22-30 | development/web/lib/development_web/live/showcase/examples/gallery.ex:20-29 | development/web/lib/development_web/live/showcase/examples/jumbotron.ex:16-24 | development/web/lib/development_web/live/showcase/examples/keyboard.ex:16-27 | development/web/lib/development_web/live/showcase/examples/layout.ex:17-26 | development/web/lib/development_web/live/showcase/examples/list.ex:16-25 | development/web/lib/development_web/live/showcase/examples/mega_menu.ex:16-25 | development/web/lib/development_web/live/showcase/examples/modal.ex:21-28 | development/web/lib/development_web/live/showcase/examples/navbar.ex:16-24 | development/web/lib/development_web/live/showcase/examples/pagination.ex:20-41 | development/web/lib/development_web/live/showcase/examples/popover.ex:16-25 | development/web/lib/development_web/live/showcase/examples/progress.ex:16-24 | development/web/lib/development_web/live/showcase/examples/radio_card.ex:16-25 | development/web/lib/development_web/live/showcase/examples/rating.ex:16-23 | development/web/lib/development_web/live/showcase/examples/scroll_area.ex:16-24 | development/web/lib/development_web/live/showcase/examples/sidebar.ex:21-29 | development/web/lib/development_web/live/showcase/examples/skeleton.ex:16-24 | development/web/lib/development_web/live/showcase/examples/speed_dial.ex:19-26 | development/web/lib/development_web/live/showcase/examples/stat.ex:16-25 | development/web/lib/development_web/live/showcase/examples/stepper.ex:16-24 | development/web/lib/development_web/live/showcase/examples/table.ex:16-24 | development/web/lib/development_web/live/showcase/examples/table_content.ex:19-28 | development/web/lib/development_web/live/showcase/examples/tabs.ex:16-25 | development/web/lib/development_web/live/showcase/examples/text_field.ex:16-23 | development/web/lib/development_web/live/showcase/examples/timeline.ex:21-30 | development/web/lib/development_web/live/showcase/examples/toast.ex:21-29 | development/web/lib/development_web/live/showcase/examples/tooltip.ex:16-25 | development/web/lib/development_web/live/showcase/examples/video.ex:26-35 — These 47 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 47 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 47 times.
D4 · Code Duplication · Duplicated block (65 lines × 4) · ×1
  • Duplicated block (65 lines × 4) development/web/lib/development_web/live/showcase/examples/button.ex:16 — development/web/lib/development_web/live/showcase/examples/button.ex:16-80 | development/web/lib/development_web/live/showcase/examples/indicator.ex:16-105 | development/web/lib/development_web/live/showcase/examples/menu.ex:19-343 | development/web/lib/development_web/live/showcase/examples/native_select.ex:16-180 — 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 — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (58 lines × 7) · ×1
  • Duplicated block (58 lines × 7) development/web/lib/development_web/live/showcase/examples/collapse.ex:16 — development/web/lib/development_web/live/showcase/examples/collapse.ex:16-97 | development/web/lib/development_web/live/showcase/examples/fieldset.ex:16-244 | development/web/lib/development_web/live/showcase/examples/image.ex:21-87 | development/web/lib/development_web/live/showcase/examples/overlay.ex:16-73 | development/web/lib/development_web/live/showcase/examples/shape.ex:16-95 | development/web/lib/development_web/live/showcase/examples/spinner.ex:16-114 | development/web/lib/development_web/live/showcase/examples/typography.ex:16-98 — 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 — a file they already depend on, or a new one alongside them — and call it from all 7 call sites, so a change lands once.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 0 typed · 77 plain JS — the untyped files are development/web/assets/js/app.js, development/web/script/claude-video/gladia/sync-captions.mjs, development/web/script/claude-video/shared/assemble.mjs, development/web/script/claude-video/shared/assemble.test.mjs, development/web/script/claude-video/shared/assets/logo.mjs, development/web/script/claude-video/shared/capture.mjs (+71 more).
R10 · Code Duplication · Duplicated block with local edits (161 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (161 matched lines × 2 locations) priv/assets/js/preview_card.js:11 — priv/assets/js/preview_card.js:11 · priv/assets/js/tooltip.js:44 — the two spans are one implementation copied and then locally edited — 1734 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (133 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (133 matched lines × 2 locations) priv/assets/js/chart_chartjs.js:20 — priv/assets/js/chart_chartjs.js:20 · priv/assets/js/chart_echarts.js:36 — the two spans are one implementation copied and then locally edited — 1118 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (114 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (114 matched lines × 2 locations) priv/assets/js/drawer.js:126 — priv/assets/js/drawer.js:126 · priv/assets/js/focus_trap.js:89 — the two spans are one implementation copied and then locally edited — 825 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (100 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (100 matched lines × 2 locations) priv/assets/js/editor_lexical.js:23 — priv/assets/js/editor_lexical.js:23 · priv/assets/js/editor_milk_down.js:45 — the two spans are one implementation copied and then locally edited — 715 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (92 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (92 matched lines × 2 locations) priv/assets/js/popover.js:71 — priv/assets/js/popover.js:71 · priv/assets/js/tooltip.js:61 — the two spans are one implementation copied and then locally edited — 759 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (60 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (60 matched lines × 2 locations) priv/assets/js/menu.js:39 — priv/assets/js/menu.js:39 · priv/assets/js/popover.js:76 — the two spans are one implementation copied and then locally edited — 530 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (55 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (55 matched lines × 2 locations) priv/assets/js/editor_code_mirror.js:100 — priv/assets/js/editor_code_mirror.js:100 · priv/assets/js/editor_lexical.js:88 — the two spans are one implementation copied and then locally edited — 439 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (47 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (47 matched lines × 2 locations) priv/assets/js/popover.js:102 — priv/assets/js/popover.js:102 · priv/assets/js/preview_card.js:44 — the two spans are one implementation copied and then locally edited — 393 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (46 lines × 2 locations) · ×1
  • Duplicated block (46 lines × 2 locations) priv/assets/js/context_menu.js:318 — priv/assets/js/context_menu.js:318 · priv/assets/js/menu.js:319 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (38 lines × 3 locations) · ×1
  • Duplicated block (38 lines × 3 locations) priv/assets/js/chart_billboard.js:152 — priv/assets/js/chart_billboard.js:152 · priv/assets/js/chart_chartjs.js:55 · priv/assets/js/chart_echarts.js:71 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (34 lines × 3 locations) · ×1
  • Duplicated block (34 lines × 3 locations) priv/assets/js/popover.js:212 — priv/assets/js/popover.js:212 · priv/assets/js/preview_card.js:164 · priv/assets/js/tooltip.js:217 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication · Duplicated block (29 lines × 2 locations) · ×1
  • Duplicated block (29 lines × 2 locations) priv/assets/js/context_menu.js:151 — priv/assets/js/context_menu.js:151 · priv/assets/js/menu.js:128 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (27 lines × 2 locations) · ×1
  • Duplicated block (27 lines × 2 locations) priv/assets/js/focus_trap.js:257 — priv/assets/js/focus_trap.js:257 · priv/assets/js/popover.js:294 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (25 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (25 matched lines × 2 locations) priv/assets/js/radio_group.js:59 — priv/assets/js/radio_group.js:59 · priv/assets/js/toggle_group.js:124 — the two spans are one implementation copied and then locally edited — 143 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (24 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (24 matched lines × 2 locations) priv/assets/js/collapsible.js:78 — priv/assets/js/collapsible.js:78 · priv/assets/js/floating.js:237 — the two spans are one implementation copied and then locally edited — 157 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (21 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (21 matched lines × 2 locations) priv/assets/js/popup.js:64 — priv/assets/js/popup.js:64 · priv/assets/js/select.js:105 — the two spans are one implementation copied and then locally edited — 187 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (18 lines × 2 locations) · ×1
  • Duplicated block (18 lines × 2 locations) priv/assets/js/editor_code_mirror.js:38 — priv/assets/js/editor_code_mirror.js:38 · priv/assets/js/editor_tiptap.js:97 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block with local edits (18 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (18 matched lines × 2 locations) priv/assets/js/menubar.js:167 — priv/assets/js/menubar.js:167 · priv/assets/js/menubar.js:216 — the two spans are one implementation copied and then locally edited — 123 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (14 lines × 3 locations) · ×1
  • Duplicated block (14 lines × 3 locations) priv/assets/js/chart_billboard.js:298 — priv/assets/js/chart_billboard.js:298 · priv/assets/js/chart_chartjs.js:192 · priv/assets/js/chart_echarts.js:240 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R2 · Cyclomatic Complexity · Complex function updatePosition (cyclomatic 41, cognitive 45) · ×1
  • Complex function updatePosition (cyclomatic 41, cognitive 45) priv/assets/js/floating.js:450 — updatePosition has cyclomatic complexity 41 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function positionPopup (cyclomatic 33, cognitive 41) · ×1
  • Complex function positionPopup (cyclomatic 33, cognitive 41) priv/assets/js/tooltip.js:187 — positionPopup has cyclomatic complexity 33 and cognitive complexity 41; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function handleKeyDown (cyclomatic 31, cognitive 35) · ×1
  • Complex function handleKeyDown (cyclomatic 31, cognitive 35) priv/assets/js/tree.js:413 — handleKeyDown has cyclomatic complexity 31 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function handleKeyDown (cyclomatic 27, cognitive 38) · ×1
  • Complex function handleKeyDown (cyclomatic 27, cognitive 38) priv/assets/js/combobox.js:564 — handleKeyDown has cyclomatic complexity 27 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function handleKeydown (cyclomatic 26, cognitive 26) · ×1
  • Complex function handleKeydown (cyclomatic 26, cognitive 26) priv/assets/js/menu.js:387 — handleKeydown has cyclomatic complexity 26 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function handleKeydown (cyclomatic 26, cognitive 24) · ×1
  • Complex function handleKeydown (cyclomatic 26, cognitive 24) priv/assets/js/context_menu.js:369 — handleKeydown has cyclomatic complexity 26 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function activate (cyclomatic 24, cognitive 35) · ×1
  • Complex function activate (cyclomatic 24, cognitive 35) priv/assets/js/navigation_menu.js:102 — activate has cyclomatic complexity 24 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function onKeyDown (cyclomatic 24, cognitive 26) · ×1
  • Complex function onKeyDown (cyclomatic 24, cognitive 26) priv/assets/js/otp.js:203 — onKeyDown has cyclomatic complexity 24 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function parse (cyclomatic 23, cognitive 25) · ×1
  • Complex function parse (cyclomatic 23, cognitive 25) priv/assets/js/number_field.js:119 — parse has cyclomatic complexity 23 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function positionPopup (cyclomatic 21, cognitive 23) · ×1
  • Complex function positionPopup (cyclomatic 21, cognitive 23) priv/assets/js/menu.js:166 — positionPopup has cyclomatic complexity 21 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function onKey (cyclomatic 20, cognitive 24) · ×1
  • Complex function onKey (cyclomatic 20, cognitive 24) priv/assets/js/toolbar.js:70 — onKey has cyclomatic complexity 20 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function mounted (cyclomatic 19, cognitive 18) · ×1
  • Complex function mounted (cyclomatic 19, cognitive 18) priv/assets/js/number_field.js:35 — mounted has cyclomatic complexity 19 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function mounted (cyclomatic 17, cognitive 17) · ×1
  • Complex function mounted (cyclomatic 17, cognitive 17) priv/assets/js/drawer.js:115 — mounted has cyclomatic complexity 17 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function main (cyclomatic 16, cognitive 35) · ×1
  • Complex function main (cyclomatic 16, cognitive 35) development/web/script/claude-video/shared/assemble.mjs:161 — main has cyclomatic complexity 16 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function moveSwipe (cyclomatic 16, cognitive 21) · ×1
  • Complex function moveSwipe (cyclomatic 16, cognitive 21) priv/assets/js/drawer.js:407 — moveSwipe has cyclomatic complexity 16 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function mounted (cyclomatic 16, cognitive 16) · ×1
  • Complex function mounted (cyclomatic 16, cognitive 16) priv/assets/js/popover.js:52 — mounted has cyclomatic complexity 16 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function runBeat (cyclomatic 16, cognitive 13) · ×1
  • Complex function runBeat (cyclomatic 16, cognitive 13) development/web/script/claude-video/shared/capture.mjs:89 — runBeat has cyclomatic complexity 16 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function handleClick (cyclomatic 15, cognitive 13) · ×1
  • Complex function handleClick (cyclomatic 15, cognitive 13) priv/assets/js/tree.js:362 — handleClick has cyclomatic complexity 15 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function select (cyclomatic 14, cognitive 31) · ×1
  • Complex function select (cyclomatic 14, cognitive 31) priv/assets/js/tabs.js:78 — select has cyclomatic complexity 14 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function set (cyclomatic 14, cognitive 25) · ×1
  • Complex function set (cyclomatic 14, cognitive 25) priv/assets/js/slider.js:198 — set has cyclomatic complexity 14 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function onKey (cyclomatic 14, cognitive 16) · ×1
  • Complex function onKey (cyclomatic 14, cognitive 16) priv/assets/js/toggle_group.js:127 — onKey has cyclomatic complexity 14 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function handleKeydown (cyclomatic 14, cognitive 14) · ×1
  • Complex function handleKeydown (cyclomatic 14, cognitive 14) priv/assets/js/disclosure.js:86 — handleKeydown has cyclomatic complexity 14 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function onKeyDown (cyclomatic 14, cognitive 14) · ×1
  • Complex function onKeyDown (cyclomatic 14, cognitive 14) priv/assets/js/number_field.js:307 — onKeyDown has cyclomatic complexity 14 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function onPopupKey (cyclomatic 14, cognitive 14) · ×1
  • Complex function onPopupKey (cyclomatic 14, cognitive 14) priv/assets/js/select.js:177 — onPopupKey has cyclomatic complexity 14 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function mounted (cyclomatic 14, cognitive 14) · ×1
  • Complex function mounted (cyclomatic 14, cognitive 14) priv/assets/js/tooltip.js:45 — mounted has cyclomatic complexity 14 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function destroyed (cyclomatic 14, cognitive 13) · ×1
  • Complex function destroyed (cyclomatic 14, cognitive 13) priv/assets/js/combobox.js:930 — destroyed has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function mounted (cyclomatic 13, cognitive 13) · ×1
  • Complex function mounted (cyclomatic 13, cognitive 13) priv/assets/js/menu.js:19 — mounted has cyclomatic complexity 13 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function onKey (cyclomatic 13, cognitive 13) · ×1
  • Complex function onKey (cyclomatic 13, cognitive 13) priv/assets/js/radio_group.js:62 — onKey has cyclomatic complexity 13 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function handleKeydown (cyclomatic 13, cognitive 13) · ×1
  • Complex function handleKeydown (cyclomatic 13, cognitive 13) priv/assets/js/roving_tabindex.js:53 — handleKeydown has cyclomatic complexity 13 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function applyTheme (cyclomatic 13, cognitive 12) · ×1
  • Complex function applyTheme (cyclomatic 13, cognitive 12) priv/assets/js/chart_chartjs.js:138 — applyTheme has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function handleKeydown (cyclomatic 13, cognitive 10) · ×1
  • Complex function handleKeydown (cyclomatic 13, cognitive 10) priv/assets/js/floating.js:398 — handleKeydown has cyclomatic complexity 13 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function updateAxis (cyclomatic 12, cognitive 17) · ×1
  • Complex function updateAxis (cyclomatic 12, cognitive 17) priv/assets/js/scrollArea.js:67 — updateAxis has cyclomatic complexity 12 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function groupWords (cyclomatic 12, cognitive 16) · ×1
  • Complex function groupWords (cyclomatic 12, cognitive 16) development/web/script/claude-video/shared/assemble.mjs:109 — groupWords has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function dropPosition (cyclomatic 12, cognitive 16) · ×1
  • Complex function dropPosition (cyclomatic 12, cognitive 16) priv/assets/js/tree.js:615 — dropPosition has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function scrubMove (cyclomatic 12, cognitive 15) · ×1
  • Complex function scrubMove (cyclomatic 12, cognitive 15) priv/assets/js/number_field.js:427 — scrubMove has cyclomatic complexity 12 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function mounted (cyclomatic 12, cognitive 13) · ×1
  • Complex function mounted (cyclomatic 12, cognitive 13) priv/assets/js/scrollArea.js:22 — mounted has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function onKey (cyclomatic 12, cognitive 13) · ×1
  • Complex function onKey (cyclomatic 12, cognitive 13) priv/assets/js/tabs.js:153 — onKey has cyclomatic complexity 12 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 12, cognitive 12) · ×1
  • Complex function (anonymous) (cyclomatic 12, cognitive 12) priv/assets/js/drawer.js:567 — (anonymous) has cyclomatic complexity 12 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · priv/assets/js/combobox.js · ×1
  • priv/assets/js/combobox.js: 854 lines of code priv/assets/js/combobox.js:1 — priv/assets/js/combobox.js has 854 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · priv/assets/js/floating.js · ×1
  • priv/assets/js/floating.js: 603 lines of code priv/assets/js/floating.js:1 — priv/assets/js/floating.js has 603 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · priv/assets/js/tree.js · ×1
  • priv/assets/js/tree.js: 569 lines of code priv/assets/js/tree.js:1 — priv/assets/js/tree.js has 569 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · priv/assets/js/drawer.js · ×1
  • priv/assets/js/drawer.js: 566 lines of code priv/assets/js/drawer.js:1 — priv/assets/js/drawer.js has 566 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · priv/assets/js/carousel.js · ×1
  • priv/assets/js/carousel.js: 513 lines of code priv/assets/js/carousel.js:1 — priv/assets/js/carousel.js has 513 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · priv/assets/js/number_field.js · ×1
  • priv/assets/js/number_field.js: 435 lines of code priv/assets/js/number_field.js:1 — priv/assets/js/number_field.js has 435 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · priv/assets/js/menu.js · ×1
  • priv/assets/js/menu.js: 423 lines of code priv/assets/js/menu.js:1 — priv/assets/js/menu.js has 423 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · priv/assets/js/context_menu.js · ×1
  • priv/assets/js/context_menu.js: 408 lines of code priv/assets/js/context_menu.js:1 — priv/assets/js/context_menu.js has 408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · priv/assets/js/clipboard.js · ×1
  • priv/assets/js/clipboard.js: 402 lines of code priv/assets/js/clipboard.js:1 — priv/assets/js/clipboard.js has 402 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling · No typecheck script · ×1
  • No typecheck script — test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
R8 · Dependency Hygiene · Unused dependency '@codemirror/commands' · ×1
  • Unused dependency '@codemirror/commands' — Declared in development/web/assets/package.json but never imported anywhere in that package or its workspace members — while priv/assets/js/editor_code_mirror.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
R8 · Dependency Hygiene · Unused dependency '@codemirror/lang-javascript' · ×1
  • Unused dependency '@codemirror/lang-javascript' — Declared in development/web/assets/package.json but never imported anywhere in that package or its workspace members — while priv/assets/js/editor_code_mirror.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
R8 · Dependency Hygiene · Unused dependency '@codemirror/language' · ×1
  • Unused dependency '@codemirror/language' — Declared in development/web/assets/package.json but never imported anywhere in that package or its workspace members — while priv/assets/js/editor_code_mirror.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
R8 · Dependency Hygiene · Unused dependency '@codemirror/state' · ×1
  • Unused dependency '@codemirror/state' — Declared in development/web/assets/package.json but never imported anywhere in that package or its workspace members — while priv/assets/js/editor_code_mirror.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
R8 · Dependency Hygiene · Unused dependency '@codemirror/view' · ×1
  • Unused dependency '@codemirror/view' — Declared in development/web/assets/package.json but never imported anywhere in that package or its workspace members — while priv/assets/js/editor_code_mirror.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
R8 · Dependency Hygiene · Unused dependency '@lexical/history' · ×1
  • Unused dependency '@lexical/history' — Declared in development/web/assets/package.json but never imported anywhere in that package or its workspace members — while priv/assets/js/editor_lexical.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
R8 · Dependency Hygiene · Unused dependency '@lexical/rich-text' · ×1
  • Unused dependency '@lexical/rich-text' — Declared in development/web/assets/package.json but never imported anywhere in that package or its workspace members — while priv/assets/js/editor_lexical.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
R8 · Dependency Hygiene · Unused dependency '@lexical/utils' · ×1
  • Unused dependency '@lexical/utils' — Declared in development/web/assets/package.json but never imported anywhere in that package or its workspace members — while priv/assets/js/editor_lexical.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
R8 · Dependency Hygiene · Unused dependency '@tiptap/core' · ×1
  • Unused dependency '@tiptap/core' — Declared in development/web/assets/package.json but never imported anywhere in that package or its workspace members — while priv/assets/js/editor_tiptap.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
R8 · Dependency Hygiene · Unused dependency '@tiptap/pm' · ×1
  • Unused dependency '@tiptap/pm' — Declared in development/web/assets/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@tiptap/starter-kit' · ×1
  • Unused dependency '@tiptap/starter-kit' — Declared in development/web/assets/package.json but never imported anywhere in that package or its workspace members — while priv/assets/js/editor_tiptap.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
R8 · Dependency Hygiene · Unused dependency 'echarts' · ×1
  • Unused dependency 'echarts' — Declared in development/web/assets/package.json but never imported anywhere in that package or its workspace members — while priv/assets/js/chart_echarts.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
R8 · Dependency Hygiene · Unused dependency 'lexical' · ×1
  • Unused dependency 'lexical' — Declared in development/web/assets/package.json but never imported anywhere in that package or its workspace members — while priv/assets/js/editor_lexical.js DOES import it and no package.json above that file declares it, so the import resolves through the copy this declaration installs. The declaration is misplaced rather than dead: removing it breaks that import. Move it to the package.json that owns the importing file (or, if the two packages are meant to share it, hoist it to the workspace root) rather than deleting it.
SC1 · Supply-chain hygiene · JavaScript dependencies are not locked · ×1
  • JavaScript dependencies are not locked development/web/script/claude-video/package.json:13 — development/web/script/claude-video/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
Minor — 52 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×40
  • Duplicated predicate development/web/lib/development_web/components/badge.ex:917 — `!is_nil(pinging) && "[&>.indicator]:animate-ping"` appears character-identically in 2 files — development/web/lib/development_web/components/badge.ex, development/web/lib/development_web/components/button.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate lib/mix/tasks/mishka.ui.gen.component.ex:109 — `!options[:sub] and Mix.env() != :test and tty?` appears character-identically in 3 files — lib/mix/tasks/mishka.ui.gen.component.ex, lib/mix/tasks/mishka.ui.gen.headless.ex, lib/mix/tasks/mishka.ui.gen.mob.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate development/mob/lib/mishka_mob/components/mishka_calendar.ex:804 — `Date.compare(date, from) == :gt and Date.compare(date, to) == :lt` appears character-identically in 2 files — development/mob/lib/mishka_mob/components/mishka_calendar.ex, development/web/lib/development_web/components/headless/calendar.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate development/mob/lib/mishka_mob/components/mishka_accordion.ex:213 — `Map.get(props, :background) || :surface_raised` appears character-identically in 6 files — development/mob/lib/mishka_mob/components/mishka_accordion.ex, development/mob/lib/mishka_mob/components/mishka_action_icon.ex, development/mob/lib/mishka_mob/components/mishka_code.ex, development/mob/lib/mishka_mob/components/mishka_pill.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate development/mob/lib/mishka_mob/components/mishka_floating_indicator.ex:108 — `Map.get(props, :color) || :surface_raised` appears character-identically in 2 files — development/mob/lib/mishka_mob/components/mishka_floating_indicator.ex, development/mob/lib/mishka_mob/components/mishka_skeleton.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate development/mob/lib/mishka_mob/components/mishka_accordion.ex:214 — `Map.get(props, :corner_radius) || :radius_md` appears character-identically in 2 files — development/mob/lib/mishka_mob/components/mishka_accordion.ex, development/mob/lib/mishka_mob/components/mishka_skeleton.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate development/mob/lib/mishka_mob/components/mishka_dock.ex:53 — `Map.get(props, :corner_radius) || :radius_pill` appears character-identically in 2 files — development/mob/lib/mishka_mob/components/mishka_dock.ex, development/mob/lib/mishka_mob/components/mishka_skeleton.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate development/mob/lib/mishka_mob/components/mishka_calendar.ex:926 — `Map.get(props, :disabled_color) || :muted` appears character-identically in 3 files — development/mob/lib/mishka_mob/components/mishka_calendar.ex, development/mob/lib/mishka_mob/components/mishka_chip.ex, development/mob/lib/mishka_mob/components/mishka_pill.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate development/mob/lib/mishka_mob/components/mishka_field.ex:116 — `Map.get(props, :label_color) || :on_surface` appears character-identically in 3 files — development/mob/lib/mishka_mob/components/mishka_field.ex, development/mob/lib/mishka_mob/components/mishka_segmented_control.ex, development/mob/lib/mishka_mob/components/mishka_toggle.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate development/mob/lib/mishka_mob/components/mishka_floating_indicator.ex:148 — `Map.get(props, :orientation) || :horizontal` appears character-identically in 6 files — development/mob/lib/mishka_mob/components/mishka_floating_indicator.ex, development/mob/lib/mishka_mob/components/mishka_navigation_menu.ex, development/mob/lib/mishka_mob/components/mishka_separator.ex, development/mob/lib/mishka_mob/components/mishka_splitter.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate development/mob/lib/mishka_mob/components/mishka_radio_group.ex:144 — `Map.get(props, :orientation) || :vertical` appears character-identically in 2 files — development/mob/lib/mishka_mob/components/mishka_radio_group.ex, development/mob/lib/mishka_mob/components/mishka_scroll_area.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate development/mob/lib/mishka_mob/components/mishka_checkbox.ex:204 — `Map.get(props, :text_color) || :on_primary` appears character-identically in 4 files — development/mob/lib/mishka_mob/components/mishka_checkbox.ex, development/mob/lib/mishka_mob/components/mishka_chip.ex, development/mob/lib/mishka_mob/components/mishka_segmented_control.ex, development/mob/lib/mishka_mob/components/mishka_toggle.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate development/mob/lib/mishka_mob/components/mishka_angle_slider.ex:240 — `Map.get(props, :text_color) || :on_surface` appears character-identically in 3 files — development/mob/lib/mishka_mob/components/mishka_angle_slider.ex, development/mob/lib/mishka_mob/components/mishka_highlight.ex, development/mob/lib/mishka_mob/components/mishka_radio.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate lib/mishka_chelekom/cms_bundle/examples.ex:153 — `allowed && MapSet.member?(allowed, value)` appears character-identically in 2 files — lib/mishka_chelekom/cms_bundle/examples.ex, lib/mishka_chelekom/cms_bundle/showcase.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate development/web/lib/development_web/components/headless/number_field.ex:118 — `assigns.format && Phoenix.json_library().encode!(assigns.format)` appears character-identically in 2 files — development/web/lib/development_web/components/headless/number_field.ex, development/web/lib/development_web/components/headless/slider.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate development/mob/lib/mishka_mob/components/mishka_action_icon.ex:208 — `border_color && (Map.get(props, :border_width) || 1)` appears character-identically in 2 files — development/mob/lib/mishka_mob/components/mishka_action_icon.ex, development/mob/lib/mishka_mob/components/mishka_theme_icon.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate development/web/lib/development_web/components/carousel.ex:240 — `is_binary(nav) or is_binary(pat) or is_binary(hrf)` appears character-identically in 2 files — development/web/lib/development_web/components/carousel.ex, development/web/lib/development_web/components/speed_dial.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate development/mob/lib/mishka_mob/components/mishka_dialog.ex:523 — `is_map(node) and Map.get(node, :type) in @slot_types` appears character-identically in 3 files — development/mob/lib/mishka_mob/components/mishka_dialog.ex, development/mob/lib/mishka_mob/components/mishka_drawer.ex, development/mob/lib/mishka_mob/components/mishka_popover.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate lib/mix/tasks/mishka.ui.gen.headless.ex:147 — `options[:module_prefix] || get_in(igniter.assigns, [:mishka_user_config, :module_prefix])` appears character-identically in 2 files — lib/mix/tasks/mishka.ui.gen.headless.ex, lib/mix/tasks/mishka.ui.gen.mob.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate development/mob/lib/mishka_mob/components/mishka_accordion.ex:203 — `truthy?(Map.get(props, :disabled, false)) or item.disabled` appears character-identically in 2 files — development/mob/lib/mishka_mob/components/mishka_accordion.ex, development/mob/lib/mishka_mob/components/mishka_checkbox_group.ex. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate priv/assets/js/drawer.js:300 — `!e.shiftKey && document.activeElement === last` appears character-identically in 3 files — priv/assets/js/drawer.js, priv/assets/js/focus_trap.js, priv/assets/js/popover.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate priv/assets/js/context_menu.js:239 — `!menu || this.stack.indexOf(menu) === -1` appears character-identically in 2 files — priv/assets/js/context_menu.js, priv/assets/js/menu.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate priv/assets/js/chart_billboard.js:309 — `!payload || (payload.id && payload.id !== this.rootId)` appears character-identically in 7 files — priv/assets/js/chart_billboard.js, priv/assets/js/chart_chartjs.js, priv/assets/js/chart_echarts.js, priv/assets/js/editor_code_mirror.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate priv/assets/js/context_menu.js:253 — `!popup || this.stack.indexOf(popup) !== -1` appears character-identically in 2 files — priv/assets/js/context_menu.js, priv/assets/js/menu.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate priv/assets/js/context_menu.js:287 — `!row || row.hasAttribute("data-disabled")` appears character-identically in 2 files — priv/assets/js/context_menu.js, priv/assets/js/menu.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • + 15 more in this group — see findings.md.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 351 significant file(s) lose their only recent owner: development/web/lib/development_web/live/showcase/headless_daisyui_examples.ex, development/web/lib/development_web/live/showcase/headless_baseui_examples.ex, development/mob/android/app/src/main/java/com/example/mishka_mob/MobBridge.kt, development/web/lib/development_web/live/showcase/headless_preview.ex, development/web/lib/development_web/components/button.ex, development/web/lib/development_web/components/pagination.ex, development/web/lib/development_web/components/combobox.ex, development/web/lib/development_web/components/password_field.ex (+343 more). Pair on, review, or document these before any departure.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found development/web/mix.exs:13 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `development/web/mix.exs` makes this repository a deployable product (line 13).
D24 · Comment Value · redundant comment · ×1
  • redundant comment priv/assets/js/clipboard.js:338 — "Announce to screen readers" repeats the code it sits on: 3 of its 3 words (announce, screen, readers) are already in `this.announceToScreenReader(success ? this.successText : this.errorText);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 3 of 7 project(s) overshoot their size bounds, lowering Project Cohesion to 1.4/10. The most over is `development/web` (105692 LoC, 310 module-visible types across 10 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `development/web`.
P3 · Security & performance tooling · Dependabot does not watch bun/gradle · ×1
  • Dependabot does not watch bun/gradle REDACTED:8 — `REDACTED` schedules updates, but no `package-ecosystem` entry covers `bun`, `gradle`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list.
R7 · Dead Code · Unused module-local declaration 'EASE' · ×1
  • Unused module-local declaration 'EASE' priv/assets/js/drawer.js:22 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code · Unused module-local declaration 'num' · ×1
  • Unused module-local declaration 'num' priv/assets/js/drawer.js:112 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
S1 · Web-Security Posture · Security headers incomplete · ×1
  • Security headers incomplete — Set: Content-Security-Policy, Referrer-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Permitted-Cross-Domain-Policies. Missing: X-Frame-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each.(−0.5 on this card.) The server: development/web/lib/development_web/endpoint.ex:2 — `Phoenix.Endpoint`.
Minor — 14 finding(s)
D10 · Test Quality · Skipped (documented) · ×11
  • Skipped (documented): (unnamed test) priv/assets/js/overflow_list.test.mjs:24 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) priv/assets/js/overflow_list.test.mjs:31 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) priv/assets/js/overflow_list.test.mjs:41 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) priv/assets/js/overflow_list.test.mjs:48 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) priv/assets/js/overflow_list.test.mjs:65 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) priv/assets/js/overflow_list.test.mjs:72 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) priv/assets/js/overflow_list.test.mjs:73 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) priv/assets/js/overflow_list.test.mjs:78 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) priv/assets/js/overflow_list.test.mjs:86 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) priv/assets/js/overflow_list.test.mjs:93 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) priv/assets/js/overflow_list.test.mjs:98 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
D12 · Dependency Hygiene · Outdated · ×2
  • Outdated: dialyxir — `:dialyxir` is locked at 1.4.8 but 1.4.9 is the current stable release on hex.pm, and it already satisfies the `"~> 1.4"` requirement declared in development/mob/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update dialyxir` and commit the updated mix.lock.
  • Outdated: mob — `:mob` is locked at 0.9.27 but 0.9.30 is the current stable release on hex.pm, and it already satisfies the `"~> 0.9.25"` requirement declared in development/mob/mix.exs — so the lockfile is behind this repository's own declared range. Run `mix deps.update mob` and commit the updated mix.lock.
D24 · Comment Value · doc comments repeat the names · ×1
  • doc comments repeat the names priv/assets/js/clipboard.js:116 — 2 of 20 documented parameters and 2 of 30 summaries in `priv/assets/js` only repeat the member or parameter name (e.g. "Remove event listeners" for `removeEventListeners`). Delete the restating tags, or add what the name does not say.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-754c9d78e21848c096ea937ebac4020f/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-754c9d78e21848c096ea937ebac4020f/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .14artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1df1d-bab2-7b65-9fcb-d513f7004a9d · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md