Public report of framework7io/framework7, 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, 04:09 UTC · Survey ID cd_e35ef7d44dc64828953f3b816ae2d5ad

framework7io/framework7

Measured 15 November 2026, 04:08 UTC, at code version 9bf9748

Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.

CAI score 30out of 100 At risk Down 1 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: 105,244 lines of product code in 1 project, tests not counted · Estimated rebuild effort: about 0.6 person-years · Weakest lens: Code Health, 23

Findings by how serious they are

83 critical 839 serious 124 minor

11 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, 04:08 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.

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

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 ▸

57of 57 dimensions measured by tools.
1034of 1046 findings point to an exact file and line, so you can open each one in the code. The other 12 concern the repository as a whole, such as missing documentation.
57dimensions across 7 lenses, read from 105,244 lines of product code in 1 project.
Chapters

Executive summary

framework7io/framework7 is rated At risk because critical security findings are open, all of them in the packages it uses. It scores 30 out of 100, which the At risk rating leaves unchanged.

Code Health, at 23, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step for the work it takes is replacing the six deprecated dependencies, worth about 2 points. Adding automated tests comes next, worth about 7 points.

Twenty-five known security holes in the packages the code depends on can be used by attackers. Forty images have no description for people who can't see them, and nine controls can't be used without a mouse. Updating the vulnerable packages, describing the images and making the controls work with a keyboard would close these risks. The four form fields without a label need a label.

The product code is 105,244 lines, about €90,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.
Code Health 23 · counts for 46%Production Readiness 24 · counts for 25%Accessibility 28 · counts for 14%Maturity 55 · counts for 8%Performance 60 · counts for 4%Security and Compliance 90 · counts for 2%Architecture 98 · counts for 1%

The weakest lenses score close to each other, so improving any of them moves the score.

Code composition: what the lines of code are
Product code 100%
New since the last survey: 22 findings

