Public report of plotly/dash, published 16 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 16 November 2026, 21:02 UTC · Survey ID cd_16082c1b097549ad908d0ea0bd4da0b9
plotly/dash
Measured 16 November 2026, 21:00 UTC, at code version 572115c
Test reliability is not measured: The python executor ran against the .py half and did not finish re-running within its tier budget.
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreAt riskUp 1.3 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 medium codebase: 67,570 lines of product code in 14 projects, tests not counted · Estimated rebuild effort: about 0.8 person-years · Weakest lens: Accessibility, 26.5
Findings by how serious they are
319 critical530 serious236 minor
12 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 21:00 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
78of 78 dimensions measured by tools.
971of 1085 findings point to an exact file and line, so you can open each one in the code. The other 114 concern the repository as a whole, such as missing documentation.
78dimensions across 7 lenses, read from 67,570 lines of product code in 14 projects.
plotly/dash is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back because it has buttons or links with no name and controls that only work with a mouse. It scores 41.1 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 26.5, is the weakest lens and counts most in the score. The best first step is labelling the form fields and buttons, worth about 7.5 points. Making the controls keyboard-usable comes next, worth about 7.3 points. Raising Accessibility to 70 would lift the score to about 53.3.
114 pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Thirty-nine buttons or links have no name a screen reader can say, and twenty-nine known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version, naming the buttons and links, and updating the vulnerable packages would close these risks. Setting a waiting period for automatic updates would fix the three automatic dependency updates that take new releases at once, and the 18 pipeline steps that install packages without pinning their versions need the packages they install pinned to exact versions. The five loops of files that import each other need breaking.
The product code is 67,570 lines, about €110,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 Accessibility rose from 26.5 to 70, the lowest score rated Strong, the score would rise from 41.1 to about 53.3.
Code composition: what the lines of code are
Product code 51%Tests 49%
New since the last survey: 136 findings
These 136 critical or serious findings weren't in the previous survey, on 4 November 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Code Duplication · Edited copy of a member (89 corresponding lines) dash/testing/application_runners.py
Code Duplication · Edited copy of a member (104 corresponding lines) dash/background_callback/managers/celery_manager.py
Code Duplication · Edited copy of a member (35 corresponding lines) REDACTED
Code Duplication · Edited copy of a member (28 corresponding lines) dash/dependencies.py
Code Duplication · Edited copy of a member (31 corresponding lines) dash/backends/_flask.py
Code Duplication · Edited copy of a member (33 corresponding lines) dash/backends/_flask.py
Code Duplication · Edited copy of a member (23 corresponding lines) dash/backends/_flask.py
Code Duplication · Edited copy of a member (39 corresponding lines) dash/backends/ws.py
Code Duplication · Edited copy of a member (19 corresponding lines) dash/backends/ws.py
Code Duplication · Edited copy of a member (16 corresponding lines) dash/testing/wait.py
Code Duplication · Edited copy of a member (16 corresponding lines) dash/background_callback/managers/celery_manager.py
Code Duplication · Edited copy of a member (14 corresponding lines) dash/backends/ws.py
Code Duplication · Edited copy of a member (16 corresponding lines) dash/backends/_flask.py
Code Duplication · Edited copy of a member (10 corresponding lines) REDACTED
Code Duplication · Edited copy of a member (11 corresponding lines) REDACTED
Code Duplication · Edited copy of a member (9 corresponding lines) dash/testing/wait.py
Code Duplication · Edited copy of a member (6 corresponding lines) dash/mcp/primitives/tools/input_schemas/input_descriptions/description_pattern_matching.py
Code Duplication · Edited copy of a member (3 corresponding lines) dash/_shared_storage/_polling.py
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test component comments Component has docstring
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test component comments Component with `@` in docstring
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test mixed generation Mixed component prop-type & typescript
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test mixed generation Standard js component is parsed
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes Array of union of shapes and string
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes Component prop has comment
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes Default props
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes Enum options
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes Nested props to any
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes Obj properties
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes Required props
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes Tuple elements
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes Union of number and string
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes Union of primitives and arrays of primitives
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes Union of shape and string
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes objectOf node
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes union and literal values
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes union of boolean and literal values
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes union of duplicated types
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names FCComponent array type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names FCComponent boolean type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names FCComponent children React.Node
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names FCComponent dash_component DashComponent
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names FCComponent element JSX.Element
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names FCComponent enum type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names FCComponent number type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names FCComponent object of components
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names FCComponent object of string
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names FCComponent object type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names FCComponent setProps func
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names FCComponent string type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names FCComponent tuple tuple
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names FCComponent union type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names MemoTypeScriptComponent array type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names MemoTypeScriptComponent boolean type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names MemoTypeScriptComponent children React.Node
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names MemoTypeScriptComponent dash_component DashComponent
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names MemoTypeScriptComponent element JSX.Element
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names MemoTypeScriptComponent enum type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names MemoTypeScriptComponent number type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names MemoTypeScriptComponent object of components
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names MemoTypeScriptComponent object of string
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names MemoTypeScriptComponent object type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names MemoTypeScriptComponent setProps func
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names MemoTypeScriptComponent string type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names MemoTypeScriptComponent tuple tuple
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names MemoTypeScriptComponent union type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptClassComponent array type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptClassComponent boolean type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptClassComponent children React.Node
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptClassComponent dash_component DashComponent
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptClassComponent element JSX.Element
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptClassComponent enum type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptClassComponent number type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptClassComponent object of components
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptClassComponent object of string
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptClassComponent object type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptClassComponent setProps func
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptClassComponent string type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptClassComponent tuple tuple
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptClassComponent union type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptComponent array type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptComponent boolean type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptComponent children React.Node
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptComponent dash_component DashComponent
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptComponent element JSX.Element
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptComponent enum type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptComponent number type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptComponent object of components
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptComponent object of string
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptComponent object type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptComponent setProps func
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptComponent string type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptComponent tuple tuple
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names TypeScriptComponent union type
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test special cases Component with picked boolean prop
Test Reliability · Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test special cases Empty Component
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 1308 findings
These 1308 critical or serious findings were in the previous survey, on 4 November 2026, and are gone from this one. The first 100 are listed here.
Code Duplication · Duplicated block with local edits (6 matched lines × 2 locations) dash/dash-renderer/src/actions/paths.js
Test Coverage · No test reaches this file dash/dash-renderer/src/react-shim.js
Test Coverage · No test reaches this file dash/dash-renderer/src/store.ts
Test Coverage · No test reaches this file @plotly/dash-jupyterlab/lib/index.js
Test Coverage · No test reaches this file components/dash-core-components/src/fragments/Loading/spinners/DefaultSpinner.tsx
Test Coverage · No test reaches this file dash/dash-renderer/src/StoreObserver.ts
Test Coverage · No test reaches this file dash/dash-renderer/src/components/error/werkzeugcss.js
Test Coverage · No test reaches this file components/dash-core-components/src/fragments/Markdown.tsx
Test Coverage · No test reaches this file components/dash-table/demo/App.tsx
Test Coverage · No test reaches this file components/dash-core-components/src/fragments/Loading/spinners/DotSpinner.tsx
Test Coverage · No test reaches this file components/dash-core-components/src/components/Slider.tsx
Test Coverage · No test reaches this file components/dash-core-components/src/components/ConfirmDialog.react.js
Test Coverage · No test reaches this file components/dash-html-components/scripts/extract-elements.js
Test Coverage · No test reaches this file dash/dash-renderer/src/reducers/profile.js
Test Coverage · No test reaches this file dash/dash-renderer/src/utils/clientsideFunctions.ts
Rebuild cost: about €110,000 · Estimate
Cost to rebuild
€37,000 to €190,000, for 622 to 1,975 hours of work, about 0.8 person-years for 1 to 2 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 41. 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
Medium: 67,570 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: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Raises the score by about 7.5 points · Medium effort · Forms & labels
2
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Raises the score by about 7.3 points · Medium effort · Keyboard semantics
3
Resolve the 49 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (46), REDACTED (3).
Raises the score by about 6.1 points · Medium effort · Dependency Hygiene
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €110,000 to build again, about 0.8 person-years of work. Its weakest lens is Accessibility, at 26.5 (Weak). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. Of all the actions in this report, it raises the score most for the work it takes: about 7.5 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.1 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 22,848 lines over the last 90 days, which is about 92,661 lines a year. At that pace, the extra work comes to an estimated 5 to 30.9 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
272 modules, with 202 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; 232 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.
components.dash-core-components.src.utils uses components.dash-core-components.src.types, so a change to components.dash-core-components.src.types can break components.dash-core-components.src.utils, while a change to components.dash-core-components.src.utils can't break components.dash-core-components.src.types.
Position
Below the diagonal: components.dash-core-components.src.utils uses a module listed above it, which is the healthy direction.
components.dash-table.src.core.syntax-tree.lexer uses components.dash-table.src.core.syntax-tree.lexicon, so a change to components.dash-table.src.core.syntax-tree.lexicon can break components.dash-table.src.core.syntax-tree.lexer, while a change to components.dash-table.src.core.syntax-tree.lexer can't break components.dash-table.src.core.syntax-tree.lexicon.
Position
Below the diagonal: components.dash-table.src.core.syntax-tree.lexer uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in components.dash-table.src.core.syntax-tree.syntaxer uses a type in components.dash-table.src.core.syntax-tree.lexicon.
components.dash-table.src.core.syntax-tree.syntaxer uses components.dash-table.src.core.syntax-tree.lexicon, so a change to components.dash-table.src.core.syntax-tree.lexicon can break components.dash-table.src.core.syntax-tree.syntaxer, while a change to components.dash-table.src.core.syntax-tree.syntaxer can't break components.dash-table.src.core.syntax-tree.lexicon.
Position
Below the diagonal: components.dash-table.src.core.syntax-tree.syntaxer uses a module listed above it, which is the healthy direction.
dash uses dash._shared_storage.base, so a change to dash._shared_storage.base can break dash, while a change to dash can't break dash._shared_storage.base.
Position
Below the diagonal: dash uses a module listed above it, which is the healthy direction.
dash uses dash.background_callback.managers, so a change to dash.background_callback.managers can break dash, while a change to dash can't break dash.background_callback.managers.
Position
Below the diagonal: dash uses a module listed above it, which is the healthy direction.
dash._shared_storage._polling uses dash._shared_storage._engine, so a change to dash._shared_storage._engine can break dash._shared_storage._polling, while a change to dash._shared_storage._polling can't break dash._shared_storage._engine.
Position
Below the diagonal: dash._shared_storage._polling uses a module listed above it, which is the healthy direction.
dash._shared_storage._polling uses dash._shared_storage.base, so a change to dash._shared_storage.base can break dash._shared_storage._polling, while a change to dash._shared_storage._polling can't break dash._shared_storage.base.
Position
Below the diagonal: dash._shared_storage._polling uses a module listed above it, which is the healthy direction.
dash.dash uses dash._shared_storage.base, so a change to dash._shared_storage.base can break dash.dash, while a change to dash.dash can't break dash._shared_storage.base.
Position
Below the diagonal: dash.dash uses a module listed above it, which is the healthy direction.
dash.dash-renderer.src.observers uses components.dash-core-components.src.components.Store_react, so a change to components.dash-core-components.src.components.Store_react can break dash.dash-renderer.src.observers, while a change to dash.dash-renderer.src.observers can't break components.dash-core-components.src.components.Store_react.
Position
Below the diagonal: dash.dash-renderer.src.observers uses a module listed above it, which is the healthy direction.
dash.dash-renderer.src.utils uses dash.dash-renderer.src.reducers.callbacks, so a change to dash.dash-renderer.src.reducers.callbacks can break dash.dash-renderer.src.utils, while a change to dash.dash-renderer.src.utils can't break dash.dash-renderer.src.reducers.callbacks.
Position
Below the diagonal: dash.dash-renderer.src.utils uses a module listed above it, which is the healthy direction.
dash.mcp.primitives.resources.base uses dash.mcp.types.protocol, so a change to dash.mcp.types.protocol can break dash.mcp.primitives.resources.base, while a change to dash.mcp.primitives.resources.base can't break dash.mcp.types.protocol.
Position
Below the diagonal: dash.mcp.primitives.resources.base uses a module listed above it, which is the healthy direction.
dash.mcp.primitives.tools.callback_adapter uses dash.mcp.types.protocol, so a change to dash.mcp.types.protocol can break dash.mcp.primitives.tools.callback_adapter, while a change to dash.mcp.primitives.tools.callback_adapter can't break dash.mcp.types.protocol.
Position
Below the diagonal: dash.mcp.primitives.tools.callback_adapter uses a module listed above it, which is the healthy direction.
dash.mcp.primitives.tools.callback_adapter uses dash.types, so a change to dash.types can break dash.mcp.primitives.tools.callback_adapter, while a change to dash.mcp.primitives.tools.callback_adapter can't break dash.types.
Position
Below the diagonal: dash.mcp.primitives.tools.callback_adapter uses a module listed above it, which is the healthy direction.
dash.mcp.primitives.tools.input_schemas.base uses dash.mcp.types.callback_types, so a change to dash.mcp.types.callback_types can break dash.mcp.primitives.tools.input_schemas.base, while a change to dash.mcp.primitives.tools.input_schemas.base can't break dash.mcp.types.callback_types.
Position
Below the diagonal: dash.mcp.primitives.tools.input_schemas.base uses a module listed above it, which is the healthy direction.
dash.mcp.primitives.tools.input_schemas.input_descriptions.base uses dash.mcp.types.callback_types, so a change to dash.mcp.types.callback_types can break dash.mcp.primitives.tools.input_schemas.input_descriptions.base, while a change to dash.mcp.primitives.tools.input_schemas.input_descriptions.base can't break dash.mcp.types.callback_types.
Position
Below the diagonal: dash.mcp.primitives.tools.input_schemas.input_descriptions.base uses a module listed above it, which is the healthy direction.
components.dash-table.src.core.syntax-tree uses components.dash-table.src.core.syntax-tree.lexicon, so a change to components.dash-table.src.core.syntax-tree.lexicon can break components.dash-table.src.core.syntax-tree, while a change to components.dash-table.src.core.syntax-tree can't break components.dash-table.src.core.syntax-tree.lexicon.
Position
Below the diagonal: components.dash-table.src.core.syntax-tree uses a module listed above it, which is the healthy direction.
components.dash-table.src.core.syntax-tree uses components.dash-table.src.core.syntax-tree.lexer, so a change to components.dash-table.src.core.syntax-tree.lexer can break components.dash-table.src.core.syntax-tree, while a change to components.dash-table.src.core.syntax-tree can't break components.dash-table.src.core.syntax-tree.lexer.
Position
Below the diagonal: components.dash-table.src.core.syntax-tree uses a module listed above it, which is the healthy direction.
components.dash-table.src.core.syntax-tree uses components.dash-table.src.core.syntax-tree.syntaxer, so a change to components.dash-table.src.core.syntax-tree.syntaxer can break components.dash-table.src.core.syntax-tree, while a change to components.dash-table.src.core.syntax-tree can't break components.dash-table.src.core.syntax-tree.syntaxer.
Position
Below the diagonal: components.dash-table.src.core.syntax-tree uses a module listed above it, which is the healthy direction.
dash._shared_storage.redis uses dash._shared_storage._engine, so a change to dash._shared_storage._engine can break dash._shared_storage.redis, while a change to dash._shared_storage.redis can't break dash._shared_storage._engine.
Position
Below the diagonal: dash._shared_storage.redis uses a module listed above it, which is the healthy direction.
dash._shared_storage.redis uses dash._shared_storage.base, so a change to dash._shared_storage.base can break dash._shared_storage.redis, while a change to dash._shared_storage.redis can't break dash._shared_storage.base.
Position
Below the diagonal: dash._shared_storage.redis uses a module listed above it, which is the healthy direction.
dash._shared_storage.redis uses dash._shared_storage._polling, so a change to dash._shared_storage._polling can break dash._shared_storage.redis, while a change to dash._shared_storage.redis can't break dash._shared_storage._polling.
Position
Below the diagonal: dash._shared_storage.redis uses a module listed above it, which is the healthy direction.
dash.mcp.primitives.tools uses dash.mcp.types.callback_types, so a change to dash.mcp.types.callback_types can break dash.mcp.primitives.tools, while a change to dash.mcp.primitives.tools can't break dash.mcp.types.callback_types.
Position
Below the diagonal: dash.mcp.primitives.tools uses a module listed above it, which is the healthy direction.
dash.mcp.primitives.tools uses dash.mcp.types.protocol, so a change to dash.mcp.types.protocol can break dash.mcp.primitives.tools, while a change to dash.mcp.primitives.tools can't break dash.mcp.types.protocol.
Position
Below the diagonal: dash.mcp.primitives.tools uses a module listed above it, which is the healthy direction.
dash.mcp.primitives.tools uses dash.types, so a change to dash.types can break dash.mcp.primitives.tools, while a change to dash.mcp.primitives.tools can't break dash.types.
Position
Below the diagonal: dash.mcp.primitives.tools uses a module listed above it, which is the healthy direction.
dash.mcp.primitives.tools uses dash.mcp.primitives.tools.callback_adapter, so a change to dash.mcp.primitives.tools.callback_adapter can break dash.mcp.primitives.tools, while a change to dash.mcp.primitives.tools can't break dash.mcp.primitives.tools.callback_adapter.
Position
Below the diagonal: dash.mcp.primitives.tools uses a module listed above it, which is the healthy direction.
dash.mcp.primitives.tools.descriptions.base uses dash.mcp.primitives.tools.callback_adapter, so a change to dash.mcp.primitives.tools.callback_adapter can break dash.mcp.primitives.tools.descriptions.base, while a change to dash.mcp.primitives.tools.descriptions.base can't break dash.mcp.primitives.tools.callback_adapter.
Position
Below the diagonal: dash.mcp.primitives.tools.descriptions.base uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in components.dash-table.src.dash-table.syntax-tree.SingleColumnSyntaxTree uses a type in components.dash-table.src.core.syntax-tree.
components.dash-table.src.dash-table.syntax-tree.SingleColumnSyntaxTree uses components.dash-table.src.core.syntax-tree, so a change to components.dash-table.src.core.syntax-tree can break components.dash-table.src.dash-table.syntax-tree.SingleColumnSyntaxTree, while a change to components.dash-table.src.dash-table.syntax-tree.SingleColumnSyntaxTree can't break components.dash-table.src.core.syntax-tree.
Position
Below the diagonal: components.dash-table.src.dash-table.syntax-tree.SingleColumnSyntaxTree uses a module listed above it, which is the healthy direction.
components.dash-table.src.dash-table.components.Table.props uses components.dash-table.src.core.sorting, so a change to components.dash-table.src.core.sorting can break components.dash-table.src.dash-table.components.Table.props, while a change to components.dash-table.src.dash-table.components.Table.props can't break components.dash-table.src.core.sorting.
Position
Below the diagonal: components.dash-table.src.dash-table.components.Table.props uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in components.dash-table.src.dash-table.components.Table.props uses a type in components.dash-table.src.dash-table.derived.paginator.
components.dash-table.src.dash-table.components.Table.props uses components.dash-table.src.dash-table.derived.paginator, so a change to components.dash-table.src.dash-table.derived.paginator can break components.dash-table.src.dash-table.components.Table.props, while a change to components.dash-table.src.dash-table.components.Table.props can't break components.dash-table.src.dash-table.derived.paginator.
Position
Below the diagonal: components.dash-table.src.dash-table.components.Table.props uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in components.dash-table.src.dash-table.components.Table.props uses a type in components.dash-table.src.dash-table.syntax-tree.SingleColumnSyntaxTree.
components.dash-table.src.dash-table.components.Table.props uses components.dash-table.src.dash-table.syntax-tree.SingleColumnSyntaxTree, so a change to components.dash-table.src.dash-table.syntax-tree.SingleColumnSyntaxTree can break components.dash-table.src.dash-table.components.Table.props, while a change to components.dash-table.src.dash-table.components.Table.props can't break components.dash-table.src.dash-table.syntax-tree.SingleColumnSyntaxTree.
Position
Below the diagonal: components.dash-table.src.dash-table.components.Table.props uses a module listed above it, which is the healthy direction.
components.dash-table.src.dash-table uses components.dash-table.src.dash-table.components.Table.props, so a change to components.dash-table.src.dash-table.components.Table.props can break components.dash-table.src.dash-table, while a change to components.dash-table.src.dash-table can't break components.dash-table.src.dash-table.components.Table.props.
Position
Below the diagonal: components.dash-table.src.dash-table uses a module listed above it, which is the healthy direction.
components.dash-table.src.dash-table.derived uses components.dash-table.src.dash-table.derived.paginator, so a change to components.dash-table.src.dash-table.derived.paginator can break components.dash-table.src.dash-table.derived, while a change to components.dash-table.src.dash-table.derived can't break components.dash-table.src.dash-table.derived.paginator.
Position
Below the diagonal: components.dash-table.src.dash-table.derived uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in components.dash-table.src.dash-table.derived uses a type in components.dash-table.src.dash-table.components.Table.props.
components.dash-table.src.dash-table.derived uses components.dash-table.src.dash-table.components.Table.props, so a change to components.dash-table.src.dash-table.components.Table.props can break components.dash-table.src.dash-table.derived, while a change to components.dash-table.src.dash-table.derived can't break components.dash-table.src.dash-table.components.Table.props.
Position
Below the diagonal: components.dash-table.src.dash-table.derived uses a module listed above it, which is the healthy direction.
9 pairs of types, where a type in components.dash-table.src.dash-table.derived.cell uses a type in components.dash-table.src.dash-table.components.Table.props.
components.dash-table.src.dash-table.derived.cell uses components.dash-table.src.dash-table.components.Table.props, so a change to components.dash-table.src.dash-table.components.Table.props can break components.dash-table.src.dash-table.derived.cell, while a change to components.dash-table.src.dash-table.derived.cell can't break components.dash-table.src.dash-table.components.Table.props.
Position
Below the diagonal: components.dash-table.src.dash-table.derived.cell uses a module listed above it, which is the healthy direction.
components.dash-table.src.dash-table.derived.header uses components.dash-table.src.core.sorting, so a change to components.dash-table.src.core.sorting can break components.dash-table.src.dash-table.derived.header, while a change to components.dash-table.src.dash-table.derived.header can't break components.dash-table.src.core.sorting.
Position
Below the diagonal: components.dash-table.src.dash-table.derived.header uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in components.dash-table.src.dash-table.derived.header uses a type in components.dash-table.src.dash-table.syntax-tree.SingleColumnSyntaxTree.
components.dash-table.src.dash-table.derived.header uses components.dash-table.src.dash-table.syntax-tree.SingleColumnSyntaxTree, so a change to components.dash-table.src.dash-table.syntax-tree.SingleColumnSyntaxTree can break components.dash-table.src.dash-table.derived.header, while a change to components.dash-table.src.dash-table.derived.header can't break components.dash-table.src.dash-table.syntax-tree.SingleColumnSyntaxTree.
Position
Below the diagonal: components.dash-table.src.dash-table.derived.header uses a module listed above it, which is the healthy direction.
12 pairs of types, where a type in components.dash-table.src.dash-table.derived.header uses a type in components.dash-table.src.dash-table.components.Table.props.
components.dash-table.src.dash-table.derived.header uses components.dash-table.src.dash-table.components.Table.props, so a change to components.dash-table.src.dash-table.components.Table.props can break components.dash-table.src.dash-table.derived.header, while a change to components.dash-table.src.dash-table.derived.header can't break components.dash-table.src.dash-table.components.Table.props.
Position
Below the diagonal: components.dash-table.src.dash-table.derived.header uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in components.dash-table.src.dash-table.utils.Markdown uses a type in components.dash-table.src.dash-table.components.Table.props.
components.dash-table.src.dash-table.utils.Markdown uses components.dash-table.src.dash-table.components.Table.props, so a change to components.dash-table.src.dash-table.components.Table.props can break components.dash-table.src.dash-table.utils.Markdown, while a change to components.dash-table.src.dash-table.utils.Markdown can't break components.dash-table.src.dash-table.components.Table.props.
Position
Below the diagonal: components.dash-table.src.dash-table.utils.Markdown uses a module listed above it, which is the healthy direction.
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
A05:2025 — Injection
158
High / Critical
A03:2025 — Software Supply Chain Failures
61
High / Critical
Roadmap
Top priorities: Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label; Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Resolve the 49 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (46), REDACTED (3).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Code Duplication: Edited copy of a member (39 corresponding lines)
REDACTED
5.8
Mixed
Static Analysis (SAST): High: REDACTED
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 319
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 — 530
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 — 236
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 12
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 78 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 78 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, 971 of 1085 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 or a scanner, 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 — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .ts, .tsx, .py, and our analyzer cannot run the .py test suite(s) — so no coverage was collected for the repository as a whole. The JavaScript/TypeScript half did build and run, and its own line coverage came back at 60.0% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 211 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 390 test source file(s) (.py) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT SCORED: this repository's production source includes .py, and the python executor ran against the .py half and did not finish re-running within its tier budget — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (jest via `npm ci --ignore-scripts` in @plotly/dash-generator-test-component-typescript/ (79 tests); jest via `npm ci --ignore-scripts` in components/dash-core-components/ (85 tests)): measured (77 flaky) suite(s) did re-run, and came back with 77 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted. The half was driven by a runner we ship, so this is not a missing-runner gap.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): 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.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover 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.
D28 Secrets (history) — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The newest 9840 of 10665 commits were scanned for secrets, back to commit 51aa31416e7b; older commits were not. `gitleaks` TIMED OUT after 41.2s against a 41.2s budget, so we killed its process tree. The budget is ours; the work may simply be larger than it allows. The working tree WAS scanned in full, and every row of the scanned ranges is reported. Nothing about the unscanned commits is asserted by the absence of a result; the budget is ours to raise.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `components/dash-core-components/src/fragments/Graph.react.js`, `components/dash-table/src/core/math/arrayZipMap.ts`, `dash/dash-renderer/src/wrapper/DashWrapper.tsx`, `dash/dash-renderer/src/wrapper/wrapping.ts` 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.
AC2 Forms & labels — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 1114 further occurrence(s) are not listed individually; the score already reflects all 1154.
AC6 Visual & motion safety — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentOutOfRangeException: startIndex cannot be larger than length of string. (Parameter 'startIndex').
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 68 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'redis' is imported (dash/_shared_storage/redis.py:98), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'redis' is imported (dash/_shared_storage/redis.py:98), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'redis' is imported (dash/_shared_storage/redis.py:98), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 40 further occurrence(s) are not listed individually; the score already reflects all 80.
R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 23 further occurrence(s) are not listed individually; the score already reflects all 63.
R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 97 further occurrence(s) are not listed individually; the score already reflects all 137.
X16 Unfloored truncation loop — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X29 Per-element action decided by a fixed element — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
Repo exclusion declarations: 52 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
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.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
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.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
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".
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.
+ 50 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with Dropdown.Dropdown (cyclomatic 102), DatePickerRange.DatePickerRange (cyclomatic 82), RangeSlider.RangeSlider (cyclomatic 70). — 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 4 together lifts Cyclomatic Complexity from 5.8 to about 6.4/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 89 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 5 bodies over 60 down to 60 or less in Cognitive Complexity — start with Dropdown.Dropdown (cognitive 107), DatePickerRange.DatePickerRange (cognitive 96), DashWrapper.DashWrapper::setHydratedProps (cognitive 91). — 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 5 together lifts Cognitive Complexity from 4.4 to about 5.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.1 / 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 20 FunctionTooLong finding(s) in God Classes — start with dependencies.js (3), callbacks.ts (2), Dropdown.tsx. — One of this dimension's main actionable groups (20 warning-level).
Resolve the 8 FileTooLong finding(s) in God Classes — start with dash.py, dependencies.js, callbacks.ts. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 3 TooManyMethods finding(s) in God Classes — start with dash.py, browser.py, index.tsx. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
26 duplicated block group(s) detected. 2.2 % of the production lines (1,497 of 67,570) are in a reported copy. A further 21 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .ts, .tsx (53% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
Edited copy of a member (16 corresponding lines) · ×3dash/testing/wait.py:17
Near-duplicate member pair (94 shared lines)dash/backends/_fastapi.py:896
+ 37 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 Edited copy of a member (16 corresponding lines) finding(s) in Code Duplication — start with wait.py, celery_manager.py, _flask.py. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Duplicated block (19 lines × 2) finding(s) in Code Duplication — start with _fastapi.py, application_runners.py. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with _fastapi.py, _flask.py. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
14 production modules (npm+Python), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 6 of the 14 (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).
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 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with _fastapi.py, _quart.py, base_component.py. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 211 tests. Measured on the JavaScript/TypeScript suite only — at least 390 test source file(s) (.py) went unread, so its test quality is unmeasured and is not in these counts.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
31 outdated direct production npm dependency(ies) of 53 graded, 0 pinning defect(s), across 14 package.json (14 of them the product) and 13 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 7 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 49 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (46), REDACTED (3). — One of this dimension's main actionable groups (49 recommendation-level).
Resolve the 14 Deprecated finding(s) in Dependency Hygiene — start with package.json (14). — One of this dimension's main actionable groups (14 warning-level).
Resolve the 4 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (4). — One of this dimension's main actionable groups (4 recommendation-level).
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 659 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 659 package(s) this repository's committed lockfile installs for a consumer — its 60 production, optional and peer dependency(ies), across 14 product package.json manifest(s), and everything those install in turn. Its 253 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. Third-party code that ships WITHOUT a manifest entry was read too: 0 component(s) whose licence travels in the tree (vendored or copied-in directories, licence comments preserved in committed bundles, compiled wasm modules) and 0 bundled package(s) named only by a bundle's module path, graded on the registry; 0 use a banned licence. 5 vendored, copied-in or compiled component(s) state no licence this pass can read — missing data, not charged. This repository publishes itself under MIT / UNLICENSED, 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.
Resolve the 11 Hotspot finding(s) in Churn × Complexity Hotspots — start with dash.py, callbacks.ts, DashWrapper.tsx. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with executedCallbacks.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor7.6 / 10Strong✓ 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.
36 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is dash/_stream_hub.py. Counted over 152 of the 422 production source files in this repository: 249 are under the ~2,400-byte size floor this dimension measures over, and the remaining 21 have no attributable history left to measure.
Off-boarding risk: anonymized user #1 · ×2
What to do
Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
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.
26 deducted task-comment markers across 54080 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 20 TodoComment finding(s) in Explicit Debt — start with REDACTED (6), test_missing_outputs.py (2), test_base_component.py. — One of this dimension's main actionable groups (20 warning-level).
Resolve the 6 FixmeComment finding(s) in Explicit Debt — start with _jupyter.py (3), store.ts (2), test_clientside_restarts.py. — One of this dimension's main actionable groups (6 warning-level).
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.
0 of 2 documentation facets pass in full; short on: F2 example, F4 map. 15 document(s) read across 16 unit(s).
Documentation: no build, run or usage example · ×4@plotly/dash-websocket-worker/README.md:1
What to do
Resolve the 4 Documentation finding(s) in Documentation Quality — start with README.md (4). — One of this dimension's main actionable groups (4 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
1 naming inconsistencies among 54 declarations measured against a convention their peers follow.
`columnID` spells `ID` where 55 names in the project spell it `Id`components/dash-table/src/dash-table/components/Export/utils.tsx:64
What to do
Resolve the 1 `columnID` spells `ID` where 55 names in the project spell it `Id` finding(s) in Naming Consistency — start with utils.tsx. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
doc comments repeat the names · ×6@plotly/dash-websocket-worker/src/MessageRouter.ts:31
What to do
Resolve the 16 redundant comment finding(s) in Comment Value — start with RangeSlider.tsx (3), helpers.ts (2), workerClient.ts (2). — One of this dimension's main actionable groups (16 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D26 · Project Cohesion2.8 / 10Weak✓ Tool-verified
What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.
4 of 11 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×4components/dash-table/package.json:1
What to do
Resolve the 4 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with package.json (4). — One of this dimension's main actionable groups (4 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: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
gitleaks scanned the current working tree and the part of the history named below, and found no secrets. History coverage: The newest 9840 of 10665 commits were scanned for secrets, back to commit 51aa31416e7b; older commits were not. `gitleaks` TIMED OUT after 41.2s against a 41.2s budget, so we killed its process tree. The budget is ours; the work may simply be larger than it allows.
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).
158 finding(s): 0 critical, 142 high, 14 medium, 2 low. 114 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 4 file(s) — `components/dash-core-components/src/fragments/Graph.react.js` (line 11), `components/dash-table/src/core/math/arrayZipMap.ts` (line 61), `dash/dash-renderer/src/wrapper/DashWrapper.tsx` (line 23), `dash/dash-renderer/src/wrapper/wrapping.ts` (line 2) — 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 3 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
+ 13 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 18 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (16), REDACTED (2). — One of this dimension's main actionable groups (18 issue-level).
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
No action in Static Analysis (SAST) — all 114 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 (114 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. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 20 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (20). — One of this dimension's main actionable groups (20 issue-level).
Resolve the 7 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7). — One of this dimension's main actionable groups (7 issue-level).
Resolve the 2 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d30_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.
70 of 173 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is components/dash-table/src/dash-table/components/ControlledTable/index.tsx. Counted over 173 of the 422 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 69 Orphaned file finding(s) in Knowledge Freshness — start with index.tsx (7), index.ts (5), wrappers.tsx (2). — One of this dimension's main actionable groups (69 recommendation-level).
Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with index.tsx. — One of this dimension's main actionable groups (1 issue-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 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with props.ts. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 4 Change coupling finding(s) in Change Coupling — start with config.ts, _callback.py, workerClient.ts. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
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 2 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.
AC2 · Forms & labels1.2 / 10Critical✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. — components/dash-core-components/src/fragments/Dropdown.tsx:555
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. (×39) — REDACTED:312, REDACTED:313, REDACTED:314, …
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"). (×4) — components/dash-core-components/index.html:2, REDACTED:3, components/dash-html-components/vignettes/dash-html-components.html:3, …
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×2) — components/dash-core-components/index.html:2, dash/dash-renderer/index.html:2
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×3) — components/dash-core-components/index.html:2, REDACTED:3, components/dash-html-components/vignettes/dash-html-components.html:3
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×2) — REDACTED:309, components/dash-html-components/vignettes/dash-html-components.html:462
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="react-entry-point">, so there is no content here to wrap — render the <main> from the component mounted into it. — dash/dash-renderer/index.html:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
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. (×8) — components/dash-core-components/src/components/Tabs.tsx:78, components/dash-table/src/dash-table/components/CellDropdown/index.tsx:30, components/dash-table/src/dash-table/derived/cell/operations.tsx:84, …
A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}. (×2) — components/dash-core-components/src/fragments/DatePickerRange.tsx:373, components/dash-core-components/src/fragments/DatePickerSingle.tsx:177
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. (×3) — components/dash-core-components/src/fragments/DatePickerRange.tsx:434, components/dash-core-components/src/fragments/DatePickerSingle.tsx:210, components/dash-core-components/src/fragments/Dropdown.tsx:515
This <th> 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. — components/dash-table/src/dash-table/derived/header/wrappers.tsx:66
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.
A plain <div> has the implicit role "generic", which supports no ARIA states, so this aria-expanded is dropped and assistive tech is never told the state at all. Put aria-expanded on the element that owns the behaviour (the button or control the user operates), or give this <div> a role that supports aria-expanded. (×2) — components/dash-core-components/src/fragments/DatePickerRange.tsx:373, components/dash-core-components/src/fragments/DatePickerSingle.tsx:177
aria-hidden="true" hides the element from assistive tech but leaves it keyboard-focusable — a confusing dead stop. Remove aria-hidden or make the element non-focusable. — components/dash-core-components/src/fragments/Dropdown.tsx:427
What to do
Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
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.
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.
`BaseDashServer` declares 17 abstract methods: `register_assets_blueprint`, `register_error_handlers`, `add_url_rule`, `before_request`, `after_request`, `has_request_context`, `run`, `make_response`, `jsonify`, `enable_compression`, `register_prune_error_handler`, `register_timing_hooks`, `register_callback_api_routes`, `setup_component_suites`, `serve_callback`, `setup_index`, `setup_catchall`. Counted over its `@abstractmethod`s (and abstract properties), once per name; concrete methods are helpers an implementer inherits, not a burden, and `_`-prefixed members are not counted. 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. — dash/backends/base_server.py:163
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.
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.
`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. — components/dash-core-components/src/utils/optionRendering.tsx:345
What to do
Remove the dead code that looks live: delete dead if(false) branches, which read as logic that runs, and either do the real async work or drop the async keyword from fake-async functions, which promise work they never wait for.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Most of the production code is in directories of its own, but 1 application file(s) sit at the repository root beside the build and tooling files (`REDACTED`).
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
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's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack as a CI step. What was searched, so you can tell an absence from a miss: the 7 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:11
What to do
Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
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.
The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — dash/development/build_process.py:161, dash/testing/application_runners.py:123
What to do
Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
R1 · Type Safety7.1 / 10Strong✓ 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.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
@plotly/dash-jupyterlab/lib/index.js:13 · @plotly/dash-jupyterlab/src/index.ts:25 — the two spans are one implementation copied and then locally edited — 408 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. — @plotly/dash-jupyterlab/lib/index.js:13
components/dash-core-components/src/fragments/DatePickerRange.tsx:111 · components/dash-core-components/src/fragments/DatePickerSingle.tsx:68 — the two spans are one implementation copied and then locally edited — 358 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. — components/dash-core-components/src/fragments/DatePickerRange.tsx:111
components/dash-core-components/src/components/DatePickerRange.tsx:17 · components/dash-core-components/src/components/DatePickerSingle.tsx:20 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — components/dash-core-components/src/components/DatePickerRange.tsx:17
components/dash-core-components/src/fragments/DatePickerRange.tsx:433 · components/dash-core-components/src/fragments/DatePickerSingle.tsx:209 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — components/dash-core-components/src/fragments/DatePickerRange.tsx:433
components/dash-table/src/dash-table/components/EdgeFactory.tsx:67 · components/dash-table/src/dash-table/components/EdgeFactory.tsx:102 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — components/dash-table/src/dash-table/components/EdgeFactory.tsx:67
components/dash-table/src/dash-table/syntax-tree/lexicon/column.ts:33 · components/dash-table/src/dash-table/syntax-tree/lexicon/columnMulti.ts:47 — 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. — components/dash-table/src/dash-table/syntax-tree/lexicon/column.ts:33
components/dash-table/src/dash-table/syntax-tree/lexicon/columnMulti.ts:43 · components/dash-table/src/dash-table/syntax-tree/lexicon/query.ts:69 — 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. — components/dash-table/src/dash-table/syntax-tree/lexicon/columnMulti.ts:43
components/dash-core-components/src/fragments/DatePickerRange.tsx:365 · components/dash-core-components/src/fragments/DatePickerSingle.tsx:169 — 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. — components/dash-core-components/src/fragments/DatePickerRange.tsx:365
components/dash-core-components/src/fragments/DatePickerRange.tsx:481 · components/dash-core-components/src/fragments/DatePickerSingle.tsx:249 — 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. — components/dash-core-components/src/fragments/DatePickerRange.tsx:481
dash/dash-renderer/src/actions/dependencies.js:170 · dash/dash-renderer/src/actions/dependencies.js:203 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — dash/dash-renderer/src/actions/dependencies.js:170
components/dash-core-components/src/utils/sliderRendering.tsx:66 · components/dash-core-components/src/utils/sliderRendering.tsx:150 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — components/dash-core-components/src/utils/sliderRendering.tsx:66
dash/dash-renderer/src/actions/dependencies_ts.ts:552 · dash/dash-renderer/src/actions/dependencies_ts.ts:654 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — dash/dash-renderer/src/actions/dependencies_ts.ts:552
dash/dash-renderer/src/actions/dependencies_ts.ts:74 · dash/dash-renderer/src/actions/dependencies_ts.ts:135 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — dash/dash-renderer/src/actions/dependencies_ts.ts:74
dash/dash-renderer/src/actions/dependencies.js:1146 · dash/dash-renderer/src/actions/dependencies.js:1213 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dash/dash-renderer/src/actions/dependencies.js:1146
dash/dash-renderer/src/actions/api.js:74 · dash/dash-renderer/src/actions/callbacks.ts:1403 — the two spans are one implementation copied and then locally edited — 96 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. — dash/dash-renderer/src/actions/api.js:74
components/dash-core-components/src/components/Checklist.tsx:24 · components/dash-core-components/src/components/RadioItems.tsx:25 — 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. — components/dash-core-components/src/components/Checklist.tsx:24
components/dash-core-components/src/fragments/DatePickerRange.tsx:202 · components/dash-core-components/src/fragments/DatePickerRange.tsx:230 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — components/dash-core-components/src/fragments/DatePickerRange.tsx:202
components/dash-core-components/src/fragments/Loading/spinners/CircleSpinner.tsx:8 · components/dash-core-components/src/fragments/Loading/spinners/CubeSpinner.tsx:5 · components/dash-core-components/src/fragments/Loading/spinners/DefaultSpinner.tsx:8 · components/dash-core-components/src/fragments/Loading/spinners/DotSpinner.tsx:8 — the 4 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — components/dash-core-components/src/fragments/Loading/spinners/CircleSpinner.tsx:8
dash/dash-renderer/src/actions/callbacks.ts:1011 · dash/dash-renderer/src/actions/callbacks.ts:1057 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dash/dash-renderer/src/actions/callbacks.ts:1011
components/dash-core-components/src/fragments/RangeSlider.tsx:287 · components/dash-core-components/src/fragments/RangeSlider.tsx:358 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — components/dash-core-components/src/fragments/RangeSlider.tsx:287
dash/dash-renderer/src/actions/dependencies.js:1317 · dash/dash-renderer/src/actions/dependencies.js:1361 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — dash/dash-renderer/src/actions/dependencies.js:1317
components/dash-core-components/src/components/ConfirmDialog.react.js:45 · components/dash-core-components/src/components/ConfirmDialogProvider.react.js:36 — 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. — components/dash-core-components/src/components/ConfirmDialog.react.js:45
components/dash-core-components/src/fragments/DatePickerRange.tsx:290 · components/dash-core-components/src/fragments/DatePickerSingle.tsx:148 — 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. — components/dash-core-components/src/fragments/DatePickerRange.tsx:290
components/dash-table/src/dash-table/components/CellFactory.tsx:200 · components/dash-table/src/dash-table/components/HeaderFactory.tsx:160 — the two spans are one implementation copied and then locally edited — 128 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. — components/dash-table/src/dash-table/components/CellFactory.tsx:200
.lintstagedrc.js:46 · .lintstagedrc.js:78 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — .lintstagedrc.js:46
components/dash-core-components/src/components/Graph.react.js:58 · components/dash-core-components/src/components/Graph.react.js:79 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — components/dash-core-components/src/components/Graph.react.js:58
components/dash-table/src/dash-table/dash/DataTable.js:842 · components/dash-table/src/dash-table/dash/DataTable.js:872 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — components/dash-table/src/dash-table/dash/DataTable.js:842
components/dash-table/src/dash-table/dash/DataTable.js:1276 · components/dash-table/src/dash-table/dash/DataTable.js:1305 · components/dash-table/src/dash-table/dash/DataTable.js:1327 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — components/dash-table/src/dash-table/dash/DataTable.js:1276
dash/dash-renderer/src/actions/dependencies_ts.ts:531 · dash/dash-renderer/src/actions/dependencies_ts.ts:634 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — dash/dash-renderer/src/actions/dependencies_ts.ts:531
components/dash-core-components/src/fragments/Loading/spinners/CircleSpinner.tsx:10 · components/dash-core-components/src/fragments/Loading/spinners/CubeSpinner.tsx:7 · components/dash-core-components/src/fragments/Loading/spinners/DefaultSpinner.tsx:10 · components/dash-core-components/src/fragments/Loading/spinners/DotSpinner.tsx:10 · +1 more site(s) not listed — the 5 copies are spread across 5 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. — components/dash-core-components/src/fragments/Loading/spinners/CircleSpinner.tsx:10
components/dash-core-components/webpack.config.js:9 · components/dash-html-components/webpack.config.js:5 — 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. — components/dash-core-components/webpack.config.js:9
components/dash-table/src/dash-table/conditional/index.ts:94 · components/dash-table/src/dash-table/conditional/index.ts:110 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — components/dash-table/src/dash-table/conditional/index.ts:94
REDACTED:452 · dash/dash-renderer/src/components/error/ComponentErrorBoundary.react.js:11 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:452
dash/dash-renderer/src/components/error/CallbackGraph/CallbackGraphEffects.js:30 · dash/dash-renderer/src/components/error/CallbackGraph/CallbackGraphEffects.js:46 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — dash/dash-renderer/src/components/error/CallbackGraph/CallbackGraphEffects.js:30
components/dash-table/src/core/browser/DOM.ts:4 · components/dash-table/src/core/browser/DOM.ts:24 — the two spans are one implementation copied and then locally edited — 55 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. — components/dash-table/src/core/browser/DOM.ts:4
components/dash-table/src/dash-table/components/EdgeFactory.tsx:134 · components/dash-table/src/dash-table/components/EdgeFactory.tsx:166 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — components/dash-table/src/dash-table/components/EdgeFactory.tsx:134
components/dash-table/src/dash-table/components/FilterFactory.tsx:198 · components/dash-table/src/dash-table/components/FilterFactory.tsx:215 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — components/dash-table/src/dash-table/components/FilterFactory.tsx:198
components/dash-table/src/dash-table/dash/DataTable.js:1257 · components/dash-table/src/dash-table/dash/DataTable.js:1278 · components/dash-table/src/dash-table/dash/DataTable.js:1307 · components/dash-table/src/dash-table/dash/DataTable.js:1329 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — components/dash-table/src/dash-table/dash/DataTable.js:1257
components/dash-core-components/src/components/Button.tsx:27 · components/dash-core-components/src/components/Textarea.tsx:56 — 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. — components/dash-core-components/src/components/Button.tsx:27
components/dash-table/src/dash-table/components/ControlledTable/index.tsx:701 · components/dash-table/src/dash-table/components/ControlledTable/index.tsx:717 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — components/dash-table/src/dash-table/components/ControlledTable/index.tsx:701
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.
dash/dash-renderer/src/checkPropTypes.js:7 imports prop-types/lib/ReactPropTypesSecret, 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. — dash/dash-renderer/src/checkPropTypes.js:7
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
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.
(anonymous) has cyclomatic complexity 43 and cognitive complexity 42; 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. — components/dash-table/tests/visual/percy-storybook/Style.percy.tsx:41
(anonymous) has cyclomatic complexity 38 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 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. — components/dash-table/tests/js-unit/dash_table_queries_test.ts:436
(anonymous) 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. — components/dash-table/tests/js-unit/dash_table_queries_test.ts:52
(anonymous) has cyclomatic complexity 30 and cognitive complexity 64; 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. — dash/dash-renderer/src/actions/callbacks.ts:1208
switchCell has cyclomatic complexity 28 and cognitive complexity 32; 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. — components/dash-table/src/dash-table/components/ControlledTable/index.tsx:616
Dropdown has cyclomatic complexity 26 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — components/dash-core-components/src/fragments/Dropdown.tsx:28
(anonymous) has cyclomatic complexity 25 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 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. — dash/extract-meta.js:731
setHydratedProps has cyclomatic complexity 24 and cognitive complexity 91; 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. — dash/dash-renderer/src/wrapper/DashWrapper.tsx:284
filterEventData has cyclomatic complexity 23 and cognitive complexity 42; 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. — components/dash-core-components/src/fragments/Graph.react.js:58
getPropType has cyclomatic complexity 22 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. — dash/extract-meta.js:352
readLoop has cyclomatic complexity 22 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dash/dash-renderer/src/utils/streamClient.ts:419
handleMessage has cyclomatic complexity 22 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 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. — dash/dash-renderer/src/utils/workerClient.ts:287
handleWebsocketCallback has cyclomatic complexity 22 and cognitive complexity 27; 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. — dash/dash-renderer/src/actions/callbacks.ts:938
DatePickerRange has cyclomatic complexity 22 and cognitive complexity 19; 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. — components/dash-core-components/src/fragments/DatePickerRange.tsx:26
(anonymous) has cyclomatic complexity 21 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — components/dash-table/src/dash-table/derived/header/content.tsx:222
normalizeDate has cyclomatic complexity 21 and cognitive complexity 19; 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. — components/dash-table/src/dash-table/type/date.ts:20
DatePickerSingle has cyclomatic complexity 21 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — components/dash-core-components/src/fragments/DatePickerSingle.tsx:20
getCallbackByOutput has cyclomatic complexity 20 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 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. — dash/dash-renderer/src/actions/dependencies.js:1296
observer has cyclomatic complexity 20 and cognitive complexity 19; 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. — dash/dash-renderer/src/observers/requestedCallbacks.ts:58
(anonymous) has cyclomatic complexity 19 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — components/dash-core-components/src/fragments/Dropdown.tsx:312
(anonymous) has cyclomatic complexity 19 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — components/dash-core-components/src/fragments/RangeSlider.tsx:274
(anonymous) has cyclomatic complexity 18 and cognitive complexity 22; 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. — components/dash-core-components/src/fragments/DatePickerRange.tsx:317
(anonymous) has cyclomatic complexity 18 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:150
handleKeyDown has cyclomatic complexity 18 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — components/dash-table/src/dash-table/components/ControlledTable/index.tsx:556
(anonymous) has cyclomatic complexity 18 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — components/dash-table/src/dash-table/components/Table/derivedPropsHelper.ts:36
(anonymous) has cyclomatic complexity 18 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — components/dash-core-components/src/utils/calendar/CalendarMonth.tsx:107
getDataTransferItems has cyclomatic complexity 17 and cognitive complexity 29; 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. — components/dash-core-components/src/fragments/Upload.react.js:98
(anonymous) has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — components/dash-table/tests/js-unit/dash_table_queries_test.ts:286
handleResize has cyclomatic complexity 17 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — components/dash-table/src/dash-table/components/ControlledTable/index.tsx:413
componentDidUpdate has cyclomatic complexity 16 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dash/dash-renderer/src/components/core/Reloader.react.js:61
getGroupedColumnIndices has cyclomatic complexity 16 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — components/dash-table/src/dash-table/utils/actions.js:4
(anonymous) has cyclomatic complexity 15 and cognitive complexity 42; 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. — dash/dash-renderer/src/actions/dependencies.js:1688
(anonymous) has cyclomatic complexity 15 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — components/dash-core-components/src/fragments/DatePickerRange.tsx:148
parse has cyclomatic complexity 14 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — components/dash-table/src/dash-table/utils/TableClipboardHelper.ts:115
(anonymous) has cyclomatic complexity 14 and cognitive complexity 19; 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. — dash/dash-renderer/src/react-shim.js:32
fetchCallback has cyclomatic complexity 14 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dash/dash-renderer/src/actions/callbacks.ts:610
partialIdMatch has cyclomatic complexity 13 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dash/dash-renderer/src/actions/dependencies.js:1182
handleOneId has cyclomatic complexity 13 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dash/dash-renderer/src/actions/dependencies.js:1618
(anonymous) has cyclomatic complexity 13 and cognitive complexity 22; 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. — components/dash-table/src/core/syntax-tree/lexer.ts:27
handleStreamedResponse has cyclomatic complexity 13 and cognitive complexity 22; 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. — dash/dash-renderer/src/actions/callbacks.ts:763
Do you agree with this assessment?
R3 · Large Files7.9 / 10Strong✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
dash/dash-renderer/src/actions/dependencies.js has 1652 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dash/dash-renderer/src/actions/dependencies.js:1
components/dash-table/src/dash-table/dash/DataTable.js has 1447 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — components/dash-table/src/dash-table/dash/DataTable.js:1
components/dash-core-components/src/types.ts has 1419 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — components/dash-core-components/src/types.ts:1
dash/dash-renderer/src/actions/callbacks.ts has 1341 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dash/dash-renderer/src/actions/callbacks.ts:1
components/dash-table/src/dash-table/components/ControlledTable/index.tsx has 1116 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — components/dash-table/src/dash-table/components/ControlledTable/index.tsx:1
dash/extract-meta.js has 772 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dash/extract-meta.js:1
dash/dash-renderer/src/utils/streamClient.ts has 714 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dash/dash-renderer/src/utils/streamClient.ts:1
dash/dash-renderer/src/actions/dependencies_ts.ts has 634 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dash/dash-renderer/src/actions/dependencies_ts.ts:1
components/dash-core-components/src/fragments/Dropdown.tsx has 618 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — components/dash-core-components/src/fragments/Dropdown.tsx:1
dash/dash-renderer/src/wrapper/DashWrapper.tsx has 561 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dash/dash-renderer/src/wrapper/DashWrapper.tsx:1
components/dash-core-components/src/fragments/Graph.react.js has 552 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — components/dash-core-components/src/fragments/Graph.react.js:1
components/dash-core-components/src/components/Graph.react.js has 512 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — components/dash-core-components/src/components/Graph.react.js:1
components/dash-table/src/dash-table/components/Table/props.ts has 505 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — components/dash-table/src/dash-table/components/Table/props.ts:1
dash/dash-renderer/src/persistence.js has 495 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dash/dash-renderer/src/persistence.js:1
components/dash-core-components/src/fragments/DatePickerRange.tsx has 482 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — components/dash-core-components/src/fragments/DatePickerRange.tsx:1
components/dash-core-components/src/fragments/RangeSlider.tsx has 454 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — components/dash-core-components/src/fragments/RangeSlider.tsx:1
dash/dash-renderer/src/actions/patch.ts has 451 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dash/dash-renderer/src/actions/patch.ts:1
REDACTED has 431 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
dash/dash-renderer/src/observers/executedCallbacks.ts has 422 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dash/dash-renderer/src/observers/executedCallbacks.ts:1
components/dash-table/src/dash-table/derived/header/content.tsx has 420 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — components/dash-table/src/dash-table/derived/header/content.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 Coverage5.8 / 10Adequate✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — components/dash-core-components/src/fragments/Graph.react.js:1, components/dash-core-components/src/components/Graph.react.js:1, components/dash-core-components/src/fragments/DatePickerRange.tsx:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
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.
`components/dash-table` is TypeScript, but a type error in it cannot fail anything this repository runs: its `private::format.prettier` script (`prettier --config .prettierrc --write "{src,tests,demo}/**/*.{js,ts,tsx}"`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. Add a type check that can fail — a `typecheck` script running `tsc --noEmit` (or `vue-tsc`/`svelte-check`) that CI or the workspace pipeline runs, or a build step that checks before it bundles. — components/dash-table/package.json:22
The package in `components/dash-html-components` declares the lint script `lint` (`eslint src scripts`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `components/dash-html-components` (or the workspace's task runner). — components/dash-html-components/package.json:19
Do you agree with this assessment?
R7 · Dead Code8.6 / 10Strong✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 73 application, 40 tooling and 133 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (73 application, 40 tooling, 133 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 (×7) — components/dash-table/generator/cssPropertiesGenerator.js, dash/dash-renderer/src/AccessDenied.react.js, @plotly/eslint-config-dash/typescript.js, …
no import path from any entry point (73 application, 40 tooling, 133 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dash/dash-renderer/src/AccessDenied.react.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — dash/dash-renderer/src/styles/styles.js
Nothing imports this binding — it is safe to review for removal. (×18) — components/dash-core-components/src/components/Upload.react.js:200, components/dash-core-components/src/utils/calendar/CalendarMonth.tsx:28, components/dash-core-components/src/utils/computeSliderMarkers.ts:251, …
Nothing ultimately consumes this binding: its only referrer is the re-export in dash/dash-renderer/src/types/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in dash/dash-renderer/src/types/index.ts in the same commit, or the barrel will import a name that no longer exists. (×3) — dash/dash-renderer/src/types/component.ts:49, dash/dash-renderer/src/types/component.ts:56, dash/dash-renderer/src/types/component.ts:60
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. (×4) — tests/unit/development/TestReactComponent.react.js:1, dash/extract-meta.js:15, dash/extract-meta.js:8, …
Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json. — components/dash-core-components/src/fragments/Markdown.tsx:3
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. — package.json:51
Declared in @plotly/dash-generator-test-component-nested/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. — @plotly/dash-generator-test-component-nested/package.json:31
Declared in @plotly/dash-generator-test-component-standard/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. — @plotly/dash-generator-test-component-standard/package.json:31
Declared in @plotly/dash-test-components/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. — @plotly/dash-test-components/package.json:34
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 — Only what this repository's own non-C# files could be read for was assessed — 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. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so 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.
`//cdnjs.cloudflare.com/ajax/libs/codemirror/5.0.0/codemirror.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. 2 such include(s) across the repository's markup. — components/dash-core-components/index.html:14
What to do
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.
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.
`forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape. (×2) — dash/dash-renderer/src/observers/executingCallbacks.ts:44, dash/dash-renderer/src/observers/prioritizedCallbacks.ts:160
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 · 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.
`objPropsToCamel` is exported and takes `value: any` from its caller, and it calls itself at line 17 (`objPropsToCamel`) with a piece of `value` — and nowhere in `objPropsToCamel` 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 `objPropsToCamel` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — components/dash-table/src/core/objPropsToCamel.ts:17
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 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 async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. 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 question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 0/2 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`requestDashVersionInfo` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — dash/dash-renderer/src/components/error/menu/VersionInfo.react.js:27
`fetchCallback` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — dash/dash-renderer/src/actions/callbacks.ts:610
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
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 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.
`debug` at line 430 is called with an argument built by `"…".join(menu.text.split("…"))` (line 430), whose cost grows with the collection it walks. Python evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on. — dash/testing/browser.py:430
What to do
In Python, put the construction behind the logger's own check (`if logger.isEnabledFor(logging.DEBUG):`), or pass the collection itself with a `%s` placeholder (`logger.debug("Items %s", items)`) so the logging module renders it only when the record is emitted. The placeholder alone is not the fix when the argument is still built first: it defers the formatting, not a `json.dumps`, a `join` or a comprehension in the argument, and an f-string defers nothing at all.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped4.7 / 10Weak✓ 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.
`md.render(String(value))` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — components/dash-table/src/dash-table/components/CellMarkdown/index.tsx:19
`md.render(value)` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — components/dash-table/src/dash-table/components/Tooltip/index.tsx:80
`layoutRequest.content` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:77
`dependenciesRequest.content` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:92
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. (×9) — dash/_streaming.py:315, dash/dash-renderer/src/utils/streamClient.ts:743, dash/dash-renderer/src/components/error/menu/DebugMenu.react.js:163, …
`except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×6) — dash/mcp/primitives/tools/callback_adapter.py:205, dash/mcp/primitives/tools/input_schemas/schema_callback_type_annotations.py:47, dash/backends/_fastapi.py:232, …
An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `close()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: narrow the catch to the exception this release can actually raise, and record it through whatever this codebase already uses to report problems — or, if it truly cannot matter, say why in a comment on the catch. — dash/_shared_storage/redis.py:417
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — components/dash-core-components/src/fragments/Graph.react.js:421
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 log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. 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 `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
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.
4/6 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.
~0.2 `!` null assertions per 1k TypeScript source lines — 5 assertion(s) across the 31496 source line(s) of the 255 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: components/dash-table/src/dash-table/components/Table/props.ts (2), dash/dash-renderer/src/observers/websocketObserver.ts (2), dash/dash-renderer/src/utils/workerClient.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
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 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 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 — 4 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.
D36 Supply-chain Provenance & Signing — 2 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
SC1 Supply-chain hygiene — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: this repository stores data through 'redis' (dash/_shared_storage/redis.py:98) but declares no persisted model this check reads (Django, SQLAlchemy, SQLModel, Peewee, Tortoise and MongoEngine model fields, Alembic and Django migration columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL files). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
C4 Data Retention — Not assessed: this repository stores data through 'redis' (dash/_shared_storage/redis.py:98) but declares no persisted model this check reads (Django, SQLAlchemy, SQLModel, Peewee, Tortoise and mongoengine model fields, Alembic and Django migration columns, SQL schemas). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
C5 Data-Subject Rights — Not assessed: this repository stores data through 'redis' (dash/_shared_storage/redis.py:98) but declares no persisted model this check reads (Django, SQLAlchemy, SQLModel, Peewee, Tortoise and mongoengine model fields, Alembic and Django migration columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL files). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 43 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.
AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AC6 Visual & motion safety — Visual & motion safety could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
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 Python 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 — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
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
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — C2 reached only 37% of this repository's production lines — typescript (28,787 lines), javascript (13,490 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
D11 Test Reliability — Test reliability not scored — polyglot repository, one half's runner produced no measurement
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.
D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed JavaScript, Python surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 reads resolved call sites in the languages it reads 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.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 4 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — polyglot repository, one half has no runner
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (17 value object(s))
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage data present for 17 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.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — X26 reached only 37% of this repository's production lines — typescript (28,787 lines), javascript (13,490 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X27 Collection changed while being enumerated — X27 reached only 37% of this repository's production lines — typescript (28,787 lines), javascript (13,490 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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.
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.
Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test mixed generation Standard js component is parsed — Passed 2×, failed 1× across repeated runs.
Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes Array of union of shapes and string — Passed 2×, failed 1× across repeated runs.
Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes Component prop has comment — Passed 2×, failed 1× across repeated runs.
Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes Default props — Passed 4×, failed 2× across repeated runs.
Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes Enum options — Passed 2×, failed 1× across repeated runs.
Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes Nested props to any — Passed 2×, failed 1× across repeated runs.
Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes Obj properties — Passed 2×, failed 1× across repeated runs.
Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes Required props — Passed 2×, failed 1× across repeated runs.
Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes Tuple elements — Passed 2×, failed 1× across repeated runs.
Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes Union of number and string — Passed 2×, failed 1× across repeated runs.
Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes Union of primitives and arrays of primitives — Passed 2×, failed 1× across repeated runs.
Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes Union of shape and string — Passed 2×, failed 1× across repeated runs.
Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes objectOf node — Passed 2×, failed 1× across repeated runs.
Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes union and literal values — Passed 2×, failed 1× across repeated runs.
Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes union of boolean and literal values — Passed 2×, failed 1× across repeated runs.
Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop attributes union of duplicated types — Passed 2×, failed 1× across repeated runs.
Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names FCComponent array type — Passed 2×, failed 1× across repeated runs.
Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names FCComponent boolean type — Passed 2×, failed 1× across repeated runs.
Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names FCComponent children React.Node — Passed 2×, failed 1× across repeated runs.
Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names FCComponent dash_component DashComponent — Passed 2×, failed 1× across repeated runs.
Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names FCComponent element JSX.Element — Passed 2×, failed 1× across repeated runs.
Flaky test: @plotly/dash-generator-test-component-typescript/generator.test.ts::Test Typescript component metadata generation Test prop type names FCComponent enum type — Passed 2×, failed 1× across repeated runs.
+ 52 more in this group — see findings.md.
AC2 · Forms & labels· Link with no accessible name · ×39
Link with no accessible name REDACTED:312— 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 REDACTED:313— 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 REDACTED:314— 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 REDACTED:315— 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 REDACTED:316— 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 REDACTED: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.
Link with no accessible name REDACTED:318— 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 REDACTED:319— 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 REDACTED:320— 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 REDACTED:323— 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 REDACTED:324— 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 REDACTED:325— 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 REDACTED:326— 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 REDACTED:327— 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 REDACTED:328— 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 REDACTED:329— 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 REDACTED:330— 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 REDACTED:331— 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 REDACTED:334— 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 REDACTED:335— 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 REDACTED:336— 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 REDACTED:337— 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 REDACTED:338— 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 REDACTED:339— 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 REDACTED:340— 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.
AC4 · Keyboard semantics· Click handler on a non-interactive <span> · ×5
Click handler on a non-interactive <span> components/dash-table/src/dash-table/derived/header/content.tsx:313— 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> components/dash-table/src/dash-table/derived/header/content.tsx:332— 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> components/dash-table/src/dash-table/derived/header/content.tsx:347— 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> components/dash-table/src/dash-table/derived/header/content.tsx:369— 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> components/dash-table/src/dash-table/derived/header/content.tsx:400— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
<html> without a lang components/dash-core-components/index.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang REDACTED:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang components/dash-html-components/vignettes/dash-html-components.html:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang dash/dash-renderer/index.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×4
Click handler on a non-interactive <div> components/dash-core-components/src/components/Tabs.tsx:78— 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> components/dash-core-components/src/fragments/DatePickerRange.tsx:373— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Click handler on a non-interactive <div> components/dash-core-components/src/fragments/DatePickerSingle.tsx:177— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Click handler on a non-interactive <div> components/dash-table/src/dash-table/components/CellDropdown/index.tsx:30— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC3 · Page structure· Document without a <title> · ×2
Document without a <title> components/dash-core-components/index.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>.
Document without a <title> dash/dash-renderer/index.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>.
AC5 · ARIA correctness· aria-expanded on a <div> with no role to carry it · ×2
aria-expanded on a <div> with no role to carry it components/dash-core-components/src/fragments/DatePickerRange.tsx:373— A plain <div> has the implicit role "generic", which supports no ARIA states, so this aria-expanded is dropped and assistive tech is never told the state at all. Put aria-expanded on the element that owns the behaviour (the button or control the user operates), or give this <div> a role that supports aria-expanded.
aria-expanded on a <div> with no role to carry it components/dash-core-components/src/fragments/DatePickerSingle.tsx:177— A plain <div> has the implicit role "generic", which supports no ARIA states, so this aria-expanded is dropped and assistive tech is never told the state at all. Put aria-expanded on the element that owns the behaviour (the button or control the user operates), or give this <div> a role that supports aria-expanded.
AC2 · Forms & labels· <input> without a programmatic label · ×1
<input> without a programmatic label components/dash-core-components/src/fragments/Dropdown.tsx:555— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
AC4 · Keyboard semantics· Click handler on a non-interactive <td> · ×1
Click handler on a non-interactive <td> components/dash-table/src/dash-table/derived/cell/operations.tsx:84— 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· Hover-only interaction on <th> · ×1
Hover-only interaction on <th> components/dash-table/src/dash-table/derived/header/wrappers.tsx:66— This <th> 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.
AC5 · ARIA correctness· aria-hidden on a focusable element · ×1
aria-hidden on a focusable element components/dash-core-components/src/fragments/Dropdown.tsx:427— aria-hidden="true" hides the element from assistive tech but leaves it keyboard-focusable — a confusing dead stop. Remove aria-hidden or make the element non-focusable.
Orphaned knowledge components/dash-table/src/dash-table/components/ControlledTable/index.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.
Boundary-crossing change coupling: props.ts ↔ extract-meta.js @plotly/dash-generator-test-component-typescript/src/props.ts:1— `@plotly/dash-generator-test-component-typescript/src/props.ts` (context @plotly) and `dash/extract-meta.js` (context dash) sit in DIFFERENT parts of the tree yet change together 57% of the time (8 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `0fbd86aa` Refactor Tab component; `59c3d697` Implement dropdown as custom/radix component; `7ec85f3a` Fix typing generation bugs #3017 #3266 — run `git show` on any of them.
Unlisted import 'react' tests/unit/development/TestReactComponent.react.js:1— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'react-docgen' dash/extract-meta.js:15— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'typescript' dash/extract-meta.js:8— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'prop-types' @plotly/dash-generator-test-component-typescript/src/components/MixedComponent.tsx:1— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Serious — 530 finding(s)
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file components/dash-core-components/src/fragments/Graph.react.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 components/dash-core-components/src/components/Graph.react.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 components/dash-core-components/src/fragments/DatePickerRange.tsx: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 components/dash-core-components/src/fragments/RangeSlider.tsx: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 dash/dash-renderer/src/observers/executedCallbacks.ts: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 components/dash-table/demo/AppMode.ts: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 dash/dash-renderer/src/observers/requestedCallbacks.ts: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 components/dash-html-components/scripts/generate-components.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 @plotly/dash-websocket-worker/src/WebSocketManager.ts: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 components/dash-core-components/src/fragments/Loading/spinners/GraphSpinner.tsx: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 components/dash-table/generator/cssPropertiesGenerator.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 dash/dash-renderer/src/observers/websocketObserver.ts: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 components/dash-core-components/src/components/Tabs.tsx: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 components/dash-core-components/src/fragments/DatePickerSingle.tsx: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 @plotly/dash-websocket-worker/src/MessageRouter.ts: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 components/dash-core-components/src/fragments/Upload.react.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 dash/dash-renderer/src/components/error/menu/VersionInfo.react.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 dash/dash-renderer/src/components/error/menu/DebugMenu.react.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 components/dash-core-components/src/components/Store.react.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 components/dash-core-components/src/components/Clipboard.react.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 dash/dash-renderer/src/components/core/Reloader.react.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 dash/dash-renderer/src/observers/prioritizedCallbacks.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
+ 15 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×27
TodoComment tests/unit/development/test_base_component.py:340— # TODO - Rename 'children' to 'children' — 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 tests/integration/devtools/test_callback_validation.py:116— # TODO: remove suppress_callback_exceptions after we move that part to FE — 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 tests/integration/callbacks/test_missing_outputs.py:48— # TODO: however it doesn't get *triggered* by the ALL emptying, — 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 tests/integration/callbacks/test_missing_outputs.py:140— # TODO: however it doesn't get *triggered* by the ALL emptying, — 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 dash/_jupyter.py:391— # TODO: why do we need this? Why only in this mode? Importing here in — 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 dash/dash.py:1112— # TODO - Set browser cache limit - pass hash into frontend — 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 REDACTED:71— # TODO _prop_names, _type, _namespace, and available_properties — 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 REDACTED:73— # TODO - Tab out the repr for the repr of these components to make it — 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 REDACTED:75— # TODO - Include "description" "defaultValue" in the repr and docstring — 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 REDACTED:77— # TODO - Handle "required" — 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 REDACTED:79— # TODO - How to handle user-given `null` values? I want to include — 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 REDACTED:140— # TODO For dash 3.0, remove the Optional and = None for proper typing. — 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 dash/development/base_component.py:438— # TODO - Should we return the number of items that have IDs — 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 dash/dash-renderer/src/store.ts:101— // TODO - Protect this under a debug mode? — 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 dash/dash-renderer/src/actions/callbacks.ts:227— // TODO: unwrapped list of wildcard ids? — 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 dash/backends/_quart.py:887— # TODO consider using a sync wraper — 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 components/dash-table/src/dash-table/components/ControlledTable/index.tsx:644— // TODO There is a better way to handle native focus being out of sync — 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 components/dash-core-components/tests/integration/graph/test_graph_basics.py:87— # TODO: not sure 2 calls actually makes sense here, shouldn't it be 1? — 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 components/dash-core-components/tests/integration/graph/test_graph_varia.py:659— # TODO: in eager mode, built-in plotly.js wins!! I don't think this is what we want. — 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 components/dash-core-components/src/components/Tabs.tsx:178— // TODO: handle components that are not dcc.Tab components (throw 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.
FunctionTooLong: Dropdown.Dropdown components/dash-core-components/src/fragments/Dropdown.tsx:28— FunctionTooLong — Dropdown runs 461 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 361 over it, 4.61× 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: extract-meta.gatherComponents dash/extract-meta.js:164— FunctionTooLong — gatherComponents runs 452 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 352 over it, 4.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: DatePickerRange.DatePickerRange components/dash-core-components/src/fragments/DatePickerRange.tsx:26— FunctionTooLong — DatePickerRange runs 367 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 267 over it, 3.67× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: DashWrapper.DashWrapper dash/dash-renderer/src/wrapper/DashWrapper.tsx:79— FunctionTooLong — DashWrapper runs 351 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 251 over it, 3.51× 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: RangeSlider.RangeSlider components/dash-core-components/src/fragments/RangeSlider.tsx:22— FunctionTooLong — RangeSlider runs 331 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 231 over it, 3.31× 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.CalendarComponent components/dash-core-components/src/utils/calendar/Calendar.tsx:57— FunctionTooLong — CalendarComponent runs 248 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 148 over it, 2.48× 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: callbacks.handleServerside dash/dash-renderer/src/actions/callbacks.ts:581— FunctionTooLong — handleServerside runs 234 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 134 over it, 2.34× 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: dependencies.computeGraphs dash/dash-renderer/src/actions/dependencies.js:707— FunctionTooLong — computeGraphs runs 233 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 133 over it, 2.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: DatePickerSingle.DatePickerSingle components/dash-core-components/src/fragments/DatePickerSingle.tsx:20— FunctionTooLong — DatePickerSingle runs 219 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 119 over it, 2.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: content.getter components/dash-table/src/dash-table/derived/header/content.tsx:197— FunctionTooLong — getter runs 204 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 104 over it, 2.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: Input.Input components/dash-core-components/src/components/Input.tsx:61— FunctionTooLong — Input runs 194 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 94 over it, 1.94× 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: CallbackGraphContainer.react.CallbackGraph REDACTED:199— FunctionTooLong — CallbackGraph 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.
FunctionTooLong: CircleSpinner.CircleSpinner components/dash-core-components/src/fragments/Loading/spinners/CircleSpinner.tsx:8— FunctionTooLong — CircleSpinner runs 161 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 61 over it, 1.61× 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: CalendarMonth.CalendarMonth components/dash-core-components/src/utils/calendar/CalendarMonth.tsx:54— FunctionTooLong — CalendarMonth runs 154 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 54 over it, 1.54× 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: Tabs.Tabs components/dash-core-components/src/components/Tabs.tsx:99— FunctionTooLong — Tabs runs 141 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: CubeSpinner.CubeSpinner components/dash-core-components/src/fragments/Loading/spinners/CubeSpinner.tsx:5— FunctionTooLong — CubeSpinner runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: websocketObserver.initializeWebSocket dash/dash-renderer/src/observers/websocketObserver.ts:81— FunctionTooLong — initializeWebSocket runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: dependencies.getUnfilteredLayoutCallbacks dash/dash-renderer/src/actions/dependencies.js:1565— FunctionTooLong — getUnfilteredLayoutCallbacks runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: dependencies.validateCallbacksToLayout dash/dash-renderer/src/actions/dependencies.js:543— FunctionTooLong — validateCallbacksToLayout runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: callbacks.handleWebsocketCallback dash/dash-renderer/src/actions/callbacks.ts:938— FunctionTooLong — handleWebsocketCallback runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Deprecated: rimraf @plotly/dash-jupyterlab/package.json:44— rimraf 3.0.2, declared in @plotly/dash-jupyterlab/package.json, is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: babel-eslint @plotly/eslint-config-dash/package.json:9— babel-eslint 10.1.0, declared in @plotly/eslint-config-dash/package.json, is marked deprecated by its publisher: "babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint @plotly/eslint-config-dash/package.json:10— eslint 8.26.0, declared in @plotly/eslint-config-dash/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @fortawesome/react-fontawesome components/dash-core-components/package.json:42— @fortawesome/react-fontawesome 0.1.19, declared in components/dash-core-components/package.json, is marked deprecated by its publisher: "v0.1x is no longer supported. Please update to v3.1.1 or greater.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint components/dash-core-components/package.json:102— eslint 8.57.1, declared in components/dash-core-components/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint components/dash-html-components/package.json:44— eslint 8.57.1, declared in components/dash-html-components/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @babel/polyfill components/dash-table/package.json:48— @babel/polyfill 7.12.1, declared in components/dash-table/package.json, is marked deprecated by its publisher: "🚨 This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more information.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @fortawesome/react-fontawesome components/dash-table/package.json:54— @fortawesome/react-fontawesome 0.2.6, declared in components/dash-table/package.json, is marked deprecated by its publisher: "v0.2.x is no longer supported. Unless you are still using FontAwesome 5, please update to v3.1.1 or greater.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint components/dash-table/package.json:73— eslint 8.57.1, declared in components/dash-table/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @babel/polyfill dash/dash-renderer/package.json:24— @babel/polyfill 7.12.1, declared in dash/dash-renderer/package.json, is marked deprecated by its publisher: "🚨 This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more information.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @babel/plugin-proposal-class-properties dash/dash-renderer/package.json:48— @babel/plugin-proposal-class-properties 7.18.6, declared in dash/dash-renderer/package.json, is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint dash/dash-renderer/package.json:67— eslint 8.57.1, declared in dash/dash-renderer/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: rimraf dash/labextension/package.json:40— rimraf 3.0.2, declared in dash/labextension/package.json, is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @lerna/filter-options package.json:51— @lerna/filter-options 6.4.1, declared in package.json, is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". Replace it with the package or version that message names, or record why this one must stay.
Hotspot: dash/dash.py dash/dash.py:515— dash/dash.py changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in Dash.__init__ at line 515. 2 of those changes were fix/bug commits, and the other 18 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:27:57 -05:00' --until='2026-11-16 12:27:57 -05:00' --full-history --no-merges -- dash/dash.py`: 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: dash/dash-renderer/src/actions/callbacks.ts dash/dash-renderer/src/actions/callbacks.ts:581— dash/dash-renderer/src/actions/callbacks.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 63 in callbacks.handleServerside at line 581. 1 of those changes was a fix/bug commit, and the other 7 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:27:57 -05:00' --until='2026-11-16 12:27:57 -05:00' --full-history --no-merges -- dash/dash-renderer/src/actions/callbacks.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: dash/dash-renderer/src/wrapper/DashWrapper.tsx dash/dash-renderer/src/wrapper/DashWrapper.tsx:79— dash/dash-renderer/src/wrapper/DashWrapper.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 70 in DashWrapper.DashWrapper at line 79. 3 of those changes were fix/bug commits, and the other 4 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:27:57 -05:00' --until='2026-11-16 12:27:57 -05:00' --full-history --no-merges -- dash/dash-renderer/src/wrapper/DashWrapper.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: dash/backends/_fastapi.py dash/backends/_fastapi.py:529— dash/backends/_fastapi.py changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in FastAPIDashServer.run at line 529. 2 of those changes were fix/bug commits, and the other 14 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:27:57 -05:00' --until='2026-11-16 12:27:57 -05:00' --full-history --no-merges -- dash/backends/_fastapi.py`: 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: dash/_callback.py dash/_callback.py:721— dash/_callback.py changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in _callback._handle_rest_background_callback at line 721. 3 of those changes were fix/bug commits, and the other 10 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:27:57 -05:00' --until='2026-11-16 12:27:57 -05:00' --full-history --no-merges -- dash/_callback.py`: 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: dash/dash-renderer/src/actions/dependencies.js dash/dash-renderer/src/actions/dependencies.js:707— dash/dash-renderer/src/actions/dependencies.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in dependencies.computeGraphs at line 707. 1 of those changes was a fix/bug commit, and the other 3 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:27:57 -05:00' --until='2026-11-16 12:27:57 -05:00' --full-history --no-merges -- dash/dash-renderer/src/actions/dependencies.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: dash/dash-renderer/src/utils/streamClient.ts dash/dash-renderer/src/utils/streamClient.ts:419— dash/dash-renderer/src/utils/streamClient.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in StreamClient.readLoop at line 419. 1 of those changes was a fix/bug commit, and the other 4 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:27:57 -05:00' --until='2026-11-16 12:27:57 -05:00' --full-history --no-merges -- dash/dash-renderer/src/utils/streamClient.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: benchmarks/run.py benchmarks/run.py:346— benchmarks/run.py changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in run.gate at line 346. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:27:57 -05:00' --until='2026-11-16 12:27:57 -05:00' --full-history --no-merges -- benchmarks/run.py`: 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: dash/dash-renderer/src/actions/paths.js dash/dash-renderer/src/actions/paths.js:36— dash/dash-renderer/src/actions/paths.js changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in paths.computePaths at line 36. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:27:57 -05:00' --until='2026-11-16 12:27:57 -05:00' --full-history --no-merges -- dash/dash-renderer/src/actions/paths.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: dash/dash-renderer/src/observers/websocketObserver.ts dash/dash-renderer/src/observers/websocketObserver.ts:81— dash/dash-renderer/src/observers/websocketObserver.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in websocketObserver.initializeWebSocket at line 81. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:27:57 -05:00' --until='2026-11-16 12:27:57 -05:00' --full-history --no-merges -- dash/dash-renderer/src/observers/websocketObserver.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: dash/dash-renderer/src/actions/dependencies_ts.ts dash/dash-renderer/src/actions/dependencies_ts.ts:45— dash/dash-renderer/src/actions/dependencies_ts.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in dependencies_ts.getCallbacksByInput at line 45. 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:27:57 -05:00' --until='2026-11-16 12:27:57 -05:00' --full-history --no-merges -- dash/dash-renderer/src/actions/dependencies_ts.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.
Swallowed exception (empty catch) dash/_streaming.py:315— 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) dash/dash-renderer/src/utils/streamClient.ts:743— 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) dash/dash-renderer/src/components/error/menu/DebugMenu.react.js:163— 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) dash/dash-renderer/src/components/error/menu/VersionInfo.react.js:76— 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) dash/dash-renderer/src/components/error/menu/VersionInfo.react.js:162— 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) dash/dash-renderer/src/components/error/menu/VersionInfo.react.js:172— 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) dash/dash-renderer/src/components/error/menu/VersionInfo.react.js:182— 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) dash/_shared_storage/redis.py:417— An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `close()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: narrow the catch to the exception this release can actually raise, and record it through whatever this codebase already uses to report problems — or, if it truly cannot matter, say why in a comment on the catch.
Swallowed exception (empty catch) components/dash-table/src/dash-table/utils/Markdown.ts:16— 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) components/dash-table/src/dash-table/utils/Markdown.ts:21— 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) components/dash-core-components/src/fragments/Graph.react.js:421— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
FileTooLong: dash/dash.py dash/dash.py— FileTooLong — 1309 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 809 over it, 2.62× 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: actions/dependencies.js dash/dash-renderer/src/actions/dependencies.js— FileTooLong — 1065 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 565 over it, 2.13× 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: actions/callbacks.ts dash/dash-renderer/src/actions/callbacks.ts— FileTooLong — 963 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 463 over it, 1.93× 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: ControlledTable/index.tsx components/dash-table/src/dash-table/components/ControlledTable/index.tsx— FileTooLong — 875 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: ControlledTable (79-1309). The bar is 500 significant lines; this is 375 over it, 1.75× 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: dash/_callback.py dash/_callback.py— FileTooLong — 861 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 361 over it, 1.72× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: backends/_fastapi.py dash/backends/_fastapi.py— FileTooLong — 835 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 335 over it, 1.67× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: backends/_quart.py dash/backends/_quart.py— FileTooLong — 620 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 120 over it, 1.24× 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: dash/extract-meta.js dash/extract-meta.js— FileTooLong — 568 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units), about 80% of them inside a single declaration: gatherComponents (164-851). 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.
FixmeComment tests/integration/clientside/test_clientside_restarts.py:7— # FIXME find another way to test clientside callbacks restarts — 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.
FixmeComment dash/_jupyter.py:364— # FIXME Move config initialization to main dash __init__ — 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.
FixmeComment dash/_jupyter.py:483— # FIXME there is a 403 on this, maybe it's updated? — 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.
FixmeComment dash/_jupyter.py:499— # FIXME valid only in jupyterlab but accepted in regular notebooks show nothing. — 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.
FixmeComment dash/dash-renderer/src/store.ts:17— // FIXME add proper type for the store. — 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.
FixmeComment dash/dash-renderer/src/store.ts:45— // FIXME Remove observer pattern and refactor to standard reducers/actions/selectors. — 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.
Swallowed exception (caught, then discarded) dash/mcp/primitives/tools/callback_adapter.py:205— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) dash/mcp/primitives/tools/input_schemas/schema_callback_type_annotations.py:47— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) dash/backends/_fastapi.py:232— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) dash/backends/_fastapi.py:891— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) dash/backends/_quart.py:606— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) dash/_shared_storage/redis.py:133— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
AC3 · Page structure· Page without a main landmark · ×4
Page without a main landmark components/dash-core-components/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark REDACTED:3— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark components/dash-html-components/vignettes/dash-html-components.html:3— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark dash/dash-renderer/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="react-entry-point">, so there is no content here to wrap — render the <main> from the component mounted into it.
Change coupling: config.ts ↔ dash.py dash/dash-renderer/src/config.ts:1— `dash/dash-renderer/src/config.ts` and `dash/dash.py` change together 64% of the time (7 of the 11 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `e33a79b3` Multiplex HTTP streams over shared storage; `08cc2b14` callback args hardening.; `8c2329fe` add configuration for heartbeat and proper te\sts for reconnect — run `git show` on any of them.
Change coupling: _callback.py ↔ callbacks.ts dash/_callback.py:1— `dash/_callback.py` and `dash/dash-renderer/src/types/callbacks.ts` change together 60% of the time (9 of the 15 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `ce7530ca` Add streaming callbacks (@callback generator functions); `4302682f` Added options to compress callback request body; `7ba747a2` fix infinite loading with persitent keyword on callbacks — run `git show` on any of them.
Change coupling: workerClient.ts ↔ dash.py dash/dash-renderer/src/utils/workerClient.ts:1— `dash/dash-renderer/src/utils/workerClient.ts` and `dash/dash.py` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `ce7530ca` Add streaming callbacks (@callback generator functions); `8c2329fe` add configuration for heartbeat and proper te\sts for reconnect; `d7161b7c` batch/debounce websocket set_props — run `git show` on any of them.
Change coupling: ws.py ↔ workerClient.ts dash/backends/ws.py:1— `dash/backends/ws.py` and `dash/dash-renderer/src/utils/workerClient.ts` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `9f4ecb00` Add partial path reads to WebSocket get_prop; `ce7530ca` Add streaming callbacks (@callback generator functions); `c2654249` improved websocket connection management — run `git show` on any of them.
Duplicated block (17 lines × 2 locations) .lintstagedrc.js:46— .lintstagedrc.js:46 · .lintstagedrc.js:78 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2 locations) components/dash-core-components/src/components/Graph.react.js:58— components/dash-core-components/src/components/Graph.react.js:58 · components/dash-core-components/src/components/Graph.react.js:79 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2 locations) components/dash-table/src/dash-table/dash/DataTable.js:842— components/dash-table/src/dash-table/dash/DataTable.js:842 · components/dash-table/src/dash-table/dash/DataTable.js:872 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2 locations) dash/dash-renderer/src/actions/dependencies_ts.ts:531— dash/dash-renderer/src/actions/dependencies_ts.ts:531 · dash/dash-renderer/src/actions/dependencies_ts.ts:634 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2 locations) components/dash-core-components/webpack.config.js:9— components/dash-core-components/webpack.config.js:9 · components/dash-html-components/webpack.config.js:5 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (15 lines × 2 locations) components/dash-table/src/dash-table/conditional/index.ts:94— components/dash-table/src/dash-table/conditional/index.ts:94 · components/dash-table/src/dash-table/conditional/index.ts:110 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2 locations) REDACTED:452— REDACTED:452 · dash/dash-renderer/src/components/error/ComponentErrorBoundary.react.js:11 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (15 lines × 2 locations) dash/dash-renderer/src/components/error/CallbackGraph/CallbackGraphEffects.js:30— dash/dash-renderer/src/components/error/CallbackGraph/CallbackGraphEffects.js:30 · dash/dash-renderer/src/components/error/CallbackGraph/CallbackGraphEffects.js:46 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×4
Untrusted text written into markup unescaped components/dash-table/src/dash-table/components/CellMarkdown/index.tsx:19— `md.render(String(value))` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped components/dash-table/src/dash-table/components/Tooltip/index.tsx:80— `md.render(value)` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:77— `layoutRequest.content` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:92— `dependenciesRequest.content` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
AC4 · Keyboard semantics· Anchor without href · ×3
Anchor without href components/dash-core-components/src/fragments/DatePickerRange.tsx:434— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href components/dash-core-components/src/fragments/DatePickerSingle.tsx:210— An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
Anchor without href components/dash-core-components/src/fragments/Dropdown.tsx:515— 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.
TooManyMethods: Dash dash/dash.py:258— TooManyMethods — 52 methods. The bar is 30 methods; this is 22 over it, 1.73× 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: Browser dash/testing/browser.py:38— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ControlledTable components/dash-table/src/dash-table/components/ControlledTable/index.tsx:79— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× 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.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×3
Edited copy of a member (16 corresponding lines) dash/testing/wait.py:17— dash/testing/wait.py:17-32 | dash/testing/wait.py:38-53 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) dash/background_callback/managers/celery_manager.py:123— dash/background_callback/managers/celery_manager.py:123-139 | dash/background_callback/managers/diskcache_manager.py:197-212 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) dash/backends/_flask.py:505— dash/backends/_flask.py:505-520 | dash/backends/_quart.py:566-581 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Low cohesion: FastAPIDashServer (LCOM4 9) dash/backends/_fastapi.py:400— FastAPIDashServer's methods fall into 9 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 9 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: QuartDashServer (LCOM4 7) dash/backends/_quart.py:114— QuartDashServer's methods fall into 7 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 7 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: Component (LCOM4 5) dash/development/base_component.py:110— Component'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.
Duplicated block (30 lines × 2 locations) components/dash-core-components/src/fragments/DatePickerRange.tsx:365— components/dash-core-components/src/fragments/DatePickerRange.tsx:365 · components/dash-core-components/src/fragments/DatePickerSingle.tsx:169 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (30 lines × 2 locations) components/dash-core-components/src/fragments/DatePickerRange.tsx:481— components/dash-core-components/src/fragments/DatePickerRange.tsx:481 · components/dash-core-components/src/fragments/DatePickerSingle.tsx:249 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (30 lines × 2 locations) dash/dash-renderer/src/actions/dependencies.js:170— dash/dash-renderer/src/actions/dependencies.js:170 · dash/dash-renderer/src/actions/dependencies.js:203 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Unused dependency 'react-jsx-parser' @plotly/dash-generator-test-component-nested/package.json:31— Declared in @plotly/dash-generator-test-component-nested/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 'react-jsx-parser' @plotly/dash-generator-test-component-standard/package.json:31— Declared in @plotly/dash-generator-test-component-standard/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 'react-jsx-parser' @plotly/dash-test-components/package.json:34— Declared in @plotly/dash-test-components/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.
ClassTooLong: ControlledTable components/dash-table/src/dash-table/components/ControlledTable/index.tsx:79— ClassTooLong — 814 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 400 significant lines; this is 414 over it, 2.04× 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: Dropdown components/dash-core-components/src/fragments/Dropdown.tsx:1— ClassTooLong — 461 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 61 over it, 1.15× 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.
MethodTooLong: ControlledTable.render components/dash-table/src/dash-table/components/ControlledTable/index.tsx:954— MethodTooLong — render runs 154 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 54 over it, 1.54× 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: CellFactory.createCells components/dash-table/src/dash-table/components/CellFactory.tsx:47— MethodTooLong — createCells runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (19 lines × 2) dash/backends/_fastapi.py:1058— dash/backends/_fastapi.py:1058-1076 | dash/backends/_quart.py:790-808 — before extracting anything, compare `dash/backends/_fastapi.py` and `dash/backends/_quart.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 175 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `dash/backends/_fastapi.py:1058` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) dash/testing/application_runners.py:484— dash/testing/application_runners.py:484-502 | dash/testing/application_runners.py:584-602 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `dash/testing/application_runners.py:484` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) dash/backends/_fastapi.py:652— dash/backends/_fastapi.py:652-663 | dash/backends/_flask.py:227-238 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) dash/backends/_flask.py:509— dash/backends/_flask.py:509-520 | dash/backends/_quart.py:570-581 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10–11 lines × 2) dash/backends/_flask.py:450— dash/backends/_flask.py:450-459 | dash/backends/_quart.py:190-200 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `dash/backends/_quart.py:190` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10–11 lines × 2) dash/backends/ws.py:305— dash/backends/ws.py:305-315 | dash/dash.py:1778-1787 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Outbound HTTP without resilience dash/development/build_process.py:161— `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience dash/testing/application_runners.py:123— `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
R10 · Code Duplication· Duplicated block with local edits (63 matched lines × 2 locations) · ×2
Duplicated block with local edits (63 matched lines × 2 locations) @plotly/dash-jupyterlab/lib/index.js:13— @plotly/dash-jupyterlab/lib/index.js:13 · @plotly/dash-jupyterlab/src/index.ts:25 — the two spans are one implementation copied and then locally edited — 408 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 (63 matched lines × 2 locations) components/dash-core-components/src/fragments/DatePickerRange.tsx:111— components/dash-core-components/src/fragments/DatePickerRange.tsx:111 · components/dash-core-components/src/fragments/DatePickerSingle.tsx:68 — the two spans are one implementation copied and then locally edited — 358 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 (29 lines × 2 locations) components/dash-core-components/src/utils/sliderRendering.tsx:66— components/dash-core-components/src/utils/sliderRendering.tsx:66 · components/dash-core-components/src/utils/sliderRendering.tsx:150 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (29 lines × 2 locations) dash/dash-renderer/src/actions/dependencies_ts.ts:552— dash/dash-renderer/src/actions/dependencies_ts.ts:552 · dash/dash-renderer/src/actions/dependencies_ts.ts:654 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (24 lines × 2 locations) components/dash-core-components/src/components/Checklist.tsx:24— components/dash-core-components/src/components/Checklist.tsx:24 · components/dash-core-components/src/components/RadioItems.tsx:25 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (24 lines × 2 locations) components/dash-core-components/src/fragments/DatePickerRange.tsx:202— components/dash-core-components/src/fragments/DatePickerRange.tsx:202 · components/dash-core-components/src/fragments/DatePickerRange.tsx:230 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2 locations) components/dash-core-components/src/fragments/RangeSlider.tsx:287— components/dash-core-components/src/fragments/RangeSlider.tsx:287 · components/dash-core-components/src/fragments/RangeSlider.tsx:358 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2 locations) dash/dash-renderer/src/actions/dependencies.js:1317— dash/dash-renderer/src/actions/dependencies.js:1317 · dash/dash-renderer/src/actions/dependencies.js:1361 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2 locations) components/dash-core-components/src/components/ConfirmDialog.react.js:45— components/dash-core-components/src/components/ConfirmDialog.react.js:45 · components/dash-core-components/src/components/ConfirmDialogProvider.react.js:36 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (18 lines × 2 locations) components/dash-core-components/src/fragments/DatePickerRange.tsx:290— components/dash-core-components/src/fragments/DatePickerRange.tsx:290 · components/dash-core-components/src/fragments/DatePickerSingle.tsx:148 — 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.
Duplicated block (14 lines × 2 locations) components/dash-table/src/dash-table/components/EdgeFactory.tsx:134— components/dash-table/src/dash-table/components/EdgeFactory.tsx:134 · components/dash-table/src/dash-table/components/EdgeFactory.tsx:166 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (14 lines × 2 locations) components/dash-table/src/dash-table/components/FilterFactory.tsx:198— components/dash-table/src/dash-table/components/FilterFactory.tsx:198 · components/dash-table/src/dash-table/components/FilterFactory.tsx:215 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2 locations) components/dash-core-components/src/components/Button.tsx:27— components/dash-core-components/src/components/Button.tsx:27 · components/dash-core-components/src/components/Textarea.tsx:56 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (13 lines × 2 locations) components/dash-table/src/dash-table/components/ControlledTable/index.tsx:701— components/dash-table/src/dash-table/components/ControlledTable/index.tsx:701 · components/dash-table/src/dash-table/components/ControlledTable/index.tsx:717 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×2
JavaScript dependencies are not locked @plotly/dash-websocket-worker/package.json:23— @plotly/dash-websocket-worker/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked dash/labextension/package.json:33— dash/labextension/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
`async` callback passed to `forEach` dash/dash-renderer/src/observers/executingCallbacks.ts:44— `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
`async` callback passed to `forEach` dash/dash-renderer/src/observers/prioritizedCallbacks.ts:160— `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
X2 · Cancellation propagation· Async function without AbortSignal · ×2
Async function without AbortSignal: requestDashVersionInfo dash/dash-renderer/src/components/error/menu/VersionInfo.react.js:27— `requestDashVersionInfo` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchCallback dash/dash-renderer/src/actions/callbacks.ts:610— `fetchCallback` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
AC3 · Page structure· Heading level jumps from h1 to h3 · ×1
Heading level jumps from h1 to h3 REDACTED:309— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC3 · Page structure· Heading level jumps from h1 to h4 · ×1
Heading level jumps from h1 to h4 components/dash-html-components/vignettes/dash-html-components.html:462— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Dropdown.Dropdown (cyclomatic 102) components/dash-core-components/src/fragments/Dropdown.tsx:28— Dropdown.Dropdown has cyclomatic complexity 102 (threshold 15). Of this number, 25 points are the body's own statements and 77 belong to 23 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.
DatePickerRange.DatePickerRange (cyclomatic 82) components/dash-core-components/src/fragments/DatePickerRange.tsx:26— DatePickerRange.DatePickerRange has cyclomatic complexity 82 (threshold 15). Of this number, 21 points are the body's own statements and 61 belong to 14 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.
RangeSlider.RangeSlider (cyclomatic 70) components/dash-core-components/src/fragments/RangeSlider.tsx:22— RangeSlider.RangeSlider has cyclomatic complexity 70 (threshold 15). Most of this is not in the body itself: 9 of the 70 points are its own statements and the rest belongs to 16 function items inside it that branch (a function literal at line 274, valueIsValid, constrainToValidValue, …). 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.
callbacks.handleServerside (cyclomatic 63) dash/dash-renderer/src/actions/callbacks.ts:581— callbacks.handleServerside has cyclomatic complexity 63 (threshold 15). Most of this is not in the body itself: 3 of the 63 points are its own statements and the rest belongs to 11 function items inside it that branch (fetchCallback, a function literal at line 763, a function literal at line 852, …). 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.
dependencies.computeGraphs (cyclomatic 41) dash/dash-renderer/src/actions/dependencies.js:707— dependencies.computeGraphs has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 4 of the 41 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 856, a function literal at line 966, a function literal at line 815, …). 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.
Input.Input (cyclomatic 40) components/dash-core-components/src/components/Input.tsx:61— Input.Input has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 6 of the 40 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 176, a function literal at line 276, a function literal at line 228, …). 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.
DatePickerSingle.DatePickerSingle (cyclomatic 37) components/dash-core-components/src/fragments/DatePickerSingle.tsx:20— DatePickerSingle.DatePickerSingle has cyclomatic complexity 37 (threshold 15). Of this number, 19 points are the body's own statements and 18 belong to 8 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.
Dash.enable_dev_tools (cyclomatic 35) dash/dash.py:2276— Dash.enable_dev_tools has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
dependencies.getUnfilteredLayoutCallbacks (cyclomatic 34) dash/dash-renderer/src/actions/dependencies.js:1565— dependencies.getUnfilteredLayoutCallbacks 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 5 function items inside it that branch (a function literal at line 1688, handleOneId, addCallback, …). 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.CalendarComponent (cyclomatic 30) components/dash-core-components/src/utils/calendar/Calendar.tsx:57— Calendar.CalendarComponent has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 4 of the 30 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 201, 137, 153, …). 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.
callbacks.executeCallback::__execute (cyclomatic 29) dash/dash-renderer/src/actions/callbacks.ts:1208— callbacks.executeCallback::__execute has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ControlledTable.switchCell (cyclomatic 28) components/dash-table/src/dash-table/components/ControlledTable/index.tsx:616— ControlledTable.switchCell has cyclomatic complexity 28 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Dash.__init__ (cyclomatic 27) dash/dash.py:515— Dash.__init__ has cyclomatic complexity 27 (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.
Tabs.Tabs (cyclomatic 26) components/dash-core-components/src/components/Tabs.tsx:99— Tabs.Tabs has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 4 of the 26 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 177, valueOrDefault, a function literal at line 255, …). 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.
dependencies.validateCallbacksToLayout (cyclomatic 26) dash/dash-renderer/src/actions/dependencies.js:543— dependencies.validateCallbacksToLayout 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 7 function items inside it that branch (validateProp, validateMap, a function literal at line 628, …). 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.
Dash.run (cyclomatic 25) dash/dash.py:2574— Dash.run 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.
FastAPIDashServer.run (cyclomatic 24) dash/backends/_fastapi.py:529— FastAPIDashServer.run 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.
Graph.react.filterEventData (cyclomatic 24) components/dash-core-components/src/fragments/Graph.react.js:58— Graph.react.filterEventData has cyclomatic complexity 24 (threshold 15). Of this number, 23 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DashWrapper.DashWrapper::setHydratedProps (cyclomatic 24) dash/dash-renderer/src/wrapper/DashWrapper.tsx:284— DashWrapper.DashWrapper::setHydratedProps 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.
CallbackGraph (cyclomatic 23) REDACTED:199— CallbackGraph has cyclomatic complexity 23 (threshold 15). Of this number, 13 points are the body's own statements and 10 belong to 26 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.
Component._get_set_or_delete (cyclomatic 22) dash/development/base_component.py:304— Component._get_set_or_delete 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.
Resources._filter_resources (cyclomatic 22) dash/resources.py:49— Resources._filter_resources 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.
content.getter (cyclomatic 22) components/dash-table/src/dash-table/derived/header/content.tsx:197— content.getter 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 2 function literals inside it that branch (lines 222, 408). 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.
utils.crawlLayout (cyclomatic 22) dash/dash-renderer/src/actions/utils.js:30— utils.crawlLayout has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 8 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 98, 38). 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.
WorkerClient.handleMessage (cyclomatic 22) dash/dash-renderer/src/utils/workerClient.ts:287— WorkerClient.handleMessage 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.
callbacks.handleWebsocketCallback (cyclomatic 22) dash/dash-renderer/src/actions/callbacks.ts:938— callbacks.handleWebsocketCallback has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
extract-meta.gatherComponents::getPropType (cyclomatic 22) dash/extract-meta.js:352— extract-meta.gatherComponents::getPropType 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.
Dash._collect_and_register_resources (cyclomatic 21) dash/dash.py:1359— Dash._collect_and_register_resources has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CalendarMonth.CalendarMonth (cyclomatic 21) components/dash-core-components/src/utils/calendar/CalendarMonth.tsx:54— CalendarMonth.CalendarMonth 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 2 function literals inside it that branch (lines 107, 205). 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.
date.normalizeDate (cyclomatic 21) components/dash-table/src/dash-table/type/date.ts:20— date.normalizeDate has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
dependencies.getCallbackByOutput (cyclomatic 20) dash/dash-renderer/src/actions/dependencies.js:1296— dependencies.getCallbackByOutput 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.
StreamClient.readLoop (cyclomatic 20) dash/dash-renderer/src/utils/streamClient.ts:419— StreamClient.readLoop 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.
ControlledTable.render (cyclomatic 19) components/dash-table/src/dash-table/components/ControlledTable/index.tsx:954— ControlledTable.render has cyclomatic complexity 19 (threshold 15). 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: 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.
websocketObserver.initializeWebSocket (cyclomatic 19) dash/dash-renderer/src/observers/websocketObserver.ts:81— websocketObserver.initializeWebSocket has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 6 function items inside it that branch (processSetProps, a function literal at line 209, a function literal at line 261, …). 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.
_callback._handle_rest_background_callback (cyclomatic 18) dash/_callback.py:721— _callback._handle_rest_background_callback 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.
_callback._prepare_response (cyclomatic 18) dash/_callback.py:780— _callback._prepare_response 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.
optionRendering.OptionsList (cyclomatic 18) components/dash-core-components/src/utils/optionRendering.tsx:212— optionRendering.OptionsList has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 322, 252, 271, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
PlotlyGraph.bindEvents (cyclomatic 18) components/dash-core-components/src/fragments/Graph.react.js:425— PlotlyGraph.bindEvents 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 6 function literals inside it that branch (lines 469, 454, 460, …). 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.
Location.updateLocation (cyclomatic 18) components/dash-core-components/src/components/Location.react.js:18— Location.updateLocation has cyclomatic complexity 18 (threshold 15). Of this number, 10 points are the body's own statements and 8 belong 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.
ControlledTable.handleKeyDown (cyclomatic 18) components/dash-table/src/dash-table/components/ControlledTable/index.tsx:556— ControlledTable.handleKeyDown 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.
derivedPropsHelper.default.<returned closure> (cyclomatic 18) components/dash-table/src/dash-table/components/Table/derivedPropsHelper.ts:36— derivedPropsHelper.default.<returned closure> 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.
APIController.react.storeEffect (cyclomatic 18) REDACTED:137— APIController.react.storeEffect 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 one function literal inside it that branches (line 150). 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.
Dash._setup_server (cyclomatic 17) dash/dash.py:1876— Dash._setup_server 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.
Upload.getDataTransferItems (cyclomatic 17) components/dash-core-components/src/fragments/Upload.react.js:98— Upload.getDataTransferItems 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.
ControlledTable.handleResize (cyclomatic 17) components/dash-table/src/dash-table/components/ControlledTable/index.tsx:413— ControlledTable.handleResize 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.
paths.computePaths (cyclomatic 17) dash/dash-renderer/src/actions/paths.js:36— paths.computePaths has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 82, editMap, a function literal at line 67, …). 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.
dependencies_ts.getCallbacksByInput (cyclomatic 17) dash/dash-renderer/src/actions/dependencies_ts.ts:45— dependencies_ts.getCallbacksByInput has cyclomatic complexity 17 (threshold 15). Of this number, 11 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.
dependencies.getWatchedKeys (cyclomatic 17) dash/dash-renderer/src/actions/dependencies.js:1480— dependencies.getWatchedKeys 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 1499). 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.
RRunner.start (cyclomatic 16) dash/testing/application_runners.py:413— RRunner.start has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (JuliaRunner.start) 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.
JuliaRunner.start (cyclomatic 16) dash/testing/application_runners.py:511— JuliaRunner.start has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (RRunner.start) 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.
tooltip.getSelectedTooltip (cyclomatic 16) components/dash-table/src/dash-table/derived/table/tooltip.ts:22— tooltip.getSelectedTooltip has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
actions.getGroupedColumnIndices (cyclomatic 16) components/dash-table/src/dash-table/utils/actions.js:4— actions.getGroupedColumnIndices has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
DebugMenu.react.Debug (cyclomatic 16) dash/dash-renderer/src/components/error/menu/DebugMenu.react.js:138— DebugMenu.react.Debug has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 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.
APIController.react.UnconnectedContainer (cyclomatic 16) REDACTED:31— APIController.react.UnconnectedContainer has cyclomatic complexity 16 (threshold 15). Of this number, 13 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.
Reloader.componentDidUpdate (cyclomatic 16) dash/dash-renderer/src/components/core/Reloader.react.js:61— Reloader.componentDidUpdate 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.
Repeated repair: dash/dash-renderer/src/observers/executedCallbacks.ts dash/dash-renderer/src/observers/executedCallbacks.ts:174— dash/dash-renderer/src/observers/executedCallbacks.ts 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 12 (its worst body is handlePaths at line 174), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(renderer): clear child paths when callback returns None”; “Extend Patch append perf fix to nested and non-tail locations”; “Fix O(total) Patch().append() slowdown into a growing container”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 12:27:57 -05:00' --until='2026-11-16 12:27:57 -05:00' --full-history --no-merges -- dash/dash-renderer/src/observers/executedCallbacks.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.
Dropdown.Dropdown (cognitive 107) components/dash-core-components/src/fragments/Dropdown.tsx:28— Dropdown.Dropdown has cognitive complexity 107 (threshold 15). Drivers by points: if/else 54 (76 pts), boolean chains 25, ternaries 5, match/switch 1 (nesting depth added 22). Of this number, 18 points are the body's own statements and 89 belong to 23 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.
DatePickerRange.DatePickerRange (cognitive 96) components/dash-core-components/src/fragments/DatePickerRange.tsx:26— DatePickerRange.DatePickerRange has cognitive complexity 96 (threshold 15). Drivers by points: if/else 42 (54 pts), boolean chains 26, ternaries 12 (14 pts), loops 1 (2 pts) (nesting depth added 15). Of this number, 18 points are the body's own statements and 78 belong to 14 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.
DashWrapper.DashWrapper::setHydratedProps (cognitive 91) dash/dash-renderer/src/wrapper/DashWrapper.tsx:284— DashWrapper.DashWrapper::setHydratedProps has cognitive complexity 91 (threshold 15). Drivers by points: if/else 24 (77 pts), loops 3 (12 pts), boolean chains 2 (nesting depth added 62). 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.
utils.crawlLayout (cognitive 71) dash/dash-renderer/src/actions/utils.js:30— utils.crawlLayout has cognitive complexity 71 (threshold 15). Drivers by points: if/else 22 (53 pts), loops 3 (14 pts), boolean chains 4 (nesting depth added 42). Most of this is not in the body itself: 7 of the 71 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 98, 38). 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.
computeGraphs (cognitive 70) dash/dash-renderer/src/actions/dependencies.js:707— computeGraphs has cognitive complexity 70 (threshold 15). Drivers by points: if/else 39 (57 pts), ternaries 3 (6 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 22). Most of this is not in the body itself: 3 of the 70 points are its own statements and the rest belongs to 23 function items inside it that branch (a function literal at line 856, a function literal at line 966, a function literal at line 835, …). 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.
Component._get_set_or_delete (cognitive 60) dash/development/base_component.py:304— Component._get_set_or_delete has cognitive complexity 60 (threshold 15). Drivers by points: if/else 17 (52 pts), error handling 2 (6 pts), loops 1 (2 pts) (nesting depth added 40). 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.
FastAPIDashServer.run (cognitive 56) dash/backends/_fastapi.py:529— FastAPIDashServer.run has cognitive complexity 56 (threshold 15). Drivers by points: if/else 14 (32 pts), loops 6 (17 pts), boolean chains 5, ternaries 1 (2 pts) (nesting depth added 30). 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.
Dash.enable_dev_tools (cognitive 56) dash/dash.py:2276— Dash.enable_dev_tools has cognitive complexity 56 (threshold 15). Drivers by points: if/else 17 (34 pts), ternaries 2 (8 pts), boolean chains 7, loops 3 (7 pts) (nesting depth added 27). 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.
callbacks.executeCallback::__execute (cognitive 55) dash/dash-renderer/src/actions/callbacks.ts:1208— callbacks.executeCallback::__execute has cognitive complexity 55 (threshold 15). Drivers by points: if/else 13 (38 pts), error handling 4 (8 pts), boolean chains 6, ternaries 2, loops 1 (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.
dependencies.getCallbackByOutput (cognitive 53) dash/dash-renderer/src/actions/dependencies.js:1296— dependencies.getCallbackByOutput has cognitive complexity 53 (threshold 15). Drivers by points: if/else 14 (40 pts), loops 3 (10 pts), boolean chains 3 (nesting depth added 33). 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.
Dash._collect_and_register_resources (cognitive 51) dash/dash.py:1359— Dash._collect_and_register_resources has cognitive complexity 51 (threshold 15). Drivers by points: if/else 11 (33 pts), loops 3 (8 pts), ternaries 2 (7 pts), boolean chains 3 (nesting depth added 32). 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.
RangeSlider.RangeSlider (cognitive 50) components/dash-core-components/src/fragments/RangeSlider.tsx:22— RangeSlider.RangeSlider has cognitive complexity 50 (threshold 15). Drivers by points: if/else 19 (22 pts), boolean chains 20, ternaries 6 (8 pts) (nesting depth added 5). Most of this is not in the body itself: 6 of the 50 points are its own statements and the rest belongs to 16 function items inside it that branch (a function literal at line 274, valueIsValid, a function literal at line 73, …). 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.
Dash.run (cognitive 46) dash/dash.py:2574— Dash.run has cognitive complexity 46 (threshold 15). Drivers by points: if/else 13 (20 pts), loops 3 (11 pts), ternaries 3 (8 pts), boolean chains 6, error handling 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Graph.react.filterEventData (cognitive 45) components/dash-core-components/src/fragments/Graph.react.js:58— Graph.react.filterEventData has cognitive complexity 45 (threshold 15). Drivers by points: if/else 16 (37 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 22). Of this number, 42 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.
Input.Input (cognitive 42) components/dash-core-components/src/components/Input.tsx:61— Input.Input has cognitive complexity 42 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 18, ternaries 4 (5 pts) (nesting depth added 4). Most of this is not in the body itself: 4 of the 42 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 176, a function literal at line 228, a function literal at line 276, …). 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.
DatePickerSingle.DatePickerSingle (cognitive 40) components/dash-core-components/src/fragments/DatePickerSingle.tsx:20— DatePickerSingle.DatePickerSingle has cognitive complexity 40 (threshold 15). Drivers by points: if/else 17 (20 pts), ternaries 10 (11 pts), boolean chains 9 (nesting depth added 4). Of this number, 16 points are the body's own statements and 24 belong to 8 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.
dependencies_ts.getCallbacksByInput (cognitive 39) dash/dash-renderer/src/actions/dependencies_ts.ts:45— dependencies_ts.getCallbacksByInput has cognitive complexity 39 (threshold 15). Drivers by points: if/else 13 (33 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 22). Of this number, 25 points are the body's own statements and 14 belong to 3 function literals inside it that branch. 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.
_callback._prepare_response (cognitive 37) dash/_callback.py:780— _callback._prepare_response has cognitive complexity 37 (threshold 15). Drivers by points: if/else 13 (25 pts), ternaries 2 (6 pts), loops 2 (5 pts), boolean chains 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.
extract-meta.gatherComponents::getPropType (cognitive 37) dash/extract-meta.js:352— extract-meta.gatherComponents::getPropType has cognitive complexity 37 (threshold 15). Drivers by points: if/else 16 (28 pts), boolean chains 9 (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.
RRunner.start (cognitive 34) dash/testing/application_runners.py:413— RRunner.start has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 2 (6 pts), error handling 2 (3 pts), ternaries 2 (3 pts), boolean chains 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (JuliaRunner.start) 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.
JuliaRunner.start (cognitive 34) dash/testing/application_runners.py:511— JuliaRunner.start has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 2 (6 pts), error handling 2 (3 pts), ternaries 2 (3 pts), boolean chains 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (RRunner.start) 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.
componentDidUpdate (cognitive 34) dash/dash-renderer/src/components/core/Reloader.react.js:61— componentDidUpdate has cognitive complexity 34 (threshold 15). Drivers by points: if/else 11 (22 pts), loops 2 (8 pts), boolean chains 4 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Component.__init__ (cognitive 33) dash/development/base_component.py:158— Component.__init__ has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (22 pts), loops 2 (5 pts), boolean chains 2, error handling 1 (2 pts), ternaries 1 (2 pts) (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.
Calendar.CalendarComponent (cognitive 33) components/dash-core-components/src/utils/calendar/Calendar.tsx:57— Calendar.CalendarComponent has cognitive complexity 33 (threshold 15). Drivers by points: if/else 19, boolean chains 7, ternaries 6 (7 pts) (nesting depth added 1). Most of this is not in the body itself: 3 of the 33 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 201, 153, 137, …). 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.
partialIdMatch (cognitive 33) dash/dash-renderer/src/actions/dependencies.js:1182— partialIdMatch has cognitive complexity 33 (threshold 15). Drivers by points: if/else 7 (20 pts), ternaries 2 (10 pts), boolean chains 2, loops 1 (nesting depth added 21). 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.
ControlledTable.switchCell (cognitive 32) components/dash-table/src/dash-table/components/ControlledTable/index.tsx:616— ControlledTable.switchCell has cognitive complexity 32 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 9, ternaries 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, 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.
CallbackGraphContainer.react.CallbackGraph (cognitive 32) REDACTED:199— CallbackGraphContainer.react.CallbackGraph has cognitive complexity 32 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 6 (8 pts), boolean chains 6, loops 1 (4 pts), match/switch 1 (2 pts) (nesting depth added 11). Of this number, 21 points are the body's own statements and 11 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.
_LocalSubscription._client_poll (cognitive 30) REDACTED:289— _LocalSubscription._client_poll has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (20 pts), error handling 3 (9 pts), 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.
Resources._filter_resources (cognitive 30) dash/resources.py:49— Resources._filter_resources has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 6, ternaries 1 (3 pts), loops 1 (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.
StreamClient.readLoop (cognitive 30) dash/dash-renderer/src/utils/streamClient.ts:419— StreamClient.readLoop has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 6, error handling 1 (2 pts), loops 1 (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.
callback_adapter._derive_output_ids (cognitive 29) dash/mcp/primitives/tools/callback_adapter.py:433— callback_adapter._derive_output_ids has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (23 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Upload.getDataTransferItems (cognitive 29) components/dash-core-components/src/fragments/Upload.react.js:98— Upload.getDataTransferItems has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 4, loops 2 (4 pts), ternaries 1 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Dash.__init__ (cognitive 28) dash/dash.py:515— Dash.__init__ has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 10, ternaries 3, loops 1 (2 pts) (nesting depth added 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.
date.normalizeDate (cognitive 28) components/dash-table/src/dash-table/type/date.ts:20— date.normalizeDate has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 6 (16 pts), boolean chains 8, if/else 4 (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.
WorkerClient.handleMessage (cognitive 28) dash/dash-renderer/src/utils/workerClient.ts:287— WorkerClient.handleMessage has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (23 pts), boolean chains 2, loops 1 (2 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.
JupyterDash.run_app (cognitive 27) dash/_jupyter.py:295— JupyterDash.run_app has cognitive complexity 27 (threshold 15). Drivers by points: if/else 20 (25 pts), error handling 2 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
callbacks.handleWebsocketCallback (cognitive 27) dash/dash-renderer/src/actions/callbacks.ts:938— callbacks.handleWebsocketCallback has cognitive complexity 27 (threshold 15). Drivers by points: if/else 16 (21 pts), boolean chains 5, error handling 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
idMatch (cognitive 27) dash/dash-renderer/src/actions/dependencies.js:1121— idMatch has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (14 pts), ternaries 2 (10 pts), boolean chains 2, loops 1 (nesting depth added 17). 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.
content.getter (cognitive 26) components/dash-table/src/dash-table/derived/header/content.tsx:197— content.getter has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 10 (15 pts), boolean chains 6, if/else 4 (5 pts) (nesting depth added 6). None of this is in the body itself: all 26 points belong to 2 function literals inside it that branch (lines 222, 408). 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.
TableClipboardHelper.parse (cognitive 26) components/dash-table/src/dash-table/utils/TableClipboardHelper.ts:115— TableClipboardHelper.parse has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
paths.computePaths (cognitive 26) dash/dash-renderer/src/actions/paths.js:36— paths.computePaths has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 6, ternaries 2 (nesting depth added 7). Most of this is not in the body itself: 5 of the 26 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 82, editMap, a function literal at line 67, …). 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.
BuildProcess.bundles (cognitive 24) dash/development/build_process.py:110— BuildProcess.bundles has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (4 pts), ternaries 2 (3 pts), error handling 1 (2 pts), boolean chains 1 (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.
_callback._handle_rest_background_callback (cognitive 23) dash/_callback.py:721— _callback._handle_rest_background_callback has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 6, ternaries 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_LocalSubscription._aclient_poll (cognitive 23) REDACTED:381— _LocalSubscription._aclient_poll has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (17 pts), error handling 2 (5 pts), loops 1 (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.
Location.updateLocation (cognitive 23) components/dash-core-components/src/components/Location.react.js:18— Location.updateLocation has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 4, ternaries 2 (4 pts) (nesting depth added 7). Of this number, 12 points are the body's own statements and 11 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.
dependencies_ts.resolvePartialDeps.<returned closure>.<returned closure> (cognitive 23) dash/dash-renderer/src/actions/dependencies_ts.ts:606— dependencies_ts.resolvePartialDeps.<returned closure>.<returned closure> has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 5 (12 pts), if/else 6 (10 pts), loops 1 (nesting depth added 11). Of this number, 13 points are the body's own statements and 10 belong to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dependencies.getUnfilteredLayoutCallbacks::handleOneId (cognitive 23) dash/dash-renderer/src/actions/dependencies.js:1618— dependencies.getUnfilteredLayoutCallbacks::handleOneId has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (4 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
exceptions.propTypeErrorHandler (cognitive 23) dash/dash-renderer/src/exceptions.js:3— exceptions.propTypeErrorHandler has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (22 pts), boolean chains 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.
api.apiThunk.<returned closure> (cognitive 23) dash/dash-renderer/src/actions/api.js:34— api.apiThunk.<returned closure> has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (17 pts), error handling 2 (3 pts), boolean chains 2, loops 1 (nesting depth added 11). Of this number, 22 points are the body's own statements and 1 belongs to one function item 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.
UnconnectedContainer (cognitive 23) REDACTED:31— UnconnectedContainer has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (14 pts), ternaries 3 (5 pts), boolean chains 4 (nesting depth added 4). Of this number, 18 points are the body's own statements and 5 belong to 4 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.
apiThunk (cognitive 23) dash/dash-renderer/src/actions/api.js:33— apiThunk has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (17 pts), error handling 2 (3 pts), boolean chains 2, loops 1 (nesting depth added 11). None of this is in the body itself: all 23 points belong to 3 function items inside it that branch (a function literal at line 34, (anonymous)::setConnectionStatus, a function literal at line 112). 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.
triggerDefaultState (cognitive 23) dash/dash-renderer/src/actions/index.js:92— triggerDefaultState has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 2 (7 pts), boolean chains 3, error handling 1 (nesting depth added 9). Most of this is not in the body itself: 2 of the 23 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 120, 142, 153). 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.
Dash._setup_server (cognitive 22) dash/dash.py:1876— Dash._setup_server has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (11 pts), loops 5 (8 pts), boolean chains 2, ternaries 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.
ComponentPropsDescription.describe (cognitive 22) dash/mcp/primitives/tools/input_schemas/input_descriptions/description_component_props.py:34— ComponentPropsDescription.describe has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 2 (4 pts), boolean chains 3, loops 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.
text.dedentText (cognitive 22) components/dash-core-components/src/utils/markdown/text.ts:36— text.dedentText has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (5 pts), ternaries 2, boolean chains 1 (nesting depth added 12). Of this number, 21 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.
_stream_hub.apump_to_storage (cognitive 21) dash/_stream_hub.py:472— _stream_hub.apump_to_storage has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (13 pts), error handling 3 (4 pts), loops 2 (3 pts), boolean chains 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.
_utils.format_traceback_html (cognitive 21) dash/backends/_utils.py:5— _utils.format_traceback_html has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 3, loops 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.
Dash._config (cognitive 21) dash/dash.py:1189— Dash._config has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (15 pts), error handling 1 (3 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Dash._walk_assets_directory (cognitive 21) dash/dash.py:2004— Dash._walk_assets_directory has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (13 pts), ternaries 2 (5 pts), loops 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CallbackAdapter.inputs (cognitive 21) dash/mcp/primitives/tools/callback_adapter.py:239— CallbackAdapter.inputs has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (5 pts), ternaries 1 (2 pts), boolean chains 1 (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.
dependencies.getWatchedKeys (cognitive 21) dash/dash-renderer/src/actions/dependencies.js:1480— dependencies.getWatchedKeys has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 3, ternaries 1 (2 pts), loops 1 (nesting depth added 6). Most of this is not in the body itself: 7 of the 21 points are its own statements and the rest belongs to one function literal inside it that branches (line 1499). 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.
checkPropTypes.checkPropTypes (cognitive 21) dash/dash-renderer/src/checkPropTypes.js:19— checkPropTypes.checkPropTypes has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 5, error handling 1 (3 pts), loops 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.
APIController.react.storeEffect (cognitive 21) REDACTED:137— APIController.react.storeEffect has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 4, error handling 1 (2 pts) (nesting depth added 7). None of this is in the body itself: all 21 points belong to one function literal inside it that branches (line 150). 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.
bindEvents (cognitive 21) components/dash-core-components/src/fragments/Graph.react.js:425— bindEvents has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 7, loops 1 (2 pts) (nesting depth added 4). None of this is in the body itself: all 21 points belong to 8 function literals inside it that branch (lines 469, 454, 460, …). 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.
_pages._page_meta_tags (cognitive 20) dash/_pages.py:403— _pages._page_meta_tags has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 6, ternaries 2 (6 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
optionRendering.OptionsList (cognitive 20) components/dash-core-components/src/utils/optionRendering.tsx:212— optionRendering.OptionsList has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 322, 252, 271, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
dependencies.validateArg (cognitive 20) dash/dash-renderer/src/actions/dependencies.js:322— dependencies.validateArg has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 2 (nesting depth added 7). 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, 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.
component_generator.generate_components (cognitive 19) dash/development/component_generator.py:40— component_generator.generate_components has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WebSocketManager.handleMessage (cognitive 19) @plotly/dash-websocket-worker/src/WebSocketManager.ts:211— WebSocketManager.handleMessage has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 1 (2 pts), error handling 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.
Tabs.Tabs (cognitive 19) components/dash-core-components/src/components/Tabs.tsx:99— Tabs.Tabs has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13, boolean chains 4, ternaries 2. Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 8 function items inside it that branch (valueOrDefault, a function literal at line 255, a function literal at line 118, …). 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.
react-shim.jsx (cognitive 19) dash/dash-renderer/src/react-shim.js:73— react-shim.jsx has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 19) dash/dash-renderer/src/react-shim.js:32— (anonymous) has cognitive complexity 19 (threshold 15). Drivers by points: loops 5 (11 pts), if/else 5, boolean chains 3 (nesting depth added 6). 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.
DiskcacheSharedStorage._poll (cognitive 18) dash/_shared_storage/diskcache.py:151— DiskcacheSharedStorage._poll has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (4 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.
Dash._on_assets_change (cognitive 18) dash/dash.py:2514— Dash._on_assets_change has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 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.
_jl_components_generation.filter_props (cognitive 18) dash/development/_jl_components_generation.py:184— _jl_components_generation.filter_props has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 2, loops 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.
CallbackAdapter._dep_param_map (cognitive 18) dash/mcp/primitives/tools/callback_adapter.py:311— CallbackAdapter._dep_param_map has cognitive complexity 18 (threshold 15). Drivers by points: loops 3 (7 pts), if/else 4 (6 pts), ternaries 1 (5 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.
Loading.Loading (cognitive 18) components/dash-core-components/src/components/Loading.tsx:82— Loading.Loading has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 5, ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 119, 112). 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.
ControlledTable.handleKeyDown (cognitive 18) components/dash-table/src/dash-table/components/ControlledTable/index.tsx:556— ControlledTable.handleKeyDown has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 6 (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.
ControlledTable.render (cognitive 18) components/dash-table/src/dash-table/components/ControlledTable/index.tsx:954— ControlledTable.render has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 17, boolean chains 1. 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: 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.
index.getSingleColumnMap (cognitive 18) components/dash-table/src/dash-table/syntax-tree/index.ts:25— index.getSingleColumnMap has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 5). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 40). 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.
_pages._infer_image (cognitive 17) dash/_pages.py:23— _pages._infer_image has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 1, 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.
_pages._import_layouts_from_pages (cognitive 17) dash/_pages.py:446— _pages._import_layouts_from_pages has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (11 pts), boolean chains 3, loops 2 (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.
_streaming._akeepalive_frames (cognitive 17) dash/_streaming.py:204— _streaming._akeepalive_frames has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 2 (3 pts), boolean chains 2, error handling 1 (2 pts), ternaries 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.
DashDependency._id_matches (cognitive 17) dash/dependencies.py:91— DashDependency._id_matches has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 5, ternaries 2, loops 1 (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.
update_components.build_components (cognitive 17) dash/development/update_components.py:72— update_components.build_components has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), error handling 1 (3 pts), ternaries 2 (3 pts), boolean chains 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ControlledTable.renderMenu (cognitive 17) components/dash-table/src/dash-table/components/ControlledTable/index.tsx:1137— ControlledTable.renderMenu has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (11 pts), boolean chains 5, if/else 1 (nesting depth added 6). 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 1176, 1161, 1232). 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.
dependencies.idValSort (cognitive 17) dash/dash-renderer/src/actions/dependencies.js:136— dependencies.idValSort has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (12 pts), if/else 4 (5 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.
callbacks.handleServerside::fetchCallback (cognitive 17) dash/dash-renderer/src/actions/callbacks.ts:610— callbacks.handleServerside::fetchCallback has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), loops 2 (4 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
getGroupedColumnIndices (cognitive 17) components/dash-table/src/dash-table/utils/actions.js:4— getGroupedColumnIndices has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FastAPIResponseAdapter.set_response (cognitive 16) dash/backends/_fastapi.py:112— FastAPIResponseAdapter.set_response has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), loops 3 (8 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaseBackgroundCallbackManager.build_cache_key (cognitive 16) dash/background_callback/managers/__init__.py:73— BaseBackgroundCallbackManager.build_cache_key has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 1 (2 pts), error handling 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.
MessageRouter.handleBatchedMessages (cognitive 16) @plotly/dash-websocket-worker/src/MessageRouter.ts:112— MessageRouter.handleBatchedMessages has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3, error handling 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.
navigation.selectionCycle (cognitive 16) components/dash-table/src/dash-table/utils/navigation.ts:16— navigation.selectionCycle has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (16 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
dependencies.validateCallbacksToLayout::validateMap (cognitive 16) dash/dash-renderer/src/actions/dependencies.js:647— dependencies.validateCallbacksToLayout::validateMap has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Near-duplicate member pair (94 shared lines) dash/backends/_fastapi.py:896— dash/backends/_fastapi.py:896-1089 | dash/backends/_quart.py:627-822 — These two members are variants of one another: 94 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) dash/testing/plugin.py:175— dash/testing/plugin.py:175-186 | dash/testing/plugin.py:191-203 | dash/testing/plugin.py:208-220 | dash/testing/plugin.py:225-237 | dash/testing/plugin.py:242-254 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) dash/backends/_fastapi.py:699— dash/backends/_fastapi.py:699-787 | dash/backends/_flask.py:277-439 | dash/backends/_quart.py:420-522 | dash/mcp/primitives/tools/callback_utils.py:20-41 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (89 corresponding lines) · ×1
Edited copy of a member (89 corresponding lines) dash/testing/application_runners.py:414— dash/testing/application_runners.py:414-502 | dash/testing/application_runners.py:512-602 — These two members are one piece of code written twice and then edited apart: 89 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (104 corresponding lines) · ×1
Edited copy of a member (104 corresponding lines) dash/background_callback/managers/celery_manager.py:152— dash/background_callback/managers/celery_manager.py:152-276 | dash/background_callback/managers/diskcache_manager.py:228-331 — These two members are one piece of code written twice and then edited apart: 104 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) REDACTED:290— REDACTED:290-328 | REDACTED:382-416 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) dash/dependencies.py:347— dash/dependencies.py:347-377 | dash/dependencies.py:396-423 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) dash/backends/_flask.py:129— dash/backends/_flask.py:129-159 | dash/dash.py:188-241 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (33 corresponding lines) · ×1
Edited copy of a member (33 corresponding lines) dash/backends/_flask.py:470— dash/backends/_flask.py:470-502 | dash/backends/_quart.py:527-563 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) dash/backends/_flask.py:443— dash/backends/_flask.py:443-465 | dash/backends/_quart.py:178-207 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (39 corresponding lines) · ×1
Edited copy of a member (39 corresponding lines) dash/backends/ws.py:679— dash/backends/ws.py:679-730 | dash/backends/ws.py:740-778 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) dash/backends/ws.py:240— dash/backends/ws.py:240-258 | dash/backends/ws.py:263-284 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) dash/backends/ws.py:604— dash/backends/ws.py:604-626 | dash/backends/ws.py:634-647 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×1
Edited copy of a member (10 corresponding lines) REDACTED:277— REDACTED:277-287 | REDACTED:370-379 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×1
Edited copy of a member (11 corresponding lines) REDACTED:354— REDACTED:354-364 | REDACTED:419-430 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) dash/testing/wait.py:63— dash/testing/wait.py:63-71 | dash/testing/wait.py:109-117 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×1
Edited copy of a member (6 corresponding lines) dash/mcp/primitives/tools/input_schemas/input_descriptions/description_pattern_matching.py:56— dash/mcp/primitives/tools/input_schemas/input_descriptions/description_pattern_matching.py:56-61 | dash/mcp/primitives/tools/input_schemas/schema_pattern_matching.py:59-64 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×1
Edited copy of a member (3 corresponding lines) dash/_shared_storage/_polling.py:53— dash/_shared_storage/_polling.py:53-55 | REDACTED:334-336 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (54–56 lines × 2) dash/testing/application_runners.py:428— dash/testing/application_runners.py:428-481 | dash/testing/application_runners.py:527-582 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `dash/testing/application_runners.py:428` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `dash/testing/application_runners.py:526` calls `isinstance` and `dash/testing/application_runners.py:427` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (53 lines × 2) dash/backends/_fastapi.py:991— dash/backends/_fastapi.py:991-1043 | dash/backends/_quart.py:723-775 — before extracting anything, compare `dash/backends/_fastapi.py` and `dash/backends/_quart.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 175 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `dash/backends/_fastapi.py:991` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (43–44 lines × 2) dash/_callback.py:951— dash/_callback.py:951-994 | dash/_callback.py:1033-1075 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (27–30 lines × 2) dash/backends/_fastapi.py:746— dash/backends/_fastapi.py:746-775 | dash/backends/_quart.py:475-501 — before extracting anything, compare `dash/backends/_fastapi.py` and `dash/backends/_quart.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 175 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (21–25 lines × 2) dash/background_callback/managers/celery_manager.py:219— dash/background_callback/managers/celery_manager.py:219-243 | dash/background_callback/managers/diskcache_manager.py:281-301 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `dash/background_callback/managers/celery_manager.py:219` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: `AttributeDict` names `..._utils` in one and `dash._utils` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (24 lines × 2) dash/background_callback/managers/celery_manager.py:193— dash/background_callback/managers/celery_manager.py:193-216 | dash/background_callback/managers/celery_manager.py:239-262 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `dash/background_callback/managers/celery_manager.py:263` calls `iscoroutine` and `dash/background_callback/managers/celery_manager.py:217` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (23 lines × 2) dash/backends/_fastapi.py:871— dash/backends/_fastapi.py:871-893 | dash/backends/_quart.py:586-608 — before extracting anything, compare `dash/backends/_fastapi.py` and `dash/backends/_quart.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 175 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19–23 lines × 2) dash/background_callback/managers/celery_manager.py:175— dash/background_callback/managers/celery_manager.py:175-197 | dash/background_callback/managers/diskcache_manager.py:244-262 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `dash/background_callback/managers/celery_manager.py:175` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: `AttributeDict` names `..._utils` in one and `dash._utils` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (22 lines × 2) dash/backends/_fastapi.py:953— dash/backends/_fastapi.py:953-974 | dash/backends/_quart.py:678-699 — before extracting anything, compare `dash/backends/_fastapi.py` and `dash/backends/_quart.py` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 175 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `dash/backends/_fastapi.py:953` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20–21 lines × 2) dash/dash.py:2869— dash/dash.py:2869-2888 | dash/dash.py:2958-2978 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) dash/development/update_components.py:47— dash/development/update_components.py:47-64 | dash/development/update_components.py:83-100 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15–16 lines × 2) dash/backends/_flask.py:371— dash/backends/_flask.py:371-386 | dash/backends/_flask.py:402-416 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `dash/backends/_flask.py:418` calls `iscoroutine` and `dash/backends/_flask.py:388` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6–14 lines × 5) dash/backends/_fastapi.py:746— dash/backends/_fastapi.py:746-759 | dash/backends/_flask.py:380-387 | dash/backends/_flask.py:410-417 | dash/backends/_quart.py:475-485 | dash/mcp/primitives/tools/callback_utils.py:30-35 — there are 5 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `dash/backends/_flask.py:418` calls `iscoroutine` and `dash/backends/_flask.py:388` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9–11 lines × 2) dash/backends/ws.py:720— dash/backends/ws.py:720-728 | dash/backends/ws.py:768-778 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `dash/backends/ws.py:768` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 5) dash/testing/plugin.py:177— dash/testing/plugin.py:177-186 | dash/testing/plugin.py:194-203 | dash/testing/plugin.py:211-220 | dash/testing/plugin.py:228-237 | dash/testing/plugin.py:245-254 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `dash/testing/plugin.py:177` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) dash/dependencies.py:347— dash/dependencies.py:347-356 | dash/dependencies.py:396-405 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 3) dash/backends/_fastapi.py:651— dash/backends/_fastapi.py:651-658 | dash/backends/_flask.py:226-233 | dash/backends/_quart.py:366-373 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `dash/backends/_fastapi.py:651` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) dash/backends/_fastapi.py:859— dash/backends/_fastapi.py:859-864 | dash/backends/_flask.py:455-460 | dash/backends/_quart.py:196-201 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (6 lines × 2) dash/testing/wait.py:74— dash/testing/wait.py:74-79 | dash/testing/wait.py:120-125 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (5 lines × 2) dash/_shared_storage/_persistence.py:56— dash/_shared_storage/_persistence.py:56-60 | REDACTED:73-77 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
IC1 · Incompleteness & stubs· Markup wires an event to an empty handler · ×1
Markup wires an event to an empty handler components/dash-core-components/src/utils/optionRendering.tsx:345— `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.
Duplicated block (44 lines × 2 locations) components/dash-core-components/src/components/DatePickerRange.tsx:17— components/dash-core-components/src/components/DatePickerRange.tsx:17 · components/dash-core-components/src/components/DatePickerSingle.tsx:20 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (35 lines × 2 locations) components/dash-core-components/src/fragments/DatePickerRange.tsx:433— components/dash-core-components/src/fragments/DatePickerRange.tsx:433 · components/dash-core-components/src/fragments/DatePickerSingle.tsx:209 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (34 lines × 2 locations) components/dash-table/src/dash-table/components/EdgeFactory.tsx:67— components/dash-table/src/dash-table/components/EdgeFactory.tsx:67 · components/dash-table/src/dash-table/components/EdgeFactory.tsx:102 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (33 lines × 2 locations) components/dash-table/src/dash-table/syntax-tree/lexicon/column.ts:33— components/dash-table/src/dash-table/syntax-tree/lexicon/column.ts:33 · components/dash-table/src/dash-table/syntax-tree/lexicon/columnMulti.ts:47 — 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.
Duplicated block (32 lines × 2 locations) components/dash-table/src/dash-table/syntax-tree/lexicon/columnMulti.ts:43— components/dash-table/src/dash-table/syntax-tree/lexicon/columnMulti.ts:43 · components/dash-table/src/dash-table/syntax-tree/lexicon/query.ts:69 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (28 lines × 2 locations) dash/dash-renderer/src/actions/dependencies_ts.ts:74— dash/dash-renderer/src/actions/dependencies_ts.ts:74 · dash/dash-renderer/src/actions/dependencies_ts.ts:135 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (27 lines × 2 locations) dash/dash-renderer/src/actions/dependencies.js:1146— dash/dash-renderer/src/actions/dependencies.js:1146 · dash/dash-renderer/src/actions/dependencies.js:1213 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (26 matched lines × 2 locations) · ×1
Duplicated block with local edits (26 matched lines × 2 locations) dash/dash-renderer/src/actions/api.js:74— dash/dash-renderer/src/actions/api.js:74 · dash/dash-renderer/src/actions/callbacks.ts:1403 — the two spans are one implementation copied and then locally edited — 96 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 (21 lines × 4 locations) components/dash-core-components/src/fragments/Loading/spinners/CircleSpinner.tsx:8— components/dash-core-components/src/fragments/Loading/spinners/CircleSpinner.tsx:8 · components/dash-core-components/src/fragments/Loading/spinners/CubeSpinner.tsx:5 · components/dash-core-components/src/fragments/Loading/spinners/DefaultSpinner.tsx:8 · components/dash-core-components/src/fragments/Loading/spinners/DotSpinner.tsx:8 — the 4 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (21 lines × 2 locations) dash/dash-renderer/src/actions/callbacks.ts:1011— dash/dash-renderer/src/actions/callbacks.ts:1011 · dash/dash-renderer/src/actions/callbacks.ts:1057 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (18 matched lines × 2 locations) · ×1
Duplicated block with local edits (18 matched lines × 2 locations) components/dash-table/src/dash-table/components/CellFactory.tsx:200— components/dash-table/src/dash-table/components/CellFactory.tsx:200 · components/dash-table/src/dash-table/components/HeaderFactory.tsx:160 — the two spans are one implementation copied and then locally edited — 128 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 (17 lines × 3 locations) components/dash-table/src/dash-table/dash/DataTable.js:1276— components/dash-table/src/dash-table/dash/DataTable.js:1276 · components/dash-table/src/dash-table/dash/DataTable.js:1305 · components/dash-table/src/dash-table/dash/DataTable.js:1327 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (16 lines × 5 locations) components/dash-core-components/src/fragments/Loading/spinners/CircleSpinner.tsx:10— components/dash-core-components/src/fragments/Loading/spinners/CircleSpinner.tsx:10 · components/dash-core-components/src/fragments/Loading/spinners/CubeSpinner.tsx:7 · components/dash-core-components/src/fragments/Loading/spinners/DefaultSpinner.tsx:10 · components/dash-core-components/src/fragments/Loading/spinners/DotSpinner.tsx:10 · +1 more site(s) not listed — the 5 copies are spread across 5 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (14 matched lines × 2 locations) · ×1
Duplicated block with local edits (14 matched lines × 2 locations) components/dash-table/src/core/browser/DOM.ts:4— components/dash-table/src/core/browser/DOM.ts:4 · components/dash-table/src/core/browser/DOM.ts:24 — the two spans are one implementation copied and then locally edited — 55 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (14 lines × 4 locations) components/dash-table/src/dash-table/dash/DataTable.js:1257— components/dash-table/src/dash-table/dash/DataTable.js:1257 · components/dash-table/src/dash-table/dash/DataTable.js:1278 · components/dash-table/src/dash-table/dash/DataTable.js:1307 · components/dash-table/src/dash-table/dash/DataTable.js:1329 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Boundary violation [package:third-party-deep-import] dash/dash-renderer/src/checkPropTypes.js:7— dash/dash-renderer/src/checkPropTypes.js:7 imports prop-types/lib/ReactPropTypesSecret, 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.
Complex function (anonymous) (cyclomatic 43, cognitive 42) components/dash-table/tests/visual/percy-storybook/Style.percy.tsx:41— (anonymous) has cyclomatic complexity 43 and cognitive complexity 42; 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 37) components/dash-table/tests/js-unit/dash_table_queries_test.ts:436— (anonymous) has cyclomatic complexity 38 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 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 32, cognitive 31) components/dash-table/tests/js-unit/dash_table_queries_test.ts:52— (anonymous) 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 (anonymous) (cyclomatic 30, cognitive 64) dash/dash-renderer/src/actions/callbacks.ts:1208— (anonymous) has cyclomatic complexity 30 and cognitive complexity 64; 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 switchCell (cyclomatic 28, cognitive 32) components/dash-table/src/dash-table/components/ControlledTable/index.tsx:616— switchCell has cyclomatic complexity 28 and cognitive complexity 32; 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 Dropdown (cyclomatic 26, cognitive 21) components/dash-core-components/src/fragments/Dropdown.tsx:28— Dropdown has cyclomatic complexity 26 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 25, cognitive 28) dash/extract-meta.js:731— (anonymous) has cyclomatic complexity 25 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 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 setHydratedProps (cyclomatic 24, cognitive 91) dash/dash-renderer/src/wrapper/DashWrapper.tsx:284— setHydratedProps has cyclomatic complexity 24 and cognitive complexity 91; 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 filterEventData (cyclomatic 23, cognitive 42) components/dash-core-components/src/fragments/Graph.react.js:58— filterEventData has cyclomatic complexity 23 and cognitive complexity 42; 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 getPropType (cyclomatic 22, cognitive 37) dash/extract-meta.js:352— getPropType has cyclomatic complexity 22 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 readLoop (cyclomatic 22, cognitive 33) dash/dash-renderer/src/utils/streamClient.ts:419— readLoop has cyclomatic complexity 22 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleMessage (cyclomatic 22, cognitive 28) dash/dash-renderer/src/utils/workerClient.ts:287— handleMessage has cyclomatic complexity 22 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 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 handleWebsocketCallback (cyclomatic 22, cognitive 27) dash/dash-renderer/src/actions/callbacks.ts:938— handleWebsocketCallback has cyclomatic complexity 22 and cognitive complexity 27; 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 DatePickerRange (cyclomatic 22, cognitive 19) components/dash-core-components/src/fragments/DatePickerRange.tsx:26— DatePickerRange has cyclomatic complexity 22 and cognitive complexity 19; 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 21, cognitive 23) components/dash-table/src/dash-table/derived/header/content.tsx:222— (anonymous) has cyclomatic complexity 21 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function normalizeDate (cyclomatic 21, cognitive 19) components/dash-table/src/dash-table/type/date.ts:20— normalizeDate has cyclomatic complexity 21 and cognitive complexity 19; 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 DatePickerSingle (cyclomatic 21, cognitive 18) components/dash-core-components/src/fragments/DatePickerSingle.tsx:20— DatePickerSingle has cyclomatic complexity 21 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getCallbackByOutput (cyclomatic 20, cognitive 53) dash/dash-renderer/src/actions/dependencies.js:1296— getCallbackByOutput has cyclomatic complexity 20 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 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 observer (cyclomatic 20, cognitive 19) dash/dash-renderer/src/observers/requestedCallbacks.ts:58— observer has cyclomatic complexity 20 and cognitive complexity 19; 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 19, cognitive 18) components/dash-core-components/src/fragments/Dropdown.tsx:312— (anonymous) has cyclomatic complexity 19 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 19, cognitive 16) components/dash-core-components/src/fragments/RangeSlider.tsx:274— (anonymous) has cyclomatic complexity 19 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 18, cognitive 22) components/dash-core-components/src/fragments/DatePickerRange.tsx:317— (anonymous) has cyclomatic complexity 18 and cognitive complexity 22; 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 18, cognitive 21) REDACTED:150— (anonymous) has cyclomatic complexity 18 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleKeyDown (cyclomatic 18, cognitive 18) components/dash-table/src/dash-table/components/ControlledTable/index.tsx:556— handleKeyDown has cyclomatic complexity 18 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 18, cognitive 13) components/dash-table/src/dash-table/components/Table/derivedPropsHelper.ts:36— (anonymous) has cyclomatic complexity 18 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 18, cognitive 12) components/dash-core-components/src/utils/calendar/CalendarMonth.tsx:107— (anonymous) has cyclomatic complexity 18 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getDataTransferItems (cyclomatic 17, cognitive 29) components/dash-core-components/src/fragments/Upload.react.js:98— getDataTransferItems has cyclomatic complexity 17 and cognitive complexity 29; 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 17, cognitive 16) components/dash-table/tests/js-unit/dash_table_queries_test.ts:286— (anonymous) has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 handleResize (cyclomatic 17, cognitive 14) components/dash-table/src/dash-table/components/ControlledTable/index.tsx:413— handleResize has cyclomatic complexity 17 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 componentDidUpdate (cyclomatic 16, cognitive 34) dash/dash-renderer/src/components/core/Reloader.react.js:61— componentDidUpdate has cyclomatic complexity 16 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getGroupedColumnIndices (cyclomatic 16, cognitive 17) components/dash-table/src/dash-table/utils/actions.js:4— getGroupedColumnIndices has cyclomatic complexity 16 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 15, cognitive 42) dash/dash-renderer/src/actions/dependencies.js:1688— (anonymous) has cyclomatic complexity 15 and cognitive complexity 42; 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 15, cognitive 13) components/dash-core-components/src/fragments/DatePickerRange.tsx:148— (anonymous) has cyclomatic complexity 15 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function parse (cyclomatic 14, cognitive 26) components/dash-table/src/dash-table/utils/TableClipboardHelper.ts:115— parse has cyclomatic complexity 14 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 14, cognitive 19) dash/dash-renderer/src/react-shim.js:32— (anonymous) has cyclomatic complexity 14 and cognitive complexity 19; 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 fetchCallback (cyclomatic 14, cognitive 17) dash/dash-renderer/src/actions/callbacks.ts:610— fetchCallback has cyclomatic complexity 14 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function partialIdMatch (cyclomatic 13, cognitive 33) dash/dash-renderer/src/actions/dependencies.js:1182— partialIdMatch has cyclomatic complexity 13 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleOneId (cyclomatic 13, cognitive 23) dash/dash-renderer/src/actions/dependencies.js:1618— handleOneId has cyclomatic complexity 13 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 13, cognitive 22) components/dash-table/src/core/syntax-tree/lexer.ts:27— (anonymous) has cyclomatic complexity 13 and cognitive complexity 22; 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 handleStreamedResponse (cyclomatic 13, cognitive 22) dash/dash-renderer/src/actions/callbacks.ts:763— handleStreamedResponse has cyclomatic complexity 13 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· dash/dash-renderer/src/actions/dependencies.js · ×1
dash/dash-renderer/src/actions/dependencies.js: 1652 lines of code dash/dash-renderer/src/actions/dependencies.js:1— dash/dash-renderer/src/actions/dependencies.js has 1652 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· components/dash-table/src/dash-table/dash/DataTable.js · ×1
components/dash-table/src/dash-table/dash/DataTable.js: 1447 lines of code components/dash-table/src/dash-table/dash/DataTable.js:1— components/dash-table/src/dash-table/dash/DataTable.js has 1447 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· components/dash-core-components/src/types.ts · ×1
components/dash-core-components/src/types.ts: 1419 lines of code components/dash-core-components/src/types.ts:1— components/dash-core-components/src/types.ts has 1419 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· dash/dash-renderer/src/actions/callbacks.ts · ×1
dash/dash-renderer/src/actions/callbacks.ts: 1341 lines of code dash/dash-renderer/src/actions/callbacks.ts:1— dash/dash-renderer/src/actions/callbacks.ts has 1341 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· components/dash-table/src/dash-table/components/ControlledTable/index.tsx · ×1
components/dash-table/src/dash-table/components/ControlledTable/index.tsx: 1116 lines of code components/dash-table/src/dash-table/components/ControlledTable/index.tsx:1— components/dash-table/src/dash-table/components/ControlledTable/index.tsx has 1116 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
dash/extract-meta.js: 772 lines of code dash/extract-meta.js:1— dash/extract-meta.js has 772 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· dash/dash-renderer/src/utils/streamClient.ts · ×1
dash/dash-renderer/src/utils/streamClient.ts: 714 lines of code dash/dash-renderer/src/utils/streamClient.ts:1— dash/dash-renderer/src/utils/streamClient.ts has 714 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· dash/dash-renderer/src/actions/dependencies_ts.ts · ×1
dash/dash-renderer/src/actions/dependencies_ts.ts: 634 lines of code dash/dash-renderer/src/actions/dependencies_ts.ts:1— dash/dash-renderer/src/actions/dependencies_ts.ts has 634 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· components/dash-core-components/src/fragments/Dropdown.tsx · ×1
components/dash-core-components/src/fragments/Dropdown.tsx: 618 lines of code components/dash-core-components/src/fragments/Dropdown.tsx:1— components/dash-core-components/src/fragments/Dropdown.tsx has 618 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· dash/dash-renderer/src/wrapper/DashWrapper.tsx · ×1
dash/dash-renderer/src/wrapper/DashWrapper.tsx: 561 lines of code dash/dash-renderer/src/wrapper/DashWrapper.tsx:1— dash/dash-renderer/src/wrapper/DashWrapper.tsx has 561 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· components/dash-core-components/src/fragments/Graph.react.js · ×1
components/dash-core-components/src/fragments/Graph.react.js: 552 lines of code components/dash-core-components/src/fragments/Graph.react.js:1— components/dash-core-components/src/fragments/Graph.react.js has 552 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· components/dash-core-components/src/components/Graph.react.js · ×1
components/dash-core-components/src/components/Graph.react.js: 512 lines of code components/dash-core-components/src/components/Graph.react.js:1— components/dash-core-components/src/components/Graph.react.js has 512 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· components/dash-table/src/dash-table/components/Table/props.ts · ×1
components/dash-table/src/dash-table/components/Table/props.ts: 505 lines of code components/dash-table/src/dash-table/components/Table/props.ts:1— components/dash-table/src/dash-table/components/Table/props.ts has 505 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· dash/dash-renderer/src/persistence.js · ×1
dash/dash-renderer/src/persistence.js: 495 lines of code dash/dash-renderer/src/persistence.js:1— dash/dash-renderer/src/persistence.js has 495 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· components/dash-core-components/src/fragments/DatePickerRange.tsx · ×1
components/dash-core-components/src/fragments/DatePickerRange.tsx: 482 lines of code components/dash-core-components/src/fragments/DatePickerRange.tsx:1— components/dash-core-components/src/fragments/DatePickerRange.tsx has 482 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· components/dash-core-components/src/fragments/RangeSlider.tsx · ×1
components/dash-core-components/src/fragments/RangeSlider.tsx: 454 lines of code components/dash-core-components/src/fragments/RangeSlider.tsx:1— components/dash-core-components/src/fragments/RangeSlider.tsx has 454 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· dash/dash-renderer/src/actions/patch.ts · ×1
dash/dash-renderer/src/actions/patch.ts: 451 lines of code dash/dash-renderer/src/actions/patch.ts:1— dash/dash-renderer/src/actions/patch.ts has 451 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: 431 lines of code REDACTED:1— REDACTED has 431 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· dash/dash-renderer/src/observers/executedCallbacks.ts · ×1
dash/dash-renderer/src/observers/executedCallbacks.ts: 422 lines of code dash/dash-renderer/src/observers/executedCallbacks.ts:1— dash/dash-renderer/src/observers/executedCallbacks.ts has 422 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· components/dash-table/src/dash-table/derived/header/content.tsx · ×1
components/dash-table/src/dash-table/derived/header/content.tsx: 420 lines of code components/dash-table/src/dash-table/derived/header/content.tsx:1— components/dash-table/src/dash-table/derived/header/content.tsx has 420 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· Type errors in this package cannot fail any build or CI step · ×1
Type errors in this package cannot fail any build or CI step components/dash-table/package.json:22— `components/dash-table` is TypeScript, but a type error in it cannot fail anything this repository runs: its `private::format.prettier` script (`prettier --config .prettierrc --write "{src,tests,demo}/**/*.{js,ts,tsx}"`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. Add a type check that can fail — a `typecheck` script running `tsc --noEmit` (or `vue-tsc`/`svelte-check`) that CI or the workspace pipeline runs, or a build step that checks before it bundles.
R6 · Tooling· This package's lint script runs in no CI job · ×1
This package's lint script runs in no CI job components/dash-html-components/package.json:19— The package in `components/dash-html-components` declares the lint script `lint` (`eslint src scripts`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `components/dash-html-components` (or the workspace's task runner).
Dead file (~332 LoC) components/dash-table/generator/cssPropertiesGenerator.js— no import path from any entry point (73 application, 40 tooling, 133 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 (~72 LoC) dash/dash-renderer/src/styles/styles.js— no import path from any entry point (73 application, 40 tooling, 133 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dash/dash-renderer/src/AccessDenied.react.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~51 LoC) dash/dash-renderer/src/AccessDenied.react.js— no import path from any entry point (73 application, 40 tooling, 133 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 (~47 LoC) @plotly/eslint-config-dash/typescript.js— no import path from any entry point (73 application, 40 tooling, 133 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 (~34 LoC) components/dash-table/src/dash-table/components/Filter/Advanced.tsx— no import path from any entry point (73 application, 40 tooling, 133 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 (~17 LoC) dash/dash-renderer/src/components/error/GlobalErrorContainerPassthrough.react.js— no import path from any entry point (73 application, 40 tooling, 133 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 (~11 LoC) components/dash-table/src/dash-table/derived/header/fixedHeaders.ts— no import path from any entry point (73 application, 40 tooling, 133 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 (~2 LoC) components/dash-core-components/src/utils/LazyLoader/slider.ts— no import path from any entry point (73 application, 40 tooling, 133 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
Unlisted import 'unified' components/dash-core-components/src/fragments/Markdown.tsx:3— Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json.
Unused dependency '@lerna/filter-options' package.json:51— 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.
Third-party script without Subresource Integrity components/dash-core-components/index.html:14— `//cdnjs.cloudflare.com/ajax/libs/codemirror/5.0.0/codemirror.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. 2 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 components/dash-table/src/core/objPropsToCamel.ts:17— `objPropsToCamel` is exported and takes `value: any` from its caller, and it calls itself at line 17 (`objPropsToCamel`) with a piece of `value` — and nowhere in `objPropsToCamel` 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 `objPropsToCamel` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Orphaned file components/dash-table/src/dash-table/derived/header/content.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 dash/development/_jl_components_generation.py: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 components/dash-table/src/dash-table/components/Table/props.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 dash/dash-renderer/src/observers/requestedCallbacks.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 components/dash-table/src/dash-table/components/EdgeFactory.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 components/dash-core-components/src/fragments/Loading/spinners/GraphSpinner.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 components/dash-table/src/dash-table/derived/style/IStyle.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 dash/testing/plugin.py: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 components/dash-core-components/src/fragments/Loading/spinners/CircleSpinner.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 dash/_grouping.py: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 components/dash-table/src/dash-table/derived/cell/contents.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 components/dash-table/src/dash-table/components/CellFactory.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 dash/development/build_process.py: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 components/dash-core-components/src/fragments/Loading/spinners/CubeSpinner.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 components/dash-table/src/dash-table/derived/style/cssProperties.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 components/dash-table/dash_table_base/Format.py: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 components/dash-table/src/dash-table/derived/edges/type.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 components/dash-table/src/dash-table/components/FilterFactory.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 components/dash-table/src/dash-table/handlers/cellEvents.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 components/dash-table/src/dash-table/derived/style/index.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 components/dash-table/src/dash-table/dash/Sanitizer.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 components/dash-table/src/dash-table/conditional/index.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 components/dash-table/src/dash-table/syntax-tree/lexeme/relational.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 components/dash-table/src/dash-table/components/Table/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 components/dash-table/src/dash-table/utils/TableClipboardHelper.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.
Deprecated: exenv-es6 REDACTED:1201— exenv-es6 1.1.1 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:1226— glob 7.1.6 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: inflight REDACTED:1248— inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @lerna/collect-updates REDACTED:884— @lerna/collect-updates 6.4.1 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @lerna/describe-ref REDACTED:902— @lerna/describe-ref 6.4.1 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @lerna/filter-packages REDACTED:934— @lerna/filter-packages 6.4.1 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @lerna/validation-error REDACTED:950— @lerna/validation-error 6.4.1 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:2134— glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: rimraf REDACTED:2156— rimraf 3.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: are-we-there-yet REDACTED:2862— are-we-there-yet 3.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: dommatrix REDACTED:3951— dommatrix 1.0.3 is resolved in REDACTED and is marked deprecated by its publisher: "dommatrix is no longer maintained. Please use @thednp/dommatrix.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: gauge REDACTED:4708— gauge 4.0.4 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: inflight REDACTED:5310— inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: lodash.clone REDACTED:6723— lodash.clone 4.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "This package is deprecated. Use structuredClone instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: lodash.isequal REDACTED:6788— lodash.isequal 4.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "This package is deprecated. Use require('node:util').isDeepStrictEqual instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: npmlog REDACTED:7711— npmlog 6.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/config-array REDACTED:2378— @humanwhocodes/config-array 0.13.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/config-array instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/object-schema REDACTED:2408— @humanwhocodes/object-schema 2.0.3 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/object-schema instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: rimraf REDACTED:5830— rimraf 3.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: core-js REDACTED:6185— core-js 2.6.12 is resolved in REDACTED and is marked deprecated by its publisher: "core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: rimraf REDACTED:7805— rimraf 3.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:8041— glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: inflight REDACTED:8683— inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: whatwg-encoding REDACTED:16334— whatwg-encoding 3.1.1 is resolved in REDACTED and is marked deprecated by its publisher: "Use @exodus/bytes instead for a more spec-conformant and faster implementation". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/config-array REDACTED:1860— @humanwhocodes/config-array 0.13.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/config-array instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
redundant comment @plotly/dash-jupyterlab/lib/index.js:68— "Create a new widget" repeats the code it sits on: 3 of its 3 words (create, new, widget) are already in `widget = new DashIFrameWidget(msgData.port, msgData.url);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment @plotly/dash-jupyterlab/src/index.ts:112— "Create a new widget" repeats the code it sits on: 3 of its 3 words (create, new, widget) are already in `widget = new DashIFrameWidget(msgData.port, msgData.url);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment @plotly/dash-websocket-worker/src/WebSocketManager.ts:299— "Check for inactivity timeout" repeats the code it sits on: 3 of its 3 words (check, inactivity, timeout) are already in `if (this.config.inactivityTimeout > 0)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment @plotly/dash-websocket-worker/src/worker.ts:16— "SharedWorker global scope" repeats the code it sits on: 4 of its 4 words (shared, worker, global, scope) are already in `declare const self: SharedWorkerGlobalScope;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment components/dash-core-components/src/fragments/RangeSlider.tsx:166— "Check if value is within min/max bounds" repeats the code it sits on: 4 of its 5 words (check, value, min, max) are already in `if (val < minMaxValues.min_mark || val > minMaxValues.max_mark)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment components/dash-core-components/src/fragments/RangeSlider.tsx:285— "Parse the input value" repeats the code it sits on: 3 of its 3 words (parse, input, value) are already in `const newMin = parseFloat(inputValue);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment components/dash-core-components/src/fragments/RangeSlider.tsx:355— "Parse the input value" repeats the code it sits on: 3 of its 3 words (parse, input, value) are already in `const newMax = parseFloat(inputValue);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment components/dash-core-components/src/fragments/Upload.react.js:56— "Check if file matches accept criteria" repeats the code it sits on: 4 of its 5 words (check, file, matches, accept) are already in `if (!this.fileMatchesAccept(file, accept))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment components/dash-core-components/src/utils/calendar/helpers.ts:174— "Check if date is outside min/max range" repeats the code it sits on: 5 of its 6 words (check, date, min, max, range) are already in `if (!isDateInRange(date, minDate, maxDate))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment components/dash-core-components/src/utils/calendar/helpers.ts:179— "Check if date is in the disabled dates array" repeats the code it sits on: 4 of its 5 words (check, date, disabled, dates) are already in `if (disabledDates)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment components/dash-table/src/dash-table/derived/table/fragments.tsx:99— "slice out fixed rows" repeats the code it sits on: 3 of its 3 words (slice, fixed, rows) are already in `const fixedRowCells = fixedRows ? cells.slice(0, fixedRows) : null;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment dash/dash-renderer/src/actions/dependencies_ts.ts:657— "Check if objKeys is a superset of idKeys" repeats the code it sits on: 4 of its 5 words (check, obj, keys, id) are already in `if (!idKeys.every((k: string) => objKeys.indexOf(k) !== -1))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment dash/dash-renderer/src/observers/requestedCallbacks.ts:344— "Get all inputs for `cb`" repeats the code it sits on: 3 of its 3 words (get, inputs, cb) are already in `const inputs = map(combineIdAndProp, flatten(cb.getInputs(paths)));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment dash/dash-renderer/src/observers/websocketObserver.ts:133— "Update the component props" repeats the code it sits on: 3 of its 3 words (update, component, props) are already in `store.dispatch(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment dash/dash-renderer/src/utils/workerClient.ts:111— "Create the SharedWorker" repeats the code it sits on: 3 of its 3 words (create, shared, worker) are already in `this.worker = new SharedWorker(workerUrl, {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment dash/dash-renderer/src/utils/workerClient.ts:119— "Create promise for connection" repeats the code it sits on: 3 of its 3 words (create, promise, connection) are already in `this.connectionPromise = new Promise(resolve =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Duplicated predicate components/dash-table/src/dash-table/components/CellLabel/index.tsx:42— `applyFocus && el && document.activeElement !== el` appears character-identically in 2 files — components/dash-table/src/dash-table/components/CellLabel/index.tsx, components/dash-table/src/dash-table/components/CellMarkdown/index.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 dash/dash-renderer/src/AppProvider.react.tsx:31— `config.websocket?.url && config.websocket?.worker_url` appears character-identically in 2 files — dash/dash-renderer/src/AppProvider.react.tsx, dash/dash-renderer/src/observers/websocketObserver.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 components/dash-table/src/dash-table/components/dropdownHelper.ts:23— `getComputedStyle(positionalParent).position !== 'relative' && getComputedStyle(positionalParent).position !== 'sticky'` appears character-identically in 2 files — components/dash-table/src/dash-table/components/dropdownHelper.ts, components/dash-table/src/dash-table/components/tooltipHelper.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 components/dash-core-components/src/components/RangeSlider.tsx:29— `typeof step === 'undefined' && Number.isInteger(props.min) && Number.isInteger(props.max)` appears character-identically in 2 files — components/dash-core-components/src/components/RangeSlider.tsx, components/dash-core-components/src/components/Slider.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 dash/backends/_fastapi.py:721— `connection_id is None or not dash_app.shared_storage_enabled` appears character-identically in 3 files — dash/backends/_fastapi.py, dash/backends/_flask.py, dash/backends/_quart.py. 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 dash/backends/_fastapi.py:889— `isinstance(result, tuple) and len(result) == 2` appears character-identically in 2 files — dash/backends/_fastapi.py, dash/backends/_quart.py. 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 dash/_layout_utils.py:168— `isinstance(v, list) and len(v) == 1 and v[0] in _WILDCARD_VALUES` appears character-identically in 2 files — dash/_layout_utils.py, dash/mcp/primitives/tools/callback_adapter.py. 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 dash/mcp/primitives/tools/input_schemas/input_descriptions/description_pattern_matching.py:58— `isinstance(value, list) and len(value) == 1` appears character-identically in 2 files — dash/mcp/primitives/tools/input_schemas/input_descriptions/description_pattern_matching.py, dash/mcp/primitives/tools/input_schemas/schema_pattern_matching.py. 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 dash/backends/_flask.py:513— `not hasattr( self.server.config, "COMPRESS_ALGORITHM" ) and _flask_compress_version >= parse_version("1.6.0")` appears character-identically in 2 files — dash/backends/_flask.py, dash/backends/_quart.py. 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 components/dash-core-components/dash_core_components_base/__init__.py:32— `not hasattr(_dash, "__plotly_dash") and not hasattr(_dash, "development")` appears character-identically in 3 files — components/dash-core-components/dash_core_components_base/__init__.py, components/dash-html-components/dash_html_components_base/__init__.py, components/dash-table/dash_table_base/__init__.py. 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.
Outdated (npm): @fortawesome/fontawesome-svg-core components/dash-core-components/package.json:39— @fortawesome/fontawesome-svg-core is pinned at 1.2.36; registry.npmjs.org publishes 7.3.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): @fortawesome/react-fontawesome components/dash-core-components/package.json:42— @fortawesome/react-fontawesome is pinned at 0.1.19; registry.npmjs.org publishes 3.5.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): react-docgen @plotly/dash-generator-test-component-nested/package.json:20— react-docgen is pinned at 5.4.3; registry.npmjs.org publishes 8.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): react-dropzone components/dash-core-components/package.json:61— react-dropzone is pinned at 4.3.0; registry.npmjs.org publishes 20.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.
Documentation: no build, run or usage example @plotly/dash-websocket-worker/README.md:1— `dash-websocket-worker` is a published package (`package.json` without `"private": true`) and neither `@plotly/dash-websocket-worker/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example @plotly/eslint-config-dash/README.md:1— `eslint-config-dash` is a published package (`package.json` without `"private": true`) and neither `@plotly/eslint-config-dash/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example @plotly/prettier-config-dash/README.md:1— `prettier-config-dash` is a published package (`package.json` without `"private": true`) and neither `@plotly/prettier-config-dash/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no map of the repository's parts README.md:1— The repository has 15 units (`dash-component-plugins`, `dash-generator-test-component-nested`, `dash-generator-test-component-standard`, `dash-generator-test-component-typescript`, `dash-jupyterlab`, ...); `README.md` and the documents it links name none of them. Add a short list of the parts and what each does.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×4
Projects may be oversized for their cohesion components/dash-table/package.json:1— `components/dash-table` (14644 LoC, 248 module-visible types across 48 directories) overshoots its size bounds. 4 of 11 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 2.8/10. 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.
Projects may be oversized for their cohesion package.json:1— `(repository root)` (25362 LoC, 298 module-visible types across 20 directories) overshoots its size bounds. 4 of 11 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 2.8/10. 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.
Projects may be oversized for their cohesion dash/dash-renderer/package.json:1— `dash/dash-renderer` (13498 LoC, 119 module-visible types across 13 directories) overshoots its size bounds. 4 of 11 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 2.8/10. 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.
Projects may be oversized for their cohesion components/dash-core-components/package.json:1— `components/dash-core-components` (11065 LoC, 116 module-visible types across 14 directories) overshoots its size bounds. 4 of 11 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 2.8/10. 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.
Silent fallback default in catch dash/_stream_hub.py:376— `stop` (in `_stop_check`) swallows every exception into `return False` — 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.
Silent fallback default in catch dash/mcp/primitives/tools/callback_adapter.py:205— `_initial_output` 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.
Silent fallback default in catch dash/dash-renderer/src/components/error/menu/VersionInfo.react.js:42— `requestDashVersionInfo` 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.
Silent fallback default in catch dash/extract-meta.js:43— `getTsConfigCompilerOptions` 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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 20 significant file(s) lose their only recent owner: dash/_stream_hub.py, dash/dash-renderer/src/utils/streamClient.ts, REDACTED, dash/_shared_storage/redis.py, benchmarks/run.py, benchmarks/scenarios.py, dash/dash-renderer/src/utils/workerClient.ts, dash/_shared_storage/_engine.py (+12 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 16 significant file(s) lose their only recent owner: components/dash-core-components/src/fragments/RangeSlider.tsx, dash/mcp/primitives/tools/callback_adapter.py, components/dash-core-components/src/utils/calendar/Calendar.tsx, components/dash-core-components/src/components/Tabs.tsx, components/dash-core-components/src/utils/calendar/CalendarMonth.tsx, components/dash-core-components/src/utils/computeSliderMarkers.ts, dash/_layout_utils.py, dash/mcp/primitives/tools/callback_adapter_collection.py (+8 more). Pair on, review, or document these before any departure.
Fat interface: BaseDashServer (17 abstract methods) dash/backends/base_server.py:163— `BaseDashServer` declares 17 abstract methods: `register_assets_blueprint`, `register_error_handlers`, `add_url_rule`, `before_request`, `after_request`, `has_request_context`, `run`, `make_response`, `jsonify`, `enable_compression`, `register_prune_error_handler`, `register_timing_hooks`, `register_callback_api_routes`, `setup_component_suites`, `serve_callback`, `setup_index`, `setup_catchall`. Counted over its `@abstractmethod`s (and abstract properties), once per name; concrete methods are helpers an implementer inherits, not a burden, and `_`-prefixed members are not counted. 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.
No ADRs found REDACTED:47— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `REDACTED` makes this repository a deployable product (line 47).
D21 · Naming Consistency· `columnID` spells `ID` where 55 names in the project spell it `Id` · ×1
`columnID` spells `ID` where 55 names in the project spell it `Id` components/dash-table/src/dash-table/components/Export/utils.tsx:64— 55 of 56 names in project dash spell the token `Id` (55 of 56; unit: names in project dash containing `Id`). Peers: MessageRouter.registerRenderer(rendererId) (@plotly/dash-websocket-worker/src/MessageRouter.ts:26); MessageRouter.unregisterRenderer(rendererId) (@plotly/dash-websocket-worker/src/MessageRouter.ts:34); MessageRouter.handleRendererMessage(rendererId) (@plotly/dash-websocket-worker/src/MessageRouter.ts:50); MessageRouter.notifyConnected(rendererId) (@plotly/dash-websocket-worker/src/MessageRouter.ts:181); MessageRouter.notifyError(rendererId) (@plotly/dash-websocket-worker/src/MessageRouter.ts:214). Rename to `columnId`. [rule N6]
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 69 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: components/dash-table/src/dash-table/derived/header/content.tsx, dash/development/_jl_components_generation.py, components/dash-table/src/dash-table/components/Table/props.ts, dash/dash-renderer/src/observers/requestedCallbacks.ts, components/dash-table/src/dash-table/components/EdgeFactory.tsx, components/dash-core-components/src/fragments/Loading/spinners/GraphSpinner.tsx, components/dash-table/src/dash-table/derived/style/IStyle.ts, dash/testing/plugin.py (and 61 more) (70 orphaned of 173 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; 173 of the 422 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.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No src/ separation — Most of the production code is in directories of its own, but 1 application file(s) sit at the repository root beside the build and tooling files (`REDACTED`).
No SAST REDACTED:11— No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack as a CI step. What was searched, so you can tell an absence from a miss: the 7 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
Unused export 'defaultProps' components/dash-core-components/src/components/Upload.react.js:200— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'NavigationDirection' · ×1
Unused export 'NavigationDirection' components/dash-core-components/src/utils/calendar/CalendarMonth.tsx:28— Nothing imports this binding — it is safe to review for removal.
Unused export 'calcValue' components/dash-core-components/src/utils/computeSliderMarkers.ts:251— Nothing imports this binding — it is safe to review for removal.
Unused export 'RequiredProp' components/dash-table/src/core/type/index.ts:7— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'isPrintableChar' · ×1
Unused export 'isPrintableChar' components/dash-table/src/dash-table/utils/unicode.ts:95— Nothing imports this binding — it is safe to review for removal.
Unused export 'isCtrlKey' components/dash-table/src/dash-table/utils/unicode.ts:147— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'setRequestQueue' · ×1
Unused export 'setRequestQueue' dash/dash-renderer/src/actions/index.js:25— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'REDIRECT_URI_PATHNAME' · ×1
Unused export 'REDIRECT_URI_PATHNAME' dash/dash-renderer/src/constants/constants.js:1— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'IStoreObserver' · ×1
Unused export 'IStoreObserver' dash/dash-renderer/src/store.ts:25— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'EnhancedDashProps' · ×1
Unused export 'EnhancedDashProps' dash/dash-renderer/src/types/component.ts:49— Nothing ultimately consumes this binding: its only referrer is the re-export in dash/dash-renderer/src/types/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in dash/dash-renderer/src/types/index.ts in the same commit, or the barrel will import a name that no longer exists.
Unused export 'DashLayout' dash/dash-renderer/src/types/component.ts:56— Nothing ultimately consumes this binding: its only referrer is the re-export in dash/dash-renderer/src/types/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in dash/dash-renderer/src/types/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code· Unused export 'DashLoadingState' · ×1
Unused export 'DashLoadingState' dash/dash-renderer/src/types/component.ts:60— Nothing ultimately consumes this binding: its only referrer is the re-export in dash/dash-renderer/src/types/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in dash/dash-renderer/src/types/index.ts in the same commit, or the barrel will import a name that no longer exists.
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 0/2 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×1
Diagnostic log message is built whether or not it is wanted dash/testing/browser.py:430— `debug` at line 430 is called with an argument built by `"…".join(menu.text.split("…"))` (line 430), whose cost grows with the collection it walks. Python evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isEnabledFor(logging.DEBUG)` test, no debug flag, no `lambda` the logger calls only when the level is on.
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 — 4/6 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 (`!`) override strict null checking — ~0.2 `!` null assertions per 1k TypeScript source lines — 5 assertion(s) across the 31496 source line(s) of the 255 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: components/dash-table/src/dash-table/components/Table/props.ts (2), dash/dash-renderer/src/observers/websocketObserver.ts (2), dash/dash-renderer/src/utils/workerClient.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Outdated (npm): @fortawesome/free-regular-svg-icons — @fortawesome/free-regular-svg-icons is pinned at 5.15.4; registry.npmjs.org publishes 7.3.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): @fortawesome/free-solid-svg-icons — @fortawesome/free-solid-svg-icons is pinned at 5.15.4; registry.npmjs.org publishes 7.3.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): @jupyterlab/application — @jupyterlab/application is pinned at 4.2.5; registry.npmjs.org publishes 4.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): @jupyterlab/console — @jupyterlab/console is pinned at 4.2.5; registry.npmjs.org publishes 4.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): @jupyterlab/notebook — @jupyterlab/notebook is pinned at 4.2.5; registry.npmjs.org publishes 4.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): cookie — cookie is pinned at 2.0.1; registry.npmjs.org publishes 2.0.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.
Outdated (npm): cytoscape — cytoscape is pinned at 3.34.3; registry.npmjs.org publishes 3.35.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): cytoscape-dagre — cytoscape-dagre is pinned at 2.5.0; registry.npmjs.org publishes 4.1.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): d3-format — d3-format is pinned at 1.4.5; registry.npmjs.org publishes 3.1.3 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): dependency-graph — dependency-graph is pinned at 0.11.0; registry.npmjs.org publishes 1.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.
Outdated (npm): mathjax — mathjax is pinned at 3.2.2; registry.npmjs.org publishes 4.1.3 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): node-polyfill-webpack-plugin — node-polyfill-webpack-plugin is pinned at 2.0.1; registry.npmjs.org publishes 4.1.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): react — react is pinned at 18.3.1; registry.npmjs.org publishes 19.3.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): react-dom — react-dom is pinned at 18.3.1; registry.npmjs.org publishes 19.3.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): react-fast-compare — react-fast-compare is pinned at 3.2.2; registry.npmjs.org publishes 3.2.3 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): react-json-tree — react-json-tree is pinned at 0.17.0; registry.npmjs.org publishes 0.20.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): react-markdown — react-markdown is pinned at 8.0.7; registry.npmjs.org publishes 10.1.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): react-redux — react-redux is pinned at 8.1.3; registry.npmjs.org publishes 9.3.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): react-window — react-window is pinned at 1.8.11; registry.npmjs.org publishes 2.5.3 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): redux — redux is pinned at 4.2.1; registry.npmjs.org publishes 5.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): redux-actions — redux-actions is pinned at 2.6.5; registry.npmjs.org publishes 3.0.3 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): redux-thunk — redux-thunk is pinned at 2.4.2; registry.npmjs.org publishes 3.1.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): rehype-raw — rehype-raw is pinned at 6.1.1; registry.npmjs.org publishes 7.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.
Outdated (npm): remark-gfm — remark-gfm is pinned at 3.0.1; registry.npmjs.org publishes 4.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): remark-math — remark-math is pinned at 5.1.1; registry.npmjs.org publishes 6.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.
doc comments repeat the names @plotly/dash-websocket-worker/src/MessageRouter.ts:31— 0 of 17 documented parameters and 3 of 53 summaries in `@plotly/dash-websocket-worker` only repeat the member or parameter name (e.g. "Unregister a renderer." for `unregisterRenderer`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names components/dash-core-components/src/components/Geolocation.react.js:145— 0 of 1 documented parameters and 1 of 464 summaries in `dash-core-components` only repeat the member or parameter name (e.g. "Position error" for `position_error`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names @plotly/dash-generator-test-component-standard/src/components/MyStandardComponent.js:16— 0 of 0 documented parameters and 1 of 4 summaries in `dash-generator-test-component-standard` only repeat the member or parameter name (e.g. "The style" for `style`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names @plotly/dash-generator-test-component-typescript/src/props.ts:19— 0 of 0 documented parameters and 1 of 5 summaries in `dash-generator-test-component-typescript` only repeat the member or parameter name (e.g. "A string" for `required_string`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names REDACTED:28— 1 of 43 documented parameters and 2 of 80 summaries in `dash-renderer` only repeat the member or parameter name (e.g. "props" for `props`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names @plotly/dash-test-components/src/components/ShapeOrExactKeepOrderComponent.js:15— 0 of 0 documented parameters and 3 of 25 summaries in `dash-test-components` only repeat the member or parameter name (e.g. "test prop for shape" for `shape_test_prop`). Delete the restating tags, or add what the name does not say.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
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 4 file(s) — `components/dash-core-components/src/fragments/Graph.react.js`, `components/dash-table/src/core/math/arrayZipMap.ts`, `dash/dash-renderer/src/wrapper/DashWrapper.tsx`, `dash/dash-renderer/src/wrapper/wrapping.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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 01a1e629-b467-71b1-8546-2977fbfeae34 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 319 · Warnings: 530 · Recommendations: 203 · Info: 33 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 21:00 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.