Public report of carbon-design-system/carbon, published 30 October 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 reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). 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, 30 October 2026, 05:02 UTC · Survey ID cd_1b91cdc3fa7442fbabe8e1b19f8df1ac
carbon-design-system/carbon
Measured 30 October 2026, 04:40 UTC, at code version 03dfc3a
Regression: 1 dimension fell since the last survey
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
CAI scoreAt riskDown 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: 203,495 lines of product code in 39 projects, tests not counted · Estimated rebuild effort: about 2.2 person-years · Weakest lens: Production Readiness, 42
Findings by how serious they are
149 critical1195 serious284 minor
7 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks 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
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
30 October 2026, 04:40 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 Watchdog. It is open to any tool that
implements it, and today Watchdog 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. Watchdog works 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 ▸
87of 87 dimensions measured by tools.
1539of 1628 findings point to an exact file and line, so you can open each one in the code. The other 89 concern the repository as a whole, such as missing documentation.
87dimensions across 7 lenses, read from 203,495 lines of product code in 39 projects.
carbon-design-system/carbon is rated At risk because critical security findings are open. Its score is held back in part because it has uses of packages that aren't listed. It scores 49 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 42, is the weakest lens and counts most in the score. The best first steps are documenting the recovery plan and tidying the declared packages, each worth about 5 points. Raising Production Readiness to 70 would lift the score to about 55.
Twenty-nine known security holes in the packages the code depends on can be used by attackers. Sixteen secrets can leak from the build pipeline, and ten pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Updating the vulnerable packages, limiting each secret to its own step and passing outside input through environment variables would close these risks. Pinning each tool to an exact version would fix the nine pipeline tools referenced by a changeable name, and the four passwords or keys in the code's history need replacing, with the old ones switched off. The 18 labels or groups of fields with no name need connecting to their fields or naming.
The product code is 203,495 lines, about €320,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 forThe 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.
If Production Readiness rose from 42 to 70, the lowest score rated Strong, the score would rise from 49 to about 55.
Code composition: what the lines of code are
Product code 59%Tests 41%
New since the last survey: 270 findings
These 270 critical or serious findings weren't in the previous survey, on 16 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
God Classes · FunctionTooLong: CardActions.CardActions packages/react/src/components/Card/CardActions.tsx
Test Quality · Skipped test: Should render the expando packages/web-components/tests/spec/code-snippet_spec.ts
Test Quality · Skipped test: Should change the button text by expanding/collapsing packages/web-components/tests/spec/code-snippet_spec.ts
Test Quality · Skipped test: Should highlight the item user types packages/web-components/tests/spec/combo-box_spec.ts
Test Quality · Skipped test: Should support selecting an item after typing packages/web-components/tests/spec/combo-box_spec.ts
Test Quality · Skipped test: should add/remove "selected" attribute packages/web-components/tests/spec/content-switcher_spec.ts
Test Quality · Skipped test: should provide a way to switch item with a value packages/web-components/tests/spec/content-switcher_spec.ts
Test Quality · Skipped test: should provide a way to cancel switching item packages/web-components/tests/spec/content-switcher_spec.ts
Test Quality · Skipped test: should add/remove "hide-divider" attribute packages/web-components/tests/spec/content-switcher_spec.ts
Test Quality · Skipped test: Should show the tooltip for 2 seconds by default packages/web-components/tests/spec/copy-button_spec.ts
Test Quality · Skipped test: Should support changing the duration packages/web-components/tests/spec/copy-button_spec.ts
Test Quality · Skipped test: should support setting zebra stripe to rows packages/web-components/tests/spec/data-table_spec.ts
Test Quality · Skipped test: should fire cds-table-row-change-selection event upon selecting packages/web-components/tests/spec/data-table_spec.ts
Test Quality · Skipped test: should fire cds-table-row-change-selection event upon unselecting packages/web-components/tests/spec/data-table_spec.ts
Test Quality · Skipped test: should support preventing table row selection from being toggled upon user gesture packages/web-components/tests/spec/data-table_spec.ts
Test Quality · Skipped test: should expand and collapse packages/web-components/tests/spec/data-table_spec.ts
Test Quality · Skipped test: should fire cds-table-row-expando-beingtoggled/cds-table-row-expando-toggled events upon expanding packages/web-components/tests/spec/data-table_spec.ts
Test Quality · Skipped test: should fire cds-table-row-expando-beingtoggled/cds-table-row-expando-toggled events upon collapsing packages/web-components/tests/spec/data-table_spec.ts
Test Quality · Skipped test: should support preventing table row from being toggled upon user gesture packages/web-components/tests/spec/data-table_spec.ts
Test Quality · Skipped test: Should not instantiate Flatpickr packages/web-components/tests/spec/date-picker_spec.ts
Test Quality · Skipped test: Should support opening calendar dropdown by clicking on calendar icon for the start date packages/web-components/tests/spec/date-picker_spec.ts
Test Quality · Skipped test: Should support opening calendar dropdown by clicking on calendar icon for the end date packages/web-components/tests/spec/date-picker_spec.ts
Test Quality · Skipped test: should support checking if required value exists packages/web-components/tests/spec/date-picker_spec.ts
Test Quality · Skipped test: should treat non-empty custom validity message as invalid packages/web-components/tests/spec/date-picker_spec.ts
Test Quality · Skipped test: Should respond to `formdata` event packages/web-components/tests/spec/date-picker_spec.ts
Test Quality · Skipped test: Should not respond to `formdata` event if disabled packages/web-components/tests/spec/date-picker_spec.ts
Test Quality · Skipped test: Should respond to `formdata` event in range mode packages/web-components/tests/spec/date-picker_spec.ts
Test Quality · Skipped test: should add/remove "selected" modifier class packages/web-components/tests/spec/dropdown_spec.ts
Test Quality · Skipped test: should update text packages/web-components/tests/spec/dropdown_spec.ts
Test Quality · Skipped test: should update value packages/web-components/tests/spec/dropdown_spec.ts
Test Quality · Skipped test: should provide a way to switch item with a value packages/web-components/tests/spec/dropdown_spec.ts
Test Quality · Skipped test: should provide a way to cancel switching item packages/web-components/tests/spec/dropdown_spec.ts
Test Quality · Skipped test: should render with minimum attributes packages/web-components/tests/spec/file-uploader_spec.ts
Test Quality · Skipped test: should render with minimum attributes packages/web-components/tests/spec/file-uploader_spec.ts
Test Quality · Skipped test: should render with various attributes packages/web-components/tests/spec/file-uploader_spec.ts
Test Quality · Skipped test: Should handle drag-over packages/web-components/tests/spec/file-uploader_spec.ts
Test Quality · Skipped test: Should handle drag-leave packages/web-components/tests/spec/file-uploader_spec.ts
Test Quality · Skipped test: Should handle drop packages/web-components/tests/spec/file-uploader_spec.ts
Test Quality · Skipped test: Should handle file upload link packages/web-components/tests/spec/file-uploader_spec.ts
Test Quality · Skipped test: Should handle filtering by file extension packages/web-components/tests/spec/file-uploader_spec.ts
Test Quality · Skipped test: should render uploaded state with various attributes packages/web-components/tests/spec/file-uploader_spec.ts
Test Quality · Skipped test: should choose the right template for overlay type packages/web-components/tests/spec/loading_spec.ts
Test Quality · Skipped test: should deactivate when inactive attribute is set packages/web-components/tests/spec/loading_spec.ts
Test Quality · Skipped test: should add/remove "selected" modifier class packages/web-components/tests/spec/multi-select_spec.ts
Test Quality · Skipped test: should update selection count packages/web-components/tests/spec/multi-select_spec.ts
Test Quality · Skipped test: should update value packages/web-components/tests/spec/multi-select_spec.ts
Test Quality · Skipped test: should support selecting an item with space key packages/web-components/tests/spec/multi-select_spec.ts
Test Quality · Skipped test: should support selecting an item with enter key packages/web-components/tests/spec/multi-select_spec.ts
Test Quality · Skipped test: should provide a way to switch item with a value packages/web-components/tests/spec/multi-select_spec.ts
Test Quality · Skipped test: should provide a way to cancel switching item packages/web-components/tests/spec/multi-select_spec.ts
Test Quality · Skipped test: should support clicking X button for clearing selection packages/web-components/tests/spec/multi-select_spec.ts
Test Quality · Skipped test: should support space key on X button for clearing selection packages/web-components/tests/spec/multi-select_spec.ts
Test Quality · Skipped test: should support enter key on X button for clearing selection packages/web-components/tests/spec/multi-select_spec.ts
Test Quality · Skipped test: should support arrow key to move focus out of the close button packages/web-components/tests/spec/multi-select_spec.ts
Test Quality · Skipped test: Should respond to `formdata` event packages/web-components/tests/spec/number-input_spec.ts
Test Quality · Skipped test: should support checking if required value exists packages/web-components/tests/spec/number-input_spec.ts
Test Quality · Skipped test: should warn if a value less than the min packages/web-components/tests/spec/number-input_spec.ts
Test Quality · Skipped test: should warn if a value is greater than the max packages/web-components/tests/spec/number-input_spec.ts
Test Quality · Skipped test: should focus on the menu body when the menu is opened by clicking on the trigger button packages/web-components/tests/spec/overflow-menu_spec.ts
Test Quality · Skipped test: should focus on the menu body when the menu is opened by space key on the trigger button packages/web-components/tests/spec/overflow-menu_spec.ts
Test Quality · Skipped test: should focus on the menu body when the menu is opened by enter key on the trigger button packages/web-components/tests/spec/overflow-menu_spec.ts
Test Quality · Skipped test: Should render with minimum attributes packages/web-components/tests/spec/tooltip_spec.ts
Test Quality · Skipped test: Should render with various attributes packages/web-components/tests/spec/tooltip_spec.ts
Test Quality · Skipped test: should collapse upon hitting ESC key packages/web-components/tests/spec/ui-shell_spec.ts
Test Quality · Skipped test: should let child side nav menu collapse if this side nav is collapsed packages/web-components/tests/spec/ui-shell_spec.ts
Test Quality · Skipped test: should support a custom class on the element with a link role packages/web-components/src/components/link/__tests__/link-test.js
Test Quality · Skipped test: should add rel="noopener" automatically if target="_blank" packages/web-components/src/components/link/__tests__/link-test.js
Test Quality · Skipped test: should use the `as` attribute to change the element in <cds-section> packages/web-components/src/components/heading/__tests__/heading-test.js
Test Quality · Skipped test: should apply field focus style when focusing the select packages/web-components/src/components/fluid-select/__tests__/fluid-select-test.js
Test Quality · Skipped test: restores focus to the end input after selecting a range end date packages/web-components/src/components/date-picker/next/__tests__/date-picker-range-test.js
Test Quality · Skipped test: @avt-default-state e2e/components/UserAvatar/UserAvatar-test.avt.e2e.js
Test Quality · Skipped test: @avt-focus-state e2e/components/UserAvatar/UserAvatar-test.avt.e2e.js
Test Quality · Skipped test: @avt-hover-state e2e/components/UserAvatar/UserAvatar-test.avt.e2e.js
Test Quality · Skipped test: @avt-default-state e2e/components/Tearsheet/Tearsheet-test.avt.e2e.js
Test Quality · Skipped test: @avt-open-and-close e2e/components/Tearsheet/Tearsheet-test.avt.e2e.js
Test Quality · Skipped test: @avt-default-state-focus-trap e2e/components/Tearsheet/Tearsheet-test.avt.e2e.js
Test Quality · Skipped test: @avt-stacking e2e/components/Tearsheet/Tearsheet-test.avt.e2e.js
Test Quality · Skipped test: @avt-narrow e2e/components/Tearsheet/Tearsheet-test.avt.e2e.js
Test Quality · Skipped test: @avt-with-influencer e2e/components/Tearsheet/Tearsheet-test.avt.e2e.js
Test Quality · Skipped test: @avt-default-state e2e/components/TagOverflow/TagOverflow-test.avt.e2e.js
Test Quality · Skipped test: @avt-default-state e2e/components/SidePanel/SidePanel-test.avt.e2e.js
Test Quality · Skipped test: @avt-multi-step e2e/components/SidePanel/SidePanel-test.avt.e2e.js
Test Quality · Skipped test: @avt-action-toolbar e2e/components/SidePanel/SidePanel-test.avt.e2e.js
Test Quality · Skipped test: @avt-focus-trap e2e/components/SidePanel/SidePanel-test.avt.e2e.js
Test Quality · Skipped test: @avt-default-state e2e/components/ScrollGradient/ScrollGradient-test.avt.e2e.js
Test Quality · Skipped test: @avt-default-state content e2e/components/PageHeader/PageHeader-test.avt.e2e.js
Test Quality · Skipped test: @avt-default-state e2e/components/NotificationsPanel/NotificationsPanel-test.avt.e2e.js
Test Quality · Skipped test: @avt-notification-panel-focus-trap e2e/components/NotificationsPanel/NotificationsPanel-test.avt.e2e.js
Test Quality · Skipped test: @avt-advanced-states open filterable multiselect e2e/components/MultiSelect/MultiSelect-test.avt.e2e.js
Test Quality · Skipped test: @avt-advanced-states open multiselect e2e/components/MultiSelect/MultiSelect-test.avt.e2e.js
Test Quality · Skipped test: @avt-full-screen-state e2e/components/InterstitialScreen/InterstitialScreen-test.avt.e2e.js
Test Quality · Skipped test: @avt-single-step-keyboard-navigation e2e/components/InterstitialScreen/InterstitialScreen-test.avt.e2e.js
Test Quality · Skipped test: @avt-multi-step-keyboard-navigation e2e/components/InterstitialScreen/InterstitialScreen-test.avt.e2e.js
Test Quality · Skipped test: @avt-open-and-close-states e2e/components/InterstitialScreen/InterstitialScreen-test.avt.e2e.js
Test Quality · Skipped test: @avt-determinate-progress-indicator e2e/components/InterstitialScreen/InterstitialScreen-test.avt.e2e.js
Test Quality · Skipped test: @avt-indeterminate-single-step e2e/components/InterstitialScreen/InterstitialScreen-test.avt.e2e.js
Watchdog compares 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: 2068 findings
These 2068 critical or serious findings were in the previous survey, on 16 October 2026, and are gone from this one. The first 100 are listed here.
€110,000 to €530,000, for 1,755 to 5,569 hours of work, about 2.2 person-years for 1 to 5 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 49. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 203,495 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: Watchdog prices 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
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
Raises the score by about 5 points · Medium effort · DR & Backup
2
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
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 €320,000 to build again, about 2.2 person-years of work. Its weakest lens is Production Readiness, at 42 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 4.8 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 8% to 18% on every change. The history of the code shows how much it changes: about 367,243 lines over the last 90 days, which is about 1,489,374 lines a year. At that pace, the extra work comes to an estimated 297.5 to 1784.8 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 Watchdog's 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 — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
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.
1151 modules, with 428 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; 1111 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.
motion.src.surfaces uses motion.src.tokens, so a change to motion.src.tokens can break motion.src.surfaces, while a change to motion.src.surfaces can't break motion.src.tokens.
Position
Below the diagonal: motion.src.surfaces uses a module listed above it, which is the healthy direction.
react.src.components.AddSelect.AddSelectRow uses react.src.components.Checkbox.Checkbox, so a change to react.src.components.Checkbox.Checkbox can break react.src.components.AddSelect.AddSelectRow, while a change to react.src.components.AddSelect.AddSelectRow can't break react.src.components.Checkbox.Checkbox.
Position
Below the diagonal: react.src.components.AddSelect.AddSelectRow uses a module listed above it, which is the healthy direction.
react.src.components.AddSelect.AddSelectRow uses react.src.components.IconButton, so a change to react.src.components.IconButton can break react.src.components.AddSelect.AddSelectRow, while a change to react.src.components.AddSelect.AddSelectRow can't break react.src.components.IconButton.
Position
Below the diagonal: react.src.components.AddSelect.AddSelectRow uses a module listed above it, which is the healthy direction.
react.src.components.AddSelect.AddSelectSelectionSummaryItem uses react.src.components.IconButton, so a change to react.src.components.IconButton can break react.src.components.AddSelect.AddSelectSelectionSummaryItem, while a change to react.src.components.AddSelect.AddSelectSelectionSummaryItem can't break react.src.components.IconButton.
Position
Below the diagonal: react.src.components.AddSelect.AddSelectSelectionSummaryItem uses a module listed above it, which is the healthy direction.
react.src.components.Card uses react.src.components.Card.Card_types, so a change to react.src.components.Card.Card_types can break react.src.components.Card, while a change to react.src.components.Card can't break react.src.components.Card.Card_types.
Position
Below the diagonal: react.src.components.Card uses a module listed above it, which is the healthy direction.
react.src.components.DataTable.DataTable uses react.src.components.DataTable.state.sortStates, so a change to react.src.components.DataTable.state.sortStates can break react.src.components.DataTable.DataTable, while a change to react.src.components.DataTable.DataTable can't break react.src.components.DataTable.state.sortStates.
Position
Below the diagonal: react.src.components.DataTable.DataTable uses a module listed above it, which is the healthy direction.
react.src.internal uses react.src.internal.FloatingMenu, so a change to react.src.internal.FloatingMenu can break react.src.internal, while a change to react.src.internal can't break react.src.internal.FloatingMenu.
Position
Below the diagonal: react.src.internal uses a module listed above it, which is the healthy direction.
utilities.src.date-picker.primitives.types uses utilities.src.date-picker.primitives.states, so a change to utilities.src.date-picker.primitives.states can break utilities.src.date-picker.primitives.types, while a change to utilities.src.date-picker.primitives.types can't break utilities.src.date-picker.primitives.states.
Position
Below the diagonal: utilities.src.date-picker.primitives.types uses a module listed above it, which is the healthy direction.
web-components.src.components.overflow-menu.overflow-menu-body uses react.src.internal.FloatingMenu, so a change to react.src.internal.FloatingMenu can break web-components.src.components.overflow-menu.overflow-menu-body, while a change to web-components.src.components.overflow-menu.overflow-menu-body can't break react.src.internal.FloatingMenu.
Position
Below the diagonal: web-components.src.components.overflow-menu.overflow-menu-body uses a module listed above it, which is the healthy direction.
web-components.src.components.text-input.text-input uses web-components.src.components.date-picker.defs, so a change to web-components.src.components.date-picker.defs can break web-components.src.components.text-input.text-input, while a change to web-components.src.components.text-input.text-input can't break web-components.src.components.date-picker.defs.
Position
Below the diagonal: web-components.src.components.text-input.text-input uses a module listed above it, which is the healthy direction.
react.src.components.DataTable uses react.src.components.DataTable.DataTable, so a change to react.src.components.DataTable.DataTable can break react.src.components.DataTable, while a change to react.src.components.DataTable can't break react.src.components.DataTable.DataTable.
Position
Below the diagonal: react.src.components.DataTable uses a module listed above it, which is the healthy direction.
react.src.components.DataTable.state.sorting uses react.src.components.DataTable.state.sortStates, so a change to react.src.components.DataTable.state.sortStates can break react.src.components.DataTable.state.sorting, while a change to react.src.components.DataTable.state.sorting can't break react.src.components.DataTable.state.sortStates.
Position
Below the diagonal: react.src.components.DataTable.state.sorting uses a module listed above it, which is the healthy direction.
react.src.components.DataTable.state.sorting uses react.src.components.DataTable.DataTable, so a change to react.src.components.DataTable.DataTable can break react.src.components.DataTable.state.sorting, while a change to react.src.components.DataTable.state.sorting can't break react.src.components.DataTable.DataTable.
Position
Below the diagonal: react.src.components.DataTable.state.sorting uses a module listed above it, which is the healthy direction.
react.src.components.DatePicker.next.hooks.useDatePicker uses utilities.src.date-picker.primitives.states, so a change to utilities.src.date-picker.primitives.states can break react.src.components.DatePicker.next.hooks.useDatePicker, while a change to react.src.components.DatePicker.next.hooks.useDatePicker can't break utilities.src.date-picker.primitives.states.
Position
Below the diagonal: react.src.components.DatePicker.next.hooks.useDatePicker uses a module listed above it, which is the healthy direction.
react.src.components.DatePicker.next.hooks.useDatePicker uses utilities.src.date-picker.primitives.types, so a change to utilities.src.date-picker.primitives.types can break react.src.components.DatePicker.next.hooks.useDatePicker, while a change to react.src.components.DatePicker.next.hooks.useDatePicker can't break utilities.src.date-picker.primitives.types.
Position
Below the diagonal: react.src.components.DatePicker.next.hooks.useDatePicker uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in web-components.src.components.date-picker.next.adapters.web-component-adapter uses a type in utilities.src.date-picker.primitives.states.
web-components.src.components.date-picker.next.adapters.web-component-adapter uses utilities.src.date-picker.primitives.states, so a change to utilities.src.date-picker.primitives.states can break web-components.src.components.date-picker.next.adapters.web-component-adapter, while a change to web-components.src.components.date-picker.next.adapters.web-component-adapter can't break utilities.src.date-picker.primitives.states.
Position
Below the diagonal: web-components.src.components.date-picker.next.adapters.web-component-adapter uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in web-components.src.components.date-picker.next.adapters.web-component-adapter uses a type in utilities.src.date-picker.primitives.types.
web-components.src.components.date-picker.next.adapters.web-component-adapter uses utilities.src.date-picker.primitives.types, so a change to utilities.src.date-picker.primitives.types can break web-components.src.components.date-picker.next.adapters.web-component-adapter, while a change to web-components.src.components.date-picker.next.adapters.web-component-adapter can't break utilities.src.date-picker.primitives.types.
Position
Below the diagonal: web-components.src.components.date-picker.next.adapters.web-component-adapter uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in web-components.src.components.number-input.number-input uses a type in web-components.src.components.date-picker.defs.
web-components.src.components.number-input.number-input uses web-components.src.components.date-picker.defs, so a change to web-components.src.components.date-picker.defs can break web-components.src.components.number-input.number-input, while a change to web-components.src.components.number-input.number-input can't break web-components.src.components.date-picker.defs.
Position
Below the diagonal: web-components.src.components.number-input.number-input uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in web-components.src.components.number-input.number-input uses a type in web-components.src.components.text-input.text-input.
web-components.src.components.number-input.number-input uses web-components.src.components.text-input.text-input, so a change to web-components.src.components.text-input.text-input can break web-components.src.components.number-input.number-input, while a change to web-components.src.components.number-input.number-input can't break web-components.src.components.text-input.text-input.
Position
Below the diagonal: web-components.src.components.number-input.number-input uses a module listed above it, which is the healthy direction.
react.src.components.DataTable.state uses react.src.components.DataTable.state.sortStates, so a change to react.src.components.DataTable.state.sortStates can break react.src.components.DataTable.state, while a change to react.src.components.DataTable.state can't break react.src.components.DataTable.state.sortStates.
Position
Below the diagonal: react.src.components.DataTable.state uses a module listed above it, which is the healthy direction.
react.src.components.DataTable.state uses react.src.components.DataTable.state.sorting, so a change to react.src.components.DataTable.state.sorting can break react.src.components.DataTable.state, while a change to react.src.components.DataTable.state can't break react.src.components.DataTable.state.sorting.
Position
Below the diagonal: react.src.components.DataTable.state uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 56% · Adequate · gated by D1, D2 ·
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 category
Findings
Severity
A03:2025 — Software Supply Chain Failures
63
High / Critical
A05:2025 — Injection
52
High / Critical
A02:2025 — Security Misconfiguration
13
High / Critical
A07:2025 — Authentication Failures
5
High / Critical
Roadmap
First, establish true disaster recovery by codifying backups and geo-recovery in infrastructure as code, explicitly documenting recovery time and data loss objectives. Next, improve dependency hygiene by removing unused packages, clarifying imports, and resolving deprecated and outdated libraries to reduce risk and clutter. Finally, strengthen web security by replacing weak cryptographic hashes with stronger alternatives for sensitive data and using non-cryptographic hashes for identifiers.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key.
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 — 149
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 — 1195
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 — 284
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 7
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
Watchdog 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. 87 of 87 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three 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; ◐ Advisory — an LLM prose judgement. 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; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 87 dimensions across the health lenses
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
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, 1539 of 1628 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.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
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.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 199 test file(s) failed while being loaded here, so none of their cases ran (typically a native addon or generated module the package's install scripts build, which the analyzer's scripts-off install does not run). The 281 production file(s) those files import that read under half covered are unmeasured in this run, not untested, so their figures are left out of the per-file rows and the 59.0% rather than published as low coverage. You can widen what we reach: optional: commit the lcov report of a run where those test files load, and their modules are read from it.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog 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's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D23 Boundary Type-Coupling — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — Watchdog 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog 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. `packages/react/src/components/BadgeIndicator/index.tsx`, `packages/react/src/components/Breadcrumb/BreadcrumbItem.tsx`, `packages/react/src/components/DataTable/TableCell.tsx`, `packages/react/src/components/DataTable/TableHeader.tsx`, `packages/react/src/components/DataTable/TableRow.tsx`, … (+26 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AC6 Visual & motion safety — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 34 further occurrence(s) are not listed individually; the score already reflects all 74.
AXR1 Runtime accessibility — not measured this run — Watchdog 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. Render strategy: boot via DevServer (dev). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
IC1 Incompleteness & stubs — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 164 further occurrence(s) are not listed individually; the score already reflects all 204.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. A badge or prose version claim scored 9/17 in its adjudication (docs/plans/deterministic-engine/adjudication/M4-v3.md: badges 9/9, prose 0/8, where prose versions are minimums or history), short of the 95 % precision gate, so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them. The .NET and Node.js version checks are a different kind and still publish.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 707 further occurrence(s) are not listed individually; the score already reflects all 747.
R3 Large Files — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 124 further occurrence(s) are not listed individually; the score already reflects all 164.
R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 440 further occurrence(s) are not listed individually; the score already reflects all 480.
R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 697 further occurrence(s) are not listed individually; the score already reflects all 737.
X2 Cancellation propagation — not measured this run — Watchdog 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; 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 — Watchdog 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 log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, 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: 43 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
Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's 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.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
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 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D25 ADR Conformance: ADR conformance is the LLM-scored fraction of sampled code that follows recorded decisions — it checks the decisions that were written down and the slices it sampled, not unrecorded rules or the whole tree.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
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.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
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 REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
162 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ComboBox.ComboBox at 183. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being size-prop-update.transform at 16 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/upgrade/transforms/size-prop-update.js (size-prop-update.transform 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.
+ 145 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 120 down to 120 or less in Cyclomatic Complexity — start with ComboBox.ComboBox (cyclomatic 183), Slider.Slider (cyclomatic 154), DatePicker.DatePicker (cyclomatic 121). — 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 3 together lifts Cyclomatic Complexity from 3.9 to about 4.6/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 181 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 120 down to 120 or less in Cognitive Complexity — start with ComboBox.ComboBox (cognitive 231), DatePicker.DatePicker (cognitive 125). — 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 2 together lifts Cognitive Complexity from 2.4 to about 3.7/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.8 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 50 FunctionTooLong finding(s) in God Classes — start with DatePicker.tsx (2), Slider.tsx, Error403SVG.tsx. — One of this dimension's main actionable groups (50 warning-level).
Resolve the 26 FileTooLong finding(s) in God Classes — start with Slider.tsx, Tabs.tsx, ComboBox.tsx. — One of this dimension's main actionable groups (26 warning-level).
Resolve the 21 MethodTooLong finding(s) in God Classes — start with text-input.ts, password-input.ts, stacking-tearsheet.ts. — One of this dimension's main actionable groups (21 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.6 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
37 production modules (npm), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; 5 module(s) off the main sequence, with abstractness counted on 14 of the 37 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: @carbon/colors · ×5
Unstable project @carbon/react
What to do
Resolve the 5 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 Unstable project @carbon/react finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Resolve the 25 Low cohesion finding(s) in Cohesion (LCOM4) — start with date-picker-input.ts (2), checkbox.ts, table-row.ts. — One of this dimension's main actionable groups (25 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
Classify ADR enforcement: 1. Record project decisions · ×10docs/decisions/0001-record-project-decisions.md
What to do
Resolve the 10 Classify ADR enforcement finding(s) in Architectural Integrity — start with 0001-record-project-decisions.md, 0002-replace-recursive-prop-passing-with-context.md, 0003-use-preview-moniker.md. — One of this dimension's main actionable groups (10 recommendation-level).
Enforce Architectural Integrity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d7_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, 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.
Line coverage 59.0% — 33 file(s) below 50%. Measured from the JavaScript/TypeScript suite (jest via `yarn install --immutable --mode=skip-build` in the repository root; web-test-runner in packages/web-components/: not run).
Resolve the 33 Low coverage finding(s) in Code Coverage — start with index.js (2), builder.js (2), tools.js. — One of this dimension's main actionable groups (33 warning-level).
Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution9.3 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
7844 test methods: 7410 unit, 0 integration, 0 BDD, 434 e2e. The JavaScript/TypeScript suite contributes 7844 `it`/`test` case(s) across 733 test file(s) declaring at least one; its tier split is read from package names and paths only.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.7 / 10Adequategated by 3 critical findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
115 skipped (1 with a documented reason), 28 zero-assertion, 3 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 7844 tests.
No assertions (empty test): should be an ol if prop ordered is passed as true · ×3packages/web-components/src/components/accordion/__tests__/accordion-test.js:162
Skipped test: Should render the expando · ×114packages/web-components/tests/spec/code-snippet_spec.ts:173
No assertions: should fire cancel click event · ×25packages/web-components/src/components/data-table/__tests__/table-batch-actions-test.js:34
Fixed-sleep synchronisation: should close menu when a menu item is clicked · ×3packages/web-components/src/components/overflow-menu/__tests__/overflow-menu-test.js:320
Test project verifies nothing: packages/react/examples/react-router-vitepackages/react/examples/react-router-vite/src/App-test.js:5
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 No assertions (empty test) finding(s) in Test Quality — start with accordion-test.js (2), AILabel-test.tsx. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 114 Skipped test finding(s) in Test Quality — start with multi-select_spec.ts (11), file-uploader_spec.ts (9), data-table_spec.ts (8). — One of this dimension's main actionable groups (114 warning-level).
Resolve the 25 No assertions finding(s) in Test Quality — start with EditInPlace-test.js (3), ActionSet-test.js (3), table-batch-actions-test.js (2). — One of this dimension's main actionable groups (25 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
73 outdated direct production npm dependency(ies) of 123 graded, 0 pinning defect(s), across 147 package.json (37 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 0 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.
Resolve the 39 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (39). — One of this dimension's main actionable groups (39 recommendation-level).
Resolve the 14 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (14). — One of this dimension's main actionable groups (14 recommendation-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
0 of 123 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 123 production dependency(ies) this repository's committed lockfile resolves, across 37 product package.json manifest(s). Its 562 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ 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 Apache-2.0, which is its own choice and is not judged here.
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.
Top hotspots: packages/react/src/components/ComboBox/ComboBox.tsx (4×183=732); packages/react/src/components/MultiSelect/MultiSelect.tsx (7×104=728); packages/react/src/components/DatePicker/DatePicker.tsx (6×121=726) Repeated repair below the complexity floor: packages/react/src/components/MultiSelect/__tests__/MultiSelect-test.js (5 of 6 changes were fixes); packages/react/src/components/DatePicker/DatePicker-test.js (5 of 6 changes were fixes); packages/react/src/components/Slider/__tests__/Slider-test.js (4 of 4 changes were fixes)
Resolve the 36 Hotspot finding(s) in Churn × Complexity Hotspots — start with ComboBox.tsx, MultiSelect.tsx, DatePicker.tsx. — One of this dimension's main actionable groups (36 warning-level).
Resolve the 11 Repeated repair finding(s) in Churn × Complexity Hotspots — start with index.tsx (2), MultiSelect-test.js, DatePicker-test.js. — One of this dimension's main actionable groups (11 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.4 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
52 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/react/src/components/Card/Card.stories.js. Counted over 896 of the 2118 production source files in this repository: 1220 are under the ~2,400-byte size floor this dimension measures over, and the remaining 2 have no attributable history left to measure.
Off-boarding risk: anonymized user #1 · ×7
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
129 deducted task-comment markers across 169581 LoC (0.1/KLoC) → score 9.8. 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.
Resolve the 104 TodoComment finding(s) in Explicit Debt — start with index.ts (19), Slider.tsx (7), toggle.ts (6). — One of this dimension's main actionable groups (104 warning-level).
Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with text-input.ts. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 TodoComment repeated across 17 files finding(s) in Explicit Debt — start with overflow-menu.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
0 of 10 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
10 domain type(s) cross context boundaries across 33 contexts; they are measured and withheld (not published, not scored). Contexts: babel-preset-carbon, carbon-components, carbon-components-react, cli, cli-reporter, colors, feature-flags, grid, icon-build-helpers, icon-helpers, icons, icons-react and 21 more.
What it measures: Whether the code actually follows the decisions recorded in the project's ADRs.
Method: Judged by language model at low temperature against ADRs plus a deterministic structural code summary; findings linked to repo-rooted ADR paths for traceability. Advisory.
1 of 1 checkable records are broken by the code or by their own declared delivery (1 of 8 binding records state a rule in checkable form or declare their delivery; prose decisions are unverifiable).
ADR not followed: 3. Use `preview` moniker instead of `experimental`docs/decisions/0003-use-preview-moniker.md:42detected by adr-prohibition
What to do
Resolve the 1 ADR not followed finding(s) in ADR Conformance — start with 0003-use-preview-moniker.md. — One of this dimension's main actionable groups (1 recommendation-level).
Enforce ADR Conformance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d25_recommendation.md · top locations in Appendix A, every location in findings.md.
2 of 39 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED 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.
4 finding(s): 0 critical, 4 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
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).
52 finding(s): 0 critical, 39 high, 13 medium, 0 low. 9 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 33 file(s) — `packages/react/.storybook/manager-head.html` (lines 40–43), `packages/react/src/components/BadgeIndicator/index.tsx` (line 30), `packages/react/src/components/Breadcrumb/BreadcrumbItem.tsx` (line 43), `packages/react/src/components/DataTable/TableCell.tsx` (line 40), `packages/react/src/components/DataTable/TableHeader.tsx` (line 149), … (+28 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 9 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 8 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 13 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (12), REDACTED. — One of this dimension's main actionable groups (13 issue-level).
Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (9), REDACTED. — One of this dimension's main actionable groups (10 issue-level).
No action in Static Analysis (SAST) — all 9 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (9 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Resolve the 26 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (26). — One of this dimension's main actionable groups (26 issue-level).
Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
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.
Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 9 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (8), REDACTED. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
74 of 898 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/react/src/components/PaginationNav/PaginationNav.tsx. Counted over 898 of the 2118 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with PaginationNav.tsx, definitions.js. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 72 Orphaned file finding(s) in Knowledge Freshness — start with index.js (3), tokens.ts (2), workspace.js (2). — One of this dimension's main actionable groups (72 recommendation-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Resolve the 3 Change coupling finding(s) in Change Coupling — start with ControlledPasswordInput.tsx, FilterableMultiSelect.tsx, CheckboxGroup.tsx. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with DismissibleTag.tsx. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 6 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 17 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (17 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
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. Scored 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. SCORED, not informational.
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.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 1 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.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
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.
Do you agree with this assessment?
AC2 · Forms & labels5.3 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. — packages/react/src/components/TreeView/TreeView.tsx:291
A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. (×5) — packages/web-components/src/components/button/button-skeleton.ts:54, packages/web-components/src/components/date-picker/date-picker.ts:568, packages/web-components/src/components/date-picker/date-picker.ts:575, …
A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). — packages/web-components/src/components/button/button-skeleton.ts:68
This <slot> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — packages/web-components/src/components/content-switcher/content-switcher.ts:519
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×3) — packages/web-components/src/components/multi-select/multi-select.ts:488, packages/web-components/src/components/password-input/password-input.ts:316, packages/web-components/src/components/time-picker/time-picker.ts:252
This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×17) — packages/web-components/src/components/password-input/password-input.ts:260, packages/web-components/src/components/tearsheet/_story-assets/stacking-tearsheet.ts:78, packages/web-components/src/components/tearsheet/_story-assets/stacking-tearsheet.ts:82, …
A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one. (×2) — packages/web-components/src/components/radio-button/radio-button-group.ts:296, packages/web-components/src/components/tile/tile-group.ts:268
This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×2) — packages/web-components/src/components/side-panel/side-panel.ts:1113, packages/web-components/src/components/ui-shell/side-nav.ts:249
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×2) — packages/web-components/src/components/slider/slider-input.ts:248, packages/web-components/src/components/structured-list/structured-list-row.ts:217
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.
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.
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — packages/web-components/.storybook/basic-example-cdn.html:2
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — packages/web-components/.storybook/basic-example-cdn.html:2
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — packages/web-components/.storybook/basic-example-cdn.html:2
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — packages/web-components/src/components/tearsheet/tearsheet-helpers.ts:173
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.
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. — packages/react/src/components/TreeView/TreeNode.tsx:587
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. — packages/web-components/.storybook/templates/with-feature-flags.ts:32
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×5) — packages/web-components/src/components/date-picker/date-picker-input.ts:351, packages/web-components/src/components/dialog/dialog.ts:278, packages/web-components/src/components/tree-view/tree-node.ts:331, …
This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus. (×2) — packages/web-components/src/components/dropdown/dropdown.ts:1343, packages/web-components/src/components/ui-shell/side-nav.ts:252
This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — packages/web-components/src/components/notification-panel/notification-panel.ts:195
An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action. — packages/web-components/src/components/ui-shell/header-menu.ts:153
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
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.
`:host( -user-avatar) . __tooltip-trigger` 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. — packages/web-components/src/components/user-avatar/user-avatar.scss:60
`:host( -header-nav-item)` 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. — packages/web-components/src/components/ui-shell/header.scss:45
`:host( -header-menu)` 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. — packages/web-components/src/components/ui-shell/header.scss:51
`:host( -header-menu-item)` 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. — packages/web-components/src/components/ui-shell/header.scss:55
`:host( -header-menu-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. — packages/web-components/src/components/ui-shell/header.scss:119
`:host( -side-nav-link)` 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. — packages/web-components/src/components/ui-shell/side-nav.scss:30
`:host( -side-nav-menu-item)` 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. — packages/web-components/src/components/ui-shell/side-nav.scss:114
`:host( -tree-node:focus-visible)` 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. — packages/web-components/src/components/tree-view/tree-view.scss:41
`:host( -toggletip)` 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. — packages/web-components/src/components/toggle-tip/toggletip.scss:28
`:host( -toggle)` 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. — packages/web-components/src/components/toggle/toggle.scss:17
`:host( -clickable-tile)` 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. — packages/web-components/src/components/tile/tile.scss:44
`:host( -radio-tile)` 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. — packages/web-components/src/components/tile/tile.scss:92
`:host( -selectable-tile)` 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. — packages/web-components/src/components/tile/tile.scss:105
`:host( -expandable-tile[with-interactive]):focus` 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. — packages/web-components/src/components/tile/tile.scss:182
`:host( -expandable-tile:not([with-interactive])) . --tile__chevron` 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. — packages/web-components/src/components/tile/tile.scss:195
`:host( -textarea)` 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. — packages/web-components/src/components/textarea/textarea.scss:20
`:host( -text-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. — packages/web-components/src/components/text-input/text-input.scss:29
`:host( -tab)` 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. — packages/web-components/src/components/tabs/tabs.scss:293
`:host( -tab[disabled][role]) . --tabs__nav-link` 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. — packages/web-components/src/components/tabs/tabs.scss:485
`:host( -slider)` 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. — packages/web-components/src/components/slider/slider.scss:20
`:host( -select)` 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. — packages/web-components/src/components/select/select.scss:35
`:host( -search)` 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. — packages/web-components/src/components/search/search.scss:26
`:host([expandable]:focus-within) . --search-magnifier ~ . --search-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. — packages/web-components/src/components/search/search.scss:37
`:host([expandable][expanded]:focus-within) . --search-magnifier` 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. — packages/web-components/src/components/search/search.scss:42
`:host( -search[disabled]) . --search-close` 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. — packages/web-components/src/components/search/search.scss:79
`:host( -radio-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. — packages/web-components/src/components/radio-button/radio-button.scss:56
`:host( -progress-step)` 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. — packages/web-components/src/components/progress-indicator/progress-indicator.scss:35
`:host( -password-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. — packages/web-components/src/components/password-input/password-input.scss:25
`:host( -pagination)` 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. — packages/web-components/src/components/pagination/pagination.scss:24
`:host( -overflow-menu-item)` 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. — packages/web-components/src/components/overflow-menu/overflow-menu.scss:101
`:host( -number-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. — packages/web-components/src/components/number-input/number-input.scss:36
`:host( -actionable-notification)` 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. — packages/web-components/src/components/notification/actionable-notification.scss:30
`:host( -callout-notification)` 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. — packages/web-components/src/components/notification/actionable-notification.scss:202
`:host( -inline-notification)` 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. — packages/web-components/src/components/notification/inline-notification.scss:26
`:host( -toast-notification)` 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. — packages/web-components/src/components/notification/toast-notification.scss:25
`:host( -multi-select) . --list-box__menu` 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. — packages/web-components/src/components/multi-select/multi-select.scss:45
`:host( -multi-select) . --text-input:focus` 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. — packages/web-components/src/components/multi-select/multi-select.scss:59
`:host( -multi-select)` 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. — packages/web-components/src/components/multi-select/multi-select.scss:27
`:host( -multi-select) . --list-box__field.no-focus-style:focus` 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. — packages/web-components/src/components/multi-select/multi-select.scss:541
`:host( -multi-select[disabled]) . --list-box__field:focus` 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. — packages/web-components/src/components/multi-select/multi-select.scss:620
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.
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
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.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
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.
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.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`DataTableRenderProps` declares 16 required operations: `getHeaderProps`, `getExpandHeaderProps`, `getRowProps`, `getExpandedRowProps`, `getSelectionProps`, `getToolbarProps`, `getBatchActionProps`, `getTableProps`, `getTableContainerProps`, `getCellProps`, `onInputChange`, `sortBy`, `selectAll`, `selectRow`, `expandRow`, `expandAll`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/react/src/components/DataTable/DataTable.tsx:121
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
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 ("<cds-slug size="xs" alignment="bottom-ri…") is still in shipped code — typical of generated boilerplate that was never filled in. — packages/web-components/src/components/side-panel/_story-assets/index.ts:194
What to do
Finish or delete the functions that still throw "not implemented", and replace placeholder text before shipping.
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.
`validateHeadings` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — actions/validate-pr-template/index.js:155
`validateChecklistItems` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — actions/validate-pr-template/index.js:182
`main` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/cli/src/cli.js:40
`emitDeclarations` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/cli/src/commands/bundle/tsdown.js:116
`writeTsDefinitions` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/icon-build-helpers/src/builders/react/next/typescript.js:88
`write` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/icon-build-helpers/src/metadata/adapters/memory.js:37
`compileIconComponent` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/pictograms-react/tasks/build.js:53
`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. — packages/react/src/components/Form/stories/form-demo.js:253
`onClick` 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. (×4) — packages/upgrade/transforms/__testfixtures__/enable-v12-overflowmenu-nowrap.input.js:19, packages/upgrade/transforms/__testfixtures__/enable-v12-overflowmenu-nowrap.output.js:21, packages/upgrade/transforms/__testfixtures__/enable-v12-overflowmenu.input.js:18, …
`onClose` 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. (×28) — packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-alias.input.tsx:16, packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-alias.output.tsx:14, packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-edge-cases.input.tsx:13, …
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.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
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
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
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.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 95 of 149 project(s) that lack one — worth up to 1.3 pts.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
docs/postmortems/README.md links to `./00-template.md`, but `docs/postmortems/00-template.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/postmortems/README.md:15
packages/carbon-components/README.md links to `./docs/sass.md#configuration`, but `packages/carbon-components/docs/sass.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/carbon-components/README.md:46
packages/icon-build-helpers/src/metadata/README.md links to `./registry.js`, but `packages/icon-build-helpers/src/metadata/registry.js` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/icon-build-helpers/src/metadata/README.md:28
packages/react/src/internal/README.md links to `./FeatureFlags.js`, but `packages/react/src/internal/FeatureFlags.js` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/react/src/internal/README.md:3
What to do
Reconcile the README with reality: docs/postmortems/README.md links to `./00-template.md`, but `docs/postmortems/00-template.md` does not exist; packages/carbon-components/README.md links to `./docs/sass.md#configuration`, but `packages/carbon-components/docs/sass.md` does not exist; packages/icon-build-helpers/src/metadata/README.md links to `./registry.js`, but `packages/icon-build-helpers/src/metadata/registry.js` does not exist; packages/react/src/internal/README.md links to `./FeatureFlags.js`, but `packages/react/src/internal/FeatureFlags.js` does not exist.
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.
Do you agree with this assessment?
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 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.
Do you agree with this assessment?
P2 · Observability6.0 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/web-components`.
`packages/upgrade/transforms/icons-react-size-prop.js` reports through `console.*` at line 321 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/upgrade/transforms/icons-react-size-prop.js:321
`packages/upgrade/transforms/wc-report-non-barrel-imports.js` reports through `console.*` at line 141 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/upgrade/transforms/wc-report-non-barrel-imports.js:141
`packages/upgrade/transforms/__testfixtures__/featureflag-deprecate-flags-prop.input.js` reports through `console.*` at line 48 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/upgrade/transforms/__testfixtures__/featureflag-deprecate-flags-prop.input.js:48
`packages/upgrade/transforms/__testfixtures__/featureflag-deprecate-flags-prop.input.js` reports through `console.*` at line 52 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/upgrade/transforms/__testfixtures__/featureflag-deprecate-flags-prop.input.js:52
`packages/upgrade/transforms/__testfixtures__/featureflag-deprecate-flags-prop.output.js` reports through `console.*` at line 48 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/upgrade/transforms/__testfixtures__/featureflag-deprecate-flags-prop.output.js:48
`packages/upgrade/transforms/__testfixtures__/featureflag-deprecate-flags-prop.output.js` reports through `console.*` at line 52 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/upgrade/transforms/__testfixtures__/featureflag-deprecate-flags-prop.output.js:52
`packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js` reports through `console.*` at line 49 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js:49
`packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js` reports through `console.*` at line 55 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js:55
`packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js` reports through `console.*` at line 71 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js:71
`packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js` reports through `console.*` at line 77 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js:77
`packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js` reports through `console.*` at line 132 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js:132
`packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js` reports through `console.*` at line 141 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js:141
`packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js` reports through `console.*` at line 47 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js:47
`packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js` reports through `console.*` at line 53 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js:53
`packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js` reports through `console.*` at line 67 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js:67
`packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js` reports through `console.*` at line 73 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js:73
`packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js` reports through `console.*` at line 120 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js:120
`packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js` reports through `console.*` at line 128 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js:128
`packages/upgrade/src/logger.js` reports through `console.*` at line 65 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/upgrade/src/logger.js:65
`packages/upgrade/src/logger.js` reports through `console.*` at line 72 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/upgrade/src/logger.js:72
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
`REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Do you agree with this assessment?
P5 · DR & Backup0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
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 the language 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.existsSync` in `inlineSassDependencies` 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. — packages/cli/src/commands/inline.js:48
`fs.existsSync` in `loadWorkspace` 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. — packages/upgrade/src/workspace.js:110
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.
Do you agree with this assessment?
R1 · Type Safety5.9 / 10Adequate✓ 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.
1614 typed · 1137 plain JS — the untyped files are achecker.js, actions/issues/src/conditions.js, actions/issues/src/manage-comment-test.js, actions/issues/src/manage-comment.js, actions/issues/src/plugins/bob-bug-triage-test.js, actions/issues/src/plugins/bob-bug-triage.js (+1131 more). 0 production file(s) opt out entirely with @ts-nocheck · 99 @ts-ignore suppression(s).
What to do
Migrate the remaining .js/.jsx files to TypeScript.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): 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. Deterministic.
217 duplicated blocks under packages/react/src/components/ have copies in at least two of the sibling directories AISkeleton, AspectRatio, BadgeIndicator, BigNumber, Breadcrumb, Button (+101 more sibling(s) not listed) — 94 of them are reported below, and 123 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 217 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 217 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 217 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. — packages/react/src/components/TextArea/TextArea.tsx:45
133 duplicated blocks under packages/ have copies in at least two of the sibling directories carbon-components, carbon-components-react, cli, feature-flags, icons, icons-react (+10 more sibling(s) not listed) — 114 of them are reported below, and 19 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 133 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 133 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 133 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. — packages/react/src/components/PageHeader/overflowHandler.ts:27
120 duplicated blocks under packages/web-components/src/components/ have copies in at least two of the sibling directories accordion, action-set, add-select, ai-label, ai-skeleton, big-number (+73 more sibling(s) not listed) — 86 of them are reported below, and 34 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 120 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 120 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 120 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. — packages/web-components/src/components/password-input/password-input.ts:136
30 duplicated blocks under packages/web-components/code-connect/ have copies in at least two of the sibling directories breadcrumb, button, checkbox, combo-box, combo-button, content-switcher (+31 more sibling(s) not listed) — 12 of them are reported below, and 18 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 30 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 30 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 30 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. — packages/web-components/code-connect/checkbox/checkbox.figma.ts:59
20 duplicated blocks under packages/react/code-connect/ have copies in at least two of the sibling directories AILabel, Accordion, Breadcrumb, Button, Checkbox, CodeSnippet (+32 more sibling(s) not listed) — 11 of them are reported below, and 9 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 20 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 20 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 20 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. — packages/react/code-connect/FileUploader/FileUploader.figma.ts:72
packages/react/src/components/TextArea/TextArea.tsx:45 · packages/react/src/components/TextInput/TextInput.tsx:35 — the two spans are one implementation copied and then locally edited — 996 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. — packages/react/src/components/TextArea/TextArea.tsx:45
packages/react/src/components/ComposedModal/ComposedModal.tsx:257 · packages/react/src/components/Modal/Modal.tsx:252 — the two spans are one implementation copied and then locally edited — 986 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. — packages/react/src/components/ComposedModal/ComposedModal.tsx:257
packages/react/src/components/ComposedModal/ComposedModal-test.js:1024 · packages/react/src/components/Modal/Modal-test.js:960 — the two spans are one implementation copied and then locally edited — 1121 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. — packages/react/src/components/ComposedModal/ComposedModal-test.js:1024
packages/web-components/src/components/password-input/password-input.ts:136 · packages/web-components/src/components/text-input/text-input.ts:345 — the two spans are one implementation copied and then locally edited — 755 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. — packages/web-components/src/components/password-input/password-input.ts:136
packages/themes/src/v10/g10.ts:8 · packages/themes/src/v10/white.ts:8 — these 2 files are line-for-line copies of one another — 143 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. — packages/themes/src/v10/g10.ts:8
packages/themes/src/v10/g100.ts:8 · packages/themes/src/v10/g90.ts:8 — these 2 files are line-for-line copies of one another — 125 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. — packages/themes/src/v10/g100.ts:8
packages/web-components/src/components/date-picker/date-picker-input.ts:245 · packages/web-components/src/components/date-picker/next/components/date-picker-input.ts:293 — the two spans are one implementation copied and then locally edited — 577 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. — packages/web-components/src/components/date-picker/date-picker-input.ts:245
packages/react/src/components/TextInput/PasswordInput.tsx:280 · packages/react/src/components/TextInput/TextInput.tsx:308 — the two spans are one implementation copied and then locally edited — 519 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. — packages/react/src/components/TextInput/PasswordInput.tsx:280
packages/react/src/components/PageHeader/overflowHandler.ts:27 · packages/web-components/src/components/page-header/_story-assets/overflowHandler.ts:21 — these 2 files are line-for-line copies of one another — 99 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. — packages/react/src/components/PageHeader/overflowHandler.ts:27
packages/utilities/src/date-picker/primitives/actions.ts:562 · packages/utilities/src/date-picker/primitives/actions.ts:937 — the two spans are one implementation copied and then locally edited — 429 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. — packages/utilities/src/date-picker/primitives/actions.ts:562
packages/upgrade/transforms/enable-v12-tile-default-icons.js:14 · packages/upgrade/transforms/enable-v12-tile-radio-icons.js:14 — these 2 files are line-for-line copies of one another — 88 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. — packages/upgrade/transforms/enable-v12-tile-default-icons.js:14
packages/react/code-connect/DatePicker/DatePickerRange.figma.ts:20 · packages/react/code-connect/DatePicker/FluidDatePickerRange.figma.ts:20 — 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. — packages/react/code-connect/DatePicker/DatePickerRange.figma.ts:20
packages/web-components/src/components/tearsheet/_story-assets/step-tearsheet-preview.ts:120 · packages/web-components/src/components/tearsheet/_story-assets/step-tearsheet.ts:109 — 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. — packages/web-components/src/components/tearsheet/_story-assets/step-tearsheet-preview.ts:120
packages/web-components/src/components/date-picker/date-picker-input.ts:30 · packages/web-components/src/components/date-picker/next/components/date-picker-input.ts:33 — the two spans are one implementation copied and then locally edited — 511 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. — packages/web-components/src/components/date-picker/date-picker-input.ts:30
packages/react/code-connect/MultiSelect/FluidFilterableMultiSelect.figma.ts:17 · packages/react/code-connect/MultiSelect/FluidMultiSelect.figma.ts:17 — 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. — packages/react/code-connect/MultiSelect/FluidFilterableMultiSelect.figma.ts:17
packages/web-components/src/components/tag/operational-tag.ts:8 · packages/web-components/src/components/tag/selectable-tag.ts:8 — these 2 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. — packages/web-components/src/components/tag/operational-tag.ts:8
packages/react/src/components/FluidMultiSelect/FluidFilterableMultiSelect.tsx:8 · packages/react/src/components/FluidMultiSelect/FluidMultiSelect.tsx:8 — these 2 files are line-for-line copies of one another — 70 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. — packages/react/src/components/FluidMultiSelect/FluidFilterableMultiSelect.tsx:8
packages/web-components/code-connect/date-picker/date-picker-range.figma.ts:18 · packages/web-components/code-connect/date-picker/fluid-date-picker-range.figma.ts:18 — the two spans are one implementation copied and then locally edited — 289 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. — packages/web-components/code-connect/date-picker/date-picker-range.figma.ts:18
packages/web-components/src/components/dialog/dialog.ts:107 · packages/web-components/src/components/modal/modal.ts:288 — the two spans are one implementation copied and then locally edited — 364 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. — packages/web-components/src/components/dialog/dialog.ts:107
packages/react/code-connect/DataTable/DataTable.figma.ts:14 · packages/web-components/code-connect/data-table/data-table.figma.ts:18 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — packages/react/code-connect/DataTable/DataTable.figma.ts:14
packages/web-components/code-connect/date-picker/date-picker-simple.figma.ts:24 · packages/web-components/code-connect/date-picker/date-picker-single.figma.ts: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. — packages/web-components/code-connect/date-picker/date-picker-simple.figma.ts:24
packages/react/src/components/PageHeader/PageHeaderContentPageActions.tsx:67 · packages/react/src/components/PageHeaderDeprecated/PageHeader.tsx:357 — the two spans are one implementation copied and then locally edited — 374 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. — packages/react/src/components/PageHeader/PageHeaderContentPageActions.tsx:67
packages/react/src/components/Checkbox/Checkbox.tsx:172 · packages/react/src/components/RadioButtonGroup/RadioButtonGroup.tsx:230 — the two spans are one implementation copied and then locally edited — 298 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. — packages/react/src/components/Checkbox/Checkbox.tsx:172
packages/react/code-connect/MultiSelect/FilterableMultiSelect.figma.ts:14 · packages/react/code-connect/MultiSelect/MultiSelect.figma.ts:14 — the two spans are one implementation copied and then locally edited — 294 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. — packages/react/code-connect/MultiSelect/FilterableMultiSelect.figma.ts:14
packages/react/src/components/Tag/OperationalTag.tsx:102 · packages/react/src/components/Tag/SelectableTag.tsx:114 — the two spans are one implementation copied and then locally edited — 318 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. — packages/react/src/components/Tag/OperationalTag.tsx:102
packages/web-components/src/components/checkbox/checkbox-group.ts:167 · packages/web-components/src/components/checkbox/checkbox.ts:248 — the two spans are one implementation copied and then locally edited — 240 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. — packages/web-components/src/components/checkbox/checkbox-group.ts:167
packages/utilities/src/overflowHandler/overflowHandler.ts:57 · packages/web-components/src/components/page-header/_story-assets/overflowHandler.ts:61 — the two spans are one implementation copied and then locally edited — 402 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. — packages/utilities/src/overflowHandler/overflowHandler.ts:57
packages/web-components/src/components/ai-label/ai-label.ts:8 · packages/web-components/src/components/slug/slug.ts:8 — these 2 files are line-for-line copies of one another — 59 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. — packages/web-components/src/components/ai-label/ai-label.ts:8
packages/react/src/components/TextInput/ControlledPasswordInput.tsx:208 · packages/react/src/components/TextInput/PasswordInput.tsx:315 — the two spans are one implementation copied and then locally edited — 259 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. — packages/react/src/components/TextInput/ControlledPasswordInput.tsx:208
packages/react/src/components/FluidComboBox/FluidComboBox.tsx:20 · packages/react/src/components/FluidDropdown/FluidDropdown.tsx:15 — 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. — packages/react/src/components/FluidComboBox/FluidComboBox.tsx:20
packages/react/code-connect/DatePicker/FluidDatePickerSimple.figma.ts:19 · packages/react/code-connect/DatePicker/FluidDatePickerSingle.figma.ts:19 — 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. — packages/react/code-connect/DatePicker/FluidDatePickerSimple.figma.ts:19
packages/react/src/components/ComposedModal/ComposedModalPresence.tsx:22 · packages/react/src/components/Modal/ModalPresence.tsx:21 — the two spans are one implementation copied and then locally edited — 275 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. — packages/react/src/components/ComposedModal/ComposedModalPresence.tsx:22
packages/react/src/components/AddSelect/AddSelectBody.tsx:206 · packages/web-components/src/components/add-select/add-select-body.ts:140 — the two spans are one implementation copied and then locally edited — 185 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. — packages/react/src/components/AddSelect/AddSelectBody.tsx:206
packages/web-components/code-connect/date-picker/fluid-date-picker-simple.figma.ts:23 · packages/web-components/code-connect/date-picker/fluid-date-picker-single.figma.ts:23 — 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. — packages/web-components/code-connect/date-picker/fluid-date-picker-simple.figma.ts:23
packages/web-components/code-connect/slider/slider-two-handles.figma.ts:18 · packages/web-components/code-connect/slider/slider.figma.ts:18 — the two spans are one implementation copied and then locally edited — 263 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. — packages/web-components/code-connect/slider/slider-two-handles.figma.ts:18
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.
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.
packages/icons-vue/tasks/build.js:11 imports @carbon/icon-build-helpers, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/icons-vue/tasks/build.js:11
packages/react/src/components/Coachmark/CoachmarkContentHeader.tsx:21 reaches into another package with a relative path (../../../../utilities/src/makeDraggable) — import the package by name instead. — packages/react/src/components/Coachmark/CoachmarkContentHeader.tsx:21
packages/react/src/components/DatePicker/DatePicker.tsx:21 imports flatpickr/dist/l10n/index, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/react/src/components/DatePicker/DatePicker.tsx:21
packages/react/src/components/DatePicker/plugins/rangePlugin.ts:8 imports flatpickr/dist/plugins/rangePlugin, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/react/src/components/DatePicker/plugins/rangePlugin.ts:8
packages/react/src/components/Guidebanner/Guidebanner.tsx:11 imports @carbon/colors, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/react/src/components/Guidebanner/Guidebanner.tsx:11
packages/react/src/components/Tearsheet/TearsheetWithSteps.jsx:10 reaches into another package with a relative path (../../../../utilities-react/src/StepFlow) — import the package by name instead. — packages/react/src/components/Tearsheet/TearsheetWithSteps.jsx:10
packages/upgrade/src/jscodeshift.js:8 imports jscodeshift/src/Runner, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/upgrade/src/jscodeshift.js:8
packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header2.input.js:6 imports @carbon/web-components/lib/components/page-header/page-header-tabs.js, which the target package's package.json `exports` does not declare — use a declared entry or declare the subpath. — packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header2.input.js:6
packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header2.output.js:6 imports @carbon/ibm-products-web-components/lib/components/page-header/page-header-tabs.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header2.output.js:6
packages/utilities-react/src/StepFlow/StepFlow-test.js:11 imports @carbon/react, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/utilities-react/src/StepFlow/StepFlow-test.js:11
packages/web-components/src/components/date-picker/append-to-plugin.ts:8 imports flatpickr/dist/types/instance, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/append-to-plugin.ts:8
packages/web-components/src/components/date-picker/append-to-plugin.ts:9 imports flatpickr/dist/types/options, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/append-to-plugin.ts:9
packages/web-components/src/components/date-picker/css-class-plugin.ts:8 imports flatpickr/dist/types/instance, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/css-class-plugin.ts:8
packages/web-components/src/components/date-picker/css-class-plugin.ts:9 imports flatpickr/dist/types/options, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/css-class-plugin.ts:9
packages/web-components/src/components/date-picker/date-picker.ts:11 imports flatpickr/dist/types/instance, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/date-picker.ts:11
packages/web-components/src/components/date-picker/date-picker.ts:12 imports flatpickr/dist/types/locale, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/date-picker.ts:12
packages/web-components/src/components/date-picker/date-picker.ts:13 imports flatpickr/dist/types/options, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/date-picker.ts:13
packages/web-components/src/components/date-picker/fix-events-plugin.ts:8 imports flatpickr/dist/types/instance, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/fix-events-plugin.ts:8
packages/web-components/src/components/date-picker/fix-events-plugin.ts:9 imports flatpickr/dist/types/options, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/fix-events-plugin.ts:9
packages/web-components/src/components/date-picker/focus-plugin.ts:8 imports flatpickr/dist/types/instance, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/focus-plugin.ts:8
packages/web-components/src/components/date-picker/focus-plugin.ts:9 imports flatpickr/dist/types/options, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/focus-plugin.ts:9
packages/web-components/src/components/date-picker/icon-plugin.ts:9 imports flatpickr/dist/types/instance, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/icon-plugin.ts:9
packages/web-components/src/components/date-picker/icon-plugin.ts:10 imports flatpickr/dist/types/options, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/icon-plugin.ts:10
packages/web-components/src/components/date-picker/month-select-plugin.ts:8 imports flatpickr/dist/types/instance, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/month-select-plugin.ts:8
packages/web-components/src/components/date-picker/month-select-plugin.ts:9 imports flatpickr/dist/types/locale, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/month-select-plugin.ts:9
packages/web-components/src/components/date-picker/month-select-plugin.ts:10 imports flatpickr/dist/types/options, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/month-select-plugin.ts:10
packages/web-components/src/components/date-picker/range-plugin.ts:8 imports flatpickr/dist/esm/plugins/rangePlugin.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/range-plugin.ts:8
packages/web-components/src/components/date-picker/range-plugin.ts:10 imports flatpickr/dist/types/instance, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/range-plugin.ts:10
packages/web-components/src/components/date-picker/range-plugin.ts:11 imports flatpickr/dist/types/options, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/range-plugin.ts:11
packages/web-components/src/components/date-picker/shadow-dom-events-plugin.ts:8 imports flatpickr/dist/types/instance, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/shadow-dom-events-plugin.ts:8
packages/web-components/src/components/date-picker/shadow-dom-events-plugin.ts:9 imports flatpickr/dist/types/options, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/shadow-dom-events-plugin.ts:9
packages/web-components/src/components/date-picker/state-handshake-plugin.ts:8 imports flatpickr/dist/types/instance, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/state-handshake-plugin.ts:8
packages/web-components/src/components/date-picker/state-handshake-plugin.ts:9 imports flatpickr/dist/types/options, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/web-components/src/components/date-picker/state-handshake-plugin.ts:9
packages/web-components/src/components/feature-flags/index.ts:25 imports @carbon/feature-flags, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/web-components/src/components/feature-flags/index.ts:25
What to do
Fix the listed violations: import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (30 rows); declare the workspace packages these files import in the importing package's own package.json dependencies (4 rows) — those imports are already bare package specifiers, so the import statements do not change, only the manifest.
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.
ModalDialog has cyclomatic complexity 55 and cognitive complexity 50; 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. — packages/react/src/components/Modal/Modal.tsx:288
(anonymous) has cyclomatic complexity 54 and cognitive complexity 53; 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. — packages/react/src/components/Slider/Slider.tsx:348
(anonymous) has cyclomatic complexity 54 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 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. — packages/react/src/components/TextArea/TextArea.tsx:215
(anonymous) has cyclomatic complexity 51 and cognitive complexity 87; 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. — packages/react/src/components/ComboBox/ComboBox.tsx:611
_handleKeyDown has cyclomatic complexity 44 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. — packages/web-components/src/components/date-picker/next/components/date-picker.ts:641
(anonymous) has cyclomatic complexity 41 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. — packages/react/src/components/ComboBox/ComboBox.tsx:384
(anonymous) has cyclomatic complexity 40 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. — packages/react/src/components/Dropdown/Dropdown.tsx:291
(anonymous) 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. — packages/react/src/components/MultiSelect/MultiSelect.tsx:299
(anonymous) has cyclomatic complexity 37 and cognitive complexity 37; 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:594
(anonymous) has cyclomatic complexity 36 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. — packages/react/src/components/TextInput/PasswordInput.tsx:182
render has cyclomatic complexity 35 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 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. — packages/web-components/src/components/password-input/password-input.ts:140
_handleStateChange has cyclomatic complexity 34 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. — packages/web-components/src/components/date-picker/next/components/date-picker.ts:245
stateReducer has cyclomatic complexity 34 and cognitive complexity 37; 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. — packages/react/src/components/MultiSelect/FilterableMultiSelect.tsx:694
computePlacement has cyclomatic complexity 34 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — packages/web-components/src/globals/controllers/floating-controller.ts:76
(anonymous) has cyclomatic complexity 33 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. — packages/react/src/components/ComboBox/ComboBox.tsx:1179
FilterableMultiSelect has cyclomatic complexity 32 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — packages/react/src/components/MultiSelect/FilterableMultiSelect.tsx:331
_fitValue has cyclomatic complexity 32 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — packages/web-components/src/components/menu/menu.ts:344
handleKeyDown has cyclomatic complexity 30 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. — packages/react/src/components/TreeView/TreeView.tsx:178
handleKeyDown has cyclomatic complexity 30 and cognitive complexity 37; 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. — packages/react/src/components/DatePicker/next/hooks/useDatePicker.ts:487
(anonymous) has cyclomatic complexity 30 and cognitive complexity 28; 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. — packages/react/src/components/Card/CardActions.tsx:94
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files6.8 / 10Adequate✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
packages/react/src/components/DatePicker/DatePicker-test.js has 2043 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/DatePicker/DatePicker-test.js:1
packages/react/src/components/Tearsheet/Tearsheet.stories.js has 1744 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/Tearsheet/Tearsheet.stories.js:1
packages/react/src/components/ComboBox/ComboBox-test.js has 1724 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/ComboBox/ComboBox-test.js:1
packages/react/src/components/Card/Card.stories.js has 1701 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/Card/Card.stories.js:1
packages/react/src/components/Tabs/Tabs.tsx has 1666 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/Tabs/Tabs.tsx:1
packages/react/src/components/Slider/Slider.tsx has 1608 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/Slider/Slider.tsx:1
packages/react/src/components/Modal/Modal-test.js has 1601 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/Modal/Modal-test.js:1
packages/react/src/components/ComboBox/ComboBox.tsx has 1462 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/ComboBox/ComboBox.tsx:1
packages/web-components/src/components/tabs/tabs.stories.ts has 1462 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-components/src/components/tabs/tabs.stories.ts:1
packages/react/src/components/Tabs/Tabs.stories.js has 1405 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/Tabs/Tabs.stories.js:1
packages/web-components/src/components/dropdown/dropdown.ts has 1368 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-components/src/components/dropdown/dropdown.ts:1
packages/web-components/src/components/card/card.stories.ts has 1355 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-components/src/components/card/card.stories.ts:1
REDACTED has 1322 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
packages/react/src/components/Notification/Notification.tsx has 1299 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/Notification/Notification.tsx:1
packages/web-components/src/components/ui-shell/ui-shell.stories.ts has 1270 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-components/src/components/ui-shell/ui-shell.stories.ts:1
packages/react/src/components/MultiSelect/FilterableMultiSelect.tsx has 1254 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/MultiSelect/FilterableMultiSelect.tsx:1
packages/web-components/src/components/slider/slider.ts has 1213 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-components/src/components/slider/slider.ts:1
packages/web-components/src/components/multi-select/multi-select.stories.ts has 1177 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-components/src/components/multi-select/multi-select.stories.ts:1
packages/utilities/src/date-picker/primitives/actions.ts has 1166 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/utilities/src/date-picker/primitives/actions.ts:1
packages/react/src/components/ComposedModal/ComposedModal-test.js has 1139 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/ComposedModal/ComposedModal-test.js:1
packages/web-components/src/components/page-header/page-header.stories.ts has 1100 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-components/src/components/page-header/page-header.stories.ts:1
packages/web-components/src/components/side-panel/side-panel.ts has 1096 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-components/src/components/side-panel/side-panel.ts:1
packages/react/src/components/DatePicker/DatePicker.tsx has 1077 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/DatePicker/DatePicker.tsx:1
packages/web-components/src/components/date-picker/next/components/date-picker.ts has 1075 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-components/src/components/date-picker/next/components/date-picker.ts:1
packages/react/src/components/Modal/Modal.tsx has 1069 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/Modal/Modal.tsx:1
packages/react/src/components/AddSelect/AddSelect.stories.js has 1068 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/AddSelect/AddSelect.stories.js:1
packages/upgrade/src/upgrades.js has 1068 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/upgrade/src/upgrades.js:1
packages/react/src/components/PageHeader/PageHeader.stories.js has 1067 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/PageHeader/PageHeader.stories.js:1
packages/react/src/components/MultiSelect/MultiSelect.tsx has 1064 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/MultiSelect/MultiSelect.tsx:1
packages/web-components/src/components/data-table/table.ts has 1000 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-components/src/components/data-table/table.ts:1
packages/react/src/components/Tile/Tile.tsx has 999 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/Tile/Tile.tsx:1
packages/react/src/components/SidePanel/SidePanel.tsx has 977 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/SidePanel/SidePanel.tsx:1
packages/web-components/src/components/add-select/add-select.stories.ts has 969 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-components/src/components/add-select/add-select.stories.ts:1
packages/web-components/src/components/modal/modal.stories.ts has 959 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-components/src/components/modal/modal.stories.ts:1
packages/web-components/src/components/multi-select/multi-select.ts has 958 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-components/src/components/multi-select/multi-select.ts:1
packages/react/src/components/Dialog/Dialog.tsx has 933 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/Dialog/Dialog.tsx:1
packages/react/src/components/DataTable/DataTable.tsx has 925 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/DataTable/DataTable.tsx:1
packages/web-components/src/components/number-input/number-input.ts has 907 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/web-components/src/components/number-input/number-input.ts:1
packages/react/src/components/Resizer/Resizer.stories.js has 889 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/Resizer/Resizer.stories.js:1
packages/react/src/components/Dropdown/Dropdown.tsx has 850 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/react/src/components/Dropdown/Dropdown.tsx:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage7.2 / 10Strong✓ 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.
packages/web-components/tests/spec/accordion_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/accordion_spec.ts:9
packages/web-components/tests/spec/code-snippet_spec.ts:9 imports '../../src/components/code-snippet/code-snippet-story', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/code-snippet_spec.ts:9
packages/web-components/tests/spec/combo-box_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/combo-box_spec.ts:9
packages/web-components/tests/spec/content-switcher_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/content-switcher_spec.ts:9
packages/web-components/tests/spec/data-table_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/data-table_spec.ts:9
packages/web-components/tests/spec/date-picker_spec.ts:11 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/date-picker_spec.ts:11
packages/web-components/tests/spec/dropdown_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/dropdown_spec.ts:9
packages/web-components/tests/spec/file-uploader_spec.ts:12 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/file-uploader_spec.ts:12
packages/web-components/tests/spec/modal_spec.ts:8 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/modal_spec.ts:8
packages/web-components/tests/spec/multi-select_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/multi-select_spec.ts:9
packages/web-components/tests/spec/notification_spec.ts:12 imports '../../src/components/notification/inline-notification-story', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/notification_spec.ts:12
packages/web-components/tests/spec/number-input_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/number-input_spec.ts:9
packages/web-components/tests/spec/pagination_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/pagination_spec.ts:9
packages/web-components/tests/spec/progress-bar_spec.ts:9 imports '../../src/components/progress-bar/progress-bar-story', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/progress-bar_spec.ts:9
packages/web-components/tests/spec/progress-indicator_spec.ts:10 imports '../../src/components/progress-indicator/progress-indicator-story', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/progress-indicator_spec.ts:10
packages/web-components/tests/spec/radio-button_spec.ts:13 imports '../../src/components/radio-button/radio-button-story', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/radio-button_spec.ts:13
packages/web-components/tests/spec/search_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/search_spec.ts:9
packages/web-components/tests/spec/select_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/select_spec.ts:9
packages/web-components/tests/spec/slider_spec.ts:9 imports '../../src/components/slider/slider-story', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/slider_spec.ts:9
packages/web-components/tests/spec/tabs_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/tabs_spec.ts:9
packages/web-components/tests/spec/tag_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/tag_spec.ts:9
packages/web-components/tests/spec/text-input_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/text-input_spec.ts:9
packages/web-components/tests/spec/textarea_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/textarea_spec.ts:9
packages/web-components/tests/spec/tile_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/tile_spec.ts:9
packages/web-components/tests/spec/ui-shell_spec.ts:14 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/web-components/tests/spec/ui-shell_spec.ts:14
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×15) — packages/react/src/components/DatePicker/DatePicker-test.js:1, packages/react/src/components/ComboBox/ComboBox-test.js:1, packages/react/src/components/Modal/Modal-test.js:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ 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.
This repository declares test tooling, and the ✓ above records that declaration — but packages/web-components/tests/spec/accordion_spec.ts and 24 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — packages/web-components/tests/spec/accordion_spec.ts:9
Do you agree with this assessment?
R7 · Dead Code6.1 / 10Adequate✓ 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.
12 file(s) (~2725 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — actions/issues
11 file(s) (~694 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: packages/colors/src/index.ts imports '../js/generated/colors.js', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — packages/colors
8 file(s) (~851 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: packages/feature-flags/src/index.ts imports './generated/feature-flags', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — packages/feature-flags
Unreachable from the 190 application, 51 tooling and 1025 test entry point(s) detected in this repo. Gate removals on `yarn run build` — an undetected custom entry would make these reachable.
no import path from any entry point (190 application, 51 tooling, 1025 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 (×36) — packages/react/src/components/DatePicker/DatePicker-test.js, packages/react/src/components/ComboBox/ComboBox-test.js, packages/react/src/components/Modal/Modal-test.js, …
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×17) — config/jest-config-carbon/setup/setup.js:8, packages/cli/src/changelog.js:8, packages/cli/src/changelog.js:9, …
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. (×3)
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
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.
Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. Markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. This repository commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. The server controls — HTTPS enforcement, HSTS, cookie flags, 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.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. — config/jest-config-carbon/transform/cssTransform.js:76
`https://1.www.s81c.com/common/carbon-for-ibm-dotcom/tag/v1/latest/footer.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 5 such include(s) across the repository's markup. — packages/react/.storybook/manager-head.html:37
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — netlify.toml:1
What to do
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key.
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
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.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. 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 `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
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.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document3.5 / 10Weak✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`getInteractiveContent` is exported, takes a document from its caller (line 75) and hands it to `findMatchingContent`, which calls itself at line 64 (`findMatchingContent`) with a piece of `node` — and nowhere in `findMatchingContent` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `findMatchingContent` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/react/src/internal/useNoInteractiveChildren.ts:64
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
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.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. 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 `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped7.8 / 10Strong✓ 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.
`this.textContent?.trim()?`Remove ${this.textContent.trim()} tab`:'Remove tab'` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the `title` attribute of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `this.textContent?.trim()?`Remove ${this.textContent.trim()} tab`:'Remove tab'` at this site, or validate it against the shape the position accepts before interpolating it. — packages/web-components/src/components/tabs/tab.ts:202
`accessibleLabel` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the text of an element of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `accessibleLabel` at this site, or validate it against the shape the position accepts before interpolating it. — packages/web-components/src/components/tabs/tab.ts:261
`this.innerText` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the `title` attribute of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `this.innerText` at this site, or validate it against the shape the position accepts before interpolating it. — packages/web-components/src/components/data-table/table-header-cell.ts:223
`label` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the text of an element of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `label` at this site, or validate it against the shape the position accepts before interpolating it. (×2) — packages/web-components/code-connect/tooltip/tooltip.figma.ts:64, packages/web-components/code-connect/tooltip/tooltip.figma.ts:83
`content` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the text of an element of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `content` at this site, or validate it against the shape the position accepts before interpolating it. — packages/web-components/code-connect/toggletip/toggletip.figma.ts:61
`description` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the text of an element of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `description` at this site, or validate it against the shape the position accepts before interpolating it. — packages/web-components/code-connect/loading/loading.figma.ts:43
`children` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the text of an element of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `children` at this site, or validate it against the shape the position accepts before interpolating it. (×2) — packages/web-components/code-connect/code-snippet/code-snippet-inline.figma.ts:45, packages/web-components/code-connect/code-snippet/code-snippet-single.figma.ts:32
`currentItem.innerHTML.replace(/\s+/g,'')` 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. — packages/react/src/components/DatePicker/DatePicker.tsx:209
`item.innerHTML.replace(/\s+/g,'')` 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. — packages/web-components/src/components/date-picker/css-class-plugin.ts:127
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.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
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.
Do you agree with this assessment?
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.
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. (×8) — packages/web-components/tasks/build-dist.js:54, packages/web-components/src/components/resizer/defs.ts:140, packages/web-components/src/components/combo-box/combo-box.ts:299, …
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
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.
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
15/35 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
~1.5 `!` null assertions per 1k TypeScript source lines — 282 assertion(s) across the 191413 source line(s) of the 1518 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/web-components/src/components/date-picker/date-picker.ts (14), packages/web-components/src/components/code-snippet/code-snippet.ts (12), packages/web-components/src/components/date-picker/date-picker-input.ts (11). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
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).
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.
Unscored — 3 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.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 42 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AX1 Captive dependencies — Not applicable: 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; this repository's TypeScript 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 — Not applicable: 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
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
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.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, TypeScript, html not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed JavaScript surface was not measured.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.js,.jsx,.mjs,.ts,.tsx), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 31 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D4 Code Duplication — This repository's production source (.ts, .tsx) 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.
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 domain event(s); its domain events are published by services or handlers — no domain entity raises one)
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
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 data present for 419 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for 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 applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
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.
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
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
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.
AC2 · Forms & labels· <label> that labels no control · ×18
<label> that labels no control packages/react/src/components/TreeView/TreeView.tsx:291— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web-components/src/components/password-input/password-input.ts:260— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web-components/src/components/tearsheet/_story-assets/stacking-tearsheet.ts:78— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web-components/src/components/tearsheet/_story-assets/stacking-tearsheet.ts:82— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web-components/src/components/tearsheet/_story-assets/stacking-tearsheet.ts:86— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web-components/src/components/tearsheet/_story-assets/stacking-tearsheet.ts:90— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web-components/src/components/tearsheet/_story-assets/stacking-tearsheet.ts:94— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web-components/src/components/tearsheet/_story-assets/stacking-tearsheet.ts:155— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web-components/src/components/tearsheet/_story-assets/stacking-tearsheet.ts:208— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web-components/src/components/tearsheet/_story-assets/stacking-tearsheet.ts:261— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web-components/src/components/tearsheet/_story-assets/step-tearsheet-preview.ts:207— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web-components/src/components/tearsheet/_story-assets/step-tearsheet.ts:197— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web-components/src/components/tearsheet/tearsheet-helpers.ts:150— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web-components/src/components/tearsheet/tearsheet-helpers.ts:154— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web-components/src/components/tearsheet/tearsheet-helpers.ts:158— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web-components/src/components/tearsheet/tearsheet-helpers.ts:162— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web-components/src/components/tearsheet/tearsheet-helpers.ts:166— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/web-components/src/components/time-picker/time-picker.ts:244— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC2 · Forms & labels· Link with no accessible name · ×5
Link with no accessible name packages/web-components/src/components/button/button-skeleton.ts:54— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
Link with no accessible name packages/web-components/src/components/date-picker/date-picker.ts:568— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
Link with no accessible name packages/web-components/src/components/date-picker/date-picker.ts:575— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
Link with no accessible name packages/web-components/src/components/notification/actionable-notification.ts:307— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
Link with no accessible name packages/web-components/src/components/notification/actionable-notification.ts:317— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
AC2 · Forms & labels· <input> without a programmatic label · ×5
<input> without a programmatic label packages/web-components/src/components/multi-select/multi-select.ts:488— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label packages/web-components/src/components/password-input/password-input.ts:316— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label packages/web-components/src/components/slider/slider-input.ts:248— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label packages/web-components/src/components/structured-list/structured-list-row.ts:217— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label packages/web-components/src/components/time-picker/time-picker.ts:252— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
AC4 · Keyboard semantics· Click handler on a non-interactive <span> · ×3
Click handler on a non-interactive <span> packages/react/src/components/TreeView/TreeNode.tsx:587— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> packages/web-components/src/components/tree-view/tree-node.ts:331— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Click handler on a non-interactive <span> packages/web-components/src/components/tree-view/tree-node.ts:352— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×3
Click handler on a non-interactive <div> packages/web-components/src/components/date-picker/date-picker-input.ts:351— 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> packages/web-components/src/components/dialog/dialog.ts:278— 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> packages/web-components/src/components/ui-shell/side-nav.ts:249— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
D10 · Test Quality· No assertions (empty test) · ×3
No assertions (empty test): should be an ol if prop ordered is passed as true packages/web-components/src/components/accordion/__tests__/accordion-test.js:162— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): should be a ul if prop ordered is passed as false packages/web-components/src/components/accordion/__tests__/accordion-test.js:163— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): should handle revert click packages/react/src/components/AILabel/__tests__/AILabel-test.tsx:122— Test method has an empty body — it asserts nothing and exercises no code.
AC2 · Forms & labels· Custom control with no accessible name on <div> · ×2
Custom control with no accessible name on <div> packages/web-components/src/components/side-panel/side-panel.ts:1113— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> packages/web-components/src/components/ui-shell/side-nav.ts:249— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC4 · Keyboard semantics· Hover-only interaction on <div> · ×2
Hover-only interaction on <div> packages/web-components/src/components/dropdown/dropdown.ts:1343— This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus.
Hover-only interaction on <div> packages/web-components/src/components/ui-shell/side-nav.ts:252— This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus.
Orphaned knowledge packages/react/src/components/PaginationNav/PaginationNav.tsx:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/scss-generator/src/types/definitions.js:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Unlisted import '@jest/globals' config/jest-config-carbon/setup/setup.js:8— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@jest/globals' packages/react/src/components/ListBox/test-helpers.ts:10— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'typescript' packages/icon-build-helpers/src/builders/react/next.js:15— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'typescript' packages/pictograms-react/tasks/build.js:14— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
AC2 · Forms & labels· <button> with no accessible text · ×1
<button> with no accessible text packages/web-components/src/components/button/button-skeleton.ts:68— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC2 · Forms & labels· Custom control with no accessible name on <slot> · ×1
Custom control with no accessible name on <slot> packages/web-components/src/components/content-switcher/content-switcher.ts:519— This <slot> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
<html> without a lang packages/web-components/.storybook/basic-example-cdn.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC3 · Page structure· Document without a <title> · ×1
Document without a <title> packages/web-components/.storybook/basic-example-cdn.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Unlisted import '@commitlint/parse' packages/cli/src/changelog.js:8— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'execa' packages/cli/src/changelog.js:9— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'semver' packages/cli/src/commands/publish.js:10— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'rollup-plugin-strip-banner' packages/feature-flags/rollup.config.js:12— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'lodash.clonedeep' packages/icon-build-helpers/src/metadata/migrations/2020-01-27.js:14— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'react-fast-compare' packages/styles/scss/__tests__/zone-test.js:14— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'commander' packages/web-components/tools/check-license.js:12— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'fast-glob' packages/web-components/.storybook/main.ts:13— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'lit-element' packages/web-components/src/components/pagination-nav/pagination-nav.stories.ts:9— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'lit-html' packages/web-components/src/components/tearsheet/tearsheet-body.ts:15— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'postcss' packages/web-components/tasks/build-dist.js:15— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'postcss-selector-parser' packages/web-components/tools/postcss-fix-host-pseudo.js:8— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Skipped test: Should render the expando packages/web-components/tests/spec/code-snippet_spec.ts:173— Skipped — switched off by xit
Skipped test: Should change the button text by expanding/collapsing packages/web-components/tests/spec/code-snippet_spec.ts:192— Skipped — switched off by xit
Skipped test: Should highlight the item user types packages/web-components/tests/spec/combo-box_spec.ts:312— Skipped — switched off by xit
Skipped test: Should support selecting an item after typing packages/web-components/tests/spec/combo-box_spec.ts:470— Skipped — switched off by xit
Skipped test: should add/remove "selected" attribute packages/web-components/tests/spec/content-switcher_spec.ts:22— Skipped — switched off by xit
Skipped test: should provide a way to switch item with a value packages/web-components/tests/spec/content-switcher_spec.ts:50— Skipped — switched off by xit
Skipped test: should provide a way to cancel switching item packages/web-components/tests/spec/content-switcher_spec.ts:67— Skipped — switched off by xit
Skipped test: should add/remove "hide-divider" attribute packages/web-components/tests/spec/content-switcher_spec.ts:101— Skipped — switched off by xit
Skipped test: Should show the tooltip for 2 seconds by default packages/web-components/tests/spec/copy-button_spec.ts:56— Skipped — switched off by xit
Skipped test: Should support changing the duration packages/web-components/tests/spec/copy-button_spec.ts:80— Skipped — switched off by xit
Skipped test: should support setting zebra stripe to rows packages/web-components/tests/spec/data-table_spec.ts:162— Skipped — switched off by xit
Skipped test: should fire cds-table-row-change-selection event upon selecting packages/web-components/tests/spec/data-table_spec.ts:392— Skipped — switched off by xit
Skipped test: should fire cds-table-row-change-selection event upon unselecting packages/web-components/tests/spec/data-table_spec.ts:412— Skipped — switched off by xit
Skipped test: should support preventing table row selection from being toggled upon user gesture packages/web-components/tests/spec/data-table_spec.ts:433— Skipped — switched off by xit
Skipped test: should expand and collapse packages/web-components/tests/spec/data-table_spec.ts:486— Skipped — switched off by xit
Skipped test: should fire cds-table-row-expando-beingtoggled/cds-table-row-expando-toggled events upon expanding packages/web-components/tests/spec/data-table_spec.ts:510— Skipped — switched off by xit
Skipped test: should fire cds-table-row-expando-beingtoggled/cds-table-row-expando-toggled events upon collapsing packages/web-components/tests/spec/data-table_spec.ts:533— Skipped — switched off by xit
Skipped test: should support preventing table row from being toggled upon user gesture packages/web-components/tests/spec/data-table_spec.ts:556— Skipped — switched off by xit
Skipped test: Should not instantiate Flatpickr packages/web-components/tests/spec/date-picker_spec.ts:82— Skipped — switched off by xit
Skipped test: Should support opening calendar dropdown by clicking on calendar icon for the start date packages/web-components/tests/spec/date-picker_spec.ts:224— Skipped — switched off by xit
Skipped test: Should support opening calendar dropdown by clicking on calendar icon for the end date packages/web-components/tests/spec/date-picker_spec.ts:236— Skipped — switched off by xit
Skipped test: should support checking if required value exists packages/web-components/tests/spec/date-picker_spec.ts:259— Skipped — switched off by xit
Skipped test: should treat non-empty custom validity message as invalid packages/web-components/tests/spec/date-picker_spec.ts:292— Skipped — switched off by xit
Skipped test: Should respond to `formdata` event packages/web-components/tests/spec/date-picker_spec.ts:301— Skipped — switched off by xit
Skipped test: Should not respond to `formdata` event if disabled packages/web-components/tests/spec/date-picker_spec.ts:320— Skipped — switched off by xit
TodoComment packages/web-components/tests/spec/file-uploader_spec.ts:175— // TODO: See if we can get around TS2683 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/web-components/tests/spec/notification_spec.ts:85— // TODO: See if we can get around TS2683 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/web-components/tests/spec/select_spec.ts:262— // TODO: See if we can get around TS2683 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/web-components/tests/spec/tooltip_spec.ts:132— // TODO: Figure out why `spyOnProperty()` with a property name that actually exists causes a TS error — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/web-components/src/index.ts:121— // TODO: uncomment in v12 — remove from product-migrated-components.mjs too — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/web-components/src/index.ts:224— // TODO: uncomment in v12 — remove from product-migrated-components.mjs and excludeProductsComponents too — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/web-components/src/index.ts:252— // TODO: uncomment in v12 — also remove from excludeProductsComponents — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/react/src/index.ts:15— // TODO: uncomment in v12 — also remove from excludeProductsComponents — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/react/src/index.ts:25— // TODO: uncomment in v12 — also remove from excludeProductsComponents — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/react/src/index.ts:48— // TODO: uncomment in v12 — also remove from excludeProductsComponents — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/react/src/index.ts:69— // TODO: uncomment in v12 — also remove from excludeProductsComponents — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/react/src/index.ts:85— // TODO: uncomment in v12 — also remove from excludeProductsComponents — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/react/src/index.ts:97— // TODO: uncomment in v12 — also remove from excludeProductsComponents — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/react/src/index.ts:108— // TODO: uncomment in v12 — also remove from excludeProductsComponents — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/react/src/index.ts:113— // TODO: uncomment in v12 — also remove from excludeProductsComponents — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/react/src/index.ts:119— // TODO: uncomment in v12 — also remove from excludeProductsComponents — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/react/src/index.ts:611— // TODO: uncomment in v12 — also remove from excludeProductsComponents — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/react/src/index.ts:817— // TODO: uncomment in v12 — also remove from excludeProductsComponents — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/react/src/index.ts:823— // TODO: uncomment in v12 — also remove from excludeProductsComponents — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/web-components/src/globals/controllers/floating-controller.ts:254— // TODO: remove reference to slug in v12 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/web-components/src/components/toggle/toggle.ts:50— // TODO: remove in v12 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/web-components/src/components/toggle/toggle.ts:72— // TODO: remove in v12 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/web-components/src/components/toggle/toggle.ts:78— // TODO: remove in v12 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/web-components/src/components/toggle/toggle.ts:92— // TODO: remove get() and set() in v12 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/web-components/src/components/toggle/toggle.ts:115— // TODO: swap value with labelB in v12 to match React — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FunctionTooLong: Slider.Slider packages/react/src/components/Slider/Slider.tsx:348— FunctionTooLong — Slider runs 849 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 749 over it, 8.49× 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: Error403SVG.Error403SVG packages/react/src/components/FullPageError/assets/Error403SVG.tsx:15— FunctionTooLong — Error403SVG runs 809 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 709 over it, 8.09× 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: ErrorGenericSVG.ErrorGenericSVG packages/react/src/components/FullPageError/assets/ErrorGenericSVG.tsx:15— FunctionTooLong — ErrorGenericSVG runs 808 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 708 over it, 8.08× 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: Error404SVG.Error404SVG packages/react/src/components/FullPageError/assets/Error404SVG.tsx:15— FunctionTooLong — Error404SVG runs 713 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 613 over it, 7.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: FilterableMultiSelect.FilterableMultiSelect packages/react/src/components/MultiSelect/FilterableMultiSelect.tsx:331— FunctionTooLong — FilterableMultiSelect runs 615 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 515 over it, 6.15× 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: DatePicker.DatePicker packages/react/src/components/DatePicker/DatePicker.tsx:386— FunctionTooLong — DatePicker runs 443 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 343 over it, 4.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: form-demo.FormDemo packages/react/src/components/Form/stories/form-demo.js:73— FunctionTooLong — FormDemo runs 387 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 287 over it, 3.87× 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: ConditionGroupBuilder.ConditionGroupBuilder packages/react/src/components/ConditionBuilder/ConditionGroupBuilder/ConditionGroupBuilder.tsx:60— FunctionTooLong — ConditionGroupBuilder runs 378 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 278 over it, 3.78× 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: DataTable.DataTable packages/react/src/components/DataTable/DataTable.tsx:351— FunctionTooLong — DataTable runs 359 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 259 over it, 3.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: TextArea.TextArea packages/react/src/components/TextArea/TextArea.tsx:215— FunctionTooLong — TextArea runs 328 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 228 over it, 3.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.
FunctionTooLong: ibm-products-update-coachmark.transform packages/upgrade/transforms/ibm-products-update-coachmark.js:39— FunctionTooLong — transform runs 317 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 217 over it, 3.17× 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: carousel.initCarousel packages/utilities/src/carousel/carousel.ts:36— FunctionTooLong — initCarousel runs 263 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 163 over it, 2.63× 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: ConditionBlock.ConditionBlock packages/react/src/components/ConditionBuilder/ConditionBlock/ConditionBlock.tsx:71— FunctionTooLong — ConditionBlock runs 249 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 149 over it, 2.49× 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: NotificationsEmptyState.NotificationsIllustration packages/react/src/components/NotificationsPanel/NotificationsEmptyState.tsx:30— FunctionTooLong — NotificationsIllustration runs 246 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 146 over it, 2.46× 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: Menu.Menu packages/react/src/components/Menu/Menu.tsx:123— FunctionTooLong — Menu 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: ibm-products-update-page-header-composable.transform packages/upgrade/transforms/ibm-products-update-page-header-composable.js:40— FunctionTooLong — transform runs 214 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 114 over it, 2.14× 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: FloatingMenu.FloatingMenu packages/react/src/internal/FloatingMenu.tsx:237— FunctionTooLong — FloatingMenu runs 207 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 107 over it, 2.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.
FunctionTooLong: ConditionBuilderItem.ConditionBuilderItem packages/react/src/components/ConditionBuilder/ConditionBuilderItem/ConditionBuilderItem.tsx:64— FunctionTooLong — ConditionBuilderItem 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.
FunctionTooLong: ConditionBuilderContent.ConditionBuilderContent packages/react/src/components/ConditionBuilder/ConditionBuilderContent/ConditionBuilderContent.tsx:41— FunctionTooLong — ConditionBuilderContent runs 197 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 97 over it, 1.97× 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: examples.main tasks/examples.js:62— FunctionTooLong — main 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: Calendar.Calendar packages/react/src/components/DatePicker/next/components/Calendar.tsx:53— FunctionTooLong — Calendar runs 175 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× 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.TreeView packages/react/src/components/TreeView/TreeView.tsx:80— FunctionTooLong — TreeView runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× 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: ItemOptionForValueField.ItemOptionForValueField packages/react/src/components/ConditionBuilder/ConditionBuilderItem/ConditionBuilderItemOption/ItemOptionForValueField.tsx:43— FunctionTooLong — ItemOptionForValueField runs 168 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 68 over it, 1.68× 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: TearsheetWithSteps.TearsheetWithStepsInner packages/react/src/components/Tearsheet/TearsheetWithSteps.jsx:172— FunctionTooLong — TearsheetWithStepsInner runs 168 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 68 over it, 1.68× 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: useGuidebannerScroll.useGuidebannerScroll packages/react/src/components/Guidebanner/useGuidebannerScroll.ts:24— FunctionTooLong — useGuidebannerScroll runs 165 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 65 over it, 1.65× 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.
+ 25 more in this group — see findings.md.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×40
Focus outline removed in CSS without a :focus replacement packages/web-components/src/components/user-avatar/user-avatar.scss:60— `:host( -user-avatar) . __tooltip-trigger` 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 packages/web-components/src/components/ui-shell/header.scss:45— `:host( -header-nav-item)` 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 packages/web-components/src/components/ui-shell/header.scss:51— `:host( -header-menu)` 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 packages/web-components/src/components/ui-shell/header.scss:55— `:host( -header-menu-item)` 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 packages/web-components/src/components/ui-shell/header.scss:119— `:host( -header-menu-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 packages/web-components/src/components/ui-shell/side-nav.scss:30— `:host( -side-nav-link)` 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 packages/web-components/src/components/ui-shell/side-nav.scss:114— `:host( -side-nav-menu-item)` 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 packages/web-components/src/components/tree-view/tree-view.scss:41— `:host( -tree-node:focus-visible)` 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 packages/web-components/src/components/toggle-tip/toggletip.scss:28— `:host( -toggletip)` 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 packages/web-components/src/components/toggle/toggle.scss:17— `:host( -toggle)` 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 packages/web-components/src/components/tile/tile.scss:44— `:host( -clickable-tile)` 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 packages/web-components/src/components/tile/tile.scss:92— `:host( -radio-tile)` 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 packages/web-components/src/components/tile/tile.scss:105— `:host( -selectable-tile)` 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 packages/web-components/src/components/tile/tile.scss:182— `:host( -expandable-tile[with-interactive]):focus` 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 packages/web-components/src/components/tile/tile.scss:195— `:host( -expandable-tile:not([with-interactive])) . --tile__chevron` 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 packages/web-components/src/components/textarea/textarea.scss:20— `:host( -textarea)` 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 packages/web-components/src/components/text-input/text-input.scss:29— `:host( -text-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 packages/web-components/src/components/tabs/tabs.scss:293— `:host( -tab)` 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 packages/web-components/src/components/tabs/tabs.scss:485— `:host( -tab[disabled][role]) . --tabs__nav-link` 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 packages/web-components/src/components/slider/slider.scss:20— `:host( -slider)` 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 packages/web-components/src/components/select/select.scss:35— `:host( -select)` 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 packages/web-components/src/components/search/search.scss:26— `:host( -search)` 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 packages/web-components/src/components/search/search.scss:37— `:host([expandable]:focus-within) . --search-magnifier ~ . --search-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 packages/web-components/src/components/search/search.scss:42— `:host([expandable][expanded]:focus-within) . --search-magnifier` 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 packages/web-components/src/components/search/search.scss:79— `:host( -search[disabled]) . --search-close` 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.
Hotspot: packages/react/src/components/ComboBox/ComboBox.tsx packages/react/src/components/ComboBox/ComboBox.tsx:384— packages/react/src/components/ComboBox/ComboBox.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 183 in ComboBox.ComboBox at line 384. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/ComboBox/ComboBox.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/react/src/components/MultiSelect/MultiSelect.tsx packages/react/src/components/MultiSelect/MultiSelect.tsx:299— packages/react/src/components/MultiSelect/MultiSelect.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 104 in MultiSelect.MultiSelect at line 299. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/MultiSelect/MultiSelect.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/react/src/components/DatePicker/DatePicker.tsx packages/react/src/components/DatePicker/DatePicker.tsx:386— packages/react/src/components/DatePicker/DatePicker.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 121 in DatePicker.DatePicker at line 386. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/DatePicker/DatePicker.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/react/src/components/MultiSelect/FilterableMultiSelect.tsx packages/react/src/components/MultiSelect/FilterableMultiSelect.tsx:331— packages/react/src/components/MultiSelect/FilterableMultiSelect.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 118 in FilterableMultiSelect.FilterableMultiSelect at line 331. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/MultiSelect/FilterableMultiSelect.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:594— REDACTED changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 117 in NumberInput.NumberInput at line 594. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/react/src/components/Slider/Slider.tsx packages/react/src/components/Slider/Slider.tsx:348— packages/react/src/components/Slider/Slider.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 154 in Slider.Slider at line 348. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/Slider/Slider.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/react/src/components/TextArea/TextArea.tsx packages/react/src/components/TextArea/TextArea.tsx:215— packages/react/src/components/TextArea/TextArea.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 103 in TextArea.TextArea at line 215. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/TextArea/TextArea.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/react/src/components/Popover/index.tsx packages/react/src/components/Popover/index.tsx:176— packages/react/src/components/Popover/index.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 89 in index.Popover at line 176. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/Popover/index.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/react/src/components/Dropdown/Dropdown.tsx packages/react/src/components/Dropdown/Dropdown.tsx:291— packages/react/src/components/Dropdown/Dropdown.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 64 in Dropdown.Dropdown at line 291. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/Dropdown/Dropdown.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/react/src/components/ComposedModal/ComposedModal.tsx packages/react/src/components/ComposedModal/ComposedModal.tsx:298— packages/react/src/components/ComposedModal/ComposedModal.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 74 in ComposedModal.ComposedModalDialog at line 298. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/ComposedModal/ComposedModal.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/react/src/components/Tabs/Tabs.tsx packages/react/src/components/Tabs/Tabs.tsx:450— packages/react/src/components/Tabs/Tabs.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in Tabs.TabList at line 450. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/Tabs/Tabs.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/web-components/src/components/text-input/text-input.ts packages/web-components/src/components/text-input/text-input.ts:349— packages/web-components/src/components/text-input/text-input.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in CDSTextInput.render at line 349. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/web-components/src/components/text-input/text-input.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/react/src/components/Search/Search.tsx packages/react/src/components/Search/Search.tsx:131— packages/react/src/components/Search/Search.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in Search.Search at line 131. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/Search/Search.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/react/src/components/Tag/Tag.tsx packages/react/src/components/Tag/Tag.tsx:143— packages/react/src/components/Tag/Tag.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in Tag.TagBase at line 143. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/Tag/Tag.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/react/src/components/TextInput/TextInput.tsx packages/react/src/components/TextInput/TextInput.tsx:192— packages/react/src/components/TextInput/TextInput.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in TextInput.TextInput at line 192. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/TextInput/TextInput.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/web-components/src/components/password-input/password-input.ts packages/web-components/src/components/password-input/password-input.ts:140— packages/web-components/src/components/password-input/password-input.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in CDSPasswordInput.render at line 140. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/web-components/src/components/password-input/password-input.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: tasks/examples.js tasks/examples.js:62— tasks/examples.js changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in examples.main at line 62. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- tasks/examples.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/react/src/components/Card/CardActions.tsx packages/react/src/components/Card/CardActions.tsx:79— packages/react/src/components/Card/CardActions.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in CardActions.CardActions at line 79. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/Card/CardActions.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/web-components/src/components/menu/menu.ts packages/web-components/src/components/menu/menu.ts:344— packages/web-components/src/components/menu/menu.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in CDSMenu._fitValue at line 344. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/web-components/src/components/menu/menu.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/react/src/components/CodeSnippet/CodeSnippet.tsx packages/react/src/components/CodeSnippet/CodeSnippet.tsx:156— packages/react/src/components/CodeSnippet/CodeSnippet.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in CodeSnippet.CodeSnippet at line 156. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/CodeSnippet/CodeSnippet.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/react/src/components/Menu/MenuItem.tsx packages/react/src/components/Menu/MenuItem.tsx:98— packages/react/src/components/Menu/MenuItem.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in MenuItem.MenuItem at line 98. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/Menu/MenuItem.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/react/src/components/TextInput/PasswordInput.tsx packages/react/src/components/TextInput/PasswordInput.tsx:182— packages/react/src/components/TextInput/PasswordInput.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in PasswordInput.PasswordInput at line 182. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/TextInput/PasswordInput.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/react/src/components/DatePickerInput/DatePickerInput.tsx packages/react/src/components/DatePickerInput/DatePickerInput.tsx:152— packages/react/src/components/DatePickerInput/DatePickerInput.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in DatePickerInput.DatePickerInput at line 152. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/DatePickerInput/DatePickerInput.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/react/src/components/Select/Select.tsx packages/react/src/components/Select/Select.tsx:149— packages/react/src/components/Select/Select.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in Select.Select at line 149. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/Select/Select.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/web-components/src/components/number-input/number-input.ts packages/web-components/src/components/number-input/number-input.ts:833— packages/web-components/src/components/number-input/number-input.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in CDSNumberInput.render at line 833. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/web-components/src/components/number-input/number-input.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Boundary violation [package:undeclared-workspace-dep] packages/icons-vue/tasks/build.js:11— packages/icons-vue/tasks/build.js:11 imports @carbon/icon-build-helpers, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:relative-cross-package] packages/react/src/components/Coachmark/CoachmarkContentHeader.tsx:21— packages/react/src/components/Coachmark/CoachmarkContentHeader.tsx:21 reaches into another package with a relative path (../../../../utilities/src/makeDraggable) — import the package by name instead.
Boundary violation [package:third-party-deep-import] packages/react/src/components/DatePicker/DatePicker.tsx:21— packages/react/src/components/DatePicker/DatePicker.tsx:21 imports flatpickr/dist/l10n/index, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/react/src/components/DatePicker/plugins/rangePlugin.ts:8— packages/react/src/components/DatePicker/plugins/rangePlugin.ts:8 imports flatpickr/dist/plugins/rangePlugin, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:undeclared-workspace-dep] packages/react/src/components/Guidebanner/Guidebanner.tsx:11— packages/react/src/components/Guidebanner/Guidebanner.tsx:11 imports @carbon/colors, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:relative-cross-package] packages/react/src/components/Tearsheet/TearsheetWithSteps.jsx:10— packages/react/src/components/Tearsheet/TearsheetWithSteps.jsx:10 reaches into another package with a relative path (../../../../utilities-react/src/StepFlow) — import the package by name instead.
Boundary violation [package:third-party-deep-import] packages/upgrade/src/jscodeshift.js:8— packages/upgrade/src/jscodeshift.js:8 imports jscodeshift/src/Runner, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:deep-import] packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header2.input.js:6— packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header2.input.js:6 imports @carbon/web-components/lib/components/page-header/page-header-tabs.js, which the target package's package.json `exports` does not declare — use a declared entry or declare the subpath.
Boundary violation [package:third-party-deep-import] packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header2.output.js:6— packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header2.output.js:6 imports @carbon/ibm-products-web-components/lib/components/page-header/page-header-tabs.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:undeclared-workspace-dep] packages/utilities-react/src/StepFlow/StepFlow-test.js:11— packages/utilities-react/src/StepFlow/StepFlow-test.js:11 imports @carbon/react, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:third-party-deep-import] packages/web-components/src/components/date-picker/append-to-plugin.ts:8— packages/web-components/src/components/date-picker/append-to-plugin.ts:8 imports flatpickr/dist/types/instance, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/web-components/src/components/date-picker/append-to-plugin.ts:9— packages/web-components/src/components/date-picker/append-to-plugin.ts:9 imports flatpickr/dist/types/options, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/web-components/src/components/date-picker/css-class-plugin.ts:8— packages/web-components/src/components/date-picker/css-class-plugin.ts:8 imports flatpickr/dist/types/instance, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/web-components/src/components/date-picker/css-class-plugin.ts:9— packages/web-components/src/components/date-picker/css-class-plugin.ts:9 imports flatpickr/dist/types/options, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/web-components/src/components/date-picker/date-picker.ts:11— packages/web-components/src/components/date-picker/date-picker.ts:11 imports flatpickr/dist/types/instance, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/web-components/src/components/date-picker/date-picker.ts:12— packages/web-components/src/components/date-picker/date-picker.ts:12 imports flatpickr/dist/types/locale, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/web-components/src/components/date-picker/date-picker.ts:13— packages/web-components/src/components/date-picker/date-picker.ts:13 imports flatpickr/dist/types/options, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/web-components/src/components/date-picker/fix-events-plugin.ts:8— packages/web-components/src/components/date-picker/fix-events-plugin.ts:8 imports flatpickr/dist/types/instance, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/web-components/src/components/date-picker/fix-events-plugin.ts:9— packages/web-components/src/components/date-picker/fix-events-plugin.ts:9 imports flatpickr/dist/types/options, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/web-components/src/components/date-picker/focus-plugin.ts:8— packages/web-components/src/components/date-picker/focus-plugin.ts:8 imports flatpickr/dist/types/instance, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/web-components/src/components/date-picker/focus-plugin.ts:9— packages/web-components/src/components/date-picker/focus-plugin.ts:9 imports flatpickr/dist/types/options, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/web-components/src/components/date-picker/icon-plugin.ts:9— packages/web-components/src/components/date-picker/icon-plugin.ts:9 imports flatpickr/dist/types/instance, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/web-components/src/components/date-picker/icon-plugin.ts:10— packages/web-components/src/components/date-picker/icon-plugin.ts:10 imports flatpickr/dist/types/options, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/web-components/src/components/date-picker/month-select-plugin.ts:8— packages/web-components/src/components/date-picker/month-select-plugin.ts:8 imports flatpickr/dist/types/instance, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/web-components/src/components/date-picker/month-select-plugin.ts:9— packages/web-components/src/components/date-picker/month-select-plugin.ts:9 imports flatpickr/dist/types/locale, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Low coverage: packages/icon-build-helpers/src/index.js packages/icon-build-helpers/src/index.js:1— 0.0% line coverage (0/4).
Low coverage: packages/icon-build-helpers/src/tools.js packages/icon-build-helpers/src/tools.js:1— 0.0% line coverage (0/3).
Low coverage: packages/icon-build-helpers/src/builders/index.js packages/icon-build-helpers/src/builders/index.js:1— 0.0% line coverage (0/7).
Low coverage: packages/icon-build-helpers/src/builders/svg.js packages/icon-build-helpers/src/builders/svg.js:1— 0.0% line coverage (0/10).
Low coverage: packages/icon-build-helpers/src/builders/vanilla.js packages/icon-build-helpers/src/builders/vanilla.js:1— 0.0% line coverage (0/27).
Low coverage: packages/icon-build-helpers/src/builders/plugins/virtual.js packages/icon-build-helpers/src/builders/plugins/virtual.js:1— 0.0% line coverage (0/18).
Low coverage: packages/icon-build-helpers/src/builders/react/builder.js packages/icon-build-helpers/src/builders/react/builder.js:1— 0.0% line coverage (0/66).
Low coverage: packages/icon-build-helpers/src/builders/react/next.js packages/icon-build-helpers/src/builders/react/next.js:1— 0.0% line coverage (0/85).
Low coverage: packages/icon-build-helpers/src/builders/react/next/convert.js packages/icon-build-helpers/src/builders/react/next/convert.js:1— 0.0% line coverage (0/38).
Low coverage: packages/icon-build-helpers/src/builders/react/next/typescript.js packages/icon-build-helpers/src/builders/react/next/typescript.js:1— 0.0% line coverage (0/42).
Low coverage: packages/icon-build-helpers/src/builders/vue/builder.js packages/icon-build-helpers/src/builders/vue/builder.js:1— 0.0% line coverage (0/30).
Low coverage: REDACTED REDACTED:1— 0.0% line coverage (0/21).
Low coverage: packages/icon-build-helpers/src/metadata/extensions/module-info.js packages/icon-build-helpers/src/metadata/extensions/module-info.js:1— 17.1% line coverage (6/35).
Low coverage: packages/icon-build-helpers/src/metadata/extensions/module-name.js packages/icon-build-helpers/src/metadata/extensions/module-name.js:1— 23.1% line coverage (3/13).
Low coverage: packages/icon-build-helpers/src/metadata/extensions/output/optimizer.js packages/icon-build-helpers/src/metadata/extensions/output/optimizer.js:1— 32.4% line coverage (11/34).
Low coverage: packages/icon-build-helpers/src/metadata/migrations/2020-01-27.js packages/icon-build-helpers/src/metadata/migrations/2020-01-27.js:1— 0.0% line coverage (0/23).
Low coverage: packages/icon-build-helpers/src/metadata/migrations/2020-02-17-remove-usage-fields.js packages/icon-build-helpers/src/metadata/migrations/2020-02-17-remove-usage-fields.js:1— 0.0% line coverage (0/12).
Low coverage: packages/icon-build-helpers/src/metadata/migrations/2020-02-17-update-pictogram-files.js packages/icon-build-helpers/src/metadata/migrations/2020-02-17-update-pictogram-files.js:1— 0.0% line coverage (0/26).
Low coverage: packages/react/src/components/Accordion/Accordion.stories.tsx packages/react/src/components/Accordion/Accordion.stories.tsx:1— 0.0% line coverage (0/39).
Low coverage: packages/react/src/components/ActionSet/ActionSet.stories.internal.js packages/react/src/components/ActionSet/ActionSet.stories.internal.js:1— 0.0% line coverage (0/17).
Low coverage: packages/react/src/components/ActionSet/actions.js packages/react/src/components/ActionSet/actions.js:1— 0.0% line coverage (0/16).
Low coverage: packages/react/src/components/Button/__story__/fluid-button-set-args.js packages/react/src/components/Button/__story__/fluid-button-set-args.js:1— 0.0% line coverage (0/17).
Low coverage: packages/react/src/components/DatePicker/next/__stories__/DatePickerV2.stories.tsx packages/react/src/components/DatePicker/next/__stories__/DatePickerV2.stories.tsx:1— 0.0% line coverage (0/32).
Low coverage: packages/react/src/components/NotificationsPanel/UnreadNotificationBell.js packages/react/src/components/NotificationsPanel/UnreadNotificationBell.js:1— 0.0% line coverage (0/2).
Low coverage: packages/react/src/components/PageHeader/_story-assets/pageActionButtonItems.tsx packages/react/src/components/PageHeader/_story-assets/pageActionButtonItems.tsx:1— 0.0% line coverage (0/1).
+ 8 more in this group — see findings.md.
IC1 · Incompleteness & stubs· Markup wires an event to an empty handler · ×33
Markup wires an event to an empty handler packages/react/src/components/Form/stories/form-demo.js:253— `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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/enable-v12-overflowmenu-nowrap.input.js:19— `onClick` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/enable-v12-overflowmenu-nowrap.output.js:21— `onClick` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/enable-v12-overflowmenu.input.js:18— `onClick` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/enable-v12-overflowmenu.output.js:22— `onClick` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-alias.input.tsx:16— `onClose` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-alias.output.tsx:14— `onClose` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-edge-cases.input.tsx:13— `onClose` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-edge-cases.input.tsx:16— `onClose` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-edge-cases.input.tsx:43— `onClose` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-edge-cases.input.tsx:62— `onClose` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-edge-cases.input.tsx:64— `onClose` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-edge-cases.input.tsx:75— `onClose` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-edge-cases.input.tsx:87— `onClose` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-edge-cases.input.tsx:100— `onClose` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-edge-cases.input.tsx:111— `onClose` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-edge-cases.output.tsx:12— `onClose` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-edge-cases.output.tsx:24— `onClose` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-edge-cases.output.tsx:65— `onClose` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-edge-cases.output.tsx:99— `onClose` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-edge-cases.output.tsx:107— `onClose` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-edge-cases.output.tsx:130— `onClose` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-edge-cases.output.tsx:150— `onClose` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-edge-cases.output.tsx:169— `onClose` 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.
Markup wires an event to an empty handler packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet-edge-cases.output.tsx:187— `onClose` 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.
FileTooLong: Slider/Slider.tsx packages/react/src/components/Slider/Slider.tsx— FileTooLong — 1055 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: SliderProps (157-1804). The bar is 500 significant lines; this is 555 over it, 2.11× 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: Tabs/Tabs.tsx packages/react/src/components/Tabs/Tabs.tsx— FileTooLong — 1011 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 511 over it, 2.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: ComboBox/ComboBox.tsx packages/react/src/components/ComboBox/ComboBox.tsx— FileTooLong — 930 significant lines (blank, comment-only and punctuation-only lines excluded), about 76% of them inside a single declaration: ComboBox (383-1385). The bar is 500 significant lines; this is 430 over it, 1.86× 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: dropdown/dropdown.ts packages/web-components/src/components/dropdown/dropdown.ts— FileTooLong — 897 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 397 over it, 1.79× 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: slider/slider.ts packages/web-components/src/components/slider/slider.ts— FileTooLong — 850 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 350 over it, 1.70× 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: assets/Error403SVG.tsx packages/react/src/components/FullPageError/assets/Error403SVG.tsx— FileTooLong — 812 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: Error403SVG (15-825). The bar is 500 significant lines; this is 312 over it, 1.62× 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: assets/ErrorGenericSVG.tsx packages/react/src/components/FullPageError/assets/ErrorGenericSVG.tsx— FileTooLong — 811 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: ErrorGenericSVG (15-824). The bar is 500 significant lines; this is 311 over it, 1.62× 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: MultiSelect/FilterableMultiSelect.tsx packages/react/src/components/MultiSelect/FilterableMultiSelect.tsx— FileTooLong — 804 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 304 over it, 1.61× 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: src/upgrades.js packages/upgrade/src/upgrades.js— FileTooLong — 799 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 299 over it, 1.60× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 777 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 277 over it, 1.55× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: side-panel/side-panel.ts packages/web-components/src/components/side-panel/side-panel.ts— FileTooLong — 737 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: CDSSidePanel (65-1254). The bar is 500 significant lines; this is 237 over it, 1.47× 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: Notification/Notification.tsx packages/react/src/components/Notification/Notification.tsx— FileTooLong — 735 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 235 over it, 1.47× 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: assets/Error404SVG.tsx packages/react/src/components/FullPageError/assets/Error404SVG.tsx— FileTooLong — 716 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: Error404SVG (15-729). The bar is 500 significant lines; this is 216 over it, 1.43× 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: Modal/Modal.tsx packages/react/src/components/Modal/Modal.tsx— FileTooLong — 703 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 203 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: SidePanel/SidePanel.tsx packages/react/src/components/SidePanel/SidePanel.tsx— FileTooLong — 680 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: SidePanel (247-1074). The bar is 500 significant lines; this is 180 over it, 1.36× 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: MultiSelect/MultiSelect.tsx packages/react/src/components/MultiSelect/MultiSelect.tsx— FileTooLong — 666 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 166 over it, 1.33× 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: DatePicker/DatePicker.tsx packages/react/src/components/DatePicker/DatePicker.tsx— FileTooLong — 658 significant lines (blank, comment-only and punctuation-only lines excluded), about 67% of them inside a single declaration: DatePicker (386-1049). The bar is 500 significant lines; this is 158 over it, 1.32× 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: DataTable/DataTable.tsx packages/react/src/components/DataTable/DataTable.tsx— FileTooLong — 647 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 147 over it, 1.29× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: multi-select/multi-select.ts packages/web-components/src/components/multi-select/multi-select.ts— FileTooLong — 644 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: CDSMultiSelect (49-1071). The bar is 500 significant lines; this is 144 over it, 1.29× 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: primitives/actions.ts packages/utilities/src/date-picker/primitives/actions.ts— FileTooLong — 632 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: actions (31-1217). The bar is 500 significant lines; this is 132 over it, 1.26× 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: Tile/Tile.tsx packages/react/src/components/Tile/Tile.tsx— FileTooLong — 596 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 96 over it, 1.19× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: components/date-picker.ts packages/web-components/src/components/date-picker/next/components/date-picker.ts— FileTooLong — 571 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 71 over it, 1.14× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: number-input/number-input.ts packages/web-components/src/components/number-input/number-input.ts— FileTooLong — 568 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: CDSNumberInput (55-1033). The bar is 500 significant lines; this is 68 over it, 1.14× 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: NotificationsPanel/NotificationsPanel.tsx packages/react/src/components/NotificationsPanel/NotificationsPanel.tsx— FileTooLong — 537 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 37 over it, 1.07× 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: data-table/table.ts packages/web-components/src/components/data-table/table.ts— FileTooLong — 532 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: CDSTable (58-1139). The bar is 500 significant lines; this is 32 over it, 1.06× 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.
No assertions: should fire cancel click event packages/web-components/src/components/data-table/__tests__/table-batch-actions-test.js:34— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should fire select all click event when select all button is rendered packages/web-components/src/components/data-table/__tests__/table-batch-actions-test.js:47— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should fire content change event on slot change packages/web-components/src/components/data-table/__tests__/table-body-test.js:17— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render packages/web-components/src/components/accordion/__tests__/accordion-test.js:27— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: adds additional props to the containing node packages/react/src/components/UserAvatar/__tests__/UserAvatar-test.js:48— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: renders packages/react/src/components/TruncatedText/__tests__/TruncatedText-test.js:44— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: expands and collapses with mouse packages/react/src/components/TruncatedText/__tests__/TruncatedText-test.js:54— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render without errors when composed with ToggletipButton, ToggletipContent, ToggletipActions packages/react/src/components/Toggletip/__tests__/Toggletip-test.js:228— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: adds additional props to the containing node packages/react/src/components/TagOverflow/__tests__/TagOverflow-test.js:55— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: renders all as visible tags when space is available packages/react/src/components/TagOverflow/__tests__/TagOverflow-test.js:74— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should be able to click on a selected row packages/react/src/components/StructuredList/__tests__/StructuredList-test.js:275— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: adds additional properties to the containing node packages/react/src/components/SidePanel/SidePanel-test.js:483— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: removes event listeners on unmount packages/react/src/components/Resizer/__tests__/Resizer-test.js:129— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: renders children packages/react/src/components/OptionsTile/__tests__/OptionsTile-test.js:88— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: adds additional props to the containing node packages/react/src/components/OptionsTile/__tests__/OptionsTile-test.js:98— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: renders children packages/react/src/components/Guidebanner/__tests__/Guidebanner-test.js:75— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: adds additional props to the containing node packages/react/src/components/Guidebanner/__tests__/Guidebanner-test.js:86— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: renders EditInPlace packages/react/src/components/EditInPlace/__tests__/EditInPlace-test.js:33— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: handles keydown packages/react/src/components/EditInPlace/__tests__/EditInPlace-test.js:219— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: adds additional properties to the containing node packages/react/src/components/EditInPlace/__tests__/EditInPlace-test.js:277— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: renders one action button packages/react/src/components/ActionSet/__tests__/ActionSet-test.js:48— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: adds additional properties to an action button packages/react/src/components/ActionSet/__tests__/ActionSet-test.js:140— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: adds additional properties to the containing node packages/react/src/components/ActionSet/__tests__/ActionSet-test.js:156— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: renders without crashing packages/react/examples/react-router-vite/src/App-test.js:5— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: renders without crashing packages/react/examples/react-router/src/App-test.js:5— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
Low cohesion: CDSCheckbox (LCOM4 6) packages/web-components/src/components/checkbox/checkbox.ts:29— CDSCheckbox's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSTableRow (LCOM4 6) packages/web-components/src/components/data-table/table-row.ts:43— CDSTableRow's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSSelect (LCOM4 6) packages/web-components/src/components/select/select.ts:34— CDSSelect's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSSideNavMenu (LCOM4 6) packages/web-components/src/components/ui-shell/side-nav-menu.ts:35— CDSSideNavMenu's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSRadioButtonGroup (LCOM4 5) packages/web-components/src/components/radio-button/radio-button-group.ts:35— CDSRadioButtonGroup's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSContainedListItem (LCOM4 5) packages/web-components/src/components/contained-list/contained-list-item.ts:24— CDSContainedListItem's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSDatePickerInput (LCOM4 5) packages/web-components/src/components/date-picker/date-picker-input.ts:30— CDSDatePickerInput's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSModal (LCOM4 5) packages/web-components/src/components/modal/modal.ts:31— CDSModal's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSActionableNotification (LCOM4 5) packages/web-components/src/components/notification/actionable-notification.ts:92— CDSActionableNotification's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSTreeView (LCOM4 5) packages/web-components/src/components/tree-view/tree-view.ts:25— CDSTreeView's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSDatePickerInput (LCOM4 5) packages/web-components/src/components/date-picker/next/components/date-picker-input.ts:33— CDSDatePickerInput's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSTag (LCOM4 4) packages/web-components/src/components/tag/tag.ts:28— CDSTag's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSTooltip (LCOM4 4) packages/web-components/src/components/tooltip/tooltip.ts:25— CDSTooltip's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSOverflowMenuBody (LCOM4 4) packages/web-components/src/components/overflow-menu/overflow-menu-body.ts:46— CDSOverflowMenuBody's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSAddSelectColumn (LCOM4 4) packages/web-components/src/components/add-select/add-select-column.ts:32— CDSAddSelectColumn's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSmenuItemSelectable (LCOM4 4) packages/web-components/src/components/menu/menu-item-selectable.ts:20— CDSmenuItemSelectable's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSDropdownItem (LCOM4 4) packages/web-components/src/components/dropdown/dropdown-item.ts:23— CDSDropdownItem's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSModalBase (LCOM4 4) packages/web-components/src/components/modal/modal-base.ts:19— CDSModalBase's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSDialog (LCOM4 4) packages/web-components/src/components/dialog/dialog.ts:28— CDSDialog's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSTab (LCOM4 4) packages/web-components/src/components/tabs/tab.ts:32— CDSTab's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSExpandableTile (LCOM4 4) packages/web-components/src/components/tile/expandable-tile.ts:31— CDSExpandableTile's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSHeaderMenu (LCOM4 4) packages/web-components/src/components/ui-shell/header-menu.ts:31— CDSHeaderMenu's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSTimePicker (LCOM4 4) packages/web-components/src/components/time-picker/time-picker.ts:29— CDSTimePicker's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSTimePickerSelect (LCOM4 4) packages/web-components/src/components/time-picker/time-picker-select.ts:26— CDSTimePickerSelect's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CDSOptionsTile (LCOM4 4) packages/web-components/src/components/options-tile/options-tile.ts:34— CDSOptionsTile's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
R4 · Test Coverage· This test file cannot be loaded · ×25
This test file cannot be loaded packages/web-components/tests/spec/accordion_spec.ts:9— packages/web-components/tests/spec/accordion_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/code-snippet_spec.ts:9— packages/web-components/tests/spec/code-snippet_spec.ts:9 imports '../../src/components/code-snippet/code-snippet-story', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/combo-box_spec.ts:9— packages/web-components/tests/spec/combo-box_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/content-switcher_spec.ts:9— packages/web-components/tests/spec/content-switcher_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/data-table_spec.ts:9— packages/web-components/tests/spec/data-table_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/date-picker_spec.ts:11— packages/web-components/tests/spec/date-picker_spec.ts:11 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/dropdown_spec.ts:9— packages/web-components/tests/spec/dropdown_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/file-uploader_spec.ts:12— packages/web-components/tests/spec/file-uploader_spec.ts:12 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/modal_spec.ts:8— packages/web-components/tests/spec/modal_spec.ts:8 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/multi-select_spec.ts:9— packages/web-components/tests/spec/multi-select_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/notification_spec.ts:12— packages/web-components/tests/spec/notification_spec.ts:12 imports '../../src/components/notification/inline-notification-story', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/number-input_spec.ts:9— packages/web-components/tests/spec/number-input_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/pagination_spec.ts:9— packages/web-components/tests/spec/pagination_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/progress-bar_spec.ts:9— packages/web-components/tests/spec/progress-bar_spec.ts:9 imports '../../src/components/progress-bar/progress-bar-story', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/progress-indicator_spec.ts:10— packages/web-components/tests/spec/progress-indicator_spec.ts:10 imports '../../src/components/progress-indicator/progress-indicator-story', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/radio-button_spec.ts:13— packages/web-components/tests/spec/radio-button_spec.ts:13 imports '../../src/components/radio-button/radio-button-story', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/search_spec.ts:9— packages/web-components/tests/spec/search_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/select_spec.ts:9— packages/web-components/tests/spec/select_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/slider_spec.ts:9— packages/web-components/tests/spec/slider_spec.ts:9 imports '../../src/components/slider/slider-story', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/tabs_spec.ts:9— packages/web-components/tests/spec/tabs_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/tag_spec.ts:9— packages/web-components/tests/spec/tag_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/text-input_spec.ts:9— packages/web-components/tests/spec/text-input_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/textarea_spec.ts:9— packages/web-components/tests/spec/textarea_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/tile_spec.ts:9— packages/web-components/tests/spec/tile_spec.ts:9 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/web-components/tests/spec/ui-shell_spec.ts:14— packages/web-components/tests/spec/ui-shell_spec.ts:14 imports '../utils/event-manager', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
MethodTooLong: CDSTextInput.render packages/web-components/src/components/text-input/text-input.ts:349— MethodTooLong — render runs 208 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 108 over it, 2.08× 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: CDSPasswordInput.render packages/web-components/src/components/password-input/password-input.ts:140— MethodTooLong — render runs 192 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 92 over it, 1.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: StackingTearsheetDemo.render packages/web-components/src/components/tearsheet/_story-assets/stacking-tearsheet.ts:74— MethodTooLong — render runs 191 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 91 over it, 1.91× 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: CDSSidePanel.render packages/web-components/src/components/side-panel/side-panel.ts:924— MethodTooLong — render 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.
MethodTooLong: CDSNumberInput.render packages/web-components/src/components/number-input/number-input.ts:833— MethodTooLong — render runs 162 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 62 over it, 1.62× 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: CDSButton.render packages/web-components/src/components/button/button.ts:268— MethodTooLong — render runs 149 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× 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: FloatingController.computePlacement packages/web-components/src/globals/controllers/floating-controller.ts:76— MethodTooLong — computePlacement runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× 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: CDSAddSelectRow.render packages/web-components/src/components/add-select/add-select-row.ts:239— MethodTooLong — render runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× 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: CDSPagination.render packages/web-components/src/components/pagination/pagination.ts:426— MethodTooLong — render runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× 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: CDSSelect.render packages/web-components/src/components/select/select.ts:414— MethodTooLong — render runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× 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: StepFullPage.render packages/web-components/src/utilities/step-flow/_story-assets/step-full-page.ts:95— MethodTooLong — render runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× 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: CDSTearsheetHeaderContent.render packages/web-components/src/components/tearsheet/tearsheet-header-content.ts:379— MethodTooLong — render runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× 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: CDSPageHeaderTagsSet.render packages/web-components/src/components/page-header/page-header-tags-set/page-header-tags-set.ts:172— MethodTooLong — render runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× 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: CDSAddSelectBody.render packages/web-components/src/components/add-select/add-select-body.ts:277— MethodTooLong — render runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× 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: StepTearsheet.render packages/web-components/src/utilities/step-flow/_story-assets/step-tearsheet.ts:101— MethodTooLong — render runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× 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: CDSAddSelectSelectionSummaryItem.render packages/web-components/src/components/add-select/add-select-selection-summary-item.ts:166— MethodTooLong — render runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× 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: StepSidePanel.render packages/web-components/src/utilities/step-flow/_story-assets/step-side-panel.ts:100— MethodTooLong — render runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× 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: CDSTreeNode.render packages/web-components/src/components/tree-view/tree-node.ts:258— MethodTooLong — render runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× 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: CDSDatePickerInput.render packages/web-components/src/components/date-picker/next/components/date-picker-input.ts:300— MethodTooLong — render 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: CDSTextarea.render packages/web-components/src/components/textarea/textarea.ts:170— MethodTooLong — render 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: CDSCodeSnippet.render packages/web-components/src/components/code-snippet/code-snippet.ts:372— MethodTooLong — render 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.
ClassTooLong: SliderProps packages/react/src/components/Slider/Slider.tsx:157— ClassTooLong — 943 significant lines (blank, comment-only and punctuation-only lines excluded), 0 methods. The bar is 400 significant lines; this is 543 over it, 2.36× 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: Error403SVG packages/react/src/components/FullPageError/assets/Error403SVG.tsx:1— ClassTooLong — 809 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 409 over it, 2.02× 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: ErrorGenericSVG packages/react/src/components/FullPageError/assets/ErrorGenericSVG.tsx:1— ClassTooLong — 808 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 408 over it, 2.02× 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: Error404SVG packages/react/src/components/FullPageError/assets/Error404SVG.tsx:1— ClassTooLong — 713 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 313 over it, 1.78× 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: ComboBox packages/react/src/components/ComboBox/ComboBox.tsx:1— ClassTooLong — 706 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 306 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.
ClassTooLong: CDSSidePanel packages/web-components/src/components/side-panel/side-panel.ts:64— ClassTooLong — 705 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 400 significant lines; this is 305 over it, 1.76× 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: CDSMultiSelect packages/web-components/src/components/multi-select/multi-select.ts:48— ClassTooLong — 619 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 219 over it, 1.55× 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: actions packages/utilities/src/date-picker/primitives/actions.ts:1— ClassTooLong — 606 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 206 over it, 1.52× 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: SidePanel packages/react/src/components/SidePanel/SidePanel.tsx:1— ClassTooLong — 603 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 203 over it, 1.51× 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: CDSNumberInput packages/web-components/src/components/number-input/number-input.ts:54— ClassTooLong — 543 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 143 over it, 1.36× 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: CDSTable packages/web-components/src/components/data-table/table.ts:57— ClassTooLong — 510 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 110 over it, 1.28× 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: CDSTabs packages/web-components/src/components/tabs/tabs.ts:51— ClassTooLong — 445 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 45 over it, 1.11× 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: DatePicker packages/react/src/components/DatePicker/DatePicker.tsx:1— ClassTooLong — 443 significant lines (blank, comment-only and punctuation-only lines excluded), 8 methods. The bar is 400 significant lines; this is 43 over it, 1.11× 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: CDSComboBox packages/web-components/src/components/combo-box/combo-box.ts:43— ClassTooLong — 413 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 13 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.
ClassTooLong: CDSOverflowMenu packages/web-components/src/components/overflow-menu/overflow-menu.ts:64— ClassTooLong — 409 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 9 over it, 1.02× 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.
R4 · Test Coverage· No test reaches this file · ×15
No test reaches this file packages/react/src/components/DatePicker/DatePicker-test.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/react/src/components/ComboBox/ComboBox-test.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/react/src/components/Modal/Modal-test.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/react/src/components/ComposedModal/ComposedModal-test.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/upgrade/src/upgrades.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/react/src/components/TextArea/TextArea-test.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/react/src/components/Tile/Tile-test.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/react/src/components/PageHeaderDeprecated/PageHeader-test.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/react/src/components/SidePanel/SidePanel-test.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/react/src/components/TreeView/TreeView-test.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/utilities/src/overflowHandler/overflowHandler-test.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/react/src/components/Loading/Loading-test.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file tasks/prepare-v12-storybook.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/react/src/components/Menu/Menu-test.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
Repeated repair: packages/react/src/components/MultiSelect/__tests__/MultiSelect-test.js packages/react/src/components/MultiSelect/__tests__/MultiSelect-test.js:1409— packages/react/src/components/MultiSelect/__tests__/MultiSelect-test.js changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is (anonymous) at line 1409), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(MultiSelect): keep highlight and selection in sync with custom sortItems (#23821)”; “fix(MultiSelect): omit empty aria-activedescendant on the toggle button (#23819)”; “fix(Dropdown): Cap floating menu height via availableHeight on flip (#20696) (#23389)”; “fix(react): warn for interactive labels in v11 (#23391)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/MultiSelect/__tests__/MultiSelect-test.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/react/src/components/DatePicker/DatePicker-test.js packages/react/src/components/DatePicker/DatePicker-test.js:1496— packages/react/src/components/DatePicker/DatePicker-test.js changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is DatePickerExample at line 1496), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(DatePicker): call onChange for typed dates (#23165)”; “fix(react): warn for interactive labels in v11 (#23391)”; “fix: sync DatePicker month on controlled value update (#23239)”; “fix(a11y): prevent nested interactive decorators (#22751)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/DatePicker/DatePicker-test.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/react/src/components/Slider/__tests__/Slider-test.js packages/react/src/components/Slider/__tests__/Slider-test.js:70— packages/react/src/components/Slider/__tests__/Slider-test.js changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is createDOMRect at line 70), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: added forward ref to slider (#23799)”; “fix(react): warn for interactive labels in v11 (#23391)”; “fix(a11y): prevent nested interactive decorators (#22751)”; “fix(ci): configure test job/workflow to fix OOM in runners (#23101)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/Slider/__tests__/Slider-test.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/react/src/components/MultiSelect/__tests__/FilterableMultiSelect-test.js packages/react/src/components/MultiSelect/__tests__/FilterableMultiSelect-test.js:679— packages/react/src/components/MultiSelect/__tests__/FilterableMultiSelect-test.js changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is customCompareItems at line 679), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(filterable-multiselect): scope internal ids per instance (#23342)”; “fix(Dropdown): Cap floating menu height via availableHeight on flip (#20696) (#23389)”; “fix(react): warn for interactive labels in v11 (#23391)”; “fix(a11y): prevent nested interactive decorators (#22751)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/MultiSelect/__tests__/FilterableMultiSelect-test.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/react/src/components/Search/Search-test.js packages/react/src/components/Search/Search-test.js:88— packages/react/src/components/Search/Search-test.js changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is (anonymous) at line 88), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(Search): apply tabIndex to the collapsed expandable search button (#23580)”; “fix(react): warn for interactive labels in v11 (#23391)”; “fix(a11y): prevent nested interactive decorators (#22751)”; “fix(search): prevent disabled expandable search from expanding (#23172)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/Search/Search-test.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/react/src/components/IconButton/index.tsx packages/react/src/components/IconButton/index.tsx:160— packages/react/src/components/IconButton/index.tsx changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is index.IconButton at line 160), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(IconButton): support danger tertiary kind (#23582)”; “fix/(OverflowMenu): surface icon button props in featureflag enable-v12-overflowmenu (#22966)”; “fix(react): resolve display-name eslint suppressions (#23188)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/IconButton/index.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/web-components/src/components/text-input/__tests__/text-input-test.js packages/web-components/src/components/text-input/__tests__/text-input-test.js:13— packages/web-components/src/components/text-input/__tests__/text-input-test.js changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is (anonymous) at line 13), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(TextInput): prevent invalid/warn when readonly or disabled (#20733) (#23765)”; “fix(text-input): associate label and describe input with helper text (#22858)”; “fix(cds-text-input): re-dispatch change event on host element (#22798)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/web-components/src/components/text-input/__tests__/text-input-test.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/react/src/components/Dropdown/__tests__/Dropdown-test.js packages/react/src/components/Dropdown/__tests__/Dropdown-test.js:774— packages/react/src/components/Dropdown/__tests__/Dropdown-test.js changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is (anonymous) at line 774), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(Dropdown): Cap floating menu height via availableHeight on flip (#20696) (#23389)”; “fix(react): warn for interactive labels in v11 (#23391)”; “fix(a11y): prevent nested interactive decorators (#22751)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/Dropdown/__tests__/Dropdown-test.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/react/src/components/OverflowMenu/next/index.tsx packages/react/src/components/OverflowMenu/next/index.tsx:137— packages/react/src/components/OverflowMenu/next/index.tsx changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is index.OverflowMenu at line 137), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix/(OverflowMenu): surface icon button props in featureflag enable-v12-overflowmenu (#22966)”; “fix(react): resolve display-name eslint suppressions (#23206)”; “fix(OverflowMenu): export v12 prop types and extend div props (#23148)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/OverflowMenu/next/index.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/react/src/components/ComboBox/ComboBox-test.js packages/react/src/components/ComboBox/ComboBox-test.js:40— packages/react/src/components/ComboBox/ComboBox-test.js changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is ControlledComboBox at line 40), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(combobox): highlight selected item when the menu opens (#23704)”; “fix(react): warn for interactive labels in v11 (#23391)”; “fix(a11y): prevent nested interactive decorators (#22751)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/ComboBox/ComboBox-test.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/react/src/components/Tile/Tile-test.js packages/react/src/components/Tile/Tile-test.js:677— packages/react/src/components/Tile/Tile-test.js changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is checkExpandedState at line 677), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(react): warn for interactive labels in v11 (#23391)”; “fix(a11y): prevent nested interactive decorators (#22751)”; “fix(SelectableTile): remove hardcoded default title prop value (#22749)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 14:03:29 +00:00' --until='2026-10-29 14:03:29 +00:00' --full-history --no-merges -- packages/react/src/components/Tile/Tile-test.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
X24 · Document value interpolated into markup unescaped· Document value reaches a markup attribute unescaped · ×9
Document value reaches a markup attribute unescaped packages/web-components/src/components/tabs/tab.ts:202— `this.textContent?.trim()?`Remove ${this.textContent.trim()} tab`:'Remove tab'` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the `title` attribute of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `this.textContent?.trim()?`Remove ${this.textContent.trim()} tab`:'Remove tab'` at this site, or validate it against the shape the position accepts before interpolating it.
Document value reaches a markup attribute unescaped packages/web-components/src/components/tabs/tab.ts:261— `accessibleLabel` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the text of an element of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `accessibleLabel` at this site, or validate it against the shape the position accepts before interpolating it.
Document value reaches a markup attribute unescaped packages/web-components/src/components/data-table/table-header-cell.ts:223— `this.innerText` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the `title` attribute of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `this.innerText` at this site, or validate it against the shape the position accepts before interpolating it.
Document value reaches a markup attribute unescaped packages/web-components/code-connect/tooltip/tooltip.figma.ts:64— `label` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the text of an element of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `label` at this site, or validate it against the shape the position accepts before interpolating it.
Document value reaches a markup attribute unescaped packages/web-components/code-connect/tooltip/tooltip.figma.ts:83— `label` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the text of an element of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `label` at this site, or validate it against the shape the position accepts before interpolating it.
Document value reaches a markup attribute unescaped packages/web-components/code-connect/toggletip/toggletip.figma.ts:61— `content` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the text of an element of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `content` at this site, or validate it against the shape the position accepts before interpolating it.
Document value reaches a markup attribute unescaped packages/web-components/code-connect/loading/loading.figma.ts:43— `description` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the text of an element of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `description` at this site, or validate it against the shape the position accepts before interpolating it.
Document value reaches a markup attribute unescaped packages/web-components/code-connect/code-snippet/code-snippet-inline.figma.ts:45— `children` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the text of an element of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `children` at this site, or validate it against the shape the position accepts before interpolating it.
Document value reaches a markup attribute unescaped packages/web-components/code-connect/code-snippet/code-snippet-single.figma.ts:32— `children` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the text of an element of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `children` at this site, or validate it against the shape the position accepts before interpolating it.
Swallowed exception (empty catch) packages/web-components/tasks/build-dist.js:54— 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) packages/web-components/src/components/resizer/defs.ts:140— 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) packages/web-components/src/components/combo-box/combo-box.ts:299— 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) packages/web-components/src/components/combo-box/combo-box.ts:418— 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) packages/web-components/src/components/combo-box/combo-box.ts:613— 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) packages/upgrade/transforms/wc-report-non-barrel-imports.js:136— 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) packages/react/src/components/FileUploader/FileUploaderDropContainer.tsx:218— 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) packages/react/.storybook/main.ts:114— 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.
Fake-async — async method never awaits actions/validate-pr-template/index.js:155— `validateHeadings` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits actions/validate-pr-template/index.js:182— `validateChecklistItems` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/cli/src/cli.js:40— `main` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/cli/src/commands/bundle/tsdown.js:116— `emitDeclarations` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/icon-build-helpers/src/builders/react/next/typescript.js:88— `writeTsDefinitions` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/icon-build-helpers/src/metadata/adapters/memory.js:37— `write` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/pictograms-react/tasks/build.js:53— `compileIconComponent` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Off the main sequence: @carbon/colors — @carbon/colors: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: @carbon/feature-flags — @carbon/feature-flags: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: @carbon/icon-helpers — @carbon/icon-helpers: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: @carbon/layout — @carbon/layout: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: @carbon/motion — @carbon/motion: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Dead file (~275 LoC) packages/upgrade/transforms/__testfixtures__/enable-v12-structured-list-visible-icons.input.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~275 LoC) packages/upgrade/transforms/__testfixtures__/enable-v12-structured-list-visible-icons.input.tsx— no import path from any entry point (190 application, 51 tooling, 1025 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 (~275 LoC) packages/upgrade/transforms/__testfixtures__/enable-v12-structured-list-visible-icons.output.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~275 LoC) packages/upgrade/transforms/__testfixtures__/enable-v12-structured-list-visible-icons.output.tsx— no import path from any entry point (190 application, 51 tooling, 1025 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
D10 · Test Quality· Fixed-sleep synchronisation · ×3
Fixed-sleep synchronisation: should close menu when a menu item is clicked packages/web-components/src/components/overflow-menu/__tests__/overflow-menu-test.js:320— This test starts work it did not wait for (`menuBody`, still running when the sleep starts) and then orders itself against it with `new Promise((r) => setTimeout(r, 0))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: should close the root menu when the managed menu emits a close event packages/web-components/src/components/overflow-menu/__tests__/overflow-menu-test.js:652— This test starts work it did not wait for (`el`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => {
setTimeout(resolve, 0);
})` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: should close when opened from the trigger and the menu emits focusout close packages/web-components/src/components/overflow-menu/__tests__/overflow-menu-test.js:752— This test starts work it did not wait for (`el`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => {
setTimeout(resolve, 0);
})` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Change coupling: ControlledPasswordInput.tsx ↔ PasswordInput.tsx packages/react/src/components/TextInput/ControlledPasswordInput.tsx:1— `packages/react/src/components/TextInput/ControlledPasswordInput.tsx` and `packages/react/src/components/TextInput/PasswordInput.tsx` change together 61% of the time (14 of the 23 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `6898a87e` fix: ignore empty helperText across form controls (#21995); `7ab92488` fix: modify show condition for `labelText` and `helperText` (#21094); `8f5ff43e` refactor: update forwardRef components to use generics (#21316) — run `git show` on any of them.
Change coupling: FilterableMultiSelect.tsx ↔ MultiSelect.tsx packages/react/src/components/MultiSelect/FilterableMultiSelect.tsx:1— `packages/react/src/components/MultiSelect/FilterableMultiSelect.tsx` and `packages/react/src/components/MultiSelect/MultiSelect.tsx` change together 53% of the time (35 of the 66 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 35 shared commits counted here, the most recent 3 are `84a093c9` fix(Dropdown): Cap floating menu height via availableHeight on flip (…; `30a1e032` refactor: unify disabled item checks in dropdowns (#22204); `aa1c85a3` refactor: extract MultiSelect select-all item helper for reuse (#22206) — run `git show` on any of them.
Change coupling: CheckboxGroup.tsx ↔ RadioButtonGroup.tsx packages/react/src/components/CheckboxGroup/CheckboxGroup.tsx:1— `packages/react/src/components/CheckboxGroup/CheckboxGroup.tsx` and `packages/react/src/components/RadioButtonGroup/RadioButtonGroup.tsx` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `6898a87e` fix: ignore empty helperText across form controls (#21995); `7ab92488` fix: modify show condition for `labelText` and `helperText` (#21094); `b78a6bda` fix: let decorator accept any component instead of ailabel (#20525) — run `git show` on any of them.
R10 · Code Duplication· Duplicated block with local edits (60 matched lines × 2 locations) · ×3
Duplicated block with local edits (60 matched lines × 2 locations) packages/react/code-connect/MultiSelect/FilterableMultiSelect.figma.ts:14— packages/react/code-connect/MultiSelect/FilterableMultiSelect.figma.ts:14 · packages/react/code-connect/MultiSelect/MultiSelect.figma.ts:14 — the two spans are one implementation copied and then locally edited — 294 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 (60 matched lines × 2 locations) packages/react/src/components/Tag/OperationalTag.tsx:102— packages/react/src/components/Tag/OperationalTag.tsx:102 · packages/react/src/components/Tag/SelectableTag.tsx:114 — the two spans are one implementation copied and then locally edited — 318 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 (60 matched lines × 2 locations) packages/web-components/src/components/checkbox/checkbox-group.ts:167— packages/web-components/src/components/checkbox/checkbox-group.ts:167 · packages/web-components/src/components/checkbox/checkbox.ts:248 — the two spans are one implementation copied and then locally edited — 240 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.
AC2 · Forms & labels· <fieldset> without a <legend> · ×2
<fieldset> without a <legend> packages/web-components/src/components/radio-button/radio-button-group.ts:296— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> packages/web-components/src/components/tile/tile-group.ts:268— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
SidePanel.SidePanel::renderHeader (cyclomatic 31) packages/react/src/components/SidePanel/SidePanel.tsx:848— SidePanel.SidePanel::renderHeader has cyclomatic complexity 31 (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 (SidePanel.SidePanel::checkSetDoAnimateTitle) 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.
SidePanel.SidePanel::checkSetDoAnimateTitle (cyclomatic 16) packages/react/src/components/SidePanel/SidePanel.tsx:551— SidePanel.SidePanel::checkSetDoAnimateTitle has cyclomatic complexity 16 (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 (SidePanel.SidePanel::renderHeader) 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.
TreeView.TreeView::handleKeyDown (cognitive 38) packages/react/src/components/TreeView/TreeView.tsx:178— TreeView.TreeView::handleKeyDown has cognitive complexity 38 (threshold 15). Drivers by points: if/else 12 (23 pts), loops 2 (6 pts), boolean chains 5, ternaries 1 (4 pts) (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 (TreeView.TreeView::handleTreeSelect) 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.
TreeView.TreeView::handleTreeSelect (cognitive 16) packages/react/src/components/TreeView/TreeView.tsx:138— TreeView.TreeView::handleTreeSelect has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (TreeView.TreeView::handleKeyDown) 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.
TooManyMethods: CDSDropdown packages/web-components/src/components/dropdown/dropdown.ts:67— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× 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: CDSSidePanel packages/web-components/src/components/side-panel/side-panel.ts:64— 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.
Sync-over-async blocking packages/cli/src/commands/inline.js:48— `fs.existsSync` in `inlineSassDependencies` 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 packages/upgrade/src/workspace.js:110— `fs.existsSync` in `loadWorkspace` 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.
R10 · Code Duplication· Duplicated block with local edits (52 matched lines × 2 locations) · ×2
Duplicated block with local edits (52 matched lines × 2 locations) packages/react/src/components/AddSelect/AddSelectBody.tsx:206— packages/react/src/components/AddSelect/AddSelectBody.tsx:206 · packages/web-components/src/components/add-select/add-select-body.ts:140 — the two spans are one implementation copied and then locally edited — 185 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 (52 matched lines × 2 locations) packages/web-components/code-connect/slider/slider-two-handles.figma.ts:18— packages/web-components/code-connect/slider/slider-two-handles.figma.ts:18 · packages/web-components/code-connect/slider/slider.figma.ts:18 — the two spans are one implementation copied and then locally edited — 263 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.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×2
Untrusted text written into markup unescaped packages/react/src/components/DatePicker/DatePicker.tsx:209— `currentItem.innerHTML.replace(/\s+/g,'')` 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 packages/web-components/src/components/date-picker/css-class-plugin.ts:127— `item.innerHTML.replace(/\s+/g,'')` 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.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark packages/web-components/.storybook/basic-example-cdn.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC3 · Page structure· Heading level jumps from h2 to h4 · ×1
Heading level jumps from h2 to h4 packages/web-components/src/components/tearsheet/tearsheet-helpers.ts:173— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC4 · Keyboard semantics· Anchor without href · ×1
Anchor without href packages/web-components/.storybook/templates/with-feature-flags.ts:32— 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.
AC4 · Keyboard semantics· Modal dialog does not manage focus · ×1
Modal dialog does not manage focus packages/web-components/src/components/notification-panel/notification-panel.ts:195— This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
AC4 · Keyboard semantics· Link used as a button (placeholder href) · ×1
Link used as a button (placeholder href) packages/web-components/src/components/ui-shell/header-menu.ts:153— An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
ComboBox.ComboBox (cyclomatic 183) packages/react/src/components/ComboBox/ComboBox.tsx:384— ComboBox.ComboBox has cyclomatic complexity 183 (threshold 15). Of this number, 42 points are the body's own statements and 141 belong to 25 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.
Slider.Slider (cyclomatic 154) packages/react/src/components/Slider/Slider.tsx:348— Slider.Slider has cyclomatic complexity 154 (threshold 15). Of this number, 55 points are the body's own statements and 99 belong to 26 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.
DatePicker.DatePicker (cyclomatic 121) packages/react/src/components/DatePicker/DatePicker.tsx:386— DatePicker.DatePicker has cyclomatic complexity 121 (threshold 15). Most of this is not in the body itself: 2 of the 121 points are its own statements and the rest belongs to 24 function items inside it that branch (a function literal at line 550, a function literal at line 699, a function literal at line 807, …). 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.
Modal.ModalDialog (cyclomatic 114) packages/react/src/components/Modal/Modal.tsx:288— Modal.ModalDialog has cyclomatic complexity 114 (threshold 15). Of this number, 54 points are the body's own statements and 60 belong to 17 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.
TextArea.TextArea (cyclomatic 103) packages/react/src/components/TextArea/TextArea.tsx:215— TextArea.TextArea has cyclomatic complexity 103 (threshold 15). Of this number, 53 points are the body's own statements and 50 belong to 11 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
index.Popover (cyclomatic 89) packages/react/src/components/Popover/index.tsx:176— index.Popover has cyclomatic complexity 89 (threshold 15). Of this number, 23 points are the body's own statements and 66 belong to 11 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ComposedModal.ComposedModalDialog (cyclomatic 74) packages/react/src/components/ComposedModal/ComposedModal.tsx:298— ComposedModal.ComposedModalDialog has cyclomatic complexity 74 (threshold 15). Of this number, 21 points are the body's own statements and 53 belong to 14 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.
Dropdown.Dropdown (cyclomatic 64) packages/react/src/components/Dropdown/Dropdown.tsx:291— Dropdown.Dropdown has cyclomatic complexity 64 (threshold 15). Of this number, 37 points are the body's own statements and 27 belong to 10 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.
ibm-products-update-page-header-composable.transform (cyclomatic 60) packages/upgrade/transforms/ibm-products-update-page-header-composable.js:40— ibm-products-update-page-header-composable.transform has cyclomatic complexity 60 (threshold 15). Most of this is not in the body itself: 3 of the 60 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 99, a function literal at line 131, a function literal at line 51, …). 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.
ibm-products-update-coachmark.transform (cyclomatic 57) packages/upgrade/transforms/ibm-products-update-coachmark.js:39— ibm-products-update-coachmark.transform has cyclomatic complexity 57 (threshold 15). Most of this is not in the body itself: 4 of the 57 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 219, a function literal at line 443, a function literal at line 208, …). 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.
useDatePicker.useDatePicker (cyclomatic 56) packages/react/src/components/DatePicker/next/hooks/useDatePicker.ts:195— useDatePicker.useDatePicker has cyclomatic complexity 56 (threshold 15). Most of this is not in the body itself: 1 of the 56 points is its own statement and the rest belongs to 9 function literals inside it that branch (lines 487, 307, 337, …). 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.
Pagination.Pagination (cyclomatic 53) packages/react/src/components/Pagination/Pagination.tsx:212— Pagination.Pagination has cyclomatic complexity 53 (threshold 15). Of this number, 19 points are the body's own statements and 34 belong to 13 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.
Tabs.TabList (cyclomatic 53) packages/react/src/components/Tabs/Tabs.tsx:450— Tabs.TabList has cyclomatic complexity 53 (threshold 15). Of this number, 23 points are the body's own statements and 30 belong to 15 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.
ConditionBuilderItem.ConditionBuilderItem (cyclomatic 53) packages/react/src/components/ConditionBuilder/ConditionBuilderItem/ConditionBuilderItem.tsx:64— ConditionBuilderItem.ConditionBuilderItem has cyclomatic complexity 53 (threshold 15). Most of this is not in the body itself: 8 of the 53 points are its own statements and the rest belongs to 12 function items inside it that branch (getPropertyDetails, a function literal at line 159, a function literal at line 206, …). 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.
ConditionGroupBuilder.ConditionGroupBuilder (cyclomatic 51) packages/react/src/components/ConditionBuilder/ConditionGroupBuilder/ConditionGroupBuilder.tsx:60— ConditionGroupBuilder.ConditionGroupBuilder has cyclomatic complexity 51 (threshold 15). Most of this is not in the body itself: 3 of the 51 points are its own statements and the rest belongs to 15 function items inside it that branch (onRemoveHandler, a function literal at line 104, getScrollableParent, …). 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.
NotificationsPanel.NotificationsPanel (cyclomatic 51) packages/react/src/components/NotificationsPanel/NotificationsPanel.tsx:350— NotificationsPanel.NotificationsPanel has cyclomatic complexity 51 (threshold 15). Most of this is not in the body itself: 13 of the 51 points are its own statements and the rest belongs to 13 function items inside it that branch (renderNotification, isActionableElement, handleAnimationEnd, …). 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.
OverflowMenu.OverflowMenu (cyclomatic 50) packages/react/src/components/OverflowMenu/OverflowMenu.tsx:260— OverflowMenu.OverflowMenu has cyclomatic complexity 50 (threshold 15). Most of this is not in the body itself: 8 of the 50 points are its own statements and the rest belongs to 18 function items inside it that branch (a function literal at line 351, a function literal at line 361, a function literal at line 505, …). 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.
FilterableMultiSelect.FilterableMultiSelect (cyclomatic 44) packages/react/src/components/MultiSelect/FilterableMultiSelect.tsx:331— FilterableMultiSelect.FilterableMultiSelect 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. This shape REPEATS in the file: one other method here (FilterableMultiSelect.FilterableMultiSelect::stateReducer) 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.
CDSDatePicker._handleKeyDown (cyclomatic 44) packages/web-components/src/components/date-picker/next/components/date-picker.ts:641— CDSDatePicker._handleKeyDown 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.
CodeSnippet.CodeSnippet (cyclomatic 43) packages/react/src/components/CodeSnippet/CodeSnippet.tsx:156— CodeSnippet.CodeSnippet has cyclomatic complexity 43 (threshold 15). Of this number, 29 points are the body's own statements and 14 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.
FloatingMenu.FloatingMenu (cyclomatic 43) packages/react/src/internal/FloatingMenu.tsx:237— FloatingMenu.FloatingMenu has cyclomatic complexity 43 (threshold 15). Most of this is not in the body itself: 9 of the 43 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 264, focusMenuContent, a function literal at line 386, …). 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.
MenuItem.MenuItem (cyclomatic 42) packages/react/src/components/Menu/MenuItem.tsx:98— MenuItem.MenuItem has cyclomatic complexity 42 (threshold 15). Of this number, 16 points are the body's own statements and 26 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.
MultiSelect.MultiSelect (cyclomatic 41) packages/react/src/components/MultiSelect/MultiSelect.tsx:299— MultiSelect.MultiSelect has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (MultiSelect.MultiSelect::stateReducer) 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.
Tabs.Tab (cyclomatic 40) packages/react/src/components/Tabs/Tabs.tsx:1303— Tabs.Tab has cyclomatic complexity 40 (threshold 15). Of this number, 23 points are the body's own statements and 17 belong to 8 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.
Resizer.Resizer (cyclomatic 40) packages/react/src/components/Resizer/Resizer.tsx:56— Resizer.Resizer has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 1 of the 40 points is its own statement and the rest belongs to 16 function items inside it that branch (a function literal at line 193, a function literal at line 118, handleDoubleClick, …). 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.
PasswordInput.PasswordInput (cyclomatic 39) packages/react/src/components/TextInput/PasswordInput.tsx:182— PasswordInput.PasswordInput has cyclomatic complexity 39 (threshold 15). Of this number, 36 points are the body's own statements and 3 belong to 3 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.
Tag.TagBase (cyclomatic 38) packages/react/src/components/Tag/Tag.tsx:143— Tag.TagBase has cyclomatic complexity 38 (threshold 15). Of this number, 37 points are the body's own statements and 1 belongs to one function item 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.
icons-react-size-prop.transform (cyclomatic 38) packages/upgrade/transforms/icons-react-size-prop.js:16— icons-react-size-prop.transform has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 4 of the 38 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 98, 147, 55, …). 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.
TextInput.TextInput (cyclomatic 37) packages/react/src/components/TextInput/TextInput.tsx:192— TextInput.TextInput has cyclomatic complexity 37 (threshold 15). Of this number, 27 points are the body's own statements and 10 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.
EditInPlace.EditInPlace (cyclomatic 37) packages/react/src/components/EditInPlace/EditInPlace.tsx:140— EditInPlace.EditInPlace has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 11 of the 37 points are its own statements and the rest belongs to 11 function items inside it that branch (onBlurHandler, handleToolbarMouseDown, onKeyHandler, …). 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.
CDSTextInput.render (cyclomatic 37) packages/web-components/src/components/text-input/text-input.ts:349— CDSTextInput.render has cyclomatic complexity 37 (threshold 15). Of this number, 36 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.
fixEventsPlugin.fixEventsPlugin (cyclomatic 36) packages/react/src/components/DatePicker/plugins/fixEventsPlugin.ts:19— fixEventsPlugin.fixEventsPlugin has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 1 of the 36 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 25, 108, 67, …). 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.
NumberInput.NumberInput (cyclomatic 36) REDACTED:594— NumberInput.NumberInput has cyclomatic complexity 36 (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 (NumberInput.NumberInput::handleStep) 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.
Search.Search (cyclomatic 35) packages/react/src/components/Search/Search.tsx:131— Search.Search has cyclomatic complexity 35 (threshold 15). Of this number, 23 points are the body's own statements and 12 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.
Select.Select (cyclomatic 35) packages/react/src/components/Select/Select.tsx:149— Select.Select has cyclomatic complexity 35 (threshold 15). Of this number, 26 points are the body's own statements and 9 belong to 3 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.
SideNav.SideNav (cyclomatic 35) packages/react/src/components/UIShell/SideNav.tsx:53— SideNav.SideNav has cyclomatic complexity 35 (threshold 15). Of this number, 16 points are the body's own statements and 19 belong to 6 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.
CDSPasswordInput.render (cyclomatic 35) packages/web-components/src/components/password-input/password-input.ts:140— CDSPasswordInput.render has cyclomatic complexity 35 (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.
CardActions.CardActions (cyclomatic 34) packages/react/src/components/Card/CardActions.tsx:79— CardActions.CardActions has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 1 of the 34 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 94, 160, 173). 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.
DataTable.DataTable (cyclomatic 34) packages/react/src/components/DataTable/DataTable.tsx:351— DataTable.DataTable has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 4 of the 34 points are its own statements and the rest belongs to 13 function items inside it that branch (getSelectionProps, a function literal at line 380, getExpandHeaderProps, …). 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.
FilterableMultiSelect.FilterableMultiSelect::stateReducer (cyclomatic 33) packages/react/src/components/MultiSelect/FilterableMultiSelect.tsx:694— FilterableMultiSelect.FilterableMultiSelect::stateReducer 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: one other method here (FilterableMultiSelect.FilterableMultiSelect) 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.
Tile.ExpandableTile (cyclomatic 33) packages/react/src/components/Tile/Tile.tsx:780— Tile.ExpandableTile has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 11 of the 33 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 876, a function literal at line 891, a function literal at line 861, …). 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.
CDSDatePicker._handleStateChange (cyclomatic 33) packages/web-components/src/components/date-picker/next/components/date-picker.ts:245— CDSDatePicker._handleStateChange has cyclomatic complexity 33 (threshold 15). Of this number, 32 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.
FileUploader.FileUploader (cyclomatic 32) packages/react/src/components/FileUploader/FileUploader.tsx:175— FileUploader.FileUploader has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 4 of the 32 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 250, a function literal at line 330, a function literal at line 398, …). 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.
PaginationNav.PaginationNav (cyclomatic 32) packages/react/src/components/PaginationNav/PaginationNav.tsx:361— PaginationNav.PaginationNav has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 14 of the 32 points are its own statements and the rest belongs to 6 function items inside it that branch (pageWouldBeHidden, a function literal at line 466, jumpToItem, …). 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.
AddSelectBody.AddSelectBody (cyclomatic 32) packages/react/src/components/AddSelect/AddSelectBody.tsx:130— AddSelectBody.AddSelectBody has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 12 of the 32 points are its own statements and the rest belongs to 5 function items inside it that branch (handleKeyDown, getItems, a function literal at line 191, …). 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.
CDSCodeSnippet.render (cyclomatic 32) packages/web-components/src/components/code-snippet/code-snippet.ts:372— CDSCodeSnippet.render has cyclomatic complexity 32 (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.
CDSDropdown.render (cyclomatic 32) packages/web-components/src/components/dropdown/dropdown.ts:1284— CDSDropdown.render has cyclomatic complexity 32 (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.
FloatingController.computePlacement (cyclomatic 31) packages/web-components/src/globals/controllers/floating-controller.ts:76— FloatingController.computePlacement has cyclomatic complexity 31 (threshold 15). Of this number, 30 points are the body's own statements and 1 belongs to one function item 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.
CDSMenu._fitValue (cyclomatic 31) packages/web-components/src/components/menu/menu.ts:344— CDSMenu._fitValue has cyclomatic complexity 31 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Menu.Menu::fitValue (cyclomatic 30) packages/react/src/components/Menu/Menu.tsx:301— Menu.Menu::fitValue has cyclomatic complexity 30 (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.
Calendar.Calendar (cyclomatic 30) packages/react/src/components/DatePicker/next/components/Calendar.tsx:53— Calendar.Calendar has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 2 of the 30 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 114, 249, 97, …). 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.
RadioButtonGroup.RadioButtonGroup (cyclomatic 30) packages/react/src/components/RadioButtonGroup/RadioButtonGroup.tsx:144— RadioButtonGroup.RadioButtonGroup has cyclomatic complexity 30 (threshold 15). Of this number, 24 points are the body's own statements and 6 belong to 3 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.
TreeView.TreeView::handleKeyDown (cyclomatic 30) packages/react/src/components/TreeView/TreeView.tsx:178— TreeView.TreeView::handleKeyDown 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.
CDSSidePanel.render (cyclomatic 30) packages/web-components/src/components/side-panel/side-panel.ts:924— CDSSidePanel.render has cyclomatic complexity 30 (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.
CDSOverflowMenu.updated (cyclomatic 29) packages/web-components/src/components/overflow-menu/overflow-menu.ts:410— CDSOverflowMenu.updated has cyclomatic complexity 29 (threshold 15). Of this number, 27 points are the body's own statements and 2 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.
form-associated.FormAssociatedMixin (cyclomatic 29) packages/web-components/src/globals/mixins/form-associated.ts:43— form-associated.FormAssociatedMixin has cyclomatic complexity 29 (threshold 15). Of this number, 26 points are the body's own statements and 3 belong to 3 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.
Notification.ActionableNotification (cyclomatic 28) packages/react/src/components/Notification/Notification.tsx:929— Notification.ActionableNotification has cyclomatic complexity 28 (threshold 15). Of this number, 16 points are the body's own statements and 12 belong to 4 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.
ItemOptionForValueField.ItemOptionForValueField (cyclomatic 28) packages/react/src/components/ConditionBuilder/ConditionBuilderItem/ConditionBuilderItemOption/ItemOptionForValueField.tsx:43— ItemOptionForValueField.ItemOptionForValueField has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 9 of the 28 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 220, onClickHandler, a function literal at line 101, …). 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.
ConditionBuilderContent.ConditionBuilderContent (cyclomatic 28) packages/react/src/components/ConditionBuilder/ConditionBuilderContent/ConditionBuilderContent.tsx:41— ConditionBuilderContent.ConditionBuilderContent has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 11 of the 28 points are its own statements and the rest belongs to 6 function items inside it that branch (onStartConditionBuilder, onChangeHandler, a function literal at line 91, …). 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.
Tearsheet.TearsheetInternal (cyclomatic 28) packages/react/src/components/Tearsheet/Tearsheet.tsx:190— Tearsheet.TearsheetInternal has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 12 of the 28 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 269, 342, 256, …). 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.
CDSRadioButton.updated (cyclomatic 28) packages/web-components/src/components/radio-button/radio-button.ts:383— CDSRadioButton.updated has cyclomatic complexity 28 (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.
InterstitialScreenFooter.InterstitialScreenFooter (cyclomatic 27) packages/react/src/components/InterstitialScreen/InterstitialScreenFooter.tsx:72— InterstitialScreenFooter.InterstitialScreenFooter has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 4 of the 27 points are its own statements and the rest belongs to 4 function items inside it that branch (getFooterContent, handleAction, a function literal at line 147, …). 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.
CheckboxGroup.CheckboxGroup (cyclomatic 26) packages/react/src/components/CheckboxGroup/CheckboxGroup.tsx:54— CheckboxGroup.CheckboxGroup has cyclomatic complexity 26 (threshold 15). Of this number, 16 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.
NumberInput.NumberInput::handleStep (cyclomatic 26) REDACTED:845— NumberInput.NumberInput::handleStep has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (NumberInput.NumberInput) 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.
useGuidebannerScroll.useGuidebannerScroll (cyclomatic 26) packages/react/src/components/Guidebanner/useGuidebannerScroll.ts:24— useGuidebannerScroll.useGuidebannerScroll has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 3 of the 26 points are its own statements and the rest belongs to 15 function literals inside it that branch (lines 208, 57, 108, …). 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.
OptionsTile.OptionsTile (cyclomatic 26) packages/react/src/components/OptionsTile/OptionsTile.tsx:123— OptionsTile.OptionsTile has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 9 of the 26 points are its own statements and the rest belongs to 4 function items inside it that branch (renderTitle, expand, collapse, …). 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.
ScrollGradient.ScrollGradient (cyclomatic 26) packages/react/src/components/ScrollGradient/ScrollGradient.tsx:41— ScrollGradient.ScrollGradient has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 8 of the 26 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 83, a function literal at line 130, a function literal at line 127, …). 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.
CDSActionableNotification._handleBlur (cyclomatic 26) packages/web-components/src/components/notification/actionable-notification.ts:148— CDSActionableNotification._handleBlur has cyclomatic complexity 26 (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.
CDSSelect.render (cyclomatic 26) packages/web-components/src/components/select/select.ts:414— CDSSelect.render 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.
DatePickerInput.DatePickerInput (cyclomatic 25) packages/react/src/components/DatePicker/next/components/DatePickerInput.tsx:181— DatePickerInput.DatePickerInput 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.
DatePicker.DatePicker (cyclomatic 25) packages/react/src/components/DatePicker/next/components/DatePicker.tsx:107— DatePicker.DatePicker has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 3 of the 25 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 176, a function literal at line 226, handleIconClick, …). 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.
enable-v12-overflowmenu.transform (cyclomatic 25) packages/upgrade/transforms/enable-v12-overflowmenu.js:29— enable-v12-overflowmenu.transform has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 5 of the 25 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 95, a function literal at line 86, a function literal at line 38, …). 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.
refactor-to-callout.transform (cyclomatic 25) packages/upgrade/transforms/refactor-to-callout.js:15— refactor-to-callout.transform has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 41, a function literal at line 135, isCarbonReactImport, …). 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.
CDSNumberInput._handleStep (cyclomatic 25) packages/web-components/src/components/number-input/number-input.ts:683— CDSNumberInput._handleStep 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.
CDSSlider.render (cyclomatic 25) packages/web-components/src/components/slider/slider.ts:969— CDSSlider.render has cyclomatic complexity 25 (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.
CDSSidePanel.updated (cyclomatic 25) packages/web-components/src/components/side-panel/side-panel.ts:1125— CDSSidePanel.updated 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.
DatePickerInput.DatePickerInput (cyclomatic 24) packages/react/src/components/DatePickerInput/DatePickerInput.tsx:152— DatePickerInput.DatePickerInput has cyclomatic complexity 24 (threshold 15). Of this number, 22 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.
CDSDialog.updated (cyclomatic 24) packages/web-components/src/components/dialog/dialog.ts:177— CDSDialog.updated 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.
CDSSlider.shouldUpdate (cyclomatic 24) packages/web-components/src/components/slider/slider.ts:896— CDSSlider.shouldUpdate has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 902, 933, 943). 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.
Dialog.Dialog (cyclomatic 23) packages/react/src/components/Dialog/Dialog.tsx:138— Dialog.Dialog has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 7 of the 23 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 235, handleModalBackdropClick, a function literal at line 191, …). 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.
MultiSelect.MultiSelect::stateReducer (cyclomatic 23) packages/react/src/components/MultiSelect/MultiSelect.tsx:616— MultiSelect.MultiSelect::stateReducer 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. This shape REPEATS in the file: one other method here (MultiSelect.MultiSelect) 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.
NumberInput.validateNumberSeparators (cyclomatic 23) REDACTED:460— NumberInput.validateNumberSeparators 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.
ProgressBar.ProgressBar (cyclomatic 23) packages/react/src/components/ProgressBar/ProgressBar.tsx:64— ProgressBar.ProgressBar has cyclomatic complexity 23 (threshold 15). Of this number, 19 points are the body's own statements and 4 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.
CDSNumberInput.render (cyclomatic 23) packages/web-components/src/components/number-input/number-input.ts:833— CDSNumberInput.render 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.
Tooltip.Tooltip (cyclomatic 22) packages/react/src/components/Tooltip/Tooltip.tsx:118— Tooltip.Tooltip has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 6 of the 22 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 189, a function literal at line 155, a function literal at line 160, …). 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.
Card.CardComponent (cyclomatic 22) packages/react/src/components/Card/Card.tsx:35— Card.CardComponent has cyclomatic complexity 22 (threshold 15). Of this number, 14 points are the body's own statements and 8 belong to 5 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.
useResizeObserver.useResizeObserver (cyclomatic 22) packages/react/src/internal/useResizeObserver.ts:10— useResizeObserver.useResizeObserver has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 33, 76, 32, …). 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.
TimePicker.TimePicker (cyclomatic 22) packages/react/src/components/TimePicker/TimePicker.tsx:144— TimePicker.TimePicker has cyclomatic complexity 22 (threshold 15). Of this number, 14 points are the body's own statements and 8 belong to 6 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.
ConditionBuilderItemDate.ConditionBuilderItemDate (cyclomatic 22) packages/react/src/components/ConditionBuilder/ConditionBuilderItem/ConditionBuilderItemDate/ConditionBuilderItemDate.tsx:26— ConditionBuilderItemDate.ConditionBuilderItemDate has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 4 function items inside it that branch (getParsedDate, onCloseHandler, onKeyPressHandler, …). 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.
storySort (cyclomatic 22) packages/react/.storybook/preview.js:231— storySort 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.
ContentSwitcher.ContentSwitcher (cyclomatic 21) packages/react/src/components/ContentSwitcher/ContentSwitcher.tsx:75— ContentSwitcher.ContentSwitcher 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 6 function items inside it that branch (handleChildChange, a function literal at line 184, hasKey, …). 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.
FileUploaderDropContainer.FileUploaderDropContainer (cyclomatic 21) packages/react/src/components/FileUploader/FileUploaderDropContainer.tsx:112— FileUploaderDropContainer.FileUploaderDropContainer 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 9 function items inside it that branch (a function literal at line 149, handleDrop, a function literal at line 193, …). 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.
NumberInput.parseNumberWithLocale (cyclomatic 21) REDACTED:371— NumberInput.parseNumberWithLocale has cyclomatic complexity 21 (threshold 15). Of this number, 13 points are the body's own statements and 8 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.
Pagination.Pagination (cyclomatic 21) packages/react/src/components/Pagination/experimental/Pagination.js:21— Pagination.Pagination has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 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.
CDSDatePickerInput.render (cyclomatic 21) packages/web-components/src/components/date-picker/date-picker-input.ts:247— CDSDatePickerInput.render 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.
focus-plugin.default (cyclomatic 21) packages/web-components/src/components/date-picker/focus-plugin.ts:69— focus-plugin.default 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 5 function literals inside it that branch (lines 82, 104, 134, …). 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.
CDSDatePicker._setCalendar (cyclomatic 21) packages/web-components/src/components/date-picker/date-picker.ts:286— CDSDatePicker._setCalendar has cyclomatic complexity 21 (threshold 15). Of this number, 18 points are the body's own statements and 3 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.
CDSDatePicker.updated (cyclomatic 21) packages/web-components/src/components/date-picker/next/components/date-picker.ts:946— CDSDatePicker.updated has cyclomatic complexity 21 (threshold 15). Of this number, 20 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.
Checkbox.Checkbox (cyclomatic 20) packages/react/src/components/Checkbox/Checkbox.tsx:114— Checkbox.Checkbox has cyclomatic complexity 20 (threshold 15). Of this number, 12 points are the body's own statements and 8 belong to 3 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.
Tabs.TabListVertical (cyclomatic 20) packages/react/src/components/Tabs/Tabs.tsx:974— Tabs.TabListVertical has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 7 function items inside it that branch (onKeyDown, a function literal at line 1057, handleBlur, …). 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.
Tile.ClickableTile (cyclomatic 20) packages/react/src/components/Tile/Tile.tsx:222— Tile.ClickableTile has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong 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.
CDSCoachmark.updated (cyclomatic 20) packages/web-components/src/components/coachmark/coachmark.ts:227— CDSCoachmark.updated has cyclomatic complexity 20 (threshold 15). Of this number, 11 points are the body's own statements and 9 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.
CDSTable.updated (cyclomatic 20) packages/web-components/src/components/data-table/table.ts:742— CDSTable.updated has cyclomatic complexity 20 (threshold 15). Of this number, 16 points are the body's own statements and 4 belong to 3 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.
CDSResizerHandle._handleKeyDown (cyclomatic 20) packages/web-components/src/components/resizer/resizer-handle.ts:328— CDSResizerHandle._handleKeyDown has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
executeBob (cyclomatic 20) actions/issues/src/plugins/bob-bug-triage.js:309— executeBob has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 9 function items inside it that branch (a function literal at line 426, (anonymous)::handleStdoutLine, a function literal at line 373, …). 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.
fn::enter (cyclomatic 20) packages/icon-build-helpers/src/metadata/extensions/output/optimizer.js:32— fn::enter 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.
TreeNode.TreeNode::handleKeyDown (cyclomatic 19) packages/react/src/components/TreeView/TreeNode.tsx:398— TreeNode.TreeNode::handleKeyDown 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: one other method here (TreeNode.TreeNode) 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.
HeaderMenu.HeaderMenu (cyclomatic 19) packages/react/src/components/UIShell/HeaderMenu.tsx:103— HeaderMenu.HeaderMenu has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 201, handleOnClick, handleMenuClose, …). 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.
InterstitialScreenBody.InterstitialScreenBody (cyclomatic 19) packages/react/src/components/InterstitialScreen/InterstitialScreenBody.tsx:56— InterstitialScreenBody.InterstitialScreenBody has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 139, renderBody, a function literal at line 81, …). 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.
PageHeader.PageHeader (cyclomatic 19) packages/react/src/components/PageHeader/PageHeader.tsx:117— PageHeader.PageHeader has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 188, 150, 154, …). 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.
CDSRadioButtonGroup.render (cyclomatic 19) packages/web-components/src/components/radio-button/radio-button-group.ts:243— CDSRadioButtonGroup.render 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.
CDSAddSelectSelectionSummaryItem.render (cyclomatic 19) packages/web-components/src/components/add-select/add-select-selection-summary-item.ts:166— CDSAddSelectSelectionSummaryItem.render 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.
TreeNode.TreeNode (cyclomatic 18) packages/react/src/components/TreeView/TreeNode.tsx:250— TreeNode.TreeNode 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 (TreeNode.TreeNode::handleKeyDown) 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.
AddSelectRow.AddSelectRow (cyclomatic 18) packages/react/src/components/AddSelect/AddSelectRow.tsx:152— AddSelectRow.AddSelectRow has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 belong to 3 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.
ibm-products-update-tearsheet.transform (cyclomatic 18) packages/upgrade/transforms/ibm-products-update-tearsheet.js:309— ibm-products-update-tearsheet.transform has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 397, 326, 345, …). 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.
CDSOverflowMenuBody._handleKeydown (cyclomatic 18) packages/web-components/src/components/overflow-menu/overflow-menu-body.ts:135— CDSOverflowMenuBody._handleKeydown has cyclomatic complexity 18 (threshold 15). Of this number, 12 points are the body's own statements and 6 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.
CDSCheckboxGroup.render (cyclomatic 18) packages/web-components/src/components/checkbox/checkbox-group.ts:152— CDSCheckboxGroup.render 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.
CDSDropdown._handleKeydownInner (cyclomatic 18) packages/web-components/src/components/dropdown/dropdown.ts:229— CDSDropdown._handleKeydownInner has cyclomatic complexity 18 (threshold 15). Of this number, 11 points are the body's own statements and 7 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.
CDSComboBox._filterItems (cyclomatic 18) packages/web-components/src/components/combo-box/combo-box.ts:201— CDSComboBox._filterItems 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 2 function literals inside it that branch (lines 208, 225). 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.
CDSNumberInput._getInputValidity (cyclomatic 18) packages/web-components/src/components/number-input/number-input.ts:604— CDSNumberInput._getInputValidity 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.
CDSSlider._handleClick (cyclomatic 18) packages/web-components/src/components/slider/slider.ts:376— CDSSlider._handleClick 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.
parseBobStreamLine (cyclomatic 18) actions/issues/src/plugins/bob-bug-triage.js:205— parseBobStreamLine 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.
ButtonBase.ButtonBase (cyclomatic 17) packages/react/src/components/Button/ButtonBase.tsx:14— ButtonBase.ButtonBase 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.
index.Toggletip (cyclomatic 17) packages/react/src/components/Toggletip/index.tsx:103— index.Toggletip 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 6 function items inside it that branch (a function literal at line 173, a function literal at line 180, onKeyDown, …). 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.
TableToolbarSearch.TableToolbarSearch (cyclomatic 17) packages/react/src/components/DataTable/TableToolbarSearch.tsx:135— TableToolbarSearch.TableToolbarSearch has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 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.
Toggle.Toggle (cyclomatic 17) packages/react/src/components/Toggle/Toggle.tsx:102— Toggle.Toggle has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 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.
CoachmarkContent.CoachmarkContent (cyclomatic 17) packages/react/src/components/Coachmark/CoachmarkContent.tsx:50— CoachmarkContent.CoachmarkContent 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 8 function literals inside it that branch (lines 84, 97, 121, …). 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.
TearsheetHeaderContent.TearsheetHeaderContent (cyclomatic 17) packages/react/src/components/Tearsheet/TearsheetHeaderContent.tsx:61— TearsheetHeaderContent.TearsheetHeaderContent 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.
json-pointer-references.jsonPointerReferences (cyclomatic 17) packages/themes/style-dictionary/preprocessors/json-pointer-references.js:29— json-pointer-references.jsonPointerReferences 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 3 function items inside it that branch (lookup, walk, resolve). 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.
ibm-products-update-tearsheet.transformTearsheetElement (cyclomatic 17) packages/upgrade/transforms/ibm-products-update-tearsheet.js:208— ibm-products-update-tearsheet.transformTearsheetElement has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 222). 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.
wc-add-barrel-imports.transform (cyclomatic 17) packages/upgrade/transforms/wc-add-barrel-imports.js:35— wc-add-barrel-imports.transform has cyclomatic complexity 17 (threshold 15). Of this number, 10 points are the body's own statements and 7 belong to 5 function items inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
CDSButton.render (cyclomatic 17) packages/web-components/src/components/button/button.ts:268— CDSButton.render 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.
CDSMultiSelect.shouldUpdate (cyclomatic 17) packages/web-components/src/components/multi-select/multi-select.ts:789— CDSMultiSelect.shouldUpdate 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.
CDSMultiSelect.updated (cyclomatic 17) packages/web-components/src/components/multi-select/multi-select.ts:864— CDSMultiSelect.updated has cyclomatic complexity 17 (threshold 15). 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, 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.
CDSTimePicker.render (cyclomatic 17) packages/web-components/src/components/time-picker/time-picker.ts:189— CDSTimePicker.render 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.
CDSTreeView._handleKeyDown (cyclomatic 17) packages/web-components/src/components/tree-view/tree-view.ts:68— CDSTreeView._handleKeyDown has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 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.
CDSSidePanel.getFocusable (cyclomatic 17) packages/web-components/src/components/side-panel/side-panel.ts:149— CDSSidePanel.getFocusable has cyclomatic complexity 17 (threshold 15). Of this number, 15 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.
examples.main (cyclomatic 17) tasks/examples.js:62— examples.main has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 129, 96, 75, …). 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.
handleKeyPressForPopover (cyclomatic 17) packages/react/src/components/ConditionBuilder/utils/handleKeyboardEvents.js:68— handleKeyPressForPopover has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs 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.
manage-comment.manageComment (cyclomatic 16) actions/issues/src/manage-comment.js:124— manage-comment.manageComment 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.
CoachmarkContentHeader.CoachmarkContentHeader (cyclomatic 16) packages/react/src/components/Coachmark/CoachmarkContentHeader.tsx:49— CoachmarkContentHeader.CoachmarkContentHeader has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 78, 104, 117). 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.
Coachmark.Coachmark (cyclomatic 16) packages/react/src/components/Coachmark/Coachmark.tsx:108— Coachmark.Coachmark has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 155, a function literal at line 163, setOpen, …). 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.
ConditionBuilderItemNumber.ConditionBuilderItemNumber (cyclomatic 16) packages/react/src/components/ConditionBuilder/ConditionBuilderItem/ConditionBuilderItemNumber/ConditionBuilderItemNumber.tsx:21— ConditionBuilderItemNumber.ConditionBuilderItemNumber has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 2 function items inside it that branch (checkIfValid, onChangeHandler). 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.
swipeEvents.registerSwipeEvents (cyclomatic 16) packages/utilities/src/carousel/swipeEvents.ts:9— swipeEvents.registerSwipeEvents 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 4 function items inside it that branch (mouseUpHandler, touchEndHandler, wheelHandler, …). 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.
CDSNumberInput.willUpdate (cyclomatic 16) packages/web-components/src/components/number-input/number-input.ts:504— CDSNumberInput.willUpdate 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.
CDSTextarea.render (cyclomatic 16) packages/web-components/src/components/textarea/textarea.ts:170— CDSTextarea.render has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 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.
CDSTab.render (cyclomatic 16) packages/web-components/src/components/tabs/tab.ts:179— CDSTab.render 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.
CDSPageHeaderActionsSet.setupOverflowDetection (cyclomatic 16) packages/web-components/src/components/page-header/page-header-actions-set/page-header-actions-set.ts:102— CDSPageHeaderActionsSet.setupOverflowDetection 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 items inside it that branch (checkOverflow, a function literal at line 172, a function literal at line 198). 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.
CDSTearsheetHeaderContent.render (cyclomatic 16) packages/web-components/src/components/tearsheet/tearsheet-header-content.ts:379— CDSTearsheetHeaderContent.render 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.
D10 · Test Quality· Test project verifies nothing · ×1
Test project verifies nothing: packages/react/examples/react-router-vite packages/react/examples/react-router-vite/src/App-test.js:5— No conventional assertion call was detected in 1 of 1 tests in `packages/react/examples/react-router-vite` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
FixmeComment packages/web-components/src/components/text-input/text-input.ts:318— // FIXME: Figure out how to deal with TS2611 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment repeated across 17 files packages/web-components/src/components/overflow-menu/overflow-menu.ts:467— The identical TodoComment appears in 17 files (23 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 23 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// TODO: V12 - Remove this class". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
HackComment packages/react/previewer/storybookStyles/index.tsx:20— // hack to enable zoom feature to trigger — 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.
ComboBox.ComboBox (cognitive 231) packages/react/src/components/ComboBox/ComboBox.tsx:384— ComboBox.ComboBox has cognitive complexity 231 (threshold 15). Drivers by points: if/else 68 (120 pts), boolean chains 58, ternaries 27 (52 pts), match/switch 1 (nesting depth added 77). Of this number, 37 points are the body's own statements and 194 belong to 25 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.
DatePicker.DatePicker (cognitive 125) packages/react/src/components/DatePicker/DatePicker.tsx:386— DatePicker.DatePicker has cognitive complexity 125 (threshold 15). Drivers by points: if/else 68 (83 pts), boolean chains 35, ternaries 6 (7 pts) (nesting depth added 16). Most of this is not in the body itself: 1 of the 125 points is its own statement and the rest belongs to 24 function items inside it that branch (a function literal at line 550, a function literal at line 699, a function literal at line 764, …). 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.
TextArea.TextArea (cognitive 106) packages/react/src/components/TextArea/TextArea.tsx:215— TextArea.TextArea has cognitive complexity 106 (threshold 15). Drivers by points: if/else 32 (51 pts), boolean chains 37, ternaries 15 (18 pts) (nesting depth added 22). Of this number, 45 points are the body's own statements and 61 belong to 11 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Modal.ModalDialog (cognitive 99) packages/react/src/components/Modal/Modal.tsx:288— Modal.ModalDialog has cognitive complexity 99 (threshold 15). Drivers by points: boolean chains 53, if/else 23 (28 pts), ternaries 12 (18 pts) (nesting depth added 11). Of this number, 49 points are the body's own statements and 50 belong to 17 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.
index.Popover (cognitive 94) packages/react/src/components/Popover/index.tsx:176— index.Popover has cognitive complexity 94 (threshold 15). Drivers by points: if/else 29 (43 pts), boolean chains 28, ternaries 13 (22 pts), loops 1 (nesting depth added 23). Of this number, 26 points are the body's own statements and 68 belong to 11 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
transform (cognitive 78) packages/upgrade/transforms/ibm-products-update-page-header-composable.js:40— transform has cognitive complexity 78 (threshold 15). Drivers by points: if/else 41 (63 pts), boolean chains 8, ternaries 3 (7 pts) (nesting depth added 26). Most of this is not in the body itself: 2 of the 78 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 99, a function literal at line 131, a function literal at line 51, …). 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.
transform (cognitive 77) packages/upgrade/transforms/ibm-products-update-coachmark.js:39— transform has cognitive complexity 77 (threshold 15). Drivers by points: if/else 40 (50 pts), ternaries 11 (20 pts), boolean chains 7 (nesting depth added 19). Most of this is not in the body itself: 3 of the 77 points are its own statements and the rest belongs to 24 function items inside it that branch (a function literal at line 219, a function literal at line 208, a function literal at line 296, …). 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.
ComposedModal.ComposedModalDialog (cognitive 75) packages/react/src/components/ComposedModal/ComposedModal.tsx:298— ComposedModal.ComposedModalDialog has cognitive complexity 75 (threshold 15). Drivers by points: boolean chains 29, if/else 20 (24 pts), ternaries 11 (22 pts) (nesting depth added 15). Of this number, 28 points are the body's own statements and 47 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.
Dropdown.Dropdown (cognitive 69) packages/react/src/components/Dropdown/Dropdown.tsx:291— Dropdown.Dropdown has cognitive complexity 69 (threshold 15). Drivers by points: boolean chains 25, ternaries 17 (23 pts), if/else 16 (21 pts) (nesting depth added 11). Of this number, 37 points are the body's own statements and 32 belong to 10 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.
useDatePicker.useDatePicker (cognitive 64) packages/react/src/components/DatePicker/next/hooks/useDatePicker.ts:195— useDatePicker.useDatePicker has cognitive complexity 64 (threshold 15). Drivers by points: if/else 30 (43 pts), boolean chains 16, ternaries 3 (5 pts) (nesting depth added 15). None of this is in the body itself: all 64 points belong to 9 function literals inside it that branch (lines 487, 307, 337, …). 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.
CDSDatePicker._handleKeyDown (cognitive 64) packages/web-components/src/components/date-picker/next/components/date-picker.ts:641— CDSDatePicker._handleKeyDown has cognitive complexity 64 (threshold 15). Drivers by points: if/else 23 (48 pts), boolean chains 12, ternaries 2 (4 pts) (nesting depth added 27). 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.
ConditionGroupBuilder.ConditionGroupBuilder (cognitive 60) packages/react/src/components/ConditionBuilder/ConditionGroupBuilder/ConditionGroupBuilder.tsx:60— ConditionGroupBuilder.ConditionGroupBuilder has cognitive complexity 60 (threshold 15). Drivers by points: if/else 21 (29 pts), boolean chains 17, ternaries 12 (13 pts), loops 1 (nesting depth added 9). Most of this is not in the body itself: 2 of the 60 points are its own statements and the rest belongs to 15 function items inside it that branch (onRemoveHandler, handleFocusOnCloseHierarchical, a function literal at line 104, …). 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.
Tabs.TabList (cognitive 58) packages/react/src/components/Tabs/Tabs.tsx:450— Tabs.TabList has cognitive complexity 58 (threshold 15). Drivers by points: if/else 26 (33 pts), boolean chains 13, ternaries 11 (12 pts) (nesting depth added 8). Of this number, 22 points are the body's own statements and 36 belong to 15 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.
Slider.Slider (cognitive 55) packages/react/src/components/Slider/Slider.tsx:348— Slider.Slider has cognitive complexity 55 (threshold 15). Drivers by points: if/else 70 (84 pts), ternaries 38 (52 pts), boolean chains 43 (nesting depth added 28). 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 (Slider.Slider::onDragStart) 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.
CodeSnippet.CodeSnippet (cognitive 54) packages/react/src/components/CodeSnippet/CodeSnippet.tsx:156— CodeSnippet.CodeSnippet has cognitive complexity 54 (threshold 15). Drivers by points: if/else 19 (32 pts), boolean chains 12, ternaries 10 (nesting depth added 13). Of this number, 38 points are the body's own statements and 16 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Pagination.Pagination (cognitive 54) packages/react/src/components/Pagination/Pagination.tsx:212— Pagination.Pagination has cognitive complexity 54 (threshold 15). Drivers by points: if/else 20 (21 pts), boolean chains 17, ternaries 13 (16 pts) (nesting depth added 4). Of this number, 21 points are the body's own statements and 33 belong to 13 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.
ConditionBuilderItem.ConditionBuilderItem (cognitive 54) packages/react/src/components/ConditionBuilder/ConditionBuilderItem/ConditionBuilderItem.tsx:64— ConditionBuilderItem.ConditionBuilderItem has cognitive complexity 54 (threshold 15). Drivers by points: if/else 23 (26 pts), boolean chains 22, ternaries 5 (6 pts) (nesting depth added 4). Most of this is not in the body itself: 7 of the 54 points are its own statements and the rest belongs to 12 function items inside it that branch (getPropertyDetails, a function literal at line 159, getLabel, …). 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.
CDSDialog.updated (cognitive 53) packages/web-components/src/components/dialog/dialog.ts:177— CDSDialog.updated has cognitive complexity 53 (threshold 15). Drivers by points: if/else 18 (47 pts), boolean chains 6 (nesting depth added 29). 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.
FileUploader.FileUploader (cognitive 52) packages/react/src/components/FileUploader/FileUploader.tsx:175— FileUploader.FileUploader has cognitive complexity 52 (threshold 15). Drivers by points: if/else 21 (36 pts), boolean chains 8, ternaries 6 (8 pts) (nesting depth added 17). Most of this is not in the body itself: 3 of the 52 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 330, a function literal at line 250, a function literal at line 398, …). 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.
MenuItem.MenuItem (cognitive 49) packages/react/src/components/Menu/MenuItem.tsx:98— MenuItem.MenuItem has cognitive complexity 49 (threshold 15). Drivers by points: if/else 18 (24 pts), boolean chains 17, ternaries 7 (8 pts) (nesting depth added 7). Most of this is not in the body itself: 13 of the 49 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 130, handleClick, handleKeyDown, …). 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.
CDSDatePicker._handleStateChange (cognitive 48) packages/web-components/src/components/date-picker/next/components/date-picker.ts:245— CDSDatePicker._handleStateChange has cognitive complexity 48 (threshold 15). Drivers by points: if/else 19 (33 pts), boolean chains 8, ternaries 3 (7 pts) (nesting depth added 18). Of this number, 46 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.
CDSDatePicker.updated (cognitive 47) packages/web-components/src/components/date-picker/next/components/date-picker.ts:946— CDSDatePicker.updated has cognitive complexity 47 (threshold 15). Drivers by points: if/else 14 (37 pts), boolean chains 5, ternaries 1 (5 pts) (nesting depth added 27). Of this number, 44 points are the body's own statements and 3 belong to one function literal inside it that branches. 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.
CDSCoachmark.updated (cognitive 46) packages/web-components/src/components/coachmark/coachmark.ts:227— CDSCoachmark.updated has cognitive complexity 46 (threshold 15). Drivers by points: if/else 15 (34 pts), ternaries 2 (9 pts), boolean chains 3 (nesting depth added 26). Of this number, 22 points are the body's own statements and 24 belong to one function literal inside it that branches. 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.
FilterableMultiSelect.FilterableMultiSelect (cognitive 45) packages/react/src/components/MultiSelect/FilterableMultiSelect.tsx:331— FilterableMultiSelect.FilterableMultiSelect has cognitive complexity 45 (threshold 15). Drivers by points: if/else 47 (67 pts), boolean chains 34, ternaries 22 (32 pts), match/switch 2 (nesting depth added 30). 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 (FilterableMultiSelect.FilterableMultiSelect::stateReducer) 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.
EditInPlace.EditInPlace (cognitive 44) packages/react/src/components/EditInPlace/EditInPlace.tsx:140— EditInPlace.EditInPlace has cognitive complexity 44 (threshold 15). Drivers by points: if/else 20 (25 pts), boolean chains 13, ternaries 3 (4 pts), loops 1, match/switch 1 (nesting depth added 6). Most of this is not in the body itself: 11 of the 44 points are its own statements and the rest belongs to 11 function items inside it that branch (onBlurHandler, handleToolbarMouseDown, onSaveHandler, …). 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.
FloatingMenu.FloatingMenu (cognitive 43) packages/react/src/internal/FloatingMenu.tsx:237— FloatingMenu.FloatingMenu has cognitive complexity 43 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 12, ternaries 7 (10 pts) (nesting depth added 9). Most of this is not in the body itself: 11 of the 43 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 264, a function literal at line 386, focusMenuContent, …). 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.
OverflowMenu.OverflowMenu (cognitive 43) packages/react/src/components/OverflowMenu/OverflowMenu.tsx:260— OverflowMenu.OverflowMenu has cognitive complexity 43 (threshold 15). Drivers by points: if/else 21, boolean chains 16, ternaries 5, match/switch 1. Most of this is not in the body itself: 6 of the 43 points are its own statements and the rest belongs to 18 function items inside it that branch (a function literal at line 339, a function literal at line 351, a function literal at line 361, …). 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.
Tag.TagBase (cognitive 42) packages/react/src/components/Tag/Tag.tsx:143— Tag.TagBase has cognitive complexity 42 (threshold 15). Drivers by points: ternaries 16 (25 pts), boolean chains 13, if/else 4 (nesting depth added 9). Of this number, 41 points are the body's own statements and 1 belongs 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.
NotificationsPanel.NotificationsPanel (cognitive 41) packages/react/src/components/NotificationsPanel/NotificationsPanel.tsx:350— NotificationsPanel.NotificationsPanel has cognitive complexity 41 (threshold 15). Drivers by points: boolean chains 21, if/else 14 (17 pts), ternaries 3 (nesting depth added 3). Most of this is not in the body itself: 10 of the 41 points are its own statements and the rest belongs to 13 function items inside it that branch (renderNotification, a function literal at line 457, handleAnimationEnd, …). 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.
Tabs.Tab (cognitive 40) packages/react/src/components/Tabs/Tabs.tsx:1303— Tabs.Tab has cognitive complexity 40 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 16, ternaries 6 (7 pts) (nesting depth added 6). Of this number, 17 points are the body's own statements and 23 belong to 8 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.
ibm-products-update-tearsheet.transform (cognitive 40) packages/upgrade/transforms/ibm-products-update-tearsheet.js:309— ibm-products-update-tearsheet.transform has cognitive complexity 40 (threshold 15). Drivers by points: if/else 14 (32 pts), ternaries 2 (5 pts), boolean chains 3 (nesting depth added 21). Most of this is not in the body itself: 1 of the 40 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 397, 326, 345, …). 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.
icons-react-size-prop.transform (cognitive 39) packages/upgrade/transforms/icons-react-size-prop.js:16— icons-react-size-prop.transform has cognitive complexity 39 (threshold 15). Drivers by points: if/else 23 (27 pts), boolean chains 10, loops 1, ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 3 of the 39 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 147, 98, 55, …). 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.
CDSSlider._handleClick (cognitive 39) packages/web-components/src/components/slider/slider.ts:376— CDSSlider._handleClick has cognitive complexity 39 (threshold 15). Drivers by points: if/else 12 (27 pts), ternaries 2 (10 pts), boolean chains 2 (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.
MultiSelect.MultiSelect (cognitive 38) packages/react/src/components/MultiSelect/MultiSelect.tsx:299— MultiSelect.MultiSelect has cognitive complexity 38 (threshold 15). Drivers by points: boolean chains 43, if/else 23 (40 pts), ternaries 13 (16 pts), loops 1 (2 pts), match/switch 1 (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 (MultiSelect.MultiSelect::stateReducer) 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.
Search.Search (cognitive 37) packages/react/src/components/Search/Search.tsx:131— Search.Search has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 12 (14 pts), boolean chains 12, if/else 9 (11 pts) (nesting depth added 4). Of this number, 23 points are the body's own statements and 14 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.
fixEventsPlugin.fixEventsPlugin (cognitive 37) packages/react/src/components/DatePicker/plugins/fixEventsPlugin.ts:19— fixEventsPlugin.fixEventsPlugin has cognitive complexity 37 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 14, ternaries 1 (3 pts) (nesting depth added 7). None of this is in the body itself: all 37 points belong to 6 function literals inside it that branch (lines 67, 108, 25, …). 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.
PaginationNav.PaginationNav (cognitive 37) packages/react/src/components/PaginationNav/PaginationNav.tsx:361— PaginationNav.PaginationNav has cognitive complexity 37 (threshold 15). Drivers by points: boolean chains 16, if/else 10 (13 pts), ternaries 5 (7 pts), match/switch 1 (nesting depth added 5). Most of this is not in the body itself: 11 of the 37 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 466, pageWouldBeHidden, jumpToNext, …). 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.
CDSDropdown._handleKeydownInner (cognitive 37) packages/web-components/src/components/dropdown/dropdown.ts:229— CDSDropdown._handleKeydownInner has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (26 pts), match/switch 2 (4 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 19). Of this number, 18 points are the body's own statements and 19 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.
CDSSlider.shouldUpdate (cognitive 37) packages/web-components/src/components/slider/slider.ts:896— CDSSlider.shouldUpdate has cognitive complexity 37 (threshold 15). Drivers by points: if/else 20 (32 pts), boolean chains 5 (nesting depth added 12). None of this is in the body itself: all 37 points belong to 3 function literals inside it that branch (lines 902, 933, 943). 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.
CDSPasswordInput.render (cognitive 37) packages/web-components/src/components/password-input/password-input.ts:140— CDSPasswordInput.render has cognitive complexity 37 (threshold 15). Drivers by points: boolean chains 16, ternaries 10 (11 pts), if/else 7 (10 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.
FilterableMultiSelect.FilterableMultiSelect::stateReducer (cognitive 36) packages/react/src/components/MultiSelect/FilterableMultiSelect.tsx:694— FilterableMultiSelect.FilterableMultiSelect::stateReducer has cognitive complexity 36 (threshold 15). Drivers by points: if/else 14 (25 pts), boolean chains 6, ternaries 2 (4 pts), match/switch 1 (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. This shape REPEATS in the file: one other method here (FilterableMultiSelect.FilterableMultiSelect) 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.
NumberInput.NumberInput::handleStep (cognitive 36) REDACTED:845— NumberInput.NumberInput::handleStep has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (27 pts), boolean chains 7, ternaries 1 (2 pts) (nesting depth added 15). 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. This shape REPEATS in the file: one other method here (NumberInput.NumberInput) 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.
NumberInput.NumberInput (cognitive 36) REDACTED:594— NumberInput.NumberInput has cognitive complexity 36 (threshold 15). Drivers by points: if/else 45 (70 pts), ternaries 29 (41 pts), boolean chains 35 (nesting depth added 37). 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 (NumberInput.NumberInput::handleStep) 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.
PasswordInput.PasswordInput (cognitive 36) packages/react/src/components/TextInput/PasswordInput.tsx:182— PasswordInput.PasswordInput has cognitive complexity 36 (threshold 15). Drivers by points: boolean chains 20, if/else 9 (12 pts), ternaries 4 (nesting depth added 3). 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, 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.
TextInput.TextInput (cognitive 36) packages/react/src/components/TextInput/TextInput.tsx:192— TextInput.TextInput has cognitive complexity 36 (threshold 15). Drivers by points: boolean chains 17, if/else 7 (12 pts), ternaries 6 (7 pts) (nesting depth added 6). Of this number, 23 points are the body's own statements and 13 belong to 6 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.
Resizer.Resizer (cognitive 36) packages/react/src/components/Resizer/Resizer.tsx:56— Resizer.Resizer has cognitive complexity 36 (threshold 15). Drivers by points: if/else 25 (27 pts), ternaries 4 (5 pts), boolean chains 4 (nesting depth added 3). None of this is in the body itself: all 36 points belong to 16 function items inside it that branch (handleDoubleClick, a function literal at line 118, a function literal at line 159, …). 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.
enable-v12-overflowmenu.transform (cognitive 36) packages/upgrade/transforms/enable-v12-overflowmenu.js:29— enable-v12-overflowmenu.transform has cognitive complexity 36 (threshold 15). Drivers by points: if/else 20 (30 pts), boolean chains 5, loops 1 (nesting depth added 10). Most of this is not in the body itself: 4 of the 36 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 95, a function literal at line 86, a function literal at line 38, …). 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.
CDSOverflowMenu.updated (cognitive 36) packages/web-components/src/components/overflow-menu/overflow-menu.ts:410— CDSOverflowMenu.updated has cognitive complexity 36 (threshold 15). Drivers by points: if/else 18 (28 pts), boolean chains 7, ternaries 1 (nesting depth added 10). Of this number, 32 points are the body's own statements and 4 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.
Tile.ExpandableTile (cognitive 35) packages/react/src/components/Tile/Tile.tsx:780— Tile.ExpandableTile has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 10 (16 pts), boolean chains 10, if/else 8 (9 pts) (nesting depth added 7). Of this number, 16 points are the body's own statements and 19 belong to 6 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.
ItemOptionForValueField.ItemOptionForValueField (cognitive 35) packages/react/src/components/ConditionBuilder/ConditionBuilderItem/ConditionBuilderItemOption/ItemOptionForValueField.tsx:43— ItemOptionForValueField.ItemOptionForValueField has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (15 pts), ternaries 9 (14 pts), boolean chains 6 (nesting depth added 8). Most of this is not in the body itself: 7 of the 35 points are its own statements and the rest belongs to 7 function items inside it that branch (onClickHandler, a function literal at line 220, a function literal at line 120, …). 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.
CDSTextInput.render (cognitive 35) packages/web-components/src/components/text-input/text-input.ts:349— CDSTextInput.render has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 18, ternaries 12 (13 pts), if/else 4 (nesting depth added 1). Of this number, 34 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.
Tearsheet.TearsheetInternal (cognitive 34) packages/react/src/components/Tearsheet/Tearsheet.tsx:190— Tearsheet.TearsheetInternal has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 8, ternaries 7 (nesting depth added 6). Most of this is not in the body itself: 11 of the 34 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 342, 269, 256, …). 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.
Column.getClassNameForBreakpoints (cognitive 33) packages/react/src/components/Grid/Column.tsx:364— Column.getClassNameForBreakpoints has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (23 pts), ternaries 2 (8 pts), boolean chains 1, loops 1 (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.
TreeNode.TreeNode::handleKeyDown (cognitive 33) packages/react/src/components/TreeView/TreeNode.tsx:398— TreeNode.TreeNode::handleKeyDown has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15 (27 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 14). 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 (TreeNode.TreeNode) 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.
refactor-to-callout.transform (cognitive 32) packages/upgrade/transforms/refactor-to-callout.js:15— refactor-to-callout.transform has cognitive complexity 32 (threshold 15). Drivers by points: if/else 16 (25 pts), boolean chains 4, ternaries 2 (3 pts) (nesting depth added 10). Most of this is not in the body itself: 1 of the 32 points is its own statement and the rest belongs to 7 function items inside it that branch (a function literal at line 41, a function literal at line 135, a function literal at line 113, …). 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.
CDSCodeSnippet.render (cognitive 32) packages/web-components/src/components/code-snippet/code-snippet.ts:372— CDSCodeSnippet.render has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 16 (17 pts), boolean chains 9, if/else 6 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CDSSlider.render (cognitive 32) packages/web-components/src/components/slider/slider.ts:969— CDSSlider.render has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 13 (22 pts), boolean chains 10 (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.
DataTable.DataTable (cognitive 31) packages/react/src/components/DataTable/DataTable.tsx:351— DataTable.DataTable has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 12, ternaries 10 (11 pts), if/else 8 (nesting depth added 1). Most of this is not in the body itself: 3 of the 31 points are its own statements and the rest belongs to 13 function items inside it that branch (getSelectionProps, getExpandHeaderProps, a function literal at line 693, …). 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.
Calendar.Calendar (cognitive 31) packages/react/src/components/DatePicker/next/components/Calendar.tsx:53— Calendar.Calendar has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 12, ternaries 4 (6 pts) (nesting depth added 3). Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 114, 249, 97, …). 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.
ConditionBuilderContent.ConditionBuilderContent (cognitive 31) packages/react/src/components/ConditionBuilder/ConditionBuilderContent/ConditionBuilderContent.tsx:41— ConditionBuilderContent.ConditionBuilderContent has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 7 (12 pts), boolean chains 10, if/else 9 (nesting depth added 5). Most of this is not in the body itself: 10 of the 31 points are its own statements and the rest belongs to 6 function items inside it that branch (onChangeHandler, a function literal at line 91, onStartConditionBuilder, …). 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.
CDSDropdown.render (cognitive 31) packages/web-components/src/components/dropdown/dropdown.ts:1284— CDSDropdown.render has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 20 (24 pts), boolean chains 7 (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.
CheckboxGroup.CheckboxGroup (cognitive 30) packages/react/src/components/CheckboxGroup/CheckboxGroup.tsx:54— CheckboxGroup.CheckboxGroup has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 11 (17 pts), boolean chains 12, if/else 1 (nesting depth added 6). Of this number, 15 points are the body's own statements and 15 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.
form-associated.FormAssociatedMixin (cognitive 30) packages/web-components/src/globals/mixins/form-associated.ts:43— form-associated.FormAssociatedMixin has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 10, loops 1 (2 pts) (nesting depth added 5). Of this number, 28 points are the body's own statements and 2 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.
handleKeyPressForPopover (cognitive 30) packages/react/src/components/ConditionBuilder/utils/handleKeyboardEvents.js:68— handleKeyPressForPopover has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (26 pts), match/switch 1 (2 pts), boolean chains 1, other 1 (nesting depth added 15). Of this number, 26 points are the body's own statements and 4 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.
handleKeyboardEvents.handleKeyPressForMainContent (cognitive 29) packages/react/src/components/ConditionBuilder/utils/handleKeyboardEvents.js:215— handleKeyboardEvents.handleKeyPressForMainContent has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (28 pts), match/switch 1 (nesting depth added 14). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CDSOverflowMenuBody._handleKeydown (cognitive 29) packages/web-components/src/components/overflow-menu/overflow-menu-body.ts:135— CDSOverflowMenuBody._handleKeydown has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (23 pts), boolean chains 6 (nesting depth added 13). Of this number, 20 points are the body's own statements and 9 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.
CDSModal.updated (cognitive 29) packages/web-components/src/components/modal/modal.ts:373— CDSModal.updated has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (26 pts), boolean chains 3 (nesting depth added 15). 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.
CDSNumberInput.willUpdate (cognitive 29) packages/web-components/src/components/number-input/number-input.ts:504— CDSNumberInput.willUpdate has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (26 pts), boolean chains 3 (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.
storySort (cognitive 29) packages/react/.storybook/preview.js:231— storySort has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 5, other 2, loops 1 (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.
CDSDatePicker._setCalendar (cognitive 28) packages/web-components/src/components/date-picker/date-picker.ts:286— CDSDatePicker._setCalendar has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (25 pts), boolean chains 3 (nesting depth added 10). Of this number, 23 points are the body's own statements and 5 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.
CDSTable.updated (cognitive 28) packages/web-components/src/components/data-table/table.ts:742— CDSTable.updated has cognitive complexity 28 (threshold 15). Drivers by points: if/else 20 (26 pts), boolean chains 2 (nesting depth added 6). Of this number, 20 points are the body's own statements and 8 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.
AddSelectBody.AddSelectBody (cognitive 27) packages/react/src/components/AddSelect/AddSelectBody.tsx:130— AddSelectBody.AddSelectBody has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 9, match/switch 1 (nesting depth added 5). Most of this is not in the body itself: 8 of the 27 points are its own statements and the rest belongs to 5 function items inside it that branch (handleKeyDown, a function literal at line 191, getItems, …). 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.
ibm-products-update-http-errors.transform (cognitive 27) packages/upgrade/transforms/ibm-products-update-http-errors.js:22— ibm-products-update-http-errors.transform has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (26 pts), boolean chains 1 (nesting depth added 14). Most of this is not in the body itself: 3 of the 27 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 35, 127, 76, …). 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.
CDSSidePanel.render (cognitive 27) packages/web-components/src/components/side-panel/side-panel.ts:924— CDSSidePanel.render has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 17, boolean chains 9, if/else 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Select.Select (cognitive 26) packages/react/src/components/Select/Select.tsx:149— Select.Select has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 19, if/else 4, ternaries 3. Of this number, 18 points are the body's own statements and 8 belong to 3 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.
OptionsTile.OptionsTile (cognitive 26) packages/react/src/components/OptionsTile/OptionsTile.tsx:123— OptionsTile.OptionsTile has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 11, ternaries 2 (nesting depth added 1). Most of this is not in the body itself: 7 of the 26 points are its own statements and the rest belongs to 4 function items inside it that branch (renderTitle, expand, collapse, …). 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.
CDSMultiSelect.updated (cognitive 26) packages/web-components/src/components/multi-select/multi-select.ts:864— CDSMultiSelect.updated has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 5 (nesting depth added 8). 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 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.
CDSSelect.render (cognitive 26) packages/web-components/src/components/select/select.ts:414— CDSSelect.render has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 11 (15 pts), boolean chains 9, if/else 2 (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.
CDSTreeNode.render (cognitive 26) packages/web-components/src/components/tree-view/tree-node.ts:258— CDSTreeNode.render has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 9 (24 pts), boolean chains 1, if/else 1 (nesting depth added 15). 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.
icons.icons.validate (cognitive 25) packages/icon-build-helpers/src/metadata/extensions/icons.js:65— icons.icons.validate has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 6 (9 pts) (nesting depth added 13). Of this number, 22 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.
DatePickerInput.DatePickerInput (cognitive 25) packages/react/src/components/DatePicker/next/components/DatePickerInput.tsx:181— DatePickerInput.DatePickerInput has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 15, ternaries 6 (10 pts) (nesting depth added 4). 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.
DatePicker.DatePicker (cognitive 25) packages/react/src/components/DatePicker/next/components/DatePicker.tsx:107— DatePicker.DatePicker has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 11, if/else 8 (9 pts), ternaries 4 (5 pts) (nesting depth added 2). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 176, handleIconClick, a function literal at line 226, …). 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.
RadioButtonGroup.RadioButtonGroup (cognitive 25) packages/react/src/components/RadioButtonGroup/RadioButtonGroup.tsx:144— RadioButtonGroup.RadioButtonGroup has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 12, ternaries 6 (7 pts), if/else 5 (6 pts) (nesting depth added 2). Of this number, 18 points are the body's own statements and 7 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.
Tabs.TabListVertical (cognitive 25) packages/react/src/components/Tabs/Tabs.tsx:974— Tabs.TabListVertical has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (16 pts), ternaries 3 (5 pts), boolean chains 4 (nesting depth added 6). Most of this is not in the body itself: 5 of the 25 points are its own statements and the rest belongs to 7 function items inside it that branch (onKeyDown, a function literal at line 1057, a function literal at line 1042, …). 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.
ProgressBar.ProgressBar (cognitive 25) packages/react/src/components/ProgressBar/ProgressBar.tsx:64— ProgressBar.ProgressBar has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 7, ternaries 4 (nesting depth added 3). Of this number, 16 points are the body's own statements and 9 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.
useGuidebannerScroll.useGuidebannerScroll (cognitive 25) packages/react/src/components/Guidebanner/useGuidebannerScroll.ts:24— useGuidebannerScroll.useGuidebannerScroll has cognitive complexity 25 (threshold 15). Drivers by points: if/else 15, boolean chains 6, ternaries 4. Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 15 function literals inside it that branch (lines 208, 57, 108, …). 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.
ScrollGradient.ScrollGradient (cognitive 25) packages/react/src/components/ScrollGradient/ScrollGradient.tsx:41— ScrollGradient.ScrollGradient has cognitive complexity 25 (threshold 15). Drivers by points: if/else 19 (20 pts), boolean chains 3, ternaries 2 (nesting depth added 1). Most of this is not in the body itself: 5 of the 25 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 83, setGradientOnIntersection, a function literal at line 130, …). 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.
swipeEvents.registerSwipeEvents (cognitive 25) packages/utilities/src/carousel/swipeEvents.ts:9— swipeEvents.registerSwipeEvents has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 3 (nesting depth added 8). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 4 function items inside it that branch (touchEndHandler, mouseUpHandler, wheelHandler, …). 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.
FloatingController.computePlacement (cognitive 25) packages/web-components/src/globals/controllers/floating-controller.ts:76— FloatingController.computePlacement has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 9 (13 pts), if/else 4 (6 pts), boolean chains 5, match/switch 1 (nesting depth added 6). Of this number, 24 points are the body's own statements and 1 belongs 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.
CDSAddSelectBody.render (cognitive 25) packages/web-components/src/components/add-select/add-select-body.ts:277— CDSAddSelectBody.render has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 8 (22 pts), boolean chains 3 (nesting depth added 14). Of this number, 20 points are the body's own statements and 5 belong to one function literal inside it that branches. 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.
CDSDropdown._handleUserInitiatedToggle (cognitive 25) packages/web-components/src/components/dropdown/dropdown.ts:687— CDSDropdown._handleUserInitiatedToggle has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (20 pts), ternaries 1 (4 pts), boolean chains 1 (nesting depth added 14). Of this number, 15 points are the body's own statements and 10 belong to one function literal inside it that branches. 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.
CDSComboBox.updated (cognitive 25) packages/web-components/src/components/combo-box/combo-box.ts:624— CDSComboBox.updated has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 4 (nesting depth added 11). 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.
CDSSidePanel.updated (cognitive 25) packages/web-components/src/components/side-panel/side-panel.ts:1125— CDSSidePanel.updated has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 8 (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.
CDSTearsheetHeaderContent._handleDecoratorChange (cognitive 25) packages/web-components/src/components/tearsheet/tearsheet-header-content.ts:312— CDSTearsheetHeaderContent._handleDecoratorChange has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 3 (8 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bob-bug-triage.parseBobStreamLine (cognitive 24) actions/issues/src/plugins/bob-bug-triage.js:205— bob-bug-triage.parseBobStreamLine has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 6 (14 pts), if/else 7 (8 pts), boolean chains 1, error handling 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.
Dialog.Dialog (cognitive 24) packages/react/src/components/Dialog/Dialog.tsx:138— Dialog.Dialog has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 10, ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 5 of the 24 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 191, a function literal at line 235, handleModalBackdropClick, …). 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.
FileUploaderDropContainer.FileUploaderDropContainer (cognitive 24) packages/react/src/components/FileUploader/FileUploaderDropContainer.tsx:112— FileUploaderDropContainer.FileUploaderDropContainer has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 3, error handling 1 (2 pts), ternaries 2 (nesting depth added 4). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 9 function items inside it that branch (a function literal at line 149, handleDrop, a function literal at line 193, …). 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.
NumberInput.validateNumberSeparators (cognitive 24) REDACTED:460— NumberInput.validateNumberSeparators has cognitive complexity 24 (threshold 15). Drivers by points: if/else 16 (17 pts), boolean chains 6, ternaries 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SideNav.SideNav (cognitive 24) packages/react/src/components/UIShell/SideNav.tsx:53— SideNav.SideNav has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 11, if/else 9, ternaries 4. Of this number, 15 points are the body's own statements and 9 belong to 6 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.
upgrade.upgrade (cognitive 24) packages/upgrade/src/commands/upgrade.js:14— upgrade.upgrade has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (18 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 9). 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, 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.
wc-add-barrel-imports.transform (cognitive 24) packages/upgrade/transforms/wc-add-barrel-imports.js:35— wc-add-barrel-imports.transform has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 4 (8 pts), boolean chains 6, ternaries 2 (nesting depth added 7). Of this number, 17 points are the body's own statements and 7 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.
CDSRadioButton.updated (cognitive 24) packages/web-components/src/components/radio-button/radio-button.ts:383— CDSRadioButton.updated has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 7, ternaries 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.
focus-plugin.default (cognitive 24) packages/web-components/src/components/date-picker/focus-plugin.ts:69— focus-plugin.default has cognitive complexity 24 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 2, ternaries 1 (nesting depth added 4). None of this is in the body itself: all 24 points belong to 5 function literals inside it that branch (lines 104, 82, 134, …). 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.
Notification.ActionableNotification (cognitive 23) packages/react/src/components/Notification/Notification.tsx:929— Notification.ActionableNotification has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 14, if/else 5, ternaries 4. Of this number, 15 points are the body's own statements and 8 belong to 4 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.
NumberInput.parseNumberWithLocale (cognitive 23) REDACTED:371— NumberInput.parseNumberWithLocale has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 6, loops 1 (nesting depth added 6). Of this number, 16 points are the body's own statements and 7 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.
ConditionBuilderItemDate.ConditionBuilderItemDate (cognitive 23) packages/react/src/components/ConditionBuilder/ConditionBuilderItem/ConditionBuilderItemDate/ConditionBuilderItemDate.tsx:26— ConditionBuilderItemDate.ConditionBuilderItemDate has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 9, ternaries 2 (nesting depth added 3). Most of this is not in the body itself: 5 of the 23 points are its own statements and the rest belongs to 4 function items inside it that branch (getParsedDate, onCloseHandler, onKeyPressHandler, …). 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.
InterstitialScreenFooter.InterstitialScreenFooter (cognitive 23) packages/react/src/components/InterstitialScreen/InterstitialScreenFooter.tsx:72— InterstitialScreenFooter.InterstitialScreenFooter has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 14, if/else 5, ternaries 3 (4 pts) (nesting depth added 1). Most of this is not in the body itself: 3 of the 23 points are its own statements and the rest belongs to 4 function items inside it that branch (getFooterContent, handleAction, a function literal at line 105, …). 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.
SidePanel.SidePanel::renderHeader (cognitive 23) packages/react/src/components/SidePanel/SidePanel.tsx:848— SidePanel.SidePanel::renderHeader has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 19, if/else 3, 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.
CDSMenu._fitValue (cognitive 23) packages/web-components/src/components/menu/menu.ts:344— CDSMenu._fitValue has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 11 (12 pts), boolean chains 7, if/else 4 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CDSDropdown._handleKeypressInner (cognitive 23) packages/web-components/src/components/dropdown/dropdown.ts:449— CDSDropdown._handleKeypressInner has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (16 pts), match/switch 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.
CDSActionableNotification._handleBlur (cognitive 23) packages/web-components/src/components/notification/actionable-notification.ts:148— CDSActionableNotification._handleBlur has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 13, if/else 5 (10 pts) (nesting depth added 5). 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.
CDSTreeNode.updated (cognitive 23) packages/web-components/src/components/tree-view/tree-node.ts:217— CDSTreeNode.updated has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 7 (9 pts), boolean chains 2 (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.
postcss-fix-host-pseudo.fixHostPseudo.Once (cognitive 23) packages/web-components/tools/postcss-fix-host-pseudo.js:58— postcss-fix-host-pseudo.fixHostPseudo.Once has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (6 pts), boolean chains 5 (nesting depth added 11). None of this is in the body itself: all 23 points belong to one function literal inside it that branches (line 61). 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.
Button.Button (cognitive 22) packages/react/src/components/Button/Button.tsx:147— Button.Button has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 3, ternaries 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ContentSwitcher.ContentSwitcher (cognitive 22) packages/react/src/components/ContentSwitcher/ContentSwitcher.tsx:75— ContentSwitcher.ContentSwitcher has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 7, ternaries 1 (nesting depth added 4). None of this is in the body itself: all 22 points belong to 6 function items inside it that branch (handleChildChange, a function literal at line 184, a function literal at line 95, …). 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.
CDSNumberInput._getInputValidity (cognitive 22) packages/web-components/src/components/number-input/number-input.ts:604— CDSNumberInput._getInputValidity has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 5, ternaries 2 (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.
categories.categories.validate (cognitive 21) packages/icon-build-helpers/src/metadata/extensions/categories.js:74— categories.categories.validate has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (12 pts), if/else 4 (9 pts) (nesting depth added 11). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Menu.Menu::fitValue (cognitive 21) packages/react/src/components/Menu/Menu.tsx:301— Menu.Menu::fitValue has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 9, boolean chains 7, if/else 5. 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.
CardActions.CardActions (cognitive 21) packages/react/src/components/Card/CardActions.tsx:79— CardActions.CardActions has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 17, if/else 2, ternaries 1 (2 pts) (nesting depth added 1). None of this is in the body itself: all 21 points belong to 3 function literals inside it that branch (lines 94, 160, 173). 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.
Checkbox.Checkbox (cognitive 21) packages/react/src/components/Checkbox/Checkbox.tsx:114— Checkbox.Checkbox has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 6 (8 pts), boolean chains 7, if/else 6 (nesting depth added 2). Of this number, 13 points are the body's own statements and 8 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.
Tile.ClickableTile (cognitive 21) packages/react/src/components/Tile/Tile.tsx:222— Tile.ClickableTile has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 11, if/else 5 (7 pts), ternaries 3 (nesting depth added 2). Of this number, 19 points are the body's own statements and 2 belong 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.
InterstitialScreenBody.InterstitialScreenBody (cognitive 21) packages/react/src/components/InterstitialScreen/InterstitialScreenBody.tsx:56— InterstitialScreenBody.InterstitialScreenBody has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 7 (9 pts), if/else 6 (7 pts), boolean chains 5 (nesting depth added 3). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 5 function items inside it that branch (a function literal at line 139, renderBody, a function literal at line 81, …). 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.
PageHeader.PageHeader (cognitive 21) packages/react/src/components/PageHeader/PageHeader.tsx:117— PageHeader.PageHeader has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 5, boolean chains 4 (nesting depth added 3). None of this is in the body itself: all 21 points belong to 6 function literals inside it that branch (lines 188, 150, 154, …). 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.
CDSNumberInput.render (cognitive 21) packages/web-components/src/components/number-input/number-input.ts:833— CDSNumberInput.render has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 11, boolean chains 8, if/else 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.
fn::enter (cognitive 21) packages/icon-build-helpers/src/metadata/extensions/output/optimizer.js:32— fn::enter has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 6 (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.
run.runPlugins (cognitive 20) actions/issues/src/run.js:21— run.runPlugins has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (6 pts), loops 2 (3 pts), error handling 1 (2 pts) (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.
TreeNode.TreeNode (cognitive 20) packages/react/src/components/TreeView/TreeNode.tsx:250— TreeNode.TreeNode has cognitive complexity 20 (threshold 15). Drivers by points: if/else 35 (51 pts), ternaries 11 (17 pts), boolean chains 10 (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. This shape REPEATS in the file: one other method here (TreeNode.TreeNode::handleKeyDown) 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.
enable-v12-tile-default-icons.transform (cognitive 20) packages/upgrade/transforms/enable-v12-tile-default-icons.js:19— enable-v12-tile-default-icons.transform has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 3 (nesting depth added 6). Most of this is not in the body itself: 9 of the 20 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 40, 85, 121, …). 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.
enable-v12-tile-radio-icons.transform (cognitive 20) packages/upgrade/transforms/enable-v12-tile-radio-icons.js:19— enable-v12-tile-radio-icons.transform has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 3 (nesting depth added 6). Most of this is not in the body itself: 9 of the 20 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 40, 85, 121, …). 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.
CDSActionSet._renderActionsFromProp (cognitive 20) packages/web-components/src/components/action-set/action-set.ts:379— CDSActionSet._renderActionsFromProp has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 5, ternaries 2 (nesting depth added 6). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 409, 387, 407). 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.
CDSCodeSnippet.updated (cognitive 20) packages/web-components/src/components/code-snippet/code-snippet.ts:323— CDSCodeSnippet.updated has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (20 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CDSNumberInput._handleStep (cognitive 20) packages/web-components/src/components/number-input/number-input.ts:683— CDSNumberInput._handleStep has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 7, ternaries 3 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
executeBob (cognitive 20) actions/issues/src/plugins/bob-bug-triage.js:309— executeBob has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (9 pts), other 4, ternaries 2 (4 pts), boolean chains 2, loops 1 (nesting depth added 3). None of this is in the body itself: all 20 points belong to 9 function items inside it that branch (a function literal at line 426, (anonymous)::handleStdoutLine, a function literal at line 373, …). 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.
DatePickerInput.DatePickerInput (cognitive 19) packages/react/src/components/DatePickerInput/DatePickerInput.tsx:152— DatePickerInput.DatePickerInput has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7, boolean chains 6, ternaries 5 (6 pts) (nesting depth added 1). Of this number, 17 points are the body's own statements and 2 belong to 2 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.
Column.getClassNameForFlexGridBreakpoints (cognitive 19) packages/react/src/components/Grid/Column.tsx:437— Column.getClassNameForFlexGridBreakpoints has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 1, loops 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.
ibm-products-update-pdlc-status.transformer (cognitive 19) packages/upgrade/transforms/ibm-products-update-pdlc-status.js:23— ibm-products-update-pdlc-status.transformer has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (16 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 8). None of this is in the body itself: all 19 points belong to one function literal inside it that branches (line 36). 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.
keyboard-utils.mapKeyboardToStateMachineEvent (cognitive 19) packages/utilities/src/date-picker/primitives/keyboard-utils.ts:46— keyboard-utils.mapKeyboardToStateMachineEvent has cognitive complexity 19 (threshold 15). Drivers by points: if/else 15 (19 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.
CDSButton.render (cognitive 19) packages/web-components/src/components/button/button.ts:268— CDSButton.render has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 6 (9 pts), boolean chains 8, if/else 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.
CDSComboBox._handleInput (cognitive 19) packages/web-components/src/components/combo-box/combo-box.ts:109— CDSComboBox._handleInput has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 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.
CDSNumberInput._handleBlur (cognitive 19) packages/web-components/src/components/number-input/number-input.ts:199— CDSNumberInput._handleBlur has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 3 (9 pts), if/else 5 (8 pts), boolean chains 2 (nesting depth added 9). 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· main (cognitive 19) · ×1
main (cognitive 19) tasks/prepare-v12-storybook.mjs:442— main has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 4 (7 pts), if/else 3 (6 pts), loops 3 (4 pts), boolean chains 1, other 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.
Tooltip.Tooltip (cognitive 18) packages/react/src/components/Tooltip/Tooltip.tsx:118— Tooltip.Tooltip has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10, boolean chains 6, ternaries 2. Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 189, onMouseMove, a function literal at line 155, …). 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.
TableToolbarSearch.TableToolbarSearch (cognitive 18) packages/react/src/components/DataTable/TableToolbarSearch.tsx:135— TableToolbarSearch.TableToolbarSearch has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 6, ternaries 4 (nesting depth added 2). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 5 function items inside it that branch (handleExpand, a function literal at line 171, a function literal at line 179, …). 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.
Slider.Slider::onDragStart (cognitive 18) packages/react/src/components/Slider/Slider.tsx:596— Slider.Slider::onDragStart 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. This shape REPEATS in the file: one other method here (Slider.Slider) 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.
HeaderMenu.HeaderMenu (cognitive 18) packages/react/src/components/UIShell/HeaderMenu.tsx:103— HeaderMenu.HeaderMenu has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, if/else 7 (8 pts), ternaries 2 (nesting depth added 1). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 6 function items inside it that branch (handleMenuClose, handleOnClick, a function literal at line 201, …). 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.
CoachmarkContent.CoachmarkContent (cognitive 18) packages/react/src/components/Coachmark/CoachmarkContent.tsx:50— CoachmarkContent.CoachmarkContent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 4 (nesting depth added 4). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 71, 84, 97, …). 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.
ibm-products-update-userprofileimage.transform (cognitive 18) packages/upgrade/transforms/ibm-products-update-userprofileimage.js:22— ibm-products-update-userprofileimage.transform has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 1 (nesting depth added 4). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 76, ensureImport, a function literal at line 53, …). 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.
CDSPopover.updated (cognitive 18) packages/web-components/src/components/popover/popover.ts:416— CDSPopover.updated has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 3 (8 pts), if/else 4 (6 pts), boolean chains 4 (nesting depth added 7). Of this number, 13 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.
CDSMultiSelect._handleClickInner (cognitive 18) packages/web-components/src/components/multi-select/multi-select.ts:209— CDSMultiSelect._handleClickInner has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 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.
CDSActionableNotification.updated (cognitive 18) packages/web-components/src/components/notification/actionable-notification.ts:268— CDSActionableNotification.updated has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (16 pts), ternaries 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.
CDSPageHeaderActionsSet.setupOverflowDetection (cognitive 18) packages/web-components/src/components/page-header/page-header-actions-set/page-header-actions-set.ts:102— CDSPageHeaderActionsSet.setupOverflowDetection has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 3, loops 2 (nesting depth added 2). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 3 function items inside it that branch (checkOverflow, a function literal at line 172, a function literal at line 198). 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.
CDSSidePanel.getFocusable (cognitive 18) packages/web-components/src/components/side-panel/side-panel.ts:149— CDSSidePanel.getFocusable has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 3 (nesting depth added 2). 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: 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.
manageComment (cognitive 18) actions/issues/src/manage-comment.js:124— manageComment has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (14 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.
publish.publish (cognitive 17) packages/cli/src/commands/publish.js:44— publish.publish has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (13 pts), loops 1 (2 pts), boolean chains 1, error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
2020-02-17-update-pictogram-files.migrate (cognitive 17) packages/icon-build-helpers/src/metadata/migrations/2020-02-17-update-pictogram-files.js:16— 2020-02-17-update-pictogram-files.migrate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (3 pts) (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.
index.Toggletip (cognitive 17) packages/react/src/components/Toggletip/index.tsx:103— index.Toggletip has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 7, ternaries 1 (nesting depth added 1). None of this is in the body itself: all 17 points belong to 6 function items inside it that branch (onKeyDown, a function literal at line 173, a function literal at line 180, …). 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.
useResizeObserver.useResizeObserver (cognitive 17) packages/react/src/internal/useResizeObserver.ts:10— useResizeObserver.useResizeObserver has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 8 (nesting depth added 1). None of this is in the body itself: all 17 points belong to 6 function literals inside it that branch (lines 33, 76, 32, …). 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.
MultiSelect.MultiSelect::stateReducer (cognitive 17) packages/react/src/components/MultiSelect/MultiSelect.tsx:616— MultiSelect.MultiSelect::stateReducer has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 2, ternaries 1 (2 pts), match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (MultiSelect.MultiSelect) 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.
RadioTile.RadioTile (cognitive 17) packages/react/src/components/RadioTile/RadioTile.tsx:113— RadioTile.RadioTile has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6 (7 pts), if/else 5 (6 pts), boolean chains 4 (nesting depth added 2). Of this number, 11 points are the body's own statements and 6 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.
TearsheetHeaderContent.TearsheetHeaderContent (cognitive 17) packages/react/src/components/Tearsheet/TearsheetHeaderContent.tsx:61— TearsheetHeaderContent.TearsheetHeaderContent has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 8 (10 pts), boolean chains 7 (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.
json-pointer-references.jsonPointerReferences (cognitive 17) packages/themes/style-dictionary/preprocessors/json-pointer-references.js:29— json-pointer-references.jsonPointerReferences has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, loops 2 (nesting depth added 3). None of this is in the body itself: all 17 points belong to 3 function items inside it that branch (walk, lookup, resolve). 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.
ibm-products-update-tearsheet.transformTearsheetElement (cognitive 17) packages/upgrade/transforms/ibm-products-update-tearsheet.js:208— ibm-products-update-tearsheet.transformTearsheetElement has cognitive complexity 17 (threshold 15). Drivers by points: if/else 15, boolean chains 2. Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 222). 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.
sort-prop-types.transform (cognitive 17) packages/upgrade/transforms/sort-prop-types.js:15— sort-prop-types.transform has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3 (nesting depth added 4). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 3 function items inside it that branch (a function literal at line 30, getPropName, a function literal at line 60). 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.
carousel.initCarousel.performAnimation (cognitive 17) packages/utilities/src/carousel/carousel.ts:310— carousel.initCarousel.performAnimation has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 4 (nesting depth added 5). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 348, 318, 370). 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.
CDSSearch._handleKeys (cognitive 17) packages/web-components/src/components/search/search.ts:126— CDSSearch._handleKeys has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3 (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.
CDSDismissibleTag._handleClick (cognitive 17) packages/web-components/src/components/tag/dismissible-tag.ts:87— CDSDismissibleTag._handleClick has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 1 (nesting depth added 10). 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.
CDSRadioButton._handleKeydown (cognitive 17) packages/web-components/src/components/radio-button/radio-button.ts:196— CDSRadioButton._handleKeydown has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 3, ternaries 1 (3 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.
CDSAddSelectSelectionSummaryItem.render (cognitive 17) packages/web-components/src/components/add-select/add-select-selection-summary-item.ts:166— CDSAddSelectSelectionSummaryItem.render has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 13 (14 pts), boolean chains 3 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CDSComboBox._filterItems (cognitive 17) packages/web-components/src/components/combo-box/combo-box.ts:201— CDSComboBox._filterItems has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6 (7 pts), boolean chains 6, if/else 4 (nesting depth added 1). None of this is in the body itself: all 17 points belong to 2 function literals inside it that branch (lines 208, 225). 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.
CDSSlider._handleKeydown (cognitive 17) packages/web-components/src/components/slider/slider.ts:259— CDSSlider._handleKeydown has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 2 (nesting depth added 9). 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.
CDSSidePanel._adjustPageContent (cognitive 17) packages/web-components/src/components/side-panel/side-panel.ts:396— CDSSidePanel._adjustPageContent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (14 pts), ternaries 1 (3 pts) (nesting depth added 10). 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.
release.cherryPickCommitsFrom (cognitive 16) REDACTED:143— release.cherryPickCommitsFrom has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (11 pts), error handling 1 (2 pts), loops 2, boolean chains 1 (nesting depth added 8). Of this number, 15 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.
Card.CardComponent (cognitive 16) packages/react/src/components/Card/Card.tsx:35— Card.CardComponent has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 10, if/else 6. Of this number, 9 points are the body's own statements and 7 belong to 5 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.
TimePicker.TimePicker (cognitive 16) packages/react/src/components/TimePicker/TimePicker.tsx:144— TimePicker.TimePicker has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 6, ternaries 2. Of this number, 8 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.
AddSelectRow.AddSelectRow (cognitive 16) packages/react/src/components/AddSelect/AddSelectRow.tsx:152— AddSelectRow.AddSelectRow has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 9, if/else 5 (6 pts), ternaries 1 (nesting depth added 1). Of this number, 14 points are the body's own statements and 2 belong to 3 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.
AddSelectSelectionSummaryItem.AddSelectSelectionSummaryItem (cognitive 16) packages/react/src/components/AddSelect/AddSelectSelectionSummaryItem.tsx:99— AddSelectSelectionSummaryItem.AddSelectSelectionSummaryItem has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (7 pts), if/else 5, boolean chains 4 (nesting depth added 3). Of this number, 13 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
form-demo.FormDemo (cognitive 16) packages/react/src/components/Form/stories/form-demo.js:73— form-demo.FormDemo has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 9 (14 pts), boolean chains 1, if/else 1 (nesting depth added 5). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 246, 255, 270, …). 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.
ibm-products-update-page-header.transformer (cognitive 16) packages/upgrade/transforms/ibm-products-update-page-header.js:104— ibm-products-update-page-header.transformer has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 2 (nesting depth added 2). None of this is in the body itself: all 16 points belong to 5 function items inside it that branch (a function literal at line 196, a function literal at line 151, a function literal at line 117, …). 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.
CDSRadioButtonGroup.render (cognitive 16) packages/web-components/src/components/radio-button/radio-button-group.ts:243— CDSRadioButtonGroup.render has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 8 (11 pts), boolean chains 5 (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.
CDSModalBase._updateLoadingElement (cognitive 16) packages/web-components/src/components/modal/modal-base.ts:223— CDSModalBase._updateLoadingElement has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CDSTextarea.render (cognitive 16) packages/web-components/src/components/textarea/textarea.ts:170— CDSTextarea.render has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 9 (10 pts), boolean chains 4, if/else 2 (nesting depth added 1). Of this number, 13 points are the body's own statements and 3 belong to one function item 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.
CDSTabs.updated (cognitive 16) packages/web-components/src/components/tabs/tabs.ts:622— CDSTabs.updated has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CDSHeaderGlobalAction.updated (cognitive 16) packages/web-components/src/components/ui-shell/header-global-action.ts:154— CDSHeaderGlobalAction.updated has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 1 (nesting depth added 9). 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.
CDSTearsheetHeaderContent.render (cognitive 16) packages/web-components/src/components/tearsheet/tearsheet-header-content.ts:379— CDSTearsheetHeaderContent.render has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 12 (13 pts), boolean chains 3 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
findGitignoreFiles (cognitive 16) eslint.config.mjs:50— findGitignoreFiles has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 2 (3 pts), boolean chains 2 (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.
Change coupling clique: DismissibleTag.tsx, OperationalTag.tsx, SelectableTag.tsx packages/react/src/components/Tag/DismissibleTag.tsx— 3 files — `packages/react/src/components/Tag/DismissibleTag.tsx`, `packages/react/src/components/Tag/OperationalTag.tsx`, `packages/react/src/components/Tag/SelectableTag.tsx` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
Unstable project @carbon/react — @carbon/react has instability 0.86 with 1 dependents.
P12 · CI test-gate honesty· Coverage collected but not gated · ×1
Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
Duplication concentrated across 107 sibling directories (217 clone groups) packages/react/src/components/TextArea/TextArea.tsx:45— 217 duplicated blocks under packages/react/src/components/ have copies in at least two of the sibling directories AISkeleton, AspectRatio, BadgeIndicator, BigNumber, Breadcrumb, Button (+101 more sibling(s) not listed) — 94 of them are reported below, and 123 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 217 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 217 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 217 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.
Duplication concentrated across 16 sibling directories (133 clone groups) packages/react/src/components/PageHeader/overflowHandler.ts:27— 133 duplicated blocks under packages/ have copies in at least two of the sibling directories carbon-components, carbon-components-react, cli, feature-flags, icons, icons-react (+10 more sibling(s) not listed) — 114 of them are reported below, and 19 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 133 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 133 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 133 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.
Duplication concentrated across 79 sibling directories (120 clone groups) packages/web-components/src/components/password-input/password-input.ts:136— 120 duplicated blocks under packages/web-components/src/components/ have copies in at least two of the sibling directories accordion, action-set, add-select, ai-label, ai-skeleton, big-number (+73 more sibling(s) not listed) — 86 of them are reported below, and 34 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 120 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 120 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 120 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.
Duplication concentrated across 37 sibling directories (30 clone groups) packages/web-components/code-connect/checkbox/checkbox.figma.ts:59— 30 duplicated blocks under packages/web-components/code-connect/ have copies in at least two of the sibling directories breadcrumb, button, checkbox, combo-box, combo-button, content-switcher (+31 more sibling(s) not listed) — 12 of them are reported below, and 18 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 30 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 30 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 30 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.
Duplication concentrated across 38 sibling directories (20 clone groups) packages/react/code-connect/FileUploader/FileUploader.figma.ts:72— 20 duplicated blocks under packages/react/code-connect/ have copies in at least two of the sibling directories AILabel, Accordion, Breadcrumb, Button, Checkbox, CodeSnippet (+32 more sibling(s) not listed) — 11 of them are reported below, and 9 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 20 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 20 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 20 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 (205 matched lines × 2 locations) · ×1
Duplicated block with local edits (205 matched lines × 2 locations) packages/react/src/components/TextArea/TextArea.tsx:45— packages/react/src/components/TextArea/TextArea.tsx:45 · packages/react/src/components/TextInput/TextInput.tsx:35 — the two spans are one implementation copied and then locally edited — 996 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 (201 matched lines × 2 locations) · ×1
Duplicated block with local edits (201 matched lines × 2 locations) packages/react/src/components/ComposedModal/ComposedModal.tsx:257— packages/react/src/components/ComposedModal/ComposedModal.tsx:257 · packages/react/src/components/Modal/Modal.tsx:252 — the two spans are one implementation copied and then locally edited — 986 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 (155 matched lines × 2 locations) · ×1
Duplicated block with local edits (155 matched lines × 2 locations) packages/react/src/components/ComposedModal/ComposedModal-test.js:1024— packages/react/src/components/ComposedModal/ComposedModal-test.js:1024 · packages/react/src/components/Modal/Modal-test.js:960 — the two spans are one implementation copied and then locally edited — 1121 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 (147 matched lines × 2 locations) · ×1
Duplicated block with local edits (147 matched lines × 2 locations) packages/web-components/src/components/password-input/password-input.ts:136— packages/web-components/src/components/password-input/password-input.ts:136 · packages/web-components/src/components/text-input/text-input.ts:345 — the two spans are one implementation copied and then locally edited — 755 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.
Wholesale file copy (143 identical lines × 2 files) packages/themes/src/v10/g10.ts:8— packages/themes/src/v10/g10.ts:8 · packages/themes/src/v10/white.ts:8 — these 2 files are line-for-line copies of one another — 143 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.
Wholesale file copy (125 identical lines × 2 files) packages/themes/src/v10/g100.ts:8— packages/themes/src/v10/g100.ts:8 · packages/themes/src/v10/g90.ts:8 — these 2 files are line-for-line copies of one another — 125 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 (117 matched lines × 2 locations) · ×1
Duplicated block with local edits (117 matched lines × 2 locations) packages/web-components/src/components/date-picker/date-picker-input.ts:245— packages/web-components/src/components/date-picker/date-picker-input.ts:245 · packages/web-components/src/components/date-picker/next/components/date-picker-input.ts:293 — the two spans are one implementation copied and then locally edited — 577 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 (104 matched lines × 2 locations) · ×1
Duplicated block with local edits (104 matched lines × 2 locations) packages/react/src/components/TextInput/PasswordInput.tsx:280— packages/react/src/components/TextInput/PasswordInput.tsx:280 · packages/react/src/components/TextInput/TextInput.tsx:308 — the two spans are one implementation copied and then locally edited — 519 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.
Wholesale file copy (99 identical lines × 2 files) packages/react/src/components/PageHeader/overflowHandler.ts:27— packages/react/src/components/PageHeader/overflowHandler.ts:27 · packages/web-components/src/components/page-header/_story-assets/overflowHandler.ts:21 — these 2 files are line-for-line copies of one another — 99 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 (89 matched lines × 2 locations) · ×1
Duplicated block with local edits (89 matched lines × 2 locations) packages/utilities/src/date-picker/primitives/actions.ts:562— packages/utilities/src/date-picker/primitives/actions.ts:562 · packages/utilities/src/date-picker/primitives/actions.ts:937 — the two spans are one implementation copied and then locally edited — 429 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.
Wholesale file copy (88 identical lines × 2 files) packages/upgrade/transforms/enable-v12-tile-default-icons.js:14— packages/upgrade/transforms/enable-v12-tile-default-icons.js:14 · packages/upgrade/transforms/enable-v12-tile-radio-icons.js:14 — these 2 files are line-for-line copies of one another — 88 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 (85 matched lines × 2 locations) · ×1
Duplicated block with local edits (85 matched lines × 2 locations) packages/react/code-connect/DatePicker/DatePickerRange.figma.ts:20— packages/react/code-connect/DatePicker/DatePickerRange.figma.ts:20 · packages/react/code-connect/DatePicker/FluidDatePickerRange.figma.ts:20 — 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.
R10 · Code Duplication· Duplicated block with local edits (84 matched lines × 2 locations) · ×1
Duplicated block with local edits (84 matched lines × 2 locations) packages/web-components/src/components/tearsheet/_story-assets/step-tearsheet-preview.ts:120— packages/web-components/src/components/tearsheet/_story-assets/step-tearsheet-preview.ts:120 · packages/web-components/src/components/tearsheet/_story-assets/step-tearsheet.ts:109 — 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 (75 matched lines × 2 locations) · ×1
Duplicated block with local edits (75 matched lines × 2 locations) packages/web-components/src/components/date-picker/date-picker-input.ts:30— packages/web-components/src/components/date-picker/date-picker-input.ts:30 · packages/web-components/src/components/date-picker/next/components/date-picker-input.ts:33 — the two spans are one implementation copied and then locally edited — 511 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 (71 lines × 2 locations) packages/react/code-connect/MultiSelect/FluidFilterableMultiSelect.figma.ts:17— packages/react/code-connect/MultiSelect/FluidFilterableMultiSelect.figma.ts:17 · packages/react/code-connect/MultiSelect/FluidMultiSelect.figma.ts:17 — 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.
Wholesale file copy (71 identical lines × 2 files) packages/web-components/src/components/tag/operational-tag.ts:8— packages/web-components/src/components/tag/operational-tag.ts:8 · packages/web-components/src/components/tag/selectable-tag.ts:8 — these 2 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.
Wholesale file copy (70 identical lines × 2 files) packages/react/src/components/FluidMultiSelect/FluidFilterableMultiSelect.tsx:8— packages/react/src/components/FluidMultiSelect/FluidFilterableMultiSelect.tsx:8 · packages/react/src/components/FluidMultiSelect/FluidMultiSelect.tsx:8 — these 2 files are line-for-line copies of one another — 70 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 (70 matched lines × 2 locations) · ×1
Duplicated block with local edits (70 matched lines × 2 locations) packages/web-components/code-connect/date-picker/date-picker-range.figma.ts:18— packages/web-components/code-connect/date-picker/date-picker-range.figma.ts:18 · packages/web-components/code-connect/date-picker/fluid-date-picker-range.figma.ts:18 — the two spans are one implementation copied and then locally edited — 289 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 (68 matched lines × 2 locations) · ×1
Duplicated block with local edits (68 matched lines × 2 locations) packages/web-components/src/components/dialog/dialog.ts:107— packages/web-components/src/components/dialog/dialog.ts:107 · packages/web-components/src/components/modal/modal.ts:288 — the two spans are one implementation copied and then locally edited — 364 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 (65 lines × 2 locations) packages/react/code-connect/DataTable/DataTable.figma.ts:14— packages/react/code-connect/DataTable/DataTable.figma.ts:14 · packages/web-components/code-connect/data-table/data-table.figma.ts:18 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited.
Duplicated block (64 lines × 2 locations) packages/web-components/code-connect/date-picker/date-picker-simple.figma.ts:24— packages/web-components/code-connect/date-picker/date-picker-simple.figma.ts:24 · packages/web-components/code-connect/date-picker/date-picker-single.figma.ts: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 (62 matched lines × 2 locations) · ×1
Duplicated block with local edits (62 matched lines × 2 locations) packages/react/src/components/PageHeader/PageHeaderContentPageActions.tsx:67— packages/react/src/components/PageHeader/PageHeaderContentPageActions.tsx:67 · packages/react/src/components/PageHeaderDeprecated/PageHeader.tsx:357 — the two spans are one implementation copied and then locally edited — 374 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 (61 matched lines × 2 locations) · ×1
Duplicated block with local edits (61 matched lines × 2 locations) packages/react/src/components/Checkbox/Checkbox.tsx:172— packages/react/src/components/Checkbox/Checkbox.tsx:172 · packages/react/src/components/RadioButtonGroup/RadioButtonGroup.tsx:230 — the two spans are one implementation copied and then locally edited — 298 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) packages/utilities/src/overflowHandler/overflowHandler.ts:57— packages/utilities/src/overflowHandler/overflowHandler.ts:57 · packages/web-components/src/components/page-header/_story-assets/overflowHandler.ts:61 — the two spans are one implementation copied and then locally edited — 402 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.
Wholesale file copy (59 identical lines × 2 files) packages/web-components/src/components/ai-label/ai-label.ts:8— packages/web-components/src/components/ai-label/ai-label.ts:8 · packages/web-components/src/components/slug/slug.ts:8 — these 2 files are line-for-line copies of one another — 59 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 (58 matched lines × 2 locations) · ×1
Duplicated block with local edits (58 matched lines × 2 locations) packages/react/src/components/TextInput/ControlledPasswordInput.tsx:208— packages/react/src/components/TextInput/ControlledPasswordInput.tsx:208 · packages/react/src/components/TextInput/PasswordInput.tsx:315 — the two spans are one implementation copied and then locally edited — 259 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) packages/react/src/components/FluidComboBox/FluidComboBox.tsx:20— packages/react/src/components/FluidComboBox/FluidComboBox.tsx:20 · packages/react/src/components/FluidDropdown/FluidDropdown.tsx:15 — 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.
Duplicated block (53 lines × 2 locations) packages/react/code-connect/DatePicker/FluidDatePickerSimple.figma.ts:19— packages/react/code-connect/DatePicker/FluidDatePickerSimple.figma.ts:19 · packages/react/code-connect/DatePicker/FluidDatePickerSingle.figma.ts:19 — 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 (53 matched lines × 2 locations) · ×1
Duplicated block with local edits (53 matched lines × 2 locations) packages/react/src/components/ComposedModal/ComposedModalPresence.tsx:22— packages/react/src/components/ComposedModal/ComposedModalPresence.tsx:22 · packages/react/src/components/Modal/ModalPresence.tsx:21 — the two spans are one implementation copied and then locally edited — 275 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 (52 lines × 2 locations) packages/web-components/code-connect/date-picker/fluid-date-picker-simple.figma.ts:23— packages/web-components/code-connect/date-picker/fluid-date-picker-simple.figma.ts:23 · packages/web-components/code-connect/date-picker/fluid-date-picker-single.figma.ts:23 — 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.
Complex function ModalDialog (cyclomatic 55, cognitive 50) packages/react/src/components/Modal/Modal.tsx:288— ModalDialog has cyclomatic complexity 55 and cognitive complexity 50; 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 (anonymous) (cyclomatic 54, cognitive 53) packages/react/src/components/Slider/Slider.tsx:348— (anonymous) has cyclomatic complexity 54 and cognitive complexity 53; 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 (anonymous) (cyclomatic 54, cognitive 49) packages/react/src/components/TextArea/TextArea.tsx:215— (anonymous) has cyclomatic complexity 54 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 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 (anonymous) (cyclomatic 51, cognitive 87) packages/react/src/components/ComboBox/ComboBox.tsx:611— (anonymous) has cyclomatic complexity 51 and cognitive complexity 87; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _handleKeyDown (cyclomatic 44, cognitive 66) packages/web-components/src/components/date-picker/next/components/date-picker.ts:641— _handleKeyDown has cyclomatic complexity 44 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.
Complex function (anonymous) (cyclomatic 41, cognitive 34) packages/react/src/components/ComboBox/ComboBox.tsx:384— (anonymous) has cyclomatic complexity 41 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.
Complex function (anonymous) (cyclomatic 40, cognitive 35) packages/react/src/components/Dropdown/Dropdown.tsx:291— (anonymous) has cyclomatic complexity 40 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.
Complex function (anonymous) (cyclomatic 38, cognitive 35) packages/react/src/components/MultiSelect/MultiSelect.tsx:299— (anonymous) 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.
Complex function (anonymous) (cyclomatic 37, cognitive 37) REDACTED:594— (anonymous) has cyclomatic complexity 37 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 36, cognitive 34) packages/react/src/components/TextInput/PasswordInput.tsx:182— (anonymous) has cyclomatic complexity 36 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.
Complex function render (cyclomatic 35, cognitive 36) packages/web-components/src/components/password-input/password-input.ts:140— render has cyclomatic complexity 35 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _handleStateChange (cyclomatic 34, cognitive 47) packages/web-components/src/components/date-picker/next/components/date-picker.ts:245— _handleStateChange has cyclomatic complexity 34 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.
Complex function stateReducer (cyclomatic 34, cognitive 37) packages/react/src/components/MultiSelect/FilterableMultiSelect.tsx:694— stateReducer has cyclomatic complexity 34 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function computePlacement (cyclomatic 34, cognitive 33) packages/web-components/src/globals/controllers/floating-controller.ts:76— computePlacement has cyclomatic complexity 34 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 (anonymous) (cyclomatic 33, cognitive 38) packages/react/src/components/ComboBox/ComboBox.tsx:1179— (anonymous) has cyclomatic complexity 33 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.
Complex function FilterableMultiSelect (cyclomatic 32, cognitive 31) packages/react/src/components/MultiSelect/FilterableMultiSelect.tsx:331— FilterableMultiSelect has cyclomatic complexity 32 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 _fitValue (cyclomatic 32, cognitive 26) packages/web-components/src/components/menu/menu.ts:344— _fitValue has cyclomatic complexity 32 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 handleKeyDown (cyclomatic 30, cognitive 40) packages/react/src/components/TreeView/TreeView.tsx:178— handleKeyDown has cyclomatic complexity 30 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.
Complex function handleKeyDown (cyclomatic 30, cognitive 37) packages/react/src/components/DatePicker/next/hooks/useDatePicker.ts:487— handleKeyDown has cyclomatic complexity 30 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 30, cognitive 28) packages/react/src/components/Card/CardActions.tsx:94— (anonymous) has cyclomatic complexity 30 and cognitive complexity 28; 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.
R3 · Large Files· packages/react/src/components/DatePicker/DatePicker-test.js · ×1
packages/react/src/components/DatePicker/DatePicker-test.js: 2043 lines of code packages/react/src/components/DatePicker/DatePicker-test.js:1— packages/react/src/components/DatePicker/DatePicker-test.js has 2043 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· packages/react/src/components/Tearsheet/Tearsheet.stories.js · ×1
packages/react/src/components/Tearsheet/Tearsheet.stories.js: 1744 lines of code packages/react/src/components/Tearsheet/Tearsheet.stories.js:1— packages/react/src/components/Tearsheet/Tearsheet.stories.js has 1744 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· packages/react/src/components/ComboBox/ComboBox-test.js · ×1
packages/react/src/components/ComboBox/ComboBox-test.js: 1724 lines of code packages/react/src/components/ComboBox/ComboBox-test.js:1— packages/react/src/components/ComboBox/ComboBox-test.js has 1724 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· packages/react/src/components/Card/Card.stories.js · ×1
packages/react/src/components/Card/Card.stories.js: 1701 lines of code packages/react/src/components/Card/Card.stories.js:1— packages/react/src/components/Card/Card.stories.js has 1701 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· packages/react/src/components/Tabs/Tabs.tsx · ×1
packages/react/src/components/Tabs/Tabs.tsx: 1666 lines of code packages/react/src/components/Tabs/Tabs.tsx:1— packages/react/src/components/Tabs/Tabs.tsx has 1666 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· packages/react/src/components/Slider/Slider.tsx · ×1
packages/react/src/components/Slider/Slider.tsx: 1608 lines of code packages/react/src/components/Slider/Slider.tsx:1— packages/react/src/components/Slider/Slider.tsx has 1608 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· packages/react/src/components/Modal/Modal-test.js · ×1
packages/react/src/components/Modal/Modal-test.js: 1601 lines of code packages/react/src/components/Modal/Modal-test.js:1— packages/react/src/components/Modal/Modal-test.js has 1601 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· packages/react/src/components/ComboBox/ComboBox.tsx · ×1
packages/react/src/components/ComboBox/ComboBox.tsx: 1462 lines of code packages/react/src/components/ComboBox/ComboBox.tsx:1— packages/react/src/components/ComboBox/ComboBox.tsx has 1462 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· packages/web-components/src/components/tabs/tabs.stories.ts · ×1
packages/web-components/src/components/tabs/tabs.stories.ts: 1462 lines of code packages/web-components/src/components/tabs/tabs.stories.ts:1— packages/web-components/src/components/tabs/tabs.stories.ts has 1462 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· packages/react/src/components/Tabs/Tabs.stories.js · ×1
packages/react/src/components/Tabs/Tabs.stories.js: 1405 lines of code packages/react/src/components/Tabs/Tabs.stories.js:1— packages/react/src/components/Tabs/Tabs.stories.js has 1405 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· packages/web-components/src/components/dropdown/dropdown.ts · ×1
packages/web-components/src/components/dropdown/dropdown.ts: 1368 lines of code packages/web-components/src/components/dropdown/dropdown.ts:1— packages/web-components/src/components/dropdown/dropdown.ts has 1368 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· packages/web-components/src/components/card/card.stories.ts · ×1
packages/web-components/src/components/card/card.stories.ts: 1355 lines of code packages/web-components/src/components/card/card.stories.ts:1— packages/web-components/src/components/card/card.stories.ts has 1355 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: 1322 lines of code REDACTED:1— REDACTED has 1322 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· packages/react/src/components/Notification/Notification.tsx · ×1
packages/react/src/components/Notification/Notification.tsx: 1299 lines of code packages/react/src/components/Notification/Notification.tsx:1— packages/react/src/components/Notification/Notification.tsx has 1299 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· packages/web-components/src/components/ui-shell/ui-shell.stories.ts · ×1
packages/web-components/src/components/ui-shell/ui-shell.stories.ts: 1270 lines of code packages/web-components/src/components/ui-shell/ui-shell.stories.ts:1— packages/web-components/src/components/ui-shell/ui-shell.stories.ts has 1270 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· packages/react/src/components/MultiSelect/FilterableMultiSelect.tsx · ×1
packages/react/src/components/MultiSelect/FilterableMultiSelect.tsx: 1254 lines of code packages/react/src/components/MultiSelect/FilterableMultiSelect.tsx:1— packages/react/src/components/MultiSelect/FilterableMultiSelect.tsx has 1254 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· packages/web-components/src/components/slider/slider.ts · ×1
packages/web-components/src/components/slider/slider.ts: 1213 lines of code packages/web-components/src/components/slider/slider.ts:1— packages/web-components/src/components/slider/slider.ts has 1213 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· packages/web-components/src/components/multi-select/multi-select.stories.ts · ×1
packages/web-components/src/components/multi-select/multi-select.stories.ts: 1177 lines of code packages/web-components/src/components/multi-select/multi-select.stories.ts:1— packages/web-components/src/components/multi-select/multi-select.stories.ts has 1177 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· packages/utilities/src/date-picker/primitives/actions.ts · ×1
packages/utilities/src/date-picker/primitives/actions.ts: 1166 lines of code packages/utilities/src/date-picker/primitives/actions.ts:1— packages/utilities/src/date-picker/primitives/actions.ts has 1166 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· packages/react/src/components/ComposedModal/ComposedModal-test.js · ×1
packages/react/src/components/ComposedModal/ComposedModal-test.js: 1139 lines of code packages/react/src/components/ComposedModal/ComposedModal-test.js:1— packages/react/src/components/ComposedModal/ComposedModal-test.js has 1139 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· packages/web-components/src/components/page-header/page-header.stories.ts · ×1
packages/web-components/src/components/page-header/page-header.stories.ts: 1100 lines of code packages/web-components/src/components/page-header/page-header.stories.ts:1— packages/web-components/src/components/page-header/page-header.stories.ts has 1100 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· packages/web-components/src/components/side-panel/side-panel.ts · ×1
packages/web-components/src/components/side-panel/side-panel.ts: 1096 lines of code packages/web-components/src/components/side-panel/side-panel.ts:1— packages/web-components/src/components/side-panel/side-panel.ts has 1096 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· packages/react/src/components/DatePicker/DatePicker.tsx · ×1
packages/react/src/components/DatePicker/DatePicker.tsx: 1077 lines of code packages/react/src/components/DatePicker/DatePicker.tsx:1— packages/react/src/components/DatePicker/DatePicker.tsx has 1077 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· packages/web-components/src/components/date-picker/next/components/date-picker.ts · ×1
packages/web-components/src/components/date-picker/next/components/date-picker.ts: 1075 lines of code packages/web-components/src/components/date-picker/next/components/date-picker.ts:1— packages/web-components/src/components/date-picker/next/components/date-picker.ts has 1075 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· packages/react/src/components/Modal/Modal.tsx · ×1
packages/react/src/components/Modal/Modal.tsx: 1069 lines of code packages/react/src/components/Modal/Modal.tsx:1— packages/react/src/components/Modal/Modal.tsx has 1069 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· packages/react/src/components/AddSelect/AddSelect.stories.js · ×1
packages/react/src/components/AddSelect/AddSelect.stories.js: 1068 lines of code packages/react/src/components/AddSelect/AddSelect.stories.js:1— packages/react/src/components/AddSelect/AddSelect.stories.js has 1068 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· packages/upgrade/src/upgrades.js · ×1
packages/upgrade/src/upgrades.js: 1068 lines of code packages/upgrade/src/upgrades.js:1— packages/upgrade/src/upgrades.js has 1068 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· packages/react/src/components/PageHeader/PageHeader.stories.js · ×1
packages/react/src/components/PageHeader/PageHeader.stories.js: 1067 lines of code packages/react/src/components/PageHeader/PageHeader.stories.js:1— packages/react/src/components/PageHeader/PageHeader.stories.js has 1067 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· packages/react/src/components/MultiSelect/MultiSelect.tsx · ×1
packages/react/src/components/MultiSelect/MultiSelect.tsx: 1064 lines of code packages/react/src/components/MultiSelect/MultiSelect.tsx:1— packages/react/src/components/MultiSelect/MultiSelect.tsx has 1064 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· packages/web-components/src/components/data-table/table.ts · ×1
packages/web-components/src/components/data-table/table.ts: 1000 lines of code packages/web-components/src/components/data-table/table.ts:1— packages/web-components/src/components/data-table/table.ts has 1000 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· packages/react/src/components/Tile/Tile.tsx · ×1
packages/react/src/components/Tile/Tile.tsx: 999 lines of code packages/react/src/components/Tile/Tile.tsx:1— packages/react/src/components/Tile/Tile.tsx has 999 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· packages/react/src/components/SidePanel/SidePanel.tsx · ×1
packages/react/src/components/SidePanel/SidePanel.tsx: 977 lines of code packages/react/src/components/SidePanel/SidePanel.tsx:1— packages/react/src/components/SidePanel/SidePanel.tsx has 977 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· packages/web-components/src/components/add-select/add-select.stories.ts · ×1
packages/web-components/src/components/add-select/add-select.stories.ts: 969 lines of code packages/web-components/src/components/add-select/add-select.stories.ts:1— packages/web-components/src/components/add-select/add-select.stories.ts has 969 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· packages/web-components/src/components/modal/modal.stories.ts · ×1
packages/web-components/src/components/modal/modal.stories.ts: 959 lines of code packages/web-components/src/components/modal/modal.stories.ts:1— packages/web-components/src/components/modal/modal.stories.ts has 959 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· packages/web-components/src/components/multi-select/multi-select.ts · ×1
packages/web-components/src/components/multi-select/multi-select.ts: 958 lines of code packages/web-components/src/components/multi-select/multi-select.ts:1— packages/web-components/src/components/multi-select/multi-select.ts has 958 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· packages/react/src/components/Dialog/Dialog.tsx · ×1
packages/react/src/components/Dialog/Dialog.tsx: 933 lines of code packages/react/src/components/Dialog/Dialog.tsx:1— packages/react/src/components/Dialog/Dialog.tsx has 933 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· packages/react/src/components/DataTable/DataTable.tsx · ×1
packages/react/src/components/DataTable/DataTable.tsx: 925 lines of code packages/react/src/components/DataTable/DataTable.tsx:1— packages/react/src/components/DataTable/DataTable.tsx has 925 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· packages/web-components/src/components/number-input/number-input.ts · ×1
packages/web-components/src/components/number-input/number-input.ts: 907 lines of code packages/web-components/src/components/number-input/number-input.ts:1— packages/web-components/src/components/number-input/number-input.ts has 907 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· packages/react/src/components/Resizer/Resizer.stories.js · ×1
packages/react/src/components/Resizer/Resizer.stories.js: 889 lines of code packages/react/src/components/Resizer/Resizer.stories.js:1— packages/react/src/components/Resizer/Resizer.stories.js has 889 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· packages/react/src/components/Dropdown/Dropdown.tsx · ×1
packages/react/src/components/Dropdown/Dropdown.tsx: 850 lines of code packages/react/src/components/Dropdown/Dropdown.tsx:1— packages/react/src/components/Dropdown/Dropdown.tsx has 850 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling· The declared test suite includes a file that cannot be loaded · ×1
The declared test suite includes a file that cannot be loaded packages/web-components/tests/spec/accordion_spec.ts:9— This repository declares test tooling, and the ✓ above records that declaration — but packages/web-components/tests/spec/accordion_spec.ts and 24 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to.
Dead file (~2322 LoC) packages/react/src/components/DatePicker/DatePicker-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~2111 LoC) packages/react/src/components/ComboBox/ComboBox-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~1806 LoC) packages/react/src/components/Modal/Modal-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~1304 LoC) packages/react/src/components/ComposedModal/ComposedModal-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~915 LoC) packages/react/src/components/TextArea/TextArea-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~867 LoC) packages/react/src/components/Tile/Tile-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~866 LoC) packages/react/src/components/PageHeaderDeprecated/PageHeader-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~741 LoC) packages/react/src/components/SidePanel/SidePanel-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~682 LoC) packages/react/src/components/TreeView/TreeView-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~669 LoC) packages/utilities/src/overflowHandler/overflowHandler-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~647 LoC) packages/react/src/components/Loading/Loading-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~565 LoC) packages/react/src/components/Menu/Menu-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~534 LoC) packages/react/src/components/OverflowMenu/OverflowMenu-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~529 LoC) packages/react/src/components/RadioButtonGroup/RadioButtonGroup-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~498 LoC) packages/react/src/components/CheckboxGroup/CheckboxGroup-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~452 LoC) packages/react/src/components/Search/Search-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~445 LoC) packages/react/src/components/Dialog/Dialog-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~442 LoC) packages/react/src/components/Tag/Tag-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~394 LoC) packages/react/src/components/TimePicker/TimePicker-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~360 LoC) packages/utilities/src/addSelect/addSelectData-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~355 LoC) packages/react/src/components/DatePicker/next/components/DatePicker-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~329 LoC) packages/react/previewer/codePreviewer.tsx— no import path from any entry point (190 application, 51 tooling, 1025 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 (~298 LoC) packages/react/src/components/MenuButton/MenuButton-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~295 LoC) packages/utilities/src/carousel/carousel-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~289 LoC) packages/upgrade/transforms/__testfixtures__/ibm-products-update-tearsheet.output.tsx— no import path from any entry point (190 application, 51 tooling, 1025 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 (~285 LoC) packages/react/src/components/RadioTile/RadioTile-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~276 LoC) packages/web-components/src/components/tearsheet/_story-assets/step-tearsheet-preview.ts— no import path from any entry point (190 application, 51 tooling, 1025 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 (~260 LoC) packages/react/src/components/OverflowMenu/next/OverflowMenu-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~250 LoC) packages/react/tasks/build-test-rtl.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~249 LoC) packages/react/src/components/OverflowMenuItem/OverflowMenuItem-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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 (~248 LoC) packages/web-components/src/components/file-uploader/demo-file-uploader.ts— no import path from any entry point (190 application, 51 tooling, 1025 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 (~247 LoC) packages/utilities/src/makeDraggable/makeDraggable-test.js— no import path from any entry point (190 application, 51 tooling, 1025 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
Unused dependency '@commitlint/cli' — 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.
Unused dependency '@commitlint/config-conventional' — 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.
Unused dependency 'unrun' — 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.
Weak hash algorithm config/jest-config-carbon/transform/cssTransform.js:76— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Third-party script without Subresource Integrity packages/react/.storybook/manager-head.html:37— `https://1.www.s81c.com/common/carbon-for-ibm-dotcom/tag/v1/latest/footer.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 5 such include(s) across the repository's markup.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×1
Recursive walk over a caller-supplied document has no depth cap packages/react/src/internal/useNoInteractiveChildren.ts:64— `getInteractiveContent` is exported, takes a document from its caller (line 75) and hands it to `findMatchingContent`, which calls itself at line 64 (`findMatchingContent`) with a piece of `node` — and nowhere in `findMatchingContent` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `findMatchingContent` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Orphaned file packages/react/src/components/ComposedModal/ModalFooter.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/upgrade/transforms/icons-react-size-prop.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/themes/src/v10/white.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/themes/src/v10/g90.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/themes/src/v10/g10.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/themes/src/v10/g100.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/react/src/components/Toggle/Toggle.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/web-components/src/components/tree-view/tree-view.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/themes/src/v10/tokens.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/upgrade/src/workspace.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/cli/src/commands/publish.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/react/src/components/RadioButton/RadioButton.stories.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/icon-build-helpers/src/metadata/extensions/output/index.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file config/stylelint-config-carbon/rules/limit-language-features.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/react/src/components/DataTable/stories/DataTable-basic.stories.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/react/src/components/DataTable/TableBatchActions.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/react/src/components/Copy/Copy.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/cli/src/commands/contribute/setup.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/react/src/components/Layout/index.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/react/src/components/UIShell/SwitcherItem.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/react/src/components/CopyButton/CopyButton.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/icon-build-helpers/src/metadata/index.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/upgrade/src/commands/upgrade.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/upgrade/src/cli.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Deprecated: @ungap/structured-clone REDACTED:8454— @ungap/structured-clone 1.3.0 is resolved in REDACTED and is marked deprecated by its publisher: "Potential CWE-502 - Update to 1.3.1 or higher". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-android-arm64 REDACTED:9109— @yuku-codegen/binding-android-arm64 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-darwin-arm64 REDACTED:9116— @yuku-codegen/binding-darwin-arm64 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-darwin-x64 REDACTED:9123— @yuku-codegen/binding-darwin-x64 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-freebsd-x64 REDACTED:9130— @yuku-codegen/binding-freebsd-x64 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-linux-arm-gnu REDACTED:9137— @yuku-codegen/binding-linux-arm-gnu 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-linux-arm-musl REDACTED:9144— @yuku-codegen/binding-linux-arm-musl 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-linux-arm64-gnu REDACTED:9151— @yuku-codegen/binding-linux-arm64-gnu 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-linux-arm64-musl REDACTED:9158— @yuku-codegen/binding-linux-arm64-musl 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-linux-x64-gnu REDACTED:9165— @yuku-codegen/binding-linux-x64-gnu 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-linux-x64-musl REDACTED:9172— @yuku-codegen/binding-linux-x64-musl 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-win32-arm64 REDACTED:9179— @yuku-codegen/binding-win32-arm64 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-win32-x64 REDACTED:9186— @yuku-codegen/binding-win32-x64 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-android-arm64 REDACTED:9193— @yuku-parser/binding-android-arm64 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-darwin-arm64 REDACTED:9200— @yuku-parser/binding-darwin-arm64 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-darwin-x64 REDACTED:9207— @yuku-parser/binding-darwin-x64 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-freebsd-x64 REDACTED:9214— @yuku-parser/binding-freebsd-x64 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-linux-arm-gnu REDACTED:9221— @yuku-parser/binding-linux-arm-gnu 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-linux-arm-musl REDACTED:9228— @yuku-parser/binding-linux-arm-musl 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-linux-arm64-gnu REDACTED:9235— @yuku-parser/binding-linux-arm64-gnu 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-linux-arm64-musl REDACTED:9242— @yuku-parser/binding-linux-arm64-musl 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-linux-x64-gnu REDACTED:9249— @yuku-parser/binding-linux-x64-gnu 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-linux-x64-musl REDACTED:9256— @yuku-parser/binding-linux-x64-musl 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-win32-arm64 REDACTED:9263— @yuku-parser/binding-win32-arm64 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-win32-x64 REDACTED:9270— @yuku-parser/binding-win32-x64 0.9.5 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Duplicated predicate packages/react/src/components/ComposedModal/ComposedModal.tsx:105— `!!contentRef.current && contentRef?.current?.scrollHeight > contentRef?.current?.clientHeight` appears character-identically in 2 files — packages/react/src/components/ComposedModal/ComposedModal.tsx, packages/react/src/components/Dialog/Dialog.tsx. 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 packages/react/src/components/ComposedModal/ModalFooter.tsx:81— `!Array.isArray(props.secondaryButtons) || props.secondaryButtons.length !== 2` appears character-identically in 3 files — packages/react/src/components/ComposedModal/ModalFooter.tsx, packages/react/src/components/Dialog/Dialog.tsx, packages/react/src/components/Modal/Modal.tsx. 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 packages/web-components/src/components/file-uploader/file-uploader-button.ts:83— `!accept || !/^(change|drop)$/.test(event.type)` appears character-identically in 2 files — packages/web-components/src/components/file-uploader/file-uploader-button.ts, packages/web-components/src/components/file-uploader/file-uploader-drop-container.ts. 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 packages/react/src/components/PageHeader/PageHeaderContentPageActions.tsx:110— `!containerRef.current || !Array.isArray(actions)` appears character-identically in 2 files — packages/react/src/components/PageHeader/PageHeaderContentPageActions.tsx, packages/react/src/components/PageHeaderDeprecated/PageHeader.tsx. 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 packages/react/src/components/PageHeader/overflowHandler.ts:35— `!el.offsetParent && getComputedStyle(el).display === 'none'` appears character-identically in 2 files — packages/react/src/components/PageHeader/overflowHandler.ts, packages/web-components/src/components/page-header/_story-assets/overflowHandler.ts. 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 packages/web-components/src/components/modal/modal.ts:127— `!event.shiftKey && document.activeElement === _lastElement` appears character-identically in 2 files — packages/web-components/src/components/modal/modal.ts, packages/web-components/src/components/side-panel/side-panel.ts. 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 packages/react/.storybook-v12/main.ts:45— `!isFeatureFlagStory(story) || story.startsWith('./')` appears character-identically in 2 files — packages/react/.storybook-v12/main.ts, packages/web-components/.storybook-v12/main.ts. 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 packages/react/src/components/ProgressBar/ProgressBar.tsx:84— `!isFinished && !isError && (value === null || value === undefined)` appears character-identically in 2 files — packages/react/src/components/ProgressBar/ProgressBar.tsx, packages/web-components/src/components/progress-bar/progress-bar.ts. 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 packages/react/src/components/TextInput/PasswordInput.tsx:423— `!isFluid && !inline && (normalizedProps.validation || helper)` appears character-identically in 2 files — packages/react/src/components/TextInput/PasswordInput.tsx, packages/react/src/components/TextInput/TextInput.tsx. 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 packages/react/src/components/AddSelect/AddSelectSelectionSummaryItem.tsx:177— `!item?.itemDetails || !Array.isArray(item.itemDetails)` appears character-identically in 2 files — packages/react/src/components/AddSelect/AddSelectSelectionSummaryItem.tsx, packages/web-components/src/components/add-select/add-select-selection-summary-item.ts. 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 packages/react/src/components/AddSelect/AddSelectItemPanel.tsx:101— `!itemDetails || !Array.isArray(itemDetails) || itemDetails.length === 0` appears character-identically in 2 files — packages/react/src/components/AddSelect/AddSelectItemPanel.tsx, packages/web-components/src/components/add-select/add-select-item-panel.ts. 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 packages/react/src/components/Checkbox/Checkbox.tsx:151— `!normalizedProps.invalid && !normalizedProps.warn` appears character-identically in 5 files — packages/react/src/components/Checkbox/Checkbox.tsx, packages/react/src/components/CheckboxGroup/CheckboxGroup.tsx, packages/web-components/src/components/checkbox/checkbox-group.ts, packages/web-components/src/components/checkbox/checkbox.ts. 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 packages/react/src/components/RadioButtonGroup/RadioButtonGroup.tsx:219— `!readOnly && !disabled && !invalid && warn` appears character-identically in 2 files — packages/react/src/components/RadioButtonGroup/RadioButtonGroup.tsx, packages/web-components/src/components/radio-button/radio-button-group.ts. 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 packages/react/src/internal/useNormalizedInputProps.tsx:72— `!readOnly && !invalid && !disabled && warn` appears character-identically in 2 files — packages/react/src/internal/useNormalizedInputProps.tsx, packages/web-components/src/components/dropdown/dropdown.ts. 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 packages/web-components/src/components/fluid-time-picker/fluid-time-picker.ts:53— `!readOnly && !invalid && !disabled && warning` appears character-identically in 2 files — packages/web-components/src/components/fluid-time-picker/fluid-time-picker.ts, packages/web-components/src/components/time-picker/time-picker.ts. 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 packages/web-components/src/components/checkbox/checkbox-group.ts:174— `!readonly && !invalid && !disabled && warn` appears character-identically in 3 files — packages/web-components/src/components/checkbox/checkbox-group.ts, packages/web-components/src/components/checkbox/checkbox.ts, packages/web-components/src/components/select/select.ts. 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 packages/react/src/components/PageHeader/utils.ts:95— `!target || !style || style.position === 'fixed'` appears character-identically in 2 files — packages/react/src/components/PageHeader/utils.ts, packages/web-components/src/components/page-header/utils.ts. 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 packages/web-components/src/components/dropdown/dropdown-item.ts:158— `!textContainer || this._hasEllipsisApplied === true` appears character-identically in 3 files — packages/web-components/src/components/dropdown/dropdown-item.ts, packages/web-components/src/components/page-header-deprecated/page-header-content.ts, packages/web-components/src/components/page-header/page-header-content.ts. 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 packages/web-components/src/components/action-set/action-set.ts:380— `!this.actions || this.actions.length === 0` appears character-identically in 2 files — packages/web-components/src/components/action-set/action-set.ts, packages/web-components/src/components/tearsheet/tearsheet-footer.ts. 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 packages/react/code-connect/Toggletip/Toggletip.figma.ts:42— `(child.name === 'Link' || child.name === 'Button') && child.hasCodeConnect()` appears character-identically in 2 files — packages/react/code-connect/Toggletip/Toggletip.figma.ts, packages/web-components/code-connect/toggletip/toggletip.figma.ts. 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 packages/web-components/src/components/date-picker/date-picker-input.ts:45— `(elem as HTMLElement).matches( (this.constructor as typeof CDSDatePickerInput).aiLabelItem ) || (elem as HTMLElement).matches( (this.constru…` appears character-identically in 2 files — packages/web-components/src/components/date-picker/date-picker-input.ts, packages/web-components/src/components/date-picker/next/components/date-picker-input.ts. 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 packages/react/src/components/ComposedModal/ModalFooter.tsx:44— `Array.isArray(secondaryButtons) && secondaryButtons.length <= 2` appears character-identically in 3 files — packages/react/src/components/ComposedModal/ModalFooter.tsx, packages/react/src/components/Dialog/Dialog.tsx, packages/react/src/components/Modal/Modal.tsx. 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 packages/react/src/components/ComposedModal/ModalFooter.tsx:236— `Array.isArray(secondaryButtons) && secondaryButtons.length === 2` appears character-identically in 3 files — packages/react/src/components/ComposedModal/ModalFooter.tsx, packages/react/src/components/Dialog/Dialog.tsx, packages/react/src/components/Modal/Modal.tsx. 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 packages/web-components/src/components/file-uploader/file-uploader-button.ts:97— `acceptedTypes.has(mimeType) || (fileExtension && acceptedTypes.has(fileExtension))` appears character-identically in 2 files — packages/web-components/src/components/file-uploader/file-uploader-button.ts, packages/web-components/src/components/file-uploader/file-uploader-drop-container.ts. 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 packages/utilities/src/overflowHandler/overflowHandler.ts:123— `accumulated + size <= available && (!maxVisibleItems || visibleItems.length < maxVisibleItems)` appears character-identically in 2 files — packages/utilities/src/overflowHandler/overflowHandler.ts, packages/web-components/src/components/page-header/_story-assets/overflowHandler.ts. 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.
P2 · Observability· Console output used as the logging channel · ×20
Console output used as the logging channel packages/upgrade/transforms/icons-react-size-prop.js:321— `packages/upgrade/transforms/icons-react-size-prop.js` reports through `console.*` at line 321 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/upgrade/transforms/wc-report-non-barrel-imports.js:141— `packages/upgrade/transforms/wc-report-non-barrel-imports.js` reports through `console.*` at line 141 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/upgrade/transforms/__testfixtures__/featureflag-deprecate-flags-prop.input.js:48— `packages/upgrade/transforms/__testfixtures__/featureflag-deprecate-flags-prop.input.js` reports through `console.*` at line 48 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/upgrade/transforms/__testfixtures__/featureflag-deprecate-flags-prop.input.js:52— `packages/upgrade/transforms/__testfixtures__/featureflag-deprecate-flags-prop.input.js` reports through `console.*` at line 52 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/upgrade/transforms/__testfixtures__/featureflag-deprecate-flags-prop.output.js:48— `packages/upgrade/transforms/__testfixtures__/featureflag-deprecate-flags-prop.output.js` reports through `console.*` at line 48 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/upgrade/transforms/__testfixtures__/featureflag-deprecate-flags-prop.output.js:52— `packages/upgrade/transforms/__testfixtures__/featureflag-deprecate-flags-prop.output.js` reports through `console.*` at line 52 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js:49— `packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js` reports through `console.*` at line 49 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js:55— `packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js` reports through `console.*` at line 55 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js:71— `packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js` reports through `console.*` at line 71 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js:77— `packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js` reports through `console.*` at line 77 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js:132— `packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js` reports through `console.*` at line 132 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js:141— `packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.input.js` reports through `console.*` at line 141 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js:47— `packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js` reports through `console.*` at line 47 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js:53— `packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js` reports through `console.*` at line 53 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js:67— `packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js` reports through `console.*` at line 67 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js:73— `packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js` reports through `console.*` at line 73 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js:120— `packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js` reports through `console.*` at line 120 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js:128— `packages/upgrade/transforms/__testfixtures__/ibm-products-update-page-header-composable.output.js` reports through `console.*` at line 128 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/upgrade/src/logger.js:65— `packages/upgrade/src/logger.js` reports through `console.*` at line 65 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/upgrade/src/logger.js:72— `packages/upgrade/src/logger.js` reports through `console.*` at line 72 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Mock-dominated test: should cancel a pending rAF when disconnect() is called packages/utilities/src/overflowHandler/overflowHandler-test.js:551— This test sets up 3 test doubles (for example `jest.spyOn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should return correct callback data when transitions or animations are disabled packages/utilities/src/carousel/carousel-test.js:141— This test sets up 8 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should call handlers in order and stop after one calls `preventDefault` packages/react/src/tools/__tests__/events-test.js:72— This test sets up 4 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 6 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: schedules a new animation frame after cleanup cancels a pending frame packages/react/src/internal/__tests__/useResizeObserver-test.js:164— This test sets up 4 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: does not run focus-wrap when a floating menu is focused on packages/react/src/internal/__tests__/wrapFocus-test.js:113— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: respects prefix overrides when checking floating menus packages/react/src/internal/__tests__/wrapFocus-test.js:126— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should call onTreeSelect, onNodeSelect, and rest.onClick when not disabled packages/react/src/components/TreeView/__tests__/TreeNode-test.js:178— This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should cancel a pending resize animation frame on unmount packages/react/src/components/Tabs/__tests__/Tabs-test.js:794— This test sets up 5 test doubles (for example `jest
.spyOn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should warn once for each deprecated surface packages/react/src/components/PageHeaderDeprecated/PageHeader-test.js:65— This test sets up 4 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 8 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should return array of files marked as invalid if they dont match accepted types packages/react/src/components/FileUploader/__tests__/FileUploaderDropContainer-test.js:479— This test sets up 3 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should ignore directory items dropped via dataTransfer.items packages/react/src/components/FileUploader/__tests__/FileUploaderDropContainer-test.js:725— This test sets up 5 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should provide access to the feature flags for a scope through deprecated flags prop packages/react/src/components/FeatureFlags/__tests__/FeatureFlags-test.js:35— This test sets up 3 test doubles (for example `jest.spyOn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should support `DialogFooter` secondary buttons array and primary submit packages/react/src/components/Dialog/Dialog-test.js:241— This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should call close handlers for secondary buttons without `onClick` packages/react/src/components/ComposedModal/ModalFooter-test.js:167— This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: skips typed-event inference when Bob already commented on opened actions/issues/src/plugins/bob-bug-triage-test.js:156— This test sets up 4 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Outdated (npm): @carbon/cli-reporter packages/cli-reporter/package.json:2— @carbon/cli-reporter is pinned at 0.0.0-use.local; registry.npmjs.org publishes 10.9.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.
Outdated (npm): @carbon/colors packages/colors/examples/colors-explorer/package.json:9— @carbon/colors is pinned at 0.0.0-use.local; registry.npmjs.org publishes 11.61.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.
Outdated (npm): @carbon/grid packages/elements/package.json:47— @carbon/grid is pinned at 0.0.0-use.local; registry.npmjs.org publishes 11.65.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.
Outdated (npm): @carbon/icons-react packages/icons-react/package.json:2— @carbon/icons-react is pinned at 0.0.0-use.local; registry.npmjs.org publishes 11.91.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.
Outdated (npm): @carbon/layout packages/elements/package.json:49— @carbon/layout is pinned at 0.0.0-use.local; registry.npmjs.org publishes 11.62.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.
Outdated (npm): @carbon/motion packages/elements/package.json:50— @carbon/motion is pinned at 0.0.0-use.local; registry.npmjs.org publishes 11.55.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.
Outdated (npm): @carbon/themes packages/colors/examples/colors-explorer/package.json:10— @carbon/themes is pinned at 0.0.0-use.local; registry.npmjs.org publishes 11.84.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.
Outdated (npm): @carbon/type packages/elements/package.json:52— @carbon/type is pinned at 0.0.0-use.local; registry.npmjs.org publishes 11.70.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.
Outdated (npm): @octokit/plugin-retry packages/cli/package.json:34— @octokit/plugin-retry is pinned at 3.0.9; registry.npmjs.org publishes 8.1.1 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.
Outdated (npm): @octokit/plugin-throttling packages/cli/package.json:35— @octokit/plugin-throttling is pinned at 4.3.0; registry.npmjs.org publishes 11.0.5 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.
Outdated (npm): @typescript-eslint/eslint-plugin config/eslint-config-carbon/package.json:37— @typescript-eslint/eslint-plugin is pinned at 5.59.6; registry.npmjs.org publishes 8.72.1 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.
Outdated (npm): @typescript-eslint/parser config/eslint-config-carbon/package.json:38— @typescript-eslint/parser is pinned at 5.60.1; registry.npmjs.org publishes 8.72.1 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.
Outdated (npm): browserslist-config-carbon config/babel-preset-carbon/package.json:29— browserslist-config-carbon is pinned at 0.0.0-use.local; registry.npmjs.org publishes 11.2.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.
Outdated (npm): stylelint-config-standard config/stylelint-config-carbon/package.json:34— stylelint-config-standard is pinned at 36.0.1; registry.npmjs.org publishes 40.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.
Classify ADR enforcement: 1. Record project decisions docs/decisions/0001-record-project-decisions.md— This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
Classify ADR enforcement: 2. Replace recursive prop passing with React Context in TreeView components docs/decisions/0002-replace-recursive-prop-passing-with-context.md— This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
Classify ADR enforcement: 3. Use `preview` moniker instead of `experimental` docs/decisions/0003-use-preview-moniker.md— This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
Classify ADR enforcement: 4. Adopt explicit package entrypoints for the utilities packages docs/decisions/0004-adopt-explicit-package-entrypoints-for-utilities.md— This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
Classify ADR enforcement: 5. Use realistic example content in stories docs/decisions/0005-use-realistic-example-content-in-stories.md— This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
Classify ADR enforcement: 6. Storybook Organization Standards docs/decisions/0006-storybook-organization.md— This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
Classify ADR enforcement: 7. Provide pure class exports and opt-in registration for `@carbon/web-components` docs/decisions/0007-provide-pure-class-exports-for-web-components.md— This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
Classify ADR enforcement: 8. Choosing an isolation strategy for breaking `@carbon/web-components` changes docs/decisions/0008-isolate-breaking-web-component-changes.md— This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
Classify ADR enforcement: 7. Migrate components from carbon-for-ibm-products to Carbon core docs/decisions/0009-ibm-products-to-core-migration.md— This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
Classify ADR enforcement: 10. Represent viewport-relative layout tokens as DTCG number tokens docs/decisions/0010-represent-viewport-relative-tokens-as-numbers.md— This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 8 significant file(s) lose their only recent owner: packages/react/src/components/Card/Card.stories.js, packages/web-components/src/components/card/card.stories.ts, packages/web-components/src/components/card/card.ts, packages/react/src/components/Card/Card.tsx, packages/react/src/components/Card/CardActions.tsx, packages/web-components/src/components/card/card-actions.ts, packages/react/src/components/Card/CardTitle.tsx, packages/react/src/components/Card/Card.types.ts. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 7 significant file(s) lose their only recent owner: actions/issues/src/plugins/bob-bug-triage.js, REDACTED, tasks/prepare-v12-storybook.mjs, packages/upgrade/transforms/enable-v12-release.js, packages/icon-build-helpers/src/metadata/extensions/output/optimizer.js, actions/validate-pr-template/index.js, actions/issues/src/run.js. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 7 significant file(s) lose their only recent owner: packages/react/src/components/Switch/IconSwitch.tsx, packages/web-components/src/components/date-picker/range-plugin.ts, packages/react/src/components/ListBox/ListBoxSelection.tsx, packages/react/src/components/ListBox/test-helpers.ts, packages/web-components/src/components/date-picker/fix-events-plugin.ts, packages/web-components/src/components/ui-shell/side-nav-link.ts, packages/react/src/components/Slider/SliderHandles.tsx. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 6 significant file(s) lose their only recent owner: packages/react/src/components/Resizer/Resizer.stories.js, packages/web-components/src/components/tearsheet/tearsheet.stories.ts, packages/react/src/components/Tearsheet/Tearsheet.tsx, packages/react/src/components/Tearsheet/TearsheetBody.tsx, packages/react/src/components/BigNumber/BigNumber.stories.js, packages/react/src/components/ActionSet/ActionSet.stories.internal.js. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #5 — If anonymized user #5 becomes unavailable, 6 significant file(s) lose their only recent owner: packages/web-components/src/components/form-group/form-group.stories.ts, packages/web-components/src/components/list/ordered-list.stories.ts, packages/react/src/components/StructuredList/StructuredList.featureflag.stories.js, packages/web-components/src/components/notification/toast-notification.stories.ts, packages/web-components/src/components/notification/inline-notification.stories.ts, packages/react/src/components/FormLabel/FormLabel.stories.js. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #6 — If anonymized user #6 becomes unavailable, 3 significant file(s) lose their only recent owner: packages/web-components/src/components/floating-menu/floating-menu.ts, packages/web-components/src/components/dialog/dialog.ts, packages/utilities/src/date-picker/primitives/types.ts. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #7 — If anonymized user #7 becomes unavailable, 3 significant file(s) lose their only recent owner: packages/utilities/src/makeDraggable/makeDraggable.ts, packages/web-components/src/components/user-avatar/user-avatar.stories.ts, packages/web-components/src/components/user-avatar/user-avatar.ts. Pair on, review, or document these before any departure.
README/code drift docs/postmortems/README.md:15— docs/postmortems/README.md links to `./00-template.md`, but `docs/postmortems/00-template.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/carbon-components/README.md:46— packages/carbon-components/README.md links to `./docs/sass.md#configuration`, but `packages/carbon-components/docs/sass.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/icon-build-helpers/src/metadata/README.md:28— packages/icon-build-helpers/src/metadata/README.md links to `./registry.js`, but `packages/icon-build-helpers/src/metadata/registry.js` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/react/src/internal/README.md:3— packages/react/src/internal/README.md links to `./FeatureFlags.js`, but `packages/react/src/internal/FeatureFlags.js` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Fat interface: DataTableRenderProps (16 required operations) packages/react/src/components/DataTable/DataTable.tsx:121— `DataTableRenderProps` declares 16 required operations: `getHeaderProps`, `getExpandHeaderProps`, `getRowProps`, `getExpandedRowProps`, `getSelectionProps`, `getToolbarProps`, `getBatchActionProps`, `getTableProps`, `getTableContainerProps`, `getCellProps`, `onInputChange`, `sortBy`, `selectAll`, `selectRow`, `expandRow`, `expandAll`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 8 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (52 single-owned of 896 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 896 of the 2118 production source files in this repository met that bar). They are anonymized user #8 (2 file(s)), anonymized user #9 (2 file(s)), anonymized user #10 (1 file(s)), anonymized user #11 (1 file(s)), anonymized user #12 (1 file(s)), anonymized user #13 (1 file(s)) (+2 more) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: packages/web-components/src/utilities/overflow-handler/overflow-handler.stories.ts, packages/react/src/components/OverflowHandler/OverflowHandler.stories.js, packages/web-components/src/globals/mixins/validity.ts, packages/web-components/src/globals/mixins/form.ts, packages/react/src/components/NotificationsPanel/NotificationsPanel.stories.js, packages/cli/src/changelog.js, packages/web-components/src/components/icon/icon.stories.ts, packages/web-components/src/components/date-picker/month-select-plugin.ts (+2 more).
ADR not followed: 3. Use `preview` moniker instead of `experimental` docs/decisions/0003-use-preview-moniker.md:42— docs/decisions/0003-use-preview-moniker.md:42 rules out `preview`, but production code uses it: packages/web-components/src/components/date-picker/next/components/date-picker.ts:1054, packages/web-components/src/components/date-picker/next/components/date-picker.ts:1063, packages/web-components/src/components/date-picker/next/components/date-picker.ts:1065, packages/web-components/src/components/date-picker/next/components/date-picker.ts:1067, packages/upgrade/transforms/__testfixtures__/enable-v12-release.input.tsx:22 (+3 more). Remove the use, or supersede the record if the decision changed.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 39 project(s) overshoot their size bounds, lowering Project Cohesion to 9.0/10. The most over is `packages/react` (95575 LoC, 1152 module-visible types across 302 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 72 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: packages/react/src/components/ComposedModal/ModalFooter.tsx, packages/upgrade/transforms/icons-react-size-prop.js, REDACTED, packages/themes/src/v10/white.ts, packages/themes/src/v10/g90.ts, packages/themes/src/v10/g10.ts, packages/themes/src/v10/g100.ts, packages/react/src/components/Toggle/Toggle.tsx (and 64 more) (74 orphaned of 898 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 898 of the 2118 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
GD1 · Unfinished & placeholder code· Placeholder literal left in code · ×1
Placeholder literal left in code packages/web-components/src/components/side-panel/_story-assets/index.ts:194— A placeholder string ("<cds-slug size="xs" alignment="bottom-ri…") is still in shipped code — typical of generated boilerplate that was never filled in.
Logging is not universal — Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/web-components`.
P3 · Security & performance tooling· Dependabot does not watch npm · ×1
Dependabot does not watch npm REDACTED:2— `REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list.
No security response headers detected netlify.toml:1— None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
X5 · Nullable reference types· Strict null checking is not enabled everywhere the repository type-checks · ×1
Strict null checking is not enabled everywhere the repository type-checks — 15/35 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Null assertions (`!`) reduce the strict null checking score — ~1.5 `!` null assertions per 1k TypeScript source lines — 282 assertion(s) across the 191413 source line(s) of the 1518 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/web-components/src/components/date-picker/date-picker.ts (14), packages/web-components/src/components/code-snippet/code-snippet.ts (12), packages/web-components/src/components/date-picker/date-picker-input.ts (11). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Silent fallback default in catch packages/web-components/src/components/resizer/defs.ts:182— `safeQuerySelectorAll` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Outdated (npm): @babel/core — @babel/core is pinned at 8.0.1; registry.npmjs.org publishes 8.0.10 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.
Outdated (npm): @babel/eslint-parser — @babel/eslint-parser is pinned at 8.0.1; registry.npmjs.org publishes 8.0.7 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.
Outdated (npm): @babel/plugin-transform-react-constant-elements — @babel/plugin-transform-react-constant-elements is pinned at 8.0.1; registry.npmjs.org publishes 8.0.5 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.
Outdated (npm): @babel/plugin-transform-runtime — @babel/plugin-transform-runtime is pinned at 8.0.1; registry.npmjs.org publishes 8.0.6 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.
Outdated (npm): @babel/preset-env — @babel/preset-env is pinned at 8.0.2; registry.npmjs.org publishes 8.0.7 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.
Outdated (npm): @babel/preset-typescript — @babel/preset-typescript is pinned at 8.0.1; registry.npmjs.org publishes 8.0.7 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.
Outdated (npm): @babel/runtime — @babel/runtime is pinned at 8.0.0; registry.npmjs.org publishes 8.0.10 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.
Outdated (npm): @carbon/feature-flags — @carbon/feature-flags is pinned at 0.0.0-use.local; registry.npmjs.org publishes 1.11.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.
Outdated (npm): @carbon/ibm-products — @carbon/ibm-products is pinned at 2.99.0; registry.npmjs.org publishes 2.102.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.
Outdated (npm): @carbon/ibm-products-web-components — @carbon/ibm-products-web-components is pinned at 0.49.0; registry.npmjs.org publishes 0.51.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.
Outdated (npm): @carbon/icon-helpers — @carbon/icon-helpers is pinned at 10.47.0; registry.npmjs.org publishes 10.84.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.
Outdated (npm): @carbon/icons — @carbon/icons is pinned at 11.90.0; registry.npmjs.org publishes 11.91.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.
Outdated (npm): @carbon/react — @carbon/react is pinned at 0.0.0-use.local; registry.npmjs.org publishes 1.119.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.
Outdated (npm): @carbon/styles — @carbon/styles is pinned at 0.0.0-use.local; registry.npmjs.org publishes 1.118.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.
Outdated (npm): @carbon/utilities — @carbon/utilities is pinned at 0.0.0-use.local; registry.npmjs.org publishes 0.28.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.
Outdated (npm): @double-great/stylelint-a11y — @double-great/stylelint-a11y is pinned at 3.4.10; registry.npmjs.org publishes 3.8.1 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.
Outdated (npm): @floating-ui/dom — @floating-ui/dom is pinned at 1.6.13; registry.npmjs.org publishes 1.8.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.
Outdated (npm): @floating-ui/react — @floating-ui/react is pinned at 0.27.4; registry.npmjs.org publishes 0.27.20 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.
Outdated (npm): @ibm/telemetry-js — @ibm/telemetry-js is pinned at 1.11.0; registry.npmjs.org publishes 1.12.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.
Outdated (npm): @internationalized/number — @internationalized/number is pinned at 3.6.1; registry.npmjs.org publishes 3.6.9 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.
Outdated (npm): @npmcli/arborist — @npmcli/arborist is pinned at 9.9.3; registry.npmjs.org publishes 10.0.4 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.
Outdated (npm): @octokit/rest — @octokit/rest is pinned at 22.0.0; registry.npmjs.org publishes 22.0.1 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.
Outdated (npm): @types/node — @types/node is pinned at 25.9.3; registry.npmjs.org publishes 26.6.6 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.
Outdated (npm): axe-core — axe-core is pinned at 4.11.0; registry.npmjs.org publishes 4.14.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.
Outdated (npm): babel-jest — babel-jest is pinned at 30.4.1; registry.npmjs.org publishes 30.5.2 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.
Skipped (documented): should both block submission when required and empty packages/web-components/src/globals/mixins/__tests__/form-associated-test.js:334— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call
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.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 31 file(s) — `packages/react/src/components/BadgeIndicator/index.tsx`, `packages/react/src/components/Breadcrumb/BreadcrumbItem.tsx`, `packages/react/src/components/DataTable/TableCell.tsx`, `packages/react/src/components/DataTable/TableHeader.tsx`, `packages/react/src/components/DataTable/TableRow.tsx`, … (+26 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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.
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.
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.
Run 01a18b1c-2ddd-709f-9cc3-c977ee5c6052 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 149 · Warnings: 1195 · Recommendations: 224 · Info: 60 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 30-10-2026 @ 04:40 UTC.
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.