These 22 critical or serious findings weren't in the previous survey, on 29 October 2026.

  • Cyclomatic Complexity · Complex function ListItemContent (cyclomatic 43, cognitive 47) src/react/components/list-item-content.jsx
  • Cyclomatic Complexity · Complex function handleTouchMove (cyclomatic 40, cognitive 57) src/core/modules/router/swipe-back.js
  • Cyclomatic Complexity · Complex function navigate (cyclomatic 40, cognitive 52) src/core/modules/router/navigate.js
  • Cyclomatic Complexity · Complex function calcDevice (cyclomatic 39, cognitive 35) REDACTED
  • Cyclomatic Complexity · Complex function ListItem (cyclomatic 38, cognitive 35) src/react/components/list-item.jsx
  • Cyclomatic Complexity · Complex function pageCallback (cyclomatic 38, cognitive 34) src/core/modules/router/router-class.js
  • Cyclomatic Complexity · Complex function load (cyclomatic 37, cognitive 36) src/core/modules/router/navigate.js
  • Cyclomatic Complexity · Complex function ListInput (cyclomatic 36, cognitive 38) src/react/components/list-input.jsx
  • Cyclomatic Complexity · Complex function search (cyclomatic 35, cognitive 58) src/core/components/searchbar/searchbar-class.js
  • Cyclomatic Complexity · Complex function handleTouchMove (cyclomatic 33, cognitive 48) src/core/components/sheet/sheet-class.js
  • Cyclomatic Complexity · Complex function resize (cyclomatic 33, cognitive 43) src/core/components/popover/popover-class.js
  • Cyclomatic Complexity · Complex function getInitialUrl (cyclomatic 33, cognitive 40) src/core/modules/router/router-class.js
  • Cyclomatic Complexity · Complex function close (cyclomatic 33, cognitive 39) src/core/components/card/card.js
  • Cyclomatic Complexity · Complex function handleMouseWheel (cyclomatic 32, cognitive 57) src/core/components/pull-to-refresh/pull-to-refresh-class.js
  • Cyclomatic Complexity · Complex function handleTouchEnd (cyclomatic 30, cognitive 49) src/core/components/sortable/sortable.js
  • Cyclomatic Complexity · Complex function handleLargeNavbarCollapse (cyclomatic 30, cognitive 38) src/core/components/navbar/navbar.js
  • Cyclomatic Complexity · Complex function handleTouchStart (cyclomatic 30, cognitive 34) src/core/components/panel/swipe-panel.js
  • Cyclomatic Complexity · Complex function dateInRange (cyclomatic 29, cognitive 56) REDACTED
  • Cyclomatic Complexity · Complex function handleTouchEnd (cyclomatic 29, cognitive 40) src/core/components/swipeout/swipeout.js
  • Cyclomatic Complexity · Complex function handleTouchMove (cyclomatic 29, cognitive 35) src/core/modules/touch/touch.js
  • Exception handling · Swallowed exception (empty catch) src/core/shared/utils.js
  • Exception handling · Swallowed exception (empty catch) src/core/shared/utils.js

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: 885 findings

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

  • Cyclomatic Complexity · build-vue-typings.generateComponentProps (cyclomatic 27) scripts/build-vue-typings.js
  • Cyclomatic Complexity · find-common-css-vars.fs.readdirSync("./src/core/components").forEach() (cyclomatic 20) scripts/find-common-css-vars.js
  • Cyclomatic Complexity · build-svelte-typings.generateComponentTypings (cyclomatic 17) scripts/build-svelte-typings.js
  • Cognitive Complexity · build-vue-typings.generateComponentProps (cognitive 30) scripts/build-vue-typings.js
  • Cognitive Complexity · find-common-css-vars.fs.readdirSync("./src/core/components").forEach() (cognitive 22) scripts/find-common-css-vars.js
  • Cognitive Complexity · build-svelte-typings.generateComponentTypings (cognitive 16) scripts/build-svelte-typings.js
  • Secret Scanning · Leaked secret: hardcoded-credential REDACTED
  • Code Duplication · Duplicated block with local edits (46 matched lines × 2 locations) src/react/components/accordion-item.jsx
  • Code Duplication · Duplicated block with local edits (43 matched lines × 2 locations) src/react/components/card.jsx
  • Code Duplication · Duplicated block with local edits (41 matched lines × 2 locations) kitchen-sink/react/src/pages/notifications.jsx
  • Code Duplication · Duplicated block (41 lines × 2 locations) src/vue/components/input.vue
  • Code Duplication · Duplicated block (40 lines × 3 locations) kitchen-sink/react/src/pages/swiper-3d-coverflow.jsx
  • Code Duplication · Duplicated block (40 lines × 2 locations) src/core/components/stepper/stepper.js
  • Code Duplication · Duplicated block (40 lines × 2 locations) src/react/components/pie-chart.jsx
  • Code Duplication · Duplicated block (39 lines × 2 locations) kitchen-sink/react/src/pages/autocomplete.jsx
  • Code Duplication · Duplicated block with local edits (39 matched lines × 2 locations) kitchen-sink/react/src/pages/progressbar.jsx
  • Code Duplication · Duplicated block with local edits (39 matched lines × 2 locations) src/core/components/accordion/accordion.js
  • Code Duplication · Duplicated block with local edits (39 matched lines × 2 locations) src/core/components/gauge/gauge.js
  • Code Duplication · Duplicated block with local edits (39 matched lines × 2 locations) src/core/components/gauge/gauge.js
  • Code Duplication · Duplicated block (39 lines × 3 locations) src/react/shared/utils.js
  • Code Duplication · Duplicated block (39 lines × 2 locations) src/svelte/shared/utils.js
  • Code Duplication · Duplicated block with local edits (38 matched lines × 2 locations) kitchen-sink/react/src/pages/calendar-page.jsx
  • Code Duplication · Duplicated block (38 lines × 2 locations) src/core/components/popup/popup-class.js
  • Code Duplication · Duplicated block with local edits (38 matched lines × 2 locations) src/core/components/range/range.js
  • Code Duplication · Duplicated block (38 lines × 2 locations) src/react/components/actions.jsx
  • Code Duplication · Duplicated block with local edits (38 matched lines × 2 locations) src/react/components/list.jsx
  • Code Duplication · Duplicated block with local edits (37 matched lines × 2 locations) kitchen-sink/react/src/pages/list.jsx
  • Code Duplication · Duplicated block with local edits (37 matched lines × 2 locations) kitchen-sink/react/src/pages/login-screen-page.jsx
  • Code Duplication · Duplicated block (37 lines × 2 locations) src/react/components/login-screen.jsx
  • Code Duplication · Duplicated block (37 lines × 2 locations) src/react/components/popover.jsx
  • Code Duplication · Duplicated block (37 lines × 2 locations) src/react/shared/get-router-initial-component.js
  • Code Duplication · Duplicated block (36 lines × 2 locations) src/core/components/messagebar/messagebar-class.js
  • Code Duplication · Duplicated block (36 lines × 2 locations) src/react/components/actions.jsx
  • Code Duplication · Duplicated block with local edits (36 matched lines × 2 locations) src/react/components/photo-browser.jsx
  • Code Duplication · Duplicated block (35 lines × 2 locations) kitchen-sink/react/src/pages/autocomplete.jsx
  • Code Duplication · Duplicated block (35 lines × 2 locations) src/core/components/autocomplete/autocomplete.js
  • Code Duplication · Duplicated block (35 lines × 2 locations) src/core/components/color-picker/color-picker-class.js
  • Code Duplication · Duplicated block (35 lines × 2 locations) src/vue/components/input.vue
  • Code Duplication · Duplicated block (34 lines × 2 locations) scripts/build-react-typings.js
  • Code Duplication · Duplicated block (34 lines × 2 locations) src/core/components/infinite-scroll/infinite-scroll.js
  • Code Duplication · Duplicated block with local edits (34 matched lines × 2 locations) src/react/components/card.jsx
  • Code Duplication · Duplicated block with local edits (34 matched lines × 2 locations) src/react/components/text-editor.jsx
  • Code Duplication · Duplicated block (33 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (32 lines × 2 locations) kitchen-sink/react/src/pages/fab-morph.jsx
  • Code Duplication · Duplicated block (32 lines × 2 locations) kitchen-sink/react/src/pages/treeview.jsx
  • Code Duplication · Duplicated block (32 lines × 2 locations) src/core/components/color-picker/color-picker-class.js
  • Code Duplication · Duplicated block (32 lines × 2 locations) src/core/components/messagebar/messagebar.js
  • Code Duplication · Duplicated block with local edits (32 matched lines × 2 locations) src/core/components/modal/modal-class.js
  • Code Duplication · Duplicated block with local edits (32 matched lines × 2 locations) src/react/components/area-chart.jsx
  • Code Duplication · Duplicated block (32 lines × 2 locations) src/react/components/photo-browser.jsx
  • Code Duplication · Duplicated block (32 lines × 2 locations) src/react/components/range.jsx
  • Code Duplication · Duplicated block (32 lines × 2 locations) src/svelte/shared/use-icon.js
  • Code Duplication · Duplicated block (31 lines × 2 locations) kitchen-sink/svelte/src/pages/calendar-page.svelte
  • Code Duplication · Duplicated block (31 lines × 2 locations) src/core/components/tooltip/tooltip-class.js
  • Code Duplication · Duplicated block (31 lines × 4 locations) src/core/shared/utils.js
  • Code Duplication · Duplicated block with local edits (30 matched lines × 2 locations) kitchen-sink/react/src/pages/messages.jsx
  • Code Duplication · Duplicated block with local edits (30 matched lines × 2 locations) scripts/build-react-typings.js
  • Code Duplication · Duplicated block (30 lines × 2 locations) src/core/components/actions/actions-class.js
  • Code Duplication · Duplicated block (30 lines × 2 locations) src/core/components/autocomplete/autocomplete-class.js
  • Code Duplication · Duplicated block with local edits (30 matched lines × 2 locations) src/svelte/components/pie-chart.svelte
  • Code Duplication · Duplicated block (29 lines × 2 locations) kitchen-sink/react/src/pages/accordion.jsx
  • Code Duplication · Duplicated block (29 lines × 2 locations) kitchen-sink/react/src/pages/action-sheet.jsx
  • Code Duplication · Duplicated block (29 lines × 2 locations) kitchen-sink/react/src/pages/autocomplete.jsx
  • Code Duplication · Duplicated block (29 lines × 2 locations) kitchen-sink/react/src/pages/calendar-page.jsx
  • Code Duplication · Duplicated block (29 lines × 3 locations) src/react/shared/get-router-initial-component.js
  • Code Duplication · Duplicated block (28 lines × 2 locations) kitchen-sink/react/src/pages/autocomplete.jsx
  • Code Duplication · Duplicated block (28 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (28 lines × 3 locations) src/core/components/color-picker/modules/alpha-slider.js
  • Code Duplication · Duplicated block with local edits (28 matched lines × 2 locations) src/core/components/sheet/sheet-class.js
  • Code Duplication · Duplicated block with local edits (28 matched lines × 2 locations) src/react/components/messagebar.jsx
  • Code Duplication · Duplicated block (27 lines × 3 locations) src/svelte/components/actions.svelte
  • Code Duplication · Duplicated block (27 lines × 3 locations) src/vue/components/actions.vue
  • Code Duplication · Duplicated block with local edits (26 matched lines × 2 locations) kitchen-sink/react/src/pages/swipeout.jsx
  • Code Duplication · Duplicated block (26 lines × 2 locations) src/core/components/panel/panel-class.js
  • Code Duplication · Duplicated block (26 lines × 2 locations) src/core/components/pie-chart/pie-chart-class.js
  • Code Duplication · Duplicated block (25 lines × 2 locations) kitchen-sink/react/src/pages/cards-expandable.jsx
  • Code Duplication · Duplicated block (25 lines × 2 locations) kitchen-sink/react/src/pages/grid.jsx
  • Code Duplication · Duplicated block (25 lines × 4 locations) kitchen-sink/react/src/pages/swipeout.jsx
  • Code Duplication · Duplicated block (25 lines × 6 locations) src/core/components/autocomplete/autocomplete-class.js
  • Code Duplication · Duplicated block (25 lines × 3 locations) src/core/components/color-picker/modules/hsb-sliders.js
  • Code Duplication · Duplicated block (25 lines × 2 locations) src/react/components/tab.jsx
  • Code Duplication · Duplicated block (25 lines × 2 locations) src/svelte/components/area-chart.svelte
  • Code Duplication · Duplicated block (24 lines × 2 locations) kitchen-sink/react/src/pages/sortable.jsx
  • Code Duplication · Duplicated block with local edits (24 matched lines × 2 locations) kitchen-sink/react/src/pages/swipeout.jsx
  • Code Duplication · Duplicated block (24 lines × 2 locations) src/core/components/swipeout/swipeout.js
  • Code Duplication · Duplicated block (24 lines × 2 locations) src/react/components/popup.jsx
  • Code Duplication · Duplicated block (24 lines × 2 locations) src/react/shared/plugin.js
  • Code Duplication · Duplicated block (23 lines × 3 locations) src/core/components/area-chart/area-chart-class.js
  • Code Duplication · Duplicated block (22 lines × 2 locations) kitchen-sink/react/src/pages/calendar.jsx
  • Code Duplication · Duplicated block (22 lines × 2 locations) kitchen-sink/react/src/pages/sheet-modal.jsx
  • Code Duplication · Duplicated block (22 lines × 3 locations) kitchen-sink/react/vite.config.js
  • Code Duplication · Duplicated block (22 lines × 2 locations) src/core/components/color-picker/modules/hsb-sliders.js
  • Code Duplication · Duplicated block (22 lines × 2 locations) src/svelte/components/block.svelte
  • Code Duplication · Duplicated block (21 lines × 2 locations) kitchen-sink/react/src/pages/color-picker.jsx
  • Code Duplication · Duplicated block (21 lines × 2 locations) kitchen-sink/vue/src/pages/tabbar-icons.vue
  • Code Duplication · Duplicated block (21 lines × 2 locations) src/core/components/area-chart/area-chart-class.js
  • Code Duplication · Duplicated block (21 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (21 lines × 2 locations) src/vue/components/input.vue
  • Code Duplication · Duplicated block (20 lines × 2 locations) kitchen-sink/react/src/pages/stepper.jsx
  • Code Duplication · Duplicated block (20 lines × 2 locations) kitchen-sink/react/src/pages/timeline.jsx
Rebuild cost: about €90,000 · Estimate
Cost to rebuild€30,000 to €150,000, for 496 to 1,573 hours of work, about 0.6 person-years for 1 to 2 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 30. 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: 105,244 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
Resolve the 6 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (6).
Raises the score by about 2 points · Low effort · Dependency Hygiene
2
Resolve the 1 No automated tests finding(s) in Code Coverage.
Raises the score by about 7 points · High effort · Code Coverage
3
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.
Raises the score by about 2 points · Medium effort · Type Safety

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 €90,000 to build again, about 0.6 person-years of work. Its weakest lens is Code Health, at 23 (Critical). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 6 Deprecated finding(s) in Dependency Hygiene. Of all the actions in this report, it raises the score most for the work it takes: about 2 points for low effort, because it clears the 6 Dependency Hygiene findings. 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 4.7 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 8% to 19% on every change. The history of the code shows how much it changes: about 984 lines over the last 90 days, which is about 3,991 lines a year. At that pace, the extra work comes to an estimated 0.8 to 5 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 · Cohesion (LCOM4) · 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.

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

107 modules, with 46 dependencies between them. Every module uses only modules listed above it, so there are no loops.

The table shows the 40 modules with the most connections; 67 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 core.shared.events-class2 core.shared.material-color-utils3 core.shared.class4 material-color-utilities.dynamiccolor.color_spec_20255 material-color-utilities.dynamiccolor.dynamic_scheme6 material-color-utilities.scheme.scheme_content7 core.components.app.app-class8 core.components.area-chart.area-chart-class9 core.components.autocomplete.autocomplete-class10 core.components.calendar.calendar-class11 core.components.color-picker.color-picker-class12 core.components.data-table.data-table-class13 core.components.gauge.gauge-class14 core.components.list-index.list-index-class15 core.components.messagebar.messagebar-class16 core.components.messages.messages-class17 core.components.modal.modal-class18 core.components.panel.panel-class19 core.components.photo-browser.photo-browser-class20 core.components.picker.picker-class21 core.components.pie-chart.pie-chart-class22 core.components.pull-to-refresh.pull-to-refresh-class23 core.components.range.range-class24 core.components.smart-select.smart-select-class25 core.components.stepper.stepper-class26 core.components.text-editor.text-editor-class27 core.components.toggle.toggle-class28 core.components.tooltip.tooltip-class29 core.components.view.view-class30 core.components.virtual-list.virtual-list-class31 core.modules.router.router-class32 core.components.actions.actions-class33 core.components.dialog.dialog-class34 core.components.login-screen.login-screen-class35 core.components.modal.custom-modal-class36 core.components.notification.notification-class37 core.components.popover.popover-class38 core.components.popup.popup-class39 core.components.sheet.sheet-class40 core.components.toast.toast-class
1 core.shared.events-class
2 core.shared.material-color-utils
3 core.shared.class1
4 material-color-utilities.dynamiccolor.color_spec_20251
5 material-color-utilities.dynamiccolor.dynamic_scheme1
6 material-color-utilities.scheme.scheme_content1
7 core.components.app.app-class1
8 core.components.area-chart.area-chart-class1
9 core.components.autocomplete.autocomplete-class1
10 core.components.calendar.calendar-class1
11 core.components.color-picker.color-picker-class1
12 core.components.data-table.data-table-class1
13 core.components.gauge.gauge-class1
14 core.components.list-index.list-index-class1
15 core.components.messagebar.messagebar-class1
16 core.components.messages.messages-class1
17 core.components.modal.modal-class1
18 core.components.panel.panel-class1
19 core.components.photo-browser.photo-browser-class1
20 core.components.picker.picker-class1
21 core.components.pie-chart.pie-chart-class1
22 core.components.pull-to-refresh.pull-to-refresh-class1
23 core.components.range.range-class1
24 core.components.smart-select.smart-select-class1
25 core.components.stepper.stepper-class1
26 core.components.text-editor.text-editor-class1
27 core.components.toggle.toggle-class1
28 core.components.tooltip.tooltip-class1
29 core.components.view.view-class1
30 core.components.virtual-list.virtual-list-class1
31 core.modules.router.router-class1
32 core.components.actions.actions-class1
33 core.components.dialog.dialog-class1
34 core.components.login-screen.login-screen-class1
35 core.components.modal.custom-modal-class1
36 core.components.notification.notification-class1
37 core.components.popover.popover-class1
38 core.components.popup.popup-class1
39 core.components.sheet.sheet-class1
40 core.components.toast.toast-class1
Uses a module listed above itPart of a loopThe module itself
1 core.shared.events-class2 core.shared.material-color-utils3 core.shared.class4 material-color-utilities.dynamiccolor.color_spec_20255 material-color-utilities.dynamiccolor.dynamic_scheme6 material-color-utilities.scheme.scheme_content7 core.components.app.app-class8 core.components.area-chart.area-chart-class9 core.components.autocomplete.autocomplete-class10 core.components.calendar.calendar-class11 core.components.color-picker.color-picker-class12 core.components.data-table.data-table-class13 core.components.gauge.gauge-class14 core.components.list-index.list-index-class15 core.components.messagebar.messagebar-class16 core.components.messages.messages-class17 core.components.modal.modal-class18 core.components.panel.panel-class19 core.components.photo-browser.photo-browser-class20 core.components.picker.picker-class21 core.components.pie-chart.pie-chart-class22 core.components.pull-to-refresh.pull-to-refresh-class23 core.components.range.range-class24 core.components.smart-select.smart-select-class25 core.components.stepper.stepper-class26 core.components.text-editor.text-editor-class27 core.components.toggle.toggle-class28 core.components.tooltip.tooltip-class29 core.components.view.view-class30 core.components.virtual-list.virtual-list-class31 core.modules.router.router-class32 core.components.actions.actions-class33 core.components.dialog.dialog-class34 core.components.login-screen.login-screen-class35 core.components.modal.custom-modal-class36 core.components.notification.notification-class37 core.components.popover.popover-class38 core.components.popup.popup-class39 core.components.sheet.sheet-class40 core.components.toast.toast-classcore.shared.events-class1core.shared.material-color-utils2core.shared.class3material-color-utilities.dynamiccolor.color_spec_20254material-color-utilities.dynamiccolor.dynamic_scheme5material-color-utilities.scheme.scheme_content6core.components.app.app-class7core.components.area-chart.area-chart-class8core.components.autocomplete.autocomplete-class9core.components.calendar.calendar-class10core.components.color-picker.color-picker-class11core.components.data-table.data-table-class12core.components.gauge.gauge-class13core.components.list-index.list-index-class14core.components.messagebar.messagebar-class15core.components.messages.messages-class16core.components.modal.modal-class17core.components.panel.panel-class18core.components.photo-browser.photo-browser-class19core.components.picker.picker-class20core.components.pie-chart.pie-chart-class21core.components.pull-to-refresh.pull-to-refresh-class22core.components.range.range-class23core.components.smart-select.smart-select-class24core.components.stepper.stepper-class25core.components.text-editor.text-editor-class26core.components.toggle.toggle-class27core.components.tooltip.tooltip-class28core.components.view.view-class29core.components.virtual-list.virtual-list-class30core.modules.router.router-class31core.components.actions.actions-class32core.components.dialog.dialog-class33core.components.login-screen.login-screen-class34core.components.modal.custom-modal-class35core.components.notification.notification-class36core.components.popover.popover-class37core.components.popup.popup-class38core.components.sheet.sheet-class39core.components.toast.toast-class4011111111111111111111111111111111111111+67 more modules (most-connected shown)

At a glance — Code Health · 23% · Critical · gated by D1, D2, R1, R10, R2, R7 ·

At a glance — Architecture · 98% · Exemplary ·

At a glance — Maturity · 55% · Adequate · gated by M2 ·

At a glance — Readiness · 24% · Critical · gated by D8, R4, P1, P3 ·

At a glance — Security · 90% · Strong ·

At a glance — Accessibility · 28% · Weak · gated by AC1, AC4 ·

At a glance — Performance · 60% · Adequate ·

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
A03:2025 — Software Supply Chain Failures42High / Critical
A05:2025 — Injection7Medium

Roadmap

Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; 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; 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.

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

Do thisHelpsEffortDimension
Resolve the 6 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (6).+2.0 ptsLowDependency Hygiene
Resolve the 1 No automated tests finding(s) in Code Coverage.+6.6 ptsHighCode Coverage
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.+2.1 ptsMediumType Safety
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.+2.1 ptsMediumText alternatives
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.+2.0 ptsMediumKeyboard semantics
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.+2.0 ptsMediumCode Duplication
Port the existing pipeline to a CI service that is still operating — the build and test steps are already specified — and remove the dead configuration and its badge so the repository stops advertising a gate that no longer exists.+1.7 ptsMediumCI/CD gates
Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.+1.7 ptsMediumSecurity & performance tooling

File quality

Per-file score 0–10 — a quality signature. Of 141 files carrying findings, judged against the Production bar: 1% slop · 72% mixed · 27% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.3MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.3MixedStatic Analysis (SAST): Medium: REDACTED
src/core/components/navbar/navbar.js6.1MixedCyclomatic Complexity: initNavbarOnScroll::handleLargeNavbarCollapse (cyclomatic 30)
src/core/components/smart-select/smart-select-class.js6.3MixedCyclomatic Complexity: SmartSelect.renderItem (cyclomatic 27)
src/core/modules/router/navigate.js6.3MixedCyclomatic Complexity: navigate.forward (cyclomatic 149)
src/core/components/form/form.js6.3MixedCyclomatic Complexity: form.formFromData (cyclomatic 22)
src/core/modules/router/router-class.js6.5MixedCyclomatic Complexity: Router.pageCallback (cyclomatic 48)
src/core/components/virtual-list/virtual-list-class.js6.5MixedCyclomatic Complexity: VirtualList.render (cyclomatic 44)
src/core/modules/router/back.js6.5MixedCyclomatic Complexity: back.backward (cyclomatic 109)
src/core/components/autocomplete/autocomplete-class.js6.5MixedCyclomatic Complexity: Autocomplete.constructor (cyclomatic 22)
src/core/modules/router/modal.js6.6MixedCyclomatic Complexity: modalLoad (cyclomatic 50)
src/core/modules/router/tab.js6.6MixedCyclomatic Complexity: tabLoad (cyclomatic 45)
package.json6.7MixedDependency Hygiene: Deprecated: conventional-changelog-cli
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
src/core/components/input/input.js6.9MixedCyclomatic Complexity: init (cyclomatic 21)
src/core/components/searchbar/searchbar-class.js7.0MixedCyclomatic Complexity: Searchbar.constructor (cyclomatic 80)
src/core/components/pull-to-refresh/pull-to-refresh-class.js7.0MixedCyclomatic Complexity: PullToRefresh.constructor::handleTouchMove (cyclomatic 66)

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 — 83

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 — 839

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 — 124

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

Could not be resolved — 11

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 57 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, 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 — 57 dimensions across the health lenses
D1D2D3D6D8D12D13D14D15D17D19D24D27D28D29D30D34D35D43D44AC1AC2AC3AC4AC6AX10AX3AX4GD1IC1M1M2M3P1P10P3P6PF3R1R10R11R2R3R4R5R6R7R8R9X12X16X21X24X28X29X3X30

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, 1034 of 1046 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 01a1dd64-2d89-7058-9a0b-b89ea1107bd2.

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.

  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (174 contributor(s) across 7146 commit(s) sampled, automation and bot accounts excluded). One of them holds 91% of the history; the other 173 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • 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.
  • 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 (packages/vue/package.json), 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.
  • D26 Project Cohesion — 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. `(repository root)` (61765 LoC, 445 module-visible types across 68 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
  • D27 Navigability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Tracing effort is measured over resolved call sites, and all 1246 sampled here came from .html/.js/.jsx files. This repository's .vue, .svelte source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
  • 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 builds user interface as HTML STRINGS — 14 script file(s) building 54 markup element(s) as HTML strings, carrying 0 role/aria/tabindex attribute(s) (e.g. src/react/components/area-chart.jsx, src/react/components/panel.jsx, kitchen-sink/react/src/pages/dialog.jsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 681 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 runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they 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.
  • 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. 148 further occurrence(s) are not listed individually; the score already reflects all 188.
  • 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 builds user interface as HTML STRINGS — 14 script file(s) building 54 markup element(s) as HTML strings, carrying 0 role/aria/tabindex attribute(s) (e.g. src/react/components/area-chart.jsx, src/react/components/panel.jsx, kitchen-sink/react/src/pages/dialog.jsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 681 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 runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they 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. 95 further occurrence(s) are not listed individually; the score already reflects all 135.
  • 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 builds user interface as HTML STRINGS — 14 script file(s) building 54 markup element(s) as HTML strings, carrying 0 role/aria/tabindex attribute(s) (e.g. src/react/components/area-chart.jsx, src/react/components/panel.jsx, kitchen-sink/react/src/pages/dialog.jsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 681 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 runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they 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 builds user interface as HTML STRINGS — 14 script file(s) building 54 markup element(s) as HTML strings, carrying 0 role/aria/tabindex attribute(s) (e.g. src/react/components/area-chart.jsx, src/react/components/panel.jsx, kitchen-sink/react/src/pages/dialog.jsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 681 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 runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they 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. 91 further occurrence(s) are not listed individually; the score already reflects all 131.
  • AC5 ARIA 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 repository builds user interface as HTML STRINGS — 14 script file(s) building 54 markup element(s) as HTML strings, carrying 0 role/aria/tabindex attribute(s) (e.g. src/react/components/area-chart.jsx, src/react/components/panel.jsx, kitchen-sink/react/src/pages/dialog.jsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 681 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 runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they 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. This repository builds user interface as HTML STRINGS — 14 script file(s) building 54 markup element(s) as HTML strings, carrying 0 role/aria/tabindex attribute(s) (e.g. src/react/components/area-chart.jsx, src/react/components/panel.jsx, kitchen-sink/react/src/pages/dialog.jsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 681 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 runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they 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. 41 further occurrence(s) are not listed individually; the score already reflects all 81.
  • AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 681 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
  • GD1 Unfinished & placeholder code — 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. 64 further occurrence(s) are not listed individually; the score already reflects all 104.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • PF3 Async & latency hygiene — 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. 6 further occurrence(s) are not listed individually; the score already reflects all 46.
  • 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. 447 further occurrence(s) are not listed individually; the score already reflects all 487.
  • 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. 214 further occurrence(s) are not listed individually; the score already reflects all 254.
  • R3 Large Files — 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. 4 further occurrence(s) are not listed individually; the score already reflects all 44.
  • R7 Dead Code — 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. 65 further occurrence(s) are not listed individually; the score already reflects all 105.
  • S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 436 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
  • 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. 46 further occurrence(s) are not listed individually; the score already reflects all 86.
  • X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, 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.
  • X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Svelte components, Vue components 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.

Repo exclusion declarations: 72 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

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.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 Complexity2.0 / 10Critical✓ 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 2.0 / 10 · rule-coverage 100% · ceiling Prevented

270 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was navigate.forward at 149. A further 3 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 autocomplete.default::onPageInit at 28 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: kitchen-sink/react/src/pages/autocomplete.jsx (autocomplete.default::onPageInit at 28), src/core/components/picker/picker-column.js (picker-column.pickerColumn at 22), src/core/components/toolbar/tabbar-highlight.js (tabbar-highlight.initTabbarHighlight at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

utils.extend (cyclomatic 16) · ×4src/core/shared/utils.js:220
PullToRefresh.constructor::handleTouchMove (cyclomatic 66) · ×3src/core/components/pull-to-refresh/pull-to-refresh-class.js:148
swipe-panel.swipePanel::handleTouchMove (cyclomatic 64) · ×3src/core/components/panel/swipe-panel.js:77
init::handleTouchMove (cyclomatic 50) · ×3src/core/components/swipeout/swipeout.js:44
mixins.actionsAttrs (cyclomatic 45) · ×3src/react/shared/mixins.js:65

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

What to do

  1. Bring the 13 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with navigate.forward (cyclomatic 149), back.backward (cyclomatic 109), Calendar.constructor (cyclomatic 95). — 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 13 together lifts Cyclomatic Complexity from 2.0 to about 3.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

D2 · Cognitive Complexity2.0 / 10Critical✓ 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 2.0 / 10 · rule-coverage 100% · ceiling Prevented

316 method(s) exceeded the cognitive complexity threshold of 15; the worst was forward at 185.

constructor::handleTouchMove (cognitive 109) · ×11src/core/components/pull-to-refresh/pull-to-refresh-class.js:148
utils.extend (cognitive 29) · ×4src/core/shared/utils.js:220
init::handleTouchMove (cognitive 82) · ×3src/core/components/swipeout/swipeout.js:44
actionsAttrs (cognitive 44) · ×3src/react/shared/mixins.js:65
mixins.actionsClasses (cognitive 23) · ×3src/react/shared/mixins.js:132

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

What to do

  1. Bring the 22 bodies over 60 down to 60 or less in Cognitive Complexity — start with forward (cognitive 185), renderMonth (cognitive 149), back.backward (cognitive 129). — 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 22 together lifts Cognitive Complexity from 2.0 to about 3.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

D3 · God Classes6.0 / 10Adequate✓ 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 6.0 / 10 · rule-coverage 100% · ceiling Prevented

111 god class(es) detected.

FunctionTooLong: list-input.ListInput · ×63src/react/components/list-input.jsx:84
MethodTooLong: Sheet.constructor · ×24src/core/components/sheet/sheet-class.js:8
FileTooLong: REDACTED · ×11REDACTED
ClassTooLong: Router · ×11src/core/modules/router/router-class.js:22
TooManyMethods: Calendar · ×2REDACTED:8

What to do

  1. Resolve the 63 FunctionTooLong finding(s) in God Classes — start with navigate.js (2), stepper.jsx (2), back.js (2). — One of this dimension's main actionable groups (63 warning-level).
  2. Resolve the 24 MethodTooLong finding(s) in God Classes — start with searchbar-class.js (2), virtual-list-class.js (2), gauge-class.js (2). — One of this dimension's main actionable groups (24 warning-level).
  3. Resolve the 11 FileTooLong finding(s) in God Classes — start with REDACTED, router-class.js, smart-select-class.js. — One of this dimension's main actionable groups (11 warning-level).

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

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

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

0 of 9 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D8 · Code Coverage0.0 / 10Critical✓ Tool-verified

What it measures: How much of the code is actually exercised by tests.

Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.

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

No automated tests — no test code was found in this repository.

No automated tests

What to do

  1. Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).

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

D12 · Dependency Hygiene7.9 / 10Strong✓ 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 7.9 / 10 · rule-coverage 100% · ceiling Verified

2 outdated direct production npm dependency(ies) of 6 graded, 0 pinning defect(s), across 2 package.json (2 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 4 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.

Deprecated: conventional-changelog-cli · ×4package.json:92
Deprecated: fsevents · ×6REDACTED:7978
Outdated (npm): path-to-regexppackage.json:71
Outdated (npm): swiper

What to do

  1. Resolve the 6 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (6). — One of this dimension's main actionable groups (6 recommendation-level).
  2. Resolve the 4 Deprecated finding(s) in Dependency Hygiene — start with package.json (4). — One of this dimension's main actionable groups (4 warning-level).
  3. Resolve the 1 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json. — One of this dimension's main actionable groups (1 recommendation-level).

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.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 6 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 6 package(s) this repository's committed lockfile installs for a consumer — its 6 production, optional and peer dependency(ies), across 2 product package.json manifest(s), and everything those install in turn. Its 45 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under MIT, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ 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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D17 · Explicit Debt9.9 / 10Stronggated by 1 serious finding✓ Tool-verified

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 9.9 / 10 · rule-coverage 100% · ceiling Prevented

1 deducted task-comment markers across 95 LoC (0.0/KLoC) → score 9.9. 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.

HackCommentscripts/icon-font/generate_font.py:41

What to do

  1. Resolve the 1 HackComment finding(s) in Explicit Debt — start with generate_font.py. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.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

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

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D24 · Comment Value3.2 3.0 / 10Weak✓ 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 3.0 / 10 · rule-coverage 94% · ceiling Documented

25 of 370 judged comments only repeat the code they sit on (6.8 %). 67 comment(s) in another language or script were not judged.

redundant comment · ×21scripts/build-react.js:81

What to do

  1. Resolve the 21 redundant comment finding(s) in Comment Value — start with navbar.js (3), form.js (2), smart-select-class.js (2). — One of this dimension's main actionable groups (21 recommendation-level).

Detailed fixes: d24_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

26 % 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. Measured over the .html/.js/.jsx source only — this repository's .vue, .svelte was not sampled for call sites, so this score covers part of the tree, not all of it.

✓ 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)7.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 7.0 / 10 · rule-coverage 100% · ceiling Documented

7 finding(s): 0 critical, 0 high, 7 medium, 0 low.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

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 0.0 / 10 · rule-coverage 100% · ceiling Documented

42 finding(s): 3 critical, 22 high, 11 medium, 6 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 21 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (21). — One of this dimension's main actionable groups (21 issue-level).
  2. Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
  3. Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.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 389 of the 840 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.

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 0 platform declaration(s) and 6 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 alternatives1.0 / 10Critical✓ 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. (×40) — kitchen-sink/react/src/pages/action-sheet.jsx:120, kitchen-sink/react/src/pages/action-sheet.jsx:129, kitchen-sink/react/src/pages/action-sheet.jsx:138, …

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 & labels4.6 / 10Weak✓ 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 UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×33) — kitchen-sink/react/src/pages/calendar.jsx:80, kitchen-sink/react/src/pages/calendar.jsx:85, kitchen-sink/react/src/pages/calendar.jsx:97, …
  • This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×3) — kitchen-sink/react/src/pages/data-table.jsx:265, kitchen-sink/react/src/pages/data-table.jsx:271, kitchen-sink/react/src/pages/data-table.jsx:277
  • This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — kitchen-sink/react/src/pages/data-table.jsx:283
  • This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×3) — kitchen-sink/react/src/pages/gauge.jsx:28, kitchen-sink/react/src/pages/icons.jsx:59, kitchen-sink/react/src/pages/progressbar.jsx:85

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.8 / 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>. — kitchen-sink/core/index.html:2
  • user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. (×4) — kitchen-sink/core/index.html:6, kitchen-sink/react/index.html:6, kitchen-sink/svelte/index.html:6, …
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it. (×3) — kitchen-sink/react/index.html:2, kitchen-sink/svelte/index.html:2, kitchen-sink/vue/index.html:2

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 semantics1.2 / 10Critical✓ 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. (×3) — kitchen-sink/react/src/pages/color-themes.jsx:104, kitchen-sink/react/src/pages/color-themes.jsx:111, kitchen-sink/react/src/pages/sheet-modal.jsx:301
  • 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. (×31) — kitchen-sink/react/src/pages/data-table.jsx:564, kitchen-sink/react/src/pages/data-table.jsx:565, kitchen-sink/react/src/pages/fab-morph.jsx:42, …
  • The repo's own CSS styles .swipe-handler with `cursor: pointer`, so this <div> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler. (×3) — kitchen-sink/react/src/pages/popup.jsx:221, kitchen-sink/react/src/pages/sheet-modal.jsx:274, kitchen-sink/react/src/pages/sheet-modal.jsx:344
  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×3) — kitchen-sink/svelte/src/pages/color-themes.svelte:102, kitchen-sink/svelte/src/pages/color-themes.svelte:107, kitchen-sink/svelte/src/pages/tabbar-icons.svelte:24

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC6 · Visual & motion safety5.0 / 10Weak✓ 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.

  • `button.text-editor-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/core/components/text-editor/text-editor.less:38
  • `.text-editor-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/core/components/text-editor/text-editor.less:79
  • `.searchbar-disable-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/core/components/searchbar/searchbar.less:144
  • `input[type='text']` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/core/components/input/input.less:22
  • `.input-clear-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/core/components/input/input.less:217
  • `.color-picker-bar-value input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/core/components/color-picker/color-picker.less:267
  • `.button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/core/components/button/button.less:21
  • `.area-chart-legend-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/core/components/area-chart/area-chart.less:91
  • `a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/core/components/app/app.less:90
  • `.ripple-wave` moves (`animation: touch-ripple-in 200ms 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. — src/core/components/touch-ripple/touch-ripple.less:33
  • `.item-link .ripple-wave` moves (`animation: touch-ripple-in-blurred 250ms 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. — src/core/components/touch-ripple/touch-ripple.less:63
  • `.tooltip` moves (`transition-property: opacity, transform`) 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. — src/core/components/tooltip/tooltip.less:18
  • `.ios .swipeout-overswipe` moves (`transition-property: transform, left, width, margin-left, margin-right`) 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. — src/core/components/swipeout/swipeout-ios.less:37
  • `.swipeout-transitioning .swipeout-content` moves (`transition-property: transform, left, background-color, border-radius, opacity`) 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. — src/core/components/swipeout/swipeout.less:18
  • `.swipeout-transitioning .swipeout-actions-right a` moves (`transition-property: transform, left, width, margin-left, margin-right`) 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. — src/core/components/swipeout/swipeout.less:24
  • `.page-content.with-searchbar-expandable-enabled` moves (`transition-property: transform`) 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. — src/core/components/searchbar/searchbar.less:216
  • `.md .range-knob` moves (`transition-property: transform, background-color`) 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. — src/core/components/range/range-md.less:9
  • `.range-knob-label` moves (`transition-property: transform`) 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. — src/core/components/range/range.less:110
  • `.ios .ptr-transitioning > *` moves (`transition-property: transform`) 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. — src/core/components/pull-to-refresh/pull-to-refresh-ios.less:30
  • `.ios .ptr-pull-up .ptr-preloader .preloader` moves (`animation: ios-ptr-preloader-spin 1s 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. — src/core/components/pull-to-refresh/pull-to-refresh-ios.less:42
  • `.ios .ptr-bottom.ptr-transitioning > *` moves (`transition-property: transform`) 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. — src/core/components/pull-to-refresh/pull-to-refresh-ios.less:66
  • `.md .ptr-transitioning .ptr-preloader` moves (`transition-property: transform, opacity`) 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. — src/core/components/pull-to-refresh/pull-to-refresh-md.less:95
  • `.ios .progressbar-infinite:before` moves (`animation: ios-progressbar-infinite 1s linear infinite`) 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. — src/core/components/progressbar/progressbar-ios.less:4
  • `.ios .progressbar-infinite.color-multi:before` moves (`animation: ios-progressbar-infinite-multicolor 3s linear infinite`) 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. — src/core/components/progressbar/progressbar-ios.less:27
  • `.md .progressbar-infinite:before` moves (`animation: md-progressbar-infinite-1 2s linear infinite`) 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. — src/core/components/progressbar/progressbar-md.less:20
  • `.md .progressbar-infinite:after` moves (`animation: md-progressbar-infinite-2 2s linear infinite`) 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. — src/core/components/progressbar/progressbar-md.less:23
  • `.md .progressbar-infinite.color-multi:after` moves (`animation: md-progressbar-infinite-multicolor-fill 3s linear infinite`) 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. — src/core/components/progressbar/progressbar-md.less:32
  • `.progressbar-in` moves (`animation: progressbar-in 150ms 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. — src/core/components/progressbar/progressbar.less:62
  • `.progressbar-out` moves (`animation: progressbar-out 150ms 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. — src/core/components/progressbar/progressbar.less:65
  • `.ios .preloader-inner` moves (`animation: ios-preloader-spin 1s steps(8, end) infinite`) 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. — src/core/components/preloader/preloader-ios.less:6
  • `.md .preloader-inner circle` moves (`animation: md-preloader-circle-rotate @speed * 4 ease-in-out infinite`) 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. — src/core/components/preloader/preloader-md.less:11
  • `.md .preloader-inner` moves (`animation: md-preloader-rotate @speed linear infinite`) 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. — src/core/components/preloader/preloader-md.less:7
  • `.md .preloader-multi-color circle` moves (`animation: md-preloader-circle-rotate @speed * 4 ease-in-out infinite, md-preloader-multicolor @speed * 4 ease-in-out infinite`) 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. — src/core/components/preloader/preloader-md.less:24
  • `.md .popover` moves (`transition-property: opacity, transform`) 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. — src/core/components/popover/popover-md.less:4
  • `.photo-browser-standalone.modal-in` moves (`animation: photo-browser-in 400ms`) 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. — src/core/components/photo-browser/photo-browser.less:15
  • `.photo-browser-standalone.modal-out` moves (`animation: photo-browser-out 400ms`) 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. — src/core/components/photo-browser/photo-browser.less:19
  • `.ios .router-transition-forward .page-next` moves (`animation: ios-page-next-to-current var(--f7-page-transition-duration) 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. — src/core/components/page/page-ios.less:27
  • `.ios .router-transition-forward .page-current` moves (`animation: ios-page-current-to-previous var(--f7-page-transition-duration) 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. — src/core/components/page/page-ios.less:36
  • `.ios .router-transition-backward .page-previous` moves (`animation: ios-page-previous-to-current var(--f7-page-transition-duration) 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. — src/core/components/page/page-ios.less:47
  • `.ios .router-transition-backward .page-current` moves (`animation: ios-page-current-to-next var(--f7-page-transition-duration) 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. — src/core/components/page/page-ios.less:56

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 composition10.0 / 10Exemplary✓ 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.

GD1 · Unfinished & placeholder code9.5 / 10Exemplary✓ Tool-verified

Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

  • A placeholder string ("Lorem Ipsum") is still in shipped code — typical of generated boilerplate that was never filled in. (×2) — kitchen-sink/react/src/pages/accordion.jsx:18, kitchen-sink/react/src/pages/accordion.jsx:58
  • A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in. (×32) — kitchen-sink/react/src/pages/accordion.jsx:21, kitchen-sink/react/src/pages/accordion.jsx:44, kitchen-sink/react/src/pages/accordion.jsx:61, …
  • A placeholder string ("Another card. Lorem ipsum dolor sit amet…") is still in shipped code — typical of generated boilerplate that was never filled in. (×3) — kitchen-sink/react/src/pages/cards.jsx:35, kitchen-sink/react/src/pages/cards.jsx:50, kitchen-sink/react/src/pages/cards.jsx:76
  • A placeholder string ("Lorem ipsum dolor sit amet consectetur a…") is still in shipped code — typical of generated boilerplate that was never filled in. — kitchen-sink/react/src/pages/content-block.jsx:33
  • A placeholder string ("Lorem ipsum dolor sit amet, consectetur") is still in shipped code — typical of generated boilerplate that was never filled in. — kitchen-sink/react/src/pages/messages.jsx:42
  • A placeholder string ("<div class="popup"> <div cla…") is still in shipped code — typical of generated boilerplate that was never filled in. — kitchen-sink/react/src/pages/popup.jsx:23

What to do

  • Finish or delete the functions that still throw "not implemented", and replace placeholder text before shipping.
IC1 · Incompleteness & stubs8.4 / 10Strong✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. — src/core/components/autocomplete/autocomplete-class.js:386
  • `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. — src/react/components/toggle.jsx:128
  • A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. (×4) — kitchen-sink/vue/src/app.js:12, src/core/components/swiper/swiper.js:11, src/core/shared/material-colors.js:11, …

What to do

  • Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
M1 · Documentation (README)8.7 / 10Strong✓ 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.

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation0.0 / 10Critical✓ 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.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure8.0 / 10Strong✓ 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.

P1 · CI/CD gates0.0 / 10Critical✓ 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.

  • The pipeline is well-formed, but the only CI definition is `.travis.yml`, and its `README.md` build badge still points at `travis-ci.org` — a service shut down in June 2021. No other CI is configured in this repository, so nothing has been building or testing changes here since that shutdown — the steps below describe a gate that is not running. Porting it is mostly mechanical: the build and test commands already written here are what a replacement pipeline would run.

What to do

  • Port the existing pipeline to a CI service that is still operating — the build and test steps are already specified — and remove the dead configuration and its badge so the repository stops advertising a gate that no longer exists.
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.

P3 · Security & performance tooling0.0 / 10Critical✓ 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.

  • No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
  • `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:68

What to do

  • Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release 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.

PF3 · Async & latency hygiene6.0 / 10Adequate✓ 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.

  • `fs.readFileSync` in `modular` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — scripts/build-core-js.js:27, scripts/build-core-js.js:28, scripts/build-core-js.js:115
  • `fs.writeFileSync` in `modular` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×6) — scripts/build-core-js.js:90, scripts/build-core-js.js:92, scripts/build-core-js.js:95, …
  • `fs.readFileSync` in `callback to files.forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/build-core-js.js:120
  • `fs.writeFileSync` in `callback to files.forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/build-core-js.js:121
  • `fs.writeFileSync` in `callback to then` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — scripts/build-core-js.js:209, scripts/build-core-js.js:210, scripts/build-material-color-utils.js:34
  • `fs.existsSync` in `callback to components.forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/build-core-js.js:236
  • `fs.readFileSync` in `buildComponentsStyles` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/build-core-styles.js:27
  • `fs.existsSync` in `callback to components.filter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/build-core-styles.js:49
  • `fs.readFileSync` in `callback to componentsToProcess.forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/build-core-styles.js:56
  • `fs.writeFileSync` in `callback to componentsToProcess.forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/build-core-styles.js:73
  • `fs.readFileSync` in `buildBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/build-core-styles.js:137
  • `fs.writeFileSync` in `buildBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — scripts/build-core-styles.js:161, scripts/build-core-styles.js:172
  • `fs.readFileSync` in `buildCore` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/build-core-styles.js:187
  • `fs.writeFileSync` in `buildCore` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — scripts/build-core-styles.js:206, scripts/build-core-styles.js:217
  • `fs.readdirSync` in `buildReact` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/build-react.js:48
  • `fs.readFileSync` in `buildReact` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — scripts/build-react.js:64, scripts/build-react.js:74
  • `fs.writeFileSync` in `buildReact` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — scripts/build-react.js:72, scripts/build-react.js:76
  • `fs.readFileSync` in `buildSponsorsList` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/build-sponsors.js:112
  • `fs.writeFileSync` in `buildSponsorsList` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/build-sponsors.js:126
  • `fs.readdirSync` in `buildSvelte` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — scripts/build-svelte.js:15, scripts/build-svelte.js:17
  • `fs.readFileSync` in `buildSvelte` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — scripts/build-svelte.js:36, scripts/build-svelte.js:57
  • `fs.writeFileSync` in `buildSvelte` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — scripts/build-svelte.js:44, scripts/build-svelte.js:59
  • `fs.copyFileSync` in `callback to svelteComponents.forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/build-svelte.js:48
  • `fs.copyFileSync` in `callback to svelteShared.forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/build-svelte.js:54

What to do

  • TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
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 · 857 plain JS — the untyped files are kitchen-sink/react/src/app.js, kitchen-sink/react/src/app.jsx, kitchen-sink/react/src/pages/404.jsx, kitchen-sink/react/src/pages/about.jsx, kitchen-sink/react/src/pages/accordion.jsx, kitchen-sink/react/src/pages/action-sheet.jsx (+851 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.5 / 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.

  • 116 duplicated blocks under src/core/components/ have copies in at least two of the sibling directories accordion, actions, area-chart, autocomplete, calendar, card (+36 more sibling(s) not listed) — 85 of them are reported below, and 31 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 116 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 116 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 116 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/core/components/photo-browser/photo-browser-class.js:635
  • 88 duplicated blocks under src/ have copies in at least two of the sibling directories core, react, svelte, vue — 64 of them are reported below, and 24 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 88 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 88 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 88 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/react/shared/components-router.js:2
  • 49 duplicated blocks under kitchen-sink/ have copies in at least two of the sibling directories react, svelte, vue — 41 of them are reported below, and 8 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 49 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 49 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 49 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — kitchen-sink/react/src/pages/picker.jsx:12
  • 6 of the duplicated blocks reported below have copies in at least two of the sibling directories components, modules, shared under src/core/. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/core/components/popover/popover.js:34
  • src/core/modules/router/back.js:23 · src/core/modules/router/navigate.js:37 — the two spans are one implementation copied and then locally edited — 1813 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. — src/core/modules/router/back.js:23
  • src/react/components/input.jsx:149 · src/react/components/list-input.jsx:164 — the two spans are one implementation copied and then locally edited — 1514 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. — src/react/components/input.jsx:149
  • src/svelte/components/input.svelte:35 · src/svelte/components/list-input.svelte:41 — the two spans are one implementation copied and then locally edited — 1351 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. — src/svelte/components/input.svelte:35
  • kitchen-sink/react/src/pages/picker.jsx:12 · kitchen-sink/vue/src/pages/picker.vue:124 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — kitchen-sink/react/src/pages/picker.jsx:12
  • src/react/shared/components-router.js:2 · src/svelte/shared/components-router.js:3 · src/vue/shared/components-router.js:2 — these 3 files are line-for-line copies of one another — 139 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — src/react/shared/components-router.js:2
  • src/core/components/photo-browser/photo-browser-class.js:635 · src/core/components/smart-select/smart-select-class.js:815 — the two spans are one implementation copied and then locally edited — 609 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. — src/core/components/photo-browser/photo-browser-class.js:635
  • src/core/components/panel/resizable-panel.js:4 · src/core/components/view/resizable-view.js:4 — the two spans are one implementation copied and then locally edited — 866 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. — src/core/components/panel/resizable-panel.js:4
  • src/react/components/area-chart.jsx:35 · src/svelte/components/area-chart.svelte:7 — the two spans are one implementation copied and then locally edited — 677 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. — src/react/components/area-chart.jsx:35
  • src/core/components/pull-to-refresh/pull-to-refresh-class.js:180 · src/core/components/pull-to-refresh/pull-to-refresh-class.js:429 — the two spans are one implementation copied and then locally edited — 536 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. — src/core/components/pull-to-refresh/pull-to-refresh-class.js:180
  • src/core/components/color-picker/modules/hs-spectrum.js:16 · src/core/components/color-picker/modules/sb-spectrum.js:15 — the two spans are one implementation copied and then locally edited — 621 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. — src/core/components/color-picker/modules/hs-spectrum.js:16
  • src/vue/components/input.vue:99 · src/vue/components/list-input.vue:123 — 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. — src/vue/components/input.vue:99
  • src/core/components/color-picker/modules/rgb-bars.js:113 · src/core/components/color-picker/modules/rgb-sliders.js:116 — the two spans are one implementation copied and then locally edited — 617 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. — src/core/components/color-picker/modules/rgb-bars.js:113
  • kitchen-sink/react/src/pages/tabbar-icons.jsx:1 · kitchen-sink/react/src/pages/tabbar.jsx:1 — these 2 files are line-for-line copies of one another — 77 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — kitchen-sink/react/src/pages/tabbar-icons.jsx:1
  • src/react/shared/mixins.js:1 · src/svelte/shared/mixins.js:1 — these 2 files are line-for-line copies of one another — 74 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — src/react/shared/mixins.js:1
  • kitchen-sink/react/src/pages/dialog.jsx:5 · kitchen-sink/svelte/src/pages/dialog.svelte:4 — the two spans are one implementation copied and then locally edited — 396 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. — kitchen-sink/react/src/pages/dialog.jsx:5
  • kitchen-sink/react/src/pages/dialog.jsx:5 · kitchen-sink/vue/src/pages/dialog.vue:58 — the two spans are one implementation copied and then locally edited — 409 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. — kitchen-sink/react/src/pages/dialog.jsx:5
  • kitchen-sink/react/src/pages/tabs-animated.jsx:1 · kitchen-sink/react/src/pages/tabs-static.jsx:1 · kitchen-sink/react/src/pages/tabs-swipeable.jsx:1 — these 3 files are line-for-line copies of one another — 71 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — kitchen-sink/react/src/pages/tabs-animated.jsx:1
  • REDACTED:1990 · src/core/components/picker/picker-class.js:525 — 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. — REDACTED:1990
  • src/core/components/color-picker/modules/sb-spectrum.js:31 · src/core/components/color-picker/modules/wheel.js:61 — the two spans are one implementation copied and then locally edited — 586 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. — src/core/components/color-picker/modules/sb-spectrum.js:31
  • src/react/shared/mixins.js:65 · src/svelte/shared/mixins.js:65 · src/vue/shared/mixins.js:154 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/react/shared/mixins.js:65
  • src/core/components/popover/popover-class.js:7 · src/core/components/popup/popup-class.js:7 — the two spans are one implementation copied and then locally edited — 437 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. — src/core/components/popover/popover-class.js:7
  • src/core/components/color-picker/modules/brightness-slider.js:10 · src/core/components/color-picker/modules/hsb-sliders.js:58 — the two spans are one implementation copied and then locally edited — 430 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. — src/core/components/color-picker/modules/brightness-slider.js:10
  • src/vue/components/login-screen.vue:33 · src/vue/components/popover.vue:55 — the two spans are one implementation copied and then locally edited — 325 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. — src/vue/components/login-screen.vue:33
  • src/svelte/components/view.svelte:132 · src/vue/components/view.vue:275 — the two spans are one implementation copied and then locally edited — 360 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. — src/svelte/components/view.svelte:132
  • kitchen-sink/react/src/pages/toast.jsx:51 · kitchen-sink/vue/src/pages/toast.vue:84 — the two spans are one implementation copied and then locally edited — 330 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. — kitchen-sink/react/src/pages/toast.jsx:51
  • src/svelte/components/actions.svelte:43 · src/svelte/components/popover.svelte:39 — 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. — src/svelte/components/actions.svelte:43
  • src/react/components/list-input.jsx:244 · src/vue/components/list-input.vue:219 — the two spans are one implementation copied and then locally edited — 303 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. — src/react/components/list-input.jsx:244
  • src/svelte/components/range.svelte:7 · src/svelte/components/stepper.svelte:7 — the two spans are one implementation copied and then locally edited — 209 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. — src/svelte/components/range.svelte:7
  • src/react/shared/f7.js:2 · src/vue/shared/f7.js:2 — these 2 files are line-for-line copies of one another — 50 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — src/react/shared/f7.js:2
  • src/core/components/data-table/data-table.js:16 · src/core/components/messages/messages.js:20 — 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. — src/core/components/data-table/data-table.js:16
  • src/svelte/components/list.svelte:164 · src/vue/components/list.vue:110 — the two spans are one implementation copied and then locally edited — 228 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. — src/svelte/components/list.svelte:164
  • src/core/components/dialog/dialog.js:56 · src/core/components/dialog/dialog.js:107 — the two spans are one implementation copied and then locally edited — 260 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. — src/core/components/dialog/dialog.js:56
  • src/core/modules/router/modal.js:189 · src/core/modules/router/tab.js:157 — the two spans are one implementation copied and then locally edited — 203 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. — src/core/modules/router/modal.js:189
  • src/react/shared/router-open-in.jsx:9 · src/vue/shared/router-open-in.js:9 — the two spans are one implementation copied and then locally edited — 245 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. — src/react/shared/router-open-in.jsx:9
  • src/vue/components/popover.vue:61 · src/vue/components/popup.vue:82 — 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. — src/vue/components/popover.vue:61
  • src/core/components/popup/popup-class.js:22 · src/core/components/sheet/sheet-class.js:25 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/core/components/popup/popup-class.js:22

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.
R11 · Import Boundaries9.2 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).

Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.

  • scripts/banners/core.js:1 reaches into another package with a relative path (../../packages/core/package.json) — import the package by name instead. — scripts/banners/core.js:1
  • scripts/banners/svelte.js:1 reaches into another package with a relative path (../../packages/svelte/package.json) — import the package by name instead. — scripts/banners/svelte.js:1
  • scripts/release.js:8 reaches into another package with a relative path (../packages/core/package.json) — import the package by name instead. — scripts/release.js:8
  • scripts/release.js:9 reaches into another package with a relative path (../packages/react/package.json) — import the package by name instead. — scripts/release.js:9
  • scripts/release.js:10 reaches into another package with a relative path (../packages/vue/package.json) — import the package by name instead. — scripts/release.js:10
  • scripts/release.js:11 reaches into another package with a relative path (../packages/svelte/package.json) — import the package by name instead. — scripts/release.js:11

What to do

  • Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity3.0 / 10Weak✓ 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.

  • forward has cyclomatic complexity 132 and cognitive complexity 167; 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. — src/core/modules/router/navigate.js:20
  • backward has cyclomatic complexity 92 and cognitive complexity 110; 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. — src/core/modules/router/back.js:11
  • show has cyclomatic complexity 84 and cognitive complexity 118; 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. — src/core/components/tabs/tabs.js:5
  • back has cyclomatic complexity 81 and cognitive complexity 101; 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. — src/core/modules/router/back.js:460
  • handleTouchMove has cyclomatic complexity 66 and cognitive complexity 109; 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. — src/core/components/pull-to-refresh/pull-to-refresh-class.js:148
  • handleTouchMove has cyclomatic complexity 64 and cognitive complexity 106; 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. — src/core/components/panel/swipe-panel.js:77
  • renderToolbar has cyclomatic complexity 64 and cognitive complexity 70; 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. — src/core/components/picker/picker-class.js:263
  • ListItemContent has cyclomatic complexity 63 and cognitive complexity 67; 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. — src/vue/components/list-item.vue:22
  • handleTouchEnd has cyclomatic complexity 59 and cognitive complexity 106; 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. — src/core/components/sheet/sheet-class.js:306
  • renderMonth has cyclomatic complexity 56 and cognitive complexity 137; 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. — REDACTED:1145
  • open has cyclomatic complexity 51 and cognitive complexity 66; 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. — src/core/components/card/card.js:9
  • handleTouchMove has cyclomatic complexity 50 and cognitive complexity 82; 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. — src/core/components/swipeout/swipeout.js:44
  • handleTouchEnd has cyclomatic complexity 50 and cognitive complexity 66; 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. — src/core/components/panel/swipe-panel.js:216
  • constructor has cyclomatic complexity 48 and cognitive complexity 61; 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. — src/core/components/searchbar/searchbar-class.js:9
  • (anonymous) has cyclomatic complexity 45 and cognitive complexity 47; 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. — src/vue/components/list-input.vue:420
  • actionsAttrs has cyclomatic complexity 45 and cognitive complexity 44; 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. (×3) — src/react/shared/mixins.js:65, src/svelte/shared/mixins.js:65, src/vue/shared/mixins.js:154
  • render has cyclomatic complexity 44 and cognitive complexity 82; 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. — src/core/components/virtual-list/virtual-list-class.js:221
  • handleClicks has cyclomatic complexity 43 and cognitive complexity 52; 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. — src/core/modules/clicks/clicks.js:6
  • ListItemContent has cyclomatic complexity 43 and cognitive complexity 47; 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. — src/react/components/list-item-content.jsx:8
  • handleTouchMove has cyclomatic complexity 40 and cognitive complexity 57; 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. — src/core/modules/router/swipe-back.js:53
  • navigate has cyclomatic complexity 40 and cognitive complexity 52; 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. — src/core/modules/router/navigate.js:623
  • calcDevice has cyclomatic complexity 39 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 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. — REDACTED:6
  • ListItem has cyclomatic complexity 38 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 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. — src/react/components/list-item.jsx:135
  • pageCallback has cyclomatic complexity 38 and cognitive complexity 34; 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. — src/core/modules/router/router-class.js:649
  • load has cyclomatic complexity 37 and cognitive complexity 36; 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. — src/core/modules/router/navigate.js:503
  • ListInput has cyclomatic complexity 36 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. — src/react/components/list-input.jsx:84
  • search has cyclomatic complexity 35 and cognitive complexity 58; 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. — src/core/components/searchbar/searchbar-class.js:516
  • handleTouchMove has cyclomatic complexity 33 and cognitive complexity 48; 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. — src/core/components/sheet/sheet-class.js:198
  • resize has cyclomatic complexity 33 and cognitive complexity 43; 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. — src/core/components/popover/popover-class.js:182
  • getInitialUrl has cyclomatic complexity 33 and cognitive complexity 40; 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. — src/core/modules/router/router-class.js:869
  • close has cyclomatic complexity 33 and cognitive complexity 39; 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. — src/core/components/card/card.js:390
  • handleMouseWheel has cyclomatic complexity 32 and cognitive complexity 57; 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. — src/core/components/pull-to-refresh/pull-to-refresh-class.js:415
  • handleTouchEnd has cyclomatic complexity 30 and cognitive complexity 49; 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. — src/core/components/sortable/sortable.js:159
  • handleLargeNavbarCollapse has cyclomatic complexity 30 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. — src/core/components/navbar/navbar.js:329
  • handleTouchStart has cyclomatic complexity 30 and cognitive complexity 34; 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. — src/core/components/panel/swipe-panel.js:33
  • dateInRange has cyclomatic complexity 29 and cognitive complexity 56; 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. — REDACTED:1073
  • handleTouchEnd has cyclomatic complexity 29 and cognitive complexity 40; 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. — src/core/components/swipeout/swipeout.js:312
  • handleTouchMove has cyclomatic complexity 29 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. — src/core/modules/touch/touch.js:252
R3 · Large Files7.9 / 10Strong✓ 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.

  • REDACTED has 1949 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • src/core/modules/router/router-class.js has 1048 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/modules/router/router-class.js:1
  • src/svelte/components/list-item.svelte has 1027 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/svelte/components/list-item.svelte:1
  • src/core/components/smart-select/smart-select-class.js has 928 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/components/smart-select/smart-select-class.js:1
  • src/core/components/autocomplete/autocomplete-class.js has 876 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/components/autocomplete/autocomplete-class.js:1
  • kitchen-sink/vue/src/pages/data-table.vue has 801 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — kitchen-sink/vue/src/pages/data-table.vue:1
  • src/core/modules/router/navigate.js has 794 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/modules/router/navigate.js:1
  • src/core/components/color-picker/color-picker-class.js has 793 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/components/color-picker/color-picker-class.js:1
  • src/svelte/components/list-input.svelte has 773 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/svelte/components/list-input.svelte:1
  • src/core/components/photo-browser/photo-browser-class.js has 749 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/components/photo-browser/photo-browser-class.js:1
  • src/core/components/sheet/sheet-class.js has 729 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/components/sheet/sheet-class.js:1
  • src/core/modules/router/back.js has 712 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/modules/router/back.js:1
  • kitchen-sink/react/src/pages/data-table.jsx has 707 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — kitchen-sink/react/src/pages/data-table.jsx:1
  • kitchen-sink/svelte/src/pages/data-table.svelte has 703 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — kitchen-sink/svelte/src/pages/data-table.svelte:1
  • kitchen-sink/svelte/src/routes.js has 647 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — kitchen-sink/svelte/src/routes.js:1
  • src/svelte/components/input.svelte has 647 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/svelte/components/input.svelte:1
  • src/core/components/searchbar/searchbar-class.js has 634 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/components/searchbar/searchbar-class.js:1
  • src/core/components/swipeout/swipeout.js has 627 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/components/swipeout/swipeout.js:1
  • src/core/components/navbar/navbar.js has 613 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/components/navbar/navbar.js:1
  • src/core/components/range/range-class.js has 597 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/components/range/range-class.js:1
  • src/core/components/virtual-list/virtual-list-class.js has 582 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/components/virtual-list/virtual-list-class.js:1
  • src/core/shared/utils.js has 572 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/shared/utils.js:1
  • src/core/components/picker/picker-class.js has 559 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/components/picker/picker-class.js:1
  • src/vue/components/list-item.vue has 559 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/vue/components/list-item.vue:1
  • src/core/components/card/card.js has 547 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/components/card/card.js:1
  • src/core/components/pull-to-refresh/pull-to-refresh-class.js has 547 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/components/pull-to-refresh/pull-to-refresh-class.js:1
  • kitchen-sink/react/src/pages/color-picker.jsx has 545 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — kitchen-sink/react/src/pages/color-picker.jsx:1
  • kitchen-sink/vue/src/pages/color-picker.vue has 540 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — kitchen-sink/vue/src/pages/color-picker.vue:1
  • src/core/components/text-editor/text-editor-class.js has 522 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/components/text-editor/text-editor-class.js:1
  • src/core/components/panel/panel-class.js has 516 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/components/panel/panel-class.js:1
  • src/react/components/list-input.jsx has 515 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/react/components/list-input.jsx:1
  • kitchen-sink/vue/src/pages/autocomplete.vue has 504 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — kitchen-sink/vue/src/pages/autocomplete.vue:1
  • src/vue/components/list-input.vue has 502 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/vue/components/list-input.vue:1
  • src/react/components/input.jsx has 494 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/react/components/input.jsx:1
  • src/core/components/messages/messages-class.js has 484 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/components/messages/messages-class.js:1
  • src/core/modules/touch/touch.js has 479 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/modules/touch/touch.js:1
  • src/vue/components/input.vue has 462 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/vue/components/input.vue:1
  • kitchen-sink/react/src/pages/autocomplete.jsx has 440 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — kitchen-sink/react/src/pages/autocomplete.jsx:1
  • kitchen-sink/svelte/src/pages/autocomplete.svelte 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. — kitchen-sink/svelte/src/pages/autocomplete.svelte:1
  • src/core/modules/component/component-class.js has 427 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/core/modules/component/component-class.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 Coverage0.0 / 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.

  • 0% of 742 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness9.4 / 10Exemplary✓ Tool-verified

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

R6 · Tooling6.7 / 10Adequate✓ 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 Code1.9 / 10Critical✓ 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.

  • Unreachable from the 308 application, 98 tooling and 0 test entry point(s) detected in this repo. Nothing this repository declares compiles or type-checks these files, so a wrong deletion here would raise no compile error — gate removals on `npm test`, which loads the modules, and note that it only covers what it exercises. An undetected custom entry would make these reachable.
  • no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/calendar/calendar.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — REDACTED
  • no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/smart-select/smart-select.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/core/components/smart-select/smart-select-class.js
  • no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/autocomplete/autocomplete.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/core/components/autocomplete/autocomplete-class.js
  • no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/color-picker/color-picker.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/core/components/color-picker/color-picker-class.js
  • no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/photo-browser/photo-browser.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/core/components/photo-browser/photo-browser-class.js
  • no import path from any entry point (308 application, 98 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×15) — src/core/components/navbar/navbar.js, src/core/components/swipeout/swipeout.js, src/core/components/card/card.js, …
  • no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/virtual-list/virtual-list.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/core/components/virtual-list/virtual-list-class.js
  • no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/picker/picker.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/core/components/picker/picker-class.js
  • no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/pull-to-refresh/pull-to-refresh.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/core/components/pull-to-refresh/pull-to-refresh-class.js
  • no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/messages/messages.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/core/components/messages/messages-class.js
  • no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/area-chart/area-chart.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/core/components/area-chart/area-chart-class.js
  • no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/stepper/stepper.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/core/components/stepper/stepper-class.js
  • no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/messagebar/messagebar.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/core/components/messagebar/messagebar-class.js
  • no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/list-index/list-index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/core/components/list-index/list-index-class.js
  • no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/tooltip/tooltip.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/core/components/tooltip/tooltip-class.js
  • no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/gauge/gauge.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/core/components/gauge/gauge-class.js
  • no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/pie-chart/pie-chart.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/core/components/pie-chart/pie-chart-class.js
  • no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/dialog/dialog.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/core/components/dialog/dialog-class.js
  • no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/notification/notification.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — REDACTED
  • no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/color-picker/color-picker-class.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×4) — src/core/components/color-picker/modules/rgb-sliders.js, src/core/components/color-picker/modules/hsb-sliders.js, src/core/components/color-picker/modules/rgb-bars.js, …
  • no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/data-table/data-table.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/core/components/data-table/data-table-class.js
  • no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/picker/picker-class.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/core/components/picker/picker-column.js

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 Hygiene9.0 / 10Exemplary✓ 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.

  • Declared in the root 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. (×2)

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.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X24 · Document value interpolated into markup unescaped5.7 / 10Adequate✓ Tool-verified

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

  • `message.text` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — kitchen-sink/react/src/pages/messages.jsx:251
  • `message.text` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — kitchen-sink/vue/src/pages/messages.vue:56
  • ``window.${callbackLoadName} = function (Framework7, Framework7AutoInstallComponent) {return ${scriptContent.trim()}}`` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/core/components/app/load-module.js:103
  • `styleContent` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/core/components/app/load-module.js:143
  • `items[i].toString().trim()` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/core/components/virtual-list/virtual-list-class.js:308
  • `vl.params.emptyTemplate` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/core/components/virtual-list/virtual-list-class.js:356
  • `this.style` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — src/core/modules/component/component-class.js:151, src/core/modules/component/component-class.js:173
  • `scriptContent` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/core/modules/component/parse-component.js:78
  • `content` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/core/modules/router/router-class.js:199

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
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.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

X3 · Exception handling5.5 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×3) — src/core/shared/utils.js:45, src/core/shared/utils.js:50, src/core/components/swiper/swiper.js:44

What to do

  • Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

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
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 Health23%Critical — gated by D1, D2, R1, R10, R2, R7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture98%ExemplaryStrongest area.
Maturity55%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness24%Critical — gated by D8, R4, P1, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security90%StrongSolid.
Accessibility28%Weak — gated by AC1, AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance60%AdequateAcceptable, with room to improve.
Unscored — 1 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.

  • X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 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.

  • 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 — 68 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.

  • AC5 ARIA correctness — AC5 could not be measured here. This repository renders user interface from HTML strings built in plain scripts — 14 script file(s) building 54 markup element(s) as HTML strings, carrying 0 role/aria/tabindex attribute(s) (e.g. src/react/components/area-chart.jsx, src/react/components/panel.jsx, kitchen-sink/react/src/pages/dialog.jsx) — which this analyzer's markup model does not read (it 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), so no ARIA usage from it could enter the population. The parsed markup carried none either, but that is a gap in our frontend coverage, NOT a statement that this repository has no ARIA usage.
  • AX1 Captive dependencies — Not applicable: this repository's JavaScript 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 function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. 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
  • AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
  • C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
  • D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
  • D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
  • 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
  • D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • 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.
  • D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D4 Code Duplication — This repository's production source (.js, .jsx, .svelte, .vue) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
  • 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.
  • D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
  • 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
  • DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
  • 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
  • M4 Documentation accuracy — Not applicable: the 6 current-state document(s) make no claim of a kind M4 checks.
  • 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'.
  • P2 Observability — This repository's JavaScript/TypeScript source (1 module(s), 436 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • S1 Web-Security Posture — Not assessed: 436 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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
  • 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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 — 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
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • 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
  • 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 — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
  • X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
  • 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 — 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
  • X5 Nullable reference types — 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
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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 — 83 finding(s)
AC1 · Text alternatives · <img> without a text alternative · ×40
  • <img> without a text alternative kitchen-sink/react/src/pages/action-sheet.jsx:120 — 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 kitchen-sink/react/src/pages/action-sheet.jsx:129 — 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 kitchen-sink/react/src/pages/action-sheet.jsx:138 — 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 kitchen-sink/react/src/pages/action-sheet.jsx:149 — 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 kitchen-sink/react/src/pages/action-sheet.jsx:158 — 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 kitchen-sink/react/src/pages/action-sheet.jsx:167 — 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 kitchen-sink/react/src/pages/cards.jsx:139 — 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 kitchen-sink/react/src/pages/cards.jsx:146 — 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 kitchen-sink/react/src/pages/cards.jsx:153 — 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 kitchen-sink/react/src/pages/chips.jsx:46 — 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 kitchen-sink/react/src/pages/chips.jsx:49 — 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 kitchen-sink/react/src/pages/chips.jsx:52 — 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 kitchen-sink/react/src/pages/chips.jsx:63 — 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 kitchen-sink/react/src/pages/chips.jsx:68 — 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 kitchen-sink/react/src/pages/list.jsx:205 — 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 kitchen-sink/react/src/pages/list.jsx:219 — 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 kitchen-sink/react/src/pages/list.jsx:233 — 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 kitchen-sink/react/src/pages/list.jsx:275 — 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 kitchen-sink/react/src/pages/list.jsx:283 — 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 kitchen-sink/react/src/pages/list.jsx:291 — 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 kitchen-sink/react/src/pages/pull-to-refresh.jsx:43 — 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 kitchen-sink/react/src/pages/skeleton.jsx:115 — 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 kitchen-sink/react/src/pages/skeleton.jsx:126 — 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 kitchen-sink/react/src/pages/skeleton.jsx:137 — 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 kitchen-sink/react/src/pages/sortable.jsx:55 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • + 15 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · High CVE · ×21
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×5
  • Click handler on a non-interactive <div> kitchen-sink/react/src/pages/color-themes.jsx:104 — 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> kitchen-sink/react/src/pages/color-themes.jsx:111 — 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> kitchen-sink/react/src/pages/sheet-modal.jsx:301 — 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> kitchen-sink/svelte/src/pages/color-themes.svelte:102 — 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> kitchen-sink/svelte/src/pages/color-themes.svelte:107 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC3 · Page structure · Viewport restricts zoom · ×4
  • Viewport restricts zoom kitchen-sink/core/index.html:6 — user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
  • Viewport restricts zoom kitchen-sink/react/index.html:6 — user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
  • Viewport restricts zoom kitchen-sink/svelte/index.html:6 — user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
  • Viewport restricts zoom kitchen-sink/vue/index.html:6 — user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
AC2 · Forms & labels · <input> without a programmatic label · ×3
  • <input> without a programmatic label kitchen-sink/react/src/pages/data-table.jsx:265 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label kitchen-sink/react/src/pages/data-table.jsx:271 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label kitchen-sink/react/src/pages/data-table.jsx:277 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
AC4 · Keyboard semantics · Clickable element isn't keyboard-operable · ×3
  • Clickable element isn't keyboard-operable kitchen-sink/react/src/pages/popup.jsx:221 — The repo's own CSS styles .swipe-handler with `cursor: pointer`, so this <div> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Clickable element isn't keyboard-operable kitchen-sink/react/src/pages/sheet-modal.jsx:274 — The repo's own CSS styles .swipe-handler with `cursor: pointer`, so this <div> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Clickable element isn't keyboard-operable kitchen-sink/react/src/pages/sheet-modal.jsx:344 — The repo's own CSS styles .swipe-handler with `cursor: pointer`, so this <div> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler.
D30 · Dependency Vulnerabilities · Critical CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <select> without a programmatic label · ×1
  • <select> without a programmatic label kitchen-sink/react/src/pages/data-table.jsx:283 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC4 · Keyboard semantics · Click handler on a non-interactive <link> · ×1
  • Click handler on a non-interactive <link> kitchen-sink/svelte/src/pages/tabbar-icons.svelte:24 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
D30 · Dependency Vulnerabilities · High vulnerability · ×1
  • REDACTED
D8 · Code Coverage · No automated tests · ×1
  • No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (pytest or unittest), and run it in CI so the gap cannot reopen.
Serious — 839 finding(s)
D3 · God Classes · FunctionTooLong · ×63
  • FunctionTooLong: list-input.ListInput src/react/components/list-input.jsx:84 — FunctionTooLong — ListInput runs 353 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 253 over it, 3.53× 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.
  • FunctionTooLong: input.Input src/react/components/input.jsx:81 — FunctionTooLong — Input runs 337 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 237 over it, 3.37× 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.
  • FunctionTooLong: sheet-modal.default kitchen-sink/react/src/pages/sheet-modal.jsx:17 — FunctionTooLong — default runs 333 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 233 over it, 3.33× 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.
  • FunctionTooLong: navigate.forward src/core/modules/router/navigate.js:20 — FunctionTooLong — forward runs 332 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 232 over it, 3.32× 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.
  • FunctionTooLong: touch.initTouch src/core/modules/touch/touch.js:8 — FunctionTooLong — initTouch runs 330 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 230 over it, 3.30× 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.
  • FunctionTooLong: color-picker.default kitchen-sink/react/src/pages/color-picker.jsx:13 — FunctionTooLong — default runs 313 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 213 over it, 3.13× 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.
  • FunctionTooLong: autocomplete.default kitchen-sink/react/src/pages/autocomplete.jsx:16 — FunctionTooLong — default runs 311 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 211 over it, 3.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.
  • FunctionTooLong: stepper.default kitchen-sink/react/src/pages/stepper.jsx:13 — FunctionTooLong — default runs 281 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 181 over it, 2.81× 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.
  • FunctionTooLong: page.Page src/react/components/page.jsx:59 — FunctionTooLong — Page runs 269 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 169 over it, 2.69× 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.
  • FunctionTooLong: area-chart.AreaChart src/react/components/area-chart.jsx:31 — FunctionTooLong — AreaChart runs 267 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 167 over it, 2.67× 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.
  • FunctionTooLong: treeview.default kitchen-sink/react/src/pages/treeview.jsx:13 — FunctionTooLong — default runs 259 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 159 over it, 2.59× 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.
  • FunctionTooLong: swipeout.default kitchen-sink/react/src/pages/swipeout.jsx:15 — FunctionTooLong — default runs 258 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 158 over it, 2.58× 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.
  • FunctionTooLong: swipe-panel.swipePanel src/core/components/panel/swipe-panel.js:4 — FunctionTooLong — swipePanel runs 253 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 153 over it, 2.53× 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.
  • FunctionTooLong: list-item.ListItem src/react/components/list-item.jsx:135 — FunctionTooLong — ListItem runs 243 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 143 over it, 2.43× 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.
  • FunctionTooLong: home.default kitchen-sink/react/src/pages/home.jsx:17 — FunctionTooLong — default runs 241 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 141 over it, 2.41× 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.
  • FunctionTooLong: back.backward src/core/modules/router/back.js:11 — FunctionTooLong — backward runs 239 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 139 over it, 2.39× 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.
  • FunctionTooLong: popup.default kitchen-sink/react/src/pages/popup.jsx:15 — FunctionTooLong — default runs 235 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 135 over it, 2.35× 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.
  • FunctionTooLong: swipe-back.SwipeBack src/core/modules/router/swipe-back.js:6 — FunctionTooLong — SwipeBack runs 230 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 130 over it, 2.30× 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.
  • FunctionTooLong: back.back src/core/modules/router/back.js:460 — FunctionTooLong — back runs 219 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 119 over it, 2.19× 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.
  • FunctionTooLong: list.List src/react/components/list.jsx:87 — FunctionTooLong — List runs 218 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 118 over it, 2.18× 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.
  • FunctionTooLong: messages.default kitchen-sink/react/src/pages/messages.jsx:18 — FunctionTooLong — default runs 200 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 100 over it, 2.00× 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.
  • FunctionTooLong: picker.default kitchen-sink/react/src/pages/picker.jsx:4 — FunctionTooLong — default runs 183 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 83 over it, 1.83× 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.
  • FunctionTooLong: progressbar.default kitchen-sink/react/src/pages/progressbar.jsx:15 — FunctionTooLong — default runs 183 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 83 over it, 1.83× 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.
  • FunctionTooLong: list-item-content.ListItemContent src/react/components/list-item-content.jsx:8 — FunctionTooLong — ListItemContent runs 180 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 80 over it, 1.80× 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.
  • FunctionTooLong: messagebar.Messagebar src/react/components/messagebar.jsx:50 — FunctionTooLong — Messagebar runs 179 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 79 over it, 1.79× 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.
  • + 38 more in this group — see findings.md.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×40
  • Sync-over-async blocking scripts/build-core-js.js:27 — `fs.readFileSync` in `modular` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-js.js:28 — `fs.readFileSync` in `modular` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-js.js:90 — `fs.writeFileSync` in `modular` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-js.js:92 — `fs.writeFileSync` in `modular` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-js.js:95 — `fs.writeFileSync` in `modular` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-js.js:97 — `fs.writeFileSync` in `modular` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-js.js:115 — `fs.readFileSync` in `modular` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-js.js:116 — `fs.writeFileSync` in `modular` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-js.js:120 — `fs.readFileSync` in `callback to files.forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-js.js:121 — `fs.writeFileSync` in `callback to files.forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-js.js:139 — `fs.writeFileSync` in `modular` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-js.js:209 — `fs.writeFileSync` in `callback to then` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-js.js:210 — `fs.writeFileSync` in `callback to then` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-js.js:236 — `fs.existsSync` in `callback to components.forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-styles.js:27 — `fs.readFileSync` in `buildComponentsStyles` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-styles.js:49 — `fs.existsSync` in `callback to components.filter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-styles.js:56 — `fs.readFileSync` in `callback to componentsToProcess.forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-styles.js:73 — `fs.writeFileSync` in `callback to componentsToProcess.forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-styles.js:137 — `fs.readFileSync` in `buildBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-styles.js:161 — `fs.writeFileSync` in `buildBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-styles.js:172 — `fs.writeFileSync` in `buildBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-styles.js:187 — `fs.readFileSync` in `buildCore` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-styles.js:206 — `fs.writeFileSync` in `buildCore` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-core-styles.js:217 — `fs.writeFileSync` in `buildCore` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking scripts/build-material-color-utils.js:34 — `fs.writeFileSync` in `callback to then` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • + 15 more in this group — see findings.md.
AC2 · Forms & labels · <ListInput> field component without a label · ×33
  • <ListInput> field component without a label kitchen-sink/react/src/pages/calendar.jsx:80 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/calendar.jsx:85 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/calendar.jsx:97 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/calendar.jsx:116 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/calendar.jsx:126 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/calendar.jsx:136 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/color-picker.jsx:59 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/color-picker.jsx:78 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/color-picker.jsx:100 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/color-picker.jsx:122 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/color-picker.jsx:146 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/color-picker.jsx:177 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/color-picker.jsx:208 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/color-picker.jsx:238 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/color-picker.jsx:267 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/color-picker.jsx:395 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/inputs.jsx:217 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/inputs.jsx:221 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/inputs.jsx:225 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/inputs.jsx:229 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/inputs.jsx:247 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/inputs.jsx:249 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/inputs.jsx:251 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/inputs.jsx:253 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <ListInput> field component without a label kitchen-sink/react/src/pages/inputs.jsx:258 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • + 8 more in this group — see findings.md.
AC4 · Keyboard semantics · Anchor without href · ×31
  • Anchor without href kitchen-sink/react/src/pages/data-table.jsx:564 — 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 kitchen-sink/react/src/pages/data-table.jsx:565 — 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 kitchen-sink/react/src/pages/fab-morph.jsx:42 — 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 kitchen-sink/react/src/pages/fab-morph.jsx:45 — 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 kitchen-sink/react/src/pages/fab-morph.jsx:48 — 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 kitchen-sink/react/src/pages/fab-morph.jsx:51 — 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 kitchen-sink/react/src/pages/fab-morph.jsx:60 — 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 kitchen-sink/react/src/pages/fab-morph.jsx:63 — 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 kitchen-sink/react/src/pages/fab-morph.jsx:66 — 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 kitchen-sink/react/src/pages/fab-morph.jsx:69 — 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 kitchen-sink/react/src/pages/preloader.jsx:80 — 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 kitchen-sink/react/src/pages/preloader.jsx:88 — 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 kitchen-sink/react/src/pages/preloader.jsx:97 — 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 kitchen-sink/react/src/pages/timeline.jsx:242 — 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 kitchen-sink/react/src/pages/timeline.jsx:245 — 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 kitchen-sink/react/src/pages/timeline.jsx:248 — 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 kitchen-sink/svelte/src/pages/data-table.svelte:561 — 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 kitchen-sink/svelte/src/pages/data-table.svelte:562 — 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 kitchen-sink/svelte/src/pages/fab-morph.svelte:25 — 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 kitchen-sink/svelte/src/pages/fab-morph.svelte:26 — 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 kitchen-sink/svelte/src/pages/fab-morph.svelte:27 — 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 kitchen-sink/svelte/src/pages/fab-morph.svelte:28 — 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 kitchen-sink/svelte/src/pages/fab-morph.svelte:35 — 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 kitchen-sink/svelte/src/pages/fab-morph.svelte:36 — 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 kitchen-sink/svelte/src/pages/fab-morph.svelte:37 — 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.
  • + 6 more in this group — see findings.md.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×31
  • Animation without a prefers-reduced-motion guard src/core/components/touch-ripple/touch-ripple.less:33 — `.ripple-wave` moves (`animation: touch-ripple-in 200ms 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 src/core/components/touch-ripple/touch-ripple.less:63 — `.item-link .ripple-wave` moves (`animation: touch-ripple-in-blurred 250ms 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 src/core/components/tooltip/tooltip.less:18 — `.tooltip` moves (`transition-property: opacity, transform`) 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 src/core/components/swipeout/swipeout-ios.less:37 — `.ios .swipeout-overswipe` moves (`transition-property: transform, left, width, margin-left, margin-right`) 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 src/core/components/swipeout/swipeout.less:18 — `.swipeout-transitioning .swipeout-content` moves (`transition-property: transform, left, background-color, border-radius, opacity`) 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 src/core/components/swipeout/swipeout.less:24 — `.swipeout-transitioning .swipeout-actions-right a` moves (`transition-property: transform, left, width, margin-left, margin-right`) 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 src/core/components/searchbar/searchbar.less:216 — `.page-content.with-searchbar-expandable-enabled` moves (`transition-property: transform`) 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 src/core/components/range/range-md.less:9 — `.md .range-knob` moves (`transition-property: transform, background-color`) 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 src/core/components/range/range.less:110 — `.range-knob-label` moves (`transition-property: transform`) 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 src/core/components/pull-to-refresh/pull-to-refresh-ios.less:30 — `.ios .ptr-transitioning > *` moves (`transition-property: transform`) 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 src/core/components/pull-to-refresh/pull-to-refresh-ios.less:42 — `.ios .ptr-pull-up .ptr-preloader .preloader` moves (`animation: ios-ptr-preloader-spin 1s 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 src/core/components/pull-to-refresh/pull-to-refresh-ios.less:66 — `.ios .ptr-bottom.ptr-transitioning > *` moves (`transition-property: transform`) 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 src/core/components/pull-to-refresh/pull-to-refresh-md.less:95 — `.md .ptr-transitioning .ptr-preloader` moves (`transition-property: transform, opacity`) 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 src/core/components/progressbar/progressbar-ios.less:4 — `.ios .progressbar-infinite:before` moves (`animation: ios-progressbar-infinite 1s linear infinite`) 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 src/core/components/progressbar/progressbar-ios.less:27 — `.ios .progressbar-infinite.color-multi:before` moves (`animation: ios-progressbar-infinite-multicolor 3s linear infinite`) 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 src/core/components/progressbar/progressbar-md.less:20 — `.md .progressbar-infinite:before` moves (`animation: md-progressbar-infinite-1 2s linear infinite`) 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 src/core/components/progressbar/progressbar-md.less:23 — `.md .progressbar-infinite:after` moves (`animation: md-progressbar-infinite-2 2s linear infinite`) 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 src/core/components/progressbar/progressbar-md.less:32 — `.md .progressbar-infinite.color-multi:after` moves (`animation: md-progressbar-infinite-multicolor-fill 3s linear infinite`) 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 src/core/components/progressbar/progressbar.less:62 — `.progressbar-in` moves (`animation: progressbar-in 150ms 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 src/core/components/progressbar/progressbar.less:65 — `.progressbar-out` moves (`animation: progressbar-out 150ms 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 src/core/components/preloader/preloader-ios.less:6 — `.ios .preloader-inner` moves (`animation: ios-preloader-spin 1s steps(8, end) infinite`) 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 src/core/components/preloader/preloader-md.less:11 — `.md .preloader-inner circle` moves (`animation: md-preloader-circle-rotate @speed * 4 ease-in-out infinite`) 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 src/core/components/preloader/preloader-md.less:7 — `.md .preloader-inner` moves (`animation: md-preloader-rotate @speed linear infinite`) 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 src/core/components/preloader/preloader-md.less:24 — `.md .preloader-multi-color circle` moves (`animation: md-preloader-circle-rotate @speed * 4 ease-in-out infinite, md-preloader-multicolor @speed * 4 ease-in-out infinite`) 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 src/core/components/popover/popover-md.less:4 — `.md .popover` moves (`transition-property: opacity, transform`) 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.
  • + 6 more in this group — see findings.md.
D3 · God Classes · MethodTooLong · ×24
  • MethodTooLong: Sheet.constructor src/core/components/sheet/sheet-class.js:8 — MethodTooLong — constructor runs 555 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 455 over it, 5.55× 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: PullToRefresh.constructor src/core/components/pull-to-refresh/pull-to-refresh-class.js:7 — MethodTooLong — constructor runs 420 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 320 over it, 4.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.
  • MethodTooLong: Range.constructor src/core/components/range/range-class.js:6 — MethodTooLong — constructor runs 306 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 206 over it, 3.06× 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: Popup.constructor src/core/components/popup/popup-class.js:8 — MethodTooLong — constructor runs 292 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 192 over it, 2.92× 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: Autocomplete.constructor src/core/components/autocomplete/autocomplete-class.js:17 — MethodTooLong — constructor runs 230 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 130 over it, 2.30× 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: Stepper.constructor src/core/components/stepper/stepper-class.js:6 — MethodTooLong — constructor runs 206 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 106 over it, 2.06× 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: Searchbar.constructor src/core/components/searchbar/searchbar-class.js:9 — MethodTooLong — constructor runs 201 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 101 over it, 2.01× 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: Actions.constructor src/core/components/actions/actions-class.js:11 — MethodTooLong — constructor runs 174 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 74 over it, 1.74× 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: Dialog.constructor src/core/components/dialog/dialog-class.js:10 — MethodTooLong — constructor runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× 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: ListIndex.constructor src/core/components/list-index/list-index-class.js:6 — MethodTooLong — constructor runs 152 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× 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: Notification.constructor REDACTED:8 — MethodTooLong — constructor runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× 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: Tooltip.constructor src/core/components/tooltip/tooltip-class.js:8 — MethodTooLong — constructor runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× 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: VirtualList.constructor src/core/components/virtual-list/virtual-list-class.js:8 — MethodTooLong — constructor runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× 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: Popover.constructor src/core/components/popover/popover-class.js:8 — MethodTooLong — constructor runs 118 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× 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: Toggle.constructor src/core/components/toggle/toggle-class.js:6 — MethodTooLong — constructor runs 113 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 13 over it, 1.13× 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: Gauge.update src/core/components/gauge/gauge-class.js:172 — MethodTooLong — update runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× 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: PhotoBrowser.onOpen src/core/components/photo-browser/photo-browser-class.js:405 — MethodTooLong — onOpen runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× 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: VirtualList.render src/core/components/virtual-list/virtual-list-class.js:221 — MethodTooLong — render runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× 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: Router.init src/core/modules/router/router-class.js:959 — MethodTooLong — init runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× 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: Searchbar.search src/core/components/searchbar/searchbar-class.js:516 — MethodTooLong — search runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× 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: SmartSelect.constructor src/core/components/smart-select/smart-select-class.js:10 — MethodTooLong — constructor runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× 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: Messagebar.constructor src/core/components/messagebar/messagebar-class.js:6 — MethodTooLong — constructor 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.
  • MethodTooLong: Gauge.render src/core/components/gauge/gauge-class.js:58 — MethodTooLong — render runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× 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: Router.pageCallback src/core/modules/router/router-class.js:649 — MethodTooLong — pageCallback runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× 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.
D2 · Cognitive Complexity · constructor · ×11
  • constructor::handleTouchMove (cognitive 109) src/core/components/pull-to-refresh/pull-to-refresh-class.js:148 — constructor::handleTouchMove has cognitive complexity 109 (threshold 15). Drivers by points: if/else 38 (72 pts), boolean chains 23, ternaries 5 (11 pts), loops 1 (3 pts) (nesting depth added 42). 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.
  • constructor::handleTouchEnd (cognitive 106) src/core/components/sheet/sheet-class.js:306 — constructor::handleTouchEnd has cognitive complexity 106 (threshold 15). Drivers by points: if/else 40 (82 pts), boolean chains 18, ternaries 4 (6 pts) (nesting depth added 44). 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.
  • constructor::handleMouseWheel (cognitive 57) src/core/components/pull-to-refresh/pull-to-refresh-class.js:415 — constructor::handleMouseWheel has cognitive complexity 57 (threshold 15). Drivers by points: if/else 27 (48 pts), boolean chains 6, ternaries 2 (3 pts) (nesting depth added 22). 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.
  • constructor::handleTouchMove (cognitive 48) src/core/components/sheet/sheet-class.js:198 — constructor::handleTouchMove has cognitive complexity 48 (threshold 15). Drivers by points: if/else 18 (28 pts), ternaries 7 (14 pts), boolean chains 6 (nesting depth added 17). 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.
  • constructor::onPageInputChange (cognitive 37) src/core/components/autocomplete/autocomplete-class.js:148 — constructor::onPageInputChange has cognitive complexity 37 (threshold 15). Drivers by points: if/else 9 (16 pts), ternaries 3 (9 pts), boolean chains 6, loops 3 (6 pts) (nesting depth added 16). 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.
  • constructor::handleInputChange (cognitive 31) src/core/components/smart-select/smart-select-class.js:100 — constructor::handleInputChange has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 4 (12 pts), boolean chains 3, loops 1 (2 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.
  • constructor::attachCalendarEvents::handleDayClick (cognitive 24) REDACTED:259 — constructor::attachCalendarEvents::handleDayClick has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 5 (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.
  • constructor::onKeyDown (cognitive 21) src/core/components/autocomplete/autocomplete-class.js:223 — constructor::onKeyDown has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 3 (7 pts), boolean chains 1 (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.
  • constructor::attachCalendarEvents::handleTouchEnd (cognitive 21) REDACTED:225 — constructor::attachCalendarEvents::handleTouchEnd has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 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.
  • constructor::handleTouchStart (cognitive 19) src/core/components/range/range-class.js:211 — constructor::handleTouchStart has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (15 pts), ternaries 4 (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.
  • constructor::open (cognitive 16) src/core/components/actions/actions-class.js:95 — constructor::open has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 5 (7 pts), ternaries 1 (2 pts) (nesting depth added 3). 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 · FileTooLong · ×11
  • FileTooLong: REDACTED REDACTED — FileTooLong — 1527 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 1500 significant lines; this is 27 over it, 1.02× 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: router/router-class.js src/core/modules/router/router-class.js — FileTooLong — 790 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: Router (22-1126). The bar is 500 significant lines; this is 290 over it, 1.58× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: smart-select/smart-select-class.js src/core/components/smart-select/smart-select-class.js — FileTooLong — 745 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: SmartSelect (9-1007). The bar is 500 significant lines; this is 245 over it, 1.49× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: pages/data-table.jsx kitchen-sink/react/src/pages/data-table.jsx — FileTooLong — 706 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 206 over it, 1.41× 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: autocomplete/autocomplete-class.js src/core/components/autocomplete/autocomplete-class.js — FileTooLong — 690 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: Autocomplete (16-957). The bar is 500 significant lines; this is 190 over it, 1.38× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: color-picker/color-picker-class.js src/core/components/color-picker/color-picker-class.js — FileTooLong — 623 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: ColorPicker (33-871). The bar is 500 significant lines; this is 123 over it, 1.25× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: router/navigate.js src/core/modules/router/navigate.js — FileTooLong — 591 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 91 over it, 1.18× 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: photo-browser/photo-browser-class.js src/core/components/photo-browser/photo-browser-class.js — FileTooLong — 581 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: PhotoBrowser (9-818). The bar is 500 significant lines; this is 81 over it, 1.16× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: sheet/sheet-class.js src/core/components/sheet/sheet-class.js — FileTooLong — 562 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: Sheet (7-774). The bar is 500 significant lines; this is 62 over it, 1.12× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: router/back.js src/core/modules/router/back.js — FileTooLong — 519 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 19 over it, 1.04× 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: searchbar/searchbar-class.js src/core/components/searchbar/searchbar-class.js — FileTooLong — 502 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: Searchbar (8-682). The bar is 500 significant lines; this is 2 over it, 1.00× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
D3 · God Classes · ClassTooLong · ×11
  • ClassTooLong: Router src/core/modules/router/router-class.js:22 — ClassTooLong — 762 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 362 over it, 1.91× 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.
  • ClassTooLong: SmartSelect src/core/components/smart-select/smart-select-class.js:9 — ClassTooLong — 739 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 339 over it, 1.85× 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.
  • ClassTooLong: Autocomplete src/core/components/autocomplete/autocomplete-class.js:16 — ClassTooLong — 677 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 277 over it, 1.69× 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.
  • ClassTooLong: ColorPicker src/core/components/color-picker/color-picker-class.js:33 — ClassTooLong — 594 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 194 over it, 1.49× 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.
  • ClassTooLong: PhotoBrowser src/core/components/photo-browser/photo-browser-class.js:9 — ClassTooLong — 575 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 400 significant lines; this is 175 over it, 1.44× 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.
  • ClassTooLong: Sheet src/core/components/sheet/sheet-class.js:7 — ClassTooLong — 556 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 156 over it, 1.39× 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.
  • ClassTooLong: Searchbar src/core/components/searchbar/searchbar-class.js:8 — ClassTooLong — 495 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 95 over it, 1.24× 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.
  • ClassTooLong: Range src/core/components/range/range-class.js:5 — ClassTooLong — 486 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 86 over it, 1.22× 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.
  • ClassTooLong: VirtualList src/core/components/virtual-list/virtual-list-class.js:7 — ClassTooLong — 439 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 39 over it, 1.10× 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.
  • ClassTooLong: PullToRefresh src/core/components/pull-to-refresh/pull-to-refresh-class.js:6 — ClassTooLong — 432 significant lines (blank, comment-only and punctuation-only lines excluded), 3 methods. The bar is 400 significant lines; this is 32 over it, 1.08× 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.
  • ClassTooLong: Picker src/core/components/picker/picker-class.js:12 — ClassTooLong — 419 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 19 over it, 1.05× 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.
D30 · Dependency Vulnerabilities · Medium CVE · ×11
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×10
  • Untrusted text written into markup unescaped kitchen-sink/react/src/pages/messages.jsx:251 — `message.text` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped kitchen-sink/vue/src/pages/messages.vue:56 — `message.text` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/core/components/app/load-module.js:103 — ``window.${callbackLoadName} = function (Framework7, Framework7AutoInstallComponent) {return ${scriptContent.trim()}}`` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/core/components/app/load-module.js:143 — `styleContent` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/core/components/virtual-list/virtual-list-class.js:308 — `items[i].toString().trim()` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/core/components/virtual-list/virtual-list-class.js:356 — `vl.params.emptyTemplate` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/core/modules/component/component-class.js:151 — `this.style` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/core/modules/component/component-class.js:173 — `this.style` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/core/modules/component/parse-component.js:78 — `scriptContent` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/core/modules/router/router-class.js:199 — `content` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×9
  • Focus outline removed in CSS without a :focus replacement src/core/components/text-editor/text-editor.less:38 — `button.text-editor-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/core/components/text-editor/text-editor.less:79 — `.text-editor-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/core/components/searchbar/searchbar.less:144 — `.searchbar-disable-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/core/components/input/input.less:22 — `input[type='text']` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/core/components/input/input.less:217 — `.input-clear-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/core/components/color-picker/color-picker.less:267 — `.color-picker-bar-value input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/core/components/button/button.less:21 — `.button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/core/components/area-chart/area-chart.less:91 — `.area-chart-legend-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/core/components/app/app.less:90 — `a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
R11 · Import Boundaries · Boundary violation [package · ×6
  • Boundary violation [package:relative-cross-package] scripts/banners/core.js:1 — scripts/banners/core.js:1 reaches into another package with a relative path (../../packages/core/package.json) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] scripts/banners/svelte.js:1 — scripts/banners/svelte.js:1 reaches into another package with a relative path (../../packages/svelte/package.json) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] scripts/release.js:8 — scripts/release.js:8 reaches into another package with a relative path (../packages/core/package.json) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] scripts/release.js:9 — scripts/release.js:9 reaches into another package with a relative path (../packages/react/package.json) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] scripts/release.js:10 — scripts/release.js:10 reaches into another package with a relative path (../packages/vue/package.json) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] scripts/release.js:11 — scripts/release.js:11 reaches into another package with a relative path (../packages/svelte/package.json) — import the package by name instead.
AC3 · Page structure · Page without a main landmark · ×4
  • Page without a main landmark kitchen-sink/core/index.html: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 kitchen-sink/react/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark kitchen-sink/svelte/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark kitchen-sink/vue/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it.
D1 · Cyclomatic Complexity · utils.extend (cyclomatic 16) · ×4
  • utils.extend (cyclomatic 16) src/core/shared/utils.js:220 — utils.extend 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.
  • utils.extend (cyclomatic 16) src/react/shared/utils.js:17 — utils.extend 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.
  • utils.extend (cyclomatic 16) src/svelte/shared/utils.js:17 — utils.extend 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.
  • utils.extend (cyclomatic 16) src/vue/shared/utils.js:19 — utils.extend 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.
D12 · Dependency Hygiene · Deprecated · ×4
  • Deprecated: conventional-changelog-cli package.json:92 — conventional-changelog-cli 3.0.0, declared in package.json, is marked deprecated by its publisher: "This package is no longer maintained. Please use the conventional-changelog package instead.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: eslint package.json:95 — eslint 8.47.0, declared in package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: glob package.json:103 — glob 7.2.3, declared in package.json, is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: opn package.json:109 — opn 6.0.0, declared in package.json, is marked deprecated by its publisher: "The package has been renamed to `open`". Replace it with the package or version that message names, or record why this one must stay.
D2 · Cognitive Complexity · utils.extend (cognitive 29) · ×4
  • utils.extend (cognitive 29) src/core/shared/utils.js:220 — utils.extend has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 13). 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.
  • utils.extend (cognitive 29) src/react/shared/utils.js:17 — utils.extend has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 13). 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.
  • utils.extend (cognitive 29) src/svelte/shared/utils.js:17 — utils.extend has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 13). 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.
  • utils.extend (cognitive 29) src/vue/shared/utils.js:19 — utils.extend has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 13). 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <Segmented> field component without a label · ×3
  • <Segmented> field component without a label kitchen-sink/react/src/pages/gauge.jsx:28 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Segmented> field component without a label kitchen-sink/react/src/pages/icons.jsx:59 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <Segmented> field component without a label kitchen-sink/react/src/pages/progressbar.jsx:85 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
D1 · Cyclomatic Complexity · PullToRefresh.constructor · ×3
  • PullToRefresh.constructor::handleTouchMove (cyclomatic 66) src/core/components/pull-to-refresh/pull-to-refresh-class.js:148 — PullToRefresh.constructor::handleTouchMove has cyclomatic complexity 66 (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 shape REPEATS in the file: 3 other methods here (PullToRefresh.constructor, PullToRefresh.constructor::handleTouchEnd, PullToRefresh.constructor::handleMouseWheel) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • PullToRefresh.constructor::handleMouseWheel (cyclomatic 32) src/core/components/pull-to-refresh/pull-to-refresh-class.js:415 — PullToRefresh.constructor::handleMouseWheel has cyclomatic complexity 32 (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 shape REPEATS in the file: 3 other methods here (PullToRefresh.constructor, PullToRefresh.constructor::handleTouchMove, PullToRefresh.constructor::handleTouchEnd) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • PullToRefresh.constructor::handleTouchEnd (cyclomatic 18) src/core/components/pull-to-refresh/pull-to-refresh-class.js:328 — PullToRefresh.constructor::handleTouchEnd has cyclomatic complexity 18 (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. This shape REPEATS in the file: 3 other methods here (PullToRefresh.constructor, PullToRefresh.constructor::handleTouchMove, PullToRefresh.constructor::handleMouseWheel) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · swipe-panel.swipePanel · ×3
  • swipe-panel.swipePanel::handleTouchMove (cyclomatic 64) src/core/components/panel/swipe-panel.js:77 — swipe-panel.swipePanel::handleTouchMove has cyclomatic complexity 64 (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 shape REPEATS in the file: 2 other methods here (swipe-panel.swipePanel::handleTouchStart, swipe-panel.swipePanel::handleTouchEnd) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • swipe-panel.swipePanel::handleTouchEnd (cyclomatic 50) src/core/components/panel/swipe-panel.js:216 — swipe-panel.swipePanel::handleTouchEnd has cyclomatic complexity 50 (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 shape REPEATS in the file: 2 other methods here (swipe-panel.swipePanel::handleTouchStart, swipe-panel.swipePanel::handleTouchMove) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • swipe-panel.swipePanel::handleTouchStart (cyclomatic 30) src/core/components/panel/swipe-panel.js:33 — swipe-panel.swipePanel::handleTouchStart has cyclomatic complexity 30 (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 shape REPEATS in the file: 2 other methods here (swipe-panel.swipePanel::handleTouchMove, swipe-panel.swipePanel::handleTouchEnd) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · init · ×3
  • init::handleTouchMove (cyclomatic 50) src/core/components/swipeout/swipeout.js:44 — init::handleTouchMove has cyclomatic complexity 50 (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.
  • init::handleTouchEnd (cyclomatic 30) src/core/components/sortable/sortable.js:159 — init::handleTouchEnd has cyclomatic complexity 30 (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.
  • init::handleTouchEnd (cyclomatic 29) src/core/components/swipeout/swipeout.js:312 — init::handleTouchEnd has cyclomatic complexity 29 (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 · mixins.actionsAttrs (cyclomatic 45) · ×3
  • mixins.actionsAttrs (cyclomatic 45) src/react/shared/mixins.js:65 — mixins.actionsAttrs has cyclomatic complexity 45 (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.
  • mixins.actionsAttrs (cyclomatic 45) src/svelte/shared/mixins.js:65 — mixins.actionsAttrs has cyclomatic complexity 45 (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.
  • mixins.actionsAttrs (cyclomatic 45) src/vue/shared/mixins.js:154 — mixins.actionsAttrs has cyclomatic complexity 45 (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 · touch.initTouch · ×3
  • touch.initTouch::handleTouchMove (cyclomatic 29) src/core/modules/touch/touch.js:252 — touch.initTouch::handleTouchMove has cyclomatic complexity 29 (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 shape REPEATS in the file: 2 other methods here (touch.initTouch::handleTouchStart, touch.initTouch::handleClick) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • touch.initTouch::handleClick (cyclomatic 20) src/core/modules/touch/touch.js:366 — touch.initTouch::handleClick 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. This shape REPEATS in the file: 2 other methods here (touch.initTouch::handleTouchStart, touch.initTouch::handleTouchMove) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • touch.initTouch::handleTouchStart (cyclomatic 16) src/core/modules/touch/touch.js:204 — touch.initTouch::handleTouchStart has cyclomatic complexity 16 (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. This shape REPEATS in the file: 2 other methods here (touch.initTouch::handleTouchMove, touch.initTouch::handleClick) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · mixins.actionsClasses (cyclomatic 24) · ×3
  • mixins.actionsClasses (cyclomatic 24) src/react/shared/mixins.js:132 — mixins.actionsClasses has cyclomatic complexity 24 (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.
  • mixins.actionsClasses (cyclomatic 24) src/svelte/shared/mixins.js:132 — mixins.actionsClasses has cyclomatic complexity 24 (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.
  • mixins.actionsClasses (cyclomatic 24) src/vue/shared/mixins.js:221 — mixins.actionsClasses has cyclomatic complexity 24 (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.
D2 · Cognitive Complexity · init · ×3
  • init::handleTouchMove (cognitive 82) src/core/components/swipeout/swipeout.js:44 — init::handleTouchMove has cognitive complexity 82 (threshold 15). Drivers by points: if/else 36 (65 pts), boolean chains 12, ternaries 3 (5 pts) (nesting depth added 31). 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.
  • init::handleTouchEnd (cognitive 49) src/core/components/sortable/sortable.js:159 — init::handleTouchEnd has cognitive complexity 49 (threshold 15). Drivers by points: if/else 25 (44 pts), boolean chains 5 (nesting depth added 19). 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.
  • init::handleTouchEnd (cognitive 40) src/core/components/swipeout/swipeout.js:312 — init::handleTouchEnd has cognitive complexity 40 (threshold 15). Drivers by points: if/else 15 (23 pts), boolean chains 8, ternaries 4 (6 pts), loops 1 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · actionsAttrs (cognitive 44) · ×3
  • actionsAttrs (cognitive 44) src/react/shared/mixins.js:65 — actionsAttrs has cognitive complexity 44 (threshold 15). Drivers by points: boolean chains 44. 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.
  • actionsAttrs (cognitive 44) src/svelte/shared/mixins.js:65 — actionsAttrs has cognitive complexity 44 (threshold 15). Drivers by points: boolean chains 44. 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.
  • actionsAttrs (cognitive 44) src/vue/shared/mixins.js:154 — actionsAttrs has cognitive complexity 44 (threshold 15). Drivers by points: boolean chains 44. 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 · mixins.actionsClasses (cognitive 23) · ×3
  • mixins.actionsClasses (cognitive 23) src/react/shared/mixins.js:132 — mixins.actionsClasses has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 23. 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.
  • mixins.actionsClasses (cognitive 23) src/svelte/shared/mixins.js:132 — mixins.actionsClasses has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 23. 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.
  • mixins.actionsClasses (cognitive 23) src/vue/shared/mixins.js:221 — mixins.actionsClasses has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 23. 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.
R10 · Code Duplication · Duplicated block with local edits (43 matched lines × 2 locations) · ×3
  • Duplicated block with local edits (43 matched lines × 2 locations) src/core/components/dialog/dialog.js:56 — src/core/components/dialog/dialog.js:56 · src/core/components/dialog/dialog.js:107 — the two spans are one implementation copied and then locally edited — 260 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 (43 matched lines × 2 locations) src/core/modules/router/modal.js:189 — src/core/modules/router/modal.js:189 · src/core/modules/router/tab.js:157 — the two spans are one implementation copied and then locally edited — 203 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 (43 matched lines × 2 locations) src/react/shared/router-open-in.jsx:9 — src/react/shared/router-open-in.jsx:9 · src/vue/shared/router-open-in.js:9 — the two spans are one implementation copied and then locally edited — 245 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.
R2 · Cyclomatic Complexity · Complex function actionsAttrs (cyclomatic 45, cognitive 44) · ×3
  • Complex function actionsAttrs (cyclomatic 45, cognitive 44) src/react/shared/mixins.js:65 — actionsAttrs has cyclomatic complexity 45 and cognitive complexity 44; 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.
  • Complex function actionsAttrs (cyclomatic 45, cognitive 44) src/svelte/shared/mixins.js:65 — actionsAttrs has cyclomatic complexity 45 and cognitive complexity 44; 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.
  • Complex function actionsAttrs (cyclomatic 45, cognitive 44) src/vue/shared/mixins.js:154 — actionsAttrs has cyclomatic complexity 45 and cognitive complexity 44; 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.
X3 · Exception handling · Swallowed exception (empty catch) · ×3
  • Swallowed exception (empty catch) src/core/shared/utils.js:45 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/core/shared/utils.js:50 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/core/components/swiper/swiper.js:44 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
D1 · Cyclomatic Complexity · Sheet.constructor · ×2
  • Sheet.constructor::handleTouchEnd (cyclomatic 59) src/core/components/sheet/sheet-class.js:306 — Sheet.constructor::handleTouchEnd has cyclomatic complexity 59 (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 shape REPEATS in the file: 2 other methods here (Sheet.constructor, Sheet.constructor::handleTouchMove) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • Sheet.constructor::handleTouchMove (cyclomatic 33) src/core/components/sheet/sheet-class.js:198 — Sheet.constructor::handleTouchMove 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. This shape REPEATS in the file: 2 other methods here (Sheet.constructor, Sheet.constructor::handleTouchEnd) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · swipe-back.SwipeBack · ×2
  • swipe-back.SwipeBack::handleTouchMove (cyclomatic 40) src/core/modules/router/swipe-back.js:53 — swipe-back.SwipeBack::handleTouchMove has cyclomatic complexity 40 (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 shape REPEATS in the file: one other method here (swipe-back.SwipeBack::handleTouchEnd) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • swipe-back.SwipeBack::handleTouchEnd (cyclomatic 18) src/core/modules/router/swipe-back.js:173 — swipe-back.SwipeBack::handleTouchEnd has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (swipe-back.SwipeBack::handleTouchMove) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · Range.constructor · ×2
  • Range.constructor::handleTouchMove (cyclomatic 20) src/core/components/range/range-class.js:270 — Range.constructor::handleTouchMove 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 shape REPEATS in the file: 2 other methods here (Range.constructor, Range.constructor::handleTouchEnd) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • Range.constructor::handleTouchEnd (cyclomatic 16) src/core/components/range/range-class.js:335 — Range.constructor::handleTouchEnd 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. This shape REPEATS in the file: 2 other methods here (Range.constructor, Range.constructor::handleTouchMove) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · init (cyclomatic 20) · ×2
  • init (cyclomatic 20) src/core/components/color-picker/modules/hs-spectrum.js:16 — init has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 6 function items inside it that branch (handleTouchStart, handleTouchMove, handleTouchEnd, …). 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.
  • init (cyclomatic 20) src/core/components/color-picker/modules/sb-spectrum.js:15 — init has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 6 function items inside it that branch (handleTouchStart, handleTouchMove, handleTouchEnd, …). 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 · constructor · ×2
  • constructor::attachCalendarEvents::handleDayClick (cyclomatic 19) REDACTED:259 — constructor::attachCalendarEvents::handleDayClick has cyclomatic complexity 19 (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.
  • constructor::attachCalendarEvents::handleTouchMove (cyclomatic 16) REDACTED:186 — constructor::attachCalendarEvents::handleTouchMove has cyclomatic complexity 16 (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.
D2 · Cognitive Complexity · swipePanel · ×2
  • swipePanel::handleTouchMove (cognitive 106) src/core/components/panel/swipe-panel.js:77 — swipePanel::handleTouchMove has cognitive complexity 106 (threshold 15). Drivers by points: if/else 40 (76 pts), ternaries 8 (16 pts), boolean chains 14 (nesting depth added 44). 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.
  • swipePanel::handleTouchStart (cognitive 34) src/core/components/panel/swipe-panel.js:33 — swipePanel::handleTouchStart has cognitive complexity 34 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 10, ternaries 3 (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.
D2 · Cognitive Complexity · swipe-back.SwipeBack · ×2
  • swipe-back.SwipeBack::handleTouchMove (cognitive 57) src/core/modules/router/swipe-back.js:53 — swipe-back.SwipeBack::handleTouchMove has cognitive complexity 57 (threshold 15). Drivers by points: if/else 26 (44 pts), boolean chains 10, ternaries 3 (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. This shape REPEATS in the file: one other method here (swipe-back.SwipeBack::handleTouchEnd) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • swipe-back.SwipeBack::handleTouchEnd (cognitive 23) src/core/modules/router/swipe-back.js:173 — swipe-back.SwipeBack::handleTouchEnd has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 6, ternaries 1 (2 pts) (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. This shape REPEATS in the file: one other method here (swipe-back.SwipeBack::handleTouchMove) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · touch.initTouch · ×2
  • touch.initTouch::handleTouchMove (cognitive 35) src/core/modules/touch/touch.js:252 — touch.initTouch::handleTouchMove has cognitive complexity 35 (threshold 15). Drivers by points: if/else 17 (26 pts), boolean chains 9 (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. This shape REPEATS in the file: one other method here (touch.initTouch::handleTouchStart) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • touch.initTouch::handleTouchStart (cognitive 18) src/core/modules/touch/touch.js:204 — touch.initTouch::handleTouchStart has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 4 (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. This shape REPEATS in the file: one other method here (touch.initTouch::handleTouchMove) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · Range.constructor · ×2
  • Range.constructor::handleTouchMove (cognitive 31) src/core/components/range/range-class.js:270 — Range.constructor::handleTouchMove has cognitive complexity 31 (threshold 15). Drivers by points: if/else 16 (24 pts), boolean chains 3, loops 1 (2 pts), ternaries 2 (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. This shape REPEATS in the file: 2 other methods here (Range.constructor, Range.constructor::handleTouchEnd) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • Range.constructor::handleTouchEnd (cognitive 20) src/core/components/range/range-class.js:335 — Range.constructor::handleTouchEnd has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 5, loops 1 (2 pts) (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 shape REPEATS in the file: 2 other methods here (Range.constructor, Range.constructor::handleTouchMove) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · init (cognitive 20) · ×2
  • init (cognitive 20) src/core/components/color-picker/modules/hs-spectrum.js:16 — init has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 5, ternaries 5 (nesting depth added 1). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 6 function items inside it that branch (handleTouchMove, handleTouchStart, handleTouchEnd, …). 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.
  • init (cognitive 20) src/core/components/color-picker/modules/sb-spectrum.js:15 — init has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 5, ternaries 5 (nesting depth added 1). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 6 function items inside it that branch (handleTouchMove, handleTouchStart, handleTouchEnd, …). 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.
D2 · Cognitive Complexity · initTouch · ×2
  • initTouch::findActivableElement (cognitive 18) src/core/modules/touch/touch.js:37 — initTouch::findActivableElement has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, loops 1 (2 pts), ternaries 1 (2 pts) (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.
  • initTouch::handleClick (cognitive 17) src/core/modules/touch/touch.js:366 — initTouch::handleClick has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 7, ternaries 1 (2 pts) (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.
D3 · God Classes · TooManyMethods · ×2
  • TooManyMethods: Calendar REDACTED:8 — TooManyMethods — 53 methods. The bar is 30 methods; this is 23 over it, 1.77× 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.
  • TooManyMethods: PhotoBrowser src/core/components/photo-browser/photo-browser-class.js:9 — TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× 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.
R10 · Code Duplication · Duplicated block with local edits (73 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (73 matched lines × 2 locations) kitchen-sink/react/src/pages/dialog.jsx:5 — kitchen-sink/react/src/pages/dialog.jsx:5 · kitchen-sink/svelte/src/pages/dialog.svelte:4 — the two spans are one implementation copied and then locally edited — 396 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 (73 matched lines × 2 locations) kitchen-sink/react/src/pages/dialog.jsx:5 — kitchen-sink/react/src/pages/dialog.jsx:5 · kitchen-sink/vue/src/pages/dialog.vue:58 — the two spans are one implementation copied and then locally edited — 409 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.
R7 · Dead Code · Dead file (~601 LoC) · ×2
  • Dead file (~601 LoC) src/core/components/card/card.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~601 LoC) src/core/components/pull-to-refresh/pull-to-refresh-class.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/pull-to-refresh/pull-to-refresh.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~202 LoC) · ×2
  • Dead file (~202 LoC) src/core/components/color-picker/modules/rgb-bars.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/color-picker/color-picker-class.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~202 LoC) src/core/modules/router/component-loader.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
D1 · Cyclomatic Complexity · navigate.forward (cyclomatic 149) · ×1
  • navigate.forward (cyclomatic 149) src/core/modules/router/navigate.js:20 — navigate.forward has cyclomatic complexity 149 (threshold 15). Of this number, 133 points are the body's own statements and 16 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 · back.backward (cyclomatic 109) · ×1
  • back.backward (cyclomatic 109) src/core/modules/router/back.js:11 — back.backward has cyclomatic complexity 109 (threshold 15). Of this number, 92 points are the body's own statements and 17 belong to 2 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 · Calendar.constructor (cyclomatic 95) · ×1
  • Calendar.constructor (cyclomatic 95) REDACTED:9 — Calendar.constructor has cyclomatic complexity 95 (threshold 15). Of this number, 32 points are the body's own statements and 63 belong to 8 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 · back (cyclomatic 92) · ×1
  • back (cyclomatic 92) src/core/modules/router/back.js:460 — back has cyclomatic complexity 92 (threshold 15). Of this number, 81 points are the body's own statements and 11 belong to 13 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 · show (cyclomatic 86) · ×1
  • show (cyclomatic 86) src/core/components/tabs/tabs.js:5 — show has cyclomatic complexity 86 (threshold 15). Of this number, 84 points are the body's own statements and 2 belong to 8 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 · Searchbar.constructor (cyclomatic 80) · ×1
  • Searchbar.constructor (cyclomatic 80) src/core/components/searchbar/searchbar-class.js:9 — Searchbar.constructor has cyclomatic complexity 80 (threshold 15). Of this number, 52 points are the body's own statements and 28 belong to 5 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 · renderToolbar (cyclomatic 75) · ×1
  • renderToolbar (cyclomatic 75) src/core/components/picker/picker-class.js:263 — renderToolbar has cyclomatic complexity 75 (threshold 15). Of this number, 64 points are the body's own statements and 11 belong to 12 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 · Actions.constructor (cyclomatic 66) · ×1
  • Actions.constructor (cyclomatic 66) src/core/components/actions/actions-class.js:11 — Actions.constructor has cyclomatic complexity 66 (threshold 15). Of this number, 29 points are the body's own statements and 37 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 · list-item.ListItem (cyclomatic 63) · ×1
  • list-item.ListItem (cyclomatic 63) src/react/components/list-item.jsx:135 — list-item.ListItem has cyclomatic complexity 63 (threshold 15). Of this number, 38 points are the body's own statements and 25 belong to 20 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 · page.Page (cyclomatic 63) · ×1
  • page.Page (cyclomatic 63) src/react/components/page.jsx:59 — page.Page has cyclomatic complexity 63 (threshold 15). Most of this is not in the body itself: 14 of the 63 points are its own statements and the rest belongs to 21 function items inside it that branch (a function literal at line 287, onPageInit, onPageBeforeIn, …). 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 · Stepper.constructor (cyclomatic 62) · ×1
  • Stepper.constructor (cyclomatic 62) src/core/components/stepper/stepper-class.js:6 — Stepper.constructor has cyclomatic complexity 62 (threshold 15). Of this number, 21 points are the body's own statements and 41 belong to 12 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 · Calendar.renderMonth (cyclomatic 60) · ×1
  • Calendar.renderMonth (cyclomatic 60) REDACTED:1145 — Calendar.renderMonth has cyclomatic complexity 60 (threshold 15). Of this number, 56 points are the body's own statements and 4 belong to 2 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 · Dialog.constructor (cyclomatic 56) · ×1
  • Dialog.constructor (cyclomatic 56) src/core/components/dialog/dialog-class.js:10 — Dialog.constructor has cyclomatic complexity 56 (threshold 15). Of this number, 29 points are the body's own statements and 27 belong to 9 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 · navigate (cyclomatic 54) · ×1
  • navigate (cyclomatic 54) src/core/modules/router/navigate.js:623 — navigate has cyclomatic complexity 54 (threshold 15). Of this number, 40 points are the body's own statements and 14 belong to 12 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 · area-chart.AreaChart (cyclomatic 53) · ×1
  • area-chart.AreaChart (cyclomatic 53) src/react/components/area-chart.jsx:31 — area-chart.AreaChart has cyclomatic complexity 53 (threshold 15). Most of this is not in the body itself: 6 of the 53 points are its own statements and the rest belongs to 21 function items inside it that branch (setTooltip, formatTooltip, a function literal at line 327, …). 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 · Searchbar.search (cyclomatic 52) · ×1
  • Searchbar.search (cyclomatic 52) src/core/components/searchbar/searchbar-class.js:516 — Searchbar.search has cyclomatic complexity 52 (threshold 15). Of this number, 35 points are the body's own statements and 17 belong to 4 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 · create (cyclomatic 52) · ×1
  • create (cyclomatic 52) src/core/components/dialog/dialog.js:26 — create has cyclomatic complexity 52 (threshold 15). Most of this is not in the body itself: 2 of the 52 points are its own statements and the rest belongs to 12 function items inside it that branch (progress, prompt, alert, …). 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 · open (cyclomatic 51) · ×1
  • open (cyclomatic 51) src/core/components/card/card.js:9 — open has cyclomatic complexity 51 (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 · modalLoad (cyclomatic 50) · ×1
  • modalLoad (cyclomatic 50) src/core/modules/router/modal.js:5 — modalLoad has cyclomatic complexity 50 (threshold 15). Most of this is not in the body itself: 6 of the 50 points are its own statements and the rest belongs to 16 function items inside it that branch (routeCallback, onModalLoaded, loadModal, …). 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 · Router.pageCallback (cyclomatic 48) · ×1
  • Router.pageCallback (cyclomatic 48) src/core/modules/router/router-class.js:649 — Router.pageCallback has cyclomatic complexity 48 (threshold 15). Of this number, 40 points are the body's own statements and 8 belong to 2 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 · Router.init (cyclomatic 48) · ×1
  • Router.init (cyclomatic 48) src/core/modules/router/router-class.js:959 — Router.init has cyclomatic complexity 48 (threshold 15). Of this number, 38 points are the body's own statements and 10 belong to one function literal inside it that branches. 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 · tabLoad (cyclomatic 45) · ×1
  • tabLoad (cyclomatic 45) src/core/modules/router/tab.js:6 — tabLoad has cyclomatic complexity 45 (threshold 15). Of this number, 27 points are the body's own statements and 18 belong to 12 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 · VirtualList.render (cyclomatic 44) · ×1
  • VirtualList.render (cyclomatic 44) src/core/components/virtual-list/virtual-list-class.js:221 — VirtualList.render has cyclomatic complexity 44 (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 · list-item-content.ListItemContent (cyclomatic 44) · ×1
  • list-item-content.ListItemContent (cyclomatic 44) src/react/components/list-item-content.jsx:8 — list-item-content.ListItemContent has cyclomatic complexity 44 (threshold 15). Of this number, 43 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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 · get-device.calcDevice (cyclomatic 43) · ×1
  • get-device.calcDevice (cyclomatic 43) REDACTED:6 — get-device.calcDevice has cyclomatic complexity 43 (threshold 15). Of this number, 41 points are the body's own statements and 2 belong to one function literal inside it that branches. 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 · Tooltip.constructor (cyclomatic 43) · ×1
  • Tooltip.constructor (cyclomatic 43) src/core/components/tooltip/tooltip-class.js:8 — Tooltip.constructor has cyclomatic complexity 43 (threshold 15). Of this number, 18 points are the body's own statements and 25 belong to 8 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 · clicks.initClicks · ×1
  • clicks.initClicks::handleClicks (cyclomatic 43) src/core/modules/clicks/clicks.js:6 — clicks.initClicks::handleClicks has cyclomatic complexity 43 (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 · vdom.getData (cyclomatic 39) · ×1
  • vdom.getData (cyclomatic 39) src/core/modules/component/vdom.js:197 — vdom.getData has cyclomatic complexity 39 (threshold 15). Most of this is not in the body itself: 4 of the 39 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 200, 239, 274, …). 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.
D1 · Cyclomatic Complexity · navbar.Navbar (cyclomatic 39) · ×1
  • navbar.Navbar (cyclomatic 39) src/react/components/navbar.jsx:43 — navbar.Navbar has cyclomatic complexity 39 (threshold 15). Of this number, 26 points are the body's own statements and 13 belong to 12 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.
D1 · Cyclomatic Complexity · load (cyclomatic 39) · ×1
  • load (cyclomatic 39) src/core/modules/router/navigate.js:503 — load has cyclomatic complexity 39 (threshold 15). Of this number, 37 points are the body's own statements and 2 belong to 5 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 · messagebar.Messagebar (cyclomatic 37) · ×1
  • messagebar.Messagebar (cyclomatic 37) src/react/components/messagebar.jsx:50 — messagebar.Messagebar has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 14 of the 37 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 191, a function literal at line 124, a function literal at line 115, …). 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 · view.View (cyclomatic 37) · ×1
  • view.View (cyclomatic 37) src/react/components/view.jsx:85 — view.View has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 15 of the 37 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 172, a function literal at line 181, onDestroy, …). 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 · list-input.ListInput (cyclomatic 36) · ×1
  • list-input.ListInput (cyclomatic 36) src/react/components/list-input.jsx:84 — list-input.ListInput has cyclomatic complexity 36 (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. This shape REPEATS in the file: one other method here (list-input.ListInput::createInput) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · close (cyclomatic 36) · ×1
  • close (cyclomatic 36) src/core/components/card/card.js:390 — close has cyclomatic complexity 36 (threshold 15). Of this number, 33 points are the body's own statements and 3 belong to 3 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 · Notification.constructor (cyclomatic 34) · ×1
  • Notification.constructor (cyclomatic 34) REDACTED:8 — Notification.constructor has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 7 of the 34 points are its own statements and the rest belongs to 9 function items inside it that branch (handleTouchMove, handleTouchEnd, a function literal at line 77, …). 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 · Popover.resize (cyclomatic 33) · ×1
  • Popover.resize (cyclomatic 33) src/core/components/popover/popover-class.js:182 — Popover.resize 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 · Router.getInitialUrl (cyclomatic 33) · ×1
  • Router.getInitialUrl (cyclomatic 33) src/core/modules/router/router-class.js:869 — Router.getInitialUrl 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 · ListIndex.constructor (cyclomatic 32) · ×1
  • ListIndex.constructor (cyclomatic 32) src/core/components/list-index/list-index-class.js:6 — ListIndex.constructor has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 13 of the 32 points are its own statements and the rest belongs to 5 function items inside it that branch (handleTouchMove, handleClick, handleTouchStart, …). 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 · list.List (cyclomatic 31) · ×1
  • list.List (cyclomatic 31) src/react/components/list.jsx:87 — list.List has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 5 of the 31 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 248, a function literal at line 187, onDestroy, …). 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 · xhrRequest (cyclomatic 31) · ×1
  • xhrRequest (cyclomatic 31) src/core/modules/router/router-class.js:486 — xhrRequest has cyclomatic complexity 31 (threshold 15). Of this number, 16 points are the body's own statements and 15 belong to 4 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 · initNavbarOnScroll · ×1
  • initNavbarOnScroll::handleLargeNavbarCollapse (cyclomatic 30) src/core/components/navbar/navbar.js:329 — initNavbarOnScroll::handleLargeNavbarCollapse has cyclomatic complexity 30 (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 · Calendar.dateInRange (cyclomatic 29) · ×1
  • Calendar.dateInRange (cyclomatic 29) REDACTED:1073 — Calendar.dateInRange has cyclomatic complexity 29 (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 · Picker.constructor (cyclomatic 29) · ×1
  • Picker.constructor (cyclomatic 29) src/core/components/picker/picker-class.js:13 — Picker.constructor has cyclomatic complexity 29 (threshold 15). Of this number, 17 points are the body's own statements and 12 belong to one function item inside it that branches. 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 · resizable-view.resizableView (cyclomatic 29) · ×1
  • resizable-view.resizableView (cyclomatic 29) src/core/components/view/resizable-view.js:4 — resizable-view.resizableView has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 4 of the 29 points are its own statements and the rest belongs to 6 function items inside it that branch (handleTouchMove, handleResize, transformCSSWidth, …). 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 · loadModule (cyclomatic 29) · ×1
  • loadModule (cyclomatic 29) src/core/components/app/load-module.js:6 — loadModule has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 1 of the 29 points is its own statement and the rest belongs to 12 function items inside it that branch (a function literal at line 10, a function literal at line 98, a function literal at line 134, …). 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 · Popup.constructor · ×1
  • Popup.constructor::handleTouchMove (cyclomatic 28) src/core/components/popup/popup-class.js:158 — Popup.constructor::handleTouchMove has cyclomatic complexity 28 (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 · card.Card (cyclomatic 28) · ×1
  • card.Card (cyclomatic 28) src/react/components/card.jsx:50 — card.Card has cyclomatic complexity 28 (threshold 15). Of this number, 14 points are the body's own statements and 14 belong to 11 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 · size (cyclomatic 28) · ×1
  • size (cyclomatic 28) src/core/components/navbar/navbar.js:6 — size has cyclomatic complexity 28 (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 · Calendar.updateValue (cyclomatic 27) · ×1
  • Calendar.updateValue (cyclomatic 27) REDACTED:634 — Calendar.updateValue 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 · Calendar.setYearMonth (cyclomatic 27) · ×1
  • Calendar.setYearMonth (cyclomatic 27) REDACTED:981 — Calendar.setYearMonth 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 · Searchbar.enable · ×1
  • Searchbar.enable::enable (cyclomatic 27) src/core/components/searchbar/searchbar-class.js:319 — Searchbar.enable::enable 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. This shape REPEATS in the file: one other method here (Searchbar.enable) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · SmartSelect.renderItem (cyclomatic 27) · ×1
  • SmartSelect.renderItem (cyclomatic 27) src/core/components/smart-select/smart-select-class.js:400 — SmartSelect.renderItem has cyclomatic complexity 27 (threshold 15). Of this number, 23 points are the body's own statements and 4 belong to 2 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 · VirtualList.constructor (cyclomatic 27) · ×1
  • VirtualList.constructor (cyclomatic 27) src/core/components/virtual-list/virtual-list-class.js:8 — VirtualList.constructor has cyclomatic complexity 27 (threshold 15). Of this number, 19 points are the body's own statements and 8 belong to 2 function literals 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 · input.Input · ×1
  • input.Input::createInput (cyclomatic 27) src/react/components/input.jsx:357 — input.Input::createInput has cyclomatic complexity 27 (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. This shape REPEATS in the file: one other method here (input.Input) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · messages.Messages (cyclomatic 27) · ×1
  • messages.Messages (cyclomatic 27) src/react/components/messages.jsx:38 — messages.Messages has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 7 of the 27 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 118, onDestroy, a function literal at line 156, …). 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 · tab.Tab (cyclomatic 27) · ×1
  • tab.Tab (cyclomatic 27) src/react/components/tab.jsx:23 — tab.Tab has cyclomatic complexity 27 (threshold 15). Of this number, 19 points are the body's own statements and 8 belong to 5 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.
D1 · Cyclomatic Complexity · init (cyclomatic 27) · ×1
  • init (cyclomatic 27) src/core/components/color-picker/modules/wheel.js:33 — init has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 2 of the 27 points are its own statements and the rest belongs to 7 function items inside it that branch (handleTouchMove, handleTouchStart, handleTouchEnd, …). 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 · Modal.open (cyclomatic 26) · ×1
  • Modal.open (cyclomatic 26) src/core/components/modal/modal-class.js:80 — Modal.open has cyclomatic complexity 26 (threshold 15). Of this number, 22 points are the body's own statements and 4 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 · ColorPicker.setValue (cyclomatic 26) · ×1
  • ColorPicker.setValue (cyclomatic 26) src/core/components/color-picker/color-picker-class.js:240 — ColorPicker.setValue has cyclomatic complexity 26 (threshold 15). Of this number, 21 points are the body's own statements and 5 belong to 2 function literals 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 · vdom.getHooks (cyclomatic 26) · ×1
  • vdom.getHooks (cyclomatic 26) src/core/modules/component/vdom.js:97 — vdom.getHooks has cyclomatic complexity 26 (threshold 15). Of this number, 19 points are the body's own statements and 7 belong to 3 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 · list-input.ListInput · ×1
  • list-input.ListInput::createInput (cyclomatic 26) src/react/components/list-input.jsx:363 — list-input.ListInput::createInput has cyclomatic complexity 26 (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. This shape REPEATS in the file: one other method here (list-input.ListInput) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · ColorPicker.constructor (cyclomatic 25) · ×1
  • ColorPicker.constructor (cyclomatic 25) src/core/components/color-picker/color-picker-class.js:34 — ColorPicker.constructor has cyclomatic complexity 25 (threshold 15). Of this number, 13 points are the body's own statements and 12 belong to one function item inside it that branches. 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 · Gauge.render (cyclomatic 25) · ×1
  • Gauge.render (cyclomatic 25) src/core/components/gauge/gauge-class.js:58 — Gauge.render has cyclomatic complexity 25 (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 · open · ×1
  • open::onTouchMove (cyclomatic 25) src/core/components/card/card.js:303 — open::onTouchMove has cyclomatic complexity 25 (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 · componentLoader (cyclomatic 25) · ×1
  • componentLoader (cyclomatic 25) src/core/modules/router/component-loader.js:81 — componentLoader has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 10 of the 25 points are its own statements and the rest belongs to 6 function items inside it that branch (compile, a function literal at line 130, a function literal at line 144, …). 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 · Gauge.update (cyclomatic 24) · ×1
  • Gauge.update (cyclomatic 24) src/core/components/gauge/gauge-class.js:172 — Gauge.update has cyclomatic complexity 24 (threshold 15). Of this number, 23 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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 · Messages.addMessages (cyclomatic 24) · ×1
  • Messages.addMessages (cyclomatic 24) src/core/components/messages/messages-class.js:361 — Messages.addMessages has cyclomatic complexity 24 (threshold 15). Of this number, 21 points are the body's own statements and 3 belong to one function literal inside it that branches. 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 · Range.constructor (cyclomatic 24) · ×1
  • Range.constructor (cyclomatic 24) src/core/components/range/range-class.js:6 — Range.constructor 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. This shape REPEATS in the file: 2 other methods here (Range.constructor::handleTouchMove, Range.constructor::handleTouchEnd) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · Range.layout (cyclomatic 24) · ×1
  • Range.layout (cyclomatic 24) src/core/components/range/range-class.js:434 — Range.layout has cyclomatic complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to one function literal inside it that branches. 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 · Searchbar.disable (cyclomatic 24) · ×1
  • Searchbar.disable (cyclomatic 24) src/core/components/searchbar/searchbar-class.js:406 — Searchbar.disable has cyclomatic complexity 24 (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 · swiper.initSwiper (cyclomatic 24) · ×1
  • swiper.initSwiper (cyclomatic 24) src/core/components/swiper/swiper.js:18 — swiper.initSwiper has cyclomatic complexity 24 (threshold 15). Of this number, 15 points are the body's own statements and 9 belong to 3 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 · Tooltip.position (cyclomatic 24) · ×1
  • Tooltip.position (cyclomatic 24) src/core/components/tooltip/tooltip-class.js:196 — Tooltip.position has cyclomatic complexity 24 (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 · gauge.Gauge (cyclomatic 24) · ×1
  • gauge.Gauge (cyclomatic 24) src/react/components/gauge.jsx:29 — gauge.Gauge 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 · icon.Icon (cyclomatic 24) · ×1
  • icon.Icon (cyclomatic 24) src/react/components/icon.jsx:25 — icon.Icon has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 3 of the 24 points are its own statements and the rest belongs to 2 function items inside it that branch (getIconText, getClasses). 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 · input.Input (cyclomatic 24) · ×1
  • input.Input (cyclomatic 24) src/react/components/input.jsx:81 — input.Input 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. This shape REPEATS in the file: one other method here (input.Input::createInput) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · toolbar.Toolbar (cyclomatic 24) · ×1
  • toolbar.Toolbar (cyclomatic 24) src/react/components/toolbar.jsx:33 — toolbar.Toolbar has cyclomatic complexity 24 (threshold 15). Of this number, 16 points are the body's own statements and 8 belong to 6 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.
D1 · Cyclomatic Complexity · initNavbarOnScroll (cyclomatic 24) · ×1
  • initNavbarOnScroll (cyclomatic 24) src/core/components/navbar/navbar.js:189 — initNavbarOnScroll has cyclomatic complexity 24 (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 · resizable-panel.resizablePanel · ×1
  • resizable-panel.resizablePanel::handleTouchMove (cyclomatic 23) src/core/components/panel/resizable-panel.js:54 — resizable-panel.resizablePanel::handleTouchMove has cyclomatic complexity 23 (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 · PhotoBrowser.onOpen (cyclomatic 23) · ×1
  • PhotoBrowser.onOpen (cyclomatic 23) src/core/components/photo-browser/photo-browser-class.js:405 — PhotoBrowser.onOpen 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 · create (cyclomatic 23) · ×1
  • create (cyclomatic 23) src/core/components/panel/panel.js:29 — create has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 6 function items inside it that branch (get, open, close, …). 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 · Autocomplete.constructor (cyclomatic 22) · ×1
  • Autocomplete.constructor (cyclomatic 22) src/core/components/autocomplete/autocomplete-class.js:17 — Autocomplete.constructor has cyclomatic complexity 22 (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 shape REPEATS in the file: one other method here (Autocomplete.constructor::onPageInputChange) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · ColorPicker.open (cyclomatic 22) · ×1
  • ColorPicker.open (cyclomatic 22) src/core/components/color-picker/color-picker-class.js:696 — ColorPicker.open has cyclomatic complexity 22 (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 · form.formFromData (cyclomatic 22) · ×1
  • form.formFromData (cyclomatic 22) src/core/components/form/form.js:144 — form.formFromData has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 5 of the 22 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 162, 175, 184, …). 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.
D1 · Cyclomatic Complexity · Popover.constructor · ×1
  • Popover.constructor::handleClick (cyclomatic 22) src/core/components/popover/popover-class.js:115 — Popover.constructor::handleClick has cyclomatic complexity 22 (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. This shape REPEATS in the file: one other method here (Popover.constructor) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · pickerColumn (cyclomatic 22) · ×1
  • pickerColumn (cyclomatic 22) src/core/components/picker/picker-column.js:3 — pickerColumn has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 11 function items inside it that branch (updateColItems, initCol, a function literal at line 75, …). 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 · loadBack (cyclomatic 22) · ×1
  • loadBack (cyclomatic 22) src/core/modules/router/back.js:385 — loadBack has cyclomatic complexity 22 (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 · messages.default (cyclomatic 21) · ×1
  • messages.default (cyclomatic 21) kitchen-sink/react/src/pages/messages.jsx:18 — messages.default has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 7 function items inside it that branch (isFirstMessage, isLastMessage, isTailMessage, …). 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 · Autocomplete.constructor · ×1
  • Autocomplete.constructor::onPageInputChange (cyclomatic 21) src/core/components/autocomplete/autocomplete-class.js:148 — Autocomplete.constructor::onPageInputChange 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 shape REPEATS in the file: one other method here (Autocomplete.constructor) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · Panel.open (cyclomatic 21) · ×1
  • Panel.open (cyclomatic 21) src/core/components/panel/panel-class.js:402 — Panel.open has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. 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 · message.Message (cyclomatic 21) · ×1
  • message.Message (cyclomatic 21) src/react/components/message.jsx:39 — message.Message has cyclomatic complexity 21 (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 · page-content.PageContent (cyclomatic 21) · ×1
  • page-content.PageContent (cyclomatic 21) src/react/components/page-content.jsx:43 — page-content.PageContent has cyclomatic complexity 21 (threshold 15). Of this number, 12 points are the body's own statements and 9 belong to 8 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 · pie-chart.PieChart (cyclomatic 21) · ×1
  • pie-chart.PieChart (cyclomatic 21) src/react/components/pie-chart.jsx:18 — pie-chart.PieChart has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 8 function items inside it that branch (setTooltip, formatTooltipText, a function literal at line 135, …). 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 · init (cyclomatic 21) · ×1
  • init (cyclomatic 21) src/core/components/input/input.js:206 — init has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 7 function items inside it that branch (onChange, onBlur, onInvalid, …). 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 · ColorPicker.onOpen (cyclomatic 20) · ×1
  • ColorPicker.onOpen (cyclomatic 20) src/core/components/color-picker/color-picker-class.js:564 — ColorPicker.onOpen has cyclomatic complexity 20 (threshold 15). Of this number, 15 points are the body's own statements and 5 belong to one function literal inside it that branches. 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 · PhotoBrowser.onSlideChange (cyclomatic 20) · ×1
  • PhotoBrowser.onSlideChange (cyclomatic 20) src/core/components/photo-browser/photo-browser-class.js:57 — PhotoBrowser.onSlideChange 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.
D1 · Cyclomatic Complexity · PullToRefresh.constructor (cyclomatic 20) · ×1
  • PullToRefresh.constructor (cyclomatic 20) src/core/components/pull-to-refresh/pull-to-refresh-class.js:7 — PullToRefresh.constructor 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 shape REPEATS in the file: 3 other methods here (PullToRefresh.constructor::handleTouchMove, PullToRefresh.constructor::handleTouchEnd, PullToRefresh.constructor::handleMouseWheel) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · TextEditor.constructor (cyclomatic 20) · ×1
  • TextEditor.constructor (cyclomatic 20) src/core/components/text-editor/text-editor-class.js:32 — TextEditor.constructor has cyclomatic complexity 20 (threshold 15). Of this number, 14 points are the body's own statements and 6 belong to 2 function literals 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 · link.Link (cyclomatic 20) · ×1
  • link.Link (cyclomatic 20) src/react/components/link.jsx:52 — link.Link has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function item inside it that branches. 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 · panel.Panel (cyclomatic 20) · ×1
  • panel.Panel (cyclomatic 20) src/react/components/panel.jsx:52 — panel.Panel has cyclomatic complexity 20 (threshold 15). Of this number, 10 points are the body's own statements and 10 belong to 5 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 · stepper.Stepper (cyclomatic 20) · ×1
  • stepper.Stepper (cyclomatic 20) src/react/components/stepper.jsx:59 — stepper.Stepper has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 8 function items inside it that branch (setValue, getValue, a function literal at line 150, …). 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 · pageInit (cyclomatic 20) · ×1
  • pageInit (cyclomatic 20) src/core/components/navbar/navbar.js:551 — pageInit 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 · material-colors.materialColors (cyclomatic 19) · ×1
  • material-colors.materialColors (cyclomatic 19) src/core/shared/material-colors.js:71 — material-colors.materialColors has cyclomatic complexity 19 (threshold 15). Of this number, 10 points are the body's own statements and 9 belong to 4 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 · Modal.close (cyclomatic 19) · ×1
  • Modal.close (cyclomatic 19) src/core/components/modal/modal-class.js:174 — Modal.close has cyclomatic complexity 19 (threshold 15). Of this number, 13 points are the body's own statements and 6 belong to 2 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 · Panel.constructor (cyclomatic 19) · ×1
  • Panel.constructor (cyclomatic 19) src/core/components/panel/panel-class.js:9 — Panel.constructor has cyclomatic complexity 19 (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 · Sheet.constructor (cyclomatic 19) · ×1
  • Sheet.constructor (cyclomatic 19) src/core/components/sheet/sheet-class.js:8 — Sheet.constructor has cyclomatic complexity 19 (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 shape REPEATS in the file: 2 other methods here (Sheet.constructor::handleTouchMove, Sheet.constructor::handleTouchEnd) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · render (cyclomatic 19) · ×1
  • render (cyclomatic 19) src/core/components/actions/actions-class.js:264 — render has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 273, 307, 271, …). 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.
D1 · Cyclomatic Complexity · show (cyclomatic 19) · ×1
  • show (cyclomatic 19) src/core/components/progressbar/progressbar.js:39 — show has cyclomatic complexity 19 (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 · toast.default (cyclomatic 18) · ×1
  • toast.default (cyclomatic 18) kitchen-sink/react/src/pages/toast.jsx:4 — toast.default has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 9 function items inside it that branch (onPageBeforeRemove, showToastIcon, showToastBottom, …). 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 · Calendar.openTimePicker (cyclomatic 18) · ×1
  • Calendar.openTimePicker (cyclomatic 18) REDACTED:1707 — Calendar.openTimePicker has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to 2 function literals 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 · Messages.renderMessage (cyclomatic 18) · ×1
  • Messages.renderMessage (cyclomatic 18) src/core/components/messages/messages-class.js:111 — Messages.renderMessage 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 · treeview-item.TreeviewItem (cyclomatic 18) · ×1
  • treeview-item.TreeviewItem (cyclomatic 18) src/react/components/treeview-item.jsx:38 — treeview-item.TreeviewItem has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 belong to 5 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 · render (cyclomatic 18) · ×1
  • render (cyclomatic 18) src/core/components/area-chart/area-chart-class.js:334 — render has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 belong to 5 function literals 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 · initAjaxForm · ×1
  • initAjaxForm::onSubmitChange (cyclomatic 18) src/core/components/form/form.js:216 — initAjaxForm::onSubmitChange has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · utils.getTranslate (cyclomatic 17) · ×1
  • utils.getTranslate (cyclomatic 17) src/core/shared/utils.js:98 — utils.getTranslate has cyclomatic complexity 17 (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 · utils.serializeObject (cyclomatic 17) · ×1
  • utils.serializeObject (cyclomatic 17) src/core/shared/utils.js:146 — utils.serializeObject has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 165, varName). 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 · CustomModal.constructor (cyclomatic 17) · ×1
  • CustomModal.constructor (cyclomatic 17) src/core/components/modal/custom-modal-class.js:6 — CustomModal.constructor has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 belong to 3 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 · Popover.constructor (cyclomatic 17) · ×1
  • Popover.constructor (cyclomatic 17) src/core/components/popover/popover-class.js:8 — Popover.constructor has cyclomatic complexity 17 (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. This shape REPEATS in the file: one other method here (Popover.constructor::handleClick) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · SmartSelect.getItemsData (cyclomatic 17) · ×1
  • SmartSelect.getItemsData (cyclomatic 17) src/core/components/smart-select/smart-select-class.js:315 — SmartSelect.getItemsData has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to one function literal inside it that branches (line 320). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · SmartSelect.onOpen (cyclomatic 17) · ×1
  • SmartSelect.onOpen (cyclomatic 17) src/core/components/smart-select/smart-select-class.js:665 — SmartSelect.onOpen has cyclomatic complexity 17 (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 · TextEditor.createLink (cyclomatic 17) · ×1
  • TextEditor.createLink (cyclomatic 17) src/core/components/text-editor/text-editor-class.js:159 — TextEditor.createLink has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. 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 · touch-highlight.initTouchHighlight (cyclomatic 17) · ×1
  • touch-highlight.initTouchHighlight (cyclomatic 17) src/core/components/touch-highlight/touch-highlight.js:3 — touch-highlight.initTouchHighlight has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 5 function items inside it that branch (onPointerDown, removeHoverHighlight, setLightPosition, …). 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 · Router.getPageData (cyclomatic 17) · ×1
  • Router.getPageData (cyclomatic 17) src/core/modules/router/router-class.js:607 — Router.getPageData has cyclomatic complexity 17 (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 · actions.Actions (cyclomatic 17) · ×1
  • actions.Actions (cyclomatic 17) src/react/components/actions.jsx:39 — actions.Actions has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 5 function items inside it that branch (onMount, a function literal at line 67, modalEvents, …). 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 · fab.Fab (cyclomatic 17) · ×1
  • fab.Fab (cyclomatic 17) src/react/components/fab.jsx:24 — fab.Fab has cyclomatic complexity 17 (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 · popover.Popover (cyclomatic 17) · ×1
  • popover.Popover (cyclomatic 17) src/react/components/popover.jsx:36 — popover.Popover has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 5 function items inside it that branch (onMount, a function literal at line 80, a function literal at line 111, …). 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 · sheet.Sheet · ×1
  • sheet.Sheet::onMount (cyclomatic 17) src/react/components/sheet.jsx:121 — sheet.Sheet::onMount has cyclomatic complexity 17 (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 · DataTable.constructor (cyclomatic 16) · ×1
  • DataTable.constructor (cyclomatic 16) src/core/components/data-table/data-table-class.js:6 — DataTable.constructor has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 2 function items inside it that branch (handleChange, handleSortableClick). 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 · PhotoBrowser.render (cyclomatic 16) · ×1
  • PhotoBrowser.render (cyclomatic 16) src/core/components/photo-browser/photo-browser-class.js:331 — PhotoBrowser.render has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 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 · Searchbar.enable (cyclomatic 16) · ×1
  • Searchbar.enable (cyclomatic 16) src/core/components/searchbar/searchbar-class.js:311 — Searchbar.enable 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. This shape REPEATS in the file: one other method here (Searchbar.enable::enable) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · SmartSelect.constructor · ×1
  • SmartSelect.constructor::handleInputChange (cyclomatic 16) src/core/components/smart-select/smart-select-class.js:100 — SmartSelect.constructor::handleInputChange 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 · Toggle.constructor · ×1
  • Toggle.constructor::handleTouchMove (cyclomatic 16) src/core/components/toggle/toggle-class.js:81 — Toggle.constructor::handleTouchMove has cyclomatic complexity 16 (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 · Router.findMatchingRoute (cyclomatic 16) · ×1
  • Router.findMatchingRoute (cyclomatic 16) src/core/modules/router/router-class.js:396 — Router.findMatchingRoute has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 403, 424, 418). 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.
D1 · Cyclomatic Complexity · view.getCurrentView (cyclomatic 16) · ×1
  • view.getCurrentView (cyclomatic 16) src/core/components/view/view.js:5 — view.getCurrentView 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 · VirtualList.setListSize (cyclomatic 16) · ×1
  • VirtualList.setListSize (cyclomatic 16) src/core/components/virtual-list/virtual-list-class.js:171 — VirtualList.setListSize 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 · init (cyclomatic 16) · ×1
  • init (cyclomatic 16) src/core/components/statusbar/statusbar.js:127 — init 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 · initTabbarHighlight (cyclomatic 16) · ×1
  • initTabbarHighlight (cyclomatic 16) src/core/components/toolbar/tabbar-highlight.js:58 — initTabbarHighlight has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 2 function items inside it that branch (f7ToolbarOnPointer, a function literal at line 86). 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 · initToolbarOnScroll · ×1
  • initToolbarOnScroll::handleScroll (cyclomatic 16) src/core/components/toolbar/toolbar.js:119 — initToolbarOnScroll::handleScroll has cyclomatic complexity 16 (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 · openIn (cyclomatic 16) · ×1
  • openIn (cyclomatic 16) src/core/modules/router/component-loader.js:6 — openIn has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 belong to 3 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.
D17 · Explicit Debt · HackComment · ×1
  • HackComment scripts/icon-font/generate_font.py:41 — # hack removal of <switch> </switch> tags — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D2 · Cognitive Complexity · forward (cognitive 185) · ×1
  • forward (cognitive 185) src/core/modules/router/navigate.js:20 — forward has cognitive complexity 185 (threshold 15). Drivers by points: if/else 69 (105 pts), boolean chains 51, ternaries 11 (20 pts), loops 3 (9 pts) (nesting depth added 51). Of this number, 167 points are the body's own statements and 18 belong to 14 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 · renderMonth (cognitive 149) · ×1
  • renderMonth (cognitive 149) REDACTED:1145 — renderMonth has cognitive complexity 149 (threshold 15). Drivers by points: if/else 37 (100 pts), ternaries 9 (29 pts), boolean chains 11, loops 4 (9 pts) (nesting depth added 88). Of this number, 137 points are the body's own statements and 12 belong to 2 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 · back.backward (cognitive 129) · ×1
  • back.backward (cognitive 129) src/core/modules/router/back.js:11 — back.backward has cognitive complexity 129 (threshold 15). Drivers by points: if/else 51 (79 pts), boolean chains 38, ternaries 8 (10 pts), loops 1 (2 pts) (nesting depth added 31). Of this number, 111 points are the body's own statements and 18 belong to 2 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 · show (cognitive 125) · ×1
  • show (cognitive 125) src/core/components/tabs/tabs.js:5 — show has cognitive complexity 125 (threshold 15). Drivers by points: if/else 41 (79 pts), boolean chains 39, ternaries 3 (7 pts) (nesting depth added 42). Of this number, 118 points are the body's own statements and 7 belong to 8 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 · back (cognitive 119) · ×1
  • back (cognitive 119) src/core/modules/router/back.js:460 — back has cognitive complexity 119 (threshold 15). Drivers by points: if/else 48 (80 pts), boolean chains 33, error handling 1 (3 pts), ternaries 1 (3 pts) (nesting depth added 36). Of this number, 101 points are the body's own statements and 18 belong to 13 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 · search (cognitive 96) · ×1
  • search (cognitive 96) src/core/components/searchbar/searchbar-class.js:516 — search has cognitive complexity 96 (threshold 15). Drivers by points: if/else 39 (72 pts), boolean chains 12, loops 3 (8 pts), ternaries 2 (4 pts) (nesting depth added 40). Of this number, 58 points are the body's own statements and 38 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 · constructor (cognitive 86) · ×1
  • constructor (cognitive 86) src/core/components/searchbar/searchbar-class.js:9 — constructor has cognitive complexity 86 (threshold 15). Drivers by points: if/else 43 (56 pts), boolean chains 30 (nesting depth added 13). Of this number, 61 points are the body's own statements and 25 belong to 10 function items inside it that branch. 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 · renderToolbar (cognitive 84) · ×1
  • renderToolbar (cognitive 84) src/core/components/picker/picker-class.js:263 — renderToolbar has cognitive complexity 84 (threshold 15). Drivers by points: if/else 47 (55 pts), boolean chains 19, ternaries 9 (10 pts) (nesting depth added 9). Of this number, 70 points are the body's own statements and 14 belong to 12 function items inside it that branch. 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 · VirtualList.render (cognitive 82) · ×1
  • VirtualList.render (cognitive 82) src/core/components/virtual-list/virtual-list-class.js:221 — VirtualList.render has cognitive complexity 82 (threshold 15). Drivers by points: if/else 39 (69 pts), boolean chains 10, loops 2 (3 pts) (nesting depth added 31). 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 · page.Page (cognitive 77) · ×1
  • page.Page (cognitive 77) src/react/components/page.jsx:59 — page.Page has cognitive complexity 77 (threshold 15). Drivers by points: if/else 42 (59 pts), boolean chains 16, ternaries 2 (nesting depth added 17). Most of this is not in the body itself: 11 of the 77 points are its own statements and the rest belongs to 21 function items inside it that branch (a function literal at line 287, onPageInit, onPageBeforeIn, …). 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 · getData (cognitive 72) · ×1
  • getData (cognitive 72) src/core/modules/component/vdom.js:197 — getData has cognitive complexity 72 (threshold 15). Drivers by points: if/else 31 (60 pts), boolean chains 7, ternaries 2 (5 pts) (nesting depth added 32). None of this is in the body itself: all 72 points belong to 4 function items inside it that branch (a function literal at line 200, a function literal at line 239, a function literal at line 274, …). 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 · navigate (cognitive 69) · ×1
  • navigate (cognitive 69) src/core/modules/router/navigate.js:623 — navigate has cognitive complexity 69 (threshold 15). Drivers by points: if/else 32 (41 pts), boolean chains 22, ternaries 2 (4 pts), error handling 1 (2 pts) (nesting depth added 12). Of this number, 52 points are the body's own statements and 17 belong to 12 function items inside it that branch. 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 · swipe-panel.swipePanel · ×1
  • swipe-panel.swipePanel::handleTouchEnd (cognitive 67) src/core/components/panel/swipe-panel.js:216 — swipe-panel.swipePanel::handleTouchEnd has cognitive complexity 67 (threshold 15). Drivers by points: if/else 32 (41 pts), boolean chains 19, ternaries 3 (7 pts) (nesting depth added 13). 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 · open (cognitive 66) · ×1
  • open (cognitive 66) src/core/components/card/card.js:9 — open has cognitive complexity 66 (threshold 15). Drivers by points: if/else 65 (81 pts), boolean chains 28, ternaries 9 (14 pts) (nesting depth added 21). 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 · tabLoad (cognitive 66) · ×1
  • tabLoad (cognitive 66) src/core/modules/router/tab.js:6 — tabLoad has cognitive complexity 66 (threshold 15). Drivers by points: if/else 36 (52 pts), boolean chains 10, error handling 2 (4 pts) (nesting depth added 18). Of this number, 36 points are the body's own statements and 30 belong to 12 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 · constructor (cognitive 65) · ×1
  • constructor (cognitive 65) src/core/components/stepper/stepper-class.js:6 — constructor has cognitive complexity 65 (threshold 15). Drivers by points: if/else 39 (45 pts), boolean chains 12, ternaries 8 (nesting depth added 6). Of this number, 20 points are the body's own statements and 45 belong to 16 function items inside it that branch. 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 · Dialog.constructor (cognitive 63) · ×1
  • Dialog.constructor (cognitive 63) src/core/components/dialog/dialog-class.js:10 — Dialog.constructor has cognitive complexity 63 (threshold 15). Drivers by points: if/else 34 (49 pts), boolean chains 14 (nesting depth added 15). Of this number, 36 points are the body's own statements and 27 belong to 9 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 · init (cognitive 62) · ×1
  • init (cognitive 62) src/core/modules/router/router-class.js:959 — init has cognitive complexity 62 (threshold 15). Drivers by points: if/else 21 (40 pts), boolean chains 20, ternaries 1 (2 pts) (nesting depth added 20). Of this number, 33 points are the body's own statements and 29 belong to 4 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 · area-chart.AreaChart (cognitive 58) · ×1
  • area-chart.AreaChart (cognitive 58) src/react/components/area-chart.jsx:31 — area-chart.AreaChart has cognitive complexity 58 (threshold 15). Drivers by points: if/else 31 (34 pts), ternaries 12 (14 pts), boolean chains 9, loops 1 (nesting depth added 5). Most of this is not in the body itself: 5 of the 58 points are its own statements and the rest belongs to 21 function items inside it that branch (setTooltip, formatTooltip, a function literal at line 106, …). 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 · list-item.ListItem (cognitive 58) · ×1
  • list-item.ListItem (cognitive 58) src/react/components/list-item.jsx:135 — list-item.ListItem has cognitive complexity 58 (threshold 15). Drivers by points: if/else 27 (28 pts), boolean chains 20, ternaries 5 (10 pts) (nesting depth added 6). Of this number, 33 points are the body's own statements and 25 belong to 20 function items inside it that branch. 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 · Actions.constructor (cognitive 57) · ×1
  • Actions.constructor (cognitive 57) src/core/components/actions/actions-class.js:11 — Actions.constructor has cognitive complexity 57 (threshold 15). Drivers by points: if/else 28 (36 pts), boolean chains 20, ternaries 1 (nesting depth added 8). Of this number, 31 points are the body's own statements and 26 belong to 7 function items inside it that branch. 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 · Calendar.dateInRange (cognitive 56) · ×1
  • Calendar.dateInRange (cognitive 56) REDACTED:1073 — Calendar.dateInRange has cognitive complexity 56 (threshold 15). Drivers by points: if/else 21 (48 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 28). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · constructor (cognitive 55) · ×1
  • constructor (cognitive 55) src/core/components/tooltip/tooltip-class.js:8 — constructor has cognitive complexity 55 (threshold 15). Drivers by points: if/else 34 (40 pts), boolean chains 11, ternaries 4 (nesting depth added 6). Most of this is not in the body itself: 15 of the 55 points are its own statements and the rest belongs to 10 function items inside it that branch (attachEvents, detachEvents, handleTouchMove, …). 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.
D2 · Cognitive Complexity · create (cognitive 53) · ×1
  • create (cognitive 53) src/core/components/dialog/dialog.js:26 — create has cognitive complexity 53 (threshold 15). Drivers by points: ternaries 22, if/else 17 (19 pts), boolean chains 12 (nesting depth added 2). Most of this is not in the body itself: 1 of the 53 points is its own statement and the rest belongs to 12 function items inside it that branch (progress, prompt, alert, …). 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.
D2 · Cognitive Complexity · clicks.initClicks · ×1
  • clicks.initClicks::handleClicks (cognitive 52) src/core/modules/clicks/clicks.js:6 — clicks.initClicks::handleClicks has cognitive complexity 52 (threshold 15). Drivers by points: if/else 21 (36 pts), boolean chains 16 (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.
D2 · Cognitive Complexity · modalLoad (cognitive 51) · ×1
  • modalLoad (cognitive 51) src/core/modules/router/modal.js:5 — modalLoad has cognitive complexity 51 (threshold 15). Drivers by points: if/else 26 (31 pts), boolean chains 11, ternaries 4 (5 pts), error handling 2 (4 pts) (nesting depth added 8). Most of this is not in the body itself: 5 of the 51 points are its own statements and the rest belongs to 16 function items inside it that branch (onModalLoaded, loadModal, routeCallback, …). 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 · Calendar.constructor (cognitive 47) · ×1
  • Calendar.constructor (cognitive 47) REDACTED:9 — Calendar.constructor has cognitive complexity 47 (threshold 15). Drivers by points: if/else 22 (26 pts), boolean chains 21 (nesting depth added 4). Of this number, 32 points are the body's own statements and 15 belong to 8 function items inside it that branch. 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 · Calendar.updateValue (cognitive 47) · ×1
  • Calendar.updateValue (cognitive 47) REDACTED:634 — Calendar.updateValue has cognitive complexity 47 (threshold 15). Drivers by points: if/else 12 (30 pts), boolean chains 9, loops 2 (6 pts), ternaries 1 (2 pts) (nesting depth added 23). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · view.View (cognitive 46) · ×1
  • view.View (cognitive 46) src/react/components/view.jsx:85 — view.View has cognitive complexity 46 (threshold 15). Drivers by points: if/else 16 (31 pts), boolean chains 11, ternaries 3 (4 pts) (nesting depth added 16). Most of this is not in the body itself: 12 of the 46 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 172, a function literal at line 181, onDestroy, …). 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 · Router.pageCallback (cognitive 44) · ×1
  • Router.pageCallback (cognitive 44) src/core/modules/router/router-class.js:649 — Router.pageCallback has cognitive complexity 44 (threshold 15). Drivers by points: if/else 23 (29 pts), boolean chains 14, ternaries 1 (nesting depth added 6). Of this number, 36 points are the body's own statements and 8 belong to 2 function items inside it that branch. 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 · loadModule (cognitive 44) · ×1
  • loadModule (cognitive 44) src/core/components/app/load-module.js:6 — loadModule has cognitive complexity 44 (threshold 15). Drivers by points: if/else 18 (28 pts), boolean chains 6, error handling 3 (6 pts), ternaries 2 (4 pts) (nesting depth added 15). None of this is in the body itself: all 44 points belong to 12 function items inside it that branch (a function literal at line 10, a function literal at line 98, a function literal at line 134, …). 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 · Popover.resize (cognitive 43) · ×1
  • Popover.resize (cognitive 43) src/core/components/popover/popover-class.js:182 — Popover.resize has cognitive complexity 43 (threshold 15). Drivers by points: if/else 20 (30 pts), boolean chains 12, ternaries 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.
D2 · Cognitive Complexity · close (cognitive 42) · ×1
  • close (cognitive 42) src/core/components/card/card.js:390 — close has cognitive complexity 42 (threshold 15). Drivers by points: if/else 24 (31 pts), boolean chains 8, ternaries 2 (3 pts) (nesting depth added 8). Of this number, 39 points are the body's own statements and 3 belong to 3 function items inside it that branch. 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 · Router.getInitialUrl (cognitive 40) · ×1
  • Router.getInitialUrl (cognitive 40) src/core/modules/router/router-class.js:869 — Router.getInitialUrl has cognitive complexity 40 (threshold 15). Drivers by points: if/else 17 (26 pts), boolean chains 13, 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 · load (cognitive 40) · ×1
  • load (cognitive 40) src/core/modules/router/navigate.js:503 — load has cognitive complexity 40 (threshold 15). Drivers by points: if/else 17 (26 pts), boolean chains 10, error handling 2 (4 pts) (nesting depth added 11). Of this number, 36 points are the body's own statements and 4 belong to 5 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 · calcDevice (cognitive 39) · ×1
  • calcDevice (cognitive 39) REDACTED:6 — calcDevice has cognitive complexity 39 (threshold 15). Drivers by points: boolean chains 19, if/else 14 (18 pts), ternaries 1 (2 pts) (nesting depth added 5). Of this number, 35 points are the body's own statements and 4 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 · constructor (cognitive 39) · ×1
  • constructor (cognitive 39) src/core/components/toggle/toggle-class.js:6 — constructor has cognitive complexity 39 (threshold 15). Drivers by points: if/else 19 (23 pts), boolean chains 10, ternaries 6 (nesting depth added 4). Most of this is not in the body itself: 4 of the 39 points are its own statements and the rest belongs to 9 function items inside it that branch (handleTouchEnd, handleTouchMove, handleTouchStart, …). 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 · Gauge.update (cognitive 38) · ×1
  • Gauge.update (cognitive 38) src/core/components/gauge/gauge-class.js:172 — Gauge.update has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 10 (20 pts), if/else 10 (12 pts), boolean chains 6 (nesting depth added 12). Of this number, 37 points are the body's own statements and 1 belongs to one function literal 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 · list-input.ListInput (cognitive 38) · ×1
  • list-input.ListInput (cognitive 38) src/react/components/list-input.jsx:84 — list-input.ListInput has cognitive complexity 38 (threshold 15). Drivers by points: boolean chains 62, if/else 47 (60 pts), ternaries 8 (nesting depth added 13). 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 shape REPEATS in the file: one other method here (list-input.ListInput::createInput) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · list-item-content.ListItemContent (cognitive 38) · ×1
  • list-item-content.ListItemContent (cognitive 38) src/react/components/list-item-content.jsx:8 — list-item-content.ListItemContent has cognitive complexity 38 (threshold 15). Drivers by points: boolean chains 20, if/else 14 (17 pts), ternaries 1 (nesting depth added 3). Of this number, 37 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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 · initNavbarOnScroll · ×1
  • initNavbarOnScroll::handleLargeNavbarCollapse (cognitive 38) src/core/components/navbar/navbar.js:329 — initNavbarOnScroll::handleLargeNavbarCollapse has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (24 pts), boolean chains 14 (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 · Range.layout (cognitive 37) · ×1
  • Range.layout (cognitive 37) src/core/components/range/range-class.js:434 — Range.layout has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 10 (17 pts), if/else 10 (14 pts), boolean chains 6 (nesting depth added 11). Of this number, 33 points are the body's own statements and 4 belong to one function literal 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 · constructor (cognitive 37) · ×1
  • constructor (cognitive 37) src/core/components/list-index/list-index-class.js:6 — constructor has cognitive complexity 37 (threshold 15). Drivers by points: if/else 22 (26 pts), boolean chains 8, ternaries 3 (nesting depth added 4). Most of this is not in the body itself: 15 of the 37 points are its own statements and the rest belongs to 9 function items inside it that branch (handleTouchMove, handleClick, handleTouchEnd, …). 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.
D2 · Cognitive Complexity · Calendar.setYearMonth (cognitive 36) · ×1
  • Calendar.setYearMonth (cognitive 36) REDACTED:981 — Calendar.setYearMonth has cognitive complexity 36 (threshold 15). Drivers by points: if/else 15 (19 pts), ternaries 8 (12 pts), boolean chains 5 (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 · Popup.constructor · ×1
  • Popup.constructor::handleTouchMove (cognitive 35) src/core/components/popup/popup-class.js:158 — Popup.constructor::handleTouchMove has cognitive complexity 35 (threshold 15). Drivers by points: if/else 16 (25 pts), boolean chains 9, 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. This shape REPEATS in the file: one other method here (Popup.constructor) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · Tooltip.position (cognitive 35) · ×1
  • Tooltip.position (cognitive 35) src/core/components/tooltip/tooltip-class.js:196 — Tooltip.position has cognitive complexity 35 (threshold 15). Drivers by points: if/else 16 (27 pts), boolean chains 7, ternaries 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 · messagebar.Messagebar (cognitive 35) · ×1
  • messagebar.Messagebar (cognitive 35) src/react/components/messagebar.jsx:50 — messagebar.Messagebar has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 18, if/else 14 (16 pts), ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 11 of the 35 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 191, a function literal at line 124, a function literal at line 115, …). 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 · open (cognitive 35) · ×1
  • open (cognitive 35) src/core/components/modal/modal-class.js:80 — open has cognitive complexity 35 (threshold 15). Drivers by points: if/else 20 (29 pts), boolean chains 6 (nesting depth added 9). Of this number, 27 points are the body's own statements and 8 belong to 5 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 · ColorPicker.open (cognitive 33) · ×1
  • ColorPicker.open (cognitive 33) src/core/components/color-picker/color-picker-class.js:696 — ColorPicker.open has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (23 pts), boolean chains 8, ternaries 1 (2 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 · constructor (cognitive 33) · ×1
  • constructor (cognitive 33) REDACTED:8 — constructor has cognitive complexity 33 (threshold 15). Drivers by points: if/else 21, boolean chains 8, ternaries 4. Most of this is not in the body itself: 6 of the 33 points are its own statements and the rest belongs to 13 function items inside it that branch (handleTouchMove, handleTouchEnd, a function literal at line 77, …). 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 · resizable-panel.resizablePanel · ×1
  • resizable-panel.resizablePanel::handleTouchMove (cognitive 32) src/core/components/panel/resizable-panel.js:54 — resizable-panel.resizablePanel::handleTouchMove has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (17 pts), ternaries 4 (8 pts), boolean chains 7 (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 · Searchbar.disable (cognitive 32) · ×1
  • Searchbar.disable (cognitive 32) src/core/components/searchbar/searchbar-class.js:406 — Searchbar.disable has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 8, ternaries 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 · swiper.initSwiper (cognitive 32) · ×1
  • swiper.initSwiper (cognitive 32) src/core/components/swiper/swiper.js:18 — swiper.initSwiper has cognitive complexity 32 (threshold 15). Drivers by points: if/else 16 (22 pts), boolean chains 6, error handling 1 (3 pts), ternaries 1 (nesting depth added 8). Most of this is not in the body itself: 15 of the 32 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 89, 39, 79). 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 · setValue (cognitive 32) · ×1
  • setValue (cognitive 32) src/core/components/smart-select/smart-select-class.js:168 — setValue has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 4 (14 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 17). 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 · Messages.addMessages (cognitive 31) · ×1
  • Messages.addMessages (cognitive 31) src/core/components/messages/messages-class.js:361 — Messages.addMessages has cognitive complexity 31 (threshold 15). Drivers by points: if/else 18 (22 pts), boolean chains 7, ternaries 1 (2 pts) (nesting depth added 5). Of this number, 24 points are the body's own statements and 7 belong to one function literal inside it that branches. 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 · Picker.constructor (cognitive 31) · ×1
  • Picker.constructor (cognitive 31) src/core/components/picker/picker-class.js:13 — Picker.constructor has cognitive complexity 31 (threshold 15). Drivers by points: if/else 16 (21 pts), boolean chains 9, ternaries 1 (nesting depth added 5). Of this number, 19 points are the body's own statements and 12 belong to one function item inside it that branches. 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 · initNavbarOnScroll (cognitive 31) · ×1
  • initNavbarOnScroll (cognitive 31) src/core/components/navbar/navbar.js:189 — initNavbarOnScroll has cognitive complexity 31 (threshold 15). Drivers by points: if/else 64 (86 pts), boolean chains 42 (nesting depth added 22). 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 · Range.constructor (cognitive 30) · ×1
  • Range.constructor (cognitive 30) src/core/components/range/range-class.js:6 — Range.constructor has cognitive complexity 30 (threshold 15). Drivers by points: if/else 60 (83 pts), boolean chains 13, ternaries 6, loops 2 (4 pts) (nesting depth added 25). 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 shape REPEATS in the file: 2 other methods here (Range.constructor::handleTouchMove, Range.constructor::handleTouchEnd) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · Searchbar.enable (cognitive 30) · ×1
  • Searchbar.enable (cognitive 30) src/core/components/searchbar/searchbar-class.js:311 — Searchbar.enable has cognitive complexity 30 (threshold 15). Drivers by points: if/else 24 (41 pts), boolean chains 13, ternaries 2 (5 pts) (nesting depth added 20). 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 shape REPEATS in the file: one other method here (Searchbar.enable::enable) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · TextEditor.createLink (cognitive 30) · ×1
  • TextEditor.createLink (cognitive 30) src/core/components/text-editor/text-editor-class.js:159 — TextEditor.createLink has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 3 (8 pts), boolean chains 4 (nesting depth added 15). Of this number, 28 points are the body's own statements and 2 belong to one function literal 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 · list.List (cognitive 30) · ×1
  • list.List (cognitive 30) src/react/components/list.jsx:87 — list.List has cognitive complexity 30 (threshold 15). Drivers by points: if/else 16 (17 pts), boolean chains 11, ternaries 2 (nesting depth added 1). Most of this is not in the body itself: 4 of the 30 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 248, a function literal at line 187, onDestroy, …). 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 · messages.Messages (cognitive 30) · ×1
  • messages.Messages (cognitive 30) src/react/components/messages.jsx:38 — messages.Messages has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 6, loops 2 (3 pts), ternaries 2 (nesting depth added 5). Most of this is not in the body itself: 7 of the 30 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 118, a function literal at line 156, onDestroy, …). 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 · navbar.Navbar (cognitive 30) · ×1
  • navbar.Navbar (cognitive 30) src/react/components/navbar.jsx:43 — navbar.Navbar has cognitive complexity 30 (threshold 15). Drivers by points: if/else 17, boolean chains 13. Of this number, 18 points are the body's own statements and 12 belong to 12 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.
D2 · Cognitive Complexity · init (cognitive 30) · ×1
  • init (cognitive 30) src/core/components/statusbar/statusbar.js:127 — init has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (26 pts), boolean chains 4 (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 · componentLoader (cognitive 30) · ×1
  • componentLoader (cognitive 30) src/core/modules/router/component-loader.js:81 — componentLoader has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 9, error handling 3 (5 pts), ternaries 2 (nesting depth added 5). Most of this is not in the body itself: 12 of the 30 points are its own statements and the rest belongs to 6 function items inside it that branch (compile, a function literal at line 130, a function literal at line 144, …). 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 · xhrRequest (cognitive 30) · ×1
  • xhrRequest (cognitive 30) src/core/modules/router/router-class.js:486 — xhrRequest has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 7, ternaries 2 (4 pts), loops 1 (2 pts), error handling 1 (nesting depth added 9). Most of this is not in the body itself: 11 of the 30 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 522, 553, 549, …). 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 · form.formFromData (cognitive 29) · ×1
  • form.formFromData (cognitive 29) src/core/components/form/form.js:144 — form.formFromData has cognitive complexity 29 (threshold 15). Drivers by points: if/else 16 (21 pts), boolean chains 6, match/switch 1 (2 pts) (nesting depth added 6). Most of this is not in the body itself: 4 of the 29 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 162, 175, 184, …). 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 · Searchbar.enable · ×1
  • Searchbar.enable::enable (cognitive 29) src/core/components/searchbar/searchbar-class.js:319 — Searchbar.enable::enable has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 9, ternaries 1 (2 pts) (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. This shape REPEATS in the file: one other method here (Searchbar.enable) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · size (cognitive 29) · ×1
  • size (cognitive 29) src/core/components/navbar/navbar.js:6 — size has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 8, ternaries 4 (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.
D2 · Cognitive Complexity · pickerColumn (cognitive 29) · ×1
  • pickerColumn (cognitive 29) src/core/components/picker/picker-column.js:3 — pickerColumn has cognitive complexity 29 (threshold 15). Drivers by points: if/else 19 (25 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 7). Most of this is not in the body itself: 1 of the 29 points is its own statement and the rest belongs to 11 function items inside it that branch (updateColItems, a function literal at line 75, initCol, …). 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 · constructor (cognitive 29) · ×1
  • constructor (cognitive 29) src/core/components/virtual-list/virtual-list-class.js:8 — constructor has cognitive complexity 29 (threshold 15). Drivers by points: if/else 21 (22 pts), boolean chains 5, ternaries 2 (nesting depth added 1). Of this number, 21 points are the body's own statements and 8 belong to 4 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.
D2 · Cognitive Complexity · ColorPicker.constructor (cognitive 28) · ×1
  • ColorPicker.constructor (cognitive 28) src/core/components/color-picker/color-picker-class.js:34 — ColorPicker.constructor has cognitive complexity 28 (threshold 15). Drivers by points: if/else 16 (20 pts), boolean chains 8 (nesting depth added 4). Of this number, 15 points are the body's own statements and 13 belong to one function item inside it that branches. 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 · ColorPicker.setValue (cognitive 28) · ×1
  • ColorPicker.setValue (cognitive 28) src/core/components/color-picker/color-picker-class.js:240 — ColorPicker.setValue has cognitive complexity 28 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 9 (nesting depth added 3). Of this number, 22 points are the body's own statements and 6 belong to 2 function literals inside it that branch. 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 · card.Card (cognitive 28) · ×1
  • card.Card (cognitive 28) src/react/components/card.jsx:50 — card.Card has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15, ternaries 7, boolean chains 6. Most of this is not in the body itself: 13 of the 28 points are its own statements and the rest belongs to 11 function items inside it that branch (attachEvents, onMount, a function literal at line 133, …). 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 · open · ×1
  • open::onTouchMove (cognitive 28) src/core/components/card/card.js:303 — open::onTouchMove has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 9, ternaries 3 (5 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 · show (cognitive 28) · ×1
  • show (cognitive 28) src/core/components/progressbar/progressbar.js:39 — show has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (15 pts), ternaries 3 (9 pts), boolean chains 4 (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 · init (cognitive 28) · ×1
  • init (cognitive 28) src/core/components/color-picker/modules/wheel.js:33 — init has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 8, ternaries 5 (nesting depth added 2). Most of this is not in the body itself: 1 of the 28 points is its own statement and the rest belongs to 7 function items inside it that branch (handleTouchMove, handleTouchStart, handleTouchEnd, …). 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.
D2 · Cognitive Complexity · Modal.close (cognitive 27) · ×1
  • Modal.close (cognitive 27) src/core/components/modal/modal-class.js:174 — Modal.close has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (21 pts), ternaries 2 (4 pts), boolean chains 2 (nesting depth added 9). Of this number, 18 points are the body's own statements and 9 belong to 2 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 · VirtualList.setListSize (cognitive 27) · ×1
  • VirtualList.setListSize (cognitive 27) src/core/components/virtual-list/virtual-list-class.js:171 — VirtualList.setListSize has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 4, 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 · utils.serializeObject (cognitive 26) · ×1
  • utils.serializeObject (cognitive 26) src/core/shared/utils.js:146 — utils.serializeObject has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (19 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 8). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to 2 function items inside it that branch (a function literal at line 165, varName). 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 · Panel.open (cognitive 26) · ×1
  • Panel.open (cognitive 26) src/core/components/panel/panel-class.js:402 — Panel.open has cognitive complexity 26 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 4, ternaries 3 (4 pts) (nesting depth added 4). Of this number, 21 points are the body's own statements and 5 belong to one function literal inside it that branches. 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 · vdom.getHooks (cognitive 26) · ×1
  • vdom.getHooks (cognitive 26) src/core/modules/component/vdom.js:97 — vdom.getHooks has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 7 (nesting depth added 5). Of this number, 15 points are the body's own statements and 11 belong to 3 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 · input.Input · ×1
  • input.Input::createInput (cognitive 26) src/react/components/input.jsx:357 — input.Input::createInput has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 11, if/else 7 (10 pts), ternaries 5 (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 shape REPEATS in the file: one other method here (input.Input) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · input.Input (cognitive 25) · ×1
  • input.Input (cognitive 25) src/react/components/input.jsx:81 — input.Input has cognitive complexity 25 (threshold 15). Drivers by points: if/else 55 (66 pts), boolean chains 52, ternaries 7 (8 pts) (nesting depth added 12). 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 shape REPEATS in the file: one other method here (input.Input::createInput) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · list-input.ListInput · ×1
  • list-input.ListInput::createInput (cognitive 25) src/react/components/list-input.jsx:363 — list-input.ListInput::createInput has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 10, if/else 7 (10 pts), ternaries 5 (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 shape REPEATS in the file: one other method here (list-input.ListInput) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · init (cognitive 25) · ×1
  • init (cognitive 25) src/core/components/input/input.js:206 — init has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 9 (nesting depth added 4). None of this is in the body itself: all 25 points belong to 7 function items inside it that branch (onBlur, onChange, onFocus, …). 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 · onOpen (cognitive 25) · ×1
  • onOpen (cognitive 25) src/core/components/photo-browser/photo-browser-class.js:405 — onOpen has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 7, ternaries 2 (3 pts) (nesting depth added 5). Most of this is not in the body itself: 11 of the 25 points are its own statements and the rest belongs to 17 function items inside it that branch (renderSlide, slideChange, click, …). 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 · resizableView (cognitive 25) · ×1
  • resizableView (cognitive 25) src/core/components/view/resizable-view.js:4 — resizableView has cognitive complexity 25 (threshold 15). Drivers by points: if/else 15, boolean chains 7, ternaries 3. Most of this is not in the body itself: 3 of the 25 points are its own statements and the rest belongs to 7 function items inside it that branch (handleTouchMove, handleResize, transformCSSWidth, …). 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 · Calendar.addValue (cognitive 24) · ×1
  • Calendar.addValue (cognitive 24) REDACTED:569 — Calendar.addValue has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 4, loops 1 (2 pts) (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 · PhotoBrowser.onSlideChange (cognitive 24) · ×1
  • PhotoBrowser.onSlideChange (cognitive 24) src/core/components/photo-browser/photo-browser-class.js:57 — PhotoBrowser.onSlideChange has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (17 pts), ternaries 4 (5 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.
D2 · Cognitive Complexity · icon.Icon (cognitive 24) · ×1
  • icon.Icon (cognitive 24) src/react/components/icon.jsx:25 — icon.Icon has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 9 (nesting depth added 4). Most of this is not in the body itself: 2 of the 24 points are its own statements and the rest belongs to 2 function items inside it that branch (getClasses, getIconText). 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.
D2 · Cognitive Complexity · tab.Tab (cognitive 24) · ×1
  • tab.Tab (cognitive 24) src/react/components/tab.jsx:23 — tab.Tab has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 11, if/else 10 (11 pts), ternaries 2 (nesting depth added 1). Of this number, 15 points are the body's own statements and 9 belong to 5 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.
D2 · Cognitive Complexity · initAjaxForm · ×1
  • initAjaxForm::onSubmitChange (cognitive 24) src/core/components/form/form.js:216 — initAjaxForm::onSubmitChange has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 7, error handling 1, ternaries 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.
D2 · Cognitive Complexity · SmartSelect.onOpen (cognitive 23) · ×1
  • SmartSelect.onOpen (cognitive 23) src/core/components/smart-select/smart-select-class.js:665 — SmartSelect.onOpen has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 4, ternaries 1 (2 pts) (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.
D2 · Cognitive Complexity · render (cognitive 23) · ×1
  • render (cognitive 23) src/core/components/gauge/gauge-class.js:58 — render has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 12, ternaries 10, 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 · modal-methods.ModalMethods (cognitive 22) · ×1
  • modal-methods.ModalMethods (cognitive 22) src/core/shared/modal-methods.js:5 — modal-methods.ModalMethods has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 2 (nesting depth added 7). Of this number, 19 points are the body's own statements and 3 belong to one function literal 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 · Autocomplete.constructor (cognitive 22) · ×1
  • Autocomplete.constructor (cognitive 22) src/core/components/autocomplete/autocomplete-class.js:17 — Autocomplete.constructor has cognitive complexity 22 (threshold 15). Drivers by points: if/else 41 (61 pts), boolean chains 23, ternaries 7 (12 pts), loops 5 (8 pts) (nesting depth added 28). 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 · PullToRefresh.constructor (cognitive 22) · ×1
  • PullToRefresh.constructor (cognitive 22) src/core/components/pull-to-refresh/pull-to-refresh-class.js:7 — PullToRefresh.constructor has cognitive complexity 22 (threshold 15). Drivers by points: if/else 109 (181 pts), boolean chains 50, loops 1 (3 pts), ternaries 2 (nesting depth added 74). 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 shape REPEATS in the file: one other method here (PullToRefresh.constructor::handleTouchEnd) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · SmartSelect.renderItem (cognitive 22) · ×1
  • SmartSelect.renderItem (cognitive 22) src/core/components/smart-select/smart-select-class.js:400 — SmartSelect.renderItem has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 8 (nesting depth added 5). Of this number, 16 points are the body's own statements and 6 belong to 2 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 · stepper.Stepper (cognitive 22) · ×1
  • stepper.Stepper (cognitive 22) src/react/components/stepper.jsx:59 — stepper.Stepper has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10, boolean chains 6, ternaries 3 (6 pts) (nesting depth added 3). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to 8 function items inside it that branch (setValue, getValue, a function literal at line 150, …). 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 · create (cognitive 22) · ×1
  • create (cognitive 22) src/core/components/panel/panel.js:29 — create has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13, boolean chains 9. None of this is in the body itself: all 22 points belong to 6 function items inside it that branch (get, open, close, …). 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.
D2 · Cognitive Complexity · loadBack (cognitive 22) · ×1
  • loadBack (cognitive 22) src/core/modules/router/back.js:385 — loadBack has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 7, error handling 2 (4 pts) (nesting depth added 3). 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 · material-colors.materialColors (cognitive 21) · ×1
  • material-colors.materialColors (cognitive 21) src/core/shared/material-colors.js:71 — material-colors.materialColors has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13, ternaries 4 (7 pts), boolean chains 1 (nesting depth added 3). Of this number, 11 points are the body's own statements and 10 belong to 4 function items inside it that branch. 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 · touch-highlight.initTouchHighlight (cognitive 21) · ×1
  • touch-highlight.initTouchHighlight (cognitive 21) src/core/components/touch-highlight/touch-highlight.js:3 — touch-highlight.initTouchHighlight has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 2 (nesting depth added 4). None of this is in the body itself: all 21 points belong to 5 function items inside it that branch (onPointerDown, removeHoverHighlight, setLightPosition, …). 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.
D2 · Cognitive Complexity · view.getCurrentView (cognitive 21) · ×1
  • view.getCurrentView (cognitive 21) src/core/components/view/view.js:5 — view.getCurrentView has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 4 (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 · fab.Fab (cognitive 21) · ×1
  • fab.Fab (cognitive 21) src/react/components/fab.jsx:24 — fab.Fab has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 7, loops 1 (2 pts) (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 · source (cognitive 21) · ×1
  • source (cognitive 21) src/core/components/autocomplete/autocomplete-class.js:420 — source has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 4 (8 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to one function literal inside it that branches (line 426). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · open (cognitive 21) · ×1
  • open (cognitive 21) src/core/components/swipeout/swipeout.js:448 — open has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 1, ternaries 1 (nesting depth added 4). Of this number, 11 points are the body's own statements and 10 belong to 3 function literals inside it that branch. 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 · constructor (cognitive 21) · ×1
  • constructor (cognitive 21) src/core/components/text-editor/text-editor-class.js:32 — constructor has cognitive complexity 21 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 4, error handling 1 (2 pts) (nesting depth added 2). Of this number, 13 points are the body's own statements and 8 belong to 2 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.
D2 · Cognitive Complexity · Sheet.constructor (cognitive 20) · ×1
  • Sheet.constructor (cognitive 20) src/core/components/sheet/sheet-class.js:8 — Sheet.constructor has cognitive complexity 20 (threshold 15). Drivers by points: if/else 121 (191 pts), boolean chains 51, ternaries 6 (8 pts) (nesting depth added 72). 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 · Router.findMatchingRoute (cognitive 20) · ×1
  • Router.findMatchingRoute (cognitive 20) src/core/modules/router/router-class.js:396 — Router.findMatchingRoute has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 5 (nesting depth added 4). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 403, 424, 418). 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 · page-content.PageContent (cognitive 20) · ×1
  • page-content.PageContent (cognitive 20) src/react/components/page-content.jsx:43 — page-content.PageContent has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11, boolean chains 5, ternaries 4. Of this number, 11 points are the body's own statements and 9 belong to 8 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.
D2 · Cognitive Complexity · pie-chart.PieChart (cognitive 20) · ×1
  • pie-chart.PieChart (cognitive 20) src/react/components/pie-chart.jsx:18 — pie-chart.PieChart has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11, boolean chains 7, ternaries 2. None of this is in the body itself: all 20 points belong to 8 function items inside it that branch (setTooltip, formatTooltipText, a function literal at line 135, …). 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 · constructor (cognitive 20) · ×1
  • constructor (cognitive 20) src/core/components/panel/panel-class.js:9 — constructor has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (12 pts), ternaries 5 (6 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · form.formToData (cognitive 19) · ×1
  • form.formToData (cognitive 19) src/core/components/form/form.js:91 — form.formToData has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 6). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 102, 115, 123, …). 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 · Popover.constructor · ×1
  • Popover.constructor::handleClick (cognitive 19) src/core/components/popover/popover-class.js:115 — Popover.constructor::handleClick has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 11, if/else 5 (8 pts) (nesting depth added 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. This shape REPEATS in the file: one other method here (Popover.constructor) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · Popover.constructor (cognitive 19) · ×1
  • Popover.constructor (cognitive 19) src/core/components/popover/popover-class.js:8 — Popover.constructor has cognitive complexity 19 (threshold 15). Drivers by points: if/else 22 (27 pts), boolean chains 19 (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 shape REPEATS in the file: one other method here (Popover.constructor::handleClick) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · PullToRefresh.constructor · ×1
  • PullToRefresh.constructor::handleTouchEnd (cognitive 19) src/core/components/pull-to-refresh/pull-to-refresh-class.js:328 — PullToRefresh.constructor::handleTouchEnd has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 4 (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. This shape REPEATS in the file: one other method here (PullToRefresh.constructor) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · eventslisteners.updateEvents (cognitive 19) · ×1
  • eventslisteners.updateEvents (cognitive 19) src/core/modules/component/eventslisteners.js:22 — eventslisteners.updateEvents has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 4 (nesting depth added 6). Of this number, 13 points are the body's own statements and 6 belong to 2 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 · message.Message (cognitive 19) · ×1
  • message.Message (cognitive 19) src/react/components/message.jsx:39 — message.Message has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 19. 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 · getTranslate (cognitive 19) · ×1
  • getTranslate (cognitive 19) src/core/shared/utils.js:98 — getTranslate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 3, ternaries 1 (2 pts) (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 · initTabbarHighlight (cognitive 19) · ×1
  • initTabbarHighlight (cognitive 19) src/core/components/toolbar/tabbar-highlight.js:58 — initTabbarHighlight has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 1 (nesting depth added 4). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 2 function items inside it that branch (f7ToolbarOnPointer, a function literal at line 86). 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 · messages.default (cognitive 18) · ×1
  • messages.default (cognitive 18) kitchen-sink/react/src/pages/messages.jsx:18 — messages.default has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12, boolean chains 5, ternaries 1. Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 7 function items inside it that branch (sendMessage, isFirstMessage, isLastMessage, …). 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 · DataTable.constructor · ×1
  • DataTable.constructor::handleChange (cognitive 18) src/core/components/data-table/data-table-class.js:41 — DataTable.constructor::handleChange has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 2 (6 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.
D2 · Cognitive Complexity · Range.setValue (cognitive 18) · ×1
  • Range.setValue (cognitive 18) src/core/components/range/range-class.js:512 — Range.setValue has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (15 pts), 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 · TextEditor.onSelectionChange (cognitive 18) · ×1
  • TextEditor.onSelectionChange (cognitive 18) src/core/components/text-editor/text-editor-class.js:249 — TextEditor.onSelectionChange has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 7 (nesting depth added 3). 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 · VirtualList.moveItem (cognitive 18) · ×1
  • VirtualList.moveItem (cognitive 18) src/core/components/virtual-list/virtual-list-class.js:495 — VirtualList.moveItem has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 3 (6 pts), boolean chains 2 (nesting depth added 6). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 513). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · link.Link (cognitive 18) · ×1
  • link.Link (cognitive 18) src/react/components/link.jsx:52 — link.Link has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, if/else 7 (8 pts), ternaries 1 (nesting depth added 1). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. 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 · blend (cognitive 18) · ×1
  • blend (cognitive 18) src/core/shared/material-colors.js:35 — blend has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 9 (13 pts), boolean chains 4, if/else 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.
D2 · Cognitive Complexity · render (cognitive 18) · ×1
  • render (cognitive 18) src/core/components/actions/actions-class.js:264 — render has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13, boolean chains 3, ternaries 2. Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 273, 307, 271, …). 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 · initToolbarOnScroll · ×1
  • initToolbarOnScroll::handleScroll (cognitive 18) src/core/components/toolbar/toolbar.js:119 — initToolbarOnScroll::handleScroll has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 4 (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 · utils.merge (cognitive 17) · ×1
  • utils.merge (cognitive 17) src/core/shared/utils.js:198 — utils.merge has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 2 (4 pts), boolean chains 3 (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 · Framework7Class.useModule (cognitive 17) · ×1
  • Framework7Class.useModule (cognitive 17) src/core/shared/class.js:44 — Framework7Class.useModule has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 1, ternaries 1 (nesting depth added 4). Of this number, 10 points are the body's own statements and 7 belong to 2 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 · Calendar.formatDate (cognitive 17) · ×1
  • Calendar.formatDate (cognitive 17) REDACTED:490 — Calendar.formatDate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 8). Of this number, 14 points are the body's own statements and 3 belong to 2 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 · ColorPicker.onOpen (cognitive 17) · ×1
  • ColorPicker.onOpen (cognitive 17) src/core/components/color-picker/color-picker-class.js:564 — ColorPicker.onOpen has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 4 (nesting depth added 1). Of this number, 13 points are the body's own statements and 4 belong to one function literal inside it that branches. 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 · CustomModal.constructor (cognitive 17) · ×1
  • CustomModal.constructor (cognitive 17) src/core/components/modal/custom-modal-class.js:6 — CustomModal.constructor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 6 (nesting depth added 1). Of this number, 9 points are the body's own statements and 8 belong to 3 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.
D2 · Cognitive Complexity · Picker.updateValue (cognitive 17) · ×1
  • Picker.updateValue (cognitive 17) src/core/components/picker/picker-class.js:209 — Picker.updateValue has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 2 (4 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 · Popup.constructor (cognitive 17) · ×1
  • Popup.constructor (cognitive 17) src/core/components/popup/popup-class.js:8 — Popup.constructor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 61 (82 pts), boolean chains 37, ternaries 2 (nesting depth added 21). 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 shape REPEATS in the file: one other method here (Popup.constructor::handleTouchMove) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · SmartSelect.constructor (cognitive 17) · ×1
  • SmartSelect.constructor (cognitive 17) src/core/components/smart-select/smart-select-class.js:10 — SmartSelect.constructor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 19 (28 pts), boolean chains 6, loops 1 (2 pts), ternaries 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.
D2 · Cognitive Complexity · TextEditor.onButtonClick (cognitive 17) · ×1
  • TextEditor.onButtonClick (cognitive 17) src/core/components/text-editor/text-editor-class.js:354 — TextEditor.onButtonClick has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 5 (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 · Router.getPageData (cognitive 17) · ×1
  • Router.getPageData (cognitive 17) src/core/modules/router/router-class.js:607 — Router.getPageData has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 10, if/else 5 (6 pts), ternaries 1 (nesting depth added 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 · actions.Actions (cognitive 17) · ×1
  • actions.Actions (cognitive 17) src/react/components/actions.jsx:39 — actions.Actions has cognitive complexity 17 (threshold 15). Drivers by points: if/else 17. None of this is in the body itself: all 17 points belong to 5 function items inside it that branch (onMount, a function literal at line 67, modalEvents, …). 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 · popover.Popover (cognitive 17) · ×1
  • popover.Popover (cognitive 17) src/react/components/popover.jsx:36 — popover.Popover has cognitive complexity 17 (threshold 15). Drivers by points: if/else 16, boolean chains 1. None of this is in the body itself: all 17 points belong to 5 function items inside it that branch (onMount, a function literal at line 80, a function literal at line 111, …). 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 · render (cognitive 17) · ×1
  • render (cognitive 17) src/core/components/area-chart/area-chart-class.js:334 — render has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, if/else 6, ternaries 4. Of this number, 12 points are the body's own statements and 5 belong to 5 function literals 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.
D2 · Cognitive Complexity · validate (cognitive 17) · ×1
  • validate (cognitive 17) src/core/components/input/input.js:64 — validate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 1 (4 pts), boolean chains 1 (nesting depth added 7). Of this number, 15 points are the body's own statements and 2 belong to 2 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 · constructor (cognitive 17) · ×1
  • constructor (cognitive 17) src/core/modules/component/component-class.js:90 — constructor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 5, error handling 2 (3 pts) (nesting depth added 2). 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 (a function literal at line 142, a function literal at line 119, a function literal at line 139, …). 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 · toast.default (cognitive 16) · ×1
  • toast.default (cognitive 16) kitchen-sink/react/src/pages/toast.jsx:4 — toast.default has cognitive complexity 16 (threshold 15). Drivers by points: if/else 16. None of this is in the body itself: all 16 points belong to 9 function items inside it that branch (onPageBeforeRemove, showToastBottom, showToastTop, …). 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.
D2 · Cognitive Complexity · Calendar.nextMonth (cognitive 16) · ×1
  • Calendar.nextMonth (cognitive 16) REDACTED:868 — Calendar.nextMonth has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 4 (6 pts), boolean chains 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 shape REPEATS in the file: one other method here (Calendar.prevMonth) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · Calendar.prevMonth (cognitive 16) · ×1
  • Calendar.prevMonth (cognitive 16) REDACTED:924 — Calendar.prevMonth has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 4 (6 pts), boolean chains 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 shape REPEATS in the file: one other method here (Calendar.nextMonth) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · Calendar.openTimePicker (cognitive 16) · ×1
  • Calendar.openTimePicker (cognitive 16) REDACTED:1707 — Calendar.openTimePicker has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 3 (4 pts), boolean chains 2, loops 2 (nesting depth added 3). 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 · Calendar.closeTimePicker (cognitive 16) · ×1
  • Calendar.closeTimePicker (cognitive 16) REDACTED:1788 — Calendar.closeTimePicker has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 4 (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 · Messages.renderMessage (cognitive 16) · ×1
  • Messages.renderMessage (cognitive 16) src/core/components/messages/messages-class.js:111 — Messages.renderMessage has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 13, if/else 2, ternaries 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 · SmartSelect.setValueText (cognitive 16) · ×1
  • SmartSelect.setValueText (cognitive 16) src/core/components/smart-select/smart-select-class.js:286 — SmartSelect.setValueText has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 6). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 296). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · VirtualList.deleteItems (cognitive 16) · ×1
  • VirtualList.deleteItems (cognitive 16) src/core/components/virtual-list/virtual-list-class.js:556 — VirtualList.deleteItems has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 1 (nesting depth added 7). Of this number, 11 points are the body's own statements and 5 belong to one function literal 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 · panel.Panel (cognitive 16) · ×1
  • panel.Panel (cognitive 16) src/react/components/panel.jsx:52 — panel.Panel has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11, boolean chains 5. Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 133, a function literal at line 138, a function literal at line 162, …). 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 · sheet.Sheet · ×1
  • sheet.Sheet::onMount (cognitive 16) src/react/components/sheet.jsx:121 — sheet.Sheet::onMount has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14, boolean chains 2. 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 · treeview-item.TreeviewItem (cognitive 16) · ×1
  • treeview-item.TreeviewItem (cognitive 16) src/react/components/treeview-item.jsx:38 — treeview-item.TreeviewItem has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 7, ternaries 2. Of this number, 11 points are the body's own statements and 5 belong to 5 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.
D2 · Cognitive Complexity · handle (cognitive 16) · ×1
  • handle (cognitive 16) src/core/shared/history.js:28 — handle has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 2 (nesting depth added 3). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 42). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · pageInit (cognitive 16) · ×1
  • pageInit (cognitive 16) src/core/components/navbar/navbar.js:551 — pageInit has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 5 (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 · setVisibleBreakpoint (cognitive 16) · ×1
  • setVisibleBreakpoint (cognitive 16) src/core/components/panel/panel-class.js:139 — setVisibleBreakpoint has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4 (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 · setHighlight (cognitive 16) · ×1
  • setHighlight (cognitive 16) src/core/components/toolbar/toolbar.js:6 — setHighlight has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 2, ternaries 1 (2 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, 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 · constructor (cognitive 16) · ×1
  • constructor (cognitive 16) src/core/components/view/view-class.js:8 — constructor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (13 pts), ternaries 1 (3 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, 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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
IC1 · Incompleteness & stubs · Both branches are identical · ×1
  • Both branches are identical — the condition decides nothing src/core/components/autocomplete/autocomplete-class.js:386 — Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
IC1 · Incompleteness & stubs · Markup wires an event to an empty handler · ×1
  • Markup wires an event to an empty handler src/react/components/toggle.jsx:128 — `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
P1 · CI/CD gates · CI pipeline targets a decommissioned service · ×1
  • CI pipeline targets a decommissioned service — The pipeline is well-formed, but the only CI definition is `.travis.yml`, and its `README.md` build badge still points at `travis-ci.org` — a service shut down in June 2021. No other CI is configured in this repository, so nothing has been building or testing changes here since that shutdown — the steps below describe a gate that is not running. Porting it is mostly mechanical: the build and test commands already written here are what a replacement pipeline would run.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 0 typed · 857 plain JS — the untyped files are kitchen-sink/react/src/app.js, kitchen-sink/react/src/app.jsx, kitchen-sink/react/src/pages/404.jsx, kitchen-sink/react/src/pages/about.jsx, kitchen-sink/react/src/pages/accordion.jsx, kitchen-sink/react/src/pages/action-sheet.jsx (+851 more).
R10 · Code Duplication · Duplication concentrated across 42 sibling directories (116 clone groups) · ×1
  • Duplication concentrated across 42 sibling directories (116 clone groups) src/core/components/photo-browser/photo-browser-class.js:635 — 116 duplicated blocks under src/core/components/ have copies in at least two of the sibling directories accordion, actions, area-chart, autocomplete, calendar, card (+36 more sibling(s) not listed) — 85 of them are reported below, and 31 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 116 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 116 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 116 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 4 sibling directories (88 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (88 clone groups) src/react/shared/components-router.js:2 — 88 duplicated blocks under src/ have copies in at least two of the sibling directories core, react, svelte, vue — 64 of them are reported below, and 24 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 88 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 88 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 88 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 3 sibling directories (49 clone groups) · ×1
  • Duplication concentrated across 3 sibling directories (49 clone groups) kitchen-sink/react/src/pages/picker.jsx:12 — 49 duplicated blocks under kitchen-sink/ have copies in at least two of the sibling directories react, svelte, vue — 41 of them are reported below, and 8 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 49 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 49 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 49 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 3 sibling directories (6 clone groups) · ×1
  • Duplication concentrated across 3 sibling directories (6 clone groups) src/core/components/popover/popover.js:34 — 6 of the duplicated blocks reported below have copies in at least two of the sibling directories components, modules, shared under src/core/. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplicated block with local edits (322 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (322 matched lines × 2 locations) src/core/modules/router/back.js:23 — src/core/modules/router/back.js:23 · src/core/modules/router/navigate.js:37 — the two spans are one implementation copied and then locally edited — 1813 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 (245 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (245 matched lines × 2 locations) src/react/components/input.jsx:149 — src/react/components/input.jsx:149 · src/react/components/list-input.jsx:164 — the two spans are one implementation copied and then locally edited — 1514 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 (236 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (236 matched lines × 2 locations) src/svelte/components/input.svelte:35 — src/svelte/components/input.svelte:35 · src/svelte/components/list-input.svelte:41 — the two spans are one implementation copied and then locally edited — 1351 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 (141 lines × 2 locations) · ×1
  • Duplicated block (141 lines × 2 locations) kitchen-sink/react/src/pages/picker.jsx:12 — kitchen-sink/react/src/pages/picker.jsx:12 · kitchen-sink/vue/src/pages/picker.vue:124 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Wholesale file copy (139 identical lines × 3 files) · ×1
  • Wholesale file copy (139 identical lines × 3 files) src/react/shared/components-router.js:2 — src/react/shared/components-router.js:2 · src/svelte/shared/components-router.js:3 · src/vue/shared/components-router.js:2 — these 3 files are line-for-line copies of one another — 139 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (115 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (115 matched lines × 2 locations) src/core/components/photo-browser/photo-browser-class.js:635 — src/core/components/photo-browser/photo-browser-class.js:635 · src/core/components/smart-select/smart-select-class.js:815 — the two spans are one implementation copied and then locally edited — 609 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 (111 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (111 matched lines × 2 locations) src/core/components/panel/resizable-panel.js:4 — src/core/components/panel/resizable-panel.js:4 · src/core/components/view/resizable-view.js:4 — the two spans are one implementation copied and then locally edited — 866 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 (98 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (98 matched lines × 2 locations) src/react/components/area-chart.jsx:35 — src/react/components/area-chart.jsx:35 · src/svelte/components/area-chart.svelte:7 — the two spans are one implementation copied and then locally edited — 677 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 (96 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (96 matched lines × 2 locations) src/core/components/pull-to-refresh/pull-to-refresh-class.js:180 — src/core/components/pull-to-refresh/pull-to-refresh-class.js:180 · src/core/components/pull-to-refresh/pull-to-refresh-class.js:429 — the two spans are one implementation copied and then locally edited — 536 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 with local edits (92 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (92 matched lines × 2 locations) src/core/components/color-picker/modules/hs-spectrum.js:16 — src/core/components/color-picker/modules/hs-spectrum.js:16 · src/core/components/color-picker/modules/sb-spectrum.js:15 — the two spans are one implementation copied and then locally edited — 621 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 (91 lines × 2 locations) · ×1
  • Duplicated block (91 lines × 2 locations) src/vue/components/input.vue:99 — src/vue/components/input.vue:99 · src/vue/components/list-input.vue:123 — 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 (79 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (79 matched lines × 2 locations) src/core/components/color-picker/modules/rgb-bars.js:113 — src/core/components/color-picker/modules/rgb-bars.js:113 · src/core/components/color-picker/modules/rgb-sliders.js:116 — the two spans are one implementation copied and then locally edited — 617 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 · Wholesale file copy (77 identical lines × 2 files) · ×1
  • Wholesale file copy (77 identical lines × 2 files) kitchen-sink/react/src/pages/tabbar-icons.jsx:1 — kitchen-sink/react/src/pages/tabbar-icons.jsx:1 · kitchen-sink/react/src/pages/tabbar.jsx:1 — these 2 files are line-for-line copies of one another — 77 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (74 identical lines × 2 files) · ×1
  • Wholesale file copy (74 identical lines × 2 files) src/react/shared/mixins.js:1 — src/react/shared/mixins.js:1 · src/svelte/shared/mixins.js:1 — these 2 files are line-for-line copies of one another — 74 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (71 identical lines × 3 files) · ×1
  • Wholesale file copy (71 identical lines × 3 files) kitchen-sink/react/src/pages/tabs-animated.jsx:1 — kitchen-sink/react/src/pages/tabs-animated.jsx:1 · kitchen-sink/react/src/pages/tabs-static.jsx:1 · kitchen-sink/react/src/pages/tabs-swipeable.jsx:1 — these 3 files are line-for-line copies of one another — 71 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block (71 lines × 2 locations) · ×1
  • Duplicated block (71 lines × 2 locations) REDACTED:1990 — REDACTED:1990 · src/core/components/picker/picker-class.js:525 — 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 (71 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (71 matched lines × 2 locations) src/core/components/color-picker/modules/sb-spectrum.js:31 — src/core/components/color-picker/modules/sb-spectrum.js:31 · src/core/components/color-picker/modules/wheel.js:61 — the two spans are one implementation copied and then locally edited — 586 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 (67 lines × 3 locations) · ×1
  • Duplicated block (67 lines × 3 locations) src/react/shared/mixins.js:65 — src/react/shared/mixins.js:65 · src/svelte/shared/mixins.js:65 · src/vue/shared/mixins.js:154 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block with local edits (65 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (65 matched lines × 2 locations) src/core/components/popover/popover-class.js:7 — src/core/components/popover/popover-class.js:7 · src/core/components/popup/popup-class.js:7 — the two spans are one implementation copied and then locally edited — 437 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 (64 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (64 matched lines × 2 locations) src/core/components/color-picker/modules/brightness-slider.js:10 — src/core/components/color-picker/modules/brightness-slider.js:10 · src/core/components/color-picker/modules/hsb-sliders.js:58 — the two spans are one implementation copied and then locally edited — 430 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 (63 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (63 matched lines × 2 locations) src/vue/components/login-screen.vue:33 — src/vue/components/login-screen.vue:33 · src/vue/components/popover.vue:55 — the two spans are one implementation copied and then locally edited — 325 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 (59 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (59 matched lines × 2 locations) src/svelte/components/view.svelte:132 — src/svelte/components/view.svelte:132 · src/vue/components/view.vue:275 — the two spans are one implementation copied and then locally edited — 360 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) kitchen-sink/react/src/pages/toast.jsx:51 — kitchen-sink/react/src/pages/toast.jsx:51 · kitchen-sink/vue/src/pages/toast.vue:84 — the two spans are one implementation copied and then locally edited — 330 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 (53 lines × 2 locations) · ×1
  • Duplicated block (53 lines × 2 locations) src/svelte/components/actions.svelte:43 — src/svelte/components/actions.svelte:43 · src/svelte/components/popover.svelte:39 — 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 (52 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (52 matched lines × 2 locations) src/react/components/list-input.jsx:244 — src/react/components/list-input.jsx:244 · src/vue/components/list-input.vue:219 — the two spans are one implementation copied and then locally edited — 303 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 (51 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (51 matched lines × 2 locations) src/svelte/components/range.svelte:7 — src/svelte/components/range.svelte:7 · src/svelte/components/stepper.svelte:7 — the two spans are one implementation copied and then locally edited — 209 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 · Wholesale file copy (50 identical lines × 2 files) · ×1
  • Wholesale file copy (50 identical lines × 2 files) src/react/shared/f7.js:2 — src/react/shared/f7.js:2 · src/vue/shared/f7.js:2 — these 2 files are line-for-line copies of one another — 50 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block (48 lines × 2 locations) · ×1
  • Duplicated block (48 lines × 2 locations) src/core/components/data-table/data-table.js:16 — src/core/components/data-table/data-table.js:16 · src/core/components/messages/messages.js:20 — 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 (47 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (47 matched lines × 2 locations) src/svelte/components/list.svelte:164 — src/svelte/components/list.svelte:164 · src/vue/components/list.vue:110 — the two spans are one implementation copied and then locally edited — 228 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 (43 lines × 2 locations) · ×1
  • Duplicated block (43 lines × 2 locations) src/vue/components/popover.vue:61 — src/vue/components/popover.vue:61 · src/vue/components/popup.vue:82 — 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 (42 lines × 2 locations) · ×1
  • Duplicated block (42 lines × 2 locations) src/core/components/popup/popup-class.js:22 — src/core/components/popup/popup-class.js:22 · src/core/components/sheet/sheet-class.js:25 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R2 · Cyclomatic Complexity · Complex function forward (cyclomatic 132, cognitive 167) · ×1
  • Complex function forward (cyclomatic 132, cognitive 167) src/core/modules/router/navigate.js:20 — forward has cyclomatic complexity 132 and cognitive complexity 167; 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 backward (cyclomatic 92, cognitive 110) · ×1
  • Complex function backward (cyclomatic 92, cognitive 110) src/core/modules/router/back.js:11 — backward has cyclomatic complexity 92 and cognitive complexity 110; 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 show (cyclomatic 84, cognitive 118) · ×1
  • Complex function show (cyclomatic 84, cognitive 118) src/core/components/tabs/tabs.js:5 — show has cyclomatic complexity 84 and cognitive complexity 118; 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 back (cyclomatic 81, cognitive 101) · ×1
  • Complex function back (cyclomatic 81, cognitive 101) src/core/modules/router/back.js:460 — back has cyclomatic complexity 81 and cognitive complexity 101; 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 handleTouchMove (cyclomatic 66, cognitive 109) · ×1
  • Complex function handleTouchMove (cyclomatic 66, cognitive 109) src/core/components/pull-to-refresh/pull-to-refresh-class.js:148 — handleTouchMove has cyclomatic complexity 66 and cognitive complexity 109; 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 handleTouchMove (cyclomatic 64, cognitive 106) · ×1
  • Complex function handleTouchMove (cyclomatic 64, cognitive 106) src/core/components/panel/swipe-panel.js:77 — handleTouchMove has cyclomatic complexity 64 and cognitive complexity 106; 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 renderToolbar (cyclomatic 64, cognitive 70) · ×1
  • Complex function renderToolbar (cyclomatic 64, cognitive 70) src/core/components/picker/picker-class.js:263 — renderToolbar has cyclomatic complexity 64 and cognitive complexity 70; 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 ListItemContent (cyclomatic 63, cognitive 67) · ×1
  • Complex function ListItemContent (cyclomatic 63, cognitive 67) src/vue/components/list-item.vue:22 — ListItemContent has cyclomatic complexity 63 and cognitive complexity 67; 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 handleTouchEnd (cyclomatic 59, cognitive 106) · ×1
  • Complex function handleTouchEnd (cyclomatic 59, cognitive 106) src/core/components/sheet/sheet-class.js:306 — handleTouchEnd has cyclomatic complexity 59 and cognitive complexity 106; 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 renderMonth (cyclomatic 56, cognitive 137) · ×1
  • Complex function renderMonth (cyclomatic 56, cognitive 137) REDACTED:1145 — renderMonth has cyclomatic complexity 56 and cognitive complexity 137; 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 open (cyclomatic 51, cognitive 66) · ×1
  • Complex function open (cyclomatic 51, cognitive 66) src/core/components/card/card.js:9 — open has cyclomatic complexity 51 and cognitive complexity 66; 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 handleTouchMove (cyclomatic 50, cognitive 82) · ×1
  • Complex function handleTouchMove (cyclomatic 50, cognitive 82) src/core/components/swipeout/swipeout.js:44 — handleTouchMove has cyclomatic complexity 50 and cognitive complexity 82; 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 handleTouchEnd (cyclomatic 50, cognitive 66) · ×1
  • Complex function handleTouchEnd (cyclomatic 50, cognitive 66) src/core/components/panel/swipe-panel.js:216 — handleTouchEnd has cyclomatic complexity 50 and cognitive complexity 66; 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 constructor (cyclomatic 48, cognitive 61) · ×1
  • Complex function constructor (cyclomatic 48, cognitive 61) src/core/components/searchbar/searchbar-class.js:9 — constructor has cyclomatic complexity 48 and cognitive complexity 61; 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 45, cognitive 47) · ×1
  • Complex function (anonymous) (cyclomatic 45, cognitive 47) src/vue/components/list-input.vue:420 — (anonymous) has cyclomatic complexity 45 and cognitive complexity 47; 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 render (cyclomatic 44, cognitive 82) · ×1
  • Complex function render (cyclomatic 44, cognitive 82) src/core/components/virtual-list/virtual-list-class.js:221 — render has cyclomatic complexity 44 and cognitive complexity 82; 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 handleClicks (cyclomatic 43, cognitive 52) · ×1
  • Complex function handleClicks (cyclomatic 43, cognitive 52) src/core/modules/clicks/clicks.js:6 — handleClicks has cyclomatic complexity 43 and cognitive complexity 52; 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 ListItemContent (cyclomatic 43, cognitive 47) · ×1
  • Complex function ListItemContent (cyclomatic 43, cognitive 47) src/react/components/list-item-content.jsx:8 — ListItemContent has cyclomatic complexity 43 and cognitive complexity 47; 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 handleTouchMove (cyclomatic 40, cognitive 57) · ×1
  • Complex function handleTouchMove (cyclomatic 40, cognitive 57) src/core/modules/router/swipe-back.js:53 — handleTouchMove has cyclomatic complexity 40 and cognitive complexity 57; 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 navigate (cyclomatic 40, cognitive 52) · ×1
  • Complex function navigate (cyclomatic 40, cognitive 52) src/core/modules/router/navigate.js:623 — navigate has cyclomatic complexity 40 and cognitive complexity 52; 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 calcDevice (cyclomatic 39, cognitive 35) · ×1
  • Complex function calcDevice (cyclomatic 39, cognitive 35) REDACTED:6 — calcDevice has cyclomatic complexity 39 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 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 ListItem (cyclomatic 38, cognitive 35) · ×1
  • Complex function ListItem (cyclomatic 38, cognitive 35) src/react/components/list-item.jsx:135 — ListItem has cyclomatic complexity 38 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 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 pageCallback (cyclomatic 38, cognitive 34) · ×1
  • Complex function pageCallback (cyclomatic 38, cognitive 34) src/core/modules/router/router-class.js:649 — pageCallback has cyclomatic complexity 38 and cognitive complexity 34; 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 load (cyclomatic 37, cognitive 36) · ×1
  • Complex function load (cyclomatic 37, cognitive 36) src/core/modules/router/navigate.js:503 — load has cyclomatic complexity 37 and cognitive complexity 36; 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 ListInput (cyclomatic 36, cognitive 38) · ×1
  • Complex function ListInput (cyclomatic 36, cognitive 38) src/react/components/list-input.jsx:84 — ListInput has cyclomatic complexity 36 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 search (cyclomatic 35, cognitive 58) · ×1
  • Complex function search (cyclomatic 35, cognitive 58) src/core/components/searchbar/searchbar-class.js:516 — search has cyclomatic complexity 35 and cognitive complexity 58; 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 handleTouchMove (cyclomatic 33, cognitive 48) · ×1
  • Complex function handleTouchMove (cyclomatic 33, cognitive 48) src/core/components/sheet/sheet-class.js:198 — handleTouchMove has cyclomatic complexity 33 and cognitive complexity 48; 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 resize (cyclomatic 33, cognitive 43) · ×1
  • Complex function resize (cyclomatic 33, cognitive 43) src/core/components/popover/popover-class.js:182 — resize has cyclomatic complexity 33 and cognitive complexity 43; 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 getInitialUrl (cyclomatic 33, cognitive 40) · ×1
  • Complex function getInitialUrl (cyclomatic 33, cognitive 40) src/core/modules/router/router-class.js:869 — getInitialUrl has cyclomatic complexity 33 and cognitive complexity 40; 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 close (cyclomatic 33, cognitive 39) · ×1
  • Complex function close (cyclomatic 33, cognitive 39) src/core/components/card/card.js:390 — close has cyclomatic complexity 33 and cognitive complexity 39; 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 handleMouseWheel (cyclomatic 32, cognitive 57) · ×1
  • Complex function handleMouseWheel (cyclomatic 32, cognitive 57) src/core/components/pull-to-refresh/pull-to-refresh-class.js:415 — handleMouseWheel has cyclomatic complexity 32 and cognitive complexity 57; 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 handleTouchEnd (cyclomatic 30, cognitive 49) · ×1
  • Complex function handleTouchEnd (cyclomatic 30, cognitive 49) src/core/components/sortable/sortable.js:159 — handleTouchEnd has cyclomatic complexity 30 and cognitive complexity 49; 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 handleLargeNavbarCollapse (cyclomatic 30, cognitive 38) · ×1
  • Complex function handleLargeNavbarCollapse (cyclomatic 30, cognitive 38) src/core/components/navbar/navbar.js:329 — handleLargeNavbarCollapse has cyclomatic complexity 30 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 handleTouchStart (cyclomatic 30, cognitive 34) · ×1
  • Complex function handleTouchStart (cyclomatic 30, cognitive 34) src/core/components/panel/swipe-panel.js:33 — handleTouchStart has cyclomatic complexity 30 and cognitive complexity 34; 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 dateInRange (cyclomatic 29, cognitive 56) · ×1
  • Complex function dateInRange (cyclomatic 29, cognitive 56) REDACTED:1073 — dateInRange has cyclomatic complexity 29 and cognitive complexity 56; 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 handleTouchEnd (cyclomatic 29, cognitive 40) · ×1
  • Complex function handleTouchEnd (cyclomatic 29, cognitive 40) src/core/components/swipeout/swipeout.js:312 — handleTouchEnd has cyclomatic complexity 29 and cognitive complexity 40; 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 handleTouchMove (cyclomatic 29, cognitive 35) · ×1
  • Complex function handleTouchMove (cyclomatic 29, cognitive 35) src/core/modules/touch/touch.js:252 — handleTouchMove has cyclomatic complexity 29 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.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 1949 lines of code REDACTED:1 — REDACTED has 1949 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 · src/core/modules/router/router-class.js · ×1
  • src/core/modules/router/router-class.js: 1048 lines of code src/core/modules/router/router-class.js:1 — src/core/modules/router/router-class.js has 1048 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 · src/svelte/components/list-item.svelte · ×1
  • src/svelte/components/list-item.svelte: 1027 lines of code src/svelte/components/list-item.svelte:1 — src/svelte/components/list-item.svelte has 1027 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 · src/core/components/smart-select/smart-select-class.js · ×1
  • src/core/components/smart-select/smart-select-class.js: 928 lines of code src/core/components/smart-select/smart-select-class.js:1 — src/core/components/smart-select/smart-select-class.js has 928 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 · src/core/components/autocomplete/autocomplete-class.js · ×1
  • src/core/components/autocomplete/autocomplete-class.js: 876 lines of code src/core/components/autocomplete/autocomplete-class.js:1 — src/core/components/autocomplete/autocomplete-class.js has 876 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 · kitchen-sink/vue/src/pages/data-table.vue · ×1
  • kitchen-sink/vue/src/pages/data-table.vue: 801 lines of code kitchen-sink/vue/src/pages/data-table.vue:1 — kitchen-sink/vue/src/pages/data-table.vue has 801 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 · src/core/modules/router/navigate.js · ×1
  • src/core/modules/router/navigate.js: 794 lines of code src/core/modules/router/navigate.js:1 — src/core/modules/router/navigate.js has 794 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 · src/core/components/color-picker/color-picker-class.js · ×1
  • src/core/components/color-picker/color-picker-class.js: 793 lines of code src/core/components/color-picker/color-picker-class.js:1 — src/core/components/color-picker/color-picker-class.js has 793 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 · src/svelte/components/list-input.svelte · ×1
  • src/svelte/components/list-input.svelte: 773 lines of code src/svelte/components/list-input.svelte:1 — src/svelte/components/list-input.svelte has 773 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 · src/core/components/photo-browser/photo-browser-class.js · ×1
  • src/core/components/photo-browser/photo-browser-class.js: 749 lines of code src/core/components/photo-browser/photo-browser-class.js:1 — src/core/components/photo-browser/photo-browser-class.js has 749 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 · src/core/components/sheet/sheet-class.js · ×1
  • src/core/components/sheet/sheet-class.js: 729 lines of code src/core/components/sheet/sheet-class.js:1 — src/core/components/sheet/sheet-class.js has 729 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 · src/core/modules/router/back.js · ×1
  • src/core/modules/router/back.js: 712 lines of code src/core/modules/router/back.js:1 — src/core/modules/router/back.js has 712 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 · kitchen-sink/react/src/pages/data-table.jsx · ×1
  • kitchen-sink/react/src/pages/data-table.jsx: 707 lines of code kitchen-sink/react/src/pages/data-table.jsx:1 — kitchen-sink/react/src/pages/data-table.jsx has 707 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 · kitchen-sink/svelte/src/pages/data-table.svelte · ×1
  • kitchen-sink/svelte/src/pages/data-table.svelte: 703 lines of code kitchen-sink/svelte/src/pages/data-table.svelte:1 — kitchen-sink/svelte/src/pages/data-table.svelte has 703 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 · kitchen-sink/svelte/src/routes.js · ×1
  • kitchen-sink/svelte/src/routes.js: 647 lines of code kitchen-sink/svelte/src/routes.js:1 — kitchen-sink/svelte/src/routes.js has 647 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 · src/svelte/components/input.svelte · ×1
  • src/svelte/components/input.svelte: 647 lines of code src/svelte/components/input.svelte:1 — src/svelte/components/input.svelte has 647 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 · src/core/components/searchbar/searchbar-class.js · ×1
  • src/core/components/searchbar/searchbar-class.js: 634 lines of code src/core/components/searchbar/searchbar-class.js:1 — src/core/components/searchbar/searchbar-class.js has 634 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 · src/core/components/swipeout/swipeout.js · ×1
  • src/core/components/swipeout/swipeout.js: 627 lines of code src/core/components/swipeout/swipeout.js:1 — src/core/components/swipeout/swipeout.js has 627 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 · src/core/components/navbar/navbar.js · ×1
  • src/core/components/navbar/navbar.js: 613 lines of code src/core/components/navbar/navbar.js:1 — src/core/components/navbar/navbar.js has 613 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 · src/core/components/range/range-class.js · ×1
  • src/core/components/range/range-class.js: 597 lines of code src/core/components/range/range-class.js:1 — src/core/components/range/range-class.js has 597 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 · src/core/components/virtual-list/virtual-list-class.js · ×1
  • src/core/components/virtual-list/virtual-list-class.js: 582 lines of code src/core/components/virtual-list/virtual-list-class.js:1 — src/core/components/virtual-list/virtual-list-class.js has 582 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 · src/core/shared/utils.js · ×1
  • src/core/shared/utils.js: 572 lines of code src/core/shared/utils.js:1 — src/core/shared/utils.js has 572 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 · src/core/components/picker/picker-class.js · ×1
  • src/core/components/picker/picker-class.js: 559 lines of code src/core/components/picker/picker-class.js:1 — src/core/components/picker/picker-class.js has 559 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 · src/vue/components/list-item.vue · ×1
  • src/vue/components/list-item.vue: 559 lines of code src/vue/components/list-item.vue:1 — src/vue/components/list-item.vue has 559 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 · src/core/components/card/card.js · ×1
  • src/core/components/card/card.js: 547 lines of code src/core/components/card/card.js:1 — src/core/components/card/card.js has 547 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 · src/core/components/pull-to-refresh/pull-to-refresh-class.js · ×1
  • src/core/components/pull-to-refresh/pull-to-refresh-class.js: 547 lines of code src/core/components/pull-to-refresh/pull-to-refresh-class.js:1 — src/core/components/pull-to-refresh/pull-to-refresh-class.js has 547 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 · kitchen-sink/react/src/pages/color-picker.jsx · ×1
  • kitchen-sink/react/src/pages/color-picker.jsx: 545 lines of code kitchen-sink/react/src/pages/color-picker.jsx:1 — kitchen-sink/react/src/pages/color-picker.jsx has 545 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 · kitchen-sink/vue/src/pages/color-picker.vue · ×1
  • kitchen-sink/vue/src/pages/color-picker.vue: 540 lines of code kitchen-sink/vue/src/pages/color-picker.vue:1 — kitchen-sink/vue/src/pages/color-picker.vue has 540 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 · src/core/components/text-editor/text-editor-class.js · ×1
  • src/core/components/text-editor/text-editor-class.js: 522 lines of code src/core/components/text-editor/text-editor-class.js:1 — src/core/components/text-editor/text-editor-class.js has 522 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 · src/core/components/panel/panel-class.js · ×1
  • src/core/components/panel/panel-class.js: 516 lines of code src/core/components/panel/panel-class.js:1 — src/core/components/panel/panel-class.js has 516 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 · src/react/components/list-input.jsx · ×1
  • src/react/components/list-input.jsx: 515 lines of code src/react/components/list-input.jsx:1 — src/react/components/list-input.jsx has 515 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 · kitchen-sink/vue/src/pages/autocomplete.vue · ×1
  • kitchen-sink/vue/src/pages/autocomplete.vue: 504 lines of code kitchen-sink/vue/src/pages/autocomplete.vue:1 — kitchen-sink/vue/src/pages/autocomplete.vue has 504 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 · src/vue/components/list-input.vue · ×1
  • src/vue/components/list-input.vue: 502 lines of code src/vue/components/list-input.vue:1 — src/vue/components/list-input.vue has 502 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 · src/react/components/input.jsx · ×1
  • src/react/components/input.jsx: 494 lines of code src/react/components/input.jsx:1 — src/react/components/input.jsx has 494 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 · src/core/components/messages/messages-class.js · ×1
  • src/core/components/messages/messages-class.js: 484 lines of code src/core/components/messages/messages-class.js:1 — src/core/components/messages/messages-class.js has 484 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 · src/core/modules/touch/touch.js · ×1
  • src/core/modules/touch/touch.js: 479 lines of code src/core/modules/touch/touch.js:1 — src/core/modules/touch/touch.js has 479 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 · src/vue/components/input.vue · ×1
  • src/vue/components/input.vue: 462 lines of code src/vue/components/input.vue:1 — src/vue/components/input.vue has 462 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 · kitchen-sink/react/src/pages/autocomplete.jsx · ×1
  • kitchen-sink/react/src/pages/autocomplete.jsx: 440 lines of code kitchen-sink/react/src/pages/autocomplete.jsx:1 — kitchen-sink/react/src/pages/autocomplete.jsx has 440 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 · kitchen-sink/svelte/src/pages/autocomplete.svelte · ×1
  • kitchen-sink/svelte/src/pages/autocomplete.svelte: 435 lines of code kitchen-sink/svelte/src/pages/autocomplete.svelte:1 — kitchen-sink/svelte/src/pages/autocomplete.svelte 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 · src/core/modules/component/component-class.js · ×1
  • src/core/modules/component/component-class.js: 427 lines of code src/core/modules/component/component-class.js:1 — src/core/modules/component/component-class.js has 427 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R4 · Test Coverage · Test Coverage · ×1
  • Test Coverage — 0% of 742 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
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.
R7 · Dead Code · Dead file (~2090 LoC) · ×1
  • Dead file (~2090 LoC) REDACTED — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/calendar/calendar.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~1009 LoC) · ×1
  • Dead file (~1009 LoC) src/core/components/smart-select/smart-select-class.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/smart-select/smart-select.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~959 LoC) · ×1
  • Dead file (~959 LoC) src/core/components/autocomplete/autocomplete-class.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/autocomplete/autocomplete.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~873 LoC) · ×1
  • Dead file (~873 LoC) src/core/components/color-picker/color-picker-class.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/color-picker/color-picker.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~820 LoC) · ×1
  • Dead file (~820 LoC) src/core/components/photo-browser/photo-browser-class.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/photo-browser/photo-browser.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~659 LoC) · ×1
  • Dead file (~659 LoC) src/core/components/navbar/navbar.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~654 LoC) · ×1
  • Dead file (~654 LoC) src/core/components/swipeout/swipeout.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~642 LoC) · ×1
  • Dead file (~642 LoC) src/core/components/virtual-list/virtual-list-class.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/virtual-list/virtual-list.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~620 LoC) · ×1
  • Dead file (~620 LoC) src/core/components/picker/picker-class.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/picker/picker.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~529 LoC) · ×1
  • Dead file (~529 LoC) src/core/components/messages/messages-class.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/messages/messages.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~514 LoC) · ×1
  • Dead file (~514 LoC) src/core/modules/touch/touch.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~466 LoC) · ×1
  • Dead file (~466 LoC) src/core/components/area-chart/area-chart-class.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/area-chart/area-chart.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~452 LoC) · ×1
  • Dead file (~452 LoC) src/core/components/stepper/stepper-class.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/stepper/stepper.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~398 LoC) · ×1
  • Dead file (~398 LoC) src/core/components/messagebar/messagebar-class.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/messagebar/messagebar.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~359 LoC) · ×1
  • Dead file (~359 LoC) src/core/components/list-index/list-index-class.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/list-index/list-index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~350 LoC) · ×1
  • Dead file (~350 LoC) src/core/components/tooltip/tooltip-class.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/tooltip/tooltip.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~334 LoC) · ×1
  • Dead file (~334 LoC) src/core/components/gauge/gauge-class.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/gauge/gauge.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~331 LoC) · ×1
  • Dead file (~331 LoC) src/core/components/form/form.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~312 LoC) · ×1
  • Dead file (~312 LoC) src/core/components/sortable/sortable.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~257 LoC) · ×1
  • Dead file (~257 LoC) src/core/components/tabs/tabs.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~251 LoC) · ×1
  • Dead file (~251 LoC) src/core/components/pie-chart/pie-chart-class.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/pie-chart/pie-chart.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~249 LoC) · ×1
  • Dead file (~249 LoC) src/core/components/dialog/dialog.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~247 LoC) · ×1
  • Dead file (~247 LoC) src/core/components/toolbar/toolbar.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~235 LoC) · ×1
  • Dead file (~235 LoC) src/core/components/dialog/dialog-class.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/dialog/dialog.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~224 LoC) · ×1
  • Dead file (~224 LoC) REDACTED — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/notification/notification.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~220 LoC) · ×1
  • Dead file (~220 LoC) src/core/components/color-picker/modules/rgb-sliders.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/color-picker/color-picker-class.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~218 LoC) · ×1
  • Dead file (~218 LoC) src/core/components/color-picker/modules/hsb-sliders.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/color-picker/color-picker-class.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~203 LoC) · ×1
  • Dead file (~203 LoC) src/core/components/statusbar/statusbar.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~198 LoC) · ×1
  • Dead file (~198 LoC) src/core/components/fab/fab.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~189 LoC) · ×1
  • Dead file (~189 LoC) src/core/components/color-picker/color-picker.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~187 LoC) · ×1
  • Dead file (~187 LoC) src/core/components/color-picker/modules/wheel.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/color-picker/color-picker-class.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~169 LoC) · ×1
  • Dead file (~169 LoC) src/core/components/progressbar/progressbar.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~168 LoC) · ×1
  • Dead file (~168 LoC) src/core/components/swiper/swiper.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~159 LoC) · ×1
  • Dead file (~159 LoC) src/core/components/data-table/data-table-class.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/data-table/data-table.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~143 LoC) · ×1
  • Dead file (~143 LoC) src/core/components/picker/picker-column.js — no import path from any entry point (308 application, 98 tooling, 0 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/core/components/picker/picker-class.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R8 · Dependency Hygiene · Unused dependency 'clean-css' · ×1
  • Unused dependency 'clean-css' — Declared in the root 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 'prop-types' · ×1
  • Unused dependency 'prop-types' — Declared in the root 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.
Minor — 123 finding(s)
GD1 · Unfinished & placeholder code · Placeholder literal left in code · ×40
  • Placeholder literal left in code kitchen-sink/react/src/pages/accordion.jsx:18 — A placeholder string ("Lorem Ipsum") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/accordion.jsx:21 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/accordion.jsx:44 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/accordion.jsx:58 — A placeholder string ("Lorem Ipsum") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/accordion.jsx:61 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/accordion.jsx:84 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/cards-expandable.jsx:128 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/cards-expandable.jsx:182 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/cards.jsx:35 — A placeholder string ("Another card. Lorem ipsum dolor sit amet…") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/cards.jsx:50 — A placeholder string ("Another card. Lorem ipsum dolor sit amet…") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/cards.jsx:76 — A placeholder string ("Another card. Lorem ipsum dolor sit amet…") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/checkbox.jsx:90 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/checkbox.jsx:98 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/checkbox.jsx:106 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/checkbox.jsx:114 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/content-block.jsx:33 — A placeholder string ("Lorem ipsum dolor sit amet consectetur a…") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/fab-morph.jsx:76 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/fab-morph.jsx:103 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/fab.jsx:64 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/fab.jsx:91 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/list.jsx:203 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/list.jsx:217 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/list.jsx:231 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/list.jsx:248 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
  • Placeholder literal left in code kitchen-sink/react/src/pages/list.jsx:255 — A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
  • + 15 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×40
  • Duplicated predicate src/react/components/input.jsx:270 — `!(validateOnBlur || validateOnBlur === '') && (validate || validate === '') && ((typeof value !== 'undefined' && value !== null && value !==…` appears character-identically in 2 files — src/react/components/input.jsx, src/react/components/list-input.jsx. 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 src/react/components/input.jsx:199 — `!(validateOnBlur || validateOnBlur === '') && (validate || validate === '') && inputElRef.current` appears character-identically in 2 files — src/react/components/input.jsx, src/react/components/list-input.jsx. 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 src/core/components/actions/actions-class.js:209 — `!device.desktop && device.cordova && ((window.Keyboard && window.Keyboard.isVisible) || (window.cordova.plugins && window.cordova.plugins.Ke…` appears character-identically in 4 files — src/core/components/actions/actions-class.js, src/core/components/popover/popover-class.js, src/core/components/popup/popup-class.js, src/core/components/sheet/sheet-class.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 src/react/shared/utils.js:109 — `!events || !events.trim().length || typeof events !== 'string'` appears character-identically in 2 files — src/react/shared/utils.js, src/svelte/shared/utils.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 REDACTED:1854 — `!inline && $inputEl && $inputEl.length && app.theme === 'md'` appears character-identically in 3 files — REDACTED, src/core/components/color-picker/color-picker-class.js, src/core/components/picker/picker-class.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 src/core/shared/utils.js:248 — `!isObject(to[nextKey]) && isObject(nextSource[nextKey])` appears character-identically in 4 files — src/core/shared/utils.js, src/react/shared/utils.js, src/svelte/shared/utils.js, src/vue/shared/utils.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 src/core/modules/router/back.js:80 — `!masterPageEl && $pagesInView[i].classList.contains('page-master')` appears character-identically in 2 files — src/core/modules/router/back.js, src/core/modules/router/navigate.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 src/core/components/area-chart/area-chart-class.js:55 — `!maxAxisLabels || axisLabels.length <= maxAxisLabels` appears character-identically in 2 files — src/core/components/area-chart/area-chart-class.js, src/react/components/area-chart.jsx. 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 src/core/components/range/range-class.js:114 — `!params[paramName] && $inputEl.attr(paramName)` appears character-identically in 2 files — src/core/components/range/range-class.js, src/core/components/stepper/stepper-class.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 src/core/modules/router/back.js:386 — `!router.allowPageChange && !ignorePageChange` appears character-identically in 2 files — src/core/modules/router/back.js, src/core/modules/router/navigate.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 REDACTED:394 — `$inputEl.parents('.view').length && $inputEl.parents('.view')[0].f7View` appears character-identically in 3 files — REDACTED, src/core/components/color-picker/color-picker-class.js, src/core/components/picker/picker-class.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 src/core/components/navbar/navbar.js:642 — `$pageContentEl && $pageContentEl.length > 0` appears character-identically in 2 files — src/core/components/navbar/navbar.js, src/core/components/sheet/sheet-class.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 src/react/components/sheet.jsx:125 — `'animate' in props && typeof animate !== 'undefined'` appears character-identically in 4 files — src/react/components/sheet.jsx, src/react/shared/mixins.js, src/svelte/shared/mixins.js, src/vue/shared/mixins.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 src/react/shared/mixins.js:37 — `'reloadDetail' in props && typeof reloadDetail !== 'undefined'` appears character-identically in 3 files — src/react/shared/mixins.js, src/svelte/shared/mixins.js, src/vue/shared/mixins.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 src/react/shared/components-router.js:31 — `(data.el && data.el === routerEl) || (data.routerId && data.routerId === routerId)` appears character-identically in 3 files — src/react/shared/components-router.js, src/svelte/shared/components-router.js, src/vue/shared/components-router.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 src/react/components/input.jsx:367 — `(errorMessage && errorMessageForce) || inputInvalid` appears character-identically in 2 files — src/react/components/input.jsx, src/react/components/list-input.jsx. 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 src/react/shared/mixins.js:108 — `(isStringProp(actionsOpen) && actionsOpen) || (isStringProp(actionsClose) && actionsClose) || undefined` appears character-identically in 3 files — src/react/shared/mixins.js, src/svelte/shared/mixins.js, src/vue/shared/mixins.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 src/react/shared/mixins.js:129 — `(isStringProp(cardOpen) && cardOpen) || (isStringProp(cardClose) && cardClose) || undefined` appears character-identically in 3 files — src/react/shared/mixins.js, src/svelte/shared/mixins.js, src/vue/shared/mixins.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 src/react/shared/mixins.js:120 — `(isStringProp(loginScreenOpen) && loginScreenOpen) || (isStringProp(loginScreenClose) && loginScreenClose) || undefined` appears character-identically in 3 files — src/react/shared/mixins.js, src/svelte/shared/mixins.js, src/vue/shared/mixins.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 src/react/shared/mixins.js:99 — `(isStringProp(panelOpen) && panelOpen) || (isStringProp(panelClose) && panelClose) || (isStringProp(panelToggle) && panelToggle) || undefine…` appears character-identically in 3 files — src/react/shared/mixins.js, src/svelte/shared/mixins.js, src/vue/shared/mixins.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 src/react/shared/mixins.js:112 — `(isStringProp(popoverOpen) && popoverOpen) || (isStringProp(popoverClose) && popoverClose) || undefined` appears character-identically in 3 files — src/react/shared/mixins.js, src/svelte/shared/mixins.js, src/vue/shared/mixins.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 src/react/shared/mixins.js:104 — `(isStringProp(popupOpen) && popupOpen) || (isStringProp(popupClose) && popupClose) || undefined` appears character-identically in 3 files — src/react/shared/mixins.js, src/svelte/shared/mixins.js, src/vue/shared/mixins.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 src/react/shared/mixins.js:93 — `(isStringProp(searchbarEnable) && searchbarEnable) || (isStringProp(searchbarDisable) && searchbarDisable) || (isStringProp(searchbarClear) …` appears character-identically in 3 files — src/react/shared/mixins.js, src/svelte/shared/mixins.js, src/vue/shared/mixins.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 src/react/shared/mixins.js:116 — `(isStringProp(sheetOpen) && sheetOpen) || (isStringProp(sheetClose) && sheetClose) || undefined` appears character-identically in 3 files — src/react/shared/mixins.js, src/svelte/shared/mixins.js, src/vue/shared/mixins.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 src/react/shared/mixins.js:124 — `(isStringProp(sortableEnable) && sortableEnable) || (isStringProp(sortableDisable) && sortableDisable) || (isStringProp(sortableToggle) && s…` appears character-identically in 3 files — src/react/shared/mixins.js, src/svelte/shared/mixins.js, src/vue/shared/mixins.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.
D24 · Comment Value · redundant comment · ×21
  • redundant comment scripts/build-react.js:81 — "remove dts-comments" repeats the code it sits on: 3 of its 3 words (remove, dts, comments) are already in `removeDtsComments(buildPath);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/core/components/autocomplete/autocomplete-class.js:749 — "Attach page events" repeats the code it sits on: 3 of its 3 words (attach, page, events) are already in `ac.attachPageEvents();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:1840 — "Update current month and year" repeats the code it sits on: 4 of its 4 words (update, current, month, year) are already in `calendar.updateCurrentMonthYear();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/core/components/form/form.js:16 — "Store form data in app.formsData" repeats the code it sits on: 4 of its 5 words (form, data, app, forms) are already in `app.form.data[`form-${formId}`] = data;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/core/components/form/form.js:50 — "Delete form data from app.formsData" repeats the code it sits on: 4 of its 5 words (form, data, app, forms) are already in `if (app.form.data[`form-${formId}`])`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/core/components/input/input.js:260 — "Check Empty State" repeats the code it sits on: 3 of its 3 words (check, empty, state) are already in `app.input.checkEmptyState($inputEl);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/core/components/navbar/navbar.js:559 — "Need Collapse On Scroll" repeats the code it sits on: 3 of its 3 words (need, collapse, scroll) are already in `let needCollapseOnScrollHandler;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/core/components/navbar/navbar.js:569 — "Need transparent on scroll" repeats the code it sits on: 3 of its 3 words (need, transparent, scroll) are already in `let needTransparentOnScroll;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/core/components/navbar/navbar.js:575 — "Need Hide On Scroll" repeats the code it sits on: 3 of its 3 words (need, hide, scroll) are already in `let needHideOnScrollHandler;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/core/components/smart-select/smart-select-class.js:732 — "Check for max length" repeats the code it sits on: 3 of its 3 words (check, max, length) are already in `if (ss.maxLength)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/core/components/smart-select/smart-select-class.js:747 — "Attach input events" repeats the code it sits on: 3 of its 3 words (attach, input, events) are already in `ss.attachInputsEvents();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/core/components/view/view-class.js:33 — "Default View params" repeats the code it sits on: 3 of its 3 words (default, view, params) are already in `view.params = extend({ el }, defaults, app.params.view, viewParams);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/core/components/virtual-list/virtual-list-class.js:329 — "Append item to fragment" repeats the code it sits on: 3 of its 3 words (append, item, fragment) are already in `vl.fragment.appendChild(itemEl);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/core/modules/router/back.js:45 — 5 comments in this file only repeat the code they sit on (lines 45, 55, 307, 330, 338), for example "Remove theme elements". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/core/modules/router/modal.js:52 — "Remove theme elements" repeats the code it sits on: 3 of its 3 words (remove, theme, elements) are already in `router.removeThemeElements(modal.el);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/core/modules/router/modal.js:136 — "Remove theme elements" repeats the code it sits on: 3 of its 3 words (remove, theme, elements) are already in `router.removeThemeElements(modal.el);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/core/modules/router/navigate.js:104 — "Remove theme elements" repeats the code it sits on: 3 of its 3 words (remove, theme, elements) are already in `router.removeThemeElements($newPage);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/core/modules/router/navigate.js:396 — "Check master detail" repeats the code it sits on: 3 of its 3 words (check, master, detail) are already in `if (masterDetailEnabled)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/core/modules/router/router-class.js:594 — "Remove theme elements" repeats the code it sits on: 3 of its 3 words (remove, theme, elements) are already in `removeThemeElements(el)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/core/modules/router/tab.js:81 — "Tab Content Loaded" repeats the code it sits on: 3 of its 3 words (tab, content, loaded) are already in `function onTabLoaded(contentEl)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/core/modules/router/tab.js:83 — "Remove theme elements" repeats the code it sits on: 3 of its 3 words (remove, theme, elements) are already in `router.removeThemeElements($newTabEl);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D12 · Dependency Hygiene · Deprecated · ×6
  • Deprecated: fsevents REDACTED:7978 — fsevents 1.2.13 is resolved in REDACTED and is marked deprecated by its publisher: "Upgrade to fsevents v2 to mitigate potential security issues". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: resolve-url REDACTED:13247 — resolve-url 0.2.1 is resolved in REDACTED and is marked deprecated by its publisher: "https://github.com/lydell/resolve-url#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: source-map-resolve REDACTED:14217 — source-map-resolve 0.5.3 is resolved in REDACTED and is marked deprecated by its publisher: "See https://github.com/lydell/source-map-resolve#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: source-map-url REDACTED:14241 — source-map-url 0.4.1 is resolved in REDACTED and is marked deprecated by its publisher: "See https://github.com/lydell/source-map-url#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: urix REDACTED:15600 — urix 0.1.0 is resolved in REDACTED and is marked deprecated by its publisher: "Please see https://github.com/lydell/urix#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: uuid REDACTED:15631 — uuid 3.4.0 is resolved in REDACTED and is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
D30 · Dependency Vulnerabilities · Low CVE · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
IC1 · Incompleteness & stubs · Blanket warning suppression · ×4
  • Blanket warning suppression kitchen-sink/vue/src/app.js:12 — A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
  • Blanket warning suppression src/core/components/swiper/swiper.js:11 — A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
  • Blanket warning suppression src/core/shared/material-colors.js:11 — A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
  • Blanket warning suppression src/core/shared/utils.js:548 — A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
D12 · Dependency Hygiene · Outdated (npm) · ×1
  • Outdated (npm): path-to-regexp package.json:71 — path-to-regexp is pinned at 6.3.0; registry.npmjs.org publishes 9.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
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.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation package.json:68 — `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
Minor — 1 finding(s)
D12 · Dependency Hygiene · Outdated (npm) · ×1
  • Outdated (npm): swiper — swiper is pinned at 12.2.0; registry.npmjs.org publishes 14.4.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.

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-dccc3523f8564a2cbf9556da5c4b15bc/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-dccc3523f8564a2cbf9556da5c4b15bc/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 --exclude .nova --exclude build --exclude kitchen-sink/core/css --exclude kitchen-sink/core/js --exclude kitchen-sink/core/pages --exclude src/material-color-utilities .7artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .42artifacts/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—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress 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 01a1dd64-2d89-7058-9a0b-b89ea1107bd2 · 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