Public report of refinedev/refine, published 26 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 26 October 2026, 21:08 UTC · Survey ID cd_d0821a7e743d46d2a12ba9b5f6efb320
refinedev/refine
Measured 26 October 2026, 21:04 UTC, at code version 2352eb5
Regression: 1 dimension fell since the last survey
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
CAI scoreAt riskDown 3 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 395,443 lines of product code in 38 projects, tests not counted · Estimated rebuild effort: about 3.1 person-years · Weakest lens: Production Readiness, 22
Findings by how serious they are
418 critical971 serious488 minor
12 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
26 October 2026, 21:04 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
89of 89 dimensions measured by tools.
1654of 1877 findings point to an exact file and line, so you can open each one in the code. The other 223 concern the repository as a whole, such as missing documentation.
89dimensions across 8 lenses, read from 395,443 lines of product code in 38 projects.
refinedev/refine is rated At risk because critical security findings are open. Its score is held back because 16 passwords or keys sit in the current code and we found no logging, tracing or health checks in the code. It scores 35 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 22, is the weakest lens and counts most in the score. The best first steps are replacing the 16 exposed passwords or keys and switching the old ones off and replacing the 77 deprecated dependencies, each worth about 10 points. Raising Production Readiness to 70 would lift the score to about 45.
135 known security holes in the packages the code depends on can be used by attackers. Sixty-seven automatic updates take new releases before a bad one can be spotted, and fifty-seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Updating the vulnerable packages, setting a waiting period for automatic updates and pinning each tool to an exact version would close these risks. Limiting each secret to its own step would fix the 17 secrets exposed to more of the pipeline than needed, and the 41 passwords or keys in the code's history and the 16 passwords or keys in the code need replacing, with the old ones switched off. The 15 uses of packages that aren't listed need adding to the project's list of dependencies.
The product code is 395,443 lines, about €450,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 22 to 70, the lowest score rated Strong, the score would rise from 35 to about 45.
Code composition: what the lines of code are
Product code 75%Tests 25%
New since the last survey: 180 findings
These 180 critical or serious findings weren't in the previous survey, on 12 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Test Quality · Skipped test: should use prop for custom text packages/ui-tests/src/tests/fields/boolean.tsx
Test Quality · Skipped test: should invalidates when button is clicked packages/ui-tests/src/tests/buttons/refresh.tsx
Test Quality · Skipped test: should has 'to' param on URL after redirected to /login cypress/e2e/with-remix-material-ui/all.cy.ts
Test Quality · Skipped test: should has 'to' param on URL after redirected to /login cypress/e2e/with-nextjs-next-auth/all.cy.ts
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 828 findings
These 828 critical or serious findings were in the previous survey, on 12 October 2026, and are gone from this one. The first 100 are listed here.
€150,000 to €750,000, for 2,476 to 7,854 hours of work, about 3.1 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 35. 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: 395,443 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 16 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (5), REDACTED (4), REDACTED (3).
Raises the score by about 10 points · Medium effort · REDACTED Scanning
2
Resolve the 77 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (77).
Raises the score by about 10 points · Medium effort · Dependency Hygiene
3
Resolve the 1 Banned license finding(s) in License Compliance — start with REDACTED.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €450,000 to build again, about 3.1 person-years of work. Its weakest lens is Production Readiness, at 22 (Critical). 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 16 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 10 points for medium effort, because it clears the 16 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 6.6 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 4% to 8% on every change. The history of the code shows how much it changes: about 709 lines over the last 90 days, which is about 2,875 lines a year. At that pace, the extra work comes to an estimated 0.3 to 1.5 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
478 modules, with 71 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; 438 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.
documentation.src.components uses documentation.src.components.browser-window, so a change to documentation.src.components.browser-window can break documentation.src.components, while a change to documentation.src.components can't break documentation.src.components.browser-window.
Position
Below the diagonal: documentation.src.components uses a module listed above it, which is the healthy direction.
documentation.src.components.landing uses documentation.src.components.browser-window, so a change to documentation.src.components.browser-window can break documentation.src.components.landing, while a change to documentation.src.components.landing can't break documentation.src.components.browser-window.
Position
Below the diagonal: documentation.src.components.landing uses a module listed above it, which is the healthy direction.
documentation.src.components.refine-week uses documentation.src.components.browser-window, so a change to documentation.src.components.browser-window can break documentation.src.components.refine-week, while a change to documentation.src.components.refine-week can't break documentation.src.components.browser-window.
Position
Below the diagonal: documentation.src.components.refine-week uses a module listed above it, which is the healthy direction.
documentation.src.components.sandpack uses documentation.src.components.browser-window, so a change to documentation.src.components.browser-window can break documentation.src.components.sandpack, while a change to documentation.src.components.sandpack can't break documentation.src.components.browser-window.
Position
Below the diagonal: documentation.src.components.sandpack uses a module listed above it, which is the healthy direction.
documentation.src.hooks uses documentation.src.components.browser-window, so a change to documentation.src.components.browser-window can break documentation.src.hooks, while a change to documentation.src.hooks can't break documentation.src.components.browser-window.
Position
Below the diagonal: documentation.src.hooks uses a module listed above it, which is the healthy direction.
31 pairs of types, where a type in documentation.src.refine-theme uses a type in documentation.src.components.browser-window. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
documentation.src.refine-theme uses documentation.src.components.browser-window, so a change to documentation.src.components.browser-window can break documentation.src.refine-theme, while a change to documentation.src.refine-theme can't break documentation.src.components.browser-window.
Position
Below the diagonal: documentation.src.refine-theme uses a module listed above it, which is the healthy direction.
documentation.src.refine-theme uses documentation.src.refine-theme.blog-toc, so a change to documentation.src.refine-theme.blog-toc can break documentation.src.refine-theme, while a change to documentation.src.refine-theme can't break documentation.src.refine-theme.blog-toc.
Position
Below the diagonal: documentation.src.refine-theme uses a module listed above it, which is the healthy direction.
documentation.src.refine-theme uses documentation.src.refine-theme.product-hunt-logo, so a change to documentation.src.refine-theme.product-hunt-logo can break documentation.src.refine-theme, while a change to documentation.src.refine-theme can't break documentation.src.refine-theme.product-hunt-logo.
Position
Below the diagonal: documentation.src.refine-theme uses a module listed above it, which is the healthy direction.
packages.ably uses packages.ably.src, so a change to packages.ably.src can break packages.ably, while a change to packages.ably can't break packages.ably.src.
Position
Below the diagonal: packages.ably uses a module listed above it, which is the healthy direction.
packages.airtable.src.utils uses packages.core.src.contexts.data.types, so a change to packages.core.src.contexts.data.types can break packages.airtable.src.utils, while a change to packages.airtable.src.utils can't break packages.core.src.contexts.data.types.
Position
Below the diagonal: packages.airtable.src.utils uses a module listed above it, which is the healthy direction.
packages.antd.src.definitions uses packages.antd.src.components.table.components.filterDropdown, so a change to packages.antd.src.components.table.components.filterDropdown can break packages.antd.src.definitions, while a change to packages.antd.src.definitions can't break packages.antd.src.components.table.components.filterDropdown.
Position
Below the diagonal: packages.antd.src.definitions uses a module listed above it, which is the healthy direction.
packages.antd.src.hooks.form.useDrawerForm uses packages.core.src.contexts.data.types, so a change to packages.core.src.contexts.data.types can break packages.antd.src.hooks.form.useDrawerForm, while a change to packages.antd.src.hooks.form.useDrawerForm can't break packages.core.src.contexts.data.types.
Position
Below the diagonal: packages.antd.src.hooks.form.useDrawerForm uses a module listed above it, which is the healthy direction.
packages.antd.src.hooks.form.useModalForm uses packages.core.src.contexts.data.types, so a change to packages.core.src.contexts.data.types can break packages.antd.src.hooks.form.useModalForm, while a change to packages.antd.src.hooks.form.useModalForm can't break packages.core.src.contexts.data.types.
Position
Below the diagonal: packages.antd.src.hooks.form.useModalForm uses a module listed above it, which is the healthy direction.
packages.antd.src.hooks.table.useEditableTable uses packages.core.src.contexts.data.types, so a change to packages.core.src.contexts.data.types can break packages.antd.src.hooks.table.useEditableTable, while a change to packages.antd.src.hooks.table.useEditableTable can't break packages.core.src.contexts.data.types.
Position
Below the diagonal: packages.antd.src.hooks.table.useEditableTable uses a module listed above it, which is the healthy direction.
packages.antd.src.hooks.table.useTable uses packages.antd.src.hooks.table.useTable.paginationLink, so a change to packages.antd.src.hooks.table.useTable.paginationLink can break packages.antd.src.hooks.table.useTable, while a change to packages.antd.src.hooks.table.useTable can't break packages.antd.src.hooks.table.useTable.paginationLink.
Position
Below the diagonal: packages.antd.src.hooks.table.useTable uses a module listed above it, which is the healthy direction.
packages.antd.src.providers uses packages.core.src.contexts.notification.types, so a change to packages.core.src.contexts.notification.types can break packages.antd.src.providers, while a change to packages.antd.src.providers can't break packages.core.src.contexts.notification.types.
Position
Below the diagonal: packages.antd.src.providers uses a module listed above it, which is the healthy direction.
packages.appwrite.src.utils uses packages.core.src.contexts.data.types, so a change to packages.core.src.contexts.data.types can break packages.appwrite.src.utils, while a change to packages.appwrite.src.utils can't break packages.core.src.contexts.data.types.
Position
Below the diagonal: packages.appwrite.src.utils uses a module listed above it, which is the healthy direction.
packages.chakra-ui.src.providers uses packages.core.src.contexts.notification.types, so a change to packages.core.src.contexts.notification.types can break packages.chakra-ui.src.providers, while a change to packages.chakra-ui.src.providers can't break packages.core.src.contexts.notification.types.
Position
Below the diagonal: packages.chakra-ui.src.providers uses a module listed above it, which is the healthy direction.
packages.cli.src uses packages.cli.src.telemetry, so a change to packages.cli.src.telemetry can break packages.cli.src, while a change to packages.cli.src can't break packages.cli.src.telemetry.
Position
Below the diagonal: packages.cli.src uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.cli.src.commands.add.sub-commands.integration uses a type in packages.cli.src.commands.add.sub-commands.integration.run-transformer.
packages.cli.src.commands.add.sub-commands.integration uses packages.cli.src.commands.add.sub-commands.integration.run-transformer, so a change to packages.cli.src.commands.add.sub-commands.integration.run-transformer can break packages.cli.src.commands.add.sub-commands.integration, while a change to packages.cli.src.commands.add.sub-commands.integration can't break packages.cli.src.commands.add.sub-commands.integration.run-transformer.
Position
Below the diagonal: packages.cli.src.commands.add.sub-commands.integration uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.cli.src.commands.add.sub-commands.integration.utils.prettify-choice uses a type in packages.cli.src.commands.add.sub-commands.integration.packages.
packages.cli.src.commands.add.sub-commands.integration.utils.prettify-choice uses packages.cli.src.commands.add.sub-commands.integration.packages, so a change to packages.cli.src.commands.add.sub-commands.integration.packages can break packages.cli.src.commands.add.sub-commands.integration.utils.prettify-choice, while a change to packages.cli.src.commands.add.sub-commands.integration.utils.prettify-choice can't break packages.cli.src.commands.add.sub-commands.integration.packages.
Position
Below the diagonal: packages.cli.src.commands.add.sub-commands.integration.utils.prettify-choice uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages.cli.src.commands.add.sub-commands.provider uses a type in packages.cli.src.commands.add.sub-commands.provider.providers.
packages.cli.src.commands.add.sub-commands.provider uses packages.cli.src.commands.add.sub-commands.provider.providers, so a change to packages.cli.src.commands.add.sub-commands.provider.providers can break packages.cli.src.commands.add.sub-commands.provider, while a change to packages.cli.src.commands.add.sub-commands.provider can't break packages.cli.src.commands.add.sub-commands.provider.providers.
Position
Below the diagonal: packages.cli.src.commands.add.sub-commands.provider uses a module listed above it, which is the healthy direction.
packages.core.src.contexts.refine.types uses packages.core.src.contexts.data.types, so a change to packages.core.src.contexts.data.types can break packages.core.src.contexts.refine.types, while a change to packages.core.src.contexts.refine.types can't break packages.core.src.contexts.data.types.
Position
Below the diagonal: packages.core.src.contexts.refine.types uses a module listed above it, which is the healthy direction.
packages.core.src.definitions.helpers.router uses packages.core.src.contexts.data.types, so a change to packages.core.src.contexts.data.types can break packages.core.src.definitions.helpers.router, while a change to packages.core.src.definitions.helpers.router can't break packages.core.src.contexts.data.types.
Position
Below the diagonal: packages.core.src.definitions.helpers.router uses a module listed above it, which is the healthy direction.
packages.core.src.definitions.helpers.router uses packages.core.src.contexts.resource.types, so a change to packages.core.src.contexts.resource.types can break packages.core.src.definitions.helpers.router, while a change to packages.core.src.definitions.helpers.router can't break packages.core.src.contexts.resource.types.
Position
Below the diagonal: packages.core.src.definitions.helpers.router uses a module listed above it, which is the healthy direction.
packages.nextjs-router.src.pages uses documentation.src.components.browser-window, so a change to documentation.src.components.browser-window can break packages.nextjs-router.src.pages, while a change to packages.nextjs-router.src.pages can't break documentation.src.components.browser-window.
Position
Below the diagonal: packages.nextjs-router.src.pages uses a module listed above it, which is the healthy direction.
packages.nextjs-router.src.pages uses packages.nextjs-router.src.pages.use-document-title, so a change to packages.nextjs-router.src.pages.use-document-title can break packages.nextjs-router.src.pages, while a change to packages.nextjs-router.src.pages can't break packages.nextjs-router.src.pages.use-document-title.
Position
Below the diagonal: packages.nextjs-router.src.pages uses a module listed above it, which is the healthy direction.
packages.react-router.src uses documentation.src.components.browser-window, so a change to documentation.src.components.browser-window can break packages.react-router.src, while a change to packages.react-router.src can't break documentation.src.components.browser-window.
Position
Below the diagonal: packages.react-router.src uses a module listed above it, which is the healthy direction.
packages.react-router.src uses packages.nextjs-router.src.pages.use-document-title, so a change to packages.nextjs-router.src.pages.use-document-title can break packages.react-router.src, while a change to packages.react-router.src can't break packages.nextjs-router.src.pages.use-document-title.
Position
Below the diagonal: packages.react-router.src uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.cli.src.commands.add.sub-commands.integration.utils uses a type in packages.cli.src.commands.add.sub-commands.integration.utils.prettify-choice.
packages.cli.src.commands.add.sub-commands.integration.utils uses packages.cli.src.commands.add.sub-commands.integration.utils.prettify-choice, so a change to packages.cli.src.commands.add.sub-commands.integration.utils.prettify-choice can break packages.cli.src.commands.add.sub-commands.integration.utils, while a change to packages.cli.src.commands.add.sub-commands.integration.utils can't break packages.cli.src.commands.add.sub-commands.integration.utils.prettify-choice.
Position
Below the diagonal: packages.cli.src.commands.add.sub-commands.integration.utils uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
227
High / Critical
A05:2025 — Injection
196
High / Critical
A07:2025 — Authentication Failures
58
High / Critical
A02:2025 — Security Misconfiguration
12
High / Critical
Roadmap
Immediately resolve the 16 leaked secrets in source files, address the 77 deprecated dependencies, and fix the single banned license to clear critical compliance and security blockers. Next, implement structured logging using pino or winston across all services to establish basic observability. Finally, integrate a SAST tool into the CI pipeline to automatically fail builds on security regressions.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 16 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (5), REDACTED (4), REDACTED (3).
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
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 — 418
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 — 971
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 — 488
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 12
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 89 of 89 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 89 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, 1654 of 1877 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D11 Test Reliability — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Test reliability for the vitest suite in the repository root was NOT MEASURED: the dependency install for the repository root failed in the analyzer sandbox (throw new Error(), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Test reliability for the jest suite in examples/blog-invoice-generator/ was NOT MEASURED: the dependency install for examples/blog-invoice-generator/ failed in the analyzer sandbox (throw new Error(), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Test reliability for the vitest suite in packages/ably/ was NOT MEASURED: the dependency install for packages/ably/ failed in the analyzer sandbox (throw new Error(), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Test reliability for the vitest suite in packages/airtable/ was NOT MEASURED: the dependency install for packages/airtable/ failed in the analyzer sandbox (throw new Error(), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Test reliability for the vitest suite in packages/antd/ was NOT MEASURED: the dependency install for packages/antd/ failed in the analyzer sandbox (throw new Error(), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Test reliability for the vitest suite in packages/appwrite/ was NOT MEASURED: the dependency install for packages/appwrite/ failed in the analyzer sandbox (throw new Error(), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Test reliability for the vitest suite in packages/chakra-ui/ was NOT MEASURED: the dependency install for packages/chakra-ui/ failed in the analyzer sandbox (throw new Error(), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Test reliability for the vitest suite in packages/cli/ was NOT MEASURED: the dependency install for packages/cli/ failed in the analyzer sandbox (throw new Error(), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Test reliability for the vitest suite in packages/codemod/ was NOT MEASURED: the dependency install for packages/codemod/ failed in the analyzer sandbox (throw new Error(), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Test reliability for the vitest suite in packages/core/ was NOT MEASURED: the dependency install for packages/core/ failed in the analyzer sandbox (throw new Error(), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D11 Test Reliability — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Test reliability for the vitest suite in packages/create-refine-app/ was NOT MEASURED: the dependency install for packages/create-refine-app/ failed in the analyzer sandbox (throw new Error(), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packages/antd/src/hooks/form/useForm.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D41 Kernel & Syscall Confinement — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Documentation/k8s/refine-documentation/templates/deployment.yaml:2 did not read as a pod spec (a templated manifest such as Helm's that is not YAML until rendered, or a workload whose pod spec this check does not locate), so the seccomp/AppArmor profile in force there was not judged and no row about them can appear on this card.
D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
AC1 Text alternatives — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository builds user interface as HTML STRINGS — 244 script file(s) building 2483 markup element(s) as HTML strings, carrying 28 role/aria/tabindex attribute(s) (e.g. packages/inferencer/src/use-infer-fetch/index.tsx, packages/inferencer/src/inferencers/mui/list.tsx, packages/inferencer/src/inferencers/mui/show.tsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 409 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository builds user interface as HTML STRINGS — 244 script file(s) building 2483 markup element(s) as HTML strings, carrying 28 role/aria/tabindex attribute(s) (e.g. packages/inferencer/src/use-infer-fetch/index.tsx, packages/inferencer/src/inferencers/mui/list.tsx, packages/inferencer/src/inferencers/mui/show.tsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 409 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository builds user interface as HTML STRINGS — 244 script file(s) building 2483 markup element(s) as HTML strings, carrying 28 role/aria/tabindex attribute(s) (e.g. packages/inferencer/src/use-infer-fetch/index.tsx, packages/inferencer/src/inferencers/mui/list.tsx, packages/inferencer/src/inferencers/mui/show.tsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 409 parsed markup document(s) only. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the runs counted here are the ones its producer could not take — an element whose TAG NAME is a concatenated expression has no statically knowable identity, and a string-built run inside a .jsx/.tsx file is already read as JSX — so they were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC4 Keyboard semantics — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository builds user interface as HTML STRINGS — 244 script file(s) building 2483 markup element(s) as HTML strings, carrying 28 role/aria/tabindex attribute(s) (e.g. packages/inferencer/src/use-infer-fetch/index.tsx, packages/inferencer/src/inferencers/mui/list.tsx, packages/inferencer/src/inferencers/mui/show.tsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 409 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository builds user interface as HTML STRINGS — 244 script file(s) building 2483 markup element(s) as HTML strings, carrying 28 role/aria/tabindex attribute(s) (e.g. packages/inferencer/src/use-infer-fetch/index.tsx, packages/inferencer/src/inferencers/mui/list.tsx, packages/inferencer/src/inferencers/mui/show.tsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 409 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository builds user interface as HTML STRINGS — 244 script file(s) building 2483 markup element(s) as HTML strings, carrying 28 role/aria/tabindex attribute(s) (e.g. packages/inferencer/src/use-infer-fetch/index.tsx, packages/inferencer/src/inferencers/mui/list.tsx, packages/inferencer/src/inferencers/mui/show.tsx) — that this run could NOT read, and the accessibility cards beside it were measured over the 409 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.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via Dockerfile (examples/store/Dockerfile). docker build failed (exit 1) — ------ Dockerfile:1 -------------------- 1 | >>> FROM refinedev/node:18 AS base 2 | 3 | ENV PNPM_HOME="/pnpm" -------------------- ERROR: failed to solve: refinedev/node:18: failed to resolve source metadata for docker.io/refinedev/node:18: failed to do request: Head "https://registry-1.docker.io/v2/refinedev/node/manifests/18": Forbidden; runtime evidence skipped.
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. '@supabase/supabase-js' is imported (packages/supabase/src/index.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. '@supabase/supabase-js' is imported (packages/supabase/src/index.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. '@supabase/supabase-js' is imported (packages/supabase/src/index.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. '@supabase/supabase-js' is imported (packages/supabase/src/index.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 436 further occurrence(s) are not listed individually; the score already reflects all 476.
R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 273 further occurrence(s) are not listed individually; the score already reflects all 313.
R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 68 further occurrence(s) are not listed individually; the score already reflects all 108.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations: 44 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
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.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
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.
108 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was list.renderer at 97. A further 3 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being index.transformMuiOperatorToCrudOperator at 23 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/nestjsx-crud/src/utils/mapOperator.ts (mapOperator.mapOperator at 22), packages/rest/src/data-providers/nestjsx-crud/utils/mapOperator.ts (mapOperator.mapOperator at 22). 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.
+ 97 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with list.renderer (cyclomatic 97), list.renderer (cyclomatic 91), list.renderer (cyclomatic 76). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 5.1 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 116 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 9 bodies over 60 down to 60 or less in Cognitive Complexity — start with index.useRelationFetch (cognitive 87), show.renderer (cognitive 78), index.createInferencer (cognitive 75). — 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 9 together lifts Cognitive Complexity from 4.7 to about 5.4/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.3 / 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 128 FunctionTooLong finding(s) in God Classes — start with REDACTED (36), REDACTED (7), REDACTED (5). — One of this dimension's main actionable groups (128 warning-level).
Resolve the 23 FileTooLong finding(s) in God Classes — start with show.tsx (5), list.tsx (4), landing-hero-mobile.tsx. — One of this dimension's main actionable groups (23 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.1 / 10Stronggated by 4 serious findings✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
37 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 5 module(s) off the main sequence, with abstractness counted on 35 of the 37 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: @refinedev/core · ×4
Off the main sequence: @refinedev/devtools-shared
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).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 92.2%. Measured from the JavaScript/TypeScript suite (jest via `pnpm install --frozen-lockfile --ignore-scripts` in documentation/; jest in examples/blog-invoice-generator/: not run).
✓ On the Gold path — maintain.
Detailed fixes: d8_recommendation.md.
Do you agree with this assessment?
D9 · Test Distribution8.5 / 10Strong✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
3507 test methods: 3107 unit, 0 integration, 0 BDD, 400 e2e. The JavaScript/TypeScript suite contributes 3507 `it`/`test` case(s) across 604 test file(s) declaring at least one; its tier split is read from package names and paths only.
What to do
Improve Test Distribution — currently 8.5/10. — 3507 test methods: 3107 unit, 0 integration, 0 BDD, 400 e2e. The JavaScript/TypeScript suite contributes 3507 `it`/`test` case(s) across 604 test file(s) declaring at least one; its tier split is read from package names and paths only.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.5 / 10Stronggated by 117 serious 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.
4 skipped, 113 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 3507 tests.
No assertions: should render success · ×113packages/ui-tests/src/tests/autoSaveIndicator.tsx:9
Skipped test: should use prop for custom text · ×4packages/ui-tests/src/tests/fields/boolean.tsx:10
Mock-dominated test: uses only the first realtime filter and warns when multiple filters are provided · ×37packages/supabase/test/liveProvider/index.spec.ts:25
What to do
Resolve the 113 No assertions finding(s) in Test Quality — start with all.cy.ts (28), index.spec.tsx (24), useUpdate.spec.tsx (8). — One of this dimension's main actionable groups (113 warning-level).
Resolve the 37 Mock-dominated test finding(s) in Test Quality — start with index.spec.ts (24), navigate-to-resource.test.tsx (5), index.test.ts (2). — One of this dimension's main actionable groups (37 recommendation-level).
Resolve the 4 Skipped test finding(s) in Test Quality — start with all.cy.ts (2), boolean.tsx, refresh.tsx. — One of this dimension's main actionable groups (4 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
0 flaky across 1 measured tier(s). JavaScript/TypeScript (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root; jest via `pnpm install --frozen-lockfile --ignore-scripts` in documentation/ (1 tests); jest via `pnpm install --frozen-lockfile --ignore-scripts` in examples/blog-invoice-generator/; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/ably/; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/airtable/; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/antd/; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/appwrite/; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/chakra-ui/; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/cli/; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/codemod/; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/core/; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/create-refine-app/): measured (0 flaky).
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
226 outdated direct production npm dependency(ies) of 279 graded, 8 pinning defect(s), across 254 REDACTED (39 of them the product) and 2 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 11 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 77 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (77). — One of this dimension's main actionable groups (77 recommendation-level).
Resolve the 15 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (15). — One of this dimension's main actionable groups (15 warning-level).
Resolve the 8 One package at two majors across the workspace finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (8 warning-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 16 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (5), REDACTED (4), REDACTED (3). — One of this dimension's main actionable groups (16 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
1 of 279 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 279 production dependency(ies) this repository's committed lockfile resolves, across 39 product REDACTED manifest(s). Its 2133 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 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 1 Banned license finding(s) in License Compliance — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Enforce License Compliance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
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.
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.
4 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/codemod/src/transformations/v5/mutation-result-to-mutation-property.ts. Counted over 333 of the 1284 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
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.
12 deducted task-comment markers across 384020 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 12 TodoComment finding(s) in Explicit Debt — start with REDACTED (2), cart.tsx (2), create-data-provider.ts. — One of this dimension's main actionable groups (12 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 1132 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.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: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
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.
33 domain type(s) cross context boundaries across 241 contexts.
Cross-context type BaseKey (core → antd) · ×4packages/antd/src/hooks/form/useModalForm/useModalForm.ts:300
Cross-context type CrudFilter (core → appwrite) · ×2packages/appwrite/src/utils/replaceIdWithAppwriteId.ts:8
Cross-context type CrudOperators (core → mui) · ×2packages/mui/src/definitions/dataGrid/index.ts:35
Cross-context type CrudFilter (core → react-table) · ×2packages/react-table/src/utils/column-filters-to-crud-filters/index.ts:18
Cross-context type CrudOperators (core → rest) · ×2packages/rest/src/data-providers/nestjsx-crud/utils/mapOperator.ts:4
+ 21 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 Cross-context type BaseKey (core → antd) finding(s) in Boundary Type-Coupling — start with useEditableTable.ts (2), useModalForm.ts, useDrawerForm.ts. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 2 Cross-context type CrudFilter (core → appwrite) finding(s) in Boundary Type-Coupling — start with replaceIdWithAppwriteId.ts, generateFilter.ts. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Cross-context type CrudOperators (core → mui) finding(s) in Boundary Type-Coupling — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d23_recommendation.md · top locations in Appendix A, every location in findings.md.
4 of 38 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
41 finding(s): 0 critical, 41 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 38 REDACTED finding(s) in Secrets (history) — start with REDACTED (8), REDACTED (6), REDACTED (5). — One of this dimension's main actionable groups (38 issue-level).
Resolve the 3 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 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).
196 finding(s): 0 critical, 165 high, 31 medium, 0 low. 57 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 8 file(s) — `documentation/blog/authors.yml`, `REDACTED`, `documentation/k8s/refine-documentation/templates/hpa.yaml`, `documentation/k8s/refine-documentation/templates/ingress.yaml`, `documentation/k8s/refine-documentation/templates/service.yaml`, … (+3 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 2 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
+ 15 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 65 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (65). — One of this dimension's main actionable groups (65 issue-level).
Resolve the 11 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (11 issue-level).
No action in Static Analysis (SAST) — all 57 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (57 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 106 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (106). — One of this dimension's main actionable groups (106 issue-level).
Resolve the 22 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (22). — One of this dimension's main actionable groups (22 issue-level).
Resolve the 4 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 6 Low IaC finding(s) in IaC & Container Security — start with REDACTED (6). — One of this dimension's main actionable groups (6 recommendation-level).
Resolve the 5 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
59 of 333 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/inferencer/src/inferencers/headless/list.tsx. Counted over 333 of the 1284 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 5 Orphaned knowledge finding(s) in Knowledge Freshness — start with list.tsx (3), data-table-filter.tsx, sidebar.tsx. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 54 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (6), edit.tsx (3), REDACTED (2). — One of this dimension's main actionable groups (54 recommendation-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 6 Change coupling finding(s) in Change Coupling — start with REDACTED (2), useUpdate.ts, useDrawerForm.ts. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 3 Change coupling clique finding(s) in Change Coupling — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Change-coupling hub finding(s) in Change Coupling — start with useDelete.ts, useList.ts. — One of this dimension's main actionable groups (2 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.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.
What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
No dependency in any ecosystem this repository declares is published as malicious.
✓ On the Gold path — maintain.
Detailed fixes: d43_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives1.0 / 10Critical✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×3) — REDACTED:40, REDACTED:86, packages/live-previews/src/components/loading.tsx:15
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels4.8 / 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 <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×4) — packages/chakra-ui/src/components/pages/auth/components/login/index.tsx:86, packages/chakra-ui/src/components/pages/auth/components/register/index.tsx:80, packages/core/src/components/pages/auth/components/login/index.tsx:62, …
A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×8) — packages/devtools-ui/src/components/add-package-drawer.tsx:203, packages/devtools-ui/src/components/json-viewer.tsx:61, packages/devtools-ui/src/components/modal.tsx:108, …
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×2) — packages/devtools-ui/src/components/add-package-drawer.tsx:239, packages/devtools-ui/src/components/filter-input.tsx:20
This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×4) — packages/devtools-ui/src/components/select.tsx:184, packages/inferencer/src/inferencers/chakra-ui/code-viewer.tsx:96, packages/inferencer/src/inferencers/headless/code-viewer.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. — packages/refine-ui/registry/new-york/refine-ui/data-table/data-table-pagination.tsx:74
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.
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — packages/core/src/components/pages/config-success/index.tsx:163
An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — packages/devtools/src/panel.tsx:132
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — packages/refine-ui/app/layout.tsx:21
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×3) — packages/devtools-ui/src/components/add-package-drawer.tsx:117, packages/devtools-ui/src/components/monitor-table.tsx:81, packages/inferencer/src/inferencers/headless/code-viewer.tsx:51
This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus. (×2) — packages/devtools-ui/src/components/sidebar.tsx:177, packages/devtools/src/components/resizable-pane.tsx:144
This <div> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it. (×2) — packages/devtools/src/components/devtools-pin.tsx:22, packages/devtools/src/components/devtools-selector.tsx:30
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
aria-hidden="true" hides the element from assistive tech but leaves it keyboard-focusable — a confusing dead stop. Remove aria-hidden or make the element non-focusable. — packages/inferencer/src/inferencers/antd/code-viewer.tsx:75
What to do
Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
Other · 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.
<svg> moves — its inline style sets `animation: top-announcement-glow 1s ease-in-out infinite alternate` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. (×2) — packages/core/src/components/gh-banner/index.tsx:205, packages/core/src/components/gh-banner/index.tsx:235
<svg> moves — its inline style sets `transition: transform 0.5s ease-in-out, opacity 0.2s ease-in-out` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — packages/core/src/components/pages/config-success/index.tsx:250
<button> takes keyboard focus, and outline:none/0 in its inline style removes the focus ring with no chance of a :focus replacement (an inline style outranks every stylesheet rule). Keep a visible focus indicator. — packages/inferencer/src/components/shared-code-viewer/index.tsx:296
<input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — packages/refine-ui/registry/new-york/ui/input.tsx:7
<textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — packages/refine-ui/registry/new-york/ui/textarea.tsx:7
`::selection` sets color: #fff on background-color: #3ecf8e — 2.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — examples/pixels/src/styles/style.css:177
`.root` 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. — examples/store/src/components/ui/Sidebar/Sidebar.module.css:2
`.actions:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — examples/store/src/components/ui/Quantity/Quantity.module.css:18
`.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. — examples/store/src/components/ui/Quantity/Quantity.module.css:26
`.modal:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — examples/store/src/components/ui/Modal/Modal.module.css:12
`.close` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — examples/store/src/components/ui/Modal/Modal.module.css:16
`.fieldset .input:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — examples/store/src/components/ui/Input/Input.module.css:10
`.root:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — examples/store/src/components/ui/Button/Button.module.css:15
`.naked` 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. — examples/store/src/components/ui/Button/Button.module.css:39
`.item` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — examples/store/src/components/common/UserNav/UserNav.module.css:10
`.item:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — examples/store/src/components/common/UserNav/UserNav.module.css:24
`.avatarButton:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — examples/store/src/components/common/UserNav/UserNav.module.css:45
`.link` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — examples/store/src/components/common/UserNav/CustomerMenuContent/CustomerMenuContent.module.css:19
`.fieldset .select:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — examples/store/src/components/common/NativeSelect/NativeSelect.module.css:14
`.options:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — examples/store/src/components/checkout/AddressSelect/AddressSelect.module.css:18
`.refine-loading__progress-bar` moves (`animation-name: loading`) 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. — packages/live-previews/src/styles/global.css:76
`.actions` moves (`transition-property: border-color, background, color, transform, box-shadow`) 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. — examples/store/src/components/ui/Quantity/Quantity.module.css:4
`.root` moves (`animation-name: slideIn`) 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. — examples/store/src/components/ui/Dropdown/Dropdown.module.css:19
`.ant-menu-tree-arrow` moves (`transition: transform 0.3s cubic-bezier(0.645, 0.045, 0.355, 1)`) 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. — examples/pixels/src/styles/style.css:34
`.ant-menu-tree-arrow::before` moves (`transition: background 0.3s cubic-bezier(0.645, 0.045, 0.355, 1),
transform 0.3s cubic-bezier(0.645, 0.045, 0.355, 1),
top 0.3s cubic-bezier(0.645, 0.045, 0.355, 1),
color 0.3s cubic-bezier(0.645, 0.045, 0.355, 1)`) 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. — examples/pixels/src/styles/style.css:44
`.wrapper` moves (`transition: transform 0.2s`) 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. — examples/blog-refine-filtering/src/components/filter/index.module.css:8
`.transition` moves (`transition-property: color, background-color, border-color, text-decoration-color, fill, stroke, opacity, box-shadow, transform, filter, backdrop-filter`) 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. — examples/blog-heroicons-example/public/styles/styles.css:665
`.transition` moves (`transition-property: color, background-color, border-color, text-decoration-color, fill, stroke, opacity, box-shadow, transform, filter, backdrop-filter, -webkit-transform, -webkit-filter, -webkit-backdrop-filter`) 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. — examples/blog-heroicons-example/public/styles/styles.css:666
`.loadingSpinner` moves (`animation: loading-spin 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — documentation/src/theme/SearchPage/styles.module.css:94
`.blog-summary-chevron` moves (`transition: transform 200ms ease-in-out`) 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. — documentation/src/refine-theme/css/blog.css:263
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add vitest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 409 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
Accessibility linting is already configured — assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Do you agree with this assessment?
C2 · Access Controls4.7 / 10Weak✓ Tool-verified
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Only 1 place(s) refuse an unauthorized caller — too few to demonstrate default-deny across handlers.
What to do
Enforce authorization at every handler — a guard on each route, or a global authentication guard/middleware with explicit public opt-outs, so protected-by-default is demonstrable.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain aggregate fused to a persistence ORM (TypeORM/Prisma/MikroORM/Sequelize/Mongoose) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.
Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.
Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
A placeholder string ("Welcome to lorem ipsum dolor.") is still in shipped code — typical of generated boilerplate that was never filled in. — packages/refine-ui/registry/new-york/refine-ui/form/sign-up-form.tsx:107
What to do
Finish or delete the functions that still throw "not implemented", and replace placeholder text before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
The guard above `return 9;` also returns `9`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — REDACTED:57
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. (×3) — REDACTED:166, packages/core/src/components/pages/config-success/index.tsx:143, packages/refine-ui/registry/new-york/refine-ui/data-table/data-table.tsx:242
`createResourceAction` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/cli/src/commands/add/sub-commands/resource/command.ts:4
`action` 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) — packages/cli/src/commands/create-resource/index.ts:25, packages/cli/src/commands/devtools/index.ts:48
`validateCorePackageIsNotDeprecated` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/cli/src/commands/devtools/index.ts:213
`addDevtoolsComponent` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/cli/src/transformers/add-devtools-component.ts:15
`fixV4Deprecations` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/codemod/src/transformations/v4/fix-v4-deprecations.ts:1144
`replacePankodImportsWithRefineDev` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/codemod/src/transformations/v4/replace-pankod-imports-with-refinedev.ts:94
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×8) — cypress/e2e/auth-keycloak/all.cy.ts:4, cypress/e2e/with-nextjs-next-auth/all.cy.ts:38, cypress/e2e/with-remix-antd/all.cy.ts:8, …
What to do
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
23 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 6 of 253 project(s) that lack one — worth up to 0 pts.
Review the README against recent changes; refresh the parts that drifted.
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 README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
packages/core/README.md links to `CODE_OF_CONDUCT.md`, but `packages/core/CODE_OF_CONDUCT.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/core/README.md:38
packages/ui-tests/README.md links to `CODE_OF_CONDUCT.md`, but `packages/ui-tests/CODE_OF_CONDUCT.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/ui-tests/README.md:39
packages/ui-types/README.md links to `CODE_OF_CONDUCT.md`, but `packages/ui-types/CODE_OF_CONDUCT.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/ui-types/README.md:39
What to do
Reconcile the README with reality: packages/core/README.md links to `CODE_OF_CONDUCT.md`, but `packages/core/CODE_OF_CONDUCT.md` does not exist; packages/ui-tests/README.md links to `CODE_OF_CONDUCT.md`, but `packages/ui-tests/CODE_OF_CONDUCT.md` does not exist; packages/ui-types/README.md links to `CODE_OF_CONDUCT.md`, but `packages/ui-types/CODE_OF_CONDUCT.md` does not exist.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
No logging call was found in the 2045 JavaScript/TypeScript production file(s) this check read across 39 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
Adopt pino (or winston) and log at meaningful points in the services you run.
Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 19909 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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 · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — packages/devtools-server/src/feed/get-feed.ts:47
What to do
Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`existsSync` in `callback to packages.map` 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. — documentation/plugins/docgen.js:140
`fs.existsSync` in `callback to packages.map` 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. — documentation/plugins/docgen.ts:108
`unlinkSync` in `callback to defaultActions.forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/cli/src/commands/add/sub-commands/resource/create-resources.ts:118
`mkdirSync` in `callback to resources.forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/cli/src/commands/add/sub-commands/resource/create-resources.ts:124
`fs.readFileSync` in `postTransform` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/codemod/src/transformations/refine1-to-refine2.ts:234, packages/codemod/src/transformations/refine2-to-refine3.ts:612
`fs.existsSync` in `makeDir` 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/create-refine-app/src/example/make-dir.ts:8
`fs.readFileSync` in `getInstalledPackageData` 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/devtools-server/src/packages/get-installed-package-data.ts:13
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 Safety10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
React / JS · Code Health — 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.
221 duplicated blocks under packages/ have copies in at least two of the sibling directories ably, airtable, antd, appwrite, chakra-ui, cli (+31 more sibling(s) not listed) — 142 of them are reported below, and 79 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 221 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 221 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 221 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/chakra-ui/refine.config.js:1
39 duplicated blocks under packages/inferencer/src/inferencers/ have copies in at least two of the sibling directories antd, chakra-ui, headless, mantine, mui — 34 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 39 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 39 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 39 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/inferencer/src/inferencers/chakra-ui/show.tsx:50
10 duplicated blocks under packages/mantine/src/components/buttons/ have copies in at least two of the sibling directories clone, create, edit, export, import, list (+2 more sibling(s) not listed) — 5 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 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/mantine/src/components/buttons/list/index.tsx:31
7 duplicated blocks under packages/mui/src/components/pages/auth/components/ have copies in at least two of the sibling directories forgotPassword, login, register, updatePassword — 6 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 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 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/src/components/pages/auth/components/forgotPassword/index.tsx:61
5 of the duplicated blocks reported below have copies in at least two of the sibling directories forgotPassword, login, register, updatePassword under packages/antd/src/components/pages/auth/components/. That concentration is one structural fact, not 5 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 5 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/antd/src/components/pages/auth/components/forgotPassword/index.tsx:54
5 duplicated blocks under packages/chakra-ui/src/components/pages/auth/components/ have copies in at least two of the sibling directories forgotPassword, login, register, updatePassword — 3 of them are reported below, and 2 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 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/chakra-ui/src/components/pages/auth/components/login/index.tsx:34
5 duplicated blocks under packages/core/src/hooks/auth/ have copies in at least two of the sibling directories useForgotPassword, useGetIdentity, useLogin, useLogout, usePermissions, useRegister (+2 more sibling(s) not listed) — 3 of them are reported below, and 2 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 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/core/src/hooks/auth/useUpdateIdentity/index.ts:45
5 duplicated blocks under packages/mui/src/components/buttons/ have copies in at least two of the sibling directories clone, create, delete, export, import, list (+3 more sibling(s) not listed) — 4 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 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/src/components/buttons/clone/index.tsx:37
packages/inferencer/src/inferencers/chakra-ui/show.tsx:50 · packages/inferencer/src/inferencers/mantine/show.tsx:51 — the two spans are one implementation copied and then locally edited — 2088 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/inferencer/src/inferencers/chakra-ui/show.tsx:50
packages/inferencer/src/inferencers/antd/show.tsx:52 · packages/inferencer/src/inferencers/mui/show.tsx:52 — the two spans are one implementation copied and then locally edited — 1990 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/inferencer/src/inferencers/antd/show.tsx:52
packages/core/src/hooks/data/useUpdate.ts:61 · packages/core/src/hooks/data/useUpdateMany.ts:62 — the two spans are one implementation copied and then locally edited — 1917 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/core/src/hooks/data/useUpdate.ts:61
packages/core/src/hooks/data/useDelete.ts:50 · packages/core/src/hooks/data/useDeleteMany.ts:50 — the two spans are one implementation copied and then locally edited — 1529 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/core/src/hooks/data/useDelete.ts:50
packages/inferencer/src/inferencers/chakra-ui/list.tsx:28 · packages/inferencer/src/inferencers/mantine/list.tsx:13 — these 2 files are line-for-line copies of one another — 257 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/inferencer/src/inferencers/chakra-ui/list.tsx:28
packages/inferencer/src/inferencers/mantine/create.tsx:47 · packages/inferencer/src/inferencers/mantine/edit.tsx:55 — the two spans are one implementation copied and then locally edited — 1081 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/inferencer/src/inferencers/mantine/create.tsx:47
packages/refine-ui/registry/new-york/refine-ui/form/sign-in-form.tsx:24 · packages/refine-ui/registry/new-york/refine-ui/form/sign-up-form.tsx:26 — the two spans are one implementation copied and then locally edited — 706 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/refine-ui/registry/new-york/refine-ui/form/sign-in-form.tsx:24
packages/core/src/hooks/data/useCreate.ts:65 · packages/core/src/hooks/data/useCreateMany.ts:47 — the two spans are one implementation copied and then locally edited — 1025 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/core/src/hooks/data/useCreate.ts:65
packages/chakra-ui/refine.config.js:1 · packages/mantine/refine.config.js:1 · packages/mui/refine.config.js:1 — these 3 files are line-for-line copies of one another — 217 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/chakra-ui/refine.config.js:1
packages/mantine/src/hooks/form/useModalForm/index.ts:61 · packages/react-hook-form/src/useModalForm/index.ts:52 — the two spans are one implementation copied and then locally edited — 864 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/mantine/src/hooks/form/useModalForm/index.ts:61
packages/inferencer/src/inferencers/headless/create.tsx:46 · packages/inferencer/src/inferencers/headless/edit.tsx:52 — the two spans are one implementation copied and then locally edited — 794 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/inferencer/src/inferencers/headless/create.tsx:46
packages/antd/src/hooks/form/useDrawerForm/useDrawerForm.ts:28 · packages/antd/src/hooks/form/useModalForm/useModalForm.ts:63 — the two spans are one implementation copied and then locally edited — 839 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/antd/src/hooks/form/useDrawerForm/useDrawerForm.ts:28
packages/core/src/hooks/data/useDelete.ts:165 · packages/core/src/hooks/data/useUpdate.ts:206 — the two spans are one implementation copied and then locally edited — 798 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/core/src/hooks/data/useDelete.ts:165
packages/core/src/hooks/data/useDeleteMany.ts:189 · packages/core/src/hooks/data/useUpdateMany.ts:234 — the two spans are one implementation copied and then locally edited — 795 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/core/src/hooks/data/useDeleteMany.ts:189
packages/chakra-ui/src/components/pages/auth/components/login/index.tsx:34 · packages/chakra-ui/src/components/pages/auth/components/register/index.tsx:31 — the two spans are one implementation copied and then locally edited — 706 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/chakra-ui/src/components/pages/auth/components/login/index.tsx:34
packages/inferencer/src/inferencers/chakra-ui/edit.tsx:52 · packages/inferencer/src/inferencers/headless/edit.tsx: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/inferencer/src/inferencers/chakra-ui/edit.tsx:52
packages/mantine/src/components/pages/auth/components/login/index.tsx:71 · packages/mantine/src/components/pages/auth/components/register/index.tsx:67 — the two spans are one implementation copied and then locally edited — 571 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/mantine/src/components/pages/auth/components/login/index.tsx:71
packages/chakra-ui/src/components/crud/edit/index.tsx:1 · packages/chakra-ui/src/components/crud/show/index.tsx:1 — these 2 files are line-for-line copies of one another — 126 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/chakra-ui/src/components/crud/edit/index.tsx:1
packages/core/src/components/pages/auth/components/login/index.tsx:13 · packages/core/src/components/pages/auth/components/register/index.tsx:15 — the two spans are one implementation copied and then locally edited — 545 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/core/src/components/pages/auth/components/login/index.tsx:13
packages/mui/src/components/crud/edit/index.tsx:71 · packages/mui/src/components/crud/show/index.tsx:64 — the two spans are one implementation copied and then locally edited — 542 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/src/components/crud/edit/index.tsx:71
packages/refine-ui/registry/new-york/ui/context-menu.tsx:110 · packages/refine-ui/registry/new-york/ui/menubar.tsx:87 — 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/refine-ui/registry/new-york/ui/context-menu.tsx:110
packages/antd/src/components/pages/auth/components/forgotPassword/index.tsx:54 · packages/antd/src/components/pages/auth/components/updatePassword/index.tsx:51 — 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/antd/src/components/pages/auth/components/forgotPassword/index.tsx:54
packages/mui/src/components/pages/auth/components/forgotPassword/index.tsx:61 · packages/mui/src/components/pages/auth/components/updatePassword/index.tsx:61 — the two spans are one implementation copied and then locally edited — 386 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/src/components/pages/auth/components/forgotPassword/index.tsx:61
packages/inferencer/src/inferencers/chakra-ui/edit.tsx:171 · packages/inferencer/src/inferencers/mui/edit.tsx:218 — the two spans are one implementation copied and then locally edited — 423 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/inferencer/src/inferencers/chakra-ui/edit.tsx:171
packages/antd/src/components/crud/edit/index.tsx:63 · packages/antd/src/components/crud/show/index.tsx:56 — the two spans are one implementation copied and then locally edited — 441 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/antd/src/components/crud/edit/index.tsx:63
packages/refine-ui/registry/new-york/ui/dropdown-menu.tsx:131 · packages/refine-ui/registry/new-york/ui/menubar.tsx:149 — 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/refine-ui/registry/new-york/ui/dropdown-menu.tsx:131
packages/inferencer/src/inferencers/antd/show.tsx:173 · packages/inferencer/src/inferencers/chakra-ui/show.tsx:185 — 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. — packages/inferencer/src/inferencers/antd/show.tsx:173
packages/core/src/hooks/data/useList.ts:104 · packages/core/src/hooks/data/useMany.ts:85 — the two spans are one implementation copied and then locally edited — 413 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/core/src/hooks/data/useList.ts:104
packages/inferencer/src/inferencers/mui/create.tsx:87 · packages/inferencer/src/inferencers/mui/edit.tsx:104 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/inferencer/src/inferencers/mui/create.tsx:87
packages/antd/src/hooks/table/useTable/useTable.ts:29 · packages/antd/src/hooks/useSimpleList/useSimpleList.ts:16 — the two spans are one implementation copied and then locally edited — 420 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/antd/src/hooks/table/useTable/useTable.ts:29
packages/chakra-ui/src/components/crud/create/index.tsx:89 · packages/chakra-ui/src/components/crud/edit/index.tsx:175 · packages/chakra-ui/src/components/crud/show/index.tsx:168 — 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. — packages/chakra-ui/src/components/crud/create/index.tsx:89
packages/graphql/src/utils/getListHelpers.ts:42 · packages/nestjs-query/src/utils/index.ts:72 — 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/graphql/src/utils/getListHelpers.ts:42
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
packages/supabase/src/index.ts:2 imports @supabase/supabase-js/dist/main/lib/types, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/supabase/src/index.ts:2
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
checkPackage has cyclomatic complexity 57 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 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/live-previews/src/utils/check-package.ts:1
Show has cyclomatic complexity 38 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mui/src/components/crud/show/index.tsx:44
(anonymous) has cyclomatic complexity 35 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/src/definitions/dataGrid/index.ts:105
createActionWithResource has cyclomatic complexity 33 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/kbar/src/hooks/useRefineKbar/index.tsx:89
Edit has cyclomatic complexity 31 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 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/src/components/crud/edit/index.tsx:47
Show has cyclomatic complexity 31 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 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/chakra-ui/src/components/crud/show/index.tsx:31
Edit has cyclomatic complexity 30 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 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/antd/src/components/crud/edit/index.tsx:36
Show has cyclomatic complexity 29 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/antd/src/components/crud/show/index.tsx:33
Show has cyclomatic complexity 29 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/mantine/src/components/crud/show/index.tsx:36
Edit 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/chakra-ui/src/components/crud/edit/index.tsx:34
renderer 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/inferencer/src/inferencers/headless/list.tsx:43
useTable has cyclomatic complexity 28 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/hooks/useTable/index.ts:182
Edit has cyclomatic complexity 28 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mantine/src/components/crud/edit/index.tsx:37
(anonymous) has cyclomatic complexity 28 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/definitions/helpers/handleRefineOptions/index.ts:44
(anonymous) has cyclomatic complexity 27 and cognitive complexity 78; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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/inferencer/src/use-relation-fetch/index.ts:47
renderer has cyclomatic complexity 27 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/inferencer/src/inferencers/mui/list.tsx:47
getCommonStyles 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/refine-ui/registry/new-york/refine-ui/data-table/data-table.tsx:261
renderer has cyclomatic complexity 25 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 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/inferencer/src/inferencers/mantine/list.tsx:54
renderer has cyclomatic complexity 24 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/inferencer/src/inferencers/chakra-ui/list.tsx:69
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
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/codemod/src/transformations/v4/fix-v4-deprecations.ts has 979 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/codemod/src/transformations/v4/fix-v4-deprecations.ts:1
packages/refine-ui/registry/new-york/refine-ui/data-table/data-table-filter.tsx has 920 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/refine-ui/registry/new-york/refine-ui/data-table/data-table-filter.tsx:1
packages/inferencer/src/inferencers/chakra-ui/list.tsx has 910 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/inferencer/src/inferencers/chakra-ui/list.tsx:1
packages/inferencer/src/inferencers/headless/list.tsx has 846 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/inferencer/src/inferencers/headless/list.tsx:1
packages/inferencer/src/inferencers/mantine/list.tsx has 821 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/inferencer/src/inferencers/mantine/list.tsx:1
packages/inferencer/src/inferencers/mui/list.tsx has 765 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/inferencer/src/inferencers/mui/list.tsx:1
packages/inferencer/src/inferencers/headless/show.tsx has 686 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/inferencer/src/inferencers/headless/show.tsx:1
packages/refine-ui/registry/new-york/ui/sidebar.tsx has 672 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/refine-ui/registry/new-york/ui/sidebar.tsx:1
packages/inferencer/src/inferencers/mui/show.tsx has 663 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/inferencer/src/inferencers/mui/show.tsx:1
packages/inferencer/src/inferencers/chakra-ui/show.tsx 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/inferencer/src/inferencers/chakra-ui/show.tsx:1
packages/inferencer/src/inferencers/mantine/show.tsx has 644 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/inferencer/src/inferencers/mantine/show.tsx:1
packages/core/src/hooks/data/useUpdateMany.ts has 640 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/core/src/hooks/data/useUpdateMany.ts:1
packages/codemod/src/transformations/refine2-to-refine3.ts 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/codemod/src/transformations/refine2-to-refine3.ts:1
packages/inferencer/src/inferencers/antd/show.tsx has 610 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/inferencer/src/inferencers/antd/show.tsx:1
packages/core/src/hooks/data/useUpdate.ts has 609 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/core/src/hooks/data/useUpdate.ts:1
packages/inferencer/src/components/shared-code-viewer/index.tsx has 566 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/inferencer/src/components/shared-code-viewer/index.tsx:1
packages/inferencer/src/inferencers/antd/list.tsx has 564 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/inferencer/src/inferencers/antd/list.tsx:1
packages/hasura/src/dataProvider/index.ts has 550 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/hasura/src/dataProvider/index.ts:1
packages/inferencer/src/inferencers/mui/edit.tsx has 487 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/inferencer/src/inferencers/mui/edit.tsx:1
packages/core/src/hooks/data/useDeleteMany.ts has 484 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/src/hooks/data/useDeleteMany.ts:1
packages/inferencer/src/inferencers/antd/edit.tsx has 482 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/inferencer/src/inferencers/antd/edit.tsx:1
packages/devtools-server/src/packages/get-available-packages.ts has 477 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/devtools-server/src/packages/get-available-packages.ts:1
packages/mui/src/components/themedLayout/sider/index.tsx has 459 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/src/components/themedLayout/sider/index.tsx:1
packages/core/src/hooks/data/useDelete.ts has 457 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/core/src/hooks/data/useDelete.ts:1
packages/inferencer/src/inferencers/mantine/edit.tsx has 444 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/inferencer/src/inferencers/mantine/edit.tsx:1
packages/core/src/components/pages/config-error/index.tsx has 440 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/src/components/pages/config-error/index.tsx:1
packages/core/src/contexts/data/types.ts has 435 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/src/contexts/data/types.ts:1
packages/inferencer/src/inferencers/headless/edit.tsx has 435 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/inferencer/src/inferencers/headless/edit.tsx:1
packages/inferencer/src/inferencers/chakra-ui/edit.tsx has 430 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/inferencer/src/inferencers/chakra-ui/edit.tsx:1
packages/devtools-ui/src/components/monitor-details.tsx has 421 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/devtools-ui/src/components/monitor-details.tsx:1
packages/devtools-ui/src/components/sidebar.tsx has 419 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/devtools-ui/src/components/sidebar.tsx:1
packages/nestjs-query/src/dataProvider/index.ts has 416 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/nestjs-query/src/dataProvider/index.ts:1
packages/devtools-ui/src/components/add-package-drawer.tsx has 408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/devtools-ui/src/components/add-package-drawer.tsx:1
packages/core/src/hooks/useTable/index.ts has 406 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/core/src/hooks/useTable/index.ts: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 Coverage6.9 / 10Adequate✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — packages/codemod/src/definitions/separated-imports/mui.ts:1, packages/codemod/src/transformations/v4/fix-v4-deprecations.ts:1, packages/refine-ui/registry/new-york/refine-ui/data-table/data-table-filter.tsx: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 REDACTED 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: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code7.7 / 10Strong✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 460 application, 140 tooling and 892 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 (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/v4/separate-imports-mui.ts) — 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/codemod/src/definitions/separated-imports/mui.ts
no import path from any entry point (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/refine3-to-refine4.ts) — 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 (×6) — packages/codemod/src/transformations/v4/fix-v4-deprecations.ts, packages/codemod/src/transformations/v4/separate-imports-antd.ts, packages/codemod/src/transformations/v4/replace-pankod-imports-with-refinedev.ts, …
no import path from any entry point (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/v4/separate-imports-chakra.ts) — 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/codemod/src/definitions/separated-imports/chakra.ts
no import path from any entry point (460 application, 140 tooling, 892 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 (×25) — packages/codemod/src/transformations/refine2-to-refine3.ts, REDACTED, packages/codemod/src/transformations/refine1-to-refine2.ts, …
no import path from any entry point (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/v4/separate-imports-mantine.ts) — 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/codemod/src/definitions/separated-imports/mantine.ts
no import path from any entry point (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/v4/separate-imports-react-table.ts) — 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/codemod/src/definitions/separated-imports/react-table.ts
no import path from any entry point (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/v4/separate-imports-antd.ts) — 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/codemod/src/definitions/separated-imports/antd.ts
no import path from any entry point (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/v4/separate-imports-react-hook-form.ts) — 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/codemod/src/definitions/separated-imports/react-hook-form.ts
no import path from any entry point (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/v4/separate-imports-react-query.ts) — 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/codemod/src/definitions/separated-imports/react-query.ts
no import path from any entry point (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/v4/separate-imports-react-router-v6.ts) — 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/codemod/src/definitions/separated-imports/react-router-v6.ts
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×15) — packages/shared/mark-as-external-plugin.ts:1, packages/antd/test/vitest.setup.ts:3, packages/antd/src/hooks/table/useTable/useTable.spec.tsx:3, …
Imported only as a TYPE and declared in no reachable REDACTED. 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 REDACTED. — packages/shared/dayjs-esm-replace-plugin.ts:1
Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
Every import is type-only — move it to devDependencies. — packages/antd/src/hooks/fields/useCheckboxGroup/index.ts:1
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.
packages/antd/src/components/crud/create/index.tsx → packages/antd/src/components/index.ts → packages/antd/src/components/crud/index.ts → packages/antd/src/components/crud/create/index.tsx (one verified cycle inside a mutually-dependent group of 17 files) — packages/antd/src/components/crud/create/index.tsx:11
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. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository. Its Node HTTP listeners were read for HTTPS enforcement alone — TLS served, a redirect to https:// or HSTS, or a TLS-terminating proxy configuration committed beside the server — each judged per server package.
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.) — packages/refine-ui/netlify.toml:1
`server.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — packages/devtools-server/src/setup-server.ts:55
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 `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document2.0 / 10Critical✓ 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.
`normalizeData` is exported and takes `data: any` from its caller, and it calls itself at line 15 (`normalizeData`) with a piece of `data` (and at line 30) — and nowhere in `normalizeData` 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 `normalizeData` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. (×2) — packages/strapi-v4/src/utils/normalizeData.ts:15, packages/rest/src/data-providers/strapi-v4/utils/normalizeData.ts:15
`deepHasKey` is exported and takes `obj: Record<string, any>` from its caller, and it calls itself at line 16 (`deepHasKey`) with a piece of `obj` — and nowhere in `deepHasKey` 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 `deepHasKey` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/inferencer/src/utilities/deep-has-key/index.ts:16
`traverseDom` is exported and takes `node: HTMLElement | null` from its caller, and it calls itself at line 152 (`traverseDom`) with a piece of `node` — and nowhere in `traverseDom` 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 `traverseDom` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/devtools/src/utilities/selector-helpers.ts:152
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether 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/18 async functions that make a cancellable request (fetch, axios, ky, ofetch) 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.
`getList` awaits `ky(…)` 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: `ky(url, { signal })`. — packages/rest/src/create-data-provider.ts:48
`getOne` awaits `ky(…)` 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: `ky(url, { signal })`. — packages/rest/src/create-data-provider.ts:72
`create` awaits `ky(…)` 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: `ky(url, { signal })`. — packages/rest/src/create-data-provider.ts:121
`update` awaits `ky(…)` 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: `ky(url, { signal })`. — packages/rest/src/create-data-provider.ts:190
`deleteOne` awaits `ky(…)` 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: `ky(url, { signal })`. — packages/rest/src/create-data-provider.ts:261
`login` awaits `axiosInstance.post(…)` 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: `axiosInstance.post(url, { signal })`. — packages/medusa/src/authProvider/index.ts:24
`logout` awaits `axiosInstance.delete(…)` 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: `axiosInstance.delete(url, { signal })`. — packages/medusa/src/authProvider/index.ts:44
`check` awaits `axiosInstance.get(…)` 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: `axiosInstance.get(url, { signal })`. — packages/medusa/src/authProvider/index.ts:64
`getIdentity` awaits `axiosInstance.get(…)` 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: `axiosInstance.get(url, { signal })`. — packages/medusa/src/authProvider/index.ts:71
`getInstalledPackages` 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/devtools-ui/src/utils/packages.ts:7
`getAvailablePackages` 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/devtools-ui/src/utils/packages.ts:19
`getLatestInfo` 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/devtools-ui/src/utils/packages.ts:27
`installPackages` 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/devtools-ui/src/utils/packages.ts:42
`fetchFeed` 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/devtools-server/src/feed/get-feed.ts:45
`getAnnouncements` 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/cli/src/utils/announcement/index.tsx:36
`telemetryHook` 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/cli/src/telemetry/index.ts:39
`createSurvey` 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 })`. — documentation/src/hooks/use-refine-cloud-survey-api.tsx:57
`updateSurvey` 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 })`. — documentation/src/hooks/use-refine-cloud-survey-api.tsx:76
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped6.1 / 10Adequate✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`item.content` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:115
`children` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/devtools/src/components/apply-styles.tsx:10
`error??""` 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. (×5) — REDACTED:19, REDACTED:28, REDACTED:33, …
`Object.entries(THEMES).map(([theme,prefix])=>`
${prefix} [data-chart=${id}] {
${colorConfig.map(([key,itemConfig])=>{…` 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:85
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`.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/react-hook-form/src/useForm/index.ts:358
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. (×12) — packages/devtools-ui/src/utils/local-storage.ts:21, packages/devtools-ui/src/components/feed.tsx:16, packages/devtools-ui/src/components/header.tsx:22, …
`.catch((e) => {})` 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/cli/src/commands/devtools/index.ts:195
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.
105/198 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
~0.1 `!` null assertions per 1k TypeScript source lines — 12 assertion(s) across the 214821 source line(s) of the 1922 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/mantine/src/providers/notificationProvider.tsx (3), packages/react-router/src/document-title-handler.tsx (2), packages/codemod/src/transformations/v5/rename-current-to-currentPage.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 9 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: this repository stores data through '@supabase/supabase-js' (packages/supabase/src/index.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
C4 Data Retention — Not assessed: this repository stores data through '@supabase/supabase-js' (packages/supabase/src/index.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
C5 Data-Subject Rights — Not assessed: this repository stores data through '@supabase/supabase-js' (packages/supabase/src/index.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 45 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
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 — docker build failed (exit 1) — ------ Dockerfile:1 -------------------- 1 | >>> FROM refinedev/node:18 AS base 2 | 3 | ENV PNPM_HOME="/pnpm" -------------------- ERROR: failed to solve: refinedev/node:18: failed to resolve source metadata for docker.io/refinedev/node:18: failed to do request: Head "https://registry-1.docker.io/v2/refinedev/node/manifests/18": Forbidden; runtime evidence skipped 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 — Not assessed: this repository stores data through '@supabase/supabase-js' (packages/supabase/src/index.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, TypeScript, html not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.js,.ts,.tsx), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
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 Aggregate boundaries — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM10 One transaction, one aggregate — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM2 Strongly-typed ids — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM4 Rich vs anemic model — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM5 Encapsulated state — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage data present for 1 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 REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
AC2 · Forms & labels· <button> with no accessible text · ×8
<button> with no accessible text packages/devtools-ui/src/components/add-package-drawer.tsx:203— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text packages/devtools-ui/src/components/json-viewer.tsx:61— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text packages/devtools-ui/src/components/modal.tsx:108— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text packages/devtools-ui/src/components/monitor-applied-filter-group.tsx:117— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text packages/devtools-ui/src/components/resizable-pane.tsx:108— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text packages/devtools-ui/src/components/select.tsx:104— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text packages/devtools-ui/src/components/select.tsx:143— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text packages/inferencer/src/components/shared-code-viewer/index.tsx:296— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
Unlisted import '@testing-library/dom' packages/antd/test/vitest.setup.ts:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@testing-library/dom' packages/chakra-ui/test/vitest.setup.ts:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@testing-library/dom' packages/mantine/test/vitest.setup.ts:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@testing-library/dom' packages/mui/test/vitest.setup.ts:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@testing-library/dom' packages/nextjs-router/src/test/vitest.setup.ts:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@testing-library/dom' packages/react-hook-form/test/vitest.setup.ts:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@testing-library/dom' packages/react-router/src/test/vitest.setup.ts:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Orphaned knowledge packages/inferencer/src/inferencers/headless/list.tsx:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/refine-ui/registry/new-york/refine-ui/data-table/data-table-filter.tsx:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/inferencer/src/inferencers/mantine/list.tsx:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/inferencer/src/inferencers/mui/list.tsx:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/refine-ui/registry/new-york/ui/sidebar.tsx:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Import cycle (3 files) packages/mantine/src/components/crud/create/index.tsx:19— packages/mantine/src/components/crud/create/index.tsx → packages/mantine/src/components/index.ts → packages/mantine/src/components/crud/index.ts → packages/mantine/src/components/crud/create/index.tsx (one verified cycle inside a mutually-dependent group of 17 files)
Import cycle (3 files) packages/mui/src/components/crud/create/index.tsx:23— packages/mui/src/components/crud/create/index.tsx → packages/mui/src/components/index.tsx → packages/mui/src/components/crud/index.tsx → packages/mui/src/components/crud/create/index.tsx (one verified cycle inside a mutually-dependent group of 17 files)
AC2 · Forms & labels· <label> that labels no control · ×4
<label> that labels no control packages/chakra-ui/src/components/pages/auth/components/login/index.tsx:86— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/chakra-ui/src/components/pages/auth/components/register/index.tsx:80— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/core/src/components/pages/auth/components/login/index.tsx:62— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/core/src/components/pages/auth/components/register/index.tsx:63— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC1 · Text alternatives· <img> without a text alternative · ×3
<img> without a text alternative REDACTED:40— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative REDACTED:86— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative packages/live-previews/src/components/loading.tsx:15— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC2 · Forms & labels· <textarea> without a programmatic label · ×3
<textarea> without a programmatic label packages/inferencer/src/inferencers/chakra-ui/code-viewer.tsx:96— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<textarea> without a programmatic label packages/inferencer/src/inferencers/headless/code-viewer.tsx:221— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<textarea> without a programmatic label packages/inferencer/src/inferencers/mantine/code-viewer.tsx:96— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
D30 · Dependency Vulnerabilities· High vulnerability · ×3
REDACTED
REDACTED
REDACTED
AC2 · Forms & labels· <input> without a programmatic label · ×2
<input> without a programmatic label packages/devtools-ui/src/components/add-package-drawer.tsx:239— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label packages/devtools-ui/src/components/filter-input.tsx:20— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×2
Click handler on a non-interactive <div> packages/devtools-ui/src/components/add-package-drawer.tsx:117— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> packages/inferencer/src/inferencers/headless/code-viewer.tsx:51— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC4 · Keyboard semantics· Hover-only interaction on <div> · ×2
Hover-only interaction on <div> packages/devtools-ui/src/components/sidebar.tsx:177— This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
Hover-only interaction on <div> packages/devtools/src/components/resizable-pane.tsx:144— This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
AC4 · Keyboard semantics· Clickable role="button" that no keyboard user can reach · ×2
Clickable role="button" that no keyboard user can reach packages/devtools/src/components/devtools-pin.tsx:22— This <div> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it.
Clickable role="button" that no keyboard user can reach packages/devtools/src/components/devtools-selector.tsx:30— This <div> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabIndex={0} in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabIndex={0}="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it.
Unlisted import '@testing-library/react' packages/nextjs-router/src/test/index.tsx:95— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@testing-library/react' packages/react-router/src/navigate-to-resource.test.tsx:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Import cycle (2 files) packages/kbar/src/components/commandBar/index.tsx:4— packages/kbar/src/components/commandBar/index.tsx → packages/kbar/src/components/index.ts → packages/kbar/src/components/commandBar/index.tsx (one verified cycle inside a mutually-dependent group of 5 files)
AC2 · Forms & labels· <select> without a programmatic label · ×1
<select> without a programmatic label packages/devtools-ui/src/components/select.tsx:184— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC3 · Page structure· <iframe> without a title · ×1
<iframe> without a title packages/devtools/src/panel.tsx:132— An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label.
AC4 · Keyboard semantics· Click handler on a non-interactive <tr> · ×1
Click handler on a non-interactive <tr> packages/devtools-ui/src/components/monitor-table.tsx:81— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC5 · ARIA correctness· aria-hidden on a focusable element · ×1
aria-hidden on a focusable element packages/inferencer/src/inferencers/antd/code-viewer.tsx:75— aria-hidden="true" hides the element from assistive tech but leaves it keyboard-focusable — a confusing dead stop. Remove aria-hidden or make the element non-focusable.
Banned license: web3 examples/with-web3/REDACTED:36— `web3` 1.10.4 is published on registry.npmjs.org under `LGPL-3.0`, which this policy bans, and it is a PRODUCTION dependency this repository's committed lockfile resolves — 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 record an accepted exception.
Unlisted import '@esbuild-plugins/node-resolve' packages/shared/mark-as-external-plugin.ts:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'lodash' packages/antd/src/hooks/table/useTable/useTable.spec.tsx:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'cross-spawn' packages/codemod/src/helpers/install.ts:4— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'react-router' packages/nextjs-router/src/test/index.tsx:2— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@testing-library/jest-dom' packages/react-router/src/test/vitest.setup.ts:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'dayjs' packages/ui-tests/src/tests/fields/date.tsx:2— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
FunctionTooLong: landing-hero-mobile.LandingHeroMobileAnimation documentation/src/refine-theme/icons/landing-hero-mobile.tsx:4— FunctionTooLong — LandingHeroMobileAnimation runs 4680 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4580 over it, 46.80× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: tutorial.SvgTutorial documentation/src/assets/popover-icons/tutorial.tsx:4— FunctionTooLong — SvgTutorial runs 835 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 735 over it, 8.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: landing-app-crm.LandingAppCrmSvg documentation/src/refine-theme/icons/landing-app-crm.tsx:3— FunctionTooLong — LandingAppCrmSvg runs 813 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 713 over it, 8.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: landing-tile-honeycomb.LandingTileHoneycombIcon documentation/src/refine-theme/icons/landing-tile-honeycomb.tsx:3— FunctionTooLong — LandingTileHoneycombIcon runs 708 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 608 over it, 7.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: landing-tile-list.LandingTileListIcon documentation/src/refine-theme/icons/landing-tile-list.tsx:3— FunctionTooLong — LandingTileListIcon runs 620 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 520 over it, 6.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: landing-tile-sides.LandingTileSidesIcon documentation/src/refine-theme/icons/landing-tile-sides.tsx:3— FunctionTooLong — LandingTileSidesIcon runs 541 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 441 over it, 5.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: landing-playground.LandingPlayground documentation/src/refine-theme/landing-playground.tsx:8— FunctionTooLong — LandingPlayground runs 371 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 271 over it, 3.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: landing-magic.LandingMagic documentation/src/refine-theme/landing-magic.tsx:103— FunctionTooLong — LandingMagic runs 370 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 270 over it, 3.70× 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: index.ThemedSider packages/mui/src/components/themedLayout/sider/index.tsx:37— FunctionTooLong — ThemedSider runs 365 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 265 over it, 3.65× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: monitor-details.MonitorDetails packages/devtools-ui/src/components/monitor-details.tsx:21— FunctionTooLong — MonitorDetails runs 361 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 261 over it, 3.61× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: add-package-drawer.AddPackageDrawer packages/devtools-ui/src/components/add-package-drawer.tsx:25— FunctionTooLong — AddPackageDrawer runs 352 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 252 over it, 3.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: index.SearchPageContent documentation/src/theme/SearchPage/index.js:113— FunctionTooLong — SearchPageContent runs 305 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 205 over it, 3.05× 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: landing-footer.LandingFooter documentation/src/refine-theme/landing-footer.tsx:14— FunctionTooLong — LandingFooter runs 291 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 191 over it, 2.91× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.SandpackBase documentation/src/components/sandpack/index.tsx:70— FunctionTooLong — SandpackBase runs 279 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 179 over it, 2.79× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: blog-plugin.blogPluginExtended documentation/plugins/blog-plugin.js:641— FunctionTooLong — blogPluginExtended runs 276 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 176 over it, 2.76× 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-plugin.blogPluginExtended.contentLoaded documentation/plugins/blog-plugin.js:652— FunctionTooLong — blogPluginExtended.contentLoaded runs 262 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 162 over it, 2.62× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.ThemedSider packages/chakra-ui/src/components/themedLayout/sider/index.tsx:34— FunctionTooLong — ThemedSider runs 255 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 155 over it, 2.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.CodeModal packages/inferencer/src/components/shared-code-viewer/index.tsx:229— FunctionTooLong — CodeModal runs 255 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 155 over it, 2.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.createInferencer packages/inferencer/src/create-inferencer/index.tsx:40— FunctionTooLong — createInferencer 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: index.LoginPage packages/mui/src/components/pages/auth/components/login/index.tsx:44— FunctionTooLong — LoginPage runs 244 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 144 over it, 2.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: package-item.PackageItem packages/devtools-ui/src/components/package-item.tsx:21— FunctionTooLong — PackageItem runs 231 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 131 over it, 2.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: landing-sweet-spot.LandingSweetSpot documentation/src/refine-theme/landing-sweet-spot.tsx:18— FunctionTooLong — LandingSweetSpot runs 226 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 126 over it, 2.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: index.ThemedSider packages/antd/src/components/themedLayout/sider/index.tsx:34— FunctionTooLong — ThemedSider runs 225 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 125 over it, 2.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: fix-v4-deprecations.fixDeprecatedUseTableProps packages/codemod/src/transformations/v4/fix-v4-deprecations.ts:436— FunctionTooLong — fixDeprecatedUseTableProps runs 222 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 122 over it, 2.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.ErrorGradient packages/core/src/components/pages/config-error/index.tsx:201— FunctionTooLong — ErrorGradient runs 219 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 119 over it, 2.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
No assertions: should render success packages/ui-tests/src/tests/autoSaveIndicator.tsx:9— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render error packages/ui-tests/src/tests/autoSaveIndicator.tsx:17— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render idle packages/ui-tests/src/tests/autoSaveIndicator.tsx: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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render loading packages/ui-tests/src/tests/autoSaveIndicator.tsx:35— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: renders date with default format packages/ui-tests/src/tests/fields/date.tsx:14— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: renders date with given format packages/ui-tests/src/tests/fields/date.tsx:22— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: renders date with given LocalizedFormat packages/ui-tests/src/tests/fields/date.tsx:30— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: renders invalid date with given incorrect date packages/ui-tests/src/tests/fields/date.tsx:58— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: renders numbers with given formatting packages/ui-tests/src/tests/fields/number.tsx:10— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render NaN when value is undefined packages/ui-tests/src/tests/fields/number.tsx:32— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render NaN when value is string packages/ui-tests/src/tests/fields/number.tsx:38— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: renders boolean values correctly packages/ui-tests/src/tests/fields/tag.tsx:10— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: renders text correctly packages/ui-tests/src/tests/fields/text.tsx:10— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render children packages/ui-tests/src/tests/crud/create.tsx:71— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render default title successfuly packages/ui-tests/src/tests/crud/create.tsx:92— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render with label instead of resource name successfully packages/ui-tests/src/tests/crud/create.tsx:105— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render optional title with title prop packages/ui-tests/src/tests/crud/create.tsx:135— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render optional resource with resource prop packages/ui-tests/src/tests/crud/create.tsx:141— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render children packages/ui-tests/src/tests/crud/edit.tsx:63— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render optional buttons with actionButtons prop packages/ui-tests/src/tests/crud/edit.tsx:125— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render default title successfuly packages/ui-tests/src/tests/crud/edit.tsx:141— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render custom title successfuly packages/ui-tests/src/tests/crud/edit.tsx:154— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render optional recordItemId with resource prop packages/ui-tests/src/tests/crud/edit.tsx:160— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render children packages/ui-tests/src/tests/crud/list.tsx:48— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should render optional title with title prop packages/ui-tests/src/tests/crud/list.tsx:58— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
+ 88 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×57
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 32 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file packages/codemod/src/definitions/separated-imports/mui.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/codemod/src/transformations/v4/fix-v4-deprecations.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/refine-ui/registry/new-york/refine-ui/data-table/data-table-filter.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/refine-ui/registry/new-york/ui/sidebar.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/codemod/src/transformations/refine2-to-refine3.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/devtools-ui/src/components/sidebar.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/devtools-ui/src/components/add-package-drawer.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/devtools-ui/src/components/monitor-details.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/refine-ui/registry/new-york/refine-ui/layout/layout-01/sidebar.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/refine-ui/examples/base-example/routes/posts/list.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/devtools-ui/src/components/monitor-filters.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/refine-ui/registry/new-york/refine-ui/data-table/data-table.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/devtools-ui/src/pages/monitor.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/codemod/src/transformations/refine1-to-refine2.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/devtools-ui/src/components/package-item.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/devtools/src/components/resizable-pane.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/inferencer/src/inferencers/headless/code-viewer.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/refine-ui/registry/new-york/ui/menubar.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/codemod/src/index.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/devtools/src/components/selectable-elements.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/refine-ui/registry/new-york/ui/dropdown-menu.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/refine-ui/registry/new-york/ui/context-menu.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/refine-ui/examples/base-example/routes/posts/edit.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/refine-ui/registry/new-york/refine-ui/form/sign-up-form.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.
FileTooLong: icons/landing-hero-mobile.tsx documentation/src/refine-theme/icons/landing-hero-mobile.tsx— FileTooLong — 4682 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 4182 over it, 9.36× 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: popover-icons/tutorial.tsx documentation/src/assets/popover-icons/tutorial.tsx— FileTooLong — 838 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 338 over it, 1.68× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: icons/landing-app-crm.tsx documentation/src/refine-theme/icons/landing-app-crm.tsx— FileTooLong — 814 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: LandingAppCrmSvg (3-813). The bar is 500 significant lines; this is 314 over it, 1.63× 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: data-table/data-table-filter.tsx packages/refine-ui/registry/new-york/refine-ui/data-table/data-table-filter.tsx— FileTooLong — 778 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 278 over it, 1.56× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: refine-theme/tutorial-sandpack.tsx documentation/src/refine-theme/tutorial-sandpack.tsx— FileTooLong — 752 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 252 over it, 1.50× 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: chakra-ui/list.tsx packages/inferencer/src/inferencers/chakra-ui/list.tsx— FileTooLong — 738 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: renderer (69-953). The bar is 500 significant lines; this is 238 over it, 1.48× 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: plugins/blog-plugin.js documentation/plugins/blog-plugin.js— FileTooLong — 711 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 211 over it, 1.42× 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: icons/landing-tile-honeycomb.tsx documentation/src/refine-theme/icons/landing-tile-honeycomb.tsx— FileTooLong — 709 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 209 over it, 1.42× 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: v4/fix-v4-deprecations.ts packages/codemod/src/transformations/v4/fix-v4-deprecations.ts— FileTooLong — 706 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 206 over it, 1.41× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: headless/list.tsx packages/inferencer/src/inferencers/headless/list.tsx— FileTooLong — 693 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 193 over it, 1.39× 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: mantine/list.tsx packages/inferencer/src/inferencers/mantine/list.tsx— FileTooLong — 657 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: renderer (54-876). The bar is 500 significant lines; this is 157 over it, 1.31× 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: icons/landing-tile-list.tsx documentation/src/refine-theme/icons/landing-tile-list.tsx— FileTooLong — 621 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 121 over it, 1.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: mui/list.tsx packages/inferencer/src/inferencers/mui/list.tsx— FileTooLong — 618 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: renderer (47-841). The bar is 500 significant lines; this is 118 over it, 1.24× 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: headless/show.tsx packages/inferencer/src/inferencers/headless/show.tsx— FileTooLong — 591 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 91 over it, 1.18× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: refine-theme/landing-hero-showcase-section.tsx documentation/src/refine-theme/landing-hero-showcase-section.tsx— FileTooLong — 571 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 71 over it, 1.14× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ui/sidebar.tsx packages/refine-ui/registry/new-york/ui/sidebar.tsx— FileTooLong — 561 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 61 over it, 1.12× 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: mui/show.tsx packages/inferencer/src/inferencers/mui/show.tsx— FileTooLong — 552 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: renderer (45-699). The bar is 500 significant lines; this is 52 over it, 1.10× 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: mantine/show.tsx packages/inferencer/src/inferencers/mantine/show.tsx— FileTooLong — 544 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: renderer (44-677). The bar is 500 significant lines; this is 44 over it, 1.09× 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: icons/landing-tile-sides.tsx documentation/src/refine-theme/icons/landing-tile-sides.tsx— FileTooLong — 542 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 42 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: chakra-ui/show.tsx packages/inferencer/src/inferencers/chakra-ui/show.tsx— FileTooLong — 534 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 34 over it, 1.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: blog-post-page/index.js documentation/src/components/blog/blog-post-page/index.js— FileTooLong — 519 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 19 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: antd/show.tsx packages/inferencer/src/inferencers/antd/show.tsx— FileTooLong — 514 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: renderer (45-619). The bar is 500 significant lines; this is 14 over it, 1.03× 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 — 508 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 8 over it, 1.02× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
X2 · Cancellation propagation· Async function without AbortSignal · ×18
Async function without AbortSignal: getList packages/rest/src/create-data-provider.ts:48— `getList` awaits `ky(…)` 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: `ky(url, { signal })`.
Async function without AbortSignal: getOne packages/rest/src/create-data-provider.ts:72— `getOne` awaits `ky(…)` 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: `ky(url, { signal })`.
Async function without AbortSignal: create packages/rest/src/create-data-provider.ts:121— `create` awaits `ky(…)` 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: `ky(url, { signal })`.
Async function without AbortSignal: update packages/rest/src/create-data-provider.ts:190— `update` awaits `ky(…)` 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: `ky(url, { signal })`.
Async function without AbortSignal: deleteOne packages/rest/src/create-data-provider.ts:261— `deleteOne` awaits `ky(…)` 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: `ky(url, { signal })`.
Async function without AbortSignal: login packages/medusa/src/authProvider/index.ts:24— `login` awaits `axiosInstance.post(…)` 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: `axiosInstance.post(url, { signal })`.
Async function without AbortSignal: logout packages/medusa/src/authProvider/index.ts:44— `logout` awaits `axiosInstance.delete(…)` 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: `axiosInstance.delete(url, { signal })`.
Async function without AbortSignal: check packages/medusa/src/authProvider/index.ts:64— `check` awaits `axiosInstance.get(…)` 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: `axiosInstance.get(url, { signal })`.
Async function without AbortSignal: getIdentity packages/medusa/src/authProvider/index.ts:71— `getIdentity` awaits `axiosInstance.get(…)` 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: `axiosInstance.get(url, { signal })`.
Async function without AbortSignal: getInstalledPackages packages/devtools-ui/src/utils/packages.ts:7— `getInstalledPackages` 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: getAvailablePackages packages/devtools-ui/src/utils/packages.ts:19— `getAvailablePackages` 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: getLatestInfo packages/devtools-ui/src/utils/packages.ts:27— `getLatestInfo` 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: installPackages packages/devtools-ui/src/utils/packages.ts:42— `installPackages` 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: fetchFeed packages/devtools-server/src/feed/get-feed.ts:45— `fetchFeed` 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: getAnnouncements packages/cli/src/utils/announcement/index.tsx:36— `getAnnouncements` 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: telemetryHook packages/cli/src/telemetry/index.ts:39— `telemetryHook` 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: createSurvey documentation/src/hooks/use-refine-cloud-survey-api.tsx:57— `createSurvey` 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: updateSurvey documentation/src/hooks/use-refine-cloud-survey-api.tsx:76— `updateSurvey` 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 })`.
Deprecated: @lerna/filter-options REDACTED:65— @lerna/filter-options 6.4.1, declared in REDACTED, is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: glob REDACTED:72— glob 10.4.2, declared in REDACTED, is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: rimraf REDACTED:84— rimraf 3.0.2, declared in REDACTED, is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: marked-terminal packages/cli/REDACTED:61— marked-terminal 6.3.0, declared in packages/cli/REDACTED, is marked deprecated by its publisher: "should have been major release. Use 7.0.0". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: rimraf packages/create-refine-app/REDACTED:28— rimraf 3.0.2, declared in packages/create-refine-app/REDACTED, is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: tar packages/create-refine-app/REDACTED:30— tar 6.2.1, declared in packages/create-refine-app/REDACTED, is marked deprecated by its publisher: "Old versions of tar are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @refinedev/strapi-graphql packages/live-previews/REDACTED:46— @refinedev/strapi-graphql 6.0.5, declared in packages/live-previews/REDACTED, is marked deprecated by its publisher: "Package no longer supported. List of supported data providers: https://refine.dev/docs/guides-concepts/data-fetching/#supported-data-providers". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: i18next-xhr-backend packages/live-previews/REDACTED:61— i18next-xhr-backend 3.2.2, declared in packages/live-previews/REDACTED, is marked deprecated by its publisher: "replaced by i18next-http-backend". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: next packages/live-previews/REDACTED:64— next 14.2.26, declared in packages/live-previews/REDACTED, is marked deprecated by its publisher: "This version has a security vulnerability. Please upgrade to a patched version. See https://nextjs.org/blog/security-update-2025-12-11 for more details.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: uuid packages/live-previews/REDACTED:72— uuid 9.0.1, declared in packages/live-previews/REDACTED, is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: rimraf packages/live-previews/REDACTED:86— rimraf 3.0.2, declared in packages/live-previews/REDACTED, is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: next packages/nextjs-router/REDACTED:101— next 14.2.26, declared in packages/nextjs-router/REDACTED, is marked deprecated by its publisher: "This version has a security vulnerability. Please upgrade to a patched version. See https://nextjs.org/blog/security-update-2025-12-11 for more details.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: next REDACTED:55— next 15.3.1, declared in REDACTED, is marked deprecated by its publisher: "This version has a security vulnerability. Please upgrade to a patched version. See https://nextjs.org/blog/[CVE redacted] for more details.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: recharts REDACTED:64— recharts 2.15.4, declared in REDACTED, is marked deprecated by its publisher: "1.x and 2.x branches are no longer active. Bump to Recharts v3 to receive latest features and bugfixes. See https://github.com/recharts/recharts/wiki/3.0-migration-guide". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint REDACTED:79— eslint 9.35.0, declared in REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×14
Focus outline removed in CSS without a :focus replacement examples/store/src/components/ui/Sidebar/Sidebar.module.css:2— `.root` 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 examples/store/src/components/ui/Quantity/Quantity.module.css:18— `.actions:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement examples/store/src/components/ui/Quantity/Quantity.module.css:26— `.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 examples/store/src/components/ui/Modal/Modal.module.css:12— `.modal:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement examples/store/src/components/ui/Modal/Modal.module.css:16— `.close` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement examples/store/src/components/ui/Input/Input.module.css:10— `.fieldset .input:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement examples/store/src/components/ui/Button/Button.module.css:15— `.root:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement examples/store/src/components/ui/Button/Button.module.css:39— `.naked` 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 examples/store/src/components/common/UserNav/UserNav.module.css:10— `.item` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement examples/store/src/components/common/UserNav/UserNav.module.css:24— `.item:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement examples/store/src/components/common/UserNav/UserNav.module.css:45— `.avatarButton:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement examples/store/src/components/common/UserNav/CustomerMenuContent/CustomerMenuContent.module.css:19— `.link` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement examples/store/src/components/common/NativeSelect/NativeSelect.module.css:14— `.fieldset .select:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement examples/store/src/components/checkout/AddressSelect/AddressSelect.module.css:18— `.options:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Swallowed exception (empty catch) packages/react-hook-form/src/useForm/index.ts:358— `.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/devtools-ui/src/utils/local-storage.ts:21— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/devtools-ui/src/components/feed.tsx:16— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/devtools-ui/src/components/header.tsx:22— 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/devtools-server/src/packages/get-installed-package-json-path.ts:22— 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/create-refine-app/src/index.ts:92— 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/codemod/src/helpers/temp-codemod-config.ts:32— 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/codemod/src/helpers/temp-codemod-config.ts:43— 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/codemod/src/helpers/temp-codemod-config.ts:73— 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/cli/src/utils/project/index.ts:15— 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/cli/src/telemetry/index.ts:50— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/cli/src/commands/runner/projectScripts.ts:29— 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/cli/src/commands/devtools/index.ts:195— `.catch((e) => {})` 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/cli/src/commands/add/sub-commands/provider/create-providers.ts:78— 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.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×13
Animation without a prefers-reduced-motion guard packages/core/src/components/gh-banner/index.tsx:205— <svg> moves — its inline style sets `animation: top-announcement-glow 1s ease-in-out infinite alternate` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard packages/core/src/components/gh-banner/index.tsx:235— <svg> moves — its inline style sets `animation: top-announcement-glow 1s ease-in-out infinite alternate` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard packages/core/src/components/pages/config-success/index.tsx:250— <svg> moves — its inline style sets `transition: transform 0.5s ease-in-out, opacity 0.2s ease-in-out` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard packages/live-previews/src/styles/global.css:76— `.refine-loading__progress-bar` moves (`animation-name: loading`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard examples/store/src/components/ui/Quantity/Quantity.module.css:4— `.actions` moves (`transition-property: border-color, background, color, transform, box-shadow`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard examples/store/src/components/ui/Dropdown/Dropdown.module.css:19— `.root` moves (`animation-name: slideIn`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard examples/pixels/src/styles/style.css:34— `.ant-menu-tree-arrow` moves (`transition: transform 0.3s cubic-bezier(0.645, 0.045, 0.355, 1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard examples/pixels/src/styles/style.css:44— `.ant-menu-tree-arrow::before` moves (`transition: background 0.3s cubic-bezier(0.645, 0.045, 0.355, 1),
transform 0.3s cubic-bezier(0.645, 0.045, 0.355, 1),
top 0.3s cubic-bezier(0.645, 0.045, 0.355, 1),
color 0.3s cubic-bezier(0.645, 0.045, 0.355, 1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard examples/blog-refine-filtering/src/components/filter/index.module.css:8— `.wrapper` moves (`transition: transform 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard examples/blog-heroicons-example/public/styles/styles.css:665— `.transition` moves (`transition-property: color, background-color, border-color, text-decoration-color, fill, stroke, opacity, box-shadow, transform, filter, backdrop-filter`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard examples/blog-heroicons-example/public/styles/styles.css:666— `.transition` moves (`transition-property: color, background-color, border-color, text-decoration-color, fill, stroke, opacity, box-shadow, transform, filter, backdrop-filter, -webkit-transform, -webkit-filter, -webkit-backdrop-filter`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard documentation/src/theme/SearchPage/styles.module.css:94— `.loadingSpinner` moves (`animation: loading-spin 1s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard documentation/src/refine-theme/css/blog.css:263— `.blog-summary-chevron` moves (`transition: transform 200ms ease-in-out`) 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.
TodoComment packages/rest/src/create-data-provider.ts:193— // TODO: Validate method name. — 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/codemod/src/transformations/v5/rename-useResource-useResourceParams.test.ts:45— // TODO: Complete migration from useResource to useResourceParams — 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/antd/src/hooks/table/useTable/useTable.spec.tsx:195— // TODO: update tests — 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:72— // TODO: Check credentials on your api — 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:39— // TODO: Request your API to check credentials — 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:61— // TODO: Request your API to create new user — 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 examples/store/src/lib/context/cart.tsx:135— //TODO: make sure to update the cart in the store with the new region — 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 examples/store/src/lib/context/cart.tsx:275— // TODO: make sure to update the cart in the store with the new line item — 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 examples/store/src/lib/context/checkout.tsx:77— //TODO: Is customer data ok? — 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 examples/store/src/components/address/EditAddress/EditAddress.tsx:143— // TODO: removed function here — 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 examples/auth-google-login/src/pages/login.tsx:7— // Todo: Update your Google Client ID here — 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 documentation/src/refine-theme/doc-generated-index-page.tsx:21— // TODO `require` this? — 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.
D12 · Dependency Hygiene· One package at two majors across the workspace · ×8
One package at two majors across the workspace: clsx — `clsx` is maintained at 2 different major versions inside this one repository — major 1 in documentation/REDACTED, packages/devtools-ui/REDACTED; major 2 in REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: framer-motion — `framer-motion` is maintained at 2 different major versions inside this one repository — major 6 in documentation/REDACTED; major 7 in packages/chakra-ui/REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: next — `next` is maintained at 2 different major versions inside this one repository — major 14 in packages/live-previews/REDACTED; major 15 in REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: react — `react` is maintained at 2 different major versions inside this one repository — major 17 in documentation/REDACTED; major 19 in packages/devtools-server/REDACTED, packages/live-previews/REDACTED, REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: react-dom — `react-dom` is maintained at 2 different major versions inside this one repository — major 17 in documentation/REDACTED; major 19 in packages/devtools-server/REDACTED, packages/live-previews/REDACTED, REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: react-markdown — `react-markdown` is maintained at 2 different major versions inside this one repository — major 6 in packages/antd/REDACTED, packages/chakra-ui/REDACTED, packages/inferencer/REDACTED (+2 more); major 8 in documentation/REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: remark-gfm — `remark-gfm` is maintained at 2 different major versions inside this one repository — major 1 in packages/antd/REDACTED, packages/chakra-ui/REDACTED, packages/inferencer/REDACTED (+2 more); major 3 in documentation/REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: tailwind-merge — `tailwind-merge` is maintained at 2 different major versions inside this one repository — major 2 in documentation/REDACTED; major 3 in REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
Sync-over-async blocking documentation/plugins/docgen.js:140— `existsSync` in `callback to packages.map` 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 documentation/plugins/docgen.ts:108— `fs.existsSync` in `callback to packages.map` 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/cli/src/commands/add/sub-commands/resource/create-resources.ts:118— `unlinkSync` in `callback to defaultActions.forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/cli/src/commands/add/sub-commands/resource/create-resources.ts:124— `mkdirSync` in `callback to resources.forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/codemod/src/transformations/refine1-to-refine2.ts:234— `fs.readFileSync` in `postTransform` 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/codemod/src/transformations/refine2-to-refine3.ts:612— `fs.readFileSync` in `postTransform` 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/create-refine-app/src/example/make-dir.ts:8— `fs.existsSync` in `makeDir` 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/devtools-server/src/packages/get-installed-package-data.ts:13— `fs.readFileSync` in `getInstalledPackageData` 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.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×8
Untrusted text written into markup unescaped REDACTED:115— `item.content` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/devtools/src/components/apply-styles.tsx:10— `children` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:19— `error??""` 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:28— `error??""` 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:33— `error??""` 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:16— `error??""` 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:25— `error??""` 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:85— `Object.entries(THEMES).map(([theme,prefix])=>`
${prefix} [data-chart=${id}] {
${colorConfig.map(([key,itemConfig])=>{…` 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.
Fake-async — async method never awaits packages/cli/src/commands/add/sub-commands/resource/command.ts:4— `createResourceAction` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/cli/src/commands/create-resource/index.ts:25— `action` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/cli/src/commands/devtools/index.ts:48— `action` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/cli/src/commands/devtools/index.ts:213— `validateCorePackageIsNotDeprecated` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/cli/src/transformers/add-devtools-component.ts:15— `addDevtoolsComponent` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/codemod/src/transformations/v4/fix-v4-deprecations.ts:1144— `fixV4Deprecations` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/codemod/src/transformations/v4/replace-pankod-imports-with-refinedev.ts:94— `replacePankodImportsWithRefineDev` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
list.renderer::renderRelationFields (cognitive 31) packages/inferencer/src/inferencers/antd/list.tsx:127— list.renderer::renderRelationFields has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (23 pts), ternaries 2 (5 pts), boolean chains 3 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: one other method here (list.renderer) 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.
list.renderer::renderRelationFields (cognitive 27) packages/inferencer/src/inferencers/mui/list.tsx:140— list.renderer::renderRelationFields has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: 2 other methods here (list.renderer, list.renderer::basicFields) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
list.renderer::renderRelationFields (cognitive 23) packages/inferencer/src/inferencers/chakra-ui/list.tsx:170— list.renderer::renderRelationFields has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 3 (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: one other method here (list.renderer) 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.
list.renderer::renderRelationFields (cognitive 23) packages/inferencer/src/inferencers/headless/list.tsx:131— list.renderer::renderRelationFields has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 3 (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: one other method here (list.renderer) 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.
list.renderer::renderRelationFields (cognitive 23) packages/inferencer/src/inferencers/mantine/list.tsx:148— list.renderer::renderRelationFields has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 3 (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: one other method here (list.renderer) 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.
list.renderer::basicFields (cognitive 17) packages/inferencer/src/inferencers/mui/list.tsx:651— list.renderer::basicFields has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 3 (5 pts), boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (list.renderer, list.renderer::renderRelationFields) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Change coupling: REDACTED ↔ REDACTED packages/antd/src/hooks/fields/useCheckboxGroup/index.ts:1— `packages/antd/src/hooks/fields/useCheckboxGroup/index.ts` and `packages/antd/src/hooks/fields/useRadioGroup/index.ts` change together 91% of the time (10 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — 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 10 shared commits counted here, the most recent 3 are `853bef97` feat(core): add `selectedOptionsOrder` in `useSelect` (#6071); `2b8d658a` fix(use-select): correct types on `useSelect` options (#5199); `fa915d52` feat(docs): add <PropsTable> to antd hooks (#2750) — run `git show` on any of them.
Change coupling: useUpdate.ts ↔ useUpdateMany.ts packages/core/src/hooks/data/useUpdate.ts:1— `packages/core/src/hooks/data/useUpdate.ts` and `packages/core/src/hooks/data/useUpdateMany.ts` change together 73% of the time (11 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — 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 `5a3e404d` fix: preserve row id in meta (#6925); `91a4d0da` feat(core): add `optimisticUpdateMap` prop on `useUpdate`, `useUpdate…; `3af99896` docs: add more information about `onCancel` property (#4659) — run `git show` on any of them.
Change coupling: useDrawerForm.ts ↔ useModalForm.ts packages/antd/src/hooks/form/useDrawerForm/useDrawerForm.ts:1— `packages/antd/src/hooks/form/useDrawerForm/useDrawerForm.ts` and `packages/antd/src/hooks/form/useModalForm/useModalForm.ts` change together 71% of the time (17 of the 24 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — 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 17 shared commits counted here, the most recent 3 are `e327cadc` feat(core): add `invalidateOnUnmount` and `invalidateOnClose` prop on…; `c9cc4398` fix(antd): `useModalForm` and `useDrawerForm` sends request twice wh…; `e6eb4dea` feat: `syncWithLocation.syncId` default to `true` for `useDrawerForm`… — run `git show` on any of them.
Change coupling: REDACTED ↔ REDACTED packages/antd/src/components/buttons/delete/index.tsx:1— `packages/antd/src/components/buttons/delete/index.tsx` and `packages/antd/src/components/buttons/refresh/index.tsx` change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — 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 8 shared commits counted here, the most recent 3 are `17348b34` fix(antd): remove deprecated api; `1076a45d` useResource hook refactor (#1696); `596d5901` handle custom routes on CRUD componenets and buttons (#1647) — run `git show` on any of them.
Change coupling: REDACTED ↔ REDACTED packages/core/src/hooks/auth/useLogin/index.ts:1— `packages/core/src/hooks/auth/useLogin/index.ts` and `packages/core/src/hooks/auth/useLogout/index.ts` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — 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 `71148278` feat(core): add success notification support for auth provider method…; `db12d600` fix(core): logical issues in `<Authenticated>` (#3890); `0387e6cc` Custom redirect on login (#1530) — run `git show` on any of them.
Change coupling: useMany.ts ↔ useOne.ts packages/core/src/hooks/data/useMany.ts:1— `packages/core/src/hooks/data/useMany.ts` and `packages/core/src/hooks/data/useOne.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 — 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 `bc07a305` fix: replaced the outdated tanstack links (#6810); `1c9a95f2` feat(devtools): devtools improvements (#5875); `3bdb9cb1` fix: return type is not mentioned correctly in useOne hook (#5316) — run `git show` on any of them.
Skipped test: should use prop for custom text packages/ui-tests/src/tests/fields/boolean.tsx:10— Skipped — switched off by it.skip
Skipped test: should invalidates when button is clicked packages/ui-tests/src/tests/buttons/refresh.tsx:95— Skipped — switched off by it.skip
Skipped test: should has 'to' param on URL after redirected to /login cypress/e2e/with-remix-material-ui/all.cy.ts:47— Skipped — switched off by it.skip
Skipped test: should has 'to' param on URL after redirected to /login cypress/e2e/with-nextjs-next-auth/all.cy.ts:38— Skipped — switched off by it.skip
Cross-context type BaseKey (core → antd) packages/antd/src/hooks/form/useModalForm/useModalForm.ts:300— BaseKey (context core) is exposed in antd's public surface via useModalForm.useModalForm.show — couples the contexts.
Cross-context type BaseKey (core → antd) packages/antd/src/hooks/form/useDrawerForm/useDrawerForm.ts:285— BaseKey (context core) is exposed in antd's public surface via useDrawerForm.useDrawerForm.show — couples the contexts.
Cross-context type BaseKey (core → antd) packages/antd/src/hooks/table/useEditableTable/useEditableTable.ts:106— BaseKey (context core) is exposed in antd's public surface via useEditableTable.useEditableTable.editButtonProps — couples the contexts.
Cross-context type BaseKey (core → antd) packages/antd/src/hooks/table/useEditableTable/useEditableTable.ts:112— BaseKey (context core) is exposed in antd's public surface via useEditableTable.useEditableTable.isEditing — couples the contexts.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×4
Off the main sequence: @refinedev/core — @refinedev/core: abstractness 0.02, instability 0.03, distance 0.94 — zone of pain — concrete and depended on by 29 project(s), so it's rigid to change.
Off the main sequence: @refinedev/react-hook-form — @refinedev/react-hook-form: abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: @refinedev/react-table — @refinedev/react-table: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: @refinedev/cli — @refinedev/cli: abstractness 0.02, instability 0.25, distance 0.73 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×4
Recursive walk over a caller-supplied document has no depth cap packages/strapi-v4/src/utils/normalizeData.ts:15— `normalizeData` is exported and takes `data: any` from its caller, and it calls itself at line 15 (`normalizeData`) with a piece of `data` (and at line 30) — and nowhere in `normalizeData` 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 `normalizeData` 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/rest/src/data-providers/strapi-v4/utils/normalizeData.ts:15— `normalizeData` is exported and takes `data: any` from its caller, and it calls itself at line 15 (`normalizeData`) with a piece of `data` (and at line 30) — and nowhere in `normalizeData` 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 `normalizeData` 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/inferencer/src/utilities/deep-has-key/index.ts:16— `deepHasKey` is exported and takes `obj: Record<string, any>` from its caller, and it calls itself at line 16 (`deepHasKey`) with a piece of `obj` — and nowhere in `deepHasKey` 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 `deepHasKey` 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/devtools/src/utilities/selector-helpers.ts:152— `traverseDom` is exported and takes `node: HTMLElement | null` from its caller, and it calls itself at line 152 (`traverseDom`) with a piece of `node` — and nowhere in `traverseDom` 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 `traverseDom` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Focus outline removed inline packages/inferencer/src/components/shared-code-viewer/index.tsx:296— <button> takes keyboard focus, and outline:none/0 in its inline style removes the focus ring with no chance of a :focus replacement (an inline style outranks every stylesheet rule). Keep a visible focus indicator.
Focus outline removed inline packages/refine-ui/registry/new-york/ui/input.tsx:7— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline packages/refine-ui/registry/new-york/ui/textarea.tsx:7— <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
show.renderer (cyclomatic 51) packages/inferencer/src/inferencers/antd/show.tsx:45— show.renderer has cyclomatic complexity 51 (threshold 15). Most of this is not in the body itself: 7 of the 51 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 552, a function literal at line 231, a function literal at line 81, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
show.renderer (cyclomatic 51) packages/inferencer/src/inferencers/mantine/show.tsx:44— show.renderer has cyclomatic complexity 51 (threshold 15). Most of this is not in the body itself: 7 of the 51 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 616, a function literal at line 79, a function literal at line 243, …). 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.
show.renderer (cyclomatic 51) packages/inferencer/src/inferencers/mui/show.tsx:45— show.renderer has cyclomatic complexity 51 (threshold 15). Most of this is not in the body itself: 7 of the 51 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 636, a function literal at line 258, a function literal at line 81, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
edit.renderer::basicInputFields (cyclomatic 17) packages/inferencer/src/inferencers/headless/edit.tsx:164— edit.renderer::basicInputFields 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.
edit.renderer::basicInputFields (cyclomatic 17) packages/inferencer/src/inferencers/mui/edit.tsx:223— edit.renderer::basicInputFields 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 (edit.renderer::renderRelationFields) 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.
edit.renderer::renderRelationFields (cyclomatic 16) packages/inferencer/src/inferencers/mui/edit.tsx:117— edit.renderer::renderRelationFields has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (edit.renderer::basicInputFields) 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.
edit.renderer::renderRelationFields (cognitive 27) packages/inferencer/src/inferencers/mui/edit.tsx:117— edit.renderer::renderRelationFields has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 10 (24 pts), boolean chains 2, if/else 1 (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: one other method here (edit.renderer::basicInputFields) 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.
edit.renderer::basicInputFields (cognitive 25) packages/inferencer/src/inferencers/headless/edit.tsx:164— edit.renderer::basicInputFields has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 8 (20 pts), if/else 2 (3 pts), boolean chains 2 (nesting depth added 13). 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.
edit.renderer::basicInputFields (cognitive 23) packages/inferencer/src/inferencers/mui/edit.tsx:223— edit.renderer::basicInputFields has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 7 (17 pts), boolean chains 3, if/else 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (edit.renderer::renderRelationFields) 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.
Change coupling clique: REDACTED, REDACTED, REDACTED, REDACTED, REDACTED packages/mui/src/components/buttons/clone/index.tsx— 5 files — `packages/mui/src/components/buttons/clone/index.tsx`, `packages/mui/src/components/buttons/create/index.tsx`, `packages/mui/src/components/buttons/edit/index.tsx`, `packages/mui/src/components/buttons/list/index.tsx`, `packages/mui/src/components/buttons/show/index.tsx` — all change together with no explicit dependency: a fully-connected co-change clique, not 10 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, REDACTED packages/mui/src/components/crud/create/index.tsx— 3 files — `packages/mui/src/components/crud/create/index.tsx`, `packages/mui/src/components/crud/edit/index.tsx`, `packages/mui/src/components/crud/show/index.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.
Change coupling clique: REDACTED, REDACTED, REDACTED packages/antd/src/components/crud/create/index.tsx— 3 files — `packages/antd/src/components/crud/create/index.tsx`, `packages/antd/src/components/crud/edit/index.tsx`, `packages/antd/src/components/crud/show/index.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.
IC1 · Incompleteness & stubs· Both branches are identical · ×3
Both branches are identical — the condition decides nothing REDACTED:166— 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.
Both branches are identical — the condition decides nothing packages/core/src/components/pages/config-success/index.tsx:143— 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.
Both branches are identical — the condition decides nothing packages/refine-ui/registry/new-york/refine-ui/data-table/data-table.tsx:242— 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.
Dead file (~66 LoC) packages/refine-ui/registry/new-york/ui/accordion.tsx— no import path from any entry point (460 application, 140 tooling, 892 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 (~66 LoC) packages/refine-ui/registry/new-york/ui/alert.tsx— no import path from any entry point (460 application, 140 tooling, 892 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 (~66 LoC) packages/refine-ui/registry/new-york/ui/tabs.tsx— no import path from any entry point (460 application, 140 tooling, 892 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
index.ThemedSider (cyclomatic 32) packages/mantine/src/components/themedLayout/sider/index.tsx:37— index.ThemedSider has cyclomatic complexity 32 (threshold 15). Of this number, 16 points are the body's own statements and 16 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.
index.ThemedSider (cyclomatic 32) packages/mui/src/components/themedLayout/sider/index.tsx:37— index.ThemedSider has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 9 of the 32 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 105, a function literal at line 130, handleLogout, …). 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.
index.Edit (cyclomatic 21) packages/mantine/src/components/crud/edit/index.tsx:37— index.Edit 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.
index.Edit (cyclomatic 21) packages/mui/src/components/crud/edit/index.tsx:47— index.Edit 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.
show.renderer (cognitive 72) packages/inferencer/src/inferencers/antd/show.tsx:45— show.renderer has cognitive complexity 72 (threshold 15). Drivers by points: if/else 30 (59 pts), boolean chains 6, ternaries 3 (6 pts), match/switch 1 (nesting depth added 32). Most of this is not in the body itself: 7 of the 72 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 231, a function literal at line 81, renderRelationFields, …). 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.
show.renderer (cognitive 72) packages/inferencer/src/inferencers/mui/show.tsx:45— show.renderer has cognitive complexity 72 (threshold 15). Drivers by points: if/else 30 (59 pts), boolean chains 6, ternaries 3 (6 pts), match/switch 1 (nesting depth added 32). Most of this is not in the body itself: 7 of the 72 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 258, a function literal at line 81, renderRelationFields, …). 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.
index.Edit (cognitive 25) packages/mantine/src/components/crud/edit/index.tsx:37— index.Edit has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 14 (19 pts), boolean chains 6 (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.
index.Edit (cognitive 25) packages/mui/src/components/crud/edit/index.tsx:47— index.Edit has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 13 (18 pts), boolean chains 7 (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.
normalize.mediaUploadMapper (cognitive 16) packages/strapi-v4/src/helpers/normalize.ts:29— normalize.mediaUploadMapper has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 2 (8 pts) (nesting depth added 10). None of this is in the body itself: all 16 points belong to one function literal inside it that branches (line 30). 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.
normalize.mediaUploadMapper (cognitive 16) packages/strapi/src/helpers/normalize.ts:29— normalize.mediaUploadMapper has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 2 (8 pts) (nesting depth added 10). None of this is in the body itself: all 16 points belong to one function literal inside it that branches (line 30). 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.
Cross-context type CrudFilter (core → appwrite) packages/appwrite/src/utils/replaceIdWithAppwriteId.ts:8— CrudFilter (context core) is exposed in appwrite's public surface via replaceIdWithAppwriteId.replaceIdWithAppwriteId — couples the contexts.
Cross-context type CrudFilter (core → appwrite) packages/appwrite/src/utils/generateFilter.ts:11— CrudFilter (context core) is exposed in appwrite's public surface via generateFilter.generateFilter — couples the contexts.
Cross-context type CrudOperators (core → mui) packages/mui/src/definitions/dataGrid/index.ts:35— CrudOperators (context core) is exposed in mui's public surface via index.transformMuiOperatorToCrudOperator — couples the contexts.
Cross-context type CrudOperators (core → mui) packages/mui/src/definitions/dataGrid/index.ts:102— CrudOperators (context core) is exposed in mui's public surface via index.transformCrudOperatorToMuiOperator — couples the contexts.
Cross-context type CrudFilter (core → react-table) packages/react-table/src/utils/column-filters-to-crud-filters/index.ts:18— CrudFilter (context core) is exposed in react-table's public surface via index.columnFiltersToCrudFilters — couples the contexts.
Cross-context type CrudFilter (core → react-table) packages/react-table/src/utils/get-removed-filters/index.ts:8— CrudFilter (context core) is exposed in react-table's public surface via index.getRemovedFilters — couples the contexts.
Cross-context type CrudOperators (core → rest) packages/rest/src/data-providers/nestjsx-crud/utils/mapOperator.ts:4— CrudOperators (context core) is exposed in rest's public surface via mapOperator.mapOperator — couples the contexts.
Cross-context type CrudOperators (core → rest) packages/rest/src/data-providers/strapi-v4/utils/mapOperator.ts:3— CrudOperators (context core) is exposed in rest's public surface via mapOperator.mapOperator — couples the contexts.
Change-coupling hub: useDelete.ts → useDeleteMany.ts, useUpdate.ts, useUpdateMany.ts packages/core/src/hooks/data/useDelete.ts— `packages/core/src/hooks/data/useDelete.ts` changes together with 3 other files — `packages/core/src/hooks/data/useDeleteMany.ts`, `packages/core/src/hooks/data/useUpdate.ts`, `packages/core/src/hooks/data/useUpdateMany.ts` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 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 3.
Change-coupling hub: useList.ts → useCustom.ts, useMany.ts, useOne.ts packages/core/src/hooks/data/useList.ts— `packages/core/src/hooks/data/useList.ts` changes together with 3 other files — `packages/core/src/hooks/data/useCustom.ts`, `packages/core/src/hooks/data/useMany.ts`, `packages/core/src/hooks/data/useOne.ts` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 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 3.
Duplication concentrated across 4 sibling directories (5 clone groups) packages/antd/src/components/pages/auth/components/forgotPassword/index.tsx:54— 5 of the duplicated blocks reported below have copies in at least two of the sibling directories forgotPassword, login, register, updatePassword under packages/antd/src/components/pages/auth/components/. That concentration is one structural fact, not 5 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 5 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 4 sibling directories (5 clone groups) packages/chakra-ui/src/components/pages/auth/components/login/index.tsx:34— 5 duplicated blocks under packages/chakra-ui/src/components/pages/auth/components/ have copies in at least two of the sibling directories forgotPassword, login, register, updatePassword — 3 of them are reported below, and 2 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (173 matched lines × 2 locations) · ×2
Duplicated block with local edits (173 matched lines × 2 locations) packages/core/src/hooks/data/useDelete.ts:165— packages/core/src/hooks/data/useDelete.ts:165 · packages/core/src/hooks/data/useUpdate.ts:206 — the two spans are one implementation copied and then locally edited — 798 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (173 matched lines × 2 locations) packages/core/src/hooks/data/useDeleteMany.ts:189— packages/core/src/hooks/data/useDeleteMany.ts:189 · packages/core/src/hooks/data/useUpdateMany.ts:234 — the two spans are one implementation copied and then locally edited — 795 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 (118 matched lines × 2 locations) · ×2
Duplicated block with local edits (118 matched lines × 2 locations) packages/core/src/components/pages/auth/components/login/index.tsx:13— packages/core/src/components/pages/auth/components/login/index.tsx:13 · packages/core/src/components/pages/auth/components/register/index.tsx:15 — the two spans are one implementation copied and then locally edited — 545 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (118 matched lines × 2 locations) packages/mui/src/components/crud/edit/index.tsx:71— packages/mui/src/components/crud/edit/index.tsx:71 · packages/mui/src/components/crud/show/index.tsx:64 — the two spans are one implementation copied and then locally edited — 542 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.
Dead file (~78 LoC) packages/codemod/src/transformations/v4/add-v3LegacyAuthProviderCompatible-true-to-auth-hooks.ts— no import path from any entry point (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/refine3-to-refine4.ts) — 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 (~78 LoC) packages/refine-ui/registry/new-york/ui/input-otp.tsx— no import path from any entry point (460 application, 140 tooling, 892 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 (~73 LoC) packages/codemod/src/definitions/separated-imports/react-query.ts— no import path from any entry point (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/v4/separate-imports-react-query.ts) — 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 (~73 LoC) packages/refine-ui/registry/new-york/ui/toggle-group.tsx— no import path from any entry point (460 application, 140 tooling, 892 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
AC2 · Forms & labels· <Select> field component without a label · ×1
<Select> field component without a label packages/refine-ui/registry/new-york/refine-ui/data-table/data-table-pagination.tsx:74— 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.
AC3 · Page structure· Heading level jumps from h1 to h4 · ×1
Heading level jumps from h1 to h4 packages/core/src/components/pages/config-success/index.tsx:163— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark packages/refine-ui/app/layout.tsx:21— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Low contrast colour pair in CSS (2.0:1) examples/pixels/src/styles/style.css:177— `::selection` sets color: #fff on background-color: #3ecf8e — 2.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
list.renderer (cyclomatic 97) packages/inferencer/src/inferencers/mui/list.tsx:47— list.renderer has cyclomatic complexity 97 (threshold 15). Of this number, 21 points are the body's own statements and 76 belong to 12 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
list.renderer (cyclomatic 91) packages/inferencer/src/inferencers/antd/list.tsx:45— list.renderer has cyclomatic complexity 91 (threshold 15). Of this number, 18 points are the body's own statements and 73 belong to 11 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
list.renderer (cyclomatic 76) packages/inferencer/src/inferencers/mantine/list.tsx:54— list.renderer has cyclomatic complexity 76 (threshold 15). Of this number, 20 points are the body's own statements and 56 belong to 12 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
list.renderer (cyclomatic 75) packages/inferencer/src/inferencers/chakra-ui/list.tsx:69— list.renderer has cyclomatic complexity 75 (threshold 15). Of this number, 19 points are the body's own statements and 56 belong to 12 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
check-package.checkPackage (cyclomatic 57) packages/live-previews/src/utils/check-package.ts:1— check-package.checkPackage has cyclomatic complexity 57 (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.
edit.renderer (cyclomatic 56) packages/inferencer/src/inferencers/antd/edit.tsx:37— edit.renderer has cyclomatic complexity 56 (threshold 15). Most of this is not in the body itself: 7 of the 56 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 77, a function literal at line 427, renderRelationFields, …). 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.
show.renderer (cyclomatic 56) packages/inferencer/src/inferencers/headless/show.tsx:32— show.renderer has cyclomatic complexity 56 (threshold 15). Most of this is not in the body itself: 11 of the 56 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 611, a function literal at line 230, a function literal at line 68, …). 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.
show.renderer (cyclomatic 52) packages/inferencer/src/inferencers/chakra-ui/show.tsx:43— show.renderer has cyclomatic complexity 52 (threshold 15). Most of this is not in the body itself: 7 of the 52 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 598, a function literal at line 252, a function literal at line 78, …). 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.
edit.renderer (cyclomatic 51) packages/inferencer/src/inferencers/mantine/edit.tsx:43— edit.renderer has cyclomatic complexity 51 (threshold 15). Most of this is not in the body itself: 7 of the 51 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 407, a function literal at line 83, textFields, …). 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.
create.renderer (cyclomatic 49) packages/inferencer/src/inferencers/antd/create.tsx:37— create.renderer has cyclomatic complexity 49 (threshold 15). Most of this is not in the body itself: 7 of the 49 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 335, renderRelationFields, basicInputFields, …). 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.
index.createInferencer (cyclomatic 48) packages/inferencer/src/create-inferencer/index.tsx:40— index.createInferencer has cyclomatic complexity 48 (threshold 15). Most of this is not in the body itself: 1 of the 48 points is its own statement and the rest belongs to 12 function items inside it that branch (Inferencer, a function literal at line 249, a function literal at line 191, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
create.renderer (cyclomatic 47) packages/inferencer/src/inferencers/mantine/create.tsx:40— create.renderer has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 7 of the 47 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 315, textFields, renderRelationFields, …). 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.
useUpdateMany.useUpdateMany (cyclomatic 41) packages/core/src/hooks/data/useUpdateMany.ts:170— useUpdateMany.useUpdateMany has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 1 of the 41 points is its own statement and the rest belongs to 13 function literals inside it that branch (lines 306, 603, 505, …). 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.
create.renderer (cyclomatic 41) packages/inferencer/src/inferencers/headless/create.tsx:37— create.renderer has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 10 of the 41 points are its own statements and the rest belongs to 6 function items inside it that branch (basicInputFields, a function literal at line 246, a function literal at line 70, …). 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.
index.useModalForm (cyclomatic 40) packages/react-hook-form/src/useModalForm/index.ts:89— index.useModalForm has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 8 of the 40 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 202, a function literal at line 226, 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.
edit.renderer (cyclomatic 39) packages/inferencer/src/inferencers/chakra-ui/edit.tsx:45— edit.renderer has cyclomatic complexity 39 (threshold 15). Most of this is not in the body itself: 7 of the 39 points are its own statements and the rest belongs to 7 function items inside it that branch (basicInputFields, a function literal at line 363, a function literal at line 86, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
useUpdate.useUpdate (cyclomatic 38) packages/core/src/hooks/data/useUpdate.ts:169— useUpdate.useUpdate has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 1 of the 38 points is its own statement and the rest belongs to 11 function literals inside it that branch (lines 467, 297, 564, …). 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.
doc-sidebar.SidebarCategory (cyclomatic 37) REDACTED:55— doc-sidebar.SidebarCategory has cyclomatic complexity 37 (threshold 15). Of this number, 34 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
index.SearchPageContent (cyclomatic 37) documentation/src/theme/SearchPage/index.js:113— index.SearchPageContent has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 13 of the 37 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 138, a function literal at line 190, a function literal at line 180, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
create.renderer (cyclomatic 36) packages/inferencer/src/inferencers/chakra-ui/create.tsx:44— create.renderer has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 7 of the 36 points are its own statements and the rest belongs to 7 function items inside it that branch (basicInputFields, a function literal at line 271, a function literal at line 79, …). 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.
index.useModalForm (cyclomatic 36) packages/mantine/src/hooks/form/useModalForm/index.ts:81— index.useModalForm has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 8 of the 36 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 181, a function literal at line 205, a function literal at line 253, …). 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.
blog-toc.BlogTOC (cyclomatic 35) REDACTED:376— blog-toc.BlogTOC has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 4 of the 35 points are its own statements and the rest belongs to 15 function literals inside it that branch (lines 538, 401, 416, …). 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.
landing-footer.LandingFooter (cyclomatic 35) documentation/src/refine-theme/landing-footer.tsx:14— landing-footer.LandingFooter has cyclomatic complexity 35 (threshold 15). Of this number, 25 points are the body's own statements and 10 belong to 4 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.
fix-v4-deprecations.fixDeprecatedUseTableProps (cyclomatic 35) packages/codemod/src/transformations/v4/fix-v4-deprecations.ts:436— fix-v4-deprecations.fixDeprecatedUseTableProps has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 1 of the 35 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 446, 468, 646, …). 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.
index.transformCrudOperatorToMuiOperator (cyclomatic 35) packages/mui/src/definitions/dataGrid/index.ts:102— index.transformCrudOperatorToMuiOperator has cyclomatic complexity 35 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
index.useRefineKbar::createActionWithResource (cyclomatic 32) packages/kbar/src/hooks/useRefineKbar/index.tsx:89— index.useRefineKbar::createActionWithResource has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
index.Show (cyclomatic 31) packages/chakra-ui/src/components/crud/show/index.tsx:31— index.Show has cyclomatic complexity 31 (threshold 15). Of this number, 27 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
index.useRelationFetch (cyclomatic 31) packages/inferencer/src/use-relation-fetch/index.ts:26— index.useRelationFetch has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 47, 275, 61, …). 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.
chart.ChartTooltipContent (cyclomatic 31) REDACTED:108— chart.ChartTooltipContent has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 5 of the 31 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 183, 132). 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.
index.ThemedSider (cyclomatic 30) packages/chakra-ui/src/components/themedLayout/sider/index.tsx:34— index.ThemedSider has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 11 of the 30 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 79, getDefaultExpandMenuItemsCB, handleLogout, …). 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.
mutation-result-to-mutation-property.mutationResultToMutationProperty (cyclomatic 30) packages/codemod/src/transformations/v5/mutation-result-to-mutation-property.ts:14— mutation-result-to-mutation-property.mutationResultToMutationProperty has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 1 of the 30 points is its own statement and the rest belongs to 9 function literals inside it that branch (lines 32, 23, 121, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
rename-useResource-useResourceParams.renameUseResourceToUseResourceParams (cyclomatic 30) packages/codemod/src/transformations/v5/rename-useResource-useResourceParams.ts:4— rename-useResource-useResourceParams.renameUseResourceToUseResourceParams 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 9 function literals inside it that branch (lines 117, 91, 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.
package-item.PackageItem (cyclomatic 30) packages/devtools-ui/src/components/package-item.tsx:21— package-item.PackageItem has cyclomatic complexity 30 (threshold 15). Of this number, 18 points are the body's own statements and 12 belong to 4 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
index.Edit (cyclomatic 29) packages/chakra-ui/src/components/crud/edit/index.tsx:34— index.Edit has cyclomatic complexity 29 (threshold 15). Of this number, 25 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
generateFilter.generateFilter (cyclomatic 29) packages/supabase/src/utils/generateFilter.ts:4— generateFilter.generateFilter has cyclomatic complexity 29 (threshold 15). Of this number, 19 points are the body's own statements and 10 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
use-react-table-return-type-update.useTableReturnTypeUpdate (cyclomatic 28) packages/codemod/src/transformations/v5/use-react-table-return-type-update.ts:4— use-react-table-return-type-update.useTableReturnTypeUpdate 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 5 function literals inside it that branch (lines 9, 70, 34, …). 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.
index.ThemedSider (cyclomatic 27) packages/antd/src/components/themedLayout/sider/index.tsx:34— index.ThemedSider has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 10 of the 27 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 65, renderClosingIcons, handleLogout, …). 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.
useModalForm.useModalForm (cyclomatic 27) packages/antd/src/hooks/form/useModalForm/useModalForm.ts:103— useModalForm.useModalForm has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 10 of the 27 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 207, 232, 327). 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.
useDrawerForm.useDrawerForm (cyclomatic 26) packages/antd/src/hooks/form/useDrawerForm/useDrawerForm.ts:95— useDrawerForm.useDrawerForm has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 9 of the 26 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 179, 201, 307). 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.
resizable-pane.ResizablePane (cyclomatic 26) packages/devtools/src/components/resizable-pane.tsx:28— resizable-pane.ResizablePane has cyclomatic complexity 26 (threshold 15). Of this number, 18 points are the body's own statements and 8 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.
doc-sidebar.SidebarLink (cyclomatic 25) REDACTED:326— doc-sidebar.SidebarLink has cyclomatic complexity 25 (threshold 15). Of this number, 21 points are the body's own statements and 4 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.
preview.Preview (cyclomatic 25) packages/live-previews/pages/preview.tsx:15— preview.Preview has cyclomatic complexity 25 (threshold 15). Of this number, 20 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, 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.
data-table.getCommonStyles (cyclomatic 25) packages/refine-ui/registry/new-york/refine-ui/data-table/data-table.tsx:261— data-table.getCommonStyles has cyclomatic complexity 25 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
list.renderer (cyclomatic 24) packages/inferencer/src/inferencers/headless/list.tsx:43— list.renderer has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (list.renderer::renderRelationFields) 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.
use-query-and-result-fields-in-list-hooks.useQueryAndResultFieldsInListHooks (cyclomatic 23) packages/codemod/src/transformations/v5/use-query-and-result-fields-in-list-hooks.ts:8— use-query-and-result-fields-in-list-hooks.useQueryAndResultFieldsInListHooks has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 59, 24, 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.
index.useTable (cyclomatic 23) packages/core/src/hooks/useTable/index.ts:182— index.useTable has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 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.
index.Show (cyclomatic 23) packages/mui/src/components/crud/show/index.tsx:44— index.Show 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.
useTable.useTable (cyclomatic 22) packages/antd/src/hooks/table/useTable/useTable.ts:57— useTable.useTable has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 7 function items inside it that branch (onChange, a function literal at line 195, onFinish, …). 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.
generateFilter.generateFilter (cyclomatic 22) packages/appwrite/src/utils/generateFilter.ts:11— generateFilter.generateFilter has cyclomatic complexity 22 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
use-query-and-result-fields-in-useOne-hook.useQueryAndResultFieldsInUseOneHook (cyclomatic 22) packages/codemod/src/transformations/v5/use-query-and-result-fields-in-useOne-hook.ts:7— use-query-and-result-fields-in-useOne-hook.useQueryAndResultFieldsInUseOneHook 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 4 function literals inside it that branch (lines 23, 106, 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.
add-package-drawer.AddPackageDrawer (cyclomatic 22) packages/devtools-ui/src/components/add-package-drawer.tsx:25— add-package-drawer.AddPackageDrawer has cyclomatic complexity 22 (threshold 15). Of this number, 12 points are the body's own statements and 10 belong to 3 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
index.Show (cyclomatic 22) packages/mantine/src/components/crud/show/index.tsx:36— index.Show 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.
fix-v4-deprecations.fixDeprecatedReactTableProps (cyclomatic 21) packages/codemod/src/transformations/v4/fix-v4-deprecations.ts:228— fix-v4-deprecations.fixDeprecatedReactTableProps 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 4 function literals inside it that branch (lines 252, 275, 322, …). 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.
getListHelpers.operatorMapper (cyclomatic 21) packages/graphql/src/utils/getListHelpers.ts:39— getListHelpers.operatorMapper has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
object.objectInfer (cyclomatic 21) packages/inferencer/src/field-inferencers/object.ts:6— object.objectInfer has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
index.operatorMapper (cyclomatic 21) packages/nestjs-query/src/utils/index.ts:69— index.operatorMapper has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
dataProvider.DataProvider (cyclomatic 21) packages/strapi-v4/src/dataProvider.ts:12— dataProvider.DataProvider has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 241, 16, 95, …). 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.
antd.SvgAntd (cyclomatic 20) documentation/src/assets/integration-icons/antd.tsx:4— antd.SvgAntd has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
index.Edit (cyclomatic 20) packages/antd/src/components/crud/edit/index.tsx:36— index.Edit has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
index.Show (cyclomatic 20) packages/antd/src/components/crud/show/index.tsx:33— index.Show has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
create-data-provider.createDataProvider (cyclomatic 20) packages/rest/src/create-data-provider.ts:24— create-data-provider.createDataProvider has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 313, 89, 148, …). 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.
doc-breadcrumbs.DocBreadcrumbs (cyclomatic 19) documentation/src/refine-theme/doc-breadcrumbs.tsx:16— doc-breadcrumbs.DocBreadcrumbs 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 4 function literals inside it that branch (lines 90, 44, 53, …). 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.
index.Create (cyclomatic 19) packages/chakra-ui/src/components/crud/create/index.tsx:18— index.Create has cyclomatic complexity 19 (threshold 15). Of this number, 15 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
index.useForm.onFinish (cyclomatic 19) packages/core/src/hooks/form/index.ts:214— index.useForm.onFinish has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 228, 289). 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.
index.useForm (cyclomatic 19) packages/react-hook-form/src/useForm/index.ts:82— index.useForm 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 6 function literals inside it that branch (lines 153, 303, 257, …). 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.
data-table-filter.DataTableFilterCombobox (cyclomatic 19) packages/refine-ui/registry/new-york/refine-ui/data-table/data-table-filter.tsx:249— data-table-filter.DataTableFilterCombobox has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 268, 298, 279, …). 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.
index.SandpackBase (cyclomatic 18) documentation/src/components/sandpack/index.tsx:70— index.SandpackBase has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
doc-thumbs-up-down-feedback-widget.DocThumbsUpDownFeedbackWidget (cyclomatic 18) documentation/src/refine-theme/doc-thumbs-up-down-feedback-widget.tsx:36— doc-thumbs-up-down-feedback-widget.DocThumbsUpDownFeedbackWidget has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
tutorial-sandpack.TutorialSandpack (cyclomatic 18) documentation/src/refine-theme/tutorial-sandpack.tsx:57— tutorial-sandpack.TutorialSandpack has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 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.
rename-pagination-current-to-currentPage.renamePaginationCurrentToCurrentPage (cyclomatic 18) packages/codemod/src/transformations/v5/rename-pagination-current-to-currentPage.ts:18— rename-pagination-current-to-currentPage.renamePaginationCurrentToCurrentPage has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 75, 34, 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.
useMany.useMany (cyclomatic 18) packages/core/src/hooks/data/useMany.ts:103— useMany.useMany has cyclomatic complexity 18 (threshold 15). Of this number, 9 points are the body's own statements and 9 belong to 4 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.
useDeleteMany.useDeleteMany (cyclomatic 18) packages/core/src/hooks/data/useDeleteMany.ts:140— useDeleteMany.useDeleteMany has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 11 function literals inside it that branch (lines 475, 261, 345, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
index.ConfigSuccessPage (cyclomatic 18) packages/core/src/components/pages/config-success/index.tsx:49— index.ConfigSuccessPage has cyclomatic complexity 18 (threshold 15). Of this number, 12 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.
get-resource-path.getResourcePath (cyclomatic 18) packages/devtools-internal/src/get-resource-path.ts:11— get-resource-path.getResourcePath has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
index.SharedCodeViewer (cyclomatic 18) packages/inferencer/src/components/shared-code-viewer/index.tsx:9— index.SharedCodeViewer has cyclomatic complexity 18 (threshold 15). Of this number, 11 points are the body's own statements and 7 belong to 5 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
replace-imports.replaceImports (cyclomatic 18) packages/live-previews/src/utils/replace-imports.ts:12— replace-imports.replaceImports has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
banner-modal.BannerModal (cyclomatic 17) documentation/src/components/banner/banner-modal.tsx:32— banner-modal.BannerModal has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 53, 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.
index.CategoryNavBarSelect (cyclomatic 17) documentation/src/components/blog/category-nav-bar/index.tsx:44— index.CategoryNavBarSelect has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 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.
template-detail.TemplatesDetail (cyclomatic 17) documentation/src/refine-theme/template-detail.tsx:50— template-detail.TemplatesDetail 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.
tutorial-paginator.TutorialPaginator (cyclomatic 17) documentation/src/refine-theme/tutorial-paginator.tsx:116— tutorial-paginator.TutorialPaginator 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.
index.action (cyclomatic 17) packages/cli/src/commands/swizzle/index.tsx:70— index.action 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 2 function literals inside it that branch (lines 193, 78). 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.
index.getProjectType (cyclomatic 17) packages/cli/src/utils/project/index.ts:4— index.getProjectType 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.
rename-current-to-currentPage.renameCurrentToCurrentPage (cyclomatic 17) packages/codemod/src/transformations/v5/rename-current-to-currentPage.ts:9— rename-current-to-currentPage.renameCurrentToCurrentPage has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 47, 25, 95, …). 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.
use-query-and-result-fields-in-useInfiniteList-hook.useQueryAndResultFieldsInUseInfiniteListHook (cyclomatic 17) packages/codemod/src/transformations/v5/use-query-and-result-fields-in-useInfiniteList-hook.ts:3— use-query-and-result-fields-in-useInfiniteList-hook.useQueryAndResultFieldsInUseInfiniteListHook 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 2 function literals inside it that branch (lines 28, 56). 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.
use-query-and-result-fields-in-useCustom-hook.useQueryAndResultFieldsInUseCustomHook (cyclomatic 17) packages/codemod/src/transformations/v5/use-query-and-result-fields-in-useCustom-hook.ts:3— use-query-and-result-fields-in-useCustom-hook.useQueryAndResultFieldsInUseCustomHook has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 31, 61, 97). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
list.renderer::renderRelationFields (cyclomatic 17) packages/inferencer/src/inferencers/headless/list.tsx:131— list.renderer::renderRelationFields 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 (list.renderer) 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.
index.useTable (cyclomatic 17) packages/react-table/src/useTable/index.ts:49— index.useTable has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 135, 152, 123, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
providers-icon.ProvidersIcon (cyclomatic 16) documentation/src/components/landing/icons/providers-icon.tsx:5— providers-icon.ProvidersIcon has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
common-header.CommonHeader (cyclomatic 16) documentation/src/refine-theme/common-header.tsx:25— common-header.CommonHeader has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
tutorial-navigation.NavigationDropdown (cyclomatic 16) documentation/src/refine-theme/tutorial-navigation.tsx:69— tutorial-navigation.NavigationDropdown has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 258, 93, 227, …). 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.
tutorial-sandpack.SandpackRightSide (cyclomatic 16) documentation/src/refine-theme/tutorial-sandpack.tsx:433— tutorial-sandpack.SandpackRightSide has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 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.
remove-useNewQueryKeys-from-refine-options.removeUseNewQueryKeysFromRefineOptions (cyclomatic 16) packages/codemod/src/transformations/v5/remove-useNewQueryKeys-from-refine-options.ts:3— remove-useNewQueryKeys-from-refine-options.removeUseNewQueryKeysFromRefineOptions 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 3 function literals inside it that branch (lines 16, 49, 25). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
welcome-page-import-from-core.welcomePageImportFromCore (cyclomatic 16) packages/codemod/src/transformations/v5/welcome-page-import-from-core.ts:14— welcome-page-import-from-core.welcomePageImportFromCore 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 26, 31, 56, …). 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.
generateFilters.mergeHasuraFilters (cyclomatic 16) packages/hasura/src/utils/generateFilters.ts:183— generateFilters.mergeHasuraFilters has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body: 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.
create.renderer::renderRelationFields (cyclomatic 16) packages/inferencer/src/inferencers/mui/create.tsx:100— create.renderer::renderRelationFields has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
index.useForm (cyclomatic 16) packages/mantine/src/hooks/form/useForm/index.ts:85— index.useForm 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 5 function literals inside it that branch (lines 152, 224, 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.
notificationProvider.useNotificationProvider (cyclomatic 16) packages/mantine/src/providers/notificationProvider.tsx:13— notificationProvider.useNotificationProvider 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 5 function items inside it that branch (a function literal at line 39, addNotification, removeNotification, …). 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.
index.liveProvider.subscribe (cyclomatic 16) packages/supabase/src/liveProvider/index.ts:14— index.liveProvider.subscribe has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 3 function items inside it that branch (listener, mapFilter, a function literal at line 58). 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.
index.useRelationFetch (cognitive 87) packages/inferencer/src/use-relation-fetch/index.ts:26— index.useRelationFetch has cognitive complexity 87 (threshold 15). Drivers by points: ternaries 8 (37 pts), if/else 12 (29 pts), error handling 4 (14 pts), boolean chains 7 (nesting depth added 56). None of this is in the body itself: all 87 points belong to 4 function literals inside it that branch (lines 47, 275, 61, …). 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.
show.renderer (cognitive 78) packages/inferencer/src/inferencers/headless/show.tsx:32— show.renderer has cognitive complexity 78 (threshold 15). Drivers by points: if/else 31 (60 pts), ternaries 7 (11 pts), boolean chains 6, match/switch 1 (nesting depth added 33). Most of this is not in the body itself: 12 of the 78 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 230, a function literal at line 68, renderRelationFields, …). 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.
index.createInferencer (cognitive 75) packages/inferencer/src/create-inferencer/index.tsx:40— index.createInferencer has cognitive complexity 75 (threshold 15). Drivers by points: if/else 22 (41 pts), boolean chains 17, ternaries 5 (17 pts) (nesting depth added 31). None of this is in the body itself: all 75 points belong to 12 function items inside it that branch (a function literal at line 249, a function literal at line 191, Inferencer, …). 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.
edit.renderer (cognitive 74) packages/inferencer/src/inferencers/antd/edit.tsx:37— edit.renderer has cognitive complexity 74 (threshold 15). Drivers by points: ternaries 15 (37 pts), if/else 18 (27 pts), boolean chains 9, match/switch 1 (nesting depth added 31). Most of this is not in the body itself: 7 of the 74 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 77, renderRelationFields, imageFields, …). 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.
show.renderer (cognitive 73) packages/inferencer/src/inferencers/chakra-ui/show.tsx:43— show.renderer has cognitive complexity 73 (threshold 15). Drivers by points: if/else 31 (60 pts), boolean chains 6, ternaries 3 (6 pts), match/switch 1 (nesting depth added 32). Most of this is not in the body itself: 7 of the 73 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 252, a function literal at line 78, renderRelationFields, …). 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.
show.renderer (cognitive 70) packages/inferencer/src/inferencers/mantine/show.tsx:44— show.renderer has cognitive complexity 70 (threshold 15). Drivers by points: if/else 31 (60 pts), boolean chains 6, ternaries 2 (3 pts), match/switch 1 (nesting depth added 30). Most of this is not in the body itself: 7 of the 70 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 243, a function literal at line 79, renderRelationFields, …). 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.
useUpdateMany.useUpdateMany (cognitive 65) packages/core/src/hooks/data/useUpdateMany.ts:170— useUpdateMany.useUpdateMany has cognitive complexity 65 (threshold 15). Drivers by points: if/else 32 (53 pts), loops 2 (5 pts), boolean chains 4, ternaries 2 (3 pts) (nesting depth added 25). None of this is in the body itself: all 65 points belong to 13 function literals inside it that branch (lines 306, 603, 505, …). 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.
useUpdate.useUpdate (cognitive 58) packages/core/src/hooks/data/useUpdate.ts:169— useUpdate.useUpdate has cognitive complexity 58 (threshold 15). Drivers by points: if/else 31 (50 pts), ternaries 3 (4 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 21). None of this is in the body itself: all 58 points belong to 11 function literals inside it that branch (lines 297, 564, 467, …). 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.
use-react-table-return-type-update.useTableReturnTypeUpdate (cognitive 55) packages/codemod/src/transformations/v5/use-react-table-return-type-update.ts:4— use-react-table-return-type-update.useTableReturnTypeUpdate has cognitive complexity 55 (threshold 15). Drivers by points: if/else 16 (45 pts), boolean chains 10 (nesting depth added 29). None of this is in the body itself: all 55 points belong to 5 function literals inside it that branch (lines 9, 70, 34, …). 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.
create.renderer (cognitive 54) packages/inferencer/src/inferencers/antd/create.tsx:37— create.renderer has cognitive complexity 54 (threshold 15). Drivers by points: if/else 18 (27 pts), ternaries 9 (18 pts), boolean chains 8, match/switch 1 (nesting depth added 18). Most of this is not in the body itself: 7 of the 54 points are its own statements and the rest belongs to 9 function items inside it that branch (renderRelationFields, imageFields, basicInputFields, …). 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.
replace-imports.replaceImports (cognitive 52) packages/live-previews/src/utils/replace-imports.ts:12— replace-imports.replaceImports has cognitive complexity 52 (threshold 15). Drivers by points: if/else 15 (48 pts), ternaries 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 34). 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.
object.objectInfer (cognitive 49) packages/inferencer/src/field-inferencers/object.ts:6— object.objectInfer has cognitive complexity 49 (threshold 15). Drivers by points: ternaries 6 (26 pts), if/else 6 (17 pts), boolean chains 6 (nesting depth added 31). Of this number, 38 points are the body's own statements and 11 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.
fix-v4-deprecations.fixDeprecatedUseTableProps (cognitive 48) packages/codemod/src/transformations/v4/fix-v4-deprecations.ts:436— fix-v4-deprecations.fixDeprecatedUseTableProps has cognitive complexity 48 (threshold 15). Drivers by points: if/else 25 (36 pts), ternaries 5 (11 pts), boolean chains 1 (nesting depth added 17). None of this is in the body itself: all 48 points belong to 7 function literals inside it that branch (lines 446, 468, 646, …). 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.
index.useModalForm (cognitive 48) packages/react-hook-form/src/useModalForm/index.ts:89— index.useModalForm has cognitive complexity 48 (threshold 15). Drivers by points: if/else 21 (31 pts), boolean chains 13, ternaries 3 (4 pts) (nesting depth added 11). Most of this is not in the body itself: 7 of the 48 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 202, a function literal at line 265, a function literal at line 226, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
index.useModalForm (cognitive 44) packages/mantine/src/hooks/form/useModalForm/index.ts:81— index.useModalForm has cognitive complexity 44 (threshold 15). Drivers by points: if/else 19 (29 pts), boolean chains 11, ternaries 3 (4 pts) (nesting depth added 11). Most of this is not in the body itself: 7 of the 44 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 181, a function literal at line 253, a function literal at line 205, …). 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.
edit.renderer (cognitive 41) packages/inferencer/src/inferencers/mantine/edit.tsx:43— edit.renderer has cognitive complexity 41 (threshold 15). Drivers by points: if/else 18 (25 pts), boolean chains 8, ternaries 4 (7 pts), match/switch 1 (nesting depth added 10). Most of this is not in the body itself: 7 of the 41 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 83, textFields, numberFields, …). 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.
index.useRefineKbar::createActionWithResource (cognitive 39) packages/kbar/src/hooks/useRefineKbar/index.tsx:89— index.useRefineKbar::createActionWithResource has cognitive complexity 39 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 17 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
check-package.checkPackage (cognitive 39) packages/live-previews/src/utils/check-package.ts:1— check-package.checkPackage has cognitive complexity 39 (threshold 15). Drivers by points: if/else 27, boolean chains 12. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
index.ThemedSider (cognitive 39) packages/mui/src/components/themedLayout/sider/index.tsx:37— index.ThemedSider has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 13 (16 pts), if/else 10 (14 pts), boolean chains 9 (nesting depth added 7). Most of this is not in the body itself: 7 of the 39 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 105, a function literal at line 130, handleLogout, …). 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.
blog-toc.BlogTOC (cognitive 38) REDACTED:376— blog-toc.BlogTOC has cognitive complexity 38 (threshold 15). Drivers by points: if/else 19 (22 pts), boolean chains 8, ternaries 5 (7 pts), loops 1 (nesting depth added 5). Most of this is not in the body itself: 3 of the 38 points are its own statements and the rest belongs to 15 function literals inside it that branch (lines 538, 401, 416, …). 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.
index.Show (cognitive 38) packages/chakra-ui/src/components/crud/show/index.tsx:31— index.Show has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 17 (24 pts), boolean chains 10, if/else 3 (4 pts) (nesting depth added 8). Of this number, 33 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
create.renderer (cognitive 36) packages/inferencer/src/inferencers/headless/create.tsx:37— create.renderer has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 10 (16 pts), if/else 9 (12 pts), boolean chains 7, match/switch 1 (nesting depth added 9). Most of this is not in the body itself: 10 of the 36 points are its own statements and the rest belongs to 6 function items inside it that branch (basicInputFields, renderRelationFields, booleanFields, …). 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.
index.Edit (cognitive 35) packages/chakra-ui/src/components/crud/edit/index.tsx:34— index.Edit has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 16 (22 pts), boolean chains 9, if/else 3 (4 pts) (nesting depth added 7). Of this number, 30 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
use-query-and-result-fields-in-useCustom-hook.useQueryAndResultFieldsInUseCustomHook (cognitive 35) packages/codemod/src/transformations/v5/use-query-and-result-fields-in-useCustom-hook.ts:3— use-query-and-result-fields-in-useCustom-hook.useQueryAndResultFieldsInUseCustomHook has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (24 pts), boolean chains 6, ternaries 1 (5 pts) (nesting depth added 18). None of this is in the body itself: all 35 points belong to 3 function literals inside it that branch (lines 31, 61, 97). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
create.renderer (cognitive 35) packages/inferencer/src/inferencers/mantine/create.tsx:40— create.renderer has cognitive complexity 35 (threshold 15). Drivers by points: if/else 18 (25 pts), boolean chains 6, ternaries 2 (3 pts), match/switch 1 (nesting depth added 8). Most of this is not in the body itself: 7 of the 35 points are its own statements and the rest belongs to 11 function items inside it that branch (textFields, numberFields, renderRelationFields, …). 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.
landing-footer.LandingFooter (cognitive 34) documentation/src/refine-theme/landing-footer.tsx:14— landing-footer.LandingFooter has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 32, ternaries 2. Of this number, 24 points are the body's own statements and 10 belong to 4 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.
index.SearchPageContent (cognitive 34) documentation/src/theme/SearchPage/index.js:113— index.SearchPageContent has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 12, ternaries 10 (12 pts), if/else 7 (8 pts), error handling 1, match/switch 1 (nesting depth added 3). Most of this is not in the body itself: 11 of the 34 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 138, a function literal at line 190, a function literal at line 180, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
useModalForm.useModalForm (cognitive 34) packages/antd/src/hooks/form/useModalForm/useModalForm.ts:103— useModalForm.useModalForm has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 9, ternaries 3 (4 pts) (nesting depth added 10). Most of this is not in the body itself: 9 of the 34 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 207, 232, 327). 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.
mutation-result-to-mutation-property.mutationResultToMutationProperty (cognitive 34) packages/codemod/src/transformations/v5/mutation-result-to-mutation-property.ts:14— mutation-result-to-mutation-property.mutationResultToMutationProperty has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 7, ternaries 6, loops 1 (nesting depth added 10). None of this is in the body itself: all 34 points belong to 9 function literals inside it that branch (lines 32, 185, 231, …). 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.
edit.renderer (cognitive 34) packages/inferencer/src/inferencers/chakra-ui/edit.tsx:45— edit.renderer has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 6 (12 pts), boolean chains 8, match/switch 1 (nesting depth added 9). Most of this is not in the body itself: 7 of the 34 points are its own statements and the rest belongs to 7 function items inside it that branch (basicInputFields, a function literal at line 86, booleanFields, …). 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.
notificationProvider.useNotificationProvider (cognitive 34) packages/mantine/src/providers/notificationProvider.tsx:13— notificationProvider.useNotificationProvider has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (20 pts), ternaries 4 (12 pts), boolean chains 2 (nesting depth added 16). None of this is in the body itself: all 34 points belong to 5 function items inside it that branch (a function literal at line 39, addNotification, removeNotification, …). 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.
useDrawerForm.useDrawerForm (cognitive 33) packages/antd/src/hooks/form/useDrawerForm/useDrawerForm.ts:95— useDrawerForm.useDrawerForm has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 8, ternaries 4 (7 pts) (nesting depth added 10). Most of this is not in the body itself: 8 of the 33 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 179, 201, 307). 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.
doc-sidebar.SidebarCategory (cognitive 32) REDACTED:55— doc-sidebar.SidebarCategory has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 22, ternaries 7, if/else 3. Of this number, 29 points are the body's own statements and 3 belong to 2 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.
use-query-and-result-fields-in-useInfiniteList-hook.useQueryAndResultFieldsInUseInfiniteListHook (cognitive 31) packages/codemod/src/transformations/v5/use-query-and-result-fields-in-useInfiniteList-hook.ts:3— use-query-and-result-fields-in-useInfiniteList-hook.useQueryAndResultFieldsInUseInfiniteListHook has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (24 pts), boolean chains 7 (nesting depth added 14). None of this is in the body itself: all 31 points belong to 2 function literals inside it that branch (lines 28, 56). 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.
index.ThemedSider (cognitive 31) packages/mantine/src/components/themedLayout/sider/index.tsx:37— index.ThemedSider has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 13, ternaries 11, if/else 6 (7 pts) (nesting depth added 1). Most of this is not in the body itself: 13 of the 31 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 105, handleLogout, getDefaultExpandMenuItemsCB, …). 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.
separate-imports.separateImports (cognitive 30) packages/codemod/src/helpers/separate-imports.ts:23— separate-imports.separateImports has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (29 pts), loops 1 (nesting depth added 14). Most of this is not in the body itself: 2 of the 30 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 52, 99, 138, …). 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.
rename-useResource-useResourceParams.renameUseResourceToUseResourceParams (cognitive 30) packages/codemod/src/transformations/v5/rename-useResource-useResourceParams.ts:4— rename-useResource-useResourceParams.renameUseResourceToUseResourceParams has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 13 (nesting depth added 4). Most of this is not in the body itself: 3 of the 30 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 117, 91, 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.
create-data-provider.createDataProvider (cognitive 30) packages/rest/src/create-data-provider.ts:24— create-data-provider.createDataProvider has cognitive complexity 30 (threshold 15). Drivers by points: if/else 18 (26 pts), ternaries 4 (nesting depth added 8). Most of this is not in the body itself: 4 of the 30 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 313, 89, 148, …). 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.
useTable.useTable (cognitive 29) packages/antd/src/hooks/table/useTable/useTable.ts:57— useTable.useTable has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 7, ternaries 3 (6 pts) (nesting depth added 8). Most of this is not in the body itself: 1 of the 29 points is its own statement and the rest belongs to 7 function items inside it that branch (onChange, a function literal at line 195, onFinish, …). 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.
use-query-and-result-fields-in-list-hooks.useQueryAndResultFieldsInListHooks (cognitive 29) packages/codemod/src/transformations/v5/use-query-and-result-fields-in-list-hooks.ts:8— use-query-and-result-fields-in-list-hooks.useQueryAndResultFieldsInListHooks has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 6, loops 1 (nesting depth added 8). None of this is in the body itself: all 29 points belong to 7 function literals inside it that branch (lines 59, 24, 155, …). 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.renderer (cognitive 29) packages/inferencer/src/inferencers/headless/list.tsx:43— list.renderer has cognitive complexity 29 (threshold 15). Drivers by points: if/else 28 (47 pts), ternaries 23 (38 pts), boolean chains 15, match/switch 1 (nesting depth added 34). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (list.renderer::renderRelationFields) 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.
index.ThemedSider (cognitive 28) packages/chakra-ui/src/components/themedLayout/sider/index.tsx:34— index.ThemedSider has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 12, ternaries 9, if/else 6 (7 pts) (nesting depth added 1). Most of this is not in the body itself: 8 of the 28 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 79, handleLogout, getDefaultExpandMenuItemsCB, …). 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.
create.renderer (cognitive 28) packages/inferencer/src/inferencers/chakra-ui/create.tsx:44— create.renderer has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 7, ternaries 4 (7 pts), match/switch 1 (nesting depth added 6). Most of this is not in the body itself: 7 of the 28 points are its own statements and the rest belongs to 7 function items inside it that branch (basicInputFields, booleanFields, a function literal at line 79, …). 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.
index.Show (cognitive 28) packages/mui/src/components/crud/show/index.tsx:44— index.Show has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 14 (20 pts), boolean chains 8 (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.
install.install (cognitive 27) packages/codemod/src/helpers/install.ts:33— install.install has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (23 pts), ternaries 2 (4 pts) (nesting depth added 12). None of this is in the body itself: all 27 points belong to 2 function literals inside it that branch (lines 49, 109). 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.
create.renderer::renderRelationFields (cognitive 27) packages/inferencer/src/inferencers/mui/create.tsx:100— create.renderer::renderRelationFields has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 10 (24 pts), boolean chains 2, if/else 1 (nesting depth added 14). 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.
index.Show (cognitive 27) packages/mantine/src/components/crud/show/index.tsx:36— index.Show has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 15 (21 pts), boolean chains 6 (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.
chart.ChartTooltipContent (cognitive 27) REDACTED:108— chart.ChartTooltipContent has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 14, ternaries 6 (9 pts), if/else 4 (nesting depth added 3). Most of this is not in the body itself: 4 of the 27 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 183, 132). 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.
index.ThemedSider (cognitive 26) packages/antd/src/components/themedLayout/sider/index.tsx:34— index.ThemedSider has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 10, boolean chains 6 (nesting depth added 1). Most of this is not in the body itself: 8 of the 26 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 65, handleLogout, renderClosingIcons, …). 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.
useDeleteMany.useDeleteMany (cognitive 25) packages/core/src/hooks/data/useDeleteMany.ts:140— useDeleteMany.useDeleteMany has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 2 (4 pts), boolean chains 3, ternaries 2 (3 pts) (nesting depth added 8). None of this is in the body itself: all 25 points belong to 11 function literals inside it that branch (lines 475, 261, 345, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
antd.ThemedTitle (cognitive 25) packages/live-previews/src/scope/antd.tsx:23— antd.ThemedTitle has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (17 pts), error handling 1 (4 pts), boolean chains 3, ternaries 1 (nesting depth added 14). Most of this is not in the body itself: 4 of the 25 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 38, 36, 52). 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.
chakra.ThemedTitle (cognitive 25) packages/live-previews/src/scope/chakra.tsx:85— chakra.ThemedTitle has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (17 pts), error handling 1 (4 pts), boolean chains 3, ternaries 1 (nesting depth added 14). Most of this is not in the body itself: 4 of the 25 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 100, 98, 114). 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.
mantine.ThemedTitle (cognitive 25) packages/live-previews/src/scope/mantine.tsx:15— mantine.ThemedTitle has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (17 pts), error handling 1 (4 pts), boolean chains 3, ternaries 1 (nesting depth added 14). Most of this is not in the body itself: 4 of the 25 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 30, 28, 44). 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.
mui.ThemedTitle (cognitive 25) packages/live-previews/src/scope/mui.tsx:69— mui.ThemedTitle has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (17 pts), error handling 1 (4 pts), boolean chains 3, ternaries 1 (nesting depth added 14). Most of this is not in the body itself: 4 of the 25 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 84, 82, 98). 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.
data-table.getCommonStyles (cognitive 25) packages/refine-ui/registry/new-york/refine-ui/data-table/data-table.tsx:261— data-table.getCommonStyles has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 13, ternaries 11 (12 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
use-query-and-result-fields-in-useOne-hook.useQueryAndResultFieldsInUseOneHook (cognitive 24) packages/codemod/src/transformations/v5/use-query-and-result-fields-in-useOne-hook.ts:7— use-query-and-result-fields-in-useOne-hook.useQueryAndResultFieldsInUseOneHook has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 6, ternaries 1 (2 pts), loops 1 (nesting depth added 7). None of this is in the body itself: all 24 points belong to 4 function literals inside it that branch (lines 23, 14, 106, …). 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.
getListHelpers.operatorMapper (cognitive 24) packages/graphql/src/utils/getListHelpers.ts:39— getListHelpers.operatorMapper has cognitive complexity 24 (threshold 15). Drivers by points: if/else 20 (24 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
preview.Preview (cognitive 24) packages/live-previews/pages/preview.tsx:15— preview.Preview has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 8, ternaries 1 (nesting depth added 6). Of this number, 20 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.operatorMapper (cognitive 24) packages/nestjs-query/src/utils/index.ts:69— index.operatorMapper has cognitive complexity 24 (threshold 15). Drivers by points: if/else 20 (24 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
index.useForm (cognitive 24) packages/react-hook-form/src/useForm/index.ts:82— index.useForm has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 3, loops 1 (nesting depth added 5). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 153, 257, 303, …). 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.
data-table-filter.DataTableFilterCombobox (cognitive 24) packages/refine-ui/registry/new-york/refine-ui/data-table/data-table-filter.tsx:249— data-table-filter.DataTableFilterCombobox has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 9 (14 pts), boolean chains 5, if/else 5 (nesting depth added 5). None of this is in the body itself: all 24 points belong to 6 function literals inside it that branch (lines 268, 279, 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.
doc-sidebar.SidebarLink (cognitive 23) REDACTED:326— doc-sidebar.SidebarLink has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 17, if/else 4 (5 pts), ternaries 1 (nesting depth added 1). Of this number, 18 points are the body's own statements and 5 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.
index.Edit (cognitive 23) packages/antd/src/components/crud/edit/index.tsx:36— index.Edit has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 13 (17 pts), boolean chains 6 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
index.Show (cognitive 23) packages/antd/src/components/crud/show/index.tsx:33— index.Show has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 13 (17 pts), boolean chains 6 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
index.Create (cognitive 23) packages/chakra-ui/src/components/crud/create/index.tsx:18— index.Create has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 11 (15 pts), boolean chains 4, if/else 3 (4 pts) (nesting depth added 5). Of this number, 18 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
use-form-query-and-mutation-result.renameUseFormQueryResultAndMutationResult (cognitive 23) packages/codemod/src/transformations/rename-query-and-mutation-result/use-form-query-and-mutation-result.ts:7— use-form-query-and-mutation-result.renameUseFormQueryResultAndMutationResult has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (18 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 12). None of this is in the body itself: all 23 points belong to 3 function items inside it that branch (renameProperties, a function literal at line 43, a function literal at line 41). 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.
use-table-query-result.renameUseTableQueryResult (cognitive 23) packages/codemod/src/transformations/rename-query-and-mutation-result/use-table-query-result.ts:7— use-table-query-result.renameUseTableQueryResult has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (18 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 12). None of this is in the body itself: all 23 points belong to 3 function items inside it that branch (renameProperties, a function literal at line 37, a function literal at line 35). 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.
use-simple-list-query-result.renameUseSimpleListQueryResult (cognitive 23) packages/codemod/src/transformations/rename-query-and-mutation-result/use-simple-list-query-result.ts:6— use-simple-list-query-result.renameUseSimpleListQueryResult has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (18 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 12). None of this is in the body itself: all 23 points belong to 3 function items inside it that branch (renameProperties, a function literal at line 35, a function literal at line 33). 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.
resizable-pane.ResizablePane (cognitive 23) packages/devtools/src/components/resizable-pane.tsx:28— resizable-pane.ResizablePane has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 9, boolean chains 8, if/else 6. Of this number, 17 points are the body's own statements and 6 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.
list.renderer (cognitive 23) packages/inferencer/src/inferencers/mui/list.tsx:47— list.renderer has cognitive complexity 23 (threshold 15). Drivers by points: if/else 34 (54 pts), ternaries 24 (43 pts), boolean chains 21, match/switch 1 (nesting depth added 39). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 2 other methods here (list.renderer::renderRelationFields, list.renderer::basicFields) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
generateFilter.generateFilter (cognitive 23) packages/supabase/src/utils/generateFilter.ts:4— generateFilter.generateFilter has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (19 pts), boolean chains 3, match/switch 1 (nesting depth added 12). Most of this is not in the body itself: 3 of the 23 points are its own statements and the rest belongs to one function literal inside it that branches (line 50). 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.
list.renderer (cognitive 22) packages/inferencer/src/inferencers/mantine/list.tsx:54— list.renderer has cognitive complexity 22 (threshold 15). Drivers by points: if/else 33 (53 pts), ternaries 16 (28 pts), boolean chains 13, match/switch 1 (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (list.renderer::renderRelationFields) 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.
index.SandpackBase (cognitive 21) documentation/src/components/sandpack/index.tsx:70— index.SandpackBase has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 10 (15 pts), boolean chains 6 (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.
tutorial-sandpack.SandpackRightSide (cognitive 21) documentation/src/refine-theme/tutorial-sandpack.tsx:433— tutorial-sandpack.SandpackRightSide has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 7 (11 pts), if/else 6 (7 pts), boolean chains 3 (nesting depth added 5). Of this number, 14 points are the body's own statements and 7 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.
fix-v4-deprecations.fixDeprecatedReactTableProps (cognitive 21) packages/codemod/src/transformations/v4/fix-v4-deprecations.ts:228— fix-v4-deprecations.fixDeprecatedReactTableProps has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15, ternaries 4 (5 pts), boolean chains 1 (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 4 function literals inside it that branch (lines 252, 275, 322, …). 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.
package-item.PackageItem (cognitive 21) packages/devtools-ui/src/components/package-item.tsx:21— package-item.PackageItem has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 13, if/else 4, match/switch 2, error handling 1, ternaries 1. Of this number, 14 points are the body's own statements and 7 belong to 4 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.
list.renderer (cognitive 21) packages/inferencer/src/inferencers/chakra-ui/list.tsx:69— list.renderer has cognitive complexity 21 (threshold 15). Drivers by points: if/else 33 (53 pts), ternaries 15 (27 pts), boolean chains 13, match/switch 1 (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (list.renderer::renderRelationFields) 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.
doc-breadcrumbs.DocBreadcrumbs (cognitive 20) documentation/src/refine-theme/doc-breadcrumbs.tsx:16— doc-breadcrumbs.DocBreadcrumbs has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 6 (9 pts), boolean chains 7, if/else 2 (3 pts), loops 1 (nesting depth added 4). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 90, 53, 40, …). 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.
fix-v4-deprecations.fixUseSelectHasPaginationToPaginationMode (cognitive 20) packages/codemod/src/transformations/v4/fix-v4-deprecations.ts:871— fix-v4-deprecations.fixUseSelectHasPaginationToPaginationMode has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 2 (6 pts), boolean chains 4 (nesting depth added 6). None of this is in the body itself: all 20 points belong to 2 function literals inside it that branch (lines 881, 905). 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.
index.ConfigSuccessPage (cognitive 20) packages/core/src/components/pages/config-success/index.tsx:49— index.ConfigSuccessPage has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 11 (14 pts), if/else 6 (nesting depth added 3). Of this number, 14 points are the body's own statements and 6 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.
index.SharedCodeViewer (cognitive 20) packages/inferencer/src/components/shared-code-viewer/index.tsx:9— index.SharedCodeViewer has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 4 (nesting depth added 4). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 36, 64, 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.
index.useForm (cognitive 20) packages/mantine/src/hooks/form/useForm/index.ts:85— index.useForm has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3, ternaries 1 (2 pts), loops 1 (nesting depth added 6). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 152, 224, 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.
antd.SvgAntd (cognitive 19) documentation/src/assets/integration-icons/antd.tsx:4— antd.SvgAntd has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 11, boolean chains 8. 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.
tutorial-sandpack.TutorialSandpack (cognitive 19) documentation/src/refine-theme/tutorial-sandpack.tsx:57— tutorial-sandpack.TutorialSandpack has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, if/else 6 (7 pts), ternaries 4 (nesting depth added 1). Of this number, 12 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.
welcome-page-import-from-core.welcomePageImportFromCore (cognitive 19) packages/codemod/src/transformations/v5/welcome-page-import-from-core.ts:14— welcome-page-import-from-core.welcomePageImportFromCore has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 6 (nesting depth added 6). None of this is in the body itself: all 19 points belong to 4 function literals inside it that branch (lines 26, 56, 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.
list.renderer (cognitive 19) packages/inferencer/src/inferencers/antd/list.tsx:45— list.renderer has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 27 (58 pts), if/else 34 (55 pts), boolean chains 20, match/switch 1 (nesting depth added 52). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (list.renderer::renderRelationFields) 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.
index.transformCrudFiltersToFilterModel (cognitive 19) packages/mui/src/definitions/dataGrid/index.ts:189— index.transformCrudFiltersToFilterModel has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 5 (13 pts), if/else 3 (4 pts), boolean chains 2 (nesting depth added 9). 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 206, 221). 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.
banner-modal.BannerModal (cognitive 18) documentation/src/components/banner/banner-modal.tsx:32— banner-modal.BannerModal has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 11, if/else 6 (7 pts) (nesting depth added 1). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 53, 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.
useSimpleList.useSimpleList (cognitive 18) packages/antd/src/hooks/useSimpleList/useSimpleList.ts:44— useSimpleList.useSimpleList has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 6). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 4 function items inside it that branch (a function literal at line 131, onFinish, onChange, …). 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.
projectScripts.resolveBin (cognitive 18) packages/cli/src/commands/runner/projectScripts.ts:5— projectScripts.resolveBin has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), error handling 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
useMany.useMany (cognitive 18) packages/core/src/hooks/data/useMany.ts:103— useMany.useMany has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 11, ternaries 2 (4 pts), if/else 3 (nesting depth added 2). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 219, 231, 190, …). 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.
index.useForm.onFinish (cognitive 18) packages/core/src/hooks/form/index.ts:214— index.useForm.onFinish has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7, ternaries 7, boolean chains 4. None of this is in the body itself: all 18 points belong to 2 function literals inside it that branch (lines 228, 289). 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.
index.useTable (cognitive 18) packages/core/src/hooks/useTable/index.ts:182— index.useTable has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, ternaries 4 (5 pts), if/else 4 (nesting depth added 1). Of this number, 14 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
generateFilters.mergeHasuraFilters (cognitive 18) packages/hasura/src/utils/generateFilters.ts:183— generateFilters.mergeHasuraFilters has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 7, ternaries 1 (nesting depth added 2). Of this number, 11 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, 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.
index.useInferFetch (cognitive 18) packages/inferencer/src/use-infer-fetch/index.tsx:17— index.useInferFetch has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 4, error handling 1 (nesting depth added 6). None of this is in the body itself: all 18 points belong to 2 function literals inside it that branch (lines 45, 120). 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.
dataProvider.DataProvider (cognitive 18) packages/strapi-v4/src/dataProvider.ts:12— dataProvider.DataProvider has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (10 pts), error handling 4, ternaries 2, boolean chains 1, match/switch 1 (nesting depth added 1). None of this is in the body itself: all 18 points belong to 8 function literals inside it that branch (lines 241, 16, 95, …). 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.
doc-thumbs-up-down-feedback-widget.DocThumbsUpDownFeedbackWidget (cognitive 17) documentation/src/refine-theme/doc-thumbs-up-down-feedback-widget.tsx:36— doc-thumbs-up-down-feedback-widget.DocThumbsUpDownFeedbackWidget has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, if/else 5, ternaries 1. Of this number, 12 points are the body's own statements and 5 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.
index.action (cognitive 17) packages/cli/src/commands/swizzle/index.tsx:70— index.action has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (13 pts), ternaries 2, boolean chains 1, error handling 1 (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 2 function literals inside it that branch (lines 193, 78). 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.
index.getProjectType (cognitive 17) packages/cli/src/utils/project/index.ts:4— index.getProjectType has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 7, error handling 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
refine2-to-refine3.updateRefineImports (cognitive 17) packages/codemod/src/transformations/refine2-to-refine3.ts:239— refine2-to-refine3.updateRefineImports has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 1 (2 pts) (nesting depth added 8). Of this number, 11 points are the body's own statements and 6 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.
index.useExport.triggerExport (cognitive 17) packages/core/src/hooks/export/index.ts:153— index.useExport.triggerExport has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (6 pts), ternaries 3 (6 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
add-package-drawer.AddPackageDrawer (cognitive 17) packages/devtools-ui/src/components/add-package-drawer.tsx:25— add-package-drawer.AddPackageDrawer has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, if/else 3 (4 pts), ternaries 3, match/switch 2 (nesting depth added 1). Of this number, 11 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
index.useTable (cognitive 17) packages/react-table/src/useTable/index.ts:49— index.useTable has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 4, ternaries 3 (4 pts) (nesting depth added 3). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 135, 152, 123, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
index.liveProvider.subscribe (cognitive 17) packages/supabase/src/liveProvider/index.ts:14— index.liveProvider.subscribe has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 4, loops 1, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 3 function items inside it that branch (listener, mapFilter, a function literal at line 58). 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.
blog-plugin.injectSitemapLastmod (cognitive 16) documentation/plugins/blog-plugin.js:550— blog-plugin.injectSitemapLastmod has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), error handling 1 (2 pts), loops 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.
index.CategoryNavBarSelect (cognitive 16) documentation/src/components/blog/category-nav-bar/index.tsx:44— index.CategoryNavBarSelect has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 13, if/else 3. Of this number, 13 points are the body's own statements and 3 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.
template-detail.TemplatesDetail (cognitive 16) documentation/src/refine-theme/template-detail.tsx:50— template-detail.TemplatesDetail has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (9 pts), boolean chains 7 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
tutorial-paginator.TutorialPaginator (cognitive 16) documentation/src/refine-theme/tutorial-paginator.tsx:116— tutorial-paginator.TutorialPaginator has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 10, boolean chains 6. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
index.mapAntdSorterToCrudSorting (cognitive 16) packages/antd/src/definitions/table/index.ts:43— index.mapAntdSorterToCrudSorting has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 3 (8 pts), if/else 4 (6 pts), boolean chains 2 (nesting depth added 7). 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.
create-providers.createProviders (cognitive 16) packages/cli/src/commands/add/sub-commands/provider/create-providers.ts:20— create-providers.createProviders has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), error handling 2 (6 pts) (nesting depth added 7). None of this is in the body itself: all 16 points belong to 2 function literals inside it that branch (lines 53, 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.
create-resources.createResources (cognitive 16) packages/cli/src/commands/add/sub-commands/resource/create-resources.ts:24— create-resources.createResources has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 4, ternaries 1 (nesting depth added 2). 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 63, 41, 116). 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.
remove-v3LegacyAuthProviderCompatible-from-auth-hooks.removeV3LegacyAuthProviderCompatibleFromAuthHooks (cognitive 16) packages/codemod/src/transformations/v5/remove-v3LegacyAuthProviderCompatible-from-auth-hooks.ts:18— remove-v3LegacyAuthProviderCompatible-from-auth-hooks.removeV3LegacyAuthProviderCompatibleFromAuthHooks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 4 (nesting depth added 6). None of this is in the body itself: all 16 points belong to 2 function literals inside it that branch (lines 28, 38). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
use-select-query-result.renameUseSelectQueryResult (cognitive 16) packages/codemod/src/transformations/rename-query-and-mutation-result/use-select-query-result.ts:7— use-select-query-result.renameUseSelectQueryResult has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 2 (nesting depth added 7). None of this is in the body itself: all 16 points belong to 3 function items inside it that branch (renameProperties, a function literal at line 47, a function literal at line 45). 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.
use-show-query-result.renameUseShowQueryResult (cognitive 16) packages/codemod/src/transformations/rename-query-and-mutation-result/use-show-query-result.ts:7— use-show-query-result.renameUseShowQueryResult has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 2 (nesting depth added 7). None of this is in the body itself: all 16 points belong to 3 function items inside it that branch (renameProperties, a function literal at line 36, a function literal at line 34). 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.
useList.useList (cognitive 16) packages/core/src/hooks/data/useList.ts:121— useList.useList has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, ternaries 3 (5 pts), if/else 4 (nesting depth added 2). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 280, 296, 209). 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.
index.Create (cognitive 16) packages/mui/src/components/crud/create/index.tsx:33— index.Create has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 9 (14 pts), boolean chains 2 (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.
Cross-context type BaseKey (core → access-control-permify) examples/access-control-permify/src/authz/permifyClient.ts:10— BaseKey (context core) is exposed in access-control-permify's public surface via PermifyClient.isAuthorized — couples the contexts.
Cross-context type CrudOperators (core → with-meta-properties) examples/with-meta-properties/src/rest-data-provider/utils/mapOperator.ts:3— CrudOperators (context core) is exposed in with-meta-properties's public surface via mapOperator.mapOperator — couples the contexts.
Cross-context type Headers (core → with-remix-antd) examples/with-remix-antd/app/entry.server.tsx:5— Headers (context core) is exposed in with-remix-antd's public surface via entry.server.handleRequest — couples the contexts.
Cross-context type Headers (core → with-remix-auth) examples/with-remix-auth/app/entry.server.tsx:5— Headers (context core) is exposed in with-remix-auth's public surface via entry.server.handleRequest — couples the contexts.
Cross-context type Headers (core → with-remix-headless) examples/with-remix-headless/app/entry.server.tsx:5— Headers (context core) is exposed in with-remix-headless's public surface via entry.server.handleRequest — couples the contexts.
Cross-context type Headers (core → with-remix-material-ui) examples/with-remix-material-ui/app/entry.server.tsx:9— Headers (context core) is exposed in with-remix-material-ui's public surface via entry.server.handleRequest — couples the contexts.
Cross-context type Headers (core → with-remix-vite-headless) examples/with-remix-vite-headless/app/entry.server.tsx:5— Headers (context core) is exposed in with-remix-vite-headless's public surface via entry.server.handleRequest — couples the contexts.
Cross-context type SortOrder (core → antd) packages/antd/src/definitions/table/index.ts:22— SortOrder (context core) is exposed in antd's public surface via index.getDefaultSortOrder — couples the contexts.
Cross-context type CrudOperators (core → antd) packages/antd/src/definitions/table/index.ts:35— CrudOperators (context core) is exposed in antd's public surface via index.getDefaultFilter — couples the contexts.
Cross-context type CrudFilter (core → antd) packages/antd/src/definitions/table/index.ts:35— CrudFilter (context core) is exposed in antd's public surface via index.getDefaultFilter — couples the contexts.
Cross-context type CrudFilter (core → graphql) packages/graphql/src/utils/getListHelpers.ts:126— CrudFilter (context core) is exposed in graphql's public surface via getListHelpers.buildFilters — couples the contexts.
Cross-context type CrudOperators (core → hasura) packages/hasura/src/utils/generateFilters.ts:34— CrudOperators (context core) is exposed in hasura's public surface via HasuraCrudOperators.HasuraCrudOperators — couples the contexts.
Cross-context type CrudOperators (core → medusa) packages/medusa/src/utils/mapOperator.ts:3— CrudOperators (context core) is exposed in medusa's public surface via mapOperator.mapOperator — couples the contexts.
Cross-context type CrudFilter (core → medusa) packages/medusa/src/utils/generateFilter.ts:4— CrudFilter (context core) is exposed in medusa's public surface via generateFilter.generateFilter — couples the contexts.
Cross-context type CrudOperators (core → nestjsx-crud) packages/nestjsx-crud/src/utils/mapOperator.ts:4— CrudOperators (context core) is exposed in nestjsx-crud's public surface via mapOperator.mapOperator — couples the contexts.
Cross-context type CrudFilter (core → nestjsx-crud) packages/nestjsx-crud/src/utils/handleFilter.ts:12— CrudFilter (context core) is exposed in nestjsx-crud's public surface via handleFilter.createSearchQuery — couples the contexts.
Cross-context type CrudFilter (core → rest) packages/rest/src/data-providers/nestjsx-crud/utils/handleFilter.ts:12— CrudFilter (context core) is exposed in rest's public surface via handleFilter.createSearchQuery — couples the contexts.
Cross-context type CrudOperators (core → simple-rest) packages/simple-rest/src/utils/mapOperator.ts:3— CrudOperators (context core) is exposed in simple-rest's public surface via mapOperator.mapOperator — couples the contexts.
Cross-context type CrudOperators (core → strapi-v4) packages/strapi-v4/src/utils/mapOperator.ts:3— CrudOperators (context core) is exposed in strapi-v4's public surface via mapOperator.mapOperator — couples the contexts.
Cross-context type CrudOperators (core → supabase) packages/supabase/src/utils/mapOperator.ts:3— CrudOperators (context core) is exposed in supabase's public surface via mapOperator.mapOperator — couples the contexts.
Cross-context type CrudFilter (core → supabase) packages/supabase/src/utils/generateFilter.ts:4— CrudFilter (context core) is exposed in supabase's public surface via generateFilter.generateFilter — couples the contexts.
IC1 · Incompleteness & stubs· Guard cannot change the result · ×1
Guard cannot change the result — returns what the code already falls through to REDACTED:57— The guard above `return 9;` also returns `9`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
M1 · Documentation (README)· README may be stale · ×1
README may be stale — 23 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
No structured logging — No logging call was found in the 2045 JavaScript/TypeScript production file(s) this check read across 39 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
Outbound HTTP without resilience packages/devtools-server/src/feed/get-feed.ts:47— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Duplication concentrated across 37 sibling directories (221 clone groups) packages/chakra-ui/refine.config.js:1— 221 duplicated blocks under packages/ have copies in at least two of the sibling directories ably, airtable, antd, appwrite, chakra-ui, cli (+31 more sibling(s) not listed) — 142 of them are reported below, and 79 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 221 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 221 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 221 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 5 sibling directories (39 clone groups) packages/inferencer/src/inferencers/chakra-ui/show.tsx:50— 39 duplicated blocks under packages/inferencer/src/inferencers/ have copies in at least two of the sibling directories antd, chakra-ui, headless, mantine, mui — 34 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 39 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 39 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 39 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 (10 clone groups) packages/mantine/src/components/buttons/list/index.tsx:31— 10 duplicated blocks under packages/mantine/src/components/buttons/ have copies in at least two of the sibling directories clone, create, edit, export, import, list (+2 more sibling(s) not listed) — 5 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 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.
Duplication concentrated across 4 sibling directories (7 clone groups) packages/mui/src/components/pages/auth/components/forgotPassword/index.tsx:61— 7 duplicated blocks under packages/mui/src/components/pages/auth/components/ have copies in at least two of the sibling directories forgotPassword, login, register, updatePassword — 6 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 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 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 (5 clone groups) packages/core/src/hooks/auth/useUpdateIdentity/index.ts:45— 5 duplicated blocks under packages/core/src/hooks/auth/ have copies in at least two of the sibling directories useForgotPassword, useGetIdentity, useLogin, useLogout, usePermissions, useRegister (+2 more sibling(s) not listed) — 3 of them are reported below, and 2 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 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 9 sibling directories (5 clone groups) packages/mui/src/components/buttons/clone/index.tsx:37— 5 duplicated blocks under packages/mui/src/components/buttons/ have copies in at least two of the sibling directories clone, create, delete, export, import, list (+3 more sibling(s) not listed) — 4 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (505 matched lines × 2 locations) · ×1
Duplicated block with local edits (505 matched lines × 2 locations) packages/inferencer/src/inferencers/chakra-ui/show.tsx:50— packages/inferencer/src/inferencers/chakra-ui/show.tsx:50 · packages/inferencer/src/inferencers/mantine/show.tsx:51 — the two spans are one implementation copied and then locally edited — 2088 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 (484 matched lines × 2 locations) · ×1
Duplicated block with local edits (484 matched lines × 2 locations) packages/inferencer/src/inferencers/antd/show.tsx:52— packages/inferencer/src/inferencers/antd/show.tsx:52 · packages/inferencer/src/inferencers/mui/show.tsx:52 — the two spans are one implementation copied and then locally edited — 1990 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 (389 matched lines × 2 locations) · ×1
Duplicated block with local edits (389 matched lines × 2 locations) packages/core/src/hooks/data/useUpdate.ts:61— packages/core/src/hooks/data/useUpdate.ts:61 · packages/core/src/hooks/data/useUpdateMany.ts:62 — the two spans are one implementation copied and then locally edited — 1917 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 (330 matched lines × 2 locations) · ×1
Duplicated block with local edits (330 matched lines × 2 locations) packages/core/src/hooks/data/useDelete.ts:50— packages/core/src/hooks/data/useDelete.ts:50 · packages/core/src/hooks/data/useDeleteMany.ts:50 — the two spans are one implementation copied and then locally edited — 1529 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 (257 identical lines × 2 files) packages/inferencer/src/inferencers/chakra-ui/list.tsx:28— packages/inferencer/src/inferencers/chakra-ui/list.tsx:28 · packages/inferencer/src/inferencers/mantine/list.tsx:13 — these 2 files are line-for-line copies of one another — 257 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 (233 matched lines × 2 locations) · ×1
Duplicated block with local edits (233 matched lines × 2 locations) packages/inferencer/src/inferencers/mantine/create.tsx:47— packages/inferencer/src/inferencers/mantine/create.tsx:47 · packages/inferencer/src/inferencers/mantine/edit.tsx:55 — the two spans are one implementation copied and then locally edited — 1081 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 (219 matched lines × 2 locations) · ×1
Duplicated block with local edits (219 matched lines × 2 locations) packages/refine-ui/registry/new-york/refine-ui/form/sign-in-form.tsx:24— packages/refine-ui/registry/new-york/refine-ui/form/sign-in-form.tsx:24 · packages/refine-ui/registry/new-york/refine-ui/form/sign-up-form.tsx:26 — the two spans are one implementation copied and then locally edited — 706 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 (218 matched lines × 2 locations) · ×1
Duplicated block with local edits (218 matched lines × 2 locations) packages/core/src/hooks/data/useCreate.ts:65— packages/core/src/hooks/data/useCreate.ts:65 · packages/core/src/hooks/data/useCreateMany.ts:47 — the two spans are one implementation copied and then locally edited — 1025 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 (217 identical lines × 3 files) packages/chakra-ui/refine.config.js:1— packages/chakra-ui/refine.config.js:1 · packages/mantine/refine.config.js:1 · packages/mui/refine.config.js:1 — these 3 files are line-for-line copies of one another — 217 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 (202 matched lines × 2 locations) · ×1
Duplicated block with local edits (202 matched lines × 2 locations) packages/mantine/src/hooks/form/useModalForm/index.ts:61— packages/mantine/src/hooks/form/useModalForm/index.ts:61 · packages/react-hook-form/src/useModalForm/index.ts:52 — the two spans are one implementation copied and then locally edited — 864 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (201 matched lines × 2 locations) · ×1
Duplicated block with local edits (201 matched lines × 2 locations) packages/inferencer/src/inferencers/headless/create.tsx:46— packages/inferencer/src/inferencers/headless/create.tsx:46 · packages/inferencer/src/inferencers/headless/edit.tsx:52 — the two spans are one implementation copied and then locally edited — 794 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 (196 matched lines × 2 locations) · ×1
Duplicated block with local edits (196 matched lines × 2 locations) packages/antd/src/hooks/form/useDrawerForm/useDrawerForm.ts:28— packages/antd/src/hooks/form/useDrawerForm/useDrawerForm.ts:28 · packages/antd/src/hooks/form/useModalForm/useModalForm.ts:63 — the two spans are one implementation copied and then locally edited — 839 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 (170 matched lines × 2 locations) · ×1
Duplicated block with local edits (170 matched lines × 2 locations) packages/chakra-ui/src/components/pages/auth/components/login/index.tsx:34— packages/chakra-ui/src/components/pages/auth/components/login/index.tsx:34 · packages/chakra-ui/src/components/pages/auth/components/register/index.tsx:31 — the two spans are one implementation copied and then locally edited — 706 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 (161 matched lines × 2 locations) · ×1
Duplicated block with local edits (161 matched lines × 2 locations) packages/inferencer/src/inferencers/chakra-ui/edit.tsx:52— packages/inferencer/src/inferencers/chakra-ui/edit.tsx:52 · packages/inferencer/src/inferencers/headless/edit.tsx: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.
R10 · Code Duplication· Duplicated block with local edits (127 matched lines × 2 locations) · ×1
Duplicated block with local edits (127 matched lines × 2 locations) packages/mantine/src/components/pages/auth/components/login/index.tsx:71— packages/mantine/src/components/pages/auth/components/login/index.tsx:71 · packages/mantine/src/components/pages/auth/components/register/index.tsx:67 — the two spans are one implementation copied and then locally edited — 571 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 (126 identical lines × 2 files) packages/chakra-ui/src/components/crud/edit/index.tsx:1— packages/chakra-ui/src/components/crud/edit/index.tsx:1 · packages/chakra-ui/src/components/crud/show/index.tsx:1 — these 2 files are line-for-line copies of one another — 126 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 (116 lines × 2 locations) packages/refine-ui/registry/new-york/ui/context-menu.tsx:110— packages/refine-ui/registry/new-york/ui/context-menu.tsx:110 · packages/refine-ui/registry/new-york/ui/menubar.tsx:87 — 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 (112 matched lines × 2 locations) · ×1
Duplicated block with local edits (112 matched lines × 2 locations) packages/antd/src/components/pages/auth/components/forgotPassword/index.tsx:54— packages/antd/src/components/pages/auth/components/forgotPassword/index.tsx:54 · packages/antd/src/components/pages/auth/components/updatePassword/index.tsx:51 — 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.
R10 · Code Duplication· Duplicated block with local edits (107 matched lines × 2 locations) · ×1
Duplicated block with local edits (107 matched lines × 2 locations) packages/mui/src/components/pages/auth/components/forgotPassword/index.tsx:61— packages/mui/src/components/pages/auth/components/forgotPassword/index.tsx:61 · packages/mui/src/components/pages/auth/components/updatePassword/index.tsx:61 — the two spans are one implementation copied and then locally edited — 386 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (100 matched lines × 2 locations) · ×1
Duplicated block with local edits (100 matched lines × 2 locations) packages/inferencer/src/inferencers/chakra-ui/edit.tsx:171— packages/inferencer/src/inferencers/chakra-ui/edit.tsx:171 · packages/inferencer/src/inferencers/mui/edit.tsx:218 — the two spans are one implementation copied and then locally edited — 423 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 (97 matched lines × 2 locations) · ×1
Duplicated block with local edits (97 matched lines × 2 locations) packages/antd/src/components/crud/edit/index.tsx:63— packages/antd/src/components/crud/edit/index.tsx:63 · packages/antd/src/components/crud/show/index.tsx:56 — the two spans are one implementation copied and then locally edited — 441 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 (96 lines × 2 locations) packages/refine-ui/registry/new-york/ui/dropdown-menu.tsx:131— packages/refine-ui/registry/new-york/ui/dropdown-menu.tsx:131 · packages/refine-ui/registry/new-york/ui/menubar.tsx:149 — 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 (90 lines × 2 locations) packages/inferencer/src/inferencers/antd/show.tsx:173— packages/inferencer/src/inferencers/antd/show.tsx:173 · packages/inferencer/src/inferencers/chakra-ui/show.tsx:185 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (88 matched lines × 2 locations) · ×1
Duplicated block with local edits (88 matched lines × 2 locations) packages/core/src/hooks/data/useList.ts:104— packages/core/src/hooks/data/useList.ts:104 · packages/core/src/hooks/data/useMany.ts:85 — the two spans are one implementation copied and then locally edited — 413 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 (87 lines × 2 locations) packages/inferencer/src/inferencers/mui/create.tsx:87— packages/inferencer/src/inferencers/mui/create.tsx:87 · packages/inferencer/src/inferencers/mui/edit.tsx:104 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication· Duplicated block with local edits (84 matched lines × 2 locations) · ×1
Duplicated block with local edits (84 matched lines × 2 locations) packages/antd/src/hooks/table/useTable/useTable.ts:29— packages/antd/src/hooks/table/useTable/useTable.ts:29 · packages/antd/src/hooks/useSimpleList/useSimpleList.ts:16 — the two spans are one implementation copied and then locally edited — 420 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 (84 lines × 3 locations) packages/chakra-ui/src/components/crud/create/index.tsx:89— packages/chakra-ui/src/components/crud/create/index.tsx:89 · packages/chakra-ui/src/components/crud/edit/index.tsx:175 · packages/chakra-ui/src/components/crud/show/index.tsx:168 — 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.
Duplicated block (83 lines × 2 locations) packages/graphql/src/utils/getListHelpers.ts:42— packages/graphql/src/utils/getListHelpers.ts:42 · packages/nestjs-query/src/utils/index.ts:72 — 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.
Boundary violation [package:third-party-deep-import] packages/supabase/src/index.ts:2— packages/supabase/src/index.ts:2 imports @supabase/supabase-js/dist/main/lib/types, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Complex function checkPackage (cyclomatic 57, cognitive 39) packages/live-previews/src/utils/check-package.ts:1— checkPackage has cyclomatic complexity 57 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function Show (cyclomatic 38, cognitive 36) · ×1
Complex function Show (cyclomatic 38, cognitive 36) packages/mui/src/components/crud/show/index.tsx:44— Show has cyclomatic complexity 38 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 35, cognitive 9) packages/mui/src/definitions/dataGrid/index.ts:105— (anonymous) has cyclomatic complexity 35 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 createActionWithResource (cyclomatic 33, cognitive 39) packages/kbar/src/hooks/useRefineKbar/index.tsx:89— createActionWithResource has cyclomatic complexity 33 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function Edit (cyclomatic 31, cognitive 30) packages/mui/src/components/crud/edit/index.tsx:47— Edit has cyclomatic complexity 31 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function Show (cyclomatic 31, cognitive 29) · ×1
Complex function Show (cyclomatic 31, cognitive 29) packages/chakra-ui/src/components/crud/show/index.tsx:31— Show has cyclomatic complexity 31 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 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 Edit (cyclomatic 30, cognitive 29) packages/antd/src/components/crud/edit/index.tsx:36— Edit has cyclomatic complexity 30 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function Show (cyclomatic 29, cognitive 28) · ×1
Complex function Show (cyclomatic 29, cognitive 28) packages/antd/src/components/crud/show/index.tsx:33— Show has cyclomatic complexity 29 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function Show (cyclomatic 29, cognitive 27) · ×1
Complex function Show (cyclomatic 29, cognitive 27) packages/mantine/src/components/crud/show/index.tsx:36— Show has cyclomatic complexity 29 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 Edit (cyclomatic 28, cognitive 27) packages/chakra-ui/src/components/crud/edit/index.tsx:34— Edit 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 renderer (cyclomatic 28, cognitive 27) packages/inferencer/src/inferencers/headless/list.tsx:43— renderer 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 useTable (cyclomatic 28, cognitive 26) packages/core/src/hooks/useTable/index.ts:182— useTable has cyclomatic complexity 28 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function Edit (cyclomatic 28, cognitive 26) packages/mantine/src/components/crud/edit/index.tsx:37— Edit has cyclomatic complexity 28 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 28, cognitive 19) packages/core/src/definitions/helpers/handleRefineOptions/index.ts:44— (anonymous) has cyclomatic complexity 28 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 27, cognitive 78) packages/inferencer/src/use-relation-fetch/index.ts:47— (anonymous) has cyclomatic complexity 27 and cognitive complexity 78; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs 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 renderer (cyclomatic 27, cognitive 25) packages/inferencer/src/inferencers/mui/list.tsx:47— renderer has cyclomatic complexity 27 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 getCommonStyles (cyclomatic 25, cognitive 24) packages/refine-ui/registry/new-york/refine-ui/data-table/data-table.tsx:261— getCommonStyles 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 renderer (cyclomatic 25, cognitive 23) packages/inferencer/src/inferencers/mantine/list.tsx:54— renderer has cyclomatic complexity 25 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 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 renderer (cyclomatic 24, cognitive 22) packages/inferencer/src/inferencers/chakra-ui/list.tsx:69— renderer has cyclomatic complexity 24 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.
R3 · Large Files· packages/codemod/src/transformations/v4/fix-v4-deprecations.ts · ×1
packages/codemod/src/transformations/v4/fix-v4-deprecations.ts: 979 lines of code packages/codemod/src/transformations/v4/fix-v4-deprecations.ts:1— packages/codemod/src/transformations/v4/fix-v4-deprecations.ts has 979 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/refine-ui/registry/new-york/refine-ui/data-table/data-table-filter.tsx · ×1
packages/refine-ui/registry/new-york/refine-ui/data-table/data-table-filter.tsx: 920 lines of code packages/refine-ui/registry/new-york/refine-ui/data-table/data-table-filter.tsx:1— packages/refine-ui/registry/new-york/refine-ui/data-table/data-table-filter.tsx has 920 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/inferencer/src/inferencers/chakra-ui/list.tsx · ×1
packages/inferencer/src/inferencers/chakra-ui/list.tsx: 910 lines of code packages/inferencer/src/inferencers/chakra-ui/list.tsx:1— packages/inferencer/src/inferencers/chakra-ui/list.tsx has 910 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/inferencer/src/inferencers/headless/list.tsx · ×1
packages/inferencer/src/inferencers/headless/list.tsx: 846 lines of code packages/inferencer/src/inferencers/headless/list.tsx:1— packages/inferencer/src/inferencers/headless/list.tsx has 846 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/inferencer/src/inferencers/mantine/list.tsx · ×1
packages/inferencer/src/inferencers/mantine/list.tsx: 821 lines of code packages/inferencer/src/inferencers/mantine/list.tsx:1— packages/inferencer/src/inferencers/mantine/list.tsx has 821 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/inferencer/src/inferencers/mui/list.tsx · ×1
packages/inferencer/src/inferencers/mui/list.tsx: 765 lines of code packages/inferencer/src/inferencers/mui/list.tsx:1— packages/inferencer/src/inferencers/mui/list.tsx has 765 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/inferencer/src/inferencers/headless/show.tsx · ×1
packages/inferencer/src/inferencers/headless/show.tsx: 686 lines of code packages/inferencer/src/inferencers/headless/show.tsx:1— packages/inferencer/src/inferencers/headless/show.tsx has 686 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/refine-ui/registry/new-york/ui/sidebar.tsx · ×1
packages/refine-ui/registry/new-york/ui/sidebar.tsx: 672 lines of code packages/refine-ui/registry/new-york/ui/sidebar.tsx:1— packages/refine-ui/registry/new-york/ui/sidebar.tsx has 672 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/inferencer/src/inferencers/mui/show.tsx · ×1
packages/inferencer/src/inferencers/mui/show.tsx: 663 lines of code packages/inferencer/src/inferencers/mui/show.tsx:1— packages/inferencer/src/inferencers/mui/show.tsx has 663 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/inferencer/src/inferencers/chakra-ui/show.tsx · ×1
packages/inferencer/src/inferencers/chakra-ui/show.tsx: 651 lines of code packages/inferencer/src/inferencers/chakra-ui/show.tsx:1— packages/inferencer/src/inferencers/chakra-ui/show.tsx 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/inferencer/src/inferencers/mantine/show.tsx · ×1
packages/inferencer/src/inferencers/mantine/show.tsx: 644 lines of code packages/inferencer/src/inferencers/mantine/show.tsx:1— packages/inferencer/src/inferencers/mantine/show.tsx has 644 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/core/src/hooks/data/useUpdateMany.ts · ×1
packages/core/src/hooks/data/useUpdateMany.ts: 640 lines of code packages/core/src/hooks/data/useUpdateMany.ts:1— packages/core/src/hooks/data/useUpdateMany.ts has 640 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/codemod/src/transformations/refine2-to-refine3.ts · ×1
packages/codemod/src/transformations/refine2-to-refine3.ts: 614 lines of code packages/codemod/src/transformations/refine2-to-refine3.ts:1— packages/codemod/src/transformations/refine2-to-refine3.ts 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/inferencer/src/inferencers/antd/show.tsx · ×1
packages/inferencer/src/inferencers/antd/show.tsx: 610 lines of code packages/inferencer/src/inferencers/antd/show.tsx:1— packages/inferencer/src/inferencers/antd/show.tsx has 610 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/core/src/hooks/data/useUpdate.ts · ×1
packages/core/src/hooks/data/useUpdate.ts: 609 lines of code packages/core/src/hooks/data/useUpdate.ts:1— packages/core/src/hooks/data/useUpdate.ts has 609 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/inferencer/src/components/shared-code-viewer/index.tsx · ×1
packages/inferencer/src/components/shared-code-viewer/index.tsx: 566 lines of code packages/inferencer/src/components/shared-code-viewer/index.tsx:1— packages/inferencer/src/components/shared-code-viewer/index.tsx has 566 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/inferencer/src/inferencers/antd/list.tsx · ×1
packages/inferencer/src/inferencers/antd/list.tsx: 564 lines of code packages/inferencer/src/inferencers/antd/list.tsx:1— packages/inferencer/src/inferencers/antd/list.tsx has 564 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/hasura/src/dataProvider/index.ts · ×1
packages/hasura/src/dataProvider/index.ts: 550 lines of code packages/hasura/src/dataProvider/index.ts:1— packages/hasura/src/dataProvider/index.ts has 550 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/inferencer/src/inferencers/mui/edit.tsx · ×1
packages/inferencer/src/inferencers/mui/edit.tsx: 487 lines of code packages/inferencer/src/inferencers/mui/edit.tsx:1— packages/inferencer/src/inferencers/mui/edit.tsx has 487 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/core/src/hooks/data/useDeleteMany.ts · ×1
packages/core/src/hooks/data/useDeleteMany.ts: 484 lines of code packages/core/src/hooks/data/useDeleteMany.ts:1— packages/core/src/hooks/data/useDeleteMany.ts has 484 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/inferencer/src/inferencers/antd/edit.tsx · ×1
packages/inferencer/src/inferencers/antd/edit.tsx: 482 lines of code packages/inferencer/src/inferencers/antd/edit.tsx:1— packages/inferencer/src/inferencers/antd/edit.tsx has 482 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/devtools-server/src/packages/get-available-packages.ts · ×1
packages/devtools-server/src/packages/get-available-packages.ts: 477 lines of code packages/devtools-server/src/packages/get-available-packages.ts:1— packages/devtools-server/src/packages/get-available-packages.ts has 477 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/src/components/themedLayout/sider/index.tsx · ×1
packages/mui/src/components/themedLayout/sider/index.tsx: 459 lines of code packages/mui/src/components/themedLayout/sider/index.tsx:1— packages/mui/src/components/themedLayout/sider/index.tsx has 459 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/core/src/hooks/data/useDelete.ts · ×1
packages/core/src/hooks/data/useDelete.ts: 457 lines of code packages/core/src/hooks/data/useDelete.ts:1— packages/core/src/hooks/data/useDelete.ts has 457 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/inferencer/src/inferencers/mantine/edit.tsx · ×1
packages/inferencer/src/inferencers/mantine/edit.tsx: 444 lines of code packages/inferencer/src/inferencers/mantine/edit.tsx:1— packages/inferencer/src/inferencers/mantine/edit.tsx has 444 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/core/src/components/pages/config-error/index.tsx · ×1
packages/core/src/components/pages/config-error/index.tsx: 440 lines of code packages/core/src/components/pages/config-error/index.tsx:1— packages/core/src/components/pages/config-error/index.tsx has 440 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/core/src/contexts/data/types.ts · ×1
packages/core/src/contexts/data/types.ts: 435 lines of code packages/core/src/contexts/data/types.ts:1— packages/core/src/contexts/data/types.ts has 435 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/inferencer/src/inferencers/headless/edit.tsx · ×1
packages/inferencer/src/inferencers/headless/edit.tsx: 435 lines of code packages/inferencer/src/inferencers/headless/edit.tsx:1— packages/inferencer/src/inferencers/headless/edit.tsx has 435 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/inferencer/src/inferencers/chakra-ui/edit.tsx · ×1
packages/inferencer/src/inferencers/chakra-ui/edit.tsx: 430 lines of code packages/inferencer/src/inferencers/chakra-ui/edit.tsx:1— packages/inferencer/src/inferencers/chakra-ui/edit.tsx has 430 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/devtools-ui/src/components/monitor-details.tsx · ×1
packages/devtools-ui/src/components/monitor-details.tsx: 421 lines of code packages/devtools-ui/src/components/monitor-details.tsx:1— packages/devtools-ui/src/components/monitor-details.tsx has 421 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/devtools-ui/src/components/sidebar.tsx · ×1
packages/devtools-ui/src/components/sidebar.tsx: 419 lines of code packages/devtools-ui/src/components/sidebar.tsx:1— packages/devtools-ui/src/components/sidebar.tsx has 419 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/nestjs-query/src/dataProvider/index.ts · ×1
packages/nestjs-query/src/dataProvider/index.ts: 416 lines of code packages/nestjs-query/src/dataProvider/index.ts:1— packages/nestjs-query/src/dataProvider/index.ts has 416 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/devtools-ui/src/components/add-package-drawer.tsx · ×1
packages/devtools-ui/src/components/add-package-drawer.tsx: 408 lines of code packages/devtools-ui/src/components/add-package-drawer.tsx:1— packages/devtools-ui/src/components/add-package-drawer.tsx has 408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/core/src/hooks/useTable/index.ts · ×1
packages/core/src/hooks/useTable/index.ts: 406 lines of code packages/core/src/hooks/useTable/index.ts:1— packages/core/src/hooks/useTable/index.ts has 406 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Dead file (~1207 LoC) packages/codemod/src/definitions/separated-imports/mui.ts— no import path from any entry point (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/v4/separate-imports-mui.ts) — 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 (~1157 LoC) packages/codemod/src/transformations/v4/fix-v4-deprecations.ts— no import path from any entry point (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/refine3-to-refine4.ts) — 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 (~782 LoC) packages/codemod/src/definitions/separated-imports/chakra.ts— no import path from any entry point (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/v4/separate-imports-chakra.ts) — 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 (~680 LoC) packages/codemod/src/transformations/refine2-to-refine3.ts— no import path from any entry point (460 application, 140 tooling, 892 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 (~536 LoC) packages/codemod/src/definitions/separated-imports/mantine.ts— no import path from any entry point (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/v4/separate-imports-mantine.ts) — 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 (~354 LoC) REDACTED— no import path from any entry point (460 application, 140 tooling, 892 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 (~296 LoC) packages/codemod/src/transformations/refine1-to-refine2.ts— no import path from any entry point (460 application, 140 tooling, 892 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 (~278 LoC) packages/inferencer/src/inferencers/headless/code-viewer.tsx— no import path from any entry point (460 application, 140 tooling, 892 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~276 LoC) packages/refine-ui/registry/new-york/ui/menubar.tsx— no import path from any entry point (460 application, 140 tooling, 892 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 (~252 LoC) packages/refine-ui/registry/new-york/ui/context-menu.tsx— no import path from any entry point (460 application, 140 tooling, 892 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 (~241 LoC) packages/refine-ui/registry/new-york/ui/carousel.tsx— no import path from any entry point (460 application, 140 tooling, 892 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 (~197 LoC) packages/codemod/src/definitions/separated-imports/react-table.ts— no import path from any entry point (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/v4/separate-imports-react-table.ts) — 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 (~176 LoC) packages/codemod/src/definitions/separated-imports/antd.ts— no import path from any entry point (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/v4/separate-imports-antd.ts) — 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 (~168 LoC) packages/refine-ui/registry/new-york/ui/navigation-menu.tsx— no import path from any entry point (460 application, 140 tooling, 892 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 (~157 LoC) packages/refine-ui/registry/new-york/ui/alert-dialog.tsx— no import path from any entry point (460 application, 140 tooling, 892 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 (~151 LoC) packages/inferencer/src/inferencers/mui/code-viewer.tsx— no import path from any entry point (460 application, 140 tooling, 892 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 (~138 LoC) packages/codemod/src/definitions/separated-imports/react-hook-form.ts— no import path from any entry point (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/v4/separate-imports-react-hook-form.ts) — 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 (~137 LoC) packages/inferencer/src/inferencers/chakra-ui/code-viewer.tsx— no import path from any entry point (460 application, 140 tooling, 892 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 (~136 LoC) packages/inferencer/src/inferencers/mantine/code-viewer.tsx— no import path from any entry point (460 application, 140 tooling, 892 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 (~132 LoC) packages/refine-ui/registry/new-york/ui/drawer.tsx— no import path from any entry point (460 application, 140 tooling, 892 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 (~128 LoC) packages/refine-ui/registry/new-york/ui/pagination.tsx— no import path from any entry point (460 application, 140 tooling, 892 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 (~124 LoC) packages/codemod/src/transformations/refine3-to-refine4.ts— no import path from any entry point (460 application, 140 tooling, 892 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 (~118 LoC) packages/codemod/src/transformations/v4/separate-imports-antd.ts— no import path from any entry point (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/refine3-to-refine4.ts) — 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 (~116 LoC) packages/inferencer/src/inferencers/antd/code-viewer.tsx— no import path from any entry point (460 application, 140 tooling, 892 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 (~104 LoC) packages/codemod/src/transformations/use-data-grid-columns.ts— no import path from any entry point (460 application, 140 tooling, 892 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 (~100 LoC) packages/codemod/src/transformations/v4/replace-pankod-imports-with-refinedev.ts— no import path from any entry point (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/refine3-to-refine4.ts) — 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 (~95 LoC) packages/devtools-ui/src/components/input.tsx— no import path from any entry point (460 application, 140 tooling, 892 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 (~94 LoC) packages/codemod/src/transformations/v4/use-menu-to-core.ts— no import path from any entry point (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/refine3-to-refine4.ts) — 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 (~85 LoC) packages/codemod/src/transformations/v4/router-to-legacy-router.ts— no import path from any entry point (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/refine3-to-refine4.ts) — 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 (~69 LoC) packages/codemod/src/definitions/separated-imports/react-router-v6.ts— no import path from any entry point (460 application, 140 tooling, 892 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/codemod/src/transformations/v4/separate-imports-react-router-v6.ts) — 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) packages/refine-ui/registry/new-york/ui/slider.tsx— no import path from any entry point (460 application, 140 tooling, 892 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 (~62 LoC) packages/codemod/src/transformations/antd4-to-antd5.ts— no import path from any entry point (460 application, 140 tooling, 892 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 'esbuild' packages/shared/dayjs-esm-replace-plugin.ts:1— Imported only as a TYPE and declared in no reachable REDACTED. 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 REDACTED.
Unused dependency '@arethetypeswrong/cli' — Declared in the root REDACTED 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 '@lerna/filter-options' — Declared in the root REDACTED 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 'pidtree' — Declared in the root REDACTED 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.
Deprecated: abab REDACTED:2221— abab 2.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native atob() and btoa() 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: domexception REDACTED:3193— domexception 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native DOMException instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: figgy-pudding REDACTED:3459— figgy-pudding 3.5.2 is resolved in REDACTED and is marked deprecated by its publisher: "This module is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: stable REDACTED:6096— stable 0.1.8 is resolved in REDACTED and is marked deprecated by its publisher: "Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: trim REDACTED:6361— trim 0.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "Use String.prototype.trim() instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: uuid REDACTED:6625— uuid 3.4.0 is resolved in REDACTED and is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-class-properties REDACTED:14747— @babel/plugin-proposal-class-properties 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-class-properties instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-nullish-coalescing-operator REDACTED:14760— @babel/plugin-proposal-nullish-coalescing-operator 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-nullish-coalescing-operator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-numeric-separator REDACTED:14767— @babel/plugin-proposal-numeric-separator 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-numeric-separator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-object-rest-spread REDACTED:14774— @babel/plugin-proposal-object-rest-spread 7.20.7 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-object-rest-spread instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-optional-chaining REDACTED:14781— @babel/plugin-proposal-optional-chaining 7.21.0 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-optional-chaining instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-private-methods REDACTED:14788— @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: @babel/plugin-proposal-private-property-in-object REDACTED:14801— @babel/plugin-proposal-private-property-in-object 7.21.11 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-property-in-object instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @effect/schema REDACTED:16300— @effect/schema 0.66.5 is resolved in REDACTED and is marked deprecated by its publisher: "this package has been merged into the main effect package". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @graphql-tools/prisma-loader REDACTED:17232— @graphql-tools/prisma-loader 8.0.3 is resolved in REDACTED and is marked deprecated by its publisher: "This package was intended to be used with an older versions of Prisma.\nThe newer versions of Prisma has a different approach to GraphQL integration.\nTherefore, this package is no longer needed and has been deprecated and removed.\nLearn more: https://www.prisma.io/graphql". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @handsontable/react REDACTED:17289— @handsontable/react 12.4.0 is resolved in REDACTED and is marked deprecated by its publisher: "Handsontable for React is now available as @handsontable/react-wrapper.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/config-array REDACTED:17328— @humanwhocodes/config-array 0.11.14 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/config-array instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/object-schema REDACTED:17337— @humanwhocodes/object-schema 2.0.3 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/object-schema instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @lerna/collect-updates REDACTED:17662— @lerna/collect-updates 6.4.1 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @lerna/create REDACTED:17667— @lerna/create 8.1.2 is resolved in REDACTED and is marked deprecated by its publisher: "This package is an implementation detail of Lerna and is no longer published separately.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @lerna/describe-ref REDACTED:17672— @lerna/describe-ref 6.4.1 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @lerna/filter-packages REDACTED:17682— @lerna/filter-packages 6.4.1 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @lerna/validation-error REDACTED:17687— @lerna/validation-error 6.4.1 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @mui/base REDACTED:17806— @mui/base 5.0.0-beta.61 is resolved in REDACTED and is marked deprecated by its publisher: "This package has been replaced by @base-ui/react". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @ungap/structured-clone REDACTED:20893— @ungap/structured-clone 1.2.0 is resolved in REDACTED and is marked deprecated by its publisher: "Potential CWE-502 - Update to 1.3.1 or higher". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Orphaned file packages/inferencer/src/inferencers/antd/edit.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/inferencer/src/inferencers/headless/edit.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/inferencer/src/inferencers/chakra-ui/edit.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/core/src/hooks/form/index.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/inferencer/src/inferencers/headless/create.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/refine-ui/registry/new-york/refine-ui/data-table/data-table.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file 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/refine-ui/registry/new-york/refine-ui/form/sign-in-form.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/refine-ui/registry/new-york/refine-ui/form/sign-up-form.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/refine-ui/registry/new-york/refine-ui/layout/layout-01/sidebar.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/refine-ui/registry/new-york/ui/menubar.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/refine-ui/registry/new-york/ui/dropdown-menu.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/refine-ui/registry/new-york/ui/context-menu.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/codemod/src/transformations/v5/mutation-result-to-mutation-property.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/core/src/hooks/form/types.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/devtools/src/components/selectable-elements.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/refine-ui/registry/new-york/ui/navigation-menu.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/codemod/src/transformations/v5/rename-useResource-useResourceParams.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/refine-ui/registry/new-york/ui/select.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/refine-ui/registry/new-york/ui/carousel.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/refine-ui/registry/new-york/refine-ui/layout/error-component.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/refine-ui/registry/new-york/ui/command.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/codemod/src/transformations/v5/use-react-table-return-type-update.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/refine-ui/registry/new-york/ui/sheet.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/refine-ui/registry/new-york/ui/drawer.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Outdated (npm): @dnd-kit/modifiers examples/app-crm-minimal/REDACTED:21— @dnd-kit/modifiers is pinned at 6.0.1; registry.npmjs.org publishes 9.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @dnd-kit/sortable examples/app-crm-minimal/REDACTED:22— @dnd-kit/sortable is pinned at 7.0.2; registry.npmjs.org publishes 10.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @handsontable/react examples/table-handson/REDACTED:13— @handsontable/react is pinned at 12.4.0; registry.npmjs.org publishes 16.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): @mantine/core examples/auth-mantine/REDACTED:14— @mantine/core is pinned at 5.10.5; registry.npmjs.org publishes 9.7.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @mantine/dates examples/form-mantine-use-steps-form/REDACTED:15— @mantine/dates is pinned at 5.10.5; registry.npmjs.org publishes 9.7.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @mantine/dropzone examples/upload-mantine-base64/REDACTED:15— @mantine/dropzone is pinned at 5.10.5; registry.npmjs.org publishes 9.7.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @mantine/form examples/auth-mantine/REDACTED:15— @mantine/form is pinned at 5.10.5; registry.npmjs.org publishes 9.7.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @mantine/hooks examples/auth-mantine/REDACTED:16— @mantine/hooks is pinned at 5.10.5; registry.npmjs.org publishes 9.7.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @mantine/notifications examples/auth-mantine/REDACTED:17— @mantine/notifications is pinned at 5.10.5; registry.npmjs.org publishes 9.7.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @mui/icons-material examples/blog-material-ui-datagrid/REDACTED:27— @mui/icons-material is pinned at 6.1.6; 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/lab examples/auth-material-ui/REDACTED:27— @mui/lab is pinned at 6.0.0-beta.14; registry.npmjs.org publishes 9.0.0-beta.10 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @mui/material examples/auth-material-ui/REDACTED:28— @mui/material is pinned at 6.1.7; 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/system packages/mui/REDACTED:41— @mui/system is pinned at 6.1.6; 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/utils examples/refine-hr-ce/REDACTED:29— @mui/utils is pinned at 6.1.6; 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): @npmcli/package-json packages/cli/REDACTED:37— @npmcli/package-json is pinned at 5.2.0; registry.npmjs.org publishes 8.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): appwrite packages/appwrite/REDACTED:43— appwrite is pinned at 15.0.0; registry.npmjs.org publishes 29.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): boxen packages/cli/REDACTED:39— boxen is pinned at 5.1.2; registry.npmjs.org publishes 9.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): camelcase packages/cli/REDACTED:40— camelcase is pinned at 6.3.0; registry.npmjs.org publishes 10.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): commander packages/cli/REDACTED:45— commander is pinned at 9.4.1; registry.npmjs.org publishes 15.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): conf packages/cli/REDACTED:46— conf is pinned at 10.2.0; registry.npmjs.org publishes 16.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): cross-env documentation/REDACTED:102— cross-env is pinned at 7.0.3; registry.npmjs.org publishes 10.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): execa packages/cli/REDACTED:51— execa is pinned at 5.1.1; registry.npmjs.org publishes 10.2.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): framer-motion documentation/REDACTED:63— framer-motion is pinned at 7.10.3; registry.npmjs.org publishes 14.6.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): globby packages/cli/REDACTED:54— globby is pinned at 11.1.0; registry.npmjs.org publishes 16.2.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): got packages/create-refine-app/REDACTED:25— got is pinned at 11.8.6; registry.npmjs.org publishes 16.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Mock-dominated test: uses only the first realtime filter and warns when multiple filters are provided packages/supabase/test/liveProvider/index.spec.ts:25— This test sets up 5 test doubles (for example `vi
.spyOn`) against 0 real object(s) of its own, and its only verification is 7 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: does not warn when a single realtime filter is provided packages/supabase/test/liveProvider/index.spec.ts:75— This test sets up 4 test doubles (for example `vi
.spyOn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should navigate to the first resource with list action packages/remix-router/src/navigate-to-resource.test.tsx:34— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should navigate to the specified resource packages/remix-router/src/navigate-to-resource.test.tsx:57— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should navigate to fallbackTo when no resource is found packages/remix-router/src/navigate-to-resource.test.tsx:75— This test sets up 3 test doubles (for example `vi
.spyOn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should not navigate when getToPath returns undefined packages/remix-router/src/navigate-to-resource.test.tsx:106— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should only navigate once using ref packages/remix-router/src/navigate-to-resource.test.tsx:121— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should compose multiple transformers into one packages/inferencer/src/compose-transformers/index.test.ts:5— This test sets up 4 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.
Mock-dominated test: should compose multiple inferencers into one packages/inferencer/src/compose-inferencers/index.test.ts:5— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 6 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should return routerProvider parse function result packages/core/src/hooks/router/use-router-misuse-warning/index.spec.ts:14— This test sets up 3 test doubles (for example `vi.spyOn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: useSubscribe enabled and all types packages/core/src/hooks/live/useSubscription/index.spec.ts:10— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: useSubscribe enabled false packages/core/src/hooks/live/useSubscription/index.spec.ts:49— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: useSubscribe spesific type packages/core/src/hooks/live/useSubscription/index.spec.ts:73— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: useSubscribe calls unsubscribe on unmount packages/core/src/hooks/live/useSubscription/index.spec.ts:113— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: useResourceSubscription enabled and all types packages/core/src/hooks/live/useResourceSubscription/index.spec.ts:33— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: useResourceSubscription liveMode off packages/core/src/hooks/live/useResourceSubscription/index.spec.ts:89— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: useResourceSubscription liveMode on context off, params auto packages/core/src/hooks/live/useResourceSubscription/index.spec.ts:122— This test sets up 6 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: useResourceSubscription calls unsubscribe on unmount packages/core/src/hooks/live/useResourceSubscription/index.spec.ts:195— This test sets up 4 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.
Mock-dominated test: should invalidate queries based on queryKey created with `identifier` packages/core/src/hooks/live/useResourceSubscription/index.spec.ts:233— This test sets up 5 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.
Mock-dominated test: publish event packages/core/src/hooks/live/usePublish/index.spec.ts:10— This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should return translate, setLocale and getLocale packages/core/src/hooks/i18n/useTranslation.spec.tsx:22— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should life-cycle methods works packages/core/src/hooks/data/useCreate.spec.tsx:1836— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should life-cycle methods works packages/core/src/hooks/data/useCreateMany.spec.tsx:1740— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should life-cycle methods works packages/core/src/hooks/data/useUpdate.spec.tsx:2405— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should life-cycle methods works packages/core/src/hooks/data/useUpdateMany.spec.tsx:2700— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 4 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.
Duplicated predicate packages/chakra-ui/src/components/crud/list/index.tsx:41— `!!resource?.create || createButtonPropsFromProps` appears character-identically in 3 files — packages/chakra-ui/src/components/crud/list/index.tsx, packages/mantine/src/components/crud/list/index.tsx, packages/mui/src/components/crud/list/index.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate documentation/plugins/docgen.js:198— `!declaration.fileName.includes("node_modules") || declaration.fileName.includes("@refinedev")` appears character-identically in 2 files — documentation/plugins/docgen.js, documentation/plugins/docgen.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/devtools-ui/src/components/add-package-drawer.tsx:143— `!delayedVisible && "re-pointer-events-none"` appears character-identically in 2 files — packages/devtools-ui/src/components/add-package-drawer.tsx, packages/devtools-ui/src/components/modal.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/inferencer/src/inferencers/antd/list.tsx:481— `!field.multiple && Array.isArray(field.accessor)` appears character-identically in 5 files — packages/inferencer/src/inferencers/antd/list.tsx, packages/inferencer/src/inferencers/chakra-ui/list.tsx, packages/inferencer/src/inferencers/headless/list.tsx, packages/inferencer/src/inferencers/mantine/list.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 documentation/src/refine-theme/tutorial-item-content.tsx:20— `!frontMatter.hide_title && typeof contentTitle === "undefined"` appears character-identically in 2 files — documentation/src/refine-theme/tutorial-item-content.tsx, documentation/src/theme/DocItem/Content/index.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 documentation/src/refine-theme/doc-toc-mobile.tsx:76— `!isActive && "hover:bg-zinc-100 dark:hover:bg-[#303035]"` appears character-identically in 2 files — documentation/src/refine-theme/doc-toc-mobile.tsx, 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 documentation/src/refine-theme/doc-toc-mobile.tsx:75— `!isActive && "text-zinc-700 dark:text-zinc-300"` appears character-identically in 2 files — documentation/src/refine-theme/doc-toc-mobile.tsx, 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 documentation/src/refine-theme/blog-tabs.tsx:88— `!isSelected && "text-zinc-500 dark:text-zinc-400"` appears character-identically in 2 files — documentation/src/refine-theme/blog-tabs.tsx, documentation/src/refine-theme/common-tabs.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/codemod/src/transformations/rename-query-and-mutation-result/use-form-query-and-mutation-result.ts:13— `"shorthand" in prop && "key" in prop && "name" in prop.key` appears character-identically in 5 files — packages/codemod/src/transformations/rename-query-and-mutation-result/use-form-query-and-mutation-result.ts, packages/codemod/src/transformations/rename-query-and-mutation-result/use-select-query-result.ts, packages/codemod/src/transformations/rename-query-and-mutation-result/use-show-query-result.ts, packages/codemod/src/transformations/rename-query-and-mutation-result/use-simple-list-query-result.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/cli/src/commands/whoami/index.ts:24— `(await getInstalledRefinePackages()) || []` appears character-identically in 2 files — packages/cli/src/commands/whoami/index.ts, packages/cli/src/telemetry/index.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 documentation/plugins/docgen.js:14— `(op === "optionalAccess" || op === "optionalCall") && value == null` appears character-identically in 3 files — documentation/plugins/docgen.js, documentation/plugins/thumbs-up-down-feedback-widget.js, documentation/plugins/tutorial-navigation.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/codemod/src/transformations/v5/mutation-result-to-mutation-property.ts:44— `(prop.type === "ObjectProperty" || prop.type === "Property") && prop.key?.type === "Identifier"` appears character-identically in 3 files — packages/codemod/src/transformations/v5/mutation-result-to-mutation-property.ts, packages/codemod/src/transformations/v5/use-query-and-result-fields-in-list-hooks.ts, packages/codemod/src/transformations/v5/use-query-and-result-fields-in-useOne-hook.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/codemod/src/transformations/v5/use-query-and-result-fields-in-useCustom-hook.ts:63— `(prop.type === "Property" || prop.type === "ObjectProperty") && prop.key?.type === "Identifier"` appears character-identically in 3 files — packages/codemod/src/transformations/v5/use-query-and-result-fields-in-useCustom-hook.ts, packages/codemod/src/transformations/v5/use-query-and-result-fields-in-useInfiniteList-hook.ts, packages/codemod/src/transformations/v5/use-react-table-return-type-update.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/graphql/src/utils/getListHelpers.ts:131— `Array.isArray(f.value) && f.value.length === 0` appears character-identically in 2 files — packages/graphql/src/utils/getListHelpers.ts, packages/nestjs-query/src/utils/index.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/inferencer/src/inferencers/antd/list.tsx:242— `Array.isArray(field.accessor) || field.multiple` appears character-identically in 5 files — packages/inferencer/src/inferencers/antd/list.tsx, packages/inferencer/src/inferencers/chakra-ui/list.tsx, packages/inferencer/src/inferencers/headless/list.tsx, packages/inferencer/src/inferencers/mantine/list.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/nestjsx-crud/src/utils/handleFilter.ts:39— `Array.isArray(filters) && filters.length > 0` appears character-identically in 2 files — packages/nestjsx-crud/src/utils/handleFilter.ts, packages/rest/src/data-providers/nestjsx-crud/utils/handleFilter.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 REDACTED:74— `React.isValidElement(item) && item.props?.mdxType === "summary"` appears character-identically in 2 files — REDACTED, documentation/src/refine-theme/common-details.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/antd/src/components/crud/edit/index.tsx:147— `action !== "list" && typeof action !== "undefined"` appears character-identically in 6 files — packages/antd/src/components/crud/edit/index.tsx, packages/antd/src/components/crud/show/index.tsx, packages/chakra-ui/src/components/crud/edit/index.tsx, packages/chakra-ui/src/components/crud/show/index.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/chakra-ui/src/components/crud/create/index.tsx:63— `action !== "list" || typeof action !== "undefined"` appears character-identically in 2 files — packages/chakra-ui/src/components/crud/create/index.tsx, packages/mui/src/components/crud/create/index.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/antd/src/hooks/form/useDrawerForm/useDrawerForm.ts:256— `autoSaveProps.status === "success" && autoSave?.invalidateOnClose` appears character-identically in 3 files — packages/antd/src/hooks/form/useDrawerForm/useDrawerForm.ts, packages/antd/src/hooks/form/useModalForm/useModalForm.ts, packages/mantine/src/hooks/form/useModalForm/index.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/devtools-ui/src/components/add-package-drawer.tsx:144— `delayedVisible && "re-pointer-events-auto"` appears character-identically in 2 files — packages/devtools-ui/src/components/add-package-drawer.tsx, packages/devtools-ui/src/components/modal.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/shared/remove-test-ids-plugin.ts:14— `el.path.endsWith(".cjs") || el.path.endsWith(".mjs") || el.path.endsWith(".js")` appears character-identically in 2 files — packages/shared/remove-test-ids-plugin.ts, packages/shared/tabler-cjs-replace-plugin.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/shared/dayjs-esm-replace-plugin.ts:13— `el.path.endsWith(".mjs") || el.path.endsWith(".js")` appears character-identically in 4 files — packages/shared/dayjs-esm-replace-plugin.ts, packages/shared/mui-icons-material-esm-replace-plugin.ts, packages/shared/next-js-esm-replace-plugin.ts, packages/shared/prism-react-renderer-theme-replace-plugin.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/inferencer/src/inferencers/antd/list.tsx:460— `field && (field.type === "text" || field.type === "number")` appears character-identically in 4 files — packages/inferencer/src/inferencers/antd/list.tsx, packages/inferencer/src/inferencers/chakra-ui/list.tsx, packages/inferencer/src/inferencers/mantine/list.tsx, packages/inferencer/src/inferencers/mui/list.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/inferencer/src/inferencers/chakra-ui/create.tsx:182— `field.type !== "date" && field.type !== "richtext"` appears character-identically in 6 files — packages/inferencer/src/inferencers/chakra-ui/create.tsx, packages/inferencer/src/inferencers/chakra-ui/edit.tsx, packages/inferencer/src/inferencers/headless/create.tsx, packages/inferencer/src/inferencers/headless/edit.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.
Silent fallback default in catch documentation/src/context/TutorialChecklistContext/index.tsx:30— `TutorialChecklistProvider` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch documentation/src/theme/BlogPostItems/index.js:30— `BlogPostItems` swallows every exception into `return "grid"` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/cli/src/utils/package/index.ts:89— `getInstalledRefinePackagesFromNodeModules` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/cli/src/utils/announcement/index.tsx:47— `getAnnouncements` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/create-refine-app/src/example/install-dependencies.ts:8— `findPM` swallows every exception into `return "npm"` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/devtools-internal/src/get-trace.ts:30— `getTrace` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/devtools-server/src/feed/get-feed.ts:50— `fetchFeed` swallows every exception into `return ""` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/devtools-server/src/feed/get-feed.ts:62— `getFeed` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/devtools-server/src/packages/get-all-packages.ts:25— `getAllPackages` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Disabled test cypress/e2e/auth-keycloak/all.cy.ts:4— 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 cypress/e2e/with-nextjs-next-auth/all.cy.ts:38— 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 cypress/e2e/with-remix-antd/all.cy.ts:8— 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 cypress/e2e/with-remix-material-ui/all.cy.ts:47— 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 cypress/e2e/with-remix-material-ui/all.cy.ts:71— 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 cypress/e2e/with-remix-material-ui/all.cy.ts:101— 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 packages/ui-tests/src/tests/buttons/refresh.tsx:95— 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 packages/ui-tests/src/tests/fields/boolean.tsx:10— 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 packages/core/README.md:38— packages/core/README.md links to `CODE_OF_CONDUCT.md`, but `packages/core/CODE_OF_CONDUCT.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/ui-tests/README.md:39— packages/ui-tests/README.md links to `CODE_OF_CONDUCT.md`, but `packages/ui-tests/CODE_OF_CONDUCT.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/ui-types/README.md:39— packages/ui-types/README.md links to `CODE_OF_CONDUCT.md`, but `packages/ui-types/CODE_OF_CONDUCT.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add vitest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 409 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 2 significant file(s) lose their only recent owner: packages/codemod/src/transformations/v5/mutation-result-to-mutation-property.ts, packages/codemod/src/transformations/v5/use-query-and-result-fields-in-useInfiniteList-hook.ts. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 2 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 (4 single-owned of 333 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; 333 of the 1284 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)), anonymized user #3 (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/codemod/src/transformations/v5/use-query-and-result-fields-in-list-hooks.ts, packages/refine-ui/registry/new-york/refine-ui/form/auto-save-indicator.tsx.
No ADRs found — 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/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 4 of 38 project(s) overshoot their size bounds, lowering Project Cohesion to 7.9/10. The most over is `documentation` (117706 LoC, 826 module-visible types across 209 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 54 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: packages/inferencer/src/inferencers/antd/edit.tsx, packages/inferencer/src/inferencers/headless/edit.tsx, packages/inferencer/src/inferencers/chakra-ui/edit.tsx, packages/core/src/hooks/form/index.ts, packages/inferencer/src/inferencers/headless/create.tsx, packages/refine-ui/registry/new-york/refine-ui/data-table/data-table.tsx, REDACTED, packages/refine-ui/registry/new-york/refine-ui/form/sign-in-form.tsx (and 46 more) (59 orphaned of 333 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; 333 of the 1284 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D40 · Network Egress Confinement· No network policy · ×1
No network policy — No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need.
GD1 · Unfinished & placeholder code· Placeholder literal left in code · ×1
Placeholder literal left in code packages/refine-ui/registry/new-york/refine-ui/form/sign-up-form.tsx:107— A placeholder string ("Welcome to lorem ipsum dolor.") is still in shipped code — typical of generated boilerplate that was never filled in.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 19909 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
R8 · Dependency Hygiene· Type-only dependency '@tanstack/react-query' in production deps · ×1
Type-only dependency '@tanstack/react-query' in production deps packages/antd/src/hooks/fields/useCheckboxGroup/index.ts:1— Every import is type-only — move it to devDependencies.
No security response headers detected packages/refine-ui/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.)
No app-layer HTTPS enforcement detected packages/devtools-server/src/setup-server.ts:55— `server.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−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/18 async functions that make a cancellable request (fetch, axios, ky, ofetch) 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 — 105/198 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Null assertions (`!`) reduce the strict null checking score — ~0.1 `!` null assertions per 1k TypeScript source lines — 12 assertion(s) across the 214821 source line(s) of the 1922 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/mantine/src/providers/notificationProvider.tsx (3), packages/react-router/src/document-title-handler.tsx (2), packages/codemod/src/transformations/v5/rename-current-to-currentPage.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Outdated (npm): @aliemir/dom-to-fiber-utils — @aliemir/dom-to-fiber-utils is pinned at 0.4.1; registry.npmjs.org publishes 0.5.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): @ant-design/cssinjs — @ant-design/cssinjs is pinned at 1.20.0; registry.npmjs.org publishes 2.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): @ant-design/graphs — @ant-design/graphs is pinned at 1.4.1; registry.npmjs.org publishes 2.1.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @ant-design/icons — @ant-design/icons is pinned at 5.5.1; registry.npmjs.org publishes 6.3.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @ant-design/nextjs-registry — @ant-design/nextjs-registry is pinned at 1.0.0; registry.npmjs.org publishes 1.3.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): @ant-design/plots — @ant-design/plots is pinned at 1.2.6; registry.npmjs.org publishes 2.6.8 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): @ant-design/pro-layout — @ant-design/pro-layout is pinned at 7.21.1; registry.npmjs.org publishes 7.22.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @auth0/auth0-react — @auth0/auth0-react is pinned at 1.12.1; registry.npmjs.org publishes 2.28.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): @cerbos/http — @cerbos/http is pinned at 0.6.0; registry.npmjs.org publishes 0.30.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): @chakra-ui/react — @chakra-ui/react is pinned at 2.8.2; registry.npmjs.org publishes 3.37.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): @chakra-ui/theme-tools — @chakra-ui/theme-tools is pinned at 2.1.2; registry.npmjs.org publishes 2.2.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): @codesandbox/sandpack-client — @codesandbox/sandpack-client is pinned at 2.13.8; registry.npmjs.org publishes 2.19.8 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): @codesandbox/sandpack-react — @codesandbox/sandpack-react is pinned at 2.13.8; registry.npmjs.org publishes 2.20.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): @dnd-kit/core — @dnd-kit/core is pinned at 6.1.0; registry.npmjs.org publishes 6.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @docsearch/react — @docsearch/react is pinned at 3.6.0; registry.npmjs.org publishes 5.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): @docusaurus/core — @docusaurus/core is pinned at 2.4.0; registry.npmjs.org publishes 3.10.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): @docusaurus/plugin-client-redirects — @docusaurus/plugin-client-redirects is pinned at 2.4.0; registry.npmjs.org publishes 3.10.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): @docusaurus/plugin-content-docs — @docusaurus/plugin-content-docs is pinned at 2.4.0; registry.npmjs.org publishes 3.10.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): @docusaurus/preset-classic — @docusaurus/preset-classic is pinned at 2.4.0; registry.npmjs.org publishes 3.10.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): @docusaurus/theme-classic — @docusaurus/theme-classic is pinned at 2.4.0; registry.npmjs.org publishes 3.10.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): @docusaurus/theme-common — @docusaurus/theme-common is pinned at 2.4.0; registry.npmjs.org publishes 3.10.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): @docusaurus/theme-search-algolia — @docusaurus/theme-search-algolia is pinned at 2.4.0; registry.npmjs.org publishes 3.10.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): @docusaurus/types — @docusaurus/types is pinned at 2.4.0; registry.npmjs.org publishes 3.10.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): @docusaurus/utils-common — @docusaurus/utils-common is pinned at 2.4.0; registry.npmjs.org publishes 3.10.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): @emotion/cache — @emotion/cache is pinned at 11.11.0; registry.npmjs.org publishes 11.14.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Off the main sequence: @refinedev/devtools-shared — @refinedev/devtools-shared: abstractness 0.00, instability 0.00, distance 1.00 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `packages/antd/src/hooks/form/useForm.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
runtime-hardening: not applicable — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
Run 01a17a07-50f7-7637-9372-83d3387fab53 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 418 · Warnings: 971 · Recommendations: 301 · Info: 187 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 21:04 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.