Public report of mui/material-ui, published 13 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.3). 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, 13 November 2026, 17:16 UTC · Survey ID cd_67f1b61a8a7a46d580679e96441af3e4
mui/material-ui
Measured 13 November 2026, 17:12 UTC, at code version 212e2e3
CAI scoreAt riskDown 2 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 280,622 lines of product code in 22 projects, tests not counted · Estimated rebuild effort: about 2.6 person-years · Weakest lens: Production Readiness, 46
Findings by how serious they are
56 critical1192 serious644 minor
7 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
13 November 2026, 17:12 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 ▸
75of 75 dimensions measured by tools.
1851of 1892 findings point to an exact file and line, so you can open each one in the code. The other 41 concern the repository as a whole, such as missing documentation.
75dimensions across 7 lenses, read from 280,622 lines of product code in 22 projects.
mui/material-ui is rated At risk because critical security findings are open. Its score is held back in part because it has packages under a licence on your banned list. It scores 54 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 46, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the password or key in the code, worth about 6 points. Replacing the 14 packages under a banned licence would lift Production Readiness itself, worth about 7 points. Raising Production Readiness to 70 would lift the score to about 60.
Fourteen packages carry licence risk. Ten known security holes in the packages the code depends on can be used by attackers, and five passwords or keys in the code's history and one in the code are open to anyone who can read the repository. Replacing each exposed password or key, replacing or clearing the banned-licence packages and updating the vulnerable packages would close these risks. Fixing the weaknesses the scanner points to would fix the five security weaknesses in the code, and setting a waiting period for automatic updates would deal with the three automatic dependency updates that take new releases at once. The nine uses of packages that aren't listed need adding to the project's list of dependencies.
The product code is 280,622 lines, about €390,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 46 to 70, the lowest score rated Strong, the score would rise from 54 to about 60.
Code composition: what the lines of code are
Product code 71%Tests 29%
New since the last survey: 117 findings
These 117 critical or serious findings weren't in the previous survey, on 24 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Large Files · packages-internal/core-docs/src/branding/brandingTheme.ts: 1590 lines of code packages-internal/core-docs/src/branding/brandingTheme.ts
Large Files · packages/mui-material/src/useAutocomplete/useAutocomplete.js: 1422 lines of code packages/mui-material/src/useAutocomplete/useAutocomplete.js
Large Files · packages/mui-material/src/Autocomplete/Autocomplete.js: 1289 lines of code packages/mui-material/src/Autocomplete/Autocomplete.js
Large Files · packages/mui-material/src/Slider/Slider.js: 1043 lines of code packages/mui-material/src/Slider/Slider.js
Large Files · packages/mui-material/src/styles/createThemeWithVars.js: 1006 lines of code packages/mui-material/src/styles/createThemeWithVars.js
Large Files · packages/mui-material/src/Select/SelectInput.js: 971 lines of code packages/mui-material/src/Select/SelectInput.js
Large Files · packages-internal/core-docs/src/MarkdownDocs/MarkdownElement.tsx: 864 lines of code packages-internal/core-docs/src/MarkdownDocs/MarkdownElement.tsx
Large Files · REDACTED: 859 lines of code REDACTED
Large Files · REDACTED: 813 lines of code REDACTED
Large Files · packages/mui-material/src/Slider/useSlider.ts: 809 lines of code packages/mui-material/src/Slider/useSlider.ts
Large Files · packages/mui-material/src/Tooltip/Tooltip.js: 794 lines of code packages/mui-material/src/Tooltip/Tooltip.js
Large Files · packages/mui-material/src/Rating/Rating.js: 780 lines of code packages/mui-material/src/Rating/Rating.js
Large Files · packages/mui-material/src/InputBase/InputBase.js: 767 lines of code packages/mui-material/src/InputBase/InputBase.js
Large Files · packages/mui-material/src/Button/Button.js: 716 lines of code packages/mui-material/src/Button/Button.js
Large Files · packages-internal/core-docs/src/DemoContent/DemoContainer.tsx: 666 lines of code packages-internal/core-docs/src/DemoContent/DemoContainer.tsx
Large Files · packages/mui-material/src/Chip/Chip.js: 660 lines of code packages/mui-material/src/Chip/Chip.js
Large Files · scripts/buildLlmsDocs/index.ts: 600 lines of code scripts/buildLlmsDocs/index.ts
Large Files · packages/mui-material/src/LinearProgress/LinearProgress.js: 570 lines of code packages/mui-material/src/LinearProgress/LinearProgress.js
Large Files · packages/mui-system/src/cssVars/createCssVarsProvider.tsx: 546 lines of code packages/mui-system/src/cssVars/createCssVarsProvider.tsx
Large Files · packages/mui-material/src/SpeedDial/SpeedDial.js: 542 lines of code packages/mui-material/src/SpeedDial/SpeedDial.js
Large Files · packages/mui-material/src/Popper/BasePopper.tsx: 510 lines of code packages/mui-material/src/Popper/BasePopper.tsx
Large Files · packages/mui-material/src/PaginationItem/PaginationItem.js: 504 lines of code packages/mui-material/src/PaginationItem/PaginationItem.js
Large Files · packages/mui-material/src/TablePagination/TablePagination.js: 492 lines of code packages/mui-material/src/TablePagination/TablePagination.js
Test Coverage · No test reaches this file packages-internal/api-docs-builder/src/types/utils.types.ts
Dead Code · Dead file (~242 LoC) netlify/functions/feedback-management.mts
Dead Code · Dead file (~55 LoC) packages-internal/core-docs/src/AppLayout/components/ArrowButton.tsx
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: 591 findings
These 591 critical or serious findings were in the previous survey, on 24 October 2026, and are gone from this one. The first 100 are listed here.
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Rebuild cost: about €390,000 · Estimate
Cost to rebuild
€130,000 to €640,000, for 2,131 to 6,761 hours of work, about 2.6 person-years for 1 to 6 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 54. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 280,622 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
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Files that change often carry extra risk · Combined risk
2 files are changed often and are hard to read, which makes them the likeliest places for a mistake. They also have under half their code tested, or were written almost entirely by one person, so a mistake there is less likely to be caught, or only one person knows the code well enough to avoid it. A change to these files therefore carries more risk than the overall score suggests.
Based on: Churn × Complexity Hotspots (19 files) · Code Coverage (128 files under half tested) · Bus Factor (0 files written almost entirely by one person) · The files: index.ts and Masonry.tsx
What to do: Add tests to these files and have a second person review every change to them, starting with index.ts and Masonry.tsx.
Where the investment is most exposed · Value at risk
This code would cost about €390,000 to build again, about 2.6 person-years of work. Its weakest lens is Production Readiness, at 46 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for low effort, because it clears the 1 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 4.9 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 8% to 17% on every change. The history of the code shows how much it changes: about 123,844 lines over the last 90 days, which is about 502,256 lines a year. At that pace, the extra work comes to an estimated 96.7 to 580.1 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
926 modules, with 278 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; 886 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.
2 pairs of types, where a type in docs.data.material.getting-started.templates.dashboard.components uses a type in docs.data.material.getting-started.templates.dashboard.components.CustomizedTreeView.
docs.data.material.getting-started.templates.dashboard.components uses docs.data.material.getting-started.templates.dashboard.components.CustomizedTreeView, so a change to docs.data.material.getting-started.templates.dashboard.components.CustomizedTreeView can break docs.data.material.getting-started.templates.dashboard.components, while a change to docs.data.material.getting-started.templates.dashboard.components can't break docs.data.material.getting-started.templates.dashboard.components.CustomizedTreeView.
Position
Below the diagonal: docs.data.material.getting-started.templates.dashboard.components uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in docs.data.material.getting-started.templates.dashboard.components uses a type in packages.mui-material.src.transitions.utils.
docs.data.material.getting-started.templates.dashboard.components uses packages.mui-material.src.transitions.utils, so a change to packages.mui-material.src.transitions.utils can break docs.data.material.getting-started.templates.dashboard.components, while a change to docs.data.material.getting-started.templates.dashboard.components can't break packages.mui-material.src.transitions.utils.
Position
Below the diagonal: docs.data.material.getting-started.templates.dashboard.components uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in docs.src.components.productX uses a type in docs.data.material.getting-started.templates.dashboard.components.CustomizedTreeView.
docs.src.components.productX uses docs.data.material.getting-started.templates.dashboard.components.CustomizedTreeView, so a change to docs.data.material.getting-started.templates.dashboard.components.CustomizedTreeView can break docs.src.components.productX, while a change to docs.src.components.productX can't break docs.data.material.getting-started.templates.dashboard.components.CustomizedTreeView.
Position
Below the diagonal: docs.src.components.productX uses a module listed above it, which is the healthy direction.
docs.src.components.productX uses docs.src.components.productX.XTreeViewDemo, so a change to docs.src.components.productX.XTreeViewDemo can break docs.src.components.productX, while a change to docs.src.components.productX can't break docs.src.components.productX.XTreeViewDemo.
Position
Below the diagonal: docs.src.components.productX uses a module listed above it, which is the healthy direction.
docs.src.components.productX uses packages.mui-material.src.transitions.utils, so a change to packages.mui-material.src.transitions.utils can break docs.src.components.productX, while a change to docs.src.components.productX can't break packages.mui-material.src.transitions.utils.
Position
Below the diagonal: docs.src.components.productX uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages-internal.api-docs-builder.src.ApiBuilders uses a type in packages-internal.api-docs-builder.src.ProjectSettings.
packages-internal.api-docs-builder.src.ApiBuilders uses packages-internal.api-docs-builder.src.ProjectSettings, so a change to packages-internal.api-docs-builder.src.ProjectSettings can break packages-internal.api-docs-builder.src.ApiBuilders, while a change to packages-internal.api-docs-builder.src.ApiBuilders can't break packages-internal.api-docs-builder.src.ProjectSettings.
Position
Below the diagonal: packages-internal.api-docs-builder.src.ApiBuilders uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages-internal.api-docs-builder.src.ApiBuilders uses a type in packages-internal.api-docs-builder.src.types.ApiBuilder_types.
packages-internal.api-docs-builder.src.ApiBuilders uses packages-internal.api-docs-builder.src.types.ApiBuilder_types, so a change to packages-internal.api-docs-builder.src.types.ApiBuilder_types can break packages-internal.api-docs-builder.src.ApiBuilders, while a change to packages-internal.api-docs-builder.src.ApiBuilders can't break packages-internal.api-docs-builder.src.types.ApiBuilder_types.
Position
Below the diagonal: packages-internal.api-docs-builder.src.ApiBuilders uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages-internal.api-docs-builder.src.ApiBuilders uses a type in packages-internal.api-docs-builder.src.utils.createTypeScriptProject.
packages-internal.api-docs-builder.src.ApiBuilders uses packages-internal.api-docs-builder.src.utils.createTypeScriptProject, so a change to packages-internal.api-docs-builder.src.utils.createTypeScriptProject can break packages-internal.api-docs-builder.src.ApiBuilders, while a change to packages-internal.api-docs-builder.src.ApiBuilders can't break packages-internal.api-docs-builder.src.utils.createTypeScriptProject.
Position
Below the diagonal: packages-internal.api-docs-builder.src.ApiBuilders uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages-internal.api-docs-builder.src.utils.getPropsFromComponentNode uses a type in packages-internal.api-docs-builder.src.utils.createTypeScriptProject.
packages-internal.api-docs-builder.src.utils.getPropsFromComponentNode uses packages-internal.api-docs-builder.src.utils.createTypeScriptProject, so a change to packages-internal.api-docs-builder.src.utils.createTypeScriptProject can break packages-internal.api-docs-builder.src.utils.getPropsFromComponentNode, while a change to packages-internal.api-docs-builder.src.utils.getPropsFromComponentNode can't break packages-internal.api-docs-builder.src.utils.createTypeScriptProject.
Position
Below the diagonal: packages-internal.api-docs-builder.src.utils.getPropsFromComponentNode uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages-internal.api-docs-builder.src.utils.parseSlotsAndClasses uses a type in packages-internal.api-docs-builder.src.ProjectSettings.
packages-internal.api-docs-builder.src.utils.parseSlotsAndClasses uses packages-internal.api-docs-builder.src.ProjectSettings, so a change to packages-internal.api-docs-builder.src.ProjectSettings can break packages-internal.api-docs-builder.src.utils.parseSlotsAndClasses, while a change to packages-internal.api-docs-builder.src.utils.parseSlotsAndClasses can't break packages-internal.api-docs-builder.src.ProjectSettings.
Position
Below the diagonal: packages-internal.api-docs-builder.src.utils.parseSlotsAndClasses uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages-internal.api-docs-builder.src.utils.parseSlotsAndClasses uses a type in packages-internal.api-docs-builder.src.utils.createTypeScriptProject.
packages-internal.api-docs-builder.src.utils.parseSlotsAndClasses uses packages-internal.api-docs-builder.src.utils.createTypeScriptProject, so a change to packages-internal.api-docs-builder.src.utils.createTypeScriptProject can break packages-internal.api-docs-builder.src.utils.parseSlotsAndClasses, while a change to packages-internal.api-docs-builder.src.utils.parseSlotsAndClasses can't break packages-internal.api-docs-builder.src.utils.createTypeScriptProject.
Position
Below the diagonal: packages-internal.api-docs-builder.src.utils.parseSlotsAndClasses uses a module listed above it, which is the healthy direction.
packages-internal.core-docs.src.Ad uses packages-internal.core-docs.src.Ad.AdProvider, so a change to packages-internal.core-docs.src.Ad.AdProvider can break packages-internal.core-docs.src.Ad, while a change to packages-internal.core-docs.src.Ad can't break packages-internal.core-docs.src.Ad.AdProvider.
Position
Below the diagonal: packages-internal.core-docs.src.Ad uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages-internal.core-docs.src.ApiPage.ApiPage uses a type in packages-internal.api-docs-builder.src.types.ApiBuilder_types.
packages-internal.core-docs.src.ApiPage.ApiPage uses packages-internal.api-docs-builder.src.types.ApiBuilder_types, so a change to packages-internal.api-docs-builder.src.types.ApiBuilder_types can break packages-internal.core-docs.src.ApiPage.ApiPage, while a change to packages-internal.core-docs.src.ApiPage.ApiPage can't break packages-internal.api-docs-builder.src.types.ApiBuilder_types.
Position
Below the diagonal: packages-internal.core-docs.src.ApiPage.ApiPage uses a module listed above it, which is the healthy direction.
packages-internal.core-docs.src.AppLayout.layout uses packages.mui-material.src.transitions.utils, so a change to packages.mui-material.src.transitions.utils can break packages-internal.core-docs.src.AppLayout.layout, while a change to packages-internal.core-docs.src.AppLayout.layout can't break packages.mui-material.src.transitions.utils.
Position
Below the diagonal: packages-internal.core-docs.src.AppLayout.layout uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages-internal.core-docs.src.AppLayout.navigation uses a type in packages.mui-system.src.styleFunctionSx.styleFunctionSx.
packages-internal.core-docs.src.AppLayout.navigation uses packages.mui-system.src.styleFunctionSx.styleFunctionSx, so a change to packages.mui-system.src.styleFunctionSx.styleFunctionSx can break packages-internal.core-docs.src.AppLayout.navigation, while a change to packages-internal.core-docs.src.AppLayout.navigation can't break packages.mui-system.src.styleFunctionSx.styleFunctionSx.
Position
Below the diagonal: packages-internal.core-docs.src.AppLayout.navigation uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages-internal.core-docs.src.DocsProvider.DocsProvider uses a type in packages-internal.core-docs.src.Ad.AdProvider.
packages-internal.core-docs.src.DocsProvider.DocsProvider uses packages-internal.core-docs.src.Ad.AdProvider, so a change to packages-internal.core-docs.src.Ad.AdProvider can break packages-internal.core-docs.src.DocsProvider.DocsProvider, while a change to packages-internal.core-docs.src.DocsProvider.DocsProvider can't break packages-internal.core-docs.src.Ad.AdProvider.
Position
Below the diagonal: packages-internal.core-docs.src.DocsProvider.DocsProvider uses a module listed above it, which is the healthy direction.
packages.mui-material.src.styles uses docs.src.components.productX.XTreeViewDemo, so a change to docs.src.components.productX.XTreeViewDemo can break packages.mui-material.src.styles, while a change to packages.mui-material.src.styles can't break docs.src.components.productX.XTreeViewDemo.
Position
Below the diagonal: packages.mui-material.src.styles uses a module listed above it, which is the healthy direction.
packages.mui-styled-engine-sc.src uses packages.mui-material.src.transitions.utils, so a change to packages.mui-material.src.transitions.utils can break packages.mui-styled-engine-sc.src, while a change to packages.mui-styled-engine-sc.src can't break packages.mui-material.src.transitions.utils.
Position
Below the diagonal: packages.mui-styled-engine-sc.src uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.mui-system.src.createTheme.createTheme uses a type in packages.mui-system.src.createBreakpoints.createBreakpoints.
packages.mui-system.src.createTheme.createTheme uses packages.mui-system.src.createBreakpoints.createBreakpoints, so a change to packages.mui-system.src.createBreakpoints.createBreakpoints can break packages.mui-system.src.createTheme.createTheme, while a change to packages.mui-system.src.createTheme.createTheme can't break packages.mui-system.src.createBreakpoints.createBreakpoints.
Position
Below the diagonal: packages.mui-system.src.createTheme.createTheme uses a module listed above it, which is the healthy direction.
packages-internal.api-docs-builder.src.utils uses packages-internal.api-docs-builder.src.ProjectSettings, so a change to packages-internal.api-docs-builder.src.ProjectSettings can break packages-internal.api-docs-builder.src.utils, while a change to packages-internal.api-docs-builder.src.utils can't break packages-internal.api-docs-builder.src.ProjectSettings.
Position
Below the diagonal: packages-internal.api-docs-builder.src.utils uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages-internal.api-docs-builder.src.utils uses a type in packages-internal.api-docs-builder.src.types.ApiBuilder_types.
packages-internal.api-docs-builder.src.utils uses packages-internal.api-docs-builder.src.types.ApiBuilder_types, so a change to packages-internal.api-docs-builder.src.types.ApiBuilder_types can break packages-internal.api-docs-builder.src.utils, while a change to packages-internal.api-docs-builder.src.utils can't break packages-internal.api-docs-builder.src.types.ApiBuilder_types.
Position
Below the diagonal: packages-internal.api-docs-builder.src.utils uses a module listed above it, which is the healthy direction.
7 pairs of types, where a type in packages-internal.api-docs-builder.src.utils uses a type in packages-internal.api-docs-builder.src.utils.createTypeScriptProject.
packages-internal.api-docs-builder.src.utils uses packages-internal.api-docs-builder.src.utils.createTypeScriptProject, so a change to packages-internal.api-docs-builder.src.utils.createTypeScriptProject can break packages-internal.api-docs-builder.src.utils, while a change to packages-internal.api-docs-builder.src.utils can't break packages-internal.api-docs-builder.src.utils.createTypeScriptProject.
Position
Below the diagonal: packages-internal.api-docs-builder.src.utils uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in packages-internal.api-docs-builder.src.utils uses a type in packages-internal.api-docs-builder.src.utils.getPropsFromComponentNode.
packages-internal.api-docs-builder.src.utils uses packages-internal.api-docs-builder.src.utils.getPropsFromComponentNode, so a change to packages-internal.api-docs-builder.src.utils.getPropsFromComponentNode can break packages-internal.api-docs-builder.src.utils, while a change to packages-internal.api-docs-builder.src.utils can't break packages-internal.api-docs-builder.src.utils.getPropsFromComponentNode.
Position
Below the diagonal: packages-internal.api-docs-builder.src.utils uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages-internal.api-docs-builder.src.utils uses a type in packages-internal.api-docs-builder.src.utils.parseSlotsAndClasses.
packages-internal.api-docs-builder.src.utils uses packages-internal.api-docs-builder.src.utils.parseSlotsAndClasses, so a change to packages-internal.api-docs-builder.src.utils.parseSlotsAndClasses can break packages-internal.api-docs-builder.src.utils, while a change to packages-internal.api-docs-builder.src.utils can't break packages-internal.api-docs-builder.src.utils.parseSlotsAndClasses.
Position
Below the diagonal: packages-internal.api-docs-builder.src.utils uses a module listed above it, which is the healthy direction.
packages-internal.core-docs.src.ApiPage uses packages-internal.core-docs.src.ApiPage.ApiPage, so a change to packages-internal.core-docs.src.ApiPage.ApiPage can break packages-internal.core-docs.src.ApiPage, while a change to packages-internal.core-docs.src.ApiPage can't break packages-internal.core-docs.src.ApiPage.ApiPage.
Position
Below the diagonal: packages-internal.core-docs.src.ApiPage uses a module listed above it, which is the healthy direction.
packages-internal.core-docs.src.DemoContent uses packages.mui-material.src.transitions.utils, so a change to packages.mui-material.src.transitions.utils can break packages-internal.core-docs.src.DemoContent, while a change to packages-internal.core-docs.src.DemoContent can't break packages.mui-material.src.transitions.utils.
Position
Below the diagonal: packages-internal.core-docs.src.DemoContent uses a module listed above it, which is the healthy direction.
packages-internal.core-docs.src.DemoContent uses packages.mui-styled-engine-sc.src, so a change to packages.mui-styled-engine-sc.src can break packages-internal.core-docs.src.DemoContent, while a change to packages-internal.core-docs.src.DemoContent can't break packages.mui-styled-engine-sc.src.
Position
Below the diagonal: packages-internal.core-docs.src.DemoContent uses a module listed above it, which is the healthy direction.
packages-internal.core-docs.src.DocsApp.DocsApp uses packages-internal.core-docs.src.Ad.AdProvider, so a change to packages-internal.core-docs.src.Ad.AdProvider can break packages-internal.core-docs.src.DocsApp.DocsApp, while a change to packages-internal.core-docs.src.DocsApp.DocsApp can't break packages-internal.core-docs.src.Ad.AdProvider.
Position
Below the diagonal: packages-internal.core-docs.src.DocsApp.DocsApp uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages-internal.core-docs.src.DocsApp.DocsApp uses a type in packages-internal.core-docs.src.DocsProvider.DocsProvider.
packages-internal.core-docs.src.DocsApp.DocsApp uses packages-internal.core-docs.src.DocsProvider.DocsProvider, so a change to packages-internal.core-docs.src.DocsProvider.DocsProvider can break packages-internal.core-docs.src.DocsApp.DocsApp, while a change to packages-internal.core-docs.src.DocsApp.DocsApp can't break packages-internal.core-docs.src.DocsProvider.DocsProvider.
Position
Below the diagonal: packages-internal.core-docs.src.DocsApp.DocsApp uses a module listed above it, which is the healthy direction.
5 pairs of types, where a type in packages.mui-material.src.styles.createThemeFoundation uses a type in packages.mui-system.src.createTheme.createTheme.
packages.mui-material.src.styles.createThemeFoundation uses packages.mui-system.src.createTheme.createTheme, so a change to packages.mui-system.src.createTheme.createTheme can break packages.mui-material.src.styles.createThemeFoundation, while a change to packages.mui-material.src.styles.createThemeFoundation can't break packages.mui-system.src.createTheme.createTheme.
Position
Below the diagonal: packages.mui-material.src.styles.createThemeFoundation uses a module listed above it, which is the healthy direction.
packages-internal.core-docs.src.DocsApp uses packages-internal.core-docs.src.DocsApp.DocsApp, so a change to packages-internal.core-docs.src.DocsApp.DocsApp can break packages-internal.core-docs.src.DocsApp, while a change to packages-internal.core-docs.src.DocsApp can't break packages-internal.core-docs.src.DocsApp.DocsApp.
Position
Below the diagonal: packages-internal.core-docs.src.DocsApp uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 55% · Adequate · gated by D1, D2 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
67
High / Critical
A03:2025 — Software Supply Chain Failures
25
High / Critical
A07:2025 — Authentication Failures
7
High / Critical
A01:2025 — Broken Access Control
2
Medium
Roadmap
Top priorities: Resolve the 14 Banned license finding(s) in License Compliance — start with REDACTED (14); Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED; Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
Bring the 2 bodies over 120 down to 120 or less in Cyclomatic Complexity — start with brandingTheme.getThemedComponents (cyclomatic 241), useAutocomplete (cyclomatic 127).
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 — 56
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 — 1192
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 — 644
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 7
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
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 75 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 — 75 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, 1851 of 1892 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.
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 included — the JavaScript/TypeScript suite (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root (6988 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in test/e2e/ (0 tests)) did not finish re-running within its budget: too large to re-run within its budget.
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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
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 on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D23 Boundary Type-Coupling — measured, with a gap in what it reached — 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 measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
D32 Data Compliance (PII/GDPR) — 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. `docs/next.config.ts`, `packages-internal/core-docs/src/AppLayout/components/Frame.tsx`, `packages-internal/core-docs/src/TableOfContents/MiniTableOfContents.tsx`, `packages/mui-icons-material/templateSvgIcon.js`, `packages/mui-lab/src/LoadingButton/index.ts`, … (+30 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AC1 Text alternatives — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository builds user interface as HTML STRINGS — at least 9 script file(s) building 29 markup element(s) as HTML strings, carrying 0 role/aria/tabindex attribute(s) (e.g. packages-internal/core-docs/src/svgIcons/BaseUiLogoIcon.tsx, packages-internal/core-docs/src/svgIcons/MuiLogomarkIcon.tsx, packages-internal/core-docs/src/NextNProgressBar/NProgressBar.tsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 458 parsed markup document(s) only. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC2 Forms & labels — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository builds user interface as HTML STRINGS — at least 9 script file(s) building 29 markup element(s) as HTML strings, carrying 0 role/aria/tabindex attribute(s) (e.g. packages-internal/core-docs/src/svgIcons/BaseUiLogoIcon.tsx, packages-internal/core-docs/src/svgIcons/MuiLogomarkIcon.tsx, packages-internal/core-docs/src/NextNProgressBar/NProgressBar.tsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 458 parsed markup document(s) only. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC3 Page structure — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository builds user interface as HTML STRINGS — at least 9 script file(s) building 29 markup element(s) as HTML strings, carrying 0 role/aria/tabindex attribute(s) (e.g. packages-internal/core-docs/src/svgIcons/BaseUiLogoIcon.tsx, packages-internal/core-docs/src/svgIcons/MuiLogomarkIcon.tsx, packages-internal/core-docs/src/NextNProgressBar/NProgressBar.tsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 458 parsed markup document(s) only. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC4 Keyboard semantics — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository builds user interface as HTML STRINGS — at least 9 script file(s) building 29 markup element(s) as HTML strings, carrying 0 role/aria/tabindex attribute(s) (e.g. packages-internal/core-docs/src/svgIcons/BaseUiLogoIcon.tsx, packages-internal/core-docs/src/svgIcons/MuiLogomarkIcon.tsx, packages-internal/core-docs/src/NextNProgressBar/NProgressBar.tsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 458 parsed markup document(s) only. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC5 ARIA correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository builds user interface as HTML STRINGS — at least 9 script file(s) building 29 markup element(s) as HTML strings, carrying 0 role/aria/tabindex attribute(s) (e.g. packages-internal/core-docs/src/svgIcons/BaseUiLogoIcon.tsx, packages-internal/core-docs/src/svgIcons/MuiLogomarkIcon.tsx, packages-internal/core-docs/src/NextNProgressBar/NProgressBar.tsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 458 parsed markup document(s) only. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC6 Visual & motion safety — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository builds user interface as HTML STRINGS — at least 9 script file(s) building 29 markup element(s) as HTML strings, carrying 0 role/aria/tabindex attribute(s) (e.g. packages-internal/core-docs/src/svgIcons/BaseUiLogoIcon.tsx, packages-internal/core-docs/src/svgIcons/MuiLogomarkIcon.tsx, packages-internal/core-docs/src/NextNProgressBar/NProgressBar.tsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 458 parsed markup document(s) only. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AXB2 Runtime readiness — 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. A program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. (rule: missing-tool). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> start / > pnpm install && pnpm docs:dev / sh: 1: pnpm: not found" No runtime evidence was gathered.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> start / > pnpm install && pnpm docs:dev / sh: 1: pnpm: not found" No runtime evidence was gathered.
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. 314 further occurrence(s) are not listed individually; the score already reflects all 354.
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. 156 further occurrence(s) are not listed individually; the score already reflects all 196.
R3 Large Files — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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. 29 further occurrence(s) are not listed individually; the score already reflects all 69.
R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 224 further occurrence(s) are not listed individually; the score already reflects all 264.
X10 Duplicated predicate — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 53 further occurrence(s) are not listed individually; the score already reflects all 93.
X24 Document value interpolated into markup unescaped — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 11 further occurrence(s) are not listed individually; the score already reflects all 51.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations: 5 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.
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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
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 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality 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.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
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.
184 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was brandingTheme.getThemedComponents at 241. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being parseMarkdown.createRender.render at 28 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: REDACTED (parseMarkdown.createRender.render at 28). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 126 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 120 down to 120 or less in Cyclomatic Complexity — start with brandingTheme.getThemedComponents (cyclomatic 241), useAutocomplete (cyclomatic 127). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 2.8 to about 4.1/10, projected with the scoring formula itself and assuming each lands exactly at 120; 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.
+ 150 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 7 bodies over 120 down to 120 or less in Cognitive Complexity — start with brandingTheme.getThemedComponents (cognitive 230), sx-v6.sxV6 (cognitive 212), transformer (cognitive 201). — 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 7 together lifts Cognitive Complexity from 2.0 to about 3.1/10, projected with the scoring formula itself and assuming each lands exactly at 120; 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 Classes7.4 / 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 146 FunctionTooLong finding(s) in God Classes — start with brandingTheme.ts (2), blog.tsx (2), Footer.js (2). — One of this dimension's main actionable groups (146 warning-level).
Resolve the 16 FileTooLong finding(s) in God Classes — start with PricingTable.tsx, brandingTheme.ts, useAutocomplete.js. — One of this dimension's main actionable groups (16 warning-level).
Resolve the 7 ClassTooLong finding(s) in God Classes — start with useAutocomplete.js, components.ts, createThemeWithVars.js. — One of this dimension's main actionable groups (7 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.5 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
21 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 4 module(s) off the main sequence, with abstractness counted on 14 of the 21 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: @mui/stylis-plugin-rtl · ×4
What to do
Resolve the 4 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 84.2% — 129 file(s) below 50%. Measured from the JavaScript/TypeScript suite (vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root; vitest in test/e2e/: not run).
Resolve the 129 Low coverage finding(s) in Code Coverage — start with index.ts (2), codemod.js, deprecations-all.js. — One of this dimension's main actionable groups (129 warning-level).
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.8 / 10Adequategated by 5 critical findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
455 skipped (453 with a documented reason), 61 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 5352 tests.
No assertions (empty test): removes event listeners on unmount · ×5packages/mui-material/src/SwipeableDrawer/SwipeableDrawer.test.js:524
No assertions: ${action} ${route} · ×56test/regressions/index.test.js:217
Skipped test: route not bundled: ${route} · ×2test/regressions/index.test.js:626
Mock-dominated test: does not call key handlers or fire when disabledpackages/mui-material/src/ButtonBase/useButtonBase.test.tsx:216
Resolve the 5 No assertions (empty test) finding(s) in Test Quality — start with SwipeableDrawer.test.js (3), TouchRipple.test.js, AlertTitle.test.js. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 56 No assertions finding(s) in Test Quality — start with index.test.js (12), demo-docs-production.baseline.ts (2), demo-docs-production.spec.ts (2). — One of this dimension's main actionable groups (56 warning-level).
Resolve the 2 Skipped test finding(s) in Test Quality — start with index.test.js, material-docs.spec.ts. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
13 outdated direct production npm dependency(ies) of 106 graded, 0 pinning defect(s), across 54 package.json (21 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 1 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 5 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (5). — One of this dimension's main actionable groups (5 recommendation-level).
Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with package.json. — One of this dimension's main actionable groups (1 warning-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.
14 of 845 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 845 package(s) this repository's committed lockfile installs for a consumer — its 106 production, optional and peer dependency(ies), across 21 product package.json manifest(s), and everything those install in turn. Its 334 `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. 6 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. This repository publishes itself under MIT, which is its own choice and is not judged here.
Resolve the 14 Banned license finding(s) in License Compliance — start with REDACTED (14). — One of this dimension's main actionable groups (14 issue-level).
Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.
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 19 Hotspot finding(s) in Churn × Complexity Hotspots — start with brandingTheme.ts, createThemeWithVars.js, SelectInput.js. — One of this dimension's main actionable groups (19 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.8 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
10 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages-internal/core-docs/src/DemoContent/DemoContainer.tsx. Counted over 494 of the 2067 production source files in this repository: 1571 are under the ~2,400-byte size floor this dimension measures over, and the remaining 2 have no attributable history left to measure.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
88 deducted task-comment markers across 172707 LoC (0.1/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 86 TodoComment finding(s) in Explicit Debt — start with index.ts (8), AppNavDrawer.tsx (6), createStyled.ts (5). — One of this dimension's main actionable groups (86 warning-level).
Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with TextField.spec.tsx. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with PricingTable.tsx. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
1 of 2 documentation facets pass in full; short on: F2 example. 258 document(s) read across 23 unit(s).
Documentation: no build, run or usage example · ×9packages-internal/scripts/README.md:1
What to do
Resolve the 9 Documentation finding(s) in Documentation Quality — start with README.md (9). — One of this dimension's main actionable groups (9 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 package.json. — 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.
2 naming inconsistencies among 78 declarations measured against a convention their peers follow.
`deployURL` spells `URL` where 15 names in the project spell it `Url`netlify/functions/on-deploy.mts:9
`moduleID` spells `ID` where 61 names in the project spell it `Id`packages-internal/core-docs/src/MarkdownDocs/RichMarkdownElement.tsx:9
What to do
Resolve the 1 `deployURL` spells `URL` where 15 names in the project spell it `Url` finding(s) in Naming Consistency — start with on-deploy.mts. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `moduleID` spells `ID` where 61 names in the project spell it `Id` finding(s) in Naming Consistency — start with RichMarkdownElement.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 domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
29 domain type(s) cross context boundaries across 19 contexts; they are measured and withheld (not published, not scored). Contexts: api-docs-builder, api-docs-builder-core, core-docs, docs, docs-utils, markdown, mui-codemod, mui-envinfo, mui-icons-material, mui-lab, mui-material, mui-material-nextjs and 7 more.
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.
5 of 22 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
0 % of calls cross a namespace and 0 % go through an interface, but 71 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
5 finding(s): 0 critical, 5 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 5 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
67 finding(s): 0 critical, 10 high, 57 medium, 0 low. semgrep hit a parse error in 42 file(s) — `docs/next.config.ts` (line 392), `examples/material-ui-react-router-ts/app/routes.ts` (line 7), `examples/material-ui-react-router-ts/react-router.config.ts` (line 7), `packages-internal/core-docs/src/AppLayout/components/Frame.tsx` (line 75, line 78), `packages-internal/core-docs/src/Demo/OpenInMUIChatButton.test.tsx` (line 27, line 32), … (+37 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 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
+ 7 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
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 12 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (12). — One of this dimension's main actionable groups (12 warning-level).
Resolve the 9 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (9). — One of this dimension's main actionable groups (9 issue-level).
Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)8.1 / 10Strong✓ Tool-verified
What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.
Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using our own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.
2 finding(s): 0 critical, 0 high, 2 medium, 0 low. semgrep could not parse 35 file(s) — `docs/next.config.ts`, `packages-internal/core-docs/src/AppLayout/components/Frame.tsx`, `packages-internal/core-docs/src/TableOfContents/MiniTableOfContents.tsx`, `packages/mui-icons-material/templateSvgIcon.js`, `packages/mui-lab/src/LoadingButton/index.ts`, … (+30 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
REDACTED
What to do
Resolve the 2 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d32_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.
72 of 496 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/mui-codemod/src/v5.0.0/jss-to-tss-react.js. Counted over 496 of the 2067 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 72 Orphaned file finding(s) in Knowledge Freshness — start with createTypeScriptProject.ts (2), jss-to-tss-react.js, index.js. — One of this dimension's main actionable groups (72 recommendation-level).
Resolve the 1 Orphaned files with no living knowledge 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 5 Change coupling finding(s) in Change Coupling — start with deprecations-all.js, BasePopper.tsx, HeaderNavBar.tsx. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 2 Change coupling clique finding(s) in Change Coupling — start with ExpandableApiItem.tsx, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with ClickAwayListener.tsx. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. 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 0 platform declaration(s) and 3 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
Do you agree with this assessment?
AC2 · Forms & labels2.9 / 10Weak✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×4) — docs/pages/experiments/website/dashboard-template-theme.tsx:221, docs/pages/experiments/website/dashboard-template-theme.tsx:222, docs/src/pages/premium-themes/onepirate/modules/views/ProductCTA.tsx:42, …
This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×4) — docs/src/components/productX/XGridFullDemo.tsx:88, docs/src/components/productX/XGridFullDemo.tsx:95, docs/src/components/productX/XGridFullDemo.tsx:109, …
This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×3) — docs/src/components/showcase/ThemeSlider.tsx:31, docs/src/components/x-grid/EditProgress.tsx:55, docs/src/components/x-grid/EditStatus.tsx:36
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.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.GalleryMenu-listbox` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — docs/public/static/components-gallery/base-theme.css:417
`.GalleryNumberInput.base--focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — docs/public/static/components-gallery/base-theme.css:475
`.GalleryNumberInput .input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — docs/public/static/components-gallery/base-theme.css:487
`.GalleryNumberInput .input:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — docs/public/static/components-gallery/base-theme.css:495
`.GallerySelect.base--focusVisible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — docs/public/static/components-gallery/base-theme.css:598
`.GallerySelect-listbox` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — docs/public/static/components-gallery/base-theme.css:625
`.GallerySlider.base--disabled` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — docs/public/static/components-gallery/base-theme.css:701
`&:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — packages-internal/core-docs/src/branding/brandingTheme.ts:1018, packages-internal/core-docs/src/TableOfContents/MiniTableOfContents.tsx:60
`.GallerySlider-thumb` moves (`transition-property: box-shadow, transform`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — docs/public/static/components-gallery/base-theme.css:732
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · 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.
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.
`deleteOne` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×2) — docs/data/material/getting-started/templates/crud-dashboard/data/employees.js:153, docs/data/material/getting-started/templates/crud-dashboard/data/employees.ts:164
Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. — docs/src/components/customers/CustomersSpotlight.tsx:35
A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. (×2) — packages/mui-material/src/useLazyRipple/useLazyRipple.ts:36, packages/mui-utils/src/ponyfillGlobal/ponyfillGlobal.ts:1
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×2) — test/e2e-website/material-docs.spec.ts:36, test/regressions/index.test.js:626
What to do
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
Maturity · Maturity — Whether the 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
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
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.
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.
test/README.md names React 18, but the manifest declares `react` 19.3.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — test/README.md:268
docs/pages/customers/coupa.md names React 17, but the manifest declares `react` 19.3.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/pages/customers/coupa.md:58
What to do
Reconcile the README with reality: test/README.md names React 18, but the manifest declares `react` 19.3.1; docs/pages/customers/coupa.md names React 17, but the manifest declares `react` 19.3.1.
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 · Observability4.5 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 1/6 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `docs`, `packages-internal/core-docs`, `packages/mui-codemod`, `packages/mui-envinfo`, `packages/mui-material-nextjs`.
`netlify/functions/feedback-management.mts` reports through `console.*` at line 231 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — netlify/functions/feedback-management.mts:231
`netlify/functions/on-deploy.mts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — netlify/functions/on-deploy.mts:38
`netlify/functions/on-deploy.mts` reports through `console.*` at line 40 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — netlify/functions/on-deploy.mts:40
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
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.
`codeql.yml`, `scorecards.yml` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.
What to do
Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate.
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.
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.
`readFileSync` in `annotateComponentDefinition` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:88
`writeFileSync` in `annotateComponentDefinition` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:282
`readFileSync` in `annotateHookDefinition` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages-internal/api-docs-builder/src/ApiBuilders/HookApiBuilder.ts:39
`writeFileSync` in `annotateHookDefinition` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages-internal/api-docs-builder/src/ApiBuilders/HookApiBuilder.ts:230
`fs.writeFileSync` in `writePrettifiedFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages-internal/api-docs-builder/src/buildApiUtils.ts:56
`statSync` in `callback to extensions.find` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages-internal/markdown/loader.mjs:239
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety4.9 / 10Weak✓ 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.
1313 typed · 1364 plain JS — the untyped files are packages-internal/api-docs-builder/src/utils/replaceUrl.test.js, packages-internal/core-docs/src/DocsApp/VersionsContext.js, packages-internal/core-docs/src/findActivePage/findActivePage.test.js, packages-internal/core-docs/src/helpers/helpers.test.js, packages-internal/core-docs/src/utils/getProductInfoFromUrl.test.js, packages-internal/markdown/apiPageTranslationLoader.mjs (+1358 more). 0 production file(s) opt out entirely with @ts-nocheck · 3 @ts-ignore suppression(s).
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
210 duplicated blocks under packages/mui-material/src/ have copies in at least two of the sibling directories Accordion, AccordionActions, AccordionDetails, AccordionSummary, Alert, AlertTitle (+116 more sibling(s) not listed) — 104 of them are reported below, and 106 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 210 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 210 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 210 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/mui-material/src/ListItemButton/ListItemButton.js:40
38 duplicated blocks under packages/ have copies in at least two of the sibling directories mui-lab, mui-material, mui-material-nextjs, mui-styled-engine, mui-styled-engine-sc, mui-system (+2 more sibling(s) not listed) — 30 of them are reported below, and 8 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 38 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 38 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 38 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/mui-styled-engine-sc/src/index.ts:420
21 duplicated blocks under packages/mui-codemod/src/deprecations/ have copies in at least two of the sibling directories accordion-props, accordion-summary-classes, alert-classes, alert-props, autocomplete-props, avatar-group-props (+53 more sibling(s) not listed) — 16 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 21 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 21 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 21 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — REDACTED:7
15 duplicated blocks under packages/mui-codemod/src/ have copies in at least two of the sibling directories deprecations, util, v1.0.0, v4.0.0, v5.0.0, v6.0.0 (+2 more sibling(s) not listed) — 12 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 15 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/mui-codemod/src/v6.0.0/system-props/removeSystemProps.js:2
10 duplicated blocks under packages/mui-lab/src/ have copies in at least two of the sibling directories AdapterDateFns, AdapterDayjs, AdapterLuxon, AdapterMoment, CalendarPicker, CalendarPickerSkeleton (+30 more sibling(s) not listed) — 9 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/mui-lab/src/TimelineContent/TimelineContent.tsx:38
packages/mui-codemod/src/v6.0.0/system-props/removeSystemProps.js:2 · packages/mui-codemod/src/v9.0.0/system-props/removeSystemProps.js:2 — these 2 files are line-for-line copies of one another — 214 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/mui-codemod/src/v6.0.0/system-props/removeSystemProps.js:2
packages-internal/api-docs-builder/src/utils/getPropsFromComponentNode.ts:1 · packages-internal/docs-utils/src/getPropsFromComponentNode.ts:1 — these 2 files are line-for-line copies of one another — 183 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages-internal/api-docs-builder/src/utils/getPropsFromComponentNode.ts:1
packages/mui-material/src/ListItemButton/ListItemButton.js:40 · packages/mui-material/src/MenuItem/MenuItem.js:44 — the two spans are one implementation copied and then locally edited — 908 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/mui-material/src/ListItemButton/ListItemButton.js:40
packages/mui-material/src/ButtonGroup/ButtonGroup.js:17 · packages/mui-material/src/ToggleButtonGroup/ToggleButtonGroup.js:38 — the two spans are one implementation copied and then locally edited — 848 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/mui-material/src/ButtonGroup/ButtonGroup.js:17
packages/mui-codemod/src/v6.0.0/grid-v2-props/grid-v2-props.js:2 · packages/mui-codemod/src/v7.0.0/grid-props/grid-props.js:2 — these 2 files are line-for-line copies of one another — 139 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/mui-codemod/src/v6.0.0/grid-v2-props/grid-v2-props.js:2
packages/mui-codemod/src/util/migrateToVariants.js:426 · packages/mui-codemod/src/v6.0.0/sx-prop/sx-v6.js:262 — the two spans are one implementation copied and then locally edited — 912 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/mui-codemod/src/util/migrateToVariants.js:426
packages/mui-material/src/Checkbox/Checkbox.js:55 · packages/mui-material/src/Radio/Radio.js:45 — the two spans are one implementation copied and then locally edited — 731 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/mui-material/src/Checkbox/Checkbox.js:55
packages/mui-material/src/Fade/Fade.js:2 · packages/mui-material/src/Zoom/Zoom.js:2 — these 2 files are line-for-line copies of one another — 115 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/mui-material/src/Fade/Fade.js:2
REDACTED:7 · REDACTED:7 · REDACTED:7 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — REDACTED:7
REDACTED:96 · REDACTED:120 — the two spans are one implementation copied and then locally edited — 481 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. — REDACTED:96
packages/mui-material/src/styles/createThemeWithVars.js:299 · packages/mui-material/src/styles/createThemeWithVars.js:625 — 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. — packages/mui-material/src/styles/createThemeWithVars.js:299
packages/mui-material/src/ListItem/ListItem.js:16 · packages/mui-material/src/ListItemButton/ListItemButton.js:18 — the two spans are one implementation copied and then locally edited — 438 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/mui-material/src/ListItem/ListItem.js:16
packages/mui-material/src/Icon/Icon.js:13 · packages/mui-material/src/SvgIcon/SvgIcon.js:13 — the two spans are one implementation copied and then locally edited — 416 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/mui-material/src/Icon/Icon.js:13
REDACTED:5 · REDACTED:5 — the two spans are one implementation copied and then locally edited — 504 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. — REDACTED:5
REDACTED:31 · packages-internal/core-docs/src/ApiPage/HooksApiContent.tsx:23 — the two spans are one implementation copied and then locally edited — 451 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. — REDACTED:31
packages/mui-material/src/locale/hrHR.ts:4 · packages/mui-material/src/locale/srRS.ts:4 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — packages/mui-material/src/locale/hrHR.ts:4
REDACTED:7 · REDACTED:7 · REDACTED:7 · REDACTED:7 · +6 more site(s) not listed — the 10 copies are spread across 10 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:7
packages/mui-material/src/Popper/BasePopper.tsx:429 · packages/mui-material/src/Popper/Popper.tsx:136 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/mui-material/src/Popper/BasePopper.tsx:429
REDACTED:7 · REDACTED:7 — 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:7
packages/mui-material/src/locale/arEG.ts:4 · packages/mui-material/src/locale/arSA.ts:4 · packages/mui-material/src/locale/arSD.ts:4 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — packages/mui-material/src/locale/arEG.ts:4
packages-internal/api-docs-builder/src/utils/createTypeScriptProject.ts:1 · packages-internal/docs-utils/src/createTypeScriptProject.ts:1 — these 2 files are line-for-line copies of one another — 66 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages-internal/api-docs-builder/src/utils/createTypeScriptProject.ts:1
REDACTED:13 · REDACTED:9 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — REDACTED:13
packages/mui-styled-engine-sc/src/index.ts:420 · packages/mui-styled-engine/src/index.ts:240 — 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. — packages/mui-styled-engine-sc/src/index.ts:420
packages/mui-lab/src/TimelineContent/TimelineContent.tsx:38 · packages/mui-lab/src/TimelineOppositeContent/TimelineOppositeContent.tsx:41 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/mui-lab/src/TimelineContent/TimelineContent.tsx:38
packages/mui-codemod/src/deprecations/utils/movePropIntoSlotProps.js:6 · packages/mui-codemod/src/deprecations/utils/movePropIntoSlots.js:6 — the two spans are one implementation copied and then locally edited — 421 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/mui-codemod/src/deprecations/utils/movePropIntoSlotProps.js:6
packages/mui-material/src/FilledInput/FilledInput.js:290 · packages/mui-material/src/Input/Input.js:187 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/mui-material/src/FilledInput/FilledInput.js:290
packages/mui-codemod/src/deprecations/all/deprecations-all.js:62 · packages/mui-codemod/src/v5.0.0/preset-safe.js:56 — the two spans are one implementation copied and then locally edited — 664 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/mui-codemod/src/deprecations/all/deprecations-all.js:62
packages-internal/core-docs/src/codeStyling/codeStyling.tsx:5 · packages-internal/core-docs/src/codeVariant/codeVariant.tsx:5 — the two spans are one implementation copied and then locally edited — 327 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages-internal/core-docs/src/codeStyling/codeStyling.tsx:5
packages/mui-material/src/Grid/Grid.tsx:151 · packages/mui-system/src/Grid/Grid.tsx:14 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/mui-material/src/Grid/Grid.tsx:151
packages/mui-material/src/PigmentGrid/PigmentGrid.tsx:144 · packages/mui-system/src/Grid/createGrid.tsx:190 — the two spans are one implementation copied and then locally edited — 321 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/mui-material/src/PigmentGrid/PigmentGrid.tsx:144
packages/mui-material/src/locale/plPL.ts:4 · packages/mui-material/src/locale/ruRU.ts:4 · packages/mui-material/src/locale/ukUA.ts:4 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/mui-material/src/locale/plPL.ts:4
REDACTED:7 · REDACTED:7 — 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:7
packages/mui-material/src/FilledInput/FilledInput.js:37 · packages/mui-material/src/Input/Input.js:28 — the two spans are one implementation copied and then locally edited — 267 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/mui-material/src/FilledInput/FilledInput.js:37
packages/mui-material/src/locale/csCZ.ts:4 · packages/mui-material/src/locale/skSK.ts:4 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/mui-material/src/locale/csCZ.ts:4
REDACTED:79 · packages-internal/api-docs-builder/src/ApiBuilders/HookApiBuilder.ts:30 — 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. — REDACTED:79
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.
scripts/a11yScorecard/rollup.mjs:1 imports test/regressions/a11y/criteriaSuites.mjs, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — scripts/a11yScorecard/rollup.mjs:1
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 80 and cognitive complexity 103; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mui-material/src/useAutocomplete/useAutocomplete.js:995
(anonymous) has cyclomatic complexity 71 and cognitive complexity 134; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mui-material/src/styles/createThemeWithVars.js:236
recurseObjectExpression has cyclomatic complexity 62 and cognitive complexity 137; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mui-codemod/src/v6.0.0/sx-prop/sx-v6.js:180
checkType has cyclomatic complexity 53 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages-internal/scripts/typescript-to-proptypes/src/getPropTypesFromFile.ts:248
root has cyclomatic complexity 52 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages-internal/core-docs/src/branding/brandingTheme.ts:1103
root has cyclomatic complexity 52 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages-internal/core-docs/src/branding/brandingTheme.ts:550
DemoContent has cyclomatic complexity 47 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages-internal/core-docs/src/DemoContent/DemoContent.tsx:87
recurseObjectExpression has cyclomatic complexity 44 and cognitive complexity 93; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mui-codemod/src/util/migrateToVariants.js:413
Demo has cyclomatic complexity 41 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages-internal/core-docs/src/Demo/Demo.tsx:408
Autocomplete has cyclomatic complexity 41 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mui-material/src/Autocomplete/Autocomplete.js:432
(anonymous) has cyclomatic complexity 36 and cognitive complexity 57; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mui-material/src/SwipeableDrawer/SwipeableDrawer.js:347
LinearProgress has cyclomatic complexity 34 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mui-material/src/LinearProgress/LinearProgress.js:421
(anonymous) has cyclomatic complexity 33 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:428
generatePropType has cyclomatic complexity 31 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages-internal/scripts/typescript-to-proptypes/src/generatePropTypes.ts:131
SelectInput has cyclomatic complexity 31 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mui-material/src/Select/SelectInput.js:146
(anonymous) has cyclomatic complexity 31 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mui-material/src/Chip/Chip.js:66
validateSource has cyclomatic complexity 29 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/a11yScorecard/validate.mjs:119
buildLlmsDocs has cyclomatic complexity 28 and cognitive complexity 51; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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. — scripts/buildLlmsDocs/index.ts:461
TablePaginationActions has cyclomatic complexity 28 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mui-material/src/TablePaginationActions/TablePaginationActions.js:59
Chip has cyclomatic complexity 27 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. — packages/mui-material/src/Chip/Chip.js:379
createTheme has cyclomatic complexity 26 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mui-material/src/styles/createTheme.ts:65
CssVarsProvider has cyclomatic complexity 26 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mui-system/src/cssVars/createCssVarsProvider.tsx:216
Tooltip has cyclomatic complexity 25 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mui-material/src/Tooltip/Tooltip.js:237
(anonymous) has cyclomatic complexity 25 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages-internal/core-docs/src/AppLayout/navigation/AppNavDrawerItem.tsx:27
DemoContentLoading has cyclomatic complexity 24 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. — packages-internal/core-docs/src/DemoContent/DemoContentLoading.tsx:35
resolveProps has cyclomatic complexity 23 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mui-utils/src/resolveProps/resolveProps.ts:12
selectNewValue has cyclomatic complexity 23 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mui-material/src/useAutocomplete/useAutocomplete.js:854
(anonymous) has cyclomatic complexity 23 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mui-codemod/src/v5.0.0/base-remove-component-prop.js:25
processApiJson has cyclomatic complexity 23 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. — packages-internal/scripts/generate-llms-txt/src/processApi.ts:239
(anonymous) has cyclomatic complexity 23 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mui-material/src/Button/Button.js:95
(anonymous) has cyclomatic complexity 23 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mui-material/src/PaginationItem/PaginationItem.js:110
(anonymous) has cyclomatic complexity 22 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mui-material/src/Slider/useSlider.ts:394
checkSymbol has cyclomatic complexity 22 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. — packages-internal/scripts/typescript-to-proptypes/src/getPropTypesFromFile.ts:542
getPropsFromVariableDeclaration has cyclomatic complexity 22 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. (×2) — packages-internal/api-docs-builder/src/utils/getPropsFromComponentNode.ts:186, packages-internal/docs-utils/src/getPropsFromComponentNode.ts:184
TextField has cyclomatic complexity 22 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. — packages/mui-material/src/TextField/TextField.js:75
useAutocomplete has cyclomatic complexity 22 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mui-material/src/useAutocomplete/useAutocomplete.js:97
(anonymous) has cyclomatic complexity 22 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. — REDACTED:522
handleClosedTypeahead has cyclomatic complexity 22 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mui-material/src/Select/SelectInput.js:550
Tabs has cyclomatic complexity 21 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. — packages/mui-material/src/Tabs/Tabs.js:257
Do you agree with this assessment?
R3 · Large Files8.7 / 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.
packages-internal/core-docs/src/branding/brandingTheme.ts has 1590 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages-internal/core-docs/src/branding/brandingTheme.ts:1
packages/mui-material/src/useAutocomplete/useAutocomplete.js has 1422 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-material/src/useAutocomplete/useAutocomplete.js:1
packages/mui-material/src/Autocomplete/Autocomplete.js has 1289 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-material/src/Autocomplete/Autocomplete.js:1
packages/mui-material/src/Slider/Slider.js has 1043 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-material/src/Slider/Slider.js:1
packages/mui-material/src/styles/createThemeWithVars.js has 1006 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-material/src/styles/createThemeWithVars.js:1
packages/mui-material/src/Tabs/Tabs.js has 986 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-material/src/Tabs/Tabs.js:1
packages/mui-material/src/Select/SelectInput.js has 971 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-material/src/Select/SelectInput.js:1
packages-internal/core-docs/src/MarkdownDocs/MarkdownElement.tsx has 864 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages-internal/core-docs/src/MarkdownDocs/MarkdownElement.tsx:1
REDACTED has 859 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
REDACTED has 813 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
packages/mui-material/src/Slider/useSlider.ts has 809 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-material/src/Slider/useSlider.ts:1
packages/mui-material/src/Tooltip/Tooltip.js has 794 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-material/src/Tooltip/Tooltip.js:1
packages-internal/scripts/typescript-to-proptypes/src/getPropTypesFromFile.ts has 783 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages-internal/scripts/typescript-to-proptypes/src/getPropTypesFromFile.ts:1
packages/mui-material/src/Rating/Rating.js has 780 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-material/src/Rating/Rating.js:1
packages/mui-material/src/InputBase/InputBase.js has 767 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-material/src/InputBase/InputBase.js:1
packages/mui-utils/src/useRovingTabIndex/useRovingTabIndex.ts has 736 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-utils/src/useRovingTabIndex/useRovingTabIndex.ts:1
packages/mui-material/src/Button/Button.js has 716 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-material/src/Button/Button.js:1
packages/mui-material/src/SwipeableDrawer/SwipeableDrawer.js has 695 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-material/src/SwipeableDrawer/SwipeableDrawer.js:1
packages-internal/core-docs/src/DemoContent/DemoContainer.tsx has 666 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages-internal/core-docs/src/DemoContent/DemoContainer.tsx:1
packages/mui-material/src/Chip/Chip.js has 660 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-material/src/Chip/Chip.js:1
packages-internal/markdown/loader.mjs has 658 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages-internal/markdown/loader.mjs:1
packages/mui-codemod/src/util/migrateToVariants.js has 651 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-codemod/src/util/migrateToVariants.js:1
packages-internal/core-docs/src/DemoContent/DemoToolbar.tsx has 614 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages-internal/core-docs/src/DemoContent/DemoToolbar.tsx:1
packages/mui-material/src/styles/enhanceHighContrast.ts has 613 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-material/src/styles/enhanceHighContrast.ts:1
packages/mui-codemod/src/v6.0.0/theme-v6/test-cases/basicTheme.expected.js has 603 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-codemod/src/v6.0.0/theme-v6/test-cases/basicTheme.expected.js:1
scripts/buildLlmsDocs/index.ts has 600 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — scripts/buildLlmsDocs/index.ts:1
packages/mui-material/src/Popover/Popover.js has 592 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-material/src/Popover/Popover.js:1
packages/mui-codemod/src/v5.0.0/jss-to-styled.js has 589 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-codemod/src/v5.0.0/jss-to-styled.js:1
packages/mui-material/src/LinearProgress/LinearProgress.js has 570 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-material/src/LinearProgress/LinearProgress.js:1
packages/mui-codemod/src/v5.0.0/theme-spacing.test/large-actual.js has 567 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-codemod/src/v5.0.0/theme-spacing.test/large-actual.js:1
packages/mui-codemod/src/v5.0.0/theme-spacing.test/large-expected.js has 567 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-codemod/src/v5.0.0/theme-spacing.test/large-expected.js:1
packages/mui-system/src/cssVars/createCssVarsProvider.tsx has 546 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-system/src/cssVars/createCssVarsProvider.tsx:1
packages/mui-material/src/SpeedDial/SpeedDial.js has 542 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-material/src/SpeedDial/SpeedDial.js:1
packages-internal/core-docs/src/DemoContent/DemoContent.tsx has 519 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages-internal/core-docs/src/DemoContent/DemoContent.tsx:1
packages/mui-codemod/src/v6.0.0/theme-v6/test-cases/basicTheme.actual.js has 513 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-codemod/src/v6.0.0/theme-v6/test-cases/basicTheme.actual.js:1
packages/mui-codemod/src/v6.0.0/sx-prop/sx-v6.js has 510 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-codemod/src/v6.0.0/sx-prop/sx-v6.js:1
packages/mui-material/src/Popper/BasePopper.tsx has 510 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-material/src/Popper/BasePopper.tsx:1
packages/mui-material/src/PaginationItem/PaginationItem.js has 504 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-material/src/PaginationItem/PaginationItem.js:1
packages/mui-material/src/internal/Transition.tsx has 498 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-material/src/internal/Transition.tsx:1
packages/mui-material/src/TablePagination/TablePagination.js has 492 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mui-material/src/TablePagination/TablePagination.js: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 Coverage9.6 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
packages/mui-codemod/src/v5.0.0/adapter-v4.test/no-styles-import.actual.js:1 imports '../other-path', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/mui-codemod/src/v5.0.0/adapter-v4.test/no-styles-import.actual.js:1
packages/mui-codemod/src/v5.0.0/adapter-v4.test/no-styles-import.expected.js:1 imports '../other-path', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/mui-codemod/src/v5.0.0/adapter-v4.test/no-styles-import.expected.js:1
packages/mui-codemod/src/v5.0.0/grid-list-component.test/actual.js:5 imports './other', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/mui-codemod/src/v5.0.0/grid-list-component.test/actual.js:5
packages/mui-codemod/src/v5.0.0/grid-list-component.test/expected.js:5 imports './other', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/mui-codemod/src/v5.0.0/grid-list-component.test/expected.js:5
packages/mui-codemod/src/v5.0.0/styled-engine-provider.test/mui-theme-provider.actual.js:3 imports './contexts', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/mui-codemod/src/v5.0.0/styled-engine-provider.test/mui-theme-provider.actual.js:3
packages/mui-codemod/src/v5.0.0/styled-engine-provider.test/mui-theme-provider.expected.js:3 imports './contexts', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/mui-codemod/src/v5.0.0/styled-engine-provider.test/mui-theme-provider.expected.js:3
packages/mui-codemod/src/v5.0.0/styled-engine-provider.test/theme-provider.actual.js:3 imports './contexts', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/mui-codemod/src/v5.0.0/styled-engine-provider.test/theme-provider.actual.js:3
packages/mui-codemod/src/v5.0.0/styled-engine-provider.test/theme-provider.expected.js:3 imports './contexts', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/mui-codemod/src/v5.0.0/styled-engine-provider.test/theme-provider.expected.js:3
packages/mui-icons-material/fixtures/material-design-icons/expected/AccessAlarms.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/mui-icons-material/fixtures/material-design-icons/expected/AccessAlarms.js:2
packages/mui-icons-material/fixtures/material-design-icons/expected/AccessAlarmsTwoTone.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/mui-icons-material/fixtures/material-design-icons/expected/AccessAlarmsTwoTone.js:2
packages/mui-icons-material/fixtures/material-design-icons/expected/Accessibility.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/mui-icons-material/fixtures/material-design-icons/expected/Accessibility.js:2
packages/mui-icons-material/fixtures/material-design-icons/expected/ElevenMp.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/mui-icons-material/fixtures/material-design-icons/expected/ElevenMp.js:2
packages/mui-icons-material/fixtures/material-design-icons/expected/FiveMp.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/mui-icons-material/fixtures/material-design-icons/expected/FiveMp.js:2
packages/mui-icons-material/fixtures/material-design-icons/expected/QueueMusicOutlined.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/mui-icons-material/fixtures/material-design-icons/expected/QueueMusicOutlined.js:2
packages/mui-icons-material/fixtures/material-design-icons/expected/RecordVoiceOverTwoTone.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/mui-icons-material/fixtures/material-design-icons/expected/RecordVoiceOverTwoTone.js:2
packages/mui-icons-material/fixtures/material-design-icons/expected/SixtyFps.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/mui-icons-material/fixtures/material-design-icons/expected/SixtyFps.js:2
packages/mui-icons-material/fixtures/material-design-icons/expected/StarRounded.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/mui-icons-material/fixtures/material-design-icons/expected/StarRounded.js:2
packages/mui-icons-material/fixtures/material-design-icons/expected/ThirtyFps.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/mui-icons-material/fixtures/material-design-icons/expected/ThirtyFps.js:2
packages/mui-icons-material/fixtures/material-design-icons/expected/TimesOneMobiledata.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/mui-icons-material/fixtures/material-design-icons/expected/TimesOneMobiledata.js:2
packages/mui-icons-material/fixtures/material-design-icons/expected/TwentyFourMp.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/mui-icons-material/fixtures/material-design-icons/expected/TwentyFourMp.js:2
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. (×20) — packages-internal/markdown/loader.mjs:1, netlify/edge-functions/og-image.tsx:1, netlify/functions/feedback-management.mts:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
This repository declares test tooling, and the ✓ above records that declaration — but packages/mui-codemod/src/v5.0.0/adapter-v4.test/no-styles-import.actual.js and 19 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — packages/mui-codemod/src/v5.0.0/adapter-v4.test/no-styles-import.actual.js:1
Do you agree with this assessment?
R7 · Dead Code7.9 / 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.
1 file(s) (~27 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an REDACTED script) so reachability can see this package. — test/bundle-size
3 file(s) (~1741 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an REDACTED script) so reachability can see this package. — test/bundling/scripts
1 file(s) (~12 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an REDACTED script) so reachability can see this package. — test/moduleResolution
2 file(s) (~33 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an REDACTED script) so reachability can see this package. — test/typescriptMinimum
Unreachable from the 509 application, 370 tooling and 1594 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (509 application, 370 tooling, 1594 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 (×29) — netlify/functions/feedback-management.mts, netlify/functions/on-deploy.mts, packages-internal/core-docs/src/AppLayout/components/ArrowButton.tsx, …
no import path from any entry point (509 application, 370 tooling, 1594 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/mui-codemod/src/deprecations/all/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/mui-codemod/src/deprecations/all/deprecations-all.js
no import path from any entry point (509 application, 370 tooling, 1594 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/mui-codemod/src/v7.0.0/all/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/mui-codemod/src/v7.0.0/all/v7-all.js
no import path from any entry point (509 application, 370 tooling, 1594 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/mui-codemod/src/v6.0.0/all/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/mui-codemod/src/v6.0.0/all/v6-all.js
no import path from any entry point (509 application, 370 tooling, 1594 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/mui-codemod/src/deprecations/all/deprecations-all.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 (×3) — packages/mui-codemod/src/deprecations/accordion-props/index.js, packages/mui-codemod/src/deprecations/accordion-summary-classes/index.js, packages/mui-codemod/src/deprecations/alert-classes/index.js
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported 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. (×3) — packages-internal/markdown/loader.mjs:117, packages/mui-codemod/src/util/appendAttribute.js:3, test/e2e-website/demo-docs-production.baseline.ts:5
Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×9) — packages/mui-codemod/src/v5.0.0/theme-spacing.test/large-actual.js:8, packages/mui-codemod/src/v5.0.0/emotion-prepend-cache.test/custom-naming.actual.js:1, packages/mui-codemod/src/v5.0.0/jss-to-styled.test/Anonymous.actual.js:2, …
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. (×8)
Declared in packages/mui-lab/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.
Every import is type-only — move it to devDependencies. (×5) — netlify/functions/feedback-management.mts:4, packages/mui-styled-engine/src/index.ts:6, packages/mui-styled-engine-sc/src/index.ts:4, …
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.
REDACTED → packages-internal/api-docs-builder/src/buildApi.ts → REDACTED (one verified cycle inside a mutually-dependent group of 6 files) — REDACTED:12
Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
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.
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — netlify.toml:1
What to do
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `REDACTED` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
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 document2.7 / 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.
`deepmerge` is exported and takes `source: unknown` from its caller, and it calls itself at line 74 (`deepmerge`) with a piece of `source` — and nowhere in `deepmerge` 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 `deepmerge` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/mui-utils/src/deepmerge/deepmerge.ts:74
`stringifyTheme` is exported, takes a document from its caller (line 34) and hands it to `serializeTheme`, which calls itself at line 46 (`serializeTheme`) with a piece of `object` — and nowhere in `serializeTheme` 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 `serializeTheme` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/mui-material/src/styles/stringifyTheme.ts:46
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 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/8 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.
`defaultFetchNotifications` 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 })`. — packages-internal/core-docs/src/DocsProvider/DocsProvider.tsx:18
`defaultFetchVersions` 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 })`. — packages-internal/core-docs/src/DocsProvider/DocsProvider.tsx:28
`submitFeedback` 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 })`. — packages-internal/core-docs/src/AppLayout/layout/AppLayoutDocsFooter.tsx:70
`tryFetch` 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 })`. — packages-internal/core-docs/src/Ad/AdCarbon.tsx:78
`run` 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 })`. (×3) — packages/mui-icons-material/scripts/download.mjs:178, docs/scripts/syncTeamMembers.ts:73, docs/scripts/updateIconSynonyms.js:26
`handler` holds an AbortSignal but calls `fetch(…)` without it, so its caller's cancellation never reaches that call and it runs to its end after whatever wanted it has given up. Hand the signal on: `fetch(…, { signal })`. — netlify/edge-functions/og-image.tsx:49
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.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped2.9 / 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.
`deprecationInfo||t('api-docs.defaultDeprecationMessage')` 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:212
`demos` 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:232
`t('api-docs.importDifference')` 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. (×3) — REDACTED:244, REDACTED:144, packages-internal/core-docs/src/ApiPage/HooksApiContent.tsx:77
`componentDescription` 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:252
`refHint` 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. (×2) — REDACTED:265, REDACTED:161
`t('api-docs.inheritanceDescription').replace(/{{component}}/,inheritance.component).replace(/{{pathname}}/,inheritanc…` 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. (×2) — REDACTED:277, REDACTED:177
`t('api-docs.themeDefaultPropsDescription').replace(/{{muiName}}/,pageContent.muiName).replace(/{{defaultPropsLink}}/,…` 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. (×2) — REDACTED:291, REDACTED:195
`t('api-docs.seeSourceCode').replace('{{href}}',`${process.env.SOURCE_CODE_REPO}/blob/v${process.env.LIB_VERSION}${pag…` 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:317
`description` 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. (×4) — packages-internal/core-docs/src/ApiPage/list/ClassesList.tsx:82, REDACTED:104, REDACTED:70, …
`deprecationInfo` 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. (×4) — packages-internal/core-docs/src/ApiPage/list/ClassesList.tsx:98, REDACTED:273, packages-internal/core-docs/src/ApiPage/table/ClassesTable.tsx:97, …
`seeMoreDescription` 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. (×2) — REDACTED:173, REDACTED:217
`t('api-docs.requires-ref')` 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. (×2) — REDACTED:178, REDACTED:234
`t(`api-docs.additional-info.${key}`)!` 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:188
`typeName` 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. (×2) — REDACTED:199, REDACTED:199
`signature` 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:216
`argTypeDescription` 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:233
`argDescription` 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:243
`signatureReturnDescription` 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:256
``.${className}`` 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:79
`spreadHint` 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. (×3) — REDACTED:88, REDACTED:92, REDACTED:74
`t('api-docs.overrideStyles')` 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:101
`t('api-docs.overrideStylesStyledComponent').replace(/{{styleOverridesLink}}/,styleOverridesLink,)` 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:104
`description||''` 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. — packages-internal/core-docs/src/ApiPage/table/ClassesTable.tsx:86
`t(`api-docs.additional-info.${key}`)` 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:226
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.
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. (×20) — packages-internal/markdown/loader.mjs:352, packages-internal/markdown/loader.mjs:379, packages-internal/markdown/loader.mjs:406, …
`.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. — packages-internal/core-docs/src/DemoContent/DemoContentLoading.tsx:49
`catch` 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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. — packages/mui-utils/src/useLocalStorageState/useLocalStorageState.ts:79
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
61/62 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
~1.0 `!` null assertions per 1k TypeScript source lines — 109 assertion(s) across the 112070 source line(s) of the 1294 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: REDACTED (7), packages-internal/api-docs-builder/src/utils/getPropsFromComponentNode.ts (5), packages-internal/core-docs/src/MarkdownDocs/RichMarkdownElement.tsx (5). 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 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
SC1 Supply-chain hygiene — 16 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 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.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 50 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.
AC4 Keyboard semantics — AC4 could not be measured here. This repository renders user interface from HTML strings built in plain scripts — at least 9 script file(s) building 29 markup element(s) as HTML strings, carrying 0 role/aria/tabindex attribute(s) (e.g. packages-internal/core-docs/src/svgIcons/BaseUiLogoIcon.tsx, packages-internal/core-docs/src/svgIcons/MuiLogomarkIcon.tsx, packages-internal/core-docs/src/NextNProgressBar/NProgressBar.tsx) — which this analyzer's markup model does not read (it reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs), so no interactive element from it could enter the population. The parsed markup carried none either, but that is a gap in our frontend coverage, NOT a statement that this repository has no interactive element.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> start / > pnpm install && pnpm docs:dev / sh: 1: pnpm: not found" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
D11 Test Reliability — Test reliability not included
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# only; the exposed JavaScript, TypeScript surface was not measured.
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D4 Code Duplication — This repository's production source (.mts, .ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
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'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage data present for 863 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not 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.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Banned license: @img/sharp-libvips-darwin-arm64 REDACTED:3285— `@img/sharp-libvips-darwin-arm64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-darwin-x64 REDACTED:3290— `@img/sharp-libvips-darwin-x64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-arm REDACTED:3301— `@img/sharp-libvips-linux-arm` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-arm64 REDACTED:3295— `@img/sharp-libvips-linux-arm64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-ppc64 REDACTED:3307— `@img/sharp-libvips-linux-ppc64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-riscv64 REDACTED:3313— `@img/sharp-libvips-linux-riscv64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-s390x REDACTED:3319— `@img/sharp-libvips-linux-s390x` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-x64 REDACTED:3325— `@img/sharp-libvips-linux-x64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linuxmusl-arm64 REDACTED:3331— `@img/sharp-libvips-linuxmusl-arm64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linuxmusl-x64 REDACTED:3337— `@img/sharp-libvips-linuxmusl-x64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-wasm32 REDACTED:3399— `@img/sharp-wasm32` 0.35.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later AND MIT`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-win32-arm64 REDACTED:3408— `@img/sharp-win32-arm64` 0.35.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-win32-ia32 REDACTED:3414— `@img/sharp-win32-ia32` 0.35.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-win32-x64 REDACTED:3420— `@img/sharp-win32-x64` 0.35.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
D10 · Test Quality· No assertions (empty test) · ×5
No assertions (empty test): removes event listeners on unmount packages/mui-material/src/SwipeableDrawer/SwipeableDrawer.test.js:524— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): does not crash when updating the parent component while swiping packages/mui-material/src/SwipeableDrawer/SwipeableDrawer.test.js:887— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): does not crash when backdrop is hidden while swiping packages/mui-material/src/SwipeableDrawer/SwipeableDrawer.test.js:918— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): should not leak on multi-touch packages/mui-material/src/ButtonBase/TouchRipple.test.js:425— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): To do packages/mui-lab/src/AlertTitle/AlertTitle.test.js:4— Test method has an empty body — it asserts nothing and exercises no code.
Unlisted import '@docsearch/react' packages/mui-codemod/src/v5.0.0/theme-spacing.test/large-actual.js:8— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@emotion/cache' packages/mui-codemod/src/v5.0.0/emotion-prepend-cache.test/custom-naming.actual.js:1— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@material-ui/styles' packages/mui-codemod/src/v5.0.0/jss-to-styled.test/Anonymous.actual.js:2— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@mui/x-date-pickers' packages/mui-codemod/src/v5.0.0/date-pickers-moved-to-x.test/expected-root-community.js:1— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@mui/x-date-pickers-pro' packages/mui-codemod/src/v5.0.0/date-pickers-moved-to-x.test/expected-root-pro.js:1— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@mui/x-tree-view' packages/mui-codemod/src/v5.0.0/tree-view-moved-to-x.test/expected-root.js:1— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'clsx' packages/mui-codemod/src/v5.0.0/jss-to-styled.test/first.actual.js:3— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'next' packages/mui-codemod/src/v5.0.0/theme-spacing.test/large-actual.js:6— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'prop-types' packages/mui-codemod/src/v5.0.0/jss-to-styled.test/first.actual.js:2— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
FunctionTooLong: useAutocomplete.useAutocomplete packages/mui-material/src/useAutocomplete/useAutocomplete.js:97— FunctionTooLong — useAutocomplete runs 926 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 826 over it, 9.26× 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: brandingTheme.getThemedComponents packages-internal/core-docs/src/branding/brandingTheme.ts:431— FunctionTooLong — getThemedComponents runs 823 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 723 over it, 8.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: createThemeWithVars.createThemeWithVars packages/mui-material/src/styles/createThemeWithVars.js:138— FunctionTooLong — createThemeWithVars runs 690 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 590 over it, 6.90× 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: PricingTable.PricingTable docs/src/components/pricing/PricingTable.tsx:1494— FunctionTooLong — PricingTable runs 563 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 463 over it, 5.63× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: SelectInput.SelectInput packages/mui-material/src/Select/SelectInput.js:146— FunctionTooLong — SelectInput runs 521 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 421 over it, 5.21× 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: useSlider.useSlider packages/mui-material/src/Slider/useSlider.ts:203— FunctionTooLong — useSlider runs 471 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 371 over it, 4.71× 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: AppSearch.AppSearch REDACTED:219— FunctionTooLong — AppSearch runs 434 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 334 over it, 4.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: jss-to-styled.transformer packages/mui-codemod/src/v5.0.0/jss-to-styled.js:7— FunctionTooLong — transformer runs 369 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 269 over it, 3.69× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: Autocomplete.Autocomplete packages/mui-material/src/Autocomplete/Autocomplete.js:432— FunctionTooLong — Autocomplete runs 338 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 238 over it, 3.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: migrateToVariants.migrateToVariants packages/mui-codemod/src/util/migrateToVariants.js:182— FunctionTooLong — migrateToVariants 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: DemoToolbar.DemoToolbar packages-internal/core-docs/src/DemoContent/DemoToolbar.tsx:275— FunctionTooLong — DemoToolbar runs 328 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 228 over it, 3.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: SwipeableDrawer.SwipeableDrawer packages/mui-material/src/SwipeableDrawer/SwipeableDrawer.js:139— FunctionTooLong — SwipeableDrawer runs 318 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 218 over it, 3.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: DemoContent.DemoContent packages-internal/core-docs/src/DemoContent/DemoContent.tsx:87— FunctionTooLong — DemoContent runs 311 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 211 over it, 3.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: MainContent.MainContent docs/data/material/getting-started/templates/blog/components/MainContent.tsx:167— FunctionTooLong — MainContent runs 310 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 210 over it, 3.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: MainContent.MainContent docs/data/material/getting-started/templates/blog/components/MainContent.js:177— FunctionTooLong — MainContent runs 309 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 209 over it, 3.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: Tooltip.Tooltip packages/mui-material/src/Tooltip/Tooltip.js:237— FunctionTooLong — Tooltip runs 304 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 204 over it, 3.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: AppLayoutDocsFooter.AppLayoutDocsFooter packages-internal/core-docs/src/AppLayout/layout/AppLayoutDocsFooter.tsx:143— FunctionTooLong — AppLayoutDocsFooter runs 296 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 196 over it, 2.96× 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: SyncFeatures.ConnectFeatures docs/src/components/productDesignKit/SyncFeatures.tsx:31— FunctionTooLong — ConnectFeatures runs 292 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 192 over it, 2.92× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: blog.Blog docs/pages/blog.tsx:187— FunctionTooLong — Blog runs 266 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 166 over it, 2.66× 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: MaterialHero.MaterialHero docs/src/components/productMaterial/MaterialHero.tsx:218— FunctionTooLong — MaterialHero runs 256 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 156 over it, 2.56× 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: Footer.Footer docs/data/material/getting-started/templates/blog/components/Footer.js:35— FunctionTooLong — Footer runs 252 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 152 over it, 2.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: Footer.Footer docs/data/material/getting-started/templates/blog/components/Footer.tsx:35— FunctionTooLong — Footer runs 252 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 152 over it, 2.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: XHero.XHero docs/src/components/productX/XHero.tsx:40— FunctionTooLong — XHero runs 251 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 151 over it, 2.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: InputBase.InputBase packages/mui-material/src/InputBase/InputBase.js:248— FunctionTooLong — InputBase 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: Footer.Footer docs/data/material/getting-started/templates/marketing-page/components/Footer.js:32— FunctionTooLong — Footer runs 245 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 145 over it, 2.45× 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.
TodoComment scripts/generateProptypes.ts:211— // TODO remove, should only have .types.ts — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages-internal/scripts/typescript-to-proptypes/src/getPropTypesFromFile.ts:711— // TODO: jsDoc from squashing is dropped — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages-internal/scripts/typescript-to-proptypes/src/injectPropTypesInFile.ts:285— // TODO: Not covered by a unit test but by e2e usage with the docs. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages-internal/core-docs/src/utils/getProductInfoFromUrl.ts:67— // TODO remove, legacy — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages-internal/core-docs/src/i18n/i18n.tsx:89— // TODO, migrate to use warnOnce() helper — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages-internal/core-docs/src/helpers/helpers.ts:31— // TODO remove post migration — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages-internal/core-docs/src/helpers/helpers.ts:36— // TODO support more than React component API (PascalCase) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages-internal/core-docs/src/branding/brandingTheme.ts:82— // TODO: enable this once types conflict is fixed — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages-internal/core-docs/src/branding/brandingTheme.ts:1577— // TODO add support for 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 packages-internal/core-docs/src/branding/BrandingCssVarsProvider.tsx:154— // TODO: remove `forceThemeRerender` once custom theme on some demos rely on CSS variables instead of `theme.palette.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 packages-internal/core-docs/src/ThemeContext/ThemeContext.tsx:141— // TODO replace with useColorScheme once all pages support css vars — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages-internal/core-docs/src/AppLayout/layout/AppSettingsDrawer.tsx:116— // TODO replace with useColorScheme once all pages support css vars — 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 docs/src/components/header/ThemeModeToggle.tsx:37— // TODO replace with useColorScheme once all pages support css vars — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages-internal/core-docs/src/ThemeContext/ThemeContext.tsx:197— // TODO: remove once all pages support css vars and replace call sites with useColorScheme() — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages-internal/core-docs/src/TableOfContents/TableOfContents.tsx:60— // TODO: We probably want `aria-current="location"` instead. — 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:67— // TODO migrate to .only-dark-mode to .only-dark-mode-v2 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages-internal/core-docs/src/DocsApp/createEmotionCache.ts:5— // TODO remove prepend: true once JSS is out — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages-internal/core-docs/src/Demo/ReactRunner.tsx:20— // TODO: uncomment once we enable eslint-plugin-react-compiler // eslint-disable-next-line react-compiler/react-compiler -- valid reason to disable the rules of hooks — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages-internal/core-docs/src/AppLayout/navigation/AppNavDrawer.tsx:30— // TODO: Collapse should expose an API to customize the duration based on the height. — 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 docs/src/components/pricing/PricingTable.tsx:25— // TODO: Collapse should expose an API to customize the duration based on the height. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages-internal/core-docs/src/AppLayout/navigation/AppNavDrawer.tsx:204— // TODO: uncomment once we enable eslint-plugin-react-compiler // eslint-disable-next-line react-compiler/react-compiler -- useEnhancedEffect uses useEffect under the hood — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages-internal/core-docs/src/ApiPage/sections/ToggleDisplayOption.tsx:45— // TODO: uncomment once we enable eslint-plugin-react-compiler // eslint-disable-next-line react-compiler/react-compiler -- useEnhancedEffect uses useEffect under the hood — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages-internal/core-docs/src/AppLayout/navigation/AppNavDrawer.tsx:217— // TODO have CssBaseline in the Next.js layout — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages-internal/core-docs/src/AppLayout/navigation/AppNavDrawer.tsx:241— // TODO have CssBaseline in the Next.js layout — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages-internal/core-docs/src/AppLayout/navigation/DiamondSponsors.tsx:9— // TODO have CssBaseline in the Next.js layout — 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.
No assertions: ${action} ${route} test/regressions/index.test.js:217— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should handle focus-visible correctly test/regressions/index.test.js:278— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should handle focus-visible with precise ratings correctly test/regressions/index.test.js:293— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render /regression-AppSearch/${fixture} correctly test/regressions/index.test.js:314— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should not close immediately when textbox expands test/regressions/index.test.js:406— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should style virtualized listbox correctly test/regressions/index.test.js:420— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render standard variant correctly in forced-colors mode test/regressions/index.test.js:433— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: keeps the outline ring visible in forced-colors mode test/regressions/index.test.js:451— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render standard variant correctly in forced-colors mode test/regressions/index.test.js:467— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should keep input caret position at the end when adding a newline test/regressions/index.test.js:483— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 1.4.12 Text Spacing: initials stay visible under the WCAG overrides test/regressions/index.test.js:513— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ${component} ${title} test/regressions/index.test.js:764— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: copies source from the active relative module tab test/e2e-website/demo-docs-production.baseline.ts:285— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: copies raw source from the toolbar test/e2e-website/demo-docs-production.baseline.ts:393— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: copies source from the active relative module tab test/e2e-website/demo-docs-production.spec.ts:325— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: copies raw source from the toolbar test/e2e-website/demo-docs-production.spec.ts:436— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should fire `onClick` when clicking on the focused label position test/e2e/index.test.ts:275— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: opens after Next.js %s navigation packages-internal/core-docs/src/DocsApp/AnalyticsProvider.test.tsx:148— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ignores falsy refs without errors packages/mui-utils/src/setRef/setRef.test.ts:26— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should support recursion packages/mui-system/src/createTheme/createSpacing.test.ts:24— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should not crash when the input ref is cleared before a pending highlighted index sync packages/mui-material/src/useAutocomplete/useAutocomplete.test.js:380— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should not attempt to focus nonexistent children packages/mui-material/src/Unstable_TrapFocus/FocusTrap.test.tsx:95— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should mount without any issue packages/mui-material/src/Tooltip/Tooltip.test.js:636— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should update height without an infinite rendering loop packages/mui-material/src/TextareaAutosize/TextareaAutosize.test.tsx:70— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should support empty children packages/mui-material/src/Tabs/Tabs.test.js:292— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
+ 31 more in this group — see findings.md.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×40
Untrusted text written into markup unescaped REDACTED:212— `deprecationInfo||t('api-docs.defaultDeprecationMessage')` 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:232— `demos` 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:244— `t('api-docs.importDifference')` 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:252— `componentDescription` 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:265— `refHint` 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:277— `t('api-docs.inheritanceDescription').replace(/{{component}}/,inheritance.component).replace(/{{pathname}}/,inheritanc…` 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:291— `t('api-docs.themeDefaultPropsDescription').replace(/{{muiName}}/,pageContent.muiName).replace(/{{defaultPropsLink}}/,…` 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:317— `t('api-docs.seeSourceCode').replace('{{href}}',`${process.env.SOURCE_CODE_REPO}/blob/v${process.env.LIB_VERSION}${pag…` 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:144— `t('api-docs.importDifference')` 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:161— `refHint` 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:177— `t('api-docs.inheritanceDescription').replace(/{{component}}/,inheritance.component).replace(/{{pathname}}/,inheritanc…` 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:195— `t('api-docs.themeDefaultPropsDescription').replace(/{{muiName}}/,pageContent.muiName).replace(/{{defaultPropsLink}}/,…` 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 packages-internal/core-docs/src/ApiPage/HooksApiContent.tsx:77— `t('api-docs.importDifference')` 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 packages-internal/core-docs/src/ApiPage/list/ClassesList.tsx:82— `description` 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 packages-internal/core-docs/src/ApiPage/list/ClassesList.tsx:98— `deprecationInfo` 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:104— `description` 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:173— `seeMoreDescription` 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:178— `t('api-docs.requires-ref')` 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:188— `t(`api-docs.additional-info.${key}`)!` 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:199— `typeName` 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:216— `signature` 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:233— `argTypeDescription` 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:243— `argDescription` 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:256— `signatureReturnDescription` 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:273— `deprecationInfo` 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.
Swallowed exception (empty catch) packages-internal/markdown/loader.mjs:352— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages-internal/markdown/loader.mjs:379— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages-internal/markdown/loader.mjs:406— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages-internal/markdown/loader.mjs:433— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages-internal/markdown/loader.mjs:450— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages-internal/markdown/loader.mjs:467— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages-internal/markdown/loader.mjs:479— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages-internal/markdown/loader.mjs:507— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages-internal/core-docs/src/DemoContent/useMuiChatExporter.ts:77— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages-internal/core-docs/src/DemoContent/DemoContentLoading.tsx:49— `.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.
Swallowed exception (empty catch) packages-internal/core-docs/src/DemoContent/DemoToolbar.tsx:368— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages-internal/core-docs/src/CodeCopy/CodeCopy.tsx:83— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages-internal/core-docs/src/ApiPage/sections/ToggleDisplayOption.tsx:64— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages-internal/api-docs-builder/src/utils/generateApiTranslation.ts:93— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/mui-utils/src/useIsFocusVisible/useIsFocusVisible.ts:108— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/mui-system/src/cssVars/localStorageManager.ts:48— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/mui-system/src/cssVars/localStorageManager.ts:57— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/mui-material/src/styles/createThemeNoVars.js:68— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/mui-material/src/styles/createThemeWithVars.js:91— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/mui-material/src/locale/utils/buildFormatNumber.ts:6— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/mui-material/src/Slider/useSlider.ts:789— 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.
R4 · Test Coverage· This test file cannot be loaded · ×20
This test file cannot be loaded packages/mui-codemod/src/v5.0.0/adapter-v4.test/no-styles-import.actual.js:1— packages/mui-codemod/src/v5.0.0/adapter-v4.test/no-styles-import.actual.js:1 imports '../other-path', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/mui-codemod/src/v5.0.0/adapter-v4.test/no-styles-import.expected.js:1— packages/mui-codemod/src/v5.0.0/adapter-v4.test/no-styles-import.expected.js:1 imports '../other-path', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/mui-codemod/src/v5.0.0/grid-list-component.test/actual.js:5— packages/mui-codemod/src/v5.0.0/grid-list-component.test/actual.js:5 imports './other', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/mui-codemod/src/v5.0.0/grid-list-component.test/expected.js:5— packages/mui-codemod/src/v5.0.0/grid-list-component.test/expected.js:5 imports './other', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/mui-codemod/src/v5.0.0/styled-engine-provider.test/mui-theme-provider.actual.js:3— packages/mui-codemod/src/v5.0.0/styled-engine-provider.test/mui-theme-provider.actual.js:3 imports './contexts', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/mui-codemod/src/v5.0.0/styled-engine-provider.test/mui-theme-provider.expected.js:3— packages/mui-codemod/src/v5.0.0/styled-engine-provider.test/mui-theme-provider.expected.js:3 imports './contexts', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/mui-codemod/src/v5.0.0/styled-engine-provider.test/theme-provider.actual.js:3— packages/mui-codemod/src/v5.0.0/styled-engine-provider.test/theme-provider.actual.js:3 imports './contexts', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/mui-codemod/src/v5.0.0/styled-engine-provider.test/theme-provider.expected.js:3— packages/mui-codemod/src/v5.0.0/styled-engine-provider.test/theme-provider.expected.js:3 imports './contexts', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/mui-icons-material/fixtures/material-design-icons/expected/AccessAlarms.js:2— packages/mui-icons-material/fixtures/material-design-icons/expected/AccessAlarms.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/mui-icons-material/fixtures/material-design-icons/expected/AccessAlarmsTwoTone.js:2— packages/mui-icons-material/fixtures/material-design-icons/expected/AccessAlarmsTwoTone.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/mui-icons-material/fixtures/material-design-icons/expected/Accessibility.js:2— packages/mui-icons-material/fixtures/material-design-icons/expected/Accessibility.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/mui-icons-material/fixtures/material-design-icons/expected/ElevenMp.js:2— packages/mui-icons-material/fixtures/material-design-icons/expected/ElevenMp.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/mui-icons-material/fixtures/material-design-icons/expected/FiveMp.js:2— packages/mui-icons-material/fixtures/material-design-icons/expected/FiveMp.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/mui-icons-material/fixtures/material-design-icons/expected/QueueMusicOutlined.js:2— packages/mui-icons-material/fixtures/material-design-icons/expected/QueueMusicOutlined.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/mui-icons-material/fixtures/material-design-icons/expected/RecordVoiceOverTwoTone.js:2— packages/mui-icons-material/fixtures/material-design-icons/expected/RecordVoiceOverTwoTone.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/mui-icons-material/fixtures/material-design-icons/expected/SixtyFps.js:2— packages/mui-icons-material/fixtures/material-design-icons/expected/SixtyFps.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/mui-icons-material/fixtures/material-design-icons/expected/StarRounded.js:2— packages/mui-icons-material/fixtures/material-design-icons/expected/StarRounded.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/mui-icons-material/fixtures/material-design-icons/expected/ThirtyFps.js:2— packages/mui-icons-material/fixtures/material-design-icons/expected/ThirtyFps.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/mui-icons-material/fixtures/material-design-icons/expected/TimesOneMobiledata.js:2— packages/mui-icons-material/fixtures/material-design-icons/expected/TimesOneMobiledata.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/mui-icons-material/fixtures/material-design-icons/expected/TwentyFourMp.js:2— packages/mui-icons-material/fixtures/material-design-icons/expected/TwentyFourMp.js:2 imports './utils/createSvgIcon', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
R4 · Test Coverage· No test reaches this file · ×20
No test reaches this file packages-internal/markdown/loader.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file netlify/edge-functions/og-image.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 netlify/functions/feedback-management.mts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/mui-icons-material/scripts/download.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file 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 packages/mui-codemod/src/deprecations/all/deprecations-all.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages-internal/core-docs/src/utils/createDemo.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 packages-internal/api-docs-builder-core/muiSystem/getSystemComponentInfo.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 packages/mui-icons-material/renameFilters/material-design-icons.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages-internal/api-docs-builder/src/types/utils.types.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 packages/mui-icons-material/scripts/create-typings.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/mui-icons-material/scripts/merge-package-json.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file netlify/functions/on-deploy.mts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages-internal/api-docs-builder-core/materialUi/projectSettings.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 packages-internal/core-docs/src/AppLayout/components/ArrowButton.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 packages-internal/markdown/apiPageTranslationLoader.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages-internal/api-docs-builder-core/muiSystem/projectSettings.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 packages/mui-material/scripts/stagePublishedDocs.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/mui-icons-material/renameFilters/default.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages-internal/core-docs/src/utils/createDemoClient.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.
Hotspot: packages-internal/core-docs/src/branding/brandingTheme.ts packages-internal/core-docs/src/branding/brandingTheme.ts:431— packages-internal/core-docs/src/branding/brandingTheme.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 241 in brandingTheme.getThemedComponents at line 431. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:34:17 +02:00' --until='2026-11-13 16:34:17 +02:00' --full-history --no-merges -- packages-internal/core-docs/src/branding/brandingTheme.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/mui-material/src/styles/createThemeWithVars.js packages/mui-material/src/styles/createThemeWithVars.js:138— packages/mui-material/src/styles/createThemeWithVars.js changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 109 in createThemeWithVars.createThemeWithVars at line 138. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:34:17 +02:00' --until='2026-11-13 16:34:17 +02:00' --full-history --no-merges -- packages/mui-material/src/styles/createThemeWithVars.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/mui-material/src/Select/SelectInput.js packages/mui-material/src/Select/SelectInput.js:146— packages/mui-material/src/Select/SelectInput.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 131 in SelectInput.SelectInput at line 146. 2 of those changes were fix/bug commits, 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:34:17 +02:00' --until='2026-11-13 16:34:17 +02:00' --full-history --no-merges -- packages/mui-material/src/Select/SelectInput.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/mui-material/src/Tabs/Tabs.js packages/mui-material/src/Tabs/Tabs.js:257— packages/mui-material/src/Tabs/Tabs.js changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 92 in Tabs.Tabs at line 257. 2 of those changes were fix/bug commits, 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:34:17 +02:00' --until='2026-11-13 16:34:17 +02:00' --full-history --no-merges -- packages/mui-material/src/Tabs/Tabs.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/mui-material/src/Autocomplete/Autocomplete.js packages/mui-material/src/Autocomplete/Autocomplete.js:432— packages/mui-material/src/Autocomplete/Autocomplete.js changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 51 in Autocomplete.Autocomplete at line 432. 2 of those changes were fix/bug commits, and the other 6 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:34:17 +02:00' --until='2026-11-13 16:34:17 +02:00' --full-history --no-merges -- packages/mui-material/src/Autocomplete/Autocomplete.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: REDACTED REDACTED:219— REDACTED changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 73 in AppSearch.AppSearch at line 219. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:34:17 +02:00' --until='2026-11-13 16:34:17 +02:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/mui-material/src/InputBase/InputBase.js packages/mui-material/src/InputBase/InputBase.js:248— packages/mui-material/src/InputBase/InputBase.js changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 58 in InputBase.InputBase at line 248. 1 of those changes was a fix/bug commit, and the other 5 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:34:17 +02:00' --until='2026-11-13 16:34:17 +02:00' --full-history --no-merges -- packages/mui-material/src/InputBase/InputBase.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/mui-material/src/useAutocomplete/useAutocomplete.js packages/mui-material/src/useAutocomplete/useAutocomplete.js:97— packages/mui-material/src/useAutocomplete/useAutocomplete.js changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 55 in useAutocomplete.useAutocomplete at line 97. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:34:17 +02:00' --until='2026-11-13 16:34:17 +02:00' --full-history --no-merges -- packages/mui-material/src/useAutocomplete/useAutocomplete.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/mui-system/src/cssVars/createCssVarsProvider.tsx packages/mui-system/src/cssVars/createCssVarsProvider.tsx:216— packages/mui-system/src/cssVars/createCssVarsProvider.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 54 in createCssVarsProvider.createCssVarsProvider.CssVarsProvider at line 216. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:34:17 +02:00' --until='2026-11-13 16:34:17 +02:00' --full-history --no-merges -- packages/mui-system/src/cssVars/createCssVarsProvider.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/mui-material/src/Tooltip/Tooltip.js packages/mui-material/src/Tooltip/Tooltip.js:237— packages/mui-material/src/Tooltip/Tooltip.js changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 62 in Tooltip.Tooltip at line 237. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:34:17 +02:00' --until='2026-11-13 16:34:17 +02:00' --full-history --no-merges -- packages/mui-material/src/Tooltip/Tooltip.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: scripts/buildLlmsDocs/index.ts scripts/buildLlmsDocs/index.ts:461— scripts/buildLlmsDocs/index.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in index.buildLlmsDocs at line 461. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:34:17 +02:00' --until='2026-11-13 16:34:17 +02:00' --full-history --no-merges -- scripts/buildLlmsDocs/index.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/mui-material/src/SpeedDial/SpeedDial.js packages/mui-material/src/SpeedDial/SpeedDial.js:152— packages/mui-material/src/SpeedDial/SpeedDial.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in SpeedDial.SpeedDial at line 152. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:34:17 +02:00' --until='2026-11-13 16:34:17 +02:00' --full-history --no-merges -- packages/mui-material/src/SpeedDial/SpeedDial.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/mui-material/src/MenuList/MenuList.js packages/mui-material/src/MenuList/MenuList.js:79— packages/mui-material/src/MenuList/MenuList.js changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in MenuList.MenuList at line 79. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:34:17 +02:00' --until='2026-11-13 16:34:17 +02:00' --full-history --no-merges -- packages/mui-material/src/MenuList/MenuList.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/mui-material/src/Slider/useSlider.ts packages/mui-material/src/Slider/useSlider.ts:203— packages/mui-material/src/Slider/useSlider.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in useSlider.useSlider at line 203. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:34:17 +02:00' --until='2026-11-13 16:34:17 +02:00' --full-history --no-merges -- packages/mui-material/src/Slider/useSlider.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/mui-lab/src/Masonry/Masonry.tsx packages/mui-lab/src/Masonry/Masonry.tsx:96— packages/mui-lab/src/Masonry/Masonry.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in Masonry.getStyle at line 96. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:34:17 +02:00' --until='2026-11-13 16:34:17 +02:00' --full-history --no-merges -- packages/mui-lab/src/Masonry/Masonry.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: scripts/a11yScorecard/validate.mjs scripts/a11yScorecard/validate.mjs:119— scripts/a11yScorecard/validate.mjs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in validate.validateSource at line 119. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:34:17 +02:00' --until='2026-11-13 16:34:17 +02:00' --full-history --no-merges -- scripts/a11yScorecard/validate.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages-internal/core-docs/src/AppLayout/layout/AppLayoutDocsFooter.tsx packages-internal/core-docs/src/AppLayout/layout/AppLayoutDocsFooter.tsx:143— packages-internal/core-docs/src/AppLayout/layout/AppLayoutDocsFooter.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in AppLayoutDocsFooter.AppLayoutDocsFooter at line 143. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:34:17 +02:00' --until='2026-11-13 16:34:17 +02:00' --full-history --no-merges -- packages-internal/core-docs/src/AppLayout/layout/AppLayoutDocsFooter.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: docs/data/material/components/autocomplete/demos/google-maps/GoogleMaps.tsx docs/data/material/components/autocomplete/demos/google-maps/GoogleMaps.tsx:127— docs/data/material/components/autocomplete/demos/google-maps/GoogleMaps.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in GoogleMaps.GoogleMaps at line 127. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:34:17 +02:00' --until='2026-11-13 16:34:17 +02:00' --full-history --no-merges -- docs/data/material/components/autocomplete/demos/google-maps/GoogleMaps.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: scripts/releaseChangelog.mjs scripts/releaseChangelog.mjs:76— scripts/releaseChangelog.mjs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in releaseChangelog.main at line 76. 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 16:34:17 +02:00' --until='2026-11-13 16:34:17 +02:00' --full-history --no-merges -- scripts/releaseChangelog.mjs`: 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.
FileTooLong: pricing/PricingTable.tsx docs/src/components/pricing/PricingTable.tsx— FileTooLong — 1656 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1156 over it, 3.31× 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: branding/brandingTheme.ts packages-internal/core-docs/src/branding/brandingTheme.ts— FileTooLong — 1115 significant lines (blank, comment-only and punctuation-only lines excluded), about 74% of them inside a single declaration: getThemedComponents (431-1600). The bar is 500 significant lines; this is 615 over it, 2.23× 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: useAutocomplete/useAutocomplete.js packages/mui-material/src/useAutocomplete/useAutocomplete.js— FileTooLong — 989 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 94% of them inside a single declaration: useAutocomplete (97-1622). The bar is 500 significant lines; this is 489 over it, 1.98× 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: styles/createThemeWithVars.js packages/mui-material/src/styles/createThemeWithVars.js— FileTooLong — 776 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 89% of them inside a single declaration: createThemeWithVars (138-1045). The bar is 500 significant lines; this is 276 over it, 1.55× 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: Autocomplete/Autocomplete.js packages/mui-material/src/Autocomplete/Autocomplete.js— FileTooLong — 730 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 230 over it, 1.46× 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: styles/components.ts packages/mui-material/src/styles/components.ts— FileTooLong — 714 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: Components (5-839). The bar is 500 significant lines; this is 214 over it, 1.43× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Slider/Slider.js packages/mui-material/src/Slider/Slider.js— FileTooLong — 664 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 164 over it, 1.33× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tabs/Tabs.js packages/mui-material/src/Tabs/Tabs.js— FileTooLong — 657 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 157 over it, 1.31× 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: Select/SelectInput.js packages/mui-material/src/Select/SelectInput.js— FileTooLong — 650 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: SelectInput (146-940). The bar is 500 significant lines; this is 150 over it, 1.30× 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: MarkdownDocs/MarkdownElement.tsx packages-internal/core-docs/src/MarkdownDocs/MarkdownElement.tsx— FileTooLong — 646 significant lines (blank, comment-only and punctuation-only lines excluded), about 79% of them inside a single declaration: Root (7-672). The bar is 500 significant lines; this is 146 over it, 1.29× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: REDACTED REDACTED— FileTooLong — 613 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 113 over it, 1.23× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Slider/useSlider.ts packages/mui-material/src/Slider/useSlider.ts— FileTooLong — 605 significant lines (blank, comment-only and punctuation-only lines excluded), about 78% of them inside a single declaration: useSlider (203-940). The bar is 500 significant lines; this is 105 over it, 1.21× 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: REDACTED REDACTED— FileTooLong — 572 significant lines (blank, comment-only and punctuation-only lines excluded), about 76% of them inside a single declaration: AppSearch (219-844). The bar is 500 significant lines; this is 72 over it, 1.14× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Rating/Rating.js packages/mui-material/src/Rating/Rating.js— FileTooLong — 539 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 39 over it, 1.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Tooltip/Tooltip.js packages/mui-material/src/Tooltip/Tooltip.js— FileTooLong — 523 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 23 over it, 1.05× 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: home/MaterialDesignComponents.tsx docs/src/components/home/MaterialDesignComponents.tsx— FileTooLong — 519 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 19 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×16
JavaScript dependencies are not locked examples/material-ui-express-ssr/package.json:9— examples/material-ui-express-ssr/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / 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 examples/material-ui-gatsby/package.json:9— examples/material-ui-gatsby/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / 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 examples/material-ui-nextjs-pages-router-ts/package.json:11— examples/material-ui-nextjs-pages-router-ts/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / 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 examples/material-ui-nextjs-pages-router/package.json:11— examples/material-ui-nextjs-pages-router/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / 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 examples/material-ui-nextjs-tailwind-ts/package.json:11— examples/material-ui-nextjs-tailwind-ts/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / 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 examples/material-ui-nextjs-ts-v4-v5-migration/package.json:11— examples/material-ui-nextjs-ts-v4-v5-migration/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / 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 examples/material-ui-nextjs-ts/package.json:11— examples/material-ui-nextjs-ts/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / 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 examples/material-ui-nextjs/package.json:10— examples/material-ui-nextjs/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / 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 examples/material-ui-pigment-css-nextjs-ts/package.json:10— examples/material-ui-pigment-css-nextjs-ts/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / 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 examples/material-ui-pigment-css-vite-ts/package.json:12— examples/material-ui-pigment-css-vite-ts/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / 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 examples/material-ui-preact/package.json:5— examples/material-ui-preact/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / 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 examples/material-ui-react-router-ts/package.json:11— examples/material-ui-react-router-ts/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / 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 examples/material-ui-remix-ts/package.json:11— examples/material-ui-remix-ts/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / 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 examples/material-ui-vite-tailwind-ts/package.json:12— examples/material-ui-vite-tailwind-ts/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / 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 examples/material-ui-vite-ts/package.json:11— examples/material-ui-vite-ts/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / 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 examples/material-ui-vite/package.json:10— examples/material-ui-vite/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / 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.
Dead file (~8 LoC) packages/mui-icons-material/custom/Apple.js— no import path from any entry point (509 application, 370 tooling, 1594 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 (~8 LoC) packages/mui-icons-material/custom/Facebook.js— no import path from any entry point (509 application, 370 tooling, 1594 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 (~8 LoC) packages/mui-icons-material/custom/GitHub.js— no import path from any entry point (509 application, 370 tooling, 1594 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 (~8 LoC) packages/mui-icons-material/custom/Google.js— no import path from any entry point (509 application, 370 tooling, 1594 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 (~8 LoC) packages/mui-icons-material/custom/Instagram.js— no import path from any entry point (509 application, 370 tooling, 1594 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 (~8 LoC) packages/mui-icons-material/custom/LinkedIn.js— no import path from any entry point (509 application, 370 tooling, 1594 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 (~8 LoC) packages/mui-icons-material/custom/Microsoft.js— no import path from any entry point (509 application, 370 tooling, 1594 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 (~8 LoC) packages/mui-icons-material/custom/Pinterest.js— no import path from any entry point (509 application, 370 tooling, 1594 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 (~8 LoC) packages/mui-icons-material/custom/Reddit.js— no import path from any entry point (509 application, 370 tooling, 1594 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 (~8 LoC) packages/mui-icons-material/custom/Telegram.js— no import path from any entry point (509 application, 370 tooling, 1594 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 (~8 LoC) packages/mui-icons-material/custom/Twitter.js— no import path from any entry point (509 application, 370 tooling, 1594 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 (~8 LoC) packages/mui-icons-material/custom/WhatsApp.js— no import path from any entry point (509 application, 370 tooling, 1594 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 (~8 LoC) packages/mui-icons-material/custom/X.js— no import path from any entry point (509 application, 370 tooling, 1594 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 (~8 LoC) packages/mui-icons-material/custom/YouTube.js— no import path from any entry point (509 application, 370 tooling, 1594 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
D30 · Dependency Vulnerabilities· Medium CVE · ×12
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×9
Focus outline removed in CSS without a :focus replacement docs/public/static/components-gallery/base-theme.css:417— `.GalleryMenu-listbox` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement docs/public/static/components-gallery/base-theme.css:475— `.GalleryNumberInput.base--focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement docs/public/static/components-gallery/base-theme.css:487— `.GalleryNumberInput .input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement docs/public/static/components-gallery/base-theme.css:495— `.GalleryNumberInput .input:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement docs/public/static/components-gallery/base-theme.css:598— `.GallerySelect.base--focusVisible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement docs/public/static/components-gallery/base-theme.css:625— `.GallerySelect-listbox` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement docs/public/static/components-gallery/base-theme.css:701— `.GallerySlider.base--disabled` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages-internal/core-docs/src/branding/brandingTheme.ts:1018— `&:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages-internal/core-docs/src/TableOfContents/MiniTableOfContents.tsx:60— `&:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
transformer (cognitive 23) REDACTED:7— transformer has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (16 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 13). None of this is in the body itself: all 23 points belong to 9 function literals inside it that branch (lines 35, 21, 15, …). 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.
transformer (cognitive 23) REDACTED:7— transformer has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (16 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 13). None of this is in the body itself: all 23 points belong to 9 function literals inside it that branch (lines 35, 21, 15, …). 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.
transformer (cognitive 23) REDACTED:7— transformer has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (16 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 13). None of this is in the body itself: all 23 points belong to 9 function literals inside it that branch (lines 37, 22, 16, …). 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.
transformer (cognitive 23) REDACTED:7— transformer has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (16 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 13). None of this is in the body itself: all 23 points belong to 9 function literals inside it that branch (lines 35, 21, 15, …). 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.
transformer (cognitive 23) REDACTED:7— transformer has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (16 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 13). None of this is in the body itself: all 23 points belong to 9 function literals inside it that branch (lines 35, 21, 15, …). 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.
transformer (cognitive 23) REDACTED:7— transformer has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (16 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 13). None of this is in the body itself: all 23 points belong to 9 function literals inside it that branch (lines 35, 21, 15, …). 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.
transformer (cognitive 23) REDACTED:7— transformer has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (16 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 13). None of this is in the body itself: all 23 points belong to 10 function literals inside it that branch (lines 32, 21, 15, …). 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.
transformer (cognitive 23) REDACTED:7— transformer has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (16 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 13). None of this is in the body itself: all 23 points belong to 9 function literals inside it that branch (lines 32, 21, 15, …). 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.
transformer (cognitive 23) REDACTED:7— transformer has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (16 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 13). None of this is in the body itself: all 23 points belong to 9 function literals inside it that branch (lines 32, 21, 15, …). 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.
X2 · Cancellation propagation· Async function without AbortSignal · ×8
Async function without AbortSignal: defaultFetchNotifications packages-internal/core-docs/src/DocsProvider/DocsProvider.tsx:18— `defaultFetchNotifications` 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: defaultFetchVersions packages-internal/core-docs/src/DocsProvider/DocsProvider.tsx:28— `defaultFetchVersions` 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: submitFeedback packages-internal/core-docs/src/AppLayout/layout/AppLayoutDocsFooter.tsx:70— `submitFeedback` 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: tryFetch packages-internal/core-docs/src/Ad/AdCarbon.tsx:78— `tryFetch` 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: run packages/mui-icons-material/scripts/download.mjs:178— `run` 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: handler netlify/edge-functions/og-image.tsx:49— `handler` holds an AbortSignal but calls `fetch(…)` without it, so its caller's cancellation never reaches that call and it runs to its end after whatever wanted it has given up. Hand the signal on: `fetch(…, { signal })`.
Async function without AbortSignal: run docs/scripts/syncTeamMembers.ts:73— `run` 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: run docs/scripts/updateIconSynonyms.js:26— `run` 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 })`.
ClassTooLong: useAutocomplete packages/mui-material/src/useAutocomplete/useAutocomplete.js:1— ClassTooLong — 926 significant lines (blank, comment-only and punctuation-only lines excluded), 51 methods. The bar is 400 significant lines; this is 526 over it, 2.32× 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: Components packages/mui-material/src/styles/components.ts:5— ClassTooLong — 711 significant lines (blank, comment-only and punctuation-only lines excluded), 0 methods. The bar is 400 significant lines; this is 311 over it, 1.78× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: createThemeWithVars packages/mui-material/src/styles/createThemeWithVars.js:1— ClassTooLong — 690 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 290 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.
ClassTooLong: PricingTable docs/src/components/pricing/PricingTable.tsx:1— ClassTooLong — 563 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 163 over it, 1.41× 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: SelectInput packages/mui-material/src/Select/SelectInput.js:1— ClassTooLong — 521 significant lines (blank, comment-only and punctuation-only lines excluded), 3 methods. The bar is 400 significant lines; this is 121 over it, 1.30× 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: useSlider packages/mui-material/src/Slider/useSlider.ts:1— ClassTooLong — 471 significant lines (blank, comment-only and punctuation-only lines excluded), 42 methods. The bar is 400 significant lines; this is 71 over it, 1.18× 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: AppSearch REDACTED:1— ClassTooLong — 434 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 34 over it, 1.09× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Sync-over-async blocking REDACTED:88— `readFileSync` in `annotateComponentDefinition` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:282— `writeFileSync` in `annotateComponentDefinition` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages-internal/api-docs-builder/src/ApiBuilders/HookApiBuilder.ts:39— `readFileSync` in `annotateHookDefinition` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages-internal/api-docs-builder/src/ApiBuilders/HookApiBuilder.ts:230— `writeFileSync` in `annotateHookDefinition` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages-internal/api-docs-builder/src/buildApiUtils.ts:56— `fs.writeFileSync` in `writePrettifiedFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages-internal/markdown/loader.mjs:239— `statSync` in `callback to extensions.find` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Dead file (~10 LoC) packages/mui-codemod/src/v6.0.0/all/v6-all.js— no import path from any entry point (509 application, 370 tooling, 1594 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/mui-codemod/src/v6.0.0/all/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~10 LoC) packages/mui-lab/src/internal/svg-icons/ArrowLeft.tsx— no import path from any entry point (509 application, 370 tooling, 1594 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 (~10 LoC) packages/mui-lab/src/internal/svg-icons/ArrowRight.tsx— no import path from any entry point (509 application, 370 tooling, 1594 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 (~10 LoC) packages/mui-lab/src/internal/svg-icons/Calendar.tsx— no import path from any entry point (509 application, 370 tooling, 1594 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 (~10 LoC) packages/mui-lab/src/internal/svg-icons/DateRange.tsx— no import path from any entry point (509 application, 370 tooling, 1594 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 (~10 LoC) packages/mui-lab/src/internal/svg-icons/Pen.tsx— no import path from any entry point (509 application, 370 tooling, 1594 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
Change coupling: deprecations-all.js ↔ postcss.config.js packages/mui-codemod/src/deprecations/all/deprecations-all.js:1— `packages/mui-codemod/src/deprecations/all/deprecations-all.js` and `packages/mui-codemod/src/deprecations/all/postcss.config.js` change together 100% of the time (16 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 16 shared commits counted here, the most recent 3 are `df4b10f8` [material-ui][InputBase] Deprecate composed classes (#45234); `bd7a9cc9` [material-ui][Slider] Deprecate composed classes (#45201); `820a76c8` [material-ui][Drawer] Deprecate composed classes (#44870) — run `git show` on any of them.
Change coupling: BasePopper.tsx ↔ useSlider.ts packages/mui-material/src/Popper/BasePopper.tsx:1— `packages/mui-material/src/Popper/BasePopper.tsx` and `packages/mui-material/src/Slider/useSlider.ts` change together 60% of the time (6 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) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `c1c0d7c7` [core] Include history from the @mui/base components & hooks v5; `656bde7c` [core] Include history from the @mui/base components & hooks v3; `6588beeb` [core] Include history from the @mui/base components & hooks v2 — run `git show` on any of them.
Change coupling: HeaderNavBar.tsx ↔ HeaderNavDropdown.tsx docs/src/components/header/HeaderNavBar.tsx:1— `docs/src/components/header/HeaderNavBar.tsx` and `docs/src/components/header/HeaderNavDropdown.tsx` change together 58% of the time (11 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `a37ef345` [website] Make beta chip consistent for Toolpad (#43392); `62854f34` [docs] Link Toolpad core docs to the docs menu (#42952); `edc6d613` [website] Copyedit Docs and Product menu taglines (#43075) — run `git show` on any of them.
Change coupling: useModal.ts ↔ useSlider.ts packages/mui-material/src/Modal/useModal.ts:1— `packages/mui-material/src/Modal/useModal.ts` and `packages/mui-material/src/Slider/useSlider.ts` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `c1c0d7c7` [core] Include history from the @mui/base components & hooks v5; `656bde7c` [core] Include history from the @mui/base components & hooks v3; `6588beeb` [core] Include history from the @mui/base components & hooks v2 — run `git show` on any of them.
Change coupling: createCssVarsProvider.tsx ↔ cssVarsParser.ts packages/mui-system/src/cssVars/createCssVarsProvider.tsx:1— `packages/mui-system/src/cssVars/createCssVarsProvider.tsx` and `packages/mui-system/src/cssVars/cssVarsParser.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) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `04c8786a` [system] Add `spacing` theme token to be used in `theme.spacing()` (#… (at that commit the file was still `packages/mui-system/src/cssVars/createCssVarsProvider.js`); `49795024` [system] Remove unnecessary parsed theme (#35239) (at that commit the file was still `packages/mui-system/src/cssVars/createCssVarsProvider.js`); `0ec69e7e` [CssVarsProvider][Material UI] Exclude dark mode variables from `:roo… (at that commit the file was still `packages/mui-system/src/cssVars/createCssVarsProvider.js`) — run `git show` on any of them.
AC2 · Forms & labels· <Select> field component without a label · ×4
<Select> field component without a label docs/src/components/productX/XGridFullDemo.tsx:88— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label docs/src/components/productX/XGridFullDemo.tsx:95— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label docs/src/components/productX/XGridFullDemo.tsx:109— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Select> field component without a label docs/src/components/x-grid/EditStatus.tsx:36— This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
Off the main sequence: @mui/stylis-plugin-rtl — @mui/stylis-plugin-rtl: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: @mui/material-nextjs — @mui/material-nextjs: abstractness 0.17, instability 0.00, distance 0.83 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: @mui/utils — @mui/utils: abstractness 0.06, instability 0.14, distance 0.79 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: @mui/internal-docs-utils — @mui/internal-docs-utils: abstractness 0.25, instability 0.00, distance 0.75 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
AC2 · Forms & labels· <TextField> field component without a label · ×3
<TextField> field component without a label docs/src/pages/premium-themes/onepirate/modules/views/AppFooter.tsx:93— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextField> field component without a label docs/src/pages/premium-themes/onepirate/modules/views/ProductCTA.tsx:42— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<TextField> field component without a label docs/src/pages/premium-themes/paperbase/Content.tsx:28— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
(anonymous) (cyclomatic 17) packages/mui-material/src/ButtonGroup/ButtonGroup.js:66— (anonymous) has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, 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.
(anonymous) (cyclomatic 17) packages/mui-material/src/MenuItem/MenuItem.js:63— (anonymous) has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
(anonymous) (cyclomatic 17) packages/mui-material/src/ListItemButton/ListItemButton.js:59— (anonymous) has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
transformer (cognitive 18) REDACTED:7— transformer has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 9). None of this is in the body itself: all 18 points belong to 8 function literals inside it that branch (lines 35, 21, 15, …). 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.
transformer (cognitive 18) REDACTED:7— transformer has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 9). None of this is in the body itself: all 18 points belong to 8 function literals inside it that branch (lines 32, 21, 15, …). 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.
transformer (cognitive 18) REDACTED:7— transformer has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 9). None of this is in the body itself: all 18 points belong to 8 function literals inside it that branch (lines 32, 21, 15, …). 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.
Dead file (~1 LoC) packages/mui-codemod/src/deprecations/accordion-props/index.js— no import path from any entry point (509 application, 370 tooling, 1594 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/mui-codemod/src/deprecations/all/deprecations-all.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 (~1 LoC) packages/mui-codemod/src/deprecations/accordion-summary-classes/index.js— no import path from any entry point (509 application, 370 tooling, 1594 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/mui-codemod/src/deprecations/all/deprecations-all.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 (~1 LoC) packages/mui-codemod/src/deprecations/alert-classes/index.js— no import path from any entry point (509 application, 370 tooling, 1594 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/mui-codemod/src/deprecations/all/deprecations-all.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
AC2 · Forms & labels· <OutlinedInput> field component without a label · ×2
<OutlinedInput> field component without a label docs/pages/experiments/website/dashboard-template-theme.tsx:221— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<OutlinedInput> field component without a label docs/pages/experiments/website/dashboard-template-theme.tsx:222— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC2 · Forms & labels· <Slider> field component without a label · ×2
<Slider> field component without a label docs/src/components/showcase/ThemeSlider.tsx:31— This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Slider> field component without a label docs/src/components/x-grid/EditProgress.tsx:55— This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
DashboardSidebarPageItem.DashboardSidebarPageItem (cyclomatic 34) docs/data/material/getting-started/templates/crud-dashboard/components/DashboardSidebarPageItem.tsx:32— DashboardSidebarPageItem.DashboardSidebarPageItem has cyclomatic complexity 34 (threshold 15). Of this number, 32 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.
DashboardSidebarPageItem.DashboardSidebarPageItem (cyclomatic 34) docs/data/material/getting-started/templates/crud-dashboard/components/DashboardSidebarPageItem.js:20— DashboardSidebarPageItem.DashboardSidebarPageItem has cyclomatic complexity 34 (threshold 15). Of this number, 32 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.
DashboardSidebar.DashboardSidebar (cyclomatic 28) docs/data/material/getting-started/templates/crud-dashboard/components/DashboardSidebar.tsx:29— DashboardSidebar.DashboardSidebar has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 10 of the 28 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 125, 105, 57, …). 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.
DashboardSidebar.DashboardSidebar (cyclomatic 28) docs/data/material/getting-started/templates/crud-dashboard/components/DashboardSidebar.js:22— DashboardSidebar.DashboardSidebar has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 10 of the 28 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 118, 98, 50, …). 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.
getPropsFromComponentNode.getPropsFromVariableDeclaration (cyclomatic 22) packages-internal/api-docs-builder/src/utils/getPropsFromComponentNode.ts:186— getPropsFromComponentNode.getPropsFromVariableDeclaration 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.
getPropsFromComponentNode.getPropsFromVariableDeclaration (cyclomatic 22) packages-internal/docs-utils/src/getPropsFromComponentNode.ts:184— getPropsFromComponentNode.getPropsFromVariableDeclaration 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.
top-level-imports.transformer (cyclomatic 19) REDACTED:3— top-level-imports.transformer has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 41, 23). 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.
top-level-imports.transformer (cyclomatic 19) REDACTED:4— top-level-imports.transformer has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 38, 20). 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.
EmployeeList.EmployeeList (cyclomatic 18) docs/data/material/getting-started/templates/crud-dashboard/components/EmployeeList.tsx:32— EmployeeList.EmployeeList has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 83, 105, 174, …). 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.
EmployeeList.EmployeeList (cyclomatic 18) docs/data/material/getting-started/templates/crud-dashboard/components/EmployeeList.js:24— EmployeeList.EmployeeList has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 72, 94, 163, …). 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.
employees.getMany (cyclomatic 16) docs/data/material/getting-started/templates/crud-dashboard/data/employees.ts:50— employees.getMany has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 70, 95, 65). 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.
employees.getMany (cyclomatic 16) docs/data/material/getting-started/templates/crud-dashboard/data/employees.js:39— employees.getMany has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 51, 82, 46). 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.
getPropsFromComponentNode.getPropsFromComponentNode (cyclomatic 16) packages-internal/api-docs-builder/src/utils/getPropsFromComponentNode.ts:286— getPropsFromComponentNode.getPropsFromComponentNode has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 311). 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.
getPropsFromComponentNode.getPropsFromComponentNode (cyclomatic 16) packages-internal/docs-utils/src/getPropsFromComponentNode.ts:284— getPropsFromComponentNode.getPropsFromComponentNode has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 309). 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.
(anonymous) (cyclomatic 16) packages/mui-material/src/FilledInput/FilledInput.js:61— (anonymous) has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to 4 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
(anonymous) (cyclomatic 16) packages/mui-material/src/AppBar/AppBar.js:42— (anonymous) has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DashboardSidebarPageItem.DashboardSidebarPageItem (cognitive 36) docs/data/material/getting-started/templates/crud-dashboard/components/DashboardSidebarPageItem.tsx:32— DashboardSidebarPageItem.DashboardSidebarPageItem has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 17 (22 pts), boolean chains 10, if/else 4 (nesting depth added 5). Of this number, 35 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
DashboardSidebarPageItem.DashboardSidebarPageItem (cognitive 36) docs/data/material/getting-started/templates/crud-dashboard/components/DashboardSidebarPageItem.js:20— DashboardSidebarPageItem.DashboardSidebarPageItem has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 17 (22 pts), boolean chains 10, if/else 4 (nesting depth added 5). Of this number, 35 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
DashboardSidebar.DashboardSidebar (cognitive 30) docs/data/material/getting-started/templates/crud-dashboard/components/DashboardSidebar.tsx:29— DashboardSidebar.DashboardSidebar has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 13 (14 pts), boolean chains 8, if/else 6 (8 pts) (nesting depth added 3). Most of this is not in the body itself: 9 of the 30 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 125, 105, 57, …). 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.
DashboardSidebar.DashboardSidebar (cognitive 30) docs/data/material/getting-started/templates/crud-dashboard/components/DashboardSidebar.js:22— DashboardSidebar.DashboardSidebar has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 13 (14 pts), boolean chains 8, if/else 6 (8 pts) (nesting depth added 3). Most of this is not in the body itself: 9 of the 30 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 118, 98, 50, …). 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.
transformer (cognitive 29) packages/mui-codemod/src/v5.0.0/date-pickers-moved-to-x.js:179— transformer has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (22 pts), ternaries 2 (6 pts), boolean chains 1 (nesting depth added 15). Most of this is not in the body itself: 1 of the 29 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 189, 225, 212). 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.
transformer (cognitive 29) REDACTED:7— transformer has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (22 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 17). None of this is in the body itself: all 29 points belong to 9 function literals inside it that branch (lines 35, 21, 15, …). 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.
getPropsFromComponentNode.getPropsFromVariableDeclaration (cognitive 23) packages-internal/api-docs-builder/src/utils/getPropsFromComponentNode.ts:186— getPropsFromComponentNode.getPropsFromVariableDeclaration has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 7 (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.
getPropsFromComponentNode.getPropsFromVariableDeclaration (cognitive 23) packages-internal/docs-utils/src/getPropsFromComponentNode.ts:184— getPropsFromComponentNode.getPropsFromVariableDeclaration has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 7 (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.
employees.getMany (cognitive 21) docs/data/material/getting-started/templates/crud-dashboard/data/employees.ts:50— employees.getMany has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 2 (8 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 12). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 95, 65, 70). 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.
employees.getMany (cognitive 21) docs/data/material/getting-started/templates/crud-dashboard/data/employees.js:39— employees.getMany has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 2 (8 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 12). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 82, 46, 51). 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.
EmployeeList.EmployeeList (cognitive 20) docs/data/material/getting-started/templates/crud-dashboard/components/EmployeeList.tsx:32— EmployeeList.EmployeeList has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 8, if/else 6, boolean chains 3, error handling 2 (3 pts) (nesting depth added 1). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 83, 105, 174, …). 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.
EmployeeList.EmployeeList (cognitive 20) docs/data/material/getting-started/templates/crud-dashboard/components/EmployeeList.js:24— EmployeeList.EmployeeList has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 8, if/else 6, boolean chains 3, error handling 2 (3 pts) (nesting depth added 1). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 72, 94, 163, …). 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.
top-level-imports.transformer (cognitive 19) REDACTED:3— top-level-imports.transformer has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 6, match/switch 1 (nesting depth added 2). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 41, 23). 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.
top-level-imports.transformer (cognitive 19) REDACTED:4— top-level-imports.transformer has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 6, match/switch 1 (nesting depth added 2). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 38, 20). 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.
getPropsFromComponentNode.getPropsFromComponentNode (cognitive 18) packages-internal/api-docs-builder/src/utils/getPropsFromComponentNode.ts:286— getPropsFromComponentNode.getPropsFromComponentNode has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 3 (nesting depth added 7). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 311). 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.
getPropsFromComponentNode.getPropsFromComponentNode (cognitive 18) packages-internal/docs-utils/src/getPropsFromComponentNode.ts:284— getPropsFromComponentNode.getPropsFromComponentNode has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 3 (nesting depth added 7). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 309). 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.
(anonymous) (cognitive 17) packages/mui-material/src/Switch/Switch.js:175— (anonymous) has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, ternaries 8. Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 189). 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.
(anonymous) (cognitive 17) packages/mui-material/src/Tab/Tab.js:53— (anonymous) has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 17. Of this number, 9 points are the body's own statements and 8 belong to 9 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
(anonymous) (cognitive 16) packages/mui-material/src/Slide/Slide.js:339— (anonymous) has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 5 (nesting depth added 6). 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.
(anonymous) (cognitive 16) packages/mui-material/src/ButtonGroup/ButtonGroup.js:66— (anonymous) has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 12, ternaries 4. Of this number, 14 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Change coupling clique: ExpandableApiItem.tsx, REDACTED, ClassesTable.tsx, REDACTED packages-internal/core-docs/src/ApiPage/list/ExpandableApiItem.tsx— 4 files — `packages-internal/core-docs/src/ApiPage/list/ExpandableApiItem.tsx`, `REDACTED`, `packages-internal/core-docs/src/ApiPage/table/ClassesTable.tsx`, `REDACTED` — all change together with no explicit dependency: a fully-connected co-change clique, not 6 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
Change coupling clique: REDACTED, REDACTED, HooksApiContent.tsx REDACTED— 3 files — `REDACTED`, `REDACTED`, `packages-internal/core-docs/src/ApiPage/HooksApiContent.tsx` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
Fake-async — async method never awaits docs/data/material/getting-started/templates/crud-dashboard/data/employees.js:153— `deleteOne` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits docs/data/material/getting-started/templates/crud-dashboard/data/employees.ts:164— `deleteOne` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Duplicated block (46 lines × 2 locations) REDACTED:7— REDACTED:7 · REDACTED:7 — 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 (46 lines × 2 locations) packages/mui-material/src/locale/csCZ.ts:4— packages/mui-material/src/locale/csCZ.ts:4 · packages/mui-material/src/locale/skSK.ts:4 — 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.
Complex function getPropsFromVariableDeclaration (cyclomatic 22, cognitive 23) packages-internal/api-docs-builder/src/utils/getPropsFromComponentNode.ts:186— getPropsFromVariableDeclaration has cyclomatic complexity 22 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 getPropsFromVariableDeclaration (cyclomatic 22, cognitive 23) packages-internal/docs-utils/src/getPropsFromComponentNode.ts:184— getPropsFromVariableDeclaration has cyclomatic complexity 22 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.
Dead file (~14 LoC) packages/mui-lab/src/internal/svg-icons/Clock.tsx— no import path from any entry point (509 application, 370 tooling, 1594 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 (~14 LoC) packages/mui-lab/src/internal/svg-icons/Time.tsx— no import path from any entry point (509 application, 370 tooling, 1594 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
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×2
Recursive walk over a caller-supplied document has no depth cap packages/mui-utils/src/deepmerge/deepmerge.ts:74— `deepmerge` is exported and takes `source: unknown` from its caller, and it calls itself at line 74 (`deepmerge`) with a piece of `source` — and nowhere in `deepmerge` 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 `deepmerge` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/mui-material/src/styles/stringifyTheme.ts:46— `stringifyTheme` is exported, takes a document from its caller (line 34) and hands it to `serializeTheme`, which calls itself at line 46 (`serializeTheme`) with a piece of `object` — and nowhere in `serializeTheme` 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 `serializeTheme` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×1
Animation without a prefers-reduced-motion guard docs/public/static/components-gallery/base-theme.css:732— `.GallerySlider-thumb` moves (`transition-property: box-shadow, transform`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
brandingTheme.getThemedComponents (cyclomatic 241) packages-internal/core-docs/src/branding/brandingTheme.ts:431— brandingTheme.getThemedComponents has cyclomatic complexity 241 (threshold 15). Most of this is not in the body itself: 1 of the 241 points is its own statement and the rest belongs to 22 function literals inside it that branch (lines 550, 1103, 436, …). 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.
useAutocomplete (cyclomatic 127) packages/mui-material/src/useAutocomplete/useAutocomplete.js:97— useAutocomplete has cyclomatic complexity 127 (threshold 15). Of this number, 22 points are the body's own statements and 105 belong to 23 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.
jss-to-styled.transformer (cyclomatic 109) packages/mui-codemod/src/v5.0.0/jss-to-styled.js:7— jss-to-styled.transformer has cyclomatic complexity 109 (threshold 15). Most of this is not in the body itself: 13 of the 109 points are its own statements and the rest belongs to 30 function items inside it that branch (getReturnStatement, a function literal at line 83, a function literal at line 453, …). 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.
createThemeWithVars.createThemeWithVars (cyclomatic 109) packages/mui-material/src/styles/createThemeWithVars.js:138— createThemeWithVars.createThemeWithVars has cyclomatic complexity 109 (threshold 15). Of this number, 18 points are the body's own statements and 91 belong to 7 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.
migrateToVariants.migrateToVariants (cyclomatic 105) packages/mui-codemod/src/util/migrateToVariants.js:182— migrateToVariants.migrateToVariants has cyclomatic complexity 105 (threshold 15). Most of this is not in the body itself: 1 of the 105 points is its own statement and the rest belongs to 17 function items inside it that branch (a function literal at line 413, a function literal at line 317, inverseBinaryExpression, …). 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.
sx-v6.sxV6 (cyclomatic 102) packages/mui-codemod/src/v6.0.0/sx-prop/sx-v6.js:33— sx-v6.sxV6 has cyclomatic complexity 102 (threshold 15). Most of this is not in the body itself: 3 of the 102 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 180, a function literal at line 57, a function literal at line 511, …). 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.
SwipeableDrawer.SwipeableDrawer (cyclomatic 87) packages/mui-material/src/SwipeableDrawer/SwipeableDrawer.js:139— SwipeableDrawer.SwipeableDrawer has cyclomatic complexity 87 (threshold 15). Most of this is not in the body itself: 10 of the 87 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 347, a function literal at line 488, a function literal at line 244, …). 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.
useAutocomplete.useAutocomplete.handleKeyDown.<returned closure> (cyclomatic 81) packages/mui-material/src/useAutocomplete/useAutocomplete.js:995— useAutocomplete.useAutocomplete.handleKeyDown.<returned closure> has cyclomatic complexity 81 (threshold 15). Of this number, 80 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.
useAutocomplete.handleKeyDown (cyclomatic 81) packages/mui-material/src/useAutocomplete/useAutocomplete.js:995— useAutocomplete.handleKeyDown has cyclomatic complexity 81 (threshold 15). Most of this is not in the body itself: 1 of the 81 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 995, 1186). 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.
AppSearch.AppSearch (cyclomatic 73) REDACTED:219— AppSearch.AppSearch has cyclomatic complexity 73 (threshold 15). Most of this is not in the body itself: 12 of the 73 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 428, 761, 263, …). 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.
DemoContent.DemoContent (cyclomatic 65) packages-internal/core-docs/src/DemoContent/DemoContent.tsx:87— DemoContent.DemoContent has cyclomatic complexity 65 (threshold 15). Of this number, 37 points are the body's own statements and 28 belong to 11 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.
Tooltip (cyclomatic 64) packages/mui-material/src/Tooltip/Tooltip.js:237— Tooltip has cyclomatic complexity 64 (threshold 15). Of this number, 25 points are the body's own statements and 39 belong to 28 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.
sxV6::(anonymous)::recurseObjectExpression (cyclomatic 62) packages/mui-codemod/src/v6.0.0/sx-prop/sx-v6.js:180— sxV6::(anonymous)::recurseObjectExpression has cyclomatic complexity 62 (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.
InputBase.InputBase (cyclomatic 58) packages/mui-material/src/InputBase/InputBase.js:248— InputBase.InputBase has cyclomatic complexity 58 (threshold 15). Of this number, 19 points are the body's own statements and 39 belong to 12 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Transition.Transition (cyclomatic 55) packages/mui-material/src/internal/Transition.tsx:100— Transition.Transition has cyclomatic complexity 55 (threshold 15). Most of this is not in the body itself: 7 of the 55 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 394, 216, 372, …). 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.
createCssVarsProvider.createCssVarsProvider.CssVarsProvider (cyclomatic 54) packages/mui-system/src/cssVars/createCssVarsProvider.tsx:216— createCssVarsProvider.createCssVarsProvider.CssVarsProvider has cyclomatic complexity 54 (threshold 15). Of this number, 26 points are the body's own statements and 28 belong to 7 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.
FocusTrap.FocusTrap (cyclomatic 53) packages/mui-material/src/Unstable_TrapFocus/FocusTrap.tsx:129— FocusTrap.FocusTrap has cyclomatic complexity 53 (threshold 15). Most of this is not in the body itself: 3 of the 53 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 286, a function literal at line 221, a function literal at line 164, …). 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.
Autocomplete (cyclomatic 53) packages/mui-material/src/Autocomplete/Autocomplete.js:432— Autocomplete has cyclomatic complexity 53 (threshold 15). Of this number, 41 points are the body's own statements and 12 belong to 15 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MaterialDesignComponents.buildTheme (cyclomatic 51) docs/src/components/home/MaterialDesignComponents.tsx:208— MaterialDesignComponents.buildTheme has cyclomatic complexity 51 (threshold 15). Most of this is not in the body itself: 1 of the 51 points is its own statement and the rest belongs to 10 function literals inside it that branch (lines 364, 284, 331, …). 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.
demoLoader (cyclomatic 51) packages-internal/markdown/loader.mjs:120— demoLoader has cyclomatic complexity 51 (threshold 15). Most of this is not in the body itself: 3 of the 51 points are its own statements and the rest belongs to 29 function items inside it that branch (a function literal at line 293, detectRelativeImports, a function literal at line 538, …). 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.
(anonymous) (cyclomatic 50) packages/mui-material/src/Chip/Chip.js:66— (anonymous) has cyclomatic complexity 50 (threshold 15). Of this number, 31 points are the body's own statements and 19 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
jss-to-tss-react.transformer (cyclomatic 45) packages/mui-codemod/src/v5.0.0/jss-to-tss-react.js:191— jss-to-tss-react.transformer has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 6 of the 45 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 204, 298, 376, …). 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.
removeSystemProps.removeSystemProps (cyclomatic 45) packages/mui-codemod/src/v9.0.0/system-props/removeSystemProps.js:148— removeSystemProps.removeSystemProps has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 5 of the 45 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 246, 265, 214, …). 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.
MenuList (cyclomatic 45) packages/mui-material/src/MenuList/MenuList.js:79— MenuList has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 1 of the 45 points is its own statement and the rest belongs to 14 function items inside it that branch (a function literal at line 258, a function literal at line 135, (anonymous)::adjustStyleForScrollbar, …). 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.
migrateToVariants::(anonymous)::recurseObjectExpression (cyclomatic 44) packages/mui-codemod/src/util/migrateToVariants.js:413— migrateToVariants::(anonymous)::recurseObjectExpression has cyclomatic complexity 44 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
(anonymous) (cyclomatic 41) packages/mui-material/src/PaginationItem/PaginationItem.js:110— (anonymous) has cyclomatic complexity 41 (threshold 15). Of this number, 23 points are the body's own statements and 18 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
HookApiBuilder.annotateHookDefinition (cyclomatic 39) packages-internal/api-docs-builder/src/ApiBuilders/HookApiBuilder.ts:30— HookApiBuilder.annotateHookDefinition has cyclomatic complexity 39 (threshold 15). Of this number, 32 points are the body's own statements and 7 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TablePaginationActions (cyclomatic 39) packages/mui-material/src/TablePaginationActions/TablePaginationActions.js:59— TablePaginationActions has cyclomatic complexity 39 (threshold 15). Of this number, 28 points are the body's own statements and 11 belong to 8 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ComponentApiBuilder.annotateComponentDefinition (cyclomatic 38) REDACTED:79— ComponentApiBuilder.annotateComponentDefinition has cyclomatic complexity 38 (threshold 15). Of this number, 31 points are the body's own statements and 7 belong to 4 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.
Popover.Popover (cyclomatic 38) packages/mui-material/src/Popover/Popover.js:95— Popover.Popover has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 8 of the 38 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 200, 140, 284, …). 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.
ButtonBase (cyclomatic 38) packages/mui-material/src/ButtonBase/ButtonBase.js:90— ButtonBase has cyclomatic complexity 38 (threshold 15). Of this number, 18 points are the body's own statements and 20 belong to 10 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
grid-v2-props.gridV2Props (cyclomatic 35) packages/mui-codemod/src/v6.0.0/grid-v2-props/grid-v2-props.js:14— grid-v2-props.gridV2Props has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 5 of the 35 points are its own statements and the rest belongs to 14 function literals inside it that branch (lines 63, 82, 46, …). 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.
removeSystemProps.removeSystemProps (cyclomatic 35) packages/mui-codemod/src/v6.0.0/system-props/removeSystemProps.js:138— removeSystemProps.removeSystemProps has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 3 of the 35 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 197, 216, 165, …). 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.
grid-props.gridV2Props (cyclomatic 35) packages/mui-codemod/src/v7.0.0/grid-props/grid-props.js:14— grid-props.gridV2Props has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 5 of the 35 points are its own statements and the rest belongs to 14 function literals inside it that branch (lines 63, 82, 46, …). 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.
Masonry.Masonry (cyclomatic 35) packages/mui-lab/src/Masonry/Masonry.tsx:238— Masonry.Masonry has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 5 of the 35 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 322, 287, 374, …). 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.
Chip.Chip (cyclomatic 35) packages/mui-material/src/Chip/Chip.js:379— Chip.Chip has cyclomatic complexity 35 (threshold 15). Of this number, 27 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
joy-text-field-to-input.transformer (cyclomatic 34) packages/mui-codemod/src/v5.0.0/joy-text-field-to-input.js:5— joy-text-field-to-input.transformer 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 7 function literals inside it that branch (lines 51, 34, 24, …). 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.
(anonymous) (cyclomatic 34) packages/mui-material/src/Button/Button.js:95— (anonymous) has cyclomatic complexity 34 (threshold 15). Of this number, 23 points are the body's own statements and 11 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
LinearProgress (cyclomatic 34) packages/mui-material/src/LinearProgress/LinearProgress.js:421— LinearProgress has cyclomatic complexity 34 (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.
SpeedDial.SpeedDial (cyclomatic 32) packages/mui-material/src/SpeedDial/SpeedDial.js:152— SpeedDial.SpeedDial has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 3 of the 32 points are its own statements and the rest belongs to 9 function items inside it that branch (handleKeyDown, handleClose, handleOpen, …). 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.
PricingCards.PlanPrice (cyclomatic 31) docs/src/components/pricing/PricingCards.tsx:254— PricingCards.PlanPrice has cyclomatic complexity 31 (threshold 15). Of this number, 27 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Rating.Rating (cyclomatic 31) packages/mui-material/src/Rating/Rating.js:369— Rating.Rating has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 7 of the 31 points are its own statements and the rest belongs to 9 function items inside it that branch (handleMouseMove, handleClear, handleMouseLeave, …). 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.
SelectInput (cyclomatic 31) packages/mui-material/src/Select/SelectInput.js:146— SelectInput has cyclomatic complexity 31 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ComponentApiBuilder.generateComponentApi (cyclomatic 30) REDACTED:724— ComponentApiBuilder.generateComponentApi has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
styled-v6.styledV6 (cyclomatic 30) packages/mui-codemod/src/v6.0.0/styled/styled-v6.js:7— styled-v6.styledV6 has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 3 of the 30 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 82, 14, 54, …). 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.
theme-color-functions.transformer (cyclomatic 29) packages/mui-codemod/src/v7.0.0/theme-color-functions/theme-color-functions.js:5— theme-color-functions.transformer has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 8 of the 29 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 166, a function literal at line 77, a function literal at line 28, …). 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.
AppLayoutDocsFooter.AppLayoutDocsFooter (cyclomatic 28) packages-internal/core-docs/src/AppLayout/layout/AppLayoutDocsFooter.tsx:143— AppLayoutDocsFooter.AppLayoutDocsFooter has cyclomatic complexity 28 (threshold 15). Of this number, 16 points are the body's own statements and 12 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.
createRender (cyclomatic 28) REDACTED:293— createRender has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 1 of the 28 points is its own statement and the rest belongs to 9 function items inside it that branch (render::heading, render::code, render::link, …). 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.
Collapse (cyclomatic 28) packages/mui-material/src/Collapse/Collapse.js:137— Collapse has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 7 of the 28 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 200, a function literal at line 257, a function literal at line 187, …). 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.
HeaderNavBar.HeaderNavBar (cyclomatic 27) docs/src/components/header/HeaderNavBar.tsx:135— HeaderNavBar.HeaderNavBar has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 7 of the 27 points are its own statements and the rest belongs to 6 function items inside it that branch (handleKeyDown, a function literal at line 143, a function literal at line 167, …). 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.
jss-to-tss-react.transformStylesExpression (cyclomatic 27) packages/mui-codemod/src/v5.0.0/jss-to-tss-react.js:49— jss-to-tss-react.transformStylesExpression has cyclomatic complexity 27 (threshold 15). Of this number, 15 points are the body's own statements and 12 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
createTheme.createTheme (cyclomatic 27) packages/mui-material/src/styles/createTheme.ts:65— createTheme.createTheme has cyclomatic complexity 27 (threshold 15). Of this number, 26 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.
TextareaAutosize.TextareaAutosize (cyclomatic 27) packages/mui-material/src/TextareaAutosize/TextareaAutosize.tsx:60— TextareaAutosize.TextareaAutosize has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 7 function items inside it that branch (a function literal at line 72, a function literal at line 144, a function literal at line 131, …). 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.
AppNavDrawerItem.Item (cyclomatic 26) packages-internal/core-docs/src/AppLayout/navigation/AppNavDrawerItem.tsx:27— AppNavDrawerItem.Item has cyclomatic complexity 26 (threshold 15). Of this number, 25 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
useRovingTabIndex.useRovingTabIndexRoot (cyclomatic 25) packages/mui-utils/src/useRovingTabIndex/useRovingTabIndex.ts:198— useRovingTabIndex.useRovingTabIndexRoot has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 4 of the 25 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 336, 264, 275, …). 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.
MiniTableOfContents.MiniTableOfContents (cyclomatic 24) packages-internal/core-docs/src/TableOfContents/MiniTableOfContents.tsx:152— MiniTableOfContents.MiniTableOfContents has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 2 of the 24 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 233, getWidthIncrease, handleBarClick, …). 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.
DemoToolbar.DemoToolbar (cyclomatic 24) packages-internal/core-docs/src/DemoContent/DemoToolbar.tsx:275— DemoToolbar.DemoToolbar has cyclomatic complexity 24 (threshold 15). Of this number, 17 points are the body's own statements and 7 belong to 4 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.
base-remove-component-prop.transformer (cyclomatic 24) packages/mui-codemod/src/v5.0.0/base-remove-component-prop.js:5— base-remove-component-prop.transformer has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 25, 16). 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.
(anonymous) (cyclomatic 24) packages/mui-material/src/ToggleButton/ToggleButton.js:46— (anonymous) has cyclomatic complexity 24 (threshold 15). Of this number, 16 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
prepareMarkdown.prepareMarkdown (cyclomatic 23) packages-internal/markdown/prepareMarkdown.mjs:78— prepareMarkdown.prepareMarkdown has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 3 of the 23 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 91, 173, 90, …). 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.
createPalette.createPalette (cyclomatic 23) packages/mui-material/src/styles/createPalette.js:211— createPalette.createPalette has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 11 of the 23 points are its own statements and the rest belongs to 2 function items inside it that branch (augmentColor, getContrastText). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
useAutocomplete.useAutocomplete.selectNewValue (cyclomatic 23) packages/mui-material/src/useAutocomplete/useAutocomplete.js:854— useAutocomplete.useAutocomplete.selectNewValue has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
resolveProps.resolveProps (cyclomatic 23) packages/mui-utils/src/resolveProps/resolveProps.ts:12— resolveProps.resolveProps has cyclomatic complexity 23 (threshold 15). Of this number, 21 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
useAutocomplete.selectNewValue (cyclomatic 23) packages/mui-material/src/useAutocomplete/useAutocomplete.js:854— useAutocomplete.selectNewValue has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
(anonymous) (cyclomatic 23) packages/mui-material/src/Tab/Tab.js:53— (anonymous) has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 10 of the 23 points are its own statements and the rest belongs to 9 function items inside it that branch (props, props, props, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
XGridGlobalStyles.XGridGlobalStyles (cyclomatic 22) docs/src/components/home/XGridGlobalStyles.tsx:4— XGridGlobalStyles.XGridGlobalStyles 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 one function literal inside it that branches (line 13). 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.
ComponentApiBuilder.attachPropsTable (cyclomatic 22) REDACTED:514— ComponentApiBuilder.attachPropsTable 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 one function literal inside it that branches (line 522). 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.
PropertiesList.PropertiesList (cyclomatic 22) REDACTED:115— PropertiesList.PropertiesList 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 120, 223). 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.
theme-v6.themeV6 (cyclomatic 22) packages/mui-codemod/src/v6.0.0/theme-v6/theme-v6.js:8— theme-v6.themeV6 has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 3 of the 22 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 15, 88, 43, …). 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.
mergeSlotProps.mergeSlotProps (cyclomatic 22) packages/mui-material/src/utils/mergeSlotProps.ts:5— mergeSlotProps.mergeSlotProps has cyclomatic complexity 22 (threshold 15). Of this number, 11 points are the body's own statements and 11 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
useAutocomplete.useAutocomplete.changeHighlightedIndex (cyclomatic 22) packages/mui-material/src/useAutocomplete/useAutocomplete.js:527— useAutocomplete.useAutocomplete.changeHighlightedIndex 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 one function item inside it that branches (getNextIndex). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
useSlider.useSlider.createHandleHiddenInputKeyDown.<returned closure> (cyclomatic 22) packages/mui-material/src/Slider/useSlider.ts:394— useSlider.useSlider.createHandleHiddenInputKeyDown.<returned closure> 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.
TextField.TextField (cyclomatic 22) packages/mui-material/src/TextField/TextField.js:75— TextField.TextField 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.
spacing.createUnaryUnit (cyclomatic 22) packages/mui-system/src/spacing/spacing.ts:101— spacing.createUnaryUnit has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 6 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 116, 143). 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.
useCurrentColorScheme.useCurrentColorScheme (cyclomatic 22) packages/mui-system/src/cssVars/useCurrentColorScheme.ts:114— useCurrentColorScheme.useCurrentColorScheme has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 6 of the 22 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 289, 144, 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.
SelectInput::handleClosedTypeahead (cyclomatic 22) packages/mui-material/src/Select/SelectInput.js:550— SelectInput::handleClosedTypeahead has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
MarkdownDocsV2.MarkdownDocsV2 (cyclomatic 21) docs/src/modules/components/MarkdownDocsV2.js:39— MarkdownDocsV2.MarkdownDocsV2 has cyclomatic complexity 21 (threshold 15). Of this number, 15 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
generatePropDescription.generatePropDescription (cyclomatic 21) packages-internal/api-docs-builder/src/utils/generatePropDescription.ts:83— generatePropDescription.generatePropDescription has cyclomatic complexity 21 (threshold 15). Of this number, 16 points are the body's own statements and 5 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.
Ad.Ad (cyclomatic 21) packages-internal/core-docs/src/Ad/Ad.tsx:113— Ad.Ad has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 147, 191, 212, …). 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.
Notifications.Notifications (cyclomatic 21) packages-internal/core-docs/src/AppLayout/layout/Notifications.tsx:60— Notifications.Notifications has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 74, handleToggle, a function literal at line 111, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
optimal-imports.transformer (cyclomatic 21) REDACTED:5— optimal-imports.transformer has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 56, a function literal at line 26, addSpecifier). 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.
Slide.Slide (cyclomatic 21) packages/mui-material/src/Slide/Slide.js:113— Slide.Slide has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 286, 242, 150, …). 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.
Slider.Slider (cyclomatic 21) packages/mui-material/src/Slider/Slider.js:563— Slider.Slider 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 3 function literals inside it that branch (lines 722, 773, 721). 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.
Tabs.Tabs (cyclomatic 21) packages/mui-material/src/Tabs/Tabs.js:257— Tabs.Tabs has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (Tabs.Tabs::getTabsMeta) 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.
createStyled.createStyled.styled (cyclomatic 21) packages/mui-system/src/createStyled/createStyled.ts:176— createStyled.createStyled.styled has cyclomatic complexity 21 (threshold 15). Of this number, 14 points are the body's own statements and 7 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppNavDrawerItem.AppNavDrawerItem (cyclomatic 20) packages-internal/core-docs/src/AppLayout/navigation/AppNavDrawerItem.tsx:315— AppNavDrawerItem.AppNavDrawerItem has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body: 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.
ApiPage.ApiPage (cyclomatic 20) REDACTED:85— ApiPage.ApiPage has cyclomatic complexity 20 (threshold 15). Of this number, 16 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
optimal-imports.transformer (cyclomatic 20) REDACTED:5— optimal-imports.transformer has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 4 of the 20 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 49, a function literal at line 26, addSpecifier). 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.
TablePagination (cyclomatic 20) packages/mui-material/src/TablePagination/TablePagination.js:169— TablePagination has cyclomatic complexity 20 (threshold 15). Of this number, 15 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CustomersSpotlight.Spotlight (cyclomatic 19) docs/src/components/customers/CustomersSpotlight.tsx:18— CustomersSpotlight.Spotlight has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 75, 51, 45, …). 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.
XDataGrid.XDataGrid (cyclomatic 19) docs/src/components/productX/XDataGrid.tsx:58— XDataGrid.XDataGrid has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 75, 82). 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.
defaultPropsHandler.getDefaultValue (cyclomatic 19) packages-internal/api-docs-builder/src/utils/defaultPropsHandler.ts:65— defaultPropsHandler.getDefaultValue has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
generatePropTypeDescription.generatePropTypeDescription (cyclomatic 19) packages-internal/api-docs-builder/src/utils/generatePropTypeDescription.ts:70— generatePropTypeDescription.generatePropTypeDescription has cyclomatic complexity 19 (threshold 15). Of this number, 18 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.
PropertiesTable.PropertiesTable (cyclomatic 19) REDACTED:138— PropertiesTable.PropertiesTable has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 156, 262). 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.
Masonry.getStyle (cyclomatic 19) packages/mui-lab/src/Masonry/Masonry.tsx:96— Masonry.getStyle has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 3 function items inside it that branch (spacingStyleFromPropValue, columnStyleFromPropValue, a function literal at line 199). 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.
useAutocomplete.useAutocomplete.syncHighlightedIndexToDOM (cyclomatic 19) packages/mui-material/src/useAutocomplete/useAutocomplete.js:414— useAutocomplete.useAutocomplete.syncHighlightedIndexToDOM has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BasePopper.PopperTooltip (cyclomatic 19) packages/mui-material/src/Popper/BasePopper.tsx:75— BasePopper.PopperTooltip has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 123, 117, 198). 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.
TableCell.TableCell (cyclomatic 19) packages/mui-material/src/TableCell/TableCell.js:174— TableCell.TableCell has cyclomatic complexity 19 (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.
useAutocomplete.useAutocomplete.syncHighlightedIndex (cyclomatic 18) packages/mui-material/src/useAutocomplete/useAutocomplete.js:651— useAutocomplete.useAutocomplete.syncHighlightedIndex 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.
(anonymous) (cyclomatic 18) packages/mui-material/src/Switch/Switch.js:175— (anonymous) has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 189). 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.
blog.Blog (cyclomatic 17) docs/pages/blog.tsx:187— blog.Blog has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 300, 385, 201, …). 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.
createDescribeableProp.createDescribeableProp (cyclomatic 17) packages-internal/api-docs-builder/src/utils/createDescribeableProp.ts:34— createDescribeableProp.createDescribeableProp has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
defaultPropsHandler.getExplicitPropsDeclaration (cyclomatic 17) packages-internal/api-docs-builder/src/utils/defaultPropsHandler.ts:201— defaultPropsHandler.getExplicitPropsDeclaration 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.
ComponentApiBuilder.generateApiPage (cyclomatic 17) REDACTED:314— ComponentApiBuilder.generateApiPage has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
brandingTheme.getDesignTokens (cyclomatic 17) packages-internal/core-docs/src/branding/brandingTheme.ts:205— brandingTheme.getDesignTokens has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DemoContentLoading.DemoContentLoading (cyclomatic 17) packages-internal/core-docs/src/DemoContent/DemoContentLoading.tsx:35— DemoContentLoading.DemoContentLoading has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs 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.
typography-props.transformer (cyclomatic 17) packages/mui-codemod/src/deprecations/typography-props/typography-props.js:9— typography-props.transformer has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 17, 80, 19, …). 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.
material-design-icons.myDestRewriter (cyclomatic 17) packages/mui-icons-material/renameFilters/material-design-icons.mjs:26— material-design-icons.myDestRewriter has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SwitchBase.SwitchBase (cyclomatic 17) packages/mui-material/src/internal/SwitchBase.js:83— SwitchBase.SwitchBase 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 3 function items inside it that branch (handleFocus, handleBlur, handleInputChange). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Tabs.Tabs::getTabsMeta (cyclomatic 17) packages/mui-material/src/Tabs/Tabs.js:361— Tabs.Tabs::getTabsMeta 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. This shape REPEATS in the file: one other method here (Tabs.Tabs) 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.
Button (cyclomatic 17) packages/mui-material/src/Button/Button.js:501— Button has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
CircularProgress (cyclomatic 17) packages/mui-material/src/CircularProgress/CircularProgress.js:223— CircularProgress 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.
MaterialDesignComponents.Grid (cyclomatic 16) docs/src/components/home/MaterialDesignComponents.tsx:33— MaterialDesignComponents.Grid has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AppTableOfContents.AppTableOfContents (cyclomatic 16) REDACTED:86— AppTableOfContents.AppTableOfContents has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 95, 143, 161, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
useMuiChatExporter.useMuiChatExporter (cyclomatic 16) packages-internal/core-docs/src/DemoContent/useMuiChatExporter.ts:136— useMuiChatExporter.useMuiChatExporter has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 166, 144, 194, …). 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.
list-item-button-prop.transformer (cyclomatic 16) packages/mui-codemod/src/v6.0.0/list-item-button-prop/list-item-button-prop.js:8— list-item-button-prop.transformer has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 101, 47, 83, …). 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.
FormControl.FormControl (cyclomatic 16) packages/mui-material/src/FormControl/FormControl.js:93— FormControl.FormControl has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 134, 155, 128, …). 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.
InputBase.useUtilityClasses (cyclomatic 16) packages/mui-material/src/InputBase/InputBase.js:50— InputBase.useUtilityClasses has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
useFocusableWhenDisabled.useFocusableWhenDisabled.props (cyclomatic 16) packages/mui-material/src/utils/useFocusableWhenDisabled.ts:49— useFocusableWhenDisabled.useFocusableWhenDisabled.props has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Grow.Grow (cyclomatic 16) packages/mui-material/src/Grow/Grow.js:34— Grow.Grow has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 114, 61, 166). 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.
useSlider.useSlider (cyclomatic 16) packages/mui-material/src/Slider/useSlider.ts:203— useSlider.useSlider has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 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.
ClickAwayListener.ClickAwayListener (cyclomatic 16) packages/mui-material/src/ClickAwayListener/ClickAwayListener.tsx:70— ClickAwayListener.ClickAwayListener has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 102, 146, 164, …). 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.
Deprecated: @material-ui/core packages/mui-codemod/package.json:42— @material-ui/core 4.12.4, declared in packages/mui-codemod/package.json, is marked deprecated by its publisher: "Material UI v4 doesn't receive active development since September 2021. See the guide https://mui.com/material-ui/migration/migration-v4/ to upgrade to v5.". Replace it with the package or version that message names, or record why this one must stay.
FixmeComment packages/mui-material/src/TextField/TextField.spec.tsx:55— // FIXME this no longer generates an error in TS 3.2, see https://github.com/Microsoft/TypeScript/issues/28926
HackComment docs/src/components/pricing/PricingTable.tsx:1533— // Hack to keep nested grid aligned with others — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
brandingTheme.getThemedComponents (cognitive 230) packages-internal/core-docs/src/branding/brandingTheme.ts:431— brandingTheme.getThemedComponents has cognitive complexity 230 (threshold 15). Drivers by points: boolean chains 230. None of this is in the body itself: all 230 points belong to 22 function literals inside it that branch (lines 1103, 550, 436, …). 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.
sx-v6.sxV6 (cognitive 212) packages/mui-codemod/src/v6.0.0/sx-prop/sx-v6.js:33— sx-v6.sxV6 has cognitive complexity 212 (threshold 15). Drivers by points: if/else 71 (174 pts), boolean chains 31, ternaries 3 (7 pts) (nesting depth added 107). Most of this is not in the body itself: 3 of the 212 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 180, a function literal at line 57, a function literal at line 511, …). 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.
transformer (cognitive 201) packages/mui-codemod/src/v5.0.0/jss-to-styled.js:7— transformer has cognitive complexity 201 (threshold 15). Drivers by points: if/else 85 (170 pts), boolean chains 18, ternaries 6 (13 pts) (nesting depth added 92). Most of this is not in the body itself: 13 of the 201 points are its own statements and the rest belongs to 50 function items inside it that branch (a function literal at line 83, getReturnStatement, a function literal at line 453, …). 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.
migrateToVariants.migrateToVariants (cognitive 199) packages/mui-codemod/src/util/migrateToVariants.js:182— migrateToVariants.migrateToVariants has cognitive complexity 199 (threshold 15). Drivers by points: if/else 73 (164 pts), boolean chains 23, ternaries 4 (8 pts), loops 2 (4 pts) (nesting depth added 97). None of this is in the body itself: all 199 points belong to 17 function items inside it that branch (a function literal at line 413, a function literal at line 321, a function literal at line 317, …). 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.
createThemeWithVars.createThemeWithVars (cognitive 188) packages/mui-material/src/styles/createThemeWithVars.js:138— createThemeWithVars.createThemeWithVars has cognitive complexity 188 (threshold 15). Drivers by points: ternaries 67 (137 pts), if/else 27 (40 pts), boolean chains 11 (nesting depth added 83). Of this number, 16 points are the body's own statements and 172 belong to 7 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.
SelectInput (cognitive 150) packages/mui-material/src/Select/SelectInput.js:146— SelectInput has cognitive complexity 150 (threshold 15). Drivers by points: if/else 76 (96 pts), boolean chains 26, ternaries 20 (26 pts), other 2 (nesting depth added 26). Of this number, 38 points are the body's own statements and 112 belong to 52 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
sxV6::(anonymous)::recurseObjectExpression (cognitive 137) packages/mui-codemod/src/v6.0.0/sx-prop/sx-v6.js:180— sxV6::(anonymous)::recurseObjectExpression has cognitive complexity 137 (threshold 15). Drivers by points: if/else 41 (112 pts), boolean chains 22, ternaries 1 (3 pts) (nesting depth added 73). 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.
SwipeableDrawer (cognitive 120) packages/mui-material/src/SwipeableDrawer/SwipeableDrawer.js:139— SwipeableDrawer has cognitive complexity 120 (threshold 15). Drivers by points: if/else 48 (69 pts), boolean chains 26, ternaries 14 (25 pts) (nesting depth added 32). Most of this is not in the body itself: 7 of the 120 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 347, a function literal at line 488, a function literal at line 244, …). 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.
useAutocomplete.handleKeyDown (cognitive 108) packages/mui-material/src/useAutocomplete/useAutocomplete.js:995— useAutocomplete.handleKeyDown has cognitive complexity 108 (threshold 15). Drivers by points: if/else 28 (75 pts), boolean chains 23, ternaries 2 (8 pts), match/switch 1 (2 pts) (nesting depth added 54). None of this is in the body itself: all 108 points belong to 2 function literals inside it that branch (lines 995, 1186). 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.
useAutocomplete.useAutocomplete.handleKeyDown.<returned closure> (cognitive 107) packages/mui-material/src/useAutocomplete/useAutocomplete.js:995— useAutocomplete.useAutocomplete.handleKeyDown.<returned closure> has cognitive complexity 107 (threshold 15). Drivers by points: if/else 28 (75 pts), boolean chains 22, ternaries 2 (8 pts), match/switch 1 (2 pts) (nesting depth added 54). Of this number, 102 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
migrateToVariants::(anonymous)::recurseObjectExpression (cognitive 93) packages/mui-codemod/src/util/migrateToVariants.js:413— migrateToVariants::(anonymous)::recurseObjectExpression has cognitive complexity 93 (threshold 15). Drivers by points: if/else 27 (79 pts), boolean chains 8, ternaries 2 (6 pts) (nesting depth added 56). 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.
jss-to-tss-react.transformer (cognitive 87) packages/mui-codemod/src/v5.0.0/jss-to-tss-react.js:191— jss-to-tss-react.transformer has cognitive complexity 87 (threshold 15). Drivers by points: if/else 35 (71 pts), boolean chains 9, ternaries 3 (7 pts) (nesting depth added 40). Most of this is not in the body itself: 5 of the 87 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 376, 204, 298, …). 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.
Tooltip (cognitive 75) packages/mui-material/src/Tooltip/Tooltip.js:237— Tooltip has cognitive complexity 75 (threshold 15). Drivers by points: if/else 35 (42 pts), ternaries 11 (16 pts), boolean chains 15, other 2 (nesting depth added 12). Of this number, 31 points are the body's own statements and 44 belong to 28 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DemoContent.DemoContent (cognitive 71) packages-internal/core-docs/src/DemoContent/DemoContent.tsx:87— DemoContent.DemoContent has cognitive complexity 71 (threshold 15). Drivers by points: if/else 19 (25 pts), ternaries 18 (23 pts), boolean chains 21, loops 1 (2 pts) (nesting depth added 12). Of this number, 40 points are the body's own statements and 31 belong to 11 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.
AppSearch.AppSearch (cognitive 70) REDACTED:219— AppSearch.AppSearch has cognitive complexity 70 (threshold 15). Drivers by points: boolean chains 53, if/else 9 (11 pts), ternaries 4, loops 1 (2 pts) (nesting depth added 3). Most of this is not in the body itself: 12 of the 70 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 428, 761, 308, …). 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.
jss-to-tss-react.transformStylesExpression (cognitive 70) packages/mui-codemod/src/v5.0.0/jss-to-tss-react.js:49— jss-to-tss-react.transformStylesExpression has cognitive complexity 70 (threshold 15). Drivers by points: if/else 25 (66 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 42). Of this number, 30 points are the body's own statements and 40 belong to 4 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.
createCssVarsProvider.createCssVarsProvider.CssVarsProvider (cognitive 70) packages/mui-system/src/cssVars/createCssVarsProvider.tsx:216— createCssVarsProvider.createCssVarsProvider.CssVarsProvider has cognitive complexity 70 (threshold 15). Drivers by points: if/else 24 (39 pts), boolean chains 17, ternaries 11 (14 pts) (nesting depth added 18). Of this number, 25 points are the body's own statements and 45 belong to 7 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.
InputBase (cognitive 70) packages/mui-material/src/InputBase/InputBase.js:248— InputBase has cognitive complexity 70 (threshold 15). Drivers by points: if/else 36 (48 pts), boolean chains 18, ternaries 4 (nesting depth added 12). Of this number, 25 points are the body's own statements and 45 belong to 13 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
Transition.Transition (cognitive 69) packages/mui-material/src/internal/Transition.tsx:100— Transition.Transition has cognitive complexity 69 (threshold 15). Drivers by points: if/else 35 (46 pts), boolean chains 15, ternaries 5 (8 pts) (nesting depth added 14). Most of this is not in the body itself: 6 of the 69 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 394, 216, 372, …). 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.
ComponentApiBuilder.generateComponentApi (cognitive 63) REDACTED:724— ComponentApiBuilder.generateComponentApi has cognitive complexity 63 (threshold 15). Drivers by points: if/else 19 (53 pts), boolean chains 5, loops 1 (3 pts), error handling 2 (nesting depth added 36). 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.
FocusTrap.FocusTrap (cognitive 63) packages/mui-material/src/Unstable_TrapFocus/FocusTrap.tsx:129— FocusTrap.FocusTrap has cognitive complexity 63 (threshold 15). Drivers by points: if/else 36 (48 pts), boolean chains 13, ternaries 2 (nesting depth added 12). Most of this is not in the body itself: 2 of the 63 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 286, a function literal at line 221, a function literal at line 164, …). 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.
LinearProgress (cognitive 55) packages/mui-material/src/LinearProgress/LinearProgress.js:421— LinearProgress has cognitive complexity 55 (threshold 15). Drivers by points: if/else 16 (37 pts), boolean chains 8, ternaries 4 (8 pts), other 2 (nesting depth added 25). 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.
Autocomplete (cognitive 54) packages/mui-material/src/Autocomplete/Autocomplete.js:432— Autocomplete has cognitive complexity 54 (threshold 15). Drivers by points: boolean chains 18, if/else 13 (17 pts), ternaries 14 (17 pts), other 2 (nesting depth added 7). Of this number, 40 points are the body's own statements and 14 belong to 15 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
HookApiBuilder.annotateHookDefinition (cognitive 53) packages-internal/api-docs-builder/src/ApiBuilders/HookApiBuilder.ts:30— HookApiBuilder.annotateHookDefinition has cognitive complexity 53 (threshold 15). Drivers by points: if/else 26 (35 pts), ternaries 8 (11 pts), boolean chains 7 (nesting depth added 12). Of this number, 41 points are the body's own statements and 12 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.
removeSystemProps (cognitive 52) packages/mui-codemod/src/v9.0.0/system-props/removeSystemProps.js:148— removeSystemProps has cognitive complexity 52 (threshold 15). Drivers by points: if/else 23 (36 pts), boolean chains 12, ternaries 2 (4 pts) (nesting depth added 15). Most of this is not in the body itself: 4 of the 52 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 246, a function literal at line 214, a function literal at line 265, …). 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.
useAutocomplete.useAutocomplete (cognitive 51) packages/mui-material/src/useAutocomplete/useAutocomplete.js:97— useAutocomplete.useAutocomplete has cognitive complexity 51 (threshold 15). Drivers by points: boolean chains 24, if/else 12 (16 pts), ternaries 7 (11 pts) (nesting depth added 8). Of this number, 22 points are the body's own statements and 29 belong to 8 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MenuList (cognitive 51) packages/mui-material/src/MenuList/MenuList.js:79— MenuList has cognitive complexity 51 (threshold 15). Drivers by points: if/else 21 (29 pts), boolean chains 15, ternaries 2 (5 pts), other 2 (nesting depth added 11). None of this is in the body itself: all 51 points belong to 14 function items inside it that branch (a function literal at line 258, a function literal at line 135, (anonymous)::adjustStyleForScrollbar, …). 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.
MaterialDesignComponents.buildTheme (cognitive 50) docs/src/components/home/MaterialDesignComponents.tsx:208— MaterialDesignComponents.buildTheme has cognitive complexity 50 (threshold 15). Drivers by points: boolean chains 50. None of this is in the body itself: all 50 points belong to 10 function literals inside it that branch (lines 364, 284, 331, …). 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.
ComponentApiBuilder.annotateComponentDefinition (cognitive 49) REDACTED:79— ComponentApiBuilder.annotateComponentDefinition has cognitive complexity 49 (threshold 15). Drivers by points: if/else 25 (33 pts), ternaries 8 (10 pts), boolean chains 6 (nesting depth added 10). Of this number, 38 points are the body's own statements and 11 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.
(anonymous) (cognitive 46) packages/mui-material/src/Chip/Chip.js:66— (anonymous) has cognitive complexity 46 (threshold 15). Drivers by points: boolean chains 40, ternaries 6. Of this number, 27 points are the body's own statements and 19 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
grid-v2-props.gridV2Props (cognitive 45) packages/mui-codemod/src/v6.0.0/grid-v2-props/grid-v2-props.js:14— grid-v2-props.gridV2Props has cognitive complexity 45 (threshold 15). Drivers by points: if/else 25 (35 pts), boolean chains 9, ternaries 1 (nesting depth added 10). Most of this is not in the body itself: 4 of the 45 points are its own statements and the rest belongs to 14 function literals inside it that branch (lines 63, 82, 46, …). 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.
grid-props.gridV2Props (cognitive 45) packages/mui-codemod/src/v7.0.0/grid-props/grid-props.js:14— grid-props.gridV2Props has cognitive complexity 45 (threshold 15). Drivers by points: if/else 25 (35 pts), boolean chains 9, ternaries 1 (nesting depth added 10). Most of this is not in the body itself: 4 of the 45 points are its own statements and the rest belongs to 14 function literals inside it that branch (lines 63, 82, 46, …). 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.
removeSystemProps (cognitive 45) packages/mui-codemod/src/v6.0.0/system-props/removeSystemProps.js:138— removeSystemProps has cognitive complexity 45 (threshold 15). Drivers by points: if/else 19 (30 pts), boolean chains 11, ternaries 2 (4 pts) (nesting depth added 13). Most of this is not in the body itself: 2 of the 45 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 197, a function literal at line 165, a function literal at line 216, …). 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.
joy-text-field-to-input.transformer (cognitive 43) packages/mui-codemod/src/v5.0.0/joy-text-field-to-input.js:5— joy-text-field-to-input.transformer has cognitive complexity 43 (threshold 15). Drivers by points: if/else 13 (30 pts), match/switch 3 (10 pts), boolean chains 3 (nesting depth added 24). None of this is in the body itself: all 43 points belong to 7 function literals inside it that branch (lines 24, 34, 51, …). 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.
createTheme.createTheme (cognitive 41) packages/mui-material/src/styles/createTheme.ts:65— createTheme.createTheme has cognitive complexity 41 (threshold 15). Drivers by points: if/else 12 (26 pts), boolean chains 10, ternaries 3 (5 pts) (nesting depth added 16). Of this number, 38 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.
resolveProps.resolveProps (cognitive 41) packages/mui-utils/src/resolveProps/resolveProps.ts:12— resolveProps.resolveProps has cognitive complexity 41 (threshold 15). Drivers by points: if/else 12 (29 pts), boolean chains 6, loops 2 (6 pts) (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.
SpeedDial (cognitive 41) packages/mui-material/src/SpeedDial/SpeedDial.js:152— SpeedDial has cognitive complexity 41 (threshold 15). Drivers by points: if/else 22 (29 pts), boolean chains 6, ternaries 5 (6 pts) (nesting depth added 8). Most of this is not in the body itself: 2 of the 41 points are its own statements and the rest belongs to 19 function items inside it that branch (handleKeyDown, handleClose, handleClick, …). 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.
PricingCards.PlanPrice (cognitive 38) docs/src/components/pricing/PricingCards.tsx:254— PricingCards.PlanPrice has cognitive complexity 38 (threshold 15). Drivers by points: if/else 17 (20 pts), ternaries 6 (10 pts), boolean chains 8 (nesting depth added 7). Of this number, 33 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Masonry.Masonry (cognitive 38) packages/mui-lab/src/Masonry/Masonry.tsx:238— Masonry.Masonry has cognitive complexity 38 (threshold 15). Drivers by points: if/else 18 (23 pts), boolean chains 9, ternaries 3 (5 pts), loops 1 (nesting depth added 7). Most of this is not in the body itself: 2 of the 38 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 322, 287, 374, …). 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.
Popover (cognitive 38) packages/mui-material/src/Popover/Popover.js:95— Popover has cognitive complexity 38 (threshold 15). Drivers by points: if/else 19 (24 pts), boolean chains 9, ternaries 5 (nesting depth added 5). Most of this is not in the body itself: 7 of the 38 points are its own statements and the rest belongs to 17 function items inside it that branch (a function literal at line 140, a function literal at line 200, a function literal at line 284, …). 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.
transformer (cognitive 38) packages/mui-codemod/src/v7.0.0/theme-color-functions/theme-color-functions.js:5— transformer has cognitive complexity 38 (threshold 15). Drivers by points: if/else 18 (28 pts), boolean chains 8, loops 1 (2 pts) (nesting depth added 11). Most of this is not in the body itself: 6 of the 38 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 166, a function literal at line 28, a function literal at line 77, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
HeaderNavBar.HeaderNavBar (cognitive 37) docs/src/components/header/HeaderNavBar.tsx:135— HeaderNavBar.HeaderNavBar has cognitive complexity 37 (threshold 15). Drivers by points: if/else 17 (27 pts), ternaries 7, boolean chains 3 (nesting depth added 10). Most of this is not in the body itself: 6 of the 37 points are its own statements and the rest belongs to 6 function items inside it that branch (handleKeyDown, a function literal at line 143, a function literal at line 167, …). 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.
spacing.createUnaryUnit (cognitive 37) packages/mui-system/src/spacing/spacing.ts:101— spacing.createUnaryUnit has cognitive complexity 37 (threshold 15). Drivers by points: if/else 17 (33 pts), boolean chains 4 (nesting depth added 16). Most of this is not in the body itself: 5 of the 37 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 116, 143). 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.
Chip (cognitive 36) packages/mui-material/src/Chip/Chip.js:379— Chip has cognitive complexity 36 (threshold 15). Drivers by points: boolean chains 16, if/else 10 (12 pts), ternaries 7 (8 pts) (nesting depth added 3). Of this number, 28 points are the body's own statements and 8 belong to 7 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
(anonymous) (cognitive 36) packages/mui-material/src/PaginationItem/PaginationItem.js:110— (anonymous) has cognitive complexity 36 (threshold 15). Drivers by points: boolean chains 34, ternaries 2. Of this number, 20 points are the body's own statements and 16 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
TablePaginationActions (cognitive 36) packages/mui-material/src/TablePaginationActions/TablePaginationActions.js:59— TablePaginationActions has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 14, boolean chains 10, other 8, if/else 4. Of this number, 27 points are the body's own statements and 9 belong to 8 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ButtonBase (cognitive 34) packages/mui-material/src/ButtonBase/ButtonBase.js:90— ButtonBase has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (17 pts), boolean chains 10, ternaries 4 (5 pts), other 2 (nesting depth added 3). Of this number, 18 points are the body's own statements and 16 belong to 10 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
defaultPropsHandler.getDefaultValue (cognitive 33) packages-internal/api-docs-builder/src/utils/defaultPropsHandler.ts:65— defaultPropsHandler.getDefaultValue has cognitive complexity 33 (threshold 15). Drivers by points: if/else 14 (27 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Rating.Rating (cognitive 33) packages/mui-material/src/Rating/Rating.js:369— Rating.Rating has cognitive complexity 33 (threshold 15). Drivers by points: if/else 16, ternaries 6 (9 pts), boolean chains 8 (nesting depth added 3). Most of this is not in the body itself: 5 of the 33 points are its own statements and the rest belongs to 9 function items inside it that branch (handleMouseMove, handleClear, handleMouseLeave, …). 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.
(anonymous) (cognitive 33) packages/mui-material/src/Button/Button.js:95— (anonymous) has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 27, ternaries 5, other 1. Of this number, 22 points are the body's own statements and 11 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
styled-v6.styledV6 (cognitive 32) packages/mui-codemod/src/v6.0.0/styled/styled-v6.js:7— styled-v6.styledV6 has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 9, ternaries 1 (2 pts) (nesting depth added 9). Most of this is not in the body itself: 3 of the 32 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 54, 82, 14, …). 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.
useSlider.useSlider.createHandleHiddenInputKeyDown.<returned closure> (cognitive 32) packages/mui-material/src/Slider/useSlider.ts:394— useSlider.useSlider.createHandleHiddenInputKeyDown.<returned closure> has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (20 pts), ternaries 3 (9 pts), match/switch 1 (3 pts) (nesting depth added 18). 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.
XDataGrid.XDataGrid (cognitive 31) docs/src/components/productX/XDataGrid.tsx:58— XDataGrid.XDataGrid has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (25 pts), boolean chains 6 (nesting depth added 14). Most of this is not in the body itself: 4 of the 31 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 75, 82). 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.
AppLayoutDocsFooter.AppLayoutDocsFooter (cognitive 31) packages-internal/core-docs/src/AppLayout/layout/AppLayoutDocsFooter.tsx:143— AppLayoutDocsFooter.AppLayoutDocsFooter has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 10 (13 pts), if/else 9 (10 pts), boolean chains 8 (nesting depth added 4). Of this number, 17 points are the body's own statements and 14 belong to 5 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
base-remove-component-prop.transformer (cognitive 31) packages/mui-codemod/src/v5.0.0/base-remove-component-prop.js:5— base-remove-component-prop.transformer has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (23 pts), boolean chains 8 (nesting depth added 8). None of this is in the body itself: all 31 points belong to 2 function literals inside it that branch (lines 25, 16). 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.
theme-v6.themeV6 (cognitive 31) packages/mui-codemod/src/v6.0.0/theme-v6/theme-v6.js:8— theme-v6.themeV6 has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (23 pts), boolean chains 6, ternaries 1 (2 pts) (nesting depth added 11). Most of this is not in the body itself: 3 of the 31 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 15, 43, 88, …). 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.
useAutocomplete.selectNewValue (cognitive 31) packages/mui-material/src/useAutocomplete/useAutocomplete.js:854— useAutocomplete.selectNewValue has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 10, ternaries 3 (5 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.
movePropIntoSlotProps.moveJsxPropIntoSlotProps (cognitive 30) packages/mui-codemod/src/deprecations/utils/movePropIntoSlotProps.js:6— movePropIntoSlotProps.moveJsxPropIntoSlotProps has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (20 pts), ternaries 3 (9 pts), boolean chains 1 (nesting depth added 17). Most of this is not in the body itself: 8 of the 30 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 19, 8). 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.
createRender (cognitive 30) REDACTED:293— createRender has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (17 pts), ternaries 7 (8 pts), boolean chains 5 (nesting depth added 3). None of this is in the body itself: all 30 points belong to 9 function items inside it that branch (render::heading, render::code, render::link, …). 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.
useCurrentColorScheme.useCurrentColorScheme.setColorScheme (cognitive 29) packages/mui-system/src/cssVars/useCurrentColorScheme.ts:183— useCurrentColorScheme.useCurrentColorScheme.setColorScheme has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (24 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 13). Most of this is not in the body itself: 7 of the 29 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 214, 200). 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.
Tabs::getTabsMeta (cognitive 29) packages/mui-material/src/Tabs/Tabs.js:361— Tabs::getTabsMeta has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (18 pts), ternaries 2 (8 pts), boolean chains 3 (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.
useAutocomplete.useAutocomplete.selectNewValue (cognitive 28) packages/mui-material/src/useAutocomplete/useAutocomplete.js:854— useAutocomplete.useAutocomplete.selectNewValue has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 9, ternaries 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.
Collapse (cognitive 28) packages/mui-material/src/Collapse/Collapse.js:137— Collapse has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11, ternaries 10, boolean chains 5, other 2. Most of this is not in the body itself: 6 of the 28 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 200, a function literal at line 257, a function literal at line 187, …). 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.
transformer (cognitive 28) REDACTED:7— transformer has cognitive complexity 28 (threshold 15). Drivers by points: if/else 6 (16 pts), ternaries 2 (9 pts), boolean chains 3 (nesting depth added 17). None of this is in the body itself: all 28 points belong to 9 function literals inside it that branch (lines 32, 21, 15, …). 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.
createPalette (cognitive 27) packages/mui-material/src/styles/createPalette.js:211— createPalette has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 7, ternaries 3 (5 pts) (nesting depth added 4). Most of this is not in the body itself: 11 of the 27 points are its own statements and the rest belongs to 2 function items inside it that branch (augmentColor, getContrastText). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
prepareMarkdown.prepareMarkdown (cognitive 26) packages-internal/markdown/prepareMarkdown.mjs:78— prepareMarkdown.prepareMarkdown has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 7, ternaries 3 (5 pts), error handling 1 (2 pts) (nesting depth added 4). Most of this is not in the body itself: 3 of the 26 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 91, 173, 90, …). 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.
Notifications.Notifications (cognitive 25) packages-internal/core-docs/src/AppLayout/layout/Notifications.tsx:60— Notifications.Notifications has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 9 (13 pts), if/else 6 (8 pts), boolean chains 4 (nesting depth added 6). Most of this is not in the body itself: 4 of the 25 points are its own statements and the rest belongs to 9 function items inside it that branch (handleToggle, a function literal at line 121, a function literal at line 74, …). 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.
AppNavDrawerItem.Item (cognitive 25) packages-internal/core-docs/src/AppLayout/navigation/AppNavDrawerItem.tsx:27— AppNavDrawerItem.Item has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 24, ternaries 1. Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
useMuiChatExporter.applyVariantTransform (cognitive 25) packages-internal/core-docs/src/DemoContent/useMuiChatExporter.ts:57— useMuiChatExporter.applyVariantTransform has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 2 (7 pts), error handling 2 (6 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppTableOfContents.AppTableOfContents (cognitive 24) REDACTED:86— AppTableOfContents.AppTableOfContents has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (nesting depth added 8). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 95, 143, 161, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
jss-to-tss-react.transformNestedKeys (cognitive 24) packages/mui-codemod/src/v5.0.0/jss-to-tss-react.js:3— jss-to-tss-react.transformNestedKeys has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (16 pts), ternaries 1 (4 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 14). None of this is in the body itself: all 24 points belong to one function literal inside it that branches (line 4). 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.
createStyled.processStyleVariants (cognitive 24) packages/mui-system/src/createStyled/createStyled.ts:115— createStyled.processStyleVariants has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (13 pts), ternaries 2 (6 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
createStyled.createStyled.styled (cognitive 24) packages/mui-system/src/createStyled/createStyled.ts:176— createStyled.createStyled.styled has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 5 (9 pts), boolean chains 6 (nesting depth added 5). Of this number, 12 points are the body's own statements and 12 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
generatePropTypeDescription.generatePropTypeDescription (cognitive 23) packages-internal/api-docs-builder/src/utils/generatePropTypeDescription.ts:70— generatePropTypeDescription.generatePropTypeDescription has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (19 pts), ternaries 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 10). Of this number, 21 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MiniTableOfContents.MiniTableOfContents (cognitive 23) packages-internal/core-docs/src/TableOfContents/MiniTableOfContents.tsx:152— MiniTableOfContents.MiniTableOfContents has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 9, if/else 8, ternaries 6. Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 6 function items inside it that branch (a function literal at line 233, getWidthIncrease, handleBarClick, …). 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.
DemoToolbar.DemoToolbar (cognitive 23) packages-internal/core-docs/src/DemoContent/DemoToolbar.tsx:275— DemoToolbar.DemoToolbar has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 12, boolean chains 6, if/else 4, error handling 1. Of this number, 16 points are the body's own statements and 7 belong to 4 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.
traverseBreakpoints.traverseBreakpoints (cognitive 23) packages/mui-system/src/Grid/traverseBreakpoints.ts:10— traverseBreakpoints.traverseBreakpoints has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 10). Most of this is not in the body itself: 7 of the 23 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 19, 38, 43). 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.
generatePropDescription.generatePropDescription (cognitive 22) packages-internal/api-docs-builder/src/utils/generatePropDescription.ts:83— generatePropDescription.generatePropDescription has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 8 (nesting depth added 5). Of this number, 18 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Ad.Ad (cognitive 22) packages-internal/core-docs/src/Ad/Ad.tsx:113— Ad.Ad has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 7, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 147, 191, 212, …). 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.
createGetSelector.default.<returned closure> (cognitive 22) packages/mui-material/src/styles/createGetSelector.ts:14— createGetSelector.default.<returned closure> has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
mergeSlotProps.mergeSlotProps (cognitive 22) packages/mui-material/src/utils/mergeSlotProps.ts:5— mergeSlotProps.mergeSlotProps has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 6, ternaries 2 (4 pts) (nesting depth added 5). 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 35, 20). 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.
Tabs.Tabs (cognitive 22) packages/mui-material/src/Tabs/Tabs.js:257— Tabs.Tabs has cognitive complexity 22 (threshold 15). Drivers by points: if/else 37 (57 pts), boolean chains 23, ternaries 18 (23 pts), loops 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Slider (cognitive 22) packages/mui-material/src/Slider/Slider.js:563— Slider has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 11, ternaries 7 (9 pts), if/else 2 (nesting depth added 2). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 722, 773, 721, …). 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.
TextField (cognitive 22) packages/mui-material/src/TextField/TextField.js:75— TextField has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 8, ternaries 5 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
XGridGlobalStyles.XGridGlobalStyles (cognitive 21) docs/src/components/home/XGridGlobalStyles.tsx:4— XGridGlobalStyles.XGridGlobalStyles has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 21. None of this is in the body itself: all 21 points belong to one function literal inside it that branches (line 13). 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.
MarkdownDocsV2.MarkdownDocsV2 (cognitive 21) docs/src/modules/components/MarkdownDocsV2.js:39— MarkdownDocsV2.MarkdownDocsV2 has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 7, if/else 6 (7 pts), ternaries 5 (6 pts), loops 1 (nesting depth added 2). Of this number, 16 points are the body's own statements and 5 belong to 3 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
defaultPropsHandler.getExplicitPropsDeclaration (cognitive 21) packages-internal/api-docs-builder/src/utils/defaultPropsHandler.ts:201— defaultPropsHandler.getExplicitPropsDeclaration has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 4, ternaries 2 (3 pts), 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.
useButtonBase.useButtonBase (cognitive 21) packages/mui-material/src/ButtonBase/useButtonBase.ts:105— useButtonBase.useButtonBase has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 4 (nesting depth added 9). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to one function literal inside it that branches (line 134). 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.
useRovingTabIndex.useRovingTabIndexRoot (cognitive 21) packages/mui-utils/src/useRovingTabIndex/useRovingTabIndex.ts:198— useRovingTabIndex.useRovingTabIndexRoot has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 3, ternaries 3, match/switch 1 (nesting depth added 3). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 336, 264, 275, …). 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.
Slide (cognitive 21) packages/mui-material/src/Slide/Slide.js:113— Slide has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12, boolean chains 6, ternaries 2 (3 pts) (nesting depth added 1). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 11 function literals inside it that branch (lines 286, 150, 242, …). 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.
(anonymous) (cognitive 21) packages/mui-material/src/ToggleButton/ToggleButton.js:46— (anonymous) has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 21. Of this number, 14 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
FormControl (cognitive 21) packages/mui-material/src/FormControl/FormControl.js:93— FormControl has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 4, ternaries 2 (3 pts) (nesting depth added 6). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 134, a function literal at line 155, a function literal at line 128, …). 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.
CoreShowcase.CoreShowcase (cognitive 20) docs/src/components/home/CoreShowcase.tsx:25— CoreShowcase.CoreShowcase has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 10 (18 pts), boolean chains 1, if/else 1 (nesting depth added 8). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 31). 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.
autocomplete-props.transformer (cognitive 20) REDACTED:316— autocomplete-props.transformer has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 4 (nesting depth added 5). None of this is in the body itself: all 20 points belong to 6 function literals inside it that branch (lines 368, 395, 452, …). 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.
joy-avatar-remove-imgProps.transformer (cognitive 20) packages/mui-codemod/src/v5.0.0/joy-avatar-remove-imgProps.js:5— joy-avatar-remove-imgProps.transformer has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 4 (nesting depth added 7). None of this is in the body itself: all 20 points belong to 5 function literals inside it that branch (lines 39, 21, 27, …). 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.
optimal-imports.transformer (cognitive 20) REDACTED:5— optimal-imports.transformer has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 6, error handling 1, match/switch 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 3 function items inside it that branch (a function literal at line 56, a function literal at line 26, addSpecifier). 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.
TextareaAutosize.TextareaAutosize (cognitive 20) packages/mui-material/src/TextareaAutosize/TextareaAutosize.tsx:60— TextareaAutosize.TextareaAutosize has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14, boolean chains 6. None of this is in the body itself: all 20 points belong to 7 function items inside it that branch (a function literal at line 72, handleChange, a function literal at line 131, …). 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.
useAutocomplete.useAutocomplete.syncHighlightedIndexToDOM (cognitive 20) packages/mui-material/src/useAutocomplete/useAutocomplete.js:414— useAutocomplete.useAutocomplete.syncHighlightedIndexToDOM has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
TableCell (cognitive 20) packages/mui-material/src/TableCell/TableCell.js:174— TableCell has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 9, ternaries 4 (6 pts), if/else 5 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
transformer (cognitive 20) packages/mui-codemod/src/deprecations/typography-props/typography-props.js:9— transformer has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 6, ternaries 1 (nesting depth added 2). None of this is in the body itself: all 20 points belong to 12 function items inside it that branch (a function literal at line 17, a function literal at line 80, a function literal at line 27, …). 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.
ComponentApiBuilder.attachPropsTable (cognitive 19) REDACTED:514— ComponentApiBuilder.attachPropsTable has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, if/else 6, match/switch 1 (2 pts), ternaries 2, error handling 1 (nesting depth added 1). None of this is in the body itself: all 19 points belong to one function literal inside it that branches (line 522). 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.
AppNavDrawerItem.AppNavDrawerItem (cognitive 19) packages-internal/core-docs/src/AppLayout/navigation/AppNavDrawerItem.tsx:315— AppNavDrawerItem.AppNavDrawerItem has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 9, ternaries 7, if/else 3. Of this number, 16 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PropertiesList.PropertiesList (cognitive 19) REDACTED:115— PropertiesList.PropertiesList has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 17, if/else 1, ternaries 1. None of this is in the body itself: all 19 points belong to 2 function literals inside it that branch (lines 120, 223). 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.
loader.demoLoader::detectRelativeImports (cognitive 19) packages-internal/markdown/loader.mjs:221— loader.demoLoader::detectRelativeImports has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
movePropIntoSlotProps.moveDefaultPropsPropIntoslotProps (cognitive 19) packages/mui-codemod/src/deprecations/utils/movePropIntoSlotProps.js:74— movePropIntoSlotProps.moveDefaultPropsPropIntoslotProps has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 2 (5 pts) (nesting depth added 9). None of this is in the body itself: all 19 points belong to 2 function literals inside it that branch (lines 86, 81). 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.
avatar-group-props.transformer (cognitive 19) packages/mui-codemod/src/deprecations/avatar-group-props/avatar-group-props.js:9— avatar-group-props.transformer has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 1 (nesting depth added 9). None of this is in the body itself: all 19 points belong to 3 function literals inside it that branch (lines 62, 24, 26). 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.
optimal-imports.transformer (cognitive 19) REDACTED:5— optimal-imports.transformer has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 6, match/switch 1 (nesting depth added 2). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 49, a function literal at line 26, addSpecifier). 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.
path-imports.transformer (cognitive 19) packages/mui-codemod/src/v5.0.0/path-imports.js:6— path-imports.transformer has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 3 (nesting depth added 5). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 47, 22). 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.
breakpoints.iterateBreakpoints (cognitive 19) packages/mui-system/src/breakpoints/breakpoints.ts:64— breakpoints.iterateBreakpoints has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (4 pts), ternaries 1 (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.
TablePagination (cognitive 19) packages/mui-material/src/TablePagination/TablePagination.js:169— TablePagination has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, ternaries 8, if/else 2, other 1. Of this number, 14 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CircularProgress (cognitive 19) packages/mui-material/src/CircularProgress/CircularProgress.js:223— CircularProgress has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 4, other 3, 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.
transformer (cognitive 19) REDACTED:7— transformer has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 2 (5 pts), boolean chains 3 (nesting depth added 9). None of this is in the body itself: all 19 points belong to 8 function literals inside it that branch (lines 32, 21, 15, …). 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.
createDescribeableProp.createDescribeableProp (cognitive 18) packages-internal/api-docs-builder/src/utils/createDescribeableProp.ts:34— createDescribeableProp.createDescribeableProp has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 4, ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
defaultPropsHandler.getRenderBody (cognitive 18) packages-internal/api-docs-builder/src/utils/defaultPropsHandler.ts:165— defaultPropsHandler.getRenderBody has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 5 (nesting depth added 7). 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.
ComponentApiBuilder.generateApiPage (cognitive 18) REDACTED:314— ComponentApiBuilder.generateApiPage has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 7, ternaries 4 (6 pts), if/else 5 (nesting depth added 2). Of this number, 13 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body: 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.
ApiPage.ApiPage (cognitive 18) REDACTED:85— ApiPage.ApiPage has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, ternaries 7, if/else 3. Of this number, 14 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Masonry.getStyle (cognitive 18) packages/mui-lab/src/Masonry/Masonry.tsx:96— Masonry.getStyle has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, if/else 4, ternaries 2 (3 pts), loops 1 (2 pts) (nesting depth added 2). Of this number, 10 points are the body's own statements and 8 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
createThemeNoVars.createThemeNoVars (cognitive 18) packages/mui-material/src/styles/createThemeNoVars.js:120— createThemeNoVars.createThemeNoVars has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 7). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 2 function items inside it that branch (traverse, 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.
TouchRipple.TouchRipple (cognitive 18) packages/mui-material/src/ButtonBase/TouchRipple.js:261— TouchRipple.TouchRipple has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 3, ternaries 2 (nesting depth added 3). None of this is in the body itself: all 18 points belong to 7 function literals inside it that branch (lines 346, 389, 285, …). 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.
useAutocomplete.createFilterOptions.<returned closure> (cognitive 18) packages/mui-material/src/useAutocomplete/useAutocomplete.js:37— useAutocomplete.createFilterOptions.<returned closure> has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 5 (7 pts), boolean chains 2 (nesting depth added 5). Of this number, 9 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.
useAutocomplete.useAutocomplete.changeHighlightedIndex::getNextIndex (cognitive 18) packages/mui-material/src/useAutocomplete/useAutocomplete.js:537— useAutocomplete.useAutocomplete.changeHighlightedIndex::getNextIndex has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 5 (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.
BasePopper.PopperTooltip (cognitive 18) packages/mui-material/src/Popper/BasePopper.tsx:75— BasePopper.PopperTooltip has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 4, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 123, 198, 117). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
useCurrentColorScheme.useCurrentColorScheme (cognitive 18) packages/mui-system/src/cssVars/useCurrentColorScheme.ts:114— useCurrentColorScheme.useCurrentColorScheme has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 12, ternaries 4, if/else 2. Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 289, 144, 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.
createFilterOptions (cognitive 18) packages/mui-material/src/useAutocomplete/useAutocomplete.js:27— createFilterOptions has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 5 (7 pts), boolean chains 2 (nesting depth added 5). None of this is in the body itself: all 18 points belong to 2 function literals inside it that branch (lines 37, 49). 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.
useAutocomplete::(anonymous)::getNextIndex (cognitive 18) packages/mui-material/src/useAutocomplete/useAutocomplete.js:537— useAutocomplete::(anonymous)::getNextIndex has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 5 (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.
computeRippleState (cognitive 18) packages/mui-material/src/ButtonBase/TouchRipple.js:72— computeRippleState has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 4 (7 pts), if/else 5 (6 pts), boolean chains 5 (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.
DemoContent.helpers.getDemoEditingDependencies (cognitive 17) packages-internal/core-docs/src/DemoContent/DemoContent.helpers.ts:70— DemoContent.helpers.getDemoEditingDependencies has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 3, loops 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
badge-overlap-value.transformer (cognitive 17) packages/mui-codemod/src/v5.0.0/badge-overlap-value.js:5— badge-overlap-value.transformer has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 4 (nesting depth added 6). None of this is in the body itself: all 17 points belong to 2 function literals inside it that branch (lines 14, 31). 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.
createTransitions.createTransitions::createTransitionValue (cognitive 17) packages/mui-material/src/styles/createTransitions.js:63— createTransitions.createTransitions::createTransitionValue has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, 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.
SwitchBase.SwitchBase (cognitive 17) packages/mui-material/src/internal/SwitchBase.js:83— SwitchBase.SwitchBase has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 5, ternaries 3 (nesting depth added 1). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to 3 function items inside it that branch (handleFocus, handleBlur, handleInputChange). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
useAutocomplete.handleFocusItem (cognitive 17) packages/mui-material/src/useAutocomplete/useAutocomplete.js:944— useAutocomplete.handleFocusItem has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToggleButtonGroup (cognitive 17) packages/mui-material/src/ToggleButtonGroup/ToggleButtonGroup.js:136— ToggleButtonGroup has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 3 (4 pts), boolean chains 3 (nesting depth added 2). None of this is in the body itself: all 17 points belong to 5 function items inside it that branch (a function literal at line 156, getButtonPositionClassName, a function literal at line 251, …). 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.
Grow (cognitive 17) packages/mui-material/src/Grow/Grow.js:34— Grow has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8, ternaries 6, boolean chains 3. Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 114, 61, 166, …). 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.
brandingTheme.getDesignTokens (cognitive 16) packages-internal/core-docs/src/branding/brandingTheme.ts:205— brandingTheme.getDesignTokens has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 11, ternaries 5. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PropertiesTable.PropertiesTable (cognitive 16) REDACTED:138— PropertiesTable.PropertiesTable has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 14, ternaries 2. Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 156, 262). 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.
DemoContentLoading.DemoContentLoading (cognitive 16) packages-internal/core-docs/src/DemoContent/DemoContentLoading.tsx:35— DemoContentLoading.DemoContentLoading has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 8 (10 pts), boolean chains 4, if/else 2 (nesting depth added 2). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: 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.
propsToObject.propsToObject (cognitive 16) packages/mui-codemod/src/util/propsToObject.js:1— propsToObject.propsToObject has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 5, ternaries 2 (nesting depth added 4). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 3 function items inside it that branch (a function literal at line 18, buildObject, a function literal at line 22). 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.
tree-view-moved-to-x.transformer (cognitive 16) packages/mui-codemod/src/v5.0.0/tree-view-moved-to-x.js:44— tree-view-moved-to-x.transformer has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 1 (nesting depth added 6). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 54, 87, 75). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
material-design-icons.myDestRewriter (cognitive 16) packages/mui-icons-material/renameFilters/material-design-icons.mjs:26— material-design-icons.myDestRewriter has cognitive complexity 16 (threshold 15). Drivers by points: if/else 15, boolean chains 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
useSlider.useSlider.createHandlePointerDown.<returned closure> (cognitive 16) packages/mui-material/src/Slider/useSlider.ts:736— useSlider.useSlider.createHandlePointerDown.<returned closure> has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, error handling 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.
styleFunctionSx.unstable_createStyleFunctionSx.styleFunctionSx::process (cognitive 16) packages/mui-system/src/styleFunctionSx/styleFunctionSx.ts:112— styleFunctionSx.unstable_createStyleFunctionSx.styleFunctionSx::process has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 2, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
createStyled.createStyled.styled.muiStyledResolver (cognitive 16) packages/mui-system/src/createStyled/createStyled.ts:259— createStyled.createStyled.styled.muiStyledResolver has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 4). Of this number, 8 points are the body's own statements and 8 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
prepareCssVars.prepareCssVars.defaultGetSelector (cognitive 16) packages/mui-system/src/cssVars/prepareCssVars.ts:56— prepareCssVars.prepareCssVars.defaultGetSelector has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Change-coupling hub: ClickAwayListener.tsx → useModal.ts, BasePopper.tsx, useSlider.ts, FocusTrap.tsx packages/mui-material/src/ClickAwayListener/ClickAwayListener.tsx— `packages/mui-material/src/ClickAwayListener/ClickAwayListener.tsx` changes together with 4 other files — `packages/mui-material/src/Modal/useModal.ts`, `packages/mui-material/src/Popper/BasePopper.tsx`, `packages/mui-material/src/Slider/useSlider.ts`, `packages/mui-material/src/Unstable_TrapFocus/FocusTrap.tsx` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
IC1 · Incompleteness & stubs· Both branches are identical · ×1
Both branches are identical — the condition decides nothing docs/src/components/customers/CustomersSpotlight.tsx:35— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
P3 · Security & performance tooling· SAST runs, but gates no merge · ×1
SAST runs, but gates no merge — `codeql.yml`, `scorecards.yml` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.
Duplication concentrated across 122 sibling directories (210 clone groups) packages/mui-material/src/ListItemButton/ListItemButton.js:40— 210 duplicated blocks under packages/mui-material/src/ have copies in at least two of the sibling directories Accordion, AccordionActions, AccordionDetails, AccordionSummary, Alert, AlertTitle (+116 more sibling(s) not listed) — 104 of them are reported below, and 106 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 210 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 210 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 210 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 8 sibling directories (38 clone groups) packages/mui-styled-engine-sc/src/index.ts:420— 38 duplicated blocks under packages/ have copies in at least two of the sibling directories mui-lab, mui-material, mui-material-nextjs, mui-styled-engine, mui-styled-engine-sc, mui-system (+2 more sibling(s) not listed) — 30 of them are reported below, and 8 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 38 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 38 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 38 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 59 sibling directories (21 clone groups) REDACTED:7— 21 duplicated blocks under packages/mui-codemod/src/deprecations/ have copies in at least two of the sibling directories accordion-props, accordion-summary-classes, alert-classes, alert-props, autocomplete-props, avatar-group-props (+53 more sibling(s) not listed) — 16 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 21 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 21 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 21 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 8 sibling directories (15 clone groups) packages/mui-codemod/src/v6.0.0/system-props/removeSystemProps.js:2— 15 duplicated blocks under packages/mui-codemod/src/ have copies in at least two of the sibling directories deprecations, util, v1.0.0, v4.0.0, v5.0.0, v6.0.0 (+2 more sibling(s) not listed) — 12 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 15 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 36 sibling directories (10 clone groups) packages/mui-lab/src/TimelineContent/TimelineContent.tsx:38— 10 duplicated blocks under packages/mui-lab/src/ have copies in at least two of the sibling directories AdapterDateFns, AdapterDayjs, AdapterLuxon, AdapterMoment, CalendarPicker, CalendarPickerSkeleton (+30 more sibling(s) not listed) — 9 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Wholesale file copy (214 identical lines × 2 files) packages/mui-codemod/src/v6.0.0/system-props/removeSystemProps.js:2— packages/mui-codemod/src/v6.0.0/system-props/removeSystemProps.js:2 · packages/mui-codemod/src/v9.0.0/system-props/removeSystemProps.js:2 — these 2 files are line-for-line copies of one another — 214 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (183 identical lines × 2 files) packages-internal/api-docs-builder/src/utils/getPropsFromComponentNode.ts:1— packages-internal/api-docs-builder/src/utils/getPropsFromComponentNode.ts:1 · packages-internal/docs-utils/src/getPropsFromComponentNode.ts:1 — these 2 files are line-for-line copies of one another — 183 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (167 matched lines × 2 locations) · ×1
Duplicated block with local edits (167 matched lines × 2 locations) packages/mui-material/src/ListItemButton/ListItemButton.js:40— packages/mui-material/src/ListItemButton/ListItemButton.js:40 · packages/mui-material/src/MenuItem/MenuItem.js:44 — the two spans are one implementation copied and then locally edited — 908 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (165 matched lines × 2 locations) · ×1
Duplicated block with local edits (165 matched lines × 2 locations) packages/mui-material/src/ButtonGroup/ButtonGroup.js:17— packages/mui-material/src/ButtonGroup/ButtonGroup.js:17 · packages/mui-material/src/ToggleButtonGroup/ToggleButtonGroup.js:38 — the two spans are one implementation copied and then locally edited — 848 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Wholesale file copy (139 identical lines × 2 files) packages/mui-codemod/src/v6.0.0/grid-v2-props/grid-v2-props.js:2— packages/mui-codemod/src/v6.0.0/grid-v2-props/grid-v2-props.js:2 · packages/mui-codemod/src/v7.0.0/grid-props/grid-props.js:2 — these 2 files are line-for-line copies of one another — 139 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (134 matched lines × 2 locations) · ×1
Duplicated block with local edits (134 matched lines × 2 locations) packages/mui-codemod/src/util/migrateToVariants.js:426— packages/mui-codemod/src/util/migrateToVariants.js:426 · packages/mui-codemod/src/v6.0.0/sx-prop/sx-v6.js:262 — the two spans are one implementation copied and then locally edited — 912 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (130 matched lines × 2 locations) · ×1
Duplicated block with local edits (130 matched lines × 2 locations) packages/mui-material/src/Checkbox/Checkbox.js:55— packages/mui-material/src/Checkbox/Checkbox.js:55 · packages/mui-material/src/Radio/Radio.js:45 — the two spans are one implementation copied and then locally edited — 731 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Wholesale file copy (115 identical lines × 2 files) packages/mui-material/src/Fade/Fade.js:2— packages/mui-material/src/Fade/Fade.js:2 · packages/mui-material/src/Zoom/Zoom.js:2 — these 2 files are line-for-line copies of one another — 115 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (109 lines × 3 locations) REDACTED:7— REDACTED:7 · REDACTED:7 · REDACTED:7 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication· Duplicated block with local edits (108 matched lines × 2 locations) · ×1
Duplicated block with local edits (108 matched lines × 2 locations) REDACTED:96— REDACTED:96 · REDACTED:120 — the two spans are one implementation copied and then locally edited — 481 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 (100 lines × 2 locations) packages/mui-material/src/styles/createThemeWithVars.js:299— packages/mui-material/src/styles/createThemeWithVars.js:299 · packages/mui-material/src/styles/createThemeWithVars.js:625 — 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 (91 matched lines × 2 locations) · ×1
Duplicated block with local edits (91 matched lines × 2 locations) packages/mui-material/src/ListItem/ListItem.js:16— packages/mui-material/src/ListItem/ListItem.js:16 · packages/mui-material/src/ListItemButton/ListItemButton.js:18 — the two spans are one implementation copied and then locally edited — 438 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (87 matched lines × 2 locations) · ×1
Duplicated block with local edits (87 matched lines × 2 locations) packages/mui-material/src/Icon/Icon.js:13— packages/mui-material/src/Icon/Icon.js:13 · packages/mui-material/src/SvgIcon/SvgIcon.js:13 — the two spans are one implementation copied and then locally edited — 416 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (79 matched lines × 2 locations) · ×1
Duplicated block with local edits (79 matched lines × 2 locations) REDACTED:5— REDACTED:5 · REDACTED:5 — the two spans are one implementation copied and then locally edited — 504 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (76 matched lines × 2 locations) · ×1
Duplicated block with local edits (76 matched lines × 2 locations) REDACTED:31— REDACTED:31 · packages-internal/core-docs/src/ApiPage/HooksApiContent.tsx:23 — the two spans are one implementation copied and then locally edited — 451 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 (76 lines × 2 locations) packages/mui-material/src/locale/hrHR.ts:4— packages/mui-material/src/locale/hrHR.ts:4 · packages/mui-material/src/locale/srRS.ts:4 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited.
Duplicated block (75 lines × 10 locations) REDACTED:7— REDACTED:7 · REDACTED:7 · REDACTED:7 · REDACTED:7 · +6 more site(s) not listed — the 10 copies are spread across 10 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 (74 lines × 2 locations) packages/mui-material/src/Popper/BasePopper.tsx:429— packages/mui-material/src/Popper/BasePopper.tsx:429 · packages/mui-material/src/Popper/Popper.tsx:136 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Duplicated block (72 lines × 2 locations) REDACTED:7— REDACTED:7 · REDACTED:7 — 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 (69 lines × 3 locations) packages/mui-material/src/locale/arEG.ts:4— packages/mui-material/src/locale/arEG.ts:4 · packages/mui-material/src/locale/arSA.ts:4 · packages/mui-material/src/locale/arSD.ts:4 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited.
Wholesale file copy (66 identical lines × 2 files) packages-internal/api-docs-builder/src/utils/createTypeScriptProject.ts:1— packages-internal/api-docs-builder/src/utils/createTypeScriptProject.ts:1 · packages-internal/docs-utils/src/createTypeScriptProject.ts:1 — these 2 files are line-for-line copies of one another — 66 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (63 lines × 2 locations) REDACTED:13— REDACTED:13 · REDACTED:9 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (58 lines × 2 locations) packages/mui-styled-engine-sc/src/index.ts:420— packages/mui-styled-engine-sc/src/index.ts:420 · packages/mui-styled-engine/src/index.ts:240 — 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 (56 lines × 2 locations) packages/mui-lab/src/TimelineContent/TimelineContent.tsx:38— packages/mui-lab/src/TimelineContent/TimelineContent.tsx:38 · packages/mui-lab/src/TimelineOppositeContent/TimelineOppositeContent.tsx:41 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (55 matched lines × 2 locations) · ×1
Duplicated block with local edits (55 matched lines × 2 locations) packages/mui-codemod/src/deprecations/utils/movePropIntoSlotProps.js:6— packages/mui-codemod/src/deprecations/utils/movePropIntoSlotProps.js:6 · packages/mui-codemod/src/deprecations/utils/movePropIntoSlots.js:6 — the two spans are one implementation copied and then locally edited — 421 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 (54 lines × 2 locations) packages/mui-material/src/FilledInput/FilledInput.js:290— packages/mui-material/src/FilledInput/FilledInput.js:290 · packages/mui-material/src/Input/Input.js:187 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (53 matched lines × 2 locations) · ×1
Duplicated block with local edits (53 matched lines × 2 locations) packages/mui-codemod/src/deprecations/all/deprecations-all.js:62— packages/mui-codemod/src/deprecations/all/deprecations-all.js:62 · packages/mui-codemod/src/v5.0.0/preset-safe.js:56 — the two spans are one implementation copied and then locally edited — 664 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (52 matched lines × 2 locations) · ×1
Duplicated block with local edits (52 matched lines × 2 locations) packages-internal/core-docs/src/codeStyling/codeStyling.tsx:5— packages-internal/core-docs/src/codeStyling/codeStyling.tsx:5 · packages-internal/core-docs/src/codeVariant/codeVariant.tsx:5 — the two spans are one implementation copied and then locally edited — 327 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (52 lines × 2 locations) packages/mui-material/src/Grid/Grid.tsx:151— packages/mui-material/src/Grid/Grid.tsx:151 · packages/mui-system/src/Grid/Grid.tsx:14 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
R10 · Code Duplication· Duplicated block with local edits (51 matched lines × 2 locations) · ×1
Duplicated block with local edits (51 matched lines × 2 locations) packages/mui-material/src/PigmentGrid/PigmentGrid.tsx:144— packages/mui-material/src/PigmentGrid/PigmentGrid.tsx:144 · packages/mui-system/src/Grid/createGrid.tsx:190 — the two spans are one implementation copied and then locally edited — 321 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 (47 lines × 3 locations) packages/mui-material/src/locale/plPL.ts:4— packages/mui-material/src/locale/plPL.ts:4 · packages/mui-material/src/locale/ruRU.ts:4 · packages/mui-material/src/locale/ukUA.ts:4 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (46 matched lines × 2 locations) · ×1
Duplicated block with local edits (46 matched lines × 2 locations) packages/mui-material/src/FilledInput/FilledInput.js:37— packages/mui-material/src/FilledInput/FilledInput.js:37 · packages/mui-material/src/Input/Input.js:28 — the two spans are one implementation copied and then locally edited — 267 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 (41 lines × 2 locations) REDACTED:79— REDACTED:79 · packages-internal/api-docs-builder/src/ApiBuilders/HookApiBuilder.ts:30 — 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.
Boundary violation [package:test-suite-dependency] scripts/a11yScorecard/rollup.mjs:1— scripts/a11yScorecard/rollup.mjs:1 imports test/regressions/a11y/criteriaSuites.mjs, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Complex function (anonymous) (cyclomatic 80, cognitive 103) packages/mui-material/src/useAutocomplete/useAutocomplete.js:995— (anonymous) has cyclomatic complexity 80 and cognitive complexity 103; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 71, cognitive 134) packages/mui-material/src/styles/createThemeWithVars.js:236— (anonymous) has cyclomatic complexity 71 and cognitive complexity 134; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 recurseObjectExpression (cyclomatic 62, cognitive 137) packages/mui-codemod/src/v6.0.0/sx-prop/sx-v6.js:180— recurseObjectExpression has cyclomatic complexity 62 and cognitive complexity 137; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function checkType (cyclomatic 53, cognitive 61) packages-internal/scripts/typescript-to-proptypes/src/getPropTypesFromFile.ts:248— checkType has cyclomatic complexity 53 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function root (cyclomatic 52, cognitive 47) packages-internal/core-docs/src/branding/brandingTheme.ts:1103— root has cyclomatic complexity 52 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 root (cyclomatic 52, cognitive 43) packages-internal/core-docs/src/branding/brandingTheme.ts:550— root has cyclomatic complexity 52 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 DemoContent (cyclomatic 47, cognitive 44) packages-internal/core-docs/src/DemoContent/DemoContent.tsx:87— DemoContent has cyclomatic complexity 47 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function recurseObjectExpression (cyclomatic 44, cognitive 93) packages/mui-codemod/src/util/migrateToVariants.js:413— recurseObjectExpression has cyclomatic complexity 44 and cognitive complexity 93; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 Demo (cyclomatic 41, cognitive 40) packages-internal/core-docs/src/Demo/Demo.tsx:408— Demo has cyclomatic complexity 41 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 Autocomplete (cyclomatic 41, cognitive 40) packages/mui-material/src/Autocomplete/Autocomplete.js:432— Autocomplete has cyclomatic complexity 41 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 36, cognitive 57) packages/mui-material/src/SwipeableDrawer/SwipeableDrawer.js:347— (anonymous) has cyclomatic complexity 36 and cognitive complexity 57; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function LinearProgress (cyclomatic 34, cognitive 55) packages/mui-material/src/LinearProgress/LinearProgress.js:421— LinearProgress has cyclomatic complexity 34 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 33, cognitive 32) REDACTED:428— (anonymous) has cyclomatic complexity 33 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 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 generatePropType (cyclomatic 31, cognitive 45) packages-internal/scripts/typescript-to-proptypes/src/generatePropTypes.ts:131— generatePropType has cyclomatic complexity 31 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function SelectInput (cyclomatic 31, cognitive 38) packages/mui-material/src/Select/SelectInput.js:146— SelectInput has cyclomatic complexity 31 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 31, cognitive 27) packages/mui-material/src/Chip/Chip.js:66— (anonymous) has cyclomatic complexity 31 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 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 validateSource (cyclomatic 29, cognitive 36) scripts/a11yScorecard/validate.mjs:119— validateSource has cyclomatic complexity 29 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function buildLlmsDocs (cyclomatic 28, cognitive 51) scripts/buildLlmsDocs/index.ts:461— buildLlmsDocs has cyclomatic complexity 28 and cognitive complexity 51; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 TablePaginationActions (cyclomatic 28, cognitive 27) packages/mui-material/src/TablePaginationActions/TablePaginationActions.js:59— TablePaginationActions has cyclomatic complexity 28 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 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 Chip (cyclomatic 27, cognitive 28) packages/mui-material/src/Chip/Chip.js:379— Chip has cyclomatic complexity 27 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 createTheme (cyclomatic 26, cognitive 39) packages/mui-material/src/styles/createTheme.ts:65— createTheme has cyclomatic complexity 26 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function CssVarsProvider (cyclomatic 26, cognitive 26) packages/mui-system/src/cssVars/createCssVarsProvider.tsx:216— CssVarsProvider has cyclomatic complexity 26 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function Tooltip (cyclomatic 25, cognitive 31) packages/mui-material/src/Tooltip/Tooltip.js:237— Tooltip has cyclomatic complexity 25 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 25, cognitive 24) packages-internal/core-docs/src/AppLayout/navigation/AppNavDrawerItem.tsx:27— (anonymous) has cyclomatic complexity 25 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function DemoContentLoading (cyclomatic 24, cognitive 18) packages-internal/core-docs/src/DemoContent/DemoContentLoading.tsx:35— DemoContentLoading has cyclomatic complexity 24 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 resolveProps (cyclomatic 23, cognitive 43) packages/mui-utils/src/resolveProps/resolveProps.ts:12— resolveProps has cyclomatic complexity 23 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function selectNewValue (cyclomatic 23, cognitive 31) packages/mui-material/src/useAutocomplete/useAutocomplete.js:854— selectNewValue has cyclomatic complexity 23 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 23, cognitive 30) packages/mui-codemod/src/v5.0.0/base-remove-component-prop.js:25— (anonymous) has cyclomatic complexity 23 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 processApiJson (cyclomatic 23, cognitive 29) packages-internal/scripts/generate-llms-txt/src/processApi.ts:239— processApiJson has cyclomatic complexity 23 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 23, cognitive 22) packages/mui-material/src/Button/Button.js:95— (anonymous) has cyclomatic complexity 23 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 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 23, cognitive 20) packages/mui-material/src/PaginationItem/PaginationItem.js:110— (anonymous) has cyclomatic complexity 23 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 22, cognitive 40) packages/mui-material/src/Slider/useSlider.ts:394— (anonymous) has cyclomatic complexity 22 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function checkSymbol (cyclomatic 22, cognitive 34) packages-internal/scripts/typescript-to-proptypes/src/getPropTypesFromFile.ts:542— checkSymbol has cyclomatic complexity 22 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 TextField (cyclomatic 22, cognitive 22) packages/mui-material/src/TextField/TextField.js:75— TextField has cyclomatic complexity 22 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 useAutocomplete (cyclomatic 22, cognitive 20) packages/mui-material/src/useAutocomplete/useAutocomplete.js:97— useAutocomplete has cyclomatic complexity 22 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 22, cognitive 18) REDACTED:522— (anonymous) has cyclomatic complexity 22 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 handleClosedTypeahead (cyclomatic 22, cognitive 15) packages/mui-material/src/Select/SelectInput.js:550— handleClosedTypeahead has cyclomatic complexity 22 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 Tabs (cyclomatic 21, cognitive 21) packages/mui-material/src/Tabs/Tabs.js:257— Tabs has cyclomatic complexity 21 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.
R3 · Large Files· packages-internal/core-docs/src/branding/brandingTheme.ts · ×1
packages-internal/core-docs/src/branding/brandingTheme.ts: 1590 lines of code packages-internal/core-docs/src/branding/brandingTheme.ts:1— packages-internal/core-docs/src/branding/brandingTheme.ts has 1590 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-material/src/useAutocomplete/useAutocomplete.js · ×1
packages/mui-material/src/useAutocomplete/useAutocomplete.js: 1422 lines of code packages/mui-material/src/useAutocomplete/useAutocomplete.js:1— packages/mui-material/src/useAutocomplete/useAutocomplete.js has 1422 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-material/src/Autocomplete/Autocomplete.js · ×1
packages/mui-material/src/Autocomplete/Autocomplete.js: 1289 lines of code packages/mui-material/src/Autocomplete/Autocomplete.js:1— packages/mui-material/src/Autocomplete/Autocomplete.js has 1289 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-material/src/Slider/Slider.js · ×1
packages/mui-material/src/Slider/Slider.js: 1043 lines of code packages/mui-material/src/Slider/Slider.js:1— packages/mui-material/src/Slider/Slider.js has 1043 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-material/src/styles/createThemeWithVars.js · ×1
packages/mui-material/src/styles/createThemeWithVars.js: 1006 lines of code packages/mui-material/src/styles/createThemeWithVars.js:1— packages/mui-material/src/styles/createThemeWithVars.js has 1006 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-material/src/Tabs/Tabs.js · ×1
packages/mui-material/src/Tabs/Tabs.js: 986 lines of code packages/mui-material/src/Tabs/Tabs.js:1— packages/mui-material/src/Tabs/Tabs.js has 986 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-material/src/Select/SelectInput.js · ×1
packages/mui-material/src/Select/SelectInput.js: 971 lines of code packages/mui-material/src/Select/SelectInput.js:1— packages/mui-material/src/Select/SelectInput.js has 971 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages-internal/core-docs/src/MarkdownDocs/MarkdownElement.tsx · ×1
packages-internal/core-docs/src/MarkdownDocs/MarkdownElement.tsx: 864 lines of code packages-internal/core-docs/src/MarkdownDocs/MarkdownElement.tsx:1— packages-internal/core-docs/src/MarkdownDocs/MarkdownElement.tsx has 864 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: 859 lines of code REDACTED:1— REDACTED has 859 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: 813 lines of code REDACTED:1— REDACTED has 813 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-material/src/Slider/useSlider.ts · ×1
packages/mui-material/src/Slider/useSlider.ts: 809 lines of code packages/mui-material/src/Slider/useSlider.ts:1— packages/mui-material/src/Slider/useSlider.ts has 809 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-material/src/Tooltip/Tooltip.js · ×1
packages/mui-material/src/Tooltip/Tooltip.js: 794 lines of code packages/mui-material/src/Tooltip/Tooltip.js:1— packages/mui-material/src/Tooltip/Tooltip.js has 794 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages-internal/scripts/typescript-to-proptypes/src/getPropTypesFromFile.ts · ×1
packages-internal/scripts/typescript-to-proptypes/src/getPropTypesFromFile.ts: 783 lines of code packages-internal/scripts/typescript-to-proptypes/src/getPropTypesFromFile.ts:1— packages-internal/scripts/typescript-to-proptypes/src/getPropTypesFromFile.ts has 783 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-material/src/Rating/Rating.js · ×1
packages/mui-material/src/Rating/Rating.js: 780 lines of code packages/mui-material/src/Rating/Rating.js:1— packages/mui-material/src/Rating/Rating.js has 780 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-material/src/InputBase/InputBase.js · ×1
packages/mui-material/src/InputBase/InputBase.js: 767 lines of code packages/mui-material/src/InputBase/InputBase.js:1— packages/mui-material/src/InputBase/InputBase.js has 767 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-utils/src/useRovingTabIndex/useRovingTabIndex.ts · ×1
packages/mui-utils/src/useRovingTabIndex/useRovingTabIndex.ts: 736 lines of code packages/mui-utils/src/useRovingTabIndex/useRovingTabIndex.ts:1— packages/mui-utils/src/useRovingTabIndex/useRovingTabIndex.ts has 736 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-material/src/Button/Button.js · ×1
packages/mui-material/src/Button/Button.js: 716 lines of code packages/mui-material/src/Button/Button.js:1— packages/mui-material/src/Button/Button.js has 716 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-material/src/SwipeableDrawer/SwipeableDrawer.js · ×1
packages/mui-material/src/SwipeableDrawer/SwipeableDrawer.js: 695 lines of code packages/mui-material/src/SwipeableDrawer/SwipeableDrawer.js:1— packages/mui-material/src/SwipeableDrawer/SwipeableDrawer.js has 695 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages-internal/core-docs/src/DemoContent/DemoContainer.tsx · ×1
packages-internal/core-docs/src/DemoContent/DemoContainer.tsx: 666 lines of code packages-internal/core-docs/src/DemoContent/DemoContainer.tsx:1— packages-internal/core-docs/src/DemoContent/DemoContainer.tsx has 666 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-material/src/Chip/Chip.js · ×1
packages/mui-material/src/Chip/Chip.js: 660 lines of code packages/mui-material/src/Chip/Chip.js:1— packages/mui-material/src/Chip/Chip.js has 660 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages-internal/markdown/loader.mjs · ×1
packages-internal/markdown/loader.mjs: 658 lines of code packages-internal/markdown/loader.mjs:1— packages-internal/markdown/loader.mjs has 658 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-codemod/src/util/migrateToVariants.js · ×1
packages/mui-codemod/src/util/migrateToVariants.js: 651 lines of code packages/mui-codemod/src/util/migrateToVariants.js:1— packages/mui-codemod/src/util/migrateToVariants.js has 651 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages-internal/core-docs/src/DemoContent/DemoToolbar.tsx · ×1
packages-internal/core-docs/src/DemoContent/DemoToolbar.tsx: 614 lines of code packages-internal/core-docs/src/DemoContent/DemoToolbar.tsx:1— packages-internal/core-docs/src/DemoContent/DemoToolbar.tsx has 614 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-material/src/styles/enhanceHighContrast.ts · ×1
packages/mui-material/src/styles/enhanceHighContrast.ts: 613 lines of code packages/mui-material/src/styles/enhanceHighContrast.ts:1— packages/mui-material/src/styles/enhanceHighContrast.ts has 613 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-codemod/src/v6.0.0/theme-v6/test-cases/basicTheme.expected.js · ×1
packages/mui-codemod/src/v6.0.0/theme-v6/test-cases/basicTheme.expected.js: 603 lines of code packages/mui-codemod/src/v6.0.0/theme-v6/test-cases/basicTheme.expected.js:1— packages/mui-codemod/src/v6.0.0/theme-v6/test-cases/basicTheme.expected.js has 603 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· scripts/buildLlmsDocs/index.ts · ×1
scripts/buildLlmsDocs/index.ts: 600 lines of code scripts/buildLlmsDocs/index.ts:1— scripts/buildLlmsDocs/index.ts has 600 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-material/src/Popover/Popover.js · ×1
packages/mui-material/src/Popover/Popover.js: 592 lines of code packages/mui-material/src/Popover/Popover.js:1— packages/mui-material/src/Popover/Popover.js has 592 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-codemod/src/v5.0.0/jss-to-styled.js · ×1
packages/mui-codemod/src/v5.0.0/jss-to-styled.js: 589 lines of code packages/mui-codemod/src/v5.0.0/jss-to-styled.js:1— packages/mui-codemod/src/v5.0.0/jss-to-styled.js has 589 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-material/src/LinearProgress/LinearProgress.js · ×1
packages/mui-material/src/LinearProgress/LinearProgress.js: 570 lines of code packages/mui-material/src/LinearProgress/LinearProgress.js:1— packages/mui-material/src/LinearProgress/LinearProgress.js has 570 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-codemod/src/v5.0.0/theme-spacing.test/large-actual.js · ×1
packages/mui-codemod/src/v5.0.0/theme-spacing.test/large-actual.js: 567 lines of code packages/mui-codemod/src/v5.0.0/theme-spacing.test/large-actual.js:1— packages/mui-codemod/src/v5.0.0/theme-spacing.test/large-actual.js has 567 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-codemod/src/v5.0.0/theme-spacing.test/large-expected.js · ×1
packages/mui-codemod/src/v5.0.0/theme-spacing.test/large-expected.js: 567 lines of code packages/mui-codemod/src/v5.0.0/theme-spacing.test/large-expected.js:1— packages/mui-codemod/src/v5.0.0/theme-spacing.test/large-expected.js has 567 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-system/src/cssVars/createCssVarsProvider.tsx · ×1
packages/mui-system/src/cssVars/createCssVarsProvider.tsx: 546 lines of code packages/mui-system/src/cssVars/createCssVarsProvider.tsx:1— packages/mui-system/src/cssVars/createCssVarsProvider.tsx has 546 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-material/src/SpeedDial/SpeedDial.js · ×1
packages/mui-material/src/SpeedDial/SpeedDial.js: 542 lines of code packages/mui-material/src/SpeedDial/SpeedDial.js:1— packages/mui-material/src/SpeedDial/SpeedDial.js has 542 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages-internal/core-docs/src/DemoContent/DemoContent.tsx · ×1
packages-internal/core-docs/src/DemoContent/DemoContent.tsx: 519 lines of code packages-internal/core-docs/src/DemoContent/DemoContent.tsx:1— packages-internal/core-docs/src/DemoContent/DemoContent.tsx has 519 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-codemod/src/v6.0.0/theme-v6/test-cases/basicTheme.actual.js · ×1
packages/mui-codemod/src/v6.0.0/theme-v6/test-cases/basicTheme.actual.js: 513 lines of code packages/mui-codemod/src/v6.0.0/theme-v6/test-cases/basicTheme.actual.js:1— packages/mui-codemod/src/v6.0.0/theme-v6/test-cases/basicTheme.actual.js has 513 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-codemod/src/v6.0.0/sx-prop/sx-v6.js · ×1
packages/mui-codemod/src/v6.0.0/sx-prop/sx-v6.js: 510 lines of code packages/mui-codemod/src/v6.0.0/sx-prop/sx-v6.js:1— packages/mui-codemod/src/v6.0.0/sx-prop/sx-v6.js has 510 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-material/src/Popper/BasePopper.tsx · ×1
packages/mui-material/src/Popper/BasePopper.tsx: 510 lines of code packages/mui-material/src/Popper/BasePopper.tsx:1— packages/mui-material/src/Popper/BasePopper.tsx has 510 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-material/src/PaginationItem/PaginationItem.js · ×1
packages/mui-material/src/PaginationItem/PaginationItem.js: 504 lines of code packages/mui-material/src/PaginationItem/PaginationItem.js:1— packages/mui-material/src/PaginationItem/PaginationItem.js has 504 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-material/src/internal/Transition.tsx · ×1
packages/mui-material/src/internal/Transition.tsx: 498 lines of code packages/mui-material/src/internal/Transition.tsx:1— packages/mui-material/src/internal/Transition.tsx has 498 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/mui-material/src/TablePagination/TablePagination.js · ×1
packages/mui-material/src/TablePagination/TablePagination.js: 492 lines of code packages/mui-material/src/TablePagination/TablePagination.js:1— packages/mui-material/src/TablePagination/TablePagination.js has 492 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling· The declared test suite includes a file that cannot be loaded · ×1
The declared test suite includes a file that cannot be loaded packages/mui-codemod/src/v5.0.0/adapter-v4.test/no-styles-import.actual.js:1— This repository declares test tooling, and the ✓ above records that declaration — but packages/mui-codemod/src/v5.0.0/adapter-v4.test/no-styles-import.actual.js and 19 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to.
Dead file (~242 LoC) netlify/functions/feedback-management.mts— no import path from any entry point (509 application, 370 tooling, 1594 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 (~119 LoC) packages/mui-codemod/src/deprecations/all/deprecations-all.js— no import path from any entry point (509 application, 370 tooling, 1594 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/mui-codemod/src/deprecations/all/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~63 LoC) netlify/functions/on-deploy.mts— no import path from any entry point (509 application, 370 tooling, 1594 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 (~55 LoC) packages-internal/core-docs/src/AppLayout/components/ArrowButton.tsx— no import path from any entry point (509 application, 370 tooling, 1594 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 (~44 LoC) packages/mui-material/src/types/OverridableComponentAugmentation.ts— no import path from any entry point (509 application, 370 tooling, 1594 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 (~38 LoC) scripts/testBuiltTypes.mjs— no import path from any entry point (509 application, 370 tooling, 1594 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) scripts/test.mjs— no import path from any entry point (509 application, 370 tooling, 1594 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 (~12 LoC) packages/mui-codemod/src/v7.0.0/all/v7-all.js— no import path from any entry point (509 application, 370 tooling, 1594 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/mui-codemod/src/v7.0.0/all/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~7 LoC) packages/mui-lab/src/internal/svg-icons/ArrowDropDown.tsx— no import path from any entry point (509 application, 370 tooling, 1594 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 (~3 LoC) packages/mui-material/src/utils/getEventTarget.ts— no import path from any entry point (509 application, 370 tooling, 1594 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 'webpack' packages-internal/markdown/loader.mjs:117— 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.
Unlisted import 'ast-types' packages/mui-codemod/src/util/appendAttribute.js: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.
Unlisted import 'lz-string' test/e2e-website/demo-docs-production.baseline.ts:5— 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 '@arethetypeswrong/cli' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@typescript/native' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'cpy-cli' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'git-url-parse' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'pkg-pr-new' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'serve' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'supports-color' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'vitest-fail-on-console' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'sinon' — Declared in packages/mui-lab/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.
Swallowed exception (caught, then discarded) packages/mui-utils/src/useLocalStorageState/useLocalStorageState.ts:79— `catch` 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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Orphaned file packages/mui-codemod/src/v5.0.0/jss-to-tss-react.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mui-material/src/index.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages-internal/scripts/typescript-to-proptypes/src/generatePropTypes.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mui-codemod/src/v5.0.0/joy-text-field-to-input.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mui-codemod/src/v5.0.0/date-pickers-moved-to-x.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mui-codemod/src/deprecations/utils/replaceComponentsWithSlots.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mui-material/src/utils/useSlot.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mui-codemod/src/v1.0.0/color-imports.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mui-system/src/style/style.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 REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mui-codemod/src/v6.0.0/list-item-button-prop/list-item-button-prop.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages-internal/api-docs-builder/src/utils/generatePropTypeDescription.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages-internal/api-docs-builder/src/utils/createTypeScriptProject.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mui-material/src/styles/createTransitions.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages-internal/docs-utils/src/createTypeScriptProject.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mui-material/src/usePagination/usePagination.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages-internal/scripts/typescript-to-proptypes/src/createType.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mui-codemod/src/v5.0.0/tree-view-moved-to-x.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mui-codemod/src/v5.0.0/base-remove-component-prop.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mui-codemod/src/v5.0.0/base-hook-imports.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mui-material/src/Paper/paperClasses.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mui-codemod/src/v5.0.0/base-use-named-exports.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/mui-codemod/src/v5.0.0/joy-avatar-remove-imgProps.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Duplicated predicate docs/data/material/getting-started/templates/crud-dashboard/components/DashboardSidebar.js:154— `!!matchPath('/employees/*', pathname) || pathname === '/'` appears character-identically in 2 files — docs/data/material/getting-started/templates/crud-dashboard/components/DashboardSidebar.js, docs/data/material/getting-started/templates/crud-dashboard/components/DashboardSidebar.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages-internal/api-docs-builder/src/utils/getPropsFromComponentNode.ts:44— `!!node.initializer && ts.isCallExpression(node.initializer) && ts.isCallExpression(node.initializer.expression) && ts.isIdentifier(node.init…` appears character-identically in 2 files — packages-internal/api-docs-builder/src/utils/getPropsFromComponentNode.ts, packages-internal/docs-utils/src/getPropsFromComponentNode.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/mui-codemod/src/v6.0.0/system-props/removeSystemProps.js:228— `!elementReplacement[elementName] || elementReplacement[elementName].matcher(key, val)` appears character-identically in 2 files — packages/mui-codemod/src/v6.0.0/system-props/removeSystemProps.js, packages/mui-codemod/src/v9.0.0/system-props/removeSystemProps.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate docs/data/material/getting-started/templates/sign-in-side/components/SignInCard.js:68— `!email.value || !/\S+@\S+\.\S+/.test(email.value)` appears character-identically in 6 files — docs/data/material/getting-started/templates/sign-in-side/components/SignInCard.js, docs/data/material/getting-started/templates/sign-in-side/components/SignInCard.tsx, docs/data/material/getting-started/templates/sign-in/SignIn.js, docs/data/material/getting-started/templates/sign-in/SignIn.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 docs/data/material/getting-started/templates/crud-dashboard/components/DashboardSidebar.js:107— `!isOverSmViewport && !hasNestedNavigation` appears character-identically in 2 files — docs/data/material/getting-started/templates/crud-dashboard/components/DashboardSidebar.js, docs/data/material/getting-started/templates/crud-dashboard/components/DashboardSidebar.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/mui-material/src/Accordion/Accordion.js:47— `!ownerState.disableGutters && styles.gutters` appears character-identically in 6 files — packages/mui-material/src/Accordion/Accordion.js, packages/mui-material/src/ListItem/ListItem.js, packages/mui-material/src/ListItemButton/ListItemButton.js, packages/mui-material/src/ListSubheader/ListSubheader.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/mui-material/src/List/List.js:29— `!ownerState.disablePadding && styles.padding` appears character-identically in 2 files — packages/mui-material/src/List/List.js, packages/mui-material/src/ListItem/ListItem.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/mui-material/src/AccordionActions/AccordionActions.js:26— `!ownerState.disableSpacing && styles.spacing` appears character-identically in 3 files — packages/mui-material/src/AccordionActions/AccordionActions.js, packages/mui-material/src/CardActions/CardActions.js, packages/mui-material/src/DialogActions/DialogActions.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/mui-material/src/FilledInput/FilledInput.js:57— `!ownerState.disableUnderline && styles.underline` appears character-identically in 2 files — packages/mui-material/src/FilledInput/FilledInput.js, packages/mui-material/src/Input/Input.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate docs/data/material/getting-started/templates/sign-in-side/components/SignInCard.js:77— `!password.value || password.value.length < 6` appears character-identically in 6 files — docs/data/material/getting-started/templates/sign-in-side/components/SignInCard.js, docs/data/material/getting-started/templates/sign-in-side/components/SignInCard.tsx, docs/data/material/getting-started/templates/sign-in/SignIn.js, docs/data/material/getting-started/templates/sign-in/SignIn.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages-internal/markdown/loader.mjs:671— `!relative.startsWith('./') && !relative.startsWith('../')` appears character-identically in 2 files — packages-internal/markdown/loader.mjs, packages-internal/scripts/generate-llms-txt/src/loadDemoSource.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages-internal/core-docs/src/DemoContent/DemoContent.tsx:264— `!variantCode || typeof variantCode === 'string'` appears character-identically in 2 files — packages-internal/core-docs/src/DemoContent/DemoContent.tsx, packages-internal/core-docs/src/DemoContent/useMuiChatExporter.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/mui-material/src/CircularProgress/CircularProgress.js:277— `!warnedInvalidMinMaxValue && (value < min || value > max || min >= max)` appears character-identically in 2 files — packages/mui-material/src/CircularProgress/CircularProgress.js, packages/mui-material/src/LinearProgress/LinearProgress.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:66— `!whitelist.has(moduleName) && moduleName !== 'withStyles'` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:330— `(aData.required && bData.required) || (!aData.required && !bData.required)` appears character-identically in 2 files — REDACTED, packages-internal/api-docs-builder/src/ApiBuilders/HookApiBuilder.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages-internal/api-docs-builder/src/utils/getPropsFromComponentNode.ts:230— `(ts.isArrowFunction(node.initializer) || ts.isFunctionExpression(node.initializer)) && node.initializer.parameters.length === 1` appears character-identically in 2 files — packages-internal/api-docs-builder/src/utils/getPropsFromComponentNode.ts, packages-internal/docs-utils/src/getPropsFromComponentNode.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages-internal/api-docs-builder/src/utils/getPropsFromComponentNode.ts:244— `(ts.isArrowFunction(potentialComponent) || ts.isFunctionExpression(potentialComponent)) && potentialComponent.parameters.length > 0 && getJS…` appears character-identically in 2 files — packages-internal/api-docs-builder/src/utils/getPropsFromComponentNode.ts, packages-internal/docs-utils/src/getPropsFromComponentNode.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/mui-material/src/locale/hrHR.ts:39— `[2, 3, 4].includes(lastDigit) && ![12, 13, 14].includes(lastTwoDigits)` appears character-identically in 2 files — packages/mui-material/src/locale/hrHR.ts, packages/mui-material/src/locale/srRS.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/mui-material/src/ListItem/ListItem.js:39— `alignItems === 'flex-start' && 'alignItemsFlexStart'` appears character-identically in 4 files — packages/mui-material/src/ListItem/ListItem.js, packages/mui-material/src/ListItemAvatar/ListItemAvatar.js, packages/mui-material/src/ListItemButton/ListItemButton.js, packages/mui-material/src/ListItemIcon/ListItemIcon.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/mui-codemod/src/v6.0.0/styled/styled-v6.js:39— `arg.type === 'ArrowFunctionExpression' && arg.params[0] && arg.params[0].type === 'ObjectPattern'` appears character-identically in 2 files — packages/mui-codemod/src/v6.0.0/styled/styled-v6.js, packages/mui-codemod/src/v6.0.0/theme-v6/theme-v6.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/mui-codemod/src/v6.0.0/system-props/removeSystemProps.js:239— `attr.type !== 'JSXAttribute' || !attrToPrune.includes(attr?.name?.name)` appears character-identically in 2 files — packages/mui-codemod/src/v6.0.0/system-props/removeSystemProps.js, packages/mui-codemod/src/v9.0.0/system-props/removeSystemProps.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/mui-codemod/src/v6.0.0/grid-v2-props/grid-v2-props.js:203— `attr.type === 'JSXAttribute' && attr.name.name === 'item'` appears character-identically in 2 files — packages/mui-codemod/src/v6.0.0/grid-v2-props/grid-v2-props.js, packages/mui-codemod/src/v7.0.0/grid-props/grid-props.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/mui-codemod/src/deprecations/divider-props/divider-props.js:42— `attr.type === 'JSXAttribute' && attr.name.name === 'sx'` appears character-identically in 2 files — packages/mui-codemod/src/deprecations/divider-props/divider-props.js, packages/mui-codemod/src/deprecations/typography-props/typography-props.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/mui-codemod/src/v6.0.0/grid-v2-props/grid-v2-props.js:213— `attr.type === 'JSXAttribute' && attr.name.name === 'zeroMinWidth'` appears character-identically in 2 files — packages/mui-codemod/src/v6.0.0/grid-v2-props/grid-v2-props.js, packages/mui-codemod/src/v7.0.0/grid-props/grid-props.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/mui-codemod/src/deprecations/utils/movePropIntoSlotProps.js:8— `attr.type === 'JSXAttribute' && attr.name.name === propName` appears character-identically in 2 files — packages/mui-codemod/src/deprecations/utils/movePropIntoSlotProps.js, packages/mui-codemod/src/deprecations/utils/movePropIntoSlots.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
redundant comment packages-internal/markdown/loader.mjs:322— "detect relative import" repeats the code it sits on: 3 of its 3 words (detect, relative, import) are already in `detectRelativeImports(demoName, moduleFilepath, 'JS', importModuleID);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages-internal/markdown/loader.mjs:567— "detect relative import" repeats the code it sits on: 3 of its 3 words (detect, relative, import) are already in `const importModuleIdWithExtension = detectRelativeImports(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages-internal/markdown/loader.mjs:603— "detect relative import" repeats the code it sits on: 3 of its 3 words (detect, relative, import) are already in `const importModuleIdWithExtension = detectRelativeImports(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/mui-codemod/src/v5.0.0/jss-to-styled.js:324— "turn prevStyleArg to ArrowFunction" repeats the code it sits on: 5 of its 6 words (prev, style, arg, arrow, function) are already in `prevStyleArg = j.arrowFunctionExpression(functionExpression.params, prevStyleArg);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/mui-codemod/src/v6.0.0/list-item-button-prop/list-item-button-prop.js:125— "Insert the import for 'ListItemButton' after the last import declaration" repeats the code it sits on: 7 of its 7 words (insert, import, list, item, button, last, declaration) are already in `lastImport.insertAfter(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/mui-codemod/src/v7.0.0/lab-removed-components/lab-removed-components.js:45— "find lab barrel import" repeats the code it sits on: 4 of its 4 words (find, lab, barrel, import) are already in `const labBarrelImports = root`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment scripts/buildLlmsDocs/index.ts:147— "Get demos for this component" repeats the code it sits on: 3 of its 3 words (get, demos, component) are already in `const demos = componentInfo.getDemos();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment scripts/buildLlmsDocs/index.ts:365— "Group files by category" repeats the code it sits on: 3 of its 3 words (group, files, category) are already in `const groupedByCategory: Record<string, GeneratedFile[]> = {};`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/regressions/fixtures/Snackbar/PositionedSnackbarRtl.js:11— "Create rtl cache" repeats the code it sits on: 3 of its 3 words (create, rtl, cache) are already in `const cacheRtl = createCache({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/regressions/fixtures/Tabs/RTLVerticalTabs.js:12— "Create rtl cache" repeats the code it sits on: 3 of its 3 words (create, rtl, cache) are already in `const cacheRtl = createCache({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment test/regressions/fixtures/Tooltip/PositionedTooltipsRtl.js:13— "Create rtl cache" repeats the code it sits on: 3 of its 3 words (create, rtl, cache) are already in `const cacheRtl = createCache({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Documentation: no build, run or usage example packages-internal/scripts/README.md:1— `scripts` is a published package (`package.json` without `"private": true`) and neither `packages-internal/scripts/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 packages/mui-core-downloads-tracker/README.md:1— `mui-core-downloads-tracker` is a published package (`package.json` without `"private": true`) and neither `packages/mui-core-downloads-tracker/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 packages/mui-material-nextjs/README.md:1— `mui-material-nextjs` is a published package (`package.json` without `"private": true`) and neither `packages/mui-material-nextjs/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 packages/mui-material-pigment-css/README.md:1— `mui-material-pigment-css` is a published package (`package.json` without `"private": true`) and neither `packages/mui-material-pigment-css/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 packages/mui-private-theming/README.md:1— `mui-private-theming` is a published package (`package.json` without `"private": true`) and neither `packages/mui-private-theming/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 packages/mui-styled-engine/README.md:1— `mui-styled-engine` is a published package (`package.json` without `"private": true`) and neither `packages/mui-styled-engine/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 packages/mui-styled-engine-sc/README.md:1— `mui-styled-engine-sc` is a published package (`package.json` without `"private": true`) and neither `packages/mui-styled-engine-sc/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 packages/mui-types/README.md:1— `mui-types` is a published package (`package.json` without `"private": true`) and neither `packages/mui-types/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 packages/mui-utils/README.md:1— `mui-utils` is a published package (`package.json` without `"private": true`) and neither `packages/mui-utils/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.
Deprecated: @babel/plugin-proposal-private-methods REDACTED:2171— @babel/plugin-proposal-private-methods 7.18.6 is resolved in REDACTED and 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-private-methods instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @material-ui/styles REDACTED:3645— @material-ui/styles 4.11.5 is resolved in REDACTED and is marked deprecated by its publisher: "Material UI v4 doesn't receive active development since September 2021. See the guide https://mui.com/material-ui/migration/migration-v4/ to upgrade to v5.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @types/parse-path REDACTED:5379— @types/parse-path 7.1.0 is resolved in REDACTED and is marked deprecated by its publisher: "This is a stub types definition. parse-path provides its own type definitions, so you do not need this installed.". 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:7682— glob 10.5.0 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: glob REDACTED:7695— glob 9.3.5 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.
P2 · Observability· Console output used as the logging channel · ×3
Console output used as the logging channel netlify/functions/feedback-management.mts:231— `netlify/functions/feedback-management.mts` reports through `console.*` at line 231 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel netlify/functions/on-deploy.mts:38— `netlify/functions/on-deploy.mts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel netlify/functions/on-deploy.mts:40— `netlify/functions/on-deploy.mts` reports through `console.*` at line 40 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
R8 · Dependency Hygiene· Type-only dependency 'csstype' in production deps · ×3
Type-only dependency 'csstype' in production deps packages/mui-styled-engine/src/index.ts:6— Every import is type-only — move it to devDependencies.
Type-only dependency 'csstype' in production deps packages/mui-styled-engine-sc/src/index.ts:4— Every import is type-only — move it to devDependencies.
Type-only dependency 'csstype' in production deps packages/mui-system/src/styleFunctionSx/OverwriteCSSProperties.ts:1— Every import is type-only — move it to devDependencies.
Blanket warning suppression packages/mui-material/src/useLazyRipple/useLazyRipple.ts:36— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression packages/mui-utils/src/ponyfillGlobal/ponyfillGlobal.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Disabled test test/e2e-website/material-docs.spec.ts:36— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test test/regressions/index.test.js:626— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
README/code drift test/README.md:268— test/README.md names React 18, but the manifest declares `react` 19.3.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/pages/customers/coupa.md:58— docs/pages/customers/coupa.md names React 17, but the manifest declares `react` 19.3.1. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Mock-dominated test: does not call key handlers or fire when disabled packages/mui-material/src/ButtonBase/useButtonBase.test.tsx:216— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 3 significant file(s) lose their only recent owner: packages-internal/core-docs/src/DemoThemeProviders/DemoThemeProviders.tsx, packages/mui-material/src/RadioGroup/RadioGroup.js, packages/mui-lab/src/TabList/TabList.tsx. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 5 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (10 single-owned of 494 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; 494 of the 2067 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)), anonymized user #3 (1 file(s)), anonymized user #4 (1 file(s)), anonymized user #5 (1 file(s)), anonymized user #6 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: packages/mui-system/src/breakpoints/breakpoints.ts, packages/mui-codemod/src/v7.0.0/grid-props/grid-props.js, packages/mui-codemod/src/v4.0.0/theme-spacing-api.js, packages/mui-material/src/styles/index.js, packages/mui-material/src/styles/responsiveFontSizes.js.
No ADRs found package.json:45— 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 `package.json` makes this repository a deployable product (line 45).
D21 · Naming Consistency· `deployURL` spells `URL` where 15 names in the project spell it `Url` · ×1
`deployURL` spells `URL` where 15 names in the project spell it `Url` netlify/functions/on-deploy.mts:9— 15 of 16 names in project repository spell the token `Url` (15 of 16; unit: names in project repository containing `Url`). Peers: GetStartedButtonsProps.primaryUrl (docs/src/components/home/GetStartedButtons.tsx:14); GetStartedButtonsProps.primaryUrlTarget (docs/src/components/home/GetStartedButtons.tsx:15); GetStartedButtonsProps.secondaryUrl (docs/src/components/home/GetStartedButtons.tsx:17); GetStartedButtonsProps.secondaryUrlTarget (docs/src/components/home/GetStartedButtons.tsx:18); AppFooterProps.stackOverflowUrl (docs/src/layouts/AppFooter.tsx:19). Rename to `deployUrl`. [rule N6]
D21 · Naming Consistency· `moduleID` spells `ID` where 61 names in the project spell it `Id` · ×1
`moduleID` spells `ID` where 61 names in the project spell it `Id` packages-internal/core-docs/src/MarkdownDocs/RichMarkdownElement.tsx:9— 61 of 62 names in project repository spell the token `Id` (61 of 62; unit: names in project repository containing `Id`). Peers: employees.getOne(employeeId) (docs/data/material/getting-started/templates/crud-dashboard/data/employees.ts:119); employees.updateOne(employeeId) (docs/data/material/getting-started/templates/crud-dashboard/data/employees.ts:143); employees.deleteOne(employeeId) (docs/data/material/getting-started/templates/crud-dashboard/data/employees.ts:164); NotificationsProvider.generateId (docs/data/material/getting-started/templates/crud-dashboard/hooks/useNotifications/NotificationsProvider.tsx:134); _app.getVersionedProductPath(productId) (docs/pages/_app.tsx:89). Rename to `moduleId`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 5 of 22 project(s) overshoot their size bounds, lowering Project Cohesion to 5.5/10. The most over is `docs` (133193 LoC, 1705 module-visible types across 820 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 72 of 496 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 496 of the 2067 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: packages/mui-codemod/src/v5.0.0/jss-to-tss-react.js, packages/mui-material/src/index.js, packages-internal/scripts/typescript-to-proptypes/src/generatePropTypes.ts, packages/mui-codemod/src/v5.0.0/joy-text-field-to-input.js, packages/mui-codemod/src/v5.0.0/date-pickers-moved-to-x.js, packages/mui-codemod/src/deprecations/utils/replaceComponentsWithSlots.js, packages/mui-material/src/utils/useSlot.ts, packages/mui-codemod/src/v1.0.0/color-imports.js (and 64 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
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.
Logging is not universal — Only 1/6 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `docs`, `packages-internal/core-docs`, `packages/mui-codemod`, `packages/mui-envinfo`, `packages/mui-material-nextjs`.
R8 · Dependency Hygiene· Type-only dependency '@netlify/functions' in production deps · ×1
Type-only dependency '@netlify/functions' in production deps netlify/functions/feedback-management.mts:4— Every import is type-only — move it to devDependencies.
R8 · Dependency Hygiene· Type-only dependency 'hoist-non-react-statics' in production deps · ×1
Type-only dependency 'hoist-non-react-statics' in production deps packages/mui-styled-engine-sc/src/index.ts:5— Every import is type-only — move it to devDependencies.
No security response headers detected netlify.toml:1— None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
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/8 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.
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 — 61/62 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 — ~1.0 `!` null assertions per 1k TypeScript source lines — 109 assertion(s) across the 112070 source line(s) of the 1294 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: REDACTED (7), packages-internal/api-docs-builder/src/utils/getPropsFromComponentNode.ts (5), packages-internal/core-docs/src/MarkdownDocs/RichMarkdownElement.tsx (5). 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.
Hand-rolled JSON/XML parsing via regex packages-internal/scripts/generate-llms-txt/src/loadDemoSource.ts:123— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Skipped (documented): (unnamed test) test/regressions/index.test.js:633— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) test/regressions/index.test.js:652— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) test/regressions/index.test.js:672— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages-internal/core-docs/src/DemoThemeProviders/DemoThemeProviders.test.tsx:147— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) packages-internal/core-docs/src/DemoContent/DemoContainer.test.tsx:78— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) packages-internal/core-docs/src/DemoContent/DemoContainer.test.tsx:108— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) packages-internal/core-docs/src/DemoContent/DemoContentLoading.client.test.tsx:45— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) packages/mui-utils/src/useId/useId.test.tsx:89— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) packages/mui-utils/src/useId/useId.test.tsx:89— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/mui-utils/src/getScrollbarSize/getScrollbarSize.test.ts:19— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) packages/mui-utils/src/getScrollbarSize/getScrollbarSize.test.ts:21— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/mui-utils/src/deepmerge/deepmerge.test.ts:64— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) packages/mui-utils/src/deepmerge/deepmerge.test.ts:64— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/mui-utils/src/appendOwnerState/appendOwnerState.spec.tsx:21— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/mui-system/src/createTheme/createTheme.test.js:59— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) packages/mui-system/src/createTheme/createTheme.test.js:59— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/mui-system/src/createTheme/createTheme.test.js:93— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) packages/mui-system/src/createTheme/createTheme.test.js:93— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/mui-system/src/createTheme/createTheme.test.js:196— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/mui-system/src/Grid/Grid.test.js:50— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) packages/mui-system/src/Grid/Grid.test.js:52— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/mui-system/src/Grid/Grid.test.js:118— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) packages/mui-system/src/Grid/Grid.test.js:118— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/mui-system/src/Box/Box.test.js:61— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) packages/mui-system/src/Box/Box.test.js:61— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Outdated (npm): @babel/core — @babel/core is pinned at 8.1.0; registry.npmjs.org publishes 8.1.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): @babel/runtime — @babel/runtime is pinned at 8.1.0; registry.npmjs.org publishes 8.1.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): @babel/traverse — @babel/traverse is pinned at 8.1.0; registry.npmjs.org publishes 8.1.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): @babel/types — @babel/types is pinned at 8.1.0; registry.npmjs.org publishes 8.1.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): @mui/material — @mui/material is pinned at 9.0.0; registry.npmjs.org publishes 9.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): @mui/material-nextjs — @mui/material-nextjs is pinned at 9.3.0; registry.npmjs.org publishes 9.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): es-toolkit — es-toolkit is pinned at 1.52.0; registry.npmjs.org publishes 1.53.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): marked — marked is pinned at 18.1.3; registry.npmjs.org publishes 18.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): next — next is pinned at 16.4.5; registry.npmjs.org publishes 16.4.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): prettier — prettier is pinned at 3.9.10; registry.npmjs.org publishes 3.10.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-virtuoso — react-virtuoso is pinned at 4.18.20; registry.npmjs.org publishes 4.18.22 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): recast — recast is pinned at 0.24.0; registry.npmjs.org publishes 0.24.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): stylis — stylis is pinned at 4.2.0; registry.npmjs.org publishes 4.4.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
doc comments repeat the names packages/mui-icons-material/scripts/download.mjs:139— 1 of 9 documented parameters and 0 of 4 summaries in `@mui/icons-material` only repeat the member or parameter name (e.g. "The icon object." for `icon`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages-internal/api-docs-builder/src/types/utils.types.ts:46— 0 of 9 documented parameters and 1 of 79 summaries in `@mui/internal-api-docs-builder` only repeat the member or parameter name (e.g. "API pathname" for `apiPathname`). 2 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages-internal/core-docs/src/DocsApp/DocsApp.tsx:54— 0 of 17 documented parameters and 1 of 164 summaries in `@mui/internal-core-docs` only repeat the member or parameter name (e.g. "The parent pages of the active page" for `activePageParents`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages-internal/scripts/generate-llms-txt/src/processApi.ts:158— 6 of 35 documented parameters and 5 of 94 summaries in `@mui/internal-scripts` only repeat the member or parameter name (e.g. "Generate props table" for `generatePropsTable`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/mui-material/src/Autocomplete/Autocomplete.js:1105— 1 of 170 documented parameters and 4 of 2767 summaries in `@mui/material` only repeat the member or parameter name (e.g. "The input value." for `inputValue`). 2 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/mui-types/src/index.ts:85— 0 of 1 documented parameters and 0 of 17 summaries in `@mui/types` only repeat the member or parameter name (e.g. "" for `actual`). 1 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/mui-utils/src/deepmerge/deepmerge.ts:50— 3 of 45 documented parameters and 0 of 85 summaries in `@mui/utils` only repeat the member or parameter name (e.g. "The target object." for `target`). 5 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names test/e2e/index.test.ts:20— 0 of 2 documented parameters and 0 of 1 summaries in `test/e2e` only repeat the member or parameter name (e.g. "" for `page`). 2 documentation tag(s) are empty. 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.
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 01a1d5e5-5cf5-7529-ad37-a8dd49a1c2fc · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 56 · Warnings: 1192 · Recommendations: 170 · Info: 474 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 13-11-2026 @ 17:12 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.